2 This document summarizes new features and bugfixes in each stable release
3 of Tor. If you want to see more detailed descriptions of the changes in
4 each development snapshot, see the ChangeLog file.
6 Changes in version 0.2.6.9 - 2015-06-11
7 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
8 requirements for receiving an HSDir flag, and addresses some other small
9 bugs in the systemd and sandbox code. Clients using circuit isolation
10 should upgrade; all directory authorities should upgrade.
12 o Major bugfixes (client-side privacy):
13 - Properly separate out each SOCKSPort when applying stream
14 isolation. The error occurred because each port's session group was
15 being overwritten by a default value when the listener connection
16 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
19 o Minor feature (directory authorities, security):
20 - The HSDir flag given by authorities now requires the Stable flag.
21 For the current network, this results in going from 2887 to 2806
22 HSDirs. Also, it makes it harder for an attacker to launch a sybil
23 attack by raising the effort for a relay to become Stable which
24 takes at the very least 7 days to do so and by keeping the 96
25 hours uptime requirement for HSDir. Implements ticket 8243.
27 o Minor bugfixes (compilation):
28 - Build with --enable-systemd correctly when libsystemd is
29 installed, but systemd is not. Fixes bug 16164; bugfix on
30 0.2.6.3-alpha. Patch from Peter Palfrader.
32 o Minor bugfixes (Linux seccomp2 sandbox):
33 - Fix sandboxing to work when running as a relaymby renaming of
34 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
35 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
36 - Allow systemd connections to work with the Linux seccomp2 sandbox
37 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
40 o Minor bugfixes (tests):
41 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
42 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
45 Changes in version 0.2.6.8 - 2015-05-21
46 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
47 fixes an authority-side bug in assigning the HSDir flag. All directory
48 authorities should upgrade.
50 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
51 - Revert commit that made directory authorities assign the HSDir
52 flag to relay without a DirPort; this was bad because such relays
53 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
56 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
57 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
58 a client authorized hidden service. Fixes bug 15823; bugfix
61 o Minor features (geoip):
62 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
63 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
67 Changes in version 0.2.6.7 - 2015-04-06
68 Tor 0.2.6.7 fixes two security issues that could be used by an
69 attacker to crash hidden services, or crash clients visiting hidden
70 services. Hidden services should upgrade as soon as possible; clients
71 should upgrade whenever packages become available.
73 This release also contains two simple improvements to make hidden
74 services a bit less vulnerable to denial-of-service attacks.
76 o Major bugfixes (security, hidden service):
77 - Fix an issue that would allow a malicious client to trigger an
78 assertion failure and halt a hidden service. Fixes bug 15600;
79 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
80 - Fix a bug that could cause a client to crash with an assertion
81 failure when parsing a malformed hidden service descriptor. Fixes
82 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
84 o Minor features (DoS-resistance, hidden service):
85 - Introduction points no longer allow multiple INTRODUCE1 cells to
86 arrive on the same circuit. This should make it more expensive for
87 attackers to overwhelm hidden services with introductions.
88 Resolves ticket 15515.
89 - Decrease the amount of reattempts that a hidden service performs
90 when its rendezvous circuits fail. This reduces the computational
91 cost for running a hidden service under heavy load. Resolves
95 Changes in version 0.2.6.6 - 2015-03-24
96 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
98 It adds numerous safety, security, correctness, and performance
99 improvements. Client programs can be configured to use more kinds of
100 sockets, AutomapHosts works better, the multithreading backend is
101 improved, cell transmission is refactored, test coverage is much
102 higher, more denial-of-service attacks are handled, guard selection is
103 improved to handle long-term guards better, pluggable transports
104 should work a bit better, and some annoying hidden service performance
105 bugs should be addressed.
107 o New compiler and system requirements:
108 - Tor 0.2.6.x requires that your compiler support more of the C99
109 language standard than before. The 'configure' script now detects
110 whether your compiler supports C99 mid-block declarations and
111 designated initializers. If it does not, Tor will not compile.
113 We may revisit this requirement if it turns out that a significant
114 number of people need to build Tor with compilers that don't
115 bother implementing a 15-year-old standard. Closes ticket 13233.
116 - Tor no longer supports systems without threading support. When we
117 began working on Tor, there were several systems that didn't have
118 threads, or where the thread support wasn't able to run the
119 threads of a single process on multiple CPUs. That no longer
120 holds: every system where Tor needs to run well now has threading
121 support. Resolves ticket 12439.
123 o Deprecated versions and removed support:
124 - Tor relays older than 0.2.4.18-rc are no longer allowed to
125 advertise themselves on the network. Closes ticket 13555.
126 - Tor clients no longer support connecting to hidden services
127 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
128 option has been removed. (There shouldn't be any hidden services
129 running these versions on the network.) Closes ticket 7803.
131 o Directory authority changes:
132 - The directory authority Faravahar has a new IP address. This
134 - Remove turtles as a directory authority.
135 - Add longclaw as a new (v3) directory authority. This implements
136 ticket 13296. This keeps the directory authority count at 9.
138 o Major features (bridges):
139 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
140 transports if they are configured via the "TOR_PT_PROXY"
141 environment variable. Implements proposal 232. Resolves
144 o Major features (changed defaults):
145 - Prevent relay operators from unintentionally running exits: When a
146 relay is configured as an exit node, we now warn the user unless
147 the "ExitRelay" option is set to 1. We warn even more loudly if
148 the relay is configured with the default exit policy, since this
149 can indicate accidental misconfiguration. Setting "ExitRelay 0"
150 stops Tor from running as an exit relay. Closes ticket 10067.
152 o Major features (client performance, hidden services):
153 - Allow clients to use optimistic data when connecting to a hidden
154 service, which should remove a round-trip from hidden service
155 initialization. See proposal 181 for details. Implements
158 o Major features (directory system):
159 - Upon receiving an unparseable directory object, if its digest
160 matches what we expected, then don't try to download it again.
161 Previously, when we got a descriptor we didn't like, we would keep
162 trying to download it over and over. Closes ticket 11243.
163 - When downloading server- or microdescriptors from a directory
164 server, we no longer launch multiple simultaneous requests to the
165 same server. This reduces load on the directory servers,
166 especially when directory guards are in use. Closes ticket 9969.
167 - When downloading server- or microdescriptors over a tunneled
168 connection, do not limit the length of our requests to what the
169 Squid proxy is willing to handle. Part of ticket 9969.
170 - Authorities can now vote on the correct digests and latest
171 versions for different software packages. This allows packages
172 that include Tor to use the Tor authority system as a way to get
173 notified of updates and their correct digests. Implements proposal
174 227. Closes ticket 10395.
176 o Major features (guards):
177 - Introduce the Guardfraction feature to improves load balancing on
178 guard nodes. Specifically, it aims to reduce the traffic gap that
179 guard nodes experience when they first get the Guard flag. This is
180 a required step if we want to increase the guard lifetime to 9
181 months or greater. Closes ticket 9321.
183 o Major features (hidden services):
184 - Make HS port scanning more difficult by immediately closing the
185 circuit when a user attempts to connect to a nonexistent port.
187 - Add a HiddenServiceStatistics option that allows Tor relays to
188 gather and publish statistics about the overall size and volume of
189 hidden service usage. Specifically, when this option is turned on,
190 an HSDir will publish an approximate number of hidden services
191 that have published descriptors to it the past 24 hours. Also, if
192 a relay has acted as a hidden service rendezvous point, it will
193 publish the approximate amount of rendezvous cells it has relayed
194 the past 24 hours. The statistics themselves are obfuscated so
195 that the exact values cannot be derived. For more details see
196 proposal 238, "Better hidden service stats from Tor relays". This
197 feature is currently disabled by default. Implements feature 13192.
199 o Major features (performance):
200 - Make the CPU worker implementation more efficient by avoiding the
201 kernel and lengthening pipelines. The original implementation used
202 sockets to transfer data from the main thread to the workers, and
203 didn't allow any thread to be assigned more than a single piece of
204 work at once. The new implementation avoids communications
205 overhead by making requests in shared memory, avoiding kernel IO
206 where possible, and keeping more requests in flight at once.
207 Implements ticket 9682.
209 o Major features (relay):
210 - Raise the minimum acceptable configured bandwidth rate for bridges
211 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
212 20 KiB/sec.) Closes ticket 13822.
213 - Complete revision of the code that relays use to decide which cell
214 to send next. Formerly, we selected the best circuit to write on
215 each channel, but we didn't select among channels in any
216 sophisticated way. Now, we choose the best circuits globally from
217 among those whose channels are ready to deliver traffic.
219 This patch implements a new inter-cmux comparison API, a global
220 high/low watermark mechanism and a global scheduler loop for
221 transmission prioritization across all channels as well as among
222 circuits on one channel. This schedule is currently tuned to
223 (tolerantly) avoid making changes in network performance, but it
224 should form the basis for major circuit performance increases in
225 the future. Code by Andrea; tuning by Rob Jansen; implements
228 o Major features (sample torrc):
229 - Add a new, infrequently-changed "torrc.minimal". This file is
230 similar to torrc.sample, but it will change as infrequently as
231 possible, for the benefit of users whose systems prompt them for
232 intervention whenever a default configuration file is changed.
233 Making this change allows us to update torrc.sample to be a more
234 generally useful "sample torrc".
236 o Major features (security, unix domain sockets):
237 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
238 applications can reach Tor without having to create AF_INET or
239 AF_INET6 sockets, meaning they can completely disable their
240 ability to make non-Tor network connections. To create a socket of
241 this type, use "SocksPort unix:/path/to/socket". Implements
243 - Support mapping hidden service virtual ports to AF_UNIX sockets.
244 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
245 Implements ticket 11485.
247 o Major bugfixes (client, automap):
248 - Repair automapping with IPv6 addresses. This automapping should
249 have worked previously, but one piece of debugging code that we
250 inserted to detect a regression actually caused the regression to
251 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
252 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
255 o Major bugfixes (crash, OSX, security):
256 - Fix a remote denial-of-service opportunity caused by a bug in
257 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
260 o Major bugfixes (directory authorities):
261 - Do not assign the HSDir flag to relays if they are not Valid, or
262 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
264 o Major bugfixes (directory bandwidth performance):
265 - Don't flush the zlib buffer aggressively when compressing
266 directory information for clients. This should save about 7% of
267 the bandwidth currently used for compressed descriptors and
268 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
270 o Major bugfixes (exit node stability):
271 - Fix an assertion failure that could occur under high DNS load.
272 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
273 diagnosed and fixed by "cypherpunks".
275 o Major bugfixes (FreeBSD IPFW transparent proxy):
276 - Fix address detection with FreeBSD transparent proxies, when
277 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
280 o Major bugfixes (hidden services):
281 - When closing an introduction circuit that was opened in parallel
282 with others, don't mark the introduction point as unreachable.
283 Previously, the first successful connection to an introduction
284 point would make the other introduction points get marked as
285 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
287 o Major bugfixes (Linux seccomp2 sandbox):
288 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
289 crash during attempts to call wait4. Fixes bug 15088; bugfix on
290 0.2.5.1-alpha. Patch from "sanic".
292 o Major bugfixes (mixed relay-client operation):
293 - When running as a relay and client at the same time (not
294 recommended), if we decide not to use a new guard because we want
295 to retry older guards, only close the locally-originating circuits
296 passing through that guard. Previously we would close all the
297 circuits through that guard. Fixes bug 9819; bugfix on
298 0.2.1.1-alpha. Reported by "skruffy".
300 o Major bugfixes (pluggable transports):
301 - Initialize the extended OR Port authentication cookie before
302 launching pluggable transports. This prevents a race condition
303 that occured when server-side pluggable transports would cache the
304 authentication cookie before it has been (re)generated. Fixes bug
305 15240; bugfix on 0.2.5.1-alpha.
307 o Major bugfixes (relay, stability, possible security):
308 - Fix a bug that could lead to a relay crashing with an assertion
309 failure if a buffer of exactly the wrong layout is passed to
310 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
311 0.2.0.10-alpha. Patch from "cypherpunks".
312 - Do not assert if the 'data' pointer on a buffer is advanced to the
313 very end of the buffer; log a BUG message instead. Only assert if
314 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
316 o Minor features (build):
317 - New --disable-system-torrc compile-time option to prevent Tor from
318 looking for the system-wide torrc or torrc-defaults files.
319 Resolves ticket 13037.
321 o Minor features (client):
322 - Clients are now willing to send optimistic data (before they
323 receive a 'connected' cell) to relays of any version. (Relays
324 without support for optimistic data are no longer supported on the
325 Tor network.) Resolves ticket 13153.
327 o Minor features (client):
328 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
329 is enabled, reject requests with IP addresses as hostnames.
330 Resolves ticket 13315.
332 o Minor features (controller):
333 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
334 write an unscheduled heartbeat message to the log. Implements
336 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
337 events so controllers can observe circuit isolation inputs. Closes
339 - ControlPort now supports the unix:/path/to/socket syntax as an
340 alternative to the ControlSocket option, for consistency with
341 SocksPort and HiddenServicePort. Closes ticket 14451.
342 - New "GETINFO bw-event-cache" to get information about recent
343 bandwidth events. Closes ticket 14128. Useful for controllers to
344 get recent bandwidth history after the fix for ticket 13988.
345 - Messages about problems in the bootstrap process now include
346 information about the server we were trying to connect to when we
347 noticed the problem. Closes ticket 15006.
349 o Minor features (Denial of service resistance):
350 - Count the total number of bytes used storing hidden service
351 descriptors against the value of MaxMemInQueues. If we're low on
352 memory, and more than 20% of our memory is used holding hidden
353 service descriptors, free them until no more than 10% of our
354 memory holds hidden service descriptors. Free the least recently
355 fetched descriptors first. Resolves ticket 13806.
356 - When we have recently been under memory pressure (over 3/4 of
357 MaxMemInQueues is allocated), then allocate smaller zlib objects
358 for small requests. Closes ticket 11791.
360 o Minor features (directory authorities):
361 - Don't list relays with a bandwidth estimate of 0 in the consensus.
362 Implements a feature proposed during discussion of bug 13000.
363 - In tor-gencert, report an error if the user provides the same
364 argument more than once.
365 - If a directory authority can't find a best consensus method in the
366 votes that it holds, it now falls back to its favorite consensus
367 method. Previously, it fell back to method 1. Neither of these is
368 likely to get enough signatures, but "fall back to favorite"
369 doesn't require us to maintain support an obsolete consensus
370 method. Implements part of proposal 215.
372 o Minor features (geoip):
373 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
374 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
377 o Minor features (guard nodes):
378 - Reduce the time delay before saving guard status to disk from 10
379 minutes to 30 seconds (or from one hour to 10 minutes if
380 AvoidDiskWrites is set). Closes ticket 12485.
382 o Minor features (heartbeat):
383 - On relays, report how many connections we negotiated using each
384 version of the Tor link protocols. This information will let us
385 know if removing support for very old versions of the Tor
386 protocols is harming the network. Closes ticket 15212.
388 o Minor features (hidden service):
389 - Make Sybil attacks against hidden services harder by changing the
390 minimum time required to get the HSDir flag from 25 hours up to 96
391 hours. Addresses ticket 14149.
392 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
393 services to disable the anti-scanning feature introduced in
394 0.2.6.2-alpha. With this option not set, a connection to an
395 unlisted port closes the circuit. With this option set, only a
396 RELAY_DONE cell is sent. Closes ticket 14084.
397 - When re-enabling the network, don't try to build introduction
398 circuits until we have successfully built a circuit. This makes
399 hidden services come up faster when the network is re-enabled.
400 Patch from "akwizgran". Closes ticket 13447.
401 - When we fail to retrieve a hidden service descriptor, send the
402 controller an "HS_DESC FAILED" controller event. Implements
404 - New HiddenServiceDirGroupReadable option to cause hidden service
405 directories and hostname files to be created group-readable. Patch
406 from "anon", David Stainton, and "meejah". Closes ticket 11291.
408 o Minor features (interface):
409 - Implement "-f -" command-line option to read torrc configuration
410 from standard input, if you don't want to store the torrc file in
411 the file system. Implements feature 13865.
413 o Minor features (logging):
414 - Add a count of unique clients to the bridge heartbeat message.
415 Resolves ticket 6852.
416 - Suppress "router info incompatible with extra info" message when
417 reading extrainfo documents from cache. (This message got loud
418 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
420 - Elevate hidden service authorized-client message from DEBUG to
421 INFO. Closes ticket 14015.
422 - On Unix-like systems, you can now use named pipes as the target of
423 the Log option, and other options that try to append to files.
424 Closes ticket 12061. Patch from "carlo von lynX".
425 - When opening a log file at startup, send it every log message that
426 we generated between startup and opening it. Previously, log
427 messages that were generated before opening the log file were only
428 logged to stdout. Closes ticket 6938.
429 - Add a TruncateLogFile option to overwrite logs instead of
430 appending to them. Closes ticket 5583.
431 - Quiet some log messages in the heartbeat and at startup. Closes
434 o Minor features (portability, Solaris):
435 - Threads are no longer disabled by default on Solaris; we believe
436 that the versions of Solaris with broken threading support are all
437 obsolete by now. Resolves ticket 9495.
439 o Minor features (relay):
440 - Re-check our address after we detect a changed IP address from
441 getsockname(). This ensures that the controller command "GETINFO
442 address" will report the correct value. Resolves ticket 11582.
444 - A new AccountingRule option lets Relays set whether they'd like
445 AccountingMax to be applied separately to inbound and outbound
446 traffic, or applied to the sum of inbound and outbound traffic.
447 Resolves ticket 961. Patch by "chobe".
448 - When identity keypair is generated for first time, log a
449 congratulatory message that links to the new relay lifecycle
450 document. Implements feature 10427.
452 o Minor features (security, memory wiping):
453 - Ensure we securely wipe keys from memory after
454 crypto_digest_get_digest and init_curve25519_keypair_from_file
455 have finished using them. Resolves ticket 13477.
457 o Minor features (security, out-of-memory handling):
458 - When handling an out-of-memory condition, allocate less memory for
459 temporary data structures. Fixes issue 10115.
460 - When handling an out-of-memory condition, consider more types of
461 buffers, including those on directory connections, and zlib
462 buffers. Resolves ticket 11792.
464 o Minor features (stability):
465 - Add assertions in our hash-table iteration code to check for
466 corrupted values that could cause infinite loops. Closes
469 o Minor features (systemd):
470 - Various improvements and modernizations in systemd hardening
471 support. Closes ticket 13805. Patch from Craig Andrews.
472 - Where supported, when running with systemd, report successful
473 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
474 - When running with systemd, support systemd watchdog messages. Part
475 of ticket 11016. Patch by Michael Scherer.
477 o Minor features (testing networks):
478 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
479 the "Exit" flag regardless of their uptime, bandwidth, or exit
480 policy. TestingTorNetwork must be set for this option to have any
481 effect. Previously, authorities would take up to 35 minutes to
482 give nodes the Exit flag in a test network. Partially implements
484 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
485 and the default on a testing network to 2 minutes. Drop the
486 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
487 keep the default on a testing network at 30 seconds. This reduces
488 HS bootstrap time to around 25 seconds. Also, change the default
489 time in test-network.sh to match. Closes ticket 13401. Patch
491 - Create TestingDirAuthVoteHSDir to correspond to
492 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
493 HSDir flag for the listed relays regardless of uptime or ORPort
494 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
495 Partial implementation for ticket 14067. Patch by "teor".
497 o Minor features (tor2web mode):
498 - Introduce the config option Tor2webRendezvousPoints, which allows
499 clients in Tor2webMode to select a specific Rendezvous Point to be
500 used in HS circuits. This might allow better performance for
501 Tor2Web nodes. Implements ticket 12844.
503 o Minor features (transparent proxy):
504 - Update the transparent proxy option checks to allow for both ipfw
505 and pf on OS X. Closes ticket 14002.
506 - Use the correct option when using IPv6 with transparent proxy
507 support on Linux. Resolves 13808. Patch by Francisco Blas
510 o Minor features (validation):
511 - Check all date/time values passed to tor_timegm and
512 parse_rfc1123_time for validity, taking leap years into account.
513 Improves HTTP header validation. Implemented with bug 13476.
514 - In correct_tm(), limit the range of values returned by system
515 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
516 This means we don't have to deal with negative or too large dates,
517 even if a clock is wrong. Otherwise we might fail to read a file
518 written by us which includes such a date. Fixes bug 13476.
519 - Stop allowing invalid address patterns like "*/24" that contain
520 both a wildcard address and a bit prefix length. This affects all
521 our address-range parsing code. Fixes bug 7484; bugfix
524 o Minor bugfixes (bridge clients):
525 - When configured to use a bridge without an identity digest (not
526 recommended), avoid launching an extra channel to it when
527 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
529 o Minor bugfixes (bridges):
530 - When DisableNetwork is set, do not launch pluggable transport
531 plugins, and if any are running, terminate them. Fixes bug 13213;
532 bugfix on 0.2.3.6-alpha.
534 o Minor bugfixes (C correctness):
535 - Fix several instances of possible integer overflow/underflow/NaN.
536 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
538 - In circuit_build_times_calculate_timeout() in circuitstats.c,
539 avoid dividing by zero in the pareto calculations. This traps
540 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
542 - Fix an integer overflow in format_time_interval(). Fixes bug
543 13393; bugfix on 0.2.0.10-alpha.
544 - Set the correct day of year value when the system's localtime(_r)
545 or gmtime(_r) functions fail to set struct tm. Not externally
546 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
547 - Avoid unlikely signed integer overflow in tor_timegm on systems
548 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
550 o Minor bugfixes (certificate handling):
551 - If an authority operator accidentally makes a signing certificate
552 with a future publication time, do not discard its real signing
553 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
554 - Remove any old authority certificates that have been superseded
555 for at least two days. Previously, we would keep superseded
556 certificates until they expired, if they were published close in
557 time to the certificate that superseded them. Fixes bug 11454;
558 bugfix on 0.2.1.8-alpha.
560 o Minor bugfixes (client):
561 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
562 BadExit flag are not considered worthy candidates. Fixes bug
563 13066; bugfix on 0.1.2.3-alpha.
564 - Use the consensus schedule for downloading consensuses, and not
565 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
566 - Handle unsupported or malformed SOCKS5 requests properly by
567 responding with the appropriate error message before closing the
568 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
570 o Minor bugfixes (client, automapping):
571 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
572 no value follows the option. Fixes bug 14142; bugfix on
573 0.2.4.7-alpha. Patch by "teor".
574 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
575 14195; bugfix on 0.1.0.1-rc.
576 - Prevent changes to other options from removing the wildcard value
577 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
579 - Allow MapAddress and AutomapHostsOnResolve to work together when
580 an address is mapped into another address type (like .onion) that
581 must be automapped at resolve time. Fixes bug 7555; bugfix
584 o Minor bugfixes (client, bridges):
585 - When we are using bridges and we had a network connectivity
586 problem, only retry connecting to our currently configured
587 bridges, not all bridges we know about and remember using. Fixes
588 bug 14216; bugfix on 0.2.2.17-alpha.
590 o Minor bugfixes (client, DNS):
591 - Report the correct cached DNS expiration times on SOCKS port or in
592 DNS replies. Previously, we would report everything as "never
593 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
594 - Avoid a small memory leak when we find a cached answer for a
595 reverse DNS lookup in a client-side DNS cache. (Remember, client-
596 side DNS caching is off by default, and is not recommended.) Fixes
597 bug 14259; bugfix on 0.2.0.1-alpha.
599 o Minor bugfixes (client, IPv6):
600 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
601 flag is not set; and not because the NoIPv4Traffic flag was set.
602 Previously we'd looked at the NoIPv4Traffic flag for both types of
603 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
605 o Minor bugfixes (client, microdescriptors):
606 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
607 computing which microdescriptors to download. This keeps us from
608 erroneous download behavior if two microdescriptor digests ever
609 have the same first 160 bits. Fixes part of bug 13399; bugfix
611 - Reset a router's status if its microdescriptor digest changes,
612 even if the first 160 bits remain the same. Fixes part of bug
613 13399; bugfix on 0.2.3.1-alpha.
615 o Minor bugfixes (client, torrc):
616 - Stop modifying the value of our DirReqStatistics torrc option just
617 because we're not a bridge or relay. This bug was causing Tor
618 Browser users to write "DirReqStatistics 0" in their torrc files
619 as if they had chosen to change the config. Fixes bug 4244; bugfix
621 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
622 that our options have changed every time we SIGHUP. Fixes bug
623 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
625 o Minor bugfixes (compilation):
626 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
628 - Silence clang warnings under --enable-expensive-hardening,
629 including implicit truncation of 64 bit values to 32 bit, const
630 char assignment to self, tautological compare, and additional
631 parentheses around equality tests. Fixes bug 13577; bugfix
633 - Fix a clang warning about checking whether an address in the
634 middle of a structure is NULL. Fixes bug 14001; bugfix
636 - The address of an array in the middle of a structure will always
637 be non-NULL. clang recognises this and complains. Disable the
638 tautologous and redundant check to silence this warning. Fixes bug
639 14001; bugfix on 0.2.1.2-alpha.
640 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
641 Addresses ticket 14188.
642 - Build without warnings with the stock OpenSSL srtp.h header, which
643 has a duplicate declaration of SSL_get_selected_srtp_profile().
644 Fixes bug 14220; this is OpenSSL's bug, not ours.
645 - Do not compile any code related to Tor2Web mode when Tor2Web mode
646 is not enabled at compile time. Previously, this code was included
647 in a disabled state. See discussion on ticket 12844.
648 - Allow our configure script to build correctly with autoconf 2.62
649 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
650 - Improve the error message from ./configure to make it clear that
651 when asciidoc has not been found, the user will have to either add
652 --disable-asciidoc argument or install asciidoc. Resolves
655 o Minor bugfixes (controller):
656 - Report "down" in response to the "GETINFO entry-guards" command
657 when relays are down with an unreachable_since value. Previously,
658 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
659 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
660 14116; bugfix on 0.2.2.9-alpha.
662 o Minor bugfixes (controller):
663 - Return an error when the second or later arguments of the
664 "setevents" controller command are invalid events. Previously we
665 would return success while silently skipping invalid events. Fixes
666 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
668 o Minor bugfixes (directory authority):
669 - Allow directory authorities to fetch more data from one another if
670 they find themselves missing lots of votes. Previously, they had
671 been bumping against the 10 MB queued data limit. Fixes bug 14261;
672 bugfix on 0.1.2.5-alpha.
673 - Do not attempt to download extrainfo documents which we will be
674 unable to validate with a matching server descriptor. Fixes bug
675 13762; bugfix on 0.2.0.1-alpha.
676 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
677 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
678 - Enlarge the buffer to read bwauth generated files to avoid an
679 issue when parsing the file in dirserv_read_measured_bandwidths().
680 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
681 - When running as a v3 directory authority, advertise that you serve
682 extra-info documents so that clients who want them can find them
683 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
685 o Minor bugfixes (directory system):
686 - Always believe that v3 directory authorities serve extra-info
687 documents, whether they advertise "caches-extra-info" or not.
688 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
689 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
690 Previously, directories offering BRIDGE_DIRINFO and some other
691 flag (i.e. microdescriptors or extrainfo) would be ignored when
692 looking for bridges. Partially fixes bug 13163; bugfix
695 o Minor bugfixes (file handling):
696 - Stop failing when key files are zero-length. Instead, generate new
697 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
698 on all versions of Tor. Patch by "teor".
699 - Stop generating a fresh .old RSA onion key file when the .old file
700 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
701 - Avoid overwriting .old key files with empty key files.
702 - Skip loading zero-length extrainfo store, router store, stats,
703 state, and key files.
704 - Avoid crashing when trying to reload a torrc specified as a
705 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
708 o Minor bugfixes (hidden services):
709 - Close the introduction circuit when we have no more usable intro
710 points, instead of waiting for it to time out. This also ensures
711 that no follow-up HS descriptor fetch is triggered when the
712 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
713 - When fetching a hidden service descriptor for a down service that
714 was recently up, do not keep refetching until we try the same
715 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
716 - Correctly send a controller event when we find that a rendezvous
717 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
718 - Pre-check directory permissions for new hidden-services to avoid
719 at least one case of "Bug: Acting on config options left us in a
720 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
721 - When fetching hidden service descriptors, we now check not only
722 for whether we got the hidden service we had in mind, but also
723 whether we got the particular descriptors we wanted. This prevents
724 a class of inefficient but annoying DoS attacks by hidden service
725 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
728 o Minor bugfixes (Linux seccomp2 sandbox):
729 - Make transparent proxy support work along with the seccomp2
730 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
731 by Francisco Blas Izquierdo Riera.
732 - Fix a memory leak in tor-resolve when running with the sandbox
733 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
734 - Allow glibc fatal errors to be sent to stderr before Tor exits.
735 Previously, glibc would try to write them to /dev/tty, and the
736 sandbox would trap the call and make Tor exit prematurely. Fixes
737 bug 14759; bugfix on 0.2.5.1-alpha.
739 o Minor bugfixes (logging):
740 - Avoid crashing when there are more log domains than entries in
741 domain_list. Bugfix on 0.2.3.1-alpha.
742 - Downgrade warnings about RSA signature failures to info log level.
743 Emit a warning when an extra info document is found incompatible
744 with a corresponding router descriptor. Fixes bug 9812; bugfix
746 - Make connection_ap_handshake_attach_circuit() log the circuit ID
747 correctly. Fixes bug 13701; bugfix on 0.0.6.
749 o Minor bugfixes (networking):
750 - Check for orconns and use connection_or_close_for_error() rather
751 than connection_mark_for_close() directly in the getsockopt()
752 failure case of connection_handle_write_impl(). Fixes bug 11302;
753 bugfix on 0.2.4.4-alpha.
755 o Minor bugfixes (parsing):
756 - Stop accepting milliseconds (or other junk) at the end of
757 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
758 - Support two-number and three-number version numbers correctly, in
759 case we change the Tor versioning system in the future. Fixes bug
760 13661; bugfix on 0.0.8pre1.
762 o Minor bugfixes (portability):
763 - Fix the ioctl()-based network interface lookup code so that it
764 will work on systems that have variable-length struct ifreq, for
766 - Use the correct datatype in the SipHash-2-4 function to prevent
767 compilers from assuming any sort of alignment. Fixes bug 15436;
768 bugfix on 0.2.5.3-alpha.
770 o Minor bugfixes (preventative security, C safety):
771 - When reading a hexadecimal, base-32, or base-64 encoded value from
772 a string, always overwrite the whole output buffer. This prevents
773 some bugs where we would look at (but fortunately, not reveal)
774 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
776 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
777 just the part that's used. This makes it harder for data leak bugs
778 to occur in the event of other programming failures. Resolves
781 o Minor bugfixes (relay):
782 - When generating our family list, remove spaces from around the
783 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
784 - If our previous bandwidth estimate was 0 bytes, allow publishing a
785 new relay descriptor immediately. Fixes bug 13000; bugfix
788 o Minor bugfixes (shutdown):
789 - When shutting down, always call event_del() on lingering read or
790 write events before freeing them. Otherwise, we risk double-frees
791 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
794 o Minor bugfixes (small memory leaks):
795 - Avoid leaking memory when using IPv6 virtual address mappings.
796 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
799 o Minor bugfixes (statistics):
800 - Increase period over which bandwidth observations are aggregated
801 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
803 o Minor bugfixes (systemd support):
804 - Run correctly under systemd with the RunAsDaemon option set. Fixes
805 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
806 - Inform the systemd supervisor about more changes in the Tor
807 process status. Implements part of ticket 14141. Patch from
810 o Minor bugfixes (testing networks):
811 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
812 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
813 - Stop using the default authorities in networks which provide both
814 AlternateDirAuthority and AlternateBridgeAuthority. Partially
815 fixes bug 13163; bugfix on 0.2.0.13-alpha.
817 o Minor bugfixes (testing networks, fast startup):
818 - Allow Tor to build circuits using a consensus with no exits. If
819 the consensus has no exits (typical of a bootstrapping test
820 network), allow Tor to build circuits once enough descriptors have
821 been downloaded. This assists in bootstrapping a testing Tor
822 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
824 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
825 header to directory servers. This allows us to obtain consensuses
826 promptly when the consensus interval is very short. This assists
827 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
828 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
829 - Stop assuming that private addresses are local when checking
830 reachability in a TestingTorNetwork. Instead, when testing, assume
831 all OR connections are remote. (This is necessary due to many test
832 scenarios running all relays on localhost.) This assists in
833 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
834 0.1.0.1-rc. Patch by "teor".
835 - Avoid building exit circuits from a consensus with no exits. Now
836 thanks to our fix for 13718, we accept a no-exit network as not
837 wholly lost, but we need to remember not to try to build exit
838 circuits on it. Closes ticket 13814; patch by "teor".
839 - Stop requiring exits to have non-zero bandwithcapacity in a
840 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
841 ignore exit bandwidthcapacity. This assists in bootstrapping a
842 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
843 on 0.2.0.3-alpha. Patch by "teor".
844 - Add "internal" to some bootstrap statuses when no exits are
845 available. If the consensus does not contain Exits, Tor will only
846 build internal circuits. In this case, relevant statuses will
847 contain the word "internal" as indicated in the Tor control-
848 spec.txt. When bootstrap completes, Tor will be ready to build
849 internal circuits. If a future consensus contains Exits, exit
850 circuits may become available. Fixes part of bug 13718; bugfix on
851 0.2.4.10-alpha. Patch by "teor".
852 - Decrease minimum consensus interval to 10 seconds when
853 TestingTorNetwork is set, or 5 seconds for the first consensus.
854 Fix assumptions throughout the code that assume larger intervals.
855 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
857 - Avoid excluding guards from path building in minimal test
858 networks, when we're in a test network and excluding guards would
859 exclude all relays. This typically occurs in incredibly small tor
860 networks, and those using "TestingAuthVoteGuard *". Fixes part of
861 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
863 o Minor bugfixes (testing):
864 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
865 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
866 - Stop spawn test failures due to a race condition between the
867 SIGCHLD handler updating the process status, and the test reading
868 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
869 - Avoid passing an extra backslash when creating a temporary
870 directory for running the unit tests on Windows. Fixes bug 12392;
871 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
873 o Minor bugfixes (TLS):
874 - Check more thoroughly throughout the TLS code for possible
875 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
877 o Minor bugfixes (transparent proxy):
878 - Use getsockname, not getsockopt, to retrieve the address for a
879 TPROXY-redirected connection. Fixes bug 13796; bugfix
882 o Minor bugfixes (windows):
883 - Remove code to special-case handling of NTE_BAD_KEYSET when
884 acquiring windows CryptoAPI context. This error can't actually
885 occur for the parameters we're providing. Fixes bug 10816; bugfix
888 o Minor bugfixes (zlib):
889 - Avoid truncating a zlib stream when trying to finalize it with an
890 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
892 o Code simplification and refactoring:
893 - Change the entry_is_live() function to take named bitfield
894 elements instead of an unnamed list of booleans. Closes
896 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
897 Resolves ticket 12205.
898 - Use calloc and reallocarray functions instead of multiply-
899 then-malloc. This makes it less likely for us to fall victim to an
900 integer overflow attack when allocating. Resolves ticket 12855.
901 - Use the standard macro name SIZE_MAX, instead of our
903 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
904 functions which take them as arguments. Replace 0 with NO_DIRINFO
905 in a function call for clarity. Seeks to prevent future issues
907 - Avoid 4 null pointer errors under clang static analysis by using
908 tor_assert() to prove that the pointers aren't null. Fixes
910 - Rework the API of policies_parse_exit_policy() to use a bitmask to
911 represent parsing options, instead of a confusing mess of
912 booleans. Resolves ticket 8197.
913 - Introduce a helper function to parse ExitPolicy in
914 or_options_t structure.
915 - Move fields related to isolating and configuring client ports into
916 a shared structure. Previously, they were duplicated across
917 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
918 to copy them correctly had been the cause of at least one bug in
919 the past. Closes ticket 8546.
920 - Refactor the get_interface_addresses_raw() doom-function into
921 multiple smaller and simpler subfunctions. Cover the resulting
922 subfunctions with unit-tests. Fixes a significant portion of
924 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
925 only for version <= 0.2.2.24 which is now deprecated. Closes
927 - Remove a test for a long-defunct broken version-one
929 - Refactor main loop to extract the 'loop' part. This makes it
930 easier to run Tor under Shadow. Closes ticket 15176.
931 - Stop using can_complete_circuits as a global variable; access it
932 with a function instead.
933 - Avoid using operators directly as macro arguments: this lets us
934 apply coccinelle transformations to our codebase more directly.
936 - Combine the functions used to parse ClientTransportPlugin and
937 ServerTransportPlugin into a single function. Closes ticket 6456.
938 - Add inline functions and convenience macros for inspecting channel
939 state. Refactor the code to use convenience macros instead of
940 checking channel state directly. Fixes issue 7356.
941 - Document all members of was_router_added_t and rename
942 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
943 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
944 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
945 constant instead of hardcoded value. Fixes issue 13840.
946 - Refactor our generic strmap and digestmap types into a single
947 implementation, so that we can add a new digest256map
951 - Add a doc/TUNING document with tips for handling large numbers of
952 TCP connections when running busy Tor relay. Update the warning
953 message to point to this file when running out of sockets
954 operating system is allowing to use simultaneously. Resolves
956 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
957 for writing the OpenBSD-specific tips. Resolves ticket 13702.
958 - Make the tor-resolve documentation match its help string and its
959 options. Resolves part of ticket 14325.
960 - Log a more useful error message from tor-resolve when failing to
961 look up a hidden service address. Resolves part of ticket 14325.
962 - Document the bridge-authority-only 'networkstatus-bridges' file.
963 Closes ticket 13713; patch from "tom".
964 - Fix typo in PredictedPortsRelevanceTime option description in
965 manpage. Resolves issue 13707.
966 - Stop suggesting that users specify relays by nickname: it isn't a
967 good idea. Also, properly cross-reference how to specify relays in
968 all parts of manual documenting options that take a list of
969 relays. Closes ticket 13381.
970 - Clarify the HiddenServiceDir option description in manpage to make
971 it clear that relative paths are taken with respect to the current
972 working directory. Also clarify that this behavior is not
973 guaranteed to remain indefinitely. Fixes issue 13913.
975 o Distribution (systemd):
976 - systemd unit file: only allow tor to write to /var/lib/tor and
977 /var/log/tor. The rest of the filesystem is accessible for reading
978 only. Patch by intrigeri; resolves ticket 12751.
979 - systemd unit file: ensure that the process and all its children
980 can never gain new privileges. Patch by intrigeri; resolves
982 - systemd unit file: set up /var/run/tor as writable for the Tor
983 service. Patch by intrigeri; resolves ticket 13196.
985 o Downgraded warnings:
986 - Don't warn when we've attempted to contact a relay using the wrong
987 ntor onion key. Closes ticket 9635.
990 - Remove some lingering dead code that once supported mempools.
991 Mempools were disabled by default in 0.2.5, and removed entirely
992 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
995 o Removed features (directory authorities):
996 - Remove code that prevented authorities from listing Tor relays
997 affected by CVE-2011-2769 as guards. These relays are already
998 rejected altogether due to the minimum version requirement of
999 0.2.3.16-alpha. Closes ticket 13152.
1000 - The "AuthDirRejectUnlisted" option no longer has any effect, as
1001 the fingerprints file (approved-routers) has been deprecated.
1002 - Directory authorities do not support being Naming dirauths anymore.
1003 The "NamingAuthoritativeDir" config option is now obsolete.
1004 - Directory authorities do not support giving out the BadDirectory
1006 - Directory authorities no longer advertise or support consensus
1007 methods 1 through 12 inclusive. These consensus methods were
1008 obsolete and/or insecure: maintaining the ability to support them
1009 served no good purpose. Implements part of proposal 215; closes
1013 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
1014 longer silently accepted as an alias for "ExitNodes".
1015 - The --enable-mempool and --enable-buf-freelists options, which
1016 were originally created to work around bad malloc implementations,
1017 no longer exist. They were off-by-default in 0.2.5. Closes
1019 - We no longer remind the user about configuration options that have
1020 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
1021 - Remove our old, non-weighted bandwidth-based node selection code.
1022 Previously, we used it as a fallback when we couldn't perform
1023 weighted bandwidth-based node selection. But that would only
1024 happen in the cases where we had no consensus, or when we had a
1025 consensus generated by buggy or ancient directory authorities. In
1026 either case, it's better to use the more modern, better maintained
1027 algorithm, with reasonable defaults for the weights. Closes
1029 - Remove the --disable-curve25519 configure option. Relays and
1030 clients now are required to support curve25519 and the
1032 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
1033 used to be deprecated synonyms for "StrictNodes", are now marked
1034 obsolete. Resolves ticket 12226.
1035 - Clients don't understand the BadDirectory flag in the consensus
1036 anymore, and ignore it.
1038 o Removed platform support:
1039 - We no longer include special code to build on Windows CE; as far
1040 as we know, nobody has used Tor on Windows CE in a very long time.
1041 Closes ticket 11446.
1043 o Testing (test-network.sh):
1044 - Stop using "echo -n", as some shells' built-in echo doesn't
1045 support "-n". Instead, use "/bin/echo -n". Partially fixes
1047 - Stop an apparent test-network hang when used with make -j2. Fixes
1049 - Add a --delay option to test-network.sh, which configures the
1050 delay before the chutney network tests for data transmission.
1051 Partially implements ticket 13161.
1054 - Test that tor does not fail when key files are zero-length. Check
1055 that tor generates new keys, and overwrites the empty key files.
1056 - Test that tor generates new keys when keys are missing
1057 (existing behavior).
1058 - Test that tor does not overwrite key files that already contain
1059 data (existing behavior). Tests bug 13111. Patch by "teor".
1060 - New "make test-stem" target to run stem integration tests.
1061 Requires that the "STEM_SOURCE_DIR" environment variable be set.
1062 Closes ticket 14107.
1063 - Make the test_cmdline_args.py script work correctly on Windows.
1064 Patch from Gisle Vanem.
1065 - Move the slower unit tests into a new "./src/test/test-slow"
1066 binary that can be run independently of the other tests. Closes
1068 - New tests for many parts of channel, relay, and circuitmux
1069 functionality. Code by Andrea; part of 9262.
1070 - New tests for parse_transport_line(). Part of ticket 6456.
1071 - In the unit tests, use chgrp() to change the group of the unit
1072 test temporary directory to the current user, so that the sticky
1073 bit doesn't interfere with tests that check directory groups.
1075 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
1077 - Refactor the function that chooses guard nodes so that it can more
1078 easily be tested; write some tests for it.
1079 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
1080 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
1081 - Create unit tests for format_time_interval(). With bug 13393.
1082 - Add unit tests for tor_timegm signed overflow, tor_timegm and
1083 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
1084 tests (visible) fixes in bug 13476.
1085 - Add a "coverage-html" make target to generate HTML-visualized
1086 coverage results when building with --enable-coverage. (Requires
1087 lcov.) Patch from Kevin Murray.
1088 - Enable the backtrace handler (where supported) when running the
1090 - Revise all unit tests that used the legacy test_* macros to
1091 instead use the recommended tt_* macros. This patch was generated
1092 with coccinelle, to avoid manual errors. Closes ticket 13119.
1094 Changes in version 0.2.5.11 - 2015-03-17
1095 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
1097 It backports several bugfixes from the 0.2.6 branch, including a
1098 couple of medium-level security fixes for relays and exit nodes.
1099 It also updates the list of directory authorities.
1101 o Directory authority changes:
1102 - Remove turtles as a directory authority.
1103 - Add longclaw as a new (v3) directory authority. This implements
1104 ticket 13296. This keeps the directory authority count at 9.
1105 - The directory authority Faravahar has a new IP address. This
1106 closes ticket 14487.
1108 o Major bugfixes (crash, OSX, security):
1109 - Fix a remote denial-of-service opportunity caused by a bug in
1110 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
1113 o Major bugfixes (relay, stability, possible security):
1114 - Fix a bug that could lead to a relay crashing with an assertion
1115 failure if a buffer of exactly the wrong layout was passed to
1116 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
1117 0.2.0.10-alpha. Patch from 'cypherpunks'.
1118 - Do not assert if the 'data' pointer on a buffer is advanced to the
1119 very end of the buffer; log a BUG message instead. Only assert if
1120 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
1122 o Major bugfixes (exit node stability):
1123 - Fix an assertion failure that could occur under high DNS load.
1124 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
1125 diagnosed and fixed by "cypherpunks".
1127 o Major bugfixes (Linux seccomp2 sandbox):
1128 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
1129 crash during attempts to call wait4. Fixes bug 15088; bugfix on
1130 0.2.5.1-alpha. Patch from "sanic".
1132 o Minor features (controller):
1133 - New "GETINFO bw-event-cache" to get information about recent
1134 bandwidth events. Closes ticket 14128. Useful for controllers to
1135 get recent bandwidth history after the fix for ticket 13988.
1137 o Minor features (geoip):
1138 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1139 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1142 o Minor bugfixes (client, automapping):
1143 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
1144 no value follows the option. Fixes bug 14142; bugfix on
1145 0.2.4.7-alpha. Patch by "teor".
1146 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
1147 14195; bugfix on 0.1.0.1-rc.
1149 o Minor bugfixes (compilation):
1150 - Build without warnings with the stock OpenSSL srtp.h header, which
1151 has a duplicate declaration of SSL_get_selected_srtp_profile().
1152 Fixes bug 14220; this is OpenSSL's bug, not ours.
1154 o Minor bugfixes (directory authority):
1155 - Allow directory authorities to fetch more data from one another if
1156 they find themselves missing lots of votes. Previously, they had
1157 been bumping against the 10 MB queued data limit. Fixes bug 14261;
1158 bugfix on 0.1.2.5-alpha.
1159 - Enlarge the buffer to read bwauth generated files to avoid an
1160 issue when parsing the file in dirserv_read_measured_bandwidths().
1161 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
1163 o Minor bugfixes (statistics):
1164 - Increase period over which bandwidth observations are aggregated
1165 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
1167 o Minor bugfixes (preventative security, C safety):
1168 - When reading a hexadecimal, base-32, or base-64 encoded value from
1169 a string, always overwrite the whole output buffer. This prevents
1170 some bugs where we would look at (but fortunately, not reveal)
1171 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
1175 Changes in version 0.2.4.26 - 2015-03-17
1176 Tor 0.2.4.26 includes an updated list of directory authorities. It
1177 also backports a couple of stability and security bugfixes from 0.2.5
1180 o Directory authority changes:
1181 - Remove turtles as a directory authority.
1182 - Add longclaw as a new (v3) directory authority. This implements
1183 ticket 13296. This keeps the directory authority count at 9.
1184 - The directory authority Faravahar has a new IP address. This
1185 closes ticket 14487.
1187 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
1188 - Fix an assertion failure that could occur under high DNS load.
1189 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
1190 diagnosed and fixed by "cypherpunks".
1192 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
1193 - Fix a bug that could lead to a relay crashing with an assertion
1194 failure if a buffer of exactly the wrong layout was passed to
1195 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
1196 0.2.0.10-alpha. Patch from 'cypherpunks'.
1197 - Do not assert if the 'data' pointer on a buffer is advanced to the
1198 very end of the buffer; log a BUG message instead. Only assert if
1199 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
1201 o Minor features (geoip):
1202 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1203 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1207 Changes in version 0.2.5.10 - 2014-10-24
1208 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
1210 It adds several new security features, including improved
1211 denial-of-service resistance for relays, new compiler hardening
1212 options, and a system-call sandbox for hardened installations on Linux
1213 (requires seccomp2). The controller protocol has several new features,
1214 resolving IPv6 addresses should work better than before, and relays
1215 should be a little more CPU-efficient. We've added support for more
1216 OpenBSD and FreeBSD transparent proxy types. We've improved the build
1217 system and testing infrastructure to allow unit testing of more parts
1218 of the Tor codebase. Finally, we've addressed several nagging pluggable
1219 transport usability issues, and included numerous other small bugfixes
1220 and features mentioned below.
1222 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
1223 have accumulated many known flaws; everyone should upgrade.
1225 o Major features (security):
1226 - The ntor handshake is now on-by-default, no matter what the
1227 directory authorities recommend. Implements ticket 8561.
1228 - Make the "tor-gencert" tool used by directory authority operators
1229 create 2048-bit signing keys by default (rather than 1024-bit, since
1230 1024-bit is uncomfortably small these days). Addresses ticket 10324.
1231 - Warn about attempts to run hidden services and relays in the same
1232 process: that's probably not a good idea. Closes ticket 12908.
1233 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
1234 today support TLS 1.0 or later, so we can safely turn off support
1235 for this old (and insecure) protocol. Fixes bug 13426.
1237 o Major features (relay security, DoS-resistance):
1238 - When deciding whether we have run out of memory and we need to
1239 close circuits, also consider memory allocated in buffers for
1240 streams attached to each circuit.
1242 This change, which extends an anti-DoS feature introduced in
1243 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
1244 better resist more memory-based DoS attacks than before. Since the
1245 MaxMemInCellQueues option now applies to all queues, it is renamed
1246 to MaxMemInQueues. This feature fixes bug 10169.
1247 - Avoid hash-flooding denial-of-service attacks by using the secure
1248 SipHash-2-4 hash function for our hashtables. Without this
1249 feature, an attacker could degrade performance of a targeted
1250 client or server by flooding their data structures with a large
1251 number of entries to be stored at the same hash table position,
1252 thereby slowing down the Tor instance. With this feature, hash
1253 table positions are derived from a randomized cryptographic key,
1254 and an attacker cannot predict which entries will collide. Closes
1256 - If you don't specify MaxMemInQueues yourself, Tor now tries to
1257 pick a good value based on your total system memory. Previously,
1258 the default was always 8 GB. You can still override the default by
1259 setting MaxMemInQueues yourself. Resolves ticket 11396.
1261 o Major features (bridges and pluggable transports):
1262 - Add support for passing arguments to managed pluggable transport
1263 proxies. Implements ticket 3594.
1264 - Bridges now track GeoIP information and the number of their users
1265 even when pluggable transports are in use, and report usage
1266 statistics in their extra-info descriptors. Resolves tickets 4773
1268 - Don't launch pluggable transport proxies if we don't have any
1269 bridges configured that would use them. Now we can list many
1270 pluggable transports, and Tor will dynamically start one when it
1271 hears a bridge address that needs it. Resolves ticket 5018.
1272 - The bridge directory authority now assigns status flags (Stable,
1273 Guard, etc) to bridges based on thresholds calculated over all
1274 Running bridges. Now bridgedb can finally make use of its features
1275 to e.g. include at least one Stable bridge in its answers. Fixes
1278 o Major features (controller):
1279 - Extend ORCONN controller event to include an "ID" parameter,
1280 and add four new controller event types CONN_BW, CIRC_BW,
1281 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
1282 The new events are emitted in private Tor networks only, with the
1283 goal of being able to better track performance and load during
1284 full-network simulations. Implements proposal 218 and ticket 7359.
1286 o Major features (relay performance):
1287 - Speed up server-side lookups of rendezvous and introduction point
1288 circuits by using hashtables instead of linear searches. These
1289 functions previously accounted between 3 and 7% of CPU usage on
1290 some busy relays. Resolves ticket 9841.
1291 - Avoid wasting CPU when extending a circuit over a channel that is
1292 nearly out of circuit IDs. Previously, we would do a linear scan
1293 over possible circuit IDs before finding one or deciding that we
1294 had exhausted our possibilities. Now, we try at most 64 random
1295 circuit IDs before deciding that we probably won't succeed. Fixes
1296 a possible root cause of ticket 11553.
1298 o Major features (seccomp2 sandbox, Linux only):
1299 - Use the seccomp2 syscall filtering facility on Linux to limit
1300 which system calls Tor can invoke. This is an experimental,
1301 Linux-only feature to provide defense-in-depth against unknown
1302 attacks. To try turning it on, set "Sandbox 1" in your torrc
1303 file. Please be ready to report bugs. We hope to add support
1304 for better sandboxing in the future, including more fine-grained
1305 filters, better division of responsibility, and support for more
1306 platforms. This work has been done by Cristian-Matei Toader for
1307 Google Summer of Code. Resolves tickets 11351 and 11465.
1309 o Major features (testing networks):
1310 - Make testing Tor networks bootstrap better: lower directory fetch
1311 retry schedules and maximum interval without directory requests,
1312 and raise maximum download tries. Implements ticket 6752.
1313 - Add make target 'test-network' to run tests on a Chutney network.
1314 Implements ticket 8530.
1316 o Major features (other):
1317 - On some platforms (currently: recent OSX versions, glibc-based
1318 platforms that support the ELF format, and a few other
1319 Unix-like operating systems), Tor can now dump stack traces
1320 when a crash occurs or an assertion fails. By default, traces
1321 are dumped to stderr (if possible) and to any logs that are
1322 reporting errors. Implements ticket 9299.
1324 o Deprecated versions:
1325 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
1326 attention for some while.
1328 o Major bugfixes (security, directory authorities):
1329 - Directory authorities now include a digest of each relay's
1330 identity key as a part of its microdescriptor.
1332 This is a workaround for bug 11743 (reported by "cypherpunks"),
1333 where Tor clients do not support receiving multiple
1334 microdescriptors with the same SHA256 digest in the same
1335 consensus. When clients receive a consensus like this, they only
1336 use one of the relays. Without this fix, a hostile relay could
1337 selectively disable some client use of target relays by
1338 constructing a router descriptor with a different identity and the
1339 same microdescriptor parameters and getting the authorities to
1340 list it in a microdescriptor consensus. This fix prevents an
1341 attacker from causing a microdescriptor collision, because the
1342 router's identity is not forgeable.
1344 o Major bugfixes (openssl bug workaround):
1345 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
1346 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
1347 bug 13471. This is a workaround for an OpenSSL bug.
1349 o Major bugfixes (client):
1350 - Perform circuit cleanup operations even when circuit
1351 construction operations are disabled (because the network is
1352 disabled, or because there isn't enough directory information).
1353 Previously, when we were not building predictive circuits, we
1354 were not closing expired circuits either. Fixes bug 8387; bugfix on
1355 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
1356 became more strict about when we have "enough directory information
1359 o Major bugfixes (client, pluggable transports):
1360 - When managing pluggable transports, use OS notification facilities
1361 to learn if they have crashed, and don't attempt to kill any
1362 process that has already exited. Fixes bug 8746; bugfix
1365 o Major bugfixes (relay denial of service):
1366 - Instead of writing destroy cells directly to outgoing connection
1367 buffers, queue them and intersperse them with other outgoing cells.
1368 This can prevent a set of resource starvation conditions where too
1369 many pending destroy cells prevent data cells from actually getting
1370 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
1371 bugfix on 0.2.0.1-alpha.
1373 o Major bugfixes (relay):
1374 - Avoid queuing or sending destroy cells for circuit ID zero when we
1375 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
1376 Found and fixed by "cypherpunks".
1377 - Fix ORPort reachability detection on relays running behind a
1378 proxy, by correctly updating the "local" mark on the controlling
1379 channel when changing the address of an or_connection_t after the
1380 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
1381 - Use a direct dirport connection when uploading non-anonymous
1382 descriptors to the directory authorities. Previously, relays would
1383 incorrectly use tunnel connections under a fairly wide variety of
1384 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
1385 - When a circuit accidentally has the same circuit ID for its
1386 forward and reverse direction, correctly detect the direction of
1387 cells using that circuit. Previously, this bug made roughly one
1388 circuit in a million non-functional. Fixes bug 12195; this is a
1389 bugfix on every version of Tor.
1391 o Minor features (security):
1392 - New --enable-expensive-hardening option to enable security
1393 hardening options that consume nontrivial amounts of CPU and
1394 memory. Right now, this includes AddressSanitizer and UbSan, which
1395 are supported in newer versions of GCC and Clang. Closes ticket
1397 - Authorities now assign the Guard flag to the fastest 25% of the
1398 network (it used to be the fastest 50%). Also raise the consensus
1399 weight that guarantees the Guard flag from 250 to 2000. For the
1400 current network, this results in about 1100 guards, down from 2500.
1401 This step paves the way for moving the number of entry guards
1402 down to 1 (proposal 236) while still providing reasonable expected
1403 performance for most users. Implements ticket 12690.
1405 o Minor features (security, memory management):
1406 - Memory allocation tricks (mempools and buffer freelists) are now
1407 disabled by default. You can turn them back on with
1408 --enable-mempools and --enable-buf-freelists respectively. We're
1409 disabling these features because malloc performance is good enough
1410 on most platforms, and a similar feature in OpenSSL exacerbated
1411 exploitation of the Heartbleed attack. Resolves ticket 11476.
1413 o Minor features (bridge client):
1414 - Report a more useful failure message when we can't connect to a
1415 bridge because we don't have the right pluggable transport
1416 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
1418 o Minor features (bridge):
1419 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
1420 cookie file for the ExtORPort g+r by default.
1422 o Minor features (bridges, pluggable transports):
1423 - Bridges now write the SHA1 digest of their identity key
1424 fingerprint (that is, a hash of a hash of their public key) to
1425 notice-level logs, and to a new hashed-fingerprint file. This
1426 information will help bridge operators look up their bridge in
1427 Globe and similar tools. Resolves ticket 10884.
1428 - Improve the message that Tor displays when running as a bridge
1429 using pluggable transports without an Extended ORPort listener.
1430 Also, log the message in the log file too. Resolves ticket 11043.
1431 - Add threshold cutoffs to the networkstatus document created by
1432 the Bridge Authority. Fixes bug 1117.
1433 - On Windows, spawn background processes using the CREATE_NO_WINDOW
1434 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
1435 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
1436 Vidalia set this option for us.) Implements ticket 10297.
1438 o Minor features (build):
1439 - The configure script has a --disable-seccomp option to turn off
1440 support for libseccomp on systems that have it, in case it (or
1441 Tor's use of it) is broken. Resolves ticket 11628.
1442 - Assume that a user using ./configure --host wants to cross-compile,
1443 and give an error if we cannot find a properly named
1444 tool-chain. Add a --disable-tool-name-check option to proceed
1445 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
1446 - If we run ./configure and the compiler recognizes -fstack-protector
1447 but the linker rejects it, warn the user about a potentially missing
1448 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
1449 - Add support for `--library-versions` flag. Implements ticket 6384.
1450 - Return the "unexpected sendme" warnings to a warn severity, but make
1451 them rate limited, to help diagnose ticket 8093.
1452 - Detect a missing asciidoc, and warn the user about it, during
1453 configure rather than at build time. Fixes issue 6506. Patch from
1456 o Minor features (client):
1457 - Add a new option, PredictedPortsRelevanceTime, to control how long
1458 after having received a request to connect to a given port Tor
1459 will try to keep circuits ready in anticipation of future requests
1460 for that port. Patch from "unixninja92"; implements ticket 9176.
1462 o Minor features (config options and command line):
1463 - Add an --allow-missing-torrc commandline option that tells Tor to
1464 run even if the configuration file specified by -f is not available.
1465 Implements ticket 10060.
1466 - Add support for the TPROXY transparent proxying facility on Linux.
1467 See documentation for the new TransProxyType option for more
1468 details. Implementation by "thomo". Closes ticket 10582.
1470 o Minor features (config options):
1471 - Config (torrc) lines now handle fingerprints which are missing
1472 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
1473 - Support a --dump-config option to print some or all of the
1474 configured options. Mainly useful for debugging the command-line
1475 option parsing code. Helps resolve ticket 4647.
1476 - Raise awareness of safer logging: notify user of potentially
1477 unsafe config options, like logging more verbosely than severity
1478 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
1479 - Add a new configuration option TestingV3AuthVotingStartOffset
1480 that bootstraps a network faster by changing the timing for
1481 consensus votes. Addresses ticket 8532.
1482 - Add a new torrc option "ServerTransportOptions" that allows
1483 bridge operators to pass configuration parameters to their
1484 pluggable transports. Resolves ticket 8929.
1485 - The config (torrc) file now accepts bandwidth and space limits in
1486 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
1487 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
1490 o Minor features (controller):
1491 - Make the entire exit policy available from the control port via
1492 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
1494 - Because of the fix for ticket 11396, the real limit for memory
1495 usage may no longer match the configured MaxMemInQueues value. The
1496 real limit is now exposed via GETINFO limits/max-mem-in-queues.
1497 - Add a new "HS_DESC" controller event that reports activities
1498 related to hidden service descriptors. Resolves ticket 8510.
1499 - New "DROPGUARDS" controller command to forget all current entry
1500 guards. Not recommended for ordinary use, since replacing guards
1501 too frequently makes several attacks easier. Resolves ticket 9934;
1503 - Implement the TRANSPORT_LAUNCHED control port event that
1504 notifies controllers about new launched pluggable
1505 transports. Resolves ticket 5609.
1507 o Minor features (diagnostic):
1508 - When logging a warning because of bug 7164, additionally check the
1509 hash table for consistency (as proposed on ticket 11737). This may
1510 help diagnose bug 7164.
1511 - When we log a heartbeat, log how many one-hop circuits we have
1512 that are at least 30 minutes old, and log status information about
1513 a few of them. This is an attempt to track down bug 8387.
1514 - When encountering an unexpected CR while writing text to a file on
1515 Windows, log the name of the file. Should help diagnosing
1517 - Give more specific warnings when a client notices that an onion
1518 handshake has failed. Fixes ticket 9635.
1519 - Add significant new logging code to attempt to diagnose bug 12184,
1520 where relays seem to run out of available circuit IDs.
1521 - Improve the diagnostic log message for bug 8387 even further to
1522 try to improve our odds of figuring out why one-hop directory
1523 circuits sometimes do not get closed.
1524 - Add more log messages to diagnose bug 7164, which causes
1525 intermittent "microdesc_free() called but md was still referenced"
1526 warnings. We now include more information, to figure out why we
1527 might be cleaning a microdescriptor for being too old if it's
1528 still referenced by a live node_t object.
1529 - Log current accounting state (bytes sent and received + remaining
1530 time for the current accounting period) in the relay's heartbeat
1531 message. Implements ticket 5526; patch from Peter Retzlaff.
1533 o Minor features (geoip):
1534 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
1537 o Minor features (interface):
1538 - Generate a warning if any ports are listed in the SocksPolicy,
1539 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
1540 AuthDirBadExit options. (These options only support address
1541 ranges.) Fixes part of ticket 11108.
1543 o Minor features (kernel API usage):
1544 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
1545 sockets in a single system call. Implements ticket 5129.
1547 o Minor features (log messages):
1548 - When ServerTransportPlugin is set on a bridge, Tor can write more
1549 useful statistics about bridge use in its extrainfo descriptors,
1550 but only if the Extended ORPort ("ExtORPort") is set too. Add a
1551 log message to inform the user in this case. Resolves ticket 9651.
1552 - When receiving a new controller connection, log the origin address.
1553 Resolves ticket 9698; patch from "sigpipe".
1554 - When logging OpenSSL engine status at startup, log the status of
1555 more engines. Fixes ticket 10043; patch from Joshua Datko.
1557 o Minor features (log verbosity):
1558 - Demote the message that we give when a flushing connection times
1559 out for too long from NOTICE to INFO. It was usually meaningless.
1560 Resolves ticket 5286.
1561 - Don't log so many notice-level bootstrapping messages at startup
1562 about downloading descriptors. Previously, we'd log a notice
1563 whenever we learned about more routers. Now, we only log a notice
1564 at every 5% of progress. Fixes bug 9963.
1565 - Warn less verbosely when receiving a malformed
1566 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
1568 o Minor features (performance):
1569 - If we're using the pure-C 32-bit curve25519_donna implementation
1570 of curve25519, build it with the -fomit-frame-pointer option to
1571 make it go faster on register-starved hosts. This improves our
1572 handshake performance by about 6% on i386 hosts without nacl.
1575 o Minor features (relay):
1576 - If a circuit timed out for at least 3 minutes, check if we have a
1577 new external IP address, and publish a new descriptor with the new
1578 IP address if it changed. Resolves ticket 2454.
1580 o Minor features (testing):
1581 - If Python is installed, "make check" now runs extra tests beyond
1582 the unit test scripts.
1583 - When bootstrapping a test network, sometimes very few relays get
1584 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
1585 specify a set of relays which should be voted Guard regardless of
1586 their uptime or bandwidth. Addresses ticket 9206.
1588 o Minor features (transparent proxy, *BSD):
1589 - Support FreeBSD's ipfw firewall interface for TransPort ports on
1590 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
1591 10267; patch from "yurivict".
1592 - Support OpenBSD's divert-to rules with the pf firewall for
1593 transparent proxy ports. To enable it, set "TransProxyType
1594 pf-divert". This allows Tor to run a TransPort transparent proxy
1595 port on OpenBSD 4.4 or later without root privileges. See the
1596 pf.conf(5) manual page for information on configuring pf to use
1597 divert-to rules. Closes ticket 10896; patch from Dana Koch.
1599 o Minor bugfixes (bridge client):
1600 - Stop accepting bridge lines containing hostnames. Doing so would
1601 cause clients to perform DNS requests on the hostnames, which was
1602 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
1604 o Minor bugfixes (bridges):
1605 - Avoid potential crashes or bad behavior when launching a
1606 server-side managed proxy with ORPort or ExtORPort temporarily
1607 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
1608 - Fix a bug where the first connection works to a bridge that uses a
1609 pluggable transport with client-side parameters, but we don't send
1610 the client-side parameters on subsequent connections. (We don't
1611 use any pluggable transports with client-side parameters yet,
1612 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
1613 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
1615 o Minor bugfixes (build, auxiliary programs):
1616 - Stop preprocessing the "torify" script with autoconf, since
1617 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
1619 - The tor-fw-helper program now follows the standard convention and
1620 exits with status code "0" on success. Fixes bug 9030; bugfix on
1621 0.2.3.1-alpha. Patch by Arlo Breault.
1622 - Corrected ./configure advice for what openssl dev package you should
1623 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
1625 o Minor bugfixes (client):
1626 - Avoid "Tried to open a socket with DisableNetwork set" warnings
1627 when starting a client with bridges configured and DisableNetwork
1628 set. (Tor launcher starts Tor with DisableNetwork set the first
1629 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
1630 - Improve the log message when we can't connect to a hidden service
1631 because all of the hidden service directory nodes hosting its
1632 descriptor are excluded. Improves on our fix for bug 10722, which
1633 was a bugfix on 0.2.0.10-alpha.
1634 - Raise a control port warning when we fail to connect to all of
1635 our bridges. Previously, we didn't inform the controller, and
1636 the bootstrap process would stall. Fixes bug 11069; bugfix on
1638 - Exit immediately when a process-owning controller exits.
1639 Previously, tor relays would wait for a little while after their
1640 controller exited, as if they had gotten an INT signal -- but this
1641 was problematic, since there was no feedback for the user. To do a
1642 clean shutdown, controllers should send an INT signal and give Tor
1643 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
1644 - Stop attempting to connect to bridges before our pluggable
1645 transports are configured (harmless but resulted in some erroneous
1646 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
1647 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
1648 generating incorrect SOCKS5 responses, and confusing client
1649 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
1651 o Minor bugfixes (client, DNSPort):
1652 - When using DNSPort, try to respond to AAAA requests with AAAA
1653 answers. Previously, we hadn't looked at the request type when
1654 deciding which answer type to prefer. Fixes bug 10468; bugfix on
1656 - When receiving a DNS query for an unsupported record type, reply
1657 with no answer rather than with a NOTIMPL error. This behavior
1658 isn't correct either, but it will break fewer client programs, we
1659 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
1662 o Minor bugfixes (client, logging during bootstrap):
1663 - Only report the first fatal bootstrap error on a given OR
1664 connection. This stops us from telling the controller bogus error
1665 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
1666 - Avoid generating spurious warnings when starting with
1667 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
1670 o Minor bugfixes (closing OR connections):
1671 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
1672 check if it's an or_connection_t and correctly call
1673 connection_or_close_for_error() rather than
1674 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
1676 - When closing all connections on setting DisableNetwork to 1, use
1677 connection_or_close_normally() rather than closing OR connections
1678 out from under the channel layer. Fixes bug 11306; bugfix on
1681 o Minor bugfixes (code correctness):
1682 - Previously we used two temporary files when writing descriptors to
1683 disk; now we only use one. Fixes bug 1376.
1684 - Remove an erroneous (but impossible and thus harmless) pointer
1685 comparison that would have allowed compilers to skip a bounds
1686 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
1687 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
1688 - Fix an always-true assertion in pluggable transports code so it
1689 actually checks what it was trying to check. Fixes bug 10046;
1690 bugfix on 0.2.3.9-alpha. Found by "dcb".
1692 o Minor bugfixes (command line):
1693 - Use a single command-line parser for parsing torrc options on the
1694 command line and for finding special command-line options to avoid
1695 inconsistent behavior for torrc option arguments that have the same
1696 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
1698 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
1699 9573; bugfix on 0.0.9pre5.
1701 o Minor bugfixes (compilation):
1702 - Compile correctly with builds and forks of OpenSSL (such as
1703 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
1704 0.2.1.1-alpha. Patch from "dhill".
1705 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
1706 turned off (that is, without support for v2 link handshakes). Fixes
1707 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
1708 - In routerlist_assert_ok(), don't take the address of a
1709 routerinfo's cache_info member unless that routerinfo is non-NULL.
1710 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
1711 - Fix a large number of false positive warnings from the clang
1712 analyzer static analysis tool. This should make real warnings
1713 easier for clang analyzer to find. Patch from "teor". Closes
1715 - Resolve GCC complaints on OpenBSD about discarding constness in
1716 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
1717 on 0.1.1.23. Patch from Dana Koch.
1718 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
1719 treatment of long and time_t as comparable types. Fixes part of
1720 bug 11633. Patch from Dana Koch.
1721 - When deciding whether to build the 64-bit curve25519
1722 implementation, detect platforms where we can compile 128-bit
1723 arithmetic but cannot link it. Fixes bug 11729; bugfix on
1724 0.2.4.8-alpha. Patch from "conradev".
1725 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
1726 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
1727 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
1729 - Build and run correctly on systems like OpenBSD-current that have
1730 patched OpenSSL to remove get_cipher_by_char and/or its
1731 implementations. Fixes issue 13325.
1733 o Minor bugfixes (controller and command-line):
1734 - If changing a config option via "setconf" fails in a recoverable
1735 way, we used to nonetheless write our new control ports to the
1736 file described by the "ControlPortWriteToFile" option. Now we only
1737 write out that file if we successfully switch to the new config
1738 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
1740 o Minor bugfixes (directory server):
1741 - No longer accept malformed http headers when parsing urls from
1742 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
1743 bugfix on 0.0.6pre1.
1744 - When sending a compressed set of descriptors or microdescriptors,
1745 make sure to finalize the zlib stream. Previously, we would write
1746 all the compressed data, but if the last descriptor we wanted to
1747 send was missing or too old, we would not mark the stream as
1748 finished. This caused problems for decompression tools. Fixes bug
1749 11648; bugfix on 0.1.1.23.
1751 o Minor bugfixes (hidden service):
1752 - Only retry attempts to connect to a chosen rendezvous point 8
1753 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
1755 o Minor bugfixes (interface):
1756 - Reject relative control socket paths and emit a warning. Previously,
1757 single-component control socket paths would be rejected, but Tor
1758 would not log why it could not validate the config. Fixes bug 9258;
1759 bugfix on 0.2.3.16-alpha.
1761 o Minor bugfixes (log messages):
1762 - Fix a bug where clients using bridges would report themselves
1763 as 50% bootstrapped even without a live consensus document.
1764 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
1765 - Suppress a warning where, if there's only one directory authority
1766 in the network, we would complain that votes and signatures cannot
1767 be uploaded to other directory authorities. Fixes bug 10842;
1768 bugfix on 0.2.2.26-beta.
1769 - Report bootstrapping progress correctly when we're downloading
1770 microdescriptors. We had updated our "do we have enough microdescs
1771 to begin building circuits?" logic most recently in 0.2.4.10-alpha
1772 (see bug 5956), but we left the bootstrap status event logic at
1773 "how far through getting 1/4 of them are we?" Fixes bug 9958;
1774 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
1776 o Minor bugfixes (logging):
1777 - Downgrade "Unexpected onionskin length after decryption" warning
1778 to a protocol-warn, since there's nothing relay operators can do
1779 about a client that sends them a malformed create cell. Resolves
1780 bug 12996; bugfix on 0.0.6rc1.
1781 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
1782 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
1783 - When logging information about an EXTEND2 or EXTENDED2 cell, log
1784 their names correctly. Fixes part of bug 12700; bugfix
1786 - When logging information about a relay cell whose command we don't
1787 recognize, log its command as an integer. Fixes part of bug 12700;
1788 bugfix on 0.2.1.10-alpha.
1789 - Escape all strings from the directory connection before logging
1790 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
1791 - Squelch a spurious LD_BUG message "No origin circuit for
1792 successful SOCKS stream" in certain hidden service failure cases;
1794 - Downgrade the severity of the 'unexpected sendme cell from client'
1795 from 'warn' to 'protocol warning'. Closes ticket 8093.
1797 o Minor bugfixes (misc code correctness):
1798 - In munge_extrainfo_into_routerinfo(), check the return value of
1799 memchr(). This would have been a serious issue if we ever passed
1800 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
1802 - On the chance that somebody manages to build Tor on a
1803 platform where time_t is unsigned, correct the way that
1804 microdesc_add_to_cache() handles negative time arguments.
1805 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
1806 - Fix various instances of undefined behavior in channeltls.c,
1807 tor_memmem(), and eventdns.c that would cause us to construct
1808 pointers to memory outside an allocated object. (These invalid
1809 pointers were not accessed, but C does not even allow them to
1810 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
1811 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
1812 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
1813 fix some miscellaneous errors in our tests and codebase. Fixes bug
1814 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
1815 - Always check return values for unlink, munmap, UnmapViewOfFile;
1816 check strftime return values more often. In some cases all we can
1817 do is report a warning, but this may help prevent deeper bugs from
1818 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
1820 - Fix numerous warnings from the clang "scan-build" static analyzer.
1821 Some of these are programming style issues; some of them are false
1822 positives that indicated awkward code; some are undefined behavior
1823 cases related to constructing (but not using) invalid pointers;
1824 some are assumptions about API behavior; some are (harmlessly)
1825 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
1826 correct; and one or two are genuine bugs that weren't reachable
1827 from the rest of the program. Fixes bug 8793; bugfixes on many,
1830 o Minor bugfixes (node selection):
1831 - If ExcludeNodes is set, consider non-excluded hidden service
1832 directory servers before excluded ones. Do not consider excluded
1833 hidden service directory servers at all if StrictNodes is
1834 set. (Previously, we would sometimes decide to connect to those
1835 servers, and then realize before we initiated a connection that
1836 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
1838 - If we set the ExitNodes option but it doesn't include any nodes
1839 that have the Exit flag, we would choose not to bootstrap. Now we
1840 bootstrap so long as ExitNodes includes nodes which can exit to
1841 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
1843 o Minor bugfixes (performance):
1844 - Avoid a bug where every successful connection made us recompute
1845 the flag telling us whether we have sufficient information to
1846 build circuits. Previously, we would forget our cached value
1847 whenever we successfully opened a channel (or marked a router as
1848 running or not running for any other reason), regardless of
1849 whether we had previously believed the router to be running. This
1850 forced us to run an expensive update operation far too often.
1851 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
1852 - Avoid using tor_memeq() for checking relay cell integrity. This
1853 removes a possible performance bottleneck. Fixes part of bug
1854 12169; bugfix on 0.2.1.31.
1856 o Minor bugfixes (platform-specific):
1857 - When dumping a malformed directory object to disk, save it in
1858 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
1860 - Don't report failures from make_socket_reuseable() on incoming
1861 sockets on OSX: this can happen when incoming connections close
1862 early. Fixes bug 10081.
1864 o Minor bugfixes (pluggable transports):
1865 - Avoid another 60-second delay when starting Tor in a pluggable-
1866 transport-using configuration when we already have cached
1867 descriptors for our bridges. Fixes bug 11965; bugfix
1870 o Minor bugfixes (protocol correctness):
1871 - When receiving a VERSIONS cell with an odd number of bytes, close
1872 the connection immediately since the cell is malformed. Fixes bug
1873 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
1876 o Minor bugfixes (relay, other):
1877 - We now drop CREATE cells for already-existent circuit IDs and for
1878 zero-valued circuit IDs, regardless of other factors that might
1879 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
1881 - When rejecting DATA cells for stream_id zero, still count them
1882 against the circuit's deliver window so that we don't fail to send
1883 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
1885 o Minor bugfixes (relay, threading):
1886 - Check return code on spawn_func() in cpuworker code, so that we
1887 don't think we've spawned a nonworking cpuworker and write junk to
1888 it forever. Fix related to bug 4345; bugfix on all released Tor
1889 versions. Found by "skruffy".
1890 - Use a pthread_attr to make sure that spawn_func() cannot return an
1891 error while at the same time launching a thread. Fix related to
1892 bug 4345; bugfix on all released Tor versions. Reported
1895 o Minor bugfixes (relays and bridges):
1896 - Avoid crashing on a malformed resolv.conf file when running a
1897 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
1898 - Non-exit relays no longer launch mock DNS requests to check for
1899 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
1900 non-exit relays stopped servicing DNS requests. Fixes bug 965;
1901 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
1902 - Bridges now report complete directory request statistics. Related
1903 to bug 5824; bugfix on 0.2.2.1-alpha.
1904 - Bridges now never collect statistics that were designed for
1905 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
1907 o Minor bugfixes (testing):
1908 - Fix all valgrind warnings produced by the unit tests. There were
1909 over a thousand memory leak warnings previously, mostly produced
1910 by forgetting to free things in the unit test code. Fixes bug
1911 11618, bugfixes on many versions of Tor.
1913 o Minor bugfixes (tor-fw-helper):
1914 - Give a correct log message when tor-fw-helper fails to launch.
1915 (Previously, we would say something like "tor-fw-helper sent us a
1916 string we could not parse".) Fixes bug 9781; bugfix
1919 o Minor bugfixes (trivial memory leaks):
1920 - Fix a small memory leak when signing a directory object. Fixes bug
1921 11275; bugfix on 0.2.4.13-alpha.
1922 - Resolve some memory leaks found by coverity in the unit tests, on
1923 exit in tor-gencert, and on a failure to compute digests for our
1924 own keys when generating a v3 networkstatus vote. These leaks
1925 should never have affected anyone in practice.
1927 o Code simplification and refactoring:
1928 - Remove some old fallback code designed to keep Tor clients working
1929 in a network with only two working relays. Elsewhere in the code we
1930 have long since stopped supporting such networks, so there wasn't
1931 much point in keeping it around. Addresses ticket 9926.
1932 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
1933 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
1934 - Extract the common duplicated code for creating a subdirectory
1935 of the data directory and writing to a file in it. Fixes ticket
1936 4282; patch from Peter Retzlaff.
1937 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
1938 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
1939 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
1940 - Add a set of accessor functions for the circuit timeout data
1941 structure. Fixes ticket 6153; patch from "piet".
1942 - Clean up exit paths from connection_listener_new(). Closes ticket
1943 8789. Patch from Arlo Breault.
1944 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
1945 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
1946 - Use a doubly-linked list to implement the global circuit list.
1947 Resolves ticket 9108. Patch from Marek Majkowski.
1948 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
1949 - Remove constants and tests for PKCS1 padding; it's insecure and
1950 shouldn't be used for anything new. Fixes bug 8792; patch
1952 - Remove instances of strcpy() from the unit tests. They weren't
1953 hurting anything, since they were only in the unit tests, but it's
1954 embarassing to have strcpy() in the code at all, and some analysis
1955 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
1956 0.2.3.8-alpha. Patch from Arlo Breault.
1957 - Remove is_internal_IP() function. Resolves ticket 4645.
1958 - Remove unused function circuit_dump_by_chan from circuitlist.c.
1959 Closes issue 9107; patch from "marek".
1960 - Change our use of the ENUM_BF macro to avoid declarations that
1962 - Get rid of router->address, since in all cases it was just the
1963 string representation of router->addr. Resolves ticket 5528.
1966 - Adjust the URLs in the README to refer to the new locations of
1967 several documents on the website. Fixes bug 12830. Patch from
1969 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
1971 - Update manpage to describe some of the files you can expect to
1972 find in Tor's DataDirectory. Addresses ticket 9839.
1973 - Clean up several option names in the manpage to match their real
1974 names, add the missing documentation for a couple of testing and
1975 directory authority options, remove the documentation for a
1976 V2-directory fetching option that no longer exists. Resolves
1978 - Correct the documenation so that it lists the correct directory
1979 for the stats files. (They are in a subdirectory called "stats",
1981 - In the manpage, move more authority-only options into the
1982 directory authority section so that operators of regular directory
1983 caches don't get confused.
1984 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
1985 11061; bugfix on 0.2.4.7-alpha.
1986 - Resolve warnings from Doxygen.
1987 - Document in the manpage that "KBytes" may also be written as
1988 "kilobytes" or "KB", that "Kbits" may also be written as
1989 "kilobits", and so forth. Closes ticket 9222.
1990 - Document that the ClientOnly config option overrides ORPort.
1991 Our old explanation made ClientOnly sound as though it did
1992 nothing at all. Resolves bug 9059.
1993 - Explain that SocksPolicy, DirPolicy, and similar options don't
1994 take port arguments. Fixes the other part of ticket 11108.
1995 - Fix a comment about the rend_server_descriptor_t.protocols field
1996 to more accurately describe its range. Also, make that field
1997 unsigned, to more accurately reflect its usage. Fixes bug 9099;
1998 bugfix on 0.2.1.5-alpha.
1999 - Fix the manpage's description of HiddenServiceAuthorizeClient:
2000 the maximum client name length is 16, not 19. Fixes bug 11118;
2001 bugfix on 0.2.1.6-alpha.
2004 - The contrib directory has been sorted and tidied. Before, it was
2005 an unsorted dumping ground for useful and not-so-useful things.
2006 Now, it is divided based on functionality, and the items which
2007 seemed to be nonfunctional or useless have been removed. Resolves
2008 ticket 8966; based on patches from "rl1987".
2010 o Removed code and features:
2011 - Clients now reject any directory authority certificates lacking
2012 a dir-key-crosscert element. These have been included since
2013 0.2.1.9-alpha, so there's no real reason for them to be optional
2014 any longer. Completes proposal 157. Resolves ticket 10162.
2015 - Remove all code that existed to support the v2 directory system,
2016 since there are no longer any v2 directory authorities. Resolves
2018 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
2019 options, which were used for designating authorities as "Hidden
2020 service authorities". There has been no use of hidden service
2021 authorities since 0.2.2.1-alpha, when we stopped uploading or
2022 downloading v0 hidden service descriptors. Fixes bug 10881; also
2023 part of a fix for bug 10841.
2024 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
2025 and MTBF calculations, but that nobody was using. Fixes bug 11742.
2026 - The TunnelDirConns and PreferTunnelledDirConns options no longer
2027 exist; tunneled directory connections have been available since
2028 0.1.2.5-alpha, and turning them off is not a good idea. This is a
2029 brute-force fix for 10849, where "TunnelDirConns 0" would break
2031 - Remove all code for the long unused v1 directory protocol.
2032 Resolves ticket 11070.
2033 - Remove all remaining code related to version-0 hidden service
2034 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
2035 the rest of bug 10841.
2036 - Remove migration code from when we renamed the "cached-routers"
2037 file to "cached-descriptors" back in 0.2.0.8-alpha. This
2038 incidentally resolves ticket 6502 by cleaning up the related code
2039 a bit. Patch from Akshay Hebbar.
2041 o Test infrastructure:
2042 - Tor now builds each source file in two modes: a mode that avoids
2043 exposing identifiers needlessly, and another mode that exposes
2044 more identifiers for testing. This lets the compiler do better at
2045 optimizing the production code, while enabling us to take more
2046 radical measures to let the unit tests test things.
2047 - The production builds no longer include functions used only in
2048 the unit tests; all functions exposed from a module only for
2049 unit-testing are now static in production builds.
2050 - Add an --enable-coverage configuration option to make the unit
2051 tests (and a new src/or/tor-cov target) to build with gcov test
2053 - Update to the latest version of tinytest.
2054 - Improve the tinytest implementation of string operation tests so
2055 that comparisons with NULL strings no longer crash the tests; they
2056 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
2057 - New macros in test.h to simplify writing mock-functions for unit
2058 tests. Part of ticket 11507. Patch from Dana Koch.
2059 - We now have rudimentary function mocking support that our unit
2060 tests can use to test functions in isolation. Function mocking
2061 lets the tests temporarily replace a function's dependencies with
2062 stub functions, so that the tests can check the function without
2063 invoking the other functions it calls.
2066 - Complete tests for the status.c module. Resolves ticket 11507.
2067 Patch from Dana Koch.
2068 - Add more unit tests for the <circid,channel>->circuit map, and
2069 the destroy-cell-tracking code to fix bug 7912.
2070 - Unit tests for failing cases of the TAP onion handshake.
2071 - More unit tests for address-manipulation functions.
2073 o Distribution (systemd):
2074 - Include a tor.service file in contrib/dist for use with systemd.
2075 Some distributions will be able to use this file unmodified;
2076 others will need to tweak it, or write their own. Patch from Jamie
2077 Nguyen; resolves ticket 8368.
2078 - Verify configuration file via ExecStartPre in the systemd unit
2079 file. Patch from intrigeri; resolves ticket 12730.
2080 - Explicitly disable RunAsDaemon in the systemd unit file. Our
2081 current systemd unit uses "Type = simple", so systemd does not
2082 expect tor to fork. If the user has "RunAsDaemon 1" in their
2083 torrc, then things won't work as expected. This is e.g. the case
2084 on Debian (and derivatives), since there we pass "--defaults-torrc
2085 /usr/share/tor/tor-service-defaults-torrc" (that contains
2086 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
2090 Changes in version 0.2.4.25 - 2014-10-20
2091 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
2092 (even though POODLE does not affect Tor). It also works around a crash
2093 bug caused by some operating systems' response to the "POODLE" attack
2094 (which does affect Tor).
2096 o Major security fixes (also in 0.2.5.9-rc):
2097 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
2098 today support TLS 1.0 or later, so we can safely turn off support
2099 for this old (and insecure) protocol. Fixes bug 13426.
2101 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
2102 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
2103 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
2104 13471. This is a workaround for an OpenSSL bug.
2107 Changes in version 0.2.4.24 - 2014-09-22
2108 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
2109 connecting to hidden services, and it updates the location of one of
2110 the directory authorities.
2113 - Clients now send the correct address for their chosen rendezvous
2114 point when trying to access a hidden service. They used to send
2115 the wrong address, which would still work some of the time because
2116 they also sent the identity digest of the rendezvous point, and if
2117 the hidden service happened to try connecting to the rendezvous
2118 point from a relay that already had a connection open to it,
2119 the relay would reuse that connection. Now connections to hidden
2120 services should be more robust and faster. Also, this bug meant
2121 that clients were leaking to the hidden service whether they were
2122 on a little-endian (common) or big-endian (rare) system, which for
2123 some users might have reduced their anonymity. Fixes bug 13151;
2124 bugfix on 0.2.1.5-alpha.
2126 o Directory authority changes:
2127 - Change IP address for gabelmoo (v3 directory authority).
2129 o Minor features (geoip):
2130 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
2134 Changes in version 0.2.4.23 - 2014-07-28
2135 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
2136 guard rotation, and also backports several important fixes from the
2137 Tor 0.2.5 alpha release series.
2140 - Clients now look at the "usecreatefast" consensus parameter to
2141 decide whether to use CREATE_FAST or CREATE cells for the first hop
2142 of their circuit. This approach can improve security on connections
2143 where Tor's circuit handshake is stronger than the available TLS
2144 connection security levels, but the tradeoff is more computational
2145 load on guard relays. Implements proposal 221. Resolves ticket 9386.
2146 - Make the number of entry guards configurable via a new
2147 NumEntryGuards consensus parameter, and the number of directory
2148 guards configurable via a new NumDirectoryGuards consensus
2149 parameter. Implements ticket 12688.
2152 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
2153 implementation that caused incorrect results on 32-bit
2154 implementations when certain malformed inputs were used along with
2155 a small class of private ntor keys. This bug does not currently
2156 appear to allow an attacker to learn private keys or impersonate a
2157 Tor server, but it could provide a means to distinguish 32-bit Tor
2158 implementations from 64-bit Tor implementations. Fixes bug 12694;
2159 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
2163 - Warn and drop the circuit if we receive an inbound 'relay early'
2164 cell. Those used to be normal to receive on hidden service circuits
2165 due to bug 1038, but the buggy Tor versions are long gone from
2166 the network so we can afford to resume watching for them. Resolves
2167 the rest of bug 1038; bugfix on 0.2.1.19.
2168 - Correct a confusing error message when trying to extend a circuit
2169 via the control protocol but we don't know a descriptor or
2170 microdescriptor for one of the specified relays. Fixes bug 12718;
2171 bugfix on 0.2.3.1-alpha.
2172 - Avoid an illegal read from stack when initializing the TLS
2173 module using a version of OpenSSL without all of the ciphers
2174 used by the v2 link handshake. Fixes bug 12227; bugfix on
2175 0.2.4.8-alpha. Found by "starlight".
2178 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
2182 Changes in version 0.2.4.22 - 2014-05-16
2183 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
2184 alpha release series. These include blocking all authority signing
2185 keys that may have been affected by the OpenSSL "heartbleed" bug,
2186 choosing a far more secure set of TLS ciphersuites by default, closing
2187 a couple of memory leaks that could be used to run a target relay out
2188 of RAM, and several others.
2190 o Major features (security, backport from 0.2.5.4-alpha):
2191 - Block authority signing keys that were used on authorities
2192 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
2193 don't have any evidence that these keys _were_ compromised; we're
2194 doing this to be prudent.) Resolves ticket 11464.
2196 o Major bugfixes (security, OOM):
2197 - Fix a memory leak that could occur if a microdescriptor parse
2198 fails during the tokenizing step. This bug could enable a memory
2199 exhaustion attack by directory servers. Fixes bug 11649; bugfix
2202 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
2203 - The relay ciphersuite list is now generated automatically based on
2204 uniform criteria, and includes all OpenSSL ciphersuites with
2205 acceptable strength and forward secrecy. Previously, we had left
2206 some perfectly fine ciphersuites unsupported due to omission or
2207 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
2208 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
2209 - Relays now trust themselves to have a better view than clients of
2210 which TLS ciphersuites are better than others. (Thanks to bug
2211 11513, the relay list is now well-considered, whereas the client
2212 list has been chosen mainly for anti-fingerprinting purposes.)
2213 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
2214 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
2215 AES128. Resolves ticket 11528.
2216 - Clients now try to advertise the same list of ciphersuites as
2217 Firefox 28. This change enables selection of (fast) GCM
2218 ciphersuites, disables some strange old ciphers, and stops
2219 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
2220 Resolves ticket 11438.
2222 o Minor bugfixes (configuration, security):
2223 - When running a hidden service, do not allow TunneledDirConns 0:
2224 trying to set that option together with a hidden service would
2225 otherwise prevent the hidden service from running, and also make
2226 it publish its descriptors directly over HTTP. Fixes bug 10849;
2227 bugfix on 0.2.1.1-alpha.
2229 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
2230 - Avoid sending a garbage value to the controller when a circuit is
2231 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
2233 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
2234 - Stop leaking memory when we successfully resolve a PTR record.
2235 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
2237 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
2238 - Avoid 60-second delays in the bootstrapping process when Tor is
2239 launching for a second time while using bridges. Fixes bug 9229;
2240 bugfix on 0.2.0.3-alpha.
2242 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
2243 - Give the correct URL in the warning message when trying to run a
2244 relay on an ancient version of Windows. Fixes bug 9393.
2246 o Minor bugfixes (compilation):
2247 - Fix a compilation error when compiling with --disable-curve25519.
2248 Fixes bug 9700; bugfix on 0.2.4.17-rc.
2251 - Downgrade the warning severity for the the "md was still
2252 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
2253 for trying to diagnose this bug, and the current warning in
2254 earlier versions of tor achieves nothing useful. Addresses warning
2257 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
2258 - When we run out of usable circuit IDs on a channel, log only one
2259 warning for the whole channel, and describe how many circuits
2260 there were on the channel. Fixes part of ticket 11553.
2262 o Minor features (security, backport from 0.2.5.4-alpha):
2263 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
2264 leave the default at 8GBytes), to better support Raspberry Pi
2265 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
2267 o Documentation (backport from 0.2.5.4-alpha):
2268 - Correctly document that we search for a system torrc file before
2269 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
2273 Changes in version 0.2.4.21 - 2014-02-28
2274 Tor 0.2.4.21 further improves security against potential adversaries who
2275 find breaking 1024-bit crypto doable, and backports several stability
2276 and robustness patches from the 0.2.5 branch.
2278 o Major features (client security):
2279 - When we choose a path for a 3-hop circuit, make sure it contains
2280 at least one relay that supports the NTor circuit extension
2281 handshake. Otherwise, there is a chance that we're building
2282 a circuit that's worth attacking by an adversary who finds
2283 breaking 1024-bit crypto doable, and that chance changes the game
2284 theory. Implements ticket 9777.
2287 - Do not treat streams that fail with reason
2288 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
2289 since it could also indicate an ENETUNREACH connection error. Fixes
2290 part of bug 10777; bugfix on 0.2.4.8-alpha.
2292 o Code simplification and refactoring:
2293 - Remove data structures which were introduced to implement the
2294 CellStatistics option: they are now redundant with the new timestamp
2295 field in the regular packed_cell_t data structure, which we did
2296 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
2299 - Always clear OpenSSL bignums before freeing them -- even bignums
2300 that don't contain secrets. Resolves ticket 10793. Patch by
2302 - Build without warnings under clang 3.4. (We have some macros that
2303 define static functions only some of which will get used later in
2304 the module. Starting with clang 3.4, these give a warning unless the
2305 unused attribute is set on them.) Resolves ticket 10904.
2306 - Update geoip and geoip6 files to the February 7 2014 Maxmind
2307 GeoLite2 Country database.
2310 - Set the listen() backlog limit to the largest actually supported
2311 on the system, not to the value in a header file. Fixes bug 9716;
2312 bugfix on every released Tor.
2313 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
2314 exit node as a NOROUTE error, not an INTERNAL error, since they
2315 can apparently happen when trying to connect to the wrong sort
2316 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
2317 - Fix build warnings about missing "a2x" comment when building the
2318 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
2319 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
2320 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
2321 not entirely remove it from the connection lists. Fixes bug 9602;
2322 bugfix on 0.2.4.4-alpha.
2323 - Fix a segmentation fault in our benchmark code when running with
2324 Fedora's OpenSSL package, or any other OpenSSL that provides
2325 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
2326 - Turn "circuit handshake stats since last time" log messages into a
2327 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
2329 o Documentation fixes:
2330 - Document that all but one DirPort entry must have the NoAdvertise
2331 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
2334 Changes in version 0.2.4.20 - 2013-12-22
2335 Tor 0.2.4.20 fixes potentially poor random number generation for users
2336 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
2337 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
2338 and 4) have no state file in their DataDirectory (as would happen on
2339 first start). Users who generated relay or hidden service identity
2340 keys in such a situation should discard them and generate new ones.
2342 This release also fixes a logic error that caused Tor clients to build
2343 many more preemptive circuits than they actually need.
2346 - Do not allow OpenSSL engines to replace the PRNG, even when
2347 HardwareAccel is set. The only default builtin PRNG engine uses
2348 the Intel RDRAND instruction to replace the entire PRNG, and
2349 ignores all attempts to seed it with more entropy. That's
2350 cryptographically stupid: the right response to a new alleged
2351 entropy source is never to discard all previously used entropy
2352 sources. Fixes bug 10402; works around behavior introduced in
2353 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
2355 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
2356 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
2357 - Avoid launching spurious extra circuits when a stream is pending.
2358 This fixes a bug where any circuit that _wasn't_ unusable for new
2359 streams would be treated as if it were, causing extra circuits to
2360 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
2363 - Avoid a crash bug when starting with a corrupted microdescriptor
2364 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
2365 - If we fail to dump a previously cached microdescriptor to disk, avoid
2366 freeing duplicate data later on. Fixes bug 10423; bugfix on
2367 0.2.4.13-alpha. Spotted by "bobnomnom".
2370 Changes in version 0.2.4.19 - 2013-12-11
2371 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
2372 (1986-2013). Aaron worked on diverse projects including helping to guide
2373 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
2374 transparency to the U.S government's PACER documents, and contributing
2375 design and development for Tor and Tor2Web. Aaron was one of the latest
2376 martyrs in our collective fight for civil liberties and human rights,
2377 and his death is all the more painful because he was one of us.
2379 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
2380 a new circuit handshake and link encryption that use ECC to provide
2381 better security and efficiency; makes relays better manage circuit
2382 creation requests; uses "directory guards" to reduce client enumeration
2383 risks; makes bridges collect and report statistics about the pluggable
2384 transports they support; cleans up and improves our geoip database;
2385 gets much closer to IPv6 support for clients, bridges, and relays; makes
2386 directory authorities use measured bandwidths rather than advertised
2387 ones when computing flags and thresholds; disables client-side DNS
2388 caching to reduce tracking risks; and fixes a big bug in bridge
2389 reachability testing. This release introduces two new design
2390 abstractions in the code: a new "channel" abstraction between circuits
2391 and or_connections to allow for implementing alternate relay-to-relay
2392 transports, and a new "circuitmux" abstraction storing the queue of
2393 circuits for a channel. The release also includes many stability,
2394 security, and privacy fixes.
2396 o Major features (new circuit handshake):
2397 - Tor now supports a new circuit extension handshake designed by Ian
2398 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
2399 circuit extension handshake, later called "TAP", was a bit slow
2400 (especially on the relay side), had a fragile security proof, and
2401 used weaker keys than we'd now prefer. The new circuit handshake
2402 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
2403 function, making it significantly more secure than the older
2404 handshake, and significantly faster. Tor can use one of two built-in
2405 pure-C curve25519-donna implementations by Adam Langley, or it
2406 can link against the "nacl" library for a tuned version if present.
2408 The built-in version is very fast for 64-bit systems when building
2409 with GCC. The built-in 32-bit version is still faster than the
2410 old TAP protocol, but using libnacl is better on most such hosts.
2412 Implements proposal 216; closes ticket 7202.
2414 o Major features (better link encryption):
2415 - Relays can now enable the ECDHE TLS ciphersuites when available
2416 and appropriate. These ciphersuites let us negotiate forward-secure
2417 TLS secret keys more safely and more efficiently than with our
2418 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
2419 public relays prefer the (faster) P224 group, and bridges prefer
2420 the (more common) P256 group; you can override this with the
2423 This feature requires clients running 0.2.3.17-beta or later,
2424 and requires both sides to be running OpenSSL 1.0.0 or later
2425 with ECC support. OpenSSL 1.0.1, with the compile-time option
2426 "enable-ec_nistp_64_gcc_128", is highly recommended.
2428 Implements the relay side of proposal 198; closes ticket 7200.
2430 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
2431 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
2432 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
2433 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
2434 them to solve bug 6033.)
2436 o Major features (relay performance):
2437 - Instead of limiting the number of queued onionskins (aka circuit
2438 create requests) to a fixed, hard-to-configure number, we limit
2439 the size of the queue based on how many we expect to be able to
2440 process in a given amount of time. We estimate the time it will
2441 take to process an onionskin based on average processing time
2442 of previous onionskins. Closes ticket 7291. You'll never have to
2443 configure MaxOnionsPending again.
2444 - Relays process the new "NTor" circuit-level handshake requests
2445 with higher priority than the old "TAP" circuit-level handshake
2446 requests. We still process some TAP requests to not totally starve
2447 0.2.3 clients when NTor becomes popular. A new consensus parameter
2448 "NumNTorsPerTAP" lets us tune the balance later if we need to.
2449 Implements ticket 9574.
2451 o Major features (client bootstrapping resilience):
2452 - Add a new "FallbackDir" torrc option to use when we can't use
2453 a directory mirror from the consensus (either because we lack a
2454 consensus, or because they're all down). Currently, all authorities
2455 are fallbacks by default, and there are no other default fallbacks,
2456 but that will change. This option will allow us to give clients a
2457 longer list of servers to try to get a consensus from when first
2458 connecting to the Tor network, and thereby reduce load on the
2459 directory authorities. Implements proposal 206, "Preconfigured
2460 directory sources for bootstrapping". We also removed the old
2461 "FallbackNetworkstatus" option, since we never got it working well
2462 enough to use it. Closes bug 572.
2463 - If we have no circuits open, use a relaxed timeout (the
2464 95th-percentile cutoff) until a circuit succeeds. This heuristic
2465 should allow Tor to succeed at building circuits even when the
2466 network connection drastically changes. Should help with bug 3443.
2468 o Major features (use of guards):
2469 - Support directory guards (proposal 207): when possible, clients now
2470 use their entry guards for non-anonymous directory requests. This
2471 can help prevent client enumeration. Note that this behavior only
2472 works when we have a usable consensus directory, and when options
2473 about what to download are more or less standard. In the future we
2474 should re-bootstrap from our guards, rather than re-bootstrapping
2475 from the preconfigured list of directory sources that ships with
2476 Tor. Resolves ticket 6526.
2477 - Raise the default time that a client keeps an entry guard from
2478 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
2479 2012 paper. (We would make it even longer, but we need better client
2480 load balancing first.) Also, make the guard lifetime controllable
2481 via a new GuardLifetime torrc option and a GuardLifetime consensus
2482 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
2484 o Major features (bridges with pluggable transports):
2485 - Bridges now report the pluggable transports they support to the
2486 bridge authority, so it can pass the supported transports on to
2487 bridgedb and/or eventually do reachability testing. Implements
2489 - Automatically forward the TCP ports of pluggable transport
2490 proxies using tor-fw-helper if PortForwarding is enabled. Implements
2493 o Major features (geoip database):
2494 - Maxmind began labelling Tor relays as being in country "A1",
2495 which breaks by-country node selection inside Tor. Now we use a
2496 script to replace "A1" ("Anonymous Proxy") entries in our geoip
2497 file with real country codes. This script fixes about 90% of "A1"
2498 entries automatically and uses manual country code assignments to
2499 fix the remaining 10%. See src/config/README.geoip for details.
2501 - Add GeoIP database for IPv6 addresses. The new config option
2503 - Update to the October 2 2013 Maxmind GeoLite Country database.
2505 o Major features (IPv6):
2506 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
2507 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
2508 to happen. Implements ticket 5535.
2509 - All kind of relays, not just bridges, can now advertise an IPv6
2510 OR port. Implements ticket 6362.
2511 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
2512 connectivity, then set the IPv6Exit flag to 1. Also make sure your
2513 exit policy reads as you would like: the address * applies to all
2514 address families, whereas *4 is IPv4 address only, and *6 is IPv6
2515 addresses only. On the client side, you'll need to wait for enough
2516 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
2517 and use Socks5. Closes ticket 5547, implements proposal 117 as
2518 revised in proposal 208.
2519 - Bridge authorities now accept IPv6 bridge addresses and include
2520 them in network status documents. Implements ticket 5534.
2521 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
2523 o Major features (directory authorities):
2524 - Directory authorities now prefer using measured bandwidths to
2525 advertised ones when computing flags and thresholds. Resolves
2527 - Directory authorities that vote measured bandwidths about more
2528 than a threshold number of relays now treat relays with
2529 unmeasured bandwidths as having bandwidth 0 when computing their
2530 flags. Resolves ticket 8435.
2531 - Directory authorities now support a new consensus method (17)
2532 where they cap the published bandwidth of relays for which
2533 insufficient bandwidth measurements exist. Fixes part of bug 2286.
2534 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
2535 serve any v2 directory information. Now we can test disabling the
2536 old deprecated v2 directory format, and see whether doing so has
2537 any effect on network load. Begins to fix bug 6783.
2539 o Major features (build and portability):
2540 - Switch to a nonrecursive Makefile structure. Now instead of each
2541 Makefile.am invoking other Makefile.am's, there is a master
2542 Makefile.am that includes the others. This change makes our build
2543 process slightly more maintainable, and improves parallelism for
2544 building with make -j. Original patch by Stewart Smith; various
2545 fixes by Jim Meyering.
2546 - Where available, we now use automake's "silent" make rules by
2547 default, so that warnings are easier to spot. You can get the old
2548 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
2549 - Resume building correctly with MSVC and Makefile.nmake. This patch
2550 resolves numerous bugs and fixes reported by ultramage, including
2551 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
2553 o Security features:
2554 - Switch to a completely time-invariant approach for picking nodes
2555 weighted by bandwidth. Our old approach would run through the
2556 part of the loop after it had made its choice slightly slower
2557 than it ran through the part of the loop before it had made its
2558 choice. Addresses ticket 6538.
2559 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
2560 by tor2web clients allows hidden services to identify tor2web
2561 clients through their repeated selection of the same rendezvous
2562 and introduction point circuit endpoints (their guards). Resolves
2565 o Major bugfixes (relay denial of service):
2566 - When we have too much memory queued in circuits (according to a new
2567 MaxMemInCellQueues option), close the circuits that have the oldest
2568 queued cells, on the theory that those are most responsible for
2569 us running low on memory. This prevents us from running out of
2570 memory as a relay if circuits fill up faster than they can be
2571 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
2572 Tor. This bug is a further fix beyond bug 6252, whose fix was
2573 merged into 0.2.3.21-rc.
2574 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
2575 ID: these could be used to create unexpected streams and circuits
2576 which would count as "present" to some parts of Tor but "absent"
2577 to others, leading to zombie circuits and streams or to a bandwidth
2578 denial-of-service. Fixes bug 7889; bugfix on every released version
2579 of Tor. Reported by "oftc_must_be_destroyed".
2580 - Avoid a bug where our response to TLS renegotiation under certain
2581 network conditions could lead to a busy-loop, with 100% CPU
2582 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
2584 o Major bugfixes (asserts, crashes, leaks):
2585 - Prevent the get_freelists() function from running off the end of
2586 the list of freelists if it somehow gets an unrecognized
2587 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
2589 - Avoid a memory leak where we would leak a consensus body when we
2590 find that a consensus which we couldn't previously verify due to
2591 missing certificates is now verifiable. Fixes bug 8719; bugfix
2593 - If we are unable to save a microdescriptor to the journal, do not
2594 drop it from memory and then reattempt downloading it. Fixes bug
2595 9645; bugfix on 0.2.2.6-alpha.
2596 - Fix an assertion failure that would occur when disabling the
2597 ORPort setting on a running Tor process while accounting was
2598 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
2599 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
2600 when an exit connection with optimistic data succeeds immediately
2601 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
2603 - Fix a memory leak that would occur whenever a configuration
2604 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
2606 o Major bugfixes (relay rate limiting):
2607 - When a TLS write is partially successful but incomplete, remember
2608 that the flushed part has been flushed, and notice that bytes were
2609 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
2610 bugfix on Tor 0.1.0.5-rc.
2611 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
2612 to 1GB/1GB. The previous defaults were intended to be "basically
2613 infinite", but it turns out they're now limiting our 100mbit+
2614 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
2615 last time we raised it).
2616 - No longer stop reading or writing on cpuworker connections when
2617 our rate limiting buckets go empty. Now we should handle circuit
2618 handshake requests more promptly. Resolves bug 9731.
2620 o Major bugfixes (client-side privacy):
2621 - When we mark a circuit as unusable for new circuits, have it
2622 continue to be unusable for new circuits even if MaxCircuitDirtiness
2623 is increased too much at the wrong time, or the system clock jumps
2624 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
2625 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
2626 which have resolved to internal addresses") is set, apply that
2627 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
2628 - When an exit relay rejects a stream with reason "exit policy", but
2629 we only know an exit policy summary (e.g. from the microdesc
2630 consensus) for it, do not mark the relay as useless for all exiting.
2631 Instead, mark just the circuit as unsuitable for that particular
2632 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
2634 o Major bugfixes (stream isolation):
2635 - Allow applications to get proper stream isolation with
2636 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
2637 username/password authentication also offer "no authentication". Tor
2638 had previously preferred "no authentication", so the applications
2639 never actually sent Tor their auth details. Now Tor selects
2640 username/password authentication if it's offered. You can disable
2641 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
2642 bug 8117; bugfix on 0.2.3.3-alpha.
2643 - Follow the socks5 protocol when offering username/password
2644 authentication. The fix for bug 8117 exposed this bug, and it
2645 turns out real-world applications like Pidgin do care. Bugfix on
2646 0.2.3.2-alpha; fixes bug 8879.
2648 o Major bugfixes (client circuit building):
2649 - Alter circuit build timeout measurement to start at the point
2650 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
2651 initialization). This should make our timeout measurements more
2652 uniform. Previously, we were sometimes including ORconn setup time
2653 in our circuit build time measurements. Should resolve bug 3443.
2654 - If the circuit build timeout logic is disabled (via the consensus,
2655 or because we are an authority), then don't build testing circuits.
2656 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
2658 o Major bugfixes (client-side DNS):
2659 - Turn off the client-side DNS cache by default. Updating and using
2660 the DNS cache is now configurable on a per-client-port
2661 level. SOCKSPort, DNSPort, etc lines may now contain
2662 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
2663 cache these types of DNS answers when we receive them from an
2664 exit node in response to an application request on this port, and
2665 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
2666 cached DNS answers of these types, we shouldn't use them. It's
2667 potentially risky to use cached DNS answers at the client, since
2668 doing so can indicate to one exit what answers we've gotten
2669 for DNS lookups in the past. With IPv6, this becomes especially
2670 problematic. Using cached DNS answers for requests on the same
2671 circuit would present less linkability risk, since all traffic
2672 on a circuit is already linkable, but it would also provide
2673 little performance benefit: the exit node caches DNS replies
2674 too. Implements a simplified version of Proposal 205. Implements
2677 o Major bugfixes (hidden service privacy):
2678 - Limit hidden service descriptors to at most ten introduction
2679 points, to slow one kind of guard enumeration. Fixes bug 9002;
2680 bugfix on 0.1.1.11-alpha.
2682 o Major bugfixes (directory fetching):
2683 - If the time to download the next old-style networkstatus is in
2684 the future, do not decline to consider whether to download the
2685 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
2687 - We used to always request authority certificates by identity digest,
2688 meaning we'd get the newest one even when we wanted one with a
2689 different signing key. Then we would complain about being given
2690 a certificate we already had, and never get the one we really
2691 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
2692 resource to request the one we want. Fixes bug 5595; bugfix on
2695 o Major bugfixes (bridge reachability):
2696 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
2697 previously they did not, which prevented them from receiving
2698 successful connections from relays for self-test or bandwidth
2699 testing. Also, when a relay is extending a circuit to a bridge,
2700 it needs to send a NETINFO cell, even when the bridge hasn't sent
2701 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
2703 o Major bugfixes (control interface):
2704 - When receiving a new configuration file via the control port's
2705 LOADCONF command, do not treat the defaults file as absent.
2706 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
2708 o Major bugfixes (directory authorities):
2709 - Stop marking every relay as having been down for one hour every
2710 time we restart a directory authority. These artificial downtimes
2711 were messing with our Stable and Guard flag calculations. Fixes
2712 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
2713 - When computing directory thresholds, ignore any rejected-as-sybil
2714 nodes during the computation so that they can't influence Fast,
2715 Guard, etc. (We should have done this for proposal 109.) Fixes
2717 - When marking a node as a likely sybil, reset its uptime metrics
2718 to zero, so that it cannot time towards getting marked as Guard,
2719 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
2721 - Fix a bug in the voting algorithm that could yield incorrect results
2722 when a non-naming authority declared too many flags. Fixes bug 9200;
2723 bugfix on 0.2.0.3-alpha.
2725 o Internal abstraction features:
2726 - Introduce new channel_t abstraction between circuits and
2727 or_connection_t to allow for implementing alternate OR-to-OR
2728 transports. A channel_t is an abstract object which can either be a
2729 cell-bearing channel, which is responsible for authenticating and
2730 handshaking with the remote OR and transmitting cells to and from
2731 it, or a listening channel, which spawns new cell-bearing channels
2732 at the request of remote ORs. Implements part of ticket 6465.
2733 - Make a channel_tls_t subclass of channel_t, adapting it to the
2734 existing or_connection_t code. The V2/V3 protocol handshaking
2735 code which formerly resided in command.c has been moved below the
2736 channel_t abstraction layer and may be found in channeltls.c now.
2737 Implements the rest of ticket 6465.
2738 - Introduce new circuitmux_t storing the queue of circuits for
2739 a channel; this encapsulates and abstracts the queue logic and
2740 circuit selection policy, and allows the latter to be overridden
2741 easily by switching out a policy object. The existing EWMA behavior
2742 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
2744 o New build requirements:
2745 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
2746 strongly recommended.
2747 - Tor maintainers now require Automake version 1.9 or later to build
2748 Tor from the Git repository. (Automake is not required when building
2749 from a source distribution.)
2751 o Minor features (protocol):
2752 - No longer include the "opt" prefix when generating routerinfos
2753 or v2 directories: it has been needless since Tor 0.1.2. Closes
2755 - Reject EXTEND cells sent to nonexistent streams. According to the
2756 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
2757 we were only checking for stream IDs that were currently in use.
2758 Found while hunting for more instances of bug 6271. Bugfix on
2759 0.0.2pre8, which introduced incremental circuit construction.
2760 - Tor relays and clients now support a better CREATE/EXTEND cell
2761 format, allowing the sender to specify multiple address, identity,
2762 and handshake types. Implements Robert Ransom's proposal 200;
2764 - Reject as invalid most directory objects containing a NUL.
2765 Belt-and-suspender fix for bug 8037.
2767 o Minor features (security):
2768 - Clear keys and key-derived material left on the stack in
2769 rendservice.c and rendclient.c. Check return value of
2770 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
2771 These fixes should make us more forward-secure against cold-boot
2772 attacks and the like. Fixes bug 2385.
2773 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
2774 Irix's random() only return 15 bits; Solaris's random() returns more
2775 bits but its RAND_MAX says it only returns 15, and so on. Motivated
2776 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
2778 o Minor features (control protocol):
2779 - Add a "GETINFO signal/names" control port command. Implements
2781 - Provide default values for all options via "GETINFO config/defaults".
2782 Implements ticket 4971.
2783 - Allow an optional $ before the node identity digest in the
2784 controller command GETINFO ns/id/<identity>, for consistency with
2785 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
2786 - Add CACHED keyword to ADDRMAP events in the control protocol
2787 to indicate whether a DNS result will be cached or not. Resolves
2789 - Generate bootstrapping status update events correctly when fetching
2790 microdescriptors. Fixes bug 9927.
2792 o Minor features (path selection):
2793 - When deciding whether we have enough descriptors to build circuits,
2794 instead of looking at raw relay counts, look at which fraction
2795 of (bandwidth-weighted) paths we're able to build. This approach
2796 keeps clients from building circuits if their paths are likely to
2797 stand out statistically. The default fraction of paths needed is
2798 taken from the consensus directory; you can override it with the
2799 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
2800 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
2801 and we have GeoIP information, also exclude all nodes with unknown
2802 countries "??" and "A1". This behavior is controlled by the
2803 new GeoIPExcludeUnknown option: you can make such nodes always
2804 excluded with "GeoIPExcludeUnknown 1", and disable the feature
2805 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
2806 gets you the default behavior. Implements feature 7706.
2808 o Minor features (hidden services):
2809 - Improve circuit build timeout handling for hidden services.
2810 In particular: adjust build timeouts more accurately depending
2811 upon the number of hop-RTTs that a particular circuit type
2812 undergoes. Additionally, launch intro circuits in parallel
2813 if they timeout, and take the first one to reply as valid.
2814 - The Tor client now ignores sub-domain components of a .onion
2815 address. This change makes HTTP "virtual" hosting
2816 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
2817 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
2818 hosted on the same hidden service. Implements proposal 204.
2819 - Enable Tor to read configuration, state, and key information from
2820 a FIFO. Previously Tor would only read from files with a positive
2821 stat.st_size. Code from meejah; fixes bug 6044.
2823 o Minor features (clients):
2824 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
2825 microdescriptor-related dir requests, and only fall back to normal
2826 descriptors if none of their bridges can handle microdescriptors
2827 (as opposed to the fix in ticket 4013, which caused them to fall
2828 back to normal descriptors if *any* of their bridges preferred
2829 them). Resolves ticket 4994.
2830 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
2831 TCP ports to forward. In the past it only accepted two ports:
2832 the ORPort and the DirPort.
2834 o Minor features (protecting client timestamps):
2835 - Clients no longer send timestamps in their NETINFO cells. These were
2836 not used for anything, and they provided one small way for clients
2837 to be distinguished from each other as they moved from network to
2838 network or behind NAT. Implements part of proposal 222.
2839 - Clients now round timestamps in INTRODUCE cells down to the nearest
2840 10 minutes. If a new Support022HiddenServices option is set to 0, or
2841 if it's set to "auto" and the feature is disabled in the consensus,
2842 the timestamp is sent as 0 instead. Implements part of proposal 222.
2843 - Stop sending timestamps in AUTHENTICATE cells. This is not such
2844 a big deal from a security point of view, but it achieves no actual
2845 good purpose, and isn't needed. Implements part of proposal 222.
2846 - Reduce down accuracy of timestamps in hidden service descriptors.
2847 Implements part of proposal 222.
2849 o Minor features (bridges):
2850 - Make bridge relays check once a minute for whether their IP
2851 address has changed, rather than only every 15 minutes. Resolves
2853 - Bridge statistics now count bridge clients connecting over IPv6:
2854 bridge statistics files now list "bridge-ip-versions" and
2855 extra-info documents list "geoip6-db-digest". The control protocol
2856 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
2857 implementation by "shkoo", addressing ticket 5055.
2858 - Add a new torrc option "ServerTransportListenAddr" to let bridge
2859 operators select the address where their pluggable transports will
2860 listen for connections. Resolves ticket 7013.
2861 - Randomize the lifetime of our SSL link certificate, so censors can't
2862 use the static value for filtering Tor flows. Resolves ticket 8443;
2863 related to ticket 4014 which was included in 0.2.2.33.
2865 o Minor features (relays):
2866 - Option OutboundBindAddress can be specified multiple times and
2867 accepts IPv6 addresses. Resolves ticket 6876.
2869 o Minor features (IPv6, client side):
2870 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
2871 prefer to hand out virtual IPv6 addresses, since there are more of
2872 them and we can't run out. To override this behavior and make IPv4
2873 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
2874 or DNSPort you're using for resolving. Implements ticket 7571.
2875 - AutomapHostsOnResolve responses are now randomized, to avoid
2876 annoying situations where Tor is restarted and applications
2877 connect to the wrong addresses.
2878 - Never try more than 1000 times to pick a new virtual address when
2879 AutomapHostsOnResolve is set. That's good enough so long as we
2880 aren't close to handing out our entire virtual address space;
2881 if you're getting there, it's best to switch to IPv6 virtual
2884 o Minor features (IPv6, relay/authority side):
2885 - New config option "AuthDirHasIPv6Connectivity 1" that directory
2886 authorities should set if they have IPv6 connectivity and want to
2887 do reachability tests for IPv6 relays. Implements feature 5974.
2888 - A relay with an IPv6 OR port now sends that address in NETINFO
2889 cells (in addition to its other address). Implements ticket 6364.
2891 o Minor features (directory authorities):
2892 - Directory authorities no long accept descriptors for any version of
2893 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
2894 These versions are insecure, unsupported, or both. Implements
2896 - When directory authorities are computing thresholds for flags,
2897 never let the threshold for the Fast flag fall below 4096
2898 bytes. Also, do not consider nodes with extremely low bandwidths
2899 when deciding thresholds for various directory flags. This change
2900 should raise our threshold for Fast relays, possibly in turn
2901 improving overall network performance; see ticket 1854. Resolves
2903 - Directory authorities now include inside each vote a statement of
2904 the performance thresholds they used when assigning flags.
2905 Implements ticket 8151.
2906 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
2907 in directory authority votes to describe whether they have enough
2908 measured bandwidths to ignore advertised (relay descriptor)
2909 bandwidth claims. Resolves ticket 8711.
2911 o Minor features (path bias detection):
2912 - Path Use Bias: Perform separate accounting for successful circuit
2913 use. Keep separate statistics on stream attempt rates versus stream
2914 success rates for each guard. Provide configurable thresholds to
2915 determine when to emit log messages or disable use of guards that
2916 fail too many stream attempts. Resolves ticket 7802.
2917 - Create three levels of Path Bias log messages, as opposed to just
2918 two. These are configurable via consensus as well as via the torrc
2919 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
2920 The default values are 0.70, 0.50, and 0.30 respectively.
2921 - Separate the log message levels from the decision to drop guards,
2922 which also is available via torrc option PathBiasDropGuards.
2923 PathBiasDropGuards still defaults to 0 (off).
2924 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
2925 in combination with PathBiasExtremeRate.
2926 - Increase the default values for PathBiasScaleThreshold and
2927 PathBiasCircThreshold from (200, 20) to (300, 150).
2928 - Add in circuit usage accounting to path bias. If we try to use a
2929 built circuit but fail for any reason, it counts as path bias.
2930 Certain classes of circuits where the adversary gets to pick your
2931 destination node are exempt from this accounting. Usage accounting
2932 can be specifically disabled via consensus parameter or torrc.
2933 - Convert all internal path bias state to double-precision floating
2934 point, to avoid roundoff error and other issues.
2935 - Only record path bias information for circuits that have completed
2936 *two* hops. Assuming end-to-end tagging is the attack vector, this
2937 makes us more resilient to ambient circuit failure without any
2938 detection capability loss.
2940 o Minor features (build):
2941 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
2942 dhill. Resolves ticket 6982.
2943 - Compile on win64 using mingw64. Fixes bug 7260; patches from
2945 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
2946 separate error codes; or at least, don't break for that reason.
2947 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
2949 o Build improvements (autotools):
2950 - Warn if building on a platform with an unsigned time_t: there
2951 are too many places where Tor currently assumes that time_t can
2952 hold negative values. We'd like to fix them all, but probably
2954 - Do not report status verbosely from autogen.sh unless the -v flag
2955 is specified. Fixes issue 4664. Patch from Onizuka.
2956 - Detect and reject attempts to build Tor with threading support
2957 when OpenSSL has been compiled without threading support.
2959 - Try to detect if we are ever building on a platform where
2960 memset(...,0,...) does not set the value of a double to 0.0. Such
2961 platforms are permitted by the C standard, though in practice
2962 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
2963 currently support them, but it's better to detect them and fail
2964 than to perform erroneously.
2965 - We no longer warn so much when generating manpages from their
2967 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
2968 the signs of types during autoconf. This is better than our old
2969 approach, which didn't work when cross-compiling.
2971 o Minor features (log messages, warnings):
2972 - Detect when we're running with a version of OpenSSL other than the
2973 one we compiled with. This conflict has occasionally given people
2974 hard-to-track-down errors.
2975 - Warn users who run hidden services on a Tor client with
2976 UseEntryGuards disabled that their hidden services will be
2977 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
2978 attack which motivated Tor to support entry guards in the first
2979 place). Resolves ticket 6889.
2980 - Warn when we are binding low ports when hibernation is enabled;
2981 previously we had warned when we were _advertising_ low ports with
2982 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
2983 - Issue a warning when running with the bufferevents backend enabled.
2984 It's still not stable, and people should know that they're likely
2985 to hit unexpected problems. Closes ticket 9147.
2987 o Minor features (log messages, notices):
2988 - Refactor resolve_my_address() so it returns the method by which we
2989 decided our public IP address (explicitly configured, resolved from
2990 explicit hostname, guessed from interfaces, learned by gethostname).
2991 Now we can provide more helpful log messages when a relay guesses
2992 its IP address incorrectly (e.g. due to unexpected lines in
2993 /etc/hosts). Resolves ticket 2267.
2994 - Track how many "TAP" and "NTor" circuit handshake requests we get,
2995 and how many we complete, and log it every hour to help relay
2996 operators follow trends in network load. Addresses ticket 9658.
2998 o Minor features (log messages, diagnostics):
2999 - If we fail to free a microdescriptor because of bug 7164, log
3000 the filename and line number from which we tried to free it.
3001 - We compute the overhead from passing onionskins back and forth to
3002 cpuworkers, and report it when dumping statistics in response to
3003 SIGUSR1. Supports ticket 7291.
3004 - Add another diagnostic to the heartbeat message: track and log
3005 overhead that TLS is adding to the data we write. If this is
3006 high, we are sending too little data to SSL_write at a time.
3007 Diagnostic for bug 7707.
3008 - Log packaged cell fullness as part of the heartbeat message.
3009 Diagnosis to try to determine the extent of bug 7743.
3010 - Add more detail to a log message about relaxed timeouts, to help
3012 - When learning a fingerprint for a bridge, log its corresponding
3013 transport type. Implements ticket 7896.
3014 - Warn more aggressively when flushing microdescriptors to a
3015 microdescriptor cache fails, in an attempt to mitigate bug 8031,
3016 or at least make it more diagnosable.
3017 - Improve the log message when "Bug/attack: unexpected sendme cell
3018 from client" occurs, to help us track bug 8093.
3019 - Improve debugging output to help track down bug 8185 ("Bug:
3020 outgoing relay cell has n_chan==NULL. Dropping.")
3022 o Minor features (log messages, quieter bootstrapping):
3023 - Log fewer lines at level "notice" about our OpenSSL and Libevent
3024 versions and capabilities when everything is going right. Resolves
3025 part of ticket 6736.
3026 - Omit the first heartbeat log message, because it never has anything
3027 useful to say, and it clutters up the bootstrapping messages.
3028 Resolves ticket 6758.
3029 - Don't log about reloading the microdescriptor cache at startup. Our
3030 bootstrap warnings are supposed to tell the user when there's a
3031 problem, and our bootstrap notices say when there isn't. Resolves
3032 ticket 6759; bugfix on 0.2.2.6-alpha.
3033 - Don't log "I learned some more directory information" when we're
3034 reading cached directory information. Reserve it for when new
3035 directory information arrives in response to a fetch. Resolves
3037 - Don't complain about bootstrapping problems while hibernating.
3038 These complaints reflect a general code problem, but not one
3039 with any problematic effects (no connections are actually
3040 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
3042 o Minor features (testing):
3043 - In our testsuite, create temporary directories with a bit more
3044 entropy in their name to make name collisions less likely. Fixes
3046 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
3047 (P-256) Diffie-Hellman handshakes to src/or/bench.
3048 - Add benchmark functions to test onion handshake performance.
3051 - The DirServer option is now DirAuthority, for consistency with
3052 current naming patterns. You can still use the old DirServer form.
3054 o Minor bugfixes (protocol):
3055 - Fix the handling of a TRUNCATE cell when it arrives while the
3056 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
3057 - When a Tor client gets a "truncated" relay cell, the first byte of
3058 its payload specifies why the circuit was truncated. We were
3059 ignoring this 'reason' byte when tearing down the circuit, resulting
3060 in the controller not being told why the circuit closed. Now we
3061 pass the reason from the truncated cell to the controller. Bugfix
3062 on 0.1.2.3-alpha; fixes bug 7039.
3063 - Fix a misframing issue when reading the version numbers in a
3064 VERSIONS cell. Previously we would recognize [00 01 00 02] as
3065 'version 1, version 2, and version 0x100', when it should have
3066 only included versions 1 and 2. Fixes bug 8059; bugfix on
3067 0.2.0.10-alpha. Reported pseudonymously.
3068 - Make the format and order of STREAM events for DNS lookups
3069 consistent among the various ways to launch DNS lookups. Fixes
3070 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
3072 o Minor bugfixes (syscalls and disk interaction):
3073 - Always check the return values of functions fcntl() and
3074 setsockopt(). We don't believe these are ever actually failing in
3075 practice, but better safe than sorry. Also, checking these return
3076 values should please analysis tools like Coverity. Patch from
3077 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
3078 - Avoid double-closing the listener socket in our socketpair()
3079 replacement (used on Windows) in the case where the addresses on
3080 our opened sockets don't match what we expected. Fixes bug 9400;
3081 bugfix on 0.0.2pre7. Found by Coverity.
3082 - Correctly store microdescriptors and extrainfo descriptors that
3083 include an internal NUL byte. Fixes bug 8037; bugfix on
3084 0.2.0.1-alpha. Bug reported by "cypherpunks".
3085 - If for some reason we fail to write a microdescriptor while
3086 rebuilding the cache, do not let the annotations from that
3087 microdescriptor linger in the cache file, and do not let the
3088 microdescriptor stay recorded as present in its old location.
3089 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
3090 - Use direct writes rather than stdio when building microdescriptor
3091 caches, in an attempt to mitigate bug 8031, or at least make it
3094 o Minor fixes (config options):
3095 - Warn and fail if a server is configured not to advertise any
3096 ORPorts at all. (We need *something* to put in our descriptor,
3097 or we just won't work.)
3098 - Behave correctly when the user disables LearnCircuitBuildTimeout
3099 but doesn't tell us what they would like the timeout to be. Fixes
3100 bug 6304; bugfix on 0.2.2.14-alpha.
3101 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
3102 to start with a triple-underscore so the controller won't touch it.
3103 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
3104 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
3105 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
3106 - When autodetecting the number of CPUs, use the number of available
3107 CPUs in preference to the number of configured CPUs. Inform the
3108 user if this reduces the number of available CPUs. Fixes bug 8002;
3109 bugfix on 0.2.3.1-alpha.
3110 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
3111 - Make it an error when you set EntryNodes but disable UseGuardNodes,
3112 since it will (surprisingly to some users) ignore EntryNodes. Fixes
3113 bug 8180; bugfix on 0.2.3.11-alpha.
3114 - Avoid overflows when the user sets MaxCircuitDirtiness to a
3115 ridiculously high value, by imposing a (ridiculously high) 30-day
3116 maximum on MaxCircuitDirtiness.
3118 o Minor bugfixes (control protocol):
3119 - Stop sending a stray "(null)" in some cases for the server status
3120 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
3122 - The ADDRMAP command can no longer generate an ill-formed error
3123 code on a failed MAPADDRESS. It now says "internal" rather than
3124 an English sentence fragment with spaces in the middle. Bugfix on
3127 o Minor bugfixes (clients / edges):
3128 - When we receive a RELAY_END cell with the reason DONE, or with no
3129 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
3130 status as "connection refused". Previously we reported these cases
3131 as success but then immediately closed the connection. Fixes bug
3132 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
3133 - If the guard we choose first doesn't answer, we would try the
3134 second guard, but once we connected to the second guard we would
3135 abandon it and retry the first one, slowing down bootstrapping.
3136 The fix is to treat all our initially chosen guards as acceptable
3137 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
3138 - When choosing which stream on a formerly stalled circuit to wake
3139 first, make better use of the platform's weak RNG. Previously,
3140 we had been using the % ("modulo") operator to try to generate a
3141 1/N chance of picking each stream, but this behaves badly with
3142 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
3145 o Minor bugfixes (path bias detection):
3146 - If the state file's path bias counts are invalid (presumably from a
3147 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
3148 additional checks and log messages to the scaling of Path Bias
3149 counts, in case there still are remaining issues with scaling.
3150 Should help resolve bug 8235.
3151 - Prevent rounding error in path bias counts when scaling
3152 them down, and use the correct scale factor default. Also demote
3153 some path bias related log messages down a level and make others
3154 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
3155 - Remove a source of rounding error during path bias count scaling;
3156 don't count cannibalized circuits as used for path bias until we
3157 actually try to use them; and fix a circuit_package_relay_cell()
3158 warning message about n_chan==NULL. Fixes bug 7802.
3159 - Paste the description for PathBias parameters from the man
3160 page into or.h, so the code documents them too. Fixes bug 7982;
3161 bugfix on 0.2.3.17-beta.
3163 o Minor bugfixes (relays):
3164 - Stop trying to resolve our hostname so often (e.g. every time we
3165 think about doing a directory fetch). Now we reuse the cached
3166 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
3167 and 2410 (bugfix on 0.1.2.2-alpha).
3168 - When examining the list of network interfaces to find our address,
3169 do not consider non-running or disabled network interfaces. Fixes
3170 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
3172 o Minor bugfixes (blocking resistance):
3173 - Only disable TLS session ticket support when running as a TLS
3174 server. Now clients will blend better with regular Firefox
3175 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
3177 o Minor bugfixes (IPv6):
3178 - Use square brackets around IPv6 addresses in numerous places
3179 that needed them, including log messages, HTTPS CONNECT proxy
3180 requests, TransportProxy statefile entries, and pluggable transport
3181 extra-info lines. Fixes bug 7011; patch by David Fifield.
3183 o Minor bugfixes (directory authorities):
3184 - Reject consensus votes with more than 64 known-flags. We aren't even
3185 close to that limit yet, and our code doesn't handle it correctly.
3186 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
3187 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
3188 bugfix on 0.2.0.3-alpha.
3190 o Minor bugfixes (memory leaks):
3191 - Avoid leaking memory if we fail to compute a consensus signature
3192 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
3193 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
3194 on 0.2.1.1-alpha; fixes bug 7816.
3195 - Fix a memory leak during safe-cookie controller authentication.
3196 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
3197 - Free some more still-in-use memory at exit, to make hunting for
3198 memory leaks easier. Resolves bug 7029.
3200 o Minor bugfixes (code correctness):
3201 - Increase the width of the field used to remember a connection's
3202 link protocol version to two bytes. Harmless for now, since the
3203 only currently recognized versions are one byte long. Reported
3204 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
3205 - Fix a crash when debugging unit tests on Windows: deallocate a
3206 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
3207 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
3208 - When detecting the largest possible file descriptor (in order to
3209 close all file descriptors when launching a new program), actually
3210 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
3211 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
3213 - Avoid a crash if we fail to generate an extrainfo descriptor.
3214 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
3216 - Avoid an off-by-one error when checking buffer boundaries when
3217 formatting the exit status of a pluggable transport helper.
3218 This is probably not an exploitable bug, but better safe than
3219 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
3221 - Get rid of a couple of harmless clang warnings, where we compared
3222 enums to ints. These warnings are newly introduced in clang 3.2.
3224 o Minor bugfixes (code cleanliness):
3225 - Avoid use of reserved identifiers in our C code. The C standard
3226 doesn't like us declaring anything that starts with an
3227 underscore, so let's knock it off before we get in trouble. Fix
3228 for bug 1031; bugfix on the first Tor commit.
3229 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
3230 with large values. This situation was untriggered, but nevertheless
3231 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
3232 - Fix an impossible buffer overrun in the AES unit tests. Fixes
3233 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
3234 - Fix handling of rendezvous client authorization types over 8.
3235 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
3236 - Remove a couple of extraneous semicolons that were upsetting the
3237 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
3238 bugfix on 0.2.2.1-alpha.
3239 - When complaining about a client port on a public address, log
3240 which address we're complaining about. Fixes bug 4020; bugfix on
3241 0.2.3.3-alpha. Patch by Tom Fitzhenry.
3243 o Minor bugfixes (log messages, warnings):
3244 - If we encounter a write failure on a SOCKS connection before we
3245 finish our SOCKS handshake, don't warn that we closed the
3246 connection before we could send a SOCKS reply. Fixes bug 8427;
3247 bugfix on 0.1.0.1-rc.
3248 - Fix a directory authority warn caused when we have a large amount
3249 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
3250 - Downgrade "Failed to hand off onionskin" messages to "debug"
3251 severity, since they're typically redundant with the "Your computer
3252 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
3253 - Avoid spurious warnings when configuring multiple client ports of
3254 which only some are nonlocal. Previously, we had claimed that some
3255 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
3258 o Minor bugfixes (log messages, other):
3259 - Fix log messages and comments to avoid saying "GMT" when we mean
3260 "UTC". Fixes bug 6113.
3261 - When rejecting a configuration because we were unable to parse a
3262 quoted string, log an actual error message. Fixes bug 7950; bugfix
3264 - Correctly recognize that [::1] is a loopback address. Fixes
3265 bug 8377; bugfix on 0.2.1.3-alpha.
3266 - Don't log inappropriate heartbeat messages when hibernating: a
3267 hibernating node is _expected_ to drop out of the consensus,
3268 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
3269 bugfix on 0.2.3.1-alpha.
3270 - Eliminate several instances where we use "Nickname=ID" to refer to
3271 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
3272 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
3275 o Minor bugfixes (build):
3276 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
3277 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
3278 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
3280 o Documentation fixes:
3281 - Make the torify manpage no longer refer to tsocks; torify hasn't
3282 supported tsocks since 0.2.3.14-alpha.
3283 - Make the tor manpage no longer reference tsocks.
3284 - Fix the GeoIPExcludeUnknown documentation to refer to
3285 ExcludeExitNodes rather than the currently nonexistent
3286 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
3287 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
3289 - Say "KBytes" rather than "KB" in the man page (for various values
3290 of K), to further reduce confusion about whether Tor counts in
3291 units of memory or fractions of units of memory. Resolves ticket 7054.
3292 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
3293 names match. Fixes bug 7768.
3294 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
3295 message is logged at notice, not at info.
3296 - Clarify the usage and risks of setting the ContactInfo torrc line
3297 for your relay or bridge. Resolves ticket 9854.
3298 - Add anchors to the manpage so we can link to the html version of
3299 the documentation for specific options. Resolves ticket 9866.
3300 - Replace remaining references to DirServer in man page and
3301 log entries. Resolves ticket 10124.
3304 - Stop exporting estimates of v2 and v3 directory traffic shares
3305 in extrainfo documents. They were unneeded and sometimes inaccurate.
3306 Also stop exporting any v2 directory request statistics. Resolves
3308 - Drop support for detecting and warning about versions of Libevent
3309 before 1.3e. Nothing reasonable ships with them any longer; warning
3310 the user about them shouldn't be needed. Resolves ticket 6826.
3311 - Now that all versions before 0.2.2.x are disallowed, we no longer
3312 need to work around their missing features. Remove a bunch of
3316 - The tor-tsocks.conf is no longer distributed or installed. We
3317 recommend that tsocks users use torsocks instead. Resolves
3319 - Remove some of the older contents of doc/ as obsolete; move others
3320 to torspec.git. Fixes bug 8965.
3322 o Code simplification:
3323 - Avoid using character buffers when constructing most directory
3324 objects: this approach was unwieldy and error-prone. Instead,
3325 build smartlists of strings, and concatenate them when done.
3326 - Rename "isin" functions to "contains", for grammar. Resolves
3328 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
3329 with the natural logarithm function from the system libm. Resolves
3331 - Start using OpenBSD's implementation of queue.h, so that we don't
3332 need to hand-roll our own pointer and list structures whenever we
3333 need them. (We can't rely on a sys/queue.h, since some operating
3334 systems don't have them, and the ones that do have them don't all
3335 present the same extensions.)
3336 - Start using OpenBSD's implementation of queue.h (originally by
3338 - Enhance our internal sscanf replacement so that we can eliminate
3339 the last remaining uses of the system sscanf. (Though those uses
3340 of sscanf were safe, sscanf itself is generally error prone, so
3341 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
3343 - Replace all calls to snprintf() outside of src/ext with
3344 tor_snprintf(). Also remove the #define to replace snprintf with
3345 _snprintf on Windows; they have different semantics, and all of
3346 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
3349 - Add a wrapper function for the common "log a message with a
3351 - Split the onion.c file into separate modules for the onion queue
3352 and the different handshakes it supports.
3353 - Move the client-side address-map/virtual-address/DNS-cache code
3354 out of connection_edge.c into a new addressmap.c module.
3355 - Move the entry node code from circuitbuild.c to its own file.
3356 - Move the circuit build timeout tracking code from circuitbuild.c
3358 - Source files taken from other packages now reside in src/ext;
3359 previously they were scattered around the rest of Tor.
3360 - Move the generic "config" code into a new file, and have "config.c"
3361 hold only torrc- and state-related code. Resolves ticket 6823.
3362 - Move the core of our "choose a weighted element at random" logic
3363 into its own function, and give it unit tests. Now the logic is
3364 testable, and a little less fragile too.
3365 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
3366 - Move last_reachable and testing_since from routerinfo_t to node_t.
3367 Implements ticket 5529.
3368 - Add replaycache_t structure, functions and unit tests, then refactor
3369 rend_service_introduce() to be more clear to read, improve, debug,
3370 and test. Resolves bug 6177.
3373 - Remove some now-needless code that tried to aggressively flush
3374 OR connections as data was added to them. Since 0.2.0.1-alpha, our
3375 cell queue logic has saved us from the failure mode that this code
3376 was supposed to prevent. Removing this code will limit the number
3377 of baroque control flow paths through Tor's network logic. Reported
3378 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
3379 - Remove unused code for parsing v1 directories and "running routers"
3380 documents. Fixes bug 6887.
3381 - Remove the marshalling/unmarshalling code for sending requests to
3382 cpuworkers over a socket, and instead just send structs. The
3383 recipient will always be the same Tor binary as the sender, so
3384 any encoding is overkill.
3385 - Remove the testing_since field of node_t, which hasn't been used
3386 for anything since 0.2.0.9-alpha.
3387 - Finally remove support for malloc_good_size and malloc_usable_size.
3388 We had hoped that these functions would let us eke a little more
3389 memory out of our malloc implementation. Unfortunately, the only
3390 implementations that provided these functions are also ones that
3391 are already efficient about not overallocation: they never got us
3392 more than 7 or so bytes per allocation. Removing them saves us a
3393 little code complexity and a nontrivial amount of build complexity.
3396 Changes in version 0.2.3.25 - 2012-11-19
3397 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
3398 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
3399 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
3400 programmer, and friend. Unstinting in his dedication to the cause of
3401 freedom, he inspired and helped many of us as we began our work on
3402 anonymity, and inspires us still. Please honor his memory by writing
3403 software to protect people's freedoms, and by helping others to do so.
3405 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
3406 significantly reduced directory overhead (via microdescriptors),
3407 enormous crypto performance improvements for fast relays on new
3408 enough hardware, a new v3 TLS handshake protocol that can better
3409 resist fingerprinting, support for protocol obfuscation plugins (aka
3410 pluggable transports), better scalability for hidden services, IPv6
3411 support for bridges, performance improvements like allowing clients
3412 to skip the first round-trip on the circuit ("optimistic data") and
3413 refilling token buckets more often, a new "stream isolation" design
3414 to isolate different applications on different circuits, and many
3415 stability, security, and privacy fixes.
3417 Major features (v3 directory protocol):
3418 - Clients now use microdescriptors instead of regular descriptors
3419 to build circuits. Microdescriptors are authority-generated
3420 summaries of regular descriptors' contents, designed to change very
3421 rarely (see proposal 158 for details). This feature is designed
3422 to save bandwidth, especially for clients on slow internet
3423 connections. Use "UseMicrodescriptors 0" to disable it.
3424 - Caches now download, cache, and serve microdescriptors, as well
3425 as multiple "flavors" of the consensus, including a flavor that
3426 describes microdescriptors.
3428 o Major features (build hardening):
3429 - Enable gcc and ld hardening by default. Resolves ticket 5210.
3431 o Major features (relay scaling):
3432 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
3433 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
3434 vectorized AES implementations as appropriate. These can be much,
3435 much faster than other AES implementations.
3436 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
3437 implementation. It makes AES_CTR about 7% faster than our old one
3438 (which was about 10% faster than the one OpenSSL used to provide).
3439 Resolves ticket 4526.
3440 - Use OpenSSL's EVP interface for AES encryption, so that all AES
3441 operations can use hardware acceleration (if present). Resolves
3443 - Unconditionally use OpenSSL's AES implementation instead of our
3444 old built-in one. OpenSSL's AES has been better for a while, and
3445 relatively few servers should still be on any version of OpenSSL
3446 that doesn't have good optimized assembly AES.
3448 o Major features (blocking resistance):
3449 - Update TLS cipher list to match Firefox 8 and later. Resolves
3451 - Remove support for clients falsely claiming to support standard
3452 ciphersuites that they can actually provide. As of modern OpenSSL
3453 versions, it's not necessary to fake any standard ciphersuite,
3454 and doing so prevents us from using better ciphersuites in the
3455 future, since servers can't know whether an advertised ciphersuite
3456 is really supported or not. Some hosts -- notably, ones with very
3457 old versions of OpenSSL or where OpenSSL has been built with ECC
3458 disabled -- will stand out because of this change; TBB users should
3459 not be affected. Implements the client side of proposal 198.
3460 - Implement a new handshake protocol (v3) for authenticating Tors to
3461 each other over TLS. It should be more resistant to fingerprinting
3462 than previous protocols, and should require less TLS hacking for
3463 future Tor implementations. Implements proposal 176.
3464 - Allow variable-length padding cells, to disguise the length of
3465 Tor's TLS records. Implements part of proposal 184.
3466 - While we're trying to bootstrap, record how many TLS connections
3467 fail in each state, and report which states saw the most failures
3468 in response to any bootstrap failures. This feature may speed up
3469 diagnosis of censorship events. Implements ticket 3116.
3471 o Major features (pluggable transports):
3472 - Clients and bridges can now be configured to use a separate
3473 "transport" proxy. This approach makes the censorship arms race
3474 easier by allowing bridges to use protocol obfuscation plugins.
3475 Implements proposal 180 (tickets 2841 and 3472).
3477 o Major features (DoS resistance):
3478 - Now that Tor 0.2.0.x is completely deprecated, enable the final
3479 part of "Proposal 110: Avoiding infinite length circuits" by
3480 refusing all circuit-extend requests that do not use a relay_early
3481 cell. This change helps Tor resist a class of denial-of-service
3482 attacks by limiting the maximum circuit length.
3483 - Tear down the circuit if we get an unexpected SENDME cell. Clients
3484 could use this trick to make their circuits receive cells faster
3485 than our flow control would have allowed, or to gum up the network,
3486 or possibly to do targeted memory denial-of-service attacks on
3487 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
3488 from July 2002, before the release of Tor 0.0.0.
3490 o Major features (hidden services):
3491 - Adjust the number of introduction points that a hidden service
3492 will try to maintain based on how long its introduction points
3493 remain in use and how many introductions they handle. Fixes
3495 - Add a "tor2web mode" for clients that want to connect to hidden
3496 services non-anonymously (and possibly more quickly). As a safety
3497 measure to try to keep users from turning this on without knowing
3498 what they are doing, tor2web mode must be explicitly enabled at
3499 compile time, and a copy of Tor compiled to run in tor2web mode
3500 cannot be used as a normal Tor client. Implements feature 2553.
3502 o Major features (IPv6):
3503 - Clients can now connect to private bridges over IPv6. Bridges
3504 still need at least one IPv4 address in order to connect to
3505 other relays. Note that we don't yet handle the case where the
3506 user has two bridge lines for the same bridge (one IPv4, one
3507 IPv6). Implements parts of proposal 186.
3509 o Major features (directory authorities):
3510 - Use a more secure consensus parameter voting algorithm. Now at
3511 least three directory authorities or a majority of them must
3512 vote on a given parameter before it will be included in the
3513 consensus. Implements proposal 178.
3514 - Remove the artificially low cutoff of 20KB to guarantee the Fast
3515 flag. In the past few years the average relay speed has picked
3516 up, and while the "top 7/8 of the network get the Fast flag" and
3517 "all relays with 20KB or more of capacity get the Fast flag" rules
3518 used to have the same result, now the top 7/8 of the network has
3519 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
3521 o Major features (performance):
3522 - Exit nodes now accept and queue data on not-yet-connected streams.
3523 Previously, the client wasn't allowed to send data until the
3524 stream was connected, which slowed down all connections. This
3525 change will enable clients to perform a "fast-start" on streams
3526 and send data without having to wait for a confirmation that the
3527 stream has opened. Patch from Ian Goldberg; implements the server
3528 side of Proposal 174.
3529 - When using an exit relay running 0.2.3.x, clients can now
3530 "optimistically" send data before the exit relay reports that
3531 the stream has opened. This saves a round trip when starting
3532 connections where the client speaks first (such as web browsing).
3533 This behavior is controlled by a consensus parameter (currently
3534 disabled). To turn it on or off manually, use the "OptimisticData"
3535 torrc option. Implements proposal 181; code by Ian Goldberg.
3536 - Add a new TokenBucketRefillInterval option to refill token buckets
3537 more frequently than once per second. This should improve network
3538 performance, alleviate queueing problems, and make traffic less
3539 bursty. Implements proposal 183; closes ticket 3630. Design by
3540 Florian Tschorsch and Björn Scheuermann; implementation by
3542 - Raise the threshold of server descriptors needed (75%) and exit
3543 server descriptors needed (50%) before we will declare ourselves
3544 bootstrapped. This will make clients start building circuits a
3545 little later, but makes the initially constructed circuits less
3546 skewed and less in conflict with further directory fetches. Fixes
3549 o Major features (relays):
3550 - Relays now try regenerating and uploading their descriptor more
3551 frequently if they are not listed in the consensus, or if the
3552 version of their descriptor listed in the consensus is too
3553 old. This fix should prevent situations where a server declines
3554 to re-publish itself because it has done so too recently, even
3555 though the authorities decided not to list its recent-enough
3556 descriptor. Fix for bug 3327.
3558 o Major features (stream isolation):
3559 - You can now configure Tor so that streams from different
3560 applications are isolated on different circuits, to prevent an
3561 attacker who sees your streams as they leave an exit node from
3562 linking your sessions to one another. To do this, choose some way
3563 to distinguish the applications: have them connect to different
3564 SocksPorts, or have one of them use SOCKS4 while the other uses
3565 SOCKS5, or have them pass different authentication strings to the
3566 SOCKS proxy. Then, use the new SocksPort syntax to configure the
3567 degree of isolation you need. This implements Proposal 171.
3568 - There's a new syntax for specifying multiple client ports (such as
3569 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
3570 multiple *Port entries with full addr:port syntax on each.
3571 The old *ListenAddress format is still supported, but you can't
3572 mix it with the new *Port syntax.
3574 o Major features (bufferevents):
3575 - Tor can now optionally build with the "bufferevents" buffered IO
3576 backend provided by Libevent 2. To use this feature, make sure you
3577 have the latest possible version of Libevent, and pass the
3578 --enable-bufferevents flag to configure when building Tor from
3579 source. This feature will make our networking code more flexible,
3580 let us stack layers on each other, and let us use more efficient
3581 zero-copy transports where available.
3582 - Add experimental support for running on Windows with IOCP and no
3583 kernel-space socket buffers. This feature is controlled by a new
3584 "UserspaceIOCPBuffers" config option (off by default), which has
3585 no effect unless Tor has been built with bufferevents enabled,
3586 you're running on Windows, and you've set "DisableIOCP 0". In the
3587 long run, this may help solve or mitigate bug 98.
3589 o Major features (path selection):
3590 - The EntryNodes option can now include country codes like {de} or IP
3591 addresses or network masks. Previously we had disallowed these
3592 options because we didn't have an efficient way to keep the list up
3593 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
3596 o Major features (port forwarding):
3597 - Add support for automatic port mapping on the many home routers
3598 that support NAT-PMP or UPnP. To build the support code, you'll
3599 need to have the libnatpnp library and/or the libminiupnpc library,
3600 and you'll need to enable the feature specifically by passing
3601 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
3602 it on, use the new PortForwarding option.
3604 o Major features (logging):
3605 - Add a new 'Heartbeat' log message type to periodically log a message
3606 describing Tor's status at level Notice. This feature is meant for
3607 operators who log at notice, and want to make sure that their Tor
3608 server is still working. Implementation by George Kadianakis.
3609 - Make logging resolution configurable with a new LogTimeGranularity
3610 option, and change the default from 1 millisecond to 1 second.
3611 Implements enhancement 1668.
3613 o Major features (other):
3614 - New "DisableNetwork" config option to prevent Tor from launching any
3615 connections or accepting any connections except on a control port.
3616 Bundles and controllers can set this option before letting Tor talk
3617 to the rest of the network, for example to prevent any connections
3618 to a non-bridge address. Packages like Orbot can also use this
3619 option to instruct Tor to save power when the network is off.
3620 - Try to use system facilities for enumerating local interface
3621 addresses, before falling back to our old approach (which was
3622 binding a UDP socket, and calling getsockname() on it). That
3623 approach was scaring OS X users whose draconian firewall
3624 software warned about binding to UDP sockets regardless of
3625 whether packets were sent. Now we try to use getifaddrs(),
3626 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
3627 system supports. Resolves ticket 1827.
3628 - Add experimental support for a "defaults" torrc file to be parsed
3629 before the regular torrc. Torrc options override the defaults file's
3630 options in the same way that the command line overrides the torrc.
3631 The SAVECONF controller command saves only those options which
3632 differ between the current configuration and the defaults file. HUP
3633 reloads both files. Implements task 4552.
3635 o New directory authorities:
3636 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
3637 authority. Closes ticket 5749.
3639 o Security/privacy fixes:
3640 - Avoid read-from-freed-memory and double-free bugs that could occur
3641 when a DNS request fails while launching it. Fixes bug 6480;
3642 bugfix on 0.2.0.1-alpha.
3643 - Reject any attempt to extend to an internal address. Without
3644 this fix, a router could be used to probe addresses on an internal
3645 network to see whether they were accepting connections. Fixes bug
3646 6710; bugfix on 0.0.8pre1.
3647 - Close any connection that sends unrecognized junk before the TLS
3648 handshake. Solves an issue noted in bug 4369.
3649 - The advertised platform of a relay now includes only its operating
3650 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
3651 its service pack level (for Windows) or its CPU architecture
3652 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
3653 can insert an extra string in the platform line by setting the
3654 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
3655 - Disable TLS session tickets. OpenSSL's implementation was giving
3656 our TLS session keys the lifetime of our TLS context objects, when
3657 perfect forward secrecy would want us to discard anything that
3658 could decrypt a link connection as soon as the link connection
3659 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
3660 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
3661 - Tor tries to wipe potentially sensitive data after using it, so
3662 that if some subsequent security failure exposes Tor's memory,
3663 the damage will be limited. But we had a bug where the compiler
3664 was eliminating these wipe operations when it decided that the
3665 memory was no longer visible to a (correctly running) program,
3666 hence defeating our attempt at defense in depth. We fix that
3667 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
3668 is unlikely to optimize away. Future versions of Tor may use
3669 a less ridiculously heavy approach for this. Fixes bug 7352.
3670 Reported in an article by Andrey Karpov.
3672 o Major bugfixes (crashes and asserts):
3673 - Avoid a pair of double-free and use-after-mark bugs that can
3674 occur with certain timings in canceled and re-received DNS
3675 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
3676 - Fix a denial of service attack by which any directory authority
3677 could crash all the others, or by which a single v2 directory
3678 authority could crash everybody downloading v2 directory
3679 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
3680 - Fix an assert that directory authorities could trigger on sighup
3681 during some configuration state transitions. We now don't treat
3682 it as a fatal error when the new descriptor we just generated in
3683 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
3684 - Avoid segfault when starting up having run with an extremely old
3685 version of Tor and parsing its state file. Fixes bug 6801; bugfix
3688 o Major bugfixes (clients):
3689 - If we are unable to find any exit that supports our predicted ports,
3690 stop calling them predicted, so that we don't loop and build
3691 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
3692 which introduced predicted ports.
3693 - Check at each new consensus whether our entry guards were picked
3694 long enough ago that we should rotate them. Previously, we only
3695 did this check at startup, which could lead to us holding a guard
3696 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
3697 - When fetching a bridge descriptor from a bridge authority,
3698 always do so anonymously, whether we have been able to open
3699 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
3700 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
3701 but we'll need to wait for bug 6010 before it's actually usable.
3703 o Major bugfixes (directory voting):
3704 - Check more thoroughly to prevent a rogue authority from
3705 double-voting on any consensus directory parameter. Previously,
3706 authorities would crash in this case if the total number of
3707 votes for any parameter exceeded the number of active voters,
3708 but would let it pass otherwise. Partially fixes bug 5786; bugfix
3710 - When computing weight parameters, behave more robustly in the
3711 presence of a bad bwweightscale value. Previously, the authorities
3712 would crash if they agreed on a sufficiently broken weight_scale
3713 value; now, they use a reasonable default and carry on. Fixes the
3714 rest of bug 5786; bugfix on 0.2.2.17-alpha.
3715 - If authorities are unable to get a v2 consensus document from other
3716 directory authorities, they no longer fall back to fetching
3717 them from regular directory caches. Fixes bug 5635; bugfix on
3718 0.2.2.26-beta, where routers stopped downloading v2 consensus
3721 o Major bugfixes (relays):
3722 - Fix a bug handling SENDME cells on nonexistent streams that could
3723 result in bizarre window values. Report and patch contributed
3724 pseudonymously. Fixes part of bug 6271. This bug was introduced
3725 before the first Tor release, in svn commit r152.
3726 - Don't update the AccountingSoftLimitHitAt state file entry whenever
3727 tor gets started. This prevents a wrong average bandwidth
3728 estimate, which would cause relays to always start a new accounting
3729 interval at the earliest possible moment. Fixes bug 2003; bugfix
3730 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
3731 immensely in tracking this bug down.
3732 - Fix a possible crash bug when checking for deactivated circuits
3733 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
3734 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
3735 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
3736 connections. This change should allow busy exit relays to stop
3737 running out of available sockets as quickly. Fixes bug 4950;
3738 bugfix on 0.2.2.26-beta.
3740 o Major bugfixes (blocking resistance):
3741 - Bridges no longer include their address in NETINFO cells on outgoing
3742 OR connections, to allow them to blend in better with clients.
3743 Removes another avenue for enumerating bridges. Reported by
3744 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
3745 cells were introduced.
3746 - Warn the user when HTTPProxy, but no other proxy type, is
3747 configured. This can cause surprising behavior: it doesn't send
3748 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
3749 directory traffic only. Resolves ticket 4663.
3751 o Major bugfixes (hidden services):
3752 - Improve hidden service robustness: when an attempt to connect to
3753 a hidden service ends, be willing to refetch its hidden service
3754 descriptors from each of the HSDir relays responsible for them
3755 immediately. Previously, we would not consider refetching the
3756 service's descriptors from each HSDir for 15 minutes after the last
3757 fetch, which was inconvenient if the hidden service was not running
3758 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
3759 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
3760 They used to check that the timestamp was within 30 minutes
3761 of their system clock, so they could cap the size of their
3762 replay-detection cache, but that approach unnecessarily refused
3763 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
3764 the v3 intro-point protocol (the first one which sent a timestamp
3765 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
3766 - When one of a hidden service's introduction points appears to be
3767 unreachable, stop trying it. Previously, we would keep trying
3768 to build circuits to the introduction point until we lost the
3769 descriptor, usually because the user gave up and restarted Tor.
3770 Fixes part of bug 3825.
3772 o Changes to default torrc file:
3773 - Stop listing "socksport 9050" in torrc.sample. We open a socks
3774 port on 9050 by default anyway, so this should not change anything
3776 - Stop mentioning the deprecated *ListenAddress options in
3777 torrc.sample. Fixes bug 5438.
3778 - Document unit of bandwidth-related options in sample torrc.
3780 - Fix broken URLs in the sample torrc file, and tell readers about
3781 the OutboundBindAddress, ExitPolicyRejectPrivate, and
3782 PublishServerDescriptor options. Addresses bug 4652.
3784 o Minor features (directory authorities):
3785 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
3786 change when the authority is deciding whether to accept a newly
3787 uploaded descriptor. Implements ticket 6423.
3788 - Directory authorities are now a little more lenient at accepting
3789 older router descriptors, or newer router descriptors that don't
3790 make big changes. This should help ameliorate past and future
3791 issues where routers think they have uploaded valid descriptors,
3792 but the authorities don't think so. Fix for ticket 2479.
3793 - Authority operators can now vote for all relays in a given
3794 set of countries to be BadDir/BadExit/Invalid/Rejected.
3795 - Provide two consensus parameters (FastFlagMinThreshold and
3796 FastFlagMaxThreshold) to control the range of allowable bandwidths
3797 for the Fast directory flag. These allow authorities to run
3798 experiments on appropriate requirements for being a "Fast" node.
3799 The AuthDirFastGuarantee config value still applies. Implements
3802 o Minor features (bridges / bridge authorities):
3803 - Make bridge SSL certificates a bit more stealthy by using random
3804 serial numbers, in the same fashion as OpenSSL when generating
3805 self-signed certificates. Implements ticket 4584.
3806 - Tag a bridge's descriptor as "never to be sent unencrypted".
3807 This shouldn't matter, since bridges don't open non-anonymous
3808 connections to the bridge authority and don't allow unencrypted
3809 directory connections from clients, but we might as well make
3810 sure. Closes bug 5139.
3811 - The Bridge Authority now writes statistics on how many bridge
3812 descriptors it gave out in total, and how many unique descriptors
3813 it gave out. It also lists how often the most and least commonly
3814 fetched descriptors were given out, as well as the median and
3815 25th/75th percentile. Implements tickets 4200 and 4294.
3817 o Minor features (IPv6):
3818 - Make the code that clients use to detect an address change be
3819 IPv6-aware, so that it won't fill clients' logs with error
3820 messages when trying to get the IPv4 address of an IPv6
3821 connection. Implements ticket 5537.
3822 - Relays now understand an IPv6 address when they get one from a
3823 directory server. Resolves ticket 4875.
3825 o Minor features (hidden services):
3826 - Expire old or over-used hidden service introduction points.
3827 Required by fix for bug 3460.
3828 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
3829 public key replay-detection cache from 60 minutes to 5 minutes. This
3830 replay-detection cache is now used only to detect multiple
3831 INTRODUCE2 cells specifying the same rendezvous point, so we can
3832 avoid launching multiple simultaneous attempts to connect to it.
3833 - When a hidden service's introduction point times out, consider
3834 trying it again during the next attempt to connect to the
3835 HS. Previously, we would not try it again unless a newly fetched
3836 descriptor contained it. Required by fixes for bugs 1297 and 3825.
3838 o Minor features (relays):
3839 - Relays now include a reason for regenerating their descriptors
3840 in an HTTP header when uploading to the authorities. This will
3841 make it easier to debug descriptor-upload issues in the future.
3842 - Turn on directory request statistics by default and include them in
3843 extra-info descriptors. Don't break if we have no GeoIP database.
3844 - Replace files in stats/ rather than appending to them. Now that we
3845 include statistics in extra-info descriptors, it makes no sense to
3846 keep old statistics forever. Implements ticket 2930.
3847 - Relays that set "ConnDirectionStatistics 1" write statistics on the
3848 bidirectional use of connections to disk every 24 hours.
3849 - Add a GeoIP file digest to the extra-info descriptor. Implements
3852 o Minor features (new config options):
3853 - New config option "DynamicDHGroups" (disabled by default) provides
3854 each bridge with a unique prime DH modulus to be used during
3855 SSL handshakes. This option attempts to help against censors
3856 who might use the Apache DH modulus as a static identifier for
3857 bridges. Addresses ticket 4548.
3858 - New config option "DisableDebuggerAttachment" (on by default)
3859 to prevent basic debugging attachment attempts by other processes.
3860 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
3861 - Ordinarily, Tor does not count traffic from private addresses (like
3862 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
3863 There is now a new option, CountPrivateBandwidth, to disable this
3864 behavior. Patch from Daniel Cagara.
3866 o Minor features (different behavior for old config options):
3867 - Allow MapAddress directives to specify matches against super-domains,
3868 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
3869 Implements issue 933.
3870 - Don't disable the DirPort when we cannot exceed our AccountingMax
3871 limit during this interval because the effective bandwidthrate is
3872 low enough. This is useful in a situation where AccountMax is only
3873 used as an additional safeguard or to provide statistics.
3874 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
3875 implements ticket 3439.
3876 - When configuring a large set of nodes in EntryNodes, and there are
3877 enough of them listed as Guard so that we don't need to consider
3878 the non-guard entries, prefer the ones listed with the Guard flag.
3879 - If you set the NumCPUs option to 0, Tor will now try to detect how
3880 many CPUs you have. This is the new default behavior.
3881 - The NodeFamily option -- which let you declare that you want to
3882 consider nodes to be part of a family whether they list themselves
3883 that way or not -- now allows IP address ranges and country codes.
3885 o Minor features (new command-line config behavior):
3886 - Slightly change behavior of "list" options (that is, config
3887 options that can appear more than once) when they appear both in
3888 torrc and on the command line. Previously, the command-line options
3889 would be appended to the ones from torrc. Now, the command-line
3890 options override the torrc options entirely. This new behavior
3891 allows the user to override list options (like exit policies and
3892 ports to listen on) from the command line, rather than simply
3893 appending to the list.
3894 - You can get the old (appending) command-line behavior for "list"
3895 options by prefixing the option name with a "+".
3896 - You can remove all the values for a "list" option from the command
3897 line without adding any new ones by prefixing the option name
3900 o Minor features (controller, new events):
3901 - Extend the control protocol to report flags that control a circuit's
3902 path selection in CIRC events and in replies to 'GETINFO
3903 circuit-status'. Implements part of ticket 2411.
3904 - Extend the control protocol to report the hidden service address
3905 and current state of a hidden-service-related circuit in CIRC
3906 events and in replies to 'GETINFO circuit-status'. Implements part
3908 - Include the creation time of a circuit in CIRC and CIRC2
3909 control-port events and the list produced by the 'GETINFO
3910 circuit-status' control-port command.
3911 - Add a new CONF_CHANGED event so that controllers can be notified
3912 of any configuration changes made by other controllers, or by the
3913 user. Implements ticket 1692.
3914 - Add a new SIGNAL event to the controller interface so that
3915 controllers can be notified when Tor handles a signal. Resolves
3916 issue 1955. Patch by John Brooks.
3918 o Minor features (controller, new getinfo options):
3919 - Expose our view of whether we have gone dormant to the controller,
3920 via a new "GETINFO dormant" value. Torbutton and other controllers
3921 can use this to avoid doing periodic requests through Tor while
3922 it's dormant (bug 4718). Resolves ticket 5954.
3923 - Add a new GETINFO option to get total bytes read and written. Patch
3924 from pipe, revised by atagar. Resolves ticket 2345.
3925 - Implement new GETINFO controller fields to provide information about
3926 the Tor process's pid, euid, username, and resource limits.
3928 o Minor features (controller, other):
3929 - Allow controllers to request an event notification whenever a
3930 circuit is cannibalized or its purpose is changed. Implements
3931 part of ticket 3457.
3932 - Use absolute path names when reporting the torrc filename in the
3933 control protocol, so a controller can more easily find the torrc
3934 file. Resolves bug 1101.
3935 - When reporting the path to the cookie file to the controller,
3936 give an absolute path. Resolves ticket 4881.
3938 o Minor features (log messages):
3939 - Add more information to a log statement that might help track down
3940 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
3941 non-IP address" messages (or any Bug messages, for that matter!),
3942 please let us know about it.
3943 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
3944 EntryNodes will have no effect. Resolves issue 2571.
3945 - Try to make the introductory warning message that Tor prints on
3946 startup more useful for actually finding help and information.
3947 Resolves ticket 2474.
3948 - When the system call to create a listener socket fails, log the
3949 error message explaining why. This may help diagnose bug 4027.
3951 o Minor features (other):
3952 - When we fail to initialize Libevent, retry with IOCP disabled so we
3953 don't need to turn on multi-threading support in Libevent, which in
3954 turn requires a working socketpair(). This is a workaround for bug
3955 4457, which affects Libevent versions from 2.0.1-alpha through
3957 - When starting as root and then changing our UID via the User
3958 control option, and we have a ControlSocket configured, make sure
3959 that the ControlSocket is owned by the same account that Tor will
3960 run under. Implements ticket 3421; fix by Jérémy Bobbio.
3961 - Accept attempts to include a password authenticator in the
3962 handshake, as supported by SOCKS5. This handles SOCKS clients that
3963 don't know how to omit a password when authenticating. Resolves
3965 - Check for and recover from inconsistency in the microdescriptor
3966 cache. This will make it harder for us to accidentally free a
3967 microdescriptor without removing it from the appropriate data
3968 structures. Fixes issue 3135; issue noted by "wanoskarnet".
3969 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
3971 o Minor bugfixes (code security):
3972 - Prevent a null-pointer dereference when receiving a data cell
3973 for a nonexistent stream when the circuit in question has an
3974 empty deliver window. We don't believe this is triggerable,
3975 since we don't currently allow deliver windows to become empty,
3976 but the logic is tricky enough that it's better to make the code
3977 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
3978 - Fix a (harmless) integer overflow in cell statistics reported by
3979 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
3980 - Fix our implementation of crypto_random_hostname() so it can't
3981 overflow on ridiculously large inputs. (No Tor version has ever
3982 provided this kind of bad inputs, but let's be correct in depth.)
3983 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
3984 - Add a (probably redundant) memory clear between iterations of
3985 the router status voting loop, to prevent future coding errors
3986 where data might leak between iterations of the loop. Resolves
3989 o Minor bugfixes (wrapper functions):
3990 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
3991 utility function used in the control-port code). This shouldn't
3992 ever happen unless Tor is completely out of memory, but if it did
3993 happen and Tor somehow recovered from it, Tor could have sent a log
3994 message to a control port in the middle of a reply to a controller
3995 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
3996 - Fix some (not actually triggerable) buffer size checks in usage of
3997 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
3999 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
4000 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
4001 - Enforce correct return behavior of tor_vsscanf() when the '%%'
4002 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
4003 - Make our replacement implementation of strtok_r() compatible with
4004 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
4005 bugfix on 0.2.2.1-alpha.
4006 - Find more places in the code that should have been testing for
4007 invalid sockets using the SOCKET_OK macro. Required for a fix
4008 for bug 4533. Bugfix on 0.2.2.28-beta.
4010 o Minor bugfixes (code correctness):
4011 - Check return value of fputs() when writing authority certificate
4012 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
4013 - When building Tor on Windows with -DUNICODE (not default), ensure
4014 that error messages, filenames, and DNS server names are always
4015 NUL-terminated when we convert them to a single-byte encoding.
4016 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
4017 - Fix a memory leak when trying to launch a DNS request when the
4018 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
4020 - Correct file sizes when reading binary files on Cygwin, to avoid
4021 a bug where Tor would fail to read its state file. Fixes bug 6844;
4022 bugfix on 0.1.2.7-alpha.
4023 - Make sure to set *socket_error in all error cases in
4024 connection_connect(), so it can't produce a warning about
4025 errno being zero from errno_to_orconn_end_reason(). Bugfix on
4026 0.2.1.1-alpha; resolves ticket 6028.
4027 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
4028 bug 4532; found by "troll_un".
4030 o Minor bugfixes (clients):
4031 - Allow one-hop directory-fetching circuits the full "circuit build
4032 timeout" period, rather than just half of it, before failing them
4033 and marking the relay down. This fix should help reduce cases where
4034 clients declare relays (or worse, bridges) unreachable because
4035 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
4036 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
4038 - Ensure we don't cannibalize circuits that are longer than three hops
4039 already, so we don't end up making circuits with 5 or more
4040 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
4041 0.1.0.1-rc which introduced cannibalization.
4043 o Minor bugfixes (relays):
4044 - Don't publish a new relay descriptor when we reload our onion key,
4045 unless the onion key has actually changed. Fixes bug 3263 and
4046 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
4047 - When relays refuse a "create" cell because their queue of pending
4048 create cells is too big (typically because their cpu can't keep up
4049 with the arrival rate), send back reason "resource limit" rather
4050 than reason "internal", so network measurement scripts can get a
4051 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
4052 - Exit nodes don't need to fetch certificates for authorities that
4053 they don't recognize; only directory authorities, bridges,
4054 and caches need to do that. Fixes part of bug 2297; bugfix on
4057 o Minor bugfixes (directory authority / mirrors):
4058 - Avoid O(n^2) performance characteristics when parsing a large
4059 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
4060 - Authorities no longer include any router in their microdescriptor
4061 consensuses for which they couldn't generate or agree on a
4062 microdescriptor. Fixes the second piece of bug 6404; fix on
4064 - When checking for requested signatures on the latest consensus
4065 before serving it to a client, make sure to check the right
4066 consensus flavor. Bugfix on 0.2.2.6-alpha.
4067 - Fix an edge case where TestingTorNetwork is set but the authorities
4068 and relays all have an uptime of zero, so the private Tor network
4069 could briefly lack support for hidden services. Fixes bug 3886;
4070 bugfix on 0.2.2.18-alpha.
4071 - Directory caches no longer refuse to clean out descriptors because
4072 of missing v2 networkstatus documents, unless they're configured
4073 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
4074 0.2.2.26-beta. Patch by Daniel Bryg.
4075 - Don't serve or accept v2 hidden service descriptors over a relay's
4076 DirPort. It's never correct to do so, and disabling it might
4077 make it more annoying to exploit any bugs that turn up in the
4078 descriptor-parsing code. Fixes bug 7149.
4080 o Minor bugfixes (hidden services, client-side):
4081 - Assert that hidden-service-related operations are not performed
4082 using single-hop circuits. Previously, Tor would assert that
4083 client-side streams are not attached to single-hop circuits,
4084 but not that other sensitive operations on the client and service
4085 side are not performed using single-hop circuits. Fixes bug 3332;
4087 - Avoid undefined behavior when parsing the list of supported
4088 rendezvous/introduction protocols in a hidden service descriptor.
4089 Previously, Tor would have confused (as-yet-unused) protocol version
4090 numbers greater than 32 with lower ones on many platforms. Fixes
4091 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
4092 - Don't close hidden service client circuits which have almost
4093 finished connecting to their destination when they reach
4094 the normal circuit-build timeout. Previously, we would close
4095 introduction circuits which are waiting for an acknowledgement
4096 from the introduction point, and rendezvous circuits which have
4097 been specified in an INTRODUCE1 cell sent to a hidden service,
4098 after the normal CBT. Now, we mark them as 'timed out', and launch
4099 another rendezvous attempt in parallel. This behavior change can
4100 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
4101 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
4103 o Minor bugfixes (hidden services, service-side):
4104 - Don't close hidden-service-side rendezvous circuits when they
4105 reach the normal circuit-build timeout. This behavior change can
4106 be disabled using the new
4107 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
4108 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
4109 - Don't launch more than 10 service-side introduction-point circuits
4110 for a hidden service in five minutes. Previously, we would consider
4111 launching more introduction-point circuits if at least one second
4112 had passed without any introduction-point circuits failing. Fixes
4113 bug 4607; bugfix on 0.0.7pre1.
4115 o Minor bugfixes (config option behavior):
4116 - If the user tries to set MyFamily on a bridge, refuse to
4117 do so, and warn about the security implications. Fixes bug 4657;
4118 bugfix on 0.2.0.3-alpha.
4119 - The "--quiet" and "--hush" options now apply not only to Tor's
4120 behavior before logs are configured, but also to Tor's behavior in
4121 the absense of configured logs. Fixes bug 3550; bugfix on
4123 - Change the AllowDotExit rules so they should actually work.
4124 We now enforce AllowDotExit only immediately after receiving an
4125 address via SOCKS or DNSPort: other sources are free to provide
4126 .exit addresses after the resolution occurs. Fixes bug 3940;
4127 bugfix on 0.2.2.1-alpha.
4128 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
4129 don't depend on the consensus parameters or compute adaptive
4130 timeouts when it is disabled. Fixes bug 5049; bugfix on
4132 - After we pick a directory mirror, we would refuse to use it if
4133 it's in our ExcludeExitNodes list, resulting in mysterious failures
4134 to bootstrap for people who just wanted to avoid exiting from
4135 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
4136 - When told to add a bridge with the same digest as a preexisting
4137 bridge but a different addr:port, change the addr:port as
4138 requested. Previously we would not notice the change. Fixes half
4139 of bug 5603; fix on 0.2.2.26-beta.
4141 o Minor bugfixes (controller):
4142 - Allow manual 'authenticate' commands to the controller interface
4143 from netcat (nc) as well as telnet. We were rejecting them because
4144 they didn't come with the expected whitespace at the end of the
4145 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
4146 - Report a real bootstrap problem to the controller on router
4147 identity mismatch. Previously we just said "foo", which probably
4148 made a lot of sense at the time. Fixes bug 4169; bugfix on
4150 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
4151 option is set to 0 (which Vidalia version 0.2.16 now does when
4152 a SAVECONF attempt fails), perform other actions that SIGHUP
4153 usually causes (like reopening the logs). Fixes bug 5095; bugfix
4155 - Correctly handle checking the permissions on the parent
4156 directory of a control socket in the root directory. Bug found
4157 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
4159 - End AUTHCHALLENGE error messages (in the control protocol) with
4160 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
4162 o Minor bugfixes (network reading/writing):
4163 - Disable writing on marked-for-close connections when they are
4164 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
4165 bug 5263; bugfix on 0.0.2pre13, where we first added a special
4166 case for flushing marked connections.
4167 - Make sure that there are no unhandled pending TLS errors before
4168 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
4169 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
4170 Bugfix on 0.1.0.5-rc; fixes bug 4528.
4171 - Detect SSL handshake even when the initial attempt to write the
4172 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
4173 - If the client fails to set a reasonable set of ciphersuites
4174 during its v2 handshake renegotiation, allow the renegotiation to
4175 continue nevertheless (i.e. send all the required certificates).
4176 Fixes bug 4591; bugfix on 0.2.0.20-rc.
4178 o Minor bugfixes (other):
4179 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
4180 resource exhaustion, so that clients can adjust their load to
4181 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
4182 started using END_STREAM_REASON_RESOURCELIMIT.
4183 - Don't check for whether the address we're using for outbound
4184 connections has changed until after the outbound connection has
4185 completed. On Windows, getsockname() doesn't succeed until the
4186 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
4187 - Don't hold a Windows file handle open for every file mapping;
4188 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
4190 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
4191 bugfix on 0.2.1.10-alpha.
4192 - If we fail to write a microdescriptor to the disk cache, do not
4193 continue replacing the old microdescriptor file. Fixes bug 2954;
4194 bugfix on 0.2.2.6-alpha.
4196 o Minor bugfixes (log messages, path selection):
4197 - Downgrade "set buildtimeout to low value" messages to "info"
4198 severity; they were never an actual problem, there was never
4199 anything reasonable to do about them, and they tended to spam logs
4200 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
4201 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
4202 more information to it, so that we can track it down in case it
4203 returns again. Mitigates bug 5235.
4204 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
4205 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
4206 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
4207 - Issue a log message if a guard completes less than 40% of your
4208 circuits. Threshold is configurable by torrc option
4209 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
4210 additional, off-by-default code to disable guards which fail too
4211 many circuits. Addresses ticket 5458.
4213 o Minor bugfixes (log messages, client):
4214 - Downgrade "Got a certificate, but we already have it" log messages
4215 from warning to info, except when we're a dirauth. Fixes bug 5238;
4216 bugfix on 0.2.1.7-alpha.
4217 - Fix the log message describing how we work around discovering
4218 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
4219 4837; bugfix on 0.2.2.9-alpha.
4220 - When logging about a disallowed .exit name, do not also call it
4221 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
4222 - Fix a log message suggesting that people contact a non-existent
4223 email address. Fixes bug 3448.
4224 - Rephrase the log message emitted if the TestSocks check is
4225 successful. Patch from Fabian Keil; fixes bug 4094.
4226 - Log (at debug level) whenever a circuit's purpose is changed.
4227 - Log SSL state transitions at log level DEBUG, log domain
4228 HANDSHAKE. This can be useful for debugging censorship events.
4229 Implements ticket 3264.
4230 - We now log which torrc file we're using on startup. Implements
4232 - Rate-limit log messages when asked to connect anonymously to
4233 a private address. When these hit, they tended to hit fast and
4234 often. Also, don't bother trying to connect to addresses that we
4235 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
4236 reply makes us think we have been lied to, even when the address the
4237 client tried to connect to was "localhost." Resolves ticket 2822.
4239 o Minor bugfixes (log messages, non-client):
4240 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
4241 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
4242 - Don't log that we have "decided to publish new relay descriptor"
4243 unless we are actually publishing a descriptor. Fixes bug 3942;
4244 bugfix on 0.2.2.28-beta.
4245 - Log which authority we're missing votes from when we go to fetch
4246 them from the other auths.
4247 - Replace "Sending publish request" log messages with "Launching
4248 upload", so that they no longer confusingly imply that we're
4249 sending something to a directory we might not even be connected
4250 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
4251 - Warn when Tor is configured to use accounting in a way that can
4252 link a hidden service to some other hidden service or public
4253 address. Resolves ticket 6490.
4254 - Fix a minor formatting issue in one of tor-gencert's error messages.
4258 - Update to the latest version of the tinytest unit testing framework.
4259 This includes a couple of bugfixes that can be relevant for
4260 running forked unit tests on Windows, and removes all reserved
4262 - Avoid a false positive in the util/threads unit test by increasing
4263 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
4264 - Make it possible to set the TestingTorNetwork configuration
4265 option using AlternateDirAuthority and AlternateBridgeAuthority
4266 as an alternative to setting DirServer. Addresses ticket 6377.
4267 - Add a unit test for the environment_variable_names_equal() function.
4268 - A wide variety of new unit tests by Esteban Manchado Velázquez.
4269 - Numerous new unit tests for functions in util.c and address.c by
4271 - The long-disabled benchmark tests are now split into their own
4272 ./src/test/bench binary.
4273 - The benchmark tests can now use more accurate timers than
4274 gettimeofday() when such timers are available.
4275 - Use tt_assert(), not tor_assert(), for checking for test failures.
4276 This makes the unit tests more able to go on in the event that
4279 o Build improvements:
4280 - Use the dead_strip option when building Tor on OS X. This reduces
4281 binary size by almost 19% when linking openssl and libevent
4282 statically, which we do for Tor Browser Bundle.
4283 - Provide a better error message about possible OSX Asciidoc failure
4284 reasons. Fixes bug 6436.
4285 - Detect attempts to build Tor on (as yet hypothetical) versions
4286 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
4287 fix for bug 4533. Bugfix on 0.2.2.28-beta.
4288 - On Windows, we now define the _WIN32_WINNT macros only if they
4289 are not already defined. This lets the person building Tor decide,
4290 if they want, to require a later version of Windows.
4291 - Our autogen.sh script now uses autoreconf to launch autoconf,
4292 automake, and so on. This is more robust against some of the failure
4293 modes associated with running the autotools pieces on their own.
4294 - Running "make version" now displays the version of Tor that
4295 we're about to build. Idea from katmagic; resolves issue 4400.
4296 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
4297 on 0.2.2.4-alpha; fixes bug 3427.
4298 - New --enable-static-tor configure option for building Tor as
4299 statically as possible. Idea, general hackery and thoughts from
4300 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
4302 - Limited, experimental support for building with nmake and MSVC.
4304 o Build requirements:
4305 - Building Tor with bufferevent support now requires Libevent
4306 2.0.13-stable or later. Previous versions of Libevent had bugs in
4307 SSL-related bufferevents and related issues that would make Tor
4308 work badly with bufferevents. Requiring 2.0.13-stable also allows
4309 Tor with bufferevents to take advantage of Libevent APIs
4310 introduced after 2.0.8-rc.
4311 - Our build system requires automake 1.6 or later to create the
4312 Makefile.in files. Previously, you could have used 1.4.
4313 This only affects developers and people building Tor from git;
4314 people who build Tor from the source distribution without changing
4315 the Makefile.am files should be fine.
4316 - Detect when we try to build on a platform that doesn't define
4317 AF_UNSPEC to 0. We don't work there, so refuse to compile.
4319 o Build fixes (compile/link):
4320 - Format more doubles with %f, not %lf. Patch from grarpamp to make
4321 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
4323 - When building with --enable-static-tor on OpenBSD, do not
4324 erroneously attempt to link -lrt. Fixes bug 5103.
4325 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
4326 that IPv6 stuff will compile on MSVC, and compilation issues
4327 will be easier to track down. Fixes bug 5861.
4328 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
4329 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
4330 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
4331 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
4333 o Build fixes (other):
4334 - Use the _WIN32 macro throughout our code to detect Windows.
4335 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
4337 - Properly handle the case where the build-tree is not the same
4338 as the source tree when generating src/common/common_sha1.i,
4339 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
4340 bugfix on 0.2.0.1-alpha.
4341 - During configure, search for library containing cos function as
4342 libm lives in libcore on some platforms (BeOS/Haiku). Linking
4343 against libm was hard-coded before. Fixes the first part of bug
4344 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
4346 - Prevent a false positive from the check-spaces script, by disabling
4347 the "whitespace between function name and (" check for functions
4350 o Packaging (RPM) changes:
4351 - Update our default RPM spec files to work with mock and rpmbuild
4352 on RHEL/Fedora. They have an updated set of dependencies and
4353 conflicts, a fix for an ancient typo when creating the "_tor"
4354 user, and better instructions. Thanks to Ondrej Mikle for the
4355 patch series. Fixes bug 6043.
4356 - On OpenSUSE, create the /var/run/tor directory on startup if it
4357 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
4359 o Code refactoring (safety):
4360 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
4361 10 lines. Also, don't nest them. Doing so in the past has
4362 led to hard-to-debug code. The new style is to use the
4363 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
4364 - Use macros to indicate OpenSSL versions, so we don't need to worry
4365 about accidental hexadecimal bit shifts.
4366 - Use tor_sscanf() in place of scanf() in more places through the
4367 code. This makes us a little more locale-independent, and
4368 should help shut up code-analysis tools that can't tell
4369 a safe sscanf string from a dangerous one.
4370 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
4371 - Use the smartlist_add_asprintf() alias more consistently.
4373 o Code refactoring (consolidate):
4374 - A major revision to our internal node-selecting and listing logic.
4375 Tor already had at least two major ways to look at the question of
4376 "which Tor servers do we know about": a list of router descriptors,
4377 and a list of entries in the current consensus. With
4378 microdescriptors, we're adding a third. Having so many systems
4379 without an abstraction layer over them was hurting the codebase.
4380 Now, we have a new "node_t" abstraction that presents a consistent
4381 interface to a client's view of a Tor node, and holds (nearly) all
4382 of the mutable state formerly in routerinfo_t and routerstatus_t.
4383 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
4384 Libevent's notion of cached time when possible.
4385 - Remove duplicate code for invoking getrlimit() from control.c.
4386 - Use OpenSSL's built-in SSL_state_string_long() instead of our
4387 own homebrewed ssl_state_to_string() replacement. Patch from
4388 Emile Snyder. Fixes bug 4653.
4389 - Change the symmetric cipher interface so that creating and
4390 initializing a stream cipher are no longer separate functions.
4392 o Code refactoring (separate):
4393 - Make a new "entry connection" struct as an internal subtype of "edge
4394 connection", to simplify the code and make exit connections smaller.
4395 - Split connection_about_to_close() into separate functions for each
4397 - Rewrite the listener-selection logic so that parsing which ports
4398 we want to listen on is now separate from binding to the ports
4401 o Code refactoring (name changes):
4402 - Rename a handful of old identifiers, mostly related to crypto
4403 structures and crypto functions. By convention, our "create an
4404 object" functions are called "type_new()", our "free an object"
4405 functions are called "type_free()", and our types indicate that
4406 they are types only with a final "_t". But a handful of older
4407 types and functions broke these rules, with function names like
4408 "type_create" or "subsystem_op_type", or with type names like
4410 - Rename Tor functions that turn strings into addresses, so that
4411 "parse" indicates that no hostname resolution occurs, and
4412 "lookup" indicates that hostname resolution may occur. This
4413 should help prevent mistakes in the future. Fixes bug 3512.
4414 - Use the name "CERTS" consistently to refer to the new cell type;
4415 we were calling it CERT in some places and CERTS in others.
4416 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
4417 invalid value, rather than just -1.
4418 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
4419 can pick them up when the tests aren't disabled. Bugfix on
4420 0.2.2.4-alpha which introduced tinytest.
4422 o Code refactoring (other):
4423 - Defensively refactor rend_mid_rendezvous() so that protocol
4424 violations and length checks happen in the beginning. Fixes
4426 - Remove the pure attribute from all functions that used it
4427 previously. In many cases we assigned it incorrectly, because the
4428 functions might assert or call impure functions, and we don't have
4429 evidence that keeping the pure attribute is worthwhile. Implements
4430 changes suggested in ticket 4421.
4431 - Move the replay-detection cache for the RSA-encrypted parts of
4432 INTRODUCE2 cells to the introduction point data structures.
4433 Previously, we would use one replay-detection cache per hidden
4434 service. Required by fix for bug 3460.
4435 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
4436 no longer link against Libevent: they never used it, but
4437 our library structure used to force them to link it.
4439 o Removed features and files:
4440 - Remove all internal support for unpadded RSA. We never used it, and
4441 it would be a bad idea to start.
4442 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
4444 - Remove some redundant #include directives throughout the code.
4445 Patch from Andrea Gelmini.
4446 - Remove some old code to remember statistics about which descriptors
4447 we've served as a directory mirror. The feature wasn't used and
4448 is outdated now that microdescriptors are around.
4449 - Remove some old code to work around even older versions of Tor that
4450 used forked processes to handle DNS requests. Such versions of Tor
4451 are no longer in use as relays.
4452 - The "torify" script no longer supports the "tsocks" socksifier
4453 tool, since tsocks doesn't support DNS and UDP right for Tor.
4454 Everyone should be using torsocks instead. Fixes bugs 3530 and
4455 5180. Based on a patch by "ugh".
4456 - Remove the torrc.bridge file: we don't use it for anything, and
4457 it had become badly desynchronized from torrc.sample. Resolves
4461 - Begin a doc/state-contents.txt file to explain the contents of
4462 the Tor state file. Fixes bug 2987.
4463 - Clarify the documentation for the Alternate*Authority options.
4465 - Document the --defaults-torrc option, and the new semantics for
4466 overriding, extending, and clearing lists of options. Closes
4468 - Add missing man page documentation for consensus and microdesc
4469 files. Resolves ticket 6732.
4470 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
4472 o Documentation fixes:
4473 - Improve the manual's documentation for the NT Service command-line
4474 options. Addresses ticket 3964.
4475 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
4476 - Document the changes to the ORPort and DirPort options, and the
4477 fact that {OR/Dir}ListenAddress is now unnecessary (and
4478 therefore deprecated). Resolves ticket 5597.
4479 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
4480 - Clarify that hidden services are TCP only. Fixes bug 6024.
4483 Changes in version 0.2.2.39 - 2012-09-11
4484 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
4488 - Fix an assertion failure in tor_timegm() that could be triggered
4489 by a badly formatted directory object. Bug found by fuzzing with
4490 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
4491 - Do not crash when comparing an address with port value 0 to an
4492 address policy. This bug could have been used to cause a remote
4493 assertion failure by or against directory authorities, or to
4494 allow some applications to crash clients. Fixes bug 6690; bugfix
4498 Changes in version 0.2.2.38 - 2012-08-12
4499 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
4500 attack that could in theory leak path information.
4503 - Avoid an uninitialized memory read when reading a vote or consensus
4504 document that has an unrecognized flavor name. This read could
4505 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
4506 - Try to leak less information about what relays a client is
4507 choosing to a side-channel attacker. Previously, a Tor client would
4508 stop iterating through the list of available relays as soon as it
4509 had chosen one, thus finishing a little earlier when it picked
4510 a router earlier in the list. If an attacker can recover this
4511 timing information (nontrivial but not proven to be impossible),
4512 they could learn some coarse-grained information about which relays
4513 a client was picking (middle nodes in particular are likelier to
4514 be affected than exits). The timing attack might be mitigated by
4515 other factors (see bug 6537 for some discussion), but it's best
4516 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
4519 Changes in version 0.2.2.37 - 2012-06-06
4520 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
4521 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
4525 - Work around a bug in OpenSSL that broke renegotiation with TLS
4526 1.1 and TLS 1.2. Without this workaround, all attempts to speak
4527 the v2 Tor connection protocol when both sides were using OpenSSL
4528 1.0.1 would fail. Resolves ticket 6033.
4529 - When waiting for a client to renegotiate, don't allow it to add
4530 any bytes to the input buffer. This fixes a potential DoS issue.
4531 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
4532 - Fix an edge case where if we fetch or publish a hidden service
4533 descriptor, we might build a 4-hop circuit and then use that circuit
4534 for exiting afterwards -- even if the new last hop doesn't obey our
4535 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
4538 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
4539 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
4542 - Tell GCC and Clang to check for any errors in format strings passed
4543 to the tor_v*(print|scan)f functions.
4546 Changes in version 0.2.2.36 - 2012-05-24
4547 Tor 0.2.2.36 updates the addresses for two of the eight directory
4548 authorities, fixes some potential anonymity and security issues,
4549 and fixes several crash bugs.
4551 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
4552 known flaws, and nobody should be using them. You should upgrade. If
4553 you're using a Linux or BSD and its packages are obsolete, stop using
4554 those packages and upgrade anyway.
4556 o Directory authority changes:
4557 - Change IP address for maatuska (v3 directory authority).
4558 - Change IP address for ides (v3 directory authority), and rename
4562 - When building or running with any version of OpenSSL earlier
4563 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
4564 versions have a bug (CVE-2011-4576) in which their block cipher
4565 padding includes uninitialized data, potentially leaking sensitive
4566 information to any peer with whom they make a SSLv3 connection. Tor
4567 does not use SSL v3 by default, but a hostile client or server
4568 could force an SSLv3 connection in order to gain information that
4569 they shouldn't have been able to get. The best solution here is to
4570 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
4571 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
4572 to make sure that the bug can't happen.
4573 - Never use a bridge or a controller-supplied node as an exit, even
4574 if its exit policy allows it. Found by wanoskarnet. Fixes bug
4575 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
4576 and 0.2.0.3-alpha (for bridge-purpose descriptors).
4577 - Only build circuits if we have a sufficient threshold of the total
4578 descriptors that are marked in the consensus with the "Exit"
4579 flag. This mitigates an attack proposed by wanoskarnet, in which
4580 all of a client's bridges collude to restrict the exit nodes that
4581 the client knows about. Fixes bug 5343.
4582 - Provide controllers with a safer way to implement the cookie
4583 authentication mechanism. With the old method, if another locally
4584 running program could convince a controller that it was the Tor
4585 process, then that program could trick the controller into telling
4586 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
4587 authentication method uses a challenge-response approach to prevent
4588 this attack. Fixes bug 5185; implements proposal 193.
4591 - Avoid logging uninitialized data when unable to decode a hidden
4592 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
4593 - Avoid a client-side assertion failure when receiving an INTRODUCE2
4594 cell on a general purpose circuit. Fixes bug 5644; bugfix on
4596 - Fix builds when the path to sed, openssl, or sha1sum contains
4597 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
4599 - Correct our replacements for the timeradd() and timersub() functions
4600 on platforms that lack them (for example, Windows). The timersub()
4601 function is used when expiring circuits, while timeradd() is
4602 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
4603 bugfix on 0.2.2.24-alpha.
4604 - Fix the SOCKET_OK test that we use to tell when socket
4605 creation fails so that it works on Win64. Fixes part of bug 4533;
4606 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
4609 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
4610 Fixes bug 5346; bugfix on 0.0.8pre3.
4611 - Make our number-parsing functions always treat too-large values
4612 as an error, even when those values exceed the width of the
4613 underlying type. Previously, if the caller provided these
4614 functions with minima or maxima set to the extreme values of the
4615 underlying integer type, these functions would return those
4616 values on overflow rather than treating overflow as an error.
4617 Fixes part of bug 5786; bugfix on 0.0.9.
4618 - Older Linux kernels erroneously respond to strange nmap behavior
4619 by having accept() return successfully with a zero-length
4620 socket. When this happens, just close the connection. Previously,
4621 we would try harder to learn the remote address: but there was
4622 no such remote address to learn, and our method for trying to
4623 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
4624 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
4625 - Correct parsing of certain date types in parse_http_time().
4626 Without this patch, If-Modified-Since would behave
4627 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
4628 Esteban Manchado Velázques.
4629 - Change the BridgePassword feature (part of the "bridge community"
4630 design, which is not yet implemented) to use a time-independent
4631 comparison. The old behavior might have allowed an adversary
4632 to use timing to guess the BridgePassword value. Fixes bug 5543;
4633 bugfix on 0.2.0.14-alpha.
4634 - Detect and reject certain misformed escape sequences in
4635 configuration values. Previously, these values would cause us
4636 to crash if received in a torrc file or over an authenticated
4637 control port. Bug found by Esteban Manchado Velázquez, and
4638 independently by Robert Connolly from Matta Consulting who further
4639 noted that it allows a post-authentication heap overflow. Patch
4640 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
4641 bugfix on 0.2.0.16-alpha.
4642 - Fix a compile warning when using the --enable-openbsd-malloc
4643 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
4644 - During configure, detect when we're building with clang version
4645 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
4646 CFLAGS. clang doesn't support them yet.
4647 - When sending an HTTP/1.1 proxy request, include a Host header.
4648 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
4649 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
4650 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
4651 - If we hit the error case where routerlist_insert() replaces an
4652 existing (old) server descriptor, make sure to remove that
4653 server descriptor from the old_routers list. Fix related to bug
4654 1776. Bugfix on 0.2.2.18-alpha.
4656 o Minor bugfixes (documentation and log messages):
4657 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
4658 Fixes bug 4856; bugfix on Tor 0.0.6.
4659 - Update "ClientOnly" man page entry to explain that there isn't
4660 really any point to messing with it. Resolves ticket 5005.
4661 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
4662 directory authority option (introduced in Tor 0.2.2.34).
4663 - Downgrade the "We're missing a certificate" message from notice
4664 to info: people kept mistaking it for a real problem, whereas it
4665 is seldom the problem even when we are failing to bootstrap. Fixes
4666 bug 5067; bugfix on 0.2.0.10-alpha.
4667 - Correctly spell "connect" in a log message on failure to create a
4668 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
4669 - Clarify the behavior of MaxCircuitDirtiness with hidden service
4670 circuits. Fixes issue 5259.
4673 - Directory authorities now reject versions of Tor older than
4674 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
4675 inclusive. These versions accounted for only a small fraction of
4676 the Tor network, and have numerous known security issues. Resolves
4678 - Update to the May 1 2012 Maxmind GeoLite Country database.
4681 - When sending or relaying a RELAY_EARLY cell, we used to convert
4682 it to a RELAY cell if the connection was using the v1 link
4683 protocol. This was a workaround for older versions of Tor, which
4684 didn't handle RELAY_EARLY cells properly. Now that all supported
4685 versions can handle RELAY_EARLY cells, and now that we're enforcing
4686 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
4687 remove this workaround. Addresses bug 4786.
4690 Changes in version 0.2.2.35 - 2011-12-16
4691 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
4692 buffers code. Absolutely everybody should upgrade.
4694 The bug relied on an incorrect calculation when making data continuous
4695 in one of our IO buffers, if the first chunk of the buffer was
4696 misaligned by just the wrong amount. The miscalculation would allow an
4697 attacker to overflow a piece of heap-allocated memory. To mount this
4698 attack, the attacker would need to either open a SOCKS connection to
4699 Tor's SocksPort (usually restricted to localhost), or target a Tor
4700 instance configured to make its connections through a SOCKS proxy
4701 (which Tor does not do by default).
4703 Good security practice requires that all heap-overflow bugs should be
4704 presumed to be exploitable until proven otherwise, so we are treating
4705 this as a potential code execution attack. Please upgrade immediately!
4706 This bug does not affect bufferevents-based builds of Tor. Special
4707 thanks to "Vektor" for reporting this issue to us!
4709 Tor 0.2.2.35 also fixes several bugs in previous versions, including
4710 crash bugs for unusual configurations, and a long-term bug that
4711 would prevent Tor from starting on Windows machines with draconian
4714 With this release, we remind everyone that 0.2.0.x has reached its
4715 formal end-of-life. Those Tor versions have many known flaws, and
4716 nobody should be using them. You should upgrade -- ideally to the
4717 0.2.2.x series. If you're using a Linux or BSD and its packages are
4718 obsolete, stop using those packages and upgrade anyway.
4720 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
4721 longer receive support after some time in early 2012.
4724 - Fix a heap overflow bug that could occur when trying to pull
4725 data into the first chunk of a buffer, when that chunk had
4726 already had some data drained from it. Fixes CVE-2011-2778;
4727 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
4728 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
4729 that it doesn't attempt to allocate a socketpair. This could cause
4730 some problems on Windows systems with overzealous firewalls. Fix for
4731 bug 4457; workaround for Libevent versions 2.0.1-alpha through
4733 - If we mark an OR connection for close based on a cell we process,
4734 don't process any further cells on it. We already avoid further
4735 reads on marked-for-close connections, but now we also discard the
4736 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
4737 which was the first version where we might mark a connection for
4738 close based on processing a cell on it.
4739 - Correctly sanity-check that we don't underflow on a memory
4740 allocation (and then assert) for hidden service introduction
4741 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
4742 bugfix on 0.2.1.5-alpha.
4743 - Fix a memory leak when we check whether a hidden service
4744 descriptor has any usable introduction points left. Fixes bug
4745 4424. Bugfix on 0.2.2.25-alpha.
4746 - Don't crash when we're running as a relay and don't have a GeoIP
4747 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
4748 we've had in the 0.2.3.x branch already.
4749 - When running as a client, do not print a misleading (and plain
4750 wrong) log message that we're collecting "directory request"
4751 statistics: clients don't collect statistics. Also don't create a
4752 useless (because empty) stats file in the stats/ directory. Fixes
4753 bug 4353; bugfix on 0.2.2.34.
4756 - Detect failure to initialize Libevent. This fix provides better
4757 detection for future instances of bug 4457.
4758 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
4759 function. This was eating up hideously large amounts of time on some
4760 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
4761 - Resolve an integer overflow bug in smartlist_ensure_capacity().
4762 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
4764 - Don't warn about unused log_mutex in log.c when building with
4765 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
4766 0.1.0.6-rc which introduced --disable-threads.
4767 - When configuring, starting, or stopping an NT service, stop
4768 immediately after the service configuration attempt has succeeded
4769 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
4770 - When sending a NETINFO cell, include the original address
4771 received for the other side, not its canonical address. Found
4772 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
4773 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
4774 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
4775 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
4776 occurred when a client tried to fetch a descriptor for a bridge
4777 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
4778 - Backport fixes for a pair of compilation warnings on Windows.
4779 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
4780 - If we had ever tried to call tor_addr_to_str on an address of
4781 unknown type, we would have done a strdup on an uninitialized
4782 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
4783 Reported by "troll_un".
4784 - Correctly detect and handle transient lookup failures from
4785 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
4786 Reported by "troll_un".
4787 - Fix null-pointer access that could occur if TLS allocation failed.
4788 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
4789 - Use tor_socket_t type for listener argument to accept(). Fixes bug
4790 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
4793 - Add two new config options for directory authorities:
4794 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
4795 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
4796 that is always sufficient to satisfy the bandwidth requirement for
4797 the Guard flag. Now it will be easier for researchers to simulate
4798 Tor networks with different values. Resolves ticket 4484.
4799 - When Tor ignores a hidden service specified in its configuration,
4800 include the hidden service's directory in the warning message.
4801 Previously, we would only tell the user that some hidden service
4802 was ignored. Bugfix on 0.0.6; fixes bug 4426.
4803 - Update to the December 6 2011 Maxmind GeoLite Country database.
4805 o Packaging changes:
4806 - Make it easier to automate expert package builds on Windows,
4807 by removing an absolute path from makensis.exe command.
4810 Changes in version 0.2.1.32 - 2011-12-16
4811 Tor 0.2.1.32 backports important security and privacy fixes for
4812 oldstable. This release is intended only for package maintainers and
4813 others who cannot use the 0.2.2 stable series. All others should be
4814 using Tor 0.2.2.x or newer.
4816 The Tor 0.2.1.x series will reach formal end-of-life some time in
4817 early 2012; we will stop releasing patches for it then.
4819 o Major bugfixes (also included in 0.2.2.x):
4820 - Correctly sanity-check that we don't underflow on a memory
4821 allocation (and then assert) for hidden service introduction
4822 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
4823 bugfix on 0.2.1.5-alpha.
4824 - Fix a heap overflow bug that could occur when trying to pull
4825 data into the first chunk of a buffer, when that chunk had
4826 already had some data drained from it. Fixes CVE-2011-2778;
4827 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
4830 - Update to the December 6 2011 Maxmind GeoLite Country database.
4833 Changes in version 0.2.2.34 - 2011-10-26
4834 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
4835 can deanonymize Tor users. Everybody should upgrade.
4837 The attack relies on four components: 1) Clients reuse their TLS cert
4838 when talking to different relays, so relays can recognize a user by
4839 the identity key in her cert. 2) An attacker who knows the client's
4840 identity key can probe each guard relay to see if that identity key
4841 is connected to that guard relay right now. 3) A variety of active
4842 attacks in the literature (starting from "Low-Cost Traffic Analysis
4843 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
4844 discover the guard relays that a Tor user visiting the website is using.
4845 4) Clients typically pick three guards at random, so the set of guards
4846 for a given user could well be a unique fingerprint for her. This
4847 release fixes components #1 and #2, which is enough to block the attack;
4848 the other two remain as open research problems. Special thanks to
4849 "frosty_un" for reporting the issue to us!
4851 Clients should upgrade so they are no longer recognizable by the TLS
4852 certs they present. Relays should upgrade so they no longer allow a
4853 remote attacker to probe them to test whether unpatched clients are
4854 currently connected to them.
4856 This release also fixes several vulnerabilities that allow an attacker
4857 to enumerate bridge relays. Some bridge enumeration attacks still
4858 remain; see for example proposal 188.
4860 o Privacy/anonymity fixes (clients):
4861 - Clients and bridges no longer send TLS certificate chains on
4862 outgoing OR connections. Previously, each client or bridge would
4863 use the same cert chain for all outgoing OR connections until
4864 its IP address changes, which allowed any relay that the client
4865 or bridge contacted to determine which entry guards it is using.
4866 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
4867 - If a relay receives a CREATE_FAST cell on a TLS connection, it
4868 no longer considers that connection as suitable for satisfying a
4869 circuit EXTEND request. Now relays can protect clients from the
4870 CVE-2011-2768 issue even if the clients haven't upgraded yet.
4871 - Directory authorities no longer assign the Guard flag to relays
4872 that haven't upgraded to the above "refuse EXTEND requests
4873 to client connections" fix. Now directory authorities can
4874 protect clients from the CVE-2011-2768 issue even if neither
4875 the clients nor the relays have upgraded yet. There's a new
4876 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
4877 to let us transition smoothly, else tomorrow there would be no
4880 o Privacy/anonymity fixes (bridge enumeration):
4881 - Bridge relays now do their directory fetches inside Tor TLS
4882 connections, like all the other clients do, rather than connecting
4883 directly to the DirPort like public relays do. Removes another
4884 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
4885 - Bridges relays now build circuits for themselves in a more similar
4886 way to how clients build them. Removes another avenue for
4887 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
4888 when bridges were introduced.
4889 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
4890 that they initiated. Relays could distinguish incoming bridge
4891 connections from client connections, creating another avenue for
4892 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
4893 Found by "frosty_un".
4896 - Fix a crash bug when changing node restrictions while a DNS lookup
4897 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
4899 - Don't launch a useless circuit after failing to use one of a
4900 hidden service's introduction points. Previously, we would
4901 launch a new introduction circuit, but not set the hidden service
4902 which that circuit was intended to connect to, so it would never
4903 actually be used. A different piece of code would then create a
4904 new introduction circuit correctly. Bug reported by katmagic and
4905 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
4908 - Change an integer overflow check in the OpenBSD_Malloc code so
4909 that GCC is less likely to eliminate it as impossible. Patch
4910 from Mansour Moufid. Fixes bug 4059.
4911 - When a hidden service turns an extra service-side introduction
4912 circuit into a general-purpose circuit, free the rend_data and
4913 intro_key fields first, so we won't leak memory if the circuit
4914 is cannibalized for use as another service-side introduction
4915 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
4916 - Bridges now skip DNS self-tests, to act a little more stealthily.
4917 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
4918 bridges. Patch by "warms0x".
4919 - Fix internal bug-checking logic that was supposed to catch
4920 failures in digest generation so that it will fail more robustly
4921 if we ask for a nonexistent algorithm. Found by Coverity Scan.
4922 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
4923 - Report any failure in init_keys() calls launched because our
4924 IP address has changed. Spotted by Coverity Scan. Bugfix on
4925 0.1.1.4-alpha; fixes CID 484.
4927 o Minor bugfixes (log messages and documentation):
4928 - Remove a confusing dollar sign from the example fingerprint in the
4929 man page, and also make the example fingerprint a valid one. Fixes
4930 bug 4309; bugfix on 0.2.1.3-alpha.
4931 - The next version of Windows will be called Windows 8, and it has
4932 a major version of 6, minor version of 2. Correctly identify that
4933 version instead of calling it "Very recent version". Resolves
4934 ticket 4153; reported by funkstar.
4935 - Downgrade log messages about circuit timeout calibration from
4936 "notice" to "info": they don't require or suggest any human
4937 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
4938 bugfix on 0.2.2.14-alpha.
4941 - Turn on directory request statistics by default and include them in
4942 extra-info descriptors. Don't break if we have no GeoIP database.
4943 Backported from 0.2.3.1-alpha; implements ticket 3951.
4944 - Update to the October 4 2011 Maxmind GeoLite Country database.
4947 Changes in version 0.2.1.31 - 2011-10-26
4948 Tor 0.2.1.31 backports important security and privacy fixes for
4949 oldstable. This release is intended only for package maintainers and
4950 others who cannot use the 0.2.2 stable series. All others should be
4951 using Tor 0.2.2.x or newer.
4953 o Security fixes (also included in 0.2.2.x):
4954 - Replace all potentially sensitive memory comparison operations
4955 with versions whose runtime does not depend on the data being
4956 compared. This will help resist a class of attacks where an
4957 adversary can use variations in timing information to learn
4958 sensitive data. Fix for one case of bug 3122. (Safe memcmp
4959 implementation by Robert Ransom based partially on code by DJB.)
4960 - Fix an assert in parsing router descriptors containing IPv6
4961 addresses. This one took down the directory authorities when
4962 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
4964 o Privacy/anonymity fixes (also included in 0.2.2.x):
4965 - Clients and bridges no longer send TLS certificate chains on
4966 outgoing OR connections. Previously, each client or bridge would
4967 use the same cert chain for all outgoing OR connections until
4968 its IP address changes, which allowed any relay that the client
4969 or bridge contacted to determine which entry guards it is using.
4970 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
4971 - If a relay receives a CREATE_FAST cell on a TLS connection, it
4972 no longer considers that connection as suitable for satisfying a
4973 circuit EXTEND request. Now relays can protect clients from the
4974 CVE-2011-2768 issue even if the clients haven't upgraded yet.
4975 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
4976 that they initiated. Relays could distinguish incoming bridge
4977 connections from client connections, creating another avenue for
4978 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
4979 Found by "frosty_un".
4980 - When receiving a hidden service descriptor, check that it is for
4981 the hidden service we wanted. Previously, Tor would store any
4982 hidden service descriptors that a directory gave it, whether it
4983 wanted them or not. This wouldn't have let an attacker impersonate
4984 a hidden service, but it did let directories pre-seed a client
4985 with descriptors that it didn't want. Bugfix on 0.0.6.
4986 - Avoid linkability based on cached hidden service descriptors: forget
4987 all hidden service descriptors cached as a client when processing a
4988 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
4989 - Make the bridge directory authority refuse to answer directory
4990 requests for "all" descriptors. It used to include bridge
4991 descriptors in its answer, which was a major information leak.
4992 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
4993 - Don't attach new streams to old rendezvous circuits after SIGNAL
4994 NEWNYM. Previously, we would keep using an existing rendezvous
4995 circuit if it remained open (i.e. if it were kept open by a
4996 long-lived stream, or if a new stream were attached to it before
4997 Tor could notice that it was old and no longer in use). Bugfix on
4998 0.1.1.15-rc; fixes bug 3375.
5000 o Minor bugfixes (also included in 0.2.2.x):
5001 - When we restart our relay, we might get a successful connection
5002 from the outside before we've started our reachability tests,
5003 triggering a warning: "ORPort found reachable, but I have no
5004 routerinfo yet. Failing to inform controller of success." This
5005 bug was harmless unless Tor is running under a controller
5006 like Vidalia, in which case the controller would never get a
5007 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
5009 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
5010 enabled. Fixes bug 1526.
5011 - Remove undocumented option "-F" from tor-resolve: it hasn't done
5012 anything since 0.2.1.16-rc.
5013 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
5014 None of the cases where we did this before were wrong, but by making
5015 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
5016 - Fix a rare crash bug that could occur when a client was configured
5017 with a large number of bridges. Fixes bug 2629; bugfix on
5018 0.2.1.2-alpha. Bugfix by trac user "shitlei".
5019 - Correct the warning displayed when a rendezvous descriptor exceeds
5020 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
5022 - Fix an uncommon assertion failure when running with DNSPort under
5023 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
5024 - When warning about missing zlib development packages during compile,
5025 give the correct package names. Bugfix on 0.2.0.1-alpha.
5026 - Require that introduction point keys and onion keys have public
5027 exponent 65537. Bugfix on 0.2.0.10-alpha.
5028 - Do not crash when our configuration file becomes unreadable, for
5029 example due to a permissions change, between when we start up
5030 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
5032 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
5034 - Always NUL-terminate the sun_path field of a sockaddr_un before
5035 passing it to the kernel. (Not a security issue: kernels are
5036 smart enough to reject bad sockaddr_uns.) Found by Coverity;
5037 CID #428. Bugfix on Tor 0.2.0.3-alpha.
5038 - Don't stack-allocate the list of supplementary GIDs when we're
5039 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
5040 could take up to 256K, which is way too much stack. Found by
5041 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
5043 o Minor bugfixes (only in 0.2.1.x):
5044 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
5045 rely on them. Bugfix on 0.2.1.30.
5046 - Use git revisions instead of svn revisions when generating our
5047 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
5049 o Minor features (also included in 0.2.2.x):
5050 - Adjust the expiration time on our SSL session certificates to
5051 better match SSL certs seen in the wild. Resolves ticket 4014.
5052 - Allow nameservers with IPv6 address. Resolves bug 2574.
5053 - Update to the October 4 2011 Maxmind GeoLite Country database.
5056 Changes in version 0.2.2.33 - 2011-09-13
5057 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
5058 TLS handshake that makes relays and bridges that run this new version
5059 reachable from Iran again.
5062 - Avoid an assertion failure when reloading a configuration with
5063 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
5064 3923; bugfix on 0.2.2.25-alpha.
5066 o Minor features (security):
5067 - Check for replays of the public-key encrypted portion of an
5068 INTRODUCE1 cell, in addition to the current check for replays of
5069 the g^x value. This prevents a possible class of active attacks
5070 by an attacker who controls both an introduction point and a
5071 rendezvous point, and who uses the malleability of AES-CTR to
5072 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
5073 that these attacks are infeasible (requiring the attacker to send
5074 on the order of zettabytes of altered cells in a short interval),
5075 but we'd rather block them off in case there are any classes of
5076 this attack that we missed. Reported by Willem Pinckaers.
5079 - Adjust the expiration time on our SSL session certificates to
5080 better match SSL certs seen in the wild. Resolves ticket 4014.
5081 - Change the default required uptime for a relay to be accepted as
5082 a HSDir (hidden service directory) from 24 hours to 25 hours.
5083 Improves on 0.2.0.10-alpha; resolves ticket 2649.
5084 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
5085 authorities to abstain from voting on assignment of the HSDir
5086 consensus flag. Related to bug 2649.
5087 - Update to the September 6 2011 Maxmind GeoLite Country database.
5089 o Minor bugfixes (documentation and log messages):
5090 - Correct the man page to explain that HashedControlPassword and
5091 CookieAuthentication can both be set, in which case either method
5092 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
5093 when we decided to allow these config options to both be set. Issue
5095 - Demote the 'replay detected' log message emitted when a hidden
5096 service receives the same Diffie-Hellman public key in two different
5097 INTRODUCE2 cells to info level. A normal Tor client can cause that
5098 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
5099 fixes part of bug 2442.
5100 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
5101 level. There is nothing that a hidden service's operator can do
5102 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
5104 - Clarify a log message specifying the characters permitted in
5105 HiddenServiceAuthorizeClient client names. Previously, the log
5106 message said that "[A-Za-z0-9+-_]" were permitted; that could have
5107 given the impression that every ASCII character between "+" and "_"
5108 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
5111 - Provide a substitute implementation of lround() for MSVC, which
5112 apparently lacks it. Patch from Gisle Vanem.
5113 - Clean up some code issues that prevented Tor from building on older
5114 BSDs. Fixes bug 3894; reported by "grarpamp".
5115 - Search for a platform-specific version of "ar" when cross-compiling.
5116 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
5119 Changes in version 0.2.2.32 - 2011-08-27
5120 The Tor 0.2.2 release series is dedicated to the memory of Andreas
5121 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
5122 a founder of the PETS community, a leader in our field, a mentor,
5123 and a friend. He left us with these words: "I had the possibility
5124 to contribute to this world that is not as it should be. I hope I
5125 could help in some areas to make the world a better place, and that
5126 I could also encourage other people to be engaged in improving the
5127 world. Please, stay engaged. This world needs you, your love, your
5128 initiative -- now I cannot be part of that anymore."
5130 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
5131 ready. More than two years in the making, this release features improved
5132 client performance and hidden service reliability, better compatibility
5133 for Android, correct behavior for bridges that listen on more than
5134 one address, more extensible and flexible directory object handling,
5135 better reporting of network statistics, improved code security, and
5136 many many other features and bugfixes.
5138 o Major features (client performance):
5139 - When choosing which cells to relay first, relays now favor circuits
5140 that have been quiet recently, to provide lower latency for
5141 low-volume circuits. By default, relays enable or disable this
5142 feature based on a setting in the consensus. They can override
5143 this default by using the new "CircuitPriorityHalflife" config
5144 option. Design and code by Ian Goldberg, Can Tang, and Chris
5146 - Directory authorities now compute consensus weightings that instruct
5147 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
5148 and no flag. Clients use these weightings to distribute network load
5149 more evenly across these different relay types. The weightings are
5150 in the consensus so we can change them globally in the future. Extra
5151 thanks to "outofwords" for finding some nasty security bugs in
5152 the first implementation of this feature.
5154 o Major features (client performance, circuit build timeout):
5155 - Tor now tracks how long it takes to build client-side circuits
5156 over time, and adapts its timeout to local network performance.
5157 Since a circuit that takes a long time to build will also provide
5158 bad performance, we get significant latency improvements by
5159 discarding the slowest 20% of circuits. Specifically, Tor creates
5160 circuits more aggressively than usual until it has enough data
5161 points for a good timeout estimate. Implements proposal 151.
5162 - Circuit build timeout constants can be controlled by consensus
5163 parameters. We set good defaults for these parameters based on
5164 experimentation on broadband and simulated high-latency links.
5165 - Circuit build time learning can be disabled via consensus parameter
5166 or by the client via a LearnCircuitBuildTimeout config option. We
5167 also automatically disable circuit build time calculation if either
5168 AuthoritativeDirectory is set, or if we fail to write our state
5169 file. Implements ticket 1296.
5171 o Major features (relays use their capacity better):
5172 - Set SO_REUSEADDR socket option on all sockets, not just
5173 listeners. This should help busy exit nodes avoid running out of
5174 useable ports just because all the ports have been used in the
5175 near past. Resolves issue 2850.
5176 - Relays now save observed peak bandwidth throughput rates to their
5177 state file (along with total usage, which was already saved),
5178 so that they can determine their correct estimated bandwidth on
5179 restart. Resolves bug 1863, where Tor relays would reset their
5180 estimated bandwidth to 0 after restarting.
5181 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
5182 should give us approximately 40-50% more Guard-flagged nodes,
5183 improving the anonymity the Tor network can provide and also
5184 decreasing the dropoff in throughput that relays experience when
5185 they first get the Guard flag.
5186 - Directory authorities now take changes in router IP address and
5187 ORPort into account when determining router stability. Previously,
5188 if a router changed its IP or ORPort, the authorities would not
5189 treat it as having any downtime for the purposes of stability
5190 calculation, whereas clients would experience downtime since the
5191 change would take a while to propagate to them. Resolves issue 1035.
5192 - New AccelName and AccelDir options add support for dynamic OpenSSL
5193 hardware crypto acceleration engines.
5195 o Major features (relays control their load better):
5196 - Exit relays now try harder to block exit attempts from unknown
5197 relays, to make it harder for people to use them as one-hop proxies
5198 a la tortunnel. Controlled by the refuseunknownexits consensus
5199 parameter (currently enabled), or you can override it on your
5200 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
5201 based on a variant of proposal 163.
5202 - Add separate per-conn write limiting to go with the per-conn read
5203 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
5204 but never per-conn write limits.
5205 - New consensus params "bwconnrate" and "bwconnburst" to let us
5206 rate-limit client connections as they enter the network. It's
5207 controlled in the consensus so we can turn it on and off for
5208 experiments. It's starting out off. Based on proposal 163.
5210 o Major features (controllers):
5211 - Export GeoIP information on bridge usage to controllers even if we
5212 have not yet been running for 24 hours. Now Vidalia bridge operators
5213 can get more accurate and immediate feedback about their
5214 contributions to the network.
5215 - Add an __OwningControllerProcess configuration option and a
5216 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
5217 that when it exits, Tor will shut down. Implements feature 3049.
5219 o Major features (directory authorities):
5220 - Directory authorities now create, vote on, and serve multiple
5221 parallel formats of directory data as part of their voting process.
5222 Partially implements Proposal 162: "Publish the consensus in
5224 - Directory authorities now agree on and publish small summaries
5225 of router information that clients can use in place of regular
5226 server descriptors. This transition will allow Tor 0.2.3 clients
5227 to use far less bandwidth for downloading information about the
5228 network. Begins the implementation of Proposal 158: "Clients
5229 download consensus + microdescriptors".
5230 - The directory voting system is now extensible to use multiple hash
5231 algorithms for signatures and resource selection. Newer formats
5232 are signed with SHA256, with a possibility for moving to a better
5233 hash algorithm in the future.
5234 - Directory authorities can now vote on arbitary integer values as
5235 part of the consensus process. This is designed to help set
5236 network-wide parameters. Implements proposal 167.
5238 o Major features and bugfixes (node selection):
5239 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
5240 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
5241 options. Previously, we had been ambiguous in describing what
5242 counted as an "exit" node, and what operations exactly "StrictNodes
5243 0" would permit. This created confusion when people saw nodes built
5244 through unexpected circuits, and made it hard to tell real bugs from
5245 surprises. Now the intended behavior is:
5246 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
5247 a node that delivers user traffic outside the Tor network.
5248 . "Entry", in the context of EntryNodes, means a node used as the
5249 first hop of a multihop circuit. It doesn't include direct
5250 connections to directory servers.
5251 . "ExcludeNodes" applies to all nodes.
5252 . "StrictNodes" changes the behavior of ExcludeNodes only. When
5253 StrictNodes is set, Tor should avoid all nodes listed in
5254 ExcludeNodes, even when it will make user requests fail. When
5255 StrictNodes is *not* set, then Tor should follow ExcludeNodes
5256 whenever it can, except when it must use an excluded node to
5257 perform self-tests, connect to a hidden service, provide a
5258 hidden service, fulfill a .exit request, upload directory
5259 information, or fetch directory information.
5260 Collectively, the changes to implement the behavior fix bug 1090.
5261 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
5262 change during a config reload, mark and discard all our origin
5263 circuits. This fix should address edge cases where we change the
5264 config options and but then choose a circuit that we created before
5266 - Make EntryNodes config option much more aggressive even when
5267 StrictNodes is not set. Before it would prepend your requested
5268 entrynodes to your list of guard nodes, but feel free to use others
5269 after that. Now it chooses only from your EntryNodes if any of
5270 those are available, and only falls back to others if a) they're
5271 all down and b) StrictNodes is not set.
5272 - Now we refresh your entry guards from EntryNodes at each consensus
5273 fetch -- rather than just at startup and then they slowly rot as
5274 the network changes.
5275 - Add support for the country code "{??}" in torrc options like
5276 ExcludeNodes, to indicate all routers of unknown country. Closes
5278 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
5279 a node is listed in both, it's treated as excluded.
5280 - ExcludeNodes now applies to directory nodes -- as a preference if
5281 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
5282 Don't exclude all the directory authorities and set StrictNodes to 1
5283 unless you really want your Tor to break.
5284 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
5285 - ExcludeExitNodes now overrides .exit requests.
5286 - We don't use bridges listed in ExcludeNodes.
5287 - When StrictNodes is 1:
5288 . We now apply ExcludeNodes to hidden service introduction points
5289 and to rendezvous points selected by hidden service users. This
5290 can make your hidden service less reliable: use it with caution!
5291 . If we have used ExcludeNodes on ourself, do not try relay
5292 reachability self-tests.
5293 . If we have excluded all the directory authorities, we will not
5294 even try to upload our descriptor if we're a relay.
5295 . Do not honor .exit requests to an excluded node.
5296 - When the set of permitted nodes changes, we now remove any mappings
5297 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
5299 - We never cannibalize a circuit that had excluded nodes on it, even
5300 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
5301 - Improve log messages related to excluded nodes.
5303 o Major features (misc):
5304 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
5305 to help Tor build correctly for Android phones.
5306 - The options SocksPort, ControlPort, and so on now all accept a
5307 value "auto" that opens a socket on an OS-selected port. A
5308 new ControlPortWriteToFile option tells Tor to write its
5309 actual control port or ports to a chosen file. If the option
5310 ControlPortFileGroupReadable is set, the file is created as
5311 group-readable. Now users can run two Tor clients on the same
5312 system without needing to manually mess with parameters. Resolves
5313 part of ticket 3076.
5314 - Tor now supports tunneling all of its outgoing connections over
5315 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
5316 configuration options. Code by Christopher Davis.
5318 o Code security improvements:
5319 - Replace all potentially sensitive memory comparison operations
5320 with versions whose runtime does not depend on the data being
5321 compared. This will help resist a class of attacks where an
5322 adversary can use variations in timing information to learn
5323 sensitive data. Fix for one case of bug 3122. (Safe memcmp
5324 implementation by Robert Ransom based partially on code by DJB.)
5325 - Enable Address Space Layout Randomization (ASLR) and Data Execution
5326 Prevention (DEP) by default on Windows to make it harder for
5327 attackers to exploit vulnerabilities. Patch from John Brooks.
5328 - New "--enable-gcc-hardening" ./configure flag (off by default)
5329 to turn on gcc compile time hardening options. It ensures
5330 that signed ints have defined behavior (-fwrapv), enables
5331 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
5332 with canaries (-fstack-protector-all), turns on ASLR protection if
5333 supported by the kernel (-fPIE, -pie), and adds additional security
5334 related warnings. Verified to work on Mac OS X and Debian Lenny.
5335 - New "--enable-linker-hardening" ./configure flag (off by default)
5336 to turn on ELF specific hardening features (relro, now). This does
5337 not work with Mac OS X or any other non-ELF binary format.
5338 - Always search the Windows system directory for system DLLs, and
5339 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
5340 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
5341 current and future memory pages via mlockall(). On supported
5342 platforms (modern Linux and probably BSD but not Windows or OS X),
5343 this should effectively disable any and all attempts to page out
5344 memory. This option requires that you start your Tor as root --
5345 if you use DisableAllSwap, please consider using the User option
5346 to properly reduce the privileges of your Tor.
5348 o Major bugfixes (crashes):
5349 - Fix crash bug on platforms where gmtime and localtime can return
5350 NULL. Windows 7 users were running into this one. Fixes part of bug
5351 2077. Bugfix on all versions of Tor. Found by boboper.
5352 - Introduce minimum/maximum values that clients will believe
5353 from the consensus. Now we'll have a better chance to avoid crashes
5354 or worse when a consensus param has a weird value.
5355 - Fix a rare crash bug that could occur when a client was configured
5356 with a large number of bridges. Fixes bug 2629; bugfix on
5357 0.2.1.2-alpha. Bugfix by trac user "shitlei".
5358 - Do not crash when our configuration file becomes unreadable, for
5359 example due to a permissions change, between when we start up
5360 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
5362 - If we're in the pathological case where there's no exit bandwidth
5363 but there is non-exit bandwidth, or no guard bandwidth but there
5364 is non-guard bandwidth, don't crash during path selection. Bugfix
5366 - Fix a crash bug when trying to initialize the evdns module in
5367 Libevent 2. Bugfix on 0.2.1.16-rc.
5369 o Major bugfixes (stability):
5370 - Fix an assert in parsing router descriptors containing IPv6
5371 addresses. This one took down the directory authorities when
5372 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
5373 - Fix an uncommon assertion failure when running with DNSPort under
5374 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
5375 - Treat an unset $HOME like an empty $HOME rather than triggering an
5376 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
5377 - More gracefully handle corrupt state files, removing asserts
5378 in favor of saving a backup and resetting state.
5379 - Instead of giving an assertion failure on an internal mismatch
5380 on estimated freelist size, just log a BUG warning and try later.
5381 Mitigates but does not fix bug 1125.
5382 - Fix an assert that got triggered when using the TestingTorNetwork
5383 configuration option and then issuing a GETINFO config-text control
5384 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
5385 - If the cached cert file is unparseable, warn but don't exit.
5387 o Privacy fixes (relays/bridges):
5388 - Don't list Windows capabilities in relay descriptors. We never made
5389 use of them, and maybe it's a bad idea to publish them. Bugfix
5391 - If the Nickname configuration option isn't given, Tor would pick a
5392 nickname based on the local hostname as the nickname for a relay.
5393 Because nicknames are not very important in today's Tor and the
5394 "Unnamed" nickname has been implemented, this is now problematic
5395 behavior: It leaks information about the hostname without being
5396 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
5397 introduced the Unnamed nickname. Reported by tagnaq.
5398 - Maintain separate TLS contexts and certificates for incoming and
5399 outgoing connections in bridge relays. Previously we would use the
5400 same TLS contexts and certs for incoming and outgoing connections.
5401 Bugfix on 0.2.0.3-alpha; addresses bug 988.
5402 - Maintain separate identity keys for incoming and outgoing TLS
5403 contexts in bridge relays. Previously we would use the same
5404 identity keys for incoming and outgoing TLS contexts. Bugfix on
5405 0.2.0.3-alpha; addresses the other half of bug 988.
5406 - Make the bridge directory authority refuse to answer directory
5407 requests for "all descriptors". It used to include bridge
5408 descriptors in its answer, which was a major information leak.
5409 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
5411 o Privacy fixes (clients):
5412 - When receiving a hidden service descriptor, check that it is for
5413 the hidden service we wanted. Previously, Tor would store any
5414 hidden service descriptors that a directory gave it, whether it
5415 wanted them or not. This wouldn't have let an attacker impersonate
5416 a hidden service, but it did let directories pre-seed a client
5417 with descriptors that it didn't want. Bugfix on 0.0.6.
5418 - Start the process of disabling ".exit" address notation, since it
5419 can be used for a variety of esoteric application-level attacks
5420 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
5422 - Reject attempts at the client side to open connections to private
5423 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
5424 a randomly chosen exit node. Attempts to do so are always
5425 ill-defined, generally prevented by exit policies, and usually
5426 in error. This will also help to detect loops in transparent
5427 proxy configurations. You can disable this feature by setting
5428 "ClientRejectInternalAddresses 0" in your torrc.
5429 - Log a notice when we get a new control connection. Now it's easier
5430 for security-conscious users to recognize when a local application
5431 is knocking on their controller door. Suggested by bug 1196.
5433 o Privacy fixes (newnym):
5434 - Avoid linkability based on cached hidden service descriptors: forget
5435 all hidden service descriptors cached as a client when processing a
5436 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
5437 - On SIGHUP, do not clear out all TrackHostExits mappings, client
5438 DNS cache entries, and virtual address mappings: that's what
5439 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
5440 - Don't attach new streams to old rendezvous circuits after SIGNAL
5441 NEWNYM. Previously, we would keep using an existing rendezvous
5442 circuit if it remained open (i.e. if it were kept open by a
5443 long-lived stream, or if a new stream were attached to it before
5444 Tor could notice that it was old and no longer in use). Bugfix on
5445 0.1.1.15-rc; fixes bug 3375.
5447 o Major bugfixes (relay bandwidth accounting):
5448 - Fix a bug that could break accounting on 64-bit systems with large
5449 time_t values, making them hibernate for impossibly long intervals.
5450 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
5451 - Fix a bug in bandwidth accounting that could make us use twice
5452 the intended bandwidth when our interval start changes due to
5453 daylight saving time. Now we tolerate skew in stored vs computed
5454 interval starts: if the start of the period changes by no more than
5455 50% of the period's duration, we remember bytes that we transferred
5456 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
5458 o Major bugfixes (bridges):
5459 - Bridges now use "reject *:*" as their default exit policy. Bugfix
5460 on 0.2.0.3-alpha. Fixes bug 1113.
5461 - If you configure your bridge with a known identity fingerprint,
5462 and the bridge authority is unreachable (as it is in at least
5463 one country now), fall back to directly requesting the descriptor
5464 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
5466 - Fix a bug where bridge users who configure the non-canonical
5467 address of a bridge automatically switch to its canonical
5468 address. If a bridge listens at more than one address, it
5469 should be able to advertise those addresses independently and
5470 any non-blocked addresses should continue to work. Bugfix on Tor
5471 0.2.0.3-alpha. Fixes bug 2510.
5472 - If you configure Tor to use bridge A, and then quit and
5473 configure Tor to use bridge B instead (or if you change Tor
5474 to use bridge B via the controller), it would happily continue
5475 to use bridge A if it's still reachable. While this behavior is
5476 a feature if your goal is connectivity, in some scenarios it's a
5477 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
5478 - When the controller configures a new bridge, don't wait 10 to 60
5479 seconds before trying to fetch its descriptor. Bugfix on
5480 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
5482 o Major bugfixes (directory authorities):
5483 - Many relays have been falling out of the consensus lately because
5484 not enough authorities know about their descriptor for them to get
5485 a majority of votes. When we deprecated the v2 directory protocol,
5486 we got rid of the only way that v3 authorities can hear from each
5487 other about other descriptors. Now authorities examine every v3
5488 vote for new descriptors, and fetch them from that authority. Bugfix
5490 - Authorities could be tricked into giving out the Exit flag to relays
5491 that didn't allow exiting to any ports. This bug could screw
5492 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
5493 1238. Bug discovered by Martin Kowalczyk.
5494 - If all authorities restart at once right before a consensus vote,
5495 nobody will vote about "Running", and clients will get a consensus
5496 with no usable relays. Instead, authorities refuse to build a
5497 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
5499 o Major bugfixes (stream-level fairness):
5500 - When receiving a circuit-level SENDME for a blocked circuit, try
5501 to package cells fairly from all the streams that had previously
5502 been blocked on that circuit. Previously, we had started with the
5503 oldest stream, and allowed each stream to potentially exhaust
5504 the circuit's package window. This gave older streams on any
5505 given circuit priority over newer ones. Fixes bug 1937. Detected
5506 originally by Camilo Viecco. This bug was introduced before the
5507 first Tor release, in svn commit r152: it is the new winner of
5508 the longest-lived bug prize.
5509 - Fix a stream fairness bug that would cause newer streams on a given
5510 circuit to get preference when reading bytes from the origin or
5511 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
5512 introduced before the first Tor release, in svn revision r152.
5513 - When the exit relay got a circuit-level sendme cell, it started
5514 reading on the exit streams, even if had 500 cells queued in the
5515 circuit queue already, so the circuit queue just grew and grew in
5516 some cases. We fix this by not re-enabling reading on receipt of a
5517 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
5518 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
5520 - Newly created streams were allowed to read cells onto circuits,
5521 even if the circuit's cell queue was blocked and waiting to drain.
5522 This created potential unfairness, as older streams would be
5523 blocked, but newer streams would gladly fill the queue completely.
5524 We add code to detect this situation and prevent any stream from
5525 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
5528 o Major bugfixes (hidden services):
5529 - Apply circuit timeouts to opened hidden-service-related circuits
5530 based on the correct start time. Previously, we would apply the
5531 circuit build timeout based on time since the circuit's creation;
5532 it was supposed to be applied based on time since the circuit
5533 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
5534 - Improve hidden service robustness: When we find that we have
5535 extended a hidden service's introduction circuit to a relay not
5536 listed as an introduction point in the HS descriptor we currently
5537 have, retry with an introduction point from the current
5538 descriptor. Previously we would just give up. Fixes bugs 1024 and
5539 1930; bugfix on 0.2.0.10-alpha.
5540 - Directory authorities now use data collected from their own
5541 uptime observations when choosing whether to assign the HSDir flag
5542 to relays, instead of trusting the uptime value the relay reports in
5543 its descriptor. This change helps prevent an attack where a small
5544 set of nodes with frequently-changing identity keys can blackhole
5545 a hidden service. (Only authorities need upgrade; others will be
5546 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
5547 - Stop assigning the HSDir flag to relays that disable their
5548 DirPort (and thus will refuse to answer directory requests). This
5549 fix should dramatically improve the reachability of hidden services:
5550 hidden services and hidden service clients pick six HSDir relays
5551 to store and retrieve the hidden service descriptor, and currently
5552 about half of the HSDir relays will refuse to work. Bugfix on
5553 0.2.0.10-alpha; fixes part of bug 1693.
5555 o Major bugfixes (misc):
5556 - Clients now stop trying to use an exit node associated with a given
5557 destination by TrackHostExits if they fail to reach that exit node.
5558 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
5559 - Fix a regression that caused Tor to rebind its ports if it receives
5560 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
5561 - Remove an extra pair of quotation marks around the error
5562 message in control-port STATUS_GENERAL BUG events. Bugfix on
5563 0.1.2.6-alpha; fixes bug 3732.
5565 o Minor features (relays):
5566 - Ensure that no empty [dirreq-](read|write)-history lines are added
5567 to an extrainfo document. Implements ticket 2497.
5568 - When bandwidth accounting is enabled, be more generous with how
5569 much bandwidth we'll use up before entering "soft hibernation".
5570 Previously, we'd refuse new connections and circuits once we'd
5571 used up 95% of our allotment. Now, we use up 95% of our allotment,
5572 AND make sure that we have no more than 500MB (or 3 hours of
5573 expected traffic, whichever is lower) remaining before we enter
5575 - Relays now log the reason for publishing a new relay descriptor,
5576 so we have a better chance of hunting down instances of bug 1810.
5577 Resolves ticket 3252.
5578 - Log a little more clearly about the times at which we're no longer
5579 accepting new connections (e.g. due to hibernating). Resolves
5581 - When AllowSingleHopExits is set, print a warning to explain to the
5582 relay operator why most clients are avoiding her relay.
5583 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
5584 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
5585 clients are already deprecated because of security bugs.
5587 o Minor features (network statistics):
5588 - Directory mirrors that set "DirReqStatistics 1" write statistics
5589 about directory requests to disk every 24 hours. As compared to the
5590 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
5591 improvements: 1) stats are written to disk exactly every 24 hours;
5592 2) estimated shares of v2 and v3 requests are determined as mean
5593 values, not at the end of a measurement period; 3) unresolved
5594 requests are listed with country code '??'; 4) directories also
5595 measure download times.
5596 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
5597 number of exit streams and transferred bytes per port to disk every
5599 - Relays that set "CellStatistics 1" write statistics on how long
5600 cells spend in their circuit queues to disk every 24 hours.
5601 - Entry nodes that set "EntryStatistics 1" write statistics on the
5602 rough number and origins of connecting clients to disk every 24
5604 - Relays that write any of the above statistics to disk and set
5605 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
5606 their extra-info documents. Implements proposal 166.
5608 o Minor features (GeoIP and statistics):
5609 - Provide a log message stating which geoip file we're parsing
5610 instead of just stating that we're parsing the geoip file.
5611 Implements ticket 2432.
5612 - Make sure every relay writes a state file at least every 12 hours.
5613 Previously, a relay could go for weeks without writing its state
5614 file, and on a crash could lose its bandwidth history, capacity
5615 estimates, client country statistics, and so on. Addresses bug 3012.
5616 - Relays report the number of bytes spent on answering directory
5617 requests in extra-info descriptors similar to {read,write}-history.
5618 Implements enhancement 1790.
5619 - Report only the top 10 ports in exit-port stats in order not to
5620 exceed the maximum extra-info descriptor length of 50 KB. Implements
5622 - If writing the state file to disk fails, wait up to an hour before
5623 retrying again, rather than trying again each second. Fixes bug
5624 2346; bugfix on Tor 0.1.1.3-alpha.
5625 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
5626 when we switch from being a public relay to a bridge. Otherwise
5627 there will still be clients that see the relay in their consensus,
5628 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
5630 - Update to the August 2 2011 Maxmind GeoLite Country database.
5632 o Minor features (clients):
5633 - When expiring circuits, use microsecond timers rather than
5634 one-second timers. This can avoid an unpleasant situation where a
5635 circuit is launched near the end of one second and expired right
5636 near the beginning of the next, and prevent fluctuations in circuit
5638 - If we've configured EntryNodes and our network goes away and/or all
5639 our entrynodes get marked down, optimistically retry them all when
5640 a new socks application request appears. Fixes bug 1882.
5641 - Always perform router selections using weighted relay bandwidth,
5642 even if we don't need a high capacity circuit at the time. Non-fast
5643 circuits now only differ from fast ones in that they can use relays
5644 not marked with the Fast flag. This "feature" could turn out to
5645 be a horrible bug; we should investigate more before it goes into
5647 - When we run out of directory information such that we can't build
5648 circuits, but then get enough that we can build circuits, log when
5649 we actually construct a circuit, so the user has a better chance of
5650 knowing what's going on. Fixes bug 1362.
5651 - Log SSL state transitions at debug level during handshake, and
5652 include SSL states in error messages. This may help debug future
5653 SSL handshake issues.
5655 o Minor features (directory authorities):
5656 - When a router changes IP address or port, authorities now launch
5657 a new reachability test for it. Implements ticket 1899.
5658 - Directory authorities now reject relays running any versions of
5659 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
5660 known bugs that keep RELAY_EARLY cells from working on rendezvous
5661 circuits. Followup to fix for bug 2081.
5662 - Directory authorities now reject relays running any version of Tor
5663 older than 0.2.0.26-rc. That version is the earliest that fetches
5664 current directory information correctly. Fixes bug 2156.
5665 - Directory authorities now do an immediate reachability check as soon
5666 as they hear about a new relay. This change should slightly reduce
5667 the time between setting up a relay and getting listed as running
5668 in the consensus. It should also improve the time between setting
5669 up a bridge and seeing use by bridge users.
5670 - Directory authorities no longer launch a TLS connection to every
5671 relay as they startup. Now that we have 2k+ descriptors cached,
5672 the resulting network hiccup is becoming a burden. Besides,
5673 authorities already avoid voting about Running for the first half
5674 hour of their uptime.
5675 - Directory authorities now log the source of a rejected POSTed v3
5676 networkstatus vote, so we can track failures better.
5677 - Backport code from 0.2.3.x that allows directory authorities to
5678 clean their microdescriptor caches. Needed to resolve bug 2230.
5680 o Minor features (hidden services):
5681 - Use computed circuit-build timeouts to decide when to launch
5682 parallel introduction circuits for hidden services. (Previously,
5683 we would retry after 15 seconds.)
5684 - Don't allow v0 hidden service authorities to act as clients.
5685 Required by fix for bug 3000.
5686 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
5687 by fix for bug 3000.
5688 - Make hidden services work better in private Tor networks by not
5689 requiring any uptime to join the hidden service descriptor
5690 DHT. Implements ticket 2088.
5691 - Log (at info level) when purging pieces of hidden-service-client
5692 state because of SIGNAL NEWNYM.
5694 o Minor features (controller interface):
5695 - New "GETINFO net/listeners/(type)" controller command to return
5696 a list of addresses and ports that are bound for listeners for a
5697 given connection type. This is useful when the user has configured
5698 "SocksPort auto" and the controller needs to know which port got
5699 chosen. Resolves another part of ticket 3076.
5700 - Have the controller interface give a more useful message than
5701 "Internal Error" in response to failed GETINFO requests.
5702 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
5703 event, to give information on the current rate of circuit timeouts
5704 over our stored history.
5705 - The 'EXTENDCIRCUIT' control port command can now be used with
5706 a circ id of 0 and no path. This feature will cause Tor to build
5707 a new 'fast' general purpose circuit using its own path selection
5709 - Added a BUILDTIMEOUT_SET controller event to describe changes
5710 to the circuit build timeout.
5711 - New controller command "getinfo config-text". It returns the
5712 contents that Tor would write if you send it a SAVECONF command,
5713 so the controller can write the file to disk itself.
5715 o Minor features (controller protocol):
5716 - Add a new ControlSocketsGroupWritable configuration option: when
5717 it is turned on, ControlSockets are group-writeable by the default
5718 group of the current user. Patch by Jérémy Bobbio; implements
5720 - Tor now refuses to create a ControlSocket in a directory that is
5721 world-readable (or group-readable if ControlSocketsGroupWritable
5722 is 0). This is necessary because some operating systems do not
5723 enforce permissions on an AF_UNIX sockets. Permissions on the
5724 directory holding the socket, however, seems to work everywhere.
5725 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
5726 not. This would lead to a cookie that is still not group readable.
5727 Closes bug 1843. Suggested by katmagic.
5728 - Future-proof the controller protocol a bit by ignoring keyword
5729 arguments we do not recognize.
5731 o Minor features (more useful logging):
5732 - Revise most log messages that refer to nodes by nickname to
5733 instead use the "$key=nickname at address" format. This should be
5734 more useful, especially since nicknames are less and less likely
5735 to be unique. Resolves ticket 3045.
5736 - When an HTTPS proxy reports "403 Forbidden", we now explain
5737 what it means rather than calling it an unexpected status code.
5738 Closes bug 2503. Patch from Michael Yakubovich.
5739 - Rate-limit a warning about failures to download v2 networkstatus
5740 documents. Resolves part of bug 1352.
5741 - Rate-limit the "your application is giving Tor only an IP address"
5742 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
5743 - Rate-limit "Failed to hand off onionskin" warnings.
5744 - When logging a rate-limited warning, we now mention how many messages
5745 got suppressed since the last warning.
5746 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
5747 2 no signature, 4 required" messages about consensus signatures
5748 easier to read, and make sure they get logged at the same severity
5749 as the messages explaining which keys are which. Fixes bug 1290.
5750 - Don't warn when we have a consensus that we can't verify because
5751 of missing certificates, unless those certificates are ones
5752 that we have been trying and failing to download. Fixes bug 1145.
5754 o Minor features (log domains):
5755 - Add documentation for configuring logging at different severities in
5756 different log domains. We've had this feature since 0.2.1.1-alpha,
5757 but for some reason it never made it into the manpage. Fixes
5759 - Make it simpler to specify "All log domains except for A and B".
5760 Previously you needed to say "[*,~A,~B]". Now you can just say
5762 - Add a "LogMessageDomains 1" option to include the domains of log
5763 messages along with the messages. Without this, there's no way
5764 to use log domains without reading the source or doing a lot
5766 - Add a new "Handshake" log domain for activities that happen
5767 during the TLS handshake.
5769 o Minor features (build process):
5770 - Make compilation with clang possible when using
5771 "--enable-gcc-warnings" by removing two warning options that clang
5772 hasn't implemented yet and by fixing a few warnings. Resolves
5774 - Detect platforms that brokenly use a signed size_t, and refuse to
5775 build there. Found and analyzed by doorss and rransom.
5776 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
5778 - Add support for statically linking zlib by specifying
5779 "--enable-static-zlib", to go with our support for statically
5780 linking openssl and libevent. Resolves bug 1358.
5781 - Instead of adding the svn revision to the Tor version string, report
5782 the git commit (when we're building from a git checkout).
5783 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
5785 - New --digests command-line switch to output the digests of the
5786 source files Tor was built with.
5787 - Generate our manpage and HTML documentation using Asciidoc. This
5788 change should make it easier to maintain the documentation, and
5789 produce nicer HTML. The build process fails if asciidoc cannot
5790 be found and building with asciidoc isn't disabled (via the
5791 "--disable-asciidoc" argument to ./configure. Skipping the manpage
5792 speeds up the build considerably.
5794 o Minor features (options / torrc):
5795 - Warn when the same option is provided more than once in a torrc
5796 file, on the command line, or in a single SETCONF statement, and
5797 the option is one that only accepts a single line. Closes bug 1384.
5798 - Warn when the user configures two HiddenServiceDir lines that point
5799 to the same directory. Bugfix on 0.0.6 (the version introducing
5800 HiddenServiceDir); fixes bug 3289.
5801 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
5802 do individual connection-level rate limiting of clients. The torrc
5803 config options with the same names trump the consensus params, if
5804 both are present. Replaces the old "bwconnrate" and "bwconnburst"
5805 consensus params which were broken from 0.2.2.7-alpha through
5806 0.2.2.14-alpha. Closes bug 1947.
5807 - New config option "WarnUnsafeSocks 0" disables the warning that
5808 occurs whenever Tor receives a socks handshake using a version of
5809 the socks protocol that can only provide an IP address (rather
5810 than a hostname). Setups that do DNS locally over Tor are fine,
5811 and we shouldn't spam the logs in that case.
5812 - New config option "CircuitStreamTimeout" to override our internal
5813 timeout schedule for how many seconds until we detach a stream from
5814 a circuit and try a new circuit. If your network is particularly
5815 slow, you might want to set this to a number like 60.
5816 - New options for SafeLogging to allow scrubbing only log messages
5817 generated while acting as a relay. Specify "SafeLogging relay" if
5818 you want to ensure that only messages known to originate from
5819 client use of the Tor process will be logged unsafely.
5820 - Time and memory units in the configuration file can now be set to
5821 fractional units. For example, "2.5 GB" is now a valid value for
5823 - Support line continuations in the torrc config file. If a line
5824 ends with a single backslash character, the newline is ignored, and
5825 the configuration value is treated as continuing on the next line.
5828 o Minor features (unit tests):
5829 - Revise our unit tests to use the "tinytest" framework, so we
5830 can run tests in their own processes, have smarter setup/teardown
5831 code, and so on. The unit test code has moved to its own
5832 subdirectory, and has been split into multiple modules.
5833 - Add a unit test for cross-platform directory-listing code.
5834 - Add some forgotten return value checks during unit tests. Found
5836 - Use GetTempDir to find the proper temporary directory location on
5837 Windows when generating temporary files for the unit tests. Patch
5840 o Minor features (misc):
5841 - The "torify" script now uses torsocks where available.
5842 - Make Libevent log messages get delivered to controllers later,
5843 and not from inside the Libevent log handler. This prevents unsafe
5844 reentrant Libevent calls while still letting the log messages
5846 - Certain Tor clients (such as those behind check.torproject.org) may
5847 want to fetch the consensus in an extra early manner. To enable this
5848 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
5849 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
5850 as only certain clients who must have this information sooner should
5852 - Expand homedirs passed to tor-checkkey. This should silence a
5853 coverity complaint about passing a user-supplied string into
5854 open() without checking it.
5855 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
5856 used on bridges, and it makes bridge scanning somewhat easier.
5857 - Create the /var/run/tor directory on startup on OpenSUSE if it is
5858 not already created. Patch from Andreas Stieger. Fixes bug 2573.
5860 o Minor bugfixes (relays):
5861 - When a relay decides that its DNS is too broken for it to serve
5862 as an exit server, it advertised itself as a non-exit, but
5863 continued to act as an exit. This could create accidental
5864 partitioning opportunities for users. Instead, if a relay is
5865 going to advertise reject *:* as its exit policy, it should
5866 really act with exit policy "reject *:*". Fixes bug 2366.
5867 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
5868 - Publish a router descriptor even if generating an extra-info
5869 descriptor fails. Previously we would not publish a router
5870 descriptor without an extra-info descriptor; this can cause fast
5871 exit relays collecting exit-port statistics to drop from the
5872 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
5873 - When we're trying to guess whether we know our IP address as
5874 a relay, we would log various ways that we failed to guess
5875 our address, but never log that we ended up guessing it
5876 successfully. Now add a log line to help confused and anxious
5877 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
5878 - For bandwidth accounting, calculate our expected bandwidth rate
5879 based on the time during which we were active and not in
5880 soft-hibernation during the last interval. Previously, we were
5881 also considering the time spent in soft-hibernation. If this
5882 was a long time, we would wind up underestimating our bandwidth
5883 by a lot, and skewing our wakeup time towards the start of the
5884 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
5885 - Demote a confusing TLS warning that relay operators might get when
5886 someone tries to talk to their ORPort. It is not the operator's
5887 fault, nor can they do anything about it. Fixes bug 1364; bugfix
5889 - Change "Application request when we're believed to be offline."
5890 notice to "Application request when we haven't used client
5891 functionality lately.", to clarify that it's not an error. Bugfix
5892 on 0.0.9.3; fixes bug 1222.
5894 o Minor bugfixes (bridges):
5895 - When a client starts or stops using bridges, never use a circuit
5896 that was built before the configuration change. This behavior could
5897 put at risk a user who uses bridges to ensure that her traffic
5898 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
5900 - Do not reset the bridge descriptor download status every time we
5901 re-parse our configuration or get a configuration change. Fixes
5902 bug 3019; bugfix on 0.2.0.3-alpha.
5903 - Users couldn't configure a regular relay to be their bridge. It
5904 didn't work because when Tor fetched the bridge descriptor, it found
5905 that it already had it, and didn't realize that the purpose of the
5906 descriptor had changed. Now we replace routers with a purpose other
5907 than bridge with bridge descriptors when fetching them. Bugfix on
5908 0.1.1.9-alpha. Fixes bug 1776.
5909 - In the special case where you configure a public exit relay as your
5910 bridge, Tor would be willing to use that exit relay as the last
5911 hop in your circuit as well. Now we fail that circuit instead.
5912 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
5914 o Minor bugfixes (clients):
5915 - We now ask the other side of a stream (the client or the exit)
5916 for more data on that stream when the amount of queued data on
5917 that stream dips low enough. Previously, we wouldn't ask the
5918 other side for more data until either it sent us more data (which
5919 it wasn't supposed to do if it had exhausted its window!) or we
5920 had completely flushed all our queued data. This flow control fix
5921 should improve throughput. Fixes bug 2756; bugfix on the earliest
5922 released versions of Tor (svn commit r152).
5923 - When a client finds that an origin circuit has run out of 16-bit
5924 stream IDs, we now mark it as unusable for new streams. Previously,
5925 we would try to close the entire circuit. Bugfix on 0.0.6.
5926 - Make it explicit that we don't cannibalize one-hop circuits. This
5927 happens in the wild, but doesn't turn out to be a problem because
5928 we fortunately don't use those circuits. Many thanks to outofwords
5929 for the initial analysis and to swissknife who confirmed that
5930 two-hop circuits are actually created.
5931 - Resolve an edge case in path weighting that could make us misweight
5932 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
5933 - Make the DNSPort option work with libevent 2.x. Don't alter the
5934 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
5936 o Minor bugfixes (directory authorities):
5937 - Make directory authorities more accurate at recording when
5938 relays that have failed several reachability tests became
5939 unreachable, so we can provide more accuracy at assigning Stable,
5940 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
5941 - Directory authorities are now more robust to hops back in time
5942 when calculating router stability. Previously, if a run of uptime
5943 or downtime appeared to be negative, the calculation could give
5944 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
5946 - Directory authorities will now attempt to download consensuses
5947 if their own efforts to make a live consensus have failed. This
5948 change means authorities that restart will fetch a valid
5949 consensus, and it means authorities that didn't agree with the
5950 current consensus will still fetch and serve it if it has enough
5951 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
5952 - Never vote for a server as "Running" if we have a descriptor for
5953 it claiming to be hibernating, and that descriptor was published
5954 more recently than our last contact with the server. Bugfix on
5955 0.2.0.3-alpha; fixes bug 911.
5956 - Directory authorities no longer change their opinion of, or vote on,
5957 whether a router is Running, unless they have themselves been
5958 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
5961 o Minor bugfixes (hidden services):
5962 - Log malformed requests for rendezvous descriptors as protocol
5963 warnings, not warnings. Also, use a more informative log message
5964 in case someone sees it at log level warning without prior
5965 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
5966 - Accept hidden service descriptors if we think we might be a hidden
5967 service directory, regardless of what our consensus says. This
5968 helps robustness, since clients and hidden services can sometimes
5969 have a more up-to-date view of the network consensus than we do,
5970 and if they think that the directory authorities list us a HSDir,
5971 we might actually be one. Related to bug 2732; bugfix on
5973 - Correct the warning displayed when a rendezvous descriptor exceeds
5974 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
5976 - Clients and hidden services now use HSDir-flagged relays for hidden
5977 service descriptor downloads and uploads even if the relays have no
5978 DirPort set and the client has disabled TunnelDirConns. This will
5979 eventually allow us to give the HSDir flag to relays with no
5980 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
5981 - Only limit the lengths of single HS descriptors, even when multiple
5982 HS descriptors are published to an HSDir relay in a single POST
5983 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
5985 o Minor bugfixes (controllers):
5986 - Allow GETINFO fingerprint to return a fingerprint even when
5987 we have not yet built a router descriptor. Fixes bug 3577;
5988 bugfix on 0.2.0.1-alpha.
5989 - Send a SUCCEEDED stream event to the controller when a reverse
5990 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
5991 discovered by katmagic.
5992 - Remove a trailing asterisk from "exit-policy/default" in the
5993 output of the control port command "GETINFO info/names". Bugfix
5995 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
5996 2917. Bugfix on 0.1.1.1-alpha.
5997 - When we restart our relay, we might get a successful connection
5998 from the outside before we've started our reachability tests,
5999 triggering a warning: "ORPort found reachable, but I have no
6000 routerinfo yet. Failing to inform controller of success." This
6001 bug was harmless unless Tor is running under a controller
6002 like Vidalia, in which case the controller would never get a
6003 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
6005 - When a controller changes TrackHostExits, remove mappings for
6006 hosts that should no longer have their exits tracked. Bugfix on
6008 - When a controller changes VirtualAddrNetwork, remove any mappings
6009 for hosts that were automapped to the old network. Bugfix on
6011 - When a controller changes one of the AutomapHosts* options, remove
6012 any mappings for hosts that should no longer be automapped. Bugfix
6014 - Fix an off-by-one error in calculating some controller command
6015 argument lengths. Fortunately, this mistake is harmless since
6016 the controller code does redundant NUL termination too. Found by
6017 boboper. Bugfix on 0.1.1.1-alpha.
6018 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
6019 would return "551 Internal error" rather than "552 Unrecognized key
6020 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
6021 - Don't spam the controller with events when we have no file
6022 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
6023 for log messages was already solved from bug 748.)
6024 - Emit a GUARD DROPPED controller event for a case we missed.
6025 - Ensure DNS requests launched by "RESOLVE" commands from the
6026 controller respect the __LeaveStreamsUnattached setconf options. The
6027 same goes for requests launched via DNSPort or transparent
6028 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
6030 o Minor bugfixes (config options):
6031 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
6032 Change the limit to 512 characters by removing base64 newlines.
6033 Fixes bug 2752. Fix by Michael Yakubovich.
6034 - Complain if PublishServerDescriptor is given multiple arguments that
6035 include 0 or 1. This configuration will be rejected in the future.
6036 Bugfix on 0.2.0.1-alpha; closes bug 1107.
6037 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
6038 Bugfix on 0.2.0.13-alpha; closes bug 928.
6040 o Minor bugfixes (log subsystem fixes):
6041 - When unable to format an address as a string, report its value
6042 as "???" rather than reusing the last formatted address. Bugfix
6044 - Be more consistent in our treatment of file system paths. "~" should
6045 get expanded to the user's home directory in the Log config option.
6046 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
6047 feature for the -f and --DataDirectory options.
6049 o Minor bugfixes (memory management):
6050 - Don't stack-allocate the list of supplementary GIDs when we're
6051 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
6052 could take up to 256K, which is way too much stack. Found by
6053 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
6054 - Save a couple bytes in memory allocation every time we escape
6055 certain characters in a string. Patch from Florian Zumbiehl.
6057 o Minor bugfixes (protocol correctness):
6058 - When checking for 1024-bit keys, check for 1024 bits, not 128
6059 bytes. This allows Tor to correctly discard keys of length 1017
6060 through 1023. Bugfix on 0.0.9pre5.
6061 - Require that introduction point keys and onion handshake keys
6062 have a public exponent of 65537. Starts to fix bug 3207; bugfix
6064 - Handle SOCKS messages longer than 128 bytes long correctly, rather
6065 than waiting forever for them to finish. Fixes bug 2330; bugfix
6066 on 0.2.0.16-alpha. Found by doorss.
6067 - Never relay a cell for a circuit we have already destroyed.
6068 Between marking a circuit as closeable and finally closing it,
6069 it may have been possible for a few queued cells to get relayed,
6070 even though they would have been immediately dropped by the next
6071 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
6072 - Never queue a cell for a circuit that's already been marked
6074 - Fix a spec conformance issue: the network-status-version token
6075 must be the first token in a v3 consensus or vote. Discovered by
6076 "parakeep". Bugfix on 0.2.0.3-alpha.
6077 - A networkstatus vote must contain exactly one signature. Spec
6078 conformance issue. Bugfix on 0.2.0.3-alpha.
6079 - When asked about a DNS record type we don't support via a
6080 client DNSPort, reply with NOTIMPL rather than an empty
6081 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
6082 - Make more fields in the controller protocol case-insensitive, since
6083 control-spec.txt said they were.
6085 o Minor bugfixes (log messages):
6086 - Fix a log message that said "bits" while displaying a value in
6087 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
6089 - Downgrade "no current certificates known for authority" message from
6090 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
6091 - Correctly describe errors that occur when generating a TLS object.
6092 Previously we would attribute them to a failure while generating a
6093 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
6095 - Fix an instance where a Tor directory mirror might accidentally
6096 log the IP address of a misbehaving Tor client. Bugfix on
6098 - Stop logging at severity 'warn' when some other Tor client tries
6099 to establish a circuit with us using weak DH keys. It's a protocol
6100 violation, but that doesn't mean ordinary users need to hear about
6101 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
6102 - If your relay can't keep up with the number of incoming create
6103 cells, it would log one warning per failure into your logs. Limit
6104 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
6106 o Minor bugfixes (build fixes):
6107 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
6108 - When warning about missing zlib development packages during compile,
6109 give the correct package names. Bugfix on 0.2.0.1-alpha.
6110 - Fix warnings that newer versions of autoconf produce during
6111 ./autogen.sh. These warnings appear to be harmless in our case,
6112 but they were extremely verbose. Fixes bug 2020.
6113 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
6116 o Minor bugfixes (portability):
6117 - Write several files in text mode, on OSes that distinguish text
6118 mode from binary mode (namely, Windows). These files are:
6119 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
6120 that collect those statistics; 'client_keys' and 'hostname' for
6121 hidden services that use authentication; and (in the tor-gencert
6122 utility) newly generated identity and signing keys. Previously,
6123 we wouldn't specify text mode or binary mode, leading to an
6124 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
6125 the DirRecordUsageByCountry option which would have triggered
6126 the assertion failure was added), although this assertion failure
6127 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
6128 - Selectively disable deprecation warnings on OS X because Lion
6129 started deprecating the shipped copy of openssl. Fixes bug 3643.
6130 - Use a wide type to hold sockets when built for 64-bit Windows.
6132 - Fix an issue that prevented static linking of libevent on
6133 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
6134 where we introduced the "--with-static-libevent" configure option.
6135 - Fix a bug with our locking implementation on Windows that couldn't
6136 correctly detect when a file was already locked. Fixes bug 2504,
6137 bugfix on 0.2.1.6-alpha.
6138 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
6140 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
6141 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
6144 o Minor bugfixes (code correctness):
6145 - Always NUL-terminate the sun_path field of a sockaddr_un before
6146 passing it to the kernel. (Not a security issue: kernels are
6147 smart enough to reject bad sockaddr_uns.) Found by Coverity;
6148 CID #428. Bugfix on Tor 0.2.0.3-alpha.
6149 - Make connection_printf_to_buf()'s behavior sane. Its callers
6150 expect it to emit a CRLF iff the format string ends with CRLF;
6151 it actually emitted a CRLF iff (a) the format string ended with
6152 CRLF or (b) the resulting string was over 1023 characters long or
6153 (c) the format string did not end with CRLF *and* the resulting
6154 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
6155 fixes part of bug 3407.
6156 - Make send_control_event_impl()'s behavior sane. Its callers
6157 expect it to always emit a CRLF at the end of the string; it
6158 might have emitted extra control characters as well. Bugfix on
6159 0.1.1.9-alpha; fixes another part of bug 3407.
6160 - Make crypto_rand_int() check the value of its input correctly.
6161 Previously, it accepted values up to UINT_MAX, but could return a
6162 negative number if given a value above INT_MAX+1. Found by George
6163 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
6164 - Fix a potential null-pointer dereference while computing a
6165 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
6167 - If we fail to compute the identity digest of a v3 legacy keypair,
6168 warn, and don't use a buffer-full of junk instead. Bugfix on
6169 0.2.1.1-alpha; fixes bug 3106.
6170 - Resolve an untriggerable issue in smartlist_string_num_isin(),
6171 where if the function had ever in the future been used to check
6172 for the presence of a too-large number, it would have given an
6173 incorrect result. (Fortunately, we only used it for 16-bit
6174 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
6175 - Be more careful about reporting the correct error from a failed
6176 connect() system call. Under some circumstances, it was possible to
6177 look at an incorrect value for errno when sending the end reason.
6178 Bugfix on 0.1.0.1-rc.
6179 - Correctly handle an "impossible" overflow cases in connection byte
6180 counting, where we write or read more than 4GB on an edge connection
6181 in a single second. Bugfix on 0.1.2.8-beta.
6182 - Avoid a double mark-for-free warning when failing to attach a
6183 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
6185 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
6186 found by "cypherpunks". This bug was introduced before the first
6187 Tor release, in svn commit r110.
6188 - Fix a bug in bandwidth history state parsing that could have been
6189 triggered if a future version of Tor ever changed the timing
6190 granularity at which bandwidth history is measured. Bugfix on
6192 - Add assertions to check for overflow in arguments to
6193 base32_encode() and base32_decode(); fix a signed-unsigned
6194 comparison there too. These bugs are not actually reachable in Tor,
6195 but it's good to prevent future errors too. Found by doorss.
6196 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
6198 - Set target port in get_interface_address6() correctly. Bugfix
6199 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
6200 - Fix an impossible-to-actually-trigger buffer overflow in relay
6201 descriptor generation. Bugfix on 0.1.0.15.
6202 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
6204 o Minor bugfixes (code improvements):
6205 - After we free an internal connection structure, overwrite it
6206 with a different memory value than we use for overwriting a freed
6207 internal circuit structure. Should help with debugging. Suggested
6209 - If OpenSSL fails to make a duplicate of a private or public key, log
6210 an error message and try to exit cleanly. May help with debugging
6211 if bug 1209 ever remanifests.
6212 - Some options used different conventions for uppercasing of acronyms
6213 when comparing manpage and source. Fix those in favor of the
6214 manpage, as it makes sense to capitalize acronyms.
6215 - Take a first step towards making or.h smaller by splitting out
6216 function definitions for all source files in src/or/. Leave
6217 structures and defines in or.h for now.
6218 - Remove a few dead assignments during router parsing. Found by
6220 - Don't use 1-bit wide signed bit fields. Found by coverity.
6221 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
6222 None of the cases where we did this before were wrong, but by making
6223 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
6224 - The memarea code now uses a sentinel value at the end of each area
6225 to make sure nothing writes beyond the end of an area. This might
6226 help debug some conceivable causes of bug 930.
6227 - Always treat failure to allocate an RSA key as an unrecoverable
6229 - Add some more defensive programming for architectures that can't
6230 handle unaligned integer accesses. We don't know of any actual bugs
6231 right now, but that's the best time to fix them. Fixes bug 1943.
6233 o Minor bugfixes (misc):
6234 - Fix a rare bug in rend_fn unit tests: we would fail a test when
6235 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
6236 on 0.2.0.10-alpha; fixes bug 1808.
6237 - Where available, use Libevent 2.0's periodic timers so that our
6238 once-per-second cleanup code gets called even more closely to
6239 once per second than it would otherwise. Fixes bug 943.
6240 - Ignore OutboundBindAddress when connecting to localhost.
6241 Connections to localhost need to come _from_ localhost, or else
6242 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
6244 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
6246 - If any of the v3 certs we download are unparseable, we should
6247 actually notice the failure so we don't retry indefinitely. Bugfix
6248 on 0.2.0.x; reported by "rotator".
6249 - When Tor fails to parse a descriptor of any kind, dump it to disk.
6250 Might help diagnosing bug 1051.
6251 - Make our 'torify' script more portable; if we have only one of
6252 'torsocks' or 'tsocks' installed, don't complain to the user;
6253 and explain our warning about tsocks better.
6254 - Fix some urls in the exit notice file and make it XHTML1.1 strict
6255 compliant. Based on a patch from Christian Kujau.
6257 o Documentation changes:
6258 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
6259 - Resolve all doxygen warnings except those for missing documentation.
6261 - Add doxygen documentation for more functions, fields, and types.
6262 - Convert the HACKING file to asciidoc, and add a few new sections
6263 to it, explaining how we use Git, how we make changelogs, and
6264 what should go in a patch.
6265 - Document the default socks host and port (127.0.0.1:9050) for
6267 - Removed some unnecessary files from the source distribution. The
6268 AUTHORS file has now been merged into the people page on the
6269 website. The roadmaps and design doc can now be found in the
6270 projects directory in svn.
6272 o Deprecated and removed features (config):
6273 - Remove the torrc.complete file. It hasn't been kept up to date
6274 and users will have better luck checking out the manpage.
6275 - Remove the HSAuthorityRecordStats option that version 0 hidden
6276 service authorities could use to track statistics of overall v0
6277 hidden service usage.
6278 - Remove the obsolete "NoPublish" option; it has been flagged
6279 as obsolete and has produced a warning since 0.1.1.18-rc.
6280 - Caches no longer download and serve v2 networkstatus documents
6281 unless FetchV2Networkstatus flag is set: these documents haven't
6282 haven't been used by clients or relays since 0.2.0.x. Resolves
6285 o Deprecated and removed features (controller):
6286 - The controller no longer accepts the old obsolete "addr-mappings/"
6287 or "unregistered-servers-" GETINFO values.
6288 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
6289 always on; using them is necessary for correct forward-compatible
6292 o Deprecated and removed features (misc):
6293 - Hidden services no longer publish version 0 descriptors, and clients
6294 do not request or use version 0 descriptors. However, the old hidden
6295 service authorities still accept and serve version 0 descriptors
6296 when contacted by older hidden services/clients.
6297 - Remove undocumented option "-F" from tor-resolve: it hasn't done
6298 anything since 0.2.1.16-rc.
6299 - Remove everything related to building the expert bundle for OS X.
6300 It has confused many users, doesn't work right on OS X 10.6,
6301 and is hard to get rid of once installed. Resolves bug 1274.
6302 - Remove support for .noconnect style addresses. Nobody was using
6303 them, and they provided another avenue for detecting Tor users
6304 via application-level web tricks.
6305 - When we fixed bug 1038 we had to put in a restriction not to send
6306 RELAY_EARLY cells on rend circuits. This was necessary as long
6307 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
6308 active. Now remove this obsolete check. Resolves bug 2081.
6309 - Remove workaround code to handle directory responses from servers
6310 that had bug 539 (they would send HTTP status 503 responses _and_
6311 send a body too). Since only server versions before
6312 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
6313 keep the workaround in place.
6314 - Remove the old 'fuzzy time' logic. It was supposed to be used for
6315 handling calculations where we have a known amount of clock skew and
6316 an allowed amount of unknown skew. But we only used it in three
6317 places, and we never adjusted the known/unknown skew values. This is
6318 still something we might want to do someday, but if we do, we'll
6319 want to do it differently.
6320 - Remove the "--enable-iphone" option to ./configure. According to
6321 reports from Marco Bonetti, Tor builds fine without any special
6322 tweaking on recent iPhone SDK versions.
6325 Changes in version 0.2.1.30 - 2011-02-23
6326 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
6327 change is a slight tweak to Tor's TLS handshake that makes relays
6328 and bridges that run this new version reachable from Iran again.
6329 We don't expect this tweak will win the arms race long-term, but it
6330 buys us time until we roll out a better solution.
6333 - Stop sending a CLOCK_SKEW controller status event whenever
6334 we fetch directory information from a relay that has a wrong clock.
6335 Instead, only inform the controller when it's a trusted authority
6336 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
6337 the rest of bug 1074.
6338 - Fix a bounds-checking error that could allow an attacker to
6339 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
6341 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
6342 Tor would ignore their RelayBandwidthBurst setting,
6343 potentially using more bandwidth than expected. Bugfix on
6344 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
6345 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
6346 hidserv" in her torrc. The 'hidserv' argument never controlled
6347 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
6350 - Adjust our TLS Diffie-Hellman parameters to match those used by
6352 - Update to the February 1 2011 Maxmind GeoLite Country database.
6355 - Check for and reject overly long directory certificates and
6356 directory tokens before they have a chance to hit any assertions.
6357 Bugfix on 0.2.1.28. Found by "doorss".
6358 - Bring the logic that gathers routerinfos and assesses the
6359 acceptability of circuits into line. This prevents a Tor OP from
6360 getting locked in a cycle of choosing its local OR as an exit for a
6361 path (due to a .exit request) and then rejecting the circuit because
6362 its OR is not listed yet. It also prevents Tor clients from using an
6363 OR running in the same instance as an exit (due to a .exit request)
6364 if the OR does not meet the same requirements expected of an OR
6365 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
6367 o Packaging changes:
6368 - Stop shipping the Tor specs files and development proposal documents
6369 in the tarball. They are now in a separate git repository at
6370 git://git.torproject.org/torspec.git
6371 - Do not include Git version tags as though they are SVN tags when
6372 generating a tarball from inside a repository that has switched
6373 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
6376 Changes in version 0.2.1.29 - 2011-01-15
6377 Tor 0.2.1.29 continues our recent code security audit work. The main
6378 fix resolves a remote heap overflow vulnerability that can allow remote
6379 code execution. Other fixes address a variety of assert and crash bugs,
6380 most of which we think are hard to exploit remotely.
6382 o Major bugfixes (security):
6383 - Fix a heap overflow bug where an adversary could cause heap
6384 corruption. This bug probably allows remote code execution
6385 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
6387 - Prevent a denial-of-service attack by disallowing any
6388 zlib-compressed data whose compression factor is implausibly
6389 high. Fixes part of bug 2324; reported by "doorss".
6390 - Zero out a few more keys in memory before freeing them. Fixes
6391 bug 2384 and part of bug 2385. These key instances found by
6392 "cypherpunks", based on Andrew Case's report about being able
6393 to find sensitive data in Tor's memory space if you have enough
6394 permissions. Bugfix on 0.0.2pre9.
6396 o Major bugfixes (crashes):
6397 - Prevent calls to Libevent from inside Libevent log handlers.
6398 This had potential to cause a nasty set of crashes, especially
6399 if running Libevent with debug logging enabled, and running
6400 Tor with a controller watching for low-severity log messages.
6401 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
6402 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
6403 underflow errors there too. Fixes the other part of bug 2324.
6404 - Fix a bug where we would assert if we ever had a
6405 cached-descriptors.new file (or another file read directly into
6406 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
6407 on 0.2.1.25. Found by doorss.
6408 - Fix some potential asserts and parsing issues with grossly
6409 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
6412 o Minor bugfixes (other):
6413 - Fix a bug with handling misformed replies to reverse DNS lookup
6414 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
6415 bug reported by doorss.
6416 - Fix compilation on mingw when a pthreads compatibility library
6417 has been installed. (We don't want to use it, so we shouldn't
6418 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
6419 - Fix a bug where we would declare that we had run out of virtual
6420 addresses when the address space was only half-exhausted. Bugfix
6422 - Correctly handle the case where AutomapHostsOnResolve is set but
6423 no virtual addresses are available. Fixes bug 2328; bugfix on
6424 0.1.2.1-alpha. Bug found by doorss.
6425 - Correctly handle wrapping around when we run out of virtual
6426 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
6429 - Update to the January 1 2011 Maxmind GeoLite Country database.
6430 - Introduce output size checks on all of our decryption functions.
6433 - Tor does not build packages correctly with Automake 1.6 and earlier;
6434 added a check to Makefile.am to make sure that we're building with
6435 Automake 1.7 or later.
6436 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
6437 because we built it with a too-old version of automake. Thus that
6438 release broke ./configure --enable-openbsd-malloc, which is popular
6439 among really fast exit relays on Linux.
6442 Changes in version 0.2.1.28 - 2010-12-17
6443 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
6444 exploitable bugs. We also took this opportunity to change the IP address
6445 for one of our directory authorities, and to update the geoip database
6449 - Fix a remotely exploitable bug that could be used to crash instances
6450 of Tor remotely by overflowing on the heap. Remote-code execution
6451 hasn't been confirmed, but can't be ruled out. Everyone should
6452 upgrade. Bugfix on the 0.1.1 series and later.
6454 o Directory authority changes:
6455 - Change IP address and ports for gabelmoo (v3 directory authority).
6458 - Update to the December 1 2010 Maxmind GeoLite Country database.
6461 Changes in version 0.2.1.27 - 2010-11-23
6462 Yet another OpenSSL security patch broke its compatibility with Tor:
6463 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
6464 also took this opportunity to fix several crash bugs, integrate a new
6465 directory authority, and update the bundled GeoIP database.
6468 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
6469 No longer set the tlsext_host_name extension on server SSL objects;
6470 but continue to set it on client SSL objects. Our goal in setting
6471 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
6472 bugfix on 0.2.1.1-alpha.
6473 - Do not log messages to the controller while shrinking buffer
6474 freelists. Doing so would sometimes make the controller connection
6475 try to allocate a buffer chunk, which would mess up the internals
6476 of the freelist and cause an assertion failure. Fixes bug 1125;
6477 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
6478 - Learn our external IP address when we're a relay or bridge, even if
6479 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
6480 where we introduced bridge relays that don't need to publish to
6481 be useful. Fixes bug 2050.
6482 - Do even more to reject (and not just ignore) annotations on
6483 router descriptors received anywhere but from the cache. Previously
6484 we would ignore such annotations at first, but cache them to disk
6485 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
6486 - When you're using bridges and your network goes away and your
6487 bridges get marked as down, recover when you attempt a new socks
6488 connection (if the network is back), rather than waiting up to an
6489 hour to try fetching new descriptors for your bridges. Bugfix on
6490 0.2.0.3-alpha; fixes bug 1981.
6493 - Move to the November 2010 Maxmind GeoLite country db (rather
6494 than the June 2009 ip-to-country GeoIP db) for our statistics that
6495 count how many users relays are seeing from each country. Now we'll
6496 have more accurate data, especially for many African countries.
6498 o New directory authorities:
6499 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
6503 - Fix an assertion failure that could occur in directory caches or
6504 bridge users when using a very short voting interval on a testing
6505 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
6507 - Enforce multiplicity rules when parsing annotations. Bugfix on
6508 0.2.0.8-alpha. Found by piebeer.
6509 - Allow handshaking OR connections to take a full KeepalivePeriod
6510 seconds to handshake. Previously, we would close them after
6511 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
6512 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
6514 - When building with --enable-gcc-warnings on OpenBSD, disable
6515 warnings in system headers. This makes --enable-gcc-warnings
6516 pass on OpenBSD 4.8.
6519 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
6520 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
6521 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
6522 Servers can start sending this code when enough clients recognize
6523 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
6524 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
6525 Patch from mingw-san.
6528 - Remove the old debian/ directory from the main Tor distribution.
6529 The official Tor-for-debian git repository lives at the URL
6530 https://git.torproject.org/debian/tor.git
6531 - Stop shipping the old doc/website/ directory in the tarball. We
6532 changed the website format in late 2010, and what we shipped in
6533 0.2.1.26 really wasn't that useful anyway.
6536 Changes in version 0.2.1.26 - 2010-05-02
6537 Tor 0.2.1.26 addresses the recent connection and memory overload
6538 problems we've been seeing on relays, especially relays with their
6539 DirPort open. If your relay has been crashing, or you turned it off
6540 because it used too many resources, give this release a try.
6542 This release also fixes yet another instance of broken OpenSSL libraries
6543 that was causing some relays to drop out of the consensus.
6546 - Teach relays to defend themselves from connection overload. Relays
6547 now close idle circuits early if it looks like they were intended
6548 for directory fetches. Relays are also more aggressive about closing
6549 TLS connections that have no circuits on them. Such circuits are
6550 unlikely to be re-used, and tens of thousands of them were piling
6551 up at the fast relays, causing the relays to run out of sockets
6552 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6553 their directory fetches over TLS).
6554 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6555 that claim to be earlier than 0.9.8m, but which have in reality
6556 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6557 behavior. Possible fix for some cases of bug 1346.
6558 - Directory mirrors were fetching relay descriptors only from v2
6559 directory authorities, rather than v3 authorities like they should.
6560 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6561 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6564 - Finally get rid of the deprecated and now harmful notion of "clique
6565 mode", where directory authorities maintain TLS connections to
6569 - In the util/threads test, no longer free the test_mutex before all
6570 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6571 - The master thread could starve the worker threads quite badly on
6572 certain systems, causing them to run only partially in the allowed
6573 window. This resulted in test failures. Now the master thread sleeps
6574 occasionally for a few microseconds while the two worker-threads
6575 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6578 Changes in version 0.2.1.25 - 2010-03-16
6579 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
6580 prevent relays from guessing their IP address correctly. It also fixes
6581 several minor potential security bugs.
6584 - Fix a regression from our patch for bug 1244 that caused relays
6585 to guess their IP address incorrectly if they didn't set Address
6586 in their torrc and/or their address fails to resolve. Bugfix on
6587 0.2.1.23; fixes bug 1269.
6588 - When freeing a session key, zero it out completely. We only zeroed
6589 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6590 patched by ekir. Fixes bug 1254.
6593 - Fix a dereference-then-NULL-check sequence when publishing
6594 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6596 - Fix another dereference-then-NULL-check sequence. Bugfix on
6597 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6598 - Make sure we treat potentially not NUL-terminated strings correctly.
6599 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6602 Changes in version 0.2.1.24 - 2010-02-21
6603 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
6607 - Work correctly out-of-the-box with even more vendor-patched versions
6608 of OpenSSL. In particular, make it so Debian and OS X don't need
6609 customized patches to run/build.
6612 Changes in version 0.2.1.23 - 2010-02-13
6613 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
6614 again on the latest OS X, and updates the location of a directory
6617 o Major bugfixes (performance):
6618 - We were selecting our guards uniformly at random, and then weighting
6619 which of our guards we'd use uniformly at random. This imbalance
6620 meant that Tor clients were severely limited on throughput (and
6621 probably latency too) by the first hop in their circuit. Now we
6622 select guards weighted by currently advertised bandwidth. We also
6623 automatically discard guards picked using the old algorithm. Fixes
6624 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6627 - Make Tor work again on the latest OS X: when deciding whether to
6628 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6629 version at run-time, not compile time. We need to do this because
6630 Apple doesn't update its dev-tools headers when it updates its
6631 libraries in a security patch.
6632 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6633 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6634 a memory leak when requesting a hidden service descriptor we've
6635 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6639 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6640 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6643 - Avoid a mad rush at the beginning of each month when each client
6644 rotates half of its guards. Instead we spread the rotation out
6645 throughout the month, but we still avoid leaving a precise timestamp
6646 in the state file about when we first picked the guard. Improves
6647 over the behavior introduced in 0.1.2.17.
6650 Changes in version 0.2.1.22 - 2010-01-19
6651 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
6652 authorities -- it would tell you its whole history of bridge descriptors
6653 if you make the right directory request. This stable update also
6654 rotates two of the seven v3 directory authority keys and locations.
6656 o Directory authority changes:
6657 - Rotate keys (both v3 identity and relay identity) for moria1
6661 - Stop bridge directory authorities from answering dbg-stability.txt
6662 directory queries, which would let people fetch a list of all
6663 bridge identities they track. Bugfix on 0.2.1.6-alpha.
6666 Changes in version 0.2.1.21 - 2009-12-21
6667 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
6668 library. If you use Tor on Linux / Unix and you're getting SSL
6669 renegotiation errors, upgrading should help. We also recommend an
6670 upgrade if you're an exit relay.
6673 - Work around a security feature in OpenSSL 0.9.8l that prevents our
6674 handshake from working unless we explicitly tell OpenSSL that we
6675 are using SSL renegotiation safely. We are, of course, but OpenSSL
6676 0.9.8l won't work unless we say we are.
6677 - Avoid crashing if the client is trying to upload many bytes and the
6678 circuit gets torn down at the same time, or if the flip side
6679 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
6682 - Do not refuse to learn about authority certs and v2 networkstatus
6683 documents that are older than the latest consensus. This bug might
6684 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
6685 Spotted and fixed by xmux.
6686 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
6687 trigger platform-specific option misparsing case found by Coverity
6689 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
6690 trigger assert. Fixes bug 1173.
6693 Changes in version 0.2.1.20 - 2009-10-15
6694 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
6695 services at once, prepares for more performance improvements, and
6696 fixes a bunch of smaller bugs.
6698 The Windows and OS X bundles also include a more recent Vidalia,
6699 and switch from Privoxy to Polipo.
6701 The OS X installers are now drag and drop. It's best to un-install
6702 Tor/Vidalia and then install this new bundle, rather than upgrade. If
6703 you want to upgrade, you'll need to update the paths for Tor and Polipo
6704 in the Vidalia Settings window.
6707 - Send circuit or stream sendme cells when our window has decreased
6708 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
6709 by Karsten when testing the "reduce circuit window" performance
6710 patch. Bugfix on the 54th commit on Tor -- from July 2002,
6711 before the release of Tor 0.0.0. This is the new winner of the
6713 - Fix a remotely triggerable memory leak when a consensus document
6714 contains more than one signature from the same voter. Bugfix on
6716 - Avoid segfault in rare cases when finishing an introduction circuit
6717 as a client and finding out that we don't have an introduction key
6718 for it. Fixes bug 1073. Reported by Aaron Swartz.
6721 - Tor now reads the "circwindow" parameter out of the consensus,
6722 and uses that value for its circuit package window rather than the
6723 default of 1000 cells. Begins the implementation of proposal 168.
6725 o New directory authorities:
6726 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
6728 - Move moria1 and tonga to alternate IP addresses.
6731 - Fix a signed/unsigned compile warning in 0.2.1.19.
6732 - Fix possible segmentation fault on directory authorities. Bugfix on
6734 - Fix an extremely rare infinite recursion bug that could occur if
6735 we tried to log a message after shutting down the log subsystem.
6736 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
6737 - Fix an obscure bug where hidden services on 64-bit big-endian
6738 systems might mis-read the timestamp in v3 introduce cells, and
6739 refuse to connect back to the client. Discovered by "rotor".
6740 Bugfix on 0.2.1.6-alpha.
6741 - We were triggering a CLOCK_SKEW controller status event whenever
6742 we connect via the v2 connection protocol to any relay that has
6743 a wrong clock. Instead, we should only inform the controller when
6744 it's a trusted authority that claims our clock is wrong. Bugfix
6745 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
6746 - We were telling the controller about CHECKING_REACHABILITY and
6747 REACHABILITY_FAILED status events whenever we launch a testing
6748 circuit or notice that one has failed. Instead, only tell the
6749 controller when we want to inform the user of overall success or
6750 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
6752 - Don't warn when we're using a circuit that ends with a node
6753 excluded in ExcludeExitNodes, but the circuit is not used to access
6754 the outside world. This should help fix bug 1090. Bugfix on
6756 - Work around a small memory leak in some versions of OpenSSL that
6757 stopped the memory used by the hostname TLS extension from being
6761 - Add a "getinfo status/accepted-server-descriptor" controller
6762 command, which is the recommended way for controllers to learn
6763 whether our server descriptor has been successfully received by at
6764 least on directory authority. Un-recommend good-server-descriptor
6765 getinfo and status events until we have a better design for them.
6768 Changes in version 0.2.1.19 - 2009-07-28
6769 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
6773 - Make accessing hidden services on 0.2.1.x work right again.
6774 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
6775 part of patch provided by "optimist".
6778 - When a relay/bridge is writing out its identity key fingerprint to
6779 the "fingerprint" file and to its logs, write it without spaces. Now
6780 it will look like the fingerprints in our bridges documentation,
6781 and confuse fewer users.
6784 - Relays no longer publish a new server descriptor if they change
6785 their MaxAdvertisedBandwidth config option but it doesn't end up
6786 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
6787 fixes bug 1026. Patch from Sebastian.
6788 - Avoid leaking memory every time we get a create cell but we have
6789 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
6790 fixes bug 1034. Reported by BarkerJr.
6793 Changes in version 0.2.1.18 - 2009-07-24
6794 Tor 0.2.1.18 lays the foundations for performance improvements,
6795 adds status events to help users diagnose bootstrap problems, adds
6796 optional authentication/authorization for hidden services, fixes a
6797 variety of potential anonymity problems, and includes a huge pile of
6798 other features and bug fixes.
6800 o Major features (clients):
6801 - Start sending "bootstrap phase" status events to the controller,
6802 so it can keep the user informed of progress fetching directory
6803 information and establishing circuits. Also inform the controller
6804 if we think we're stuck at a particular bootstrap phase. Implements
6806 - Clients replace entry guards that were chosen more than a few months
6807 ago. This change should significantly improve client performance,
6808 especially once more people upgrade, since relays that have been
6809 a guard for a long time are currently overloaded.
6810 - Network status consensus documents and votes now contain bandwidth
6811 information for each relay. Clients use the bandwidth values
6812 in the consensus, rather than the bandwidth values in each
6813 relay descriptor. This approach opens the door to more accurate
6814 bandwidth estimates once the directory authorities start doing
6815 active measurements. Implements part of proposal 141.
6817 o Major features (relays):
6818 - Disable and refactor some debugging checks that forced a linear scan
6819 over the whole server-side DNS cache. These accounted for over 50%
6820 of CPU time on a relatively busy exit node's gprof profile. Also,
6821 disable some debugging checks that appeared in exit node profile
6822 data. Found by Jacob.
6823 - New DirPortFrontPage option that takes an html file and publishes
6824 it as "/" on the DirPort. Now relay operators can provide a
6825 disclaimer without needing to set up a separate webserver. There's
6826 a sample disclaimer in contrib/tor-exit-notice.html.
6828 o Major features (hidden services):
6829 - Make it possible to build hidden services that only certain clients
6830 are allowed to connect to. This is enforced at several points,
6831 so that unauthorized clients are unable to send INTRODUCE cells
6832 to the service, or even (depending on the type of authentication)
6833 to learn introduction points. This feature raises the bar for
6834 certain kinds of active attacks against hidden services. Design
6835 and code by Karsten Loesing. Implements proposal 121.
6836 - Relays now store and serve v2 hidden service descriptors by default,
6837 i.e., the new default value for HidServDirectoryV2 is 1. This is
6838 the last step in proposal 114, which aims to make hidden service
6839 lookups more reliable.
6841 o Major features (path selection):
6842 - ExitNodes and Exclude*Nodes config options now allow you to restrict
6843 by country code ("{US}") or IP address or address pattern
6844 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
6845 refinement to decide what config options should take priority if
6846 you ask to both use a particular node and exclude it.
6848 o Major features (misc):
6849 - When building a consensus, do not include routers that are down.
6850 This cuts down 30% to 40% on consensus size. Implements proposal
6852 - New TestingTorNetwork config option to allow adjustment of
6853 previously constant values that could slow bootstrapping. Implements
6854 proposal 135. Patch from Karsten.
6855 - Convert many internal address representations to optionally hold
6856 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
6857 elements. Make resolver code handle nameservers located at IPv6
6859 - More work on making our TLS handshake blend in: modify the list
6860 of ciphers advertised by OpenSSL in client mode to even more
6861 closely resemble a common web browser. We cheat a little so that
6862 we can advertise ciphers that the locally installed OpenSSL doesn't
6864 - Use the TLS1 hostname extension to more closely resemble browser
6867 o Security fixes (anonymity/entropy):
6868 - Never use a connection with a mismatched address to extend a
6869 circuit, unless that connection is canonical. A canonical
6870 connection is one whose address is authenticated by the router's
6871 identity key, either in a NETINFO cell or in a router descriptor.
6872 - Implement most of proposal 110: The first K cells to be sent
6873 along a circuit are marked as special "early" cells; only K "early"
6874 cells will be allowed. Once this code is universal, we can block
6875 certain kinds of denial-of-service attack by requiring that EXTEND
6876 commands must be sent using an "early" cell.
6877 - Resume using OpenSSL's RAND_poll() for better (and more portable)
6878 cross-platform entropy collection again. We used to use it, then
6879 stopped using it because of a bug that could crash systems that
6880 called RAND_poll when they had a lot of fds open. It looks like the
6881 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
6882 at startup, and to call RAND_poll() when we reseed later only if
6883 we have a non-buggy OpenSSL version.
6884 - When the client is choosing entry guards, now it selects at most
6885 one guard from a given relay family. Otherwise we could end up with
6886 all of our entry points into the network run by the same operator.
6887 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
6888 - Do not use or believe expired v3 authority certificates. Patch
6889 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
6890 - Drop begin cells to a hidden service if they come from the middle
6891 of a circuit. Patch from lark.
6892 - When we erroneously receive two EXTEND cells for the same circuit
6893 ID on the same connection, drop the second. Patch from lark.
6894 - Authorities now vote for the Stable flag for any router whose
6895 weighted MTBF is at least 5 days, regardless of the mean MTBF.
6896 - Clients now never report any stream end reason except 'MISC'.
6897 Implements proposal 148.
6899 o Major bugfixes (crashes):
6900 - Parse dates and IPv4 addresses in a locale- and libc-independent
6901 manner, to avoid platform-dependent behavior on malformed input.
6902 - Fix a crash that occurs on exit nodes when a nameserver request
6903 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
6904 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
6906 - Do not assume that a stack-allocated character array will be
6907 64-bit aligned on platforms that demand that uint64_t access is
6908 aligned. Possible fix for bug 604.
6909 - Resolve a very rare crash bug that could occur when the user forced
6910 a nameserver reconfiguration during the middle of a nameserver
6911 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
6912 - Avoid a "0 divided by 0" calculation when calculating router uptime
6913 at directory authorities. Bugfix on 0.2.0.8-alpha.
6914 - Fix an assertion bug in parsing policy-related options; possible fix
6916 - Rate-limit too-many-sockets messages: when they happen, they happen
6917 a lot and end up filling up the disk. Resolves bug 748.
6918 - Fix a race condition that could cause crashes or memory corruption
6919 when running as a server with a controller listening for log
6921 - Avoid crashing when we have a policy specified in a DirPolicy or
6922 SocksPolicy or ReachableAddresses option with ports set on it,
6923 and we re-load the policy. May fix bug 996.
6924 - Fix an assertion failure on 64-bit platforms when we allocated
6925 memory right up to the end of a memarea, then realigned the memory
6926 one step beyond the end. Fixes a possible cause of bug 930.
6927 - Protect the count of open sockets with a mutex, so we can't
6928 corrupt it when two threads are closing or opening sockets at once.
6929 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
6931 o Major bugfixes (clients):
6932 - Discard router descriptors as we load them if they are more than
6933 five days old. Otherwise if Tor is off for a long time and then
6934 starts with cached descriptors, it will try to use the onion keys
6935 in those obsolete descriptors when building circuits. Fixes bug 887.
6936 - When we choose to abandon a new entry guard because we think our
6937 older ones might be better, close any circuits pending on that
6938 new entry guard connection. This fix should make us recover much
6939 faster when our network is down and then comes back. Bugfix on
6940 0.1.2.8-beta; found by lodger.
6941 - When Tor clients restart after 1-5 days, they discard all their
6942 cached descriptors as too old, but they still use the cached
6943 consensus document. This approach is good for robustness, but
6944 bad for performance: since they don't know any bandwidths, they
6945 end up choosing at random rather than weighting their choice by
6946 speed. Fixed by the above feature of putting bandwidths in the
6949 o Major bugfixes (relays):
6950 - Relays were falling out of the networkstatus consensus for
6951 part of a day if they changed their local config but the
6952 authorities discarded their new descriptor as "not sufficiently
6953 different". Now directory authorities accept a descriptor as changed
6954 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
6956 - Ensure that two circuits can never exist on the same connection
6957 with the same circuit ID, even if one is marked for close. This
6958 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
6959 - Directory authorities were neglecting to mark relays down in their
6960 internal histories if the relays fall off the routerlist without
6961 ever being found unreachable. So there were relays in the histories
6962 that haven't been seen for eight months, and are listed as being
6963 up for eight months. This wreaked havoc on the "median wfu" and
6964 "median mtbf" calculations, in turn making Guard and Stable flags
6965 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
6968 o Major bugfixes (hidden services):
6969 - When establishing a hidden service, introduction points that
6970 originate from cannibalized circuits were completely ignored
6971 and not included in rendezvous service descriptors. This might
6972 have been another reason for delay in making a hidden service
6973 available. Bugfix from long ago (0.0.9.x?)
6975 o Major bugfixes (memory and resource management):
6976 - Fixed some memory leaks -- some quite frequent, some almost
6977 impossible to trigger -- based on results from Coverity.
6978 - Speed up parsing and cut down on memory fragmentation by using
6979 stack-style allocations for parsing directory objects. Previously,
6980 this accounted for over 40% of allocations from within Tor's code
6981 on a typical directory cache.
6982 - Use a Bloom filter rather than a digest-based set to track which
6983 descriptors we need to keep around when we're cleaning out old
6984 router descriptors. This speeds up the computation significantly,
6985 and may reduce fragmentation.
6987 o New/changed config options:
6988 - Now NodeFamily and MyFamily config options allow spaces in
6989 identity fingerprints, so it's easier to paste them in.
6990 Suggested by Lucky Green.
6991 - Allow ports 465 and 587 in the default exit policy again. We had
6992 rejected them in 0.1.0.15, because back in 2005 they were commonly
6993 misconfigured and ended up as spam targets. We hear they are better
6994 locked down these days.
6995 - Make TrackHostExit mappings expire a while after their last use, not
6996 after their creation. Patch from Robert Hogan.
6997 - Add an ExcludeExitNodes option so users can list a set of nodes
6998 that should be be excluded from the exit node position, but
6999 allowed elsewhere. Implements proposal 151.
7000 - New --hush command-line option similar to --quiet. While --quiet
7001 disables all logging to the console on startup, --hush limits the
7002 output to messages of warning and error severity.
7003 - New configure/torrc options (--enable-geoip-stats,
7004 DirRecordUsageByCountry) to record how many IPs we've served
7005 directory info to in each country code, how many status documents
7006 total we've sent to each country code, and what share of the total
7007 directory requests we should expect to see.
7008 - Make outbound DNS packets respect the OutboundBindAddress setting.
7009 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
7010 - Allow separate log levels to be configured for different logging
7011 domains. For example, this allows one to log all notices, warnings,
7012 or errors, plus all memory management messages of level debug or
7013 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
7014 - Update to the "June 3 2009" ip-to-country file.
7016 o Minor features (relays):
7017 - Raise the minimum rate limiting to be a relay from 20000 bytes
7018 to 20480 bytes (aka 20KB/s), to match our documentation. Also
7019 update directory authorities so they always assign the Fast flag
7020 to relays with 20KB/s of capacity. Now people running relays won't
7021 suddenly find themselves not seeing any use, if the network gets
7023 - If we're a relay and we change our IP address, be more verbose
7024 about the reason that made us change. Should help track down
7025 further bugs for relays on dynamic IP addresses.
7026 - Exit servers can now answer resolve requests for ip6.arpa addresses.
7027 - Implement most of Proposal 152: allow specialized servers to permit
7028 single-hop circuits, and clients to use those servers to build
7029 single-hop circuits when using a specialized controller. Patch
7030 from Josh Albrecht. Resolves feature request 768.
7031 - When relays do their initial bandwidth measurement, don't limit
7032 to just our entry guards for the test circuits. Otherwise we tend
7033 to have multiple test circuits going through a single entry guard,
7034 which makes our bandwidth test less accurate. Fixes part of bug 654;
7035 patch contributed by Josh Albrecht.
7037 o Minor features (directory authorities):
7038 - Try not to open more than one descriptor-downloading connection
7039 to an authority at once. This should reduce load on directory
7040 authorities. Fixes bug 366.
7041 - Add cross-certification to newly generated certificates, so that
7042 a signing key is enough information to look up a certificate. Start
7043 serving certificates by <identity digest, signing key digest>
7044 pairs. Implements proposal 157.
7045 - When a directory authority downloads a descriptor that it then
7046 immediately rejects, do not retry downloading it right away. Should
7047 save some bandwidth on authorities. Fix for bug 888. Patch by
7049 - Directory authorities now serve a /tor/dbg-stability.txt URL to
7050 help debug WFU and MTBF calculations.
7051 - In directory authorities' approved-routers files, allow
7052 fingerprints with or without space.
7054 o Minor features (directory mirrors):
7055 - When a download gets us zero good descriptors, do not notify
7056 Tor that new directory information has arrived.
7057 - Servers support a new URL scheme for consensus downloads that
7058 allows the client to specify which authorities are trusted.
7059 The server then only sends the consensus if the client will trust
7060 it. Otherwise a 404 error is sent back. Clients use this
7061 new scheme when the server supports it (meaning it's running
7062 0.2.1.1-alpha or later). Implements proposal 134.
7064 o Minor features (bridges):
7065 - If the bridge config line doesn't specify a port, assume 443.
7066 This makes bridge lines a bit smaller and easier for users to
7068 - If we're using bridges and our network goes away, be more willing
7069 to forgive our bridges and try again when we get an application
7072 o Minor features (hidden services):
7073 - When the client launches an introduction circuit, retry with a
7074 new circuit after 30 seconds rather than 60 seconds.
7075 - Launch a second client-side introduction circuit in parallel
7076 after a delay of 15 seconds (based on work by Christian Wilms).
7077 - Hidden services start out building five intro circuits rather
7078 than three, and when the first three finish they publish a service
7079 descriptor using those. Now we publish our service descriptor much
7080 faster after restart.
7081 - Drop the requirement to have an open dir port for storing and
7082 serving v2 hidden service descriptors.
7084 o Minor features (build and packaging):
7085 - On Linux, use the prctl call to re-enable core dumps when the User
7087 - Try to make sure that the version of Libevent we're running with
7088 is binary-compatible with the one we built with. May address bug
7090 - Add a new --enable-local-appdata configuration switch to change
7091 the default location of the datadir on win32 from APPDATA to
7092 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
7093 entirely. Patch from coderman.
7094 - Build correctly against versions of OpenSSL 0.9.8 or later that
7095 are built without support for deprecated functions.
7096 - On platforms with a maximum syslog string length, truncate syslog
7097 messages to that length ourselves, rather than relying on the
7098 system to do it for us.
7099 - Automatically detect MacOSX versions earlier than 10.4.0, and
7100 disable kqueue from inside Tor when running with these versions.
7101 We previously did this from the startup script, but that was no
7102 help to people who didn't use the startup script. Resolves bug 863.
7103 - Build correctly when configured to build outside the main source
7104 path. Patch from Michael Gold.
7105 - Disable GCC's strict alias optimization by default, to avoid the
7106 likelihood of its introducing subtle bugs whenever our code violates
7107 the letter of C99's alias rules.
7108 - Change the contrib/tor.logrotate script so it makes the new
7109 logs as "_tor:_tor" rather than the default, which is generally
7110 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
7111 - Change our header file guard macros to be less likely to conflict
7112 with system headers. Adam Langley noticed that we were conflicting
7113 with log.h on Android.
7114 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
7115 and stop using a warning that had become unfixably verbose under
7117 - Use a lockfile to make sure that two Tor processes are not
7118 simultaneously running with the same datadir.
7119 - Allow OpenSSL to use dynamic locks if it wants.
7120 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
7122 o Minor features (controllers):
7123 - When generating circuit events with verbose nicknames for
7124 controllers, try harder to look up nicknames for routers on a
7125 circuit. (Previously, we would look in the router descriptors we had
7126 for nicknames, but not in the consensus.) Partial fix for bug 941.
7127 - New controller event NEWCONSENSUS that lists the networkstatus
7128 lines for every recommended relay. Now controllers like Torflow
7129 can keep up-to-date on which relays they should be using.
7130 - New controller event "clients_seen" to report a geoip-based summary
7131 of which countries we've seen clients from recently. Now controllers
7132 like Vidalia can show bridge operators that they're actually making
7134 - Add a 'getinfo status/clients-seen' controller command, in case
7135 controllers want to hear clients_seen events but connect late.
7136 - New CONSENSUS_ARRIVED event to note when a new consensus has
7137 been fetched and validated.
7138 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
7139 controllers to prevent SIGHUP from reloading the configuration.
7141 - Return circuit purposes in response to GETINFO circuit-status.
7143 - Serve the latest v3 networkstatus consensus via the control
7144 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
7145 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
7146 controller can query our current bootstrap state in case it attaches
7147 partway through and wants to catch up.
7148 - Provide circuit purposes along with circuit events to the controller.
7150 o Minor features (tools):
7151 - Do not have tor-resolve automatically refuse all .onion addresses;
7152 if AutomapHostsOnResolve is set in your torrc, this will work fine.
7153 - Add a -p option to tor-resolve for specifying the SOCKS port: some
7154 people find host:port too confusing.
7155 - Print the SOCKS5 error message string as well as the error code
7156 when a tor-resolve request fails. Patch from Jacob.
7158 o Minor bugfixes (memory and resource management):
7159 - Clients no longer cache certificates for authorities they do not
7160 recognize. Bugfix on 0.2.0.9-alpha.
7161 - Do not use C's stdio library for writing to log files. This will
7162 improve logging performance by a minute amount, and will stop
7163 leaking fds when our disk is full. Fixes bug 861.
7164 - Stop erroneous use of O_APPEND in cases where we did not in fact
7165 want to re-seek to the end of a file before every last write().
7166 - Fix a small alignment and memory-wasting bug on buffer chunks.
7168 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
7169 to avoid unused RAM in buffer chunks and memory pools.
7170 - Reduce the default smartlist size from 32 to 16; it turns out that
7171 most smartlists hold around 8-12 elements tops.
7172 - Make dumpstats() log the fullness and size of openssl-internal
7174 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
7175 patch to their OpenSSL, turn it on to save memory on servers. This
7176 patch will (with any luck) get included in a mainline distribution
7178 - Fix a memory leak when v3 directory authorities load their keys
7179 and cert from disk. Bugfix on 0.2.0.1-alpha.
7180 - Stop using malloc_usable_size() to use more area than we had
7181 actually allocated: it was safe, but made valgrind really unhappy.
7182 - Make the assert_circuit_ok() function work correctly on circuits that
7183 have already been marked for close.
7184 - Fix uninitialized size field for memory area allocation: may improve
7185 memory performance during directory parsing.
7187 o Minor bugfixes (clients):
7188 - Stop reloading the router list from disk for no reason when we
7189 run out of reachable directory mirrors. Once upon a time reloading
7190 it would set the 'is_running' flag back to 1 for them. It hasn't
7191 done that for a long time.
7192 - When we had picked an exit node for a connection, but marked it as
7193 "optional", and it turned out we had no onion key for the exit,
7194 stop wanting that exit and try again. This situation may not
7195 be possible now, but will probably become feasible with proposal
7196 158. Spotted by rovv. Fixes another case of bug 752.
7197 - Fix a bug in address parsing that was preventing bridges or hidden
7198 service targets from being at IPv6 addresses.
7199 - Do not remove routers as too old if we do not have any consensus
7200 document. Bugfix on 0.2.0.7-alpha.
7201 - When an exit relay resolves a stream address to a local IP address,
7202 do not just keep retrying that same exit relay over and
7203 over. Instead, just close the stream. Addresses bug 872. Bugfix
7204 on 0.2.0.32. Patch from rovv.
7205 - Made Tor a little less aggressive about deleting expired
7206 certificates. Partial fix for bug 854.
7207 - Treat duplicate certificate fetches as failures, so that we do
7208 not try to re-fetch an expired certificate over and over and over.
7209 - Do not say we're fetching a certificate when we'll in fact skip it
7210 because of a pending download.
7211 - If we have correct permissions on $datadir, we complain to stdout
7212 and fail to start. But dangerous permissions on
7213 $datadir/cached-status/ would cause us to open a log and complain
7214 there. Now complain to stdout and fail to start in both cases. Fixes
7215 bug 820, reported by seeess.
7217 o Minor bugfixes (bridges):
7218 - When we made bridge authorities stop serving bridge descriptors over
7219 unencrypted links, we also broke DirPort reachability testing for
7220 bridges. So bridges with a non-zero DirPort were printing spurious
7221 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
7222 - Don't allow a bridge to publish its router descriptor to a
7223 non-bridge directory authority. Fixes part of bug 932.
7224 - When we change to or from being a bridge, reset our counts of
7225 client usage by country. Fixes bug 932.
7227 o Minor bugfixes (relays):
7228 - Log correct error messages for DNS-related network errors on
7230 - Actually return -1 in the error case for read_bandwidth_usage().
7231 Harmless bug, since we currently don't care about the return value
7232 anywhere. Bugfix on 0.2.0.9-alpha.
7233 - Provide a more useful log message if bug 977 (related to buffer
7234 freelists) ever reappears, and do not crash right away.
7235 - We were already rejecting relay begin cells with destination port
7236 of 0. Now also reject extend cells with destination port or address
7237 of 0. Suggested by lark.
7238 - When we can't transmit a DNS request due to a network error, retry
7239 it after a while, and eventually transmit a failing response to
7240 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
7241 - Solve a bug that kept hardware crypto acceleration from getting
7242 enabled when accounting was turned on. Fixes bug 907. Bugfix on
7244 - When a canonical connection appears later in our internal list
7245 than a noncanonical one for a given OR ID, always use the
7246 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
7248 - Avoid some nasty corner cases in the logic for marking connections
7249 as too old or obsolete or noncanonical for circuits. Partial
7251 - Fix another interesting corner-case of bug 891 spotted by rovv:
7252 Previously, if two hosts had different amounts of clock drift, and
7253 one of them created a new connection with just the wrong timing,
7254 the other might decide to deprecate the new connection erroneously.
7255 Bugfix on 0.1.1.13-alpha.
7256 - If one win32 nameserver fails to get added, continue adding the
7257 rest, and don't automatically fail.
7258 - Fix a bug where an unreachable relay would establish enough
7259 reachability testing circuits to do a bandwidth test -- if
7260 we already have a connection to the middle hop of the testing
7261 circuit, then it could establish the last hop by using the existing
7262 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
7263 circuits no longer use entry guards in 0.2.1.3-alpha.
7265 o Minor bugfixes (directory authorities):
7266 - Limit uploaded directory documents to be 16M rather than 500K.
7267 The directory authorities were refusing v3 consensus votes from
7268 other authorities, since the votes are now 504K. Fixes bug 959;
7269 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
7270 - Directory authorities should never send a 503 "busy" response to
7271 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
7273 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
7274 headers. Bugfix on 0.2.0.10-alpha.
7276 o Minor bugfixes (hidden services):
7277 - When we can't find an intro key for a v2 hidden service descriptor,
7278 fall back to the v0 hidden service descriptor and log a bug message.
7279 Workaround for bug 1024.
7280 - In very rare situations new hidden service descriptors were
7281 published earlier than 30 seconds after the last change to the
7282 service. (We currently think that a hidden service descriptor
7283 that's been stable for 30 seconds is worth publishing.)
7284 - If a hidden service sends us an END cell, do not consider
7285 retrying the connection; just close it. Patch from rovv.
7286 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
7287 service directories if they have no advertised dir port. Bugfix
7290 o Minor bugfixes (tools):
7291 - In the torify(1) manpage, mention that tsocks will leak your
7294 o Minor bugfixes (controllers):
7295 - If the controller claimed responsibility for a stream, but that
7296 stream never finished making its connection, it would live
7297 forever in circuit_wait state. Now we close it after SocksTimeout
7298 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
7299 - Make DNS resolved controller events into "CLOSED", not
7300 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
7302 - The control port would close the connection before flushing long
7303 replies, such as the network consensus, if a QUIT command was issued
7304 before the reply had completed. Now, the control port flushes all
7305 pending replies before closing the connection. Also fix a spurious
7306 warning when a QUIT command is issued after a malformed or rejected
7307 AUTHENTICATE command, but before the connection was closed. Patch
7308 by Marcus Griep. Fixes bugs 1015 and 1016.
7309 - Fix a bug that made stream bandwidth get misreported to the
7312 o Deprecated and removed features:
7313 - The old "tor --version --version" command, which would print out
7314 the subversion "Id" of most of the source files, is now removed. It
7315 turned out to be less useful than we'd expected, and harder to
7317 - RedirectExits has been removed. It was deprecated since
7319 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
7320 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
7321 - Cell pools are now always enabled; --disable-cell-pools is ignored.
7322 - Directory mirrors no longer fetch the v1 directory or
7323 running-routers files. They are obsolete, and nobody asks for them
7324 anymore. This is the first step to making v1 authorities obsolete.
7325 - Take out the TestVia config option, since it was a workaround for
7326 a bug that was fixed in Tor 0.1.1.21.
7327 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
7328 HiddenServiceExcludeNodes as obsolete: they never worked properly,
7329 and nobody seems to be using them. Fixes bug 754. Bugfix on
7330 0.1.0.1-rc. Patch from Christian Wilms.
7331 - Remove all backward-compatibility code for relays running
7332 versions of Tor so old that they no longer work at all on the
7335 o Code simplifications and refactoring:
7336 - Tool-assisted documentation cleanup. Nearly every function or
7337 static variable in Tor should have its own documentation now.
7338 - Rename the confusing or_is_obsolete field to the more appropriate
7339 is_bad_for_new_circs, and move it to or_connection_t where it
7341 - Move edge-only flags from connection_t to edge_connection_t: not
7342 only is this better coding, but on machines of plausible alignment,
7343 it should save 4-8 bytes per connection_t. "Every little bit helps."
7344 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
7345 for consistency; keep old option working for backward compatibility.
7346 - Simplify the code for finding connections to use for a circuit.
7347 - Revise the connection_new functions so that a more typesafe variant
7348 exists. This will work better with Coverity, and let us find any
7349 actual mistakes we're making here.
7350 - Refactor unit testing logic so that dmalloc can be used sensibly
7351 with unit tests to check for memory leaks.
7352 - Move all hidden-service related fields from connection and circuit
7353 structure to substructures: this way they won't eat so much memory.
7354 - Squeeze 2-5% out of client performance (according to oprofile) by
7355 improving the implementation of some policy-manipulation functions.
7356 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
7357 be more efficient. Formerly it was quadratic in the number of
7358 servers; now it should be linear. Fixes bug 509.
7359 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
7360 and n_conn_id_digest fields into a separate structure that's
7361 only needed when the circuit has not yet attached to an n_conn.
7362 - Optimize out calls to time(NULL) that occur for every IO operation,
7363 or for every cell. On systems like Windows where time() is a
7364 slow syscall, this fix will be slightly helpful.
7367 Changes in version 0.2.0.35 - 2009-06-24
7369 - Avoid crashing in the presence of certain malformed descriptors.
7370 Found by lark, and by automated fuzzing.
7371 - Fix an edge case where a malicious exit relay could convince a
7372 controller that the client's DNS question resolves to an internal IP
7373 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7376 - Finally fix the bug where dynamic-IP relays disappear when their
7377 IP address changes: directory mirrors were mistakenly telling
7378 them their old address if they asked via begin_dir, so they
7379 never got an accurate answer about their new address, so they
7380 just vanished after a day. For belt-and-suspenders, relays that
7381 don't set Address in their config now avoid using begin_dir for
7382 all direct connections. Should fix bugs 827, 883, and 900.
7383 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7384 that would occur on some exit nodes when DNS failures and timeouts
7385 occurred in certain patterns. Fix for bug 957.
7388 - When starting with a cache over a few days old, do not leak
7389 memory for the obsolete router descriptors in it. Bugfix on
7390 0.2.0.33; fixes bug 672.
7391 - Hidden service clients didn't use a cached service descriptor that
7392 was older than 15 minutes, but wouldn't fetch a new one either,
7393 because there was already one in the cache. Now, fetch a v2
7394 descriptor unless the same descriptor was added to the cache within
7395 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7398 Changes in version 0.2.0.34 - 2009-02-08
7399 Tor 0.2.0.34 features several more security-related fixes. You should
7400 upgrade, especially if you run an exit relay (remote crash) or a
7401 directory authority (remote infinite loop), or you're on an older
7402 (pre-XP) or not-recently-patched Windows (remote exploit).
7404 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
7405 have many known flaws, and nobody should be using them. You should
7406 upgrade. If you're using a Linux or BSD and its packages are obsolete,
7407 stop using those packages and upgrade anyway.
7410 - Fix an infinite-loop bug on handling corrupt votes under certain
7411 circumstances. Bugfix on 0.2.0.8-alpha.
7412 - Fix a temporary DoS vulnerability that could be performed by
7413 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7414 - Avoid a potential crash on exit nodes when processing malformed
7415 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
7416 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
7417 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
7420 - Fix compilation on systems where time_t is a 64-bit integer.
7421 Patch from Matthias Drochner.
7422 - Don't consider expiring already-closed client connections. Fixes
7423 bug 893. Bugfix on 0.0.2pre20.
7426 Changes in version 0.2.0.33 - 2009-01-21
7427 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
7428 useful to users. It also finally fixes a bug where a relay or client
7429 that's been off for many days would take a long time to bootstrap.
7431 This update also fixes an important security-related bug reported by
7432 Ilja van Sprundel. You should upgrade. (We'll send out more details
7433 about the bug once people have had some time to upgrade.)
7436 - Fix a heap-corruption bug that may be remotely triggerable on
7437 some platforms. Reported by Ilja van Sprundel.
7440 - When a stream at an exit relay is in state "resolving" or
7441 "connecting" and it receives an "end" relay cell, the exit relay
7442 would silently ignore the end cell and not close the stream. If
7443 the client never closes the circuit, then the exit relay never
7444 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
7446 - When sending CREATED cells back for a given circuit, use a 64-bit
7447 connection ID to find the right connection, rather than an addr:port
7448 combination. Now that we can have multiple OR connections between
7449 the same ORs, it is no longer possible to use addr:port to uniquely
7450 identify a connection.
7451 - Bridge relays that had DirPort set to 0 would stop fetching
7452 descriptors shortly after startup, and then briefly resume
7453 after a new bandwidth test and/or after publishing a new bridge
7454 descriptor. Bridge users that try to bootstrap from them would
7455 get a recent networkstatus but would get descriptors from up to
7456 18 hours earlier, meaning most of the descriptors were obsolete
7457 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
7458 - Prevent bridge relays from serving their 'extrainfo' document
7459 to anybody who asks, now that extrainfo docs include potentially
7460 sensitive aggregated client geoip summaries. Bugfix on
7462 - If the cached networkstatus consensus is more than five days old,
7463 discard it rather than trying to use it. In theory it could be
7464 useful because it lists alternate directory mirrors, but in practice
7465 it just means we spend many minutes trying directory mirrors that
7466 are long gone from the network. Also discard router descriptors as
7467 we load them if they are more than five days old, since the onion
7468 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
7471 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
7472 could make gcc generate non-functional binary search code. Bugfix
7474 - Build correctly on platforms without socklen_t.
7475 - Compile without warnings on solaris.
7476 - Avoid potential crash on internal error during signature collection.
7477 Fixes bug 864. Patch from rovv.
7478 - Correct handling of possible malformed authority signing key
7479 certificates with internal signature types. Fixes bug 880.
7480 Bugfix on 0.2.0.3-alpha.
7481 - Fix a hard-to-trigger resource leak when logging credential status.
7483 - When we can't initialize DNS because the network is down, do not
7484 automatically stop Tor from starting. Instead, we retry failed
7485 dns_init() every 10 minutes, and change the exit policy to reject
7486 *:* until one succeeds. Fixes bug 691.
7487 - Use 64 bits instead of 32 bits for connection identifiers used with
7488 the controller protocol, to greatly reduce risk of identifier reuse.
7489 - When we're choosing an exit node for a circuit, and we have
7490 no pending streams, choose a good general exit rather than one that
7491 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
7492 - Fix another case of assuming, when a specific exit is requested,
7493 that we know more than the user about what hosts it allows.
7494 Fixes one case of bug 752. Patch from rovv.
7495 - Clip the MaxCircuitDirtiness config option to a minimum of 10
7496 seconds. Warn the user if lower values are given in the
7497 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
7498 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
7499 user if lower values are given in the configuration. Bugfix on
7500 0.1.1.17-rc. Patch by Sebastian.
7501 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
7502 the cache because we already had a v0 descriptor with the same ID.
7503 Bugfix on 0.2.0.18-alpha.
7504 - Fix a race condition when freeing keys shared between main thread
7505 and CPU workers that could result in a memory leak. Bugfix on
7506 0.1.0.1-rc. Fixes bug 889.
7507 - Send a valid END cell back when a client tries to connect to a
7508 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
7509 840. Patch from rovv.
7510 - Check which hops rendezvous stream cells are associated with to
7511 prevent possible guess-the-streamid injection attacks from
7512 intermediate hops. Fixes another case of bug 446. Based on patch
7514 - If a broken client asks a non-exit router to connect somewhere,
7515 do not even do the DNS lookup before rejecting the connection.
7516 Fixes another case of bug 619. Patch from rovv.
7517 - When a relay gets a create cell it can't decrypt (e.g. because it's
7518 using the wrong onion key), we were dropping it and letting the
7519 client time out. Now actually answer with a destroy cell. Fixes
7520 bug 904. Bugfix on 0.0.2pre8.
7522 o Minor bugfixes (hidden services):
7523 - Do not throw away existing introduction points on SIGHUP. Bugfix on
7524 0.0.6pre1. Patch by Karsten. Fixes bug 874.
7527 - Report the case where all signatures in a detached set are rejected
7528 differently than the case where there is an error handling the
7530 - When we realize that another process has modified our cached
7531 descriptors, print out a more useful error message rather than
7532 triggering an assertion. Fixes bug 885. Patch from Karsten.
7533 - Implement the 0x20 hack to better resist DNS poisoning: set the
7534 case on outgoing DNS requests randomly, and reject responses that do
7535 not match the case correctly. This logic can be disabled with the
7536 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
7537 of servers that do not reliably preserve case in replies. See
7538 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
7540 - Check DNS replies for more matching fields to better resist DNS
7542 - Never use OpenSSL compression: it wastes RAM and CPU trying to
7543 compress cells, which are basically all encrypted, compressed, or
7547 Changes in version 0.2.0.32 - 2008-11-20
7548 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
7549 packages (and maybe other packages) noticed by Theo de Raadt, fixes
7550 a smaller security flaw that might allow an attacker to access local
7551 services, further improves hidden service performance, and fixes a
7552 variety of other issues.
7555 - The "User" and "Group" config options did not clear the
7556 supplementary group entries for the Tor process. The "User" option
7557 is now more robust, and we now set the groups to the specified
7558 user's primary group. The "Group" option is now ignored. For more
7559 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
7560 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
7561 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
7562 - The "ClientDNSRejectInternalAddresses" config option wasn't being
7563 consistently obeyed: if an exit relay refuses a stream because its
7564 exit policy doesn't allow it, we would remember what IP address
7565 the relay said the destination address resolves to, even if it's
7566 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
7569 - Fix a DOS opportunity during the voting signature collection process
7570 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
7572 o Major bugfixes (hidden services):
7573 - When fetching v0 and v2 rendezvous service descriptors in parallel,
7574 we were failing the whole hidden service request when the v0
7575 descriptor fetch fails, even if the v2 fetch is still pending and
7576 might succeed. Similarly, if the last v2 fetch fails, we were
7577 failing the whole hidden service request even if a v0 fetch is
7578 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
7579 - When extending a circuit to a hidden service directory to upload a
7580 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
7581 requests failed, because the router descriptor has not been
7582 downloaded yet. In these cases, do not attempt to upload the
7583 rendezvous descriptor, but wait until the router descriptor is
7584 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
7585 descriptor from a hidden service directory for which the router
7586 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
7590 - Fix several infrequent memory leaks spotted by Coverity.
7591 - When testing for libevent functions, set the LDFLAGS variable
7592 correctly. Found by Riastradh.
7593 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
7594 bootstrapping with tunneled directory connections. Bugfix on
7595 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
7596 - When asked to connect to A.B.exit:80, if we don't know the IP for A
7597 and we know that server B rejects most-but-not all connections to
7598 port 80, we would previously reject the connection. Now, we assume
7599 the user knows what they were asking for. Fixes bug 752. Bugfix
7600 on 0.0.9rc5. Diagnosed by BarkerJr.
7601 - If we overrun our per-second write limits a little, count this as
7602 having used up our write allocation for the second, and choke
7603 outgoing directory writes. Previously, we had only counted this when
7604 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
7605 Bugfix on 0.2.0.x (??).
7606 - Remove the old v2 directory authority 'lefkada' from the default
7607 list. It has been gone for many months.
7608 - Stop doing unaligned memory access that generated bus errors on
7609 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
7610 - Make USR2 log-level switch take effect immediately. Bugfix on
7613 o Minor bugfixes (controller):
7614 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
7615 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
7618 Changes in version 0.2.0.31 - 2008-09-03
7619 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
7620 a big bug we're seeing where in rare cases traffic from one Tor stream
7621 gets mixed into another stream, and fixes a variety of smaller issues.
7624 - Make sure that two circuits can never exist on the same connection
7625 with the same circuit ID, even if one is marked for close. This
7626 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
7627 - Relays now reject risky extend cells: if the extend cell includes
7628 a digest of all zeroes, or asks to extend back to the relay that
7629 sent the extend cell, tear down the circuit. Ideas suggested
7631 - If not enough of our entry guards are available so we add a new
7632 one, we might use the new one even if it overlapped with the
7633 current circuit's exit relay (or its family). Anonymity bugfix
7634 pointed out by rovv.
7637 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
7638 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
7639 - Correctly detect the presence of the linux/netfilter_ipv4.h header
7640 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
7641 - Pick size of default geoip filename string correctly on windows.
7642 Fixes bug 806. Bugfix on 0.2.0.30.
7643 - Make the autoconf script accept the obsolete --with-ssl-dir
7644 option as an alias for the actually-working --with-openssl-dir
7645 option. Fix the help documentation to recommend --with-openssl-dir.
7646 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
7647 - When using the TransPort option on OpenBSD, and using the User
7648 option to change UID and drop privileges, make sure to open
7649 /dev/pf before dropping privileges. Fixes bug 782. Patch from
7650 Christopher Davis. Bugfix on 0.1.2.1-alpha.
7651 - Try to attach connections immediately upon receiving a RENDEZVOUS2
7652 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
7653 on the client side when connecting to a hidden service. Bugfix
7654 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
7655 - When closing an application-side connection because its circuit is
7656 getting torn down, generate the stream event correctly. Bugfix on
7657 0.1.2.x. Anonymous patch.
7660 Changes in version 0.2.0.30 - 2008-07-15
7661 This new stable release switches to a more efficient directory
7662 distribution design, adds features to make connections to the Tor
7663 network harder to block, allows Tor to act as a DNS proxy, adds separate
7664 rate limiting for relayed traffic to make it easier for clients to
7665 become relays, fixes a variety of potential anonymity problems, and
7666 includes the usual huge pile of other features and bug fixes.
7668 o New v3 directory design:
7669 - Tor now uses a new way to learn about and distribute information
7670 about the network: the directory authorities vote on a common
7671 network status document rather than each publishing their own
7672 opinion. Now clients and caches download only one networkstatus
7673 document to bootstrap, rather than downloading one for each
7674 authority. Clients only download router descriptors listed in
7675 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
7677 - Set up moria1, tor26, and dizum as v3 directory authorities
7678 in addition to being v2 authorities. Also add three new ones:
7679 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
7680 dannenberg (run by CCC).
7681 - Switch to multi-level keys for directory authorities: now their
7682 long-term identity key can be kept offline, and they periodically
7683 generate a new signing key. Clients fetch the "key certificates"
7684 to keep up to date on the right keys. Add a standalone tool
7685 "tor-gencert" to generate key certificates. Implements proposal 103.
7686 - Add a new V3AuthUseLegacyKey config option to make it easier for
7687 v3 authorities to change their identity keys if another bug like
7688 Debian's OpenSSL RNG flaw appears.
7689 - Authorities and caches fetch the v2 networkstatus documents
7690 less often, now that v3 is recommended.
7692 o Make Tor connections stand out less on the wire:
7693 - Use an improved TLS handshake designed by Steven Murdoch in proposal
7694 124, as revised in proposal 130. The new handshake is meant to
7695 be harder for censors to fingerprint, and it adds the ability
7696 to detect certain kinds of man-in-the-middle traffic analysis
7697 attacks. The new handshake format includes version negotiation for
7698 OR connections as described in proposal 105, which will allow us
7699 to improve Tor's link protocol more safely in the future.
7700 - Enable encrypted directory connections by default for non-relays,
7701 so censor tools that block Tor directory connections based on their
7702 plaintext patterns will no longer work. This means Tor works in
7703 certain censored countries by default again.
7704 - Stop including recognizeable strings in the commonname part of
7705 Tor's x509 certificates.
7707 o Implement bridge relays:
7708 - Bridge relays (or "bridges" for short) are Tor relays that aren't
7709 listed in the main Tor directory. Since there is no complete public
7710 list of them, even an ISP that is filtering connections to all the
7711 known Tor relays probably won't be able to block all the bridges.
7712 See doc/design-paper/blocking.pdf and proposal 125 for details.
7713 - New config option BridgeRelay that specifies you want to be a
7714 bridge relay rather than a normal relay. When BridgeRelay is set
7715 to 1, then a) you cache dir info even if your DirPort ins't on,
7716 and b) the default for PublishServerDescriptor is now "bridge"
7717 rather than "v2,v3".
7718 - New config option "UseBridges 1" for clients that want to use bridge
7719 relays instead of ordinary entry guards. Clients then specify
7720 bridge relays by adding "Bridge" lines to their config file. Users
7721 can learn about a bridge relay either manually through word of
7722 mouth, or by one of our rate-limited mechanisms for giving out
7723 bridge addresses without letting an attacker easily enumerate them
7724 all. See https://www.torproject.org/bridges for details.
7725 - Bridge relays behave like clients with respect to time intervals
7726 for downloading new v3 consensus documents -- otherwise they
7727 stand out. Bridge users now wait until the end of the interval,
7728 so their bridge relay will be sure to have a new consensus document.
7730 o Implement bridge directory authorities:
7731 - Bridge authorities are like normal directory authorities, except
7732 they don't serve a list of known bridges. Therefore users that know
7733 a bridge's fingerprint can fetch a relay descriptor for that bridge,
7734 including fetching updates e.g. if the bridge changes IP address,
7735 yet an attacker can't just fetch a list of all the bridges.
7736 - Set up Tonga as the default bridge directory authority.
7737 - Bridge authorities refuse to serve bridge descriptors or other
7738 bridge information over unencrypted connections (that is, when
7739 responding to direct DirPort requests rather than begin_dir cells.)
7740 - Bridge directory authorities do reachability testing on the
7741 bridges they know. They provide router status summaries to the
7742 controller via "getinfo ns/purpose/bridge", and also dump summaries
7743 to a file periodically, so we can keep internal stats about which
7744 bridges are functioning.
7745 - If bridge users set the UpdateBridgesFromAuthority config option,
7746 but the digest they ask for is a 404 on the bridge authority,
7747 they fall back to contacting the bridge directly.
7748 - Bridges always use begin_dir to publish their server descriptor to
7749 the bridge authority using an anonymous encrypted tunnel.
7750 - Early work on a "bridge community" design: if bridge authorities set
7751 the BridgePassword config option, they will serve a snapshot of
7752 known bridge routerstatuses from their DirPort to anybody who
7753 knows that password. Unset by default.
7754 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
7755 report sanitized aggregated summaries in their extra-info documents
7756 privately to the bridge authority, listing which countries are
7757 able to reach them. We hope this mechanism will let us learn when
7758 certain countries start trying to block bridges.
7759 - Bridge authorities write bridge descriptors to disk, so they can
7760 reload them after a reboot. They can also export the descriptors
7761 to other programs, so we can distribute them to blocked users via
7762 the BridgeDB interface, e.g. via https://bridges.torproject.org/
7763 and bridges@torproject.org.
7765 o Tor can be a DNS proxy:
7766 - The new client-side DNS proxy feature replaces the need for
7767 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
7768 for DNS requests on port 9999, use the Tor network to resolve them
7769 anonymously, and send the reply back like a regular DNS server.
7770 The code still only implements a subset of DNS.
7771 - Add a new AutomapHostsOnResolve option: when it is enabled, any
7772 resolve request for hosts matching a given pattern causes Tor to
7773 generate an internal virtual address mapping for that host. This
7774 allows DNSPort to work sensibly with hidden service users. By
7775 default, .exit and .onion addresses are remapped; the list of
7776 patterns can be reconfigured with AutomapHostsSuffixes.
7777 - Add an "-F" option to tor-resolve to force a resolve for a .onion
7778 address. Thanks to the AutomapHostsOnResolve option, this is no
7779 longer a completely silly thing to do.
7781 o Major features (relay usability):
7782 - New config options RelayBandwidthRate and RelayBandwidthBurst:
7783 a separate set of token buckets for relayed traffic. Right now
7784 relayed traffic is defined as answers to directory requests, and
7785 OR connections that don't have any local circuits on them. See
7786 proposal 111 for details.
7787 - Create listener connections before we setuid to the configured
7788 User and Group. Now non-Windows users can choose port values
7789 under 1024, start Tor as root, and have Tor bind those ports
7790 before it changes to another UID. (Windows users could already
7792 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
7793 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
7794 on "vserver" accounts. Patch from coderman.
7796 o Major features (directory authorities):
7797 - Directory authorities track weighted fractional uptime and weighted
7798 mean-time-between failures for relays. WFU is suitable for deciding
7799 whether a node is "usually up", while MTBF is suitable for deciding
7800 whether a node is "likely to stay up." We need both, because
7801 "usually up" is a good requirement for guards, while "likely to
7802 stay up" is a good requirement for long-lived connections.
7803 - Directory authorities use a new formula for selecting which relays
7804 to advertise as Guards: they must be in the top 7/8 in terms of
7805 how long we have known about them, and above the median of those
7806 nodes in terms of weighted fractional uptime.
7807 - Directory authorities use a new formula for selecting which relays
7808 to advertise as Stable: when we have 4 or more days of data, use
7809 median measured MTBF rather than median declared uptime. Implements
7811 - Directory authorities accept and serve "extra info" documents for
7812 routers. Routers now publish their bandwidth-history lines in the
7813 extra-info docs rather than the main descriptor. This step saves
7814 60% (!) on compressed router descriptor downloads. Servers upload
7815 extra-info docs to any authority that accepts them; directory
7816 authorities now allow multiple router descriptors and/or extra
7817 info documents to be uploaded in a single go. Authorities, and
7818 caches that have been configured to download extra-info documents,
7819 download them as needed. Implements proposal 104.
7820 - Authorities now list relays who have the same nickname as
7821 a different named relay, but list them with a new flag:
7822 "Unnamed". Now we can make use of relays that happen to pick the
7823 same nickname as a server that registered two years ago and then
7824 disappeared. Implements proposal 122.
7825 - Store routers in a file called cached-descriptors instead of in
7826 cached-routers. Initialize cached-descriptors from cached-routers
7827 if the old format is around. The new format allows us to store
7828 annotations along with descriptors, to record the time we received
7829 each descriptor, its source, and its purpose: currently one of
7830 general, controller, or bridge.
7832 o Major features (other):
7833 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
7834 Tor can warn and/or refuse connections to ports commonly used with
7835 vulnerable-plaintext protocols. Currently we warn on ports 23,
7836 109, 110, and 143, but we don't reject any. Based on proposal 129
7837 by Kevin Bauer and Damon McCoy.
7838 - Integrate Karsten Loesing's Google Summer of Code project to publish
7839 hidden service descriptors on a set of redundant relays that are a
7840 function of the hidden service address. Now we don't have to rely
7841 on three central hidden service authorities for publishing and
7842 fetching every hidden service descriptor. Implements proposal 114.
7843 - Allow tunnelled directory connections to ask for an encrypted
7844 "begin_dir" connection or an anonymized "uses a full Tor circuit"
7845 connection independently. Now we can make anonymized begin_dir
7846 connections for (e.g.) more secure hidden service posting and
7849 o Major bugfixes (crashes and assert failures):
7850 - Stop imposing an arbitrary maximum on the number of file descriptors
7851 used for busy servers. Bug reported by Olaf Selke; patch from
7853 - Avoid possible failures when generating a directory with routers
7854 with over-long versions strings, or too many flags set.
7855 - Fix a rare assert error when we're closing one of our threads:
7856 use a mutex to protect the list of logs, so we never write to the
7857 list as it's being freed. Fixes the very rare bug 575, which is
7858 kind of the revenge of bug 222.
7859 - Avoid segfault in the case where a badly behaved v2 versioning
7860 directory sends a signed networkstatus with missing client-versions.
7861 - When we hit an EOF on a log (probably because we're shutting down),
7862 don't try to remove the log from the list: just mark it as
7863 unusable. (Bulletproofs against bug 222.)
7865 o Major bugfixes (code security fixes):
7866 - Detect size overflow in zlib code. Reported by Justin Ferguson and
7868 - Rewrite directory tokenization code to never run off the end of
7869 a string. Fixes bug 455. Patch from croup.
7870 - Be more paranoid about overwriting sensitive memory on free(),
7871 as a defensive programming tactic to ensure forward secrecy.
7873 o Major bugfixes (anonymity fixes):
7874 - Reject requests for reverse-dns lookup of names that are in
7875 a private address space. Patch from lodger.
7876 - Never report that we've used more bandwidth than we're willing to
7877 relay: it leaks how much non-relay traffic we're using. Resolves
7879 - As a client, do not believe any server that tells us that an
7880 address maps to an internal address space.
7881 - Warn about unsafe ControlPort configurations.
7882 - Directory authorities now call routers Fast if their bandwidth is
7883 at least 100KB/s, and consider their bandwidth adequate to be a
7884 Guard if it is at least 250KB/s, no matter the medians. This fix
7885 complements proposal 107.
7886 - Directory authorities now never mark more than 2 servers per IP as
7887 Valid and Running (or 5 on addresses shared by authorities).
7888 Implements proposal 109, by Kevin Bauer and Damon McCoy.
7889 - If we're a relay, avoid picking ourselves as an introduction point,
7890 a rendezvous point, or as the final hop for internal circuits. Bug
7891 reported by taranis and lodger.
7892 - Exit relays that are used as a client can now reach themselves
7893 using the .exit notation, rather than just launching an infinite
7894 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
7895 - Fix a bug where, when we were choosing the 'end stream reason' to
7896 put in our relay end cell that we send to the exit relay, Tor
7897 clients on Windows were sometimes sending the wrong 'reason'. The
7898 anonymity problem is that exit relays may be able to guess whether
7899 the client is running Windows, thus helping partition the anonymity
7900 set. Down the road we should stop sending reasons to exit relays,
7901 or otherwise prevent future versions of this bug.
7902 - Only update guard status (usable / not usable) once we have
7903 enough directory information. This was causing us to discard all our
7904 guards on startup if we hadn't been running for a few weeks. Fixes
7906 - When our directory information has been expired for a while, stop
7907 being willing to build circuits using it. Fixes bug 401.
7909 o Major bugfixes (peace of mind for relay operators)
7910 - Non-exit relays no longer answer "resolve" relay cells, so they
7911 can't be induced to do arbitrary DNS requests. (Tor clients already
7912 avoid using non-exit relays for resolve cells, but now servers
7913 enforce this too.) Fixes bug 619. Patch from lodger.
7914 - When we setconf ClientOnly to 1, close any current OR and Dir
7915 listeners. Reported by mwenge.
7917 o Major bugfixes (other):
7918 - If we only ever used Tor for hidden service lookups or posts, we
7919 would stop building circuits and start refusing connections after
7920 24 hours, since we falsely believed that Tor was dormant. Reported
7922 - Add a new __HashedControlSessionPassword option for controllers
7923 to use for one-off session password hashes that shouldn't get
7924 saved to disk by SAVECONF --- Vidalia users were accumulating a
7925 pile of HashedControlPassword lines in their torrc files, one for
7926 each time they had restarted Tor and then clicked Save. Make Tor
7927 automatically convert "HashedControlPassword" to this new option but
7928 only when it's given on the command line. Partial fix for bug 586.
7929 - Patch from "Andrew S. Lists" to catch when we contact a directory
7930 mirror at IP address X and he says we look like we're coming from
7931 IP address X. Otherwise this would screw up our address detection.
7932 - Reject uploaded descriptors and extrainfo documents if they're
7933 huge. Otherwise we'll cache them all over the network and it'll
7934 clog everything up. Suggested by Aljosha Judmayer.
7935 - When a hidden service was trying to establish an introduction point,
7936 and Tor *did* manage to reuse one of the preemptively built
7937 circuits, it didn't correctly remember which one it used,
7938 so it asked for another one soon after, until there were no
7939 more preemptive circuits, at which point it launched one from
7940 scratch. Bugfix on 0.0.9.x.
7942 o Rate limiting and load balancing improvements:
7943 - When we add data to a write buffer in response to the data on that
7944 write buffer getting low because of a flush, do not consider the
7945 newly added data as a candidate for immediate flushing, but rather
7946 make it wait until the next round of writing. Otherwise, we flush
7947 and refill recursively, and a single greedy TLS connection can
7948 eat all of our bandwidth.
7949 - When counting the number of bytes written on a TLS connection,
7950 look at the BIO actually used for writing to the network, not
7951 at the BIO used (sometimes) to buffer data for the network.
7952 Looking at different BIOs could result in write counts on the
7953 order of ULONG_MAX. Fixes bug 614.
7954 - If we change our MaxAdvertisedBandwidth and then reload torrc,
7955 Tor won't realize it should publish a new relay descriptor. Fixes
7956 bug 688, reported by mfr.
7957 - Avoid using too little bandwidth when our clock skips a few seconds.
7958 - Choose which bridge to use proportional to its advertised bandwidth,
7959 rather than uniformly at random. This should speed up Tor for
7960 bridge users. Also do this for people who set StrictEntryNodes.
7962 o Bootstrapping faster and building circuits more intelligently:
7963 - Fix bug 660 that was preventing us from knowing that we should
7964 preemptively build circuits to handle expected directory requests.
7965 - When we're checking if we have enough dir info for each relay
7966 to begin establishing circuits, make sure that we actually have
7967 the descriptor listed in the consensus, not just any descriptor.
7968 - Correctly notify one-hop connections when a circuit build has
7969 failed. Possible fix for bug 669. Found by lodger.
7970 - Clients now hold circuitless TLS connections open for 1.5 times
7971 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
7972 rebuild a new circuit over them within that timeframe. Previously,
7973 they held them open only for KeepalivePeriod (5 minutes).
7975 o Performance improvements (memory):
7976 - Add OpenBSD malloc code from "phk" as an optional malloc
7977 replacement on Linux: some glibc libraries do very poorly with
7978 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
7979 ./configure to get the replacement malloc code.
7980 - Switch our old ring buffer implementation for one more like that
7981 used by free Unix kernels. The wasted space in a buffer with 1mb
7982 of data will now be more like 8k than 1mb. The new implementation
7983 also avoids realloc();realloc(); patterns that can contribute to
7984 memory fragmentation.
7985 - Change the way that Tor buffers data that it is waiting to write.
7986 Instead of queueing data cells in an enormous ring buffer for each
7987 client->OR or OR->OR connection, we now queue cells on a separate
7988 queue for each circuit. This lets us use less slack memory, and
7989 will eventually let us be smarter about prioritizing different kinds
7991 - Reference-count and share copies of address policy entries; only 5%
7992 of them were actually distinct.
7993 - Tune parameters for cell pool allocation to minimize amount of
7995 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
7996 for every single inactive connection_t. Free items from the
7997 4k/16k-buffer free lists when they haven't been used for a while.
7998 - Make memory debugging information describe more about history
7999 of cell allocation, so we can help reduce our memory use.
8000 - Be even more aggressive about releasing RAM from small
8001 empty buffers. Thanks to our free-list code, this shouldn't be too
8002 performance-intensive.
8003 - Log malloc statistics from mallinfo() on platforms where it exists.
8004 - Use memory pools to allocate cells with better speed and memory
8005 efficiency, especially on platforms where malloc() is inefficient.
8006 - Add a --with-tcmalloc option to the configure script to link
8007 against tcmalloc (if present). Does not yet search for non-system
8010 o Performance improvements (socket management):
8011 - Count the number of open sockets separately from the number of
8012 active connection_t objects. This will let us avoid underusing
8013 our allocated connection limit.
8014 - We no longer use socket pairs to link an edge connection to an
8015 anonymous directory connection or a DirPort test connection.
8016 Instead, we track the link internally and transfer the data
8017 in-process. This saves two sockets per "linked" connection (at the
8018 client and at the server), and avoids the nasty Windows socketpair()
8020 - We were leaking a file descriptor if Tor started with a zero-length
8021 cached-descriptors file. Patch by "freddy77".
8023 o Performance improvements (CPU use):
8024 - Never walk through the list of logs if we know that no log target
8025 is interested in a given message.
8026 - Call routerlist_remove_old_routers() much less often. This should
8027 speed startup, especially on directory caches.
8028 - Base64 decoding was actually showing up on our profile when parsing
8029 the initial descriptor file; switch to an in-process all-at-once
8030 implementation that's about 3.5x times faster than calling out to
8032 - Use a slightly simpler string hashing algorithm (copying Python's
8033 instead of Java's) and optimize our digest hashing algorithm to take
8034 advantage of 64-bit platforms and to remove some possibly-costly
8036 - When implementing AES counter mode, update only the portions of the
8037 counter buffer that need to change, and don't keep separate
8038 network-order and host-order counters on big-endian hosts (where
8040 - Add an in-place version of aes_crypt() so that we can avoid doing a
8041 needless memcpy() call on each cell payload.
8042 - Use Critical Sections rather than Mutexes for synchronizing threads
8043 on win32; Mutexes are heavier-weight, and designed for synchronizing
8046 o Performance improvements (bandwidth use):
8047 - Don't try to launch new descriptor downloads quite so often when we
8048 already have enough directory information to build circuits.
8049 - Version 1 directories are no longer generated in full. Instead,
8050 authorities generate and serve "stub" v1 directories that list
8051 no servers. This will stop Tor versions 0.1.0.x and earlier from
8052 working, but (for security reasons) nobody should be running those
8054 - Avoid going directly to the directory authorities even if you're a
8055 relay, if you haven't found yourself reachable yet or if you've
8056 decided not to advertise your dirport yet. Addresses bug 556.
8057 - If we've gone 12 hours since our last bandwidth check, and we
8058 estimate we have less than 50KB bandwidth capacity but we could
8059 handle more, do another bandwidth test.
8060 - Support "If-Modified-Since" when answering HTTP requests for
8061 directories, running-routers documents, and v2 and v3 networkstatus
8062 documents. (There's no need to support it for router descriptors,
8063 since those are downloaded by descriptor digest.)
8064 - Stop fetching directory info so aggressively if your DirPort is
8065 on but your ORPort is off; stop fetching v2 dir info entirely.
8066 You can override these choices with the new FetchDirInfoEarly
8069 o Changed config option behavior (features):
8070 - Configuration files now accept C-style strings as values. This
8071 helps encode characters not allowed in the current configuration
8072 file format, such as newline or #. Addresses bug 557.
8073 - Add hidden services and DNSPorts to the list of things that make
8074 Tor accept that it has running ports. Change starting Tor with no
8075 ports from a fatal error to a warning; we might change it back if
8076 this turns out to confuse anybody. Fixes bug 579.
8077 - Make PublishServerDescriptor default to 1, so the default doesn't
8078 have to change as we invent new directory protocol versions.
8079 - Allow people to say PreferTunnelledDirConns rather than
8080 PreferTunneledDirConns, for those alternate-spellers out there.
8081 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
8082 accommodate the growing number of servers that use the default
8083 and are reaching it.
8084 - Make it possible to enable HashedControlPassword and
8085 CookieAuthentication at the same time.
8086 - When a TrackHostExits-chosen exit fails too many times in a row,
8087 stop using it. Fixes bug 437.
8089 o Changed config option behavior (bugfixes):
8090 - Do not read the configuration file when we've only been told to
8091 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
8092 based on patch from Sebastian Hahn.
8093 - Actually validate the options passed to AuthDirReject,
8094 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
8095 - Make "ClientOnly 1" config option disable directory ports too.
8096 - Don't stop fetching descriptors when FetchUselessDescriptors is
8097 set, even if we stop asking for circuits. Bug reported by tup
8099 - Servers used to decline to publish their DirPort if their
8100 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
8101 they look only at BandwidthRate and RelayBandwidthRate.
8102 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
8103 minus 1 byte: the actual maximum declared bandwidth.
8104 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
8105 - Make the NodeFamilies config option work. (Reported by
8106 lodger -- it has never actually worked, even though we added it
8108 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
8109 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
8111 o New config options:
8112 - New configuration options AuthDirMaxServersPerAddr and
8113 AuthDirMaxServersperAuthAddr to override default maximum number
8114 of servers allowed on a single IP address. This is important for
8115 running a test network on a single host.
8116 - Three new config options (AlternateDirAuthority,
8117 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
8118 user selectively replace the default directory authorities by type,
8119 rather than the all-or-nothing replacement that DirServer offers.
8120 - New config options AuthDirBadDir and AuthDirListBadDirs for
8121 authorities to mark certain relays as "bad directories" in the
8122 networkstatus documents. Also supports the "!baddir" directive in
8123 the approved-routers file.
8124 - New config option V2AuthoritativeDirectory that all v2 directory
8125 authorities must set. This lets v3 authorities choose not to serve
8126 v2 directory information.
8128 o Minor features (other):
8129 - When we're not serving v2 directory information, there is no reason
8130 to actually keep any around. Remove the obsolete files and directory
8131 on startup if they are very old and we aren't going to serve them.
8132 - When we negotiate a v2 link-layer connection (not yet implemented),
8133 accept RELAY_EARLY cells and turn them into RELAY cells if we've
8134 negotiated a v1 connection for their next step. Initial steps for
8136 - When we have no consensus, check FallbackNetworkstatusFile (defaults
8137 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
8138 we can start out knowing some directory caches. We don't ship with
8139 a fallback consensus by default though, because it was making
8140 bootstrapping take too long while we tried many down relays.
8141 - Authorities send back an X-Descriptor-Not-New header in response to
8142 an accepted-but-discarded descriptor upload. Partially implements
8144 - If we find a cached-routers file that's been sitting around for more
8145 than 28 days unmodified, then most likely it's a leftover from
8146 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
8148 - When we (as a cache) download a descriptor because it was listed
8149 in a consensus, remember when the consensus was supposed to expire,
8150 and don't expire the descriptor until then.
8151 - Optionally (if built with -DEXPORTMALLINFO) export the output
8152 of mallinfo via http, as tor/mallinfo.txt. Only accessible
8154 - Tag every guard node in our state file with the version that
8155 we believe added it, or with our own version if we add it. This way,
8156 if a user temporarily runs an old version of Tor and then switches
8157 back to a new one, she doesn't automatically lose her guards.
8158 - When somebody requests a list of statuses or servers, and we have
8159 none of those, return a 404 rather than an empty 200.
8160 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
8162 - Add an HSAuthorityRecordStats option that hidden service authorities
8163 can use to track statistics of overall hidden service usage without
8164 logging information that would be as useful to an attacker.
8165 - Allow multiple HiddenServicePort directives with the same virtual
8166 port; when they occur, the user is sent round-robin to one
8167 of the target ports chosen at random. Partially fixes bug 393 by
8168 adding limited ad-hoc round-robining.
8169 - Revamp file-writing logic so we don't need to have the entire
8170 contents of a file in memory at once before we write to disk. Tor,
8173 o Minor bugfixes (other):
8174 - Alter the code that tries to recover from unhandled write
8175 errors, to not try to flush onto a socket that's given us
8177 - Directory mirrors no longer include a guess at the client's IP
8178 address if the connection appears to be coming from the same /24
8179 network; it was producing too many wrong guesses.
8180 - If we're trying to flush the last bytes on a connection (for
8181 example, when answering a directory request), reset the
8182 time-to-give-up timeout every time we manage to write something
8184 - Reject router descriptors with out-of-range bandwidthcapacity or
8185 bandwidthburst values.
8186 - If we can't expand our list of entry guards (e.g. because we're
8187 using bridges or we have StrictEntryNodes set), don't mark relays
8188 down when they fail a directory request. Otherwise we're too quick
8189 to mark all our entry points down.
8190 - Authorities no longer send back "400 you're unreachable please fix
8191 it" errors to Tor servers that aren't online all the time. We're
8192 supposed to tolerate these servers now.
8193 - Let directory authorities startup even when they can't generate
8194 a descriptor immediately, e.g. because they don't know their
8196 - Correctly enforce that elements of directory objects do not appear
8197 more often than they are allowed to appear.
8198 - Stop allowing hibernating servers to be "stable" or "fast".
8199 - On Windows, we were preventing other processes from reading
8200 cached-routers while Tor was running. (Reported by janbar)
8201 - Check return values from pthread_mutex functions.
8202 - When opening /dev/null in finish_daemonize(), do not pass the
8203 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
8204 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
8206 o Controller features:
8207 - The GETCONF command now escapes and quotes configuration values
8208 that don't otherwise fit into the torrc file.
8209 - The SETCONF command now handles quoted values correctly.
8210 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
8211 ask about source, timestamp of arrival, purpose, etc. We need
8212 something like this to help Vidalia not do GeoIP lookups on bridge
8214 - Allow multiple HashedControlPassword config lines, to support
8215 multiple controller passwords.
8216 - Accept LF instead of CRLF on controller, since some software has a
8217 hard time generating real Internet newlines.
8218 - Add GETINFO values for the server status events
8219 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
8221 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
8222 GETINFO for Torstat to use until it can switch to using extrainfos.
8223 - New config option CookieAuthFile to choose a new location for the
8224 cookie authentication file, and config option
8225 CookieAuthFileGroupReadable to make it group-readable.
8226 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
8227 match requests to applications. Patch from Robert Hogan.
8228 - Add a RESOLVE command to launch hostname lookups. Original patch
8230 - Add GETINFO status/enough-dir-info to let controllers tell whether
8231 Tor has downloaded sufficient directory information. Patch from Tup.
8232 - You can now use the ControlSocket option to tell Tor to listen for
8233 controller connections on Unix domain sockets on systems that
8234 support them. Patch from Peter Palfrader.
8235 - New "GETINFO address-mappings/*" command to get address mappings
8236 with expiry information. "addr-mappings/*" is now deprecated.
8238 - Add a new config option __DisablePredictedCircuits designed for
8239 use by the controller, when we don't want Tor to build any circuits
8241 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
8242 so we can exit from the middle of the circuit.
8243 - Implement "getinfo status/circuit-established".
8244 - Implement "getinfo status/version/..." so a controller can tell
8245 whether the current version is recommended, and whether any versions
8246 are good, and how many authorities agree. Patch from "shibz".
8247 - Controllers should now specify cache=no or cache=yes when using
8248 the +POSTDESCRIPTOR command.
8249 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
8250 Robert Hogan. Fixes the first part of bug 681.
8251 - When reporting clock skew, and we know that the clock is _at least
8252 as skewed_ as some value, but we don't know the actual value,
8253 report the value as a "minimum skew."
8255 o Controller bugfixes:
8256 - Generate "STATUS_SERVER" events rather than misspelled
8257 "STATUS_SEVER" events. Caught by mwenge.
8258 - Reject controller commands over 1MB in length, so rogue
8259 processes can't run us out of memory.
8260 - Change the behavior of "getinfo status/good-server-descriptor"
8261 so it doesn't return failure when any authority disappears.
8262 - Send NAMESERVER_STATUS messages for a single failed nameserver
8264 - When the DANGEROUS_VERSION controller status event told us we're
8265 running an obsolete version, it used the string "OLD" to describe
8266 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
8267 "OBSOLETE" in both cases.
8268 - Respond to INT and TERM SIGNAL commands before we execute the
8269 signal, in case the signal shuts us down. We had a patch in
8270 0.1.2.1-alpha that tried to do this by queueing the response on
8271 the connection's buffer before shutting down, but that really
8272 isn't the same thing at all. Bug located by Matt Edman.
8273 - Provide DNS expiry times in GMT, not in local time. For backward
8274 compatibility, ADDRMAP events only provide GMT expiry in an extended
8275 field. "GETINFO address-mappings" always does the right thing.
8276 - Use CRLF line endings properly in NS events.
8277 - Make 'getinfo fingerprint' return a 551 error if we're not a
8278 server, so we match what the control spec claims we do. Reported
8280 - Fix a typo in an error message when extendcircuit fails that
8281 caused us to not follow the \r\n-based delimiter protocol. Reported
8283 - When tunneling an encrypted directory connection, and its first
8284 circuit fails, do not leave it unattached and ask the controller
8285 to deal. Fixes the second part of bug 681.
8286 - Treat some 403 responses from directory servers as INFO rather than
8287 WARN-severity events.
8289 o Portability / building / compiling:
8290 - When building with --enable-gcc-warnings, check for whether Apple's
8291 warning "-Wshorten-64-to-32" is available.
8292 - Support compilation to target iPhone; patch from cjacker huang.
8293 To build for iPhone, pass the --enable-iphone option to configure.
8294 - Port Tor to build and run correctly on Windows CE systems, using
8295 the wcecompat library. Contributed by Valerio Lupi.
8296 - Detect non-ASCII platforms (if any still exist) and refuse to
8297 build there: some of our code assumes that 'A' is 65 and so on.
8298 - Clear up some MIPSPro compiler warnings.
8299 - Make autoconf search for libevent, openssl, and zlib consistently.
8300 - Update deprecated macros in configure.in.
8301 - When warning about missing headers, tell the user to let us
8302 know if the compile succeeds anyway, so we can downgrade the
8304 - Include the current subversion revision as part of the version
8305 string: either fetch it directly if we're in an SVN checkout, do
8306 some magic to guess it if we're in an SVK checkout, or use
8307 the last-detected version if we're building from a .tar.gz.
8308 Use this version consistently in log messages.
8309 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
8310 - Read resolv.conf files correctly on platforms where read() returns
8311 partial results on small file reads.
8312 - Build without verbose warnings even on gcc 4.2 and 4.3.
8313 - On Windows, correctly detect errors when listing the contents of
8314 a directory. Fix from lodger.
8315 - Run 'make test' as part of 'make dist', so we stop releasing so
8316 many development snapshots that fail their unit tests.
8317 - Add support to detect Libevent versions in the 1.4.x series
8319 - Add command-line arguments to unit-test executable so that we can
8320 invoke any chosen test from the command line rather than having
8321 to run the whole test suite at once; and so that we can turn on
8322 logging for the unit tests.
8323 - Do not automatically run configure from autogen.sh. This
8324 non-standard behavior tended to annoy people who have built other
8326 - Fix a macro/CPP interaction that was confusing some compilers:
8327 some GCCs don't like #if/#endif pairs inside macro arguments.
8329 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
8330 Fixes bug 704; fix from Steven Murdoch.
8331 - Correctly detect transparent proxy support on Linux hosts that
8332 require in.h to be included before netfilter_ipv4.h. Patch
8335 o Logging improvements:
8336 - When we haven't had any application requests lately, don't bother
8337 logging that we have expired a bunch of descriptors.
8338 - When attempting to open a logfile fails, tell us why.
8339 - Only log guard node status when guard node status has changed.
8340 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
8341 make "INFO" 75% less verbose.
8342 - When SafeLogging is disabled, log addresses along with all TLS
8344 - Report TLS "zero return" case as a "clean close" and "IO error"
8345 as a "close". Stop calling closes "unexpected closes": existing
8346 Tors don't use SSL_close(), so having a connection close without
8347 the TLS shutdown handshake is hardly unexpected.
8348 - When we receive a consensus from the future, warn about skew.
8349 - Make "not enough dir info yet" warnings describe *why* Tor feels
8350 it doesn't have enough directory info yet.
8351 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
8352 consumers. (We already do this on HUP.)
8353 - Give more descriptive well-formedness errors for out-of-range
8354 hidden service descriptor/protocol versions.
8355 - Stop recommending that every server operator send mail to tor-ops.
8356 Resolves bug 597. Bugfix on 0.1.2.x.
8357 - Improve skew reporting: try to give the user a better log message
8358 about how skewed they are, and how much this matters.
8359 - New --quiet command-line option to suppress the default console log.
8360 Good in combination with --hash-password.
8361 - Don't complain that "your server has not managed to confirm that its
8362 ports are reachable" if we haven't been able to build any circuits
8364 - Detect the reason for failing to mmap a descriptor file we just
8365 wrote, and give a more useful log message. Fixes bug 533.
8366 - Always prepend "Bug: " to any log message about a bug.
8367 - When dumping memory usage, list bytes used in buffer memory
8369 - When running with dmalloc, dump more stats on hup and on exit.
8370 - Put a platform string (e.g. "Linux i686") in the startup log
8371 message, so when people paste just their logs, we know if it's
8372 OpenBSD or Windows or what.
8373 - When logging memory usage, break down memory used in buffers by
8375 - When we are reporting the DirServer line we just parsed, we were
8376 logging the second stanza of the key fingerprint, not the first.
8377 - Even though Windows is equally happy with / and \ as path separators,
8378 try to use \ consistently on Windows and / consistently on Unix: it
8379 makes the log messages nicer.
8380 - On OSX, stop warning the user that kqueue support in libevent is
8381 "experimental", since it seems to have worked fine for ages.
8383 o Contributed scripts and tools:
8384 - Update linux-tor-prio.sh script to allow QoS based on the uid of
8385 the Tor process. Patch from Marco Bonetti with tweaks from Mike
8387 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
8388 Unix users an easy way to script their Tor process (e.g. by
8389 adjusting bandwidth based on the time of the day).
8390 - In the exitlist script, only consider the most recently published
8391 server descriptor for each server. Also, when the user requests
8392 a list of servers that _reject_ connections to a given address,
8393 explicitly exclude the IPs that also have servers that accept
8394 connections to that address. Resolves bug 405.
8395 - Include a new contrib/tor-exit-notice.html file that exit relay
8396 operators can put on their website to help reduce abuse queries.
8398 o Newly deprecated features:
8399 - The status/version/num-versioning and status/version/num-concurring
8400 GETINFO controller options are no longer useful in the v3 directory
8401 protocol: treat them as deprecated, and warn when they're used.
8402 - The RedirectExits config option is now deprecated.
8405 - Drop the old code to choke directory connections when the
8406 corresponding OR connections got full: thanks to the cell queue
8407 feature, OR conns don't get full any more.
8408 - Remove the old "dns worker" server DNS code: it hasn't been default
8409 since 0.1.2.2-alpha, and all the servers are using the new
8411 - Remove the code to generate the oldest (v1) directory format.
8412 - Remove support for the old bw_accounting file: we've been storing
8413 bandwidth accounting information in the state file since
8414 0.1.2.5-alpha. This may result in bandwidth accounting errors
8415 if you try to upgrade from 0.1.1.x or earlier, or if you try to
8416 downgrade to 0.1.1.x or earlier.
8417 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
8418 it, it had no AES, and it hasn't seen any security patches since
8420 - Stop overloading the circuit_t.onionskin field for both "onionskin
8421 from a CREATE cell that we are waiting for a cpuworker to be
8422 assigned" and "onionskin from an EXTEND cell that we are going to
8423 send to an OR as soon as we are connected". Might help with bug 600.
8424 - Remove the tor_strpartition() function: its logic was confused,
8425 and it was only used for one thing that could be implemented far
8427 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
8428 and TorControl.py, as they use the old v0 controller protocol,
8429 and are obsoleted by TorFlow anyway.
8430 - Drop support for v1 rendezvous descriptors, since we never used
8431 them anyway, and the code has probably rotted by now. Based on
8432 patch from Karsten Loesing.
8433 - Stop allowing address masks that do not correspond to bit prefixes.
8434 We have warned about these for a really long time; now it's time
8435 to reject them. (Patch from croup.)
8436 - Remove an optimization in the AES counter-mode code that assumed
8437 that the counter never exceeded 2^68. When the counter can be set
8438 arbitrarily as an IV (as it is by Karsten's new hidden services
8439 code), this assumption no longer holds.
8440 - Disable the SETROUTERPURPOSE controller command: it is now
8444 Changes in version 0.1.2.19 - 2008-01-17
8445 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
8446 exit policy a little bit more conservative so it's safer to run an
8447 exit relay on a home system, and fixes a variety of smaller issues.
8450 - Exit policies now reject connections that are addressed to a
8451 relay's public (external) IP address too, unless
8452 ExitPolicyRejectPrivate is turned off. We do this because too
8453 many relays are running nearby to services that trust them based
8457 - When the clock jumps forward a lot, do not allow the bandwidth
8458 buckets to become negative. Fixes bug 544.
8459 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
8460 on every successful resolve. Reported by Mike Perry.
8461 - Purge old entries from the "rephist" database and the hidden
8462 service descriptor database even when DirPort is zero.
8463 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
8464 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
8465 crashing or mis-answering these requests.
8466 - When we decide to send a 503 response to a request for servers, do
8467 not then also send the server descriptors: this defeats the whole
8468 purpose. Fixes bug 539.
8471 - Changing the ExitPolicyRejectPrivate setting should cause us to
8472 rebuild our server descriptor.
8473 - Fix handling of hex nicknames when answering controller requests for
8474 networkstatus by name, or when deciding whether to warn about
8475 unknown routers in a config option. (Patch from mwenge.)
8476 - Fix a couple of hard-to-trigger autoconf problems that could result
8477 in really weird results on platforms whose sys/types.h files define
8478 nonstandard integer types.
8479 - Don't try to create the datadir when running --verify-config or
8480 --hash-password. Resolves bug 540.
8481 - If we were having problems getting a particular descriptor from the
8482 directory caches, and then we learned about a new descriptor for
8483 that router, we weren't resetting our failure count. Reported
8485 - Although we fixed bug 539 (where servers would send HTTP status 503
8486 responses _and_ send a body too), there are still servers out there
8487 that haven't upgraded. Therefore, make clients parse such bodies
8488 when they receive them.
8489 - Run correctly on systems where rlim_t is larger than unsigned long.
8490 This includes some 64-bit systems.
8491 - Run correctly on platforms (like some versions of OS X 10.5) where
8492 the real limit for number of open files is OPEN_FILES, not rlim_max
8493 from getrlimit(RLIMIT_NOFILES).
8494 - Avoid a spurious free on base64 failure.
8495 - Avoid segfaults on certain complex invocations of
8496 router_get_by_hexdigest().
8497 - Fix rare bug on REDIRECTSTREAM control command when called with no
8498 port set: it could erroneously report an error when none had
8502 Changes in version 0.1.2.18 - 2007-10-28
8503 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
8504 hidden service introduction that were causing huge delays, and a big
8505 bug that was causing some servers to disappear from the network status
8506 lists for a few hours each day.
8508 o Major bugfixes (crashes):
8509 - If a connection is shut down abruptly because of something that
8510 happened inside connection_flushed_some(), do not call
8511 connection_finished_flushing(). Should fix bug 451:
8512 "connection_stop_writing: Assertion conn->write_event failed"
8513 Bugfix on 0.1.2.7-alpha.
8514 - Fix possible segfaults in functions called from
8515 rend_process_relay_cell().
8517 o Major bugfixes (hidden services):
8518 - Hidden services were choosing introduction points uniquely by
8519 hexdigest, but when constructing the hidden service descriptor
8520 they merely wrote the (potentially ambiguous) nickname.
8521 - Clients now use the v2 intro format for hidden service
8522 connections: they specify their chosen rendezvous point by identity
8523 digest rather than by (potentially ambiguous) nickname. These
8524 changes could speed up hidden service connections dramatically.
8526 o Major bugfixes (other):
8527 - Stop publishing a new server descriptor just because we get a
8528 HUP signal. This led (in a roundabout way) to some servers getting
8529 dropped from the networkstatus lists for a few hours each day.
8530 - When looking for a circuit to cannibalize, consider family as well
8531 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
8532 circuit cannibalization).
8533 - When a router wasn't listed in a new networkstatus, we were leaving
8534 the flags for that router alone -- meaning it remained Named,
8535 Running, etc -- even though absence from the networkstatus means
8536 that it shouldn't be considered to exist at all anymore. Now we
8537 clear all the flags for routers that fall out of the networkstatus
8538 consensus. Fixes bug 529.
8541 - Don't try to access (or alter) the state file when running
8542 --list-fingerprint or --verify-config or --hash-password. Resolves
8544 - When generating information telling us how to extend to a given
8545 router, do not try to include the nickname if it is
8546 absent. Resolves bug 467.
8547 - Fix a user-triggerable segfault in expand_filename(). (There isn't
8548 a way to trigger this remotely.)
8549 - When sending a status event to the controller telling it that an
8550 OR address is reachable, set the port correctly. (Previously we
8551 were reporting the dir port.)
8552 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
8553 command. Bugfix on 0.1.2.17.
8554 - When loading bandwidth history, do not believe any information in
8555 the future. Fixes bug 434.
8556 - When loading entry guard information, do not believe any information
8558 - When we have our clock set far in the future and generate an
8559 onion key, then re-set our clock to be correct, we should not stop
8560 the onion key from getting rotated.
8561 - On some platforms, accept() can return a broken address. Detect
8562 this more quietly, and deal accordingly. Fixes bug 483.
8563 - It's not actually an error to find a non-pending entry in the DNS
8564 cache when canceling a pending resolve. Don't log unless stuff
8565 is fishy. Resolves bug 463.
8566 - Don't reset trusted dir server list when we set a configuration
8567 option. Patch from Robert Hogan.
8570 Changes in version 0.1.2.17 - 2007-08-30
8571 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
8572 X bundles. Vidalia 0.0.14 makes authentication required for the
8573 ControlPort in the default configuration, which addresses important
8574 security risks. Everybody who uses Vidalia (or another controller)
8577 In addition, this Tor update fixes major load balancing problems with
8578 path selection, which should speed things up a lot once many people
8581 o Major bugfixes (security):
8582 - We removed support for the old (v0) control protocol. It has been
8583 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
8584 become more of a headache than it's worth.
8586 o Major bugfixes (load balancing):
8587 - When choosing nodes for non-guard positions, weight guards
8588 proportionally less, since they already have enough load. Patch
8590 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
8591 will allow fast Tor servers to get more attention.
8592 - When we're upgrading from an old Tor version, forget our current
8593 guards and pick new ones according to the new weightings. These
8594 three load balancing patches could raise effective network capacity
8595 by a factor of four. Thanks to Mike Perry for measurements.
8597 o Major bugfixes (stream expiration):
8598 - Expire not-yet-successful application streams in all cases if
8599 they've been around longer than SocksTimeout. Right now there are
8600 some cases where the stream will live forever, demanding a new
8601 circuit every 15 seconds. Fixes bug 454; reported by lodger.
8603 o Minor features (controller):
8604 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
8605 is valid before any authentication has been received. It tells
8606 a controller what kind of authentication is expected, and what
8607 protocol is spoken. Implements proposal 119.
8609 o Minor bugfixes (performance):
8610 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
8611 greatly speeding up loading cached-routers from disk on startup.
8612 - Disable sentinel-based debugging for buffer code: we squashed all
8613 the bugs that this was supposed to detect a long time ago, and now
8614 its only effect is to change our buffer sizes from nice powers of
8615 two (which platform mallocs tend to like) to values slightly over
8616 powers of two (which make some platform mallocs sad).
8618 o Minor bugfixes (misc):
8619 - If exit bandwidth ever exceeds one third of total bandwidth, then
8620 use the correct formula to weight exit nodes when choosing paths.
8621 Based on patch from Mike Perry.
8622 - Choose perfectly fairly among routers when choosing by bandwidth and
8623 weighting by fraction of bandwidth provided by exits. Previously, we
8624 would choose with only approximate fairness, and correct ourselves
8625 if we ran off the end of the list.
8626 - If we require CookieAuthentication but we fail to write the
8627 cookie file, we would warn but not exit, and end up in a state
8628 where no controller could authenticate. Now we exit.
8629 - If we require CookieAuthentication, stop generating a new cookie
8630 every time we change any piece of our config.
8631 - Refuse to start with certain directory authority keys, and
8632 encourage people using them to stop.
8633 - Terminate multi-line control events properly. Original patch
8635 - Fix a minor memory leak when we fail to find enough suitable
8636 servers to choose a circuit.
8637 - Stop leaking part of the descriptor when we run into a particularly
8638 unparseable piece of it.
8641 Changes in version 0.1.2.16 - 2007-08-01
8642 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
8643 remote attacker in certain situations to rewrite the user's torrc
8644 configuration file. This can completely compromise anonymity of users
8645 in most configurations, including those running the Vidalia bundles,
8646 TorK, etc. Or worse.
8648 o Major security fixes:
8649 - Close immediately after missing authentication on control port;
8650 do not allow multiple authentication attempts.
8653 Changes in version 0.1.2.15 - 2007-07-17
8654 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
8655 problems, fixes compilation on BSD, and fixes a variety of other
8656 bugs. Everybody should upgrade.
8658 o Major bugfixes (compilation):
8659 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
8661 o Major bugfixes (crashes):
8662 - Try even harder not to dereference the first character after
8663 an mmap(). Reported by lodger.
8664 - Fix a crash bug in directory authorities when we re-number the
8665 routerlist while inserting a new router.
8666 - When the cached-routers file is an even multiple of the page size,
8667 don't run off the end and crash. (Fixes bug 455; based on idea
8669 - Fix eventdns.c behavior on Solaris: It is critical to include
8670 orconfig.h _before_ sys/types.h, so that we can get the expected
8671 definition of _FILE_OFFSET_BITS.
8673 o Major bugfixes (security):
8674 - Fix a possible buffer overrun when using BSD natd support. Bug
8676 - When sending destroy cells from a circuit's origin, don't include
8677 the reason for tearing down the circuit. The spec says we didn't,
8678 and now we actually don't. Reported by lodger.
8679 - Keep streamids from different exits on a circuit separate. This
8680 bug may have allowed other routers on a given circuit to inject
8681 cells into streams. Reported by lodger; fixes bug 446.
8682 - If there's a never-before-connected-to guard node in our list,
8683 never choose any guards past it. This way we don't expand our
8684 guard list unless we need to.
8686 o Minor bugfixes (guard nodes):
8687 - Weight guard selection by bandwidth, so that low-bandwidth nodes
8688 don't get overused as guards.
8690 o Minor bugfixes (directory):
8691 - Correctly count the number of authorities that recommend each
8692 version. Previously, we were under-counting by 1.
8693 - Fix a potential crash bug when we load many server descriptors at
8694 once and some of them make others of them obsolete. Fixes bug 458.
8696 o Minor bugfixes (hidden services):
8697 - Stop tearing down the whole circuit when the user asks for a
8698 connection to a port that the hidden service didn't configure.
8701 o Minor bugfixes (misc):
8702 - On Windows, we were preventing other processes from reading
8703 cached-routers while Tor was running. Reported by janbar.
8704 - Fix a possible (but very unlikely) bug in picking routers by
8705 bandwidth. Add a log message to confirm that it is in fact
8706 unlikely. Patch from lodger.
8707 - Backport a couple of memory leak fixes.
8708 - Backport miscellaneous cosmetic bugfixes.
8711 Changes in version 0.1.2.14 - 2007-05-25
8712 Tor 0.1.2.14 changes the addresses of two directory authorities (this
8713 change especially affects those who serve or use hidden services),
8714 and fixes several other crash- and security-related bugs.
8716 o Directory authority changes:
8717 - Two directory authorities (moria1 and moria2) just moved to new
8718 IP addresses. This change will particularly affect those who serve
8719 or use hidden services.
8721 o Major bugfixes (crashes):
8722 - If a directory server runs out of space in the connection table
8723 as it's processing a begin_dir request, it will free the exit stream
8724 but leave it attached to the circuit, leading to unpredictable
8725 behavior. (Reported by seeess, fixes bug 425.)
8726 - Fix a bug in dirserv_remove_invalid() that would cause authorities
8727 to corrupt memory under some really unlikely scenarios.
8728 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
8729 - Avoid segfaults when reading from mmaped descriptor file. (Reported
8732 o Major bugfixes (security):
8733 - When choosing an entry guard for a circuit, avoid using guards
8734 that are in the same family as the chosen exit -- not just guards
8735 that are exactly the chosen exit. (Reported by lodger.)
8737 o Major bugfixes (resource management):
8738 - If a directory authority is down, skip it when deciding where to get
8739 networkstatus objects or descriptors. Otherwise we keep asking
8740 every 10 seconds forever. Fixes bug 384.
8741 - Count it as a failure if we fetch a valid network-status but we
8742 don't want to keep it. Otherwise we'll keep fetching it and keep
8743 not wanting to keep it. Fixes part of bug 422.
8744 - If all of our dirservers have given us bad or no networkstatuses
8745 lately, then stop hammering them once per minute even when we
8746 think they're failed. Fixes another part of bug 422.
8749 - Actually set the purpose correctly for descriptors inserted with
8751 - When we have k non-v2 authorities in our DirServer config,
8752 we ignored the last k authorities in the list when updating our
8754 - Correctly back-off from requesting router descriptors that we are
8755 having a hard time downloading.
8756 - Read resolv.conf files correctly on platforms where read() returns
8757 partial results on small file reads.
8758 - Don't rebuild the entire router store every time we get 32K of
8759 routers: rebuild it when the journal gets very large, or when
8760 the gaps in the store get very large.
8763 - When routers publish SVN revisions in their router descriptors,
8764 authorities now include those versions correctly in networkstatus
8766 - Warn when using a version of libevent before 1.3b to run a server on
8767 OSX or BSD: these versions interact badly with userspace threads.
8770 Changes in version 0.1.2.13 - 2007-04-24
8771 This release features some major anonymity fixes, such as safer path
8772 selection; better client performance; faster bootstrapping, better
8773 address detection, and better DNS support for servers; write limiting as
8774 well as read limiting to make servers easier to run; and a huge pile of
8775 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
8777 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
8778 of the Freenode IRC network, remembering his patience and vision for
8779 free speech on the Internet.
8781 o Major features, client performance:
8782 - Weight directory requests by advertised bandwidth. Now we can
8783 let servers enable write limiting but still allow most clients to
8784 succeed at their directory requests. (We still ignore weights when
8785 choosing a directory authority; I hope this is a feature.)
8786 - Stop overloading exit nodes -- avoid choosing them for entry or
8787 middle hops when the total bandwidth available from non-exit nodes
8788 is much higher than the total bandwidth available from exit nodes.
8789 - Rather than waiting a fixed amount of time between retrying
8790 application connections, we wait only 10 seconds for the first,
8791 10 seconds for the second, and 15 seconds for each retry after
8792 that. Hopefully this will improve the expected user experience.
8793 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
8794 to open a stream fails; now we do in more cases. This should
8795 make clients able to find a good exit faster in some cases, since
8796 unhandleable requests will now get an error rather than timing out.
8798 o Major features, client functionality:
8799 - Implement BEGIN_DIR cells, so we can connect to a directory
8800 server via TLS to do encrypted directory requests rather than
8801 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
8802 config options if you like. For now, this feature only works if
8803 you already have a descriptor for the destination dirserver.
8804 - Add support for transparent application connections: this basically
8805 bundles the functionality of trans-proxy-tor into the Tor
8806 mainline. Now hosts with compliant pf/netfilter implementations
8807 can redirect TCP connections straight to Tor without diverting
8808 through SOCKS. (Based on patch from tup.)
8809 - Add support for using natd; this allows FreeBSDs earlier than
8810 5.1.2 to have ipfw send connections through Tor without using
8811 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
8813 o Major features, servers:
8814 - Setting up a dyndns name for your server is now optional: servers
8815 with no hostname or IP address will learn their IP address by
8816 asking the directory authorities. This code only kicks in when you
8817 would normally have exited with a "no address" error. Nothing's
8818 authenticated, so use with care.
8819 - Directory servers now spool server descriptors, v1 directories,
8820 and v2 networkstatus objects to buffers as needed rather than en
8821 masse. They also mmap the cached-routers files. These steps save
8823 - Stop requiring clients to have well-formed certificates, and stop
8824 checking nicknames in certificates. (Clients have certificates so
8825 that they can look like Tor servers, but in the future we might want
8826 to allow them to look like regular TLS clients instead. Nicknames
8827 in certificates serve no purpose other than making our protocol
8828 easier to recognize on the wire.) Implements proposal 106.
8830 o Improvements on DNS support:
8831 - Add "eventdns" asynchronous dns library originally based on code
8832 from Adam Langley. Now we can discard the old rickety dnsworker
8833 concept, and support a wider variety of DNS functions. Allows
8834 multithreaded builds on NetBSD and OpenBSD again.
8835 - Add server-side support for "reverse" DNS lookups (using PTR
8836 records so clients can determine the canonical hostname for a given
8837 IPv4 address). Only supported by servers using eventdns; servers
8838 now announce in their descriptors if they don't support eventdns.
8839 - Workaround for name servers (like Earthlink's) that hijack failing
8840 DNS requests and replace the no-such-server answer with a "helpful"
8841 redirect to an advertising-driven search portal. Also work around
8842 DNS hijackers who "helpfully" decline to hijack known-invalid
8843 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
8844 lets you turn it off.
8845 - Servers now check for the case when common DNS requests are going to
8846 wildcarded addresses (i.e. all getting the same answer), and change
8847 their exit policy to reject *:* if it's happening.
8848 - When asked to resolve a hostname, don't use non-exit servers unless
8849 requested to do so. This allows servers with broken DNS to be
8850 useful to the network.
8851 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
8852 useless IPv6 DNS resolves.
8853 - Specify and implement client-side SOCKS5 interface for reverse DNS
8854 lookups (see doc/socks-extensions.txt). Also cache them.
8855 - When we change nameservers or IP addresses, reset and re-launch
8856 our tests for DNS hijacking.
8858 o Improvements on reachability testing:
8859 - Servers send out a burst of long-range padding cells once they've
8860 established that they're reachable. Spread them over 4 circuits,
8861 so hopefully a few will be fast. This exercises bandwidth and
8862 bootstraps them into the directory more quickly.
8863 - When we find our DirPort to be reachable, publish a new descriptor
8864 so we'll tell the world (reported by pnx).
8865 - Directory authorities now only decide that routers are reachable
8866 if their identity keys are as expected.
8867 - Do DirPort reachability tests less often, since a single test
8868 chews through many circuits before giving up.
8869 - Avoid some false positives during reachability testing: don't try
8870 to test via a server that's on the same /24 network as us.
8871 - Start publishing one minute or so after we find our ORPort
8872 to be reachable. This will help reduce the number of descriptors
8873 we have for ourselves floating around, since it's quite likely
8874 other things (e.g. DirPort) will change during that minute too.
8875 - Routers no longer try to rebuild long-term connections to directory
8876 authorities, and directory authorities no longer try to rebuild
8877 long-term connections to all servers. We still don't hang up
8878 connections in these two cases though -- we need to look at it
8879 more carefully to avoid flapping, and we likely need to wait til
8880 0.1.1.x is obsolete.
8882 o Improvements on rate limiting:
8883 - Enable write limiting as well as read limiting. Now we sacrifice
8884 capacity if we're pushing out lots of directory traffic, rather
8885 than overrunning the user's intended bandwidth limits.
8886 - Include TLS overhead when counting bandwidth usage; previously, we
8887 would count only the bytes sent over TLS, but not the bytes used
8889 - Servers decline directory requests much more aggressively when
8890 they're low on bandwidth. Otherwise they end up queueing more and
8891 more directory responses, which can't be good for latency.
8892 - But never refuse directory requests from local addresses.
8893 - Be willing to read or write on local connections (e.g. controller
8894 connections) even when the global rate limiting buckets are empty.
8895 - Flush local controller connection buffers periodically as we're
8896 writing to them, so we avoid queueing 4+ megabytes of data before
8898 - Revise and clean up the torrc.sample that we ship with; add
8899 a section for BandwidthRate and BandwidthBurst.
8901 o Major features, NT services:
8902 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
8903 command-line flag so that admins can override the default by saying
8904 "tor --service install --user "SomeUser"". This will not affect
8905 existing installed services. Also, warn the user that the service
8906 will look for its configuration file in the service user's
8907 %appdata% directory. (We can't do the "hardwire the user's appdata
8908 directory" trick any more, since we may not have read access to that
8910 - Support running the Tor service with a torrc not in the same
8911 directory as tor.exe and default to using the torrc located in
8912 the %appdata%\Tor\ of the user who installed the service. Patch
8914 - Add an --ignore-missing-torrc command-line option so that we can
8915 get the "use sensible defaults if the configuration file doesn't
8916 exist" behavior even when specifying a torrc location on the
8918 - When stopping an NT service, wait up to 10 sec for it to actually
8919 stop. (Patch from Matt Edman; resolves bug 295.)
8921 o Directory authority improvements:
8922 - Stop letting hibernating or obsolete servers affect uptime and
8924 - Stop listing hibernating servers in the v1 directory.
8925 - Authorities no longer recommend exits as guards if this would shift
8926 too much load to the exit nodes.
8927 - Authorities now specify server versions in networkstatus. This adds
8928 about 2% to the size of compressed networkstatus docs, and allows
8929 clients to tell which servers support BEGIN_DIR and which don't.
8930 The implementation is forward-compatible with a proposed future
8931 protocol version scheme not tied to Tor versions.
8932 - DirServer configuration lines now have an orport= option so
8933 clients can open encrypted tunnels to the authorities without
8934 having downloaded their descriptors yet. Enabled for moria1,
8935 moria2, tor26, and lefkada now in the default configuration.
8936 - Add a BadDirectory flag to network status docs so that authorities
8937 can (eventually) tell clients about caches they believe to be
8938 broken. Not used yet.
8939 - Allow authorities to list nodes as bad exits in their
8940 approved-routers file by fingerprint or by address. If most
8941 authorities set a BadExit flag for a server, clients don't think
8942 of it as a general-purpose exit. Clients only consider authorities
8943 that advertise themselves as listing bad exits.
8944 - Patch from Steve Hildrey: Generate network status correctly on
8945 non-versioning dirservers.
8946 - Have directory authorities allow larger amounts of drift in uptime
8947 without replacing the server descriptor: previously, a server that
8948 restarted every 30 minutes could have 48 "interesting" descriptors
8950 - Reserve the nickname "Unnamed" for routers that can't pick
8951 a hostname: any router can call itself Unnamed; directory
8952 authorities will never allocate Unnamed to any particular router;
8953 clients won't believe that any router is the canonical Unnamed.
8955 o Directory mirrors and clients:
8956 - Discard any v1 directory info that's over 1 month old (for
8957 directories) or over 1 week old (for running-routers lists).
8958 - Clients track responses with status 503 from dirservers. After a
8959 dirserver has given us a 503, we try not to use it until an hour has
8960 gone by, or until we have no dirservers that haven't given us a 503.
8961 - When we get a 503 from a directory, and we're not a server, we no
8962 longer count the failure against the total number of failures
8963 allowed for the object we're trying to download.
8964 - Prepare for servers to publish descriptors less often: never
8965 discard a descriptor simply for being too old until either it is
8966 recommended by no authorities, or until we get a better one for
8967 the same router. Make caches consider retaining old recommended
8968 routers for even longer.
8969 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
8970 headers for content, so that we can work better in the presence of
8971 caching HTTP proxies.
8972 - Stop fetching descriptors if you're not a dir mirror and you
8973 haven't tried to establish any circuits lately. (This currently
8974 causes some dangerous behavior, because when you start up again
8975 you'll use your ancient server descriptors.)
8977 o Major fixes, crashes:
8978 - Stop crashing when the controller asks us to resetconf more than
8979 one config option at once. (Vidalia 0.0.11 does this.)
8980 - Fix a longstanding obscure crash bug that could occur when we run
8981 out of DNS worker processes, if we're not using eventdns. (Resolves
8983 - Fix an assert that could trigger if a controller quickly set then
8984 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
8985 - Avoid crash when telling controller about stream-status and a
8987 - Avoid sending junk to controllers or segfaulting when a controller
8988 uses EVENT_NEW_DESC with verbose nicknames.
8989 - Stop triggering asserts if the controller tries to extend hidden
8990 service circuits (reported by mwenge).
8991 - If we start a server with ClientOnly 1, then set ClientOnly to 0
8992 and hup, stop triggering an assert based on an empty onion_key.
8993 - Mask out all signals in sub-threads; only the libevent signal
8994 handler should be processing them. This should prevent some crashes
8995 on some machines using pthreads. (Patch from coderman.)
8996 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
8998 o Major fixes, anonymity/security:
8999 - Automatically avoid picking more than one node from the same
9000 /16 network when constructing a circuit. Add an
9001 "EnforceDistinctSubnets" option to let people disable it if they
9002 want to operate private test networks on a single subnet.
9003 - When generating bandwidth history, round down to the nearest
9004 1k. When storing accounting data, round up to the nearest 1k.
9005 - When we're running as a server, remember when we last rotated onion
9006 keys, so that we will rotate keys once they're a week old even if
9007 we never stay up for a week ourselves.
9008 - If a client asked for a server by name, and there's a named server
9009 in our network-status but we don't have its descriptor yet, we
9010 could return an unnamed server instead.
9011 - Reject (most) attempts to use Tor circuits with length one. (If
9012 many people start using Tor as a one-hop proxy, exit nodes become
9013 a more attractive target for compromise.)
9014 - Just because your DirPort is open doesn't mean people should be
9015 able to remotely teach you about hidden service descriptors. Now
9016 only accept rendezvous posts if you've got HSAuthoritativeDir set.
9017 - Fix a potential race condition in the rpm installer. Found by
9019 - Do not log IPs with TLS failures for incoming TLS
9020 connections. (Fixes bug 382.)
9022 o Major fixes, other:
9023 - If our system clock jumps back in time, don't publish a negative
9024 uptime in the descriptor.
9025 - When we start during an accounting interval before it's time to wake
9026 up, remember to wake up at the correct time. (May fix bug 342.)
9027 - Previously, we would cache up to 16 old networkstatus documents
9028 indefinitely, if they came from nontrusted authorities. Now we
9029 discard them if they are more than 10 days old.
9030 - When we have a state file we cannot parse, tell the user and
9031 move it aside. Now we avoid situations where the user starts
9032 Tor in 1904, Tor writes a state file with that timestamp in it,
9033 the user fixes her clock, and Tor refuses to start.
9034 - Publish a new descriptor after we hup/reload. This is important
9035 if our config has changed such that we'll want to start advertising
9036 our DirPort now, etc.
9037 - If we are using an exit enclave and we can't connect, e.g. because
9038 its webserver is misconfigured to not listen on localhost, then
9039 back off and try connecting from somewhere else before we fail.
9041 o New config options or behaviors:
9042 - When EntryNodes are configured, rebuild the guard list to contain,
9043 in order: the EntryNodes that were guards before; the rest of the
9044 EntryNodes; the nodes that were guards before.
9045 - Do not warn when individual nodes in the configuration's EntryNodes,
9046 ExitNodes, etc are down: warn only when all possible nodes
9047 are down. (Fixes bug 348.)
9048 - Put a lower-bound on MaxAdvertisedBandwidth.
9049 - Start using the state file to store bandwidth accounting data:
9050 the bw_accounting file is now obsolete. We'll keep generating it
9051 for a while for people who are still using 0.1.2.4-alpha.
9052 - Try to batch changes to the state file so that we do as few
9053 disk writes as possible while still storing important things in
9055 - The state file and the bw_accounting file get saved less often when
9056 the AvoidDiskWrites config option is set.
9057 - Make PIDFile work on Windows.
9058 - Add internal descriptions for a bunch of configuration options:
9059 accessible via controller interface and in comments in saved
9061 - Reject *:563 (NNTPS) in the default exit policy. We already reject
9062 NNTP by default, so this seems like a sensible addition.
9063 - Clients now reject hostnames with invalid characters. This should
9064 avoid some inadvertent info leaks. Add an option
9065 AllowNonRFC953Hostnames to disable this behavior, in case somebody
9066 is running a private network with hosts called @, !, and #.
9067 - Check for addresses with invalid characters at the exit as well,
9068 and warn less verbosely when they fail. You can override this by
9069 setting ServerDNSAllowNonRFC953Addresses to 1.
9070 - Remove some options that have been deprecated since at least
9071 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
9072 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
9073 to set log options. Mark PathlenCoinWeight as obsolete.
9074 - Stop accepting certain malformed ports in configured exit policies.
9075 - When the user uses bad syntax in the Log config line, stop
9076 suggesting other bad syntax as a replacement.
9077 - Add new config option "ResolvConf" to let the server operator
9078 choose an alternate resolve.conf file when using eventdns.
9079 - If one of our entry guards is on the ExcludeNodes list, or the
9080 directory authorities don't think it's a good guard, treat it as
9081 if it were unlisted: stop using it as a guard, and throw it off
9082 the guards list if it stays that way for a long time.
9083 - Allow directory authorities to be marked separately as authorities
9084 for the v1 directory protocol, the v2 directory protocol, and
9085 as hidden service directories, to make it easier to retire old
9086 authorities. V1 authorities should set "HSAuthoritativeDir 1"
9087 to continue being hidden service authorities too.
9088 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
9089 - Make TrackExitHosts case-insensitive, and fix the behavior of
9090 ".suffix" TrackExitHosts items to avoid matching in the middle of
9092 - New DirPort behavior: if you have your dirport set, you download
9093 descriptors aggressively like a directory mirror, whether or not
9097 - Create a new file ReleaseNotes which was the old ChangeLog. The
9098 new ChangeLog file now includes the notes for all development
9100 - Add a new address-spec.txt document to describe our special-case
9101 addresses: .exit, .onion, and .noconnnect.
9102 - Fork the v1 directory protocol into its own spec document,
9103 and mark dir-spec.txt as the currently correct (v2) spec.
9105 o Packaging, porting, and contrib
9106 - "tor --verify-config" now exits with -1(255) or 0 depending on
9107 whether the config options are bad or good.
9108 - The Debian package now uses --verify-config when (re)starting,
9109 to distinguish configuration errors from other errors.
9110 - Adapt a patch from goodell to let the contrib/exitlist script
9111 take arguments rather than require direct editing.
9112 - Prevent the contrib/exitlist script from printing the same
9113 result more than once.
9114 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
9115 - In the hidden service example in torrc.sample, stop recommending
9116 esoteric and discouraged hidden service options.
9117 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
9118 values before failing, and always enables eventdns.
9119 - Try to detect Windows correctly when cross-compiling.
9120 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
9121 Try to fix this in configure.in by checking for most functions
9122 before we check for libevent.
9123 - Update RPMs to require libevent 1.2.
9124 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
9125 or later. Log when we are doing this, so we can diagnose it when
9126 it fails. (Also, recommend libevent 1.1b for kqueue and
9127 win32 methods; deprecate libevent 1.0b harder; make libevent
9128 recommendation system saner.)
9129 - Build with recent (1.3+) libevents on platforms that do not
9130 define the nonstandard types "u_int8_t" and friends.
9131 - Remove architecture from OS X builds. The official builds are
9132 now universal binaries.
9133 - Run correctly on OS X platforms with case-sensitive filesystems.
9134 - Correctly set maximum connection limit on Cygwin. (This time
9136 - Start compiling on MinGW on Windows (patches from Mike Chiussi
9138 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
9139 - Finally fix the openssl warnings from newer gccs that believe that
9140 ignoring a return value is okay, but casting a return value and
9141 then ignoring it is a sign of madness.
9142 - On architectures where sizeof(int)>4, still clamp declarable
9143 bandwidth to INT32_MAX.
9145 o Minor features, controller:
9146 - Warn the user when an application uses the obsolete binary v0
9147 control protocol. We're planning to remove support for it during
9148 the next development series, so it's good to give people some
9150 - Add STREAM_BW events to report per-entry-stream bandwidth
9151 use. (Patch from Robert Hogan.)
9152 - Rate-limit SIGNEWNYM signals in response to controllers that
9153 impolitely generate them for every single stream. (Patch from
9154 mwenge; closes bug 394.)
9155 - Add a REMAP status to stream events to note that a stream's
9156 address has changed because of a cached address or a MapAddress
9158 - Make REMAP stream events have a SOURCE (cache or exit), and
9159 make them generated in every case where we get a successful
9160 connected or resolved cell.
9161 - Track reasons for OR connection failure; make these reasons
9162 available via the controller interface. (Patch from Mike Perry.)
9163 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
9164 can learn when clients are sending malformed hostnames to Tor.
9165 - Specify and implement some of the controller status events.
9166 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
9167 - Reimplement GETINFO so that info/names stays in sync with the
9169 - Implement "GETINFO fingerprint".
9170 - Implement "SETEVENTS GUARD" so controllers can get updates on
9171 entry guard status as it changes.
9172 - Make all connections to addresses of the form ".noconnect"
9173 immediately get closed. This lets application/controller combos
9174 successfully test whether they're talking to the same Tor by
9175 watching for STREAM events.
9176 - Add a REASON field to CIRC events; for backward compatibility, this
9177 field is sent only to controllers that have enabled the extended
9178 event format. Also, add additional reason codes to explain why
9179 a given circuit has been destroyed or truncated. (Patches from
9181 - Add a REMOTE_REASON field to extended CIRC events to tell the
9182 controller why a remote OR told us to close a circuit.
9183 - Stream events also now have REASON and REMOTE_REASON fields,
9184 working much like those for circuit events.
9185 - There's now a GETINFO ns/... field so that controllers can ask Tor
9186 about the current status of a router.
9187 - A new event type "NS" to inform a controller when our opinion of
9188 a router's status has changed.
9189 - Add a GETINFO events/names and GETINFO features/names so controllers
9190 can tell which events and features are supported.
9191 - A new CLEARDNSCACHE signal to allow controllers to clear the
9192 client-side DNS cache without expiring circuits.
9193 - Fix CIRC controller events so that controllers can learn the
9194 identity digests of non-Named servers used in circuit paths.
9195 - Let controllers ask for more useful identifiers for servers. Instead
9196 of learning identity digests for un-Named servers and nicknames
9197 for Named servers, the new identifiers include digest, nickname,
9198 and indication of Named status. Off by default; see control-spec.txt
9199 for more information.
9200 - Add a "getinfo address" controller command so it can display Tor's
9201 best guess to the user.
9202 - New controller event to alert the controller when our server
9203 descriptor has changed.
9204 - Give more meaningful errors on controller authentication failure.
9205 - Export the default exit policy via the control port, so controllers
9206 don't need to guess what it is / will be later.
9208 o Minor bugfixes, controller:
9209 - When creating a circuit via the controller, send a 'launched'
9210 event when we're done, so we follow the spec better.
9211 - Correct the control spec to match how the code actually responds
9212 to 'getinfo addr-mappings/*'. Reported by daejees.
9213 - The control spec described a GUARDS event, but the code
9214 implemented a GUARD event. Standardize on GUARD, but let people
9215 ask for GUARDS too. Reported by daejees.
9216 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
9217 clear the corresponding on_circuit variable, and remember later
9218 that we don't need to send a redundant CLOSED event. (Resolves part
9220 - Report events where a resolve succeeded or where we got a socks
9221 protocol error correctly, rather than calling both of them
9223 - Change reported stream target addresses to IP consistently when
9224 we finally get the IP from an exit node.
9225 - Send log messages to the controller even if they happen to be very
9227 - Flush ERR-level controller status events just like we currently
9228 flush ERR-level log events, so that a Tor shutdown doesn't prevent
9229 the controller from learning about current events.
9230 - Report the circuit number correctly in STREAM CLOSED events. Bug
9231 reported by Mike Perry.
9232 - Do not report bizarre values for results of accounting GETINFOs
9233 when the last second's write or read exceeds the allotted bandwidth.
9234 - Report "unrecognized key" rather than an empty string when the
9235 controller tries to fetch a networkstatus that doesn't exist.
9236 - When the controller does a "GETINFO network-status", tell it
9237 about even those routers whose descriptors are very old, and use
9238 long nicknames where appropriate.
9239 - Fix handling of verbose nicknames with ORCONN controller events:
9240 make them show up exactly when requested, rather than exactly when
9242 - Controller signals now work on non-Unix platforms that don't define
9243 SIGUSR1 and SIGUSR2 the way we expect.
9244 - Respond to SIGNAL command before we execute the signal, in case
9245 the signal shuts us down. Suggested by Karsten Loesing.
9246 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
9248 o Minor features, code performance:
9249 - Major performance improvement on inserting descriptors: change
9250 algorithm from O(n^2) to O(n).
9251 - Do not rotate onion key immediately after setting it for the first
9253 - Call router_have_min_dir_info half as often. (This is showing up in
9254 some profiles, but not others.)
9255 - When using GCC, make log_debug never get called at all, and its
9256 arguments never get evaluated, when no debug logs are configured.
9257 (This is showing up in some profiles, but not others.)
9258 - Statistics dumped by -USR2 now include a breakdown of public key
9259 operations, for profiling.
9260 - Make the common memory allocation path faster on machines where
9261 malloc(0) returns a pointer.
9262 - Split circuit_t into origin_circuit_t and or_circuit_t, and
9263 split connection_t into edge, or, dir, control, and base structs.
9264 These will save quite a bit of memory on busy servers, and they'll
9265 also help us track down bugs in the code and bugs in the spec.
9266 - Use OpenSSL's AES implementation on platforms where it's faster.
9267 This could save us as much as 10% CPU usage.
9269 o Minor features, descriptors and descriptor handling:
9270 - Avoid duplicate entries on MyFamily line in server descriptor.
9271 - When Tor receives a router descriptor that it asked for, but
9272 no longer wants (because it has received fresh networkstatuses
9273 in the meantime), do not warn the user. Cache the descriptor if
9274 we're a cache; drop it if we aren't.
9275 - Servers no longer ever list themselves in their "family" line,
9276 even if configured to do so. This makes it easier to configure
9277 family lists conveniently.
9279 o Minor fixes, confusing/misleading log messages:
9280 - Display correct results when reporting which versions are
9281 recommended, and how recommended they are. (Resolves bug 383.)
9282 - Inform the server operator when we decide not to advertise a
9283 DirPort due to AccountingMax enabled or a low BandwidthRate.
9284 - Only include function names in log messages for info/debug messages.
9285 For notice/warn/err, the content of the message should be clear on
9286 its own, and printing the function name only confuses users.
9287 - Remove even more protocol-related warnings from Tor server logs,
9288 such as bad TLS handshakes and malformed begin cells.
9289 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
9290 when the IP address is mapped through MapAddress to a hostname.
9291 - Fix misleading log messages: an entry guard that is "unlisted",
9292 as well as not known to be "down" (because we've never heard
9293 of it), is not therefore "up".
9295 o Minor fixes, old/obsolete behavior:
9296 - Start assuming we can use a create_fast cell if we don't know
9297 what version a router is running.
9298 - We no longer look for identity and onion keys in "identity.key" and
9299 "onion.key" -- these were replaced by secret_id_key and
9300 secret_onion_key in 0.0.8pre1.
9301 - We no longer require unrecognized directory entries to be
9303 - Drop compatibility with obsolete Tors that permit create cells
9304 to have the wrong circ_id_type.
9305 - Remove code to special-case "-cvs" ending, since it has not
9306 actually mattered since 0.0.9.
9307 - Don't re-write the fingerprint file every restart, unless it has
9310 o Minor fixes, misc client-side behavior:
9311 - Always remove expired routers and networkstatus docs before checking
9312 whether we have enough information to build circuits. (Fixes
9314 - When computing clock skew from directory HTTP headers, consider what
9315 time it was when we finished asking for the directory, not what
9317 - Make our socks5 handling more robust to broken socks clients:
9318 throw out everything waiting on the buffer in between socks
9319 handshake phases, since they can't possibly (so the theory
9320 goes) have predicted what we plan to respond to them.
9321 - Expire socks connections if they spend too long waiting for the
9322 handshake to finish. Previously we would let them sit around for
9323 days, if the connecting application didn't close them either.
9324 - And if the socks handshake hasn't started, don't send a
9325 "DNS resolve socks failed" handshake reply; just close it.
9326 - If the user asks to use invalid exit nodes, be willing to use
9328 - Track unreachable entry guards correctly: don't conflate
9329 'unreachable by us right now' with 'listed as down by the directory
9330 authorities'. With the old code, if a guard was unreachable by us
9331 but listed as running, it would clog our guard list forever.
9332 - Behave correctly in case we ever have a network with more than
9333 2GB/s total advertised capacity.
9334 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
9335 - Fix a memory leak when we ask for "all" networkstatuses and we
9336 get one we don't recognize.
9339 Changes in version 0.1.1.26 - 2006-12-14
9340 o Security bugfixes:
9341 - Stop sending the HttpProxyAuthenticator string to directory
9342 servers when directory connections are tunnelled through Tor.
9343 - Clients no longer store bandwidth history in the state file.
9344 - Do not log introduction points for hidden services if SafeLogging
9348 - Fix an assert failure when a directory authority sets
9349 AuthDirRejectUnlisted and then receives a descriptor from an
9350 unlisted router (reported by seeess).
9353 Changes in version 0.1.1.25 - 2006-11-04
9355 - When a client asks us to resolve (rather than connect to)
9356 an address, and we have a cached answer, give them the cached
9357 answer. Previously, we would give them no answer at all.
9358 - We were building exactly the wrong circuits when we predict
9359 hidden service requirements, meaning Tor would have to build all
9360 its circuits on demand.
9361 - If none of our live entry guards have a high uptime, but we
9362 require a guard with a high uptime, try adding a new guard before
9363 we give up on the requirement. This patch should make long-lived
9364 connections more stable on average.
9365 - When testing reachability of our DirPort, don't launch new
9366 tests when there's already one in progress -- unreachable
9367 servers were stacking up dozens of testing streams.
9369 o Security bugfixes:
9370 - When the user sends a NEWNYM signal, clear the client-side DNS
9371 cache too. Otherwise we continue to act on previous information.
9374 - Avoid a memory corruption bug when creating a hash table for
9376 - Avoid possibility of controller-triggered crash when misusing
9377 certain commands from a v0 controller on platforms that do not
9378 handle printf("%s",NULL) gracefully.
9379 - Avoid infinite loop on unexpected controller input.
9380 - Don't log spurious warnings when we see a circuit close reason we
9381 don't recognize; it's probably just from a newer version of Tor.
9382 - Add Vidalia to the OS X uninstaller script, so when we uninstall
9383 Tor/Privoxy we also uninstall Vidalia.
9386 Changes in version 0.1.1.24 - 2006-09-29
9388 - Allow really slow clients to not hang up five minutes into their
9389 directory downloads (suggested by Adam J. Richter).
9390 - Fix major performance regression from 0.1.0.x: instead of checking
9391 whether we have enough directory information every time we want to
9392 do something, only check when the directory information has changed.
9393 This should improve client CPU usage by 25-50%.
9394 - Don't crash if, after a server has been running for a while,
9395 it can't resolve its hostname.
9396 - When a client asks us to resolve (not connect to) an address,
9397 and we have a cached answer, give them the cached answer.
9398 Previously, we would give them no answer at all.
9401 - Allow Tor to start when RunAsDaemon is set but no logs are set.
9402 - Don't crash when the controller receives a third argument to an
9403 "extendcircuit" request.
9404 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
9405 response; fix error code when "getinfo dir/status/" fails.
9406 - Fix configure.in to not produce broken configure files with
9407 more recent versions of autoconf. Thanks to Clint for his auto*
9409 - Fix security bug on NetBSD that could allow someone to force
9410 uninitialized RAM to be sent to a server's DNS resolver. This
9411 only affects NetBSD and other platforms that do not bounds-check
9413 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
9414 methods: these are known to be buggy.
9415 - If we're a directory mirror and we ask for "all" network status
9416 documents, we would discard status documents from authorities
9420 Changes in version 0.1.1.23 - 2006-07-30
9422 - Fast Tor servers, especially exit nodes, were triggering asserts
9423 due to a bug in handling the list of pending DNS resolves. Some
9424 bugs still remain here; we're hunting them.
9425 - Entry guards could crash clients by sending unexpected input.
9426 - More fixes on reachability testing: if you find yourself reachable,
9427 then don't ever make any client requests (so you stop predicting
9428 circuits), then hup or have your clock jump, then later your IP
9429 changes, you won't think circuits are working, so you won't try to
9430 test reachability, so you won't publish.
9433 - Avoid a crash if the controller does a resetconf firewallports
9434 and then a setconf fascistfirewall=1.
9435 - Avoid an integer underflow when the dir authority decides whether
9436 a router is stable: we might wrongly label it stable, and compute
9437 a slightly wrong median stability, when a descriptor is published
9439 - Fix a place where we might trigger an assert if we can't build our
9440 own server descriptor yet.
9443 Changes in version 0.1.1.22 - 2006-07-05
9445 - Fix a big bug that was causing servers to not find themselves
9446 reachable if they changed IP addresses. Since only 0.1.1.22+
9447 servers can do reachability testing correctly, now we automatically
9448 make sure to test via one of these.
9449 - Fix to allow clients and mirrors to learn directory info from
9450 descriptor downloads that get cut off partway through.
9451 - Directory authorities had a bug in deciding if a newly published
9452 descriptor was novel enough to make everybody want a copy -- a few
9453 servers seem to be publishing new descriptors many times a minute.
9455 - Fix a rare bug that was causing some servers to complain about
9456 "closing wedged cpuworkers" and skip some circuit create requests.
9457 - Make the Exit flag in directory status documents actually work.
9460 Changes in version 0.1.1.21 - 2006-06-10
9461 o Crash and assert fixes from 0.1.1.20:
9462 - Fix a rare crash on Tor servers that have enabled hibernation.
9463 - Fix a seg fault on startup for Tor networks that use only one
9464 directory authority.
9465 - Fix an assert from a race condition that occurs on Tor servers
9466 while exiting, where various threads are trying to log that they're
9467 exiting, and delete the logs, at the same time.
9468 - Make our unit tests pass again on certain obscure platforms.
9471 - Add support for building SUSE RPM packages.
9472 - Speed up initial bootstrapping for clients: if we are making our
9473 first ever connection to any entry guard, then don't mark it down
9475 - When only one Tor server in the network is labelled as a guard,
9476 and we've already picked him, we would cycle endlessly picking him
9477 again, being unhappy about it, etc. Now we specifically exclude
9478 current guards when picking a new guard.
9479 - Servers send create cells more reliably after the TLS connection
9480 is established: we were sometimes forgetting to send half of them
9481 when we had more than one pending.
9482 - If we get a create cell that asks us to extend somewhere, but the
9483 Tor server there doesn't match the expected digest, we now send
9484 a destroy cell back, rather than silently doing nothing.
9485 - Make options->RedirectExit work again.
9486 - Make cookie authentication for the controller work again.
9487 - Stop being picky about unusual characters in the arguments to
9488 mapaddress. It's none of our business.
9489 - Add a new config option "TestVia" that lets you specify preferred
9490 middle hops to use for test circuits. Perhaps this will let me
9491 debug the reachability problems better.
9493 o Log / documentation fixes:
9494 - If we're a server and some peer has a broken TLS certificate, don't
9495 log about it unless ProtocolWarnings is set, i.e., we want to hear
9496 about protocol violations by others.
9497 - Fix spelling of VirtualAddrNetwork in man page.
9498 - Add a better explanation at the top of the autogenerated torrc file
9499 about what happened to our old torrc.
9502 Changes in version 0.1.1.20 - 2006-05-23
9503 o Crash and assert fixes from 0.1.0.17:
9504 - Fix assert bug in close_logs() on exit: when we close and delete
9505 logs, remove them all from the global "logfiles" list.
9506 - Fix an assert error when we're out of space in the connection_list
9507 and we try to post a hidden service descriptor (reported by Peter
9509 - Fix a rare assert error when we've tried all intro points for
9510 a hidden service and we try fetching the service descriptor again:
9511 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
9512 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
9513 out and refuse the setconf if it would fail.
9514 - If you specify a relative torrc path and you set RunAsDaemon in
9515 your torrc, then it chdir()'s to the new directory. If you then
9516 HUP, it tries to load the new torrc location, fails, and exits.
9517 The fix: no longer allow a relative path to torrc when using -f.
9518 - Check for integer overflows in more places, when adding elements
9519 to smartlists. This could possibly prevent a buffer overflow
9520 on malicious huge inputs.
9522 o Security fixes, major:
9523 - When we're printing strings from the network, don't try to print
9524 non-printable characters. Now we're safer against shell escape
9525 sequence exploits, and also against attacks to fool users into
9526 misreading their logs.
9527 - Implement entry guards: automatically choose a handful of entry
9528 nodes and stick with them for all circuits. Only pick new guards
9529 when the ones you have are unsuitable, and if the old guards
9530 become suitable again, switch back. This will increase security
9531 dramatically against certain end-point attacks. The EntryNodes
9532 config option now provides some hints about which entry guards you
9533 want to use most; and StrictEntryNodes means to only use those.
9534 Fixes CVE-2006-0414.
9535 - Implement exit enclaves: if we know an IP address for the
9536 destination, and there's a running Tor server at that address
9537 which allows exit to the destination, then extend the circuit to
9538 that exit first. This provides end-to-end encryption and end-to-end
9539 authentication. Also, if the user wants a .exit address or enclave,
9540 use 4 hops rather than 3, and cannibalize a general circ for it
9542 - Obey our firewall options more faithfully:
9543 . If we can't get to a dirserver directly, try going via Tor.
9544 . Don't ever try to connect (as a client) to a place our
9545 firewall options forbid.
9546 . If we specify a proxy and also firewall options, obey the
9547 firewall options even when we're using the proxy: some proxies
9548 can only proxy to certain destinations.
9549 - Make clients regenerate their keys when their IP address changes.
9550 - For the OS X package's modified privoxy config file, comment
9551 out the "logfile" line so we don't log everything passed
9553 - Our TLS handshakes were generating a single public/private
9554 keypair for the TLS context, rather than making a new one for
9555 each new connection. Oops. (But we were still rotating them
9556 periodically, so it's not so bad.)
9557 - When we were cannibalizing a circuit with a particular exit
9558 node in mind, we weren't checking to see if that exit node was
9559 already present earlier in the circuit. Now we are.
9560 - Require server descriptors to list IPv4 addresses -- hostnames
9561 are no longer allowed. This also fixes potential vulnerabilities
9562 to servers providing hostnames as their address and then
9563 preferentially resolving them so they can partition users.
9564 - Our logic to decide if the OR we connected to was the right guy
9565 was brittle and maybe open to a mitm for invalid routers.
9567 o Security fixes, minor:
9568 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
9569 Ian Goldberg can prove things about our handshake protocol more
9571 - Make directory authorities generate a separate "guard" flag to
9572 mean "would make a good entry guard". Clients now honor the
9573 is_guard flag rather than looking at is_fast or is_stable.
9574 - Try to list MyFamily elements by key, not by nickname, and warn
9575 if we've not heard of a server.
9576 - Start using RAND_bytes rather than RAND_pseudo_bytes from
9577 OpenSSL. Also, reseed our entropy every hour, not just at
9578 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
9579 - Refuse server descriptors where the fingerprint line doesn't match
9580 the included identity key. Tor doesn't care, but other apps (and
9581 humans) might actually be trusting the fingerprint line.
9582 - We used to kill the circuit when we receive a relay command we
9583 don't recognize. Now we just drop that cell.
9584 - Fix a bug found by Lasse Overlier: when we were making internal
9585 circuits (intended to be cannibalized later for rendezvous and
9586 introduction circuits), we were picking them so that they had
9587 useful exit nodes. There was no need for this, and it actually
9588 aids some statistical attacks.
9589 - Start treating internal circuits and exit circuits separately.
9590 It's important to keep them separate because internal circuits
9591 have their last hops picked like middle hops, rather than like
9592 exit hops. So exiting on them will break the user's expectations.
9593 - Fix a possible way to DoS dirservers.
9594 - When the client asked for a rendezvous port that the hidden
9595 service didn't want to provide, we were sending an IP address
9596 back along with the end cell. Fortunately, it was zero. But stop
9599 o Packaging improvements:
9600 - Implement --with-libevent-dir option to ./configure. Improve
9601 search techniques to find libevent, and use those for openssl too.
9602 - Fix a couple of bugs in OpenSSL detection. Deal better when
9603 there are multiple SSLs installed with different versions.
9604 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
9605 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
9607 - Make unit tests (and other invocations that aren't the real Tor)
9608 run without launching listeners, creating subdirectories, and so on.
9609 - The OS X installer was adding a symlink for tor_resolve but
9610 the binary was called tor-resolve (reported by Thomas Hardly).
9611 - Now we can target arch and OS in rpm builds (contributed by
9612 Phobos). Also make the resulting dist-rpm filename match the
9614 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
9615 if you log to syslog and want something other than LOG_DAEMON.
9616 - Fix the torify (tsocks) config file to not use Tor for localhost
9618 - Start shipping socks-extensions.txt, tor-doc-unix.html,
9619 tor-doc-server.html, and stylesheet.css in the tarball.
9620 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
9621 They are useless now.
9622 - Add Peter Palfrader's contributed check-tor script. It lets you
9623 easily check whether a given server (referenced by nickname)
9624 is reachable by you.
9625 - Add BSD-style contributed startup script "rc.subr" from Peter
9628 o Directory improvements -- new directory protocol:
9629 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
9630 - Authorities and caches publish individual descriptors (by
9631 digest, by fingerprint, by "all", and by "tell me yours").
9632 - Clients don't download or use the old directory anymore. Now they
9633 download network-statuses from the directory authorities, and
9634 fetch individual server descriptors as needed from mirrors.
9635 - Clients don't download descriptors of non-running servers.
9636 - Download descriptors by digest, not by fingerprint. Caches try to
9637 download all listed digests from authorities; clients try to
9638 download "best" digests from caches. This avoids partitioning
9639 and isolating attacks better.
9640 - Only upload a new server descriptor when options change, 18
9641 hours have passed, uptime is reset, or bandwidth changes a lot.
9642 - Directory authorities silently throw away new descriptors that
9643 haven't changed much if the timestamps are similar. We do this to
9644 tolerate older Tor servers that upload a new descriptor every 15
9645 minutes. (It seemed like a good idea at the time.)
9646 - Clients choose directory servers from the network status lists,
9647 not from their internal list of router descriptors. Now they can
9648 go to caches directly rather than needing to go to authorities
9649 to bootstrap the first set of descriptors.
9650 - When picking a random directory, prefer non-authorities if any
9652 - Add a new flag to network-status indicating whether the server
9653 can answer v2 directory requests too.
9654 - Directory mirrors now cache up to 16 unrecognized network-status
9655 docs, so new directory authorities will be cached too.
9656 - Stop parsing, storing, or using running-routers output (but
9657 mirrors still cache and serve it).
9658 - Clients consider a threshold of "versioning" directory authorities
9659 before deciding whether to warn the user that he's obsolete.
9660 - Authorities publish separate sorted lists of recommended versions
9661 for clients and for servers.
9662 - Change DirServers config line to note which dirs are v1 authorities.
9663 - Put nicknames on the DirServer line, so we can refer to them
9664 without requiring all our users to memorize their IP addresses.
9665 - Remove option when getting directory cache to see whether they
9666 support running-routers; they all do now. Replace it with one
9667 to see whether caches support v2 stuff.
9668 - Stop listing down or invalid nodes in the v1 directory. This
9669 reduces its bulk by about 1/3, and reduces load on mirrors.
9670 - Mirrors no longer cache the v1 directory as often.
9671 - If we as a directory mirror don't know of any v1 directory
9672 authorities, then don't try to cache any v1 directories.
9674 o Other directory improvements:
9675 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
9676 fifth authoritative directory servers.
9677 - Directory authorities no longer require an open connection from
9678 a server to consider him "reachable". We need this change because
9679 when we add new directory authorities, old servers won't know not
9681 - Dir authorities now do their own external reachability testing
9682 of each server, and only list as running the ones they found to
9683 be reachable. We also send back warnings to the server's logs if
9684 it uploads a descriptor that we already believe is unreachable.
9685 - Spread the directory authorities' reachability testing over the
9686 entire testing interval, so we don't try to do 500 TLS's at once
9688 - Make the "stable" router flag in network-status be the median of
9689 the uptimes of running valid servers, and make clients pay
9690 attention to the network-status flags. Thus the cutoff adapts
9691 to the stability of the network as a whole, making IRC, IM, etc
9692 connections more reliable.
9693 - Make the v2 dir's "Fast" flag based on relative capacity, just
9694 like "Stable" is based on median uptime. Name everything in the
9695 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
9696 - Retry directory requests if we fail to get an answer we like
9697 from a given dirserver (we were retrying before, but only if
9698 we fail to connect).
9699 - Return a robots.txt on our dirport to discourage google indexing.
9701 o Controller protocol improvements:
9702 - Revised controller protocol (version 1) that uses ascii rather
9703 than binary: tor/doc/control-spec.txt. Add supporting libraries
9704 in python and java and c# so you can use the controller from your
9705 applications without caring how our protocol works.
9706 - Allow the DEBUG controller event to work again. Mark certain log
9707 entries as "don't tell this to controllers", so we avoid cycles.
9708 - New controller function "getinfo accounting", to ask how
9709 many bytes we've used in this time period.
9710 - Add a "resetconf" command so you can set config options like
9711 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
9712 a config option in the torrc with no value, then it clears it
9713 entirely (rather than setting it to its default).
9714 - Add a "getinfo config-file" to tell us where torrc is. Also
9715 expose guard nodes, config options/names.
9716 - Add a "quit" command (when when using the controller manually).
9717 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
9718 stop using any currently-dirty circuits for new streams, so we
9719 don't link new actions to old actions. This also occurs on HUP
9721 - If we would close a stream early (e.g. it asks for a .exit that
9722 we know would refuse it) but the LeaveStreamsUnattached config
9723 option is set by the controller, then don't close it.
9724 - Add a new controller event type "authdir_newdescs" that allows
9725 controllers to get all server descriptors that were uploaded to
9726 a router in its role as directory authority.
9727 - New controller option "getinfo desc/all-recent" to fetch the
9728 latest server descriptor for every router that Tor knows about.
9729 - Fix the controller's "attachstream 0" command to treat conn like
9730 it just connected, doing address remapping, handling .exit and
9731 .onion idioms, and so on. Now we're more uniform in making sure
9732 that the controller hears about new and closing connections.
9733 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
9734 the controller. Also, rotate dns and cpu workers if the controller
9735 changes options that will affect them; and initialize the dns
9736 worker cache tree whether or not we start out as a server.
9737 - Add a new circuit purpose 'controller' to let the controller ask
9738 for a circuit that Tor won't try to use. Extend the "extendcircuit"
9739 controller command to let you specify the purpose if you're starting
9740 a new circuit. Add a new "setcircuitpurpose" controller command to
9741 let you change a circuit's purpose after it's been created.
9742 - Let the controller ask for "getinfo dir/server/foo" so it can ask
9743 directly rather than connecting to the dir port. "getinfo
9744 dir/status/foo" also works, but currently only if your DirPort
9746 - Let the controller tell us about certain router descriptors
9747 that it doesn't want Tor to use in circuits. Implement
9748 "setrouterpurpose" and modify "+postdescriptor" to do this.
9749 - If the controller's *setconf commands fail, collect an error
9750 message in a string and hand it back to the controller -- don't
9751 just tell them to go read their logs.
9753 o Scalability, resource management, and performance:
9754 - Fix a major load balance bug: we were round-robin reading in 16 KB
9755 chunks, and servers with bandwidthrate of 20 KB, while downloading
9756 a 600 KB directory, would starve their other connections. Now we
9757 try to be a bit more fair.
9758 - Be more conservative about whether to advertise our DirPort.
9759 The main change is to not advertise if we're running at capacity
9760 and either a) we could hibernate ever or b) our capacity is low
9761 and we're using a default DirPort.
9762 - We weren't cannibalizing circuits correctly for
9763 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
9764 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
9765 build those from scratch. This should make hidden services faster.
9766 - Predict required circuits better, with an eye toward making hidden
9767 services faster on the service end.
9768 - Compress exit policies even more: look for duplicate lines and
9770 - Generate 18.0.0.0/8 address policy format in descs when we can;
9771 warn when the mask is not reducible to a bit-prefix.
9772 - There used to be two ways to specify your listening ports in a
9773 server descriptor: on the "router" line and with a separate "ports"
9774 line. Remove support for the "ports" line.
9775 - Reduce memory requirements in our structs by changing the order
9776 of fields. Replace balanced trees with hash tables. Inline
9777 bottleneck smartlist functions. Add a "Map from digest to void*"
9778 abstraction so we can do less hex encoding/decoding, and use it
9779 in router_get_by_digest(). Many other CPU and memory improvements.
9780 - Allow tor_gzip_uncompress to extract as much as possible from
9781 truncated compressed data. Try to extract as many
9782 descriptors as possible from truncated http responses (when
9783 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
9784 - Make circ->onionskin a pointer, not a static array. moria2 was using
9785 125000 circuit_t's after it had been up for a few weeks, which
9786 translates to 20+ megs of wasted space.
9787 - The private half of our EDH handshake keys are now chosen out
9788 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
9789 - Stop doing the complex voodoo overkill checking for insecure
9790 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
9791 - Do round-robin writes for TLS of at most 16 kB per write. This
9792 might be more fair on loaded Tor servers.
9793 - Do not use unaligned memory access on alpha, mips, or mipsel.
9794 It *works*, but is very slow, so we treat them as if it doesn't.
9796 o Other bugfixes and improvements:
9797 - Start storing useful information to $DATADIR/state, so we can
9798 remember things across invocations of Tor. Retain unrecognized
9799 lines so we can be forward-compatible, and write a TorVersion line
9800 so we can be backward-compatible.
9801 - If ORPort is set, Address is not explicitly set, and our hostname
9802 resolves to a private IP address, try to use an interface address
9803 if it has a public address. Now Windows machines that think of
9804 themselves as localhost can guess their address.
9805 - Regenerate our local descriptor if it's dirty and we try to use
9806 it locally (e.g. if it changes during reachability detection).
9807 This was causing some Tor servers to keep publishing the same
9808 initial descriptor forever.
9809 - Tor servers with dynamic IP addresses were needing to wait 18
9810 hours before they could start doing reachability testing using
9811 the new IP address and ports. This is because they were using
9812 the internal descriptor to learn what to test, yet they were only
9813 rebuilding the descriptor once they decided they were reachable.
9814 - It turns out we couldn't bootstrap a network since we added
9815 reachability detection in 0.1.0.1-rc. Good thing the Tor network
9816 has never gone down. Add an AssumeReachable config option to let
9817 servers and authorities bootstrap. When we're trying to build a
9818 high-uptime or high-bandwidth circuit but there aren't enough
9819 suitable servers, try being less picky rather than simply failing.
9820 - Newly bootstrapped Tor networks couldn't establish hidden service
9821 circuits until they had nodes with high uptime. Be more tolerant.
9822 - Really busy servers were keeping enough circuits open on stable
9823 connections that they were wrapping around the circuit_id
9824 space. (It's only two bytes.) This exposed a bug where we would
9825 feel free to reuse a circuit_id even if it still exists but has
9826 been marked for close. Try to fix this bug. Some bug remains.
9827 - When we fail to bind or listen on an incoming or outgoing
9828 socket, we now close it before refusing, rather than just
9829 leaking it. (Thanks to Peter Palfrader for finding.)
9830 - Fix a file descriptor leak in start_daemon().
9831 - On Windows, you can't always reopen a port right after you've
9832 closed it. So change retry_listeners() to only close and re-open
9833 ports that have changed.
9834 - Workaround a problem with some http proxies that refuse GET
9835 requests that specify "Content-Length: 0". Reported by Adrian.
9836 - Recover better from TCP connections to Tor servers that are
9837 broken but don't tell you (it happens!); and rotate TLS
9838 connections once a week.
9839 - Fix a scary-looking but apparently harmless bug where circuits
9840 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
9841 servers, and never switch to state CIRCUIT_STATE_OPEN.
9842 - Check for even more Windows version flags when writing the platform
9843 string in server descriptors, and note any we don't recognize.
9844 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
9845 get a better idea of why their circuits failed. Not used yet.
9846 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
9847 We don't use them yet, but maybe one day our DNS resolver will be
9848 able to discover them.
9849 - Let people type "tor --install" as well as "tor -install" when they
9850 want to make it an NT service.
9851 - Looks like we were never delivering deflated (i.e. compressed)
9852 running-routers lists, even when asked. Oops.
9853 - We were leaking some memory every time the client changed IPs.
9854 - Clean up more of the OpenSSL memory when exiting, so we can detect
9855 memory leaks better.
9856 - Never call free() on tor_malloc()d memory. This will help us
9857 use dmalloc to detect memory leaks.
9858 - Some Tor servers process billions of cells per day. These
9859 statistics are now uint64_t's.
9860 - Check [X-]Forwarded-For headers in HTTP requests when generating
9861 log messages. This lets people run dirservers (and caches) behind
9862 Apache but still know which IP addresses are causing warnings.
9863 - Fix minor integer overflow in calculating when we expect to use up
9864 our bandwidth allocation before hibernating.
9865 - Lower the minimum required number of file descriptors to 1000,
9866 so we can have some overhead for Valgrind on Linux, where the
9867 default ulimit -n is 1024.
9868 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
9869 and its existence is confusing some users.
9871 o Config option fixes:
9872 - Add a new config option ExitPolicyRejectPrivate which defaults
9873 to on. Now all exit policies will begin with rejecting private
9874 addresses, unless the server operator explicitly turns it off.
9875 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
9876 - Add new ReachableORAddresses and ReachableDirAddresses options
9877 that understand address policies. FascistFirewall is now a synonym
9878 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
9879 - Start calling it FooListenAddress rather than FooBindAddress,
9880 since few of our users know what it means to bind an address
9882 - If the user gave Tor an odd number of command-line arguments,
9883 we were silently ignoring the last one. Now we complain and fail.
9884 This wins the oldest-bug prize -- this bug has been present since
9885 November 2002, as released in Tor 0.0.0.
9886 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
9887 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
9888 it would silently ignore the 6668.
9889 - If we get a linelist or linelist_s config option from the torrc,
9890 e.g. ExitPolicy, and it has no value, warn and skip rather than
9891 silently resetting it to its default.
9892 - Setconf was appending items to linelists, not clearing them.
9893 - Add MyFamily to torrc.sample in the server section, so operators
9894 will be more likely to learn that it exists.
9895 - Make ContactInfo mandatory for authoritative directory servers.
9896 - MaxConn has been obsolete for a while now. Document the ConnLimit
9897 config option, which is a *minimum* number of file descriptors
9898 that must be available else Tor refuses to start.
9899 - Get rid of IgnoreVersion undocumented config option, and make us
9900 only warn, never exit, when we're running an obsolete version.
9901 - Make MonthlyAccountingStart config option truly obsolete now.
9902 - Correct the man page entry on TrackHostExitsExpire.
9903 - Let directory authorities start even if they don't specify an
9904 Address config option.
9905 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
9906 reflect the updated flags in our v2 dir protocol.
9908 o Config option features:
9909 - Add a new config option FastFirstHopPK (on by default) so clients
9910 do a trivial crypto handshake for their first hop, since TLS has
9911 already taken care of confidentiality and authentication.
9912 - Let the user set ControlListenAddress in the torrc. This can be
9913 dangerous, but there are some cases (like a secured LAN) where it
9915 - New config options to help controllers: FetchServerDescriptors
9916 and FetchHidServDescriptors for whether to fetch server
9917 info and hidserv info or let the controller do it, and
9918 PublishServerDescriptor and PublishHidServDescriptors.
9919 - Also let the controller set the __AllDirActionsPrivate config
9920 option if you want all directory fetches/publishes to happen via
9921 Tor (it assumes your controller bootstraps your circuits).
9922 - Add "HardwareAccel" config option: support for crypto hardware
9923 accelerators via OpenSSL. Off by default, until we find somebody
9924 smart who can test it for us. (It appears to produce seg faults
9925 in at least some cases.)
9926 - New config option "AuthDirRejectUnlisted" for directory authorities
9927 as a panic button: if we get flooded with unusable servers we can
9928 revert to only listing servers in the approved-routers file.
9929 - Directory authorities can now reject/invalidate by key and IP,
9930 with the config options "AuthDirInvalid" and "AuthDirReject", or
9931 by marking a fingerprint as "!reject" or "!invalid" (as its
9932 nickname) in the approved-routers file. This is useful since
9933 currently we automatically list servers as running and usable
9934 even if we know they're jerks.
9935 - Add a new config option TestSocks so people can see whether their
9936 applications are using socks4, socks4a, socks5-with-ip, or
9937 socks5-with-fqdn. This way they don't have to keep mucking
9938 with tcpdump and wondering if something got cached somewhere.
9939 - Add "private:*" as an alias in configuration for policies. Now
9940 you can simplify your exit policy rather than needing to list
9941 every single internal or nonroutable network space.
9942 - Accept "private:*" in routerdesc exit policies; not generated yet
9943 because older Tors do not understand it.
9944 - Add configuration option "V1AuthoritativeDirectory 1" which
9945 moria1, moria2, and tor26 have set.
9946 - Implement an option, VirtualAddrMask, to set which addresses
9947 get handed out in response to mapaddress requests. This works
9948 around a bug in tsocks where 127.0.0.0/8 is never socksified.
9949 - Add a new config option FetchUselessDescriptors, off by default,
9950 for when you plan to run "exitlist" on your client and you want
9951 to know about even the non-running descriptors.
9952 - SocksTimeout: How long do we let a socks connection wait
9953 unattached before we fail it?
9954 - CircuitBuildTimeout: Cull non-open circuits that were born
9955 at least this many seconds ago.
9956 - CircuitIdleTimeout: Cull open clean circuits that were born
9957 at least this many seconds ago.
9958 - New config option SafeSocks to reject all application connections
9959 using unsafe socks protocols. Defaults to off.
9961 o Improved and clearer log messages:
9962 - Reduce clutter in server logs. We're going to try to make
9963 them actually usable now. New config option ProtocolWarnings that
9964 lets you hear about how _other Tors_ are breaking the protocol. Off
9966 - Divide log messages into logging domains. Once we put some sort
9967 of interface on this, it will let people looking at more verbose
9968 log levels specify the topics they want to hear more about.
9969 - Log server fingerprint on startup, so new server operators don't
9970 have to go hunting around their filesystem for it.
9971 - Provide dire warnings to any users who set DirServer manually;
9972 move it out of torrc.sample and into torrc.complete.
9973 - Make the log message less scary when all the dirservers are
9974 temporarily unreachable.
9975 - When tor_socketpair() fails in Windows, give a reasonable
9976 Windows-style errno back.
9977 - Improve tor_gettimeofday() granularity on windows.
9978 - We were printing the number of idle dns workers incorrectly when
9980 - Handle duplicate lines in approved-routers files without warning.
9981 - We were whining about using socks4 or socks5-with-local-lookup
9982 even when it's an IP address in the "virtual" range we designed
9983 exactly for this case.
9984 - Check for named servers when looking them up by nickname;
9985 warn when we're calling a non-named server by its nickname;
9986 don't warn twice about the same name.
9987 - Downgrade the dirserver log messages when whining about
9989 - Correct "your server is reachable" log entries to indicate that
9990 it was self-testing that told us so.
9991 - If we're trying to be a Tor server and running Windows 95/98/ME
9992 as a server, explain that we'll likely crash.
9993 - Provide a more useful warn message when our onion queue gets full:
9994 the CPU is too slow or the exit policy is too liberal.
9995 - Don't warn when we receive a 503 from a dirserver/cache -- this
9996 will pave the way for them being able to refuse if they're busy.
9997 - When we fail to bind a listener, try to provide a more useful
9998 log message: e.g., "Is Tor already running?"
9999 - Only start testing reachability once we've established a
10000 circuit. This will make startup on dir authorities less noisy.
10001 - Don't try to upload hidden service descriptors until we have
10002 established a circuit.
10003 - Tor didn't warn when it failed to open a log file.
10004 - Warn when listening on a public address for socks. We suspect a
10005 lot of people are setting themselves up as open socks proxies,
10006 and they have no idea that jerks on the Internet are using them,
10007 since they simply proxy the traffic into the Tor network.
10008 - Give a useful message when people run Tor as the wrong user,
10009 rather than telling them to start chowning random directories.
10010 - Fix a harmless bug that was causing Tor servers to log
10011 "Got an end because of misc error, but we're not an AP. Closing."
10012 - Fix wrong log message when you add a "HiddenServiceNodes" config
10013 line without any HiddenServiceDir line (reported by Chris Thomas).
10014 - Directory authorities now stop whining so loudly about bad
10015 descriptors that they fetch from other dirservers. So when there's
10016 a log complaint, it's for sure from a freshly uploaded descriptor.
10017 - When logging via syslog, include the pid whenever we provide
10018 a log entry. Suggested by Todd Fries.
10019 - When we're shutting down and we do something like try to post a
10020 server descriptor or rendezvous descriptor, don't complain that
10021 we seem to be unreachable. Of course we are, we're shutting down.
10022 - Change log line for unreachability to explicitly suggest /etc/hosts
10023 as the culprit. Also make it clearer what IP address and ports we're
10024 testing for reachability.
10025 - Put quotes around user-supplied strings when logging so users are
10026 more likely to realize if they add bad characters (like quotes)
10028 - NT service patch from Matt Edman to improve error messages on Win32.
10031 Changes in version 0.1.0.17 - 2006-02-17
10032 o Crash bugfixes on 0.1.0.x:
10033 - When servers with a non-zero DirPort came out of hibernation,
10034 sometimes they would trigger an assert.
10036 o Other important bugfixes:
10037 - On platforms that don't have getrlimit (like Windows), we were
10038 artificially constraining ourselves to a max of 1024
10039 connections. Now just assume that we can handle as many as 15000
10040 connections. Hopefully this won't cause other problems.
10042 o Backported features:
10043 - When we're a server, a client asks for an old-style directory,
10044 and our write bucket is empty, don't give it to him. This way
10045 small servers can continue to serve the directory *sometimes*,
10046 without getting overloaded.
10047 - Whenever you get a 503 in response to a directory fetch, try
10048 once more. This will become important once servers start sending
10049 503's whenever they feel busy.
10050 - Fetch a new directory every 120 minutes, not every 40 minutes.
10051 Now that we have hundreds of thousands of users running the old
10052 directory algorithm, it's starting to hurt a lot.
10053 - Bump up the period for forcing a hidden service descriptor upload
10054 from 20 minutes to 1 hour.
10057 Changes in version 0.1.0.16 - 2006-01-02
10058 o Crash bugfixes on 0.1.0.x:
10059 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
10060 corrupting the heap, losing FDs, or crashing when we need to resize
10061 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
10062 - It turns out sparc64 platforms crash on unaligned memory access
10063 too -- so detect and avoid this.
10064 - Handle truncated compressed data correctly (by detecting it and
10066 - Fix possible-but-unlikely free(NULL) in control.c.
10067 - When we were closing connections, there was a rare case that
10068 stomped on memory, triggering seg faults and asserts.
10069 - Avoid potential infinite recursion when building a descriptor. (We
10070 don't know that it ever happened, but better to fix it anyway.)
10071 - We were neglecting to unlink marked circuits from soon-to-close OR
10072 connections, which caused some rare scribbling on freed memory.
10073 - Fix a memory stomping race bug when closing the joining point of two
10074 rendezvous circuits.
10075 - Fix an assert in time parsing found by Steven Murdoch.
10077 o Other bugfixes on 0.1.0.x:
10078 - When we're doing reachability testing, provide more useful log
10079 messages so the operator knows what to expect.
10080 - Do not check whether DirPort is reachable when we are suppressing
10081 advertising it because of hibernation.
10082 - When building with -static or on Solaris, we sometimes needed -ldl.
10083 - One of the dirservers (tor26) changed its IP address.
10084 - When we're deciding whether a stream has enough circuits around
10085 that can handle it, count the freshly dirty ones and not the ones
10086 that are so dirty they won't be able to handle it.
10087 - When we're expiring old circuits, we had a logic error that caused
10088 us to close new rendezvous circuits rather than old ones.
10089 - Give a more helpful log message when you try to change ORPort via
10090 the controller: you should upgrade Tor if you want that to work.
10091 - We were failing to parse Tor versions that start with "Tor ".
10092 - Tolerate faulty streams better: when a stream fails for reason
10093 exitpolicy, stop assuming that the router is lying about his exit
10094 policy. When a stream fails for reason misc, allow it to retry just
10095 as if it was resolvefailed. When a stream has failed three times,
10096 reset its failure count so we can try again and get all three tries.
10099 Changes in version 0.1.0.15 - 2005-09-23
10100 o Bugfixes on 0.1.0.x:
10101 - Reject ports 465 and 587 (spam targets) in default exit policy.
10102 - Don't crash when we don't have any spare file descriptors and we
10103 try to spawn a dns or cpu worker.
10104 - Get rid of IgnoreVersion undocumented config option, and make us
10105 only warn, never exit, when we're running an obsolete version.
10106 - Don't try to print a null string when your server finds itself to
10107 be unreachable and the Address config option is empty.
10108 - Make the numbers in read-history and write-history into uint64s,
10109 so they don't overflow and publish negatives in the descriptor.
10110 - Fix a minor memory leak in smartlist_string_remove().
10111 - We were only allowing ourselves to upload a server descriptor at
10112 most every 20 minutes, even if it changed earlier than that.
10113 - Clean up log entries that pointed to old URLs.
10116 Changes in version 0.1.0.14 - 2005-08-08
10117 o Bugfixes on 0.1.0.x:
10118 - Fix the other half of the bug with crypto handshakes
10120 - Fix an assert trigger if you send a 'signal term' via the
10121 controller when it's listening for 'event info' messages.
10124 Changes in version 0.1.0.13 - 2005-08-04
10125 o Bugfixes on 0.1.0.x:
10126 - Fix a critical bug in the security of our crypto handshakes.
10127 - Fix a size_t underflow in smartlist_join_strings2() that made
10128 it do bad things when you hand it an empty smartlist.
10129 - Fix Windows installer to ship Tor license (thanks to Aphex for
10130 pointing out this oversight) and put a link to the doc directory
10132 - Explicitly set no-unaligned-access for sparc: it turns out the
10133 new gcc's let you compile broken code, but that doesn't make it
10137 Changes in version 0.1.0.12 - 2005-07-18
10138 o New directory servers:
10139 - tor26 has changed IP address.
10141 o Bugfixes on 0.1.0.x:
10142 - Fix a possible double-free in tor_gzip_uncompress().
10143 - When --disable-threads is set, do not search for or link against
10144 pthreads libraries.
10145 - Don't trigger an assert if an authoritative directory server
10146 claims its dirport is 0.
10147 - Fix bug with removing Tor as an NT service: some people were
10148 getting "The service did not return an error." Thanks to Matt
10152 Changes in version 0.1.0.11 - 2005-06-30
10153 o Bugfixes on 0.1.0.x:
10154 - Fix major security bug: servers were disregarding their
10155 exit policies if clients behaved unexpectedly.
10156 - Make OS X init script check for missing argument, so we don't
10157 confuse users who invoke it incorrectly.
10158 - Fix a seg fault in "tor --hash-password foo".
10159 - The MAPADDRESS control command was broken.
10162 Changes in version 0.1.0.10 - 2005-06-14
10164 - Make NT services work and start on startup on Win32 (based on
10165 patch by Matt Edman). See the FAQ entry for details.
10166 - Make 'platform' string in descriptor more accurate for Win32
10167 servers, so it's not just "unknown platform".
10168 - REUSEADDR on normal platforms means you can rebind to the port
10169 right after somebody else has let it go. But REUSEADDR on Win32
10170 means you can bind to the port _even when somebody else already
10171 has it bound_! So, don't do that on Win32.
10172 - Clean up the log messages when starting on Win32 with no config
10174 - Allow seeding the RNG on Win32 even when you're not running as
10175 Administrator. If seeding the RNG on Win32 fails, quit.
10177 o Assert / crash bugs:
10178 - Refuse relay cells that claim to have a length larger than the
10179 maximum allowed. This prevents a potential attack that could read
10180 arbitrary memory (e.g. keys) from an exit server's process
10182 - If unofficial Tor clients connect and send weird TLS certs, our
10183 Tor server triggers an assert. Stop asserting, and start handling
10184 TLS errors better in other situations too.
10185 - Fix a race condition that can trigger an assert when we have a
10186 pending create cell and an OR connection attempt fails.
10189 - Use pthreads for worker processes rather than forking. This was
10190 forced because when we forked, we ended up wasting a lot of
10191 duplicate ram over time.
10192 - Also switch to foo_r versions of some library calls to allow
10193 reentry and threadsafeness.
10194 - Implement --disable-threads configure option. Disable threads on
10195 netbsd and openbsd by default, because they have no reentrant
10196 resolver functions (!), and on solaris since it has other
10198 - Fix possible bug on threading platforms (e.g. win32) which was
10199 leaking a file descriptor whenever a cpuworker or dnsworker died.
10200 - Fix a minor memory leak when somebody establishes an introduction
10201 point at your Tor server.
10202 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
10204 - Add ./configure --with-dmalloc option, to track memory leaks.
10205 - And try to free all memory on closing, so we can detect what
10208 o Protocol correctness:
10209 - When we've connected to an OR and handshaked but didn't like
10210 the result, we were closing the conn without sending destroy
10211 cells back for pending circuits. Now send those destroys.
10212 - Start sending 'truncated' cells back rather than destroy cells
10213 if the circuit closes in front of you. This means we won't have
10214 to abandon partially built circuits.
10215 - Handle changed router status correctly when dirserver reloads
10216 fingerprint file. We used to be dropping all unverified descriptors
10217 right then. The bug was hidden because we would immediately
10218 fetch a directory from another dirserver, which would include the
10219 descriptors we just dropped.
10220 - Revise tor-spec to add more/better stream end reasons.
10221 - Revise all calls to connection_edge_end to avoid sending 'misc',
10222 and to take errno into account where possible.
10223 - Client now retries when streams end early for 'hibernating' or
10224 'resource limit' reasons, rather than failing them.
10225 - Try to be more zealous about calling connection_edge_end when
10226 things go bad with edge conns in connection.c.
10228 o Robustness improvements:
10229 - Better handling for heterogeneous / unreliable nodes:
10230 - Annotate circuits with whether they aim to contain high uptime
10231 nodes and/or high capacity nodes. When building circuits, choose
10233 - This means that every single node in an intro rend circuit,
10234 not just the last one, will have a minimum uptime.
10235 - New config option LongLivedPorts to indicate application streams
10236 that will want high uptime circuits.
10237 - Servers reset uptime when a dir fetch entirely fails. This
10238 hopefully reflects stability of the server's network connectivity.
10239 - If somebody starts his tor server in Jan 2004 and then fixes his
10240 clock, don't make his published uptime be a year.
10241 - Reset published uptime when we wake up from hibernation.
10242 - Introduce a notion of 'internal' circs, which are chosen without
10243 regard to the exit policy of the last hop. Intro and rendezvous
10244 circs must be internal circs, to avoid leaking information. Resolve
10245 and connect streams can use internal circs if they want.
10246 - New circuit pooling algorithm: keep track of what destination ports
10247 we've used recently (start out assuming we'll want to use 80), and
10248 make sure to have enough circs around to satisfy these ports. Also
10249 make sure to have 2 internal circs around if we've required internal
10250 circs lately (and with high uptime if we've seen that lately too).
10251 - Turn addr_policy_compare from a tristate to a quadstate; this should
10252 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
10253 for google.com" problem.
10254 - When a client asks us for a dir mirror and we don't have one,
10255 launch an attempt to get a fresh one.
10256 - First cut at support for "create-fast" cells. Clients can use
10257 these when extending to their first hop, since the TLS already
10258 provides forward secrecy and authentication. Not enabled on
10261 o Reachability testing.
10262 - Your Tor server will automatically try to see if its ORPort and
10263 DirPort are reachable from the outside, and it won't upload its
10264 descriptor until it decides at least ORPort is reachable (when
10265 DirPort is not yet found reachable, publish it as zero).
10266 - When building testing circs for ORPort testing, use only
10267 high-bandwidth nodes, so fewer circuits fail.
10268 - Notice when our IP changes, and reset stats/uptime/reachability.
10269 - Authdirservers don't do ORPort reachability detection, since
10270 they're in clique mode, so it will be rare to find a server not
10271 already connected to them.
10272 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
10276 - Now we allow two unverified servers with the same nickname
10277 but different keys. But if a nickname is verified, only that
10278 nickname+key are allowed.
10279 - If you're an authdirserver connecting to an address:port,
10280 and it's not the OR you were expecting, forget about that
10281 descriptor. If he *was* the one you were expecting, then forget
10282 about all other descriptors for that address:port.
10283 - Allow servers to publish descriptors from 12 hours in the future.
10284 Corollary: only whine about clock skew from the dirserver if
10285 he's a trusted dirserver (since now even verified servers could
10286 have quite wrong clocks).
10287 - Require servers that use the default dirservers to have public IP
10288 addresses. We have too many servers that are configured with private
10289 IPs and their admins never notice the log entries complaining that
10290 their descriptors are being rejected.
10292 o Efficiency improvements:
10293 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
10294 and /dev/poll), and hopefully work better on Windows too.
10295 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
10296 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
10297 - Find libevent even if it's hiding in /usr/local/ and your
10298 CFLAGS and LDFLAGS don't tell you to look there.
10299 - Be able to link with libevent as a shared library (the default
10300 after 1.0d), even if it's hiding in /usr/local/lib and even
10301 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
10302 assuming you're running gcc. Otherwise fail and give a useful
10304 - Switch to a new buffer management algorithm, which tries to avoid
10305 reallocing and copying quite as much. In first tests it looks like
10306 it uses *more* memory on average, but less cpu.
10307 - Switch our internal buffers implementation to use a ring buffer,
10308 to hopefully improve performance for fast servers a lot.
10309 - Reenable the part of the code that tries to flush as soon as an
10310 OR outbuf has a full TLS record available. Perhaps this will make
10311 OR outbufs not grow as huge except in rare cases, thus saving lots
10312 of CPU time plus memory.
10313 - Improve performance for dirservers: stop re-parsing the whole
10314 directory every time you regenerate it.
10315 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
10316 it much faster to look up a circuit for each relay cell.
10317 - Remove most calls to assert_all_pending_dns_resolves_ok(),
10318 since they're eating our cpu on exit nodes.
10319 - Stop wasting time doing a case insensitive comparison for every
10320 dns name every time we do any lookup. Canonicalize the names to
10321 lowercase when you first see them.
10324 - Handle unavailable hidden services better. Handle slow or busy
10325 hidden services better.
10326 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
10327 circ as necessary, if there are any completed ones lying around
10328 when we try to launch one.
10329 - Make hidden services try to establish a rendezvous for 30 seconds
10330 after fetching the descriptor, rather than for n (where n=3)
10331 attempts to build a circuit.
10332 - Adjust maximum skew and age for rendezvous descriptors: let skew
10333 be 48 hours rather than 90 minutes.
10334 - Reject malformed .onion addresses rather then passing them on as
10335 normal web requests.
10338 - More Tor controller support. See
10339 http://tor.eff.org/doc/control-spec.txt for all the new features,
10340 including signals to emulate unix signals from any platform;
10341 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
10342 closestream; closecircuit; etc.
10343 - Encode hashed controller passwords in hex instead of base64,
10344 to make it easier to write controllers.
10345 - Revise control spec and implementation to allow all log messages to
10346 be sent to controller with their severities intact (suggested by
10347 Matt Edman). Disable debug-level logs while delivering a debug-level
10348 log to the controller, to prevent loop. Update TorControl to handle
10349 new log event types.
10351 o New config options/defaults:
10352 - Begin scrubbing sensitive strings from logs by default. Turn off
10353 the config option SafeLogging if you need to do debugging.
10354 - New exit policy: accept most low-numbered ports, rather than
10355 rejecting most low-numbered ports.
10356 - Put a note in the torrc about abuse potential with the default
10358 - Add support for CONNECTing through https proxies, with "HttpsProxy"
10360 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
10361 based on patch from Adam Langley (basic auth only).
10362 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
10363 the fast servers that have been joining lately. (Clients are now
10364 willing to load balance over up to 2 MB of advertised bandwidth
10366 - New config option MaxAdvertisedBandwidth which lets you advertise
10367 a low bandwidthrate (to not attract as many circuits) while still
10368 allowing a higher bandwidthrate in reality.
10369 - Require BandwidthRate to be at least 20kB/s for servers.
10370 - Add a NoPublish config option, so you can be a server (e.g. for
10371 testing running Tor servers in other Tor networks) without
10372 publishing your descriptor to the primary dirservers.
10373 - Add a new AddressMap config directive to rewrite incoming socks
10374 addresses. This lets you, for example, declare an implicit
10375 required exit node for certain sites.
10376 - Add a new TrackHostExits config directive to trigger addressmaps
10377 for certain incoming socks addresses -- for sites that break when
10378 your exit keeps changing (based on patch from Mike Perry).
10379 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
10380 which describes how often we retry making new circuits if current
10381 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
10382 how long we're willing to make use of an already-dirty circuit.
10383 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
10384 a config option "ShutdownWaitLength" (when using kill -INT on
10386 - Fix an edge case in parsing config options: if they say "--"
10387 on the commandline, it's not a config option (thanks weasel).
10388 - New config option DirAllowPrivateAddresses for authdirservers.
10389 Now by default they refuse router descriptors that have non-IP or
10390 private-IP addresses.
10391 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
10392 smart" default value: low for servers and high for clients.
10393 - Some people were putting "Address " in their torrc, and they had
10394 a buggy resolver that resolved " " to 0.0.0.0. Oops.
10395 - If DataDir is ~/.tor, and that expands to /.tor, then default to
10396 LOCALSTATEDIR/tor instead.
10397 - Implement --verify-config command-line option to check if your torrc
10398 is valid without actually launching Tor.
10400 o Logging improvements:
10401 - When dirservers refuse a server descriptor, we now log its
10402 contactinfo, platform, and the poster's IP address.
10403 - Only warn once per nickname from add_nickname_list_to_smartlist()
10404 per failure, so an entrynode or exitnode choice that's down won't
10406 - When we're connecting to an OR and he's got a different nickname/key
10407 than we were expecting, only complain loudly if we're an OP or a
10408 dirserver. Complaining loudly to the OR admins just confuses them.
10409 - Whine at you if you're a server and you don't set your contactinfo.
10410 - Warn when exit policy implicitly allows local addresses.
10411 - Give a better warning when some other server advertises an
10412 ORPort that is actually an apache running ssl.
10413 - If we get an incredibly skewed timestamp from a dirserver mirror
10414 that isn't a verified OR, don't warn -- it's probably him that's
10416 - When a dirserver causes you to give a warn, mention which dirserver
10418 - Initialize libevent later in the startup process, so the logs are
10419 already established by the time we start logging libevent warns.
10420 - Use correct errno on win32 if libevent fails.
10421 - Check and warn about known-bad/slow libevent versions.
10422 - Stop warning about sigpipes in the logs. We're going to
10423 pretend that getting these occassionally is normal and fine.
10425 o New contrib scripts:
10426 - New experimental script tor/contrib/exitlist: a simple python
10427 script to parse directories and find Tor nodes that exit to listed
10429 - New experimental script tor/contrib/ExerciseServer.py (needs more
10430 work) that uses the controller interface to build circuits and
10431 fetch pages over them. This will help us bootstrap servers that
10432 have lots of capacity but haven't noticed it yet.
10433 - New experimental script tor/contrib/PathDemo.py (needs more work)
10434 that uses the controller interface to let you choose whole paths
10436 "<hostname>.<path,separated by dots>.<length of path>.path"
10437 - New contributed script "privoxy-tor-toggle" to toggle whether
10438 Privoxy uses Tor. Seems to be configured for Debian by default.
10439 - Have torctl.in/tor.sh.in check for location of su binary (needed
10443 - chdir() to your datadirectory at the *end* of the daemonize process,
10444 not the beginning. This was a problem because the first time you
10445 run tor, if your datadir isn't there, and you have runasdaemon set
10446 to 1, it will try to chdir to it before it tries to create it. Oops.
10447 - Fix several double-mark-for-close bugs, e.g. where we were finding
10448 a conn for a cell even if that conn is already marked for close.
10449 - Stop most cases of hanging up on a socks connection without sending
10451 - Fix a bug in the RPM package: set home directory for _tor to
10452 something more reasonable when first installing.
10453 - Stop putting nodename in the Platform string in server descriptors.
10454 It doesn't actually help, and it is confusing/upsetting some people.
10455 - When using preferred entry or exit nodes, ignore whether the
10456 circuit wants uptime or capacity. They asked for the nodes, they
10458 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
10459 artificially capped at 500kB.
10460 - Cache local dns resolves correctly even when they're .exit
10462 - If we're hibernating and we get a SIGINT, exit immediately.
10463 - tor-resolve requests were ignoring .exit if there was a working circuit
10464 they could use instead.
10465 - Pay more attention to the ClientOnly config option.
10466 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
10467 installer screens; and don't put stuff into StartupItems unless
10468 the user asks you to.
10471 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
10472 rather than just rejecting it.
10473 - If our clock jumps forward by 100 seconds or more, assume something
10474 has gone wrong with our network and abandon all not-yet-used circs.
10475 - When an application is using socks5, give him the whole variety of
10476 potential socks5 responses (connect refused, host unreachable, etc),
10477 rather than just "success" or "failure".
10478 - A more sane version numbering system. See
10479 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
10480 - Change version parsing logic: a version is "obsolete" if it is not
10481 recommended and (1) there is a newer recommended version in the
10482 same series, or (2) there are no recommended versions in the same
10483 series, but there are some recommended versions in a newer series.
10484 A version is "new" if it is newer than any recommended version in
10486 - Report HTTP reasons to client when getting a response from directory
10487 servers -- so you can actually know what went wrong.
10488 - Reject odd-looking addresses at the client (e.g. addresses that
10489 contain a colon), rather than having the server drop them because
10491 - Stop publishing socksport in the directory, since it's not
10492 actually meant to be public. For compatibility, publish a 0 there
10494 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
10495 cookies to disk and doesn't log each web request to disk. (Thanks
10496 to Brett Carrington for pointing this out.)
10497 - Add OSX uninstall instructions. An actual uninstall script will
10499 - Add "opt hibernating 1" to server descriptor to make it clearer
10500 whether the server is hibernating.
10503 Changes in version 0.0.9.10 - 2005-06-16
10504 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
10505 - Refuse relay cells that claim to have a length larger than the
10506 maximum allowed. This prevents a potential attack that could read
10507 arbitrary memory (e.g. keys) from an exit server's process
10511 Changes in version 0.0.9.9 - 2005-04-23
10512 o Bugfixes on 0.0.9.x:
10513 - If unofficial Tor clients connect and send weird TLS certs, our
10514 Tor server triggers an assert. This release contains a minimal
10515 backport from the broader fix that we put into 0.1.0.4-rc.
10518 Changes in version 0.0.9.8 - 2005-04-07
10519 o Bugfixes on 0.0.9.x:
10520 - We have a bug that I haven't found yet. Sometimes, very rarely,
10521 cpuworkers get stuck in the 'busy' state, even though the cpuworker
10522 thinks of itself as idle. This meant that no new circuits ever got
10523 established. Here's a workaround to kill any cpuworker that's been
10524 busy for more than 100 seconds.
10527 Changes in version 0.0.9.7 - 2005-04-01
10528 o Bugfixes on 0.0.9.x:
10529 - Fix another race crash bug (thanks to Glenn Fink for reporting).
10530 - Compare identity to identity, not to nickname, when extending to
10531 a router not already in the directory. This was preventing us from
10532 extending to unknown routers. Oops.
10533 - Make sure to create OS X Tor user in <500 range, so we aren't
10534 creating actual system users.
10535 - Note where connection-that-hasn't-sent-end was marked, and fix
10536 a few really loud instances of this harmless bug (it's fixed more
10540 Changes in version 0.0.9.6 - 2005-03-24
10541 o Bugfixes on 0.0.9.x (crashes and asserts):
10542 - Add new end stream reasons to maintainance branch. Fix bug where
10543 reason (8) could trigger an assert. Prevent bug from recurring.
10544 - Apparently win32 stat wants paths to not end with a slash.
10545 - Fix assert triggers in assert_cpath_layer_ok(), where we were
10546 blowing away the circuit that conn->cpath_layer points to, then
10547 checking to see if the circ is well-formed. Backport check to make
10548 sure we dont use the cpath on a closed connection.
10549 - Prevent circuit_resume_edge_reading_helper() from trying to package
10550 inbufs for marked-for-close streams.
10551 - Don't crash on hup if your options->address has become unresolvable.
10552 - Some systems (like OS X) sometimes accept() a connection and tell
10553 you the remote host is 0.0.0.0:0. If this happens, due to some
10554 other mis-features, we get confused; so refuse the conn for now.
10556 o Bugfixes on 0.0.9.x (other):
10557 - Fix harmless but scary "Unrecognized content encoding" warn message.
10558 - Add new stream error reason: TORPROTOCOL reason means "you are not
10559 speaking a version of Tor I understand; say bye-bye to your stream."
10560 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
10561 into the future, now that we are more tolerant of skew. This
10562 resolves a bug where a Tor server would refuse to cache a directory
10563 because all the directories it gets are too far in the future;
10564 yet the Tor server never logs any complaints about clock skew.
10565 - Mac packaging magic: make man pages useable, and do not overwrite
10566 existing torrc files.
10567 - Make OS X log happily to /var/log/tor/tor.log
10570 Changes in version 0.0.9.5 - 2005-02-22
10571 o Bugfixes on 0.0.9.x:
10572 - Fix an assert race at exit nodes when resolve requests fail.
10573 - Stop picking unverified dir mirrors--it only leads to misery.
10574 - Patch from Matt Edman to make NT services work better. Service
10575 support is still not compiled into the executable by default.
10576 - Patch from Dmitri Bely so the Tor service runs better under
10577 the win32 SYSTEM account.
10578 - Make tor-resolve actually work (?) on Win32.
10579 - Fix a sign bug when getrlimit claims to have 4+ billion
10580 file descriptors available.
10581 - Stop refusing to start when bandwidthburst == bandwidthrate.
10582 - When create cells have been on the onion queue more than five
10583 seconds, just send back a destroy and take them off the list.
10586 Changes in version 0.0.9.4 - 2005-02-03
10587 o Bugfixes on 0.0.9:
10588 - Fix an assert bug that took down most of our servers: when
10589 a server claims to have 1 GB of bandwidthburst, don't
10591 - Don't crash as badly if we have spawned the max allowed number
10592 of dnsworkers, or we're out of file descriptors.
10593 - Block more file-sharing ports in the default exit policy.
10594 - MaxConn is now automatically set to the hard limit of max
10595 file descriptors we're allowed (ulimit -n), minus a few for
10597 - Give a clearer message when servers need to raise their
10598 ulimit -n when they start running out of file descriptors.
10599 - SGI Compatibility patches from Jan Schaumann.
10600 - Tolerate a corrupt cached directory better.
10601 - When a dirserver hasn't approved your server, list which one.
10602 - Go into soft hibernation after 95% of the bandwidth is used,
10603 not 99%. This is especially important for daily hibernators who
10604 have a small accounting max. Hopefully it will result in fewer
10605 cut connections when the hard hibernation starts.
10606 - Load-balance better when using servers that claim more than
10607 800kB/s of capacity.
10608 - Make NT services work (experimental, only used if compiled in).
10611 Changes in version 0.0.9.3 - 2005-01-21
10612 o Bugfixes on 0.0.9:
10613 - Backport the cpu use fixes from main branch, so busy servers won't
10614 need as much processor time.
10615 - Work better when we go offline and then come back, or when we
10616 run Tor at boot before the network is up. We do this by
10617 optimistically trying to fetch a new directory whenever an
10618 application request comes in and we think we're offline -- the
10619 human is hopefully a good measure of when the network is back.
10620 - Backport some minimal hidserv bugfixes: keep rend circuits open as
10621 long as you keep using them; actually publish hidserv descriptors
10622 shortly after they change, rather than waiting 20-40 minutes.
10623 - Enable Mac startup script by default.
10624 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
10625 - When you update AllowUnverifiedNodes or FirewallPorts via the
10626 controller's setconf feature, we were always appending, never
10628 - When you update HiddenServiceDir via setconf, it was screwing up
10629 the order of reading the lines, making it fail.
10630 - Do not rewrite a cached directory back to the cache; otherwise we
10631 will think it is recent and not fetch a newer one on startup.
10632 - Workaround for webservers that lie about Content-Encoding: Tor
10633 now tries to autodetect compressed directories and compression
10634 itself. This lets us Proxypass dir fetches through apache.
10637 Changes in version 0.0.9.2 - 2005-01-04
10638 o Bugfixes on 0.0.9 (crashes and asserts):
10639 - Fix an assert on startup when the disk is full and you're logging
10641 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
10642 style address, then we'd crash.
10643 - Fix an assert trigger when the running-routers string we get from
10644 a dirserver is broken.
10645 - Make worker threads start and run on win32. Now win32 servers
10647 - Bandaid (not actually fix, but now it doesn't crash) an assert
10648 where the dns worker dies mysteriously and the main Tor process
10649 doesn't remember anything about the address it was resolving.
10651 o Bugfixes on 0.0.9 (Win32):
10652 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
10653 name out of the warning/assert messages.
10654 - Fix a superficial "unhandled error on read" bug on win32.
10655 - The win32 installer no longer requires a click-through for our
10656 license, since our Free Software license grants rights but does not
10658 - Win32: When connecting to a dirserver fails, try another one
10659 immediately. (This was already working for non-win32 Tors.)
10660 - Stop trying to parse $HOME on win32 when hunting for default
10662 - Make tor-resolve.c work on win32 by calling network_init().
10664 o Bugfixes on 0.0.9 (other):
10665 - Make 0.0.9.x build on Solaris again.
10666 - Due to a fencepost error, we were blowing away the \n when reporting
10667 confvalue items in the controller. So asking for multiple config
10668 values at once couldn't work.
10669 - When listing circuits that are pending on an opening OR connection,
10670 if we're an OR we were listing circuits that *end* at us as
10671 being pending on every listener, dns/cpu worker, etc. Stop that.
10672 - Dirservers were failing to create 'running-routers' or 'directory'
10673 strings if we had more than some threshold of routers. Fix them so
10674 they can handle any number of routers.
10675 - Fix a superficial "Duplicate mark for close" bug.
10676 - Stop checking for clock skew for OR connections, even for servers.
10677 - Fix a fencepost error that was chopping off the last letter of any
10678 nickname that is the maximum allowed nickname length.
10679 - Update URLs in log messages so they point to the new website.
10680 - Fix a potential problem in mangling server private keys while
10681 writing to disk (not triggered yet, as far as we know).
10682 - Include the licenses for other free software we include in Tor,
10683 now that we're shipping binary distributions more regularly.
10686 Changes in version 0.0.9.1 - 2004-12-15
10687 o Bugfixes on 0.0.9:
10688 - Make hibernation actually work.
10689 - Make HashedControlPassword config option work.
10690 - When we're reporting event circuit status to a controller,
10691 don't use the stream status code.
10694 Changes in version 0.0.9 - 2004-12-12
10695 o Bugfixes on 0.0.8.1 (Crashes and asserts):
10696 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
10697 write() call will fail and we handle it there.
10698 - When we run out of disk space, or other log writing error, don't
10699 crash. Just stop logging to that log and continue.
10700 - Fix isspace() and friends so they still make Solaris happy
10701 but also so they don't trigger asserts on win32.
10702 - Fix assert failure on malformed socks4a requests.
10703 - Fix an assert bug where a hidden service provider would fail if
10704 the first hop of his rendezvous circuit was down.
10705 - Better handling of size_t vs int, so we're more robust on 64
10708 o Bugfixes on 0.0.8.1 (Win32):
10709 - Make windows sockets actually non-blocking (oops), and handle
10710 win32 socket errors better.
10711 - Fix parse_iso_time on platforms without strptime (eg win32).
10712 - win32: when being multithreaded, leave parent fdarray open.
10713 - Better handling of winsock includes on non-MSV win32 compilers.
10714 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
10716 - Make unit tests work on win32.
10718 o Bugfixes on 0.0.8.1 (Path selection and streams):
10719 - Calculate timeout for waiting for a connected cell from the time
10720 we sent the begin cell, not from the time the stream started. If
10721 it took a long time to establish the circuit, we would time out
10722 right after sending the begin cell.
10723 - Fix router_compare_addr_to_addr_policy: it was not treating a port
10724 of * as always matching, so we were picking reject *:* nodes as
10725 exit nodes too. Oops.
10726 - When read() failed on a stream, we would close it without sending
10727 back an end. So 'connection refused' would simply be ignored and
10728 the user would get no response.
10729 - Stop a sigpipe: when an 'end' cell races with eof from the app,
10730 we shouldn't hold-open-until-flush if the eof arrived first.
10731 - Let resolve conns retry/expire also, rather than sticking around
10733 - Fix more dns related bugs: send back resolve_failed and end cells
10734 more reliably when the resolve fails, rather than closing the
10735 circuit and then trying to send the cell. Also attach dummy resolve
10736 connections to a circuit *before* calling dns_resolve(), to fix
10737 a bug where cached answers would never be sent in RESOLVED cells.
10739 o Bugfixes on 0.0.8.1 (Circuits):
10740 - Finally fix a bug that's been plaguing us for a year:
10741 With high load, circuit package window was reaching 0. Whenever
10742 we got a circuit-level sendme, we were reading a lot on each
10743 socket, but only writing out a bit. So we would eventually reach
10744 eof. This would be noticed and acted on even when there were still
10745 bytes sitting in the inbuf.
10746 - Use identity comparison, not nickname comparison, to choose which
10747 half of circuit-ID-space each side gets to use. This is needed
10748 because sometimes we think of a router as a nickname, and sometimes
10749 as a hex ID, and we can't predict what the other side will do.
10751 o Bugfixes on 0.0.8.1 (Other):
10752 - Fix a whole slew of memory leaks.
10753 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
10754 - If we are using select, make sure we stay within FD_SETSIZE.
10755 - When poll() is interrupted, we shouldn't believe the revents values.
10756 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
10757 and smartlist_len, which are two major profiling offenders.
10758 - If do_hup fails, actually notice.
10759 - Flush the log file descriptor after we print "Tor opening log file",
10760 so we don't see those messages days later.
10761 - Hidden service operators now correctly handle version 1 style
10762 INTRODUCE1 cells (nobody generates them still, so not a critical
10764 - Handle more errnos from accept() without closing the listener.
10765 Some OpenBSD machines were closing their listeners because
10766 they ran out of file descriptors.
10767 - Some people had wrapped their tor client/server in a script
10768 that would restart it whenever it died. This did not play well
10769 with our "shut down if your version is obsolete" code. Now people
10770 don't fetch a new directory if their local cached version is
10772 - Make our autogen.sh work on ksh as well as bash.
10773 - Better torrc example lines for dirbindaddress and orbindaddress.
10774 - Improved bounds checking on parsed ints (e.g. config options and
10775 the ones we find in directories.)
10776 - Stop using separate defaults for no-config-file and
10777 empty-config-file. Now you have to explicitly turn off SocksPort,
10778 if you don't want it open.
10779 - We were starting to daemonize before we opened our logs, so if
10780 there were any problems opening logs, we would complain to stderr,
10781 which wouldn't work, and then mysteriously exit.
10782 - If a verified OR connects to us before he's uploaded his descriptor,
10783 or we verify him and hup but he still has the original TLS
10784 connection, then conn->nickname is still set like he's unverified.
10786 o Code security improvements, inspired by Ilja:
10787 - tor_snprintf wrapper over snprintf with consistent (though not C99)
10789 - Replace sprintf with tor_snprintf. (I think they were all safe, but
10791 - Replace strcpy/strncpy with strlcpy in more places.
10792 - Avoid strcat; use tor_snprintf or strlcat instead.
10794 o Features (circuits and streams):
10795 - New circuit building strategy: keep a list of ports that we've
10796 used in the past 6 hours, and always try to have 2 circuits open
10797 or on the way that will handle each such port. Seed us with port
10798 80 so web users won't complain that Tor is "slow to start up".
10799 - Make kill -USR1 dump more useful stats about circuits.
10800 - When warning about retrying or giving up, print the address, so
10801 the user knows which one it's talking about.
10802 - If you haven't used a clean circuit in an hour, throw it away,
10803 just to be on the safe side. (This means after 6 hours a totally
10804 unused Tor client will have no circuits open.)
10805 - Support "foo.nickname.exit" addresses, to let Alice request the
10806 address "foo" as viewed by exit node "nickname". Based on a patch
10807 from Geoff Goodell.
10808 - If your requested entry or exit node has advertised bandwidth 0,
10810 - Be more greedy about filling up relay cells -- we try reading again
10811 once we've processed the stuff we read, in case enough has arrived
10812 to fill the last cell completely.
10813 - Refuse application socks connections to port 0.
10814 - Use only 0.0.9pre1 and later servers for resolve cells.
10816 o Features (bandwidth):
10817 - Hibernation: New config option "AccountingMax" lets you
10818 set how many bytes per month (in each direction) you want to
10819 allow your server to consume. Rather than spreading those
10820 bytes out evenly over the month, we instead hibernate for some
10821 of the month and pop up at a deterministic time, work until
10822 the bytes are consumed, then hibernate again. Config option
10823 "MonthlyAccountingStart" lets you specify which day of the month
10824 your billing cycle starts on.
10825 - Implement weekly/monthly/daily accounting: now you specify your
10826 hibernation properties by
10827 AccountingMax N bytes|KB|MB|GB|TB
10828 AccountingStart day|week|month [day] HH:MM
10829 Defaults to "month 1 0:00".
10830 - Let bandwidth and interval config options be specified as 5 bytes,
10831 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
10833 o Features (directories):
10834 - New "router-status" line in directory, to better bind each verified
10835 nickname to its identity key.
10836 - Clients can ask dirservers for /dir.z to get a compressed version
10837 of the directory. Only works for servers running 0.0.9, of course.
10838 - Make clients cache directories and use them to seed their router
10839 lists at startup. This means clients have a datadir again.
10840 - Respond to content-encoding headers by trying to uncompress as
10842 - Clients and servers now fetch running-routers; cache
10843 running-routers; compress running-routers; serve compressed
10845 - Make moria2 advertise a dirport of 80, so people behind firewalls
10846 will be able to get a directory.
10847 - Http proxy support
10848 - Dirservers translate requests for http://%s:%d/x to /x
10849 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
10850 be routed through this host.
10851 - Clients ask for /tor/x rather than /x for new enough dirservers.
10852 This way we can one day coexist peacefully with apache.
10853 - Clients specify a "Host: %s%d" http header, to be compatible
10854 with more proxies, and so running squid on an exit node can work.
10855 - Protect dirservers from overzealous descriptor uploading -- wait
10856 10 seconds after directory gets dirty, before regenerating.
10858 o Features (packages and install):
10859 - Add NSI installer contributed by J Doe.
10860 - Apply NT service patch from Osamu Fujino. Still needs more work.
10861 - Commit VC6 and VC7 workspace/project files.
10862 - Commit a tor.spec for making RPM files, with help from jbash.
10863 - Add contrib/torctl.in contributed by Glenn Fink.
10864 - Make expand_filename handle ~ and ~username.
10865 - Use autoconf to enable largefile support where necessary. Use
10866 ftello where available, since ftell can fail at 2GB.
10867 - Ship src/win32/ in the tarball, so people can use it to build.
10868 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
10871 o Features (ui controller):
10872 - Control interface: a separate program can now talk to your
10873 client/server over a socket, and get/set config options, receive
10874 notifications of circuits and streams starting/finishing/dying,
10875 bandwidth used, etc. The next step is to get some GUIs working.
10876 Let us know if you want to help out. See doc/control-spec.txt .
10877 - Ship a contrib/tor-control.py as an example script to interact
10878 with the control port.
10879 - "tor --hash-password zzyxz" will output a salted password for
10880 use in authenticating to the control interface.
10881 - Implement the control-spec's SAVECONF command, to write your
10882 configuration to torrc.
10883 - Get cookie authentication for the controller closer to working.
10884 - When set_conf changes our server descriptor, upload a new copy.
10885 But don't upload it too often if there are frequent changes.
10887 o Features (config and command-line):
10888 - Deprecate unofficial config option abbreviations, and abbreviations
10889 not on the command line.
10890 - Configuration infrastructure support for warning on obsolete
10892 - Give a slightly more useful output for "tor -h".
10893 - Break DirFetchPostPeriod into:
10894 - DirFetchPeriod for fetching full directory,
10895 - StatusFetchPeriod for fetching running-routers,
10896 - DirPostPeriod for posting server descriptor,
10897 - RendPostPeriod for posting hidden service descriptors.
10898 - New log format in config:
10899 "Log minsev[-maxsev] stdout|stderr|syslog" or
10900 "Log minsev[-maxsev] file /var/foo"
10901 - DirPolicy config option, to let people reject incoming addresses
10902 from their dirserver.
10903 - "tor --list-fingerprint" will list your identity key fingerprint
10905 - Make tor --version --version dump the cvs Id of every file.
10906 - New 'MyFamily nick1,...' config option for a server to
10907 specify other servers that shouldn't be used in the same circuit
10908 with it. Only believed if nick1 also specifies us.
10909 - New 'NodeFamily nick1,nick2,...' config option for a client to
10910 specify nodes that it doesn't want to use in the same circuit.
10911 - New 'Redirectexit pattern address:port' config option for a
10912 server to redirect exit connections, e.g. to a local squid.
10913 - Add "pass" target for RedirectExit, to make it easier to break
10914 out of a sequence of RedirectExit rules.
10915 - Make the dirservers file obsolete.
10916 - Include a dir-signing-key token in directories to tell the
10917 parsing entity which key is being used to sign.
10918 - Remove the built-in bulky default dirservers string.
10919 - New config option "Dirserver %s:%d [fingerprint]", which can be
10920 repeated as many times as needed. If no dirservers specified,
10921 default to moria1,moria2,tor26.
10922 - Make 'Routerfile' config option obsolete.
10923 - Discourage people from setting their dirfetchpostperiod more often
10924 than once per minute.
10926 o Features (other):
10927 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
10928 get back to normal.)
10929 - Accept *:706 (silc) in default exit policy.
10930 - Implement new versioning format for post 0.1.
10931 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
10932 log more informatively.
10933 - Check clock skew for verified servers, but allow unverified
10934 servers and clients to have any clock skew.
10935 - Make sure the hidden service descriptors are at a random offset
10936 from each other, to hinder linkability.
10937 - Clients now generate a TLS cert too, in preparation for having
10938 them act more like real nodes.
10939 - Add a pure-C tor-resolve implementation.
10940 - Use getrlimit and friends to ensure we can reach MaxConn (currently
10941 1024) file descriptors.
10942 - Raise the max dns workers from 50 to 100.
10945 Changes in version 0.0.8.1 - 2004-10-13
10947 - Fix a seg fault that can be triggered remotely for Tor
10948 clients/servers with an open dirport.
10949 - Fix a rare assert trigger, where routerinfos for entries in
10950 our cpath would expire while we're building the path.
10951 - Fix a bug in OutboundBindAddress so it (hopefully) works.
10952 - Fix a rare seg fault for people running hidden services on
10953 intermittent connections.
10954 - Fix a bug in parsing opt keywords with objects.
10955 - Fix a stale pointer assert bug when a stream detaches and
10957 - Fix a string format vulnerability (probably not exploitable)
10958 in reporting stats locally.
10959 - Fix an assert trigger: sometimes launching circuits can fail
10960 immediately, e.g. because too many circuits have failed recently.
10961 - Fix a compile warning on 64 bit platforms.
10964 Changes in version 0.0.8 - 2004-08-25
10966 - Made our unit tests compile again on OpenBSD 3.5, and tor
10967 itself compile again on OpenBSD on a sparc64.
10968 - We were neglecting milliseconds when logging on win32, so
10969 everything appeared to happen at the beginning of each second.
10970 - Check directory signature _before_ you decide whether you're
10971 you're running an obsolete version and should exit.
10972 - Check directory signature _before_ you parse the running-routers
10973 list to decide who's running.
10974 - Check return value of fclose while writing to disk, so we don't
10975 end up with broken files when servers run out of disk space.
10976 - Port it to SunOS 5.9 / Athena
10977 - Fix two bugs in saving onion keys to disk when rotating, so
10978 hopefully we'll get fewer people using old onion keys.
10979 - Remove our mostly unused -- and broken -- hex_encode()
10980 function. Use base16_encode() instead. (Thanks to Timo Lindfors
10981 for pointing out this bug.)
10982 - Only pick and establish intro points after we've gotten a
10984 - Fix assert triggers: if the other side returns an address 0.0.0.0,
10985 don't put it into the client dns cache.
10986 - If a begin failed due to exit policy, but we believe the IP
10987 address should have been allowed, switch that router to exitpolicy
10988 reject *:* until we get our next directory.
10990 o Protocol changes:
10991 - 'Extend' relay cell payloads now include the digest of the
10992 intended next hop's identity key. Now we can verify that we're
10993 extending to the right router, and also extend to routers we
10994 hadn't heard of before.
10997 - Tor nodes can now act as relays (with an advertised ORPort)
10998 without being manually verified by the dirserver operators.
10999 - Uploaded descriptors of unverified routers are now accepted
11000 by the dirservers, and included in the directory.
11001 - Verified routers are listed by nickname in the running-routers
11002 list; unverified routers are listed as "$<fingerprint>".
11003 - We now use hash-of-identity-key in most places rather than
11004 nickname or addr:port, for improved security/flexibility.
11005 - AllowUnverifiedNodes config option to let circuits choose no-name
11006 routers in entry,middle,exit,introduction,rendezvous positions.
11007 Allow middle and rendezvous positions by default.
11008 - When picking unverified routers, skip those with low uptime and/or
11009 low bandwidth, depending on what properties you care about.
11010 - ClientOnly option for nodes that never want to become servers.
11011 - Directory caching.
11012 - "AuthoritativeDir 1" option for the official dirservers.
11013 - Now other nodes (clients and servers) will cache the latest
11014 directory they've pulled down.
11015 - They can enable their DirPort to serve it to others.
11016 - Clients will pull down a directory from any node with an open
11017 DirPort, and check the signature/timestamp correctly.
11018 - Authoritative dirservers now fetch directories from other
11019 authdirservers, to stay better synced.
11020 - Running-routers list tells who's down also, along with noting
11021 if they're verified (listed by nickname) or unverified (listed
11023 - Allow dirservers to serve running-router list separately.
11024 This isn't used yet.
11025 - You can now fetch $DIRURL/running-routers to get just the
11026 running-routers line, not the whole descriptor list. (But
11027 clients don't use this yet.)
11028 - Clients choose nodes proportional to advertised bandwidth.
11029 - Clients avoid using nodes with low uptime as introduction points.
11030 - Handle servers with dynamic IP addresses: don't just replace
11031 options->Address with the resolved one at startup, and
11032 detect our address right before we make a routerinfo each time.
11033 - 'FascistFirewall' option to pick dirservers and ORs on specific
11034 ports; plus 'FirewallPorts' config option to tell FascistFirewall
11035 which ports are open. (Defaults to 80,443)
11036 - Try other dirservers immediately if the one you try is down. This
11037 should tolerate down dirservers better now.
11038 - ORs connect-on-demand to other ORs
11039 - If you get an extend cell to an OR you're not connected to,
11040 connect, handshake, and forward the create cell.
11041 - The authoritative dirservers stay connected to everybody,
11042 and everybody stays connected to 0.0.7 servers, but otherwise
11043 clients/servers expire unused connections after 5 minutes.
11044 - When servers get a sigint, they delay 30 seconds (refusing new
11045 connections) then exit. A second sigint causes immediate exit.
11046 - File and name management:
11047 - Look for .torrc if no CONFDIR "torrc" is found.
11048 - If no datadir is defined, then choose, make, and secure ~/.tor
11050 - If torrc not found, exitpolicy reject *:*.
11051 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
11052 - If no nickname is defined, derive default from hostname.
11053 - Rename secret key files, e.g. identity.key -> secret_id_key,
11054 to discourage people from mailing their identity key to tor-ops.
11055 - Refuse to build a circuit before the directory has arrived --
11056 it won't work anyway, since you won't know the right onion keys
11058 - Parse tor version numbers so we can do an is-newer-than check
11059 rather than an is-in-the-list check.
11060 - New socks command 'resolve', to let us shim gethostbyname()
11062 - A 'tor_resolve' script to access the socks resolve functionality.
11063 - A new socks-extensions.txt doc file to describe our
11064 interpretation and extensions to the socks protocols.
11065 - Add a ContactInfo option, which gets published in descriptor.
11066 - Write tor version at the top of each log file
11067 - New docs in the tarball:
11069 - Document that you should proxy your SSL traffic too.
11070 - Log a warning if the user uses an unsafe socks variant, so people
11071 are more likely to learn about privoxy or socat.
11072 - Log a warning if you're running an unverified server, to let you
11073 know you might want to get it verified.
11074 - Change the default exit policy to reject the default edonkey,
11075 kazaa, gnutella ports.
11076 - Add replace_file() to util.[ch] to handle win32's rename().
11077 - Publish OR uptime in descriptor (and thus in directory) too.
11078 - Remember used bandwidth (both in and out), and publish 15-minute
11079 snapshots for the past day into our descriptor.
11080 - Be more aggressive about trying to make circuits when the network
11081 has changed (e.g. when you unsuspend your laptop).
11082 - Check for time skew on http headers; report date in response to
11084 - If the entrynode config line has only one node, don't pick it as
11086 - Add strict{entry|exit}nodes config options. If set to 1, then
11087 we refuse to build circuits that don't include the specified entry
11089 - OutboundBindAddress config option, to bind to a specific
11090 IP address for outgoing connect()s.
11091 - End truncated log entries (e.g. directories) with "[truncated]".
11094 Changes in version 0.0.7.3 - 2004-08-12
11095 o Stop dnsworkers from triggering an assert failure when you
11096 ask them to resolve the host "".
11099 Changes in version 0.0.7.2 - 2004-07-07
11100 o A better fix for the 0.0.0.0 problem, that will hopefully
11101 eliminate the remaining related assertion failures.
11104 Changes in version 0.0.7.1 - 2004-07-04
11105 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
11106 since internally we use 0.0.0.0 to signify "not yet resolved".
11109 Changes in version 0.0.7 - 2004-06-07
11110 o Fixes for crashes and other obnoxious bugs:
11111 - Fix an epipe bug: sometimes when directory connections failed
11112 to connect, we would give them a chance to flush before closing
11114 - When we detached from a circuit because of resolvefailed, we
11115 would immediately try the same circuit twice more, and then
11116 give up on the resolve thinking we'd tried three different
11118 - Limit the number of intro circuits we'll attempt to build for a
11119 hidden service per 15-minute period.
11120 - Check recommended-software string *early*, before actually parsing
11121 the directory. Thus we can detect an obsolete version and exit,
11122 even if the new directory format doesn't parse.
11123 o Fixes for security bugs:
11124 - Remember which nodes are dirservers when you startup, and if a
11125 random OR enables his dirport, don't automatically assume he's
11126 a trusted dirserver.
11128 - Directory connections were asking the wrong poll socket to
11129 start writing, and not asking themselves to start writing.
11130 - When we detached from a circuit because we sent a begin but
11131 didn't get a connected, we would use it again the first time;
11132 but after that we would correctly switch to a different one.
11133 - Stop warning when the first onion decrypt attempt fails; they
11134 will sometimes legitimately fail now that we rotate keys.
11135 - Override unaligned-access-ok check when $host_cpu is ia64 or
11136 arm. Apparently they allow it but the kernel whines.
11137 - Dirservers try to reconnect periodically too, in case connections
11139 - Fix some memory leaks in directory servers.
11140 - Allow backslash in Win32 filenames.
11141 - Made Tor build complain-free on FreeBSD, hopefully without
11142 breaking other BSD builds. We'll see.
11143 - Check directory signatures based on name of signer, not on whom
11144 we got the directory from. This will let us cache directories more
11146 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
11149 - Doxygen markup on all functions and global variables.
11150 - Make directory functions update routerlist, not replace it. So
11151 now directory disagreements are not so critical a problem.
11152 - Remove the upper limit on number of descriptors in a dirserver's
11153 directory (not that we were anywhere close).
11154 - Allow multiple logfiles at different severity ranges.
11155 - Allow *BindAddress to specify ":port" rather than setting *Port
11156 separately. Allow multiple instances of each BindAddress config
11157 option, so you can bind to multiple interfaces if you want.
11158 - Allow multiple exit policy lines, which are processed in order.
11159 Now we don't need that huge line with all the commas in it.
11160 - Enable accept/reject policies on SOCKS connections, so you can bind
11161 to 0.0.0.0 but still control who can use your OP.
11162 - Updated the man page to reflect these features.
11165 Changes in version 0.0.6.2 - 2004-05-16
11166 o Our integrity-checking digest was checking only the most recent cell,
11167 not the previous cells like we'd thought.
11168 Thanks to Stefan Mark for finding the flaw!
11171 Changes in version 0.0.6.1 - 2004-05-06
11172 o Fix two bugs in our AES counter-mode implementation (this affected
11173 onion-level stream encryption, but not TLS-level). It turns
11174 out we were doing something much more akin to a 16-character
11175 polyalphabetic cipher. Oops.
11176 Thanks to Stefan Mark for finding the flaw!
11177 o Retire moria3 as a directory server, and add tor26 as a directory
11181 Changes in version 0.0.6 - 2004-05-02
11183 - Hidden services and rendezvous points are implemented. Go to
11184 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
11185 hidden services. (This only works via a socks4a proxy such as
11186 Privoxy, and currently it's quite slow.)
11187 - We now rotate link (tls context) keys and onion keys.
11188 - CREATE cells now include oaep padding, so you can tell
11189 if you decrypted them correctly.
11190 - Retry stream correctly when we fail to connect because of
11191 exit-policy-reject (should try another) or can't-resolve-address.
11192 - When we hup a dirserver and we've *removed* a server from the
11193 approved-routers list, now we remove that server from the
11194 in-memory directories too.
11195 - Add bandwidthburst to server descriptor.
11196 - Directories now say which dirserver signed them.
11197 - Use a tor_assert macro that logs failed assertions too.
11198 - Since we don't support truncateds much, don't bother sending them;
11199 just close the circ.
11200 - Fetch randomness from /dev/urandom better (not via fopen/fread)
11201 - Better debugging for tls errors
11202 - Set Content-Type on the directory and hidserv descriptor.
11203 - Remove IVs from cipher code, since AES-ctr has none.
11205 - Fix an assert trigger for exit nodes that's been plaguing us since
11206 the days of 0.0.2prexx (thanks weasel!)
11207 - Fix a bug where we were closing tls connections intermittently.
11208 It turns out openssl keeps its errors around -- so if an error
11209 happens, and you don't ask about it, and then another openssl
11210 operation happens and succeeds, and you ask if there was an error,
11211 it tells you about the first error.
11212 - Fix a bug that's been lurking since 27 may 03 (!)
11213 When passing back a destroy cell, we would use the wrong circ id.
11214 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
11215 - Some versions of openssl have an SSL_pending function that erroneously
11216 returns bytes when there is a non-application record pending.
11217 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
11218 o We were using an array of length zero in a few places.
11219 o Win32's gethostbyname can't resolve an IP to an IP.
11220 o Win32's close can't close a socket.
11221 o Handle windows socket errors correctly.
11223 - check for <sys/limits.h> so we build on FreeBSD again, and
11224 <machine/limits.h> for NetBSD.
11227 Changes in version 0.0.5 - 2004-03-30
11228 o Install torrc as torrc.sample -- we no longer clobber your
11230 o Fix mangled-state bug in directory fetching (was causing sigpipes).
11231 o Only build circuits after we've fetched the directory: clients were
11232 using only the directory servers before they'd fetched a directory.
11233 This also means longer startup time; so it goes.
11234 o Fix an assert trigger where an OP would fail to handshake, and we'd
11235 expect it to have a nickname.
11236 o Work around a tsocks bug: do a socks reject when AP connection dies
11237 early, else tsocks goes into an infinite loop.
11238 o Hold socks connection open until reply is flushed (if possible)
11239 o Make exit nodes resolve IPs to IPs immediately, rather than asking
11240 the dns farm to do it.
11241 o Fix c99 aliasing warnings in rephist.c
11242 o Don't include server descriptors that are older than 24 hours in the
11244 o Give socks 'reject' replies their whole 15s to attempt to flush,
11245 rather than seeing the 60s timeout and assuming the flush had failed.
11246 o Clean automake droppings from the cvs repository
11247 o Add in a 'notice' log level for things the operator should hear
11248 but that aren't warnings
11251 Changes in version 0.0.4 - 2004-03-26
11252 o When connecting to a dirserver or OR and the network is down,
11256 Changes in version 0.0.3 - 2004-03-26
11257 o Warn and fail if server chose a nickname with illegal characters
11258 o Port to Solaris and Sparc:
11259 - include missing header fcntl.h
11260 - have autoconf find -lsocket -lnsl automatically
11261 - deal with hardware word alignment
11262 - make uname() work (solaris has a different return convention)
11263 - switch from using signal() to sigaction()
11264 o Preliminary work on reputation system:
11265 - Keep statistics on success/fail of connect attempts; they're published
11266 by kill -USR1 currently.
11267 - Add a RunTesting option to try to learn link state by creating test
11268 circuits, even when SocksPort is off.
11269 - Remove unused open circuits when there are too many.
11272 Changes in version 0.0.2 - 2004-03-19
11273 - Include strlcpy and strlcat for safer string ops
11274 - define INADDR_NONE so we compile (but still not run) on solaris
11277 Changes in version 0.0.2pre27 - 2004-03-14
11279 - Allow internal tor networks (we were rejecting internal IPs,
11280 now we allow them if they're set explicitly).
11281 - And fix a few endian issues.
11284 Changes in version 0.0.2pre26 - 2004-03-14
11286 - If a stream times out after 15s without a connected cell, don't
11287 try that circuit again: try a new one.
11288 - Retry streams at most 4 times. Then give up.
11289 - When a dirserver gets a descriptor from an unknown router, it
11290 logs its fingerprint (so the dirserver operator can choose to
11291 accept it even without mail from the server operator).
11292 - Inform unapproved servers when we reject their descriptors.
11293 - Make tor build on Windows again. It works as a client, who knows
11295 - Clearer instructions in the torrc for how to set up a server.
11296 - Be more efficient about reading fd's when our global token bucket
11297 (used for rate limiting) becomes empty.
11299 - Stop asserting that computers always go forward in time. It's
11301 - When we sent a cell (e.g. destroy) and then marked an OR connection
11302 expired, we might close it before finishing a flush if the other
11303 side isn't reading right then.
11304 - Don't allow dirservers to start if they haven't defined
11305 RecommendedVersions
11306 - We were caching transient dns failures. Oops.
11307 - Prevent servers from publishing an internal IP as their address.
11308 - Address a strcat vulnerability in circuit.c
11311 Changes in version 0.0.2pre25 - 2004-03-04
11313 - Put the OR's IP in its router descriptor, not its fqdn. That way
11314 we'll stop being stalled by gethostbyname for nodes with flaky dns,
11317 - If the user typed in an address that didn't resolve, the server
11321 Changes in version 0.0.2pre24 - 2004-03-03
11323 - Fix an assertion failure in dns.c, where we were trying to dequeue
11324 a pending dns resolve even if it wasn't pending
11325 - Fix a spurious socks5 warning about still trying to write after the
11326 connection is finished.
11327 - Hold certain marked_for_close connections open until they're finished
11328 flushing, rather than losing bytes by closing them too early.
11329 - Correctly report the reason for ending a stream
11330 - Remove some duplicate calls to connection_mark_for_close
11331 - Put switch_id and start_daemon earlier in the boot sequence, so it
11332 will actually try to chdir() to options.DataDirectory
11333 - Make 'make test' exit(1) if a test fails; fix some unit tests
11334 - Make tor fail when you use a config option it doesn't know about,
11335 rather than warn and continue.
11336 - Make --version work
11337 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
11340 Changes in version 0.0.2pre23 - 2004-02-29
11342 - Print a statement when the first circ is finished, so the user
11343 knows it's working.
11344 - If a relay cell is unrecognized at the end of the circuit,
11345 send back a destroy. (So attacks to mutate cells are more
11347 - New config option 'excludenodes' to avoid certain nodes for circuits.
11348 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
11349 so you can collect coredumps there.
11351 - Fix a bug in tls flushing where sometimes data got wedged and
11352 didn't flush until more data got sent. Hopefully this bug was
11353 a big factor in the random delays we were seeing.
11354 - Make 'connected' cells include the resolved IP, so the client
11355 dns cache actually gets populated.
11356 - Disallow changing from ORPort=0 to ORPort>0 on hup.
11357 - When we time-out on a stream and detach from the circuit, send an
11358 end cell down it first.
11359 - Only warn about an unknown router (in exitnodes, entrynodes,
11360 excludenodes) after we've fetched a directory.
11363 Changes in version 0.0.2pre22 - 2004-02-26
11365 - Servers publish less revealing uname information in descriptors.
11366 - More memory tracking and assertions, to crash more usefully when
11368 - If the default torrc isn't there, just use some default defaults.
11369 Plus provide an internal dirservers file if they don't have one.
11370 - When the user tries to use Tor as an http proxy, give them an http
11371 501 failure explaining that we're a socks proxy.
11372 - Dump a new router.desc on hup, to help confused people who change
11373 their exit policies and then wonder why router.desc doesn't reflect
11375 - Clean up the generic tor.sh init script that we ship with.
11377 - If the exit stream is pending on the resolve, and a destroy arrives,
11378 then the stream wasn't getting removed from the pending list. I
11379 think this was the one causing recent server crashes.
11380 - Use a more robust poll on OSX 10.3, since their poll is flaky.
11381 - When it couldn't resolve any dirservers, it was useless from then on.
11382 Now it reloads the RouterFile (or default dirservers) if it has no
11384 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
11385 many users don't even *have* a /usr/local/sbin/.
11388 Changes in version 0.0.2pre21 - 2004-02-18
11390 - There's a ChangeLog file that actually reflects the changelog.
11391 - There's a 'torify' wrapper script, with an accompanying
11392 tor-tsocks.conf, that simplifies the process of using tsocks for
11393 tor. It even has a man page.
11394 - The tor binary gets installed to sbin rather than bin now.
11395 - Retry streams where the connected cell hasn't arrived in 15 seconds
11396 - Clean up exit policy handling -- get the default out of the torrc,
11397 so we can update it without forcing each server operator to fix
11399 - Allow imaps and pop3s in default exit policy
11401 - Prevent picking middleman nodes as the last node in the circuit
11404 Changes in version 0.0.2pre20 - 2004-01-30
11406 - We now have a deb package, and it's in debian unstable. Go to
11407 it, apt-getters. :)
11408 - I've split the TotalBandwidth option into BandwidthRate (how many
11409 bytes per second you want to allow, long-term) and
11410 BandwidthBurst (how many bytes you will allow at once before the cap
11411 kicks in). This better token bucket approach lets you, say, set
11412 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
11413 performance while not exceeding your monthly bandwidth quota.
11414 - Push out a tls record's worth of data once you've got it, rather
11415 than waiting until you've read everything waiting to be read. This
11416 may improve performance by pipelining better. We'll see.
11417 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
11418 from failed circuits (if they haven't been connected yet) and attach
11420 - Expire old streams that haven't managed to connect. Some day we'll
11421 have them reattach to new circuits instead.
11424 - Fix several memory leaks that were causing servers to become bloated
11426 - Fix a few very rare assert triggers. A few more remain.
11427 - Setuid to User _before_ complaining about running as root.
11430 Changes in version 0.0.2pre19 - 2004-01-07
11432 - Fix deadlock condition in dns farm. We were telling a child to die by
11433 closing the parent's file descriptor to him. But newer children were
11434 inheriting the open file descriptor from the parent, and since they
11435 weren't closing it, the socket never closed, so the child never read
11436 eof, so he never knew to exit. Similarly, dns workers were holding
11437 open other sockets, leading to all sorts of chaos.
11438 - New cleaner daemon() code for forking and backgrounding.
11439 - If you log to a file, it now prints an entry at the top of the
11440 logfile so you know it's working.
11441 - The onionskin challenge length was 30 bytes longer than necessary.
11442 - Started to patch up the spec so it's not quite so out of date.
11445 Changes in version 0.0.2pre18 - 2004-01-02
11447 - Fix endian issues with the 'integrity' field in the relay header.
11448 - Fix a potential bug where connections in state
11449 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
11452 Changes in version 0.0.2pre17 - 2003-12-30
11454 - Made --debuglogfile (or any second log file, actually) work.
11455 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
11456 adversary could force us into an infinite loop.
11459 - Each onionskin handshake now includes a hash of the computed key,
11460 to prove the server's identity and help perfect forward secrecy.
11461 - Changed cell size from 256 to 512 bytes (working toward compatibility
11463 - Changed cell length to 2 bytes, and moved it to the relay header.
11464 - Implemented end-to-end integrity checking for the payloads of
11466 - Separated streamid from 'recognized' (otherwise circuits will get
11467 messed up when we try to have streams exit from the middle). We
11468 use the integrity-checking to confirm that a cell is addressed to
11470 - Randomize the initial circid and streamid values, so an adversary who
11471 breaks into a node can't learn how many circuits or streams have
11475 Changes in version 0.0.2pre16 - 2003-12-14
11477 - Fixed a bug that made HUP trigger an assert
11478 - Fixed a bug where a circuit that immediately failed wasn't being
11479 counted as a failed circuit in counting retries.
11482 - Now we close the circuit when we get a truncated cell: otherwise we're
11483 open to an anonymity attack where a bad node in the path truncates
11484 the circuit and then we open streams at him.
11485 - Add port ranges to exit policies
11486 - Add a conservative default exit policy
11487 - Warn if you're running tor as root
11488 - on HUP, retry OR connections and close/rebind listeners
11489 - options.EntryNodes: try these nodes first when picking the first node
11490 - options.ExitNodes: if your best choices happen to include any of
11491 your preferred exit nodes, you choose among just those preferred
11493 - options.ExcludedNodes: nodes that are never picked in path building
11496 Changes in version 0.0.2pre15 - 2003-12-03
11497 o Robustness and bugfixes:
11498 - Sometimes clients would cache incorrect DNS resolves, which would
11499 really screw things up.
11500 - An OP that goes offline would slowly leak all its sockets and stop
11502 - A wide variety of bugfixes in exit node selection, exit policy
11503 handling, and processing pending streams when a new circuit is
11505 - Pick nodes for a path only from those the directory says are up
11506 - Choose randomly from all running dirservers, not always the first one
11507 - Increase allowed http header size for directory fetch.
11508 - Stop writing to stderr (if we're daemonized it will be closed).
11509 - Enable -g always, so cores will be more useful to me.
11510 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
11513 - Wrote a man page. It lists commonly used options.
11516 - Change default loglevel to warn.
11517 - Make PidFile default to null rather than littering in your CWD.
11518 - OnionRouter config option is now obsolete. Instead it just checks
11520 - Moved to a single unified torrc file for both clients and servers.
11523 Changes in version 0.0.2pre14 - 2003-11-29
11524 o Robustness and bugfixes:
11525 - Force the admin to make the DataDirectory himself
11526 - to get ownership/permissions right
11527 - so clients no longer make a DataDirectory and then never use it
11528 - fix bug where a client who was offline for 45 minutes would never
11529 pull down a directory again
11530 - fix (or at least hide really well) the dns assert bug that was
11531 causing server crashes
11532 - warnings and improved robustness wrt clockskew for certs
11533 - use the native daemon(3) to daemonize, when available
11534 - exit if bind() fails
11535 - exit if neither socksport nor orport is defined
11536 - include our own tor_timegm (Win32 doesn't have its own)
11537 - bugfix for win32 with lots of connections
11538 - fix minor bias in PRNG
11539 - make dirserver more robust to corrupt cached directory
11542 - Wrote the design document (woo)
11544 o Circuit building and exit policies:
11545 - Circuits no longer try to use nodes that the directory has told them
11547 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
11548 bitcounts (18.0.0.0/8).
11549 - Make AP connections standby for a circuit if no suitable circuit
11550 exists, rather than failing
11551 - Circuits choose exit node based on addr/port, exit policies, and
11552 which AP connections are standing by
11553 - Bump min pathlen from 2 to 3
11554 - Relay end cells have a payload to describe why the stream ended.
11555 - If the stream failed because of exit policy, try again with a new
11557 - Clients have a dns cache to remember resolved addresses.
11558 - Notice more quickly when we have no working circuits
11561 - APPort is now called SocksPort
11562 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
11564 - RecommendedVersions is now a config variable rather than
11565 hardcoded (for dirservers)
11566 - Reloads config on HUP
11567 - Usage info on -h or --help
11568 - If you set User and Group config vars, it'll setu/gid to them.
11570 Changes in version 0.0.2pre13 - 2003-10-19
11571 o General stability:
11572 - SSL_write no longer fails when it returns WANTWRITE and the number
11573 of bytes in the buf has changed by the next SSL_write call.
11574 - Fix segfault fetching directory when network is down
11575 - Fix a variety of minor memory leaks
11576 - Dirservers reload the fingerprints file on HUP, so I don't have
11577 to take down the network when I approve a new router
11578 - Default server config file has explicit Address line to specify fqdn
11581 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
11582 - Make listener connections not ever alloc bufs
11584 o Autoconf improvements:
11585 - don't clobber an external CFLAGS in ./configure
11586 - Make install now works
11587 - create var/lib/tor on make install
11588 - autocreate a tor.sh initscript to help distribs
11589 - autocreate the torrc and sample-server-torrc with correct paths
11591 o Log files and Daemonizing now work:
11592 - If --DebugLogFile is specified, log to it at -l debug
11593 - If --LogFile is specified, use it instead of commandline
11594 - If --RunAsDaemon is set, tor forks and backgrounds on startup