1 Changes in version 0.2.6.4-?? - 2015-0?-??
5 Changes in version 0.2.6.3-alpha - 2015-02-19
6 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
7 the 0.2.6.x series. It introduces support for more kinds of sockets,
8 makes it harder to accidentally run an exit, improves our
9 multithreading backend, incorporates several fixes for the
10 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
12 If no major regressions or security holes are found in this version,
13 the next version will be a release candidate.
15 o Deprecated versions:
16 - Tor relays older than 0.2.4.18-rc are no longer allowed to
17 advertise themselves on the network. Closes ticket 13555.
19 o Major features (security, unix domain sockets):
20 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
21 applications can reach Tor without having to create AF_INET or
22 AF_INET6 sockets, meaning they can completely disable their
23 ability to make non-Tor network connections. To create a socket of
24 this type, use "SocksPort unix:/path/to/socket". Implements
26 - Support mapping hidden service virtual ports to AF_UNIX sockets.
27 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
28 Implements ticket 11485.
30 o Major features (changed defaults):
31 - Prevent relay operators from unintentionally running exits: When a
32 relay is configured as an exit node, we now warn the user unless
33 the "ExitRelay" option is set to 1. We warn even more loudly if
34 the relay is configured with the default exit policy, since this
35 can indicate accidental misconfiguration. Setting "ExitRelay 0"
36 stops Tor from running as an exit relay. Closes ticket 10067.
38 o Major features (directory system):
39 - When downloading server- or microdescriptors from a directory
40 server, we no longer launch multiple simultaneous requests to the
41 same server. This reduces load on the directory servers,
42 especially when directory guards are in use. Closes ticket 9969.
43 - When downloading server- or microdescriptors over a tunneled
44 connection, do not limit the length of our requests to what the
45 Squid proxy is willing to handle. Part of ticket 9969.
46 - Authorities can now vote on the correct digests and latest
47 versions for different software packages. This allows packages
48 that include Tor to use the Tor authority system as a way to get
49 notified of updates and their correct digests. Implements proposal
50 227. Closes ticket 10395.
52 o Major features (guards):
53 - Introduce the Guardfraction feature to improves load balancing on
54 guard nodes. Specifically, it aims to reduce the traffic gap that
55 guard nodes experience when they first get the Guard flag. This is
56 a required step if we want to increase the guard lifetime to 9
57 months or greater. Closes ticket 9321.
59 o Major features (performance):
60 - Make the CPU worker implementation more efficient by avoiding the
61 kernel and lengthening pipelines. The original implementation used
62 sockets to transfer data from the main thread to the workers, and
63 didn't allow any thread to be assigned more than a single piece of
64 work at once. The new implementation avoids communications
65 overhead by making requests in shared memory, avoiding kernel IO
66 where possible, and keeping more requests in flight at once.
67 Implements ticket 9682.
69 o Major features (relay):
70 - Raise the minimum acceptable configured bandwidth rate for bridges
71 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
72 20 KiB/sec.) Closes ticket 13822.
74 o Major bugfixes (exit node stability):
75 - Fix an assertion failure that could occur under high DNS load.
76 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
77 diagnosed and fixed by "cypherpunks".
79 o Major bugfixes (mixed relay-client operation):
80 - When running as a relay and client at the same time (not
81 recommended), if we decide not to use a new guard because we want
82 to retry older guards, only close the locally-originating circuits
83 passing through that guard. Previously we would close all the
84 circuits through that guard. Fixes bug 9819; bugfix on
85 0.2.1.1-alpha. Reported by "skruffy".
87 o Minor features (build):
88 - New --disable-system-torrc compile-time option to prevent Tor from
89 looking for the system-wide torrc or torrc-defaults files.
90 Resolves ticket 13037.
92 o Minor features (controller):
93 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
94 events so controllers can observe circuit isolation inputs. Closes
96 - ControlPort now supports the unix:/path/to/socket syntax as an
97 alternative to the ControlSocket option, for consistency with
98 SocksPort and HiddenServicePort. Closes ticket 14451.
99 - New "GETINFO bw-event-cache" to get information about recent
100 bandwidth events. Closes ticket 14128. Useful for controllers to
101 get recent bandwidth history after the fix for ticket 13988.
103 o Minor features (Denial of service resistance):
104 - Count the total number of bytes used storing hidden service
105 descriptors against the value of MaxMemInQueues. If we're low on
106 memory, and more than 20% of our memory is used holding hidden
107 service descriptors, free them until no more than 10% of our
108 memory holds hidden service descriptors. Free the least recently
109 fetched descriptors first. Resolves ticket 13806.
110 - When we have recently been under memory pressure (over 3/4 of
111 MaxMemInQueues is allocated), then allocate smaller zlib objects
112 for small requests. Closes ticket 11791.
114 o Minor features (geoip):
115 - Update geoip and geoip6 files to the January 7 2015 Maxmind
116 GeoLite2 Country database.
118 o Minor features (guard nodes):
119 - Reduce the time delay before saving guard status to disk from 10
120 minutes to 30 seconds (or from one hour to 10 minutes if
121 AvoidDiskWrites is set). Closes ticket 12485.
123 o Minor features (hidden service):
124 - Make Sybil attacks against hidden services harder by changing the
125 minimum time required to get the HSDir flag from 25 hours up to 96
126 hours. Addresses ticket 14149.
127 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
128 services to disable the anti-scanning feature introduced in
129 0.2.6.2-alpha. With this option not set, a connection to an
130 unlisted port closes the circuit. With this option set, only a
131 RELAY_DONE cell is sent. Closes ticket 14084.
133 o Minor features (interface):
134 - Implement "-f -" command-line option to read torrc configuration
135 from standard input, if you don't want to store the torrc file in
136 the file system. Implements feature 13865.
138 o Minor features (logging):
139 - Add a count of unique clients to the bridge heartbeat message.
140 Resolves ticket 6852.
141 - Suppress "router info incompatible with extra info" message when
142 reading extrainfo documents from cache. (This message got loud
143 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
145 - Elevate hidden service authorized-client message from DEBUG to
146 INFO. Closes ticket 14015.
148 o Minor features (stability):
149 - Add assertions in our hash-table iteration code to check for
150 corrupted values that could cause infinite loops. Closes
153 o Minor features (systemd):
154 - Various improvements and modernizations in systemd hardening
155 support. Closes ticket 13805. Patch from Craig Andrews.
157 o Minor features (testing networks):
158 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
159 and the default on a testing network to 2 minutes. Drop the
160 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
161 keep the default on a testing network at 30 seconds. This reduces
162 HS bootstrap time to around 25 seconds. Also, change the default
163 time in test-network.sh to match. Closes ticket 13401. Patch
165 - Create TestingDirAuthVoteHSDir to correspond to
166 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
167 HSDir flag for the listed relays regardless of uptime or ORPort
168 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
169 Partial implementation for ticket 14067. Patch by "teor".
171 o Minor features (tor2web mode):
172 - Introduce the config option Tor2webRendezvousPoints, which allows
173 clients in Tor2webMode to select a specific Rendezvous Point to be
174 used in HS circuits. This might allow better performance for
175 Tor2Web nodes. Implements ticket 12844.
177 o Minor bugfixes (client DNS):
178 - Report the correct cached DNS expiration times on SOCKS port or in
179 DNS replies. Previously, we would report everything as "never
180 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
181 - Avoid a small memory leak when we find a cached answer for a
182 reverse DNS lookup in a client-side DNS cache. (Remember, client-
183 side DNS caching is off by default, and is not recommended.) Fixes
184 bug 14259; bugfix on 0.2.0.1-alpha.
186 o Minor bugfixes (client, automapping):
187 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
188 no value follows the option. Fixes bug 14142; bugfix on
189 0.2.4.7-alpha. Patch by "teor".
190 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
191 14195; bugfix on 0.1.0.1-rc.
192 - Prevent changes to other options from removing the wildcard value
193 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
195 - Allow MapAddress and AutomapHostsOnResolve to work together when
196 an address is mapped into another address type (like .onion) that
197 must be automapped at resolve time. Fixes bug 7555; bugfix
200 o Minor bugfixes (client, bridges):
201 - When we are using bridges and we had a network connectivity
202 problem, only retry connecting to our currently configured
203 bridges, not all bridges we know about and remember using. Fixes
204 bug 14216; bugfix on 0.2.2.17-alpha.
206 o Minor bugfixes (client, IPv6):
207 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
208 flag is not set; and not because the NoIPv4Traffic flag was set.
209 Previously we'd looked at the NoIPv4Traffic flag for both types of
210 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
212 o Minor bugfixes (compilation):
213 - The address of an array in the middle of a structure will always
214 be non-NULL. clang recognises this and complains. Disable the
215 tautologous and redundant check to silence this warning. Fixes bug
216 14001; bugfix on 0.2.1.2-alpha.
217 - Avoid warnings when building with systemd 209 or later. Fixes bug
218 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
219 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
220 Addresses ticket 14188.
221 - Build without warnings with the stock OpenSSL srtp.h header, which
222 has a duplicate declaration of SSL_get_selected_srtp_profile().
223 Fixes bug 14220; this is OpenSSL's bug, not ours.
224 - Do not compile any code related to Tor2Web mode when Tor2Web mode
225 is not enabled at compile time. Previously, this code was included
226 in a disabled state. See discussion on ticket 12844.
227 - Remove the --disable-threads configure option again. It was
228 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
229 14819; bugfix on 0.2.6.2-alpha.
231 o Minor bugfixes (controller):
232 - Report "down" in response to the "GETINFO entry-guards" command
233 when relays are down with an unreachable_since value. Previously,
234 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
235 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
236 14116; bugfix on 0.2.2.9-alpha.
237 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
238 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
240 o Minor bugfixes (directory authority):
241 - Allow directory authorities to fetch more data from one another if
242 they find themselves missing lots of votes. Previously, they had
243 been bumping against the 10 MB queued data limit. Fixes bug 14261;
244 bugfix on 0.1.2.5-alpha.
245 - Do not attempt to download extrainfo documents which we will be
246 unable to validate with a matching server descriptor. Fixes bug
247 13762; bugfix on 0.2.0.1-alpha.
248 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
249 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
250 - Enlarge the buffer to read bwauth generated files to avoid an
251 issue when parsing the file in dirserv_read_measured_bandwidths().
252 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
254 o Minor bugfixes (file handling):
255 - Stop failing when key files are zero-length. Instead, generate new
256 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
257 on all versions of Tor. Patch by "teor".
258 - Stop generating a fresh .old RSA onion key file when the .old file
259 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
260 - Avoid overwriting .old key files with empty key files.
261 - Skip loading zero-length extrainfo store, router store, stats,
262 state, and key files.
263 - Avoid crashing when trying to reload a torrc specified as a
264 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
267 o Minor bugfixes (hidden services):
268 - Close the introduction circuit when we have no more usable intro
269 points, instead of waiting for it to time out. This also ensures
270 that no follow-up HS descriptor fetch is triggered when the
271 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
272 - When fetching a hidden service descriptor for a down service that
273 was recently up, do not keep refetching until we try the same
274 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
275 - Successfully launch Tor with a nonexistent hidden service
276 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
277 14106; bugfix on 0.2.6.2-alpha.
279 o Minor bugfixes (logging):
280 - Avoid crashing when there are more log domains than entries in
281 domain_list. Bugfix on 0.2.3.1-alpha.
282 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
284 - Don't log messages to stdout twice when starting up. Fixes bug
285 13993; bugfix on 0.2.6.1-alpha.
287 o Minor bugfixes (parsing):
288 - Stop accepting milliseconds (or other junk) at the end of
289 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
290 - Support two-number and three-number version numbers correctly, in
291 case we change the Tor versioning system in the future. Fixes bug
292 13661; bugfix on 0.0.8pre1.
294 o Minor bugfixes (path counting):
295 - When deciding whether the consensus lists any exit nodes, count
296 the number listed in the consensus, not the number we have
297 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
298 - When deciding whether we have any exit nodes, only examine
299 ExitNodes when the ExitNodes option is actually set. Fixes part of
300 bug 14918; bugfix on 0.2.6.2-alpha.
301 - Get rid of redundant and possibly scary warnings that we are
302 missing directory information while we bootstrap. Fixes part of
303 bug 14918; bugfix on 0.2.6.2-alpha.
305 o Minor bugfixes (portability):
306 - Fix the ioctl()-based network interface lookup code so that it
307 will work on systems that have variable-length struct ifreq, for
309 - Fix scheduler compilation on targets where char is unsigned. Fixes
310 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
312 o Minor bugfixes (sandbox):
313 - Allow glibc fatal errors to be sent to stderr before Tor exits.
314 Previously, glibc would try to write them to /dev/tty, and the
315 sandbox would trap the call and make Tor exit prematurely. Fixes
316 bug 14759; bugfix on 0.2.5.1-alpha.
318 o Minor bugfixes (shutdown):
319 - When shutting down, always call event_del() on lingering read or
320 write events before freeing them. Otherwise, we risk double-frees
321 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
324 o Minor bugfixes (small memory leaks):
325 - Avoid leaking memory when using IPv6 virtual address mappings.
326 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
329 o Minor bugfixes (statistics):
330 - Increase period over which bandwidth observations are aggregated
331 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
333 o Minor bugfixes (systemd support):
334 - Fix detection and operation of systemd watchdog. Fixes part of bug
335 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
336 - Run correctly under systemd with the RunAsDaemon option set. Fixes
337 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
338 - Inform the systemd supervisor about more changes in the Tor
339 process status. Implements part of ticket 14141. Patch from
341 - Cause the "--disable-systemd" option to actually disable systemd
342 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
345 o Minor bugfixes (TLS):
346 - Check more thoroughly throughout the TLS code for possible
347 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
349 o Minor bugfixes (transparent proxy):
350 - Use getsockname, not getsockopt, to retrieve the address for a
351 TPROXY-redirected connection. Fixes bug 13796; bugfix
354 o Code simplification and refactoring:
355 - Move fields related to isolating and configuring client ports into
356 a shared structure. Previously, they were duplicated across
357 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
358 to copy them correctly had been the cause of at least one bug in
359 the past. Closes ticket 8546.
360 - Refactor the get_interface_addresses_raw() doom-function into
361 multiple smaller and simpler subfunctions. Cover the resulting
362 subfunctions with unit-tests. Fixes a significant portion of
364 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
365 only for version <= 0.2.2.24 which is now deprecated. Closes
367 - Remove a test for a long-defunct broken version-one
371 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
372 for writing the OpenBSD-specific tips. Resolves ticket 13702.
373 - Make the tor-resolve documentation match its help string and its
374 options. Resolves part of ticket 14325.
375 - Log a more useful error message from tor-resolve when failing to
376 look up a hidden service address. Resolves part of ticket 14325.
378 o Downgraded warnings:
379 - Don't warn when we've attempted to contact a relay using the wrong
380 ntor onion key. Closes ticket 9635.
383 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
384 longer silently accepted as an alias for "ExitNodes".
385 - The --enable-mempool and --enable-buf-freelists options, which
386 were originally created to work around bad malloc implementations,
387 no longer exist. They were off-by-default in 0.2.5. Closes
391 - Make the checkdir/perms test complete successfully even if the
392 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
393 - Test that tor does not fail when key files are zero-length. Check
394 that tor generates new keys, and overwrites the empty key files.
395 - Test that tor generates new keys when keys are missing
397 - Test that tor does not overwrite key files that already contain
398 data (existing behavior). Tests bug 13111. Patch by "teor".
399 - New "make test-stem" target to run stem integration tests.
400 Requires that the "STEM_SOURCE_DIR" environment variable be set.
402 - Make the test_cmdline_args.py script work correctly on Windows.
403 Patch from Gisle Vanem.
404 - Move the slower unit tests into a new "./src/test/test-slow"
405 binary that can be run independently of the other tests. Closes
407 - Avoid undefined behavior when sampling huge values from the
408 Laplace distribution. This made unittests fail on Raspberry Pi.
409 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
412 Changes in version 0.2.6.2-alpha - 2014-12-31
413 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
414 It introduces a major new backend for deciding when to send cells on
415 channels, which should lead down the road to big performance
416 increases. It contains security and statistics features for better
417 work on hidden services, and numerous bugfixes.
419 This release contains many new unit tests, along with major
420 performance improvements for running testing networks using Chutney.
421 Thanks to a series of patches contributed by "teor", testing networks
422 should now bootstrap in seconds, rather than minutes.
424 o Major features (relay, infrastructure):
425 - Complete revision of the code that relays use to decide which cell
426 to send next. Formerly, we selected the best circuit to write on
427 each channel, but we didn't select among channels in any
428 sophisticated way. Now, we choose the best circuits globally from
429 among those whose channels are ready to deliver traffic.
431 This patch implements a new inter-cmux comparison API, a global
432 high/low watermark mechanism and a global scheduler loop for
433 transmission prioritization across all channels as well as among
434 circuits on one channel. This schedule is currently tuned to
435 (tolerantly) avoid making changes in network performance, but it
436 should form the basis for major circuit performance increases in
437 the future. Code by Andrea; tuning by Rob Jansen; implements
440 o Major features (hidden services):
441 - Make HS port scanning more difficult by immediately closing the
442 circuit when a user attempts to connect to a nonexistent port.
444 - Add a HiddenServiceStatistics option that allows Tor relays to
445 gather and publish statistics about the overall size and volume of
446 hidden service usage. Specifically, when this option is turned on,
447 an HSDir will publish an approximate number of hidden services
448 that have published descriptors to it the past 24 hours. Also, if
449 a relay has acted as a hidden service rendezvous point, it will
450 publish the approximate amount of rendezvous cells it has relayed
451 the past 24 hours. The statistics themselves are obfuscated so
452 that the exact values cannot be derived. For more details see
453 proposal 238, "Better hidden service stats from Tor relays". This
454 feature is currently disabled by default. Implements feature 13192.
456 o Major bugfixes (client, automap):
457 - Repair automapping with IPv6 addresses. This automapping should
458 have worked previously, but one piece of debugging code that we
459 inserted to detect a regression actually caused the regression to
460 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
461 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
464 o Major bugfixes (hidden services):
465 - When closing an introduction circuit that was opened in parallel
466 with others, don't mark the introduction point as unreachable.
467 Previously, the first successful connection to an introduction
468 point would make the other introduction points get marked as
469 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
471 o Directory authority changes:
472 - Remove turtles as a directory authority.
473 - Add longclaw as a new (v3) directory authority. This implements
474 ticket 13296. This keeps the directory authority count at 9.
476 o Major removed features:
477 - Tor clients no longer support connecting to hidden services
478 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
479 option has been removed. (There shouldn't be any hidden services
480 running these versions on the network.) Closes ticket 7803.
482 o Minor features (client):
483 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
484 is enabled, reject requests with IP addresses as hostnames.
485 Resolves ticket 13315.
487 o Minor features (controller):
488 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
489 write an unscheduled heartbeat message to the log. Implements
492 o Minor features (geoip):
493 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
496 o Minor features (hidden services):
497 - When re-enabling the network, don't try to build introduction
498 circuits until we have successfully built a circuit. This makes
499 hidden services come up faster when the network is re-enabled.
500 Patch from "akwizgran". Closes ticket 13447.
501 - When we fail to retrieve a hidden service descriptor, send the
502 controller an "HS_DESC FAILED" controller event. Implements
504 - New HiddenServiceDirGroupReadable option to cause hidden service
505 directories and hostname files to be created group-readable. Patch
506 from "anon", David Stainton, and "meejah". Closes ticket 11291.
508 o Minor features (systemd):
509 - Where supported, when running with systemd, report successful
510 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
511 - When running with systemd, support systemd watchdog messages. Part
512 of ticket 11016. Patch by Michael Scherer.
514 o Minor features (transparent proxy):
515 - Update the transparent proxy option checks to allow for both ipfw
516 and pf on OS X. Closes ticket 14002.
517 - Use the correct option when using IPv6 with transparent proxy
518 support on Linux. Resolves 13808. Patch by Francisco Blas
521 o Minor bugfixes (preventative security, C safety):
522 - When reading a hexadecimal, base-32, or base-64 encoded value from
523 a string, always overwrite the whole output buffer. This prevents
524 some bugs where we would look at (but fortunately, not reveal)
525 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
527 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
528 just the part that's used. This makes it harder for data leak bugs
529 to occur in the event of other programming failures. Resolves
532 o Minor bugfixes (client, microdescriptors):
533 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
534 computing which microdescriptors to download. This keeps us from
535 erroneous download behavior if two microdescriptor digests ever
536 have the same first 160 bits. Fixes part of bug 13399; bugfix
538 - Reset a router's status if its microdescriptor digest changes,
539 even if the first 160 bits remain the same. Fixes part of bug
540 13399; bugfix on 0.2.3.1-alpha.
542 o Minor bugfixes (compilation):
543 - Silence clang warnings under --enable-expensive-hardening,
544 including implicit truncation of 64 bit values to 32 bit, const
545 char assignment to self, tautological compare, and additional
546 parentheses around equality tests. Fixes bug 13577; bugfix
548 - Fix a clang warning about checking whether an address in the
549 middle of a structure is NULL. Fixes bug 14001; bugfix
552 o Minor bugfixes (hidden services):
553 - Correctly send a controller event when we find that a rendezvous
554 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
555 - Pre-check directory permissions for new hidden-services to avoid
556 at least one case of "Bug: Acting on config options left us in a
557 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
558 - When adding a new hidden service (for example, via SETCONF), Tor
559 no longer congratulates the user for running a relay. Fixes bug
560 13941; bugfix on 0.2.6.1-alpha.
561 - When fetching hidden service descriptors, we now check not only
562 for whether we got the hidden service we had in mind, but also
563 whether we got the particular descriptors we wanted. This prevents
564 a class of inefficient but annoying DoS attacks by hidden service
565 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
568 o Minor bugfixes (Linux seccomp2 sandbox):
569 - Make transparent proxy support work along with the seccomp2
570 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
571 by Francisco Blas Izquierdo Riera.
572 - Fix a memory leak in tor-resolve when running with the sandbox
573 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
575 o Minor bugfixes (logging):
576 - Downgrade warnings about RSA signature failures to info log level.
577 Emit a warning when an extra info document is found incompatible
578 with a corresponding router descriptor. Fixes bug 9812; bugfix
580 - Make connection_ap_handshake_attach_circuit() log the circuit ID
581 correctly. Fixes bug 13701; bugfix on 0.0.6.
583 o Minor bugfixes (misc):
584 - Stop allowing invalid address patterns like "*/24" that contain
585 both a wildcard address and a bit prefix length. This affects all
586 our address-range parsing code. Fixes bug 7484; bugfix
589 o Minor bugfixes (testing networks, fast startup):
590 - Allow Tor to build circuits using a consensus with no exits. If
591 the consensus has no exits (typical of a bootstrapping test
592 network), allow Tor to build circuits once enough descriptors have
593 been downloaded. This assists in bootstrapping a testing Tor
594 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
596 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
597 header to directory servers. This allows us to obtain consensuses
598 promptly when the consensus interval is very short. This assists
599 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
600 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
601 - Stop assuming that private addresses are local when checking
602 reachability in a TestingTorNetwork. Instead, when testing, assume
603 all OR connections are remote. (This is necessary due to many test
604 scenarios running all relays on localhost.) This assists in
605 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
606 0.1.0.1-rc. Patch by "teor".
607 - Avoid building exit circuits from a consensus with no exits. Now
608 thanks to our fix for 13718, we accept a no-exit network as not
609 wholly lost, but we need to remember not to try to build exit
610 circuits on it. Closes ticket 13814; patch by "teor".
611 - Stop requiring exits to have non-zero bandwithcapacity in a
612 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
613 ignore exit bandwidthcapacity. This assists in bootstrapping a
614 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
615 on 0.2.0.3-alpha. Patch by "teor".
616 - Add "internal" to some bootstrap statuses when no exits are
617 available. If the consensus does not contain Exits, Tor will only
618 build internal circuits. In this case, relevant statuses will
619 contain the word "internal" as indicated in the Tor control-
620 spec.txt. When bootstrap completes, Tor will be ready to build
621 internal circuits. If a future consensus contains Exits, exit
622 circuits may become available. Fixes part of bug 13718; bugfix on
623 0.2.4.10-alpha. Patch by "teor".
624 - Decrease minimum consensus interval to 10 seconds when
625 TestingTorNetwork is set, or 5 seconds for the first consensus.
626 Fix assumptions throughout the code that assume larger intervals.
627 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
629 - Avoid excluding guards from path building in minimal test
630 networks, when we're in a test network and excluding guards would
631 exclude all relays. This typically occurs in incredibly small tor
632 networks, and those using "TestingAuthVoteGuard *". Fixes part of
633 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
635 o Code simplification and refactoring:
636 - Stop using can_complete_circuits as a global variable; access it
637 with a function instead.
638 - Avoid using operators directly as macro arguments: this lets us
639 apply coccinelle transformations to our codebase more directly.
641 - Combine the functions used to parse ClientTransportPlugin and
642 ServerTransportPlugin into a single function. Closes ticket 6456.
643 - Add inline functions and convenience macros for inspecting channel
644 state. Refactor the code to use convenience macros instead of
645 checking channel state directly. Fixes issue 7356.
646 - Document all members of was_router_added_t and rename
647 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
648 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
649 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
650 constant instead of hardcoded value. Fixes issue 13840.
651 - Refactor our generic strmap and digestmap types into a single
652 implementation, so that we can add a new digest256map
656 - Document the bridge-authority-only 'networkstatus-bridges' file.
657 Closes ticket 13713; patch from "tom".
658 - Fix typo in PredictedPortsRelevanceTime option description in
659 manpage. Resolves issue 13707.
660 - Stop suggesting that users specify relays by nickname: it isn't a
661 good idea. Also, properly cross-reference how to specify relays in
662 all parts of manual documenting options that take a list of
663 relays. Closes ticket 13381.
664 - Clarify the HiddenServiceDir option description in manpage to make
665 it clear that relative paths are taken with respect to the current
666 working directory. Also clarify that this behavior is not
667 guaranteed to remain indefinitely. Fixes issue 13913.
670 - New tests for many parts of channel, relay, and circuitmux
671 functionality. Code by Andrea; part of 9262.
672 - New tests for parse_transport_line(). Part of ticket 6456.
673 - In the unit tests, use chgrp() to change the group of the unit
674 test temporary directory to the current user, so that the sticky
675 bit doesn't interfere with tests that check directory groups.
677 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
681 Changes in version 0.2.6.1-alpha - 2014-10-30
682 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
683 includes numerous code cleanups and new tests, and fixes a large
684 number of annoying bugs. Out-of-memory conditions are handled better
685 than in 0.2.5, pluggable transports have improved proxy support, and
686 clients now use optimistic data for contacting hidden services. Also,
687 we are now more robust to changes in what we consider a parseable
688 directory object, so that tightening restrictions does not have a risk
689 of introducing infinite download loops.
691 This is the first alpha release in a new series, so expect there to be
692 bugs. Users who would rather test out a more stable branch should stay
693 with 0.2.5.x for now.
695 o New compiler and system requirements:
696 - Tor 0.2.6.x requires that your compiler support more of the C99
697 language standard than before. The 'configure' script now detects
698 whether your compiler supports C99 mid-block declarations and
699 designated initializers. If it does not, Tor will not compile.
701 We may revisit this requirement if it turns out that a significant
702 number of people need to build Tor with compilers that don't
703 bother implementing a 15-year-old standard. Closes ticket 13233.
704 - Tor no longer supports systems without threading support. When we
705 began working on Tor, there were several systems that didn't have
706 threads, or where the thread support wasn't able to run the
707 threads of a single process on multiple CPUs. That no longer
708 holds: every system where Tor needs to run well now has threading
709 support. Resolves ticket 12439.
711 o Removed platform support:
712 - We no longer include special code to build on Windows CE; as far
713 as we know, nobody has used Tor on Windows CE in a very long time.
716 o Major features (bridges):
717 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
718 transports if they are configured via the "TOR_PT_PROXY"
719 environment variable. Implements proposal 232. Resolves
722 o Major features (client performance, hidden services):
723 - Allow clients to use optimistic data when connecting to a hidden
724 service, which should remove a round-trip from hidden service
725 initialization. See proposal 181 for details. Implements
728 o Major features (directory system):
729 - Upon receiving an unparseable directory object, if its digest
730 matches what we expected, then don't try to download it again.
731 Previously, when we got a descriptor we didn't like, we would keep
732 trying to download it over and over. Closes ticket 11243.
734 o Major features (sample torrc):
735 - Add a new, infrequently-changed "torrc.minimal". This file is
736 similar to torrc.sample, but it will change as infrequently as
737 possible, for the benefit of users whose systems prompt them for
738 intervention whenever a default configuration file is changed.
739 Making this change allows us to update torrc.sample to be a more
740 generally useful "sample torrc".
742 o Major bugfixes (directory authorities):
743 - Do not assign the HSDir flag to relays if they are not Valid, or
744 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
746 o Major bugfixes (directory bandwidth performance):
747 - Don't flush the zlib buffer aggressively when compressing
748 directory information for clients. This should save about 7% of
749 the bandwidth currently used for compressed descriptors and
750 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
752 o Minor features (security, memory wiping):
753 - Ensure we securely wipe keys from memory after
754 crypto_digest_get_digest and init_curve25519_keypair_from_file
755 have finished using them. Resolves ticket 13477.
757 o Minor features (security, out-of-memory handling):
758 - When handling an out-of-memory condition, allocate less memory for
759 temporary data structures. Fixes issue 10115.
760 - When handling an out-of-memory condition, consider more types of
761 buffers, including those on directory connections, and zlib
762 buffers. Resolves ticket 11792.
765 - When identity keypair is generated for first time, log a
766 congratulatory message that links to the new relay lifecycle
767 document. Implements feature 10427.
769 o Minor features (client):
770 - Clients are now willing to send optimistic data (before they
771 receive a 'connected' cell) to relays of any version. (Relays
772 without support for optimistic data are no longer supported on the
773 Tor network.) Resolves ticket 13153.
775 o Minor features (directory authorities):
776 - Don't list relays with a bandwidth estimate of 0 in the consensus.
777 Implements a feature proposed during discussion of bug 13000.
778 - In tor-gencert, report an error if the user provides the same
779 argument more than once.
780 - If a directory authority can't find a best consensus method in the
781 votes that it holds, it now falls back to its favorite consensus
782 method. Previously, it fell back to method 1. Neither of these is
783 likely to get enough signatures, but "fall back to favorite"
784 doesn't require us to maintain support an obsolete consensus
785 method. Implements part of proposal 215.
787 o Minor features (logging):
788 - On Unix-like systems, you can now use named pipes as the target of
789 the Log option, and other options that try to append to files.
790 Closes ticket 12061. Patch from "carlo von lynX".
791 - When opening a log file at startup, send it every log message that
792 we generated between startup and opening it. Previously, log
793 messages that were generated before opening the log file were only
794 logged to stdout. Closes ticket 6938.
795 - Add a TruncateLogFile option to overwrite logs instead of
796 appending to them. Closes ticket 5583.
798 o Minor features (portability, Solaris):
799 - Threads are no longer disabled by default on Solaris; we believe
800 that the versions of Solaris with broken threading support are all
801 obsolete by now. Resolves ticket 9495.
803 o Minor features (relay):
804 - Re-check our address after we detect a changed IP address from
805 getsockname(). This ensures that the controller command "GETINFO
806 address" will report the correct value. Resolves ticket 11582.
808 - A new AccountingRule option lets Relays set whether they'd like
809 AccountingMax to be applied separately to inbound and outbound
810 traffic, or applied to the sum of inbound and outbound traffic.
811 Resolves ticket 961. Patch by "chobe".
813 o Minor features (testing networks):
814 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
815 the "Exit" flag regardless of their uptime, bandwidth, or exit
816 policy. TestingTorNetwork must be set for this option to have any
817 effect. Previously, authorities would take up to 35 minutes to
818 give nodes the Exit flag in a test network. Partially implements
821 o Minor features (validation):
822 - Check all date/time values passed to tor_timegm and
823 parse_rfc1123_time for validity, taking leap years into account.
824 Improves HTTP header validation. Implemented with bug 13476.
825 - In correct_tm(), limit the range of values returned by system
826 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
827 This means we don't have to deal with negative or too large dates,
828 even if a clock is wrong. Otherwise we might fail to read a file
829 written by us which includes such a date. Fixes bug 13476.
831 o Minor bugfixes (bridge clients):
832 - When configured to use a bridge without an identity digest (not
833 recommended), avoid launching an extra channel to it when
834 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
836 o Minor bugfixes (bridges):
837 - When DisableNetwork is set, do not launch pluggable transport
838 plugins, and if any are running, terminate them. Fixes bug 13213;
839 bugfix on 0.2.3.6-alpha.
841 o Minor bugfixes (C correctness):
842 - Fix several instances of possible integer overflow/underflow/NaN.
843 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
845 - In circuit_build_times_calculate_timeout() in circuitstats.c,
846 avoid dividing by zero in the pareto calculations. This traps
847 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
849 - Fix an integer overflow in format_time_interval(). Fixes bug
850 13393; bugfix on 0.2.0.10-alpha.
851 - Set the correct day of year value when the system's localtime(_r)
852 or gmtime(_r) functions fail to set struct tm. Not externally
853 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
854 - Avoid unlikely signed integer overflow in tor_timegm on systems
855 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
857 o Minor bugfixes (client):
858 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
859 BadExit flag are not considered worthy candidates. Fixes bug
860 13066; bugfix on 0.1.2.3-alpha.
861 - Use the consensus schedule for downloading consensuses, and not
862 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
863 - Handle unsupported or malformed SOCKS5 requests properly by
864 responding with the appropriate error message before closing the
865 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
867 o Minor bugfixes (client, torrc):
868 - Stop modifying the value of our DirReqStatistics torrc option just
869 because we're not a bridge or relay. This bug was causing Tor
870 Browser users to write "DirReqStatistics 0" in their torrc files
871 as if they had chosen to change the config. Fixes bug 4244; bugfix
873 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
874 that our options have changed every time we SIGHUP. Fixes bug
875 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
877 o Minor bugfixes (controller):
878 - Return an error when the second or later arguments of the
879 "setevents" controller command are invalid events. Previously we
880 would return success while silently skipping invalid events. Fixes
881 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
883 o Minor bugfixes (directory system):
884 - Always believe that v3 directory authorities serve extra-info
885 documents, whether they advertise "caches-extra-info" or not.
886 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
887 - When running as a v3 directory authority, advertise that you serve
888 extra-info documents so that clients who want them can find them
889 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
890 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
891 Previously, directories offering BRIDGE_DIRINFO and some other
892 flag (i.e. microdescriptors or extrainfo) would be ignored when
893 looking for bridges. Partially fixes bug 13163; bugfix
896 o Minor bugfixes (networking):
897 - Check for orconns and use connection_or_close_for_error() rather
898 than connection_mark_for_close() directly in the getsockopt()
899 failure case of connection_handle_write_impl(). Fixes bug 11302;
900 bugfix on 0.2.4.4-alpha.
902 o Minor bugfixes (relay):
903 - When generating our family list, remove spaces from around the
904 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
905 - If our previous bandwidth estimate was 0 bytes, allow publishing a
906 new relay descriptor immediately. Fixes bug 13000; bugfix
909 o Minor bugfixes (testing networks):
910 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
911 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
912 - Stop using the default authorities in networks which provide both
913 AlternateDirAuthority and AlternateBridgeAuthority. Partially
914 fixes bug 13163; bugfix on 0.2.0.13-alpha.
916 o Minor bugfixes (testing):
917 - Stop spawn test failures due to a race condition between the
918 SIGCHLD handler updating the process status, and the test reading
919 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
921 o Minor bugfixes (testing, Windows):
922 - Avoid passing an extra backslash when creating a temporary
923 directory for running the unit tests on Windows. Fixes bug 12392;
924 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
926 o Minor bugfixes (windows):
927 - Remove code to special-case handling of NTE_BAD_KEYSET when
928 acquiring windows CryptoAPI context. This error can't actually
929 occur for the parameters we're providing. Fixes bug 10816; bugfix
932 o Minor bugfixes (zlib):
933 - Avoid truncating a zlib stream when trying to finalize it with an
934 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
937 - Allow our configure script to build correctly with autoconf 2.62
938 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
939 - Improve the error message from ./configure to make it clear that
940 when asciidoc has not been found, the user will have to either add
941 --disable-asciidoc argument or install asciidoc. Resolves
944 o Code simplification and refactoring:
945 - Change the entry_is_live() function to take named bitfield
946 elements instead of an unnamed list of booleans. Closes
948 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
949 Resolves ticket 12205.
950 - Use calloc and reallocarray functions instead of multiply-
951 then-malloc. This makes it less likely for us to fall victim to an
952 integer overflow attack when allocating. Resolves ticket 12855.
953 - Use the standard macro name SIZE_MAX, instead of our
955 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
956 functions which take them as arguments. Replace 0 with NO_DIRINFO
957 in a function call for clarity. Seeks to prevent future issues
959 - Avoid 4 null pointer errors under clang static analysis by using
960 tor_assert() to prove that the pointers aren't null. Fixes
962 - Rework the API of policies_parse_exit_policy() to use a bitmask to
963 represent parsing options, instead of a confusing mess of
964 booleans. Resolves ticket 8197.
965 - Introduce a helper function to parse ExitPolicy in
966 or_options_t structure.
969 - Add a doc/TUNING document with tips for handling large numbers of
970 TCP connections when running busy Tor relay. Update the warning
971 message to point to this file when running out of sockets
972 operating system is allowing to use simultaneously. Resolves
976 - We no longer remind the user about configuration options that have
977 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
978 - Remove our old, non-weighted bandwidth-based node selection code.
979 Previously, we used it as a fallback when we couldn't perform
980 weighted bandwidth-based node selection. But that would only
981 happen in the cases where we had no consensus, or when we had a
982 consensus generated by buggy or ancient directory authorities. In
983 either case, it's better to use the more modern, better maintained
984 algorithm, with reasonable defaults for the weights. Closes
986 - Remove the --disable-curve25519 configure option. Relays and
987 clients now are required to support curve25519 and the
989 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
990 used to be deprecated synonyms for "StrictNodes", are now marked
991 obsolete. Resolves ticket 12226.
992 - Clients don't understand the BadDirectory flag in the consensus
993 anymore, and ignore it.
996 - Refactor the function that chooses guard nodes so that it can more
997 easily be tested; write some tests for it.
998 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
999 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
1000 - Create unit tests for format_time_interval(). With bug 13393.
1001 - Add unit tests for tor_timegm signed overflow, tor_timegm and
1002 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
1003 tests (visible) fixes in bug 13476.
1004 - Add a "coverage-html" make target to generate HTML-visualized
1005 coverage results when building with --enable-coverage. (Requires
1006 lcov.) Patch from Kevin Murray.
1007 - Enable the backtrace handler (where supported) when running the
1009 - Revise all unit tests that used the legacy test_* macros to
1010 instead use the recommended tt_* macros. This patch was generated
1011 with coccinelle, to avoid manual errors. Closes ticket 13119.
1013 o Distribution (systemd):
1014 - systemd unit file: only allow tor to write to /var/lib/tor and
1015 /var/log/tor. The rest of the filesystem is accessible for reading
1016 only. Patch by intrigeri; resolves ticket 12751.
1017 - systemd unit file: ensure that the process and all its children
1018 can never gain new privileges. Patch by intrigeri; resolves
1020 - systemd unit file: set up /var/run/tor as writable for the Tor
1021 service. Patch by intrigeri; resolves ticket 13196.
1023 o Removed features (directory authorities):
1024 - Remove code that prevented authorities from listing Tor relays
1025 affected by CVE-2011-2769 as guards. These relays are already
1026 rejected altogether due to the minimum version requirement of
1027 0.2.3.16-alpha. Closes ticket 13152.
1028 - The "AuthDirRejectUnlisted" option no longer has any effect, as
1029 the fingerprints file (approved-routers) has been deprecated.
1030 - Directory authorities do not support being Naming dirauths anymore.
1031 The "NamingAuthoritativeDir" config option is now obsolete.
1032 - Directory authorities do not support giving out the BadDirectory
1034 - Directory authorities no longer advertise or support consensus
1035 methods 1 through 12 inclusive. These consensus methods were
1036 obsolete and/or insecure: maintaining the ability to support them
1037 served no good purpose. Implements part of proposal 215; closes
1040 o Testing (test-network.sh):
1041 - Stop using "echo -n", as some shells' built-in echo doesn't
1042 support "-n". Instead, use "/bin/echo -n". Partially fixes
1044 - Stop an apparent test-network hang when used with make -j2. Fixes
1046 - Add a --delay option to test-network.sh, which configures the
1047 delay before the chutney network tests for data transmission.
1048 Partially implements ticket 13161.
1051 Changes in version 0.2.5.10 - 2014-10-24
1052 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
1054 It adds several new security features, including improved
1055 denial-of-service resistance for relays, new compiler hardening
1056 options, and a system-call sandbox for hardened installations on Linux
1057 (requires seccomp2). The controller protocol has several new features,
1058 resolving IPv6 addresses should work better than before, and relays
1059 should be a little more CPU-efficient. We've added support for more
1060 OpenBSD and FreeBSD transparent proxy types. We've improved the build
1061 system and testing infrastructure to allow unit testing of more parts
1062 of the Tor codebase. Finally, we've addressed several nagging pluggable
1063 transport usability issues, and included numerous other small bugfixes
1064 and features mentioned below.
1066 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
1067 have accumulated many known flaws; everyone should upgrade.
1069 o Deprecated versions:
1070 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
1071 attention for some while.
1074 Changes in version 0.2.5.9-rc - 2014-10-20
1075 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
1076 series. It disables SSL3 in response to the recent "POODLE" attack
1077 (even though POODLE does not affect Tor). It also works around a crash
1078 bug caused by some operating systems' response to the "POODLE" attack
1079 (which does affect Tor). It also contains a few miscellaneous fixes.
1081 o Major security fixes:
1082 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
1083 today support TLS 1.0 or later, so we can safely turn off support
1084 for this old (and insecure) protocol. Fixes bug 13426.
1086 o Major bugfixes (openssl bug workaround):
1087 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
1088 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
1089 13471. This is a workaround for an OpenSSL bug.
1092 - Disable the sandbox name resolver cache when running tor-resolve:
1093 tor-resolve doesn't use the sandbox code, and turning it on was
1094 breaking attempts to do tor-resolve on a non-default server on
1095 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
1097 o Compilation fixes:
1098 - Build and run correctly on systems like OpenBSD-current that have
1099 patched OpenSSL to remove get_cipher_by_char and/or its
1100 implementations. Fixes issue 13325.
1102 o Downgraded warnings:
1103 - Downgrade the severity of the 'unexpected sendme cell from client'
1104 from 'warn' to 'protocol warning'. Closes ticket 8093.
1107 Changes in version 0.2.4.25 - 2014-10-20
1108 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
1109 (even though POODLE does not affect Tor). It also works around a crash
1110 bug caused by some operating systems' response to the "POODLE" attack
1111 (which does affect Tor).
1113 o Major security fixes (also in 0.2.5.9-rc):
1114 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
1115 today support TLS 1.0 or later, so we can safely turn off support
1116 for this old (and insecure) protocol. Fixes bug 13426.
1118 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
1119 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
1120 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
1121 13471. This is a workaround for an OpenSSL bug.
1124 Changes in version 0.2.5.8-rc - 2014-09-22
1125 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
1126 series. It fixes a bug that affects consistency and speed when
1127 connecting to hidden services, and it updates the location of one of
1128 the directory authorities.
1131 - Clients now send the correct address for their chosen rendezvous
1132 point when trying to access a hidden service. They used to send
1133 the wrong address, which would still work some of the time because
1134 they also sent the identity digest of the rendezvous point, and if
1135 the hidden service happened to try connecting to the rendezvous
1136 point from a relay that already had a connection open to it,
1137 the relay would reuse that connection. Now connections to hidden
1138 services should be more robust and faster. Also, this bug meant
1139 that clients were leaking to the hidden service whether they were
1140 on a little-endian (common) or big-endian (rare) system, which for
1141 some users might have reduced their anonymity. Fixes bug 13151;
1142 bugfix on 0.2.1.5-alpha.
1144 o Directory authority changes:
1145 - Change IP address for gabelmoo (v3 directory authority).
1148 Changes in version 0.2.4.24 - 2014-09-22
1149 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
1150 connecting to hidden services, and it updates the location of one of
1151 the directory authorities.
1154 - Clients now send the correct address for their chosen rendezvous
1155 point when trying to access a hidden service. They used to send
1156 the wrong address, which would still work some of the time because
1157 they also sent the identity digest of the rendezvous point, and if
1158 the hidden service happened to try connecting to the rendezvous
1159 point from a relay that already had a connection open to it,
1160 the relay would reuse that connection. Now connections to hidden
1161 services should be more robust and faster. Also, this bug meant
1162 that clients were leaking to the hidden service whether they were
1163 on a little-endian (common) or big-endian (rare) system, which for
1164 some users might have reduced their anonymity. Fixes bug 13151;
1165 bugfix on 0.2.1.5-alpha.
1167 o Directory authority changes:
1168 - Change IP address for gabelmoo (v3 directory authority).
1170 o Minor features (geoip):
1171 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
1175 Changes in version 0.2.5.7-rc - 2014-09-11
1176 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
1177 release series, and some long-standing bugs related to ORPort reachability
1178 testing and failure to send CREATE cells. It is the first release
1179 candidate for the Tor 0.2.5.x series.
1181 o Major bugfixes (client, startup):
1182 - Start making circuits as soon as DisabledNetwork is turned off.
1183 When Tor started with DisabledNetwork set, it would correctly
1184 conclude that it shouldn't build circuits, but it would mistakenly
1185 cache this conclusion, and continue believing it even when
1186 DisableNetwork is set to 0. Fixes the bug introduced by the fix
1187 for bug 11200; bugfix on 0.2.5.4-alpha.
1188 - Resume expanding abbreviations for command-line options. The fix
1189 for bug 4647 accidentally removed our hack from bug 586 that
1190 rewrote HashedControlPassword to __HashedControlSessionPassword
1191 when it appears on the commandline (which allowed the user to set
1192 her own HashedControlPassword in the torrc file while the
1193 controller generates a fresh session password for each run). Fixes
1194 bug 12948; bugfix on 0.2.5.1-alpha.
1195 - Warn about attempts to run hidden services and relays in the same
1196 process: that's probably not a good idea. Closes ticket 12908.
1198 o Major bugfixes (relay):
1199 - Avoid queuing or sending destroy cells for circuit ID zero when we
1200 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
1201 Found and fixed by "cypherpunks".
1202 - Fix ORPort reachability detection on relays running behind a
1203 proxy, by correctly updating the "local" mark on the controlling
1204 channel when changing the address of an or_connection_t after the
1205 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
1207 o Minor features (bridge):
1208 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
1209 cookie file for the ExtORPort g+r by default.
1211 o Minor features (geoip):
1212 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
1215 o Minor bugfixes (logging):
1216 - Reduce the log severity of the "Pluggable transport proxy does not
1217 provide any needed transports and will not be launched." message,
1218 since Tor Browser includes several ClientTransportPlugin lines in
1219 its torrc-defaults file, leading every Tor Browser user who looks
1220 at her logs to see these notices and wonder if they're dangerous.
1221 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
1222 - Downgrade "Unexpected onionskin length after decryption" warning
1223 to a protocol-warn, since there's nothing relay operators can do
1224 about a client that sends them a malformed create cell. Resolves
1225 bug 12996; bugfix on 0.0.6rc1.
1226 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
1227 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
1228 - When logging information about an EXTEND2 or EXTENDED2 cell, log
1229 their names correctly. Fixes part of bug 12700; bugfix
1231 - When logging information about a relay cell whose command we don't
1232 recognize, log its command as an integer. Fixes part of bug 12700;
1233 bugfix on 0.2.1.10-alpha.
1234 - Escape all strings from the directory connection before logging
1235 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
1237 o Minor bugfixes (controller):
1238 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
1239 bug 12864; bugfix on 0.2.5.1-alpha.
1240 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
1241 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
1244 o Minor bugfixes (compilation):
1245 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
1246 bugfix on 0.2.5.5-alpha.
1247 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
1248 0.2.5.1-alpha. Patch from "NewEraCracker".
1249 - In routerlist_assert_ok(), don't take the address of a
1250 routerinfo's cache_info member unless that routerinfo is non-NULL.
1251 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
1252 - Fix a large number of false positive warnings from the clang
1253 analyzer static analysis tool. This should make real warnings
1254 easier for clang analyzer to find. Patch from "teor". Closes
1257 o Distribution (systemd):
1258 - Verify configuration file via ExecStartPre in the systemd unit
1259 file. Patch from intrigeri; resolves ticket 12730.
1260 - Explicitly disable RunAsDaemon in the systemd unit file. Our
1261 current systemd unit uses "Type = simple", so systemd does not
1262 expect tor to fork. If the user has "RunAsDaemon 1" in their
1263 torrc, then things won't work as expected. This is e.g. the case
1264 on Debian (and derivatives), since there we pass "--defaults-torrc
1265 /usr/share/tor/tor-service-defaults-torrc" (that contains
1266 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
1270 - Adjust the URLs in the README to refer to the new locations of
1271 several documents on the website. Fixes bug 12830. Patch from
1273 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
1277 Changes in version 0.2.5.6-alpha - 2014-07-28
1278 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
1279 risk from guard rotation, and fixes a variety of other issues to get
1280 us closer to a release candidate.
1282 o Major features (also in 0.2.4.23):
1283 - Make the number of entry guards configurable via a new
1284 NumEntryGuards consensus parameter, and the number of directory
1285 guards configurable via a new NumDirectoryGuards consensus
1286 parameter. Implements ticket 12688.
1288 o Major bugfixes (also in 0.2.4.23):
1289 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
1290 implementation that caused incorrect results on 32-bit
1291 implementations when certain malformed inputs were used along with
1292 a small class of private ntor keys. This bug does not currently
1293 appear to allow an attacker to learn private keys or impersonate a
1294 Tor server, but it could provide a means to distinguish 32-bit Tor
1295 implementations from 64-bit Tor implementations. Fixes bug 12694;
1296 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
1300 - Perform circuit cleanup operations even when circuit
1301 construction operations are disabled (because the network is
1302 disabled, or because there isn't enough directory information).
1303 Previously, when we were not building predictive circuits, we
1304 were not closing expired circuits either. Fixes bug 8387; bugfix on
1305 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
1306 became more strict about when we have "enough directory information
1310 - Authorities now assign the Guard flag to the fastest 25% of the
1311 network (it used to be the fastest 50%). Also raise the consensus
1312 weight that guarantees the Guard flag from 250 to 2000. For the
1313 current network, this results in about 1100 guards, down from 2500.
1314 This step paves the way for moving the number of entry guards
1315 down to 1 (proposal 236) while still providing reasonable expected
1316 performance for most users. Implements ticket 12690.
1317 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
1319 - Slightly enhance the diagnostic message for bug 12184.
1321 o Minor bugfixes (also in 0.2.4.23):
1322 - Warn and drop the circuit if we receive an inbound 'relay early'
1323 cell. Those used to be normal to receive on hidden service circuits
1324 due to bug 1038, but the buggy Tor versions are long gone from
1325 the network so we can afford to resume watching for them. Resolves
1326 the rest of bug 1038; bugfix on 0.2.1.19.
1327 - Correct a confusing error message when trying to extend a circuit
1328 via the control protocol but we don't know a descriptor or
1329 microdescriptor for one of the specified relays. Fixes bug 12718;
1330 bugfix on 0.2.3.1-alpha.
1333 - Fix compilation when building with bufferevents enabled. (This
1334 configuration is still not expected to work, however.)
1335 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
1336 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
1338 - Compile correctly with builds and forks of OpenSSL (such as
1339 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
1340 0.2.1.1-alpha. Patch from "dhill".
1343 Changes in version 0.2.4.23 - 2014-07-28
1344 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
1345 guard rotation, and also backports several important fixes from the
1346 Tor 0.2.5 alpha release series.
1349 - Clients now look at the "usecreatefast" consensus parameter to
1350 decide whether to use CREATE_FAST or CREATE cells for the first hop
1351 of their circuit. This approach can improve security on connections
1352 where Tor's circuit handshake is stronger than the available TLS
1353 connection security levels, but the tradeoff is more computational
1354 load on guard relays. Implements proposal 221. Resolves ticket 9386.
1355 - Make the number of entry guards configurable via a new
1356 NumEntryGuards consensus parameter, and the number of directory
1357 guards configurable via a new NumDirectoryGuards consensus
1358 parameter. Implements ticket 12688.
1361 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
1362 implementation that caused incorrect results on 32-bit
1363 implementations when certain malformed inputs were used along with
1364 a small class of private ntor keys. This bug does not currently
1365 appear to allow an attacker to learn private keys or impersonate a
1366 Tor server, but it could provide a means to distinguish 32-bit Tor
1367 implementations from 64-bit Tor implementations. Fixes bug 12694;
1368 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
1372 - Warn and drop the circuit if we receive an inbound 'relay early'
1373 cell. Those used to be normal to receive on hidden service circuits
1374 due to bug 1038, but the buggy Tor versions are long gone from
1375 the network so we can afford to resume watching for them. Resolves
1376 the rest of bug 1038; bugfix on 0.2.1.19.
1377 - Correct a confusing error message when trying to extend a circuit
1378 via the control protocol but we don't know a descriptor or
1379 microdescriptor for one of the specified relays. Fixes bug 12718;
1380 bugfix on 0.2.3.1-alpha.
1381 - Avoid an illegal read from stack when initializing the TLS
1382 module using a version of OpenSSL without all of the ciphers
1383 used by the v2 link handshake. Fixes bug 12227; bugfix on
1384 0.2.4.8-alpha. Found by "starlight".
1387 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
1391 Changes in version 0.2.5.5-alpha - 2014-06-18
1392 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
1393 0.2.5.x release series, including a couple of DoS issues, some
1394 performance regressions, a large number of bugs affecting the Linux
1395 seccomp2 sandbox code, and various other bugfixes. It also adds
1396 diagnostic bugfixes for a few tricky issues that we're trying to
1399 o Major features (security, traffic analysis resistance):
1400 - Several major improvements to the algorithm used to decide when to
1401 close TLS connections. Previous versions of Tor closed connections
1402 at a fixed interval after the last time a non-padding cell was
1403 sent over the connection, regardless of the target of the
1404 connection. Now, we randomize the intervals by adding up to 50% of
1405 their base value, we measure the length of time since connection
1406 last had at least one circuit, and we allow connections to known
1407 ORs to remain open a little longer (15 minutes instead of 3
1408 minutes minimum). These changes should improve Tor's resistance
1409 against some kinds of traffic analysis, and lower some overhead
1410 from needlessly closed connections. Fixes ticket 6799.
1411 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
1413 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
1414 - Fix a memory leak that could occur if a microdescriptor parse
1415 fails during the tokenizing step. This bug could enable a memory
1416 exhaustion attack by directory servers. Fixes bug 11649; bugfix
1419 o Major bugfixes (security, directory authorities):
1420 - Directory authorities now include a digest of each relay's
1421 identity key as a part of its microdescriptor.
1423 This is a workaround for bug 11743 (reported by "cypherpunks"),
1424 where Tor clients do not support receiving multiple
1425 microdescriptors with the same SHA256 digest in the same
1426 consensus. When clients receive a consensus like this, they only
1427 use one of the relays. Without this fix, a hostile relay could
1428 selectively disable some client use of target relays by
1429 constructing a router descriptor with a different identity and the
1430 same microdescriptor parameters and getting the authorities to
1431 list it in a microdescriptor consensus. This fix prevents an
1432 attacker from causing a microdescriptor collision, because the
1433 router's identity is not forgeable.
1435 o Major bugfixes (relay):
1436 - Use a direct dirport connection when uploading non-anonymous
1437 descriptors to the directory authorities. Previously, relays would
1438 incorrectly use tunnel connections under a fairly wide variety of
1439 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
1440 - When a circuit accidentally has the same circuit ID for its
1441 forward and reverse direction, correctly detect the direction of
1442 cells using that circuit. Previously, this bug made roughly one
1443 circuit in a million non-functional. Fixes bug 12195; this is a
1444 bugfix on every version of Tor.
1446 o Major bugfixes (client, pluggable transports):
1447 - When managing pluggable transports, use OS notification facilities
1448 to learn if they have crashed, and don't attempt to kill any
1449 process that has already exited. Fixes bug 8746; bugfix
1452 o Minor features (diagnostic):
1453 - When logging a warning because of bug 7164, additionally check the
1454 hash table for consistency (as proposed on ticket 11737). This may
1455 help diagnose bug 7164.
1456 - When we log a heartbeat, log how many one-hop circuits we have
1457 that are at least 30 minutes old, and log status information about
1458 a few of them. This is an attempt to track down bug 8387.
1459 - When encountering an unexpected CR while writing text to a file on
1460 Windows, log the name of the file. Should help diagnosing
1462 - Give more specific warnings when a client notices that an onion
1463 handshake has failed. Fixes ticket 9635.
1464 - Add significant new logging code to attempt to diagnose bug 12184,
1465 where relays seem to run out of available circuit IDs.
1466 - Improve the diagnostic log message for bug 8387 even further to
1467 try to improve our odds of figuring out why one-hop directory
1468 circuits sometimes do not get closed.
1470 o Minor features (security, memory management):
1471 - Memory allocation tricks (mempools and buffer freelists) are now
1472 disabled by default. You can turn them back on with
1473 --enable-mempools and --enable-buf-freelists respectively. We're
1474 disabling these features because malloc performance is good enough
1475 on most platforms, and a similar feature in OpenSSL exacerbated
1476 exploitation of the Heartbleed attack. Resolves ticket 11476.
1478 o Minor features (security):
1479 - Apply the secure SipHash-2-4 function to the hash table mapping
1480 circuit IDs and channels to circuits. We missed this one when we
1481 were converting all the other hash functions to use SipHash back
1482 in 0.2.5.3-alpha. Resolves ticket 11750.
1484 o Minor features (build):
1485 - The configure script has a --disable-seccomp option to turn off
1486 support for libseccomp on systems that have it, in case it (or
1487 Tor's use of it) is broken. Resolves ticket 11628.
1489 o Minor features (other):
1490 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
1493 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
1494 - When running a hidden service, do not allow TunneledDirConns 0;
1495 this will keep the hidden service from running, and also
1496 make it publish its descriptors directly over HTTP. Fixes bug 10849;
1497 bugfix on 0.2.1.1-alpha.
1499 o Minor bugfixes (performance):
1500 - Avoid a bug where every successful connection made us recompute
1501 the flag telling us whether we have sufficient information to
1502 build circuits. Previously, we would forget our cached value
1503 whenever we successfully opened a channel (or marked a router as
1504 running or not running for any other reason), regardless of
1505 whether we had previously believed the router to be running. This
1506 forced us to run an expensive update operation far too often.
1507 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
1508 - Avoid using tor_memeq() for checking relay cell integrity. This
1509 removes a possible performance bottleneck. Fixes part of bug
1510 12169; bugfix on 0.2.1.31.
1512 o Minor bugfixes (compilation):
1513 - Fix compilation of test_status.c when building with MVSC. Bugfix
1514 on 0.2.5.4-alpha. Patch from Gisle Vanem.
1515 - Resolve GCC complaints on OpenBSD about discarding constness in
1516 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
1517 on 0.1.1.23. Patch from Dana Koch.
1518 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
1519 treatment of long and time_t as comparable types. Fixes part of
1520 bug 11633. Patch from Dana Koch.
1521 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
1522 11623; bugfix on 0.2.5.3-alpha.
1523 - When deciding whether to build the 64-bit curve25519
1524 implementation, detect platforms where we can compile 128-bit
1525 arithmetic but cannot link it. Fixes bug 11729; bugfix on
1526 0.2.4.8-alpha. Patch from "conradev".
1527 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
1528 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
1529 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
1532 o Minor bugfixes (Directory server):
1533 - When sending a compressed set of descriptors or microdescriptors,
1534 make sure to finalize the zlib stream. Previously, we would write
1535 all the compressed data, but if the last descriptor we wanted to
1536 send was missing or too old, we would not mark the stream as
1537 finished. This caused problems for decompression tools. Fixes bug
1538 11648; bugfix on 0.1.1.23.
1540 o Minor bugfixes (Linux seccomp sandbox):
1541 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
1542 11622; bugfix on 0.2.5.1-alpha.
1543 - Avoid crashing when re-opening listener ports with the seccomp
1544 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
1545 - Avoid crashing with the seccomp sandbox enabled along with
1546 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
1547 - When we receive a SIGHUP with the sandbox enabled, correctly
1548 support rotating our log files. Fixes bug 12032; bugfix
1550 - Avoid crash when running with sandboxing enabled and
1551 DirReqStatistics not disabled. Fixes bug 12035; bugfix
1553 - Fix a "BUG" warning when trying to write bridge-stats files with
1554 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
1556 - Prevent the sandbox from crashing on startup when run with the
1557 --enable-expensive-hardening configuration option. Fixes bug
1558 11477; bugfix on 0.2.5.4-alpha.
1559 - When running with DirPortFrontPage and sandboxing both enabled,
1560 reload the DirPortFrontPage correctly when restarting. Fixes bug
1561 12028; bugfix on 0.2.5.1-alpha.
1562 - Don't try to enable the sandbox when using the Tor binary to check
1563 its configuration, hash a passphrase, or so on. Doing so was
1564 crashing on startup for some users. Fixes bug 11609; bugfix
1566 - Avoid warnings when running with sandboxing and node statistics
1567 enabled at the same time. Fixes part of 12064; bugfix on
1568 0.2.5.1-alpha. Patch from Michael Wolf.
1569 - Avoid warnings when running with sandboxing enabled at the same
1570 time as cookie authentication, hidden services, or directory
1571 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
1572 - Do not allow options that require calls to exec to be enabled
1573 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
1574 bug 12043; bugfix on 0.2.5.1-alpha.
1575 - Handle failures in getpwnam()/getpwuid() when running with the
1576 User option set and the Linux syscall sandbox enabled. Fixes bug
1577 11946; bugfix on 0.2.5.1-alpha.
1578 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
1579 to avoid calling getaddrinfo() after installing the sandbox
1580 filters. Previously, it preloaded a cache with the IPv4 address
1581 for our hostname, and nothing else. Now, it loads the cache with
1582 every address that it used to initialize the Tor process. Fixes
1583 bug 11970; bugfix on 0.2.5.1-alpha.
1585 o Minor bugfixes (pluggable transports):
1586 - Enable the ExtORPortCookieAuthFile option, to allow changing the
1587 default location of the authentication token for the extended OR
1588 Port as used by sever-side pluggable transports. We had
1589 implemented this option before, but the code to make it settable
1590 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
1591 - Avoid another 60-second delay when starting Tor in a pluggable-
1592 transport-using configuration when we already have cached
1593 descriptors for our bridges. Fixes bug 11965; bugfix
1596 o Minor bugfixes (client):
1597 - Avoid "Tried to open a socket with DisableNetwork set" warnings
1598 when starting a client with bridges configured and DisableNetwork
1599 set. (Tor launcher starts Tor with DisableNetwork set the first
1600 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
1602 o Minor bugfixes (testing):
1603 - The Python parts of the test scripts now work on Python 3 as well
1604 as Python 2, so systems where '/usr/bin/python' is Python 3 will
1605 no longer have the tests break. Fixes bug 11608; bugfix
1607 - When looking for versions of python that we could run the tests
1608 with, check for "python2.7" and "python3.3"; previously we were
1609 only looking for "python", "python2", and "python3". Patch from
1610 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
1611 - Fix all valgrind warnings produced by the unit tests. There were
1612 over a thousand memory leak warnings previously, mostly produced
1613 by forgetting to free things in the unit test code. Fixes bug
1614 11618, bugfixes on many versions of Tor.
1616 o Minor bugfixes (tor-fw-helper):
1617 - Give a correct log message when tor-fw-helper fails to launch.
1618 (Previously, we would say something like "tor-fw-helper sent us a
1619 string we could not parse".) Fixes bug 9781; bugfix
1622 o Minor bugfixes (relay, threading):
1623 - Check return code on spawn_func() in cpuworker code, so that we
1624 don't think we've spawned a nonworking cpuworker and write junk to
1625 it forever. Fix related to bug 4345; bugfix on all released Tor
1626 versions. Found by "skruffy".
1627 - Use a pthread_attr to make sure that spawn_func() cannot return an
1628 error while at the same time launching a thread. Fix related to
1629 bug 4345; bugfix on all released Tor versions. Reported
1632 o Minor bugfixes (relay, oom prevention):
1633 - Correctly detect the total available system memory. We tried to do
1634 this in 0.2.5.4-alpha, but the code was set up to always return an
1635 error value, even on success. Fixes bug 11805; bugfix
1638 o Minor bugfixes (relay, other):
1639 - We now drop CREATE cells for already-existent circuit IDs and for
1640 zero-valued circuit IDs, regardless of other factors that might
1641 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
1643 - Avoid an illegal read from stack when initializing the TLS module
1644 using a version of OpenSSL without all of the ciphers used by the
1645 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
1647 - When rejecting DATA cells for stream_id zero, still count them
1648 against the circuit's deliver window so that we don't fail to send
1649 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
1651 o Minor bugfixes (logging):
1652 - Fix a misformatted log message about delayed directory fetches.
1653 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
1654 - Squelch a spurious LD_BUG message "No origin circuit for
1655 successful SOCKS stream" in certain hidden service failure cases;
1659 - Include a tor.service file in contrib/dist for use with systemd.
1660 Some distributions will be able to use this file unmodified;
1661 others will need to tweak it, or write their own. Patch from Jamie
1662 Nguyen; resolves ticket 8368.
1665 - Clean up several option names in the manpage to match their real
1666 names, add the missing documentation for a couple of testing and
1667 directory authority options, remove the documentation for a
1668 V2-directory fetching option that no longer exists. Resolves
1670 - Correct the documenation so that it lists the correct directory
1671 for the stats files. (They are in a subdirectory called "stats",
1673 - In the manpage, move more authority-only options into the
1674 directory authority section so that operators of regular directory
1675 caches don't get confused.
1678 - The contrib directory has been sorted and tidied. Before, it was
1679 an unsorted dumping ground for useful and not-so-useful things.
1680 Now, it is divided based on functionality, and the items which
1681 seemed to be nonfunctional or useless have been removed. Resolves
1682 ticket 8966; based on patches from "rl1987".
1685 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
1686 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
1687 - The TunnelDirConns and PreferTunnelledDirConns options no longer
1688 exist; tunneled directory connections have been available since
1689 0.1.2.5-alpha, and turning them off is not a good idea. This is a
1690 brute-force fix for 10849, where "TunnelDirConns 0" would break
1694 Changes in version 0.2.4.22 - 2014-05-16
1695 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
1696 alpha release series. These include blocking all authority signing
1697 keys that may have been affected by the OpenSSL "heartbleed" bug,
1698 choosing a far more secure set of TLS ciphersuites by default, closing
1699 a couple of memory leaks that could be used to run a target relay out
1700 of RAM, and several others.
1702 o Major features (security, backport from 0.2.5.4-alpha):
1703 - Block authority signing keys that were used on authorities
1704 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
1705 don't have any evidence that these keys _were_ compromised; we're
1706 doing this to be prudent.) Resolves ticket 11464.
1708 o Major bugfixes (security, OOM):
1709 - Fix a memory leak that could occur if a microdescriptor parse
1710 fails during the tokenizing step. This bug could enable a memory
1711 exhaustion attack by directory servers. Fixes bug 11649; bugfix
1714 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
1715 - The relay ciphersuite list is now generated automatically based on
1716 uniform criteria, and includes all OpenSSL ciphersuites with
1717 acceptable strength and forward secrecy. Previously, we had left
1718 some perfectly fine ciphersuites unsupported due to omission or
1719 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
1720 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
1721 - Relays now trust themselves to have a better view than clients of
1722 which TLS ciphersuites are better than others. (Thanks to bug
1723 11513, the relay list is now well-considered, whereas the client
1724 list has been chosen mainly for anti-fingerprinting purposes.)
1725 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
1726 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
1727 AES128. Resolves ticket 11528.
1728 - Clients now try to advertise the same list of ciphersuites as
1729 Firefox 28. This change enables selection of (fast) GCM
1730 ciphersuites, disables some strange old ciphers, and stops
1731 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
1732 Resolves ticket 11438.
1734 o Minor bugfixes (configuration, security):
1735 - When running a hidden service, do not allow TunneledDirConns 0:
1736 trying to set that option together with a hidden service would
1737 otherwise prevent the hidden service from running, and also make
1738 it publish its descriptors directly over HTTP. Fixes bug 10849;
1739 bugfix on 0.2.1.1-alpha.
1741 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
1742 - Avoid sending a garbage value to the controller when a circuit is
1743 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
1745 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
1746 - Stop leaking memory when we successfully resolve a PTR record.
1747 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
1749 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
1750 - Avoid 60-second delays in the bootstrapping process when Tor is
1751 launching for a second time while using bridges. Fixes bug 9229;
1752 bugfix on 0.2.0.3-alpha.
1754 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
1755 - Give the correct URL in the warning message when trying to run a
1756 relay on an ancient version of Windows. Fixes bug 9393.
1758 o Minor bugfixes (compilation):
1759 - Fix a compilation error when compiling with --disable-curve25519.
1760 Fixes bug 9700; bugfix on 0.2.4.17-rc.
1763 - Downgrade the warning severity for the the "md was still
1764 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
1765 for trying to diagnose this bug, and the current warning in
1766 earlier versions of tor achieves nothing useful. Addresses warning
1769 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
1770 - When we run out of usable circuit IDs on a channel, log only one
1771 warning for the whole channel, and describe how many circuits
1772 there were on the channel. Fixes part of ticket 11553.
1774 o Minor features (security, backport from 0.2.5.4-alpha):
1775 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
1776 leave the default at 8GBytes), to better support Raspberry Pi
1777 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
1779 o Documentation (backport from 0.2.5.4-alpha):
1780 - Correctly document that we search for a system torrc file before
1781 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
1785 Changes in version 0.2.5.4-alpha - 2014-04-25
1786 Tor 0.2.5.4-alpha includes several security and performance
1787 improvements for clients and relays, including blacklisting authority
1788 signing keys that were used while susceptible to the OpenSSL
1789 "heartbleed" bug, fixing two expensive functions on busy relays,
1790 improved TLS ciphersuite preference lists, support for run-time
1791 hardening on compilers that support AddressSanitizer, and more work on
1792 the Linux sandbox code.
1794 There are also several usability fixes for clients (especially clients
1795 that use bridges), two new TransPort protocols supported (one on
1796 OpenBSD, one on FreeBSD), and various other bugfixes.
1798 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
1799 have accumulated many known flaws; everyone should upgrade.
1801 o Major features (security):
1802 - If you don't specify MaxMemInQueues yourself, Tor now tries to
1803 pick a good value based on your total system memory. Previously,
1804 the default was always 8 GB. You can still override the default by
1805 setting MaxMemInQueues yourself. Resolves ticket 11396.
1806 - Block authority signing keys that were used on authorities
1807 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
1808 don't have any evidence that these keys _were_ compromised; we're
1809 doing this to be prudent.) Resolves ticket 11464.
1811 o Major features (relay performance):
1812 - Speed up server-side lookups of rendezvous and introduction point
1813 circuits by using hashtables instead of linear searches. These
1814 functions previously accounted between 3 and 7% of CPU usage on
1815 some busy relays. Resolves ticket 9841.
1816 - Avoid wasting CPU when extending a circuit over a channel that is
1817 nearly out of circuit IDs. Previously, we would do a linear scan
1818 over possible circuit IDs before finding one or deciding that we
1819 had exhausted our possibilities. Now, we try at most 64 random
1820 circuit IDs before deciding that we probably won't succeed. Fixes
1821 a possible root cause of ticket 11553.
1823 o Major features (seccomp2 sandbox, Linux only):
1824 - The seccomp2 sandbox can now run a test network for multiple hours
1825 without crashing. The sandbox is still experimental, and more bugs
1826 will probably turn up. To try it, enable "Sandbox 1" on a Linux
1827 host. Resolves ticket 11351.
1828 - Strengthen sandbox code: the sandbox can now test the arguments
1829 for rename(), and blocks _sysctl() entirely. Resolves another part
1831 - When the sandbox blocks a system call, it now tries to log a stack
1832 trace before exiting. Resolves ticket 11465.
1834 o Major bugfixes (TLS cipher selection):
1835 - The relay ciphersuite list is now generated automatically based on
1836 uniform criteria, and includes all OpenSSL ciphersuites with
1837 acceptable strength and forward secrecy. Previously, we had left
1838 some perfectly fine ciphersuites unsupported due to omission or
1839 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
1840 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
1841 - Relays now trust themselves to have a better view than clients of
1842 which TLS ciphersuites are better than others. (Thanks to bug
1843 11513, the relay list is now well-considered, whereas the client
1844 list has been chosen mainly for anti-fingerprinting purposes.)
1845 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
1846 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
1847 AES128. Resolves ticket 11528.
1848 - Clients now try to advertise the same list of ciphersuites as
1849 Firefox 28. This change enables selection of (fast) GCM
1850 ciphersuites, disables some strange old ciphers, and stops
1851 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
1852 Resolves ticket 11438.
1854 o Major bugfixes (bridge client):
1855 - Avoid 60-second delays in the bootstrapping process when Tor is
1856 launching for a second time while using bridges. Fixes bug 9229;
1857 bugfix on 0.2.0.3-alpha.
1859 o Minor features (transparent proxy, *BSD):
1860 - Support FreeBSD's ipfw firewall interface for TransPort ports on
1861 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
1862 10267; patch from "yurivict".
1863 - Support OpenBSD's divert-to rules with the pf firewall for
1864 transparent proxy ports. To enable it, set "TransProxyType
1865 pf-divert". This allows Tor to run a TransPort transparent proxy
1866 port on OpenBSD 4.4 or later without root privileges. See the
1867 pf.conf(5) manual page for information on configuring pf to use
1868 divert-to rules. Closes ticket 10896; patch from Dana Koch.
1870 o Minor features (security):
1871 - New --enable-expensive-hardening option to enable security
1872 hardening options that consume nontrivial amounts of CPU and
1873 memory. Right now, this includes AddressSanitizer and UbSan, which
1874 are supported in newer versions of GCC and Clang. Closes ticket
1877 o Minor features (log verbosity):
1878 - Demote the message that we give when a flushing connection times
1879 out for too long from NOTICE to INFO. It was usually meaningless.
1880 Resolves ticket 5286.
1881 - Don't log so many notice-level bootstrapping messages at startup
1882 about downloading descriptors. Previously, we'd log a notice
1883 whenever we learned about more routers. Now, we only log a notice
1884 at every 5% of progress. Fixes bug 9963.
1885 - Warn less verbosely when receiving a malformed
1886 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
1887 - When we run out of usable circuit IDs on a channel, log only one
1888 warning for the whole channel, and describe how many circuits
1889 there were on the channel. Fixes part of ticket 11553.
1891 o Minor features (relay):
1892 - If a circuit timed out for at least 3 minutes, check if we have a
1893 new external IP address, and publish a new descriptor with the new
1894 IP address if it changed. Resolves ticket 2454.
1896 o Minor features (controller):
1897 - Make the entire exit policy available from the control port via
1898 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
1900 - Because of the fix for ticket 11396, the real limit for memory
1901 usage may no longer match the configured MaxMemInQueues value. The
1902 real limit is now exposed via GETINFO limits/max-mem-in-queues.
1904 o Minor features (bridge client):
1905 - Report a more useful failure message when we can't connect to a
1906 bridge because we don't have the right pluggable transport
1907 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
1909 o Minor features (diagnostic):
1910 - Add more log messages to diagnose bug 7164, which causes
1911 intermittent "microdesc_free() called but md was still referenced"
1912 warnings. We now include more information, to figure out why we
1913 might be cleaning a microdescriptor for being too old if it's
1914 still referenced by a live node_t object.
1916 o Minor bugfixes (client, DNSPort):
1917 - When using DNSPort, try to respond to AAAA requests with AAAA
1918 answers. Previously, we hadn't looked at the request type when
1919 deciding which answer type to prefer. Fixes bug 10468; bugfix on
1921 - When receiving a DNS query for an unsupported record type, reply
1922 with no answer rather than with a NOTIMPL error. This behavior
1923 isn't correct either, but it will break fewer client programs, we
1924 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
1927 o Minor bugfixes (exit relay):
1928 - Stop leaking memory when we successfully resolve a PTR record.
1929 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
1931 o Minor bugfixes (bridge client):
1932 - Stop accepting bridge lines containing hostnames. Doing so would
1933 cause clients to perform DNS requests on the hostnames, which was
1934 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
1935 - Avoid a 60-second delay in the bootstrapping process when a Tor
1936 client with pluggable transports re-reads its configuration at
1937 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
1939 o Minor bugfixes (client, logging during bootstrap):
1940 - Warn only once if we start logging in an unsafe way. Previously,
1941 we complain as many times as we had problems. Fixes bug 9870;
1942 bugfix on 0.2.5.1-alpha.
1943 - Only report the first fatal bootstrap error on a given OR
1944 connection. This stops us from telling the controller bogus error
1945 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
1946 - Be more helpful when trying to run sandboxed on Linux without
1947 libseccomp. Instead of saying "Sandbox is not implemented on this
1948 platform", we now explain that we need to be built with
1949 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
1950 - Avoid generating spurious warnings when starting with
1951 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
1954 o Minor bugfixes (closing OR connections):
1955 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
1956 check if it's an or_connection_t and correctly call
1957 connection_or_close_for_error() rather than
1958 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
1960 - When closing all connections on setting DisableNetwork to 1, use
1961 connection_or_close_normally() rather than closing OR connections
1962 out from under the channel layer. Fixes bug 11306; bugfix on
1965 o Minor bugfixes (controller):
1966 - Avoid sending a garbage value to the controller when a circuit is
1967 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
1969 o Minor bugfixes (tor-fw-helper):
1970 - Allow tor-fw-helper to build again by adding src/ext to its
1971 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
1973 o Minor bugfixes (bridges):
1974 - Avoid potential crashes or bad behavior when launching a
1975 server-side managed proxy with ORPort or ExtORPort temporarily
1976 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
1978 o Minor bugfixes (platform-specific):
1979 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
1980 bug 11426; bugfix on 0.2.5.3-alpha.
1981 - When dumping a malformed directory object to disk, save it in
1982 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
1984 - Don't report failures from make_socket_reuseable() on incoming
1985 sockets on OSX: this can happen when incoming connections close
1986 early. Fixes bug 10081.
1988 o Minor bugfixes (trivial memory leaks):
1989 - Fix a small memory leak when signing a directory object. Fixes bug
1990 11275; bugfix on 0.2.4.13-alpha.
1991 - Free placeholder entries in our circuit table at exit; fixes a
1992 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
1993 - Don't re-initialize a second set of OpenSSL mutexes when starting
1994 up. Previously, we'd make one set of mutexes, and then immediately
1995 replace them with another. Fixes bug 11726; bugfix on
1997 - Resolve some memory leaks found by coverity in the unit tests, on
1998 exit in tor-gencert, and on a failure to compute digests for our
1999 own keys when generating a v3 networkstatus vote. These leaks
2000 should never have affected anyone in practice.
2002 o Minor bugfixes (hidden service):
2003 - Only retry attempts to connect to a chosen rendezvous point 8
2004 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
2006 o Minor bugfixes (misc code correctness):
2007 - Fix various instances of undefined behavior in channeltls.c,
2008 tor_memmem(), and eventdns.c that would cause us to construct
2009 pointers to memory outside an allocated object. (These invalid
2010 pointers were not accessed, but C does not even allow them to
2011 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
2012 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
2013 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
2014 fix some miscellaneous errors in our tests and codebase. Fixes bug
2015 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
2016 - Always check return values for unlink, munmap, UnmapViewOfFile;
2017 check strftime return values more often. In some cases all we can
2018 do is report a warning, but this may help prevent deeper bugs from
2019 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
2021 - Fix numerous warnings from the clang "scan-build" static analyzer.
2022 Some of these are programming style issues; some of them are false
2023 positives that indicated awkward code; some are undefined behavior
2024 cases related to constructing (but not using) invalid pointers;
2025 some are assumptions about API behavior; some are (harmlessly)
2026 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
2027 correct; and one or two are genuine bugs that weren't reachable
2028 from the rest of the program. Fixes bug 8793; bugfixes on many,
2032 - Build the torify.1 manpage again. Previously, we were only trying
2033 to build it when also building tor-fw-helper. That's why we didn't
2034 notice that we'd broken the ability to build it. Fixes bug 11321;
2035 bugfix on 0.2.5.1-alpha.
2036 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
2037 11061; bugfix on 0.2.4.7-alpha.
2038 - Correctly document that we search for a system torrc file before
2039 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
2041 - Resolve warnings from Doxygen.
2043 o Code simplifications and refactoring:
2044 - Remove is_internal_IP() function. Resolves ticket 4645.
2045 - Remove unused function circuit_dump_by_chan from circuitlist.c.
2046 Closes issue 9107; patch from "marek".
2047 - Change our use of the ENUM_BF macro to avoid declarations that
2050 o Deprecated versions:
2051 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
2052 attention for some while. Directory authorities no longer accept
2053 descriptors from relays running any version of Tor prior to Tor
2054 0.2.3.16-alpha. Resolves ticket 11149.
2057 - New macros in test.h to simplify writing mock-functions for unit
2058 tests. Part of ticket 11507. Patch from Dana Koch.
2059 - Complete tests for the status.c module. Resolves ticket 11507.
2060 Patch from Dana Koch.
2063 - Remove all code for the long unused v1 directory protocol.
2064 Resolves ticket 11070.
2067 Changes in version 0.2.5.3-alpha - 2014-03-22
2068 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
2069 two new anti-DoS features for Tor relays, resolves a bug that kept
2070 SOCKS5 support for IPv6 from working, fixes several annoying usability
2071 issues for bridge users, and removes more old code for unused
2074 The Tor 0.2.5.x release series is now in patch-freeze: no feature
2075 patches not already written will be considered for inclusion in 0.2.5.x.
2077 o Major features (relay security, DoS-resistance):
2078 - When deciding whether we have run out of memory and we need to
2079 close circuits, also consider memory allocated in buffers for
2080 streams attached to each circuit.
2082 This change, which extends an anti-DoS feature introduced in
2083 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
2084 better resist more memory-based DoS attacks than before. Since the
2085 MaxMemInCellQueues option now applies to all queues, it is renamed
2086 to MaxMemInQueues. This feature fixes bug 10169.
2087 - Avoid hash-flooding denial-of-service attacks by using the secure
2088 SipHash-2-4 hash function for our hashtables. Without this
2089 feature, an attacker could degrade performance of a targeted
2090 client or server by flooding their data structures with a large
2091 number of entries to be stored at the same hash table position,
2092 thereby slowing down the Tor instance. With this feature, hash
2093 table positions are derived from a randomized cryptographic key,
2094 and an attacker cannot predict which entries will collide. Closes
2096 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
2097 the default at 8GBytes), to better support Raspberry Pi users. Fixes
2098 bug 9686; bugfix on 0.2.4.14-alpha.
2100 o Minor features (bridges, pluggable transports):
2101 - Bridges now write the SHA1 digest of their identity key
2102 fingerprint (that is, a hash of a hash of their public key) to
2103 notice-level logs, and to a new hashed-fingerprint file. This
2104 information will help bridge operators look up their bridge in
2105 Globe and similar tools. Resolves ticket 10884.
2106 - Improve the message that Tor displays when running as a bridge
2107 using pluggable transports without an Extended ORPort listener.
2108 Also, log the message in the log file too. Resolves ticket 11043.
2110 o Minor features (other):
2111 - Add a new option, PredictedPortsRelevanceTime, to control how long
2112 after having received a request to connect to a given port Tor
2113 will try to keep circuits ready in anticipation of future requests
2114 for that port. Patch from "unixninja92"; implements ticket 9176.
2115 - Generate a warning if any ports are listed in the SocksPolicy,
2116 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
2117 AuthDirBadExit options. (These options only support address
2118 ranges.) Fixes part of ticket 11108.
2119 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
2122 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
2123 - Build without warnings under clang 3.4. (We have some macros that
2124 define static functions only some of which will get used later in
2125 the module. Starting with clang 3.4, these give a warning unless the
2126 unused attribute is set on them.) Resolves ticket 10904.
2127 - Fix build warnings about missing "a2x" comment when building the
2128 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
2129 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
2131 o Minor bugfixes (client):
2132 - Improve the log message when we can't connect to a hidden service
2133 because all of the hidden service directory nodes hosting its
2134 descriptor are excluded. Improves on our fix for bug 10722, which
2135 was a bugfix on 0.2.0.10-alpha.
2136 - Raise a control port warning when we fail to connect to all of
2137 our bridges. Previously, we didn't inform the controller, and
2138 the bootstrap process would stall. Fixes bug 11069; bugfix on
2140 - Exit immediately when a process-owning controller exits.
2141 Previously, tor relays would wait for a little while after their
2142 controller exited, as if they had gotten an INT signal -- but this
2143 was problematic, since there was no feedback for the user. To do a
2144 clean shutdown, controllers should send an INT signal and give Tor
2145 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
2146 - Stop attempting to connect to bridges before our pluggable
2147 transports are configured (harmless but resulted in some erroneous
2148 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
2149 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
2150 generating incorrect SOCKS5 responses, and confusing client
2151 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
2153 o Minor bugfixes (relays and bridges):
2154 - Avoid crashing on a malformed resolv.conf file when running a
2155 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
2156 - Non-exit relays no longer launch mock DNS requests to check for
2157 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
2158 non-exit relays stopped servicing DNS requests. Fixes bug 965;
2159 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
2160 - Bridges now report complete directory request statistics. Related
2161 to bug 5824; bugfix on 0.2.2.1-alpha.
2162 - Bridges now never collect statistics that were designed for
2163 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
2164 - Stop giving annoying warning messages when we decide not to launch
2165 a pluggable transport proxy that we don't need (because there are
2166 no bridges configured to use it). Resolves ticket 5018; bugfix
2168 - Give the correct URL in the warning message when trying to run a
2169 relay on an ancient version of Windows. Fixes bug 9393.
2171 o Minor bugfixes (backtrace support):
2172 - Support automatic backtraces on more platforms by using the
2173 "-fasynchronous-unwind-tables" compiler option. This option is
2174 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
2175 is on by default and table generation is not. This doesn't yet
2176 add Windows support; only Linux, OSX, and some BSDs are affected.
2177 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
2178 - Avoid strange behavior if two threads hit failed assertions at the
2179 same time and both try to log backtraces at once. (Previously, if
2180 this had happened, both threads would have stored their intermediate
2181 results in the same buffer, and generated junk outputs.) Reported by
2182 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
2183 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
2184 0.2.5.2-alpha; patch from Nick Hopper.
2186 o Minor bugfixes (unit tests):
2187 - Fix a small bug in the unit tests that might have made the tests
2188 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
2189 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
2192 - Remove all remaining code related to version-0 hidden service
2193 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
2194 the rest of bug 10841.
2197 - Document in the manpage that "KBytes" may also be written as
2198 "kilobytes" or "KB", that "Kbits" may also be written as
2199 "kilobits", and so forth. Closes ticket 9222.
2200 - Document that the ClientOnly config option overrides ORPort.
2201 Our old explanation made ClientOnly sound as though it did
2202 nothing at all. Resolves bug 9059.
2203 - Explain that SocksPolicy, DirPolicy, and similar options don't
2204 take port arguments. Fixes the other part of ticket 11108.
2205 - Fix a comment about the rend_server_descriptor_t.protocols field
2206 to more accurately describe its range. Also, make that field
2207 unsigned, to more accurately reflect its usage. Fixes bug 9099;
2208 bugfix on 0.2.1.5-alpha.
2209 - Fix the manpage's description of HiddenServiceAuthorizeClient:
2210 the maximum client name length is 16, not 19. Fixes bug 11118;
2211 bugfix on 0.2.1.6-alpha.
2213 o Code simplifications and refactoring:
2214 - Get rid of router->address, since in all cases it was just the
2215 string representation of router->addr. Resolves ticket 5528.
2217 o Test infrastructure:
2218 - Update to the latest version of tinytest.
2219 - Improve the tinytest implementation of string operation tests so
2220 that comparisons with NULL strings no longer crash the tests; they
2221 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
2224 Changes in version 0.2.4.21 - 2014-02-28
2225 Tor 0.2.4.21 further improves security against potential adversaries who
2226 find breaking 1024-bit crypto doable, and backports several stability
2227 and robustness patches from the 0.2.5 branch.
2229 o Major features (client security):
2230 - When we choose a path for a 3-hop circuit, make sure it contains
2231 at least one relay that supports the NTor circuit extension
2232 handshake. Otherwise, there is a chance that we're building
2233 a circuit that's worth attacking by an adversary who finds
2234 breaking 1024-bit crypto doable, and that chance changes the game
2235 theory. Implements ticket 9777.
2238 - Do not treat streams that fail with reason
2239 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
2240 since it could also indicate an ENETUNREACH connection error. Fixes
2241 part of bug 10777; bugfix on 0.2.4.8-alpha.
2243 o Code simplification and refactoring:
2244 - Remove data structures which were introduced to implement the
2245 CellStatistics option: they are now redundant with the new timestamp
2246 field in the regular packed_cell_t data structure, which we did
2247 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
2250 - Always clear OpenSSL bignums before freeing them -- even bignums
2251 that don't contain secrets. Resolves ticket 10793. Patch by
2253 - Build without warnings under clang 3.4. (We have some macros that
2254 define static functions only some of which will get used later in
2255 the module. Starting with clang 3.4, these give a warning unless the
2256 unused attribute is set on them.) Resolves ticket 10904.
2257 - Update geoip and geoip6 files to the February 7 2014 Maxmind
2258 GeoLite2 Country database.
2261 - Set the listen() backlog limit to the largest actually supported
2262 on the system, not to the value in a header file. Fixes bug 9716;
2263 bugfix on every released Tor.
2264 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
2265 exit node as a NOROUTE error, not an INTERNAL error, since they
2266 can apparently happen when trying to connect to the wrong sort
2267 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
2268 - Fix build warnings about missing "a2x" comment when building the
2269 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
2270 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
2271 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
2272 not entirely remove it from the connection lists. Fixes bug 9602;
2273 bugfix on 0.2.4.4-alpha.
2274 - Fix a segmentation fault in our benchmark code when running with
2275 Fedora's OpenSSL package, or any other OpenSSL that provides
2276 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
2277 - Turn "circuit handshake stats since last time" log messages into a
2278 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
2280 o Documentation fixes:
2281 - Document that all but one DirPort entry must have the NoAdvertise
2282 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
2285 Changes in version 0.2.5.2-alpha - 2014-02-13
2286 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
2287 like the "poor random number generation" fix and the "building too many
2288 circuits" fix. It also further improves security against potential
2289 adversaries who find breaking 1024-bit crypto doable, and launches
2290 pluggable transports on demand (which gets us closer to integrating
2291 pluggable transport support by default -- not to be confused with Tor
2292 bundles enabling pluggable transports and bridges by default).
2294 o Major features (client security):
2295 - When we choose a path for a 3-hop circuit, make sure it contains
2296 at least one relay that supports the NTor circuit extension
2297 handshake. Otherwise, there is a chance that we're building
2298 a circuit that's worth attacking by an adversary who finds
2299 breaking 1024-bit crypto doable, and that chance changes the game
2300 theory. Implements ticket 9777.
2301 - Clients now look at the "usecreatefast" consensus parameter to
2302 decide whether to use CREATE_FAST or CREATE cells for the first hop
2303 of their circuit. This approach can improve security on connections
2304 where Tor's circuit handshake is stronger than the available TLS
2305 connection security levels, but the tradeoff is more computational
2306 load on guard relays. Implements proposal 221. Resolves ticket 9386.
2308 o Major features (bridges):
2309 - Don't launch pluggable transport proxies if we don't have any
2310 bridges configured that would use them. Now we can list many
2311 pluggable transports, and Tor will dynamically start one when it
2312 hears a bridge address that needs it. Resolves ticket 5018.
2313 - The bridge directory authority now assigns status flags (Stable,
2314 Guard, etc) to bridges based on thresholds calculated over all
2315 Running bridges. Now bridgedb can finally make use of its features
2316 to e.g. include at least one Stable bridge in its answers. Fixes
2319 o Major features (other):
2320 - Extend ORCONN controller event to include an "ID" parameter,
2321 and add four new controller event types CONN_BW, CIRC_BW,
2322 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
2323 The new events are emitted in private Tor networks only, with the
2324 goal of being able to better track performance and load during
2325 full-network simulations. Implements proposal 218 and ticket 7359.
2326 - On some platforms (currently: recent OSX versions, glibc-based
2327 platforms that support the ELF format, and a few other
2328 Unix-like operating systems), Tor can now dump stack traces
2329 when a crash occurs or an assertion fails. By default, traces
2330 are dumped to stderr (if possible) and to any logs that are
2331 reporting errors. Implements ticket 9299.
2334 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
2335 not entirely remove it from the connection lists. Fixes bug 9602;
2336 bugfix on 0.2.4.4-alpha.
2337 - Do not treat streams that fail with reason
2338 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
2339 since it could also indicate an ENETUNREACH connection error. Fixes
2340 part of bug 10777; bugfix on 0.2.4.8-alpha.
2342 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
2343 - Do not allow OpenSSL engines to replace the PRNG, even when
2344 HardwareAccel is set. The only default builtin PRNG engine uses
2345 the Intel RDRAND instruction to replace the entire PRNG, and
2346 ignores all attempts to seed it with more entropy. That's
2347 cryptographically stupid: the right response to a new alleged
2348 entropy source is never to discard all previously used entropy
2349 sources. Fixes bug 10402; works around behavior introduced in
2350 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
2352 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
2353 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
2354 - Avoid launching spurious extra circuits when a stream is pending.
2355 This fixes a bug where any circuit that _wasn't_ unusable for new
2356 streams would be treated as if it were, causing extra circuits to
2357 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
2359 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2360 - No longer stop reading or writing on cpuworker connections when
2361 our rate limiting buckets go empty. Now we should handle circuit
2362 handshake requests more promptly. Resolves bug 9731.
2363 - Stop trying to bootstrap all our directory information from
2364 only our first guard. Discovered while fixing bug 9946; bugfix
2367 o Minor features (bridges, pluggable transports):
2368 - Add threshold cutoffs to the networkstatus document created by
2369 the Bridge Authority. Fixes bug 1117.
2370 - On Windows, spawn background processes using the CREATE_NO_WINDOW
2371 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
2372 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
2373 Vidalia set this option for us.) Implements ticket 10297.
2375 o Minor features (security):
2376 - Always clear OpenSSL bignums before freeing them -- even bignums
2377 that don't contain secrets. Resolves ticket 10793. Patch by
2380 o Minor features (config options and command line):
2381 - Add an --allow-missing-torrc commandline option that tells Tor to
2382 run even if the configuration file specified by -f is not available.
2383 Implements ticket 10060.
2384 - Add support for the TPROXY transparent proxying facility on Linux.
2385 See documentation for the new TransProxyType option for more
2386 details. Implementation by "thomo". Closes ticket 10582.
2388 o Minor features (controller):
2389 - Add a new "HS_DESC" controller event that reports activities
2390 related to hidden service descriptors. Resolves ticket 8510.
2391 - New "DROPGUARDS" controller command to forget all current entry
2392 guards. Not recommended for ordinary use, since replacing guards
2393 too frequently makes several attacks easier. Resolves ticket 9934;
2396 o Minor features (build):
2397 - Assume that a user using ./configure --host wants to cross-compile,
2398 and give an error if we cannot find a properly named
2399 tool-chain. Add a --disable-tool-name-check option to proceed
2400 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
2401 - If we run ./configure and the compiler recognizes -fstack-protector
2402 but the linker rejects it, warn the user about a potentially missing
2403 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
2405 o Minor features (testing):
2406 - If Python is installed, "make check" now runs extra tests beyond
2407 the unit test scripts.
2408 - When bootstrapping a test network, sometimes very few relays get
2409 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
2410 specify a set of relays which should be voted Guard regardless of
2411 their uptime or bandwidth. Addresses ticket 9206.
2413 o Minor features (log messages):
2414 - When ServerTransportPlugin is set on a bridge, Tor can write more
2415 useful statistics about bridge use in its extrainfo descriptors,
2416 but only if the Extended ORPort ("ExtORPort") is set too. Add a
2417 log message to inform the user in this case. Resolves ticket 9651.
2418 - When receiving a new controller connection, log the origin address.
2419 Resolves ticket 9698; patch from "sigpipe".
2420 - When logging OpenSSL engine status at startup, log the status of
2421 more engines. Fixes ticket 10043; patch from Joshua Datko.
2422 - Turn "circuit handshake stats since last time" log messages into a
2423 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
2425 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2426 - Improve the circuit queue out-of-memory handler. Previously, when
2427 we ran low on memory, we'd close whichever circuits had the most
2428 queued cells. Now, we close those that have the *oldest* queued
2429 cells, on the theory that those are most responsible for us
2430 running low on memory. Based on analysis from a forthcoming paper
2431 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
2432 - Generate bootstrapping status update events correctly when fetching
2433 microdescriptors. Fixes bug 9927.
2434 - Update to the October 2 2013 Maxmind GeoLite Country database.
2436 o Minor bugfixes (clients):
2437 - When closing a channel that has already been open, do not close
2438 pending circuits that were waiting to connect to the same relay.
2439 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
2442 o Minor bugfixes (relays):
2443 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
2444 exit node as a NOROUTE error, not an INTERNAL error, since they
2445 can apparently happen when trying to connect to the wrong sort
2446 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
2448 o Minor bugfixes (bridges):
2449 - Fix a bug where the first connection works to a bridge that uses a
2450 pluggable transport with client-side parameters, but we don't send
2451 the client-side parameters on subsequent connections. (We don't
2452 use any pluggable transports with client-side parameters yet,
2453 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
2454 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
2456 o Minor bugfixes (node selection):
2457 - If ExcludeNodes is set, consider non-excluded hidden service
2458 directory servers before excluded ones. Do not consider excluded
2459 hidden service directory servers at all if StrictNodes is
2460 set. (Previously, we would sometimes decide to connect to those
2461 servers, and then realize before we initiated a connection that
2462 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
2464 - If we set the ExitNodes option but it doesn't include any nodes
2465 that have the Exit flag, we would choose not to bootstrap. Now we
2466 bootstrap so long as ExitNodes includes nodes which can exit to
2467 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
2469 o Minor bugfixes (controller and command-line):
2470 - If changing a config option via "setconf" fails in a recoverable
2471 way, we used to nonetheless write our new control ports to the
2472 file described by the "ControlPortWriteToFile" option. Now we only
2473 write out that file if we successfully switch to the new config
2474 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
2475 - When a command-line option such as --version or --help that
2476 ordinarily implies --hush appears on the command line along with
2477 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
2478 only if it appeared later on the command line. Fixes bug 9578;
2479 bugfix on 0.2.5.1-alpha.
2481 o Minor bugfixes (code correctness):
2482 - Previously we used two temporary files when writing descriptors to
2483 disk; now we only use one. Fixes bug 1376.
2484 - Remove an erroneous (but impossible and thus harmless) pointer
2485 comparison that would have allowed compilers to skip a bounds
2486 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
2487 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
2488 - Fix an always-true assertion in pluggable transports code so it
2489 actually checks what it was trying to check. Fixes bug 10046;
2490 bugfix on 0.2.3.9-alpha. Found by "dcb".
2492 o Minor bugfixes (protocol correctness):
2493 - When receiving a VERSIONS cell with an odd number of bytes, close
2494 the connection immediately since the cell is malformed. Fixes bug
2495 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
2498 o Minor bugfixes (build):
2499 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
2500 turned off (that is, without support for v2 link handshakes). Fixes
2501 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
2502 - Fix compilation warnings and startup issues when running with
2503 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
2505 - Fix compilation on Solaris 9, which didn't like us having an
2506 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
2508 o Minor bugfixes (testing):
2509 - Fix a segmentation fault in our benchmark code when running with
2510 Fedora's OpenSSL package, or any other OpenSSL that provides
2511 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
2513 o Minor bugfixes (log messages):
2514 - Fix a bug where clients using bridges would report themselves
2515 as 50% bootstrapped even without a live consensus document.
2516 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
2517 - Suppress a warning where, if there's only one directory authority
2518 in the network, we would complain that votes and signatures cannot
2519 be uploaded to other directory authorities. Fixes bug 10842;
2520 bugfix on 0.2.2.26-beta.
2521 - Report bootstrapping progress correctly when we're downloading
2522 microdescriptors. We had updated our "do we have enough microdescs
2523 to begin building circuits?" logic most recently in 0.2.4.10-alpha
2524 (see bug 5956), but we left the bootstrap status event logic at
2525 "how far through getting 1/4 of them are we?" Fixes bug 9958;
2526 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
2528 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
2529 - Avoid a crash bug when starting with a corrupted microdescriptor
2530 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
2531 - If we fail to dump a previously cached microdescriptor to disk, avoid
2532 freeing duplicate data later on. Fixes bug 10423; bugfix on
2533 0.2.4.13-alpha. Spotted by "bobnomnom".
2535 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2536 - Correctly log long IPv6 exit policies, instead of truncating them
2537 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
2538 - Our default TLS ecdhe groups were backwards: we meant to be using
2539 P224 for relays (for performance win) and P256 for bridges (since
2540 it is more common in the wild). Instead we had it backwards. After
2541 reconsideration, we decided that the default should be P256 on all
2542 hosts, since its security is probably better, and since P224 is
2543 reportedly used quite little in the wild. Found by "skruffy" on
2544 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
2545 - Free directory authority certificate download statuses on exit
2546 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
2548 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2549 - If the guard we choose first doesn't answer, we would try the
2550 second guard, but once we connected to the second guard we would
2551 abandon it and retry the first one, slowing down bootstrapping.
2552 The fix is to treat all our initially chosen guards as acceptable
2553 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
2554 - Fix an assertion failure that would occur when disabling the
2555 ORPort setting on a running Tor process while accounting was
2556 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
2557 - When examining the list of network interfaces to find our address,
2558 do not consider non-running or disabled network interfaces. Fixes
2559 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
2560 - Avoid an off-by-one error when checking buffer boundaries when
2561 formatting the exit status of a pluggable transport helper.
2562 This is probably not an exploitable bug, but better safe than
2563 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
2566 o Removed code and features:
2567 - Clients now reject any directory authority certificates lacking
2568 a dir-key-crosscert element. These have been included since
2569 0.2.1.9-alpha, so there's no real reason for them to be optional
2570 any longer. Completes proposal 157. Resolves ticket 10162.
2571 - Remove all code that existed to support the v2 directory system,
2572 since there are no longer any v2 directory authorities. Resolves
2574 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
2575 options, which were used for designating authorities as "Hidden
2576 service authorities". There has been no use of hidden service
2577 authorities since 0.2.2.1-alpha, when we stopped uploading or
2578 downloading v0 hidden service descriptors. Fixes bug 10881; also
2579 part of a fix for bug 10841.
2581 o Code simplification and refactoring:
2582 - Remove some old fallback code designed to keep Tor clients working
2583 in a network with only two working relays. Elsewhere in the code we
2584 have long since stopped supporting such networks, so there wasn't
2585 much point in keeping it around. Addresses ticket 9926.
2586 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
2587 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
2588 - Remove data structures which were introduced to implement the
2589 CellStatistics option: they are now redundant with the addition
2590 of a timestamp to the regular packed_cell_t data structure, which
2591 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
2594 o Documentation (man page) fixes:
2595 - Update manpage to describe some of the files you can expect to
2596 find in Tor's DataDirectory. Addresses ticket 9839.
2597 - Document that all but one DirPort entry must have the NoAdvertise
2598 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
2600 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2601 - Clarify the usage and risks of setting the ContactInfo torrc line
2602 for your relay or bridge. Resolves ticket 9854.
2603 - Add anchors to the manpage so we can link to the html version of
2604 the documentation for specific options. Resolves ticket 9866.
2605 - Replace remaining references to DirServer in man page and
2606 log entries. Resolves ticket 10124.
2609 - Make the "tor-gencert" tool used by directory authority operators
2610 create 2048-bit signing keys by default (rather than 1024-bit, since
2611 1024-bit is uncomfortably small these days). Addresses ticket 10324.
2614 Changes in version 0.2.4.20 - 2013-12-22
2615 Tor 0.2.4.20 fixes potentially poor random number generation for users
2616 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
2617 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
2618 and 4) have no state file in their DataDirectory (as would happen on
2619 first start). Users who generated relay or hidden service identity
2620 keys in such a situation should discard them and generate new ones.
2622 This release also fixes a logic error that caused Tor clients to build
2623 many more preemptive circuits than they actually need.
2626 - Do not allow OpenSSL engines to replace the PRNG, even when
2627 HardwareAccel is set. The only default builtin PRNG engine uses
2628 the Intel RDRAND instruction to replace the entire PRNG, and
2629 ignores all attempts to seed it with more entropy. That's
2630 cryptographically stupid: the right response to a new alleged
2631 entropy source is never to discard all previously used entropy
2632 sources. Fixes bug 10402; works around behavior introduced in
2633 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
2635 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
2636 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
2637 - Avoid launching spurious extra circuits when a stream is pending.
2638 This fixes a bug where any circuit that _wasn't_ unusable for new
2639 streams would be treated as if it were, causing extra circuits to
2640 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
2643 - Avoid a crash bug when starting with a corrupted microdescriptor
2644 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
2645 - If we fail to dump a previously cached microdescriptor to disk, avoid
2646 freeing duplicate data later on. Fixes bug 10423; bugfix on
2647 0.2.4.13-alpha. Spotted by "bobnomnom".
2650 Changes in version 0.2.4.19 - 2013-12-11
2651 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
2652 (1986-2013). Aaron worked on diverse projects including helping to guide
2653 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
2654 transparency to the U.S government's PACER documents, and contributing
2655 design and development for Tor and Tor2Web. Aaron was one of the latest
2656 martyrs in our collective fight for civil liberties and human rights,
2657 and his death is all the more painful because he was one of us.
2659 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
2660 a new circuit handshake and link encryption that use ECC to provide
2661 better security and efficiency; makes relays better manage circuit
2662 creation requests; uses "directory guards" to reduce client enumeration
2663 risks; makes bridges collect and report statistics about the pluggable
2664 transports they support; cleans up and improves our geoip database;
2665 gets much closer to IPv6 support for clients, bridges, and relays; makes
2666 directory authorities use measured bandwidths rather than advertised
2667 ones when computing flags and thresholds; disables client-side DNS
2668 caching to reduce tracking risks; and fixes a big bug in bridge
2669 reachability testing. This release introduces two new design
2670 abstractions in the code: a new "channel" abstraction between circuits
2671 and or_connections to allow for implementing alternate relay-to-relay
2672 transports, and a new "circuitmux" abstraction storing the queue of
2673 circuits for a channel. The release also includes many stability,
2674 security, and privacy fixes.
2677 Changes in version 0.2.4.18-rc - 2013-11-16
2678 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
2679 series. It takes a variety of fixes from the 0.2.5.x branch to improve
2680 stability, performance, and better handling of edge cases.
2683 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
2684 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
2685 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
2686 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
2687 them to solve bug 6033.)
2690 - No longer stop reading or writing on cpuworker connections when
2691 our rate limiting buckets go empty. Now we should handle circuit
2692 handshake requests more promptly. Resolves bug 9731.
2693 - If we are unable to save a microdescriptor to the journal, do not
2694 drop it from memory and then reattempt downloading it. Fixes bug
2695 9645; bugfix on 0.2.2.6-alpha.
2696 - Stop trying to bootstrap all our directory information from
2697 only our first guard. Discovered while fixing bug 9946; bugfix
2699 - The new channel code sometimes lost track of in-progress circuits,
2700 causing long-running clients to stop building new circuits. The
2701 fix is to always call circuit_n_chan_done(chan, 0) from
2702 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
2704 o Minor bugfixes (on 0.2.4.x):
2705 - Correctly log long IPv6 exit policies, instead of truncating them
2706 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
2707 - Our default TLS ecdhe groups were backwards: we meant to be using
2708 P224 for relays (for performance win) and P256 for bridges (since
2709 it is more common in the wild). Instead we had it backwards. After
2710 reconsideration, we decided that the default should be P256 on all
2711 hosts, since its security is probably better, and since P224 is
2712 reportedly used quite little in the wild. Found by "skruffy" on
2713 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
2714 - Free directory authority certificate download statuses on exit
2715 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
2717 o Minor bugfixes (on 0.2.3.x and earlier):
2718 - If the guard we choose first doesn't answer, we would try the
2719 second guard, but once we connected to the second guard we would
2720 abandon it and retry the first one, slowing down bootstrapping.
2721 The fix is to treat all our initially chosen guards as acceptable
2722 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
2723 - Fix an assertion failure that would occur when disabling the
2724 ORPort setting on a running Tor process while accounting was
2725 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
2726 - When examining the list of network interfaces to find our address,
2727 do not consider non-running or disabled network interfaces. Fixes
2728 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
2729 - Avoid an off-by-one error when checking buffer boundaries when
2730 formatting the exit status of a pluggable transport helper.
2731 This is probably not an exploitable bug, but better safe than
2732 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
2735 o Minor features (protecting client timestamps):
2736 - Clients no longer send timestamps in their NETINFO cells. These were
2737 not used for anything, and they provided one small way for clients
2738 to be distinguished from each other as they moved from network to
2739 network or behind NAT. Implements part of proposal 222.
2740 - Clients now round timestamps in INTRODUCE cells down to the nearest
2741 10 minutes. If a new Support022HiddenServices option is set to 0, or
2742 if it's set to "auto" and the feature is disabled in the consensus,
2743 the timestamp is sent as 0 instead. Implements part of proposal 222.
2744 - Stop sending timestamps in AUTHENTICATE cells. This is not such
2745 a big deal from a security point of view, but it achieves no actual
2746 good purpose, and isn't needed. Implements part of proposal 222.
2747 - Reduce down accuracy of timestamps in hidden service descriptors.
2748 Implements part of proposal 222.
2750 o Minor features (other):
2751 - Improve the circuit queue out-of-memory handler. Previously, when
2752 we ran low on memory, we'd close whichever circuits had the most
2753 queued cells. Now, we close those that have the *oldest* queued
2754 cells, on the theory that those are most responsible for us
2755 running low on memory. Based on analysis from a forthcoming paper
2756 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
2757 - Generate bootstrapping status update events correctly when fetching
2758 microdescriptors. Fixes bug 9927.
2759 - Update to the October 2 2013 Maxmind GeoLite Country database.
2761 o Documentation fixes:
2762 - Clarify the usage and risks of setting the ContactInfo torrc line
2763 for your relay or bridge. Resolves ticket 9854.
2764 - Add anchors to the manpage so we can link to the html version of
2765 the documentation for specific options. Resolves ticket 9866.
2766 - Replace remaining references to DirServer in man page and
2767 log entries. Resolves ticket 10124.
2770 Changes in version 0.2.5.1-alpha - 2013-10-02
2771 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
2772 on Linux, allows bridges that offer pluggable transports to report usage
2773 statistics, fixes many issues to make testing easier, and provides
2774 a pile of minor features and bugfixes that have been waiting for a
2775 release of the new branch.
2777 This is the first alpha release in a new series, so expect there to
2778 be bugs. Users who would rather test out a more stable branch should
2779 stay with 0.2.4.x for now.
2781 o Major features (security):
2782 - Use the seccomp2 syscall filtering facility on Linux to limit
2783 which system calls Tor can invoke. This is an experimental,
2784 Linux-only feature to provide defense-in-depth against unknown
2785 attacks. To try turning it on, set "Sandbox 1" in your torrc
2786 file. Please be ready to report bugs. We hope to add support
2787 for better sandboxing in the future, including more fine-grained
2788 filters, better division of responsibility, and support for more
2789 platforms. This work has been done by Cristian-Matei Toader for
2790 Google Summer of Code.
2791 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
2792 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
2793 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
2794 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
2795 them to solve bug 6033.)
2797 o Major features (other):
2798 - Add support for passing arguments to managed pluggable transport
2799 proxies. Implements ticket 3594.
2800 - Bridges now track GeoIP information and the number of their users
2801 even when pluggable transports are in use, and report usage
2802 statistics in their extra-info descriptors. Resolves tickets 4773
2804 - Make testing Tor networks bootstrap better: lower directory fetch
2805 retry schedules and maximum interval without directory requests,
2806 and raise maximum download tries. Implements ticket 6752.
2807 - Add make target 'test-network' to run tests on a Chutney network.
2808 Implements ticket 8530.
2809 - The ntor handshake is now on-by-default, no matter what the
2810 directory authorities recommend. Implements ticket 8561.
2813 - Instead of writing destroy cells directly to outgoing connection
2814 buffers, queue them and intersperse them with other outgoing cells.
2815 This can prevent a set of resource starvation conditions where too
2816 many pending destroy cells prevent data cells from actually getting
2817 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
2818 bugfix on 0.2.0.1-alpha.
2819 - If we are unable to save a microdescriptor to the journal, do not
2820 drop it from memory and then reattempt downloading it. Fixes bug
2821 9645; bugfix on 0.2.2.6-alpha.
2822 - The new channel code sometimes lost track of in-progress circuits,
2823 causing long-running clients to stop building new circuits. The
2824 fix is to always call circuit_n_chan_done(chan, 0) from
2825 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
2828 - Tor now builds each source file in two modes: a mode that avoids
2829 exposing identifiers needlessly, and another mode that exposes
2830 more identifiers for testing. This lets the compiler do better at
2831 optimizing the production code, while enabling us to take more
2832 radical measures to let the unit tests test things.
2833 - The production builds no longer include functions used only in
2834 the unit tests; all functions exposed from a module only for
2835 unit-testing are now static in production builds.
2836 - Add an --enable-coverage configuration option to make the unit
2837 tests (and a new src/or/tor-cov target) to build with gcov test
2841 - We now have rudimentary function mocking support that our unit
2842 tests can use to test functions in isolation. Function mocking
2843 lets the tests temporarily replace a function's dependencies with
2844 stub functions, so that the tests can check the function without
2845 invoking the other functions it calls.
2846 - Add more unit tests for the <circid,channel>->circuit map, and
2847 the destroy-cell-tracking code to fix bug 7912.
2848 - Unit tests for failing cases of the TAP onion handshake.
2849 - More unit tests for address-manipulation functions.
2851 o Minor features (protecting client timestamps):
2852 - Clients no longer send timestamps in their NETINFO cells. These were
2853 not used for anything, and they provided one small way for clients
2854 to be distinguished from each other as they moved from network to
2855 network or behind NAT. Implements part of proposal 222.
2856 - Clients now round timestamps in INTRODUCE cells down to the nearest
2857 10 minutes. If a new Support022HiddenServices option is set to 0, or
2858 if it's set to "auto" and the feature is disabled in the consensus,
2859 the timestamp is sent as 0 instead. Implements part of proposal 222.
2860 - Stop sending timestamps in AUTHENTICATE cells. This is not such
2861 a big deal from a security point of view, but it achieves no actual
2862 good purpose, and isn't needed. Implements part of proposal 222.
2863 - Reduce down accuracy of timestamps in hidden service descriptors.
2864 Implements part of proposal 222.
2866 o Minor features (config options):
2867 - Config (torrc) lines now handle fingerprints which are missing
2868 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
2869 - Support a --dump-config option to print some or all of the
2870 configured options. Mainly useful for debugging the command-line
2871 option parsing code. Helps resolve ticket 4647.
2872 - Raise awareness of safer logging: notify user of potentially
2873 unsafe config options, like logging more verbosely than severity
2874 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
2875 - Add a new configuration option TestingV3AuthVotingStartOffset
2876 that bootstraps a network faster by changing the timing for
2877 consensus votes. Addresses ticket 8532.
2878 - Add a new torrc option "ServerTransportOptions" that allows
2879 bridge operators to pass configuration parameters to their
2880 pluggable transports. Resolves ticket 8929.
2881 - The config (torrc) file now accepts bandwidth and space limits in
2882 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
2883 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
2886 o Minor features (build):
2887 - Add support for `--library-versions` flag. Implements ticket 6384.
2888 - Return the "unexpected sendme" warnings to a warn severity, but make
2889 them rate limited, to help diagnose ticket 8093.
2890 - Detect a missing asciidoc, and warn the user about it, during
2891 configure rather than at build time. Fixes issue 6506. Patch from
2894 o Minor features (other):
2895 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
2896 sockets in a single system call. Implements ticket 5129.
2897 - Log current accounting state (bytes sent and received + remaining
2898 time for the current accounting period) in the relay's heartbeat
2899 message. Implements ticket 5526; patch from Peter Retzlaff.
2900 - Implement the TRANSPORT_LAUNCHED control port event that
2901 notifies controllers about new launched pluggable
2902 transports. Resolves ticket 5609.
2903 - If we're using the pure-C 32-bit curve25519_donna implementation
2904 of curve25519, build it with the -fomit-frame-pointer option to
2905 make it go faster on register-starved hosts. This improves our
2906 handshake performance by about 6% on i386 hosts without nacl.
2908 - Update to the September 4 2013 Maxmind GeoLite Country database.
2911 - Set the listen() backlog limit to the largest actually supported
2912 on the system, not to the value in a header file. Fixes bug 9716;
2913 bugfix on every released Tor.
2914 - No longer accept malformed http headers when parsing urls from
2915 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
2916 bugfix on 0.0.6pre1.
2917 - In munge_extrainfo_into_routerinfo(), check the return value of
2918 memchr(). This would have been a serious issue if we ever passed
2919 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
2921 - On the chance that somebody manages to build Tor on a
2922 platform where time_t is unsigned, correct the way that
2923 microdesc_add_to_cache() handles negative time arguments.
2924 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
2925 - Reject relative control socket paths and emit a warning. Previously,
2926 single-component control socket paths would be rejected, but Tor
2927 would not log why it could not validate the config. Fixes bug 9258;
2928 bugfix on 0.2.3.16-alpha.
2930 o Minor bugfixes (command line):
2931 - Use a single command-line parser for parsing torrc options on the
2932 command line and for finding special command-line options to avoid
2933 inconsistent behavior for torrc option arguments that have the same
2934 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
2936 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
2937 9573; bugfix on 0.0.9pre5.
2939 o Minor fixes (build, auxiliary programs):
2940 - Stop preprocessing the "torify" script with autoconf, since
2941 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
2943 - The tor-fw-helper program now follows the standard convention and
2944 exits with status code "0" on success. Fixes bug 9030; bugfix on
2945 0.2.3.1-alpha. Patch by Arlo Breault.
2946 - Corrected ./configure advice for what openssl dev package you should
2947 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
2949 o Minor code improvements:
2950 - Remove constants and tests for PKCS1 padding; it's insecure and
2951 shouldn't be used for anything new. Fixes bug 8792; patch
2953 - Remove instances of strcpy() from the unit tests. They weren't
2954 hurting anything, since they were only in the unit tests, but it's
2955 embarassing to have strcpy() in the code at all, and some analysis
2956 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
2957 0.2.3.8-alpha. Patch from Arlo Breault.
2960 - Remove migration code from when we renamed the "cached-routers"
2961 file to "cached-descriptors" back in 0.2.0.8-alpha. This
2962 incidentally resolves ticket 6502 by cleaning up the related code
2963 a bit. Patch from Akshay Hebbar.
2965 o Code simplification and refactoring:
2966 - Extract the common duplicated code for creating a subdirectory
2967 of the data directory and writing to a file in it. Fixes ticket
2968 4282; patch from Peter Retzlaff.
2969 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
2970 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
2971 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
2972 - Add a set of accessor functions for the circuit timeout data
2973 structure. Fixes ticket 6153; patch from "piet".
2974 - Clean up exit paths from connection_listener_new(). Closes ticket
2975 8789. Patch from Arlo Breault.
2976 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
2977 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
2978 - Use a doubly-linked list to implement the global circuit list.
2979 Resolves ticket 9108. Patch from Marek Majkowski.
2980 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
2983 Changes in version 0.2.4.17-rc - 2013-09-05
2984 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
2985 series. It adds an emergency step to help us tolerate the massive
2986 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
2987 circuit-level handshakes now effectively jump the queue compared to
2988 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
2989 big bug hindering bridge reachability tests.
2992 - Relays now process the new "NTor" circuit-level handshake requests
2993 with higher priority than the old "TAP" circuit-level handshake
2994 requests. We still process some TAP requests to not totally starve
2995 0.2.3 clients when NTor becomes popular. A new consensus parameter
2996 "NumNTorsPerTAP" lets us tune the balance later if we need to.
2997 Implements ticket 9574.
3000 - If the circuit build timeout logic is disabled (via the consensus,
3001 or because we are an authority), then don't build testing circuits.
3002 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
3003 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
3004 previously they did not, which prevented them from receiving
3005 successful connections from relays for self-test or bandwidth
3006 testing. Also, when a relay is extending a circuit to a bridge,
3007 it needs to send a NETINFO cell, even when the bridge hasn't sent
3008 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
3009 - If the time to download the next old-style networkstatus is in
3010 the future, do not decline to consider whether to download the
3011 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
3015 - Avoid double-closing the listener socket in our socketpair()
3016 replacement (used on Windows) in the case where the addresses on
3017 our opened sockets don't match what we expected. Fixes bug 9400;
3018 bugfix on 0.0.2pre7. Found by Coverity.
3020 o Minor fixes (config options):
3021 - Avoid overflows when the user sets MaxCircuitDirtiness to a
3022 ridiculously high value, by imposing a (ridiculously high) 30-day
3023 maximum on MaxCircuitDirtiness.
3024 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
3025 message is logged at notice, not at info.
3026 - Warn and fail if a server is configured not to advertise any
3027 ORPorts at all. (We need *something* to put in our descriptor,
3028 or we just won't work.)
3031 - Track how many "TAP" and "NTor" circuit handshake requests we get,
3032 and how many we complete, and log it every hour to help relay
3033 operators follow trends in network load. Addresses ticket 9658.
3034 - Update to the August 7 2013 Maxmind GeoLite Country database.
3037 Changes in version 0.2.4.16-rc - 2013-08-10
3038 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
3039 series. It fixes several crash bugs in the 0.2.4 branch.
3042 - Fix a bug in the voting algorithm that could yield incorrect results
3043 when a non-naming authority declared too many flags. Fixes bug 9200;
3044 bugfix on 0.2.0.3-alpha.
3045 - Fix an uninitialized read that could in some cases lead to a remote
3046 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
3047 Anybody running a hidden service on the experimental 0.2.4.x
3048 branch should upgrade. (This is, so far as we know, unrelated to
3050 - Avoid an assertion failure when processing DNS replies without the
3051 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
3052 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
3053 0.2.4.15-rc. Found by stem integration tests.
3056 - Fix an invalid memory read that occured when a pluggable
3057 transport proxy failed its configuration protocol.
3058 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
3059 - When evaluating whether to use a connection that we haven't
3060 decided is canonical using a recent link protocol version,
3061 decide that it's canonical only if it used address _does_
3062 match the desired address. Fixes bug 9309; bugfix on
3063 0.2.4.4-alpha. Reported by skruffy.
3064 - Make the default behavior of NumDirectoryGuards be to track
3065 NumEntryGuards. Now a user who changes only NumEntryGuards will get
3066 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
3067 - Fix a spurious compilation warning with some older versions of
3068 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
3071 - Update to the July 3 2013 Maxmind GeoLite Country database.
3074 Changes in version 0.2.4.15-rc - 2013-07-01
3075 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
3076 series. It fixes a few smaller bugs, but generally appears stable.
3077 Please test it and let us know whether it is!
3080 - When receiving a new configuration file via the control port's
3081 LOADCONF command, do not treat the defaults file as absent.
3082 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
3085 - Issue a warning when running with the bufferevents backend enabled.
3086 It's still not stable, and people should know that they're likely
3087 to hit unexpected problems. Closes ticket 9147.
3090 Changes in version 0.2.4.14-alpha - 2013-06-18
3091 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
3092 present in 0.2.4.13-alpha.
3095 - When we have too much memory queued in circuits (according to a new
3096 MaxMemInCellQueues option), close the circuits consuming the most
3097 memory. This prevents us from running out of memory as a relay if
3098 circuits fill up faster than they can be drained. Fixes bug 9063;
3099 bugfix on the 54th commit of Tor. This bug is a further fix beyond
3100 bug 6252, whose fix was merged into 0.2.3.21-rc.
3102 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
3103 where we tried to solve this issue simply by imposing an upper limit
3104 on the number of queued cells for a single circuit. That approach
3105 proved to be problematic, since there are ways to provoke clients to
3106 send a number of cells in excess of any such reasonable limit. Fixes
3107 bug 9072; bugfix on 0.2.4.13-alpha.
3109 - Limit hidden service descriptors to at most ten introduction
3110 points, to slow one kind of guard enumeration. Fixes bug 9002;
3111 bugfix on 0.1.1.11-alpha.
3114 Changes in version 0.2.4.13-alpha - 2013-06-14
3115 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
3116 vulnerabilities, makes socks5 username/password circuit isolation
3117 actually actually work (this time for sure!), and cleans up a bunch
3118 of other issues in preparation for a release candidate.
3120 o Major bugfixes (robustness):
3121 - Close any circuit that has too many cells queued on it. Fixes
3122 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
3123 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
3124 - Prevent the get_freelists() function from running off the end of
3125 the list of freelists if it somehow gets an unrecognized
3126 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
3128 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
3129 when an exit connection with optimistic data succeeds immediately
3130 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
3132 - Fix a directory authority crash bug when building a consensus
3133 using an older consensus as its basis. Fixes bug 8833. Bugfix
3137 - Avoid a memory leak where we would leak a consensus body when we
3138 find that a consensus which we couldn't previously verify due to
3139 missing certificates is now verifiable. Fixes bug 8719; bugfix
3141 - We used to always request authority certificates by identity digest,
3142 meaning we'd get the newest one even when we wanted one with a
3143 different signing key. Then we would complain about being given
3144 a certificate we already had, and never get the one we really
3145 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
3146 resource to request the one we want. Fixes bug 5595; bugfix on
3148 - Follow the socks5 protocol when offering username/password
3149 authentication. The fix for bug 8117 exposed this bug, and it
3150 turns out real-world applications like Pidgin do care. Bugfix on
3151 0.2.3.2-alpha; fixes bug 8879.
3152 - Prevent failures on Windows Vista and later when rebuilding the
3153 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
3154 bugfix on 0.2.4.12-alpha.
3157 - Fix an impossible buffer overrun in the AES unit tests. Fixes
3158 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
3159 - If for some reason we fail to write a microdescriptor while
3160 rebuilding the cache, do not let the annotations from that
3161 microdescriptor linger in the cache file, and do not let the
3162 microdescriptor stay recorded as present in its old location.
3163 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
3164 - Fix a memory leak that would occur whenever a configuration
3165 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
3166 - Paste the description for PathBias parameters from the man
3167 page into or.h, so the code documents them too. Fixes bug 7982;
3168 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
3169 - Relays now treat a changed IPv6 ORPort as sufficient reason to
3170 publish an updated descriptor. Fixes bug 6026; bugfix on
3172 - When launching a resolve request on behalf of an AF_UNIX control
3173 socket, omit the address field of the new entry connection, used in
3174 subsequent controller events, rather than letting tor_dup_addr()
3175 set it to "<unknown address type>". Fixes bug 8639; bugfix on
3178 o Minor bugfixes (log messages):
3179 - Fix a scaling issue in the path bias accounting code that
3180 resulted in "Bug:" log messages from either
3181 pathbias_scale_close_rates() or pathbias_count_build_success().
3182 This represents a bugfix on a previous bugfix: the original fix
3183 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
3185 - Give a less useless error message when the user asks for an IPv4
3186 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
3190 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
3191 to tolerate bug 8093 for now.
3192 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
3193 in directory authority votes to describe whether they have enough
3194 measured bandwidths to ignore advertised (relay descriptor)
3195 bandwidth claims. Resolves ticket 8711.
3196 - Update to the June 5 2013 Maxmind GeoLite Country database.
3198 o Removed documentation:
3199 - Remove some of the older contents of doc/ as obsolete; move others
3200 to torspec.git. Fixes bug 8965.
3202 o Code simplification and refactoring:
3203 - Avoid using character buffers when constructing most directory
3204 objects: this approach was unwieldy and error-prone. Instead,
3205 build smartlists of strings, and concatenate them when done.
3208 Changes in version 0.2.4.12-alpha - 2013-04-18
3209 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
3210 process for lengthening the guard rotation period, makes directory
3211 authority opinions in the consensus a bit less gameable, makes socks5
3212 username/password circuit isolation actually work, and fixes a wide
3213 variety of other issues.
3216 - Raise the default time that a client keeps an entry guard from
3217 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
3218 2012 paper. (We would make it even longer, but we need better client
3219 load balancing first.) Also, make the guard lifetime controllable
3220 via a new GuardLifetime torrc option and a GuardLifetime consensus
3221 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
3222 - Directory authorities now prefer using measured bandwidths to
3223 advertised ones when computing flags and thresholds. Resolves
3225 - Directory authorities that have more than a threshold number
3226 of relays with measured bandwidths now treat relays with unmeasured
3227 bandwidths as having bandwidth 0. Resolves ticket 8435.
3229 o Major bugfixes (assert / resource use):
3230 - Avoid a bug where our response to TLS renegotiation under certain
3231 network conditions could lead to a busy-loop, with 100% CPU
3232 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
3233 - Avoid an assertion when we discover that we'd like to write a cell
3234 onto a closing connection: just discard the cell. Fixes another
3235 case of bug 7350; bugfix on 0.2.4.4-alpha.
3237 o Major bugfixes (client-side privacy):
3238 - When we mark a circuit as unusable for new circuits, have it
3239 continue to be unusable for new circuits even if MaxCircuitDirtiness
3240 is increased too much at the wrong time, or the system clock jumps
3241 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
3242 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
3243 which have resolved to internal addresses") is set, apply that
3244 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
3245 - When an exit relay rejects a stream with reason "exit policy", but
3246 we only know an exit policy summary (e.g. from the microdesc
3247 consensus) for it, do not mark the relay as useless for all exiting.
3248 Instead, mark just the circuit as unsuitable for that particular
3249 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
3250 - Allow applications to get proper stream isolation with
3251 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
3252 username/password authentication also offer "no authentication". Tor
3253 had previously preferred "no authentication", so the applications
3254 never actually sent Tor their auth details. Now Tor selects
3255 username/password authentication if it's offered. You can disable
3256 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
3257 bug 8117; bugfix on 0.2.3.3-alpha.
3259 o Major bugfixes (other):
3260 - When unable to find any working directory nodes to use as a
3261 directory guard, give up rather than adding the same non-working
3262 nodes to the directory guard list over and over. Fixes bug 8231;
3263 bugfix on 0.2.4.8-alpha.
3266 - Reject as invalid most directory objects containing a NUL.
3267 Belt-and-suspender fix for bug 8037.
3268 - In our testsuite, create temporary directories with a bit more
3269 entropy in their name to make name collisions less likely. Fixes
3271 - Add CACHED keyword to ADDRMAP events in the control protocol
3272 to indicate whether a DNS result will be cached or not. Resolves
3274 - Update to the April 3 2013 Maxmind GeoLite Country database.
3276 o Minor features (build):
3277 - Detect and reject attempts to build Tor with threading support
3278 when OpenSSL has been compiled without threading support.
3280 - Clarify that when autoconf is checking for nacl, it is checking
3281 specifically for nacl with a fast curve25519 implementation.
3283 - Warn if building on a platform with an unsigned time_t: there
3284 are too many places where Tor currently assumes that time_t can
3285 hold negative values. We'd like to fix them all, but probably
3288 o Minor bugfixes (build):
3289 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
3290 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
3291 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
3292 - Add the old src/or/micro-revision.i filename to CLEANFILES.
3293 On the off chance that somebody has one, it will go away as soon
3294 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
3295 - Build Tor correctly on 32-bit platforms where the compiler can build
3296 but not run code using the "uint128_t" construction. Fixes bug 8587;
3297 bugfix on 0.2.4.8-alpha.
3298 - Fix compilation warning with some versions of clang that would
3299 prefer the -Wswitch-enum compiler flag to warn about switch
3300 statements with missing enum values, even if those switch
3301 statements have a "default:" statement. Fixes bug 8598; bugfix
3304 o Minor bugfixes (protocol):
3305 - Fix the handling of a TRUNCATE cell when it arrives while the
3306 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
3307 - Fix a misframing issue when reading the version numbers in a
3308 VERSIONS cell. Previously we would recognize [00 01 00 02] as
3309 'version 1, version 2, and version 0x100', when it should have
3310 only included versions 1 and 2. Fixes bug 8059; bugfix on
3311 0.2.0.10-alpha. Reported pseudonymously.
3312 - Make the format and order of STREAM events for DNS lookups
3313 consistent among the various ways to launch DNS lookups. Fixes
3314 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
3315 - Correct our check for which versions of Tor support the EXTEND2
3316 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
3317 later, when support was really added in version 0.2.4.8-alpha.
3318 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
3320 o Minor bugfixes (other):
3321 - Correctly store microdescriptors and extrainfo descriptors with
3322 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
3323 Bug reported by "cypherpunks".
3324 - Increase the width of the field used to remember a connection's
3325 link protocol version to two bytes. Harmless for now, since the
3326 only currently recognized versions are one byte long. Reported
3327 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
3328 - If the state file's path bias counts are invalid (presumably from a
3329 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
3330 additional checks and log messages to the scaling of Path Bias
3331 counts, in case there still are remaining issues with scaling.
3332 Should help resolve bug 8235.
3333 - Eliminate several instances where we use "Nickname=ID" to refer to
3334 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
3335 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
3336 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
3338 o Minor bugfixes (syscalls):
3339 - Always check the return values of functions fcntl() and
3340 setsockopt(). We don't believe these are ever actually failing in
3341 practice, but better safe than sorry. Also, checking these return
3342 values should please analysis tools like Coverity. Patch from
3343 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
3344 - Use direct writes rather than stdio when building microdescriptor
3345 caches, in an attempt to mitigate bug 8031, or at least make it
3348 o Minor bugfixes (config):
3349 - When rejecting a configuration because we were unable to parse a
3350 quoted string, log an actual error message. Fixes bug 7950; bugfix
3352 - Behave correctly when the user disables LearnCircuitBuildTimeout
3353 but doesn't tell us what they would like the timeout to be. Fixes
3354 bug 6304; bugfix on 0.2.2.14-alpha.
3355 - When autodetecting the number of CPUs, use the number of available
3356 CPUs in preference to the number of configured CPUs. Inform the
3357 user if this reduces the number of available CPUs. Fixes bug 8002;
3358 bugfix on 0.2.3.1-alpha.
3359 - Make it an error when you set EntryNodes but disable UseGuardNodes,
3360 since it will (surprisingly to some users) ignore EntryNodes. Fixes
3361 bug 8180; bugfix on 0.2.3.11-alpha.
3362 - Allow TestingTorNetworks to override the 4096-byte minimum for
3363 the Fast threshold. Otherwise they can't bootstrap until they've
3364 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
3365 - Fix some logic errors when the user manually overrides the
3366 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
3369 o Minor bugfixes (log messages to help diagnose bugs):
3370 - If we fail to free a microdescriptor because of bug 7164, log
3371 the filename and line number from which we tried to free it.
3372 - Add another diagnostic to the heartbeat message: track and log
3373 overhead that TLS is adding to the data we write. If this is
3374 high, we are sending too little data to SSL_write at a time.
3375 Diagnostic for bug 7707.
3376 - Add more detail to a log message about relaxed timeouts, to help
3378 - Warn more aggressively when flushing microdescriptors to a
3379 microdescriptor cache fails, in an attempt to mitigate bug 8031,
3380 or at least make it more diagnosable.
3381 - Improve debugging output to help track down bug 8185 ("Bug:
3382 outgoing relay cell has n_chan==NULL. Dropping.")
3383 - Log the purpose of a path-bias testing circuit correctly.
3384 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
3386 o Minor bugfixes (0.2.4.x log messages that were too noisy):
3387 - Don't attempt to relax the timeout of already opened 1-hop circuits.
3388 They might never timeout. This should eliminate some/all cases of
3389 the relaxed timeout log message.
3390 - Use circuit creation time for network liveness evaluation. This
3391 should eliminate warning log messages about liveness caused
3392 by changes in timeout evaluation. Fixes bug 6572; bugfix on
3394 - Reduce a path bias length check from notice to info. The message
3395 is triggered when creating controller circuits. Fixes bug 8196;
3396 bugfix on 0.2.4.8-alpha.
3397 - Fix a path state issue that triggered a notice during relay startup.
3398 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
3399 - Reduce occurrences of warns about circuit purpose in
3400 connection_ap_expire_building(). Fixes bug 8477; bugfix on
3403 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
3404 - If we encounter a write failure on a SOCKS connection before we
3405 finish our SOCKS handshake, don't warn that we closed the
3406 connection before we could send a SOCKS reply. Fixes bug 8427;
3407 bugfix on 0.1.0.1-rc.
3408 - Correctly recognize that [::1] is a loopback address. Fixes
3409 bug 8377; bugfix on 0.2.1.3-alpha.
3410 - Fix a directory authority warn caused when we have a large amount
3411 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
3412 - Don't log inappropriate heartbeat messages when hibernating: a
3413 hibernating node is _expected_ to drop out of the consensus,
3414 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
3415 bugfix on 0.2.3.1-alpha.
3416 - Don't complain about bootstrapping problems while hibernating.
3417 These complaints reflect a general code problem, but not one
3418 with any problematic effects (no connections are actually
3419 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
3421 o Documentation fixes:
3422 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
3423 names match. Fixes bug 7768.
3424 - Make the torify manpage no longer refer to tsocks; torify hasn't
3425 supported tsocks since 0.2.3.14-alpha.
3426 - Make the tor manpage no longer reference tsocks.
3427 - Fix the GeoIPExcludeUnknown documentation to refer to
3428 ExcludeExitNodes rather than the currently nonexistent
3429 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
3432 - The tor-tsocks.conf is no longer distributed or installed. We
3433 recommend that tsocks users use torsocks instead. Resolves
3437 Changes in version 0.2.4.11-alpha - 2013-03-11
3438 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
3439 more robust, makes hidden service authentication work again, and
3440 resolves a DPI fingerprint for Tor's SSL transport.
3442 o Major features (directory authorities):
3443 - Directory authorities now support a new consensus method (17)
3444 where they cap the published bandwidth of servers for which
3445 insufficient bandwidth measurements exist. Fixes part of bug 2286.
3446 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
3447 serve any v2 directory information. Now we can test disabling the
3448 old deprecated v2 directory format, and see whether doing so has
3449 any effect on network load. Begins to fix bug 6783.
3450 - Directory authorities now include inside each vote a statement of
3451 the performance thresholds they used when assigning flags.
3452 Implements ticket 8151.
3454 o Major bugfixes (directory authorities):
3455 - Stop marking every relay as having been down for one hour every
3456 time we restart a directory authority. These artificial downtimes
3457 were messing with our Stable and Guard flag calculations. Fixes
3458 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
3460 o Major bugfixes (hidden services):
3461 - Allow hidden service authentication to succeed again. When we
3462 refactored the hidden service introduction code back
3463 in 0.2.4.1-alpha, we didn't update the code that checks
3464 whether authentication information is present, causing all
3465 authentication checks to return "false". Fix for bug 8207; bugfix
3466 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
3468 o Minor features (relays, bridges):
3469 - Make bridge relays check once a minute for whether their IP
3470 address has changed, rather than only every 15 minutes. Resolves
3472 - Refactor resolve_my_address() so it returns the method by which we
3473 decided our public IP address (explicitly configured, resolved from
3474 explicit hostname, guessed from interfaces, learned by gethostname).
3475 Now we can provide more helpful log messages when a relay guesses
3476 its IP address incorrectly (e.g. due to unexpected lines in
3477 /etc/hosts). Resolves ticket 2267.
3478 - Teach bridge-using clients to avoid 0.2.2 bridges when making
3479 microdescriptor-related dir requests, and only fall back to normal
3480 descriptors if none of their bridges can handle microdescriptors
3481 (as opposed to the fix in ticket 4013, which caused them to fall
3482 back to normal descriptors if *any* of their bridges preferred
3483 them). Resolves ticket 4994.
3484 - Randomize the lifetime of our SSL link certificate, so censors can't
3485 use the static value for filtering Tor flows. Resolves ticket 8443;
3486 related to ticket 4014 which was included in 0.2.2.33.
3487 - Support a new version of the link protocol that allows 4-byte circuit
3488 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
3489 a possible resource exhaustion issue. Closes ticket 7351; implements
3492 o Minor features (portability):
3493 - Tweak the curve25519-donna*.c implementations to tolerate systems
3494 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
3495 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
3496 the signs of types during autoconf. This is better than our old
3497 approach, which didn't work when cross-compiling.
3498 - Detect the sign of enum values, rather than assuming that MSC is the
3499 only compiler where enum types are all signed. Fixes bug 7727;
3500 bugfix on 0.2.4.10-alpha.
3502 o Minor features (other):
3503 - Say "KBytes" rather than "KB" in the man page (for various values
3504 of K), to further reduce confusion about whether Tor counts in
3505 units of memory or fractions of units of memory. Resolves ticket 7054.
3506 - Clear the high bit on curve25519 public keys before passing them to
3507 our backend, in case we ever wind up using a backend that doesn't do
3508 so itself. If we used such a backend, and *didn't* clear the high bit,
3509 we could wind up in a situation where users with such backends would
3510 be distinguishable from users without. Fixes bug 8121; bugfix on
3512 - Update to the March 6 2013 Maxmind GeoLite Country database.
3514 o Minor bugfixes (clients):
3515 - When we receive a RELAY_END cell with the reason DONE, or with no
3516 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
3517 status as "connection refused". Previously we reported these cases
3518 as success but then immediately closed the connection. Fixes bug
3519 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
3520 - Downgrade an assertion in connection_ap_expire_beginning to an
3521 LD_BUG message. The fix for bug 8024 should prevent this message
3522 from displaying, but just in case, a warn that we can diagnose
3523 is better than more assert crashes. Fixes bug 8065; bugfix on
3525 - Lower path use bias thresholds to .80 for notice and .60 for warn.
3526 Also make the rate limiting flags for the path use bias log messages
3527 independent from the original path bias flags. Fixes bug 8161;
3528 bugfix on 0.2.4.10-alpha.
3530 o Minor bugfixes (relays):
3531 - Stop trying to resolve our hostname so often (e.g. every time we
3532 think about doing a directory fetch). Now we reuse the cached
3533 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
3534 and 2410 (bugfix on 0.1.2.2-alpha).
3535 - Stop sending a stray "(null)" in some cases for the server status
3536 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
3538 - When choosing which stream on a formerly stalled circuit to wake
3539 first, make better use of the platform's weak RNG. Previously,
3540 we had been using the % ("modulo") operator to try to generate a
3541 1/N chance of picking each stream, but this behaves badly with
3542 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
3544 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
3545 Irix's random() only return 15 bits; Solaris's random() returns more
3546 bits but its RAND_MAX says it only returns 15, and so on. Motivated
3547 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
3549 o Minor bugfixes (directory authorities):
3550 - Directory authorities now use less space when formatting identical
3551 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
3554 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
3555 - Avoid leaking memory if we fail to compute a consensus signature
3556 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
3557 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
3559 - Fix a memory leak during safe-cookie controller authentication.
3560 Bugfix on 0.2.3.13-alpha.
3561 - Avoid memory leak of IPv6 policy content if we fail to format it into
3562 a router descriptor. Bugfix on 0.2.4.7-alpha.
3564 o Minor bugfixes (other code correctness issues):
3565 - Avoid a crash if we fail to generate an extrainfo descriptor.
3566 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
3568 - When detecting the largest possible file descriptor (in order to
3569 close all file descriptors when launching a new program), actually
3570 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
3571 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
3573 - Fix a copy-and-paste error when adding a missing A1 to a routerset
3574 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
3575 Bugfix on 0.2.4.10-alpha.
3576 - Fix an impossible-to-trigger integer overflow when estimating how
3577 long our onionskin queue would take. (This overflow would require us
3578 to accept 4 million onionskins before processing 100 of them.) Fixes
3579 bug 8210; bugfix on 0.2.4.10-alpha.
3581 o Code simplification and refactoring:
3582 - Add a wrapper function for the common "log a message with a
3586 Changes in version 0.2.4.10-alpha - 2013-02-04
3587 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
3588 certain attacks that flood the network with relays; changes the queue
3589 for circuit create requests from a sized-based limit to a time-based
3590 limit; resumes building with MSVC on Windows; and fixes a wide variety
3593 o Major bugfixes (directory authority):
3594 - When computing directory thresholds, ignore any rejected-as-sybil
3595 nodes during the computation so that they can't influence Fast,
3596 Guard, etc. (We should have done this for proposal 109.) Fixes
3598 - When marking a node as a likely sybil, reset its uptime metrics
3599 to zero, so that it cannot time towards getting marked as Guard,
3600 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
3604 - When a TLS write is partially successful but incomplete, remember
3605 that the flushed part has been flushed, and notice that bytes were
3606 actually written. Reported and fixed pseudonymously. Fixes bug
3607 7708; bugfix on Tor 0.1.0.5-rc.
3608 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
3609 ID: these could be used to create unexpected streams and circuits
3610 which would count as "present" to some parts of Tor but "absent"
3611 to others, leading to zombie circuits and streams or to a bandwidth
3612 denial-of-service. Fixes bug 7889; bugfix on every released version
3613 of Tor. Reported by "oftc_must_be_destroyed".
3614 - Rename all macros in our local copy of queue.h to begin with "TOR_".
3615 This change seems the only good way to permanently prevent conflicts
3616 with queue.h on various operating systems. Fixes bug 8107; bugfix
3619 o Major features (relay):
3620 - Instead of limiting the number of queued onionskins (aka circuit
3621 create requests) to a fixed, hard-to-configure number, we limit
3622 the size of the queue based on how many we expect to be able to
3623 process in a given amount of time. We estimate the time it will
3624 take to process an onionskin based on average processing time
3625 of previous onionskins. Closes ticket 7291. You'll never have to
3626 configure MaxOnionsPending again.
3628 o Major features (portability):
3629 - Resume building correctly with MSVC and Makefile.nmake. This patch
3630 resolves numerous bugs and fixes reported by ultramage, including
3631 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
3632 - Make the ntor and curve25519 code build correctly with MSVC.
3633 Fix on 0.2.4.8-alpha.
3636 - When directory authorities are computing thresholds for flags,
3637 never let the threshold for the Fast flag fall below 4096
3638 bytes. Also, do not consider nodes with extremely low bandwidths
3639 when deciding thresholds for various directory flags. This change
3640 should raise our threshold for Fast relays, possibly in turn
3641 improving overall network performance; see ticket 1854. Resolves
3643 - The Tor client now ignores sub-domain components of a .onion
3644 address. This change makes HTTP "virtual" hosting
3645 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
3646 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
3647 hosted on the same hidden service. Implements proposal 204.
3648 - We compute the overhead from passing onionskins back and forth to
3649 cpuworkers, and report it when dumping statistics in response to
3650 SIGUSR1. Supports ticket 7291.
3652 o Minor features (path selection):
3653 - When deciding whether we have enough descriptors to build circuits,
3654 instead of looking at raw relay counts, look at which fraction
3655 of (bandwidth-weighted) paths we're able to build. This approach
3656 keeps clients from building circuits if their paths are likely to
3657 stand out statistically. The default fraction of paths needed is
3658 taken from the consensus directory; you can override it with the
3659 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
3660 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
3661 and we have GeoIP information, also exclude all nodes with unknown
3662 countries "??" and "A1". This behavior is controlled by the
3663 new GeoIPExcludeUnknown option: you can make such nodes always
3664 excluded with "GeoIPExcludeUnknown 1", and disable the feature
3665 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
3666 gets you the default behavior. Implements feature 7706.
3667 - Path Use Bias: Perform separate accounting for successful circuit
3668 use. Keep separate statistics on stream attempt rates versus stream
3669 success rates for each guard. Provide configurable thresholds to
3670 determine when to emit log messages or disable use of guards that
3671 fail too many stream attempts. Resolves ticket 7802.
3673 o Minor features (log messages):
3674 - When learning a fingerprint for a bridge, log its corresponding
3675 transport type. Implements ticket 7896.
3676 - Improve the log message when "Bug/attack: unexpected sendme cell
3677 from client" occurs, to help us track bug 8093.
3680 - Remove a couple of extraneous semicolons that were upsetting the
3681 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
3682 bugfix on 0.2.2.1-alpha.
3683 - Remove a source of rounding error during path bias count scaling;
3684 don't count cannibalized circuits as used for path bias until we
3685 actually try to use them; and fix a circuit_package_relay_cell()
3686 warning message about n_chan==NULL. Fixes bug 7802.
3687 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
3688 actually link against nacl when we're configured to use it. Fixes
3689 bug 7972; bugfix on 0.2.4.8-alpha.
3690 - Compile correctly with the --disable-curve25519 option. Fixes
3691 bug 8153; bugfix on 0.2.4.8-alpha.
3693 o Build improvements:
3694 - Do not report status verbosely from autogen.sh unless the -v flag
3695 is specified. Fixes issue 4664. Patch from Onizuka.
3696 - Replace all calls to snprintf() outside of src/ext with
3697 tor_snprintf(). Also remove the #define to replace snprintf with
3698 _snprintf on Windows; they have different semantics, and all of
3699 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
3700 - Try to detect if we are ever building on a platform where
3701 memset(...,0,...) does not set the value of a double to 0.0. Such
3702 platforms are permitted by the C standard, though in practice
3703 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
3704 currently support them, but it's better to detect them and fail
3705 than to perform erroneously.
3708 - Stop exporting estimates of v2 and v3 directory traffic shares
3709 in extrainfo documents. They were unneeded and sometimes inaccurate.
3710 Also stop exporting any v2 directory request statistics. Resolves
3712 - Drop support for detecting and warning about versions of Libevent
3713 before 1.3e. Nothing reasonable ships with them any longer;
3714 warning the user about them shouldn't be needed. Resolves ticket
3717 o Code simplifications and refactoring:
3718 - Rename "isin" functions to "contains", for grammar. Resolves
3720 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
3721 with the natural logarithm function from the system libm. Resolves
3725 Changes in version 0.2.4.9-alpha - 2013-01-15
3726 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
3730 - Fix backward compatibility logic when receiving an embedded ntor
3731 handshake tunneled in a CREATE cell. This clears up the "Bug:
3732 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
3736 Changes in version 0.2.4.8-alpha - 2013-01-14
3737 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
3738 risks, adds a new stronger and faster circuit handshake, and offers
3739 stronger and faster link encryption when both sides support it.
3742 - Preliminary support for directory guards (proposal 207): when
3743 possible, clients now use their entry guards for non-anonymous
3744 directory requests. This can help prevent client enumeration. Note
3745 that this behavior only works when we have a usable consensus
3746 directory, and when options about what to download are more or less
3747 standard. In the future we should re-bootstrap from our guards,
3748 rather than re-bootstrapping from the preconfigured list of
3749 directory sources that ships with Tor. Resolves ticket 6526.
3750 - Tor relays and clients now support a better CREATE/EXTEND cell
3751 format, allowing the sender to specify multiple address, identity,
3752 and handshake types. Implements Robert Ransom's proposal 200;
3755 o Major features (new circuit handshake):
3756 - Tor now supports a new circuit extension handshake designed by Ian
3757 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
3758 circuit extension handshake, later called "TAP", was a bit slow
3759 (especially on the relay side), had a fragile security proof, and
3760 used weaker keys than we'd now prefer. The new circuit handshake
3761 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
3762 function, making it significantly more secure than the older
3763 handshake, and significantly faster. Tor can use one of two built-in
3764 pure-C curve25519-donna implementations by Adam Langley, or it
3765 can link against the "nacl" library for a tuned version if present.
3767 The built-in version is very fast for 64-bit systems when building
3768 with GCC. The built-in 32-bit version is still faster than the
3769 old TAP protocol, but using libnacl is better on most such hosts.
3771 Clients don't currently use this protocol by default, since
3772 comparatively few clients support it so far. To try it, set
3773 UseNTorHandshake to 1.
3775 Implements proposal 216; closes ticket 7202.
3777 o Major features (better link encryption):
3778 - Relays can now enable the ECDHE TLS ciphersuites when available
3779 and appropriate. These ciphersuites let us negotiate forward-secure
3780 TLS secret keys more safely and more efficiently than with our
3781 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
3782 public relays prefer the (faster) P224 group, and bridges prefer
3783 the (more common) P256 group; you can override this with the
3786 Enabling these ciphers was a little tricky, since for a long time,
3787 clients had been claiming to support them without actually doing
3788 so, in order to foil fingerprinting. But with the client-side
3789 implementation of proposal 198 in 0.2.3.17-beta, clients can now
3790 match the ciphers from recent Firefox versions *and* list the
3791 ciphers they actually mean, so relays can believe such clients
3792 when they advertise ECDHE support in their TLS ClientHello messages.
3794 This feature requires clients running 0.2.3.17-beta or later,
3795 and requires both sides to be running OpenSSL 1.0.0 or later
3796 with ECC support. OpenSSL 1.0.1, with the compile-time option
3797 "enable-ec_nistp_64_gcc_128", is highly recommended.
3799 Implements the relay side of proposal 198; closes ticket 7200.
3802 - Avoid crashing when, as a relay without IPv6-exit support, a
3803 client insists on getting an IPv6 address or nothing. Fixes bug
3804 7814; bugfix on 0.2.4.7-alpha.
3807 - Improve circuit build timeout handling for hidden services.
3808 In particular: adjust build timeouts more accurately depending
3809 upon the number of hop-RTTs that a particular circuit type
3810 undergoes. Additionally, launch intro circuits in parallel
3811 if they timeout, and take the first one to reply as valid.
3812 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
3813 separate error codes; or at least, don't break for that reason.
3814 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
3815 - Update to the January 2 2013 Maxmind GeoLite Country database.
3817 o Minor features (testing):
3818 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
3819 (P-256) Diffie-Hellman handshakes to src/or/bench.
3820 - Add benchmark functions to test onion handshake performance.
3822 o Minor features (path bias detection):
3823 - Alter the Path Bias log messages to be more descriptive in terms
3824 of reporting timeouts and other statistics.
3825 - Create three levels of Path Bias log messages, as opposed to just
3826 two. These are configurable via consensus as well as via the torrc
3827 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
3828 The default values are 0.70, 0.50, and 0.30 respectively.
3829 - Separate the log message levels from the decision to drop guards,
3830 which also is available via torrc option PathBiasDropGuards.
3831 PathBiasDropGuards still defaults to 0 (off).
3832 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
3833 in combination with PathBiasExtremeRate.
3834 - Increase the default values for PathBiasScaleThreshold and
3835 PathBiasCircThreshold from (200, 20) to (300, 150).
3836 - Add in circuit usage accounting to path bias. If we try to use a
3837 built circuit but fail for any reason, it counts as path bias.
3838 Certain classes of circuits where the adversary gets to pick your
3839 destination node are exempt from this accounting. Usage accounting
3840 can be specifically disabled via consensus parameter or torrc.
3841 - Convert all internal path bias state to double-precision floating
3842 point, to avoid roundoff error and other issues.
3843 - Only record path bias information for circuits that have completed
3844 *two* hops. Assuming end-to-end tagging is the attack vector, this
3845 makes us more resilient to ambient circuit failure without any
3846 detection capability loss.
3848 o Minor bugfixes (log messages):
3849 - Rate-limit the "No circuits are opened. Relaxed timeout for a
3850 circuit with channel state open..." message to once per hour to
3851 keep it from filling the notice logs. Mitigates bug 7799 but does
3852 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
3853 - Avoid spurious warnings when configuring multiple client ports of
3854 which only some are nonlocal. Previously, we had claimed that some
3855 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
3858 o Code simplifications and refactoring:
3859 - Get rid of a couple of harmless clang warnings, where we compared
3860 enums to ints. These warnings are newly introduced in clang 3.2.
3861 - Split the onion.c file into separate modules for the onion queue
3862 and the different handshakes it supports.
3863 - Remove the marshalling/unmarshalling code for sending requests to
3864 cpuworkers over a socket, and instead just send structs. The
3865 recipient will always be the same Tor binary as the sender, so
3866 any encoding is overkill.
3869 Changes in version 0.2.4.7-alpha - 2012-12-24
3870 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
3871 directory mirrors for more robust bootstrapping; fixes more issues where
3872 clients with changing network conditions refuse to make any circuits;
3873 adds initial support for exiting to IPv6 addresses; resumes being able
3874 to update our GeoIP database, and includes the geoip6 file this time;
3875 turns off the client-side DNS cache by default due to privacy risks;
3876 and fixes a variety of other issues.
3878 o Major features (client resilience):
3879 - Add a new "FallbackDir" torrc option to use when we can't use
3880 a directory mirror from the consensus (either because we lack a
3881 consensus, or because they're all down). Currently, all authorities
3882 are fallbacks by default, and there are no other default fallbacks,
3883 but that will change. This option will allow us to give clients a
3884 longer list of servers to try to get a consensus from when first
3885 connecting to the Tor network, and thereby reduce load on the
3886 directory authorities. Implements proposal 206, "Preconfigured
3887 directory sources for bootstrapping". We also removed the old
3888 "FallbackNetworkstatus" option, since we never got it working well
3889 enough to use it. Closes bug 572.
3890 - If we have no circuits open, use a relaxed timeout (the
3891 95-percentile cutoff) until a circuit succeeds. This heuristic
3892 should allow Tor to succeed at building circuits even when the
3893 network connection drastically changes. Should help with bug 3443.
3895 o Major features (IPv6):
3896 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
3897 connectivity, then set the IPv6Exit flag to 1. Also make sure your
3898 exit policy reads as you would like: the address * applies to all
3899 address families, whereas *4 is IPv4 address only, and *6 is IPv6
3900 addresses only. On the client side, you'll need to wait until the
3901 authorities have upgraded, wait for enough exits to support IPv6,
3902 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
3903 ticket 5547, implements proposal 117 as revised in proposal 208.
3905 We DO NOT recommend that clients with actual anonymity needs start
3906 using IPv6 over Tor yet, since not enough exits support it yet.
3908 o Major features (geoip database):
3909 - Maxmind began labelling Tor relays as being in country "A1",
3910 which breaks by-country node selection inside Tor. Now we use a
3911 script to replace "A1" ("Anonymous Proxy") entries in our geoip
3912 file with real country codes. This script fixes about 90% of "A1"
3913 entries automatically and uses manual country code assignments to
3914 fix the remaining 10%. See src/config/README.geoip for details.
3915 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
3916 Country database, as modified above.
3918 o Major bugfixes (client-side DNS):
3919 - Turn off the client-side DNS cache by default. Updating and using
3920 the DNS cache is now configurable on a per-client-port
3921 level. SOCKSPort, DNSPort, etc lines may now contain
3922 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
3923 cache these types of DNS answers when we receive them from an
3924 exit node in response to an application request on this port, and
3925 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
3926 cached DNS answers of these types, we shouldn't use them. It's
3927 potentially risky to use cached DNS answers at the client, since
3928 doing so can indicate to one exit what answers we've gotten
3929 for DNS lookups in the past. With IPv6, this becomes especially
3930 problematic. Using cached DNS answers for requests on the same
3931 circuit would present less linkability risk, since all traffic
3932 on a circuit is already linkable, but it would also provide
3933 little performance benefit: the exit node caches DNS replies
3934 too. Implements a simplified version of Proposal 205. Implements
3937 o Major bugfixes (other):
3938 - Alter circuit build timeout measurement to start at the point
3939 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
3940 initialization). This should make our timeout measurements more
3941 uniform. Previously, we were sometimes including ORconn setup time
3942 in our circuit build time measurements. Should resolve bug 3443.
3943 - Fix an assertion that could trigger in hibernate_go_dormant() when
3944 closing an or_connection_t: call channel_mark_for_close() rather
3945 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
3947 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
3948 7655; bugfix on 0.2.4.6-alpha.
3951 - Add a new torrc option "ServerTransportListenAddr" to let bridge
3952 operators select the address where their pluggable transports will
3953 listen for connections. Resolves ticket 7013.
3954 - Allow an optional $ before the node identity digest in the
3955 controller command GETINFO ns/id/<identity>, for consistency with
3956 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
3957 - Log packaged cell fullness as part of the heartbeat message.
3958 Diagnosis to try to determine the extent of bug 7743.
3960 o Minor features (IPv6):
3961 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
3962 prefer to hand out virtual IPv6 addresses, since there are more of
3963 them and we can't run out. To override this behavior and make IPv4
3964 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
3965 or DNSPort you're using for resolving. Implements ticket 7571.
3966 - AutomapHostsOnResolve responses are now randomized, to avoid
3967 annoying situations where Tor is restarted and applications
3968 connect to the wrong addresses.
3969 - Never try more than 1000 times to pick a new virtual address when
3970 AutomapHostsOnResolve is set. That's good enough so long as we
3971 aren't close to handing out our entire virtual address space;
3972 if you're getting there, it's best to switch to IPv6 virtual
3976 - The ADDRMAP command can no longer generate an ill-formed error
3977 code on a failed MAPADDRESS. It now says "internal" rather than
3978 an English sentence fragment with spaces in the middle. Bugfix on
3980 - Fix log messages and comments to avoid saying "GMT" when we mean
3981 "UTC". Fixes bug 6113.
3982 - Compile on win64 using mingw64. Fixes bug 7260; patches from
3984 - Fix a crash when debugging unit tests on Windows: deallocate a
3985 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
3986 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
3989 - The DirServer option is now DirAuthority, for consistency with
3990 current naming patterns. You can still use the old DirServer form.
3992 o Code simplification and refactoring:
3993 - Move the client-side address-map/virtual-address/DNS-cache code
3994 out of connection_edge.c into a new addressmap.c module.
3995 - Remove unused code for parsing v1 directories and "running routers"
3996 documents. Fixes bug 6887.
3999 Changes in version 0.2.3.25 - 2012-11-19
4000 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
4001 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
4002 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
4003 programmer, and friend. Unstinting in his dedication to the cause of
4004 freedom, he inspired and helped many of us as we began our work on
4005 anonymity, and inspires us still. Please honor his memory by writing
4006 software to protect people's freedoms, and by helping others to do so.
4008 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
4009 significantly reduced directory overhead (via microdescriptors),
4010 enormous crypto performance improvements for fast relays on new
4011 enough hardware, a new v3 TLS handshake protocol that can better
4012 resist fingerprinting, support for protocol obfuscation plugins (aka
4013 pluggable transports), better scalability for hidden services, IPv6
4014 support for bridges, performance improvements like allowing clients
4015 to skip the first round-trip on the circuit ("optimistic data") and
4016 refilling token buckets more often, a new "stream isolation" design
4017 to isolate different applications on different circuits, and many
4018 stability, security, and privacy fixes.
4021 - Tor tries to wipe potentially sensitive data after using it, so
4022 that if some subsequent security failure exposes Tor's memory,
4023 the damage will be limited. But we had a bug where the compiler
4024 was eliminating these wipe operations when it decided that the
4025 memory was no longer visible to a (correctly running) program,
4026 hence defeating our attempt at defense in depth. We fix that
4027 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
4028 is unlikely to optimize away. Future versions of Tor may use
4029 a less ridiculously heavy approach for this. Fixes bug 7352.
4030 Reported in an article by Andrey Karpov.
4033 - Fix a harmless bug when opting against publishing a relay descriptor
4034 because DisableNetwork is set. Fixes bug 7464; bugfix on
4038 Changes in version 0.2.4.6-alpha - 2012-11-13
4039 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
4040 makes our defense-in-depth memory wiping more reliable, and begins to
4041 count IPv6 addresses in bridge statistics,
4044 - Fix an assertion failure that could occur when closing a connection
4045 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
4047 - Tor tries to wipe potentially sensitive data after using it, so
4048 that if some subsequent security failure exposes Tor's memory,
4049 the damage will be limited. But we had a bug where the compiler
4050 was eliminating these wipe operations when it decided that the
4051 memory was no longer visible to a (correctly running) program,
4052 hence defeating our attempt at defense in depth. We fix that
4053 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
4054 is unlikely to optimize away. Future versions of Tor may use
4055 a less ridiculously heavy approach for this. Fixes bug 7352.
4056 Reported in an article by Andrey Karpov.
4059 - Add GeoIP database for IPv6 addresses. The new config option
4061 - Bridge statistics now count bridge clients connecting over IPv6:
4062 bridge statistics files now list "bridge-ip-versions" and
4063 extra-info documents list "geoip6-db-digest". The control protocol
4064 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
4065 implementation by "shkoo", addressing ticket 5055.
4068 - Warn when we are binding low ports when hibernation is enabled;
4069 previously we had warned when we were _advertising_ low ports with
4070 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
4071 - Fix a harmless bug when opting against publishing a relay descriptor
4072 because DisableNetwork is set. Fixes bug 7464; bugfix on
4074 - Add warning message when a managed proxy dies during configuration.
4075 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
4076 - Fix a linking error when building tor-fw-helper without miniupnp.
4077 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
4078 - Check for closing an or_connection_t without going through correct
4079 channel functions; emit a warning and then call
4080 connection_or_close_for_error() so we don't assert as in bugs 7212
4082 - Compile correctly on compilers without C99 designated initializer
4083 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
4084 - Avoid a possible assert that can occur when channel_send_destroy() is
4085 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
4086 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
4087 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
4088 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
4089 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
4091 o Code simplification and refactoring:
4092 - Start using OpenBSD's implementation of queue.h, so that we don't
4093 need to hand-roll our own pointer and list structures whenever we
4094 need them. (We can't rely on a sys/queue.h, since some operating
4095 systems don't have them, and the ones that do have them don't all
4096 present the same extensions.)
4099 Changes in version 0.2.4.5-alpha - 2012-10-25
4100 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
4101 two important security vulnerabilities that could lead to remotely
4102 triggerable relay crashes, fix a major bug that was preventing clients
4103 from choosing suitable exit nodes, and refactor some of our code.
4105 o Major bugfixes (security, also in 0.2.3.24-rc):
4106 - Fix a group of remotely triggerable assertion failures related to
4107 incorrect link protocol negotiation. Found, diagnosed, and fixed
4108 by "some guy from France". Fix for CVE-2012-2250; bugfix on
4110 - Fix a denial of service attack by which any directory authority
4111 could crash all the others, or by which a single v2 directory
4112 authority could crash everybody downloading v2 directory
4113 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
4115 o Major bugfixes (also in 0.2.3.24-rc):
4116 - When parsing exit policy summaries from microdescriptors, we had
4117 previously been ignoring the last character in each one, so that
4118 "accept 80,443,8080" would be treated by clients as indicating
4119 a node that allows access to ports 80, 443, and 808. That would
4120 lead to clients attempting connections that could never work,
4121 and ignoring exit nodes that would support their connections. Now
4122 clients parse these exit policy summaries correctly. Fixes bug 7192;
4123 bugfix on 0.2.3.1-alpha.
4125 o Minor bugfixes (also in 0.2.3.24-rc):
4126 - Clients now consider the ClientRejectInternalAddresses config option
4127 when using a microdescriptor consensus stanza to decide whether
4128 an exit relay would allow exiting to an internal address. Fixes
4129 bug 7190; bugfix on 0.2.3.1-alpha.
4132 - Only disable TLS session ticket support when running as a TLS
4133 server. Now clients will blend better with regular Firefox
4134 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
4136 o Code simplification and refactoring:
4137 - Start using OpenBSD's implementation of queue.h (originally by
4139 - Move the entry node code from circuitbuild.c to its own file.
4140 - Move the circuit build timeout tracking code from circuitbuild.c
4144 Changes in version 0.2.3.24-rc - 2012-10-25
4145 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
4146 could lead to remotely triggerable relay crashes, and fixes
4147 a major bug that was preventing clients from choosing suitable exit
4150 o Major bugfixes (security):
4151 - Fix a group of remotely triggerable assertion failures related to
4152 incorrect link protocol negotiation. Found, diagnosed, and fixed
4153 by "some guy from France". Fix for CVE-2012-2250; bugfix on
4155 - Fix a denial of service attack by which any directory authority
4156 could crash all the others, or by which a single v2 directory
4157 authority could crash everybody downloading v2 directory
4158 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
4161 - When parsing exit policy summaries from microdescriptors, we had
4162 previously been ignoring the last character in each one, so that
4163 "accept 80,443,8080" would be treated by clients as indicating
4164 a node that allows access to ports 80, 443, and 808. That would
4165 lead to clients attempting connections that could never work,
4166 and ignoring exit nodes that would support their connections. Now
4167 clients parse these exit policy summaries correctly. Fixes bug 7192;
4168 bugfix on 0.2.3.1-alpha.
4171 - Clients now consider the ClientRejectInternalAddresses config option
4172 when using a microdescriptor consensus stanza to decide whether
4173 an exit relay would allow exiting to an internal address. Fixes
4174 bug 7190; bugfix on 0.2.3.1-alpha.
4177 Changes in version 0.2.4.4-alpha - 2012-10-20
4178 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
4179 vulnerability introduced by a change in OpenSSL, fixes a remotely
4180 triggerable assert, and adds new channel_t and circuitmux_t abstractions
4181 that will make it easier to test new connection transport and cell
4182 scheduling algorithms.
4184 o New directory authorities (also in 0.2.3.23-rc):
4185 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
4186 authority. Closes ticket 5749.
4188 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
4189 - Disable TLS session tickets. OpenSSL's implementation was giving
4190 our TLS session keys the lifetime of our TLS context objects, when
4191 perfect forward secrecy would want us to discard anything that
4192 could decrypt a link connection as soon as the link connection
4193 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
4194 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
4195 - Discard extraneous renegotiation attempts once the V3 link
4196 protocol has been initiated. Failure to do so left us open to
4197 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
4198 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
4200 o Internal abstraction features:
4201 - Introduce new channel_t abstraction between circuits and
4202 or_connection_t to allow for implementing alternate OR-to-OR
4203 transports. A channel_t is an abstract object which can either be a
4204 cell-bearing channel, which is responsible for authenticating and
4205 handshaking with the remote OR and transmitting cells to and from
4206 it, or a listening channel, which spawns new cell-bearing channels
4207 at the request of remote ORs. Implements part of ticket 6465.
4208 - Also new is the channel_tls_t subclass of channel_t, adapting it
4209 to the existing or_connection_t code. The V2/V3 protocol handshaking
4210 code which formerly resided in command.c has been moved below the
4211 channel_t abstraction layer and may be found in channeltls.c now.
4212 Implements the rest of ticket 6465.
4213 - Introduce new circuitmux_t storing the queue of circuits for
4214 a channel; this encapsulates and abstracts the queue logic and
4215 circuit selection policy, and allows the latter to be overridden
4216 easily by switching out a policy object. The existing EWMA behavior
4217 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
4219 o Required libraries:
4220 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
4221 strongly recommended.
4224 - Warn users who run hidden services on a Tor client with
4225 UseEntryGuards disabled that their hidden services will be
4226 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
4227 attack which motivated Tor to support entry guards in the first
4228 place). Resolves ticket 6889.
4229 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
4230 dhill. Resolves ticket 6982.
4231 - Option OutboundBindAddress can be specified multiple times and
4232 accepts IPv6 addresses. Resolves ticket 6876.
4234 o Minor bugfixes (also in 0.2.3.23-rc):
4235 - Don't serve or accept v2 hidden service descriptors over a
4236 relay's DirPort. It's never correct to do so, and disabling it
4237 might make it more annoying to exploit any bugs that turn up in the
4238 descriptor-parsing code. Fixes bug 7149.
4239 - Fix two cases in src/or/transports.c where we were calling
4240 fmt_addr() twice in a parameter list. Bug found by David
4241 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
4242 - Fix memory leaks whenever we logged any message about the "path
4243 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
4244 - When relays refuse a "create" cell because their queue of pending
4245 create cells is too big (typically because their cpu can't keep up
4246 with the arrival rate), send back reason "resource limit" rather
4247 than reason "internal", so network measurement scripts can get a
4248 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
4251 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
4252 - Free some more still-in-use memory at exit, to make hunting for
4253 memory leaks easier. Resolves bug 7029.
4254 - When a Tor client gets a "truncated" relay cell, the first byte of
4255 its payload specifies why the circuit was truncated. We were
4256 ignoring this 'reason' byte when tearing down the circuit, resulting
4257 in the controller not being told why the circuit closed. Now we
4258 pass the reason from the truncated cell to the controller. Bugfix
4259 on 0.1.2.3-alpha; fixes bug 7039.
4260 - Downgrade "Failed to hand off onionskin" messages to "debug"
4261 severity, since they're typically redundant with the "Your computer
4262 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
4263 - Make clients running with IPv6 bridges connect over IPv6 again,
4264 even without setting new config options ClientUseIPv6 and
4265 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
4266 - Use square brackets around IPv6 addresses in numerous places
4267 that needed them, including log messages, HTTPS CONNECT proxy
4268 requests, TransportProxy statefile entries, and pluggable transport
4269 extra-info lines. Fixes bug 7011; patch by David Fifield.
4271 o Code refactoring and cleanup:
4272 - Source files taken from other packages now reside in src/ext;
4273 previously they were scattered around the rest of Tor.
4274 - Avoid use of reserved identifiers in our C code. The C standard
4275 doesn't like us declaring anything that starts with an
4276 underscore, so let's knock it off before we get in trouble. Fix
4277 for bug 1031; bugfix on the first Tor commit.
4280 Changes in version 0.2.3.23-rc - 2012-10-20
4281 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
4282 vulnerability introduced by a change in OpenSSL, and fixes a variety
4283 of smaller bugs in preparation for the release.
4285 o New directory authorities:
4286 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
4287 authority. Closes ticket 5749.
4289 o Major bugfixes (security/privacy):
4290 - Disable TLS session tickets. OpenSSL's implementation was giving
4291 our TLS session keys the lifetime of our TLS context objects, when
4292 perfect forward secrecy would want us to discard anything that
4293 could decrypt a link connection as soon as the link connection
4294 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
4295 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
4296 - Discard extraneous renegotiation attempts once the V3 link
4297 protocol has been initiated. Failure to do so left us open to
4298 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
4299 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
4302 - Fix a possible crash bug when checking for deactivated circuits
4303 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
4304 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
4306 o Minor bugfixes (on 0.2.3.x):
4307 - Fix two cases in src/or/transports.c where we were calling
4308 fmt_addr() twice in a parameter list. Bug found by David
4309 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
4310 - Convert an assert in the pathbias code to a log message. The assert
4311 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
4312 bugfix on 0.2.3.17-beta.
4313 - Fix memory leaks whenever we logged any message about the "path
4314 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
4316 o Minor bugfixes (on 0.2.2.x and earlier):
4317 - Don't serve or accept v2 hidden service descriptors over a relay's
4318 DirPort. It's never correct to do so, and disabling it might
4319 make it more annoying to exploit any bugs that turn up in the
4320 descriptor-parsing code. Fixes bug 7149.
4321 - When relays refuse a "create" cell because their queue of pending
4322 create cells is too big (typically because their cpu can't keep up
4323 with the arrival rate), send back reason "resource limit" rather
4324 than reason "internal", so network measurement scripts can get a
4325 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
4326 - Correct file sizes when reading binary files on Cygwin, to avoid
4327 a bug where Tor would fail to read its state file. Fixes bug 6844;
4328 bugfix on 0.1.2.7-alpha.
4329 - Avoid undefined behavior when parsing the list of supported
4330 rendezvous/introduction protocols in a hidden service descriptor.
4331 Previously, Tor would have confused (as-yet-unused) protocol version
4332 numbers greater than 32 with lower ones on many platforms. Fixes
4333 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
4335 o Documentation fixes:
4336 - Clarify that hidden services are TCP only. Fixes bug 6024.
4339 Changes in version 0.2.4.3-alpha - 2012-09-22
4340 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
4341 assertion, resumes letting relays test reachability of their DirPort,
4342 and cleans up a bunch of smaller bugs.
4345 - Fix an assertion failure in tor_timegm() that could be triggered
4346 by a badly formatted directory object. Bug found by fuzzing with
4347 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
4350 - Fix a possible crash bug when checking for deactivated circuits
4351 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
4352 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
4353 - Allow routers to detect that their own DirPorts are running. When
4354 we removed support for versions_supports_begindir, we also
4355 accidentally removed the mechanism we used to self-test our
4356 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
4357 bugfix on 0.2.4.2-alpha.
4359 o Security features:
4360 - Switch to a completely time-invariant approach for picking nodes
4361 weighted by bandwidth. Our old approach would run through the
4362 part of the loop after it had made its choice slightly slower
4363 than it ran through the part of the loop before it had made its
4364 choice. Addresses ticket 6538.
4365 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
4366 by tor2web clients allows hidden services to identify tor2web
4367 clients through their repeated selection of the same rendezvous
4368 and introduction point circuit endpoints (their guards). Resolves
4372 - Enable Tor to read configuration, state, and key information from
4373 a FIFO. Previously Tor would only read from files with a positive
4374 stat.st_size. Code from meejah; fixes bug 6044.
4377 - Correct file sizes when reading binary files on Cygwin, to avoid
4378 a bug where Tor would fail to read its state file. Fixes bug 6844;
4379 bugfix on 0.1.2.7-alpha.
4380 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
4381 bugfix on 0.2.0.3-alpha.
4382 - When complaining about a client port on a public address, log
4383 which address we're complaining about. Fixes bug 4020; bugfix on
4384 0.2.3.3-alpha. Patch by Tom Fitzhenry.
4385 - Convert an assert in the pathbias code to a log message. The assert
4386 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
4387 bugfix on 0.2.3.17-beta.
4388 - Our new buildsystem was overzealous about rebuilding manpages: it
4389 would rebuild them all whenever any one of them changed. Now our
4390 dependency checking should be correct. Fixes bug 6843; bugfix on
4392 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
4393 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
4394 - Correct log printout about which address family is preferred
4395 when connecting to a bridge with both an IPv4 and IPv6 OR port.
4396 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
4398 o Minor bugfixes (code cleanliness):
4399 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
4400 with large values. This situation was untriggered, but nevertheless
4401 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
4402 - Reject consensus votes with more than 64 known-flags. We aren't even
4403 close to that limit yet, and our code doesn't handle it correctly.
4404 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
4405 - Avoid undefined behavior when parsing the list of supported
4406 rendezvous/introduction protocols in a hidden service descriptor.
4407 Previously, Tor would have confused (as-yet-unused) protocol version
4408 numbers greater than 32 with lower ones on many platforms. Fixes
4409 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
4410 - Fix handling of rendezvous client authorization types over 8.
4411 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
4412 - Fix building with older versions of GCC (2.95, for one) that don't
4413 like preprocessor directives inside macro arguments. Found by
4414 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
4415 - Switch weighted node selection rule from using a list of doubles
4416 to using a list of int64_t. This change should make the process
4417 slightly easier to debug and maintain. Needed to finish ticket 6538.
4419 o Code simplification and refactoring:
4420 - Move the generic "config" code into a new file, and have "config.c"
4421 hold only torrc- and state-related code. Resolves ticket 6823.
4422 - Move the core of our "choose a weighted element at random" logic
4423 into its own function, and give it unit tests. Now the logic is
4424 testable, and a little less fragile too.
4425 - Removed the testing_since field of node_t, which hasn't been used
4426 for anything since 0.2.0.9-alpha.
4428 o Documentation fixes:
4429 - Clarify that hidden services are TCP only. Fixes bug 6024.
4430 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
4434 Changes in version 0.2.3.22-rc - 2012-09-11
4435 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
4439 - Fix an assertion failure in tor_timegm() that could be triggered
4440 by a badly formatted directory object. Bug found by fuzzing with
4441 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
4444 - Avoid segfault when starting up having run with an extremely old
4445 version of Tor and parsing its state file. Fixes bug 6801; bugfix
4449 Changes in version 0.2.2.39 - 2012-09-11
4450 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
4454 - Fix an assertion failure in tor_timegm() that could be triggered
4455 by a badly formatted directory object. Bug found by fuzzing with
4456 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
4457 - Do not crash when comparing an address with port value 0 to an
4458 address policy. This bug could have been used to cause a remote
4459 assertion failure by or against directory authorities, or to
4460 allow some applications to crash clients. Fixes bug 6690; bugfix
4464 Changes in version 0.2.4.2-alpha - 2012-09-10
4465 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
4466 raises the default rate limiting even more, and makes the bootstrapping
4467 log messages less noisy.
4470 - Automatically forward the TCP ports of pluggable transport
4471 proxies using tor-fw-helper if PortForwarding is enabled. Implements
4475 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
4476 to 1GB/1GB. The previous defaults were intended to be "basically
4477 infinite", but it turns out they're now limiting our 100mbit+
4478 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
4479 last time we raised it).
4482 - Detect when we're running with a version of OpenSSL other than the
4483 one we compiled with. This has occasionally given people hard-to-
4485 - Log fewer lines at level "notice" about our OpenSSL and Libevent
4486 versions and capabilities when everything is going right. Resolves
4487 part of ticket 6736.
4488 - Directory authorities no long accept descriptors for any version of
4489 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
4490 These versions are insecure, unsupported, or both. Implements
4494 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
4495 to start with a triple-underscore so the controller won't touch it.
4496 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
4497 - Avoid segfault when starting up having run with an extremely old
4498 version of Tor and parsing its state file. Fixes bug 6801; bugfix
4500 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
4501 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
4502 - Don't follow the NULL pointer if microdescriptor generation fails.
4503 (This does not appear to be triggerable, but it's best to be safe.)
4504 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
4505 - Fix mis-declared dependencies on src/common/crypto.c and
4506 src/or/tor_main.c that could break out-of-tree builds under some
4507 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
4508 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
4509 6778; bugfix on 0.2.4.1-alpha.
4510 - Fix a harmless (in this case) build warning for implicitly
4511 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
4514 - Now that all versions before 0.2.2.x are disallowed, we no longer
4515 need to work around their missing features. Thus we can remove a
4516 bunch of compatibility code.
4519 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
4520 TCP ports to forward. In the past it only accepted two ports:
4521 the ORPort and the DirPort.
4524 Changes in version 0.2.4.1-alpha - 2012-09-05
4525 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
4526 bridgedb; lets relays use IPv6 addresses and directory authorities
4527 advertise them; and switches to a cleaner build interface.
4529 This is the first alpha release in a new series, so expect there to
4530 be bugs. Users who would rather test out a more stable branch should
4531 stay with 0.2.3.x for now.
4533 o Major features (bridges):
4534 - Bridges now report the pluggable transports they support to the
4535 bridge authority, so it can pass the supported transports on to
4536 bridgedb and/or eventually do reachability testing. Implements
4539 o Major features (IPv6):
4540 - Bridge authorities now accept IPv6 bridge addresses and include
4541 them in network status documents. Implements ticket 5534.
4542 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
4543 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
4544 to happen. Implements ticket 5535.
4545 - All kind of relays, not just bridges, can now advertise an IPv6
4546 OR port. Implements ticket 6362.
4547 - Directory authorities vote on IPv6 OR ports using the new consensus
4548 method 14. Implements ticket 6363.
4550 o Major features (build):
4551 - Switch to a nonrecursive Makefile structure. Now instead of each
4552 Makefile.am invoking other Makefile.am's, there is a master
4553 Makefile.am that includes the others. This change makes our build
4554 process slightly more maintainable, and improves parallelism for
4555 building with make -j. Original patch by Stewart Smith; various
4556 fixes by Jim Meyering.
4557 - Where available, we now use automake's "silent" make rules by
4558 default, so that warnings are easier to spot. You can get the old
4559 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
4561 o Minor features (code security and spec conformance):
4562 - Clear keys and key-derived material left on the stack in
4563 rendservice.c and rendclient.c. Check return value of
4564 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
4565 These fixes should make us more forward-secure against cold-boot
4566 attacks and the like. Fixes bug 2385.
4567 - Reject EXTEND cells sent to nonexistent streams. According to the
4568 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
4569 we were only checking for stream IDs that were currently in use.
4570 Found while hunting for more instances of bug 6271. Bugfix on
4571 0.0.2pre8, which introduced incremental circuit construction.
4573 o Minor features (streamlining);
4574 - No longer include the "opt" prefix when generating routerinfos
4575 or v2 directories: it has been needless since Tor 0.1.2. Closes
4577 - Remove some now-needless code that tried to aggressively flush
4578 OR connections as data was added to them. Since 0.2.0.1-alpha, our
4579 cell queue logic has saved us from the failure mode that this code
4580 was supposed to prevent. Removing this code will limit the number
4581 of baroque control flow paths through Tor's network logic. Reported
4582 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
4584 o Minor features (controller):
4585 - Add a "GETINFO signal/names" control port command. Implements
4587 - Provide default values for all options via "GETINFO config/defaults".
4588 Implements ticket 4971.
4590 o Minor features (IPv6):
4591 - New config option "AuthDirHasIPv6Connectivity 1" that directory
4592 authorities should set if they have IPv6 connectivity and want to
4593 do reachability tests for IPv6 relays. Implements feature 5974.
4594 - A relay with an IPv6 OR port now sends that address in NETINFO
4595 cells (in addition to its other address). Implements ticket 6364.
4597 o Minor features (log messages):
4598 - Omit the first heartbeat log message, because it never has anything
4599 useful to say, and it clutters up the bootstrapping messages.
4600 Resolves ticket 6758.
4601 - Don't log about reloading the microdescriptor cache at startup. Our
4602 bootstrap warnings are supposed to tell the user when there's a
4603 problem, and our bootstrap notices say when there isn't. Resolves
4604 ticket 6759; bugfix on 0.2.2.6-alpha.
4605 - Don't log "I learned some more directory information" when we're
4606 reading cached directory information. Reserve it for when new
4607 directory information arrives in response to a fetch. Resolves
4609 - Prevent rounding error in path bias counts when scaling
4610 them down, and use the correct scale factor default. Also demote
4611 some path bias related log messages down a level and make others
4612 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
4613 - We no longer warn so much when generating manpages from their
4616 o Code simplifications and refactoring:
4617 - Enhance our internal sscanf replacement so that we can eliminate
4618 the last remaining uses of the system sscanf. (Though those uses
4619 of sscanf were safe, sscanf itself is generally error prone, so
4620 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
4622 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
4623 - Move last_reachable and testing_since from routerinfo_t to node_t.
4624 Implements ticket 5529.
4625 - Add replaycache_t structure, functions and unit tests, then refactor
4626 rend_service_introduce() to be more clear to read, improve, debug,
4627 and test. Resolves bug 6177.
4628 - Finally remove support for malloc_good_size and malloc_usable_size.
4629 We had hoped that these functions would let us eke a little more
4630 memory out of our malloc implementation. Unfortunately, the only
4631 implementations that provided these functions are also ones that
4632 are already efficient about not overallocation: they never got us
4633 more than 7 or so bytes per allocation. Removing them saves us a
4634 little code complexity and a nontrivial amount of build complexity.
4637 - Tor maintainers now require Automake version 1.9 or later to build
4638 Tor from the Git repository. (Automake is not required when building
4639 from a source distribution.)
4642 Changes in version 0.2.3.21-rc - 2012-09-05
4643 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
4644 series. It fixes a trio of potential security bugs, fixes a bug where
4645 we were leaving some of the fast relays out of the microdescriptor
4646 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
4647 and cleans up other smaller issues.
4649 o Major bugfixes (security):
4650 - Tear down the circuit if we get an unexpected SENDME cell. Clients
4651 could use this trick to make their circuits receive cells faster
4652 than our flow control would have allowed, or to gum up the network,
4653 or possibly to do targeted memory denial-of-service attacks on
4654 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
4655 from July 2002, before the release of Tor 0.0.0. We had committed
4656 this patch previously, but we had to revert it because of bug 6271.
4657 Now that 6271 is fixed, this patch appears to work.
4658 - Reject any attempt to extend to an internal address. Without
4659 this fix, a router could be used to probe addresses on an internal
4660 network to see whether they were accepting connections. Fixes bug
4661 6710; bugfix on 0.0.8pre1.
4662 - Do not crash when comparing an address with port value 0 to an
4663 address policy. This bug could have been used to cause a remote
4664 assertion failure by or against directory authorities, or to
4665 allow some applications to crash clients. Fixes bug 6690; bugfix
4669 - Remove the upper bound on microdescriptor length. We were hitting
4670 the limit for routers with complex exit policies or family
4671 declarations, causing clients to not use them. Fixes the first
4672 piece of bug 6404; fix on 0.2.2.6-alpha.
4673 - Detect "ORPort 0" as meaning, uniformly, that we're not running
4674 as a relay. Previously, some of our code would treat the presence
4675 of any ORPort line as meaning that we should act like a relay,
4676 even though our new listener code would correctly not open any
4677 ORPorts for ORPort 0. Similar bugs in other Port options are also
4678 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
4681 - Avoid a pair of double-free and use-after-mark bugs that can
4682 occur with certain timings in canceled and re-received DNS
4683 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
4684 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
4685 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
4686 - Allow one-hop directory fetching circuits the full "circuit build
4687 timeout" period, rather than just half of it, before failing them
4688 and marking the relay down. This fix should help reduce cases where
4689 clients declare relays (or worse, bridges) unreachable because
4690 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
4691 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
4693 - Authorities no longer include any router in their microdescriptor
4694 consensuses for which they couldn't generate or agree on a
4695 microdescriptor. Fixes the second piece of bug 6404; fix on
4697 - Detect and reject attempts to specify both "FooPort" and
4698 "FooPort 0" in the same configuration domain. (It's still okay
4699 to have a FooPort in your configuration file, and use "FooPort 0"
4700 on the command line to disable it.) Fixes the second half of bug
4701 6507; bugfix on 0.2.3.3-alpha.
4702 - Make wildcarded addresses (that is, ones beginning with "*.") work
4703 when provided via the controller's MapAddress command. Previously,
4704 they were accepted, but we never actually noticed that they were
4705 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
4706 - Avoid crashing on a malformed state file where EntryGuardPathBias
4707 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
4708 - Add a (probably redundant) memory clear between iterations of
4709 the router status voting loop, to prevent future coding errors
4710 where data might leak between iterations of the loop. Resolves
4713 o Minor bugfixes (log messages):
4714 - Downgrade "set buildtimeout to low value" messages to "info"
4715 severity; they were never an actual problem, there was never
4716 anything reasonable to do about them, and they tended to spam logs
4717 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
4718 - Downgrade path-bias warning messages to "info". We'll try to get
4719 them working better in 0.2.4. Add internal circuit construction
4720 state to protect against the noisy warn message "Unexpectedly high
4721 circuit_successes". Also add some additional rate-limited notice
4722 messages to help determine the root cause of the warn. Fixes bug
4723 6475. Bugfix against 0.2.3.17-beta.
4724 - Move log message when unable to find a microdesc in a routerstatus
4725 entry to parse time. Previously we'd spam this warning every time
4726 we tried to figure out which microdescriptors to download. Fixes
4727 the third piece of bug 6404; fix on 0.2.3.18-rc.
4730 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
4731 change when the authority is deciding whether to accept a newly
4732 uploaded descriptor. Implements ticket 6423.
4733 - Add missing documentation for consensus and microdesc files.
4734 Resolves ticket 6732.
4737 Changes in version 0.2.2.38 - 2012-08-12
4738 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
4739 attack that could in theory leak path information.
4742 - Avoid an uninitialized memory read when reading a vote or consensus
4743 document that has an unrecognized flavor name. This read could
4744 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
4745 - Try to leak less information about what relays a client is
4746 choosing to a side-channel attacker. Previously, a Tor client would
4747 stop iterating through the list of available relays as soon as it
4748 had chosen one, thus finishing a little earlier when it picked
4749 a router earlier in the list. If an attacker can recover this
4750 timing information (nontrivial but not proven to be impossible),
4751 they could learn some coarse-grained information about which relays
4752 a client was picking (middle nodes in particular are likelier to
4753 be affected than exits). The timing attack might be mitigated by
4754 other factors (see bug 6537 for some discussion), but it's best
4755 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
4758 Changes in version 0.2.3.20-rc - 2012-08-05
4759 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
4760 series. It fixes a pair of code security bugs and a potential anonymity
4761 issue, updates our RPM spec files, and cleans up other smaller issues.
4764 - Avoid read-from-freed-memory and double-free bugs that could occur
4765 when a DNS request fails while launching it. Fixes bug 6480;
4766 bugfix on 0.2.0.1-alpha.
4767 - Avoid an uninitialized memory read when reading a vote or consensus
4768 document that has an unrecognized flavor name. This read could
4769 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
4770 - Try to leak less information about what relays a client is
4771 choosing to a side-channel attacker. Previously, a Tor client would
4772 stop iterating through the list of available relays as soon as it
4773 had chosen one, thus finishing a little earlier when it picked
4774 a router earlier in the list. If an attacker can recover this
4775 timing information (nontrivial but not proven to be impossible),
4776 they could learn some coarse-grained information about which relays
4777 a client was picking (middle nodes in particular are likelier to
4778 be affected than exits). The timing attack might be mitigated by
4779 other factors (see bug 6537 for some discussion), but it's best
4780 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
4783 - Try to make the warning when giving an obsolete SOCKSListenAddress
4784 a little more useful.
4785 - Terminate active server managed proxies if Tor stops being a
4786 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
4787 - Provide a better error message about possible OSX Asciidoc failure
4788 reasons. Fixes bug 6436.
4789 - Warn when Tor is configured to use accounting in a way that can
4790 link a hidden service to some other hidden service or public
4791 address. Resolves ticket 6490.
4794 - Check return value of fputs() when writing authority certificate
4795 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
4796 - Ignore ServerTransportPlugin lines when Tor is not configured as
4797 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
4798 - When disabling guards for having too high a proportion of failed
4799 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
4803 - Update our default RPM spec files to work with mock and rpmbuild
4804 on RHEL/Fedora. They have an updated set of dependencies and
4805 conflicts, a fix for an ancient typo when creating the "_tor"
4806 user, and better instructions. Thanks to Ondrej Mikle for the
4807 patch series. Fixes bug 6043.
4810 - Make it possible to set the TestingTorNetwork configuration
4811 option using AlternateDirAuthority and AlternateBridgeAuthority
4812 as an alternative to setting DirServer. Addresses ticket 6377.
4815 - Clarify the documentation for the Alternate*Authority options.
4817 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
4819 o Code simplification and refactoring:
4820 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
4821 10 lines. Also, don't nest them. Doing so in the past has
4822 led to hard-to-debug code. The new style is to use the
4823 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
4826 Changes in version 0.2.3.19-rc - 2012-07-06
4827 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
4828 series. It fixes the compile on Windows, reverts to a GeoIP database
4829 that isn't as broken, and fixes a flow control bug that has been around
4830 since the beginning of Tor.
4833 - Fix a bug handling SENDME cells on nonexistent streams that could
4834 result in bizarre window values. Report and patch contributed
4835 pseudonymously. Fixes part of bug 6271. This bug was introduced
4836 before the first Tor release, in svn commit r152.
4837 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
4838 June 2012 database, Maxmind marked many Tor relays as country "A1",
4839 which will cause risky behavior for clients that set EntryNodes
4840 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
4841 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
4842 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
4845 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
4846 bugfix on 0.2.1.10-alpha.
4849 Changes in version 0.2.3.18-rc - 2012-06-28
4850 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
4851 series. It fixes a few smaller bugs, but generally appears stable.
4852 Please test it and let us know whether it is!
4855 - Allow wildcarded mapaddress targets to be specified on the
4856 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
4857 - Make our linker option detection code more robust against linkers
4858 such as on FreeBSD 8, where a bad combination of options completes
4859 successfully but makes an unrunnable binary. Fixes bug 6173;
4860 bugfix on 0.2.3.17-beta.
4862 o Minor bugfixes (on 0.2.2.x and earlier):
4863 - Avoid a false positive in the util/threads unit test by increasing
4864 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
4865 - Replace "Sending publish request" log messages with "Launching
4866 upload", so that they no longer confusingly imply that we're
4867 sending something to a directory we might not even be connected
4868 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
4869 - Make sure to set *socket_error in all error cases in
4870 connection_connect(), so it can't produce a warning about
4871 errno being zero from errno_to_orconn_end_reason(). Bugfix on
4872 0.2.1.1-alpha; resolves ticket 6028.
4873 - Downgrade "Got a certificate, but we already have it" log messages
4874 from warning to info, except when we're a dirauth. Fixes bug 5238;
4875 bugfix on 0.2.1.7-alpha.
4876 - When checking for requested signatures on the latest consensus
4877 before serving it to a client, make sure to check the right
4878 consensus flavor. Bugfix on 0.2.2.6-alpha.
4879 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
4880 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
4882 o Minor bugfixes (on 0.2.3.x):
4883 - Make format_helper_exit_status() avoid unnecessary space padding
4884 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
4886 - Downgrade a message about cleaning the microdescriptor cache to
4887 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
4888 - Log a BUG message at severity INFO if we have a networkstatus with
4889 a missing entry for some microdescriptor. Continues on a patch
4891 - Improve the log message when a managed proxy fails to launch. Fixes
4892 bug 5099; bugfix on 0.2.3.6-alpha.
4893 - Don't do DNS lookups when parsing corrupted managed proxy protocol
4894 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
4895 - When formatting wildcarded address mappings for the controller,
4896 be sure to include "*." as appropriate. Partially fixes bug 6244;
4897 bugfix on 0.2.3.9-alpha.
4898 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
4899 Bugfix on 0.2.3.13-alpha.
4900 - Stop logging messages about running with circuit timeout learning
4901 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
4902 - Disable a spurious warning about reading on a marked and flushing
4903 connection. We shouldn't be doing that, but apparently we
4904 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
4905 - Fix a bug that stopped AllowDotExit from working on addresses
4906 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
4909 o Code simplification, refactoring, unit tests:
4910 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
4911 Libevent's notion of cached time when possible.
4912 - Remove duplicate code for invoking getrlimit() from control.c.
4913 - Add a unit test for the environment_variable_names_equal function.
4916 - Document the --defaults-torrc option, and the new (in 0.2.3)
4917 semantics for overriding, extending, and clearing lists of
4918 options. Closes bug 4748.
4921 Changes in version 0.2.3.17-beta - 2012-06-15
4922 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
4923 gets our TLS handshake back on track for being able to blend in with
4924 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
4925 with Vidalia, and otherwise continues to get us closer to a release
4929 - Enable gcc and ld hardening by default. Resolves ticket 5210.
4930 - Update TLS cipher list to match Firefox 8 and later. Resolves
4932 - Implement the client side of proposal 198: remove support for
4933 clients falsely claiming to support standard ciphersuites that
4934 they can actually provide. As of modern OpenSSL versions, it's not
4935 necessary to fake any standard ciphersuite, and doing so prevents
4936 us from using better ciphersuites in the future, since servers
4937 can't know whether an advertised ciphersuite is really supported or
4938 not. Some hosts -- notably, ones with very old versions of OpenSSL
4939 or where OpenSSL has been built with ECC disabled -- will stand
4940 out because of this change; TBB users should not be affected.
4943 - Change the default value for DynamicDHGroups (introduced in
4944 0.2.3.9-alpha) to 0. This feature can make Tor relays less
4945 identifiable by their use of the mod_ssl DH group, but at
4946 the cost of some usability (#4721) and bridge tracing (#6087)
4947 regressions. Resolves ticket 5598.
4948 - Send a CRLF at the end of each STATUS_* control protocol event. This
4949 bug tickled a bug in Vidalia which would make it freeze. Fixes
4950 bug 6094; bugfix on 0.2.3.16-alpha.
4953 - Disable writing on marked-for-close connections when they are
4954 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
4955 bug 5263; bugfix on 0.0.2pre13, where we first added a special
4956 case for flushing marked connections.
4957 - Detect SSL handshake even when the initial attempt to write the
4958 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
4959 - Change the AllowDotExit rules so they should actually work.
4960 We now enforce AllowDotExit only immediately after receiving an
4961 address via SOCKS or DNSPort: other sources are free to provide
4962 .exit addresses after the resolution occurs. Fixes bug 3940;
4963 bugfix on 0.2.2.1-alpha.
4964 - Fix a (harmless) integer overflow in cell statistics reported by
4965 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
4966 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
4967 right places and never depends on the consensus parameters or
4968 computes adaptive timeouts when it is disabled. Fixes bug 5049;
4969 bugfix on 0.2.2.14-alpha.
4970 - When building Tor on Windows with -DUNICODE (not default), ensure
4971 that error messages, filenames, and DNS server names are always
4972 NUL-terminated when we convert them to a single-byte encoding.
4973 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
4974 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
4975 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
4976 - Fix an edge case where TestingTorNetwork is set but the authorities
4977 and relays all have an uptime of zero, where the private Tor network
4978 could briefly lack support for hidden services. Fixes bug 3886;
4979 bugfix on 0.2.2.18-alpha.
4980 - Correct the manpage's descriptions for the default values of
4981 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
4983 - Fix the documentation for the --hush and --quiet command line
4984 options, which changed their behavior back in 0.2.3.3-alpha.
4985 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
4989 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
4990 more information to it, so that we can track it down in case it
4991 returns again. Mitigates bug 5235.
4992 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
4993 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
4994 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
4995 - Warn the user when HTTPProxy, but no other proxy type, is
4996 configured. This can cause surprising behavior: it doesn't send
4997 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
4998 directory traffic only. Resolves ticket 4663.
4999 - Issue a notice if a guard completes less than 40% of your circuits.
5000 Threshold is configurable by torrc option PathBiasNoticeRate and
5001 consensus parameter pb_noticepct. There is additional, off-by-
5002 default code to disable guards which fail too many circuits.
5003 Addresses ticket 5458.
5004 - Update to the June 6 2012 Maxmind GeoLite Country database.
5006 o Code simplifications and refactoring:
5007 - Remove validate_pluggable_transports_config(): its warning
5008 message is now handled by connection_or_connect().
5011 Changes in version 0.2.2.37 - 2012-06-06
5012 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
5013 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
5017 - Work around a bug in OpenSSL that broke renegotiation with TLS
5018 1.1 and TLS 1.2. Without this workaround, all attempts to speak
5019 the v2 Tor connection protocol when both sides were using OpenSSL
5020 1.0.1 would fail. Resolves ticket 6033.
5021 - When waiting for a client to renegotiate, don't allow it to add
5022 any bytes to the input buffer. This fixes a potential DoS issue.
5023 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
5024 - Fix an edge case where if we fetch or publish a hidden service
5025 descriptor, we might build a 4-hop circuit and then use that circuit
5026 for exiting afterwards -- even if the new last hop doesn't obey our
5027 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
5030 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
5031 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
5034 - Tell GCC and Clang to check for any errors in format strings passed
5035 to the tor_v*(print|scan)f functions.
5038 Changes in version 0.2.3.16-alpha - 2012-06-05
5039 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
5040 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
5041 currently). It also fixes a variety of smaller bugs and other cleanups
5042 that get us closer to a release candidate.
5044 o Major bugfixes (general):
5045 - Work around a bug in OpenSSL that broke renegotiation with TLS
5046 1.1 and TLS 1.2. Without this workaround, all attempts to speak
5047 the v2 Tor connection protocol when both sides were using OpenSSL
5048 1.0.1 would fail. Resolves ticket 6033.
5049 - When waiting for a client to renegotiate, don't allow it to add
5050 any bytes to the input buffer. This fixes a potential DoS issue.
5051 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
5052 - Pass correct OR address to managed proxies (like obfsproxy),
5053 even when ORListenAddress is used. Fixes bug 4865; bugfix on
5055 - The advertised platform of a router now includes only its operating
5056 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
5057 service pack level (for Windows) or its CPU architecture (for Unix).
5058 We also no longer include the "git-XYZ" tag in the version. Resolves
5061 o Major bugfixes (clients):
5062 - If we are unable to find any exit that supports our predicted ports,
5063 stop calling them predicted, so that we don't loop and build
5064 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
5065 which introduced predicted ports.
5066 - Fix an edge case where if we fetch or publish a hidden service
5067 descriptor, we might build a 4-hop circuit and then use that circuit
5068 for exiting afterwards -- even if the new last hop doesn't obey our
5069 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
5070 - Check at each new consensus whether our entry guards were picked
5071 long enough ago that we should rotate them. Previously, we only
5072 did this check at startup, which could lead to us holding a guard
5073 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
5074 - When fetching a bridge descriptor from a bridge authority,
5075 always do so anonymously, whether we have been able to open
5076 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
5077 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
5078 but we'll need to wait for bug 6010 before it's actually usable.
5080 o Major bugfixes (directory authorities):
5081 - When computing weight parameters, behave more robustly in the
5082 presence of a bad bwweightscale value. Previously, the authorities
5083 would crash if they agreed on a sufficiently broken weight_scale
5084 value: now, they use a reasonable default and carry on. Partial
5085 fix for 5786; bugfix on 0.2.2.17-alpha.
5086 - Check more thoroughly to prevent a rogue authority from
5087 double-voting on any consensus directory parameter. Previously,
5088 authorities would crash in this case if the total number of
5089 votes for any parameter exceeded the number of active voters,
5090 but would let it pass otherwise. Partial fix for bug 5786; bugfix
5094 - Rate-limit log messages when asked to connect anonymously to
5095 a private address. When these hit, they tended to hit fast and
5096 often. Also, don't bother trying to connect to addresses that we
5097 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
5098 reply makes us think we have been lied to, even when the address the
5099 client tried to connect to was "localhost." Resolves ticket 2822.
5100 - Allow packagers to insert an extra string in server descriptor
5101 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
5102 Resolves the rest of ticket 2988.
5103 - Raise the threshold of server descriptors needed (75%) and exit
5104 server descriptors needed (50%) before we will declare ourselves
5105 bootstrapped. This will make clients start building circuits a
5106 little later, but makes the initially constructed circuits less
5107 skewed and less in conflict with further directory fetches. Fixes
5109 - Close any connection that sends unrecognized junk before the
5110 handshake. Solves an issue noted in bug 4369.
5111 - Improve log messages about managed transports. Resolves ticket 5070.
5112 - Tag a bridge's descriptor as "never to be sent unencrypted".
5113 This shouldn't matter, since bridges don't open non-anonymous
5114 connections to the bridge authority and don't allow unencrypted
5115 directory connections from clients, but we might as well make
5116 sure. Closes bug 5139.
5117 - Expose our view of whether we have gone dormant to the controller,
5118 via a new "GETINFO dormant" value. Torbutton and other controllers
5119 can use this to avoid doing periodic requests through Tor while
5120 it's dormant (bug 4718). Fixes bug 5954.
5121 - Tell GCC and Clang to check for any errors in format strings passed
5122 to the tor_v*(print|scan)f functions.
5123 - Update to the May 1 2012 Maxmind GeoLite Country database.
5125 o Minor bugfixes (already included in 0.2.2.36):
5126 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
5127 Fixes bug 5346; bugfix on 0.0.8pre3.
5128 - Correct parsing of certain date types in parse_http_time().
5129 Without this patch, If-Modified-Since would behave
5130 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
5131 Esteban Manchado Velázques.
5132 - Make our number-parsing functions always treat too-large values
5133 as an error, even when those values exceed the width of the
5134 underlying type. Previously, if the caller provided these
5135 functions with minima or maxima set to the extreme values of the
5136 underlying integer type, these functions would return those
5137 values on overflow rather than treating overflow as an error.
5138 Fixes part of bug 5786; bugfix on 0.0.9.
5139 - If we hit the error case where routerlist_insert() replaces an
5140 existing (old) server descriptor, make sure to remove that
5141 server descriptor from the old_routers list. Fix related to bug
5142 1776. Bugfix on 0.2.2.18-alpha.
5143 - Clarify the behavior of MaxCircuitDirtiness with hidden service
5144 circuits. Fixes issue 5259.
5146 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
5147 - Prevent a null-pointer dereference when receiving a data cell
5148 for a nonexistent stream when the circuit in question has an
5149 empty deliver window. We don't believe this is triggerable,
5150 since we don't currently allow deliver windows to become empty,
5151 but the logic is tricky enough that it's better to make the code
5152 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
5153 - Fix a memory leak when trying to launch a DNS request when the
5154 network is disabled or the nameservers are unconfigurable. Fixes
5155 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
5156 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
5157 - Don't hold a Windows file handle open for every file mapping;
5158 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
5160 - Avoid O(n^2) performance characteristics when parsing a large
5161 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
5162 - Format more doubles with %f, not %lf. Patch from grarpamp to make
5163 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
5165 - Make our replacement implementation of strtok_r() compatible with
5166 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
5167 bugfix on 0.2.2.1-alpha.
5168 - Fix a NULL-pointer dereference on a badly formed
5169 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
5170 bugfix on 0.2.2.9-alpha.
5171 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
5172 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
5173 - Defensively refactor rend_mid_rendezvous() so that protocol
5174 violations and length checks happen in the beginning. Fixes
5176 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
5177 that IPv6 stuff will compile on MSVC, and compilation issues
5178 will be easier to track down. Fixes bug 5861.
5180 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
5181 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
5182 resource exhaustion, so that clients can adjust their load to
5183 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
5184 started using END_STREAM_REASON_RESOURCELIMIT.
5185 - Don't check for whether the address we're using for outbound
5186 connections has changed until after the outbound connection has
5187 completed. On Windows, getsockname() doesn't succeed until the
5188 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
5189 - If the configuration tries to set MyFamily on a bridge, refuse to
5190 do so, and warn about the security implications. Fixes bug 4657;
5191 bugfix on 0.2.0.3-alpha.
5192 - If the client fails to set a reasonable set of ciphersuites
5193 during its v2 handshake renegotiation, allow the renegotiation to
5194 continue nevertheless (i.e. send all the required certificates).
5195 Fixes bug 4591; bugfix on 0.2.0.20-rc.
5196 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
5197 option is set to 0 (which Vidalia version 0.2.16 now does when
5198 a SAVECONF attempt fails), perform other actions that SIGHUP
5199 usually causes (like reopening the logs). Fixes bug 5095; bugfix
5201 - If we fail to write a microdescriptor to the disk cache, do not
5202 continue replacing the old microdescriptor file. Fixes bug 2954;
5203 bugfix on 0.2.2.6-alpha.
5204 - Exit nodes don't need to fetch certificates for authorities that
5205 they don't recognize; only directory authorities, bridges,
5206 and caches need to do that. Fixes part of bug 2297; bugfix on
5208 - Correctly handle checking the permissions on the parent
5209 directory of a control socket in the root directory. Bug found
5210 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
5212 - When told to add a bridge with the same digest as a preexisting
5213 bridge but a different addr:port, change the addr:port as
5214 requested. Previously we would not notice the change. Fixes half
5215 of bug 5603; fix on 0.2.2.26-beta.
5216 - End AUTHCHALLENGE error messages (in the control protocol) with
5217 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
5219 o Minor bugfixes (on 0.2.3.x):
5220 - Turn an assertion (that the number of handshakes received as a
5221 server is not < 1) into a warning. Fixes bug 4873; bugfix on
5223 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
5224 we had reversed them when the answer was cached.) Fixes bug
5225 5723; bugfix on 0.2.3.1-alpha.
5226 - Work correctly on Linux systems with accept4 support advertised in
5227 their headers, but without accept4 support in the kernel. Fix
5228 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
5229 - When told to add a bridge with the same addr:port as a preexisting
5230 bridge but a different transport, change the transport as
5231 requested. Previously we would not notice the change. Fixes half
5232 of bug 5603; fix on 0.2.3.2-alpha.
5233 - Avoid a "double-reply" warning when replying to a SOCKS request
5234 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
5235 bugfix on 0.2.3.4-alpha.
5236 - Fix a bug where a bridge authority crashes if it has seen no
5237 directory requests when it's time to write statistics to disk.
5238 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
5240 - Don't try to open non-control listeners when DisableNetwork is set.
5241 Previously, we'd open all listeners, then immediately close them.
5242 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
5243 - Don't abort the managed proxy protocol if the managed proxy
5244 sends us an unrecognized line; ignore it instead. Fixes bug
5245 5910; bugfix on 0.2.3.9-alpha.
5246 - Fix a compile warning in crypto.c when compiling with clang 3.1.
5247 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
5248 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
5249 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
5250 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
5251 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
5252 - Resolve numerous small warnings and build issues with MSVC. Resolves
5255 o Documentation fixes:
5256 - Improve the manual's documentation for the NT Service command-line
5257 options. Addresses ticket 3964.
5258 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
5259 - Document the changes to the ORPort and DirPort options, and the
5260 fact that {OR/Dir}ListenAddress is now unnecessary (and
5261 therefore deprecated). Resolves ticket 5597.
5264 - Remove the torrc.bridge file: we don't use it for anything, and
5265 it had become badly desynchronized from torrc.sample. Resolves
5269 Changes in version 0.2.2.36 - 2012-05-24
5270 Tor 0.2.2.36 updates the addresses for two of the eight directory
5271 authorities, fixes some potential anonymity and security issues,
5272 and fixes several crash bugs.
5274 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
5275 known flaws, and nobody should be using them. You should upgrade. If
5276 you're using a Linux or BSD and its packages are obsolete, stop using
5277 those packages and upgrade anyway.
5279 o Directory authority changes:
5280 - Change IP address for maatuska (v3 directory authority).
5281 - Change IP address for ides (v3 directory authority), and rename
5285 - When building or running with any version of OpenSSL earlier
5286 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
5287 versions have a bug (CVE-2011-4576) in which their block cipher
5288 padding includes uninitialized data, potentially leaking sensitive
5289 information to any peer with whom they make a SSLv3 connection. Tor
5290 does not use SSL v3 by default, but a hostile client or server
5291 could force an SSLv3 connection in order to gain information that
5292 they shouldn't have been able to get. The best solution here is to
5293 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
5294 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
5295 to make sure that the bug can't happen.
5296 - Never use a bridge or a controller-supplied node as an exit, even
5297 if its exit policy allows it. Found by wanoskarnet. Fixes bug
5298 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
5299 and 0.2.0.3-alpha (for bridge-purpose descriptors).
5300 - Only build circuits if we have a sufficient threshold of the total
5301 descriptors that are marked in the consensus with the "Exit"
5302 flag. This mitigates an attack proposed by wanoskarnet, in which
5303 all of a client's bridges collude to restrict the exit nodes that
5304 the client knows about. Fixes bug 5343.
5305 - Provide controllers with a safer way to implement the cookie
5306 authentication mechanism. With the old method, if another locally
5307 running program could convince a controller that it was the Tor
5308 process, then that program could trick the controller into telling
5309 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
5310 authentication method uses a challenge-response approach to prevent
5311 this attack. Fixes bug 5185; implements proposal 193.
5314 - Avoid logging uninitialized data when unable to decode a hidden
5315 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
5316 - Avoid a client-side assertion failure when receiving an INTRODUCE2
5317 cell on a general purpose circuit. Fixes bug 5644; bugfix on
5319 - Fix builds when the path to sed, openssl, or sha1sum contains
5320 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
5322 - Correct our replacements for the timeradd() and timersub() functions
5323 on platforms that lack them (for example, Windows). The timersub()
5324 function is used when expiring circuits, while timeradd() is
5325 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
5326 bugfix on 0.2.2.24-alpha.
5327 - Fix the SOCKET_OK test that we use to tell when socket
5328 creation fails so that it works on Win64. Fixes part of bug 4533;
5329 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
5332 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
5333 Fixes bug 5346; bugfix on 0.0.8pre3.
5334 - Make our number-parsing functions always treat too-large values
5335 as an error, even when those values exceed the width of the
5336 underlying type. Previously, if the caller provided these
5337 functions with minima or maxima set to the extreme values of the
5338 underlying integer type, these functions would return those
5339 values on overflow rather than treating overflow as an error.
5340 Fixes part of bug 5786; bugfix on 0.0.9.
5341 - Older Linux kernels erroneously respond to strange nmap behavior
5342 by having accept() return successfully with a zero-length
5343 socket. When this happens, just close the connection. Previously,
5344 we would try harder to learn the remote address: but there was
5345 no such remote address to learn, and our method for trying to
5346 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
5347 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
5348 - Correct parsing of certain date types in parse_http_time().
5349 Without this patch, If-Modified-Since would behave
5350 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
5351 Esteban Manchado Velázques.
5352 - Change the BridgePassword feature (part of the "bridge community"
5353 design, which is not yet implemented) to use a time-independent
5354 comparison. The old behavior might have allowed an adversary
5355 to use timing to guess the BridgePassword value. Fixes bug 5543;
5356 bugfix on 0.2.0.14-alpha.
5357 - Detect and reject certain misformed escape sequences in
5358 configuration values. Previously, these values would cause us
5359 to crash if received in a torrc file or over an authenticated
5360 control port. Bug found by Esteban Manchado Velázquez, and
5361 independently by Robert Connolly from Matta Consulting who further
5362 noted that it allows a post-authentication heap overflow. Patch
5363 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
5364 bugfix on 0.2.0.16-alpha.
5365 - Fix a compile warning when using the --enable-openbsd-malloc
5366 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
5367 - During configure, detect when we're building with clang version
5368 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
5369 CFLAGS. clang doesn't support them yet.
5370 - When sending an HTTP/1.1 proxy request, include a Host header.
5371 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
5372 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
5373 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
5374 - If we hit the error case where routerlist_insert() replaces an
5375 existing (old) server descriptor, make sure to remove that
5376 server descriptor from the old_routers list. Fix related to bug
5377 1776. Bugfix on 0.2.2.18-alpha.
5379 o Minor bugfixes (documentation and log messages):
5380 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
5381 Fixes bug 4856; bugfix on Tor 0.0.6.
5382 - Update "ClientOnly" man page entry to explain that there isn't
5383 really any point to messing with it. Resolves ticket 5005.
5384 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
5385 directory authority option (introduced in Tor 0.2.2.34).
5386 - Downgrade the "We're missing a certificate" message from notice
5387 to info: people kept mistaking it for a real problem, whereas it
5388 is seldom the problem even when we are failing to bootstrap. Fixes
5389 bug 5067; bugfix on 0.2.0.10-alpha.
5390 - Correctly spell "connect" in a log message on failure to create a
5391 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
5392 - Clarify the behavior of MaxCircuitDirtiness with hidden service
5393 circuits. Fixes issue 5259.
5396 - Directory authorities now reject versions of Tor older than
5397 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
5398 inclusive. These versions accounted for only a small fraction of
5399 the Tor network, and have numerous known security issues. Resolves
5401 - Update to the May 1 2012 Maxmind GeoLite Country database.
5404 - When sending or relaying a RELAY_EARLY cell, we used to convert
5405 it to a RELAY cell if the connection was using the v1 link
5406 protocol. This was a workaround for older versions of Tor, which
5407 didn't handle RELAY_EARLY cells properly. Now that all supported
5408 versions can handle RELAY_EARLY cells, and now that we're enforcing
5409 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
5410 remove this workaround. Addresses bug 4786.
5413 Changes in version 0.2.3.15-alpha - 2012-04-30
5414 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
5415 the development branch build on Windows again.
5417 o Minor bugfixes (on 0.2.2.x and earlier):
5418 - Make sure that there are no unhandled pending TLS errors before
5419 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
5420 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
5421 Bugfix on 0.1.0.5-rc; fixes bug 4528.
5422 - Fix an assert that directory authorities could trigger on sighup
5423 during some configuration state transitions. We now don't treat
5424 it as a fatal error when the new descriptor we just generated in
5425 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
5426 - After we pick a directory mirror, we would refuse to use it if
5427 it's in our ExcludeExitNodes list, resulting in mysterious failures
5428 to bootstrap for people who just wanted to avoid exiting from
5429 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
5430 - When building with --enable-static-tor on OpenBSD, do not
5431 erroneously attempt to link -lrt. Fixes bug 5103.
5433 o Minor bugfixes (on 0.2.3.x):
5434 - When Tor is built with kernel headers from a recent (last few
5435 years) Linux kernel, do not fail to run on older (pre-2.6.28
5436 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
5437 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
5439 - Fix compilation with miniupnpc version 1.6; patch from
5440 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
5441 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
5442 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
5443 - Fix compilation on platforms without unistd.h, or where environ
5444 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
5447 - Directory authorities are now a little more lenient at accepting
5448 older router descriptors, or newer router descriptors that don't
5449 make big changes. This should help ameliorate past and future
5450 issues where routers think they have uploaded valid descriptors,
5451 but the authorities don't think so. Fix for ticket 2479.
5452 - Make the code that clients use to detect an address change be
5453 IPv6-aware, so that it won't fill clients' logs with error
5454 messages when trying to get the IPv4 address of an IPv6
5455 connection. Implements ticket 5537.
5458 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
5459 authorities needed to use it for a while to keep the network working
5460 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
5461 that was six months ago. As of now, it should no longer be needed
5465 Changes in version 0.2.3.14-alpha - 2012-04-23
5466 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
5467 candidate. It also dramatically speeds up AES: fast relays should
5468 consider switching to the newer OpenSSL library.
5470 o Directory authority changes:
5471 - Change IP address for ides (v3 directory authority), and rename
5475 - Avoid logging uninitialized data when unable to decode a hidden
5476 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
5477 - Avoid a client-side assertion failure when receiving an INTRODUCE2
5478 cell on a general purpose circuit. Fixes bug 5644; bugfix on
5480 - If authorities are unable to get a v2 consensus document from other
5481 directory authorities, they no longer fall back to fetching
5482 them from regular directory caches. Fixes bug 5635; bugfix on
5483 0.2.2.26-beta, where routers stopped downloading v2 consensus
5485 - When we start a Tor client with a normal consensus already cached,
5486 be willing to download a microdescriptor consensus. Fixes bug 4011;
5487 fix on 0.2.3.1-alpha.
5489 o Major features (performance):
5490 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
5491 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
5492 vectorized AES implementations as appropriate. These can be much,
5493 much faster than other AES implementations.
5495 o Minor bugfixes (0.2.2.x and earlier):
5496 - Don't launch more than 10 service-side introduction-point circuits
5497 for a hidden service in five minutes. Previously, we would consider
5498 launching more introduction-point circuits if at least one second
5499 had passed without any introduction-point circuits failing. Fixes
5500 bug 4607; bugfix on 0.0.7pre1.
5501 - Change the BridgePassword feature (part of the "bridge community"
5502 design, which is not yet implemented) to use a time-independent
5503 comparison. The old behavior might have allowed an adversary
5504 to use timing to guess the BridgePassword value. Fixes bug 5543;
5505 bugfix on 0.2.0.14-alpha.
5506 - Enforce correct return behavior of tor_vsscanf() when the '%%'
5507 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
5508 - When sending an HTTP/1.1 proxy request, include a Host header.
5509 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
5510 - Don't log that we have "decided to publish new relay descriptor"
5511 unless we are actually publishing a descriptor. Fixes bug 3942;
5512 bugfix on 0.2.2.28-beta.
5514 o Minor bugfixes (0.2.3.x):
5515 - Fix a bug where a bridge authority crashes (on a failed assert)
5516 if it has seen no directory requests when it's time to write
5517 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
5518 - Fix bug stomping on ORPort option NoListen and ignoring option
5519 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
5520 - In the testsuite, provide a large enough buffer in the tor_sscanf
5521 unit test. Otherwise we'd overrun that buffer and crash during
5522 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
5524 - Make sure we create the keys directory if it doesn't exist and we're
5525 about to store the dynamic Diffie-Hellman parameters. Fixes bug
5526 5572; bugfix on 0.2.3.13-alpha.
5527 - Fix a small memory leak when trying to decode incorrect base16
5528 authenticator during SAFECOOKIE authentication. Found by
5529 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
5532 - Add more information to a log statement that might help track down
5533 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
5534 non-IP address" messages (or any Bug messages, for that matter!),
5535 please let us know about it.
5536 - Relays now understand an IPv6 address when they get one from a
5537 directory server. Resolves ticket 4875.
5538 - Resolve IPv6 addresses in bridge and entry statistics to country
5539 code "??" which means we at least count them. Resolves ticket 5053;
5540 improves on 0.2.3.9-alpha.
5541 - Update to the April 3 2012 Maxmind GeoLite Country database.
5542 - Begin a doc/state-contents.txt file to explain the contents of
5543 the Tor state file. Fixes bug 2987.
5545 o Default torrc changes:
5546 - Stop listing "socksport 9050" in torrc.sample. We open a socks
5547 port on 9050 by default anyway, so this should not change anything
5549 - Stop mentioning the deprecated *ListenAddress options in
5550 torrc.sample. Fixes bug 5438.
5551 - Document unit of bandwidth related options in sample torrc.
5555 - The "torify" script no longer supports the "tsocks" socksifier
5556 tool, since tsocks doesn't support DNS and UDP right for Tor.
5557 Everyone should be using torsocks instead. Fixes bugs 3530 and
5558 5180. Based on a patch by "ugh".
5561 - Change the symmetric cipher interface so that creating and
5562 initializing a stream cipher are no longer separate functions.
5563 - Remove all internal support for unpadded RSA. We never used it, and
5564 it would be a bad idea to start.
5567 Changes in version 0.2.3.13-alpha - 2012-03-26
5568 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
5569 in managed pluggable transports, as well as providing other cleanups
5570 that get us closer to a release candidate.
5572 o Directory authority changes:
5573 - Change IP address for maatuska (v3 directory authority).
5576 - Provide controllers with a safer way to implement the cookie
5577 authentication mechanism. With the old method, if another locally
5578 running program could convince a controller that it was the Tor
5579 process, then that program could trick the controller into telling
5580 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
5581 authentication method uses a challenge-response approach to prevent
5582 this attack. Fixes bug 5185, implements proposal 193.
5583 - Never use a bridge or a controller-supplied node as an exit, even
5584 if its exit policy allows it. Found by wanoskarnet. Fixes bug
5585 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
5586 and 0.2.0.3-alpha (for bridge-purpose descriptors).
5587 - Only build circuits if we have a sufficient threshold of the total
5588 descriptors that are marked in the consensus with the "Exit"
5589 flag. This mitigates an attack proposed by wanoskarnet, in which
5590 all of a client's bridges collude to restrict the exit nodes that
5591 the client knows about. Fixes bug 5343.
5593 o Major bugfixes (on Tor 0.2.3.x):
5594 - Avoid an assert when managed proxies like obfsproxy are configured,
5595 and we receive HUP signals or setconf attempts too rapidly. This
5596 situation happens most commonly when Vidalia tries to attach to
5597 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
5598 bugfix on 0.2.3.6-alpha.
5599 - Fix a relay-side pluggable transports bug where managed proxies were
5600 unreachable from the Internet, because Tor asked them to bind on
5601 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
5602 - Stop discarding command-line arguments when TestingTorNetwork
5603 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
5604 0.2.3.9-alpha, where task 4552 added support for two layers of
5606 - Resume allowing the unit tests to run in gdb. This was accidentally
5607 made impossible when the DisableDebuggerAttachment option was
5608 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
5609 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
5610 0.2.3.11-alpha. Reported by Anthony G. Basile.
5612 o Minor bugfixes (on 0.2.2.x and earlier):
5613 - Ensure we don't cannibalize circuits that are longer than three hops
5614 already, so we don't end up making circuits with 5 or more
5615 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
5616 0.1.0.1-rc which introduced cannibalization.
5617 - Detect and reject certain misformed escape sequences in
5618 configuration values. Previously, these values would cause us
5619 to crash if received in a torrc file or over an authenticated
5620 control port. Bug found by Esteban Manchado Velázquez, and
5621 independently by Robert Connolly from Matta Consulting who further
5622 noted that it allows a post-authentication heap overflow. Patch
5623 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
5624 bugfix on 0.2.0.16-alpha.
5625 - Fix a compile warning when using the --enable-openbsd-malloc
5626 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
5627 - Directory caches no longer refuse to clean out descriptors because
5628 of missing v2 networkstatus documents, unless they're configured
5629 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
5630 0.2.2.26-beta. Patch by Daniel Bryg.
5631 - Update to the latest version of the tinytest unit testing framework.
5632 This includes a couple of bugfixes that can be relevant for
5633 running forked unit tests on Windows, and removes all reserved
5636 o Minor bugfixes (on 0.2.3.x):
5637 - On a failed pipe() call, don't leak file descriptors. Fixes bug
5638 4296; bugfix on 0.2.3.1-alpha.
5639 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
5640 until after we have received a CERTS cell. Fixes bug 4361; bugfix
5641 on 0.2.3.6-alpha. Patch by "frosty".
5642 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
5643 option, so that the IP stack doesn't decide to use it for IPv4
5644 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
5645 - Ensure that variables set in Tor's environment cannot override
5646 environment variables that Tor passes to a managed
5647 pluggable-transport proxy. Previously, Tor would pass every
5648 variable in its environment to managed proxies along with the new
5649 ones, in such a way that on many operating systems, the inherited
5650 environment variables would override those which Tor tried to
5651 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
5652 bugfix on 0.2.3.9-alpha for Windows.
5655 - A wide variety of new unit tests by Esteban Manchado Velázquez.
5656 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
5657 - Update to the March 6 2012 Maxmind GeoLite Country database.
5660 Changes in version 0.2.3.12-alpha - 2012-02-13
5661 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
5662 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
5663 when Tor is configured to use a pluggable transport like obfsproxy.
5666 - Fix builds when the path to sed, openssl, or sha1sum contains
5667 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
5669 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
5670 connections. This change should allow busy exit relays to stop
5671 running out of available sockets as quickly. Fixes bug 4950;
5672 bugfix on 0.2.2.26-beta.
5673 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
5674 would ask the bridge for microdescriptors, which are only supported
5675 in 0.2.3.x, and then fail to bootstrap when it didn't get the
5676 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
5677 - Properly set up obfsproxy's environment when in managed mode. The
5678 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
5679 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
5680 5076 and 5082; bugfix on 0.2.3.6-alpha.
5683 - Use the dead_strip option when building Tor on OS X. This reduces
5684 binary size by almost 19% when linking openssl and libevent
5685 statically, which we do for Tor Browser Bundle.
5686 - Fix broken URLs in the sample torrc file, and tell readers about
5687 the OutboundBindAddress, ExitPolicyRejectPrivate, and
5688 PublishServerDescriptor options. Addresses bug 4652.
5689 - Update to the February 7 2012 Maxmind GeoLite Country database.
5692 - Downgrade the "We're missing a certificate" message from notice
5693 to info: people kept mistaking it for a real problem, whereas it
5694 is seldom the problem even when we are failing to bootstrap. Fixes
5695 bug 5067; bugfix on 0.2.0.10-alpha.
5696 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
5697 managed pluggable transport server proxy's environment.
5698 Previously, we would put it there, even though Tor doesn't
5699 implement an 'extended server port' yet, and even though Tor
5700 almost certainly isn't listening at that address. For now, we set
5701 it to an empty string to avoid crashing older obfsproxies. Bugfix
5703 - Log the heartbeat message every HeartbeatPeriod seconds, not every
5704 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
5705 0.2.3.1-alpha. Bug reported by Scott Bennett.
5706 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
5707 bugfix on 0.2.3.11-alpha.
5708 - Update "ClientOnly" man page entry to explain that there isn't
5709 really any point to messing with it. Resolves ticket 5005.
5710 - Use the correct CVE number for CVE-2011-4576 in our comments and
5711 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
5714 o Code simplifications and refactoring:
5715 - Use the _WIN32 macro throughout our code to detect Windows.
5716 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
5720 Changes in version 0.2.3.11-alpha - 2012-01-22
5721 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
5722 the last step of the plan to limit maximum circuit length, includes
5723 a wide variety of hidden service performance and correctness fixes,
5724 works around an OpenSSL security flaw if your distro is too stubborn
5725 to upgrade, and fixes a bunch of smaller issues.
5728 - Now that Tor 0.2.0.x is completely deprecated, enable the final
5729 part of "Proposal 110: Avoiding infinite length circuits" by
5730 refusing all circuit-extend requests that do not use a relay_early
5731 cell. This change helps Tor resist a class of denial-of-service
5732 attacks by limiting the maximum circuit length.
5733 - Adjust the number of introduction points that a hidden service
5734 will try to maintain based on how long its introduction points
5735 remain in use and how many introductions they handle. Fixes
5737 - Try to use system facilities for enumerating local interface
5738 addresses, before falling back to our old approach (which was
5739 binding a UDP socket, and calling getsockname() on it). That
5740 approach was scaring OS X users whose draconian firewall
5741 software warned about binding to UDP sockets, regardless of
5742 whether packets were sent. Now we try to use getifaddrs(),
5743 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
5744 system supports. Resolves ticket 1827.
5746 o Major security workaround:
5747 - When building or running with any version of OpenSSL earlier
5748 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
5749 versions have a bug (CVE-2011-4576) in which their block cipher
5750 padding includes uninitialized data, potentially leaking sensitive
5751 information to any peer with whom they make a SSLv3 connection. Tor
5752 does not use SSL v3 by default, but a hostile client or server
5753 could force an SSLv3 connection in order to gain information that
5754 they shouldn't have been able to get. The best solution here is to
5755 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
5756 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
5757 to make sure that the bug can't happen.
5760 - Fix the SOCKET_OK test that we use to tell when socket
5761 creation fails so that it works on Win64. Fixes part of bug 4533;
5762 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
5763 - Correct our replacements for the timeradd() and timersub() functions
5764 on platforms that lack them (for example, Windows). The timersub()
5765 function is used when expiring circuits, while timeradd() is
5766 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
5767 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
5768 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
5769 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
5770 bug at runtime, not compile time, because some distributions hack
5771 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
5772 on 0.2.3.9-alpha. Found by Pascal.
5774 o Minor features (controller):
5775 - Use absolute path names when reporting the torrc filename in the
5776 control protocol, so a controller can more easily find the torrc
5777 file. Resolves bug 1101.
5778 - Extend the control protocol to report flags that control a circuit's
5779 path selection in CIRC events and in replies to 'GETINFO
5780 circuit-status'. Implements part of ticket 2411.
5781 - Extend the control protocol to report the hidden service address
5782 and current state of a hidden-service-related circuit in CIRC
5783 events and in replies to 'GETINFO circuit-status'. Implements part
5785 - When reporting the path to the cookie file to the controller,
5786 give an absolute path. Resolves ticket 4881.
5787 - Allow controllers to request an event notification whenever a
5788 circuit is cannibalized or its purpose is changed. Implements
5789 part of ticket 3457.
5790 - Include the creation time of a circuit in CIRC and CIRC2
5791 control-port events and the list produced by the 'GETINFO
5792 circuit-status' control-port command.
5794 o Minor features (directory authorities):
5795 - Directory authorities now reject versions of Tor older than
5796 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
5797 inclusive. These versions accounted for only a small fraction of
5798 the Tor network, and have numerous known security issues. Resolves
5800 - Authority operators can now vote for all relays in a given
5801 set of countries to be BadDir/BadExit/Invalid/Rejected.
5802 - Provide two consensus parameters (FastFlagMinThreshold and
5803 FastFlagMaxThreshold) to control the range of allowable bandwidths
5804 for the Fast directory flag. These allow authorities to run
5805 experiments on appropriate requirements for being a "Fast" node.
5806 The AuthDirFastGuarantee config value still applies. Implements
5808 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
5809 directory authority option (introduced in Tor 0.2.2.34).
5811 o Minor features (other):
5812 - Don't disable the DirPort when we cannot exceed our AccountingMax
5813 limit during this interval because the effective bandwidthrate is
5814 low enough. This is useful in a situation where AccountMax is only
5815 used as an additional safeguard or to provide statistics.
5816 - Prepend an informative header to generated dynamic_dh_params files.
5817 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
5818 EntryNodes will have no effect. Resolves issue 2571.
5819 - Log more useful messages when we fail to disable debugger
5821 - Log which authority we're missing votes from when we go to fetch
5822 them from the other auths.
5823 - Log (at debug level) whenever a circuit's purpose is changed.
5824 - Add missing documentation for the MaxClientCircuitsPending,
5825 UseMicrodescriptors, UserspaceIOCPBuffers, and
5826 _UseFilteringSSLBufferevents options, all introduced during
5828 - Update to the January 3 2012 Maxmind GeoLite Country database.
5830 o Minor bugfixes (hidden services):
5831 - Don't close hidden service client circuits which have almost
5832 finished connecting to their destination when they reach
5833 the normal circuit-build timeout. Previously, we would close
5834 introduction circuits which are waiting for an acknowledgement
5835 from the introduction point, and rendezvous circuits which have
5836 been specified in an INTRODUCE1 cell sent to a hidden service,
5837 after the normal CBT. Now, we mark them as 'timed out', and launch
5838 another rendezvous attempt in parallel. This behavior change can
5839 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
5840 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
5841 - Don't close hidden-service-side rendezvous circuits when they
5842 reach the normal circuit-build timeout. This behavior change can
5843 be disabled using the new
5844 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
5845 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
5846 - Make sure we never mark the wrong rendezvous circuit as having
5847 had its introduction cell acknowleged by the introduction-point
5848 relay. Previously, when we received an INTRODUCE_ACK cell on a
5849 client-side hidden-service introduction circuit, we might have
5850 marked a rendezvous circuit other than the one we specified in
5851 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
5852 a warning message and interfered with the hidden service
5853 connection-establishment process. Fixes bug 4759; bugfix on
5854 0.2.3.3-alpha, when we added the stream-isolation feature which
5855 might cause Tor to open multiple rendezvous circuits for the same
5857 - Don't trigger an assertion failure when we mark a new client-side
5858 hidden-service introduction circuit for close during the process
5859 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
5862 o Minor bugfixes (log messages):
5863 - Correctly spell "connect" in a log message on failure to create a
5864 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
5866 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
5867 Fixes bug 4856; bugfix on Tor 0.0.6.
5868 - Fix the log message describing how we work around discovering
5869 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
5870 4837; bugfix on 0.2.2.9-alpha.
5871 - When logging about a disallowed .exit name, do not also call it
5872 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
5874 o Minor bugfixes (build fixes):
5875 - During configure, detect when we're building with clang version
5876 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
5877 CFLAGS. clang doesn't support them yet.
5878 - During configure, search for library containing cos function as
5879 libm lives in libcore on some platforms (BeOS/Haiku). Linking
5880 against libm was hard-coded before. Fixes the first part of bug
5881 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
5883 - Detect attempts to build Tor on (as yet hypothetical) versions
5884 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
5885 fix for bug 4533. Bugfix on 0.2.2.28-beta.
5886 - Preprocessor directives should not be put inside the arguments
5887 of a macro. This would break compilation with GCC releases prior
5888 to version 3.3. We would never recommend such an old GCC version,
5889 but it is apparently required for binary compatibility on some
5890 platforms (namely, certain builds of Haiku). Fixes the other part
5891 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
5894 o Minor bugfixes (other):
5895 - Older Linux kernels erroneously respond to strange nmap behavior
5896 by having accept() return successfully with a zero-length
5897 socket. When this happens, just close the connection. Previously,
5898 we would try harder to learn the remote address: but there was
5899 no such remote address to learn, and our method for trying to
5900 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
5901 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
5902 - Fix null-pointer access that could occur if TLS allocation failed.
5903 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
5904 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
5905 accidentally been reverted.
5906 - Fix our implementation of crypto_random_hostname() so it can't
5907 overflow on ridiculously large inputs. (No Tor version has ever
5908 provided this kind of bad inputs, but let's be correct in depth.)
5909 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
5910 - Find more places in the code that should have been testing for
5911 invalid sockets using the SOCKET_OK macro. Required for a fix
5912 for bug 4533. Bugfix on 0.2.2.28-beta.
5913 - Fix an assertion failure when, while running with bufferevents, a
5914 connection finishes connecting after it is marked for close, but
5915 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
5916 - test_util_spawn_background_ok() hardcoded the expected value
5917 for ENOENT to 2. This isn't portable as error numbers are
5918 platform specific, and particularly the hurd has ENOENT at
5919 0x40000002. Construct expected string at runtime, using the correct
5920 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
5921 - Reject attempts to disable DisableDebuggerAttachment while Tor is
5922 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
5923 - Use an appropriate-width type for sockets in tor-fw-helper on
5924 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
5927 - When sending or relaying a RELAY_EARLY cell, we used to convert
5928 it to a RELAY cell if the connection was using the v1 link
5929 protocol. This was a workaround for older versions of Tor, which
5930 didn't handle RELAY_EARLY cells properly. Now that all supported
5931 versions can handle RELAY_EARLY cells, and now that we're enforcing
5932 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
5933 remove this workaround. Addresses bug 4786.
5935 o Code simplifications and refactoring:
5936 - Use OpenSSL's built-in SSL_state_string_long() instead of our
5937 own homebrewed ssl_state_to_string() replacement. Patch from
5938 Emile Snyder. Fixes bug 4653.
5939 - Use macros to indicate OpenSSL versions, so we don't need to worry
5940 about accidental hexadecimal bit shifts.
5941 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
5943 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
5944 - Use the smartlist_add_asprintf() alias more consistently.
5945 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
5946 invalid value, rather than just -1.
5947 - Rename a handful of old identifiers, mostly related to crypto
5948 structures and crypto functions. By convention, our "create an
5949 object" functions are called "type_new()", our "free an object"
5950 functions are called "type_free()", and our types indicate that
5951 they are types only with a final "_t". But a handful of older
5952 types and functions broke these rules, with function names like
5953 "type_create" or "subsystem_op_type", or with type names like
5957 Changes in version 0.2.3.10-alpha - 2011-12-16
5958 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
5959 Tor's buffers code. Absolutely everybody should upgrade.
5961 The bug relied on an incorrect calculation when making data continuous
5962 in one of our IO buffers, if the first chunk of the buffer was
5963 misaligned by just the wrong amount. The miscalculation would allow an
5964 attacker to overflow a piece of heap-allocated memory. To mount this
5965 attack, the attacker would need to either open a SOCKS connection to
5966 Tor's SocksPort (usually restricted to localhost), or target a Tor
5967 instance configured to make its connections through a SOCKS proxy
5968 (which Tor does not do by default).
5970 Good security practice requires that all heap-overflow bugs should be
5971 presumed to be exploitable until proven otherwise, so we are treating
5972 this as a potential code execution attack. Please upgrade immediately!
5973 This bug does not affect bufferevents-based builds of Tor. Special
5974 thanks to "Vektor" for reporting this issue to us!
5976 This release also contains a few minor bugfixes for issues discovered
5980 - Fix a heap overflow bug that could occur when trying to pull
5981 data into the first chunk of a buffer, when that chunk had
5982 already had some data drained from it. Fixes CVE-2011-2778;
5983 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
5986 - If we can't attach streams to a rendezvous circuit when we
5987 finish connecting to a hidden service, clear the rendezvous
5988 circuit's stream-isolation state and try to attach streams
5989 again. Previously, we cleared rendezvous circuits' isolation
5990 state either too early (if they were freshly built) or not at all
5991 (if they had been built earlier and were cannibalized). Bugfix on
5992 0.2.3.3-alpha; fixes bug 4655.
5993 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
5994 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
5995 - Fix an assertion failure when a relay with accounting enabled
5996 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
5999 - Update to the December 6 2011 Maxmind GeoLite Country database.
6002 Changes in version 0.2.2.35 - 2011-12-16
6003 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
6004 buffers code. Absolutely everybody should upgrade.
6006 The bug relied on an incorrect calculation when making data continuous
6007 in one of our IO buffers, if the first chunk of the buffer was
6008 misaligned by just the wrong amount. The miscalculation would allow an
6009 attacker to overflow a piece of heap-allocated memory. To mount this
6010 attack, the attacker would need to either open a SOCKS connection to
6011 Tor's SocksPort (usually restricted to localhost), or target a Tor
6012 instance configured to make its connections through a SOCKS proxy
6013 (which Tor does not do by default).
6015 Good security practice requires that all heap-overflow bugs should be
6016 presumed to be exploitable until proven otherwise, so we are treating
6017 this as a potential code execution attack. Please upgrade immediately!
6018 This bug does not affect bufferevents-based builds of Tor. Special
6019 thanks to "Vektor" for reporting this issue to us!
6021 Tor 0.2.2.35 also fixes several bugs in previous versions, including
6022 crash bugs for unusual configurations, and a long-term bug that
6023 would prevent Tor from starting on Windows machines with draconian
6026 With this release, we remind everyone that 0.2.0.x has reached its
6027 formal end-of-life. Those Tor versions have many known flaws, and
6028 nobody should be using them. You should upgrade -- ideally to the
6029 0.2.2.x series. If you're using a Linux or BSD and its packages are
6030 obsolete, stop using those packages and upgrade anyway.
6032 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
6033 longer receive support after some time in early 2012.
6036 - Fix a heap overflow bug that could occur when trying to pull
6037 data into the first chunk of a buffer, when that chunk had
6038 already had some data drained from it. Fixes CVE-2011-2778;
6039 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
6040 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
6041 that it doesn't attempt to allocate a socketpair. This could cause
6042 some problems on Windows systems with overzealous firewalls. Fix for
6043 bug 4457; workaround for Libevent versions 2.0.1-alpha through
6045 - If we mark an OR connection for close based on a cell we process,
6046 don't process any further cells on it. We already avoid further
6047 reads on marked-for-close connections, but now we also discard the
6048 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
6049 which was the first version where we might mark a connection for
6050 close based on processing a cell on it.
6051 - Correctly sanity-check that we don't underflow on a memory
6052 allocation (and then assert) for hidden service introduction
6053 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
6054 bugfix on 0.2.1.5-alpha.
6055 - Fix a memory leak when we check whether a hidden service
6056 descriptor has any usable introduction points left. Fixes bug
6057 4424. Bugfix on 0.2.2.25-alpha.
6058 - Don't crash when we're running as a relay and don't have a GeoIP
6059 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
6060 we've had in the 0.2.3.x branch already.
6061 - When running as a client, do not print a misleading (and plain
6062 wrong) log message that we're collecting "directory request"
6063 statistics: clients don't collect statistics. Also don't create a
6064 useless (because empty) stats file in the stats/ directory. Fixes
6065 bug 4353; bugfix on 0.2.2.34.
6068 - Detect failure to initialize Libevent. This fix provides better
6069 detection for future instances of bug 4457.
6070 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
6071 function. This was eating up hideously large amounts of time on some
6072 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
6073 - Resolve an integer overflow bug in smartlist_ensure_capacity().
6074 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
6076 - Don't warn about unused log_mutex in log.c when building with
6077 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
6078 0.1.0.6-rc which introduced --disable-threads.
6079 - When configuring, starting, or stopping an NT service, stop
6080 immediately after the service configuration attempt has succeeded
6081 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
6082 - When sending a NETINFO cell, include the original address
6083 received for the other side, not its canonical address. Found
6084 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
6085 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
6086 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
6087 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
6088 occurred when a client tried to fetch a descriptor for a bridge
6089 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
6090 - Backport fixes for a pair of compilation warnings on Windows.
6091 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
6092 - If we had ever tried to call tor_addr_to_str on an address of
6093 unknown type, we would have done a strdup on an uninitialized
6094 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
6095 Reported by "troll_un".
6096 - Correctly detect and handle transient lookup failures from
6097 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
6098 Reported by "troll_un".
6099 - Fix null-pointer access that could occur if TLS allocation failed.
6100 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
6101 - Use tor_socket_t type for listener argument to accept(). Fixes bug
6102 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
6105 - Add two new config options for directory authorities:
6106 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
6107 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
6108 that is always sufficient to satisfy the bandwidth requirement for
6109 the Guard flag. Now it will be easier for researchers to simulate
6110 Tor networks with different values. Resolves ticket 4484.
6111 - When Tor ignores a hidden service specified in its configuration,
6112 include the hidden service's directory in the warning message.
6113 Previously, we would only tell the user that some hidden service
6114 was ignored. Bugfix on 0.0.6; fixes bug 4426.
6115 - Update to the December 6 2011 Maxmind GeoLite Country database.
6117 o Packaging changes:
6118 - Make it easier to automate expert package builds on Windows,
6119 by removing an absolute path from makensis.exe command.
6122 Changes in version 0.2.1.32 - 2011-12-16
6123 Tor 0.2.1.32 backports important security and privacy fixes for
6124 oldstable. This release is intended only for package maintainers and
6125 others who cannot use the 0.2.2 stable series. All others should be
6126 using Tor 0.2.2.x or newer.
6128 The Tor 0.2.1.x series will reach formal end-of-life some time in
6129 early 2012; we will stop releasing patches for it then.
6131 o Major bugfixes (also included in 0.2.2.x):
6132 - Correctly sanity-check that we don't underflow on a memory
6133 allocation (and then assert) for hidden service introduction
6134 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
6135 bugfix on 0.2.1.5-alpha.
6136 - Fix a heap overflow bug that could occur when trying to pull
6137 data into the first chunk of a buffer, when that chunk had
6138 already had some data drained from it. Fixes CVE-2011-2778;
6139 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
6142 - Update to the December 6 2011 Maxmind GeoLite Country database.
6145 Changes in version 0.2.3.9-alpha - 2011-12-08
6146 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
6147 a "DisableNetwork" security feature that bundles can use to avoid
6148 touching the network until bridges are configured, moves forward on
6149 the pluggable transport design, fixes a flaw in the hidden service
6150 design that unnecessarily prevented clients with wrong clocks from
6151 reaching hidden services, and fixes a wide variety of other issues.
6154 - Clients can now connect to private bridges over IPv6. Bridges
6155 still need at least one IPv4 address in order to connect to
6156 other relays. Note that we don't yet handle the case where the
6157 user has two bridge lines for the same bridge (one IPv4, one
6158 IPv6). Implements parts of proposal 186.
6159 - New "DisableNetwork" config option to prevent Tor from launching any
6160 connections or accepting any connections except on a control port.
6161 Bundles and controllers can set this option before letting Tor talk
6162 to the rest of the network, for example to prevent any connections
6163 to a non-bridge address. Packages like Orbot can also use this
6164 option to instruct Tor to save power when the network is off.
6165 - Clients and bridges can now be configured to use a separate
6166 "transport" proxy. This approach makes the censorship arms race
6167 easier by allowing bridges to use protocol obfuscation plugins. It
6168 implements the "managed proxy" part of proposal 180 (ticket 3472).
6169 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
6170 implementation. It makes AES_CTR about 7% faster than our old one
6171 (which was about 10% faster than the one OpenSSL used to provide).
6172 Resolves ticket 4526.
6173 - Add a "tor2web mode" for clients that want to connect to hidden
6174 services non-anonymously (and possibly more quickly). As a safety
6175 measure to try to keep users from turning this on without knowing
6176 what they are doing, tor2web mode must be explicitly enabled at
6177 compile time, and a copy of Tor compiled to run in tor2web mode
6178 cannot be used as a normal Tor client. Implements feature 2553.
6179 - Add experimental support for running on Windows with IOCP and no
6180 kernel-space socket buffers. This feature is controlled by a new
6181 "UserspaceIOCPBuffers" config option (off by default), which has
6182 no effect unless Tor has been built with support for bufferevents,
6183 is running on Windows, and has enabled IOCP. This may, in the long
6184 run, help solve or mitigate bug 98.
6185 - Use a more secure consensus parameter voting algorithm. Now at
6186 least three directory authorities or a majority of them must
6187 vote on a given parameter before it will be included in the
6188 consensus. Implements proposal 178.
6191 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
6192 They used to check that the timestamp was within 30 minutes
6193 of their system clock, so they could cap the size of their
6194 replay-detection cache, but that approach unnecessarily refused
6195 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
6196 the v3 intro-point protocol (the first one which sent a timestamp
6197 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
6198 - Only use the EVP interface when AES acceleration is enabled,
6199 to avoid a 5-7% performance regression. Resolves issue 4525;
6200 bugfix on 0.2.3.8-alpha.
6202 o Privacy/anonymity features (bridge detection):
6203 - Make bridge SSL certificates a bit more stealthy by using random
6204 serial numbers, in the same fashion as OpenSSL when generating
6205 self-signed certificates. Implements ticket 4584.
6206 - Introduce a new config option "DynamicDHGroups", enabled by
6207 default, which provides each bridge with a unique prime DH modulus
6208 to be used during SSL handshakes. This option attempts to help
6209 against censors who might use the Apache DH modulus as a static
6210 identifier for bridges. Addresses ticket 4548.
6212 o Minor features (new/different config options):
6213 - New configuration option "DisableDebuggerAttachment" (on by default)
6214 to prevent basic debugging attachment attempts by other processes.
6215 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
6216 - Allow MapAddress directives to specify matches against super-domains,
6217 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
6218 Implements issue 933.
6219 - Slightly change behavior of "list" options (that is, config
6220 options that can appear more than once) when they appear both in
6221 torrc and on the command line. Previously, the command-line options
6222 would be appended to the ones from torrc. Now, the command-line
6223 options override the torrc options entirely. This new behavior
6224 allows the user to override list options (like exit policies and
6225 ports to listen on) from the command line, rather than simply
6226 appending to the list.
6227 - You can get the old (appending) command-line behavior for "list"
6228 options by prefixing the option name with a "+".
6229 - You can remove all the values for a "list" option from the command
6230 line without adding any new ones by prefixing the option name
6232 - Add experimental support for a "defaults" torrc file to be parsed
6233 before the regular torrc. Torrc options override the defaults file's
6234 options in the same way that the command line overrides the torrc.
6235 The SAVECONF controller command saves only those options which
6236 differ between the current configuration and the defaults file. HUP
6237 reloads both files. (Note: This is an experimental feature; its
6238 behavior will probably be refined in future 0.2.3.x-alpha versions
6239 to better meet packagers' needs.) Implements task 4552.
6242 - Try to make the introductory warning message that Tor prints on
6243 startup more useful for actually finding help and information.
6244 Resolves ticket 2474.
6245 - Running "make version" now displays the version of Tor that
6246 we're about to build. Idea from katmagic; resolves issue 4400.
6247 - Expire old or over-used hidden service introduction points.
6248 Required by fix for bug 3460.
6249 - Move the replay-detection cache for the RSA-encrypted parts of
6250 INTRODUCE2 cells to the introduction point data structures.
6251 Previously, we would use one replay-detection cache per hidden
6252 service. Required by fix for bug 3460.
6253 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
6254 public key replay-detection cache from 60 minutes to 5 minutes. This
6255 replay-detection cache is now used only to detect multiple
6256 INTRODUCE2 cells specifying the same rendezvous point, so we can
6257 avoid launching multiple simultaneous attempts to connect to it.
6259 o Minor bugfixes (on Tor 0.2.2.x and earlier):
6260 - Resolve an integer overflow bug in smartlist_ensure_capacity().
6261 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
6263 - Fix a minor formatting issue in one of tor-gencert's error messages.
6265 - Prevent a false positive from the check-spaces script, by disabling
6266 the "whitespace between function name and (" check for functions
6268 - Fix a log message suggesting that people contact a non-existent
6269 email address. Fixes bug 3448.
6270 - Fix null-pointer access that could occur if TLS allocation failed.
6271 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
6272 - Report a real bootstrap problem to the controller on router
6273 identity mismatch. Previously we just said "foo", which probably
6274 made a lot of sense at the time. Fixes bug 4169; bugfix on
6276 - If we had ever tried to call tor_addr_to_str() on an address of
6277 unknown type, we would have done a strdup() on an uninitialized
6278 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
6279 Reported by "troll_un".
6280 - Correctly detect and handle transient lookup failures from
6281 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
6282 Reported by "troll_un".
6283 - Use tor_socket_t type for listener argument to accept(). Fixes bug
6284 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
6285 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
6286 bug 4532; found by "troll_un".
6288 o Minor bugfixes (on Tor 0.2.3.x):
6289 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
6291 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
6292 circuit for use as a hidden service client's rendezvous point.
6293 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
6294 with help from wanoskarnet.
6295 - Restore behavior of overriding SocksPort, ORPort, and similar
6296 options from the command line. Bugfix on 0.2.3.3-alpha.
6299 - Properly handle the case where the build-tree is not the same
6300 as the source tree when generating src/common/common_sha1.i,
6301 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
6302 bugfix on 0.2.0.1-alpha.
6304 o Code simplifications, cleanups, and refactorings:
6305 - Remove the pure attribute from all functions that used it
6306 previously. In many cases we assigned it incorrectly, because the
6307 functions might assert or call impure functions, and we don't have
6308 evidence that keeping the pure attribute is worthwhile. Implements
6309 changes suggested in ticket 4421.
6310 - Remove some dead code spotted by coverity. Fixes cid 432.
6311 Bugfix on 0.2.3.1-alpha, closes bug 4637.
6314 Changes in version 0.2.3.8-alpha - 2011-11-22
6315 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
6316 socketpair-related bug that has been bothering Windows users. It adds
6317 support to serve microdescriptors to controllers, so Vidalia's network
6318 map can resume listing relays (once Vidalia implements its side),
6319 and adds better support for hardware AES acceleration. Finally, it
6320 starts the process of adjusting the bandwidth cutoff for getting the
6321 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
6322 that tiny relays harm performance more than they help network capacity.
6325 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
6326 that it doesn't attempt to allocate a socketpair. This could cause
6327 some problems on Windows systems with overzealous firewalls. Fix for
6328 bug 4457; workaround for Libevent versions 2.0.1-alpha through
6330 - Correctly sanity-check that we don't underflow on a memory
6331 allocation (and then assert) for hidden service introduction
6332 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
6333 bugfix on 0.2.1.5-alpha.
6334 - Remove the artificially low cutoff of 20KB to guarantee the Fast
6335 flag. In the past few years the average relay speed has picked
6336 up, and while the "top 7/8 of the network get the Fast flag" and
6337 "all relays with 20KB or more of capacity get the Fast flag" rules
6338 used to have the same result, now the top 7/8 of the network has
6339 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
6340 - Fix a rare assertion failure when checking whether a v0 hidden
6341 service descriptor has any usable introduction points left, and
6342 we don't have enough information to build a circuit to the first
6343 intro point named in the descriptor. The HS client code in
6344 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
6345 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
6346 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
6347 - Make bridge authorities not crash when they are asked for their own
6348 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
6349 - When running as a client, do not print a misleading (and plain
6350 wrong) log message that we're collecting "directory request"
6351 statistics: clients don't collect statistics. Also don't create a
6352 useless (because empty) stats file in the stats/ directory. Fixes
6353 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
6356 - Allow Tor controllers like Vidalia to obtain the microdescriptor
6357 for a relay by identity digest or nickname. Previously,
6358 microdescriptors were only available by their own digests, so a
6359 controller would have to ask for and parse the whole microdescriptor
6360 consensus in order to look up a single relay's microdesc. Fixes
6361 bug 3832; bugfix on 0.2.3.1-alpha.
6362 - Use OpenSSL's EVP interface for AES encryption, so that all AES
6363 operations can use hardware acceleration (if present). Resolves
6366 o Minor bugfixes (on 0.2.2.x and earlier):
6367 - Detect failure to initialize Libevent. This fix provides better
6368 detection for future instances of bug 4457.
6369 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
6370 function. This was eating up hideously large amounts of time on some
6371 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
6372 - Don't warn about unused log_mutex in log.c when building with
6373 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
6374 0.1.0.6-rc which introduced --disable-threads.
6375 - Allow manual 'authenticate' commands to the controller interface
6376 from netcat (nc) as well as telnet. We were rejecting them because
6377 they didn't come with the expected whitespace at the end of the
6378 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
6379 - Fix some (not actually triggerable) buffer size checks in usage of
6380 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
6382 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
6383 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
6384 - When configuring, starting, or stopping an NT service, stop
6385 immediately after the service configuration attempt has succeeded
6386 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
6387 - When sending a NETINFO cell, include the original address
6388 received for the other side, not its canonical address. Found
6389 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
6390 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
6391 can pick them up when the tests aren't disabled. Bugfix on
6392 0.2.2.4-alpha which introduced tinytest.
6393 - Fix a memory leak when we check whether a hidden service
6394 descriptor has any usable introduction points left. Fixes bug
6395 4424. Bugfix on 0.2.2.25-alpha.
6396 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
6397 occurred when a client tried to fetch a descriptor for a bridge
6398 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
6400 o Minor bugfixes (on 0.2.3.x):
6401 - Make util unit tests build correctly with MSVC. Bugfix on
6402 0.2.3.3-alpha. Patch by Gisle Vanem.
6403 - Successfully detect AUTH_CHALLENGE cells with no recognized
6404 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
6406 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
6407 it should still send a NETINFO cell to allow the connection to
6408 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
6410 - Log less loudly when we get an invalid authentication certificate
6411 from a source other than a directory authority: it's not unusual
6412 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
6414 - Tolerate servers with more clock skew in their authentication
6415 certificates than previously. Fixes bug 4371; bugfix on
6417 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
6418 on 0.2.3.4-alpha and 0.2.3.6-alpha.
6421 - Add two new config options for directory authorities:
6422 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
6423 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
6424 that is always sufficient to satisfy the bandwidth requirement for
6425 the Guard flag. Now it will be easier for researchers to simulate
6426 Tor networks with different values. Resolves ticket 4484.
6427 - When Tor ignores a hidden service specified in its configuration,
6428 include the hidden service's directory in the warning message.
6429 Previously, we would only tell the user that some hidden service
6430 was ignored. Bugfix on 0.0.6; fixes bug 4426.
6431 - When we fail to initialize Libevent, retry with IOCP disabled so we
6432 don't need to turn on multi-threading support in Libevent, which in
6433 turn requires a working socketpair(). This is a workaround for bug
6434 4457, which affects Libevent versions from 2.0.1-alpha through
6436 - Detect when we try to build on a platform that doesn't define
6437 AF_UNSPEC to 0. We don't work there, so refuse to compile.
6438 - Update to the November 1 2011 Maxmind GeoLite Country database.
6440 o Packaging changes:
6441 - Make it easier to automate expert package builds on Windows,
6442 by removing an absolute path from makensis.exe command.
6444 o Code simplifications and refactoring:
6445 - Remove some redundant #include directives throughout the code.
6446 Patch from Andrea Gelmini.
6447 - Unconditionally use OpenSSL's AES implementation instead of our
6448 old built-in one. OpenSSL's AES has been better for a while, and
6449 relatively few servers should still be on any version of OpenSSL
6450 that doesn't have good optimized assembly AES.
6451 - Use the name "CERTS" consistently to refer to the new cell type;
6452 we were calling it CERT in some places and CERTS in others.
6455 - Numerous new unit tests for functions in util.c and address.c by
6457 - The long-disabled benchmark tests are now split into their own
6458 ./src/test/bench binary.
6459 - The benchmark tests can now use more accurate timers than
6460 gettimeofday() when such timers are available.
6463 Changes in version 0.2.3.7-alpha - 2011-10-30
6464 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
6465 the new v3 handshake. It also resolves yet another bridge address
6469 - If we mark an OR connection for close based on a cell we process,
6470 don't process any further cells on it. We already avoid further
6471 reads on marked-for-close connections, but now we also discard the
6472 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
6473 which was the first version where we might mark a connection for
6474 close based on processing a cell on it.
6475 - Fix a double-free bug that would occur when we received an invalid
6476 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
6477 bugfix on 0.2.3.6-alpha.
6478 - Bridges no longer include their address in NETINFO cells on outgoing
6479 OR connections, to allow them to blend in better with clients.
6480 Removes another avenue for enumerating bridges. Reported by
6481 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
6482 cells were introduced.
6485 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
6486 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
6489 Changes in version 0.2.3.6-alpha - 2011-10-26
6490 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
6491 anonymity vulnerability where an attacker can deanonymize Tor
6492 users. Everybody should upgrade.
6494 This release also features support for a new v3 connection handshake
6495 protocol, and fixes to make hidden service connections more robust.
6498 - Implement a new handshake protocol (v3) for authenticating Tors to
6499 each other over TLS. It should be more resistant to fingerprinting
6500 than previous protocols, and should require less TLS hacking for
6501 future Tor implementations. Implements proposal 176.
6502 - Allow variable-length padding cells to disguise the length of
6503 Tor's TLS records. Implements part of proposal 184.
6505 o Privacy/anonymity fixes (clients):
6506 - Clients and bridges no longer send TLS certificate chains on
6507 outgoing OR connections. Previously, each client or bridge would
6508 use the same cert chain for all outgoing OR connections until
6509 its IP address changes, which allowed any relay that the client
6510 or bridge contacted to determine which entry guards it is using.
6511 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
6512 - If a relay receives a CREATE_FAST cell on a TLS connection, it
6513 no longer considers that connection as suitable for satisfying a
6514 circuit EXTEND request. Now relays can protect clients from the
6515 CVE-2011-2768 issue even if the clients haven't upgraded yet.
6516 - Directory authorities no longer assign the Guard flag to relays
6517 that haven't upgraded to the above "refuse EXTEND requests
6518 to client connections" fix. Now directory authorities can
6519 protect clients from the CVE-2011-2768 issue even if neither
6520 the clients nor the relays have upgraded yet. There's a new
6521 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
6522 to let us transition smoothly, else tomorrow there would be no
6525 o Major bugfixes (hidden services):
6526 - Improve hidden service robustness: when an attempt to connect to
6527 a hidden service ends, be willing to refetch its hidden service
6528 descriptors from each of the HSDir relays responsible for them
6529 immediately. Previously, we would not consider refetching the
6530 service's descriptors from each HSDir for 15 minutes after the last
6531 fetch, which was inconvenient if the hidden service was not running
6532 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
6533 - When one of a hidden service's introduction points appears to be
6534 unreachable, stop trying it. Previously, we would keep trying
6535 to build circuits to the introduction point until we lost the
6536 descriptor, usually because the user gave up and restarted Tor.
6537 Partly fixes bug 3825.
6538 - Don't launch a useless circuit after failing to use one of a
6539 hidden service's introduction points. Previously, we would
6540 launch a new introduction circuit, but not set the hidden service
6541 which that circuit was intended to connect to, so it would never
6542 actually be used. A different piece of code would then create a
6543 new introduction circuit correctly. Bug reported by katmagic and
6544 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
6546 o Major bugfixes (other):
6547 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
6548 that they initiated. Relays could distinguish incoming bridge
6549 connections from client connections, creating another avenue for
6550 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
6551 Found by "frosty_un".
6552 - Don't update the AccountingSoftLimitHitAt state file entry whenever
6553 tor gets started. This prevents a wrong average bandwidth
6554 estimate, which would cause relays to always start a new accounting
6555 interval at the earliest possible moment. Fixes bug 2003; bugfix
6556 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
6557 immensely in tracking this bug down.
6558 - Fix a crash bug when changing node restrictions while a DNS lookup
6559 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
6562 o Minor bugfixes (on 0.2.2.x and earlier):
6563 - When a hidden service turns an extra service-side introduction
6564 circuit into a general-purpose circuit, free the rend_data and
6565 intro_key fields first, so we won't leak memory if the circuit
6566 is cannibalized for use as another service-side introduction
6567 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
6568 - Rephrase the log message emitted if the TestSocks check is
6569 successful. Patch from Fabian Keil; fixes bug 4094.
6570 - Bridges now skip DNS self-tests, to act a little more stealthily.
6571 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
6572 bridges. Patch by "warms0x".
6573 - Remove a confusing dollar sign from the example fingerprint in the
6574 man page, and also make the example fingerprint a valid one. Fixes
6575 bug 4309; bugfix on 0.2.1.3-alpha.
6576 - Fix internal bug-checking logic that was supposed to catch
6577 failures in digest generation so that it will fail more robustly
6578 if we ask for a nonexistent algorithm. Found by Coverity Scan.
6579 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
6580 - Report any failure in init_keys() calls launched because our
6581 IP address has changed. Spotted by Coverity Scan. Bugfix on
6582 0.1.1.4-alpha; fixes CID 484.
6584 o Minor bugfixes (on 0.2.3.x):
6585 - Fix a bug in configure.in that kept it from building a configure
6586 script with autoconf versions earlier than 2.61. Fixes bug 2430;
6587 bugfix on 0.2.3.1-alpha.
6588 - Don't warn users that they are exposing a client port to the
6589 Internet if they have specified an RFC1918 address. Previously,
6590 we would warn if the user had specified any non-loopback
6591 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
6592 - Fix memory leaks in the failing cases of the new SocksPort and
6593 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
6594 fixes coverity CIDs 485, 486, and 487.
6597 - When a hidden service's introduction point times out, consider
6598 trying it again during the next attempt to connect to the
6599 HS. Previously, we would not try it again unless a newly fetched
6600 descriptor contained it. Required by fixes for bugs 1297 and 3825.
6601 - The next version of Windows will be called Windows 8, and it has
6602 a major version of 6, minor version of 2. Correctly identify that
6603 version instead of calling it "Very recent version". Resolves
6604 ticket 4153; reported by funkstar.
6605 - The Bridge Authority now writes statistics on how many bridge
6606 descriptors it gave out in total, and how many unique descriptors
6607 it gave out. It also lists how often the most and least commonly
6608 fetched descriptors were given out, as well as the median and
6609 25th/75th percentile. Implements tickets 4200 and 4294.
6610 - Update to the October 4 2011 Maxmind GeoLite Country database.
6612 o Code simplifications and refactoring:
6613 - Remove some old code to remember statistics about which descriptors
6614 we've served as a directory mirror. The feature wasn't used and
6615 is outdated now that microdescriptors are around.
6616 - Rename Tor functions that turn strings into addresses, so that
6617 "parse" indicates that no hostname resolution occurs, and
6618 "lookup" indicates that hostname resolution may occur. This
6619 should help prevent mistakes in the future. Fixes bug 3512.
6622 Changes in version 0.2.2.34 - 2011-10-26
6623 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
6624 can deanonymize Tor users. Everybody should upgrade.
6626 The attack relies on four components: 1) Clients reuse their TLS cert
6627 when talking to different relays, so relays can recognize a user by
6628 the identity key in her cert. 2) An attacker who knows the client's
6629 identity key can probe each guard relay to see if that identity key
6630 is connected to that guard relay right now. 3) A variety of active
6631 attacks in the literature (starting from "Low-Cost Traffic Analysis
6632 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
6633 discover the guard relays that a Tor user visiting the website is using.
6634 4) Clients typically pick three guards at random, so the set of guards
6635 for a given user could well be a unique fingerprint for her. This
6636 release fixes components #1 and #2, which is enough to block the attack;
6637 the other two remain as open research problems. Special thanks to
6638 "frosty_un" for reporting the issue to us!
6640 Clients should upgrade so they are no longer recognizable by the TLS
6641 certs they present. Relays should upgrade so they no longer allow a
6642 remote attacker to probe them to test whether unpatched clients are
6643 currently connected to them.
6645 This release also fixes several vulnerabilities that allow an attacker
6646 to enumerate bridge relays. Some bridge enumeration attacks still
6647 remain; see for example proposal 188.
6649 o Privacy/anonymity fixes (clients):
6650 - Clients and bridges no longer send TLS certificate chains on
6651 outgoing OR connections. Previously, each client or bridge would
6652 use the same cert chain for all outgoing OR connections until
6653 its IP address changes, which allowed any relay that the client
6654 or bridge contacted to determine which entry guards it is using.
6655 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
6656 - If a relay receives a CREATE_FAST cell on a TLS connection, it
6657 no longer considers that connection as suitable for satisfying a
6658 circuit EXTEND request. Now relays can protect clients from the
6659 CVE-2011-2768 issue even if the clients haven't upgraded yet.
6660 - Directory authorities no longer assign the Guard flag to relays
6661 that haven't upgraded to the above "refuse EXTEND requests
6662 to client connections" fix. Now directory authorities can
6663 protect clients from the CVE-2011-2768 issue even if neither
6664 the clients nor the relays have upgraded yet. There's a new
6665 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
6666 to let us transition smoothly, else tomorrow there would be no
6669 o Privacy/anonymity fixes (bridge enumeration):
6670 - Bridge relays now do their directory fetches inside Tor TLS
6671 connections, like all the other clients do, rather than connecting
6672 directly to the DirPort like public relays do. Removes another
6673 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
6674 - Bridges relays now build circuits for themselves in a more similar
6675 way to how clients build them. Removes another avenue for
6676 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
6677 when bridges were introduced.
6678 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
6679 that they initiated. Relays could distinguish incoming bridge
6680 connections from client connections, creating another avenue for
6681 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
6682 Found by "frosty_un".
6685 - Fix a crash bug when changing node restrictions while a DNS lookup
6686 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
6688 - Don't launch a useless circuit after failing to use one of a
6689 hidden service's introduction points. Previously, we would
6690 launch a new introduction circuit, but not set the hidden service
6691 which that circuit was intended to connect to, so it would never
6692 actually be used. A different piece of code would then create a
6693 new introduction circuit correctly. Bug reported by katmagic and
6694 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
6697 - Change an integer overflow check in the OpenBSD_Malloc code so
6698 that GCC is less likely to eliminate it as impossible. Patch
6699 from Mansour Moufid. Fixes bug 4059.
6700 - When a hidden service turns an extra service-side introduction
6701 circuit into a general-purpose circuit, free the rend_data and
6702 intro_key fields first, so we won't leak memory if the circuit
6703 is cannibalized for use as another service-side introduction
6704 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
6705 - Bridges now skip DNS self-tests, to act a little more stealthily.
6706 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
6707 bridges. Patch by "warms0x".
6708 - Fix internal bug-checking logic that was supposed to catch
6709 failures in digest generation so that it will fail more robustly
6710 if we ask for a nonexistent algorithm. Found by Coverity Scan.
6711 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
6712 - Report any failure in init_keys() calls launched because our
6713 IP address has changed. Spotted by Coverity Scan. Bugfix on
6714 0.1.1.4-alpha; fixes CID 484.
6716 o Minor bugfixes (log messages and documentation):
6717 - Remove a confusing dollar sign from the example fingerprint in the
6718 man page, and also make the example fingerprint a valid one. Fixes
6719 bug 4309; bugfix on 0.2.1.3-alpha.
6720 - The next version of Windows will be called Windows 8, and it has
6721 a major version of 6, minor version of 2. Correctly identify that
6722 version instead of calling it "Very recent version". Resolves
6723 ticket 4153; reported by funkstar.
6724 - Downgrade log messages about circuit timeout calibration from
6725 "notice" to "info": they don't require or suggest any human
6726 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
6727 bugfix on 0.2.2.14-alpha.
6730 - Turn on directory request statistics by default and include them in
6731 extra-info descriptors. Don't break if we have no GeoIP database.
6732 Backported from 0.2.3.1-alpha; implements ticket 3951.
6733 - Update to the October 4 2011 Maxmind GeoLite Country database.
6736 Changes in version 0.2.1.31 - 2011-10-26
6737 Tor 0.2.1.31 backports important security and privacy fixes for
6738 oldstable. This release is intended only for package maintainers and
6739 others who cannot use the 0.2.2 stable series. All others should be
6740 using Tor 0.2.2.x or newer.
6742 o Security fixes (also included in 0.2.2.x):
6743 - Replace all potentially sensitive memory comparison operations
6744 with versions whose runtime does not depend on the data being
6745 compared. This will help resist a class of attacks where an
6746 adversary can use variations in timing information to learn
6747 sensitive data. Fix for one case of bug 3122. (Safe memcmp
6748 implementation by Robert Ransom based partially on code by DJB.)
6749 - Fix an assert in parsing router descriptors containing IPv6
6750 addresses. This one took down the directory authorities when
6751 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
6753 o Privacy/anonymity fixes (also included in 0.2.2.x):
6754 - Clients and bridges no longer send TLS certificate chains on
6755 outgoing OR connections. Previously, each client or bridge would
6756 use the same cert chain for all outgoing OR connections until
6757 its IP address changes, which allowed any relay that the client
6758 or bridge contacted to determine which entry guards it is using.
6759 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
6760 - If a relay receives a CREATE_FAST cell on a TLS connection, it
6761 no longer considers that connection as suitable for satisfying a
6762 circuit EXTEND request. Now relays can protect clients from the
6763 CVE-2011-2768 issue even if the clients haven't upgraded yet.
6764 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
6765 that they initiated. Relays could distinguish incoming bridge
6766 connections from client connections, creating another avenue for
6767 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
6768 Found by "frosty_un".
6769 - When receiving a hidden service descriptor, check that it is for
6770 the hidden service we wanted. Previously, Tor would store any
6771 hidden service descriptors that a directory gave it, whether it
6772 wanted them or not. This wouldn't have let an attacker impersonate
6773 a hidden service, but it did let directories pre-seed a client
6774 with descriptors that it didn't want. Bugfix on 0.0.6.
6775 - Avoid linkability based on cached hidden service descriptors: forget
6776 all hidden service descriptors cached as a client when processing a
6777 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
6778 - Make the bridge directory authority refuse to answer directory
6779 requests for "all" descriptors. It used to include bridge
6780 descriptors in its answer, which was a major information leak.
6781 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
6782 - Don't attach new streams to old rendezvous circuits after SIGNAL
6783 NEWNYM. Previously, we would keep using an existing rendezvous
6784 circuit if it remained open (i.e. if it were kept open by a
6785 long-lived stream, or if a new stream were attached to it before
6786 Tor could notice that it was old and no longer in use). Bugfix on
6787 0.1.1.15-rc; fixes bug 3375.
6789 o Minor bugfixes (also included in 0.2.2.x):
6790 - When we restart our relay, we might get a successful connection
6791 from the outside before we've started our reachability tests,
6792 triggering a warning: "ORPort found reachable, but I have no
6793 routerinfo yet. Failing to inform controller of success." This
6794 bug was harmless unless Tor is running under a controller
6795 like Vidalia, in which case the controller would never get a
6796 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
6798 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
6799 enabled. Fixes bug 1526.
6800 - Remove undocumented option "-F" from tor-resolve: it hasn't done
6801 anything since 0.2.1.16-rc.
6802 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
6803 None of the cases where we did this before were wrong, but by making
6804 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
6805 - Fix a rare crash bug that could occur when a client was configured
6806 with a large number of bridges. Fixes bug 2629; bugfix on
6807 0.2.1.2-alpha. Bugfix by trac user "shitlei".
6808 - Correct the warning displayed when a rendezvous descriptor exceeds
6809 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
6811 - Fix an uncommon assertion failure when running with DNSPort under
6812 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
6813 - When warning about missing zlib development packages during compile,
6814 give the correct package names. Bugfix on 0.2.0.1-alpha.
6815 - Require that introduction point keys and onion keys have public
6816 exponent 65537. Bugfix on 0.2.0.10-alpha.
6817 - Do not crash when our configuration file becomes unreadable, for
6818 example due to a permissions change, between when we start up
6819 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
6821 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
6823 - Always NUL-terminate the sun_path field of a sockaddr_un before
6824 passing it to the kernel. (Not a security issue: kernels are
6825 smart enough to reject bad sockaddr_uns.) Found by Coverity;
6826 CID #428. Bugfix on Tor 0.2.0.3-alpha.
6827 - Don't stack-allocate the list of supplementary GIDs when we're
6828 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
6829 could take up to 256K, which is way too much stack. Found by
6830 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
6832 o Minor bugfixes (only in 0.2.1.x):
6833 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
6834 rely on them. Bugfix on 0.2.1.30.
6835 - Use git revisions instead of svn revisions when generating our
6836 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
6838 o Minor features (also included in 0.2.2.x):
6839 - Adjust the expiration time on our SSL session certificates to
6840 better match SSL certs seen in the wild. Resolves ticket 4014.
6841 - Allow nameservers with IPv6 address. Resolves bug 2574.
6842 - Update to the October 4 2011 Maxmind GeoLite Country database.
6845 Changes in version 0.2.3.5-alpha - 2011-09-28
6846 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
6847 bridge relays; fixes an assertion error that many users started hitting
6848 today; and adds the ability to refill token buckets more often than
6849 once per second, allowing significant performance improvements.
6852 - Bridge relays now do their directory fetches inside Tor TLS
6853 connections, like all the other clients do, rather than connecting
6854 directly to the DirPort like public relays do. Removes another
6855 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
6856 - Bridges relays now build circuits for themselves in a more similar
6857 way to how clients build them. Removes another avenue for
6858 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
6859 when bridges were introduced.
6862 - Fix an "Assertion md->held_by_node == 1 failed" error that could
6863 occur when the same microdescriptor was referenced by two node_t
6864 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
6866 o Major features (networking):
6867 - Add a new TokenBucketRefillInterval option to refill token buckets
6868 more frequently than once per second. This should improve network
6869 performance, alleviate queueing problems, and make traffic less
6870 bursty. Implements proposal 183; closes ticket 3630. Design by
6871 Florian Tschorsch and Björn Scheuermann; implementation by
6875 - Change an integer overflow check in the OpenBSD_Malloc code so
6876 that GCC is less likely to eliminate it as impossible. Patch
6877 from Mansour Moufid. Fixes bug 4059.
6879 o Minor bugfixes (usability):
6880 - Downgrade log messages about circuit timeout calibration from
6881 "notice" to "info": they don't require or suggest any human
6882 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
6883 bugfix on 0.2.2.14-alpha.
6885 o Minor features (diagnostics):
6886 - When the system call to create a listener socket fails, log the
6887 error message explaining why. This may help diagnose bug 4027.
6890 Changes in version 0.2.3.4-alpha - 2011-09-13
6891 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
6892 tweak to Tor's TLS handshake that makes relays and bridges that run
6893 this new version reachable from Iran again. It also fixes a few new
6894 bugs in 0.2.3.x, and teaches relays to recognize when they're not
6895 listed in the network consensus and republish.
6897 o Major bugfixes (also part of 0.2.2.33):
6898 - Avoid an assertion failure when reloading a configuration with
6899 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
6900 3923; bugfix on 0.2.2.25-alpha.
6902 o Minor features (security, also part of 0.2.2.33):
6903 - Check for replays of the public-key encrypted portion of an
6904 INTRODUCE1 cell, in addition to the current check for replays of
6905 the g^x value. This prevents a possible class of active attacks
6906 by an attacker who controls both an introduction point and a
6907 rendezvous point, and who uses the malleability of AES-CTR to
6908 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
6909 that these attacks are infeasible (requiring the attacker to send
6910 on the order of zettabytes of altered cells in a short interval),
6911 but we'd rather block them off in case there are any classes of
6912 this attack that we missed. Reported by Willem Pinckaers.
6914 o Minor features (also part of 0.2.2.33):
6915 - Adjust the expiration time on our SSL session certificates to
6916 better match SSL certs seen in the wild. Resolves ticket 4014.
6917 - Change the default required uptime for a relay to be accepted as
6918 a HSDir (hidden service directory) from 24 hours to 25 hours.
6919 Improves on 0.2.0.10-alpha; resolves ticket 2649.
6920 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
6921 authorities to abstain from voting on assignment of the HSDir
6922 consensus flag. Related to bug 2649.
6923 - Update to the September 6 2011 Maxmind GeoLite Country database.
6925 o Minor bugfixes (also part of 0.2.2.33):
6926 - Demote the 'replay detected' log message emitted when a hidden
6927 service receives the same Diffie-Hellman public key in two different
6928 INTRODUCE2 cells to info level. A normal Tor client can cause that
6929 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
6930 fixes part of bug 2442.
6931 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
6932 level. There is nothing that a hidden service's operator can do
6933 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
6935 - Clarify a log message specifying the characters permitted in
6936 HiddenServiceAuthorizeClient client names. Previously, the log
6937 message said that "[A-Za-z0-9+-_]" were permitted; that could have
6938 given the impression that every ASCII character between "+" and "_"
6939 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
6941 o Build fixes (also part of 0.2.2.33):
6942 - Clean up some code issues that prevented Tor from building on older
6943 BSDs. Fixes bug 3894; reported by "grarpamp".
6944 - Search for a platform-specific version of "ar" when cross-compiling.
6945 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
6948 - Fix a bug where the SocksPort option (for example) would get
6949 ignored and replaced by the default if a SocksListenAddress
6950 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
6954 - Relays now try regenerating and uploading their descriptor more
6955 frequently if they are not listed in the consensus, or if the
6956 version of their descriptor listed in the consensus is too
6957 old. This fix should prevent situations where a server declines
6958 to re-publish itself because it has done so too recently, even
6959 though the authorities decided not to list its recent-enough
6960 descriptor. Fix for bug 3327.
6963 - Relays now include a reason for regenerating their descriptors
6964 in an HTTP header when uploading to the authorities. This will
6965 make it easier to debug descriptor-upload issues in the future.
6966 - When starting as root and then changing our UID via the User
6967 control option, and we have a ControlSocket configured, make sure
6968 that the ControlSocket is owned by the same account that Tor will
6969 run under. Implements ticket 3421; fix by Jérémy Bobbio.
6972 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
6973 utility function used in the control-port code). This shouldn't
6974 ever happen unless Tor is completely out of memory, but if it did
6975 happen and Tor somehow recovered from it, Tor could have sent a log
6976 message to a control port in the middle of a reply to a controller
6977 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
6978 - Make 'FetchUselessDescriptors' cause all descriptor types and
6979 all consensus types (including microdescriptors) to get fetched.
6980 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
6983 - Make a new "entry connection" struct as an internal subtype of "edge
6984 connection", to simplify the code and make exit connections smaller.
6987 Changes in version 0.2.2.33 - 2011-09-13
6988 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
6989 TLS handshake that makes relays and bridges that run this new version
6990 reachable from Iran again.
6993 - Avoid an assertion failure when reloading a configuration with
6994 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
6995 3923; bugfix on 0.2.2.25-alpha.
6997 o Minor features (security):
6998 - Check for replays of the public-key encrypted portion of an
6999 INTRODUCE1 cell, in addition to the current check for replays of
7000 the g^x value. This prevents a possible class of active attacks
7001 by an attacker who controls both an introduction point and a
7002 rendezvous point, and who uses the malleability of AES-CTR to
7003 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
7004 that these attacks are infeasible (requiring the attacker to send
7005 on the order of zettabytes of altered cells in a short interval),
7006 but we'd rather block them off in case there are any classes of
7007 this attack that we missed. Reported by Willem Pinckaers.
7010 - Adjust the expiration time on our SSL session certificates to
7011 better match SSL certs seen in the wild. Resolves ticket 4014.
7012 - Change the default required uptime for a relay to be accepted as
7013 a HSDir (hidden service directory) from 24 hours to 25 hours.
7014 Improves on 0.2.0.10-alpha; resolves ticket 2649.
7015 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
7016 authorities to abstain from voting on assignment of the HSDir
7017 consensus flag. Related to bug 2649.
7018 - Update to the September 6 2011 Maxmind GeoLite Country database.
7020 o Minor bugfixes (documentation and log messages):
7021 - Correct the man page to explain that HashedControlPassword and
7022 CookieAuthentication can both be set, in which case either method
7023 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
7024 when we decided to allow these config options to both be set. Issue
7026 - Demote the 'replay detected' log message emitted when a hidden
7027 service receives the same Diffie-Hellman public key in two different
7028 INTRODUCE2 cells to info level. A normal Tor client can cause that
7029 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
7030 fixes part of bug 2442.
7031 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
7032 level. There is nothing that a hidden service's operator can do
7033 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
7035 - Clarify a log message specifying the characters permitted in
7036 HiddenServiceAuthorizeClient client names. Previously, the log
7037 message said that "[A-Za-z0-9+-_]" were permitted; that could have
7038 given the impression that every ASCII character between "+" and "_"
7039 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
7042 - Provide a substitute implementation of lround() for MSVC, which
7043 apparently lacks it. Patch from Gisle Vanem.
7044 - Clean up some code issues that prevented Tor from building on older
7045 BSDs. Fixes bug 3894; reported by "grarpamp".
7046 - Search for a platform-specific version of "ar" when cross-compiling.
7047 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
7050 Changes in version 0.2.3.3-alpha - 2011-09-01
7051 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
7052 security, and provides client-side support for the microdescriptor
7053 and optimistic data features introduced earlier in the 0.2.3.x
7054 series. It also includes numerous critical bugfixes in the (optional)
7055 bufferevent-based networking backend.
7057 o Major features (stream isolation):
7058 - You can now configure Tor so that streams from different
7059 applications are isolated on different circuits, to prevent an
7060 attacker who sees your streams as they leave an exit node from
7061 linking your sessions to one another. To do this, choose some way
7062 to distinguish the applications: have them connect to different
7063 SocksPorts, or have one of them use SOCKS4 while the other uses
7064 SOCKS5, or have them pass different authentication strings to the
7065 SOCKS proxy. Then, use the new SocksPort syntax to configure the
7066 degree of isolation you need. This implements Proposal 171.
7067 - There's a new syntax for specifying multiple client ports (such as
7068 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
7069 multiple *Port entries with full addr:port syntax on each.
7070 The old *ListenAddress format is still supported, but you can't
7071 mix it with the new *Port syntax.
7073 o Major features (other):
7074 - Enable microdescriptor fetching by default for clients. This allows
7075 clients to download a much smaller amount of directory information.
7076 To disable it (and go back to the old-style consensus and
7077 descriptors), set "UseMicrodescriptors 0" in your torrc file.
7078 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
7079 "PortForwarding" config option), now supports Windows.
7080 - When using an exit relay running 0.2.3.x, clients can now
7081 "optimistically" send data before the exit relay reports that
7082 the stream has opened. This saves a round trip when starting
7083 connections where the client speaks first (such as web browsing).
7084 This behavior is controlled by a consensus parameter (currently
7085 disabled). To turn it on or off manually, use the "OptimisticData"
7086 torrc option. Implements proposal 181; code by Ian Goldberg.
7088 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
7089 - When using IOCP on Windows, we need to enable Libevent windows
7091 - The IOCP backend now works even when the user has not specified
7092 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
7093 Fixes part of bug 3752.
7094 - Correctly record the bytes we've read and written when using
7095 bufferevents, so that we can include them in our bandwidth history
7096 and advertised bandwidth. Fixes bug 3803.
7097 - Apply rate-limiting only at the bottom of a chain of filtering
7098 bufferevents. This prevents us from filling up internal read
7099 buffers and violating rate-limits when filtering bufferevents
7100 are enabled. Fixes part of bug 3804.
7101 - Add high-watermarks to the output buffers for filtered
7102 bufferevents. This prevents us from filling up internal write
7103 buffers and wasting CPU cycles when filtering bufferevents are
7104 enabled. Fixes part of bug 3804.
7105 - Correctly notice when data has been written from a bufferevent
7106 without flushing it completely. Fixes bug 3805.
7107 - Fix a bug where server-side tunneled bufferevent-based directory
7108 streams would get closed prematurely. Fixes bug 3814.
7109 - Fix a use-after-free error with per-connection rate-limiting
7110 buckets. Fixes bug 3888.
7112 o Major bugfixes (also part of 0.2.2.31-rc):
7113 - If we're configured to write our ControlPorts to disk, only write
7114 them after switching UID and creating the data directory. This way,
7115 we don't fail when starting up with a nonexistent DataDirectory
7116 and a ControlPortWriteToFile setting based on that directory. Fixes
7117 bug 3747; bugfix on Tor 0.2.2.26-beta.
7120 - Added a new CONF_CHANGED event so that controllers can be notified
7121 of any configuration changes made by other controllers, or by the
7122 user. Implements ticket 1692.
7123 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
7124 leak when using bufferevents, and lets Libevent worry about how to
7125 best copy data out of a buffer.
7126 - Replace files in stats/ rather than appending to them. Now that we
7127 include statistics in extra-info descriptors, it makes no sense to
7128 keep old statistics forever. Implements ticket 2930.
7130 o Minor features (build compatibility):
7131 - Limited, experimental support for building with nmake and MSVC.
7132 - Provide a substitute implementation of lround() for MSVC, which
7133 apparently lacks it. Patch from Gisle Vanem.
7135 o Minor features (also part of 0.2.2.31-rc):
7136 - Update to the August 2 2011 Maxmind GeoLite Country database.
7138 o Minor bugfixes (on 0.2.3.x-alpha):
7139 - Fix a spurious warning when parsing SOCKS requests with
7140 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
7141 - Get rid of a harmless warning that could happen on relays running
7142 with bufferevents. The warning was caused by someone doing an http
7143 request to a relay's orport. Also don't warn for a few related
7144 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
7146 o Minor bugfixes (on 2.2.x and earlier):
7147 - Correct the man page to explain that HashedControlPassword and
7148 CookieAuthentication can both be set, in which case either method
7149 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
7150 when we decided to allow these config options to both be set. Issue
7152 - The "--quiet" and "--hush" options now apply not only to Tor's
7153 behavior before logs are configured, but also to Tor's behavior in
7154 the absense of configured logs. Fixes bug 3550; bugfix on
7157 o Minor bugfixes (also part of 0.2.2.31-rc):
7158 - Write several files in text mode, on OSes that distinguish text
7159 mode from binary mode (namely, Windows). These files are:
7160 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
7161 that collect those statistics; 'client_keys' and 'hostname' for
7162 hidden services that use authentication; and (in the tor-gencert
7163 utility) newly generated identity and signing keys. Previously,
7164 we wouldn't specify text mode or binary mode, leading to an
7165 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
7166 the DirRecordUsageByCountry option which would have triggered
7167 the assertion failure was added), although this assertion failure
7168 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
7169 - Selectively disable deprecation warnings on OS X because Lion
7170 started deprecating the shipped copy of openssl. Fixes bug 3643.
7171 - Remove an extra pair of quotation marks around the error
7172 message in control-port STATUS_GENERAL BUG events. Bugfix on
7173 0.1.2.6-alpha; fixes bug 3732.
7174 - When unable to format an address as a string, report its value
7175 as "???" rather than reusing the last formatted address. Bugfix
7178 o Code simplifications and refactoring:
7179 - Rewrite the listener-selection logic so that parsing which ports
7180 we want to listen on is now separate from binding to the ports
7184 - Building Tor with bufferevent support now requires Libevent
7185 2.0.13-stable or later. Previous versions of Libevent had bugs in
7186 SSL-related bufferevents and related issues that would make Tor
7187 work badly with bufferevents. Requiring 2.0.13-stable also allows
7188 Tor with bufferevents to take advantage of Libevent APIs
7189 introduced after 2.0.8-rc.
7192 Changes in version 0.2.2.32 - 2011-08-27
7193 The Tor 0.2.2 release series is dedicated to the memory of Andreas
7194 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
7195 a founder of the PETS community, a leader in our field, a mentor,
7196 and a friend. He left us with these words: "I had the possibility
7197 to contribute to this world that is not as it should be. I hope I
7198 could help in some areas to make the world a better place, and that
7199 I could also encourage other people to be engaged in improving the
7200 world. Please, stay engaged. This world needs you, your love, your
7201 initiative -- now I cannot be part of that anymore."
7203 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
7204 ready. More than two years in the making, this release features improved
7205 client performance and hidden service reliability, better compatibility
7206 for Android, correct behavior for bridges that listen on more than
7207 one address, more extensible and flexible directory object handling,
7208 better reporting of network statistics, improved code security, and
7209 many many other features and bugfixes.
7212 Changes in version 0.2.2.31-rc - 2011-08-17
7213 Tor 0.2.2.31-rc is the second and hopefully final release candidate
7214 for the Tor 0.2.2.x series.
7217 - Remove an extra pair of quotation marks around the error
7218 message in control-port STATUS_GENERAL BUG events. Bugfix on
7219 0.1.2.6-alpha; fixes bug 3732.
7220 - If we're configured to write our ControlPorts to disk, only write
7221 them after switching UID and creating the data directory. This way,
7222 we don't fail when starting up with a nonexistent DataDirectory
7223 and a ControlPortWriteToFile setting based on that directory. Fixes
7224 bug 3747; bugfix on Tor 0.2.2.26-beta.
7227 - Update to the August 2 2011 Maxmind GeoLite Country database.
7230 - Allow GETINFO fingerprint to return a fingerprint even when
7231 we have not yet built a router descriptor. Fixes bug 3577;
7232 bugfix on 0.2.0.1-alpha.
7233 - Write several files in text mode, on OSes that distinguish text
7234 mode from binary mode (namely, Windows). These files are:
7235 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
7236 that collect those statistics; 'client_keys' and 'hostname' for
7237 hidden services that use authentication; and (in the tor-gencert
7238 utility) newly generated identity and signing keys. Previously,
7239 we wouldn't specify text mode or binary mode, leading to an
7240 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
7241 the DirRecordUsageByCountry option which would have triggered
7242 the assertion failure was added), although this assertion failure
7243 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
7244 - Selectively disable deprecation warnings on OS X because Lion
7245 started deprecating the shipped copy of openssl. Fixes bug 3643.
7246 - When unable to format an address as a string, report its value
7247 as "???" rather than reusing the last formatted address. Bugfix
7251 Changes in version 0.2.3.2-alpha - 2011-07-18
7252 Tor 0.2.3.2-alpha introduces two new experimental features:
7253 microdescriptors and pluggable transports. It also continues cleaning
7254 up a variety of recently introduced features.
7257 - Clients can now use microdescriptors instead of regular descriptors
7258 to build circuits. Microdescriptors are authority-generated
7259 summaries of regular descriptors' contents, designed to change
7260 very rarely (see proposal 158 for details). This feature is
7261 designed to save bandwidth, especially for clients on slow internet
7262 connections. It's off by default for now, since nearly no caches
7263 support it, but it will be on-by-default for clients in a future
7264 version. You can use the UseMicrodescriptors option to turn it on.
7265 - Tor clients using bridges can now be configured to use a separate
7266 'transport' proxy for each bridge. This approach helps to resist
7267 censorship by allowing bridges to use protocol obfuscation
7268 plugins. It implements part of proposal 180. Implements ticket 2841.
7269 - While we're trying to bootstrap, record how many TLS connections
7270 fail in each state, and report which states saw the most failures
7271 in response to any bootstrap failures. This feature may speed up
7272 diagnosis of censorship events. Implements ticket 3116.
7274 o Major bugfixes (on 0.2.3.1-alpha):
7275 - When configuring a large set of nodes in EntryNodes (as with
7276 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
7277 random subset to be guards, and choose them in random
7278 order. Fixes bug 2798.
7279 - Tor could crash when remembering a consensus in a non-used consensus
7280 flavor without having a current consensus set. Fixes bug 3361.
7281 - Comparing an unknown address to a microdescriptor's shortened exit
7282 policy would always give a "rejected" result. Fixes bug 3599.
7283 - Using microdescriptors as a client no longer prevents Tor from
7284 uploading and downloading hidden service descriptors. Fixes
7288 - Allow nameservers with IPv6 address. Resolves bug 2574.
7289 - Accept attempts to include a password authenticator in the
7290 handshake, as supported by SOCKS5. This handles SOCKS clients that
7291 don't know how to omit a password when authenticating. Resolves
7293 - When configuring a large set of nodes in EntryNodes, and there are
7294 enough of them listed as Guard so that we don't need to consider
7295 the non-guard entries, prefer the ones listed with the Guard flag.
7296 - Check for and recover from inconsistency in the microdescriptor
7297 cache. This will make it harder for us to accidentally free a
7298 microdescriptor without removing it from the appropriate data
7299 structures. Fixes issue 3135; issue noted by "wanoskarnet".
7300 - Log SSL state transitions at log level DEBUG, log domain
7301 HANDSHAKE. This can be useful for debugging censorship events.
7302 Implements ticket 3264.
7303 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
7304 implements ticket 3439.
7306 o Minor bugfixes (on 0.2.3.1-alpha):
7307 - Do not free all general-purpose regular descriptors just
7308 because microdescriptor use is enabled. Fixes bug 3113.
7309 - Correctly link libevent_openssl when --enable-static-libevent
7310 is passed to configure. Fixes bug 3118.
7311 - Bridges should not complain during their heartbeat log messages that
7312 they are unlisted in the consensus: that's more or less the point
7313 of being a bridge. Fixes bug 3183.
7314 - Report a SIGNAL event to controllers when acting on a delayed
7315 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
7316 event to the controller if we acted on a SIGNAL NEWNYM command
7317 immediately, and otherwise not report a SIGNAL event for the
7318 command at all. Fixes bug 3349.
7319 - Fix a crash when handling the SIGNAL controller command or
7320 reporting ERR-level status events with bufferevents enabled. Found
7321 by Robert Ransom. Fixes bug 3367.
7322 - Always ship the tor-fw-helper manpage in our release tarballs.
7323 Fixes bug 3389. Reported by Stephen Walker.
7324 - Fix a class of double-mark-for-close bugs when bufferevents
7325 are enabled. Fixes bug 3403.
7326 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
7327 - Add SIGNAL to the list returned by the 'GETINFO events/names'
7328 control-port command. Fixes part of bug 3465.
7329 - Prevent using negative indices during unit test runs when read_all()
7330 fails. Spotted by coverity.
7331 - Fix a rare memory leak when checking the nodelist without it being
7332 present. Found by coverity.
7333 - Only try to download a microdescriptor-flavored consensus from
7334 a directory cache that provides them.
7336 o Minor bugfixes (on 0.2.2.x and earlier):
7337 - Assert that hidden-service-related operations are not performed
7338 using single-hop circuits. Previously, Tor would assert that
7339 client-side streams are not attached to single-hop circuits,
7340 but not that other sensitive operations on the client and service
7341 side are not performed using single-hop circuits. Fixes bug 3332;
7343 - Don't publish a new relay descriptor when we reload our onion key,
7344 unless the onion key has actually changed. Fixes bug 3263 and
7345 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
7346 - Allow GETINFO fingerprint to return a fingerprint even when
7347 we have not yet built a router descriptor. Fixes bug 3577;
7348 bugfix on 0.2.0.1-alpha.
7349 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
7350 on 0.2.2.4-alpha; fixes bug 3427.
7352 o Code simplification and refactoring:
7353 - Use tor_sscanf() in place of scanf() in more places through the
7354 code. This makes us a little more locale-independent, and
7355 should help shut up code-analysis tools that can't tell
7356 a safe sscanf string from a dangerous one.
7357 - Use tt_assert(), not tor_assert(), for checking for test failures.
7358 This makes the unit tests more able to go on in the event that
7360 - Split connection_about_to_close() into separate functions for each
7364 - On Windows, we now define the _WIN32_WINNT macros only if they
7365 are not already defined. This lets the person building Tor decide,
7366 if they want, to require a later version of Windows.
7369 Changes in version 0.2.2.30-rc - 2011-07-07
7370 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
7371 series. It fixes a few smaller bugs, but generally appears stable.
7372 Please test it and let us know whether it is!
7375 - Send a SUCCEEDED stream event to the controller when a reverse
7376 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
7377 discovered by katmagic.
7378 - Always NUL-terminate the sun_path field of a sockaddr_un before
7379 passing it to the kernel. (Not a security issue: kernels are
7380 smart enough to reject bad sockaddr_uns.) Found by Coverity;
7381 CID #428. Bugfix on Tor 0.2.0.3-alpha.
7382 - Don't stack-allocate the list of supplementary GIDs when we're
7383 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
7384 could take up to 256K, which is way too much stack. Found by
7385 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
7386 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
7387 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
7388 fixes part of bug 3465.
7389 - Fix a memory leak when receiving a descriptor for a hidden
7390 service we didn't ask for. Found by Coverity; CID #30. Bugfix
7394 - Update to the July 1 2011 Maxmind GeoLite Country database.
7397 Changes in version 0.2.2.29-beta - 2011-06-20
7398 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
7399 have bridge lines in their torrc but don't want to use them; gets
7400 us closer to having the control socket feature working on Debian;
7401 and fixes a variety of smaller bugs.
7404 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
7405 When we changed the default behavior to "use bridges if any
7406 are listed in the torrc", we surprised users who had bridges
7407 in their torrc files but who didn't actually want to use them.
7408 Partial resolution for bug 3354.
7411 - Don't attach new streams to old rendezvous circuits after SIGNAL
7412 NEWNYM. Previously, we would keep using an existing rendezvous
7413 circuit if it remained open (i.e. if it were kept open by a
7414 long-lived stream, or if a new stream were attached to it before
7415 Tor could notice that it was old and no longer in use). Bugfix on
7416 0.1.1.15-rc; fixes bug 3375.
7419 - Fix a bug when using ControlSocketsGroupWritable with User. The
7420 directory's group would be checked against the current group, not
7421 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
7422 bugfix on 0.2.2.26-beta.
7423 - Make connection_printf_to_buf()'s behavior sane. Its callers
7424 expect it to emit a CRLF iff the format string ends with CRLF;
7425 it actually emitted a CRLF iff (a) the format string ended with
7426 CRLF or (b) the resulting string was over 1023 characters long or
7427 (c) the format string did not end with CRLF *and* the resulting
7428 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
7429 fixes part of bug 3407.
7430 - Make send_control_event_impl()'s behavior sane. Its callers
7431 expect it to always emit a CRLF at the end of the string; it
7432 might have emitted extra control characters as well. Bugfix on
7433 0.1.1.9-alpha; fixes another part of bug 3407.
7434 - Make crypto_rand_int() check the value of its input correctly.
7435 Previously, it accepted values up to UINT_MAX, but could return a
7436 negative number if given a value above INT_MAX+1. Found by George
7437 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
7438 - Avoid a segfault when reading a malformed circuit build state
7439 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
7441 - When asked about a DNS record type we don't support via a
7442 client DNSPort, reply with NOTIMPL rather than an empty
7443 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
7444 - Fix a rare memory leak during stats writing. Found by coverity.
7447 - Update to the June 1 2011 Maxmind GeoLite Country database.
7449 o Code simplifications and refactoring:
7450 - Remove some dead code as indicated by coverity.
7451 - Remove a few dead assignments during router parsing. Found by
7453 - Add some forgotten return value checks during unit tests. Found
7455 - Don't use 1-bit wide signed bit fields. Found by coverity.
7458 Changes in version 0.2.2.28-beta - 2011-06-04
7459 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
7460 fixed a big bug in whether relays stay in the consensus consistently,
7461 we moved closer to handling bridges and hidden services correctly,
7462 and we started the process of better handling the dreaded "my Vidalia
7463 died, and now my Tor demands a password when I try to reconnect to it"
7467 - Don't decide to make a new descriptor when receiving a HUP signal.
7468 This bug has caused a lot of 0.2.2.x relays to disappear from the
7469 consensus periodically. Fixes the most common case of triggering
7470 bug 1810; bugfix on 0.2.2.7-alpha.
7471 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
7472 - Don't try to build descriptors if "ORPort auto" is set and we
7473 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
7475 - Resolve a crash that occurred when setting BridgeRelay to 1 with
7476 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
7477 - Apply circuit timeouts to opened hidden-service-related circuits
7478 based on the correct start time. Previously, we would apply the
7479 circuit build timeout based on time since the circuit's creation;
7480 it was supposed to be applied based on time since the circuit
7481 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
7482 - Use the same circuit timeout for client-side introduction
7483 circuits as for other four-hop circuits, rather than the timeout
7484 for single-hop directory-fetch circuits; the shorter timeout may
7485 have been appropriate with the static circuit build timeout in
7486 0.2.1.x and earlier, but caused many hidden service access attempts
7487 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
7488 on 0.2.2.2-alpha; fixes another part of bug 1297.
7489 - In ticket 2511 we fixed a case where you could use an unconfigured
7490 bridge if you had configured it as a bridge the last time you ran
7491 Tor. Now fix another edge case: if you had configured it as a bridge
7492 but then switched to a different bridge via the controller, you
7493 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
7497 - Add an __OwningControllerProcess configuration option and a
7498 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
7499 that when it exits, Tor will shut down. Implements feature 3049.
7500 - If "UseBridges 1" is set and no bridges are configured, Tor will
7501 now refuse to build any circuits until some bridges are set.
7502 If "UseBridges auto" is set, Tor will use bridges if they are
7503 configured and we are not running as a server, but otherwise will
7504 make circuits as usual. The new default is "auto". Patch by anonym,
7505 so the Tails LiveCD can stop automatically revealing you as a Tor
7509 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
7510 - Remove a trailing asterisk from "exit-policy/default" in the
7511 output of the control port command "GETINFO info/names". Bugfix
7513 - Use a wide type to hold sockets when built for 64-bit Windows builds.
7515 - Warn when the user configures two HiddenServiceDir lines that point
7516 to the same directory. Bugfix on 0.0.6 (the version introducing
7517 HiddenServiceDir); fixes bug 3289.
7518 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
7519 part of bug 2748; bugfix on 0.2.0.10-alpha.
7520 - Log malformed requests for rendezvous descriptors as protocol
7521 warnings, not warnings. Also, use a more informative log message
7522 in case someone sees it at log level warning without prior
7523 info-level messages. Fixes the other part of bug 2748; bugfix
7525 - Clear the table recording the time of the last request for each
7526 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
7527 Previously, we would clear our HS descriptor cache on SIGNAL
7528 NEWNYM, but if we had previously retrieved a descriptor (or tried
7529 to) from every directory responsible for it, we would refuse to
7530 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
7532 - Fix a log message that said "bits" while displaying a value in
7533 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
7535 - When checking for 1024-bit keys, check for 1024 bits, not 128
7536 bytes. This allows Tor to correctly discard keys of length 1017
7537 through 1023. Bugfix on 0.0.9pre5.
7540 - Relays now log the reason for publishing a new relay descriptor,
7541 so we have a better chance of hunting down instances of bug 1810.
7542 Resolves ticket 3252.
7543 - Revise most log messages that refer to nodes by nickname to
7544 instead use the "$key=nickname at address" format. This should be
7545 more useful, especially since nicknames are less and less likely
7546 to be unique. Resolves ticket 3045.
7547 - Log (at info level) when purging pieces of hidden-service-client
7548 state because of SIGNAL NEWNYM.
7551 - Remove undocumented option "-F" from tor-resolve: it hasn't done
7552 anything since 0.2.1.16-rc.
7555 Changes in version 0.2.2.27-beta - 2011-05-18
7556 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
7557 release, and also adds a few more general bugfixes.
7560 - Fix a crash bug when changing bridges in a running Tor process.
7561 Fixes bug 3213; bugfix on 0.2.2.26-beta.
7562 - When the controller configures a new bridge, don't wait 10 to 60
7563 seconds before trying to fetch its descriptor. Bugfix on
7564 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
7567 - Require that onion keys have exponent 65537 in microdescriptors too.
7568 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
7569 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
7570 Changed the limit to 512 characters by removing base64 newlines.
7571 Fixes bug 2752. Fix by Michael Yakubovich.
7572 - When a client starts or stops using bridges, never use a circuit
7573 that was built before the configuration change. This behavior could
7574 put at risk a user who uses bridges to ensure that her traffic
7575 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
7579 Changes in version 0.2.2.26-beta - 2011-05-17
7580 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
7581 also introduces a new "socksport auto" approach that should make it
7582 easier to run multiple Tors on the same system, and does a lot of
7583 cleanup to get us closer to a release candidate.
7585 o Security/privacy fixes:
7586 - Replace all potentially sensitive memory comparison operations
7587 with versions whose runtime does not depend on the data being
7588 compared. This will help resist a class of attacks where an
7589 adversary can use variations in timing information to learn
7590 sensitive data. Fix for one case of bug 3122. (Safe memcmp
7591 implementation by Robert Ransom based partially on code by DJB.)
7592 - When receiving a hidden service descriptor, check that it is for
7593 the hidden service we wanted. Previously, Tor would store any
7594 hidden service descriptors that a directory gave it, whether it
7595 wanted them or not. This wouldn't have let an attacker impersonate
7596 a hidden service, but it did let directories pre-seed a client
7597 with descriptors that it didn't want. Bugfix on 0.0.6.
7598 - On SIGHUP, do not clear out all TrackHostExits mappings, client
7599 DNS cache entries, and virtual address mappings: that's what
7600 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
7603 - The options SocksPort, ControlPort, and so on now all accept a
7604 value "auto" that opens a socket on an OS-selected port. A
7605 new ControlPortWriteToFile option tells Tor to write its
7606 actual control port or ports to a chosen file. If the option
7607 ControlPortFileGroupReadable is set, the file is created as
7608 group-readable. Now users can run two Tor clients on the same
7609 system without needing to manually mess with parameters. Resolves
7610 part of ticket 3076.
7611 - Set SO_REUSEADDR on all sockets, not just listeners. This should
7612 help busy exit nodes avoid running out of useable ports just
7613 because all the ports have been used in the near past. Resolves
7617 - New "GETINFO net/listeners/(type)" controller command to return
7618 a list of addresses and ports that are bound for listeners for a
7619 given connection type. This is useful when the user has configured
7620 "SocksPort auto" and the controller needs to know which port got
7621 chosen. Resolves another part of ticket 3076.
7622 - Add a new ControlSocketsGroupWritable configuration option: when
7623 it is turned on, ControlSockets are group-writeable by the default
7624 group of the current user. Patch by Jérémy Bobbio; implements
7626 - Tor now refuses to create a ControlSocket in a directory that is
7627 world-readable (or group-readable if ControlSocketsGroupWritable
7628 is 0). This is necessary because some operating systems do not
7629 enforce permissions on an AF_UNIX sockets. Permissions on the
7630 directory holding the socket, however, seems to work everywhere.
7631 - Rate-limit a warning about failures to download v2 networkstatus
7632 documents. Resolves part of bug 1352.
7633 - Backport code from 0.2.3.x that allows directory authorities to
7634 clean their microdescriptor caches. Needed to resolve bug 2230.
7635 - When an HTTPS proxy reports "403 Forbidden", we now explain
7636 what it means rather than calling it an unexpected status code.
7637 Closes bug 2503. Patch from Michael Yakubovich.
7638 - Update to the May 1 2011 Maxmind GeoLite Country database.
7641 - Authorities now clean their microdesc cache periodically and when
7642 reading from disk initially, not only when adding new descriptors.
7643 This prevents a bug where we could lose microdescriptors. Bugfix
7644 on 0.2.2.6-alpha. Fixes bug 2230.
7645 - Do not crash when our configuration file becomes unreadable, for
7646 example due to a permissions change, between when we start up
7647 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
7649 - Avoid a bug that would keep us from replacing a microdescriptor
7650 cache on Windows. (We would try to replace the file while still
7651 holding it open. That's fine on Unix, but Windows doesn't let us
7652 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
7653 - Add missing explanations for the authority-related torrc options
7654 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
7655 man page. Resolves issue 2379.
7656 - As an authority, do not upload our own vote or signature set to
7657 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
7658 it would get flagged as a duplicate. Resolves bug 3026.
7659 - Accept hidden service descriptors if we think we might be a hidden
7660 service directory, regardless of what our consensus says. This
7661 helps robustness, since clients and hidden services can sometimes
7662 have a more up-to-date view of the network consensus than we do,
7663 and if they think that the directory authorities list us a HSDir,
7664 we might actually be one. Related to bug 2732; bugfix on
7666 - When a controller changes TrackHostExits, remove mappings for
7667 hosts that should no longer have their exits tracked. Bugfix on
7669 - When a controller changes VirtualAddrNetwork, remove any mappings
7670 for hosts that were automapped to the old network. Bugfix on
7672 - When a controller changes one of the AutomapHosts* options, remove
7673 any mappings for hosts that should no longer be automapped. Bugfix
7675 - Do not reset the bridge descriptor download status every time we
7676 re-parse our configuration or get a configuration change. Fixes
7677 bug 3019; bugfix on 0.2.0.3-alpha.
7679 o Minor bugfixes (code cleanup):
7680 - When loading the microdesc journal, remember its current size.
7681 In 0.2.2, this helps prevent the microdesc journal from growing
7682 without limit on authorities (who are the only ones to use it in
7683 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
7684 Fix posted by "cypherpunks."
7685 - The microdesc journal is supposed to get rebuilt only if it is
7686 at least _half_ the length of the store, not _twice_ the length
7687 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
7688 - Fix a potential null-pointer dereference while computing a
7689 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
7691 - Avoid a possible null-pointer dereference when rebuilding the mdesc
7692 cache without actually having any descriptors to cache. Bugfix on
7693 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
7694 - If we fail to compute the identity digest of a v3 legacy keypair,
7695 warn, and don't use a buffer-full of junk instead. Bugfix on
7696 0.2.1.1-alpha; fixes bug 3106.
7697 - Resolve an untriggerable issue in smartlist_string_num_isin(),
7698 where if the function had ever in the future been used to check
7699 for the presence of a too-large number, it would have given an
7700 incorrect result. (Fortunately, we only used it for 16-bit
7701 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
7702 - Require that introduction point keys and onion handshake keys
7703 have a public exponent of 65537. Starts to fix bug 3207; bugfix
7707 - Caches no longer download and serve v2 networkstatus documents
7708 unless FetchV2Networkstatus flag is set: these documents haven't
7709 haven't been used by clients or relays since 0.2.0.x. Resolves
7713 Changes in version 0.2.3.1-alpha - 2011-05-05
7714 Tor 0.2.3.1-alpha adds some new experimental features, including support
7715 for an improved network IO backend, IOCP networking on Windows,
7716 microdescriptor caching, "fast-start" support for streams, and automatic
7717 home router configuration. There are also numerous internal improvements
7718 to try to make the code easier for developers to work with.
7720 This is the first alpha release in a new series, so expect there to be
7721 bugs. Users who would rather test out a more stable branch should
7722 stay with 0.2.2.x for now.
7725 - Tor can now optionally build with the "bufferevents" buffered IO
7726 backend provided by Libevent 2. To use this feature, make sure you
7727 have the latest possible version of Libevent, and pass the
7728 --enable-bufferevents flag to configure when building Tor from
7729 source. This feature will make our networking code more flexible,
7730 let us stack layers on each other, and let us use more efficient
7731 zero-copy transports where available.
7732 - As an experimental feature, Tor can use IOCP for networking on Windows.
7733 Once this code is tuned and optimized, it promises much better
7734 performance than the select-based backend we've used in the past. To
7735 try this feature, you must build Tor with Libevent 2, configure Tor
7736 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
7737 your torrc. There are known bugs here: only try this if you can help
7738 debug it as it breaks.
7739 - The EntryNodes option can now include country codes like {de} or IP
7740 addresses or network masks. Previously we had disallowed these options
7741 because we didn't have an efficient way to keep the list up to
7742 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
7743 - Exit nodes now accept and queue data on not-yet-connected streams.
7744 Previously, the client wasn't allowed to send data until the stream was
7745 connected, which slowed down all connections. This change will enable
7746 clients to perform a "fast-start" on streams and send data without
7747 having to wait for a confirmation that the stream has opened. (Patch
7748 from Ian Goldberg; implements the server side of Proposal 174.)
7749 - Tor now has initial support for automatic port mapping on the many
7750 home routers that support NAT-PMP or UPnP. (Not yet supported on
7751 Windows). To build the support code, you'll need to have libnatpnp
7752 library and/or the libminiupnpc library, and you'll need to enable the
7753 feature specifically by passing "--enable-upnp" and/or
7754 "--enable-natpnp" to configure. To turn it on, use the new
7755 PortForwarding option.
7756 - Caches now download, cache, and serve multiple "flavors" of the
7757 consensus, including a flavor that describes microdescriptors.
7758 - Caches now download, cache, and serve microdescriptors -- small
7759 summaries of router descriptors that are authenticated by all of the
7760 directory authorities. Once enough caches are running this code,
7761 clients will be able to save significant amounts of directory bandwidth
7762 by downloading microdescriptors instead of router descriptors.
7765 - Make logging resolution configurable with a new LogTimeGranularity
7766 option, and change the default from 1 millisecond to 1 second.
7767 Implements enhancement 1668.
7768 - We log which torrc file we're using on startup. Implements ticket
7770 - Ordinarily, Tor does not count traffic from private addresses (like
7771 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
7772 There is now a new option, CountPrivateBandwidth, to disable this
7773 behavior. Patch from Daniel Cagara.
7774 - New --enable-static-tor configure option for building Tor as
7775 statically as possible. Idea, general hackery and thoughts from
7776 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
7778 - If you set the NumCPUs option to 0, Tor will now try to detect how
7779 many CPUs you have. This is the new default behavior.
7780 - Turn on directory request statistics by default and include them in
7781 extra-info descriptors. Don't break if we have no GeoIP database.
7782 - Relays that set "ConnDirectionStatistics 1" write statistics on the
7783 bidirectional use of connections to disk every 24 hours.
7784 - Add a GeoIP file digest to the extra-info descriptor. Implements
7786 - The NodeFamily option -- which let you declare that you want to
7787 consider nodes to be part of a family whether they list themselves
7788 that way or not -- now allows IP address ranges and country codes.
7789 - Add a new 'Heartbeat' log message type to periodically log a message
7790 describing Tor's status at level Notice. This feature is meant for
7791 operators who log at notice, and want to make sure that their Tor
7792 server is still working. Implementation by George Kadianakis.
7794 o Minor bugfixes (on 0.2.2.25-alpha):
7795 - When loading the microdesc journal, remember its current size.
7796 In 0.2.2, this helps prevent the microdesc journal from growing
7797 without limit on authorities (who are the only ones to use it in
7798 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
7799 Fix posted by "cypherpunks."
7800 - The microdesc journal is supposed to get rebuilt only if it is
7801 at least _half_ the length of the store, not _twice_ the length
7802 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
7803 - If as an authority we fail to compute the identity digest of a v3
7804 legacy keypair, warn, and don't use a buffer-full of junk instead.
7805 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
7806 - Authorities now clean their microdesc cache periodically and when
7807 reading from disk initially, not only when adding new descriptors.
7808 This prevents a bug where we could lose microdescriptors. Bugfix
7811 o Minor features (controller):
7812 - Add a new SIGNAL event to the controller interface so that
7813 controllers can be notified when Tor handles a signal. Resolves
7814 issue 1955. Patch by John Brooks.
7815 - Add a new GETINFO option to get total bytes read and written. Patch
7816 from pipe, revised by atagar. Resolves ticket 2345.
7817 - Implement some GETINFO controller fields to provide information about
7818 the Tor process's pid, euid, username, and resource limits.
7821 - Our build system requires automake 1.6 or later to create the
7822 Makefile.in files. Previously, you could have used 1.4.
7823 This only affects developers and people building Tor from git;
7824 people who build Tor from the source distribution without changing
7825 the Makefile.am files should be fine.
7826 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
7827 so on. This is more robust against some of the failure modes
7828 associated with running the autotools pieces on their own.
7830 o Minor packaging issues:
7831 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
7832 already created. Patch from Andreas Stieger. Fixes bug 2573.
7834 o Code simplifications and refactoring:
7835 - A major revision to our internal node-selecting and listing logic.
7836 Tor already had at least two major ways to look at the question of
7837 "which Tor servers do we know about": a list of router descriptors,
7838 and a list of entries in the current consensus. With
7839 microdescriptors, we're adding a third. Having so many systems
7840 without an abstraction layer over them was hurting the codebase.
7841 Now, we have a new "node_t" abstraction that presents a consistent
7842 interface to a client's view of a Tor node, and holds (nearly) all
7843 of the mutable state formerly in routerinfo_t and routerstatus_t.
7844 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
7845 no longer link against Libevent: they never used it, but
7846 our library structure used to force them to link it.
7849 - Remove some old code to work around even older versions of Tor that
7850 used forked processes to handle DNS requests. Such versions of Tor
7851 are no longer in use as servers.
7853 o Documentation fixes:
7854 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
7855 - Add missing documentation for the authority-related torrc options
7856 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
7860 Changes in version 0.2.2.25-alpha - 2011-04-29
7861 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
7862 robust, routers no longer overreport their bandwidth, Win7 should crash
7863 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
7864 now prevents hidden service-related activity from being linkable. It
7865 provides more information to Vidalia so you can see if your bridge is
7866 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
7867 StrictNodes configuration options to make them more reliable, more
7868 understandable, and more regularly applied. If you use those options,
7869 please see the revised documentation for them in the manual page.
7872 - Relays were publishing grossly inflated bandwidth values because
7873 they were writing their state files wrong--now they write the
7874 correct value. Also, resume reading bandwidth history from the
7875 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
7876 - Improve hidden service robustness: When we find that we have
7877 extended a hidden service's introduction circuit to a relay not
7878 listed as an introduction point in the HS descriptor we currently
7879 have, retry with an introduction point from the current
7880 descriptor. Previously we would just give up. Fixes bugs 1024 and
7881 1930; bugfix on 0.2.0.10-alpha.
7882 - Clients now stop trying to use an exit node associated with a given
7883 destination by TrackHostExits if they fail to reach that exit node.
7884 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
7885 - Fix crash bug on platforms where gmtime and localtime can return
7886 NULL. Windows 7 users were running into this one. Fixes part of bug
7887 2077. Bugfix on all versions of Tor. Found by boboper.
7889 o Security and stability fixes:
7890 - Don't double-free a parsable, but invalid, microdescriptor, even if
7891 it is followed in the blob we're parsing by an unparsable
7892 microdescriptor. Fixes an issue reported in a comment on bug 2954.
7893 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
7894 - If the Nickname configuration option isn't given, Tor would pick a
7895 nickname based on the local hostname as the nickname for a relay.
7896 Because nicknames are not very important in today's Tor and the
7897 "Unnamed" nickname has been implemented, this is now problematic
7898 behavior: It leaks information about the hostname without being
7899 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
7900 introduced the Unnamed nickname. Reported by tagnaq.
7901 - Fix an uncommon assertion failure when running with DNSPort under
7902 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
7903 - Avoid linkability based on cached hidden service descriptors: forget
7904 all hidden service descriptors cached as a client when processing a
7905 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
7908 - Export GeoIP information on bridge usage to controllers even if we
7909 have not yet been running for 24 hours. Now Vidalia bridge operators
7910 can get more accurate and immediate feedback about their
7911 contributions to the network.
7913 o Major features and bugfixes (node selection):
7914 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
7915 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
7916 options. Previously, we had been ambiguous in describing what
7917 counted as an "exit" node, and what operations exactly "StrictNodes
7918 0" would permit. This created confusion when people saw nodes built
7919 through unexpected circuits, and made it hard to tell real bugs from
7920 surprises. Now the intended behavior is:
7921 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
7922 a node that delivers user traffic outside the Tor network.
7923 . "Entry", in the context of EntryNodes, means a node used as the
7924 first hop of a multihop circuit. It doesn't include direct
7925 connections to directory servers.
7926 . "ExcludeNodes" applies to all nodes.
7927 . "StrictNodes" changes the behavior of ExcludeNodes only. When
7928 StrictNodes is set, Tor should avoid all nodes listed in
7929 ExcludeNodes, even when it will make user requests fail. When
7930 StrictNodes is *not* set, then Tor should follow ExcludeNodes
7931 whenever it can, except when it must use an excluded node to
7932 perform self-tests, connect to a hidden service, provide a
7933 hidden service, fulfill a .exit request, upload directory
7934 information, or fetch directory information.
7935 Collectively, the changes to implement the behavior fix bug 1090.
7936 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
7937 a node is listed in both, it's treated as excluded.
7938 - ExcludeNodes now applies to directory nodes -- as a preference if
7939 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
7940 Don't exclude all the directory authorities and set StrictNodes to 1
7941 unless you really want your Tor to break.
7942 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
7943 - ExcludeExitNodes now overrides .exit requests.
7944 - We don't use bridges listed in ExcludeNodes.
7945 - When StrictNodes is 1:
7946 . We now apply ExcludeNodes to hidden service introduction points
7947 and to rendezvous points selected by hidden service users. This
7948 can make your hidden service less reliable: use it with caution!
7949 . If we have used ExcludeNodes on ourself, do not try relay
7950 reachability self-tests.
7951 . If we have excluded all the directory authorities, we will not
7952 even try to upload our descriptor if we're a relay.
7953 . Do not honor .exit requests to an excluded node.
7954 - Remove a misfeature that caused us to ignore the Fast/Stable flags
7955 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
7956 - When the set of permitted nodes changes, we now remove any mappings
7957 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
7959 - We never cannibalize a circuit that had excluded nodes on it, even
7960 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
7961 - Revert a change where we would be laxer about attaching streams to
7962 circuits than when building the circuits. This was meant to prevent
7963 a set of bugs where streams were never attachable, but our improved
7964 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
7965 - Keep track of how many times we launch a new circuit to handle a
7966 given stream. Too many launches could indicate an inconsistency
7967 between our "launch a circuit to handle this stream" logic and our
7968 "attach this stream to one of the available circuits" logic.
7969 - Improve log messages related to excluded nodes.
7972 - Fix a spurious warning when moving from a short month to a long
7973 month on relays with month-based BandwidthAccounting. Bugfix on
7974 0.2.2.17-alpha; fixes bug 3020.
7975 - When a client finds that an origin circuit has run out of 16-bit
7976 stream IDs, we now mark it as unusable for new streams. Previously,
7977 we would try to close the entire circuit. Bugfix on 0.0.6.
7978 - Add a forgotten cast that caused a compile warning on OS X 10.6.
7979 Bugfix on 0.2.2.24-alpha.
7980 - Be more careful about reporting the correct error from a failed
7981 connect() system call. Under some circumstances, it was possible to
7982 look at an incorrect value for errno when sending the end reason.
7983 Bugfix on 0.1.0.1-rc.
7984 - Correctly handle an "impossible" overflow cases in connection byte
7985 counting, where we write or read more than 4GB on an edge connection
7986 in a single second. Bugfix on 0.1.2.8-beta.
7987 - Correct the warning displayed when a rendezvous descriptor exceeds
7988 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
7990 - Clients and hidden services now use HSDir-flagged relays for hidden
7991 service descriptor downloads and uploads even if the relays have no
7992 DirPort set and the client has disabled TunnelDirConns. This will
7993 eventually allow us to give the HSDir flag to relays with no
7994 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
7995 - Downgrade "no current certificates known for authority" message from
7996 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
7997 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
7998 2917. Bugfix on 0.1.1.1-alpha.
7999 - Only limit the lengths of single HS descriptors, even when multiple
8000 HS descriptors are published to an HSDir relay in a single POST
8001 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
8002 - Write the current time into the LastWritten line in our state file,
8003 rather than the time from the previous write attempt. Also, stop
8004 trying to use a time of -1 in our log statements. Fixes bug 3039;
8005 bugfix on 0.2.2.14-alpha.
8006 - Be more consistent in our treatment of file system paths. "~" should
8007 get expanded to the user's home directory in the Log config option.
8008 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
8009 feature for the -f and --DataDirectory options.
8012 - Make sure every relay writes a state file at least every 12 hours.
8013 Previously, a relay could go for weeks without writing its state
8014 file, and on a crash could lose its bandwidth history, capacity
8015 estimates, client country statistics, and so on. Addresses bug 3012.
8016 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
8017 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
8018 clients are already deprecated because of security bugs.
8019 - Don't allow v0 hidden service authorities to act as clients.
8020 Required by fix for bug 3000.
8021 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
8022 by fix for bug 3000.
8023 - Ensure that no empty [dirreq-](read|write)-history lines are added
8024 to an extrainfo document. Implements ticket 2497.
8026 o Code simplification and refactoring:
8027 - Remove workaround code to handle directory responses from servers
8028 that had bug 539 (they would send HTTP status 503 responses _and_
8029 send a body too). Since only server versions before
8030 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
8031 keep the workaround in place.
8032 - Remove the old 'fuzzy time' logic. It was supposed to be used for
8033 handling calculations where we have a known amount of clock skew and
8034 an allowed amount of unknown skew. But we only used it in three
8035 places, and we never adjusted the known/unknown skew values. This is
8036 still something we might want to do someday, but if we do, we'll
8037 want to do it differently.
8038 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
8039 None of the cases where we did this before were wrong, but by making
8040 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
8041 - Use GetTempDir to find the proper temporary directory location on
8042 Windows when generating temporary files for the unit tests. Patch by
8046 Changes in version 0.2.2.24-alpha - 2011-04-08
8047 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
8048 prevented Tor clients from effectively using "multihomed" bridges,
8049 that is, bridges that listen on multiple ports or IP addresses so users
8050 can continue to use some of their addresses even if others get blocked.
8053 - Fix a bug where bridge users who configure the non-canonical
8054 address of a bridge automatically switch to its canonical
8055 address. If a bridge listens at more than one address, it should be
8056 able to advertise those addresses independently and any non-blocked
8057 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
8059 - If you configured Tor to use bridge A, and then quit and
8060 configured Tor to use bridge B instead, it would happily continue
8061 to use bridge A if it's still reachable. While this behavior is
8062 a feature if your goal is connectivity, in some scenarios it's a
8063 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
8064 - Directory authorities now use data collected from their own
8065 uptime observations when choosing whether to assign the HSDir flag
8066 to relays, instead of trusting the uptime value the relay reports in
8067 its descriptor. This change helps prevent an attack where a small
8068 set of nodes with frequently-changing identity keys can blackhole
8069 a hidden service. (Only authorities need upgrade; others will be
8070 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
8073 - When we restart our relay, we might get a successful connection
8074 from the outside before we've started our reachability tests,
8075 triggering a warning: "ORPort found reachable, but I have no
8076 routerinfo yet. Failing to inform controller of success." This
8077 bug was harmless unless Tor is running under a controller
8078 like Vidalia, in which case the controller would never get a
8079 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
8081 - Make directory authorities more accurate at recording when
8082 relays that have failed several reachability tests became
8083 unreachable, so we can provide more accuracy at assigning Stable,
8084 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
8085 - Fix an issue that prevented static linking of libevent on
8086 some platforms (notably Linux). Fixes bug 2698; bugfix on
8087 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
8088 the --with-static-libevent configure option).
8089 - We now ask the other side of a stream (the client or the exit)
8090 for more data on that stream when the amount of queued data on
8091 that stream dips low enough. Previously, we wouldn't ask the
8092 other side for more data until either it sent us more data (which
8093 it wasn't supposed to do if it had exhausted its window!) or we
8094 had completely flushed all our queued data. This flow control fix
8095 should improve throughput. Fixes bug 2756; bugfix on the earliest
8096 released versions of Tor (svn commit r152).
8097 - Avoid a double-mark-for-free warning when failing to attach a
8098 transparent proxy connection. (We thought we had fixed this in
8099 0.2.2.23-alpha, but it turns out our fix was checking the wrong
8100 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
8101 bug) and 0.2.2.23-alpha (the incorrect fix).
8102 - When warning about missing zlib development packages during compile,
8103 give the correct package names. Bugfix on 0.2.0.1-alpha.
8106 - Directory authorities now log the source of a rejected POSTed v3
8108 - Make compilation with clang possible when using
8109 --enable-gcc-warnings by removing two warning options that clang
8110 hasn't implemented yet and by fixing a few warnings. Implements
8112 - When expiring circuits, use microsecond timers rather than
8113 one-second timers. This can avoid an unpleasant situation where a
8114 circuit is launched near the end of one second and expired right
8115 near the beginning of the next, and prevent fluctuations in circuit
8117 - Use computed circuit-build timeouts to decide when to launch
8118 parallel introduction circuits for hidden services. (Previously,
8119 we would retry after 15 seconds.)
8120 - Update to the April 1 2011 Maxmind GeoLite Country database.
8123 - Create the /var/run/tor directory on startup on OpenSUSE if it is
8124 not already created. Patch from Andreas Stieger. Fixes bug 2573.
8126 o Documentation changes:
8127 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
8128 - Resolve all doxygen warnings except those for missing documentation.
8130 - Add doxygen documentation for more functions, fields, and types.
8133 Changes in version 0.2.2.23-alpha - 2011-03-08
8134 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
8135 they restart they don't lose their bandwidth capacity estimate. This
8136 release also fixes a diverse set of user-facing bugs, ranging from
8137 relays overrunning their rate limiting to clients falsely warning about
8138 clock skew to bridge descriptor leaks by our bridge directory authority.
8141 - Stop sending a CLOCK_SKEW controller status event whenever
8142 we fetch directory information from a relay that has a wrong clock.
8143 Instead, only inform the controller when it's a trusted authority
8144 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
8145 the rest of bug 1074.
8146 - Fix an assert in parsing router descriptors containing IPv6
8147 addresses. This one took down the directory authorities when
8148 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
8149 - Make the bridge directory authority refuse to answer directory
8150 requests for "all" descriptors. It used to include bridge
8151 descriptors in its answer, which was a major information leak.
8152 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
8153 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
8154 Tor would ignore their RelayBandwidthBurst setting,
8155 potentially using more bandwidth than expected. Bugfix on
8156 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
8157 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
8158 hidserv" in her torrc. The 'hidserv' argument never controlled
8159 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
8162 - Relays now save observed peak bandwidth throughput rates to their
8163 state file (along with total usage, which was already saved)
8164 so that they can determine their correct estimated bandwidth on
8165 restart. Resolves bug 1863, where Tor relays would reset their
8166 estimated bandwidth to 0 after restarting.
8167 - Directory authorities now take changes in router IP address and
8168 ORPort into account when determining router stability. Previously,
8169 if a router changed its IP or ORPort, the authorities would not
8170 treat it as having any downtime for the purposes of stability
8171 calculation, whereas clients would experience downtime since the
8172 change could take a while to propagate to them. Resolves issue 1035.
8173 - Enable Address Space Layout Randomization (ASLR) and Data Execution
8174 Prevention (DEP) by default on Windows to make it harder for
8175 attackers to exploit vulnerabilities. Patch from John Brooks.
8177 o Minor bugfixes (on 0.2.1.x and earlier):
8178 - Fix a rare crash bug that could occur when a client was configured
8179 with a large number of bridges. Fixes bug 2629; bugfix on
8180 0.2.1.2-alpha. Bugfix by trac user "shitlei".
8181 - Avoid a double mark-for-free warning when failing to attach a
8182 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
8184 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
8185 found by "cypherpunks". This bug was introduced before the first
8186 Tor release, in svn commit r110.
8187 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
8188 don't mention them in the manpage. Fixes bug 2450; issue
8189 spotted by keb and G-Lo.
8190 - Fix a bug in bandwidth history state parsing that could have been
8191 triggered if a future version of Tor ever changed the timing
8192 granularity at which bandwidth history is measured. Bugfix on
8194 - When a relay decides that its DNS is too broken for it to serve
8195 as an exit server, it advertised itself as a non-exit, but
8196 continued to act as an exit. This could create accidental
8197 partitioning opportunities for users. Instead, if a relay is
8198 going to advertise reject *:* as its exit policy, it should
8199 really act with exit policy "reject *:*". Fixes bug 2366.
8200 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
8201 - In the special case where you configure a public exit relay as your
8202 bridge, Tor would be willing to use that exit relay as the last
8203 hop in your circuit as well. Now we fail that circuit instead.
8204 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
8205 - Fix a bug with our locking implementation on Windows that couldn't
8206 correctly detect when a file was already locked. Fixes bug 2504,
8207 bugfix on 0.2.1.6-alpha.
8208 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
8209 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
8211 - Set target port in get_interface_address6() correctly. Bugfix
8212 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
8213 - Directory authorities are now more robust to hops back in time
8214 when calculating router stability. Previously, if a run of uptime
8215 or downtime appeared to be negative, the calculation could give
8216 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
8218 - Fix an assert that got triggered when using the TestingTorNetwork
8219 configuration option and then issuing a GETINFO config-text control
8220 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
8222 o Minor bugfixes (on 0.2.2.x):
8223 - Clients should not weight BadExit nodes as Exits in their node
8224 selection. Similarly, directory authorities should not count BadExit
8225 bandwidth as Exit bandwidth when computing bandwidth-weights.
8226 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
8227 - Correctly clear our dir_read/dir_write history when there is an
8228 error parsing any bw history value from the state file. Bugfix on
8230 - Resolve a bug in verifying signatures of directory objects
8231 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
8232 Fixes bug 2409. Found by "piebeer".
8233 - Bridge authorities no longer crash on SIGHUP when they try to
8234 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
8238 - Log less aggressively about circuit timeout changes, and improve
8239 some other circuit timeout messages. Resolves bug 2004.
8240 - Log a little more clearly about the times at which we're no longer
8241 accepting new connections. Resolves bug 2181.
8242 - Reject attempts at the client side to open connections to private
8243 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
8244 a randomly chosen exit node. Attempts to do so are always
8245 ill-defined, generally prevented by exit policies, and usually
8246 in error. This will also help to detect loops in transparent
8247 proxy configurations. You can disable this feature by setting
8248 "ClientRejectInternalAddresses 0" in your torrc.
8249 - Always treat failure to allocate an RSA key as an unrecoverable
8251 - Update to the March 1 2011 Maxmind GeoLite Country database.
8253 o Minor features (log subsystem):
8254 - Add documentation for configuring logging at different severities in
8255 different log domains. We've had this feature since 0.2.1.1-alpha,
8256 but for some reason it never made it into the manpage. Fixes
8258 - Make it simpler to specify "All log domains except for A and B".
8259 Previously you needed to say "[*,~A,~B]". Now you can just say
8261 - Add a "LogMessageDomains 1" option to include the domains of log
8262 messages along with the messages. Without this, there's no way
8263 to use log domains without reading the source or doing a lot
8266 o Packaging changes:
8267 - Stop shipping the Tor specs files and development proposal documents
8268 in the tarball. They are now in a separate git repository at
8269 git://git.torproject.org/torspec.git
8272 Changes in version 0.2.1.30 - 2011-02-23
8273 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
8274 change is a slight tweak to Tor's TLS handshake that makes relays
8275 and bridges that run this new version reachable from Iran again.
8276 We don't expect this tweak will win the arms race long-term, but it
8277 buys us time until we roll out a better solution.
8280 - Stop sending a CLOCK_SKEW controller status event whenever
8281 we fetch directory information from a relay that has a wrong clock.
8282 Instead, only inform the controller when it's a trusted authority
8283 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
8284 the rest of bug 1074.
8285 - Fix a bounds-checking error that could allow an attacker to
8286 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
8288 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
8289 Tor would ignore their RelayBandwidthBurst setting,
8290 potentially using more bandwidth than expected. Bugfix on
8291 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
8292 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
8293 hidserv" in her torrc. The 'hidserv' argument never controlled
8294 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
8297 - Adjust our TLS Diffie-Hellman parameters to match those used by
8299 - Update to the February 1 2011 Maxmind GeoLite Country database.
8302 - Check for and reject overly long directory certificates and
8303 directory tokens before they have a chance to hit any assertions.
8304 Bugfix on 0.2.1.28. Found by "doorss".
8305 - Bring the logic that gathers routerinfos and assesses the
8306 acceptability of circuits into line. This prevents a Tor OP from
8307 getting locked in a cycle of choosing its local OR as an exit for a
8308 path (due to a .exit request) and then rejecting the circuit because
8309 its OR is not listed yet. It also prevents Tor clients from using an
8310 OR running in the same instance as an exit (due to a .exit request)
8311 if the OR does not meet the same requirements expected of an OR
8312 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
8314 o Packaging changes:
8315 - Stop shipping the Tor specs files and development proposal documents
8316 in the tarball. They are now in a separate git repository at
8317 git://git.torproject.org/torspec.git
8318 - Do not include Git version tags as though they are SVN tags when
8319 generating a tarball from inside a repository that has switched
8320 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
8323 Changes in version 0.2.2.22-alpha - 2011-01-25
8324 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
8325 main other change is a slight tweak to Tor's TLS handshake that makes
8326 relays and bridges that run this new version reachable from Iran again.
8327 We don't expect this tweak will win the arms race long-term, but it
8328 will buy us a bit more time until we roll out a better solution.
8331 - Fix a bounds-checking error that could allow an attacker to
8332 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
8334 - Don't assert when changing from bridge to relay or vice versa
8335 via the controller. The assert happened because we didn't properly
8336 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
8337 bug 2433. Reported by bastik.
8340 - Adjust our TLS Diffie-Hellman parameters to match those used by
8342 - Provide a log message stating which geoip file we're parsing
8343 instead of just stating that we're parsing the geoip file.
8344 Implements ticket 2432.
8347 - Check for and reject overly long directory certificates and
8348 directory tokens before they have a chance to hit any assertions.
8349 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
8352 Changes in version 0.2.2.21-alpha - 2011-01-15
8353 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
8354 continues our recent code security audit work. The main fix resolves
8355 a remote heap overflow vulnerability that can allow remote code
8356 execution (CVE-2011-0427). Other fixes address a variety of assert
8357 and crash bugs, most of which we think are hard to exploit remotely.
8359 o Major bugfixes (security), also included in 0.2.1.29:
8360 - Fix a heap overflow bug where an adversary could cause heap
8361 corruption. This bug probably allows remote code execution
8362 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
8364 - Prevent a denial-of-service attack by disallowing any
8365 zlib-compressed data whose compression factor is implausibly
8366 high. Fixes part of bug 2324; reported by "doorss".
8367 - Zero out a few more keys in memory before freeing them. Fixes
8368 bug 2384 and part of bug 2385. These key instances found by
8369 "cypherpunks", based on Andrew Case's report about being able
8370 to find sensitive data in Tor's memory space if you have enough
8371 permissions. Bugfix on 0.0.2pre9.
8373 o Major bugfixes (crashes), also included in 0.2.1.29:
8374 - Prevent calls to Libevent from inside Libevent log handlers.
8375 This had potential to cause a nasty set of crashes, especially
8376 if running Libevent with debug logging enabled, and running
8377 Tor with a controller watching for low-severity log messages.
8378 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
8379 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
8380 underflow errors there too. Fixes the other part of bug 2324.
8381 - Fix a bug where we would assert if we ever had a
8382 cached-descriptors.new file (or another file read directly into
8383 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
8384 on 0.2.1.25. Found by doorss.
8385 - Fix some potential asserts and parsing issues with grossly
8386 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
8389 o Minor bugfixes (other), also included in 0.2.1.29:
8390 - Fix a bug with handling misformed replies to reverse DNS lookup
8391 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
8392 bug reported by doorss.
8393 - Fix compilation on mingw when a pthreads compatibility library
8394 has been installed. (We don't want to use it, so we shouldn't
8395 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
8396 - Fix a bug where we would declare that we had run out of virtual
8397 addresses when the address space was only half-exhausted. Bugfix
8399 - Correctly handle the case where AutomapHostsOnResolve is set but
8400 no virtual addresses are available. Fixes bug 2328; bugfix on
8401 0.1.2.1-alpha. Bug found by doorss.
8402 - Correctly handle wrapping around when we run out of virtual
8403 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
8405 o Minor features, also included in 0.2.1.29:
8406 - Update to the January 1 2011 Maxmind GeoLite Country database.
8407 - Introduce output size checks on all of our decryption functions.
8409 o Build changes, also included in 0.2.1.29:
8410 - Tor does not build packages correctly with Automake 1.6 and earlier;
8411 added a check to Makefile.am to make sure that we're building with
8412 Automake 1.7 or later.
8413 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
8414 because we built it with a too-old version of automake. Thus that
8415 release broke ./configure --enable-openbsd-malloc, which is popular
8416 among really fast exit relays on Linux.
8418 o Major bugfixes, new in 0.2.2.21-alpha:
8419 - Prevent crash/heap corruption when the cbtnummodes consensus
8420 parameter is set to 0 or large values. Fixes bug 2317; bugfix
8423 o Major features, new in 0.2.2.21-alpha:
8424 - Introduce minimum/maximum values that clients will believe
8425 from the consensus. Now we'll have a better chance to avoid crashes
8426 or worse when a consensus param has a weird value.
8428 o Minor features, new in 0.2.2.21-alpha:
8429 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
8430 used on bridges, and it makes bridge scanning somewhat easier.
8431 - If writing the state file to disk fails, wait up to an hour before
8432 retrying again, rather than trying again each second. Fixes bug
8433 2346; bugfix on Tor 0.1.1.3-alpha.
8434 - Make Libevent log messages get delivered to controllers later,
8435 and not from inside the Libevent log handler. This prevents unsafe
8436 reentrant Libevent calls while still letting the log messages
8438 - Detect platforms that brokenly use a signed size_t, and refuse to
8439 build there. Found and analyzed by doorss and rransom.
8440 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
8443 o Minor bugfixes, new in 0.2.2.21-alpha:
8444 - Handle SOCKS messages longer than 128 bytes long correctly, rather
8445 than waiting forever for them to finish. Fixes bug 2330; bugfix
8446 on 0.2.0.16-alpha. Found by doorss.
8447 - Add assertions to check for overflow in arguments to
8448 base32_encode() and base32_decode(); fix a signed-unsigned
8449 comparison there too. These bugs are not actually reachable in Tor,
8450 but it's good to prevent future errors too. Found by doorss.
8451 - Correctly detect failures to create DNS requests when using Libevent
8452 versions before v2. (Before Libevent 2, we used our own evdns
8453 implementation. Its return values for Libevent's evdns_resolve_*()
8454 functions are not consistent with those from Libevent.) Fixes bug
8455 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
8457 o Documentation, new in 0.2.2.21-alpha:
8458 - Document the default socks host and port (127.0.0.1:9050) for
8462 Changes in version 0.2.1.29 - 2011-01-15
8463 Tor 0.2.1.29 continues our recent code security audit work. The main
8464 fix resolves a remote heap overflow vulnerability that can allow remote
8465 code execution. Other fixes address a variety of assert and crash bugs,
8466 most of which we think are hard to exploit remotely.
8468 o Major bugfixes (security):
8469 - Fix a heap overflow bug where an adversary could cause heap
8470 corruption. This bug probably allows remote code execution
8471 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
8473 - Prevent a denial-of-service attack by disallowing any
8474 zlib-compressed data whose compression factor is implausibly
8475 high. Fixes part of bug 2324; reported by "doorss".
8476 - Zero out a few more keys in memory before freeing them. Fixes
8477 bug 2384 and part of bug 2385. These key instances found by
8478 "cypherpunks", based on Andrew Case's report about being able
8479 to find sensitive data in Tor's memory space if you have enough
8480 permissions. Bugfix on 0.0.2pre9.
8482 o Major bugfixes (crashes):
8483 - Prevent calls to Libevent from inside Libevent log handlers.
8484 This had potential to cause a nasty set of crashes, especially
8485 if running Libevent with debug logging enabled, and running
8486 Tor with a controller watching for low-severity log messages.
8487 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
8488 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
8489 underflow errors there too. Fixes the other part of bug 2324.
8490 - Fix a bug where we would assert if we ever had a
8491 cached-descriptors.new file (or another file read directly into
8492 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
8493 on 0.2.1.25. Found by doorss.
8494 - Fix some potential asserts and parsing issues with grossly
8495 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
8498 o Minor bugfixes (other):
8499 - Fix a bug with handling misformed replies to reverse DNS lookup
8500 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
8501 bug reported by doorss.
8502 - Fix compilation on mingw when a pthreads compatibility library
8503 has been installed. (We don't want to use it, so we shouldn't
8504 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
8505 - Fix a bug where we would declare that we had run out of virtual
8506 addresses when the address space was only half-exhausted. Bugfix
8508 - Correctly handle the case where AutomapHostsOnResolve is set but
8509 no virtual addresses are available. Fixes bug 2328; bugfix on
8510 0.1.2.1-alpha. Bug found by doorss.
8511 - Correctly handle wrapping around to when we run out of virtual
8512 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
8513 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
8514 because we built it with a too-old version of automake. Thus that
8515 release broke ./configure --enable-openbsd-malloc, which is popular
8516 among really fast exit relays on Linux.
8519 - Update to the January 1 2011 Maxmind GeoLite Country database.
8520 - Introduce output size checks on all of our decryption functions.
8523 - Tor does not build packages correctly with Automake 1.6 and earlier;
8524 added a check to Makefile.am to make sure that we're building with
8525 Automake 1.7 or later.
8528 Changes in version 0.2.2.20-alpha - 2010-12-17
8529 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
8530 exploitable bugs. We also fix a variety of other significant bugs,
8531 change the IP address for one of our directory authorities, and update
8532 the minimum version that Tor relays must run to join the network.
8535 - Fix a remotely exploitable bug that could be used to crash instances
8536 of Tor remotely by overflowing on the heap. Remote-code execution
8537 hasn't been confirmed, but can't be ruled out. Everyone should
8538 upgrade. Bugfix on the 0.1.1 series and later.
8539 - Fix a bug that could break accounting on 64-bit systems with large
8540 time_t values, making them hibernate for impossibly long intervals.
8541 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
8542 - Fix a logic error in directory_fetches_from_authorities() that
8543 would cause all _non_-exits refusing single-hop-like circuits
8544 to fetch from authorities, when we wanted to have _exits_ fetch
8545 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
8547 - Fix a stream fairness bug that would cause newer streams on a given
8548 circuit to get preference when reading bytes from the origin or
8549 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
8550 introduced before the first Tor release, in svn revision r152.
8552 o Directory authority changes:
8553 - Change IP address and ports for gabelmoo (v3 directory authority).
8556 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
8557 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
8558 - Fix an off-by-one error in calculating some controller command
8559 argument lengths. Fortunately, this mistake is harmless since
8560 the controller code does redundant NUL termination too. Found by
8561 boboper. Bugfix on 0.1.1.1-alpha.
8562 - Do not dereference NULL if a bridge fails to build its
8563 extra-info descriptor. Found by an anonymous commenter on
8564 Trac. Bugfix on 0.2.2.19-alpha.
8567 - Update to the December 1 2010 Maxmind GeoLite Country database.
8568 - Directory authorities now reject relays running any versions of
8569 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
8570 known bugs that keep RELAY_EARLY cells from working on rendezvous
8571 circuits. Followup to fix for bug 2081.
8572 - Directory authorities now reject relays running any version of Tor
8573 older than 0.2.0.26-rc. That version is the earliest that fetches
8574 current directory information correctly. Fixes bug 2156.
8575 - Report only the top 10 ports in exit-port stats in order not to
8576 exceed the maximum extra-info descriptor length of 50 KB. Implements
8580 Changes in version 0.2.1.28 - 2010-12-17
8581 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
8582 exploitable bugs. We also took this opportunity to change the IP address
8583 for one of our directory authorities, and to update the geoip database
8587 - Fix a remotely exploitable bug that could be used to crash instances
8588 of Tor remotely by overflowing on the heap. Remote-code execution
8589 hasn't been confirmed, but can't be ruled out. Everyone should
8590 upgrade. Bugfix on the 0.1.1 series and later.
8592 o Directory authority changes:
8593 - Change IP address and ports for gabelmoo (v3 directory authority).
8596 - Update to the December 1 2010 Maxmind GeoLite Country database.
8599 Changes in version 0.2.1.27 - 2010-11-23
8600 Yet another OpenSSL security patch broke its compatibility with Tor:
8601 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
8602 also took this opportunity to fix several crash bugs, integrate a new
8603 directory authority, and update the bundled GeoIP database.
8606 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
8607 No longer set the tlsext_host_name extension on server SSL objects;
8608 but continue to set it on client SSL objects. Our goal in setting
8609 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
8610 bugfix on 0.2.1.1-alpha.
8611 - Do not log messages to the controller while shrinking buffer
8612 freelists. Doing so would sometimes make the controller connection
8613 try to allocate a buffer chunk, which would mess up the internals
8614 of the freelist and cause an assertion failure. Fixes bug 1125;
8615 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
8616 - Learn our external IP address when we're a relay or bridge, even if
8617 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
8618 where we introduced bridge relays that don't need to publish to
8619 be useful. Fixes bug 2050.
8620 - Do even more to reject (and not just ignore) annotations on
8621 router descriptors received anywhere but from the cache. Previously
8622 we would ignore such annotations at first, but cache them to disk
8623 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
8624 - When you're using bridges and your network goes away and your
8625 bridges get marked as down, recover when you attempt a new socks
8626 connection (if the network is back), rather than waiting up to an
8627 hour to try fetching new descriptors for your bridges. Bugfix on
8628 0.2.0.3-alpha; fixes bug 1981.
8631 - Move to the November 2010 Maxmind GeoLite country db (rather
8632 than the June 2009 ip-to-country GeoIP db) for our statistics that
8633 count how many users relays are seeing from each country. Now we'll
8634 have more accurate data, especially for many African countries.
8636 o New directory authorities:
8637 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
8641 - Fix an assertion failure that could occur in directory caches or
8642 bridge users when using a very short voting interval on a testing
8643 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
8645 - Enforce multiplicity rules when parsing annotations. Bugfix on
8646 0.2.0.8-alpha. Found by piebeer.
8647 - Allow handshaking OR connections to take a full KeepalivePeriod
8648 seconds to handshake. Previously, we would close them after
8649 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
8650 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
8652 - When building with --enable-gcc-warnings on OpenBSD, disable
8653 warnings in system headers. This makes --enable-gcc-warnings
8654 pass on OpenBSD 4.8.
8657 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
8658 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
8659 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
8660 Servers can start sending this code when enough clients recognize
8661 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
8662 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
8663 Patch from mingw-san.
8666 - Remove the old debian/ directory from the main Tor distribution.
8667 The official Tor-for-debian git repository lives at the URL
8668 https://git.torproject.org/debian/tor.git
8669 - Stop shipping the old doc/website/ directory in the tarball. We
8670 changed the website format in late 2010, and what we shipped in
8671 0.2.1.26 really wasn't that useful anyway.
8674 Changes in version 0.2.2.19-alpha - 2010-11-22
8675 Yet another OpenSSL security patch broke its compatibility with Tor:
8676 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
8679 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
8680 No longer set the tlsext_host_name extension on server SSL objects;
8681 but continue to set it on client SSL objects. Our goal in setting
8682 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
8683 bugfix on 0.2.1.1-alpha.
8686 - Try harder not to exceed the maximum length of 50 KB when writing
8687 statistics to extra-info descriptors. This bug was triggered by very
8688 fast relays reporting exit-port, entry, and dirreq statistics.
8689 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
8690 - Publish a router descriptor even if generating an extra-info
8691 descriptor fails. Previously we would not publish a router
8692 descriptor without an extra-info descriptor; this can cause fast
8693 exit relays collecting exit-port statistics to drop from the
8694 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
8697 Changes in version 0.2.2.18-alpha - 2010-11-16
8698 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
8699 us lately, makes unpublished bridge relays able to detect their IP
8700 address, and fixes a wide variety of other bugs to get us much closer
8701 to a stable release.
8704 - Do even more to reject (and not just ignore) annotations on
8705 router descriptors received anywhere but from the cache. Previously
8706 we would ignore such annotations at first, but cache them to disk
8707 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
8708 - Do not log messages to the controller while shrinking buffer
8709 freelists. Doing so would sometimes make the controller connection
8710 try to allocate a buffer chunk, which would mess up the internals
8711 of the freelist and cause an assertion failure. Fixes bug 1125;
8712 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
8713 - Learn our external IP address when we're a relay or bridge, even if
8714 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
8715 where we introduced bridge relays that don't need to publish to
8716 be useful. Fixes bug 2050.
8717 - Maintain separate TLS contexts and certificates for incoming and
8718 outgoing connections in bridge relays. Previously we would use the
8719 same TLS contexts and certs for incoming and outgoing connections.
8720 Bugfix on 0.2.0.3-alpha; addresses bug 988.
8721 - Maintain separate identity keys for incoming and outgoing TLS
8722 contexts in bridge relays. Previously we would use the same
8723 identity keys for incoming and outgoing TLS contexts. Bugfix on
8724 0.2.0.3-alpha; addresses the other half of bug 988.
8725 - Avoid an assertion failure when we as an authority receive a
8726 duplicate upload of a router descriptor that we already have,
8727 but which we previously considered an obsolete descriptor.
8728 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
8729 - Avoid a crash bug triggered by looking at a dangling pointer while
8730 setting the network status consensus. Found by Robert Ransom.
8731 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
8732 - Fix a logic error where servers that _didn't_ act as exits would
8733 try to keep their server lists more aggressively up to date than
8734 exits, when it was supposed to be the other way around. Bugfix
8737 o Minor bugfixes (on Tor 0.2.1.x and earlier):
8738 - When we're trying to guess whether we know our IP address as
8739 a relay, we would log various ways that we failed to guess
8740 our address, but never log that we ended up guessing it
8741 successfully. Now add a log line to help confused and anxious
8742 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
8743 - Bring the logic that gathers routerinfos and assesses the
8744 acceptability of circuits into line. This prevents a Tor OP from
8745 getting locked in a cycle of choosing its local OR as an exit for a
8746 path (due to a .exit request) and then rejecting the circuit because
8747 its OR is not listed yet. It also prevents Tor clients from using an
8748 OR running in the same instance as an exit (due to a .exit request)
8749 if the OR does not meet the same requirements expected of an OR
8750 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
8751 - Correctly describe errors that occur when generating a TLS object.
8752 Previously we would attribute them to a failure while generating a
8753 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
8755 - Enforce multiplicity rules when parsing annotations. Bugfix on
8756 0.2.0.8-alpha. Found by piebeer.
8757 - Fix warnings that newer versions of autoconf produced during
8758 ./autogen.sh. These warnings appear to be harmless in our case,
8759 but they were extremely verbose. Fixes bug 2020.
8761 o Minor bugfixes (on Tor 0.2.2.x):
8762 - Enable protection of small arrays whenever we build with gcc
8763 hardening features, not only when also building with warnings
8764 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
8767 - Make hidden services work better in private Tor networks by not
8768 requiring any uptime to join the hidden service descriptor
8769 DHT. Implements ticket 2088.
8770 - Rate-limit the "your application is giving Tor only an IP address"
8771 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
8772 - When AllowSingleHopExits is set, print a warning to explain to the
8773 relay operator why most clients are avoiding her relay.
8774 - Update to the November 1 2010 Maxmind GeoLite Country database.
8776 o Code simplifications and refactoring:
8777 - When we fixed bug 1038 we had to put in a restriction not to send
8778 RELAY_EARLY cells on rend circuits. This was necessary as long
8779 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
8780 active. Now remove this obsolete check. Resolves bug 2081.
8781 - Some options used different conventions for uppercasing of acronyms
8782 when comparing manpage and source. Fix those in favor of the
8783 manpage, as it makes sense to capitalize acronyms.
8784 - Remove the torrc.complete file. It hasn't been kept up to date
8785 and users will have better luck checking out the manpage.
8786 - Remove the obsolete "NoPublish" option; it has been flagged
8787 as obsolete and has produced a warning since 0.1.1.18-rc.
8788 - Remove everything related to building the expert bundle for OS X.
8789 It has confused many users, doesn't work right on OS X 10.6,
8790 and is hard to get rid of once installed. Resolves bug 1274.
8793 Changes in version 0.2.2.17-alpha - 2010-09-30
8794 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
8795 to use one-hop circuits (which can put the exit relays at higher risk,
8796 plus unbalance the network); fixes a big bug in bandwidth accounting
8797 for relays that want to limit their monthly bandwidth use; fixes a
8798 big pile of bugs in how clients tolerate temporary network failure;
8799 and makes our adaptive circuit build timeout feature (which improves
8800 client performance if your network is fast while not breaking things
8801 if your network is slow) better handle bad networks.
8804 - Exit relays now try harder to block exit attempts from unknown
8805 relays, to make it harder for people to use them as one-hop proxies
8806 a la tortunnel. Controlled by the refuseunknownexits consensus
8807 parameter (currently enabled), or you can override it on your
8808 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
8810 o Major bugfixes (0.2.1.x and earlier):
8811 - Fix a bug in bandwidth accounting that could make us use twice
8812 the intended bandwidth when our interval start changes due to
8813 daylight saving time. Now we tolerate skew in stored vs computed
8814 interval starts: if the start of the period changes by no more than
8815 50% of the period's duration, we remember bytes that we transferred
8816 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
8817 - Always search the Windows system directory for system DLLs, and
8818 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
8819 - When you're using bridges and your network goes away and your
8820 bridges get marked as down, recover when you attempt a new socks
8821 connection (if the network is back), rather than waiting up to an
8822 hour to try fetching new descriptors for your bridges. Bugfix on
8823 0.2.0.3-alpha; fixes bug 1981.
8825 o Major bugfixes (on 0.2.2.x):
8826 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
8828 - Fix a segfault that could happen when operating a bridge relay with
8829 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
8830 - The consensus bandwidth-weights (used by clients to choose fast
8831 relays) entered an unexpected edge case in September where
8832 Exits were much scarcer than Guards, resulting in bad weight
8833 recommendations. Now we compute them using new constraints that
8834 should succeed in all cases. Also alter directory authorities to
8835 not include the bandwidth-weights line if they fail to produce
8836 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
8837 - When weighting bridges during path selection, we used to trust
8838 the bandwidths they provided in their descriptor, only capping them
8839 at 10MB/s. This turned out to be problematic for two reasons:
8840 Bridges could claim to handle a lot more traffic then they
8841 actually would, thus making more clients pick them and have a
8842 pretty effective DoS attack. The other issue is that new bridges
8843 that might not have a good estimate for their bw capacity yet
8844 would not get used at all unless no other bridges are available
8845 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
8847 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
8848 - Ignore cannibalized circuits when recording circuit build times.
8849 This should provide for a minor performance improvement for hidden
8850 service users using 0.2.2.14-alpha, and should remove two spurious
8851 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
8852 - Simplify the logic that causes us to decide if the network is
8853 unavailable for purposes of recording circuit build times. If we
8854 receive no cells whatsoever for the entire duration of a circuit's
8855 full measured lifetime, the network is probably down. Also ignore
8856 one-hop directory fetching circuit timeouts when calculating our
8857 circuit build times. These changes should hopefully reduce the
8858 cases where we see ridiculous circuit build timeouts for people
8859 with spotty wireless connections. Fixes part of bug 1772; bugfix
8861 - Prevent the circuit build timeout from becoming larger than
8862 the maximum build time we have ever seen. Also, prevent the time
8863 period for measurement circuits from becoming larger than twice that
8864 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
8867 - When we run out of directory information such that we can't build
8868 circuits, but then get enough that we can build circuits, log when
8869 we actually construct a circuit, so the user has a better chance of
8870 knowing what's going on. Fixes bug 1362.
8871 - Be more generous with how much bandwidth we'd use up (with
8872 accounting enabled) before entering "soft hibernation". Previously,
8873 we'd refuse new connections and circuits once we'd used up 95% of
8874 our allotment. Now, we use up 95% of our allotment, AND make sure
8875 that we have no more than 500MB (or 3 hours of expected traffic,
8876 whichever is lower) remaining before we enter soft hibernation.
8877 - If we've configured EntryNodes and our network goes away and/or all
8878 our entrynodes get marked down, optimistically retry them all when
8879 a new socks application request appears. Fixes bug 1882.
8880 - Add some more defensive programming for architectures that can't
8881 handle unaligned integer accesses. We don't know of any actual bugs
8882 right now, but that's the best time to fix them. Fixes bug 1943.
8883 - Support line continuations in the torrc config file. If a line
8884 ends with a single backslash character, the newline is ignored, and
8885 the configuration value is treated as continuing on the next line.
8888 o Minor bugfixes (on 0.2.1.x and earlier):
8889 - For bandwidth accounting, calculate our expected bandwidth rate
8890 based on the time during which we were active and not in
8891 soft-hibernation during the last interval. Previously, we were
8892 also considering the time spent in soft-hibernation. If this
8893 was a long time, we would wind up underestimating our bandwidth
8894 by a lot, and skewing our wakeup time towards the start of the
8895 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
8897 o Minor bugfixes (on 0.2.2.x):
8898 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
8899 which were disabled by the circuit build timeout changes in
8900 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
8901 - Make sure we don't warn about missing bandwidth weights when
8902 choosing bridges or other relays not in the consensus. Bugfix on
8903 0.2.2.10-alpha; fixes bug 1805.
8904 - In our logs, do not double-report signatures from unrecognized
8905 authorities both as "from unknown authority" and "not
8906 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
8909 Changes in version 0.2.2.16-alpha - 2010-09-17
8910 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
8911 evident at exit relays), and also continues to resolve all the little
8912 bugs that have been filling up trac lately.
8914 o Major bugfixes (stream-level fairness):
8915 - When receiving a circuit-level SENDME for a blocked circuit, try
8916 to package cells fairly from all the streams that had previously
8917 been blocked on that circuit. Previously, we had started with the
8918 oldest stream, and allowed each stream to potentially exhaust
8919 the circuit's package window. This gave older streams on any
8920 given circuit priority over newer ones. Fixes bug 1937. Detected
8921 originally by Camilo Viecco. This bug was introduced before the
8922 first Tor release, in svn commit r152: it is the new winner of
8923 the longest-lived bug prize.
8924 - When the exit relay got a circuit-level sendme cell, it started
8925 reading on the exit streams, even if had 500 cells queued in the
8926 circuit queue already, so the circuit queue just grew and grew in
8927 some cases. We fix this by not re-enabling reading on receipt of a
8928 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
8929 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
8931 - Newly created streams were allowed to read cells onto circuits,
8932 even if the circuit's cell queue was blocked and waiting to drain.
8933 This created potential unfairness, as older streams would be
8934 blocked, but newer streams would gladly fill the queue completely.
8935 We add code to detect this situation and prevent any stream from
8936 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
8940 - Update to the September 1 2010 Maxmind GeoLite Country database.
8941 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
8942 not. This would lead to a cookie that is still not group readable.
8943 Closes bug 1843. Suggested by katmagic.
8944 - When logging a rate-limited warning, we now mention how many messages
8945 got suppressed since the last warning.
8946 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
8947 do individual connection-level rate limiting of clients. The torrc
8948 config options with the same names trump the consensus params, if
8949 both are present. Replaces the old "bwconnrate" and "bwconnburst"
8950 consensus params which were broken from 0.2.2.7-alpha through
8951 0.2.2.14-alpha. Closes bug 1947.
8952 - When a router changes IP address or port, authorities now launch
8953 a new reachability test for it. Implements ticket 1899.
8954 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
8955 2 no signature, 4 required" messages about consensus signatures
8956 easier to read, and make sure they get logged at the same severity
8957 as the messages explaining which keys are which. Fixes bug 1290.
8958 - Don't warn when we have a consensus that we can't verify because
8959 of missing certificates, unless those certificates are ones
8960 that we have been trying and failing to download. Fixes bug 1145.
8961 - If you configure your bridge with a known identity fingerprint,
8962 and the bridge authority is unreachable (as it is in at least
8963 one country now), fall back to directly requesting the descriptor
8964 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
8966 - When building with --enable-gcc-warnings on OpenBSD, disable
8967 warnings in system headers. This makes --enable-gcc-warnings
8968 pass on OpenBSD 4.8.
8970 o Minor bugfixes (on 0.2.1.x and earlier):
8971 - Authorities will now attempt to download consensuses if their
8972 own efforts to make a live consensus have failed. This change
8973 means authorities that restart will fetch a valid consensus, and
8974 it means authorities that didn't agree with the current consensus
8975 will still fetch and serve it if it has enough signatures. Bugfix
8976 on 0.2.0.9-alpha; fixes bug 1300.
8977 - Ensure DNS requests launched by "RESOLVE" commands from the
8978 controller respect the __LeaveStreamsUnattached setconf options. The
8979 same goes for requests launched via DNSPort or transparent
8980 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
8981 - Allow handshaking OR connections to take a full KeepalivePeriod
8982 seconds to handshake. Previously, we would close them after
8983 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
8984 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
8986 - Rate-limit "Failed to hand off onionskin" warnings.
8987 - Never relay a cell for a circuit we have already destroyed.
8988 Between marking a circuit as closeable and finally closing it,
8989 it may have been possible for a few queued cells to get relayed,
8990 even though they would have been immediately dropped by the next
8991 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
8992 - Never queue a cell for a circuit that's already been marked
8994 - Never vote for a server as "Running" if we have a descriptor for
8995 it claiming to be hibernating, and that descriptor was published
8996 more recently than our last contact with the server. Bugfix on
8997 0.2.0.3-alpha; fixes bug 911.
8998 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
9001 o Minor bugfixes (on 0.2.2.x):
9002 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
9003 down if a directory fetch fails and you've configured either
9004 bridges or EntryNodes. The intent was to mark the relay as down
9005 _unless_ you're using bridges or EntryNodes, since if you are
9006 then you could quickly run out of entry points.
9007 - Fix the Windows directory-listing code. A bug introduced in
9008 0.2.2.14-alpha could make Windows directory servers forget to load
9009 some of their cached v2 networkstatus files.
9010 - Really allow clients to use relays as bridges. Fixes bug 1776;
9011 bugfix on 0.2.2.15-alpha.
9012 - Demote a warn to info that happens when the CellStatistics option
9013 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
9014 Reported by Moritz Bartl.
9015 - On Windows, build correctly either with or without Unicode support.
9016 This is necessary so that Tor can support fringe platforms like
9017 Windows 98 (which has no Unicode), or Windows CE (which has no
9018 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
9021 - Add a unit test for cross-platform directory-listing code.
9024 Changes in version 0.2.2.15-alpha - 2010-08-18
9025 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
9026 fixes a variety of other bugs that were preventing performance
9027 experiments from moving forward, fixes several bothersome memory leaks,
9028 and generally closes a lot of smaller bugs that have been filling up
9032 - Stop assigning the HSDir flag to relays that disable their
9033 DirPort (and thus will refuse to answer directory requests). This
9034 fix should dramatically improve the reachability of hidden services:
9035 hidden services and hidden service clients pick six HSDir relays
9036 to store and retrieve the hidden service descriptor, and currently
9037 about half of the HSDir relays will refuse to work. Bugfix on
9038 0.2.0.10-alpha; fixes part of bug 1693.
9039 - The PerConnBWRate and Burst config options, along with the
9040 bwconnrate and bwconnburst consensus params, initialized each conn's
9041 token bucket values only when the connection is established. Now we
9042 update them if the config options change, and update them every time
9043 we get a new consensus. Otherwise we can encounter an ugly edge
9044 case where we initialize an OR conn to client-level bandwidth,
9045 but then later the relay joins the consensus and we leave it
9046 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
9047 - Fix a regression that caused Tor to rebind its ports if it receives
9048 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
9051 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
9052 should give us approximately 40-50% more Guard-flagged nodes,
9053 improving the anonymity the Tor network can provide and also
9054 decreasing the dropoff in throughput that relays experience when
9055 they first get the Guard flag.
9056 - Allow enabling or disabling the *Statistics config options while
9060 - Update to the August 1 2010 Maxmind GeoLite Country database.
9061 - Have the controller interface give a more useful message than
9062 "Internal Error" in response to failed GETINFO requests.
9063 - Warn when the same option is provided more than once in a torrc
9064 file, on the command line, or in a single SETCONF statement, and
9065 the option is one that only accepts a single line. Closes bug 1384.
9066 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
9067 Patch from mingw-san.
9068 - Add support for the country code "{??}" in torrc options like
9069 ExcludeNodes, to indicate all routers of unknown country. Closes
9071 - Relays report the number of bytes spent on answering directory
9072 requests in extra-info descriptors similar to {read,write}-history.
9073 Implements enhancement 1790.
9075 o Minor bugfixes (on 0.2.1.x and earlier):
9076 - Complain if PublishServerDescriptor is given multiple arguments that
9077 include 0 or 1. This configuration will be rejected in the future.
9078 Bugfix on 0.2.0.1-alpha; closes bug 1107.
9079 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
9080 Bugfix on 0.2.0.13-alpha; closes bug 928.
9081 - Change "Application request when we're believed to be offline."
9082 notice to "Application request when we haven't used client
9083 functionality lately.", to clarify that it's not an error. Bugfix
9084 on 0.0.9.3; fixes bug 1222.
9085 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
9086 would return "551 Internal error" rather than "552 Unrecognized key
9087 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
9088 - Users can't configure a regular relay to be their bridge. It didn't
9089 work because when Tor fetched the bridge descriptor, it found
9090 that it already had it, and didn't realize that the purpose of the
9091 descriptor had changed. Now we replace routers with a purpose other
9092 than bridge with bridge descriptors when fetching them. Bugfix on
9093 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
9094 refetch the descriptor with router purpose 'general', disabling
9096 - Fix a rare bug in rend_fn unit tests: we would fail a test when
9097 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
9098 on 0.2.0.10-alpha; fixes bug 1808.
9099 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
9100 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
9101 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
9102 Servers can start sending this code when enough clients recognize
9103 it. Also update the spec to reflect this new reason. Bugfix on
9104 0.1.0.1-rc; fixes part of bug 1793.
9105 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
9106 when we switch from being a public relay to a bridge. Otherwise
9107 there will still be clients that see the relay in their consensus,
9108 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
9110 - Instead of giving an assertion failure on an internal mismatch
9111 on estimated freelist size, just log a BUG warning and try later.
9112 Mitigates but does not fix bug 1125.
9113 - Fix an assertion failure that could occur in caches or bridge users
9114 when using a very short voting interval on a testing network.
9115 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
9117 o Minor bugfixes (on 0.2.2.x):
9118 - Alter directory authorities to always consider Exit-flagged nodes
9119 as potential Guard nodes in their votes. The actual decision to
9120 use Exits as Guards is done in the consensus bandwidth weights.
9121 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
9122 - When the controller is reporting the purpose of circuits that
9123 didn't finish building before the circuit build timeout, it was
9124 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
9125 - Our libevent version parsing code couldn't handle versions like
9126 1.4.14b-stable and incorrectly warned the user about using an
9127 old and broken version of libevent. Treat 1.4.14b-stable like
9128 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
9130 - Don't use substitution references like $(VAR:MOD) when
9131 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
9132 '$(:x)' to 'x' rather than the empty string. This bites us in
9133 doc/ when configured with --disable-asciidoc. Bugfix on
9134 0.2.2.9-alpha; fixes bug 1773.
9135 - Remove a spurious hidden service server-side log notice about
9136 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
9138 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
9140 - Correctly report written bytes on linked connections. Found while
9141 implementing 1790. Bugfix on 0.2.2.4-alpha.
9142 - Fix three memory leaks: one in circuit_build_times_parse_state(),
9143 one in dirvote_add_signatures_to_pending_consensus(), and one every
9144 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
9145 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
9147 o Code simplifications and refactoring:
9148 - Take a first step towards making or.h smaller by splitting out
9149 function definitions for all source files in src/or/. Leave
9150 structures and defines in or.h for now.
9151 - Remove a bunch of unused function declarations as well as a block of
9152 #if 0'd code from the unit tests. Closes bug 1824.
9153 - New unit tests for exit-port history statistics; refactored exit
9154 statistics code to be more easily tested.
9155 - Remove the old debian/ directory from the main Tor distribution.
9156 The official Tor-for-debian git repository lives at the URL
9157 https://git.torproject.org/debian/tor.git
9160 Changes in version 0.2.2.14-alpha - 2010-07-12
9161 Tor 0.2.2.14-alpha greatly improves client-side handling of
9162 circuit build timeouts, which are used to estimate speed and improve
9163 performance. We also move to a much better GeoIP database, port Tor to
9164 Windows CE, introduce new compile flags that improve code security,
9165 add an eighth v3 directory authority, and address a lot of more
9169 - Tor directory authorities no longer crash when started with a
9170 cached-microdesc-consensus file in their data directory. Bugfix
9171 on 0.2.2.6-alpha; fixes bug 1532.
9172 - Treat an unset $HOME like an empty $HOME rather than triggering an
9173 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
9174 - Ignore negative and large circuit build timeout values that can
9175 happen during a suspend or hibernate. These values caused various
9176 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
9177 - Alter calculation of Pareto distribution parameter 'Xm' for
9178 Circuit Build Timeout learning to use the weighted average of the
9179 top N=3 modes (because we have three entry guards). Considering
9180 multiple modes should improve the timeout calculation in some cases,
9181 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
9183 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
9184 right censored distribution model. This approach improves over the
9185 synthetic timeout generation approach that was producing insanely
9186 high timeout values. Now we calculate build timeouts using truncated
9187 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
9188 - Do not close circuits that are under construction when they reach
9189 the circuit build timeout. Instead, leave them building (but do not
9190 use them) for up until the time corresponding to the 95th percentile
9191 on the Pareto CDF or 60 seconds, whichever is greater. This is done
9192 to provide better data for the new Pareto model. This percentile
9193 can be controlled by the consensus.
9196 - Move to the June 2010 Maxmind GeoLite country db (rather than the
9197 June 2009 ip-to-country GeoIP db) for our statistics that count
9198 how many users relays are seeing from each country. Now we have
9199 more accurate data for many African countries.
9200 - Port Tor to build and run correctly on Windows CE systems, using
9201 the wcecompat library. Contributed by Valerio Lupi.
9202 - New "--enable-gcc-hardening" ./configure flag (off by default)
9203 to turn on gcc compile time hardening options. It ensures
9204 that signed ints have defined behavior (-fwrapv), enables
9205 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
9206 with canaries (-fstack-protector-all), turns on ASLR protection if
9207 supported by the kernel (-fPIE, -pie), and adds additional security
9208 related warnings. Verified to work on Mac OS X and Debian Lenny.
9209 - New "--enable-linker-hardening" ./configure flag (off by default)
9210 to turn on ELF specific hardening features (relro, now). This does
9211 not work with Mac OS X or any other non-ELF binary format.
9213 o New directory authorities:
9214 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
9218 - New config option "WarnUnsafeSocks 0" disables the warning that
9219 occurs whenever Tor receives a socks handshake using a version of
9220 the socks protocol that can only provide an IP address (rather
9221 than a hostname). Setups that do DNS locally over Tor are fine,
9222 and we shouldn't spam the logs in that case.
9223 - Convert the HACKING file to asciidoc, and add a few new sections
9224 to it, explaining how we use Git, how we make changelogs, and
9225 what should go in a patch.
9226 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
9227 event, to give information on the current rate of circuit timeouts
9228 over our stored history.
9229 - Add ability to disable circuit build time learning via consensus
9230 parameter and via a LearnCircuitBuildTimeout config option. Also
9231 automatically disable circuit build time calculation if we are
9232 either a AuthoritativeDirectory, or if we fail to write our state
9233 file. Fixes bug 1296.
9234 - More gracefully handle corrupt state files, removing asserts
9235 in favor of saving a backup and resetting state.
9236 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
9240 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
9242 - When a2x fails, mention that the user could disable manpages instead
9243 of trying to fix their asciidoc installation.
9244 - Where available, use Libevent 2.0's periodic timers so that our
9245 once-per-second cleanup code gets called even more closely to
9246 once per second than it would otherwise. Fixes bug 943.
9247 - If you run a bridge that listens on multiple IP addresses, and
9248 some user configures a bridge address that uses a different IP
9249 address than your bridge writes in its router descriptor, and the
9250 user doesn't specify an identity key, their Tor would discard the
9251 descriptor because "it isn't one of our configured bridges", and
9252 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
9253 Bugfix on 0.2.0.3-alpha.
9254 - If OpenSSL fails to make a duplicate of a private or public key, log
9255 an error message and try to exit cleanly. May help with debugging
9256 if bug 1209 ever remanifests.
9257 - Save a couple bytes in memory allocation every time we escape
9258 certain characters in a string. Patch from Florian Zumbiehl.
9259 - Make it explicit that we don't cannibalize one-hop circuits. This
9260 happens in the wild, but doesn't turn out to be a problem because
9261 we fortunately don't use those circuits. Many thanks to outofwords
9262 for the initial analysis and to swissknife who confirmed that
9263 two-hop circuits are actually created.
9264 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
9265 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
9266 - Eliminate a case where a circuit build time warning was displayed
9267 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
9270 Changes in version 0.2.1.26 - 2010-05-02
9271 Tor 0.2.1.26 addresses the recent connection and memory overload
9272 problems we've been seeing on relays, especially relays with their
9273 DirPort open. If your relay has been crashing, or you turned it off
9274 because it used too many resources, give this release a try.
9276 This release also fixes yet another instance of broken OpenSSL libraries
9277 that was causing some relays to drop out of the consensus.
9280 - Teach relays to defend themselves from connection overload. Relays
9281 now close idle circuits early if it looks like they were intended
9282 for directory fetches. Relays are also more aggressive about closing
9283 TLS connections that have no circuits on them. Such circuits are
9284 unlikely to be re-used, and tens of thousands of them were piling
9285 up at the fast relays, causing the relays to run out of sockets
9286 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
9287 their directory fetches over TLS).
9288 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
9289 that claim to be earlier than 0.9.8m, but which have in reality
9290 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
9291 behavior. Possible fix for some cases of bug 1346.
9292 - Directory mirrors were fetching relay descriptors only from v2
9293 directory authorities, rather than v3 authorities like they should.
9294 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
9295 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
9298 - Finally get rid of the deprecated and now harmful notion of "clique
9299 mode", where directory authorities maintain TLS connections to
9303 - In the util/threads test, no longer free the test_mutex before all
9304 worker threads have finished. Bugfix on 0.2.1.6-alpha.
9305 - The master thread could starve the worker threads quite badly on
9306 certain systems, causing them to run only partially in the allowed
9307 window. This resulted in test failures. Now the master thread sleeps
9308 occasionally for a few microseconds while the two worker-threads
9309 compete for the mutex. Bugfix on 0.2.0.1-alpha.
9312 Changes in version 0.2.2.13-alpha - 2010-04-24
9313 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
9314 problems we've been seeing on relays, especially relays with their
9315 DirPort open. If your relay has been crashing, or you turned it off
9316 because it used too many resources, give this release a try.
9319 - Teach relays to defend themselves from connection overload. Relays
9320 now close idle circuits early if it looks like they were intended
9321 for directory fetches. Relays are also more aggressive about closing
9322 TLS connections that have no circuits on them. Such circuits are
9323 unlikely to be re-used, and tens of thousands of them were piling
9324 up at the fast relays, causing the relays to run out of sockets
9325 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
9326 their directory fetches over TLS).
9329 - Finally get rid of the deprecated and now harmful notion of "clique
9330 mode", where directory authorities maintain TLS connections to
9332 - Directory authorities now do an immediate reachability check as soon
9333 as they hear about a new relay. This change should slightly reduce
9334 the time between setting up a relay and getting listed as running
9335 in the consensus. It should also improve the time between setting
9336 up a bridge and seeing use by bridge users.
9337 - Directory authorities no longer launch a TLS connection to every
9338 relay as they startup. Now that we have 2k+ descriptors cached,
9339 the resulting network hiccup is becoming a burden. Besides,
9340 authorities already avoid voting about Running for the first half
9341 hour of their uptime.
9344 Changes in version 0.2.2.12-alpha - 2010-04-20
9345 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
9346 handle and vote on descriptors. It was causing relays to drop out of
9350 - Many relays have been falling out of the consensus lately because
9351 not enough authorities know about their descriptor for them to get
9352 a majority of votes. When we deprecated the v2 directory protocol,
9353 we got rid of the only way that v3 authorities can hear from each
9354 other about other descriptors. Now authorities examine every v3
9355 vote for new descriptors, and fetch them from that authority. Bugfix
9357 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
9358 and a warning in or.h related to bandwidth_weight_rule_t that
9359 prevented clean compile on OS X. Fixes bug 1363; bugfix on
9361 - Fix a segfault on relays when DirReqStatistics is enabled
9362 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
9366 - Demote a confusing TLS warning that relay operators might get when
9367 someone tries to talk to their OrPort. It is neither the operator's
9368 fault nor can they do anything about it. Fixes bug 1364; bugfix
9372 Changes in version 0.2.2.11-alpha - 2010-04-15
9373 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
9374 libraries that was causing some relays to drop out of the consensus.
9377 - Directory mirrors were fetching relay descriptors only from v2
9378 directory authorities, rather than v3 authorities like they should.
9379 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
9380 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
9381 - Fix a parsing error that made every possible value of
9382 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
9383 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
9384 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
9385 about the option without breaking older ones.
9386 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
9387 that claim to be earlier than 0.9.8m, but which have in reality
9388 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
9389 behavior. Possible fix for some cases of bug 1346.
9392 - Experiment with a more aggressive approach to preventing clients
9393 from making one-hop exit streams. Exit relays who want to try it
9394 out can set "RefuseUnknownExits 1" in their torrc, and then look
9395 for "Attempt by %s to open a stream" log messages. Let us know
9397 - Add support for statically linking zlib by specifying
9398 --enable-static-zlib, to go with our support for statically linking
9399 openssl and libevent. Resolves bug 1358.
9402 - Fix a segfault that happens whenever a Tor client that is using
9403 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
9405 - When we cleaned up the contrib/tor-exit-notice.html file, we left
9406 out the first line. Fixes bug 1295.
9407 - When building the manpage from a tarball, we required asciidoc, but
9408 the asciidoc -> roff/html conversion was already done for the
9409 tarball. Make 'make' complain only when we need asciidoc (either
9410 because we're compiling directly from git, or because we altered
9411 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
9412 - When none of the directory authorities vote on any params, Tor
9413 segfaulted when trying to make the consensus from the votes. We
9414 didn't trigger the bug in practice, because authorities do include
9415 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
9418 - In the util/threads test, no longer free the test_mutex before all
9419 worker threads have finished. Bugfix on 0.2.1.6-alpha.
9420 - The master thread could starve the worker threads quite badly on
9421 certain systems, causing them to run only partially in the allowed
9422 window. This resulted in test failures. Now the master thread sleeps
9423 occasionally for a few microseconds while the two worker-threads
9424 compete for the mutex. Bugfix on 0.2.0.1-alpha.
9427 Changes in version 0.2.2.10-alpha - 2010-03-07
9428 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
9429 could prevent relays from guessing their IP address correctly. It also
9430 starts the groundwork for another client-side performance boost, since
9431 currently we're not making efficient use of relays that have both the
9432 Guard flag and the Exit flag.
9435 - Fix a regression from our patch for bug 1244 that caused relays
9436 to guess their IP address incorrectly if they didn't set Address
9437 in their torrc and/or their address fails to resolve. Bugfix on
9438 0.2.2.9-alpha; fixes bug 1269.
9440 o Major features (performance):
9441 - Directory authorities now compute consensus weightings that instruct
9442 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
9443 and no flag. Clients that use these weightings will distribute
9444 network load more evenly across these different relay types. The
9445 weightings are in the consensus so we can change them globally in
9446 the future. Extra thanks to "outofwords" for finding some nasty
9447 security bugs in the first implementation of this feature.
9449 o Minor features (performance):
9450 - Always perform router selections using weighted relay bandwidth,
9451 even if we don't need a high capacity circuit at the time. Non-fast
9452 circuits now only differ from fast ones in that they can use relays
9453 not marked with the Fast flag. This "feature" could turn out to
9454 be a horrible bug; we should investigate more before it goes into
9458 - Allow disabling building of the manpages. Skipping the manpage
9459 speeds up the build considerably.
9461 o Minor bugfixes (on 0.2.2.x):
9462 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
9463 Bugfix on 0.2.2.9-alpha.
9464 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
9465 config option. Bugfix on 0.2.2.7-alpha.
9466 - Ship the asciidoc-helper file in the tarball, so that people can
9467 build from source if they want to, and touching the .1.txt files
9468 doesn't break the build. Bugfix on 0.2.2.9-alpha.
9470 o Minor bugfixes (on 0.2.1.x or earlier):
9471 - Fix a dereference-then-NULL-check sequence when publishing
9472 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
9474 - Fix another dereference-then-NULL-check sequence. Bugfix on
9475 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
9476 - Make sure we treat potentially not NUL-terminated strings correctly.
9477 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
9479 o Code simplifications and refactoring:
9480 - Fix some urls in the exit notice file and make it XHTML1.1 strict
9481 compliant. Based on a patch from Christian Kujau.
9482 - Don't use sed in asciidoc-helper anymore.
9483 - Make the build process fail if asciidoc cannot be found and
9484 building with asciidoc isn't disabled.
9487 Changes in version 0.2.2.9-alpha - 2010-02-22
9488 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
9489 location of a directory authority, and cleans up a bunch of small bugs.
9491 o Directory authority changes:
9492 - Change IP address for dannenberg (v3 directory authority), and
9493 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
9494 service directory authority) from the list.
9497 - Make Tor work again on the latest OS X: when deciding whether to
9498 use strange flags to turn TLS renegotiation on, detect the OpenSSL
9499 version at run-time, not compile time. We need to do this because
9500 Apple doesn't update its dev-tools headers when it updates its
9501 libraries in a security patch.
9502 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
9503 that could happen on 32-bit platforms with 64-bit time_t. Also fix
9504 a memory leak when requesting a hidden service descriptor we've
9505 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
9507 - Authorities could be tricked into giving out the Exit flag to relays
9508 that didn't allow exiting to any ports. This bug could screw
9509 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
9510 1238. Bug discovered by Martin Kowalczyk.
9511 - When freeing a session key, zero it out completely. We only zeroed
9512 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
9513 patched by ekir. Fixes bug 1254.
9516 - Fix static compilation by listing the openssl libraries in the right
9517 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
9518 - Resume handling .exit hostnames in a special way: originally we
9519 stripped the .exit part and used the requested exit relay. In
9520 0.2.2.1-alpha we stopped treating them in any special way, meaning
9521 if you use a .exit address then Tor will pass it on to the exit
9522 relay. Now we reject the .exit stream outright, since that behavior
9523 might be more expected by the user. Found and diagnosed by Scott
9524 Bennett and Downie on or-talk.
9525 - Don't spam the controller with events when we have no file
9526 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
9527 for log messages was already solved from bug 748.)
9528 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
9530 - Make the DNSPort option work with libevent 2.x. Don't alter the
9531 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
9532 - Emit a GUARD DROPPED controller event for a case we missed.
9533 - Make more fields in the controller protocol case-insensitive, since
9534 control-spec.txt said they were.
9535 - Refactor resolve_my_address() to not use gethostbyname() anymore.
9536 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
9537 - Fix a spec conformance issue: the network-status-version token
9538 must be the first token in a v3 consensus or vote. Discovered by
9539 parakeep. Bugfix on 0.2.0.3-alpha.
9541 o Code simplifications and refactoring:
9542 - Generate our manpage and HTML documentation using Asciidoc. This
9543 change should make it easier to maintain the documentation, and
9545 - Remove the --enable-iphone option. According to reports from Marco
9546 Bonetti, Tor builds fine without any special tweaking on recent
9547 iPhone SDK versions.
9548 - Removed some unnecessary files from the source distribution. The
9549 AUTHORS file has now been merged into the people page on the
9550 website. The roadmaps and design doc can now be found in the
9551 projects directory in svn.
9552 - Enabled various circuit build timeout constants to be controlled
9553 by consensus parameters. Also set better defaults for these
9554 parameters based on experimentation on broadband and simulated
9558 - The 'EXTENDCIRCUIT' control port command can now be used with
9559 a circ id of 0 and no path. This feature will cause Tor to build
9560 a new 'fast' general purpose circuit using its own path selection
9562 - Added a BUILDTIMEOUT_SET controller event to describe changes
9563 to the circuit build timeout.
9564 - Future-proof the controller protocol a bit by ignoring keyword
9565 arguments we do not recognize.
9566 - Expand homedirs passed to tor-checkkey. This should silence a
9567 coverity complaint about passing a user-supplied string into
9568 open() without checking it.
9571 Changes in version 0.2.1.25 - 2010-03-16
9572 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
9573 prevent relays from guessing their IP address correctly. It also fixes
9574 several minor potential security bugs.
9577 - Fix a regression from our patch for bug 1244 that caused relays
9578 to guess their IP address incorrectly if they didn't set Address
9579 in their torrc and/or their address fails to resolve. Bugfix on
9580 0.2.1.23; fixes bug 1269.
9581 - When freeing a session key, zero it out completely. We only zeroed
9582 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
9583 patched by ekir. Fixes bug 1254.
9586 - Fix a dereference-then-NULL-check sequence when publishing
9587 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
9589 - Fix another dereference-then-NULL-check sequence. Bugfix on
9590 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
9591 - Make sure we treat potentially not NUL-terminated strings correctly.
9592 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
9596 Changes in version 0.2.1.24 - 2010-02-21
9597 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
9601 - Work correctly out-of-the-box with even more vendor-patched versions
9602 of OpenSSL. In particular, make it so Debian and OS X don't need
9603 customized patches to run/build.
9606 Changes in version 0.2.1.23 - 2010-02-13
9607 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
9608 again on the latest OS X, and updates the location of a directory
9611 o Major bugfixes (performance):
9612 - We were selecting our guards uniformly at random, and then weighting
9613 which of our guards we'd use uniformly at random. This imbalance
9614 meant that Tor clients were severely limited on throughput (and
9615 probably latency too) by the first hop in their circuit. Now we
9616 select guards weighted by currently advertised bandwidth. We also
9617 automatically discard guards picked using the old algorithm. Fixes
9618 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
9621 - Make Tor work again on the latest OS X: when deciding whether to
9622 use strange flags to turn TLS renegotiation on, detect the OpenSSL
9623 version at run-time, not compile time. We need to do this because
9624 Apple doesn't update its dev-tools headers when it updates its
9625 libraries in a security patch.
9626 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
9627 that could happen on 32-bit platforms with 64-bit time_t. Also fix
9628 a memory leak when requesting a hidden service descriptor we've
9629 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
9632 o Directory authority changes:
9633 - Change IP address for dannenberg (v3 directory authority), and
9634 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
9635 service directory authority) from the list.
9638 - Refactor resolve_my_address() to not use gethostbyname() anymore.
9639 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
9642 - Avoid a mad rush at the beginning of each month when each client
9643 rotates half of its guards. Instead we spread the rotation out
9644 throughout the month, but we still avoid leaving a precise timestamp
9645 in the state file about when we first picked the guard. Improves
9646 over the behavior introduced in 0.1.2.17.
9649 Changes in version 0.2.2.8-alpha - 2010-01-26
9650 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
9651 causing bridge relays to disappear. If you're running a bridge,
9655 - Fix a memory corruption bug on bridges that occured during the
9656 inclusion of stats data in extra-info descriptors. Also fix the
9657 interface for geoip_get_bridge_stats* to prevent similar bugs in
9658 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
9659 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
9662 - Ignore OutboundBindAddress when connecting to localhost.
9663 Connections to localhost need to come _from_ localhost, or else
9664 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
9668 Changes in version 0.2.2.7-alpha - 2010-01-19
9669 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
9670 as laying the groundwork for further relay-side performance fixes. It
9671 also starts cleaning up client behavior with respect to the EntryNodes,
9672 ExitNodes, and StrictNodes config options.
9674 This release also rotates two directory authority keys, due to a
9675 security breach of some of the Torproject servers.
9677 o Directory authority changes:
9678 - Rotate keys (both v3 identity and relay identity) for moria1
9681 o Major features (performance):
9682 - We were selecting our guards uniformly at random, and then weighting
9683 which of our guards we'd use uniformly at random. This imbalance
9684 meant that Tor clients were severely limited on throughput (and
9685 probably latency too) by the first hop in their circuit. Now we
9686 select guards weighted by currently advertised bandwidth. We also
9687 automatically discard guards picked using the old algorithm. Fixes
9688 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
9689 - When choosing which cells to relay first, relays can now favor
9690 circuits that have been quiet recently, to provide lower latency
9691 for low-volume circuits. By default, relays enable or disable this
9692 feature based on a setting in the consensus. You can override
9693 this default by using the new "CircuitPriorityHalflife" config
9694 option. Design and code by Ian Goldberg, Can Tang, and Chris
9696 - Add separate per-conn write limiting to go with the per-conn read
9697 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
9698 but never per-conn write limits.
9699 - New consensus params "bwconnrate" and "bwconnburst" to let us
9700 rate-limit client connections as they enter the network. It's
9701 controlled in the consensus so we can turn it on and off for
9702 experiments. It's starting out off. Based on proposal 163.
9704 o Major features (relay selection options):
9705 - Switch to a StrictNodes config option, rather than the previous
9706 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
9707 "StrictExcludeNodes" option.
9708 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
9709 change during a config reload, mark and discard all our origin
9710 circuits. This fix should address edge cases where we change the
9711 config options and but then choose a circuit that we created before
9713 - If EntryNodes or ExitNodes are set, be more willing to use an
9714 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
9716 - Make EntryNodes config option much more aggressive even when
9717 StrictNodes is not set. Before it would prepend your requested
9718 entrynodes to your list of guard nodes, but feel free to use others
9719 after that. Now it chooses only from your EntryNodes if any of
9720 those are available, and only falls back to others if a) they're
9721 all down and b) StrictNodes is not set.
9722 - Now we refresh your entry guards from EntryNodes at each consensus
9723 fetch -- rather than just at startup and then they slowly rot as
9724 the network changes.
9727 - Stop bridge directory authorities from answering dbg-stability.txt
9728 directory queries, which would let people fetch a list of all
9729 bridge identities they track. Bugfix on 0.2.1.6-alpha.
9732 - Log a notice when we get a new control connection. Now it's easier
9733 for security-conscious users to recognize when a local application
9734 is knocking on their controller door. Suggested by bug 1196.
9735 - New config option "CircuitStreamTimeout" to override our internal
9736 timeout schedule for how many seconds until we detach a stream from
9737 a circuit and try a new circuit. If your network is particularly
9738 slow, you might want to set this to a number like 60.
9739 - New controller command "getinfo config-text". It returns the
9740 contents that Tor would write if you send it a SAVECONF command,
9741 so the controller can write the file to disk itself.
9742 - New options for SafeLogging to allow scrubbing only log messages
9743 generated while acting as a relay.
9744 - Ship the bridges spec file in the tarball too.
9745 - Avoid a mad rush at the beginning of each month when each client
9746 rotates half of its guards. Instead we spread the rotation out
9747 throughout the month, but we still avoid leaving a precise timestamp
9748 in the state file about when we first picked the guard. Improves
9749 over the behavior introduced in 0.1.2.17.
9751 o Minor bugfixes (compiling):
9752 - Fix compilation on OS X 10.3, which has a stub mlockall() but
9753 hides it. Bugfix on 0.2.2.6-alpha.
9754 - Fix compilation on Solaris by removing support for the
9755 DisableAllSwap config option. Solaris doesn't have an rlimit for
9756 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
9759 o Minor bugfixes (crashes):
9760 - Do not segfault when writing buffer stats when we haven't observed
9761 a single circuit to report about. Found by Fabian Lanze. Bugfix on
9763 - If we're in the pathological case where there's no exit bandwidth
9764 but there is non-exit bandwidth, or no guard bandwidth but there
9765 is non-guard bandwidth, don't crash during path selection. Bugfix
9767 - Fix an impossible-to-actually-trigger buffer overflow in relay
9768 descriptor generation. Bugfix on 0.1.0.15.
9770 o Minor bugfixes (privacy):
9771 - Fix an instance where a Tor directory mirror might accidentally
9772 log the IP address of a misbehaving Tor client. Bugfix on
9774 - Don't list Windows capabilities in relay descriptors. We never made
9775 use of them, and maybe it's a bad idea to publish them. Bugfix
9778 o Minor bugfixes (other):
9779 - Resolve an edge case in path weighting that could make us misweight
9780 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
9781 - Fix statistics on client numbers by country as seen by bridges that
9782 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
9783 intervals instead of variable 12-to-48-hour intervals.
9784 - After we free an internal connection structure, overwrite it
9785 with a different memory value than we use for overwriting a freed
9786 internal circuit structure. Should help with debugging. Suggested
9788 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
9792 - Remove the HSAuthorityRecordStats option that version 0 hidden
9793 service authorities could have used to track statistics of overall
9794 hidden service usage.
9797 Changes in version 0.2.1.22 - 2010-01-19
9798 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
9799 authorities -- it would tell you its whole history of bridge descriptors
9800 if you make the right directory request. This stable update also
9801 rotates two of the seven v3 directory authority keys and locations.
9803 o Directory authority changes:
9804 - Rotate keys (both v3 identity and relay identity) for moria1
9808 - Stop bridge directory authorities from answering dbg-stability.txt
9809 directory queries, which would let people fetch a list of all
9810 bridge identities they track. Bugfix on 0.2.1.6-alpha.
9813 Changes in version 0.2.1.21 - 2009-12-21
9814 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
9815 library. If you use Tor on Linux / Unix and you're getting SSL
9816 renegotiation errors, upgrading should help. We also recommend an
9817 upgrade if you're an exit relay.
9820 - Work around a security feature in OpenSSL 0.9.8l that prevents our
9821 handshake from working unless we explicitly tell OpenSSL that we
9822 are using SSL renegotiation safely. We are, of course, but OpenSSL
9823 0.9.8l won't work unless we say we are.
9824 - Avoid crashing if the client is trying to upload many bytes and the
9825 circuit gets torn down at the same time, or if the flip side
9826 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
9829 - Do not refuse to learn about authority certs and v2 networkstatus
9830 documents that are older than the latest consensus. This bug might
9831 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
9832 Spotted and fixed by xmux.
9833 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
9834 trigger platform-specific option misparsing case found by Coverity
9836 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
9837 trigger assert. Fixes bug 1173.
9840 Changes in version 0.2.2.6-alpha - 2009-11-19
9841 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
9842 support for the new lower-footprint "microdescriptor" directory design,
9843 future-proofing our consensus format against new hash functions or
9844 other changes, and an Android port. It also makes Tor compatible with
9845 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
9848 - Directory authorities can now create, vote on, and serve multiple
9849 parallel formats of directory data as part of their voting process.
9850 Partially implements Proposal 162: "Publish the consensus in
9852 - Directory authorities can now agree on and publish small summaries
9853 of router information that clients can use in place of regular
9854 server descriptors. This transition will eventually allow clients
9855 to use far less bandwidth for downloading information about the
9856 network. Begins the implementation of Proposal 158: "Clients
9857 download consensus + microdescriptors".
9858 - The directory voting system is now extensible to use multiple hash
9859 algorithms for signatures and resource selection. Newer formats
9860 are signed with SHA256, with a possibility for moving to a better
9861 hash algorithm in the future.
9862 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
9863 current and future memory pages via mlockall(). On supported
9864 platforms (modern Linux and probably BSD but not Windows or OS X),
9865 this should effectively disable any and all attempts to page out
9866 memory. This option requires that you start your Tor as root --
9867 if you use DisableAllSwap, please consider using the User option
9868 to properly reduce the privileges of your Tor.
9869 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
9870 to help Tor build correctly for Android phones.
9873 - Work around a security feature in OpenSSL 0.9.8l that prevents our
9874 handshake from working unless we explicitly tell OpenSSL that we
9875 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
9876 won't work unless we say we are.
9879 - Fix a crash bug when trying to initialize the evdns module in
9880 Libevent 2. Bugfix on 0.2.1.16-rc.
9881 - Stop logging at severity 'warn' when some other Tor client tries
9882 to establish a circuit with us using weak DH keys. It's a protocol
9883 violation, but that doesn't mean ordinary users need to hear about
9884 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
9885 - Do not refuse to learn about authority certs and v2 networkstatus
9886 documents that are older than the latest consensus. This bug might
9887 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
9888 Spotted and fixed by xmux.
9889 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
9890 - If all authorities restart at once right before a consensus vote,
9891 nobody will vote about "Running", and clients will get a consensus
9892 with no usable relays. Instead, authorities refuse to build a
9893 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
9894 - If your relay can't keep up with the number of incoming create
9895 cells, it would log one warning per failure into your logs. Limit
9896 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
9897 - Bridges now use "reject *:*" as their default exit policy. Bugfix
9898 on 0.2.0.3-alpha; fixes bug 1113.
9899 - Fix a memory leak on directory authorities during voting that was
9900 introduced in 0.2.2.1-alpha. Found via valgrind.
9903 Changes in version 0.2.1.20 - 2009-10-15
9904 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
9905 services at once, prepares for more performance improvements, and
9906 fixes a bunch of smaller bugs.
9908 The Windows and OS X bundles also include a more recent Vidalia,
9909 and switch from Privoxy to Polipo.
9911 The OS X installers are now drag and drop. It's best to un-install
9912 Tor/Vidalia and then install this new bundle, rather than upgrade. If
9913 you want to upgrade, you'll need to update the paths for Tor and Polipo
9914 in the Vidalia Settings window.
9917 - Send circuit or stream sendme cells when our window has decreased
9918 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
9919 by Karsten when testing the "reduce circuit window" performance
9920 patch. Bugfix on the 54th commit on Tor -- from July 2002,
9921 before the release of Tor 0.0.0. This is the new winner of the
9923 - Fix a remotely triggerable memory leak when a consensus document
9924 contains more than one signature from the same voter. Bugfix on
9926 - Avoid segfault in rare cases when finishing an introduction circuit
9927 as a client and finding out that we don't have an introduction key
9928 for it. Fixes bug 1073. Reported by Aaron Swartz.
9931 - Tor now reads the "circwindow" parameter out of the consensus,
9932 and uses that value for its circuit package window rather than the
9933 default of 1000 cells. Begins the implementation of proposal 168.
9935 o New directory authorities:
9936 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
9938 - Move moria1 and tonga to alternate IP addresses.
9941 - Fix a signed/unsigned compile warning in 0.2.1.19.
9942 - Fix possible segmentation fault on directory authorities. Bugfix on
9944 - Fix an extremely rare infinite recursion bug that could occur if
9945 we tried to log a message after shutting down the log subsystem.
9946 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
9947 - Fix an obscure bug where hidden services on 64-bit big-endian
9948 systems might mis-read the timestamp in v3 introduce cells, and
9949 refuse to connect back to the client. Discovered by "rotor".
9950 Bugfix on 0.2.1.6-alpha.
9951 - We were triggering a CLOCK_SKEW controller status event whenever
9952 we connect via the v2 connection protocol to any relay that has
9953 a wrong clock. Instead, we should only inform the controller when
9954 it's a trusted authority that claims our clock is wrong. Bugfix
9955 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
9956 - We were telling the controller about CHECKING_REACHABILITY and
9957 REACHABILITY_FAILED status events whenever we launch a testing
9958 circuit or notice that one has failed. Instead, only tell the
9959 controller when we want to inform the user of overall success or
9960 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
9962 - Don't warn when we're using a circuit that ends with a node
9963 excluded in ExcludeExitNodes, but the circuit is not used to access
9964 the outside world. This should help fix bug 1090. Bugfix on
9966 - Work around a small memory leak in some versions of OpenSSL that
9967 stopped the memory used by the hostname TLS extension from being
9971 - Add a "getinfo status/accepted-server-descriptor" controller
9972 command, which is the recommended way for controllers to learn
9973 whether our server descriptor has been successfully received by at
9974 least on directory authority. Un-recommend good-server-descriptor
9975 getinfo and status events until we have a better design for them.
9978 Changes in version 0.2.2.5-alpha - 2009-10-11
9979 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
9982 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
9984 o Directory authorities:
9985 - Temporarily (just for this release) move dizum to an alternate
9989 Changes in version 0.2.2.4-alpha - 2009-10-10
9990 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
9991 introduces a new unit test framework, shifts directry authority
9992 addresses around to reduce the impact from recent blocking events,
9993 and fixes a few smaller bugs.
9996 - Fix several more asserts in the circuit_build_times code, for
9997 example one that causes Tor to fail to start once we have
9998 accumulated 5000 build times in the state file. Bugfixes on
9999 0.2.2.2-alpha; fixes bug 1108.
10001 o New directory authorities:
10002 - Move moria1 and Tonga to alternate IP addresses.
10005 - Log SSL state transitions at debug level during handshake, and
10006 include SSL states in error messages. This may help debug future
10007 SSL handshake issues.
10008 - Add a new "Handshake" log domain for activities that happen
10009 during the TLS handshake.
10010 - Revert to the "June 3 2009" ip-to-country file. The September one
10011 seems to have removed most US IP addresses.
10012 - Directory authorities now reject Tor relays with versions less than
10013 0.1.2.14. This step cuts out four relays from the current network,
10014 none of which are very big.
10017 - Fix a couple of smaller issues with gathering statistics. Bugfixes
10019 - Fix two memory leaks in the error case of
10020 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
10021 - Don't count one-hop circuits when we're estimating how long it
10022 takes circuits to build on average. Otherwise we'll set our circuit
10023 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
10024 - Directory authorities no longer change their opinion of, or vote on,
10025 whether a router is Running, unless they have themselves been
10026 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
10029 o Code simplifications and refactoring:
10030 - Revise our unit tests to use the "tinytest" framework, so we
10031 can run tests in their own processes, have smarter setup/teardown
10032 code, and so on. The unit test code has moved to its own
10033 subdirectory, and has been split into multiple modules.
10036 Changes in version 0.2.2.3-alpha - 2009-09-23
10037 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
10040 - Fix an overzealous assert in our new circuit build timeout code.
10041 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
10044 - If the networkstatus consensus tells us that we should use a
10045 negative circuit package window, ignore it. Otherwise we'll
10046 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
10049 Changes in version 0.2.2.2-alpha - 2009-09-21
10050 Tor 0.2.2.2-alpha introduces our latest performance improvement for
10051 clients: Tor tracks the average time it takes to build a circuit, and
10052 avoids using circuits that take too long to build. For fast connections,
10053 this feature can cut your expected latency in half. For slow or flaky
10054 connections, it could ruin your Tor experience. Let us know if it does!
10057 - Tor now tracks how long it takes to build client-side circuits
10058 over time, and adapts its timeout to local network performance.
10059 Since a circuit that takes a long time to build will also provide
10060 bad performance, we get significant latency improvements by
10061 discarding the slowest 20% of circuits. Specifically, Tor creates
10062 circuits more aggressively than usual until it has enough data
10063 points for a good timeout estimate. Implements proposal 151.
10064 We are especially looking for reports (good and bad) from users with
10065 both EDGE and broadband connections that can move from broadband
10066 to EDGE and find out if the build-time data in the .tor/state gets
10067 reset without loss of Tor usability. You should also see a notice
10068 log message telling you that Tor has reset its timeout.
10069 - Directory authorities can now vote on arbitary integer values as
10070 part of the consensus process. This is designed to help set
10071 network-wide parameters. Implements proposal 167.
10072 - Tor now reads the "circwindow" parameter out of the consensus,
10073 and uses that value for its circuit package window rather than the
10074 default of 1000 cells. Begins the implementation of proposal 168.
10077 - Fix a remotely triggerable memory leak when a consensus document
10078 contains more than one signature from the same voter. Bugfix on
10082 - Fix an extremely rare infinite recursion bug that could occur if
10083 we tried to log a message after shutting down the log subsystem.
10084 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
10085 - Fix parsing for memory or time units given without a space between
10086 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
10087 - A networkstatus vote must contain exactly one signature. Spec
10088 conformance issue. Bugfix on 0.2.0.3-alpha.
10089 - Fix an obscure bug where hidden services on 64-bit big-endian
10090 systems might mis-read the timestamp in v3 introduce cells, and
10091 refuse to connect back to the client. Discovered by "rotor".
10092 Bugfix on 0.2.1.6-alpha.
10093 - We were triggering a CLOCK_SKEW controller status event whenever
10094 we connect via the v2 connection protocol to any relay that has
10095 a wrong clock. Instead, we should only inform the controller when
10096 it's a trusted authority that claims our clock is wrong. Bugfix
10097 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
10098 - We were telling the controller about CHECKING_REACHABILITY and
10099 REACHABILITY_FAILED status events whenever we launch a testing
10100 circuit or notice that one has failed. Instead, only tell the
10101 controller when we want to inform the user of overall success or
10102 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
10104 - Don't warn when we're using a circuit that ends with a node
10105 excluded in ExcludeExitNodes, but the circuit is not used to access
10106 the outside world. This should help fix bug 1090, but more problems
10107 remain. Bugfix on 0.2.1.6-alpha.
10108 - Work around a small memory leak in some versions of OpenSSL that
10109 stopped the memory used by the hostname TLS extension from being
10111 - Make our 'torify' script more portable; if we have only one of
10112 'torsocks' or 'tsocks' installed, don't complain to the user;
10113 and explain our warning about tsocks better.
10116 - Add a "getinfo status/accepted-server-descriptor" controller
10117 command, which is the recommended way for controllers to learn
10118 whether our server descriptor has been successfully received by at
10119 least on directory authority. Un-recommend good-server-descriptor
10120 getinfo and status events until we have a better design for them.
10121 - Update to the "September 4 2009" ip-to-country file.
10124 Changes in version 0.2.2.1-alpha - 2009-08-26
10125 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
10126 Tor clients to bootstrap on networks where only port 80 is reachable,
10127 makes it more straightforward to support hardware crypto accelerators,
10128 and starts the groundwork for gathering stats safely at relays.
10131 - Start the process of disabling ".exit" address notation, since it
10132 can be used for a variety of esoteric application-level attacks
10133 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
10136 o New directory authorities:
10137 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
10141 - New AccelName and AccelDir options add support for dynamic OpenSSL
10142 hardware crypto acceleration engines.
10143 - Tor now supports tunneling all of its outgoing connections over
10144 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
10145 configuration options. Code by Christopher Davis.
10148 - Send circuit or stream sendme cells when our window has decreased
10149 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
10150 by Karsten when testing the "reduce circuit window" performance
10151 patch. Bugfix on the 54th commit on Tor -- from July 2002,
10152 before the release of Tor 0.0.0. This is the new winner of the
10155 o New options for gathering stats safely:
10156 - Directory mirrors that set "DirReqStatistics 1" write statistics
10157 about directory requests to disk every 24 hours. As compared to the
10158 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
10159 1) stats are written to disk exactly every 24 hours; 2) estimated
10160 shares of v2 and v3 requests are determined as mean values, not at
10161 the end of a measurement period; 3) unresolved requests are listed
10162 with country code '??'; 4) directories also measure download times.
10163 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
10164 number of exit streams and transferred bytes per port to disk every
10166 - Relays that set "CellStatistics 1" write statistics on how long
10167 cells spend in their circuit queues to disk every 24 hours.
10168 - Entry nodes that set "EntryStatistics 1" write statistics on the
10169 rough number and origins of connecting clients to disk every 24
10171 - Relays that write any of the above statistics to disk and set
10172 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
10173 their extra-info documents.
10176 - New --digests command-line switch to output the digests of the
10177 source files Tor was built with.
10178 - The "torify" script now uses torsocks where available.
10179 - The memarea code now uses a sentinel value at the end of each area
10180 to make sure nothing writes beyond the end of an area. This might
10181 help debug some conceivable causes of bug 930.
10182 - Time and memory units in the configuration file can now be set to
10183 fractional units. For example, "2.5 GB" is now a valid value for
10185 - Certain Tor clients (such as those behind check.torproject.org) may
10186 want to fetch the consensus in an extra early manner. To enable this
10187 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
10188 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
10189 as only certain clients who must have this information sooner should
10191 - Instead of adding the svn revision to the Tor version string, report
10192 the git commit (when we're building from a git checkout).
10195 - If any of the v3 certs we download are unparseable, we should
10196 actually notice the failure so we don't retry indefinitely. Bugfix
10197 on 0.2.0.x; reported by "rotator".
10198 - If the cached cert file is unparseable, warn but don't exit.
10199 - Fix possible segmentation fault on directory authorities. Bugfix on
10201 - When Tor fails to parse a descriptor of any kind, dump it to disk.
10202 Might help diagnosing bug 1051.
10204 o Deprecated and removed features:
10205 - The controller no longer accepts the old obsolete "addr-mappings/"
10206 or "unregistered-servers-" GETINFO values.
10207 - Hidden services no longer publish version 0 descriptors, and clients
10208 do not request or use version 0 descriptors. However, the old hidden
10209 service authorities still accept and serve version 0 descriptors
10210 when contacted by older hidden services/clients.
10211 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
10212 always on; using them is necessary for correct forward-compatible
10214 - Remove support for .noconnect style addresses. Nobody was using
10215 them, and they provided another avenue for detecting Tor users
10216 via application-level web tricks.
10218 o Packaging changes:
10219 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
10220 installer bundles. See
10221 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
10222 for details of what's new in Vidalia 0.2.3.
10223 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
10224 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
10225 configuration file, rather than the old Privoxy.
10226 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
10227 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
10228 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
10229 better compatibility with OS X 10.6, aka Snow Leopard.
10230 - OS X Vidalia Bundle: The multi-package installer is now replaced
10231 by a simple drag and drop to the /Applications folder. This change
10232 occurred with the upgrade to Vidalia 0.2.3.
10235 Changes in version 0.2.1.19 - 2009-07-28
10236 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
10237 services on Tor 0.2.1.3-alpha through 0.2.1.18.
10240 - Make accessing hidden services on 0.2.1.x work right again.
10241 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
10242 part of patch provided by "optimist".
10245 - When a relay/bridge is writing out its identity key fingerprint to
10246 the "fingerprint" file and to its logs, write it without spaces. Now
10247 it will look like the fingerprints in our bridges documentation,
10248 and confuse fewer users.
10251 - Relays no longer publish a new server descriptor if they change
10252 their MaxAdvertisedBandwidth config option but it doesn't end up
10253 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
10254 fixes bug 1026. Patch from Sebastian.
10255 - Avoid leaking memory every time we get a create cell but we have
10256 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
10257 fixes bug 1034. Reported by BarkerJr.
10260 Changes in version 0.2.1.18 - 2009-07-24
10261 Tor 0.2.1.18 lays the foundations for performance improvements,
10262 adds status events to help users diagnose bootstrap problems, adds
10263 optional authentication/authorization for hidden services, fixes a
10264 variety of potential anonymity problems, and includes a huge pile of
10265 other features and bug fixes.
10268 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
10271 Changes in version 0.2.1.17-rc - 2009-07-07
10272 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
10273 candidate for the 0.2.1.x series. It lays the groundwork for further
10274 client performance improvements, and also fixes a big bug with directory
10275 authorities that were causing them to assign Guard and Stable flags
10278 The Windows bundles also finally include the geoip database that we
10279 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
10280 should actually install Torbutton rather than giving you a cryptic
10281 failure message (oops).
10284 - Clients now use the bandwidth values in the consensus, rather than
10285 the bandwidth values in each relay descriptor. This approach opens
10286 the door to more accurate bandwidth estimates once the directory
10287 authorities start doing active measurements. Implements more of
10291 - When Tor clients restart after 1-5 days, they discard all their
10292 cached descriptors as too old, but they still use the cached
10293 consensus document. This approach is good for robustness, but
10294 bad for performance: since they don't know any bandwidths, they
10295 end up choosing at random rather than weighting their choice by
10296 speed. Fixed by the above feature of putting bandwidths in the
10297 consensus. Bugfix on 0.2.0.x.
10298 - Directory authorities were neglecting to mark relays down in their
10299 internal histories if the relays fall off the routerlist without
10300 ever being found unreachable. So there were relays in the histories
10301 that haven't been seen for eight months, and are listed as being
10302 up for eight months. This wreaked havoc on the "median wfu"
10303 and "median mtbf" calculations, in turn making Guard and Stable
10304 flags very wrong, hurting network performance. Fixes bugs 696 and
10305 969. Bugfix on 0.2.0.6-alpha.
10308 - Serve the DirPortFrontPage page even when we have been approaching
10309 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
10310 - The control port would close the connection before flushing long
10311 replies, such as the network consensus, if a QUIT command was issued
10312 before the reply had completed. Now, the control port flushes all
10313 pending replies before closing the connection. Also fixed a spurious
10314 warning when a QUIT command is issued after a malformed or rejected
10315 AUTHENTICATE command, but before the connection was closed. Patch
10316 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
10317 - When we can't find an intro key for a v2 hidden service descriptor,
10318 fall back to the v0 hidden service descriptor and log a bug message.
10319 Workaround for bug 1024.
10320 - Fix a log message that did not respect the SafeLogging option.
10324 - If we're a relay and we change our IP address, be more verbose
10325 about the reason that made us change. Should help track down
10326 further bugs for relays on dynamic IP addresses.
10329 Changes in version 0.2.0.35 - 2009-06-24
10331 - Avoid crashing in the presence of certain malformed descriptors.
10332 Found by lark, and by automated fuzzing.
10333 - Fix an edge case where a malicious exit relay could convince a
10334 controller that the client's DNS question resolves to an internal IP
10335 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
10338 - Finally fix the bug where dynamic-IP relays disappear when their
10339 IP address changes: directory mirrors were mistakenly telling
10340 them their old address if they asked via begin_dir, so they
10341 never got an accurate answer about their new address, so they
10342 just vanished after a day. For belt-and-suspenders, relays that
10343 don't set Address in their config now avoid using begin_dir for
10344 all direct connections. Should fix bugs 827, 883, and 900.
10345 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
10346 that would occur on some exit nodes when DNS failures and timeouts
10347 occurred in certain patterns. Fix for bug 957.
10350 - When starting with a cache over a few days old, do not leak
10351 memory for the obsolete router descriptors in it. Bugfix on
10352 0.2.0.33; fixes bug 672.
10353 - Hidden service clients didn't use a cached service descriptor that
10354 was older than 15 minutes, but wouldn't fetch a new one either,
10355 because there was already one in the cache. Now, fetch a v2
10356 descriptor unless the same descriptor was added to the cache within
10357 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
10360 Changes in version 0.2.1.16-rc - 2009-06-20
10361 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
10362 a bunch of minor bugs.
10365 - Fix an edge case where a malicious exit relay could convince a
10366 controller that the client's DNS question resolves to an internal IP
10367 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
10369 o Major performance improvements (on 0.2.0.x):
10370 - Disable and refactor some debugging checks that forced a linear scan
10371 over the whole server-side DNS cache. These accounted for over 50%
10372 of CPU time on a relatively busy exit node's gprof profile. Found
10374 - Disable some debugging checks that appeared in exit node profile
10378 - Update to the "June 3 2009" ip-to-country file.
10379 - Do not have tor-resolve automatically refuse all .onion addresses;
10380 if AutomapHostsOnResolve is set in your torrc, this will work fine.
10382 o Minor bugfixes (on 0.2.0.x):
10383 - Log correct error messages for DNS-related network errors on
10385 - Fix a race condition that could cause crashes or memory corruption
10386 when running as a server with a controller listening for log
10388 - Avoid crashing when we have a policy specified in a DirPolicy or
10389 SocksPolicy or ReachableAddresses option with ports set on it,
10390 and we re-load the policy. May fix bug 996.
10391 - Hidden service clients didn't use a cached service descriptor that
10392 was older than 15 minutes, but wouldn't fetch a new one either,
10393 because there was already one in the cache. Now, fetch a v2
10394 descriptor unless the same descriptor was added to the cache within
10395 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
10397 o Minor bugfixes (on 0.2.1.x):
10398 - Don't warn users about low port and hibernation mix when they
10399 provide a *ListenAddress directive to fix that. Bugfix on
10401 - When switching back and forth between bridge mode, do not start
10402 gathering GeoIP data until two hours have passed.
10403 - Do not complain that the user has requested an excluded node as
10404 an exit when the node is not really an exit. This could happen
10405 because the circuit was for testing, or an introduction point.
10409 Changes in version 0.2.1.15-rc - 2009-05-25
10410 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
10411 series. It fixes a major bug on fast exit relays, as well as a variety
10412 of more minor bugs.
10414 o Major bugfixes (on 0.2.0.x):
10415 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
10416 that would occur on some exit nodes when DNS failures and timeouts
10417 occurred in certain patterns. Fix for bug 957.
10419 o Minor bugfixes (on 0.2.0.x):
10420 - Actually return -1 in the error case for read_bandwidth_usage().
10421 Harmless bug, since we currently don't care about the return value
10422 anywhere. Bugfix on 0.2.0.9-alpha.
10423 - Provide a more useful log message if bug 977 (related to buffer
10424 freelists) ever reappears, and do not crash right away.
10425 - Fix an assertion failure on 64-bit platforms when we allocated
10426 memory right up to the end of a memarea, then realigned the memory
10427 one step beyond the end. Fixes a possible cause of bug 930.
10428 - Protect the count of open sockets with a mutex, so we can't
10429 corrupt it when two threads are closing or opening sockets at once.
10430 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
10431 - Don't allow a bridge to publish its router descriptor to a
10432 non-bridge directory authority. Fixes part of bug 932.
10433 - When we change to or from being a bridge, reset our counts of
10434 client usage by country. Fixes bug 932.
10435 - Fix a bug that made stream bandwidth get misreported to the
10437 - Stop using malloc_usable_size() to use more area than we had
10438 actually allocated: it was safe, but made valgrind really unhappy.
10439 - Fix a memory leak when v3 directory authorities load their keys
10440 and cert from disk. Bugfix on 0.2.0.1-alpha.
10442 o Minor bugfixes (on 0.2.1.x):
10443 - Fix use of freed memory when deciding to mark a non-addable
10444 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
10447 Changes in version 0.2.1.14-rc - 2009-04-12
10448 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
10449 series. It begins fixing some major performance problems, and also
10450 finally addresses the bug that was causing relays on dynamic IP
10451 addresses to fall out of the directory.
10454 - Clients replace entry guards that were chosen more than a few months
10455 ago. This change should significantly improve client performance,
10456 especially once more people upgrade, since relays that have been
10457 a guard for a long time are currently overloaded.
10459 o Major bugfixes (on 0.2.0):
10460 - Finally fix the bug where dynamic-IP relays disappear when their
10461 IP address changes: directory mirrors were mistakenly telling
10462 them their old address if they asked via begin_dir, so they
10463 never got an accurate answer about their new address, so they
10464 just vanished after a day. For belt-and-suspenders, relays that
10465 don't set Address in their config now avoid using begin_dir for
10466 all direct connections. Should fix bugs 827, 883, and 900.
10467 - Relays were falling out of the networkstatus consensus for
10468 part of a day if they changed their local config but the
10469 authorities discarded their new descriptor as "not sufficiently
10470 different". Now directory authorities accept a descriptor as changed
10471 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
10472 patch by Sebastian.
10473 - Avoid crashing in the presence of certain malformed descriptors.
10474 Found by lark, and by automated fuzzing.
10477 - When generating circuit events with verbose nicknames for
10478 controllers, try harder to look up nicknames for routers on a
10479 circuit. (Previously, we would look in the router descriptors we had
10480 for nicknames, but not in the consensus.) Partial fix for bug 941.
10481 - If the bridge config line doesn't specify a port, assume 443.
10482 This makes bridge lines a bit smaller and easier for users to
10484 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
10485 bytes (aka 20KB/s), to match our documentation. Also update
10486 directory authorities so they always assign the Fast flag to relays
10487 with 20KB/s of capacity. Now people running relays won't suddenly
10488 find themselves not seeing any use, if the network gets faster
10490 - Update to the "April 3 2009" ip-to-country file.
10493 - Avoid trying to print raw memory to the logs when we decide to
10494 give up on downloading a given relay descriptor. Bugfix on
10496 - In tor-resolve, when the Tor client to use is specified by
10497 <hostname>:<port>, actually use the specified port rather than
10498 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
10499 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
10500 - When starting with a cache over a few days old, do not leak
10501 memory for the obsolete router descriptors in it. Bugfix on
10503 - Avoid double-free on list of successfully uploaded hidden
10504 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
10505 - Change memarea_strndup() implementation to work even when
10506 duplicating a string at the end of a page. This bug was
10507 harmless for now, but could have meant crashes later. Fix by
10508 lark. Bugfix on 0.2.1.1-alpha.
10509 - Limit uploaded directory documents to be 16M rather than 500K.
10510 The directory authorities were refusing v3 consensus votes from
10511 other authorities, since the votes are now 504K. Fixes bug 959;
10512 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
10513 - Directory authorities should never send a 503 "busy" response to
10514 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
10518 Changes in version 0.2.1.13-alpha - 2009-03-09
10519 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
10520 cleanups. We're finally getting close to a release candidate.
10523 - Correctly update the list of which countries we exclude as
10524 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
10525 lark. Bugfix on 0.2.1.6-alpha.
10527 o Minor bugfixes (on 0.2.0.x and earlier):
10528 - Automatically detect MacOSX versions earlier than 10.4.0, and
10529 disable kqueue from inside Tor when running with these versions.
10530 We previously did this from the startup script, but that was no
10531 help to people who didn't use the startup script. Resolves bug 863.
10532 - When we had picked an exit node for a connection, but marked it as
10533 "optional", and it turned out we had no onion key for the exit,
10534 stop wanting that exit and try again. This situation may not
10535 be possible now, but will probably become feasible with proposal
10536 158. Spotted by rovv. Fixes another case of bug 752.
10537 - Clients no longer cache certificates for authorities they do not
10538 recognize. Bugfix on 0.2.0.9-alpha.
10539 - When we can't transmit a DNS request due to a network error, retry
10540 it after a while, and eventually transmit a failing response to
10541 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
10542 - If the controller claimed responsibility for a stream, but that
10543 stream never finished making its connection, it would live
10544 forever in circuit_wait state. Now we close it after SocksTimeout
10545 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
10546 - Drop begin cells to a hidden service if they come from the middle
10547 of a circuit. Patch from lark.
10548 - When we erroneously receive two EXTEND cells for the same circuit
10549 ID on the same connection, drop the second. Patch from lark.
10550 - Fix a crash that occurs on exit nodes when a nameserver request
10551 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
10552 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
10554 - Do not assume that a stack-allocated character array will be
10555 64-bit aligned on platforms that demand that uint64_t access is
10556 aligned. Possible fix for bug 604.
10557 - Parse dates and IPv4 addresses in a locale- and libc-independent
10558 manner, to avoid platform-dependent behavior on malformed input.
10559 - Build correctly when configured to build outside the main source
10560 path. Patch from Michael Gold.
10561 - We were already rejecting relay begin cells with destination port
10562 of 0. Now also reject extend cells with destination port or address
10563 of 0. Suggested by lark.
10565 o Minor bugfixes (on 0.2.1.x):
10566 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
10567 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
10568 - If we're an exit node, scrub the IP address to which we are exiting
10569 in the logs. Bugfix on 0.2.1.8-alpha.
10572 - On Linux, use the prctl call to re-enable core dumps when the user
10574 - New controller event NEWCONSENSUS that lists the networkstatus
10575 lines for every recommended relay. Now controllers like Torflow
10576 can keep up-to-date on which relays they should be using.
10577 - Update to the "February 26 2009" ip-to-country file.
10580 Changes in version 0.2.0.34 - 2009-02-08
10581 Tor 0.2.0.34 features several more security-related fixes. You should
10582 upgrade, especially if you run an exit relay (remote crash) or a
10583 directory authority (remote infinite loop), or you're on an older
10584 (pre-XP) or not-recently-patched Windows (remote exploit).
10586 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
10587 have many known flaws, and nobody should be using them. You should
10588 upgrade. If you're using a Linux or BSD and its packages are obsolete,
10589 stop using those packages and upgrade anyway.
10592 - Fix an infinite-loop bug on handling corrupt votes under certain
10593 circumstances. Bugfix on 0.2.0.8-alpha.
10594 - Fix a temporary DoS vulnerability that could be performed by
10595 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
10596 - Avoid a potential crash on exit nodes when processing malformed
10597 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
10598 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
10599 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
10602 - Fix compilation on systems where time_t is a 64-bit integer.
10603 Patch from Matthias Drochner.
10604 - Don't consider expiring already-closed client connections. Fixes
10605 bug 893. Bugfix on 0.0.2pre20.
10608 Changes in version 0.2.1.12-alpha - 2009-02-08
10609 Tor 0.2.1.12-alpha features several more security-related fixes. You
10610 should upgrade, especially if you run an exit relay (remote crash) or
10611 a directory authority (remote infinite loop), or you're on an older
10612 (pre-XP) or not-recently-patched Windows (remote exploit). It also
10613 includes a big pile of minor bugfixes and cleanups.
10616 - Fix an infinite-loop bug on handling corrupt votes under certain
10617 circumstances. Bugfix on 0.2.0.8-alpha.
10618 - Fix a temporary DoS vulnerability that could be performed by
10619 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
10620 - Avoid a potential crash on exit nodes when processing malformed
10621 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
10624 - Let controllers actually ask for the "clients_seen" event for
10625 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
10626 reported by Matt Edman.
10627 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
10629 - Fix a bug in address parsing that was preventing bridges or hidden
10630 service targets from being at IPv6 addresses.
10631 - Solve a bug that kept hardware crypto acceleration from getting
10632 enabled when accounting was turned on. Fixes bug 907. Bugfix on
10634 - Remove a bash-ism from configure.in to build properly on non-Linux
10635 platforms. Bugfix on 0.2.1.1-alpha.
10636 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
10637 headers. Bugfix on 0.2.0.10-alpha.
10638 - Don't consider expiring already-closed client connections. Fixes
10639 bug 893. Bugfix on 0.0.2pre20.
10640 - Fix another interesting corner-case of bug 891 spotted by rovv:
10641 Previously, if two hosts had different amounts of clock drift, and
10642 one of them created a new connection with just the wrong timing,
10643 the other might decide to deprecate the new connection erroneously.
10644 Bugfix on 0.1.1.13-alpha.
10645 - Resolve a very rare crash bug that could occur when the user forced
10646 a nameserver reconfiguration during the middle of a nameserver
10647 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
10648 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
10649 Bugfix on 0.2.1.7-alpha.
10650 - If we're using bridges and our network goes away, be more willing
10651 to forgive our bridges and try again when we get an application
10652 request. Bugfix on 0.2.0.x.
10655 - Support platforms where time_t is 64 bits long. (Congratulations,
10656 NetBSD!) Patch from Matthias Drochner.
10657 - Add a 'getinfo status/clients-seen' controller command, in case
10658 controllers want to hear clients_seen events but connect late.
10661 - Disable GCC's strict alias optimization by default, to avoid the
10662 likelihood of its introducing subtle bugs whenever our code violates
10663 the letter of C99's alias rules.
10666 Changes in version 0.2.0.33 - 2009-01-21
10667 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
10668 useful to users. It also finally fixes a bug where a relay or client
10669 that's been off for many days would take a long time to bootstrap.
10671 This update also fixes an important security-related bug reported by
10672 Ilja van Sprundel. You should upgrade. (We'll send out more details
10673 about the bug once people have had some time to upgrade.)
10676 - Fix a heap-corruption bug that may be remotely triggerable on
10677 some platforms. Reported by Ilja van Sprundel.
10680 - When a stream at an exit relay is in state "resolving" or
10681 "connecting" and it receives an "end" relay cell, the exit relay
10682 would silently ignore the end cell and not close the stream. If
10683 the client never closes the circuit, then the exit relay never
10684 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
10685 reported by "wood".
10686 - When sending CREATED cells back for a given circuit, use a 64-bit
10687 connection ID to find the right connection, rather than an addr:port
10688 combination. Now that we can have multiple OR connections between
10689 the same ORs, it is no longer possible to use addr:port to uniquely
10690 identify a connection.
10691 - Bridge relays that had DirPort set to 0 would stop fetching
10692 descriptors shortly after startup, and then briefly resume
10693 after a new bandwidth test and/or after publishing a new bridge
10694 descriptor. Bridge users that try to bootstrap from them would
10695 get a recent networkstatus but would get descriptors from up to
10696 18 hours earlier, meaning most of the descriptors were obsolete
10697 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
10698 - Prevent bridge relays from serving their 'extrainfo' document
10699 to anybody who asks, now that extrainfo docs include potentially
10700 sensitive aggregated client geoip summaries. Bugfix on
10702 - If the cached networkstatus consensus is more than five days old,
10703 discard it rather than trying to use it. In theory it could be
10704 useful because it lists alternate directory mirrors, but in practice
10705 it just means we spend many minutes trying directory mirrors that
10706 are long gone from the network. Also discard router descriptors as
10707 we load them if they are more than five days old, since the onion
10708 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
10711 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
10712 could make gcc generate non-functional binary search code. Bugfix
10714 - Build correctly on platforms without socklen_t.
10715 - Compile without warnings on solaris.
10716 - Avoid potential crash on internal error during signature collection.
10717 Fixes bug 864. Patch from rovv.
10718 - Correct handling of possible malformed authority signing key
10719 certificates with internal signature types. Fixes bug 880.
10720 Bugfix on 0.2.0.3-alpha.
10721 - Fix a hard-to-trigger resource leak when logging credential status.
10723 - When we can't initialize DNS because the network is down, do not
10724 automatically stop Tor from starting. Instead, we retry failed
10725 dns_init() every 10 minutes, and change the exit policy to reject
10726 *:* until one succeeds. Fixes bug 691.
10727 - Use 64 bits instead of 32 bits for connection identifiers used with
10728 the controller protocol, to greatly reduce risk of identifier reuse.
10729 - When we're choosing an exit node for a circuit, and we have
10730 no pending streams, choose a good general exit rather than one that
10731 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
10732 - Fix another case of assuming, when a specific exit is requested,
10733 that we know more than the user about what hosts it allows.
10734 Fixes one case of bug 752. Patch from rovv.
10735 - Clip the MaxCircuitDirtiness config option to a minimum of 10
10736 seconds. Warn the user if lower values are given in the
10737 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
10738 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
10739 user if lower values are given in the configuration. Bugfix on
10740 0.1.1.17-rc. Patch by Sebastian.
10741 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
10742 the cache because we already had a v0 descriptor with the same ID.
10743 Bugfix on 0.2.0.18-alpha.
10744 - Fix a race condition when freeing keys shared between main thread
10745 and CPU workers that could result in a memory leak. Bugfix on
10746 0.1.0.1-rc. Fixes bug 889.
10747 - Send a valid END cell back when a client tries to connect to a
10748 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
10749 840. Patch from rovv.
10750 - Check which hops rendezvous stream cells are associated with to
10751 prevent possible guess-the-streamid injection attacks from
10752 intermediate hops. Fixes another case of bug 446. Based on patch
10754 - If a broken client asks a non-exit router to connect somewhere,
10755 do not even do the DNS lookup before rejecting the connection.
10756 Fixes another case of bug 619. Patch from rovv.
10757 - When a relay gets a create cell it can't decrypt (e.g. because it's
10758 using the wrong onion key), we were dropping it and letting the
10759 client time out. Now actually answer with a destroy cell. Fixes
10760 bug 904. Bugfix on 0.0.2pre8.
10762 o Minor bugfixes (hidden services):
10763 - Do not throw away existing introduction points on SIGHUP. Bugfix on
10764 0.0.6pre1. Patch by Karsten. Fixes bug 874.
10767 - Report the case where all signatures in a detached set are rejected
10768 differently than the case where there is an error handling the
10770 - When we realize that another process has modified our cached
10771 descriptors, print out a more useful error message rather than
10772 triggering an assertion. Fixes bug 885. Patch from Karsten.
10773 - Implement the 0x20 hack to better resist DNS poisoning: set the
10774 case on outgoing DNS requests randomly, and reject responses that do
10775 not match the case correctly. This logic can be disabled with the
10776 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
10777 of servers that do not reliably preserve case in replies. See
10778 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
10780 - Check DNS replies for more matching fields to better resist DNS
10782 - Never use OpenSSL compression: it wastes RAM and CPU trying to
10783 compress cells, which are basically all encrypted, compressed, or
10787 Changes in version 0.2.1.11-alpha - 2009-01-20
10788 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
10789 week it will take a long time to bootstrap again" bug. It also fixes
10790 an important security-related bug reported by Ilja van Sprundel. You
10791 should upgrade. (We'll send out more details about the bug once people
10792 have had some time to upgrade.)
10795 - Fix a heap-corruption bug that may be remotely triggerable on
10796 some platforms. Reported by Ilja van Sprundel.
10799 - Discard router descriptors as we load them if they are more than
10800 five days old. Otherwise if Tor is off for a long time and then
10801 starts with cached descriptors, it will try to use the onion
10802 keys in those obsolete descriptors when building circuits. Bugfix
10803 on 0.2.0.x. Fixes bug 887.
10806 - Try to make sure that the version of Libevent we're running with
10807 is binary-compatible with the one we built with. May address bug
10809 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
10810 for bug 905. Bugfix on 0.2.1.7-alpha.
10811 - Add a new --enable-local-appdata configuration switch to change
10812 the default location of the datadir on win32 from APPDATA to
10813 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
10814 entirely. Patch from coderman.
10817 - Make outbound DNS packets respect the OutboundBindAddress setting.
10818 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
10819 - When our circuit fails at the first hop (e.g. we get a destroy
10820 cell back), avoid using that OR connection anymore, and also
10821 tell all the one-hop directory requests waiting for it that they
10822 should fail. Bugfix on 0.2.1.3-alpha.
10823 - In the torify(1) manpage, mention that tsocks will leak your
10827 Changes in version 0.2.1.10-alpha - 2009-01-06
10828 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
10829 would make the bridge relay not so useful if it had DirPort set to 0,
10830 and one that could let an attacker learn a little bit of information
10831 about the bridge's users), and a bug that would cause your Tor relay
10832 to ignore a circuit create request it can't decrypt (rather than reply
10833 with an error). It also fixes a wide variety of other bugs.
10836 - If the cached networkstatus consensus is more than five days old,
10837 discard it rather than trying to use it. In theory it could
10838 be useful because it lists alternate directory mirrors, but in
10839 practice it just means we spend many minutes trying directory
10840 mirrors that are long gone from the network. Helps bug 887 a bit;
10842 - Bridge relays that had DirPort set to 0 would stop fetching
10843 descriptors shortly after startup, and then briefly resume
10844 after a new bandwidth test and/or after publishing a new bridge
10845 descriptor. Bridge users that try to bootstrap from them would
10846 get a recent networkstatus but would get descriptors from up to
10847 18 hours earlier, meaning most of the descriptors were obsolete
10848 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
10849 - Prevent bridge relays from serving their 'extrainfo' document
10850 to anybody who asks, now that extrainfo docs include potentially
10851 sensitive aggregated client geoip summaries. Bugfix on
10855 - New controller event "clients_seen" to report a geoip-based summary
10856 of which countries we've seen clients from recently. Now controllers
10857 like Vidalia can show bridge operators that they're actually making
10859 - Build correctly against versions of OpenSSL 0.9.8 or later built
10860 without support for deprecated functions.
10861 - Update to the "December 19 2008" ip-to-country file.
10863 o Minor bugfixes (on 0.2.0.x):
10864 - Authorities now vote for the Stable flag for any router whose
10865 weighted MTBF is at least 5 days, regardless of the mean MTBF.
10866 - Do not remove routers as too old if we do not have any consensus
10867 document. Bugfix on 0.2.0.7-alpha.
10868 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
10869 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
10870 - When an exit relay resolves a stream address to a local IP address,
10871 do not just keep retrying that same exit relay over and
10872 over. Instead, just close the stream. Addresses bug 872. Bugfix
10873 on 0.2.0.32. Patch from rovv.
10874 - If a hidden service sends us an END cell, do not consider
10875 retrying the connection; just close it. Patch from rovv.
10876 - When we made bridge authorities stop serving bridge descriptors over
10877 unencrypted links, we also broke DirPort reachability testing for
10878 bridges. So bridges with a non-zero DirPort were printing spurious
10879 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
10880 - When a relay gets a create cell it can't decrypt (e.g. because it's
10881 using the wrong onion key), we were dropping it and letting the
10882 client time out. Now actually answer with a destroy cell. Fixes
10883 bug 904. Bugfix on 0.0.2pre8.
10884 - Squeeze 2-5% out of client performance (according to oprofile) by
10885 improving the implementation of some policy-manipulation functions.
10887 o Minor bugfixes (on 0.2.1.x):
10888 - Make get_interface_address() function work properly again; stop
10889 guessing the wrong parts of our address as our address.
10890 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
10891 send on that circuit. Otherwise we might violate the proposal-110
10892 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
10894 - When we're sending non-EXTEND cells to the first hop in a circuit,
10895 for example to use an encrypted directory connection, we don't need
10896 to use RELAY_EARLY cells: the first hop knows what kind of cell
10897 it is, and nobody else can even see the cell type. Conserving
10898 RELAY_EARLY cells makes it easier to cannibalize circuits like
10900 - Stop logging nameserver addresses in reverse order.
10901 - If we are retrying a directory download slowly over and over, do
10902 not automatically give up after the 254th failure. Bugfix on
10904 - Resume reporting accurate "stream end" reasons to the local control
10905 port. They were lost in the changes for Proposal 148. Bugfix on
10908 o Deprecated and removed features:
10909 - The old "tor --version --version" command, which would print out
10910 the subversion "Id" of most of the source files, is now removed. It
10911 turned out to be less useful than we'd expected, and harder to
10914 o Code simplifications and refactoring:
10915 - Change our header file guard macros to be less likely to conflict
10916 with system headers. Adam Langley noticed that we were conflicting
10917 with log.h on Android.
10918 - Tool-assisted documentation cleanup. Nearly every function or
10919 static variable in Tor should have its own documentation now.
10922 Changes in version 0.2.1.9-alpha - 2008-12-25
10923 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
10925 o New directory authorities:
10926 - gabelmoo (the authority run by Karsten Loesing) now has a new
10930 - Never use a connection with a mismatched address to extend a
10931 circuit, unless that connection is canonical. A canonical
10932 connection is one whose address is authenticated by the router's
10933 identity key, either in a NETINFO cell or in a router descriptor.
10934 - Avoid a possible memory corruption bug when receiving hidden service
10935 descriptors. Bugfix on 0.2.1.6-alpha.
10938 - Fix a logic error that would automatically reject all but the first
10939 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
10940 part of bug 813/868. Bug spotted by coderman.
10941 - When a stream at an exit relay is in state "resolving" or
10942 "connecting" and it receives an "end" relay cell, the exit relay
10943 would silently ignore the end cell and not close the stream. If
10944 the client never closes the circuit, then the exit relay never
10945 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
10946 reported by "wood".
10947 - When we can't initialize DNS because the network is down, do not
10948 automatically stop Tor from starting. Instead, retry failed
10949 dns_init() every 10 minutes, and change the exit policy to reject
10950 *:* until one succeeds. Fixes bug 691.
10953 - Give a better error message when an overzealous init script says
10954 "sudo -u username tor --user username". Makes Bug 882 easier for
10956 - When a directory authority gives us a new guess for our IP address,
10957 log which authority we used. Hopefully this will help us debug
10958 the recent complaints about bad IP address guesses.
10959 - Detect svn revision properly when we're using git-svn.
10960 - Try not to open more than one descriptor-downloading connection
10961 to an authority at once. This should reduce load on directory
10962 authorities. Fixes bug 366.
10963 - Add cross-certification to newly generated certificates, so that
10964 a signing key is enough information to look up a certificate.
10965 Partial implementation of proposal 157.
10966 - Start serving certificates by <identity digest, signing key digest>
10967 pairs. Partial implementation of proposal 157.
10968 - Clients now never report any stream end reason except 'MISC'.
10969 Implements proposal 148.
10970 - On platforms with a maximum syslog string length, truncate syslog
10971 messages to that length ourselves, rather than relying on the
10972 system to do it for us.
10973 - Optimize out calls to time(NULL) that occur for every IO operation,
10974 or for every cell. On systems where time() is a slow syscall,
10975 this fix will be slightly helpful.
10976 - Exit servers can now answer resolve requests for ip6.arpa addresses.
10977 - When we download a descriptor that we then immediately (as
10978 a directory authority) reject, do not retry downloading it right
10979 away. Should save some bandwidth on authorities. Fix for bug
10980 888. Patch by Sebastian Hahn.
10981 - When a download gets us zero good descriptors, do not notify
10982 Tor that new directory information has arrived.
10983 - Avoid some nasty corner cases in the logic for marking connections
10984 as too old or obsolete or noncanonical for circuits. Partial
10987 o Minor features (controller):
10988 - New CONSENSUS_ARRIVED event to note when a new consensus has
10989 been fetched and validated.
10990 - When we realize that another process has modified our cached
10991 descriptors file, print out a more useful error message rather
10992 than triggering an assertion. Fixes bug 885. Patch from Karsten.
10993 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
10994 controllers to prevent SIGHUP from reloading the
10995 configuration. Fixes bug 856.
10998 - Resume using the correct "REASON=" stream when telling the
10999 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
11000 - When a canonical connection appears later in our internal list
11001 than a noncanonical one for a given OR ID, always use the
11002 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
11004 - Clip the MaxCircuitDirtiness config option to a minimum of 10
11005 seconds. Warn the user if lower values are given in the
11006 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
11007 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
11008 user if lower values are given in the configuration. Bugfix on
11009 0.1.1.17-rc. Patch by Sebastian.
11010 - Fix a race condition when freeing keys shared between main thread
11011 and CPU workers that could result in a memory leak. Bugfix on
11012 0.1.0.1-rc. Fixes bug 889.
11014 o Minor bugfixes (hidden services):
11015 - Do not throw away existing introduction points on SIGHUP (bugfix on
11016 0.0.6pre1); also, do not stall hidden services because we're
11017 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
11018 by John Brooks. Patch by Karsten. Fixes bug 874.
11019 - Fix a memory leak when we decline to add a v2 rendezvous
11020 descriptor to the cache because we already had a v0 descriptor
11021 with the same ID. Bugfix on 0.2.0.18-alpha.
11023 o Deprecated and removed features:
11024 - RedirectExits has been removed. It was deprecated since
11026 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
11027 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
11028 - Cell pools are now always enabled; --disable-cell-pools is ignored.
11030 o Code simplifications and refactoring:
11031 - Rename the confusing or_is_obsolete field to the more appropriate
11032 is_bad_for_new_circs, and move it to or_connection_t where it
11034 - Move edge-only flags from connection_t to edge_connection_t: not
11035 only is this better coding, but on machines of plausible alignment,
11036 it should save 4-8 bytes per connection_t. "Every little bit helps."
11037 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
11038 for consistency; keep old option working for backward compatibility.
11039 - Simplify the code for finding connections to use for a circuit.
11042 Changes in version 0.2.1.8-alpha - 2008-12-08
11043 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
11044 builds better on unusual platforms like Solaris and old OS X, and
11045 fixes a variety of other issues.
11048 - New DirPortFrontPage option that takes an html file and publishes
11049 it as "/" on the DirPort. Now relay operators can provide a
11050 disclaimer without needing to set up a separate webserver. There's
11051 a sample disclaimer in contrib/tor-exit-notice.html.
11054 - When the client is choosing entry guards, now it selects at most
11055 one guard from a given relay family. Otherwise we could end up with
11056 all of our entry points into the network run by the same operator.
11057 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
11060 - Fix a DOS opportunity during the voting signature collection process
11061 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
11062 - Fix a possible segfault when establishing an exit connection. Bugfix
11066 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
11068 - Made Tor a little less aggressive about deleting expired
11069 certificates. Partial fix for bug 854.
11070 - Stop doing unaligned memory access that generated bus errors on
11071 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
11072 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
11073 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
11074 - Make USR2 log-level switch take effect immediately. Bugfix on
11076 - If one win32 nameserver fails to get added, continue adding the
11077 rest, and don't automatically fail.
11078 - Use fcntl() for locking when flock() is not available. Should fix
11079 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
11080 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
11081 could make gcc generate non-functional binary search code. Bugfix
11083 - Build correctly on platforms without socklen_t.
11084 - Avoid potential crash on internal error during signature collection.
11085 Fixes bug 864. Patch from rovv.
11086 - Do not use C's stdio library for writing to log files. This will
11087 improve logging performance by a minute amount, and will stop
11088 leaking fds when our disk is full. Fixes bug 861.
11089 - Stop erroneous use of O_APPEND in cases where we did not in fact
11090 want to re-seek to the end of a file before every last write().
11091 - Correct handling of possible malformed authority signing key
11092 certificates with internal signature types. Fixes bug 880. Bugfix
11094 - Fix a hard-to-trigger resource leak when logging credential status.
11098 - Directory mirrors no longer fetch the v1 directory or
11099 running-routers files. They are obsolete, and nobody asks for them
11100 anymore. This is the first step to making v1 authorities obsolete.
11102 o Minor features (controller):
11103 - Return circuit purposes in response to GETINFO circuit-status. Fixes
11107 Changes in version 0.2.0.32 - 2008-11-20
11108 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
11109 packages (and maybe other packages) noticed by Theo de Raadt, fixes
11110 a smaller security flaw that might allow an attacker to access local
11111 services, further improves hidden service performance, and fixes a
11112 variety of other issues.
11115 - The "User" and "Group" config options did not clear the
11116 supplementary group entries for the Tor process. The "User" option
11117 is now more robust, and we now set the groups to the specified
11118 user's primary group. The "Group" option is now ignored. For more
11119 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
11120 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
11121 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
11122 - The "ClientDNSRejectInternalAddresses" config option wasn't being
11123 consistently obeyed: if an exit relay refuses a stream because its
11124 exit policy doesn't allow it, we would remember what IP address
11125 the relay said the destination address resolves to, even if it's
11126 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
11129 - Fix a DOS opportunity during the voting signature collection process
11130 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
11132 o Major bugfixes (hidden services):
11133 - When fetching v0 and v2 rendezvous service descriptors in parallel,
11134 we were failing the whole hidden service request when the v0
11135 descriptor fetch fails, even if the v2 fetch is still pending and
11136 might succeed. Similarly, if the last v2 fetch fails, we were
11137 failing the whole hidden service request even if a v0 fetch is
11138 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
11139 - When extending a circuit to a hidden service directory to upload a
11140 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
11141 requests failed, because the router descriptor has not been
11142 downloaded yet. In these cases, do not attempt to upload the
11143 rendezvous descriptor, but wait until the router descriptor is
11144 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
11145 descriptor from a hidden service directory for which the router
11146 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
11150 - Fix several infrequent memory leaks spotted by Coverity.
11151 - When testing for libevent functions, set the LDFLAGS variable
11152 correctly. Found by Riastradh.
11153 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
11154 bootstrapping with tunneled directory connections. Bugfix on
11155 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
11156 - When asked to connect to A.B.exit:80, if we don't know the IP for A
11157 and we know that server B rejects most-but-not all connections to
11158 port 80, we would previously reject the connection. Now, we assume
11159 the user knows what they were asking for. Fixes bug 752. Bugfix
11160 on 0.0.9rc5. Diagnosed by BarkerJr.
11161 - If we overrun our per-second write limits a little, count this as
11162 having used up our write allocation for the second, and choke
11163 outgoing directory writes. Previously, we had only counted this when
11164 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
11165 Bugfix on 0.2.0.x (??).
11166 - Remove the old v2 directory authority 'lefkada' from the default
11167 list. It has been gone for many months.
11168 - Stop doing unaligned memory access that generated bus errors on
11169 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
11170 - Make USR2 log-level switch take effect immediately. Bugfix on
11173 o Minor bugfixes (controller):
11174 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
11175 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
11178 Changes in version 0.2.1.7-alpha - 2008-11-08
11179 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
11180 packages (and maybe other packages) noticed by Theo de Raadt, fixes
11181 a smaller security flaw that might allow an attacker to access local
11182 services, adds better defense against DNS poisoning attacks on exit
11183 relays, further improves hidden service performance, and fixes a
11184 variety of other issues.
11187 - The "ClientDNSRejectInternalAddresses" config option wasn't being
11188 consistently obeyed: if an exit relay refuses a stream because its
11189 exit policy doesn't allow it, we would remember what IP address
11190 the relay said the destination address resolves to, even if it's
11191 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
11192 - The "User" and "Group" config options did not clear the
11193 supplementary group entries for the Tor process. The "User" option
11194 is now more robust, and we now set the groups to the specified
11195 user's primary group. The "Group" option is now ignored. For more
11196 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
11197 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
11198 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
11199 - Do not use or believe expired v3 authority certificates. Patch
11200 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
11203 - Now NodeFamily and MyFamily config options allow spaces in
11204 identity fingerprints, so it's easier to paste them in.
11205 Suggested by Lucky Green.
11206 - Implement the 0x20 hack to better resist DNS poisoning: set the
11207 case on outgoing DNS requests randomly, and reject responses that do
11208 not match the case correctly. This logic can be disabled with the
11209 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
11210 of servers that do not reliably preserve case in replies. See
11211 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
11213 - Preserve case in replies to DNSPort requests in order to support
11214 the 0x20 hack for resisting DNS poisoning attacks.
11216 o Hidden service performance improvements:
11217 - When the client launches an introduction circuit, retry with a
11218 new circuit after 30 seconds rather than 60 seconds.
11219 - Launch a second client-side introduction circuit in parallel
11220 after a delay of 15 seconds (based on work by Christian Wilms).
11221 - Hidden services start out building five intro circuits rather
11222 than three, and when the first three finish they publish a service
11223 descriptor using those. Now we publish our service descriptor much
11224 faster after restart.
11227 - Minor fix in the warning messages when you're having problems
11228 bootstrapping; also, be more forgiving of bootstrap problems when
11229 we're still making incremental progress on a given bootstrap phase.
11230 - When we're choosing an exit node for a circuit, and we have
11231 no pending streams, choose a good general exit rather than one that
11232 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
11233 - Send a valid END cell back when a client tries to connect to a
11234 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
11235 840. Patch from rovv.
11236 - If a broken client asks a non-exit router to connect somewhere,
11237 do not even do the DNS lookup before rejecting the connection.
11238 Fixes another case of bug 619. Patch from rovv.
11239 - Fix another case of assuming, when a specific exit is requested,
11240 that we know more than the user about what hosts it allows.
11241 Fixes another case of bug 752. Patch from rovv.
11242 - Check which hops rendezvous stream cells are associated with to
11243 prevent possible guess-the-streamid injection attacks from
11244 intermediate hops. Fixes another case of bug 446. Based on patch
11246 - Avoid using a negative right-shift when comparing 32-bit
11247 addresses. Possible fix for bug 845 and bug 811.
11248 - Make the assert_circuit_ok() function work correctly on circuits that
11249 have already been marked for close.
11250 - Fix read-off-the-end-of-string error in unit tests when decoding
11251 introduction points.
11252 - Fix uninitialized size field for memory area allocation: may improve
11253 memory performance during directory parsing.
11254 - Treat duplicate certificate fetches as failures, so that we do
11255 not try to re-fetch an expired certificate over and over and over.
11256 - Do not say we're fetching a certificate when we'll in fact skip it
11257 because of a pending download.
11260 Changes in version 0.2.1.6-alpha - 2008-09-30
11261 Tor 0.2.1.6-alpha further improves performance and robustness of
11262 hidden services, starts work on supporting per-country relay selection,
11263 and fixes a variety of smaller issues.
11266 - Implement proposal 121: make it possible to build hidden services
11267 that only certain clients are allowed to connect to. This is
11268 enforced at several points, so that unauthorized clients are unable
11269 to send INTRODUCE cells to the service, or even (depending on the
11270 type of authentication) to learn introduction points. This feature
11271 raises the bar for certain kinds of active attacks against hidden
11272 services. Code by Karsten Loesing.
11273 - Relays now store and serve v2 hidden service descriptors by default,
11274 i.e., the new default value for HidServDirectoryV2 is 1. This is
11275 the last step in proposal 114, which aims to make hidden service
11276 lookups more reliable.
11277 - Start work to allow node restrictions to include country codes. The
11278 syntax to exclude nodes in a country with country code XX is
11279 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
11280 refinement to decide what config options should take priority if
11281 you ask to both use a particular node and exclude it.
11282 - Allow ExitNodes list to include IP ranges and country codes, just
11283 like the Exclude*Nodes lists. Patch from Robert Hogan.
11286 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
11287 Tor to fail to start if you had it configured to use a bridge
11288 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
11289 - When extending a circuit to a hidden service directory to upload a
11290 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
11291 requests failed, because the router descriptor had not been
11292 downloaded yet. In these cases, we now wait until the router
11293 descriptor is downloaded, and then retry. Likewise, clients
11294 now skip over a hidden service directory if they don't yet have
11295 its router descriptor, rather than futilely requesting it and
11296 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
11298 - When fetching v0 and v2 rendezvous service descriptors in parallel,
11299 we were failing the whole hidden service request when the v0
11300 descriptor fetch fails, even if the v2 fetch is still pending and
11301 might succeed. Similarly, if the last v2 fetch fails, we were
11302 failing the whole hidden service request even if a v0 fetch is
11303 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
11304 - DNS replies need to have names matching their requests, but
11305 these names should be in the questions section, not necessarily
11306 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
11309 - Update to the "September 1 2008" ip-to-country file.
11310 - Allow ports 465 and 587 in the default exit policy again. We had
11311 rejected them in 0.1.0.15, because back in 2005 they were commonly
11312 misconfigured and ended up as spam targets. We hear they are better
11313 locked down these days.
11314 - Use a lockfile to make sure that two Tor processes are not
11315 simultaneously running with the same datadir.
11316 - Serve the latest v3 networkstatus consensus via the control
11317 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
11318 - Better logging about stability/reliability calculations on directory
11320 - Drop the requirement to have an open dir port for storing and
11321 serving v2 hidden service descriptors.
11322 - Directory authorities now serve a /tor/dbg-stability.txt URL to
11323 help debug WFU and MTBF calculations.
11324 - Implement most of Proposal 152: allow specialized servers to permit
11325 single-hop circuits, and clients to use those servers to build
11326 single-hop circuits when using a specialized controller. Patch
11327 from Josh Albrecht. Resolves feature request 768.
11328 - Add a -p option to tor-resolve for specifying the SOCKS port: some
11329 people find host:port too confusing.
11330 - Make TrackHostExit mappings expire a while after their last use, not
11331 after their creation. Patch from Robert Hogan.
11332 - Provide circuit purposes along with circuit events to the controller.
11335 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
11337 - Fixed some memory leaks -- some quite frequent, some almost
11338 impossible to trigger -- based on results from Coverity.
11339 - When testing for libevent functions, set the LDFLAGS variable
11340 correctly. Found by Riastradh.
11341 - Fix an assertion bug in parsing policy-related options; possible fix
11343 - Catch and report a few more bootstrapping failure cases when Tor
11344 fails to establish a TCP connection. Cleanup on 0.2.1.x.
11345 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
11346 bootstrapping with tunneled directory connections. Bugfix on
11347 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
11348 - When asked to connect to A.B.exit:80, if we don't know the IP for A
11349 and we know that server B rejects most-but-not all connections to
11350 port 80, we would previously reject the connection. Now, we assume
11351 the user knows what they were asking for. Fixes bug 752. Bugfix
11352 on 0.0.9rc5. Diagnosed by BarkerJr.
11353 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
11354 service directories if they have no advertised dir port. Bugfix
11356 - If we overrun our per-second write limits a little, count this as
11357 having used up our write allocation for the second, and choke
11358 outgoing directory writes. Previously, we had only counted this when
11359 we had met our limits precisely. Fixes bug 824. Patch by rovv.
11360 Bugfix on 0.2.0.x (??).
11361 - Avoid a "0 divided by 0" calculation when calculating router uptime
11362 at directory authorities. Bugfix on 0.2.0.8-alpha.
11363 - Make DNS resolved controller events into "CLOSED", not
11364 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
11366 - Fix a bug where an unreachable relay would establish enough
11367 reachability testing circuits to do a bandwidth test -- if
11368 we already have a connection to the middle hop of the testing
11369 circuit, then it could establish the last hop by using the existing
11370 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
11371 circuits no longer use entry guards in 0.2.1.3-alpha.
11372 - If we have correct permissions on $datadir, we complain to stdout
11373 and fail to start. But dangerous permissions on
11374 $datadir/cached-status/ would cause us to open a log and complain
11375 there. Now complain to stdout and fail to start in both cases. Fixes
11376 bug 820, reported by seeess.
11377 - Remove the old v2 directory authority 'lefkada' from the default
11378 list. It has been gone for many months.
11380 o Code simplifications and refactoring:
11381 - Revise the connection_new functions so that a more typesafe variant
11382 exists. This will work better with Coverity, and let us find any
11383 actual mistakes we're making here.
11384 - Refactor unit testing logic so that dmalloc can be used sensibly
11385 with unit tests to check for memory leaks.
11386 - Move all hidden-service related fields from connection and circuit
11387 structure to substructures: this way they won't eat so much memory.
11390 Changes in version 0.2.0.31 - 2008-09-03
11391 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
11392 a big bug we're seeing where in rare cases traffic from one Tor stream
11393 gets mixed into another stream, and fixes a variety of smaller issues.
11396 - Make sure that two circuits can never exist on the same connection
11397 with the same circuit ID, even if one is marked for close. This
11398 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
11399 - Relays now reject risky extend cells: if the extend cell includes
11400 a digest of all zeroes, or asks to extend back to the relay that
11401 sent the extend cell, tear down the circuit. Ideas suggested
11403 - If not enough of our entry guards are available so we add a new
11404 one, we might use the new one even if it overlapped with the
11405 current circuit's exit relay (or its family). Anonymity bugfix
11406 pointed out by rovv.
11409 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
11410 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
11411 - Correctly detect the presence of the linux/netfilter_ipv4.h header
11412 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
11413 - Pick size of default geoip filename string correctly on windows.
11414 Fixes bug 806. Bugfix on 0.2.0.30.
11415 - Make the autoconf script accept the obsolete --with-ssl-dir
11416 option as an alias for the actually-working --with-openssl-dir
11417 option. Fix the help documentation to recommend --with-openssl-dir.
11418 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
11419 - When using the TransPort option on OpenBSD, and using the User
11420 option to change UID and drop privileges, make sure to open
11421 /dev/pf before dropping privileges. Fixes bug 782. Patch from
11422 Christopher Davis. Bugfix on 0.1.2.1-alpha.
11423 - Try to attach connections immediately upon receiving a RENDEZVOUS2
11424 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
11425 on the client side when connecting to a hidden service. Bugfix
11426 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
11427 - When closing an application-side connection because its circuit is
11428 getting torn down, generate the stream event correctly. Bugfix on
11429 0.1.2.x. Anonymous patch.
11432 Changes in version 0.2.1.5-alpha - 2008-08-31
11433 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
11434 in a lot of the infrastructure for adding authorization to hidden
11435 services, lays the groundwork for having clients read their load
11436 balancing information out of the networkstatus consensus rather than
11437 the individual router descriptors, addresses two potential anonymity
11438 issues, and fixes a variety of smaller issues.
11441 - Convert many internal address representations to optionally hold
11443 - Generate and accept IPv6 addresses in many protocol elements.
11444 - Make resolver code handle nameservers located at ipv6 addresses.
11445 - Begin implementation of proposal 121 ("Client authorization for
11446 hidden services"): configure hidden services with client
11447 authorization, publish descriptors for them, and configure
11448 authorization data for hidden services at clients. The next
11449 step is to actually access hidden services that perform client
11451 - More progress toward proposal 141: Network status consensus
11452 documents and votes now contain bandwidth information for each
11453 router and a summary of that router's exit policy. Eventually this
11454 will be used by clients so that they do not have to download every
11455 known descriptor before building circuits.
11457 o Major bugfixes (on 0.2.0.x and before):
11458 - When sending CREATED cells back for a given circuit, use a 64-bit
11459 connection ID to find the right connection, rather than an addr:port
11460 combination. Now that we can have multiple OR connections between
11461 the same ORs, it is no longer possible to use addr:port to uniquely
11462 identify a connection.
11463 - Relays now reject risky extend cells: if the extend cell includes
11464 a digest of all zeroes, or asks to extend back to the relay that
11465 sent the extend cell, tear down the circuit. Ideas suggested
11467 - If not enough of our entry guards are available so we add a new
11468 one, we might use the new one even if it overlapped with the
11469 current circuit's exit relay (or its family). Anonymity bugfix
11470 pointed out by rovv.
11473 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
11474 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
11475 - When using the TransPort option on OpenBSD, and using the User
11476 option to change UID and drop privileges, make sure to open /dev/pf
11477 before dropping privileges. Fixes bug 782. Patch from Christopher
11478 Davis. Bugfix on 0.1.2.1-alpha.
11479 - Correctly detect the presence of the linux/netfilter_ipv4.h header
11480 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
11481 - Add a missing safe_str() call for a debug log message.
11482 - Use 64 bits instead of 32 bits for connection identifiers used with
11483 the controller protocol, to greatly reduce risk of identifier reuse.
11484 - Make the autoconf script accept the obsolete --with-ssl-dir
11485 option as an alias for the actually-working --with-openssl-dir
11486 option. Fix the help documentation to recommend --with-openssl-dir.
11487 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
11490 - Rate-limit too-many-sockets messages: when they happen, they happen
11491 a lot. Resolves bug 748.
11492 - Resist DNS poisoning a little better by making sure that names in
11493 answer sections match.
11494 - Print the SOCKS5 error message string as well as the error code
11495 when a tor-resolve request fails. Patch from Jacob.
11498 Changes in version 0.2.1.4-alpha - 2008-08-04
11499 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
11502 - The address part of exit policies was not correctly written
11503 to router descriptors. This generated router descriptors that failed
11504 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
11506 - Tor triggered a false assert when extending a circuit to a relay
11507 but we already have a connection open to that relay. Noticed by
11508 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
11511 - Fix a hidden service logging bug: in some edge cases, the router
11512 descriptor of a previously picked introduction point becomes
11513 obsolete and we need to give up on it rather than continually
11514 complaining that it has become obsolete. Observed by xiando. Bugfix
11517 o Removed features:
11518 - Take out the TestVia config option, since it was a workaround for
11519 a bug that was fixed in Tor 0.1.1.21.
11522 Changes in version 0.2.1.3-alpha - 2008-08-03
11523 Tor 0.2.1.3-alpha implements most of the pieces to prevent
11524 infinite-length circuit attacks (see proposal 110); fixes a bug that
11525 might cause exit relays to corrupt streams they send back; allows
11526 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
11527 ExcludeExitNodes config options; and fixes a big pile of bugs.
11529 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
11530 - Send a bootstrap problem "warn" event on the first problem if the
11531 reason is NO_ROUTE (that is, our network is down).
11534 - Implement most of proposal 110: The first K cells to be sent
11535 along a circuit are marked as special "early" cells; only K "early"
11536 cells will be allowed. Once this code is universal, we can block
11537 certain kinds of DOS attack by requiring that EXTEND commands must
11538 be sent using an "early" cell.
11541 - Try to attach connections immediately upon receiving a RENDEZVOUS2
11542 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
11543 on the client side when connecting to a hidden service. Bugfix
11544 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
11545 - Ensure that two circuits can never exist on the same connection
11546 with the same circuit ID, even if one is marked for close. This
11547 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
11550 - When relays do their initial bandwidth measurement, don't limit
11551 to just our entry guards for the test circuits. Otherwise we tend
11552 to have multiple test circuits going through a single entry guard,
11553 which makes our bandwidth test less accurate. Fixes part of bug 654;
11554 patch contributed by Josh Albrecht.
11555 - Add an ExcludeExitNodes option so users can list a set of nodes
11556 that should be be excluded from the exit node position, but
11557 allowed elsewhere. Implements proposal 151.
11558 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
11559 ExcludeNodes and ExcludeExitNodes lists.
11560 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
11561 be more efficient. Formerly it was quadratic in the number of
11562 servers; now it should be linear. Fixes bug 509.
11563 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
11564 and n_conn_id_digest fields into a separate structure that's
11565 only needed when the circuit has not yet attached to an n_conn.
11568 - Change the contrib/tor.logrotate script so it makes the new
11569 logs as "_tor:_tor" rather than the default, which is generally
11570 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
11571 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
11572 warnings (occasionally), but it can also cause the compiler to
11573 eliminate error-checking code. Suggested by Peter Gutmann.
11574 - When a hidden service is giving up on an introduction point candidate
11575 that was not included in the last published rendezvous descriptor,
11576 don't reschedule publication of the next descriptor. Fixes bug 763.
11578 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
11579 HiddenServiceExcludeNodes as obsolete: they never worked properly,
11580 and nobody claims to be using them. Fixes bug 754. Bugfix on
11581 0.1.0.1-rc. Patch from Christian Wilms.
11582 - Fix a small alignment and memory-wasting bug on buffer chunks.
11585 o Minor bugfixes (controller):
11586 - When closing an application-side connection because its circuit
11587 is getting torn down, generate the stream event correctly.
11588 Bugfix on 0.1.2.x. Anonymous patch.
11590 o Removed features:
11591 - Remove all backward-compatibility code to support relays running
11592 versions of Tor so old that they no longer work at all on the
11596 Changes in version 0.2.0.30 - 2008-07-15
11598 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
11599 warnings (occasionally), but it can also cause the compiler to
11600 eliminate error-checking code. Suggested by Peter Gutmann.
11603 Changes in version 0.2.0.29-rc - 2008-07-08
11604 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
11605 hidden-service performance bugs, and fixes a bunch of smaller bugs.
11608 - If you have more than one bridge but don't know their keys,
11609 you would only launch a request for the descriptor of the first one
11610 on your list. (Tor considered launching requests for the others, but
11611 found that it already had a connection on the way for $0000...0000
11612 so it didn't open another.) Bugfix on 0.2.0.x.
11613 - If you have more than one bridge but don't know their keys, and the
11614 connection to one of the bridges failed, you would cancel all
11615 pending bridge connections. (After all, they all have the same
11616 digest.) Bugfix on 0.2.0.x.
11617 - When a hidden service was trying to establish an introduction point,
11618 and Tor had built circuits preemptively for such purposes, we
11619 were ignoring all the preemptive circuits and launching a new one
11620 instead. Bugfix on 0.2.0.14-alpha.
11621 - When a hidden service was trying to establish an introduction point,
11622 and Tor *did* manage to reuse one of the preemptively built
11623 circuits, it didn't correctly remember which one it used,
11624 so it asked for another one soon after, until there were no
11625 more preemptive circuits, at which point it launched one from
11626 scratch. Bugfix on 0.0.9.x.
11627 - Make directory servers include the X-Your-Address-Is: http header in
11628 their responses even for begin_dir conns. Now clients who only
11629 ever use begin_dir connections still have a way to learn their IP
11630 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
11633 - Fix a macro/CPP interaction that was confusing some compilers:
11634 some GCCs don't like #if/#endif pairs inside macro arguments.
11636 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
11637 Fixes bug 704; fix from Steven Murdoch.
11638 - When opening /dev/null in finish_daemonize(), do not pass the
11639 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
11640 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
11641 - Correctly detect transparent proxy support on Linux hosts that
11642 require in.h to be included before netfilter_ipv4.h. Patch
11644 - Disallow session resumption attempts during the renegotiation
11645 stage of the v2 handshake protocol. Clients should never be trying
11646 session resumption at this point, but apparently some did, in
11647 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
11648 found by Geoff Goodell.
11651 Changes in version 0.2.1.2-alpha - 2008-06-20
11652 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
11653 make it easier to set up your own private Tor network; fixes several
11654 big bugs with using more than one bridge relay; fixes a big bug with
11655 offering hidden services quickly after Tor starts; and uses a better
11656 API for reporting potential bootstrapping problems to the controller.
11659 - New TestingTorNetwork config option to allow adjustment of
11660 previously constant values that, while reasonable, could slow
11661 bootstrapping. Implements proposal 135. Patch from Karsten.
11664 - If you have more than one bridge but don't know their digests,
11665 you would only learn a request for the descriptor of the first one
11666 on your list. (Tor considered launching requests for the others, but
11667 found that it already had a connection on the way for $0000...0000
11668 so it didn't open another.) Bugfix on 0.2.0.x.
11669 - If you have more than one bridge but don't know their digests,
11670 and the connection to one of the bridges failed, you would cancel
11671 all pending bridge connections. (After all, they all have the
11672 same digest.) Bugfix on 0.2.0.x.
11673 - When establishing a hidden service, introduction points that
11674 originate from cannibalized circuits are completely ignored and not
11675 included in rendezvous service descriptors. This might be another
11676 reason for delay in making a hidden service available. Bugfix
11677 from long ago (0.0.9.x?)
11680 - Allow OpenSSL to use dynamic locks if it wants.
11681 - When building a consensus, do not include routers that are down.
11682 This will cut down 30% to 40% on consensus size. Implements
11684 - In directory authorities' approved-routers files, allow
11685 fingerprints with or without space.
11686 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
11687 controller can query our current bootstrap state in case it attaches
11688 partway through and wants to catch up.
11689 - Send an initial "Starting" bootstrap status event, so we have a
11690 state to start out in.
11693 - Asking for a conditional consensus at .../consensus/<fingerprints>
11694 would crash a dirserver if it did not already have a
11695 consensus. Bugfix on 0.2.1.1-alpha.
11696 - Clean up some macro/CPP interactions: some GCC versions don't like
11697 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
11700 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
11701 - Directory authorities shouldn't complain about bootstrapping
11702 problems just because they do a lot of reachability testing and
11703 some of the connection attempts fail.
11704 - Start sending "count" and "recommendation" key/value pairs in
11705 bootstrap problem status events, so the controller can hear about
11706 problems even before Tor decides they're worth reporting for sure.
11707 - If you're using bridges, generate "bootstrap problem" warnings
11708 as soon as you run out of working bridges, rather than waiting
11709 for ten failures -- which will never happen if you have less than
11711 - If we close our OR connection because there's been a circuit
11712 pending on it for too long, we were telling our bootstrap status
11713 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
11716 Changes in version 0.2.1.1-alpha - 2008-06-13
11717 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
11718 were making the Tor process bloat especially on Linux; makes our TLS
11719 handshake blend in better; sends "bootstrap phase" status events to
11720 the controller, so it can keep the user informed of progress (and
11721 problems) fetching directory information and establishing circuits;
11722 and adds a variety of smaller features.
11725 - More work on making our TLS handshake blend in: modify the list
11726 of ciphers advertised by OpenSSL in client mode to even more
11727 closely resemble a common web browser. We cheat a little so that
11728 we can advertise ciphers that the locally installed OpenSSL doesn't
11730 - Start sending "bootstrap phase" status events to the controller,
11731 so it can keep the user informed of progress fetching directory
11732 information and establishing circuits. Also inform the controller
11733 if we think we're stuck at a particular bootstrap phase. Implements
11735 - Resume using OpenSSL's RAND_poll() for better (and more portable)
11736 cross-platform entropy collection again. We used to use it, then
11737 stopped using it because of a bug that could crash systems that
11738 called RAND_poll when they had a lot of fds open. It looks like the
11739 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
11740 at startup, and to call RAND_poll() when we reseed later only if
11741 we have a non-buggy OpenSSL version.
11744 - When we choose to abandon a new entry guard because we think our
11745 older ones might be better, close any circuits pending on that
11746 new entry guard connection. This fix should make us recover much
11747 faster when our network is down and then comes back. Bugfix on
11748 0.1.2.8-beta; found by lodger.
11750 o Memory fixes and improvements:
11751 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
11752 to avoid unused RAM in buffer chunks and memory pools.
11753 - Speed up parsing and cut down on memory fragmentation by using
11754 stack-style allocations for parsing directory objects. Previously,
11755 this accounted for over 40% of allocations from within Tor's code
11756 on a typical directory cache.
11757 - Use a Bloom filter rather than a digest-based set to track which
11758 descriptors we need to keep around when we're cleaning out old
11759 router descriptors. This speeds up the computation significantly,
11760 and may reduce fragmentation.
11761 - Reduce the default smartlist size from 32 to 16; it turns out that
11762 most smartlists hold around 8-12 elements tops.
11763 - Make dumpstats() log the fullness and size of openssl-internal
11765 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
11766 patch to their OpenSSL, turn it on to save memory on servers. This
11767 patch will (with any luck) get included in a mainline distribution
11769 - Never use OpenSSL compression: it wastes RAM and CPU trying to
11770 compress cells, which are basically all encrypted, compressed,
11774 - Stop reloading the router list from disk for no reason when we
11775 run out of reachable directory mirrors. Once upon a time reloading
11776 it would set the 'is_running' flag back to 1 for them. It hasn't
11777 done that for a long time.
11778 - In very rare situations new hidden service descriptors were
11779 published earlier than 30 seconds after the last change to the
11780 service. (We currently think that a hidden service descriptor
11781 that's been stable for 30 seconds is worth publishing.)
11784 - Allow separate log levels to be configured for different logging
11785 domains. For example, this allows one to log all notices, warnings,
11786 or errors, plus all memory management messages of level debug or
11787 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
11788 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
11789 and stop using a warning that had become unfixably verbose under
11791 - New --hush command-line option similar to --quiet. While --quiet
11792 disables all logging to the console on startup, --hush limits the
11793 output to messages of warning and error severity.
11794 - Servers support a new URL scheme for consensus downloads that
11795 allows the client to specify which authorities are trusted.
11796 The server then only sends the consensus if the client will trust
11797 it. Otherwise a 404 error is sent back. Clients use this
11798 new scheme when the server supports it (meaning it's running
11799 0.2.1.1-alpha or later). Implements proposal 134.
11800 - New configure/torrc options (--enable-geoip-stats,
11801 DirRecordUsageByCountry) to record how many IPs we've served
11802 directory info to in each country code, how many status documents
11803 total we've sent to each country code, and what share of the total
11804 directory requests we should expect to see.
11805 - Use the TLS1 hostname extension to more closely resemble browser
11807 - Lots of new unit tests.
11808 - Add a macro to implement the common pattern of iterating through
11809 two parallel lists in lockstep.
11812 Changes in version 0.2.0.28-rc - 2008-06-13
11813 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
11814 performance bug, and fixes a bunch of smaller bugs.
11817 - Fix a bug where, when we were choosing the 'end stream reason' to
11818 put in our relay end cell that we send to the exit relay, Tor
11819 clients on Windows were sometimes sending the wrong 'reason'. The
11820 anonymity problem is that exit relays may be able to guess whether
11821 the client is running Windows, thus helping partition the anonymity
11822 set. Down the road we should stop sending reasons to exit relays,
11823 or otherwise prevent future versions of this bug.
11826 - While setting up a hidden service, some valid introduction circuits
11827 were overlooked and abandoned. This might be the reason for
11828 the long delay in making a hidden service available. Bugfix on
11832 - Update to the "June 9 2008" ip-to-country file.
11833 - Run 'make test' as part of 'make dist', so we stop releasing so
11834 many development snapshots that fail their unit tests.
11837 - When we're checking if we have enough dir info for each relay
11838 to begin establishing circuits, make sure that we actually have
11839 the descriptor listed in the consensus, not just any descriptor.
11841 - Bridge relays no longer print "xx=0" in their extrainfo document
11842 for every single country code in the geoip db. Bugfix on
11844 - Only warn when we fail to load the geoip file if we were planning to
11845 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
11846 - If we change our MaxAdvertisedBandwidth and then reload torrc,
11847 Tor won't realize it should publish a new relay descriptor. Fixes
11848 bug 688, reported by mfr. Bugfix on 0.1.2.x.
11849 - When we haven't had any application requests lately, don't bother
11850 logging that we have expired a bunch of descriptors. Bugfix
11852 - Make relay cells written on a connection count as non-padding when
11853 tracking how long a connection has been in use. Bugfix on
11854 0.2.0.1-alpha. Spotted by lodger.
11855 - Fix unit tests in 0.2.0.27-rc.
11856 - Fix compile on Windows.
11859 Changes in version 0.2.0.27-rc - 2008-06-03
11860 Tor 0.2.0.27-rc adds a few features we left out of the earlier
11861 release candidates. In particular, we now include an IP-to-country
11862 GeoIP database, so controllers can easily look up what country a
11863 given relay is in, and so bridge relays can give us some sanitized
11864 summaries about which countries are making use of bridges. (See proposal
11865 126-geoip-fetching.txt for details.)
11868 - Include an IP-to-country GeoIP file in the tarball, so bridge
11869 relays can report sanitized summaries of the usage they're seeing.
11872 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
11873 Robert Hogan. Fixes the first part of bug 681.
11874 - Make bridge authorities never serve extrainfo docs.
11875 - Add support to detect Libevent versions in the 1.4.x series
11877 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
11878 - Include a new contrib/tor-exit-notice.html file that exit relay
11879 operators can put on their website to help reduce abuse queries.
11882 - When tunneling an encrypted directory connection, and its first
11883 circuit fails, do not leave it unattached and ask the controller
11884 to deal. Fixes the second part of bug 681.
11885 - Make bridge authorities correctly expire old extrainfo documents
11889 Changes in version 0.2.0.26-rc - 2008-05-13
11890 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
11891 in Debian's OpenSSL packages. All users running any 0.2.0.x version
11892 should upgrade, whether they're running Debian or not.
11894 o Major security fixes:
11895 - Use new V3 directory authority keys on the tor26, gabelmoo, and
11896 moria1 V3 directory authorities. The old keys were generated with
11897 a vulnerable version of Debian's OpenSSL package, and must be
11898 considered compromised. Other authorities' keys were not generated
11899 with an affected version of OpenSSL.
11902 - List authority signatures as "unrecognized" based on DirServer
11903 lines, not on cert cache. Bugfix on 0.2.0.x.
11906 - Add a new V3AuthUseLegacyKey option to make it easier for
11907 authorities to change their identity keys if they have to.
11910 Changes in version 0.2.0.25-rc - 2008-04-23
11911 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
11914 - Remember to initialize threading before initializing logging.
11915 Otherwise, many BSD-family implementations will crash hard on
11916 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
11919 - Authorities correctly free policies on bad servers on
11920 exit. Fixes bug 672. Bugfix on 0.2.0.x.
11923 Changes in version 0.2.0.24-rc - 2008-04-22
11924 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
11925 v3 directory authority, makes relays with dynamic IP addresses and no
11926 DirPort notice more quickly when their IP address changes, fixes a few
11927 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
11929 o New directory authorities:
11930 - Take lefkada out of the list of v3 directory authorities, since
11931 it has been down for months.
11932 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
11936 - Detect address changes more quickly on non-directory mirror
11937 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
11939 o Minor features (security):
11940 - Reject requests for reverse-dns lookup of names that are in
11941 a private address space. Patch from lodger.
11942 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
11945 o Minor bugfixes (crashes):
11946 - Avoid a rare assert that can trigger when Tor doesn't have much
11947 directory information yet and it tries to fetch a v2 hidden
11948 service descriptor. Fixes bug 651, reported by nwf.
11949 - Initialize log mutex before initializing dmalloc. Otherwise,
11950 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
11951 - Use recursive pthread mutexes in order to avoid deadlock when
11952 logging debug-level messages to a controller. Bug spotted by nwf,
11953 bugfix on 0.2.0.16-alpha.
11955 o Minor bugfixes (resource management):
11956 - Keep address policies from leaking memory: start their refcount
11957 at 1, not 2. Bugfix on 0.2.0.16-alpha.
11958 - Free authority certificates on exit, so they don't look like memory
11959 leaks. Bugfix on 0.2.0.19-alpha.
11960 - Free static hashtables for policy maps and for TLS connections on
11961 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
11962 - Avoid allocating extra space when computing consensuses on 64-bit
11963 platforms. Bug spotted by aakova.
11965 o Minor bugfixes (misc):
11966 - Do not read the configuration file when we've only been told to
11967 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
11968 based on patch from Sebastian Hahn.
11969 - Exit relays that are used as a client can now reach themselves
11970 using the .exit notation, rather than just launching an infinite
11971 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
11972 - When attempting to open a logfile fails, tell us why.
11973 - Fix a dumb bug that was preventing us from knowing that we should
11974 preemptively build circuits to handle expected directory requests.
11975 Fixes bug 660. Bugfix on 0.1.2.x.
11976 - Warn less verbosely about clock skew from netinfo cells from
11977 untrusted sources. Fixes bug 663.
11978 - Make controller stream events for DNS requests more consistent,
11979 by adding "new stream" events for DNS requests, and removing
11980 spurious "stream closed" events" for cached reverse resolves.
11981 Patch from mwenge. Fixes bug 646.
11982 - Correctly notify one-hop connections when a circuit build has
11983 failed. Possible fix for bug 669. Found by lodger.
11986 Changes in version 0.2.0.23-rc - 2008-03-24
11987 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
11988 makes bootstrapping faster if the first directory mirror you contact
11989 is down. The bundles also include the new Vidalia 0.1.2 release.
11992 - When a tunneled directory request is made to a directory server
11993 that's down, notice after 30 seconds rather than 120 seconds. Also,
11994 fail any begindir streams that are pending on it, so they can
11995 retry elsewhere. This was causing multi-minute delays on bootstrap.
11998 Changes in version 0.2.0.22-rc - 2008-03-18
11999 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
12000 enables encrypted directory connections by default for non-relays, fixes
12001 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
12002 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
12005 - Enable encrypted directory connections by default for non-relays,
12006 so censor tools that block Tor directory connections based on their
12007 plaintext patterns will no longer work. This means Tor works in
12008 certain censored countries by default again.
12011 - Make sure servers always request certificates from clients during
12012 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
12013 - Do not enter a CPU-eating loop when a connection is closed in
12014 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
12015 diagnosed by lodger; bugfix on 0.2.0.20-rc.
12016 - Fix assertion failure that could occur when a blocked circuit
12017 became unblocked, and it had pending client DNS requests. Bugfix
12018 on 0.2.0.1-alpha. Fixes bug 632.
12020 o Minor bugfixes (on 0.1.2.x):
12021 - Generate "STATUS_SERVER" events rather than misspelled
12022 "STATUS_SEVER" events. Caught by mwenge.
12023 - When counting the number of bytes written on a TLS connection,
12024 look at the BIO actually used for writing to the network, not
12025 at the BIO used (sometimes) to buffer data for the network.
12026 Looking at different BIOs could result in write counts on the
12027 order of ULONG_MAX. Fixes bug 614.
12028 - On Windows, correctly detect errors when listing the contents of
12029 a directory. Fix from lodger.
12031 o Minor bugfixes (on 0.2.0.x):
12032 - Downgrade "sslv3 alert handshake failure" message to INFO.
12033 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
12034 left BandwidthRate and BandwidthBurst at the default, we would be
12035 silently limited by those defaults. Now raise them to match the
12036 RelayBandwidth* values.
12037 - Fix the SVK version detection logic to work correctly on a branch.
12038 - Make --enable-openbsd-malloc work correctly on Linux with alpha
12039 CPUs. Fixes bug 625.
12040 - Logging functions now check that the passed severity is sane.
12041 - Use proper log levels in the testsuite call of
12042 get_interface_address6().
12043 - When using a nonstandard malloc, do not use the platform values for
12044 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
12045 - Make the openbsd malloc code use 8k pages on alpha CPUs and
12047 - Detect mismatched page sizes when using --enable-openbsd-malloc.
12048 - Avoid double-marked-for-close warning when certain kinds of invalid
12049 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
12050 for bug 617. Bugfix on 0.2.0.1-alpha.
12051 - Make sure that the "NULL-means-reject *:*" convention is followed by
12052 all the policy manipulation functions, avoiding some possible crash
12053 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
12054 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
12055 actually works, and doesn't warn about every single reverse lookup.
12056 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
12059 - Only log guard node status when guard node status has changed.
12060 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
12061 make "INFO" 75% less verbose.
12064 Changes in version 0.2.0.21-rc - 2008-03-02
12065 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
12066 makes Tor work well with Vidalia again, fixes a rare assert bug,
12067 and fixes a pair of more minor bugs. The bundles also include Vidalia
12068 0.1.0 and Torbutton 1.1.16.
12071 - The control port should declare that it requires password auth
12072 when HashedControlSessionPassword is set too. Patch from Matt Edman;
12073 bugfix on 0.2.0.20-rc. Fixes bug 615.
12074 - Downgrade assert in connection_buckets_decrement() to a log message.
12075 This may help us solve bug 614, and in any case will make its
12076 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
12077 - We were sometimes miscounting the number of bytes read from the
12078 network, causing our rate limiting to not be followed exactly.
12079 Bugfix on 0.2.0.16-alpha. Reported by lodger.
12082 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
12083 OpenSSL versions should have been working fine. Diagnosis and patch
12084 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
12085 Bugfix on 0.2.0.20-rc.
12088 Changes in version 0.2.0.20-rc - 2008-02-24
12089 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
12090 makes more progress towards normalizing Tor's TLS handshake, makes
12091 hidden services work better again, helps relays bootstrap if they don't
12092 know their IP address, adds optional support for linking in openbsd's
12093 allocator or tcmalloc, allows really fast relays to scale past 15000
12094 sockets, and fixes a bunch of minor bugs reported by Veracode.
12097 - Enable the revised TLS handshake based on the one designed by
12098 Steven Murdoch in proposal 124, as revised in proposal 130. It
12099 includes version negotiation for OR connections as described in
12100 proposal 105. The new handshake is meant to be harder for censors
12101 to fingerprint, and it adds the ability to detect certain kinds of
12102 man-in-the-middle traffic analysis attacks. The version negotiation
12103 feature will allow us to improve Tor's link protocol more safely
12105 - Choose which bridge to use proportional to its advertised bandwidth,
12106 rather than uniformly at random. This should speed up Tor for
12107 bridge users. Also do this for people who set StrictEntryNodes.
12108 - When a TrackHostExits-chosen exit fails too many times in a row,
12109 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
12112 - Resolved problems with (re-)fetching hidden service descriptors.
12113 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
12114 and 0.2.0.19-alpha.
12115 - If we only ever used Tor for hidden service lookups or posts, we
12116 would stop building circuits and start refusing connections after
12117 24 hours, since we falsely believed that Tor was dormant. Reported
12118 by nwf; bugfix on 0.1.2.x.
12119 - Servers that don't know their own IP address should go to the
12120 authorities for their first directory fetch, even if their DirPort
12121 is off or if they don't know they're reachable yet. This will help
12122 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
12123 - When counting the number of open sockets, count not only the number
12124 of sockets we have received from the socket() call, but also
12125 the number we've gotten from accept() and socketpair(). This bug
12126 made us fail to count all sockets that we were using for incoming
12127 connections. Bugfix on 0.2.0.x.
12128 - Fix code used to find strings within buffers, when those strings
12129 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
12130 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
12131 - Add a new __HashedControlSessionPassword option for controllers
12132 to use for one-off session password hashes that shouldn't get
12133 saved to disk by SAVECONF --- Vidalia users were accumulating a
12134 pile of HashedControlPassword lines in their torrc files, one for
12135 each time they had restarted Tor and then clicked Save. Make Tor
12136 automatically convert "HashedControlPassword" to this new option but
12137 only when it's given on the command line. Partial fix for bug 586.
12139 o Minor features (performance):
12140 - Tune parameters for cell pool allocation to minimize amount of
12142 - Add OpenBSD malloc code from phk as an optional malloc
12143 replacement on Linux: some glibc libraries do very poorly
12144 with Tor's memory allocation patterns. Pass
12145 --enable-openbsd-malloc to get the replacement malloc code.
12146 - Add a --with-tcmalloc option to the configure script to link
12147 against tcmalloc (if present). Does not yet search for
12148 non-system include paths.
12149 - Stop imposing an arbitrary maximum on the number of file descriptors
12150 used for busy servers. Bug reported by Olaf Selke; patch from
12153 o Minor features (other):
12154 - When SafeLogging is disabled, log addresses along with all TLS
12156 - When building with --enable-gcc-warnings, check for whether Apple's
12157 warning "-Wshorten-64-to-32" is available.
12158 - Add a --passphrase-fd argument to the tor-gencert command for
12161 o Minor bugfixes (memory leaks and code problems):
12162 - We were leaking a file descriptor if Tor started with a zero-length
12163 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
12164 - Detect size overflow in zlib code. Reported by Justin Ferguson and
12166 - We were comparing the raw BridgePassword entry with a base64'ed
12167 version of it, when handling a "/tor/networkstatus-bridges"
12168 directory request. Now compare correctly. Noticed by Veracode.
12169 - Recover from bad tracked-since value in MTBF-history file.
12170 Should fix bug 537.
12171 - Alter the code that tries to recover from unhandled write
12172 errors, to not try to flush onto a socket that's given us
12173 unhandled errors. Bugfix on 0.1.2.x.
12174 - Make Unix controlsockets work correctly on OpenBSD. Patch from
12175 tup. Bugfix on 0.2.0.3-alpha.
12177 o Minor bugfixes (other):
12178 - If we have an extra-info document for our server, always make
12179 it available on the control port, even if we haven't gotten
12180 a copy of it from an authority yet. Patch from mwenge.
12181 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
12182 - Directory mirrors no longer include a guess at the client's IP
12183 address if the connection appears to be coming from the same /24
12184 network; it was producing too many wrong guesses.
12185 - Make the new hidden service code respect the SafeLogging setting.
12186 Bugfix on 0.2.0.x. Patch from Karsten.
12187 - When starting as an authority, do not overwrite all certificates
12188 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
12189 - If we're trying to flush the last bytes on a connection (for
12190 example, when answering a directory request), reset the
12191 time-to-give-up timeout every time we manage to write something
12192 on the socket. Bugfix on 0.1.2.x.
12193 - Change the behavior of "getinfo status/good-server-descriptor"
12194 so it doesn't return failure when any authority disappears.
12195 - Even though the man page said that "TrackHostExits ." should
12196 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
12197 - Report TLS "zero return" case as a "clean close" and "IO error"
12198 as a "close". Stop calling closes "unexpected closes": existing
12199 Tors don't use SSL_close(), so having a connection close without
12200 the TLS shutdown handshake is hardly unexpected.
12201 - Send NAMESERVER_STATUS messages for a single failed nameserver
12204 o Code simplifications and refactoring:
12205 - Remove the tor_strpartition function: its logic was confused,
12206 and it was only used for one thing that could be implemented far
12210 Changes in version 0.2.0.19-alpha - 2008-02-09
12211 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
12212 handshake, makes path selection for relays more secure and IP address
12213 guessing more robust, and generally fixes a lot of bugs in preparation
12214 for calling the 0.2.0 branch stable.
12217 - Do not include recognizeable strings in the commonname part of
12218 Tor's x509 certificates.
12221 - If we're a relay, avoid picking ourselves as an introduction point,
12222 a rendezvous point, or as the final hop for internal circuits. Bug
12223 reported by taranis and lodger. Bugfix on 0.1.2.x.
12224 - Patch from "Andrew S. Lists" to catch when we contact a directory
12225 mirror at IP address X and he says we look like we're coming from
12226 IP address X. Bugfix on 0.1.2.x.
12228 o Minor features (security):
12229 - Be more paranoid about overwriting sensitive memory on free(),
12230 as a defensive programming tactic to ensure forward secrecy.
12232 o Minor features (directory authority):
12233 - Actually validate the options passed to AuthDirReject,
12234 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
12235 - Reject router descriptors with out-of-range bandwidthcapacity or
12236 bandwidthburst values.
12238 o Minor features (controller):
12239 - Reject controller commands over 1MB in length. This keeps rogue
12240 processes from running us out of memory.
12242 o Minor features (misc):
12243 - Give more descriptive well-formedness errors for out-of-range
12244 hidden service descriptor/protocol versions.
12245 - Make memory debugging information describe more about history
12246 of cell allocation, so we can help reduce our memory use.
12248 o Deprecated features (controller):
12249 - The status/version/num-versioning and status/version/num-concurring
12250 GETINFO options are no longer useful in the v3 directory protocol:
12251 treat them as deprecated, and warn when they're used.
12254 - When our consensus networkstatus has been expired for a while, stop
12255 being willing to build circuits using it. Fixes bug 401. Bugfix
12257 - Directory caches now fetch certificates from all authorities
12258 listed in a networkstatus consensus, even when they do not
12259 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
12260 - When connecting to a bridge without specifying its key, insert
12261 the connection into the identity-to-connection map as soon as
12262 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
12263 - Detect versions of OS X where malloc_good_size() is present in the
12264 library but never actually declared. Resolves bug 587. Bugfix
12266 - Stop incorrectly truncating zlib responses to directory authority
12267 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
12268 - Stop recommending that every server operator send mail to tor-ops.
12269 Resolves bug 597. Bugfix on 0.1.2.x.
12270 - Don't trigger an assert if we start a directory authority with a
12271 private IP address (like 127.0.0.1).
12272 - Avoid possible failures when generating a directory with routers
12273 with over-long versions strings, or too many flags set. Bugfix
12275 - If an attempt to launch a DNS resolve request over the control
12276 port fails because we have overrun the limit on the number of
12277 connections, tell the controller that the request has failed.
12278 - Avoid using too little bandwidth when our clock skips a few
12279 seconds. Bugfix on 0.1.2.x.
12280 - Fix shell error when warning about missing packages in configure
12281 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
12282 - Do not become confused when receiving a spurious VERSIONS-like
12283 cell from a confused v1 client. Bugfix on 0.2.0.x.
12284 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
12285 introduction points for a hidden service have failed. Patch from
12286 Karsten Loesing. Bugfix on 0.2.0.x.
12288 o Code simplifications and refactoring:
12289 - Remove some needless generality from cpuworker code, for improved
12291 - Stop overloading the circuit_t.onionskin field for both "onionskin
12292 from a CREATE cell that we are waiting for a cpuworker to be
12293 assigned" and "onionskin from an EXTEND cell that we are going to
12294 send to an OR as soon as we are connected". Might help with bug 600.
12295 - Add an in-place version of aes_crypt() so that we can avoid doing a
12296 needless memcpy() call on each cell payload.
12299 Changes in version 0.2.0.18-alpha - 2008-01-25
12300 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
12301 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
12302 that can warn or reject connections to ports generally associated with
12303 vulnerable-plaintext protocols.
12305 o New directory authorities:
12306 - Set up dannenberg (run by CCC) as the sixth v3 directory
12310 - Fix a major memory leak when attempting to use the v2 TLS
12311 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
12312 - We accidentally enabled the under-development v2 TLS handshake
12313 code, which was causing log entries like "TLS error while
12314 renegotiating handshake". Disable it again. Resolves bug 590.
12315 - We were computing the wrong Content-Length: header for directory
12316 responses that need to be compressed on the fly, causing clients
12317 asking for those items to always fail. Bugfix on 0.2.0.x; partially
12321 - Avoid going directly to the directory authorities even if you're a
12322 relay, if you haven't found yourself reachable yet or if you've
12323 decided not to advertise your dirport yet. Addresses bug 556.
12324 - If we've gone 12 hours since our last bandwidth check, and we
12325 estimate we have less than 50KB bandwidth capacity but we could
12326 handle more, do another bandwidth test.
12327 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
12328 Tor can warn and/or refuse connections to ports commonly used with
12329 vulnerable-plaintext protocols. Currently we warn on ports 23,
12330 109, 110, and 143, but we don't reject any.
12333 - When we setconf ClientOnly to 1, close any current OR and Dir
12334 listeners. Reported by mwenge.
12335 - When we get a consensus that's been signed by more people than
12336 we expect, don't log about it; it's not a big deal. Reported
12340 - Don't answer "/tor/networkstatus-bridges" directory requests if
12341 the request isn't encrypted.
12342 - Make "ClientOnly 1" config option disable directory ports too.
12343 - Patches from Karsten Loesing to make v2 hidden services more
12344 robust: work even when there aren't enough HSDir relays available;
12345 retry when a v2 rend desc fetch fails; but don't retry if we
12346 already have a usable v0 rend desc.
12349 Changes in version 0.2.0.17-alpha - 2008-01-17
12350 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
12353 - Make the tor-gencert man page get included correctly in the tarball.
12356 Changes in version 0.2.0.16-alpha - 2008-01-17
12357 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
12358 Loesing, and generally cleans up a lot of features and minor bugs.
12360 o New directory authorities:
12361 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
12364 o Major performance improvements:
12365 - Switch our old ring buffer implementation for one more like that
12366 used by free Unix kernels. The wasted space in a buffer with 1mb
12367 of data will now be more like 8k than 1mb. The new implementation
12368 also avoids realloc();realloc(); patterns that can contribute to
12369 memory fragmentation.
12372 - Configuration files now accept C-style strings as values. This
12373 helps encode characters not allowed in the current configuration
12374 file format, such as newline or #. Addresses bug 557.
12375 - Although we fixed bug 539 (where servers would send HTTP status 503
12376 responses _and_ send a body too), there are still servers out
12377 there that haven't upgraded. Therefore, make clients parse such
12378 bodies when they receive them.
12379 - When we're not serving v2 directory information, there is no reason
12380 to actually keep any around. Remove the obsolete files and directory
12381 on startup if they are very old and we aren't going to serve them.
12383 o Minor performance improvements:
12384 - Reference-count and share copies of address policy entries; only 5%
12385 of them were actually distinct.
12386 - Never walk through the list of logs if we know that no log is
12387 interested in a given message.
12390 - When an authority has not signed a consensus, do not try to
12391 download a nonexistent "certificate with key 00000000". Bugfix
12392 on 0.2.0.x. Fixes bug 569.
12393 - Fix a rare assert error when we're closing one of our threads:
12394 use a mutex to protect the list of logs, so we never write to the
12395 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
12396 bug 575, which is kind of the revenge of bug 222.
12397 - Patch from Karsten Loesing to complain less at both the client
12398 and the relay when a relay used to have the HSDir flag but doesn't
12399 anymore, and we try to upload a hidden service descriptor.
12400 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
12402 - Do not try to download missing certificates until we have tried
12403 to check our fallback consensus. Fixes bug 583.
12404 - Make bridges round reported GeoIP stats info up to the nearest
12405 estimate, not down. Now we can distinguish between "0 people from
12406 this country" and "1 person from this country".
12407 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
12408 - Avoid possible segfault if key generation fails in
12409 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
12410 - Avoid segfault in the case where a badly behaved v2 versioning
12411 directory sends a signed networkstatus with missing client-versions.
12413 - Avoid segfaults on certain complex invocations of
12414 router_get_by_hexdigest(). Bugfix on 0.1.2.
12415 - Correct bad index on array access in parse_http_time(). Bugfix
12417 - Fix possible bug in vote generation when server versions are present
12418 but client versions are not.
12419 - Fix rare bug on REDIRECTSTREAM control command when called with no
12420 port set: it could erroneously report an error when none had
12422 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
12423 compressing large objects and find ourselves with more than 4k
12424 left over. Bugfix on 0.2.0.
12425 - Fix a small memory leak when setting up a hidden service.
12426 - Fix a few memory leaks that could in theory happen under bizarre
12428 - Fix an assert if we post a general-purpose descriptor via the
12429 control port but that descriptor isn't mentioned in our current
12430 network consensus. Bug reported by Jon McLachlan; bugfix on
12433 o Minor features (controller):
12434 - Get NS events working again. Patch from tup.
12435 - The GETCONF command now escapes and quotes configuration values
12436 that don't otherwise fit into the torrc file.
12437 - The SETCONF command now handles quoted values correctly.
12439 o Minor features (directory authorities):
12440 - New configuration options to override default maximum number of
12441 servers allowed on a single IP address. This is important for
12442 running a test network on a single host.
12443 - Actually implement the -s option to tor-gencert.
12444 - Add a manual page for tor-gencert.
12446 o Minor features (bridges):
12447 - Bridge authorities no longer serve bridge descriptors over
12448 unencrypted connections.
12450 o Minor features (other):
12451 - Add hidden services and DNSPorts to the list of things that make
12452 Tor accept that it has running ports. Change starting Tor with no
12453 ports from a fatal error to a warning; we might change it back if
12454 this turns out to confuse anybody. Fixes bug 579.
12457 Changes in version 0.1.2.19 - 2008-01-17
12458 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
12459 exit policy a little bit more conservative so it's safer to run an
12460 exit relay on a home system, and fixes a variety of smaller issues.
12463 - Exit policies now reject connections that are addressed to a
12464 relay's public (external) IP address too, unless
12465 ExitPolicyRejectPrivate is turned off. We do this because too
12466 many relays are running nearby to services that trust them based
12467 on network address.
12470 - When the clock jumps forward a lot, do not allow the bandwidth
12471 buckets to become negative. Fixes bug 544.
12472 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
12473 on every successful resolve. Reported by Mike Perry.
12474 - Purge old entries from the "rephist" database and the hidden
12475 service descriptor database even when DirPort is zero.
12476 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
12477 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
12478 crashing or mis-answering these requests.
12479 - When we decide to send a 503 response to a request for servers, do
12480 not then also send the server descriptors: this defeats the whole
12481 purpose. Fixes bug 539.
12484 - Changing the ExitPolicyRejectPrivate setting should cause us to
12485 rebuild our server descriptor.
12486 - Fix handling of hex nicknames when answering controller requests for
12487 networkstatus by name, or when deciding whether to warn about
12488 unknown routers in a config option. (Patch from mwenge.)
12489 - Fix a couple of hard-to-trigger autoconf problems that could result
12490 in really weird results on platforms whose sys/types.h files define
12491 nonstandard integer types.
12492 - Don't try to create the datadir when running --verify-config or
12493 --hash-password. Resolves bug 540.
12494 - If we were having problems getting a particular descriptor from the
12495 directory caches, and then we learned about a new descriptor for
12496 that router, we weren't resetting our failure count. Reported
12498 - Although we fixed bug 539 (where servers would send HTTP status 503
12499 responses _and_ send a body too), there are still servers out there
12500 that haven't upgraded. Therefore, make clients parse such bodies
12501 when they receive them.
12502 - Run correctly on systems where rlim_t is larger than unsigned long.
12503 This includes some 64-bit systems.
12504 - Run correctly on platforms (like some versions of OS X 10.5) where
12505 the real limit for number of open files is OPEN_FILES, not rlim_max
12506 from getrlimit(RLIMIT_NOFILES).
12507 - Avoid a spurious free on base64 failure.
12508 - Avoid segfaults on certain complex invocations of
12509 router_get_by_hexdigest().
12510 - Fix rare bug on REDIRECTSTREAM control command when called with no
12511 port set: it could erroneously report an error when none had
12515 Changes in version 0.2.0.15-alpha - 2007-12-25
12516 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
12517 features added in 0.2.0.13-alpha.
12520 - Fix several remotely triggerable asserts based on DirPort requests
12521 for a v2 or v3 networkstatus object before we were prepared. This
12522 was particularly bad for 0.2.0.13 and later bridge relays, who
12523 would never have a v2 networkstatus and would thus always crash
12524 when used. Bugfixes on 0.2.0.x.
12525 - Estimate the v3 networkstatus size more accurately, rather than
12526 estimating it at zero bytes and giving it artificially high priority
12527 compared to other directory requests. Bugfix on 0.2.0.x.
12530 - Fix configure.in logic for cross-compilation.
12531 - When we load a bridge descriptor from the cache, and it was
12532 previously unreachable, mark it as retriable so we won't just
12533 ignore it. Also, try fetching a new copy immediately. Bugfixes
12535 - The bridge GeoIP stats were counting other relays, for example
12536 self-reachability and authority-reachability tests.
12539 - Support compilation to target iPhone; patch from cjacker huang.
12540 To build for iPhone, pass the --enable-iphone option to configure.
12543 Changes in version 0.2.0.14-alpha - 2007-12-23
12545 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
12546 without a datadirectory from a previous Tor install. Reported
12548 - Fix a crash when we fetch a descriptor that turns out to be
12549 unexpected (it used to be in our networkstatus when we started
12550 fetching it, but it isn't in our current networkstatus), and we
12551 aren't using bridges. Bugfix on 0.2.0.x.
12552 - Fix a crash when accessing hidden services: it would work the first
12553 time you use a given introduction point for your service, but
12554 on subsequent requests we'd be using garbage memory. Fixed by
12555 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
12556 - Fix a crash when we load a bridge descriptor from disk but we don't
12557 currently have a Bridge line for it in our torrc. Bugfix on
12561 - If bridge authorities set BridgePassword, they will serve a
12562 snapshot of known bridge routerstatuses from their DirPort to
12563 anybody who knows that password. Unset by default.
12566 - Make the unit tests build again.
12567 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
12568 - Make PublishServerDescriptor default to 1, so the default doesn't
12569 have to change as we invent new directory protocol versions.
12570 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
12571 be included unless sys/time.h is already included. Fixes
12572 bug 553. Bugfix on 0.2.0.x.
12573 - If we receive a general-purpose descriptor and then receive an
12574 identical bridge-purpose descriptor soon after, don't discard
12575 the next one as a duplicate.
12578 - If BridgeRelay is set to 1, then the default for
12579 PublishServerDescriptor is now "bridge" rather than "v2,v3".
12580 - If the user sets RelayBandwidthRate but doesn't set
12581 RelayBandwidthBurst, then make them equal rather than erroring out.
12584 Changes in version 0.2.0.13-alpha - 2007-12-21
12585 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
12586 Goodell, fixes many more bugs, and adds a lot of infrastructure for
12589 o New directory authorities:
12590 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
12594 - Only update guard status (usable / not usable) once we have
12595 enough directory information. This was causing us to always pick
12596 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
12597 causing us to discard all our guards on startup if we hadn't been
12598 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
12599 - Purge old entries from the "rephist" database and the hidden
12600 service descriptor databases even when DirPort is zero. Bugfix
12602 - We were ignoring our RelayBandwidthRate for the first 30 seconds
12603 after opening a circuit -- even a relayed circuit. Bugfix on
12605 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
12606 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
12607 crashing or mis-answering these types of requests.
12608 - Relays were publishing their server descriptor to v1 and v2
12609 directory authorities, but they didn't try publishing to v3-only
12610 authorities. Fix this; and also stop publishing to v1 authorities.
12612 - When we were reading router descriptors from cache, we were ignoring
12613 the annotations -- so for example we were reading in bridge-purpose
12614 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
12615 - When we decided to send a 503 response to a request for servers, we
12616 were then also sending the server descriptors: this defeats the
12617 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
12620 - Bridge relays now behave like clients with respect to time
12621 intervals for downloading new consensus documents -- otherwise they
12622 stand out. Bridge users now wait until the end of the interval,
12623 so their bridge relay will be sure to have a new consensus document.
12624 - Three new config options (AlternateDirAuthority,
12625 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
12626 user selectively replace the default directory authorities by type,
12627 rather than the all-or-nothing replacement that DirServer offers.
12628 - Tor can now be configured to read a GeoIP file from disk in one
12629 of two formats. This can be used by controllers to map IP addresses
12630 to countries. Eventually, it may support exit-by-country.
12631 - When possible, bridge relays remember which countries users
12632 are coming from, and report aggregate information in their
12633 extra-info documents, so that the bridge authorities can learn
12634 where Tor is blocked.
12635 - Bridge directory authorities now do reachability testing on the
12636 bridges they know. They provide router status summaries to the
12637 controller via "getinfo ns/purpose/bridge", and also dump summaries
12638 to a file periodically.
12639 - Stop fetching directory info so aggressively if your DirPort is
12640 on but your ORPort is off; stop fetching v2 dir info entirely.
12641 You can override these choices with the new FetchDirInfoEarly
12645 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
12646 consensus documents when there are too many relays at a single
12647 IP address. Now clear it in v2 network status documents too, and
12648 also clear it in routerinfo_t when the relay is no longer listed
12649 in the relevant networkstatus document.
12650 - Don't crash if we get an unexpected value for the
12651 PublishServerDescriptor config option. Reported by Matt Edman;
12652 bugfix on 0.2.0.9-alpha.
12653 - Our new v2 hidden service descriptor format allows descriptors
12654 that have no introduction points. But Tor crashed when we tried
12655 to build a descriptor with no intro points (and it would have
12656 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
12657 by Karsten Loesing.
12658 - Fix building with dmalloc 5.5.2 with glibc.
12659 - Reject uploaded descriptors and extrainfo documents if they're
12660 huge. Otherwise we'll cache them all over the network and it'll
12661 clog everything up. Reported by Aljosha Judmayer.
12662 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
12663 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
12664 - When the DANGEROUS_VERSION controller status event told us we're
12665 running an obsolete version, it used the string "OLD" to describe
12666 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
12667 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
12668 - If we can't expand our list of entry guards (e.g. because we're
12669 using bridges or we have StrictEntryNodes set), don't mark relays
12670 down when they fail a directory request. Otherwise we're too quick
12671 to mark all our entry points down. Bugfix on 0.1.2.x.
12672 - Fix handling of hex nicknames when answering controller requests for
12673 networkstatus by name, or when deciding whether to warn about unknown
12674 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
12675 - Fix a couple of hard-to-trigger autoconf problems that could result
12676 in really weird results on platforms whose sys/types.h files define
12677 nonstandard integer types. Bugfix on 0.1.2.x.
12678 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
12679 - Don't crash on name lookup when we have no current consensus. Fixes
12680 bug 538; bugfix on 0.2.0.x.
12681 - Only Tors that want to mirror the v2 directory info should
12682 create the "cached-status" directory in their datadir. (All Tors
12683 used to create it.) Bugfix on 0.2.0.9-alpha.
12684 - Directory authorities should only automatically download Extra Info
12685 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
12688 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
12689 consumers. (We already do this on HUP.)
12690 - Authorities and caches fetch the v2 networkstatus documents
12691 less often, now that v3 is encouraged.
12692 - Add a new config option BridgeRelay that specifies you want to
12693 be a bridge relay. Right now the only difference is that it makes
12694 you answer begin_dir requests, and it makes you cache dir info,
12695 even if your DirPort isn't on.
12696 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
12697 ask about source, timestamp of arrival, purpose, etc. We need
12698 something like this to help Vidalia not do GeoIP lookups on bridge
12700 - Allow multiple HashedControlPassword config lines, to support
12701 multiple controller passwords.
12702 - Authorities now decide whether they're authoritative for a given
12703 router based on the router's purpose.
12704 - New config options AuthDirBadDir and AuthDirListBadDirs for
12705 authorities to mark certain relays as "bad directories" in the
12706 networkstatus documents. Also supports the "!baddir" directive in
12707 the approved-routers file.
12710 Changes in version 0.2.0.12-alpha - 2007-11-16
12711 This twelfth development snapshot fixes some more build problems as
12712 well as a few minor bugs.
12715 - Make it build on OpenBSD again. Patch from tup.
12716 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
12717 package-building for Red Hat, OS X, etc.
12719 o Minor bugfixes (on 0.1.2.x):
12720 - Changing the ExitPolicyRejectPrivate setting should cause us to
12721 rebuild our server descriptor.
12723 o Minor bugfixes (on 0.2.0.x):
12724 - When we're lacking a consensus, don't try to perform rendezvous
12725 operations. Reported by Karsten Loesing.
12726 - Fix a small memory leak whenever we decide against using a
12727 newly picked entry guard. Reported by Mike Perry.
12728 - When authorities detected more than two relays running on the same
12729 IP address, they were clearing all the status flags but forgetting
12730 to clear the "hsdir" flag. So clients were being told that a
12731 given relay was the right choice for a v2 hsdir lookup, yet they
12732 never had its descriptor because it was marked as 'not running'
12734 - If we're trying to fetch a bridge descriptor and there's no way
12735 the bridge authority could help us (for example, we don't know
12736 a digest, or there is no bridge authority), don't be so eager to
12737 fall back to asking the bridge authority.
12738 - If we're using bridges or have strictentrynodes set, and our
12739 chosen exit is in the same family as all our bridges/entry guards,
12740 then be flexible about families.
12743 - When we negotiate a v2 link-layer connection (not yet implemented),
12744 accept RELAY_EARLY cells and turn them into RELAY cells if we've
12745 negotiated a v1 connection for their next step. Initial code for
12749 Changes in version 0.2.0.11-alpha - 2007-11-12
12750 This eleventh development snapshot fixes some build problems with
12751 the previous snapshot. It also includes a more secure-by-default exit
12752 policy for relays, fixes an enormous memory leak for exit relays, and
12753 fixes another bug where servers were falling out of the directory list.
12756 - Exit policies now reject connections that are addressed to a
12757 relay's public (external) IP address too, unless
12758 ExitPolicyRejectPrivate is turned off. We do this because too
12759 many relays are running nearby to services that trust them based
12760 on network address. Bugfix on 0.1.2.x.
12763 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
12764 on every successful resolve. Reported by Mike Perry; bugfix
12766 - On authorities, never downgrade to old router descriptors simply
12767 because they're listed in the consensus. This created a catch-22
12768 where we wouldn't list a new descriptor because there was an
12769 old one in the consensus, and we couldn't get the new one in the
12770 consensus because we wouldn't list it. Possible fix for bug 548.
12771 Also, this might cause bug 543 to appear on authorities; if so,
12772 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
12774 o Packaging fixes on 0.2.0.10-alpha:
12775 - We were including instructions about what to do with the
12776 src/config/fallback-consensus file, but we weren't actually
12777 including it in the tarball. Disable all of that for now.
12780 - Allow people to say PreferTunnelledDirConns rather than
12781 PreferTunneledDirConns, for those alternate-spellers out there.
12784 - Don't reevaluate all the information from our consensus document
12785 just because we've downloaded a v2 networkstatus that we intend
12786 to cache. Fixes bug 545; bugfix on 0.2.0.x.
12789 Changes in version 0.2.0.10-alpha - 2007-11-10
12790 This tenth development snapshot adds a third v3 directory authority
12791 run by Mike Perry, adds most of Karsten Loesing's new hidden service
12792 descriptor format, fixes a bad crash bug and new bridge bugs introduced
12793 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
12794 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
12795 addresses many more minor issues.
12797 o New directory authorities:
12798 - Set up ides (run by Mike Perry) as the third v3 directory authority.
12801 - Allow tunnelled directory connections to ask for an encrypted
12802 "begin_dir" connection or an anonymized "uses a full Tor circuit"
12803 connection independently. Now we can make anonymized begin_dir
12804 connections for (e.g.) more secure hidden service posting and
12806 - More progress on proposal 114: code from Karsten Loesing to
12807 implement new hidden service descriptor format.
12808 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
12809 accommodate the growing number of servers that use the default
12810 and are reaching it.
12811 - Directory authorities use a new formula for selecting which nodes
12812 to advertise as Guards: they must be in the top 7/8 in terms of
12813 how long we have known about them, and above the median of those
12814 nodes in terms of weighted fractional uptime.
12815 - Make "not enough dir info yet" warnings describe *why* Tor feels
12816 it doesn't have enough directory info yet.
12819 - Stop servers from crashing if they set a Family option (or
12820 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
12822 - Make bridge users work again -- the move to v3 directories in
12823 0.2.0.9-alpha had introduced a number of bugs that made bridges
12824 no longer work for clients.
12825 - When the clock jumps forward a lot, do not allow the bandwidth
12826 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
12828 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
12829 - When the consensus lists a router descriptor that we previously were
12830 mirroring, but that we considered non-canonical, reload the
12831 descriptor as canonical. This fixes bug 543 where Tor servers
12832 would start complaining after a few days that they don't have
12833 enough directory information to build a circuit.
12834 - Consider replacing the current consensus when certificates arrive
12835 that make the pending consensus valid. Previously, we were only
12836 considering replacement when the new certs _didn't_ help.
12837 - Fix an assert error on startup if we didn't already have the
12838 consensus and certs cached in our datadirectory: we were caching
12839 the consensus in consensus_waiting_for_certs but then free'ing it
12841 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
12842 Request) if we need more v3 certs but we've already got pending
12843 requests for all of them.
12844 - Correctly back off from failing certificate downloads. Fixes
12846 - Authorities don't vote on the Running flag if they have been running
12847 for less than 30 minutes themselves. Fixes bug 547, where a newly
12848 started authority would vote that everyone was down.
12850 o New requirements:
12851 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
12852 it, it had no AES, and it hasn't seen any security patches since
12856 - Clients now hold circuitless TLS connections open for 1.5 times
12857 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
12858 rebuild a new circuit over them within that timeframe. Previously,
12859 they held them open only for KeepalivePeriod (5 minutes).
12860 - Use "If-Modified-Since" to avoid retrieving consensus
12861 networkstatuses that we already have.
12862 - When we have no consensus, check FallbackNetworkstatusFile (defaults
12863 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
12864 we start knowing some directory caches.
12865 - When we receive a consensus from the future, warn about skew.
12866 - Improve skew reporting: try to give the user a better log message
12867 about how skewed they are, and how much this matters.
12868 - When we have a certificate for an authority, believe that
12869 certificate's claims about the authority's IP address.
12870 - New --quiet command-line option to suppress the default console log.
12871 Good in combination with --hash-password.
12872 - Authorities send back an X-Descriptor-Not-New header in response to
12873 an accepted-but-discarded descriptor upload. Partially implements
12875 - Make the log message for "tls error. breaking." more useful.
12876 - Better log messages about certificate downloads, to attempt to
12877 track down the second incarnation of bug 546.
12879 o Minor features (bridges):
12880 - If bridge users set UpdateBridgesFromAuthority, but the digest
12881 they ask for is a 404 from the bridge authority, they now fall
12882 back to trying the bridge directly.
12883 - Bridges now use begin_dir to publish their server descriptor to
12884 the bridge authority, even when they haven't set TunnelDirConns.
12886 o Minor features (controller):
12887 - When reporting clock skew, and we know that the clock is _at least
12888 as skewed_ as some value, but we don't know the actual value,
12889 report the value as a "minimum skew."
12892 - Update linux-tor-prio.sh script to allow QoS based on the uid of
12893 the Tor process. Patch from Marco Bonetti with tweaks from Mike
12897 - Refuse to start if both ORPort and UseBridges are set. Bugfix
12898 on 0.2.0.x, suggested by Matt Edman.
12899 - Don't stop fetching descriptors when FetchUselessDescriptors is
12900 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
12901 reported by tup and ioerror.
12902 - Better log message on vote from unknown authority.
12903 - Don't log "Launching 0 request for 0 router" message.
12905 o Minor bugfixes (memory leaks):
12906 - Stop leaking memory every time we parse a v3 certificate. Bugfix
12908 - Stop leaking memory every time we load a v3 certificate. Bugfix
12909 on 0.2.0.1-alpha. Fixes bug 536.
12910 - Stop leaking a cached networkstatus on exit. Bugfix on
12912 - Stop leaking voter information every time we free a consensus.
12913 Bugfix on 0.2.0.3-alpha.
12914 - Stop leaking signed data every time we check a voter signature.
12915 Bugfix on 0.2.0.3-alpha.
12916 - Stop leaking a signature every time we fail to parse a consensus or
12917 a vote. Bugfix on 0.2.0.3-alpha.
12918 - Stop leaking v2_download_status_map on shutdown. Bugfix on
12920 - Stop leaking conn->nickname every time we make a connection to a
12921 Tor relay without knowing its expected identity digest (e.g. when
12922 using bridges). Bugfix on 0.2.0.3-alpha.
12924 - Minor bugfixes (portability):
12925 - Run correctly on platforms where rlim_t is larger than unsigned
12926 long, and/or where the real limit for number of open files is
12927 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
12928 particular, these may be needed for OS X 10.5.
12931 Changes in version 0.1.2.18 - 2007-10-28
12932 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
12933 hidden service introduction that were causing huge delays, and a big
12934 bug that was causing some servers to disappear from the network status
12935 lists for a few hours each day.
12937 o Major bugfixes (crashes):
12938 - If a connection is shut down abruptly because of something that
12939 happened inside connection_flushed_some(), do not call
12940 connection_finished_flushing(). Should fix bug 451:
12941 "connection_stop_writing: Assertion conn->write_event failed"
12942 Bugfix on 0.1.2.7-alpha.
12943 - Fix possible segfaults in functions called from
12944 rend_process_relay_cell().
12946 o Major bugfixes (hidden services):
12947 - Hidden services were choosing introduction points uniquely by
12948 hexdigest, but when constructing the hidden service descriptor
12949 they merely wrote the (potentially ambiguous) nickname.
12950 - Clients now use the v2 intro format for hidden service
12951 connections: they specify their chosen rendezvous point by identity
12952 digest rather than by (potentially ambiguous) nickname. These
12953 changes could speed up hidden service connections dramatically.
12955 o Major bugfixes (other):
12956 - Stop publishing a new server descriptor just because we get a
12957 HUP signal. This led (in a roundabout way) to some servers getting
12958 dropped from the networkstatus lists for a few hours each day.
12959 - When looking for a circuit to cannibalize, consider family as well
12960 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
12961 circuit cannibalization).
12962 - When a router wasn't listed in a new networkstatus, we were leaving
12963 the flags for that router alone -- meaning it remained Named,
12964 Running, etc -- even though absence from the networkstatus means
12965 that it shouldn't be considered to exist at all anymore. Now we
12966 clear all the flags for routers that fall out of the networkstatus
12967 consensus. Fixes bug 529.
12970 - Don't try to access (or alter) the state file when running
12971 --list-fingerprint or --verify-config or --hash-password. Resolves
12973 - When generating information telling us how to extend to a given
12974 router, do not try to include the nickname if it is
12975 absent. Resolves bug 467.
12976 - Fix a user-triggerable segfault in expand_filename(). (There isn't
12977 a way to trigger this remotely.)
12978 - When sending a status event to the controller telling it that an
12979 OR address is reachable, set the port correctly. (Previously we
12980 were reporting the dir port.)
12981 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
12982 command. Bugfix on 0.1.2.17.
12983 - When loading bandwidth history, do not believe any information in
12984 the future. Fixes bug 434.
12985 - When loading entry guard information, do not believe any information
12987 - When we have our clock set far in the future and generate an
12988 onion key, then re-set our clock to be correct, we should not stop
12989 the onion key from getting rotated.
12990 - On some platforms, accept() can return a broken address. Detect
12991 this more quietly, and deal accordingly. Fixes bug 483.
12992 - It's not actually an error to find a non-pending entry in the DNS
12993 cache when canceling a pending resolve. Don't log unless stuff
12994 is fishy. Resolves bug 463.
12995 - Don't reset trusted dir server list when we set a configuration
12996 option. Patch from Robert Hogan.
12997 - Don't try to create the datadir when running --verify-config or
12998 --hash-password. Resolves bug 540.
13001 Changes in version 0.2.0.9-alpha - 2007-10-24
13002 This ninth development snapshot switches clients to the new v3 directory
13003 system; allows servers to be listed in the network status even when they
13004 have the same nickname as a registered server; and fixes many other
13005 bugs including a big one that was causing some servers to disappear
13006 from the network status lists for a few hours each day.
13008 o Major features (directory system):
13009 - Clients now download v3 consensus networkstatus documents instead
13010 of v2 networkstatus documents. Clients and caches now base their
13011 opinions about routers on these consensus documents. Clients only
13012 download router descriptors listed in the consensus.
13013 - Authorities now list servers who have the same nickname as
13014 a different named server, but list them with a new flag,
13015 "Unnamed". Now we can list servers that happen to pick the same
13016 nickname as a server that registered two years ago and then
13017 disappeared. Partially implements proposal 122.
13018 - If the consensus lists a router as "Unnamed", the name is assigned
13019 to a different router: do not identify the router by that name.
13020 Partially implements proposal 122.
13021 - Authorities can now come to a consensus on which method to use to
13022 compute the consensus. This gives us forward compatibility.
13025 - Stop publishing a new server descriptor just because we HUP or
13026 when we find our DirPort to be reachable but won't actually publish
13027 it. New descriptors without any real changes are dropped by the
13028 authorities, and can screw up our "publish every 18 hours" schedule.
13030 - When a router wasn't listed in a new networkstatus, we were leaving
13031 the flags for that router alone -- meaning it remained Named,
13032 Running, etc -- even though absence from the networkstatus means
13033 that it shouldn't be considered to exist at all anymore. Now we
13034 clear all the flags for routers that fall out of the networkstatus
13035 consensus. Fixes bug 529; bugfix on 0.1.2.x.
13036 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
13037 extrainfo documents and then discard them immediately for not
13038 matching the latest router. Bugfix on 0.2.0.1-alpha.
13040 o Minor features (v3 directory protocol):
13041 - Allow tor-gencert to generate a new certificate without replacing
13043 - Allow certificates to include an address.
13044 - When we change our directory-cache settings, reschedule all voting
13045 and download operations.
13046 - Reattempt certificate downloads immediately on failure, as long as
13047 we haven't failed a threshold number of times yet.
13048 - Delay retrying consensus downloads while we're downloading
13049 certificates to verify the one we just got. Also, count getting a
13050 consensus that we already have (or one that isn't valid) as a failure,
13051 and count failing to get the certificates after 20 minutes as a
13053 - Build circuits and download descriptors even if our consensus is a
13054 little expired. (This feature will go away once authorities are
13057 o Minor features (router descriptor cache):
13058 - If we find a cached-routers file that's been sitting around for more
13059 than 28 days unmodified, then most likely it's a leftover from
13060 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
13062 - When we (as a cache) download a descriptor because it was listed
13063 in a consensus, remember when the consensus was supposed to expire,
13064 and don't expire the descriptor until then.
13066 o Minor features (performance):
13067 - Call routerlist_remove_old_routers() much less often. This should
13068 speed startup, especially on directory caches.
13069 - Don't try to launch new descriptor downloads quite so often when we
13070 already have enough directory information to build circuits.
13071 - Base64 decoding was actually showing up on our profile when parsing
13072 the initial descriptor file; switch to an in-process all-at-once
13073 implementation that's about 3.5x times faster than calling out to
13076 o Minor features (compilation):
13077 - Detect non-ASCII platforms (if any still exist) and refuse to
13078 build there: some of our code assumes that 'A' is 65 and so on.
13080 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
13081 - Make the "next period" votes into "current period" votes immediately
13082 after publishing the consensus; avoid a heisenbug that made them
13083 stick around indefinitely.
13084 - When we discard a vote as a duplicate, do not report this as
13086 - Treat missing v3 keys or certificates as an error when running as a
13087 v3 directory authority.
13088 - When we're configured to be a v3 authority, but we're only listed
13089 as a non-v3 authority in our DirServer line for ourself, correct
13091 - If an authority doesn't have a qualified hostname, just put
13092 its address in the vote. This fixes the problem where we referred to
13093 "moria on moria:9031."
13094 - Distinguish between detached signatures for the wrong period, and
13095 detached signatures for a divergent vote.
13096 - Fix a small memory leak when computing a consensus.
13097 - When there's no concensus, we were forming a vote every 30
13098 minutes, but writing the "valid-after" line in our vote based
13099 on our configured V3AuthVotingInterval: so unless the intervals
13100 matched up, we immediately rejected our own vote because it didn't
13101 start at the voting interval that caused us to construct a vote.
13103 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
13104 - Delete unverified-consensus when the real consensus is set.
13105 - Consider retrying a consensus networkstatus fetch immediately
13106 after one fails: don't wait 60 seconds to notice.
13107 - When fetching a consensus as a cache, wait until a newer consensus
13108 should exist before trying to replace the current one.
13109 - Use a more forgiving schedule for retrying failed consensus
13110 downloads than for other types.
13112 o Minor bugfixes (other directory issues):
13113 - Correct the implementation of "download votes by digest." Bugfix on
13115 - Authorities no longer send back "400 you're unreachable please fix
13116 it" errors to Tor servers that aren't online all the time. We're
13117 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
13119 o Minor bugfixes (controller):
13120 - Don't reset trusted dir server list when we set a configuration
13121 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
13122 - Respond to INT and TERM SIGNAL commands before we execute the
13123 signal, in case the signal shuts us down. We had a patch in
13124 0.1.2.1-alpha that tried to do this by queueing the response on
13125 the connection's buffer before shutting down, but that really
13126 isn't the same thing at all. Bug located by Matt Edman.
13128 o Minor bugfixes (misc):
13129 - Correctly check for bad options to the "PublishServerDescriptor"
13130 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
13131 - Stop leaking memory on failing case of base32_decode, and make
13132 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
13133 - Don't try to download extrainfo documents when we're trying to
13134 fetch enough directory info to build a circuit: having enough
13135 info should get priority. Bugfix on 0.2.0.x.
13136 - Don't complain that "your server has not managed to confirm that its
13137 ports are reachable" if we haven't been able to build any circuits
13138 yet. Bug found by spending four hours without a v3 consensus. Bugfix
13140 - Detect the reason for failing to mmap a descriptor file we just
13141 wrote, and give a more useful log message. Fixes bug 533. Bugfix
13144 o Code simplifications and refactoring:
13145 - Remove support for the old bw_accounting file: we've been storing
13146 bandwidth accounting information in the state file since
13147 0.1.2.5-alpha. This may result in bandwidth accounting errors
13148 if you try to upgrade from 0.1.1.x or earlier, or if you try to
13149 downgrade to 0.1.1.x or earlier.
13150 - New convenience code to locate a file within the DataDirectory.
13151 - Move non-authority functionality out of dirvote.c.
13152 - Refactor the arguments for router_pick_{directory_|trusteddir}server
13153 so that they all take the same named flags.
13156 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
13157 Unix users an easy way to script their Tor process (e.g. by
13158 adjusting bandwidth based on the time of the day).
13161 Changes in version 0.2.0.8-alpha - 2007-10-12
13162 This eighth development snapshot fixes a crash bug that's been bothering
13163 us since February 2007, lets bridge authorities store a list of bridge
13164 descriptors they've seen, gets v3 directory voting closer to working,
13165 starts caching v3 directory consensus documents on directory mirrors,
13166 and fixes a variety of smaller issues including some minor memory leaks.
13168 o Major features (router descriptor cache):
13169 - Store routers in a file called cached-descriptors instead of in
13170 cached-routers. Initialize cached-descriptors from cached-routers
13171 if the old format is around. The new format allows us to store
13172 annotations along with descriptors.
13173 - Use annotations to record the time we received each descriptor, its
13174 source, and its purpose.
13175 - Disable the SETROUTERPURPOSE controller command: it is now
13177 - Controllers should now specify cache=no or cache=yes when using
13178 the +POSTDESCRIPTOR command.
13179 - Bridge authorities now write bridge descriptors to disk, meaning
13180 we can export them to other programs and begin distributing them
13183 o Major features (directory authorities):
13184 - When a v3 authority is missing votes or signatures, it now tries
13186 - Directory authorities track weighted fractional uptime as well as
13187 weighted mean-time-between failures. WFU is suitable for deciding
13188 whether a node is "usually up", while MTBF is suitable for deciding
13189 whether a node is "likely to stay up." We need both, because
13190 "usually up" is a good requirement for guards, while "likely to
13191 stay up" is a good requirement for long-lived connections.
13193 o Major features (v3 directory system):
13194 - Caches now download v3 network status documents as needed,
13195 and download the descriptors listed in them.
13196 - All hosts now attempt to download and keep fresh v3 authority
13197 certificates, and re-attempt after failures.
13198 - More internal-consistency checks for vote parsing.
13200 o Major bugfixes (crashes):
13201 - If a connection is shut down abruptly because of something that
13202 happened inside connection_flushed_some(), do not call
13203 connection_finished_flushing(). Should fix bug 451. Bugfix on
13206 o Major bugfixes (performance):
13207 - Fix really bad O(n^2) performance when parsing a long list of
13208 routers: Instead of searching the entire list for an "extra-info "
13209 string which usually wasn't there, once for every routerinfo
13210 we read, just scan lines forward until we find one we like.
13212 - When we add data to a write buffer in response to the data on that
13213 write buffer getting low because of a flush, do not consider the
13214 newly added data as a candidate for immediate flushing, but rather
13215 make it wait until the next round of writing. Otherwise, we flush
13216 and refill recursively, and a single greedy TLS connection can
13217 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
13219 o Minor features (v3 authority system):
13220 - Add more ways for tools to download the votes that lead to the
13222 - Send a 503 when low on bandwidth and a vote, consensus, or
13223 certificate is requested.
13224 - If-modified-since is now implemented properly for all kinds of
13225 certificate requests.
13227 o Minor bugfixes (network statuses):
13228 - Tweak the implementation of proposal 109 slightly: allow at most
13229 two Tor servers on the same IP address, except if it's the location
13230 of a directory authority, in which case allow five. Bugfix on
13233 o Minor bugfixes (controller):
13234 - When sending a status event to the controller telling it that an
13235 OR address is reachable, set the port correctly. (Previously we
13236 were reporting the dir port.) Bugfix on 0.1.2.x.
13238 o Minor bugfixes (v3 directory system):
13239 - Fix logic to look up a cert by its signing key digest. Bugfix on
13241 - Only change the reply to a vote to "OK" if it's not already
13242 set. This gets rid of annoying "400 OK" log messages, which may
13243 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
13244 - When we get a valid consensus, recompute the voting schedule.
13245 - Base the valid-after time of a vote on the consensus voting
13246 schedule, not on our preferred schedule.
13247 - Make the return values and messages from signature uploads and
13248 downloads more sensible.
13249 - Fix a memory leak when serving votes and consensus documents, and
13250 another when serving certificates.
13252 o Minor bugfixes (performance):
13253 - Use a slightly simpler string hashing algorithm (copying Python's
13254 instead of Java's) and optimize our digest hashing algorithm to take
13255 advantage of 64-bit platforms and to remove some possibly-costly
13257 - Fix a minor memory leak whenever we parse guards from our state
13258 file. Bugfix on 0.2.0.7-alpha.
13259 - Fix a minor memory leak whenever we write out a file. Bugfix on
13261 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
13262 command. Bugfix on 0.2.0.5-alpha.
13264 o Minor bugfixes (portability):
13265 - On some platforms, accept() can return a broken address. Detect
13266 this more quietly, and deal accordingly. Fixes bug 483.
13267 - Stop calling tor_strlower() on uninitialized memory in some cases.
13268 Bugfix in 0.2.0.7-alpha.
13270 o Minor bugfixes (usability):
13271 - Treat some 403 responses from directory servers as INFO rather than
13272 WARN-severity events.
13273 - It's not actually an error to find a non-pending entry in the DNS
13274 cache when canceling a pending resolve. Don't log unless stuff is
13275 fishy. Resolves bug 463.
13277 o Minor bugfixes (anonymity):
13278 - Never report that we've used more bandwidth than we're willing to
13279 relay: it leaks how much non-relay traffic we're using. Resolves
13281 - When looking for a circuit to cannibalize, consider family as well
13282 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
13283 circuit cannibalization).
13285 o Code simplifications and refactoring:
13286 - Make a bunch of functions static. Remove some dead code.
13287 - Pull out about a third of the really big routerlist.c; put it in a
13288 new module, networkstatus.c.
13289 - Merge the extra fields in local_routerstatus_t back into
13290 routerstatus_t: we used to need one routerstatus_t for each
13291 authority's opinion, plus a local_routerstatus_t for the locally
13292 computed consensus opinion. To save space, we put the locally
13293 modified fields into local_routerstatus_t, and only the common
13294 stuff into routerstatus_t. But once v3 directories are in use,
13295 clients and caches will no longer need to hold authority opinions;
13296 thus, the rationale for keeping the types separate is now gone.
13297 - Make the code used to reschedule and reattempt downloads more
13299 - Turn all 'Are we a directory server/mirror?' logic into a call to
13301 - Remove the code to generate the oldest (v1) directory format.
13302 The code has been disabled since 0.2.0.5-alpha.
13305 Changes in version 0.2.0.7-alpha - 2007-09-21
13306 This seventh development snapshot makes bridges work again, makes bridge
13307 authorities work for the first time, fixes two huge performance flaws
13308 in hidden services, and fixes a variety of minor issues.
13310 o New directory authorities:
13311 - Set up moria1 and tor26 as the first v3 directory authorities. See
13312 doc/spec/dir-spec.txt for details on the new directory design.
13314 o Major bugfixes (crashes):
13315 - Fix possible segfaults in functions called from
13316 rend_process_relay_cell(). Bugfix on 0.1.2.x.
13318 o Major bugfixes (bridges):
13319 - Fix a bug that made servers send a "404 Not found" in response to
13320 attempts to fetch their server descriptor. This caused Tor servers
13321 to take many minutes to establish reachability for their DirPort,
13322 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
13323 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
13324 users configure that and specify a bridge with an identity
13325 fingerprint, now they will lookup the bridge descriptor at the
13326 default bridge authority via a one-hop tunnel, but once circuits
13327 are established they will switch to a three-hop tunnel for later
13328 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
13330 o Major bugfixes (hidden services):
13331 - Hidden services were choosing introduction points uniquely by
13332 hexdigest, but when constructing the hidden service descriptor
13333 they merely wrote the (potentially ambiguous) nickname.
13334 - Clients now use the v2 intro format for hidden service
13335 connections: they specify their chosen rendezvous point by identity
13336 digest rather than by (potentially ambiguous) nickname. Both
13337 are bugfixes on 0.1.2.x, and they could speed up hidden service
13338 connections dramatically. Thanks to Karsten Loesing.
13340 o Minor features (security):
13341 - As a client, do not believe any server that tells us that an
13342 address maps to an internal address space.
13343 - Make it possible to enable HashedControlPassword and
13344 CookieAuthentication at the same time.
13346 o Minor features (guard nodes):
13347 - Tag every guard node in our state file with the version that
13348 we believe added it, or with our own version if we add it. This way,
13349 if a user temporarily runs an old version of Tor and then switches
13350 back to a new one, she doesn't automatically lose her guards.
13352 o Minor features (speed):
13353 - When implementing AES counter mode, update only the portions of the
13354 counter buffer that need to change, and don't keep separate
13355 network-order and host-order counters when they are the same (i.e.,
13356 on big-endian hosts.)
13358 o Minor features (controller):
13359 - Accept LF instead of CRLF on controller, since some software has a
13360 hard time generating real Internet newlines.
13361 - Add GETINFO values for the server status events
13362 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
13365 o Removed features:
13366 - Routers no longer include bandwidth-history lines in their
13367 descriptors; this information is already available in extra-info
13368 documents, and including it in router descriptors took up 60%
13369 (!) of compressed router descriptor downloads. Completes
13370 implementation of proposal 104.
13371 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
13372 and TorControl.py, as they use the old v0 controller protocol,
13373 and are obsoleted by TorFlow anyway.
13374 - Drop support for v1 rendezvous descriptors, since we never used
13375 them anyway, and the code has probably rotted by now. Based on
13376 patch from Karsten Loesing.
13377 - On OSX, stop warning the user that kqueue support in libevent is
13378 "experimental", since it seems to have worked fine for ages.
13381 - When generating information telling us how to extend to a given
13382 router, do not try to include the nickname if it is absent. Fixes
13383 bug 467. Bugfix on 0.2.0.3-alpha.
13384 - Fix a user-triggerable (but not remotely-triggerable) segfault
13385 in expand_filename(). Bugfix on 0.1.2.x.
13386 - Fix a memory leak when freeing incomplete requests from DNSPort.
13387 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
13388 - Don't try to access (or alter) the state file when running
13389 --list-fingerprint or --verify-config or --hash-password. (Resolves
13390 bug 499.) Bugfix on 0.1.2.x.
13391 - Servers used to decline to publish their DirPort if their
13392 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
13393 were below a threshold. Now they only look at BandwidthRate and
13394 RelayBandwidthRate. Bugfix on 0.1.2.x.
13395 - Remove an optimization in the AES counter-mode code that assumed
13396 that the counter never exceeded 2^68. When the counter can be set
13397 arbitrarily as an IV (as it is by Karsten's new hidden services
13398 code), this assumption no longer holds. Bugfix on 0.1.2.x.
13399 - Resume listing "AUTHORITY" flag for authorities in network status.
13400 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
13402 o Code simplifications and refactoring:
13403 - Revamp file-writing logic so we don't need to have the entire
13404 contents of a file in memory at once before we write to disk. Tor,
13406 - Turn "descriptor store" into a full-fledged type.
13407 - Move all NT services code into a separate source file.
13408 - Unify all code that computes medians, percentile elements, etc.
13409 - Get rid of a needless malloc when parsing address policies.
13412 Changes in version 0.1.2.17 - 2007-08-30
13413 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
13414 X bundles. Vidalia 0.0.14 makes authentication required for the
13415 ControlPort in the default configuration, which addresses important
13416 security risks. Everybody who uses Vidalia (or another controller)
13419 In addition, this Tor update fixes major load balancing problems with
13420 path selection, which should speed things up a lot once many people
13423 o Major bugfixes (security):
13424 - We removed support for the old (v0) control protocol. It has been
13425 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
13426 become more of a headache than it's worth.
13428 o Major bugfixes (load balancing):
13429 - When choosing nodes for non-guard positions, weight guards
13430 proportionally less, since they already have enough load. Patch
13432 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
13433 will allow fast Tor servers to get more attention.
13434 - When we're upgrading from an old Tor version, forget our current
13435 guards and pick new ones according to the new weightings. These
13436 three load balancing patches could raise effective network capacity
13437 by a factor of four. Thanks to Mike Perry for measurements.
13439 o Major bugfixes (stream expiration):
13440 - Expire not-yet-successful application streams in all cases if
13441 they've been around longer than SocksTimeout. Right now there are
13442 some cases where the stream will live forever, demanding a new
13443 circuit every 15 seconds. Fixes bug 454; reported by lodger.
13445 o Minor features (controller):
13446 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
13447 is valid before any authentication has been received. It tells
13448 a controller what kind of authentication is expected, and what
13449 protocol is spoken. Implements proposal 119.
13451 o Minor bugfixes (performance):
13452 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
13453 greatly speeding up loading cached-routers from disk on startup.
13454 - Disable sentinel-based debugging for buffer code: we squashed all
13455 the bugs that this was supposed to detect a long time ago, and now
13456 its only effect is to change our buffer sizes from nice powers of
13457 two (which platform mallocs tend to like) to values slightly over
13458 powers of two (which make some platform mallocs sad).
13460 o Minor bugfixes (misc):
13461 - If exit bandwidth ever exceeds one third of total bandwidth, then
13462 use the correct formula to weight exit nodes when choosing paths.
13463 Based on patch from Mike Perry.
13464 - Choose perfectly fairly among routers when choosing by bandwidth and
13465 weighting by fraction of bandwidth provided by exits. Previously, we
13466 would choose with only approximate fairness, and correct ourselves
13467 if we ran off the end of the list.
13468 - If we require CookieAuthentication but we fail to write the
13469 cookie file, we would warn but not exit, and end up in a state
13470 where no controller could authenticate. Now we exit.
13471 - If we require CookieAuthentication, stop generating a new cookie
13472 every time we change any piece of our config.
13473 - Refuse to start with certain directory authority keys, and
13474 encourage people using them to stop.
13475 - Terminate multi-line control events properly. Original patch
13477 - Fix a minor memory leak when we fail to find enough suitable
13478 servers to choose a circuit.
13479 - Stop leaking part of the descriptor when we run into a particularly
13480 unparseable piece of it.
13483 Changes in version 0.2.0.6-alpha - 2007-08-26
13484 This sixth development snapshot features a new Vidalia version in the
13485 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
13486 the ControlPort in the default configuration, which addresses important
13489 In addition, this snapshot fixes major load balancing problems
13490 with path selection, which should speed things up a lot once many
13491 people have upgraded. The directory authorities also use a new
13492 mean-time-between-failure approach to tracking which servers are stable,
13493 rather than just looking at the most recent uptime.
13495 o New directory authorities:
13496 - Set up Tonga as the default bridge directory authority.
13499 - Directory authorities now track servers by weighted
13500 mean-times-between-failures. When we have 4 or more days of data,
13501 use measured MTBF rather than declared uptime to decide whether
13502 to call a router Stable. Implements proposal 108.
13504 o Major bugfixes (load balancing):
13505 - When choosing nodes for non-guard positions, weight guards
13506 proportionally less, since they already have enough load. Patch
13508 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
13509 will allow fast Tor servers to get more attention.
13510 - When we're upgrading from an old Tor version, forget our current
13511 guards and pick new ones according to the new weightings. These
13512 three load balancing patches could raise effective network capacity
13513 by a factor of four. Thanks to Mike Perry for measurements.
13515 o Major bugfixes (descriptor parsing):
13516 - Handle unexpected whitespace better in malformed descriptors. Bug
13517 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
13520 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
13521 GETINFO for Torstat to use until it can switch to using extrainfos.
13522 - Optionally (if built with -DEXPORTMALLINFO) export the output
13523 of mallinfo via http, as tor/mallinfo.txt. Only accessible
13527 - Do not intermix bridge routers with controller-added
13528 routers. (Bugfix on 0.2.0.x)
13529 - Do not fail with an assert when accept() returns an unexpected
13530 address family. Addresses but does not wholly fix bug 483. (Bugfix
13532 - Let directory authorities startup even when they can't generate
13533 a descriptor immediately, e.g. because they don't know their
13535 - Stop putting the authentication cookie in a file called "0"
13536 in your working directory if you don't specify anything for the
13537 new CookieAuthFile option. Reported by Matt Edman.
13538 - Make it possible to read the PROTOCOLINFO response in a way that
13539 conforms to our control-spec. Reported by Matt Edman.
13540 - Fix a minor memory leak when we fail to find enough suitable
13541 servers to choose a circuit. Bugfix on 0.1.2.x.
13542 - Stop leaking part of the descriptor when we run into a particularly
13543 unparseable piece of it. Bugfix on 0.1.2.x.
13544 - Unmap the extrainfo cache file on exit.
13547 Changes in version 0.2.0.5-alpha - 2007-08-19
13548 This fifth development snapshot fixes compilation on Windows again;
13549 fixes an obnoxious client-side bug that slowed things down and put
13550 extra load on the network; gets us closer to using the v3 directory
13551 voting scheme; makes it easier for Tor controllers to use cookie-based
13552 authentication; and fixes a variety of other bugs.
13554 o Removed features:
13555 - Version 1 directories are no longer generated in full. Instead,
13556 authorities generate and serve "stub" v1 directories that list
13557 no servers. This will stop Tor versions 0.1.0.x and earlier from
13558 working, but (for security reasons) nobody should be running those
13561 o Major bugfixes (compilation, 0.2.0.x):
13562 - Try to fix Win32 compilation again: improve checking for IPv6 types.
13563 - Try to fix MSVC compilation: build correctly on platforms that do
13564 not define s6_addr16 or s6_addr32.
13565 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
13568 o Major bugfixes (stream expiration):
13569 - Expire not-yet-successful application streams in all cases if
13570 they've been around longer than SocksTimeout. Right now there are
13571 some cases where the stream will live forever, demanding a new
13572 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
13573 reported by lodger.
13575 o Minor features (directory servers):
13576 - When somebody requests a list of statuses or servers, and we have
13577 none of those, return a 404 rather than an empty 200.
13579 o Minor features (directory voting):
13580 - Store v3 consensus status consensuses on disk, and reload them
13583 o Minor features (security):
13584 - Warn about unsafe ControlPort configurations.
13585 - Refuse to start with certain directory authority keys, and
13586 encourage people using them to stop.
13588 o Minor features (controller):
13589 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
13590 is valid before any authentication has been received. It tells
13591 a controller what kind of authentication is expected, and what
13592 protocol is spoken. Implements proposal 119.
13593 - New config option CookieAuthFile to choose a new location for the
13594 cookie authentication file, and config option
13595 CookieAuthFileGroupReadable to make it group-readable.
13597 o Minor features (unit testing):
13598 - Add command-line arguments to unit-test executable so that we can
13599 invoke any chosen test from the command line rather than having
13600 to run the whole test suite at once; and so that we can turn on
13601 logging for the unit tests.
13603 o Minor bugfixes (on 0.1.2.x):
13604 - If we require CookieAuthentication but we fail to write the
13605 cookie file, we would warn but not exit, and end up in a state
13606 where no controller could authenticate. Now we exit.
13607 - If we require CookieAuthentication, stop generating a new cookie
13608 every time we change any piece of our config.
13609 - When loading bandwidth history, do not believe any information in
13610 the future. Fixes bug 434.
13611 - When loading entry guard information, do not believe any information
13613 - When we have our clock set far in the future and generate an
13614 onion key, then re-set our clock to be correct, we should not stop
13615 the onion key from getting rotated.
13616 - Clean up torrc sample config file.
13617 - Do not automatically run configure from autogen.sh. This
13618 non-standard behavior tended to annoy people who have built other
13621 o Minor bugfixes (on 0.2.0.x):
13622 - Fix a bug with AutomapHostsOnResolve that would always cause
13623 the second request to fail. Bug reported by Kate. Bugfix on
13625 - Fix a bug in ADDRMAP controller replies that would sometimes
13626 try to print a NULL. Patch from tup.
13627 - Read v3 directory authority keys from the right location.
13628 - Numerous bugfixes to directory voting code.
13631 Changes in version 0.1.2.16 - 2007-08-01
13632 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
13633 remote attacker in certain situations to rewrite the user's torrc
13634 configuration file. This can completely compromise anonymity of users
13635 in most configurations, including those running the Vidalia bundles,
13636 TorK, etc. Or worse.
13638 o Major security fixes:
13639 - Close immediately after missing authentication on control port;
13640 do not allow multiple authentication attempts.
13643 Changes in version 0.2.0.4-alpha - 2007-08-01
13644 This fourth development snapshot fixes a critical security vulnerability
13645 for most users, specifically those running Vidalia, TorK, etc. Everybody
13646 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
13648 o Major security fixes:
13649 - Close immediately after missing authentication on control port;
13650 do not allow multiple authentication attempts.
13652 o Major bugfixes (compilation):
13653 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
13656 o Minor features (performance):
13657 - Be even more aggressive about releasing RAM from small
13658 empty buffers. Thanks to our free-list code, this shouldn't be too
13659 performance-intensive.
13660 - Disable sentinel-based debugging for buffer code: we squashed all
13661 the bugs that this was supposed to detect a long time ago, and
13662 now its only effect is to change our buffer sizes from nice
13663 powers of two (which platform mallocs tend to like) to values
13664 slightly over powers of two (which make some platform mallocs sad).
13665 - Log malloc statistics from mallinfo() on platforms where it
13669 Changes in version 0.2.0.3-alpha - 2007-07-29
13670 This third development snapshot introduces new experimental
13671 blocking-resistance features and a preliminary version of the v3
13672 directory voting design, and includes many other smaller features
13676 - The first pieces of our "bridge" design for blocking-resistance
13677 are implemented. People can run bridge directory authorities;
13678 people can run bridges; and people can configure their Tor clients
13679 with a set of bridges to use as the first hop into the Tor network.
13680 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
13682 - Create listener connections before we setuid to the configured
13683 User and Group. Now non-Windows users can choose port values
13684 under 1024, start Tor as root, and have Tor bind those ports
13685 before it changes to another UID. (Windows users could already
13687 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
13688 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
13689 on "vserver" accounts. (Patch from coderman.)
13690 - Be even more aggressive about separating local traffic from relayed
13691 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
13693 o Major features (experimental):
13694 - First cut of code for "v3 dir voting": directory authorities will
13695 vote on a common network status document rather than each publishing
13696 their own opinion. This code needs more testing and more corner-case
13697 handling before it's ready for use.
13700 - Directory authorities now call routers Fast if their bandwidth is
13701 at least 100KB/s, and consider their bandwidth adequate to be a
13702 Guard if it is at least 250KB/s, no matter the medians. This fix
13703 complements proposal 107. [Bugfix on 0.1.2.x]
13704 - Directory authorities now never mark more than 3 servers per IP as
13705 Valid and Running. (Implements proposal 109, by Kevin Bauer and
13707 - Minor change to organizationName and commonName generation
13708 procedures in TLS certificates during Tor handshakes, to invalidate
13709 some earlier censorware approaches. This is not a long-term
13710 solution, but applying it will give us a bit of time to look into
13711 the epidemiology of countermeasures as they spread.
13713 o Major bugfixes (directory):
13714 - Rewrite directory tokenization code to never run off the end of
13715 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
13717 o Minor features (controller):
13718 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
13719 match requests to applications. (Patch from Robert Hogan.)
13720 - Report address and port correctly on connections to DNSPort. (Patch
13721 from Robert Hogan.)
13722 - Add a RESOLVE command to launch hostname lookups. (Original patch
13723 from Robert Hogan.)
13724 - Add GETINFO status/enough-dir-info to let controllers tell whether
13725 Tor has downloaded sufficient directory information. (Patch
13727 - You can now use the ControlSocket option to tell Tor to listen for
13728 controller connections on Unix domain sockets on systems that
13729 support them. (Patch from Peter Palfrader.)
13730 - STREAM NEW events are generated for DNSPort requests and for
13731 tunneled directory connections. (Patch from Robert Hogan.)
13732 - New "GETINFO address-mappings/*" command to get address mappings
13733 with expiry information. "addr-mappings/*" is now deprecated.
13736 o Minor features (misc):
13737 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
13739 - The tor-gencert tool for v3 directory authorities now creates all
13740 files as readable to the file creator only, and write-protects
13741 the authority identity key.
13742 - When dumping memory usage, list bytes used in buffer memory
13744 - When running with dmalloc, dump more stats on hup and on exit.
13745 - Directory authorities now fail quickly and (relatively) harmlessly
13746 if they generate a network status document that is somehow
13749 o Traffic load balancing improvements:
13750 - If exit bandwidth ever exceeds one third of total bandwidth, then
13751 use the correct formula to weight exit nodes when choosing paths.
13752 (Based on patch from Mike Perry.)
13753 - Choose perfectly fairly among routers when choosing by bandwidth and
13754 weighting by fraction of bandwidth provided by exits. Previously, we
13755 would choose with only approximate fairness, and correct ourselves
13756 if we ran off the end of the list. [Bugfix on 0.1.2.x]
13758 o Performance improvements:
13759 - Be more aggressive with freeing buffer RAM or putting it on the
13761 - Use Critical Sections rather than Mutexes for synchronizing threads
13762 on win32; Mutexes are heavier-weight, and designed for synchronizing
13765 o Deprecated and removed features:
13766 - RedirectExits is now deprecated.
13767 - Stop allowing address masks that do not correspond to bit prefixes.
13768 We have warned about these for a really long time; now it's time
13769 to reject them. (Patch from croup.)
13771 o Minor bugfixes (directory):
13772 - Fix another crash bug related to extra-info caching. (Bug found by
13773 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
13774 - Directories no longer return a "304 not modified" when they don't
13775 have the networkstatus the client asked for. Also fix a memory
13776 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
13777 - We had accidentally labelled 0.1.2.x directory servers as not
13778 suitable for begin_dir requests, and had labelled no directory
13779 servers as suitable for uploading extra-info documents. [Bugfix
13782 o Minor bugfixes (dns):
13783 - Fix a crash when DNSPort is set more than once. (Patch from Robert
13784 Hogan.) [Bugfix on 0.2.0.2-alpha]
13785 - Add DNSPort connections to the global connection list, so that we
13786 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
13788 - Fix a dangling reference that could lead to a crash when DNSPort is
13789 changed or closed (Patch from Robert Hogan.) [Bugfix on
13792 o Minor bugfixes (controller):
13793 - Provide DNS expiry times in GMT, not in local time. For backward
13794 compatibility, ADDRMAP events only provide GMT expiry in an extended
13795 field. "GETINFO address-mappings" always does the right thing.
13796 - Use CRLF line endings properly in NS events.
13797 - Terminate multi-line control events properly. (Original patch
13798 from tup.) [Bugfix on 0.1.2.x-alpha]
13799 - Do not include spaces in SOURCE_ADDR fields in STREAM
13800 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
13803 Changes in version 0.1.2.15 - 2007-07-17
13804 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
13805 problems, fixes compilation on BSD, and fixes a variety of other
13806 bugs. Everybody should upgrade.
13808 o Major bugfixes (compilation):
13809 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
13811 o Major bugfixes (crashes):
13812 - Try even harder not to dereference the first character after
13813 an mmap(). Reported by lodger.
13814 - Fix a crash bug in directory authorities when we re-number the
13815 routerlist while inserting a new router.
13816 - When the cached-routers file is an even multiple of the page size,
13817 don't run off the end and crash. (Fixes bug 455; based on idea
13819 - Fix eventdns.c behavior on Solaris: It is critical to include
13820 orconfig.h _before_ sys/types.h, so that we can get the expected
13821 definition of _FILE_OFFSET_BITS.
13823 o Major bugfixes (security):
13824 - Fix a possible buffer overrun when using BSD natd support. Bug
13826 - When sending destroy cells from a circuit's origin, don't include
13827 the reason for tearing down the circuit. The spec says we didn't,
13828 and now we actually don't. Reported by lodger.
13829 - Keep streamids from different exits on a circuit separate. This
13830 bug may have allowed other routers on a given circuit to inject
13831 cells into streams. Reported by lodger; fixes bug 446.
13832 - If there's a never-before-connected-to guard node in our list,
13833 never choose any guards past it. This way we don't expand our
13834 guard list unless we need to.
13836 o Minor bugfixes (guard nodes):
13837 - Weight guard selection by bandwidth, so that low-bandwidth nodes
13838 don't get overused as guards.
13840 o Minor bugfixes (directory):
13841 - Correctly count the number of authorities that recommend each
13842 version. Previously, we were under-counting by 1.
13843 - Fix a potential crash bug when we load many server descriptors at
13844 once and some of them make others of them obsolete. Fixes bug 458.
13846 o Minor bugfixes (hidden services):
13847 - Stop tearing down the whole circuit when the user asks for a
13848 connection to a port that the hidden service didn't configure.
13851 o Minor bugfixes (misc):
13852 - On Windows, we were preventing other processes from reading
13853 cached-routers while Tor was running. Reported by janbar.
13854 - Fix a possible (but very unlikely) bug in picking routers by
13855 bandwidth. Add a log message to confirm that it is in fact
13856 unlikely. Patch from lodger.
13857 - Backport a couple of memory leak fixes.
13858 - Backport miscellaneous cosmetic bugfixes.
13861 Changes in version 0.2.0.2-alpha - 2007-06-02
13862 o Major bugfixes on 0.2.0.1-alpha:
13863 - Fix an assertion failure related to servers without extra-info digests.
13864 Resolves bugs 441 and 442.
13866 o Minor features (directory):
13867 - Support "If-Modified-Since" when answering HTTP requests for
13868 directories, running-routers documents, and network-status documents.
13869 (There's no need to support it for router descriptors, since those
13870 are downloaded by descriptor digest.)
13872 o Minor build issues:
13873 - Clear up some MIPSPro compiler warnings.
13874 - When building from a tarball on a machine that happens to have SVK
13875 installed, report the micro-revision as whatever version existed
13876 in the tarball, not as "x".
13879 Changes in version 0.2.0.1-alpha - 2007-06-01
13880 This early development snapshot provides new features for people running
13881 Tor as both a client and a server (check out the new RelayBandwidth
13882 config options); lets Tor run as a DNS proxy; and generally moves us
13883 forward on a lot of fronts.
13885 o Major features, server usability:
13886 - New config options RelayBandwidthRate and RelayBandwidthBurst:
13887 a separate set of token buckets for relayed traffic. Right now
13888 relayed traffic is defined as answers to directory requests, and
13889 OR connections that don't have any local circuits on them.
13891 o Major features, client usability:
13892 - A client-side DNS proxy feature to replace the need for
13893 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
13894 for DNS requests on port 9999, use the Tor network to resolve them
13895 anonymously, and send the reply back like a regular DNS server.
13896 The code still only implements a subset of DNS.
13897 - Make PreferTunneledDirConns and TunnelDirConns work even when
13898 we have no cached directory info. This means Tor clients can now
13899 do all of their connections protected by TLS.
13901 o Major features, performance and efficiency:
13902 - Directory authorities accept and serve "extra info" documents for
13903 routers. These documents contain fields from router descriptors
13904 that aren't usually needed, and that use a lot of excess
13905 bandwidth. Once these fields are removed from router descriptors,
13906 the bandwidth savings should be about 60%. [Partially implements
13908 - Servers upload extra-info documents to any authority that accepts
13909 them. Authorities (and caches that have been configured to download
13910 extra-info documents) download them as needed. [Partially implements
13912 - Change the way that Tor buffers data that it is waiting to write.
13913 Instead of queueing data cells in an enormous ring buffer for each
13914 client->OR or OR->OR connection, we now queue cells on a separate
13915 queue for each circuit. This lets us use less slack memory, and
13916 will eventually let us be smarter about prioritizing different kinds
13918 - Use memory pools to allocate cells with better speed and memory
13919 efficiency, especially on platforms where malloc() is inefficient.
13920 - Stop reading on edge connections when their corresponding circuit
13921 buffers are full; start again as the circuits empty out.
13923 o Major features, other:
13924 - Add an HSAuthorityRecordStats option that hidden service authorities
13925 can use to track statistics of overall hidden service usage without
13926 logging information that would be very useful to an attacker.
13927 - Start work implementing multi-level keys for directory authorities:
13928 Add a standalone tool to generate key certificates. (Proposal 103.)
13931 - Directory authorities now call routers Stable if they have an
13932 uptime of at least 30 days, even if that's not the median uptime
13933 in the network. Implements proposal 107, suggested by Kevin Bauer
13936 o Minor fixes (resource management):
13937 - Count the number of open sockets separately from the number
13938 of active connection_t objects. This will let us avoid underusing
13939 our allocated connection limit.
13940 - We no longer use socket pairs to link an edge connection to an
13941 anonymous directory connection or a DirPort test connection.
13942 Instead, we track the link internally and transfer the data
13943 in-process. This saves two sockets per "linked" connection (at the
13944 client and at the server), and avoids the nasty Windows socketpair()
13946 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
13947 for every single inactive connection_t. Free items from the
13948 4k/16k-buffer free lists when they haven't been used for a while.
13950 o Minor features (build):
13951 - Make autoconf search for libevent, openssl, and zlib consistently.
13952 - Update deprecated macros in configure.in.
13953 - When warning about missing headers, tell the user to let us
13954 know if the compile succeeds anyway, so we can downgrade the
13956 - Include the current subversion revision as part of the version
13957 string: either fetch it directly if we're in an SVN checkout, do
13958 some magic to guess it if we're in an SVK checkout, or use
13959 the last-detected version if we're building from a .tar.gz.
13960 Use this version consistently in log messages.
13962 o Minor features (logging):
13963 - Always prepend "Bug: " to any log message about a bug.
13964 - Put a platform string (e.g. "Linux i686") in the startup log
13965 message, so when people paste just their logs, we know if it's
13966 OpenBSD or Windows or what.
13967 - When logging memory usage, break down memory used in buffers by
13970 o Minor features (directory system):
13971 - New config option V2AuthoritativeDirectory that all directory
13972 authorities should set. This will let future authorities choose
13973 not to serve V2 directory information.
13974 - Directory authorities allow multiple router descriptors and/or extra
13975 info documents to be uploaded in a single go. This will make
13976 implementing proposal 104 simpler.
13978 o Minor features (controller):
13979 - Add a new config option __DisablePredictedCircuits designed for
13980 use by the controller, when we don't want Tor to build any circuits
13982 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
13983 so we can exit from the middle of the circuit.
13984 - Implement "getinfo status/circuit-established".
13985 - Implement "getinfo status/version/..." so a controller can tell
13986 whether the current version is recommended, and whether any versions
13987 are good, and how many authorities agree. (Patch from shibz.)
13989 o Minor features (hidden services):
13990 - Allow multiple HiddenServicePort directives with the same virtual
13991 port; when they occur, the user is sent round-robin to one
13992 of the target ports chosen at random. Partially fixes bug 393 by
13993 adding limited ad-hoc round-robining.
13995 o Minor features (other):
13997 - Add a new AutomapHostsOnResolve option: when it is enabled, any
13998 resolve request for hosts matching a given pattern causes Tor to
13999 generate an internal virtual address mapping for that host. This
14000 allows DNSPort to work sensibly with hidden service users. By
14001 default, .exit and .onion addresses are remapped; the list of
14002 patterns can be reconfigured with AutomapHostsSuffixes.
14003 - Add an "-F" option to tor-resolve to force a resolve for a .onion
14004 address. Thanks to the AutomapHostsOnResolve option, this is no
14005 longer a completely silly thing to do.
14006 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
14007 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
14008 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
14009 minus 1 byte: the actual maximum declared bandwidth.
14011 o Removed features:
14012 - Removed support for the old binary "version 0" controller protocol.
14013 This has been deprecated since 0.1.1, and warnings have been issued
14014 since 0.1.2. When we encounter a v0 control message, we now send
14015 back an error and close the connection.
14016 - Remove the old "dns worker" server DNS code: it hasn't been default
14017 since 0.1.2.2-alpha, and all the servers seem to be using the new
14020 o Minor bugfixes (portability):
14021 - Even though Windows is equally happy with / and \ as path separators,
14022 try to use \ consistently on Windows and / consistently on Unix: it
14023 makes the log messages nicer.
14024 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
14025 - Read resolv.conf files correctly on platforms where read() returns
14026 partial results on small file reads.
14028 o Minor bugfixes (directory):
14029 - Correctly enforce that elements of directory objects do not appear
14030 more often than they are allowed to appear.
14031 - When we are reporting the DirServer line we just parsed, we were
14032 logging the second stanza of the key fingerprint, not the first.
14034 o Minor bugfixes (logging):
14035 - When we hit an EOF on a log (probably because we're shutting down),
14036 don't try to remove the log from the list: just mark it as
14037 unusable. (Bulletproofs against bug 222.)
14039 o Minor bugfixes (other):
14040 - In the exitlist script, only consider the most recently published
14041 server descriptor for each server. Also, when the user requests
14042 a list of servers that _reject_ connections to a given address,
14043 explicitly exclude the IPs that also have servers that accept
14044 connections to that address. (Resolves bug 405.)
14045 - Stop allowing hibernating servers to be "stable" or "fast".
14046 - On Windows, we were preventing other processes from reading
14047 cached-routers while Tor was running. (Reported by janbar)
14048 - Make the NodeFamilies config option work. (Reported by
14049 lodger -- it has never actually worked, even though we added it
14051 - Check return values from pthread_mutex functions.
14052 - Don't save non-general-purpose router descriptors to the disk cache,
14053 because we have no way of remembering what their purpose was when
14055 - Add even more asserts to hunt down bug 417.
14056 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
14057 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
14058 Add a log message to confirm that it is in fact unlikely.
14060 o Minor bugfixes (controller):
14061 - Make 'getinfo fingerprint' return a 551 error if we're not a
14062 server, so we match what the control spec claims we do. Reported
14064 - Fix a typo in an error message when extendcircuit fails that
14065 caused us to not follow the \r\n-based delimiter protocol. Reported
14068 o Code simplifications and refactoring:
14069 - Stop passing around circuit_t and crypt_path_t pointers that are
14070 implicit in other procedure arguments.
14071 - Drop the old code to choke directory connections when the
14072 corresponding OR connections got full: thanks to the cell queue
14073 feature, OR conns don't get full any more.
14074 - Make dns_resolve() handle attaching connections to circuits
14075 properly, so the caller doesn't have to.
14076 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
14077 - Keep the connection array as a dynamic smartlist_t, rather than as
14078 a fixed-sized array. This is important, as the number of connections
14079 is becoming increasingly decoupled from the number of sockets.
14082 Changes in version 0.1.2.14 - 2007-05-25
14083 Tor 0.1.2.14 changes the addresses of two directory authorities (this
14084 change especially affects those who serve or use hidden services),
14085 and fixes several other crash- and security-related bugs.
14087 o Directory authority changes:
14088 - Two directory authorities (moria1 and moria2) just moved to new
14089 IP addresses. This change will particularly affect those who serve
14090 or use hidden services.
14092 o Major bugfixes (crashes):
14093 - If a directory server runs out of space in the connection table
14094 as it's processing a begin_dir request, it will free the exit stream
14095 but leave it attached to the circuit, leading to unpredictable
14096 behavior. (Reported by seeess, fixes bug 425.)
14097 - Fix a bug in dirserv_remove_invalid() that would cause authorities
14098 to corrupt memory under some really unlikely scenarios.
14099 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
14100 - Avoid segfaults when reading from mmaped descriptor file. (Reported
14103 o Major bugfixes (security):
14104 - When choosing an entry guard for a circuit, avoid using guards
14105 that are in the same family as the chosen exit -- not just guards
14106 that are exactly the chosen exit. (Reported by lodger.)
14108 o Major bugfixes (resource management):
14109 - If a directory authority is down, skip it when deciding where to get
14110 networkstatus objects or descriptors. Otherwise we keep asking
14111 every 10 seconds forever. Fixes bug 384.
14112 - Count it as a failure if we fetch a valid network-status but we
14113 don't want to keep it. Otherwise we'll keep fetching it and keep
14114 not wanting to keep it. Fixes part of bug 422.
14115 - If all of our dirservers have given us bad or no networkstatuses
14116 lately, then stop hammering them once per minute even when we
14117 think they're failed. Fixes another part of bug 422.
14120 - Actually set the purpose correctly for descriptors inserted with
14121 purpose=controller.
14122 - When we have k non-v2 authorities in our DirServer config,
14123 we ignored the last k authorities in the list when updating our
14125 - Correctly back-off from requesting router descriptors that we are
14126 having a hard time downloading.
14127 - Read resolv.conf files correctly on platforms where read() returns
14128 partial results on small file reads.
14129 - Don't rebuild the entire router store every time we get 32K of
14130 routers: rebuild it when the journal gets very large, or when
14131 the gaps in the store get very large.
14134 - When routers publish SVN revisions in their router descriptors,
14135 authorities now include those versions correctly in networkstatus
14137 - Warn when using a version of libevent before 1.3b to run a server on
14138 OSX or BSD: these versions interact badly with userspace threads.
14141 Changes in version 0.1.2.13 - 2007-04-24
14142 This release features some major anonymity fixes, such as safer path
14143 selection; better client performance; faster bootstrapping, better
14144 address detection, and better DNS support for servers; write limiting as
14145 well as read limiting to make servers easier to run; and a huge pile of
14146 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
14148 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
14149 of the Freenode IRC network, remembering his patience and vision for
14150 free speech on the Internet.
14153 - Fix a memory leak when we ask for "all" networkstatuses and we
14154 get one we don't recognize.
14155 - Add more asserts to hunt down bug 417.
14156 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
14159 Changes in version 0.1.2.12-rc - 2007-03-16
14161 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
14162 directory information requested inside Tor connections (i.e. via
14163 begin_dir cells). It only triggered when the same connection was
14164 serving other data at the same time. Reported by seeess.
14167 - When creating a circuit via the controller, send a 'launched'
14168 event when we're done, so we follow the spec better.
14171 Changes in version 0.1.2.11-rc - 2007-03-15
14172 o Minor bugfixes (controller), reported by daejees:
14173 - Correct the control spec to match how the code actually responds
14174 to 'getinfo addr-mappings/*'.
14175 - The control spec described a GUARDS event, but the code
14176 implemented a GUARD event. Standardize on GUARD, but let people
14177 ask for GUARDS too.
14180 Changes in version 0.1.2.10-rc - 2007-03-07
14181 o Major bugfixes (Windows):
14182 - Do not load the NT services library functions (which may not exist)
14183 just to detect if we're a service trying to shut down. Now we run
14184 on Win98 and friends again.
14186 o Minor bugfixes (other):
14187 - Clarify a couple of log messages.
14188 - Fix a misleading socks5 error number.
14191 Changes in version 0.1.2.9-rc - 2007-03-02
14192 o Major bugfixes (Windows):
14193 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
14194 of the usual GCC "%llu". This prevents a bug when saving 64-bit
14195 int configuration values: the high-order 32 bits would get
14196 truncated. In particular, we were being bitten by the default
14197 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
14198 and maybe also bug 397.)
14200 o Minor bugfixes (performance):
14201 - Use OpenSSL's AES implementation on platforms where it's faster.
14202 This could save us as much as 10% CPU usage.
14204 o Minor bugfixes (server):
14205 - Do not rotate onion key immediately after setting it for the first
14208 o Minor bugfixes (directory authorities):
14209 - Stop calling servers that have been hibernating for a long time
14210 "stable". Also, stop letting hibernating or obsolete servers affect
14211 uptime and bandwidth cutoffs.
14212 - Stop listing hibernating servers in the v1 directory.
14214 o Minor bugfixes (hidden services):
14215 - Upload hidden service descriptors slightly less often, to reduce
14216 load on authorities.
14218 o Minor bugfixes (other):
14219 - Fix an assert that could trigger if a controller quickly set then
14220 cleared EntryNodes. Bug found by Udo van den Heuvel.
14221 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
14223 - Fix a potential race condition in the rpm installer. Found by
14225 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
14226 of 2 as indicating that the server is completely bad; it sometimes
14227 means that the server is just bad for the request in question. (may fix
14228 the last of bug 326.)
14229 - Disable encrypted directory connections when we don't have a server
14230 descriptor for the destination. We'll get this working again in
14234 Changes in version 0.1.2.8-beta - 2007-02-26
14235 o Major bugfixes (crashes):
14236 - Stop crashing when the controller asks us to resetconf more than
14237 one config option at once. (Vidalia 0.0.11 does this.)
14238 - Fix a crash that happened on Win98 when we're given command-line
14239 arguments: don't try to load NT service functions from advapi32.dll
14240 except when we need them. (Bug introduced in 0.1.2.7-alpha;
14242 - Fix a longstanding obscure crash bug that could occur when
14243 we run out of DNS worker processes. (Resolves bug 390.)
14245 o Major bugfixes (hidden services):
14246 - Correctly detect whether hidden service descriptor downloads are
14247 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
14249 o Major bugfixes (accounting):
14250 - When we start during an accounting interval before it's time to wake
14251 up, remember to wake up at the correct time. (May fix bug 342.)
14253 o Minor bugfixes (controller):
14254 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
14255 clear the corresponding on_circuit variable, and remember later
14256 that we don't need to send a redundant CLOSED event. Resolves part
14258 - Report events where a resolve succeeded or where we got a socks
14259 protocol error correctly, rather than calling both of them
14261 - Change reported stream target addresses to IP consistently when
14262 we finally get the IP from an exit node.
14263 - Send log messages to the controller even if they happen to be very
14266 o Minor bugfixes (other):
14267 - Display correct results when reporting which versions are
14268 recommended, and how recommended they are. (Resolves bug 383.)
14269 - Improve our estimates for directory bandwidth to be less random:
14270 guess that an unrecognized directory will have the average bandwidth
14271 from all known directories, not that it will have the average
14272 bandwidth from those directories earlier than it on the list.
14273 - If we start a server with ClientOnly 1, then set ClientOnly to 0
14274 and hup, stop triggering an assert based on an empty onion_key.
14275 - On platforms with no working mmap() equivalent, don't warn the
14276 user when cached-routers doesn't exist.
14277 - Warn the user when mmap() [or its equivalent] fails for some reason
14278 other than file-not-found.
14279 - Don't warn the user when cached-routers.new doesn't exist: that's
14280 perfectly fine when starting up for the first time.
14281 - When EntryNodes are configured, rebuild the guard list to contain,
14282 in order: the EntryNodes that were guards before; the rest of the
14283 EntryNodes; the nodes that were guards before.
14284 - Mask out all signals in sub-threads; only the libevent signal
14285 handler should be processing them. This should prevent some crashes
14286 on some machines using pthreads. (Patch from coderman.)
14287 - Fix switched arguments on memset in the implementation of
14288 tor_munmap() for systems with no mmap() call.
14289 - When Tor receives a router descriptor that it asked for, but
14290 no longer wants (because it has received fresh networkstatuses
14291 in the meantime), do not warn the user. Cache the descriptor if
14292 we're a cache; drop it if we aren't.
14293 - Make earlier entry guards _really_ get retried when the network
14295 - On a malformed DNS reply, always give an error to the corresponding
14297 - Build with recent libevents on platforms that do not define the
14298 nonstandard types "u_int8_t" and friends.
14300 o Minor features (controller):
14301 - Warn the user when an application uses the obsolete binary v0
14302 control protocol. We're planning to remove support for it during
14303 the next development series, so it's good to give people some
14305 - Add STREAM_BW events to report per-entry-stream bandwidth
14306 use. (Patch from Robert Hogan.)
14307 - Rate-limit SIGNEWNYM signals in response to controllers that
14308 impolitely generate them for every single stream. (Patch from
14309 mwenge; closes bug 394.)
14310 - Make REMAP stream events have a SOURCE (cache or exit), and
14311 make them generated in every case where we get a successful
14312 connected or resolved cell.
14314 o Minor bugfixes (performance):
14315 - Call router_have_min_dir_info half as often. (This is showing up in
14316 some profiles, but not others.)
14317 - When using GCC, make log_debug never get called at all, and its
14318 arguments never get evaluated, when no debug logs are configured.
14319 (This is showing up in some profiles, but not others.)
14322 - Remove some never-implemented options. Mark PathlenCoinWeight as
14324 - Implement proposal 106: Stop requiring clients to have well-formed
14325 certificates; stop checking nicknames in certificates. (Clients
14326 have certificates so that they can look like Tor servers, but in
14327 the future we might want to allow them to look like regular TLS
14328 clients instead. Nicknames in certificates serve no purpose other
14329 than making our protocol easier to recognize on the wire.)
14330 - Revise messages on handshake failure again to be even more clear about
14331 which are incoming connections and which are outgoing.
14332 - Discard any v1 directory info that's over 1 month old (for
14333 directories) or over 1 week old (for running-routers lists).
14334 - Do not warn when individual nodes in the configuration's EntryNodes,
14335 ExitNodes, etc are down: warn only when all possible nodes
14336 are down. (Fixes bug 348.)
14337 - Always remove expired routers and networkstatus docs before checking
14338 whether we have enough information to build circuits. (Fixes
14340 - Put a lower-bound on MaxAdvertisedBandwidth.
14343 Changes in version 0.1.2.7-alpha - 2007-02-06
14344 o Major bugfixes (rate limiting):
14345 - Servers decline directory requests much more aggressively when
14346 they're low on bandwidth. Otherwise they end up queueing more and
14347 more directory responses, which can't be good for latency.
14348 - But never refuse directory requests from local addresses.
14349 - Fix a memory leak when sending a 503 response for a networkstatus
14351 - Be willing to read or write on local connections (e.g. controller
14352 connections) even when the global rate limiting buckets are empty.
14353 - If our system clock jumps back in time, don't publish a negative
14354 uptime in the descriptor. Also, don't let the global rate limiting
14355 buckets go absurdly negative.
14356 - Flush local controller connection buffers periodically as we're
14357 writing to them, so we avoid queueing 4+ megabytes of data before
14360 o Major bugfixes (NT services):
14361 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
14362 command-line flag so that admins can override the default by saying
14363 "tor --service install --user "SomeUser"". This will not affect
14364 existing installed services. Also, warn the user that the service
14365 will look for its configuration file in the service user's
14366 %appdata% directory. (We can't do the 'hardwire the user's appdata
14367 directory' trick any more, since we may not have read access to that
14370 o Major bugfixes (other):
14371 - Previously, we would cache up to 16 old networkstatus documents
14372 indefinitely, if they came from nontrusted authorities. Now we
14373 discard them if they are more than 10 days old.
14374 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
14376 - Detect and reject malformed DNS responses containing circular
14378 - If exits are rare enough that we're not marking exits as guards,
14379 ignore exit bandwidth when we're deciding the required bandwidth
14381 - When we're handling a directory connection tunneled over Tor,
14382 don't fill up internal memory buffers with all the data we want
14383 to tunnel; instead, only add it if the OR connection that will
14384 eventually receive it has some room for it. (This can lead to
14385 slowdowns in tunneled dir connections; a better solution will have
14386 to wait for 0.2.0.)
14388 o Minor bugfixes (dns):
14389 - Add some defensive programming to eventdns.c in an attempt to catch
14390 possible memory-stomping bugs.
14391 - Detect and reject DNS replies containing IPv4 or IPv6 records with
14392 an incorrect number of bytes. (Previously, we would ignore the
14394 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
14395 in the correct order, and doesn't crash.
14396 - Free memory held in recently-completed DNS lookup attempts on exit.
14397 This was not a memory leak, but may have been hiding memory leaks.
14398 - Handle TTL values correctly on reverse DNS lookups.
14399 - Treat failure to parse resolv.conf as an error.
14401 o Minor bugfixes (other):
14402 - Fix crash with "tor --list-fingerprint" (reported by seeess).
14403 - When computing clock skew from directory HTTP headers, consider what
14404 time it was when we finished asking for the directory, not what
14406 - Expire socks connections if they spend too long waiting for the
14407 handshake to finish. Previously we would let them sit around for
14408 days, if the connecting application didn't close them either.
14409 - And if the socks handshake hasn't started, don't send a
14410 "DNS resolve socks failed" handshake reply; just close it.
14411 - Stop using C functions that OpenBSD's linker doesn't like.
14412 - Don't launch requests for descriptors unless we have networkstatuses
14413 from at least half of the authorities. This delays the first
14414 download slightly under pathological circumstances, but can prevent
14415 us from downloading a bunch of descriptors we don't need.
14416 - Do not log IPs with TLS failures for incoming TLS
14417 connections. (Fixes bug 382.)
14418 - If the user asks to use invalid exit nodes, be willing to use
14420 - Stop using the reserved ac_cv namespace in our configure script.
14421 - Call stat() slightly less often; use fstat() when possible.
14422 - Refactor the way we handle pending circuits when an OR connection
14423 completes or fails, in an attempt to fix a rare crash bug.
14424 - Only rewrite a conn's address based on X-Forwarded-For: headers
14425 if it's a parseable public IP address; and stop adding extra quotes
14426 to the resulting address.
14429 - Weight directory requests by advertised bandwidth. Now we can
14430 let servers enable write limiting but still allow most clients to
14431 succeed at their directory requests. (We still ignore weights when
14432 choosing a directory authority; I hope this is a feature.)
14435 - Create a new file ReleaseNotes which was the old ChangeLog. The
14436 new ChangeLog file now includes the summaries for all development
14438 - Check for addresses with invalid characters at the exit as well
14439 as at the client, and warn less verbosely when they fail. You can
14440 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
14441 - Adapt a patch from goodell to let the contrib/exitlist script
14442 take arguments rather than require direct editing.
14443 - Inform the server operator when we decide not to advertise a
14444 DirPort due to AccountingMax enabled or a low BandwidthRate. It
14445 was confusing Zax, so now we're hopefully more helpful.
14446 - Bring us one step closer to being able to establish an encrypted
14447 directory tunnel without knowing a descriptor first. Still not
14448 ready yet. As part of the change, now assume we can use a
14449 create_fast cell if we don't know anything about a router.
14450 - Allow exit nodes to use nameservers running on ports other than 53.
14451 - Servers now cache reverse DNS replies.
14452 - Add an --ignore-missing-torrc command-line option so that we can
14453 get the "use sensible defaults if the configuration file doesn't
14454 exist" behavior even when specifying a torrc location on the command
14457 o Minor features (controller):
14458 - Track reasons for OR connection failure; make these reasons
14459 available via the controller interface. (Patch from Mike Perry.)
14460 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
14461 can learn when clients are sending malformed hostnames to Tor.
14462 - Clean up documentation for controller status events.
14463 - Add a REMAP status to stream events to note that a stream's
14464 address has changed because of a cached address or a MapAddress
14468 Changes in version 0.1.2.6-alpha - 2007-01-09
14470 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
14471 connection handles more than 4 gigs in either direction, we crash.
14472 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
14473 advertised exit node, somebody might try to exit from us when
14474 we're bootstrapping and before we've built our descriptor yet.
14475 Refuse the connection rather than crashing.
14478 - Warn if we (as a server) find that we've resolved an address that we
14479 weren't planning to resolve.
14480 - Warn that using select() on any libevent version before 1.1 will be
14481 unnecessarily slow (even for select()).
14482 - Flush ERR-level controller status events just like we currently
14483 flush ERR-level log events, so that a Tor shutdown doesn't prevent
14484 the controller from learning about current events.
14486 o Minor features (more controller status events):
14487 - Implement EXTERNAL_ADDRESS server status event so controllers can
14488 learn when our address changes.
14489 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
14490 can learn when directories reject our descriptor.
14491 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
14492 can learn when a client application is speaking a non-socks protocol
14494 - Implement DANGEROUS_SOCKS client status event so controllers
14495 can learn when a client application is leaking DNS addresses.
14496 - Implement BUG general status event so controllers can learn when
14497 Tor is unhappy about its internal invariants.
14498 - Implement CLOCK_SKEW general status event so controllers can learn
14499 when Tor thinks the system clock is set incorrectly.
14500 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
14501 server status events so controllers can learn when their descriptors
14502 are accepted by a directory.
14503 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
14504 server status events so controllers can learn about Tor's progress in
14505 deciding whether it's reachable from the outside.
14506 - Implement BAD_LIBEVENT general status event so controllers can learn
14507 when we have a version/method combination in libevent that needs to
14509 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
14510 and DNS_USELESS server status events so controllers can learn
14511 about changes to DNS server status.
14513 o Minor features (directory):
14514 - Authorities no longer recommend exits as guards if this would shift
14515 too much load to the exit nodes.
14518 Changes in version 0.1.2.5-alpha - 2007-01-06
14520 - Enable write limiting as well as read limiting. Now we sacrifice
14521 capacity if we're pushing out lots of directory traffic, rather
14522 than overrunning the user's intended bandwidth limits.
14523 - Include TLS overhead when counting bandwidth usage; previously, we
14524 would count only the bytes sent over TLS, but not the bytes used
14526 - Support running the Tor service with a torrc not in the same
14527 directory as tor.exe and default to using the torrc located in
14528 the %appdata%\Tor\ of the user who installed the service. Patch
14530 - Servers now check for the case when common DNS requests are going to
14531 wildcarded addresses (i.e. all getting the same answer), and change
14532 their exit policy to reject *:* if it's happening.
14533 - Implement BEGIN_DIR cells, so we can connect to the directory
14534 server via TLS to do encrypted directory requests rather than
14535 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
14536 config options if you like.
14538 o Minor features (config and docs):
14539 - Start using the state file to store bandwidth accounting data:
14540 the bw_accounting file is now obsolete. We'll keep generating it
14541 for a while for people who are still using 0.1.2.4-alpha.
14542 - Try to batch changes to the state file so that we do as few
14543 disk writes as possible while still storing important things in
14545 - The state file and the bw_accounting file get saved less often when
14546 the AvoidDiskWrites config option is set.
14547 - Make PIDFile work on Windows (untested).
14548 - Add internal descriptions for a bunch of configuration options:
14549 accessible via controller interface and in comments in saved
14551 - Reject *:563 (NNTPS) in the default exit policy. We already reject
14552 NNTP by default, so this seems like a sensible addition.
14553 - Clients now reject hostnames with invalid characters. This should
14554 avoid some inadvertent info leaks. Add an option
14555 AllowNonRFC953Hostnames to disable this behavior, in case somebody
14556 is running a private network with hosts called @, !, and #.
14557 - Add a maintainer script to tell us which options are missing
14558 documentation: "make check-docs".
14559 - Add a new address-spec.txt document to describe our special-case
14560 addresses: .exit, .onion, and .noconnnect.
14562 o Minor features (DNS):
14563 - Ongoing work on eventdns infrastructure: now it has dns server
14564 and ipv6 support. One day Tor will make use of it.
14565 - Add client-side caching for reverse DNS lookups.
14566 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
14567 - When we change nameservers or IP addresses, reset and re-launch
14568 our tests for DNS hijacking.
14570 o Minor features (directory):
14571 - Authorities now specify server versions in networkstatus. This adds
14572 about 2% to the size of compressed networkstatus docs, and allows
14573 clients to tell which servers support BEGIN_DIR and which don't.
14574 The implementation is forward-compatible with a proposed future
14575 protocol version scheme not tied to Tor versions.
14576 - DirServer configuration lines now have an orport= option so
14577 clients can open encrypted tunnels to the authorities without
14578 having downloaded their descriptors yet. Enabled for moria1,
14579 moria2, tor26, and lefkada now in the default configuration.
14580 - Directory servers are more willing to send a 503 "busy" if they
14581 are near their write limit, especially for v1 directory requests.
14582 Now they can use their limited bandwidth for actual Tor traffic.
14583 - Clients track responses with status 503 from dirservers. After a
14584 dirserver has given us a 503, we try not to use it until an hour has
14585 gone by, or until we have no dirservers that haven't given us a 503.
14586 - When we get a 503 from a directory, and we're not a server, we don't
14587 count the failure against the total number of failures allowed
14588 for the thing we're trying to download.
14589 - Report X-Your-Address-Is correctly from tunneled directory
14590 connections; don't report X-Your-Address-Is when it's an internal
14591 address; and never believe reported remote addresses when they're
14593 - Protect against an unlikely DoS attack on directory servers.
14594 - Add a BadDirectory flag to network status docs so that authorities
14595 can (eventually) tell clients about caches they believe to be
14598 o Minor features (controller):
14599 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
14600 - Reimplement GETINFO so that info/names stays in sync with the
14602 - Implement "GETINFO fingerprint".
14603 - Implement "SETEVENTS GUARD" so controllers can get updates on
14604 entry guard status as it changes.
14606 o Minor features (clean up obsolete pieces):
14607 - Remove some options that have been deprecated since at least
14608 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
14609 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
14610 to set log options.
14611 - We no longer look for identity and onion keys in "identity.key" and
14612 "onion.key" -- these were replaced by secret_id_key and
14613 secret_onion_key in 0.0.8pre1.
14614 - We no longer require unrecognized directory entries to be
14617 o Major bugfixes (security):
14618 - Stop sending the HttpProxyAuthenticator string to directory
14619 servers when directory connections are tunnelled through Tor.
14620 - Clients no longer store bandwidth history in the state file.
14621 - Do not log introduction points for hidden services if SafeLogging
14623 - When generating bandwidth history, round down to the nearest
14624 1k. When storing accounting data, round up to the nearest 1k.
14625 - When we're running as a server, remember when we last rotated onion
14626 keys, so that we will rotate keys once they're a week old even if
14627 we never stay up for a week ourselves.
14629 o Major bugfixes (other):
14630 - Fix a longstanding bug in eventdns that prevented the count of
14631 timed-out resolves from ever being reset. This bug caused us to
14632 give up on a nameserver the third time it timed out, and try it
14633 10 seconds later... and to give up on it every time it timed out
14635 - Take out the '5 second' timeout from the connection retry
14636 schedule. Now the first connect attempt will wait a full 10
14637 seconds before switching to a new circuit. Perhaps this will help
14638 a lot. Based on observations from Mike Perry.
14639 - Fix a bug on the Windows implementation of tor_mmap_file() that
14640 would prevent the cached-routers file from ever loading. Reported
14644 - Fix an assert failure when a directory authority sets
14645 AuthDirRejectUnlisted and then receives a descriptor from an
14646 unlisted router. Reported by seeess.
14647 - Avoid a double-free when parsing malformed DirServer lines.
14648 - Fix a bug when a BSD-style PF socket is first used. Patch from
14650 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
14651 to resolve an address at a given exit node even when they ask for
14653 - Servers no longer ever list themselves in their "family" line,
14654 even if configured to do so. This makes it easier to configure
14655 family lists conveniently.
14656 - When running as a server, don't fall back to 127.0.0.1 when no
14657 nameservers are configured in /etc/resolv.conf; instead, make the
14658 user fix resolv.conf or specify nameservers explicitly. (Resolves
14660 - Stop accepting certain malformed ports in configured exit policies.
14661 - Don't re-write the fingerprint file every restart, unless it has
14663 - Stop warning when a single nameserver fails: only warn when _all_ of
14664 our nameservers have failed. Also, when we only have one nameserver,
14665 raise the threshold for deciding that the nameserver is dead.
14666 - Directory authorities now only decide that routers are reachable
14667 if their identity keys are as expected.
14668 - When the user uses bad syntax in the Log config line, stop
14669 suggesting other bad syntax as a replacement.
14670 - Correctly detect ipv6 DNS capability on OpenBSD.
14672 o Minor bugfixes (controller):
14673 - Report the circuit number correctly in STREAM CLOSED events. Bug
14674 reported by Mike Perry.
14675 - Do not report bizarre values for results of accounting GETINFOs
14676 when the last second's write or read exceeds the allotted bandwidth.
14677 - Report "unrecognized key" rather than an empty string when the
14678 controller tries to fetch a networkstatus that doesn't exist.
14681 Changes in version 0.1.1.26 - 2006-12-14
14682 o Security bugfixes:
14683 - Stop sending the HttpProxyAuthenticator string to directory
14684 servers when directory connections are tunnelled through Tor.
14685 - Clients no longer store bandwidth history in the state file.
14686 - Do not log introduction points for hidden services if SafeLogging
14690 - Fix an assert failure when a directory authority sets
14691 AuthDirRejectUnlisted and then receives a descriptor from an
14692 unlisted router (reported by seeess).
14695 Changes in version 0.1.2.4-alpha - 2006-12-03
14697 - Add support for using natd; this allows FreeBSDs earlier than
14698 5.1.2 to have ipfw send connections through Tor without using
14699 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
14702 - Make all connections to addresses of the form ".noconnect"
14703 immediately get closed. This lets application/controller combos
14704 successfully test whether they're talking to the same Tor by
14705 watching for STREAM events.
14706 - Make cross.sh cross-compilation script work even when autogen.sh
14707 hasn't been run. (Patch from Michael Mohr.)
14708 - Statistics dumped by -USR2 now include a breakdown of public key
14709 operations, for profiling.
14712 - Fix a major leak when directory authorities parse their
14713 approved-routers list, a minor memory leak when we fail to pick
14714 an exit node, and a few rare leaks on errors.
14715 - Handle TransPort connections even when the server sends data before
14716 the client sends data. Previously, the connection would just hang
14717 until the client sent data. (Patch from tup based on patch from
14719 - Avoid assert failure when our cached-routers file is empty on
14723 - Don't log spurious warnings when we see a circuit close reason we
14724 don't recognize; it's probably just from a newer version of Tor.
14725 - Have directory authorities allow larger amounts of drift in uptime
14726 without replacing the server descriptor: previously, a server that
14727 restarted every 30 minutes could have 48 "interesting" descriptors
14729 - Start linking to the Tor specification and Tor reference manual
14730 correctly in the Windows installer.
14731 - Add Vidalia to the OS X uninstaller script, so when we uninstall
14732 Tor/Privoxy we also uninstall Vidalia.
14733 - Resume building on Irix64, and fix a lot of warnings from its
14734 MIPSpro C compiler.
14735 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
14736 when we're running as a client.
14739 Changes in version 0.1.1.25 - 2006-11-04
14741 - When a client asks us to resolve (rather than connect to)
14742 an address, and we have a cached answer, give them the cached
14743 answer. Previously, we would give them no answer at all.
14744 - We were building exactly the wrong circuits when we predict
14745 hidden service requirements, meaning Tor would have to build all
14746 its circuits on demand.
14747 - If none of our live entry guards have a high uptime, but we
14748 require a guard with a high uptime, try adding a new guard before
14749 we give up on the requirement. This patch should make long-lived
14750 connections more stable on average.
14751 - When testing reachability of our DirPort, don't launch new
14752 tests when there's already one in progress -- unreachable
14753 servers were stacking up dozens of testing streams.
14755 o Security bugfixes:
14756 - When the user sends a NEWNYM signal, clear the client-side DNS
14757 cache too. Otherwise we continue to act on previous information.
14760 - Avoid a memory corruption bug when creating a hash table for
14762 - Avoid possibility of controller-triggered crash when misusing
14763 certain commands from a v0 controller on platforms that do not
14764 handle printf("%s",NULL) gracefully.
14765 - Avoid infinite loop on unexpected controller input.
14766 - Don't log spurious warnings when we see a circuit close reason we
14767 don't recognize; it's probably just from a newer version of Tor.
14768 - Add Vidalia to the OS X uninstaller script, so when we uninstall
14769 Tor/Privoxy we also uninstall Vidalia.
14772 Changes in version 0.1.2.3-alpha - 2006-10-29
14774 - Prepare for servers to publish descriptors less often: never
14775 discard a descriptor simply for being too old until either it is
14776 recommended by no authorities, or until we get a better one for
14777 the same router. Make caches consider retaining old recommended
14778 routers for even longer.
14779 - If most authorities set a BadExit flag for a server, clients
14780 don't think of it as a general-purpose exit. Clients only consider
14781 authorities that advertise themselves as listing bad exits.
14782 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
14783 headers for content, so that we can work better in the presence of
14784 caching HTTP proxies.
14785 - Allow authorities to list nodes as bad exits by fingerprint or by
14788 o Minor features, controller:
14789 - Add a REASON field to CIRC events; for backward compatibility, this
14790 field is sent only to controllers that have enabled the extended
14791 event format. Also, add additional reason codes to explain why
14792 a given circuit has been destroyed or truncated. (Patches from
14794 - Add a REMOTE_REASON field to extended CIRC events to tell the
14795 controller about why a remote OR told us to close a circuit.
14796 - Stream events also now have REASON and REMOTE_REASON fields,
14797 working much like those for circuit events.
14798 - There's now a GETINFO ns/... field so that controllers can ask Tor
14799 about the current status of a router.
14800 - A new event type "NS" to inform a controller when our opinion of
14801 a router's status has changed.
14802 - Add a GETINFO events/names and GETINFO features/names so controllers
14803 can tell which events and features are supported.
14804 - A new CLEARDNSCACHE signal to allow controllers to clear the
14805 client-side DNS cache without expiring circuits.
14807 o Security bugfixes:
14808 - When the user sends a NEWNYM signal, clear the client-side DNS
14809 cache too. Otherwise we continue to act on previous information.
14812 - Avoid sending junk to controllers or segfaulting when a controller
14813 uses EVENT_NEW_DESC with verbose nicknames.
14814 - Stop triggering asserts if the controller tries to extend hidden
14815 service circuits (reported by mwenge).
14816 - Avoid infinite loop on unexpected controller input.
14817 - When the controller does a "GETINFO network-status", tell it
14818 about even those routers whose descriptors are very old, and use
14819 long nicknames where appropriate.
14820 - Change NT service functions to be loaded on demand. This lets us
14821 build with MinGW without breaking Tor for Windows 98 users.
14822 - Do DirPort reachability tests less often, since a single test
14823 chews through many circuits before giving up.
14824 - In the hidden service example in torrc.sample, stop recommending
14825 esoteric and discouraged hidden service options.
14826 - When stopping an NT service, wait up to 10 sec for it to actually
14827 stop. Patch from Matt Edman; resolves bug 295.
14828 - Fix handling of verbose nicknames with ORCONN controller events:
14829 make them show up exactly when requested, rather than exactly when
14831 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
14832 printing a duplicate "$" in the keys we send (reported by mwenge).
14833 - Correctly set maximum connection limit on Cygwin. (This time
14835 - Try to detect Windows correctly when cross-compiling.
14836 - Detect the size of the routers file correctly even if it is
14837 corrupted (on systems without mmap) or not page-aligned (on systems
14838 with mmap). This bug was harmless.
14839 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
14840 to open a stream fails; now we do in more cases. This should
14841 make clients able to find a good exit faster in some cases, since
14842 unhandleable requests will now get an error rather than timing out.
14843 - Resolve two memory leaks when rebuilding the on-disk router cache
14844 (reported by fookoowa).
14845 - Clean up minor code warnings suggested by the MIPSpro C compiler,
14846 and reported by some Centos users.
14847 - Controller signals now work on non-Unix platforms that don't define
14848 SIGUSR1 and SIGUSR2 the way we expect.
14849 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
14850 values before failing, and always enables eventdns.
14851 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
14852 Try to fix this in configure.in by checking for most functions
14853 before we check for libevent.
14856 Changes in version 0.1.2.2-alpha - 2006-10-07
14858 - Make our async eventdns library on-by-default for Tor servers,
14859 and plan to deprecate the separate dnsworker threads.
14860 - Add server-side support for "reverse" DNS lookups (using PTR
14861 records so clients can determine the canonical hostname for a given
14862 IPv4 address). Only supported by servers using eventdns; servers
14863 now announce in their descriptors whether they support eventdns.
14864 - Specify and implement client-side SOCKS5 interface for reverse DNS
14865 lookups (see doc/socks-extensions.txt).
14866 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
14867 connect to directory servers through Tor. Previously, clients needed
14868 to find Tor exits to make private connections to directory servers.
14869 - Avoid choosing Exit nodes for entry or middle hops when the
14870 total bandwidth available from non-Exit nodes is much higher than
14871 the total bandwidth available from Exit nodes.
14872 - Workaround for name servers (like Earthlink's) that hijack failing
14873 DNS requests and replace the no-such-server answer with a "helpful"
14874 redirect to an advertising-driven search portal. Also work around
14875 DNS hijackers who "helpfully" decline to hijack known-invalid
14876 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
14877 lets you turn it off.
14878 - Send out a burst of long-range padding cells once we've established
14879 that we're reachable. Spread them over 4 circuits, so hopefully
14880 a few will be fast. This exercises our bandwidth and bootstraps
14881 us into the directory more quickly.
14883 o New/improved config options:
14884 - Add new config option "ResolvConf" to let the server operator
14885 choose an alternate resolve.conf file when using eventdns.
14886 - Add an "EnforceDistinctSubnets" option to control our "exclude
14887 servers on the same /16" behavior. It's still on by default; this
14888 is mostly for people who want to operate private test networks with
14889 all the machines on the same subnet.
14890 - If one of our entry guards is on the ExcludeNodes list, or the
14891 directory authorities don't think it's a good guard, treat it as
14892 if it were unlisted: stop using it as a guard, and throw it off
14893 the guards list if it stays that way for a long time.
14894 - Allow directory authorities to be marked separately as authorities
14895 for the v1 directory protocol, the v2 directory protocol, and
14896 as hidden service directories, to make it easier to retire old
14897 authorities. V1 authorities should set "HSAuthoritativeDir 1"
14898 to continue being hidden service authorities too.
14899 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
14901 o Minor features, controller:
14902 - Fix CIRC controller events so that controllers can learn the
14903 identity digests of non-Named servers used in circuit paths.
14904 - Let controllers ask for more useful identifiers for servers. Instead
14905 of learning identity digests for un-Named servers and nicknames
14906 for Named servers, the new identifiers include digest, nickname,
14907 and indication of Named status. Off by default; see control-spec.txt
14908 for more information.
14909 - Add a "getinfo address" controller command so it can display Tor's
14910 best guess to the user.
14911 - New controller event to alert the controller when our server
14912 descriptor has changed.
14913 - Give more meaningful errors on controller authentication failure.
14915 o Minor features, other:
14916 - When asked to resolve a hostname, don't use non-exit servers unless
14917 requested to do so. This allows servers with broken DNS to be
14918 useful to the network.
14919 - Divide eventdns log messages into warn and info messages.
14920 - Reserve the nickname "Unnamed" for routers that can't pick
14921 a hostname: any router can call itself Unnamed; directory
14922 authorities will never allocate Unnamed to any particular router;
14923 clients won't believe that any router is the canonical Unnamed.
14924 - Only include function names in log messages for info/debug messages.
14925 For notice/warn/err, the content of the message should be clear on
14926 its own, and printing the function name only confuses users.
14927 - Avoid some false positives during reachability testing: don't try
14928 to test via a server that's on the same /24 as us.
14929 - If we fail to build a circuit to an intended enclave, and it's
14930 not mandatory that we use that enclave, stop wanting it.
14931 - When eventdns is enabled, allow multithreaded builds on NetBSD and
14932 OpenBSD. (We had previously disabled threads on these platforms
14933 because they didn't have working thread-safe resolver functions.)
14935 o Major bugfixes, anonymity/security:
14936 - If a client asked for a server by name, and there's a named server
14937 in our network-status but we don't have its descriptor yet, we
14938 could return an unnamed server instead.
14939 - Fix NetBSD bug that could allow someone to force uninitialized RAM
14940 to be sent to a server's DNS resolver. This only affects NetBSD
14941 and other platforms that do not bounds-check tolower().
14942 - Reject (most) attempts to use Tor circuits with length one. (If
14943 many people start using Tor as a one-hop proxy, exit nodes become
14944 a more attractive target for compromise.)
14945 - Just because your DirPort is open doesn't mean people should be
14946 able to remotely teach you about hidden service descriptors. Now
14947 only accept rendezvous posts if you've got HSAuthoritativeDir set.
14949 o Major bugfixes, other:
14950 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
14951 - When a client asks the server to resolve (not connect to)
14952 an address, and it has a cached answer, give them the cached answer.
14953 Previously, the server would give them no answer at all.
14954 - Allow really slow clients to not hang up five minutes into their
14955 directory downloads (suggested by Adam J. Richter).
14956 - We were building exactly the wrong circuits when we anticipated
14957 hidden service requirements, meaning Tor would have to build all
14958 its circuits on demand.
14959 - Avoid crashing when we mmap a router cache file of size 0.
14960 - When testing reachability of our DirPort, don't launch new
14961 tests when there's already one in progress -- unreachable
14962 servers were stacking up dozens of testing streams.
14964 o Minor bugfixes, correctness:
14965 - If we're a directory mirror and we ask for "all" network status
14966 documents, we would discard status documents from authorities
14967 we don't recognize.
14968 - Avoid a memory corruption bug when creating a hash table for
14970 - Avoid controller-triggered crash when misusing certain commands
14971 from a v0 controller on platforms that do not handle
14972 printf("%s",NULL) gracefully.
14973 - Don't crash when a controller sends a third argument to an
14974 "extendcircuit" request.
14975 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
14976 response; fix error code when "getinfo dir/status/" fails.
14977 - Avoid crash when telling controller stream-status and a stream
14979 - Patch from Adam Langley to fix assert() in eventdns.c.
14980 - Fix a debug log message in eventdns to say "X resolved to Y"
14981 instead of "X resolved to X".
14982 - Make eventdns give strings for DNS errors, not just error numbers.
14983 - Track unreachable entry guards correctly: don't conflate
14984 'unreachable by us right now' with 'listed as down by the directory
14985 authorities'. With the old code, if a guard was unreachable by
14986 us but listed as running, it would clog our guard list forever.
14987 - Behave correctly in case we ever have a network with more than
14988 2GB/s total advertised capacity.
14989 - Make TrackExitHosts case-insensitive, and fix the behavior of
14990 ".suffix" TrackExitHosts items to avoid matching in the middle of
14992 - Finally fix the openssl warnings from newer gccs that believe that
14993 ignoring a return value is okay, but casting a return value and
14994 then ignoring it is a sign of madness.
14995 - Prevent the contrib/exitlist script from printing the same
14996 result more than once.
14997 - Patch from Steve Hildrey: Generate network status correctly on
14998 non-versioning dirservers.
14999 - Don't listen to the X-Your-Address-Is hint if you did the lookup
15000 via Tor; otherwise you'll think you're the exit node's IP address.
15002 o Minor bugfixes, performance:
15003 - Two small performance improvements on parsing descriptors.
15004 - Major performance improvement on inserting descriptors: change
15005 algorithm from O(n^2) to O(n).
15006 - Make the common memory allocation path faster on machines where
15007 malloc(0) returns a pointer.
15008 - Start remembering X-Your-Address-Is directory hints even if you're
15009 a client, so you can become a server more smoothly.
15010 - Avoid duplicate entries on MyFamily line in server descriptor.
15012 o Packaging, features:
15013 - Remove architecture from OS X builds. The official builds are
15014 now universal binaries.
15015 - The Debian package now uses --verify-config when (re)starting,
15016 to distinguish configuration errors from other errors.
15017 - Update RPMs to require libevent 1.1b.
15019 o Packaging, bugfixes:
15020 - Patches so Tor builds with MinGW on Windows.
15021 - Patches so Tor might run on Cygwin again.
15022 - Resume building on non-gcc compilers and ancient gcc. Resume
15023 building with the -O0 compile flag. Resume building cleanly on
15025 - Run correctly on OS X platforms with case-sensitive filesystems.
15026 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
15027 - Add autoconf checks so Tor can build on Solaris x86 again.
15030 - Documented (and renamed) ServerDNSSearchDomains and
15031 ServerDNSResolvConfFile options.
15032 - Be clearer that the *ListenAddress directives can be repeated
15036 Changes in version 0.1.1.24 - 2006-09-29
15038 - Allow really slow clients to not hang up five minutes into their
15039 directory downloads (suggested by Adam J. Richter).
15040 - Fix major performance regression from 0.1.0.x: instead of checking
15041 whether we have enough directory information every time we want to
15042 do something, only check when the directory information has changed.
15043 This should improve client CPU usage by 25-50%.
15044 - Don't crash if, after a server has been running for a while,
15045 it can't resolve its hostname.
15048 - Allow Tor to start when RunAsDaemon is set but no logs are set.
15049 - Don't crash when the controller receives a third argument to an
15050 "extendcircuit" request.
15051 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
15052 response; fix error code when "getinfo dir/status/" fails.
15053 - Fix configure.in to not produce broken configure files with
15054 more recent versions of autoconf. Thanks to Clint for his auto*
15056 - Fix security bug on NetBSD that could allow someone to force
15057 uninitialized RAM to be sent to a server's DNS resolver. This
15058 only affects NetBSD and other platforms that do not bounds-check
15060 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
15061 methods: these are known to be buggy.
15062 - If we're a directory mirror and we ask for "all" network status
15063 documents, we would discard status documents from authorities
15064 we don't recognize.
15067 Changes in version 0.1.2.1-alpha - 2006-08-27
15069 - Add "eventdns" async dns library from Adam Langley, tweaked to
15070 build on OSX and Windows. Only enabled if you pass the
15071 --enable-eventdns argument to configure.
15072 - Allow servers with no hostname or IP address to learn their
15073 IP address by asking the directory authorities. This code only
15074 kicks in when you would normally have exited with a "no address"
15075 error. Nothing's authenticated, so use with care.
15076 - Rather than waiting a fixed amount of time between retrying
15077 application connections, we wait only 5 seconds for the first,
15078 10 seconds for the second, and 15 seconds for each retry after
15079 that. Hopefully this will improve the expected user experience.
15080 - Patch from Tup to add support for transparent AP connections:
15081 this basically bundles the functionality of trans-proxy-tor
15082 into the Tor mainline. Now hosts with compliant pf/netfilter
15083 implementations can redirect TCP connections straight to Tor
15084 without diverting through SOCKS. Needs docs.
15085 - Busy directory servers save lots of memory by spooling server
15086 descriptors, v1 directories, and v2 networkstatus docs to buffers
15087 as needed rather than en masse. Also mmap the cached-routers
15088 files, so we don't need to keep the whole thing in memory too.
15089 - Automatically avoid picking more than one node from the same
15090 /16 network when constructing a circuit.
15091 - Revise and clean up the torrc.sample that we ship with; add
15092 a section for BandwidthRate and BandwidthBurst.
15095 - Split circuit_t into origin_circuit_t and or_circuit_t, and
15096 split connection_t into edge, or, dir, control, and base structs.
15097 These will save quite a bit of memory on busy servers, and they'll
15098 also help us track down bugs in the code and bugs in the spec.
15099 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
15100 or later. Log when we are doing this, so we can diagnose it when
15101 it fails. (Also, recommend libevent 1.1b for kqueue and
15102 win32 methods; deprecate libevent 1.0b harder; make libevent
15103 recommendation system saner.)
15104 - Start being able to build universal binaries on OS X (thanks
15106 - Export the default exit policy via the control port, so controllers
15107 don't need to guess what it is / will be later.
15108 - Add a man page entry for ProtocolWarnings.
15109 - Add TestVia config option to the man page.
15110 - Remove even more protocol-related warnings from Tor server logs,
15111 such as bad TLS handshakes and malformed begin cells.
15112 - Stop fetching descriptors if you're not a dir mirror and you
15113 haven't tried to establish any circuits lately. [This currently
15114 causes some dangerous behavior, because when you start up again
15115 you'll use your ancient server descriptors.]
15116 - New DirPort behavior: if you have your dirport set, you download
15117 descriptors aggressively like a directory mirror, whether or not
15118 your ORPort is set.
15119 - Get rid of the router_retry_connections notion. Now routers
15120 no longer try to rebuild long-term connections to directory
15121 authorities, and directory authorities no longer try to rebuild
15122 long-term connections to all servers. We still don't hang up
15123 connections in these two cases though -- we need to look at it
15124 more carefully to avoid flapping, and we likely need to wait til
15125 0.1.1.x is obsolete.
15126 - Drop compatibility with obsolete Tors that permit create cells
15127 to have the wrong circ_id_type.
15128 - Re-enable per-connection rate limiting. Get rid of the "OP
15129 bandwidth" concept. Lay groundwork for "bandwidth classes" --
15130 separate global buckets that apply depending on what sort of conn
15132 - Start publishing one minute or so after we find our ORPort
15133 to be reachable. This will help reduce the number of descriptors
15134 we have for ourselves floating around, since it's quite likely
15135 other things (e.g. DirPort) will change during that minute too.
15136 - Fork the v1 directory protocol into its own spec document,
15137 and mark dir-spec.txt as the currently correct (v2) spec.
15140 - When we find our DirPort to be reachable, publish a new descriptor
15141 so we'll tell the world (reported by pnx).
15142 - Publish a new descriptor after we hup/reload. This is important
15143 if our config has changed such that we'll want to start advertising
15144 our DirPort now, etc.
15145 - Allow Tor to start when RunAsDaemon is set but no logs are set.
15146 - When we have a state file we cannot parse, tell the user and
15147 move it aside. Now we avoid situations where the user starts
15148 Tor in 1904, Tor writes a state file with that timestamp in it,
15149 the user fixes her clock, and Tor refuses to start.
15150 - Fix configure.in to not produce broken configure files with
15151 more recent versions of autoconf. Thanks to Clint for his auto*
15153 - "tor --verify-config" now exits with -1(255) or 0 depending on
15154 whether the config options are bad or good.
15155 - Resolve bug 321 when using dnsworkers: append a period to every
15156 address we resolve at the exit node, so that we do not accidentally
15157 pick up local addresses, and so that failing searches are retried
15158 in the resolver search domains. (This is already solved for
15159 eventdns.) (This breaks Blossom servers for now.)
15160 - If we are using an exit enclave and we can't connect, e.g. because
15161 its webserver is misconfigured to not listen on localhost, then
15162 back off and try connecting from somewhere else before we fail.
15165 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
15166 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
15167 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
15168 when the IP address is mapped through MapAddress to a hostname.
15169 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
15170 useless IPv6 DNS resolves.
15171 - Patch suggested by Karsten Loesing: respond to SIGNAL command
15172 before we execute the signal, in case the signal shuts us down.
15173 - Clean up AllowInvalidNodes man page entry.
15174 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
15175 - Add more asserts to track down an assert error on a windows Tor
15176 server with connection_add being called with socket == -1.
15177 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
15178 - Fix misleading log messages: an entry guard that is "unlisted",
15179 as well as not known to be "down" (because we've never heard
15180 of it), is not therefore "up".
15181 - Remove code to special-case "-cvs" ending, since it has not
15182 actually mattered since 0.0.9.
15183 - Make our socks5 handling more robust to broken socks clients:
15184 throw out everything waiting on the buffer in between socks
15185 handshake phases, since they can't possibly (so the theory
15186 goes) have predicted what we plan to respond to them.
15189 Changes in version 0.1.1.23 - 2006-07-30
15191 - Fast Tor servers, especially exit nodes, were triggering asserts
15192 due to a bug in handling the list of pending DNS resolves. Some
15193 bugs still remain here; we're hunting them.
15194 - Entry guards could crash clients by sending unexpected input.
15195 - More fixes on reachability testing: if you find yourself reachable,
15196 then don't ever make any client requests (so you stop predicting
15197 circuits), then hup or have your clock jump, then later your IP
15198 changes, you won't think circuits are working, so you won't try to
15199 test reachability, so you won't publish.
15202 - Avoid a crash if the controller does a resetconf firewallports
15203 and then a setconf fascistfirewall=1.
15204 - Avoid an integer underflow when the dir authority decides whether
15205 a router is stable: we might wrongly label it stable, and compute
15206 a slightly wrong median stability, when a descriptor is published
15208 - Fix a place where we might trigger an assert if we can't build our
15209 own server descriptor yet.
15212 Changes in version 0.1.1.22 - 2006-07-05
15214 - Fix a big bug that was causing servers to not find themselves
15215 reachable if they changed IP addresses. Since only 0.1.1.22+
15216 servers can do reachability testing correctly, now we automatically
15217 make sure to test via one of these.
15218 - Fix to allow clients and mirrors to learn directory info from
15219 descriptor downloads that get cut off partway through.
15220 - Directory authorities had a bug in deciding if a newly published
15221 descriptor was novel enough to make everybody want a copy -- a few
15222 servers seem to be publishing new descriptors many times a minute.
15224 - Fix a rare bug that was causing some servers to complain about
15225 "closing wedged cpuworkers" and skip some circuit create requests.
15226 - Make the Exit flag in directory status documents actually work.
15229 Changes in version 0.1.1.21 - 2006-06-10
15230 o Crash and assert fixes from 0.1.1.20:
15231 - Fix a rare crash on Tor servers that have enabled hibernation.
15232 - Fix a seg fault on startup for Tor networks that use only one
15233 directory authority.
15234 - Fix an assert from a race condition that occurs on Tor servers
15235 while exiting, where various threads are trying to log that they're
15236 exiting, and delete the logs, at the same time.
15237 - Make our unit tests pass again on certain obscure platforms.
15240 - Add support for building SUSE RPM packages.
15241 - Speed up initial bootstrapping for clients: if we are making our
15242 first ever connection to any entry guard, then don't mark it down
15244 - When only one Tor server in the network is labelled as a guard,
15245 and we've already picked him, we would cycle endlessly picking him
15246 again, being unhappy about it, etc. Now we specifically exclude
15247 current guards when picking a new guard.
15248 - Servers send create cells more reliably after the TLS connection
15249 is established: we were sometimes forgetting to send half of them
15250 when we had more than one pending.
15251 - If we get a create cell that asks us to extend somewhere, but the
15252 Tor server there doesn't match the expected digest, we now send
15253 a destroy cell back, rather than silently doing nothing.
15254 - Make options->RedirectExit work again.
15255 - Make cookie authentication for the controller work again.
15256 - Stop being picky about unusual characters in the arguments to
15257 mapaddress. It's none of our business.
15258 - Add a new config option "TestVia" that lets you specify preferred
15259 middle hops to use for test circuits. Perhaps this will let me
15260 debug the reachability problems better.
15262 o Log / documentation fixes:
15263 - If we're a server and some peer has a broken TLS certificate, don't
15264 log about it unless ProtocolWarnings is set, i.e., we want to hear
15265 about protocol violations by others.
15266 - Fix spelling of VirtualAddrNetwork in man page.
15267 - Add a better explanation at the top of the autogenerated torrc file
15268 about what happened to our old torrc.
15271 Changes in version 0.1.1.20 - 2006-05-23
15273 - Downgrade a log severity where servers complain that they're
15275 - Avoid a compile warning on FreeBSD.
15276 - Remove string size limit on NEWDESC messages; solve bug 291.
15277 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
15278 more thoroughly when we're running on windows.
15281 Changes in version 0.1.1.19-rc - 2006-05-03
15283 - Regenerate our local descriptor if it's dirty and we try to use
15284 it locally (e.g. if it changes during reachability detection).
15285 - If we setconf our ORPort to 0, we continued to listen on the
15286 old ORPort and receive connections.
15287 - Avoid a second warning about machine/limits.h on Debian
15289 - Be willing to add our own routerinfo into the routerlist.
15290 Now authorities will include themselves in their directories
15291 and network-statuses.
15292 - Stop trying to upload rendezvous descriptors to every
15293 directory authority: only try the v1 authorities.
15294 - Servers no longer complain when they think they're not
15295 registered with the directory authorities. There were too many
15297 - Backport dist-rpm changes so rpms can be built without errors.
15300 - Implement an option, VirtualAddrMask, to set which addresses
15301 get handed out in response to mapaddress requests. This works
15302 around a bug in tsocks where 127.0.0.0/8 is never socksified.
15305 Changes in version 0.1.1.18-rc - 2006-04-10
15307 - Work harder to download live network-statuses from all the
15308 directory authorities we know about. Improve the threshold
15309 decision logic so we're more robust to edge cases.
15310 - When fetching rendezvous descriptors, we were willing to ask
15311 v2 authorities too, which would always return 404.
15314 - Stop listing down or invalid nodes in the v1 directory. This will
15315 reduce its bulk by about 1/3, and reduce load on directory
15317 - When deciding whether a router is Fast or Guard-worthy, consider
15318 his advertised BandwidthRate and not just the BandwidthCapacity.
15319 - No longer ship INSTALL and README files -- they are useless now.
15320 - Force rpmbuild to behave and honor target_cpu.
15321 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
15322 - Start to include translated versions of the tor-doc-*.html
15323 files, along with the screenshots. Still needs more work.
15324 - Start sending back 512 and 451 errors if mapaddress fails,
15325 rather than not sending anything back at all.
15326 - When we fail to bind or listen on an incoming or outgoing
15327 socket, we should close it before failing. otherwise we just
15328 leak it. (thanks to weasel for finding.)
15329 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
15330 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
15331 - Make NoPublish (even though deprecated) work again.
15332 - Fix a minor security flaw where a versioning auth dirserver
15333 could list a recommended version many times in a row to make
15334 clients more convinced that it's recommended.
15335 - Fix crash bug if there are two unregistered servers running
15336 with the same nickname, one of them is down, and you ask for
15337 them by nickname in your EntryNodes or ExitNodes. Also, try
15338 to pick the one that's running rather than an arbitrary one.
15339 - Fix an infinite loop we could hit if we go offline for too long.
15340 - Complain when we hit WSAENOBUFS on recv() or write() too.
15341 Perhaps this will help us hunt the bug.
15342 - If you're not a versioning dirserver, don't put the string
15343 "client-versions \nserver-versions \n" in your network-status.
15344 - Lower the minimum required number of file descriptors to 1000,
15345 so we can have some overhead for Valgrind on Linux, where the
15346 default ulimit -n is 1024.
15349 - Add tor.dizum.com as the fifth authoritative directory server.
15350 - Add a new config option FetchUselessDescriptors, off by default,
15351 for when you plan to run "exitlist" on your client and you want
15352 to know about even the non-running descriptors.
15355 Changes in version 0.1.1.17-rc - 2006-03-28
15357 - Clients and servers since 0.1.1.10-alpha have been expiring
15358 connections whenever they are idle for 5 minutes and they *do*
15359 have circuits on them. Oops. With this new version, clients will
15360 discard their previous entry guard choices and avoid choosing
15361 entry guards running these flawed versions.
15362 - Fix memory leak when uncompressing concatenated zlib streams. This
15363 was causing substantial leaks over time on Tor servers.
15364 - The v1 directory was including servers as much as 48 hours old,
15365 because that's how the new routerlist->routers works. Now only
15366 include them if they're 20 hours old or less.
15369 - Resume building on irix64, netbsd 2.0, etc.
15370 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
15372 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
15373 and it is confusing some users.
15374 - Mirrors stop caching the v1 directory so often.
15375 - Make the max number of old descriptors that a cache will hold
15376 rise with the number of directory authorities, so we can scale.
15377 - Change our win32 uname() hack to be more forgiving about what
15378 win32 versions it thinks it's found.
15381 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
15383 - When the controller's *setconf commands fail, collect an error
15384 message in a string and hand it back to the controller.
15385 - Make the v2 dir's "Fast" flag based on relative capacity, just
15386 like "Stable" is based on median uptime. Name everything in the
15387 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
15388 - Log server fingerprint on startup, so new server operators don't
15389 have to go hunting around their filesystem for it.
15390 - Return a robots.txt on our dirport to discourage google indexing.
15391 - Let the controller ask for GETINFO dir/status/foo so it can ask
15392 directly rather than connecting to the dir port. Only works when
15393 dirport is set for now.
15395 o New config options rather than constants in the code:
15396 - SocksTimeout: How long do we let a socks connection wait
15397 unattached before we fail it?
15398 - CircuitBuildTimeout: Cull non-open circuits that were born
15399 at least this many seconds ago.
15400 - CircuitIdleTimeout: Cull open clean circuits that were born
15401 at least this many seconds ago.
15404 Changes in version 0.1.1.16-rc - 2006-03-18
15405 o Bugfixes on 0.1.1.15-rc:
15406 - Fix assert when the controller asks to attachstream a connect-wait
15407 or resolve-wait stream.
15408 - Now do address rewriting when the controller asks us to attach
15409 to a particular circuit too. This will let Blossom specify
15410 "moria2.exit" without having to learn what moria2's IP address is.
15411 - Make the "tor --verify-config" command-line work again, so people
15412 can automatically check if their torrc will parse.
15413 - Authoritative dirservers no longer require an open connection from
15414 a server to consider him "reachable". We need this change because
15415 when we add new auth dirservers, old servers won't know not to
15417 - Let Tor build on Sun CC again.
15418 - Fix an off-by-one buffer size in dirserv.c that magically never
15419 hit our three authorities but broke sjmurdoch's own tor network.
15420 - If we as a directory mirror don't know of any v1 directory
15421 authorities, then don't try to cache any v1 directories.
15422 - Stop warning about unknown servers in our family when they are
15423 given as hex digests.
15424 - Stop complaining as quickly to the server operator that he
15425 hasn't registered his nickname/key binding.
15426 - Various cleanups so we can add new V2 Auth Dirservers.
15427 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
15428 reflect the updated flags in our v2 dir protocol.
15429 - Resume allowing non-printable characters for exit streams (both
15430 for connecting and for resolving). Now we tolerate applications
15431 that don't follow the RFCs. But continue to block malformed names
15434 o Bugfixes on 0.1.0.x:
15435 - Fix assert bug in close_logs(): when we close and delete logs,
15436 remove them all from the global "logfiles" list.
15437 - Fix minor integer overflow in calculating when we expect to use up
15438 our bandwidth allocation before hibernating.
15439 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
15440 there are multiple SSLs installed with different versions.
15441 - When we try to be a server and Address is not explicitly set and
15442 our hostname resolves to a private IP address, try to use an
15443 interface address if it has a public address. Now Windows machines
15444 that think of themselves as localhost can work by default.
15447 - Let the controller ask for GETINFO dir/server/foo so it can ask
15448 directly rather than connecting to the dir port.
15449 - Let the controller tell us about certain router descriptors
15450 that it doesn't want Tor to use in circuits. Implement
15451 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
15452 - New config option SafeSocks to reject all application connections
15453 using unsafe socks protocols. Defaults to off.
15456 Changes in version 0.1.1.15-rc - 2006-03-11
15457 o Bugfixes and cleanups:
15458 - When we're printing strings from the network, don't try to print
15459 non-printable characters. This protects us against shell escape
15460 sequence exploits, and also against attacks to fool humans into
15461 misreading their logs.
15462 - Fix a bug where Tor would fail to establish any connections if you
15463 left it off for 24 hours and then started it: we were happy with
15464 the obsolete network statuses, but they all referred to router
15465 descriptors that were too old to fetch, so we ended up with no
15466 valid router descriptors.
15467 - Fix a seg fault in the controller's "getinfo orconn-status"
15468 command while listing status on incoming handshaking connections.
15469 Introduce a status name "NEW" for these connections.
15470 - If we get a linelist or linelist_s config option from the torrc
15471 (e.g. ExitPolicy) and it has no value, warn and skip rather than
15472 silently resetting it to its default.
15473 - Don't abandon entry guards until they've been down or gone for
15475 - Cleaner and quieter log messages.
15478 - New controller signal NEWNYM that makes new application requests
15479 use clean circuits.
15480 - Add a new circuit purpose 'controller' to let the controller ask
15481 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
15482 controller command to let you specify the purpose if you're
15483 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
15484 command to let you change a circuit's purpose after it's been
15486 - Accept "private:*" in routerdesc exit policies; not generated yet
15487 because older Tors do not understand it.
15488 - Add BSD-style contributed startup script "rc.subr" from Peter
15492 Changes in version 0.1.1.14-alpha - 2006-02-20
15493 o Bugfixes on 0.1.1.x:
15494 - Don't die if we ask for a stdout or stderr log (even implicitly)
15495 and we're set to RunAsDaemon -- just warn.
15496 - We still had a few bugs in the OR connection rotation code that
15497 caused directory servers to slowly aggregate connections to other
15498 fast Tor servers. This time for sure!
15499 - Make log entries on Win32 include the name of the function again.
15500 - We were treating a pair of exit policies if they were equal even
15501 if one said accept and the other said reject -- causing us to
15502 not always publish a new descriptor since we thought nothing
15504 - Retry pending server downloads as well as pending networkstatus
15505 downloads when we unexpectedly get a socks request.
15506 - We were ignoring the IS_FAST flag in the directory status,
15507 meaning we were willing to pick trivial-bandwidth nodes for "fast"
15509 - If the controller's SAVECONF command fails (e.g. due to file
15510 permissions), let the controller know that it failed.
15513 - If we're trying to be a Tor server and running Windows 95/98/ME
15514 as a server, explain that we'll likely crash.
15515 - When we're a server, a client asks for an old-style directory,
15516 and our write bucket is empty, don't give it to him. This way
15517 small servers can continue to serve the directory *sometimes*,
15518 without getting overloaded.
15519 - Compress exit policies even more -- look for duplicate lines
15521 - Clients now honor the "guard" flag in the router status when
15522 picking entry guards, rather than looking at is_fast or is_stable.
15523 - Retain unrecognized lines in $DATADIR/state file, so that we can
15524 be forward-compatible.
15525 - Generate 18.0.0.0/8 address policy format in descs when we can;
15526 warn when the mask is not reducible to a bit-prefix.
15527 - Let the user set ControlListenAddress in the torrc. This can be
15528 dangerous, but there are some cases (like a secured LAN) where it
15530 - Split ReachableAddresses into ReachableDirAddresses and
15531 ReachableORAddresses, so we can restrict Dir conns to port 80
15532 and OR conns to port 443.
15533 - Now we can target arch and OS in rpm builds (contributed by
15534 Phobos). Also make the resulting dist-rpm filename match the
15536 - New config options to help controllers: FetchServerDescriptors
15537 and FetchHidServDescriptors for whether to fetch server
15538 info and hidserv info or let the controller do it, and
15539 PublishServerDescriptor and PublishHidServDescriptors.
15540 - Also let the controller set the __AllDirActionsPrivate config
15541 option if you want all directory fetches/publishes to happen via
15542 Tor (it assumes your controller bootstraps your circuits).
15545 Changes in version 0.1.0.17 - 2006-02-17
15546 o Crash bugfixes on 0.1.0.x:
15547 - When servers with a non-zero DirPort came out of hibernation,
15548 sometimes they would trigger an assert.
15550 o Other important bugfixes:
15551 - On platforms that don't have getrlimit (like Windows), we were
15552 artificially constraining ourselves to a max of 1024
15553 connections. Now just assume that we can handle as many as 15000
15554 connections. Hopefully this won't cause other problems.
15556 o Backported features:
15557 - When we're a server, a client asks for an old-style directory,
15558 and our write bucket is empty, don't give it to him. This way
15559 small servers can continue to serve the directory *sometimes*,
15560 without getting overloaded.
15561 - Whenever you get a 503 in response to a directory fetch, try
15562 once more. This will become important once servers start sending
15563 503's whenever they feel busy.
15564 - Fetch a new directory every 120 minutes, not every 40 minutes.
15565 Now that we have hundreds of thousands of users running the old
15566 directory algorithm, it's starting to hurt a lot.
15567 - Bump up the period for forcing a hidden service descriptor upload
15568 from 20 minutes to 1 hour.
15571 Changes in version 0.1.1.13-alpha - 2006-02-09
15572 o Crashes in 0.1.1.x:
15573 - When you tried to setconf ORPort via the controller, Tor would
15574 crash. So people using TorCP to become a server were sad.
15575 - Solve (I hope) the stack-smashing bug that we were seeing on fast
15576 servers. The problem appears to be something do with OpenSSL's
15577 random number generation, or how we call it, or something. Let me
15578 know if the crashes continue.
15579 - Turn crypto hardware acceleration off by default, until we find
15580 somebody smart who can test it for us. (It appears to produce
15581 seg faults in at least some cases.)
15582 - Fix a rare assert error when we've tried all intro points for
15583 a hidden service and we try fetching the service descriptor again:
15584 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
15587 - Fix a major load balance bug: we were round-robining in 16 KB
15588 chunks, and servers with bandwidthrate of 20 KB, while downloading
15589 a 600 KB directory, would starve their other connections. Now we
15590 try to be a bit more fair.
15591 - Dir authorities and mirrors were never expiring the newest
15592 descriptor for each server, causing memory and directory bloat.
15593 - Fix memory-bloating and connection-bloating bug on servers: We
15594 were never closing any connection that had ever had a circuit on
15595 it, because we were checking conn->n_circuits == 0, yet we had a
15596 bug that let it go negative.
15597 - Make Tor work using squid as your http proxy again -- squid
15598 returns an error if you ask for a URL that's too long, and it uses
15599 a really generic error message. Plus, many people are behind a
15600 transparent squid so they don't even realize it.
15601 - On platforms that don't have getrlimit (like Windows), we were
15602 artificially constraining ourselves to a max of 1024
15603 connections. Now just assume that we can handle as many as 15000
15604 connections. Hopefully this won't cause other problems.
15605 - Add a new config option ExitPolicyRejectPrivate which defaults to
15606 1. This means all exit policies will begin with rejecting private
15607 addresses, unless the server operator explicitly turns it off.
15610 - Clients no longer download descriptors for non-running
15612 - Before we add new directory authorities, we should make it
15613 clear that only v1 authorities should receive/publish hidden
15614 service descriptors.
15617 - As soon as we've fetched some more directory info, immediately
15618 try to download more server descriptors. This way we don't have
15619 a 10 second pause during initial bootstrapping.
15620 - Remove even more loud log messages that the server operator can't
15622 - When we're running an obsolete or un-recommended version, make
15623 the log message more clear about what the problem is and what
15624 versions *are* still recommended.
15625 - Provide a more useful warn message when our onion queue gets full:
15626 the CPU is too slow or the exit policy is too liberal.
15627 - Don't warn when we receive a 503 from a dirserver/cache -- this
15628 will pave the way for them being able to refuse if they're busy.
15629 - When we fail to bind a listener, try to provide a more useful
15630 log message: e.g., "Is Tor already running?"
15631 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
15632 Goldberg can prove things about our handshake protocol more
15634 - MaxConn has been obsolete for a while now. Document the ConnLimit
15635 config option, which is a *minimum* number of file descriptors
15636 that must be available else Tor refuses to start.
15637 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
15638 if you log to syslog and want something other than LOG_DAEMON.
15639 - Make dirservers generate a separate "guard" flag to mean,
15640 "would make a good entry guard". Make clients parse it and vote
15641 on it. Not used by clients yet.
15642 - Implement --with-libevent-dir option to ./configure. Also, improve
15643 search techniques to find libevent, and use those for openssl too.
15644 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
15645 - Only start testing reachability once we've established a
15646 circuit. This will make startup on dirservers less noisy.
15647 - Don't try to upload hidden service descriptors until we have
15648 established a circuit.
15649 - Fix the controller's "attachstream 0" command to treat conn like
15650 it just connected, doing address remapping, handling .exit and
15651 .onion idioms, and so on. Now we're more uniform in making sure
15652 that the controller hears about new and closing connections.
15655 Changes in version 0.1.1.12-alpha - 2006-01-11
15656 o Bugfixes on 0.1.1.x:
15657 - The fix to close duplicate server connections was closing all
15658 Tor client connections if they didn't establish a circuit
15659 quickly enough. Oops.
15660 - Fix minor memory issue (double-free) that happened on exit.
15662 o Bugfixes on 0.1.0.x:
15663 - Tor didn't warn when it failed to open a log file.
15666 Changes in version 0.1.1.11-alpha - 2006-01-10
15667 o Crashes in 0.1.1.x:
15668 - Include all the assert/crash fixes from 0.1.0.16.
15669 - If you start Tor and then quit very quickly, there were some
15670 races that tried to free things that weren't allocated yet.
15671 - Fix a rare memory stomp if you're running hidden services.
15672 - Fix segfault when specifying DirServer in config without nickname.
15673 - Fix a seg fault when you finish connecting to a server but at
15674 that moment you dump his server descriptor.
15675 - Extendcircuit and Attachstream controller commands would
15676 assert/crash if you don't give them enough arguments.
15677 - Fix an assert error when we're out of space in the connection_list
15678 and we try to post a hidden service descriptor (reported by weasel).
15679 - If you specify a relative torrc path and you set RunAsDaemon in
15680 your torrc, then it chdir()'s to the new directory. If you HUP,
15681 it tries to load the new torrc location, fails, and exits.
15682 The fix: no longer allow a relative path to torrc using -f.
15685 - Implement "entry guards": automatically choose a handful of entry
15686 nodes and stick with them for all circuits. Only pick new guards
15687 when the ones you have are unsuitable, and if the old guards
15688 become suitable again, switch back. This will increase security
15689 dramatically against certain end-point attacks. The EntryNodes
15690 config option now provides some hints about which entry guards you
15691 want to use most; and StrictEntryNodes means to only use those.
15692 - New directory logic: download by descriptor digest, not by
15693 fingerprint. Caches try to download all listed digests from
15694 authorities; clients try to download "best" digests from caches.
15695 This avoids partitioning and isolating attacks better.
15696 - Make the "stable" router flag in network-status be the median of
15697 the uptimes of running valid servers, and make clients pay
15698 attention to the network-status flags. Thus the cutoff adapts
15699 to the stability of the network as a whole, making IRC, IM, etc
15700 connections more reliable.
15703 - Tor servers with dynamic IP addresses were needing to wait 18
15704 hours before they could start doing reachability testing using
15705 the new IP address and ports. This is because they were using
15706 the internal descriptor to learn what to test, yet they were only
15707 rebuilding the descriptor once they decided they were reachable.
15708 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
15709 to download certain server descriptors, throw them away, and then
15710 fetch them again after 30 minutes. Now mirrors throw away these
15711 server descriptors so clients can't get them.
15712 - We were leaving duplicate connections to other ORs open for a week,
15713 rather than closing them once we detect a duplicate. This only
15714 really affected authdirservers, but it affected them a lot.
15715 - Spread the authdirservers' reachability testing over the entire
15716 testing interval, so we don't try to do 500 TLS's at once every
15720 - If the network is down, and we try to connect to a conn because
15721 we have a circuit in mind, and we timeout (30 seconds) because the
15722 network never answers, we were expiring the circuit, but we weren't
15723 obsoleting the connection or telling the entry_guards functions.
15724 - Some Tor servers process billions of cells per day. These statistics
15725 need to be uint64_t's.
15726 - Check for integer overflows in more places, when adding elements
15727 to smartlists. This could possibly prevent a buffer overflow
15728 on malicious huge inputs. I don't see any, but I haven't looked
15730 - ReachableAddresses kept growing new "reject *:*" lines on every
15732 - When you "setconf log" via the controller, it should remove all
15733 logs. We were automatically adding back in a "log notice stdout".
15734 - Newly bootstrapped Tor networks couldn't establish hidden service
15735 circuits until they had nodes with high uptime. Be more tolerant.
15736 - We were marking servers down when they could not answer every piece
15737 of the directory request we sent them. This was far too harsh.
15738 - Fix the torify (tsocks) config file to not use Tor for localhost
15740 - Directory authorities now go to the proper authority when asking for
15741 a networkstatus, even when they want a compressed one.
15742 - Fix a harmless bug that was causing Tor servers to log
15743 "Got an end because of misc error, but we're not an AP. Closing."
15744 - Authorities were treating their own descriptor changes as cosmetic,
15745 meaning the descriptor available in the network-status and the
15746 descriptor that clients downloaded were different.
15747 - The OS X installer was adding a symlink for tor_resolve but
15748 the binary was called tor-resolve (reported by Thomas Hardly).
15749 - Workaround a problem with some http proxies where they refuse GET
15750 requests that specify "Content-Length: 0" (reported by Adrian).
15751 - Fix wrong log message when you add a "HiddenServiceNodes" config
15752 line without any HiddenServiceDir line (reported by Chris Thomas).
15755 - Write the TorVersion into the state file so we have a prayer of
15756 keeping forward and backward compatibility.
15757 - Revive the FascistFirewall config option rather than eliminating it:
15758 now it's a synonym for ReachableAddresses *:80,*:443.
15759 - Clients choose directory servers from the network status lists,
15760 not from their internal list of router descriptors. Now they can
15761 go to caches directly rather than needing to go to authorities
15763 - Directory authorities ignore router descriptors that have only
15764 cosmetic differences: do this for 0.1.0.x servers now too.
15765 - Add a new flag to network-status indicating whether the server
15766 can answer v2 directory requests too.
15767 - Authdirs now stop whining so loudly about bad descriptors that
15768 they fetch from other dirservers. So when there's a log complaint,
15769 it's for sure from a freshly uploaded descriptor.
15770 - Reduce memory requirements in our structs by changing the order
15772 - There used to be two ways to specify your listening ports in a
15773 server descriptor: on the "router" line and with a separate "ports"
15774 line. Remove support for the "ports" line.
15775 - New config option "AuthDirRejectUnlisted" for auth dirservers as
15776 a panic button: if we get flooded with unusable servers we can
15777 revert to only listing servers in the approved-routers file.
15778 - Auth dir servers can now mark a fingerprint as "!reject" or
15779 "!invalid" in the approved-routers file (as its nickname), to
15780 refuse descriptors outright or include them but marked as invalid.
15781 - Servers store bandwidth history across restarts/crashes.
15782 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
15783 get a better idea of why their circuits failed. Not used yet.
15784 - Directory mirrors now cache up to 16 unrecognized network-status
15785 docs. Now we can add new authdirservers and they'll be cached too.
15786 - When picking a random directory, prefer non-authorities if any
15788 - New controller option "getinfo desc/all-recent" to fetch the
15789 latest server descriptor for every router that Tor knows about.
15792 Changes in version 0.1.0.16 - 2006-01-02
15793 o Crash bugfixes on 0.1.0.x:
15794 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
15795 corrupting the heap, losing FDs, or crashing when we need to resize
15796 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
15797 - It turns out sparc64 platforms crash on unaligned memory access
15798 too -- so detect and avoid this.
15799 - Handle truncated compressed data correctly (by detecting it and
15801 - Fix possible-but-unlikely free(NULL) in control.c.
15802 - When we were closing connections, there was a rare case that
15803 stomped on memory, triggering seg faults and asserts.
15804 - Avoid potential infinite recursion when building a descriptor. (We
15805 don't know that it ever happened, but better to fix it anyway.)
15806 - We were neglecting to unlink marked circuits from soon-to-close OR
15807 connections, which caused some rare scribbling on freed memory.
15808 - Fix a memory stomping race bug when closing the joining point of two
15809 rendezvous circuits.
15810 - Fix an assert in time parsing found by Steven Murdoch.
15812 o Other bugfixes on 0.1.0.x:
15813 - When we're doing reachability testing, provide more useful log
15814 messages so the operator knows what to expect.
15815 - Do not check whether DirPort is reachable when we are suppressing
15816 advertising it because of hibernation.
15817 - When building with -static or on Solaris, we sometimes needed -ldl.
15818 - When we're deciding whether a stream has enough circuits around
15819 that can handle it, count the freshly dirty ones and not the ones
15820 that are so dirty they won't be able to handle it.
15821 - When we're expiring old circuits, we had a logic error that caused
15822 us to close new rendezvous circuits rather than old ones.
15823 - Give a more helpful log message when you try to change ORPort via
15824 the controller: you should upgrade Tor if you want that to work.
15825 - We were failing to parse Tor versions that start with "Tor ".
15826 - Tolerate faulty streams better: when a stream fails for reason
15827 exitpolicy, stop assuming that the router is lying about his exit
15828 policy. When a stream fails for reason misc, allow it to retry just
15829 as if it was resolvefailed. When a stream has failed three times,
15830 reset its failure count so we can try again and get all three tries.
15833 Changes in version 0.1.1.10-alpha - 2005-12-11
15834 o Correctness bugfixes on 0.1.0.x:
15835 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
15836 corrupting the heap, losing FDs, or crashing when we need to resize
15837 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
15838 - Stop doing the complex voodoo overkill checking for insecure
15839 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
15840 - When we were closing connections, there was a rare case that
15841 stomped on memory, triggering seg faults and asserts.
15842 - We were neglecting to unlink marked circuits from soon-to-close OR
15843 connections, which caused some rare scribbling on freed memory.
15844 - When we're deciding whether a stream has enough circuits around
15845 that can handle it, count the freshly dirty ones and not the ones
15846 that are so dirty they won't be able to handle it.
15847 - Recover better from TCP connections to Tor servers that are
15848 broken but don't tell you (it happens!); and rotate TLS
15849 connections once a week.
15850 - When we're expiring old circuits, we had a logic error that caused
15851 us to close new rendezvous circuits rather than old ones.
15852 - Fix a scary-looking but apparently harmless bug where circuits
15853 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
15854 servers, and never switch to state CIRCUIT_STATE_OPEN.
15855 - When building with -static or on Solaris, we sometimes needed to
15857 - Give a useful message when people run Tor as the wrong user,
15858 rather than telling them to start chowning random directories.
15859 - We were failing to inform the controller about new .onion streams.
15861 o Security bugfixes on 0.1.0.x:
15862 - Refuse server descriptors if the fingerprint line doesn't match
15863 the included identity key. Tor doesn't care, but other apps (and
15864 humans) might actually be trusting the fingerprint line.
15865 - We used to kill the circuit when we receive a relay command we
15866 don't recognize. Now we just drop it.
15867 - Start obeying our firewall options more rigorously:
15868 . If we can't get to a dirserver directly, try going via Tor.
15869 . Don't ever try to connect (as a client) to a place our
15870 firewall options forbid.
15871 . If we specify a proxy and also firewall options, obey the
15872 firewall options even when we're using the proxy: some proxies
15873 can only proxy to certain destinations.
15874 - Fix a bug found by Lasse Overlier: when we were making internal
15875 circuits (intended to be cannibalized later for rendezvous and
15876 introduction circuits), we were picking them so that they had
15877 useful exit nodes. There was no need for this, and it actually
15878 aids some statistical attacks.
15879 - Start treating internal circuits and exit circuits separately.
15880 It's important to keep them separate because internal circuits
15881 have their last hops picked like middle hops, rather than like
15882 exit hops. So exiting on them will break the user's expectations.
15884 o Bugfixes on 0.1.1.x:
15885 - Take out the mis-feature where we tried to detect IP address
15886 flapping for people with DynDNS, and chose not to upload a new
15887 server descriptor sometimes.
15888 - Try to be compatible with OpenSSL 0.9.6 again.
15889 - Log fix: when the controller is logging about .onion addresses,
15890 sometimes it didn't include the ".onion" part of the address.
15891 - Don't try to modify options->DirServers internally -- if the
15892 user didn't specify any, just add the default ones directly to
15893 the trusted dirserver list. This fixes a bug where people running
15894 controllers would use SETCONF on some totally unrelated config
15895 option, and Tor would start yelling at them about changing their
15897 - Let the controller's redirectstream command specify a port, in
15898 case the controller wants to change that too.
15899 - When we requested a pile of server descriptors, we sometimes
15900 accidentally launched a duplicate request for the first one.
15901 - Bugfix for trackhostexits: write down the fingerprint of the
15902 chosen exit, not its nickname, because the chosen exit might not
15904 - When parsing foo.exit, if foo is unknown, and we are leaving
15905 circuits unattached, set the chosen_exit field and leave the
15906 address empty. This matters because controllers got confused
15908 - Directory authorities no longer try to download server
15909 descriptors that they know they will reject.
15911 o Features and updates:
15912 - Replace balanced trees with hash tables: this should make stuff
15913 significantly faster.
15914 - Resume using the AES counter-mode implementation that we ship,
15915 rather than OpenSSL's. Ours is significantly faster.
15916 - Many other CPU and memory improvements.
15917 - Add a new config option FastFirstHopPK (on by default) so clients
15918 do a trivial crypto handshake for their first hop, since TLS has
15919 already taken care of confidentiality and authentication.
15920 - Add a new config option TestSocks so people can see if their
15921 applications are using socks4, socks4a, socks5-with-ip, or
15922 socks5-with-hostname. This way they don't have to keep mucking
15923 with tcpdump and wondering if something got cached somewhere.
15924 - Warn when listening on a public address for socks. I suspect a
15925 lot of people are setting themselves up as open socks proxies,
15926 and they have no idea that jerks on the Internet are using them,
15927 since they simply proxy the traffic into the Tor network.
15928 - Add "private:*" as an alias in configuration for policies. Now
15929 you can simplify your exit policy rather than needing to list
15930 every single internal or nonroutable network space.
15931 - Add a new controller event type that allows controllers to get
15932 all server descriptors that were uploaded to a router in its role
15933 as authoritative dirserver.
15934 - Start shipping socks-extensions.txt, tor-doc-unix.html,
15935 tor-doc-server.html, and stylesheet.css in the tarball.
15936 - Stop shipping tor-doc.html in the tarball.
15939 Changes in version 0.1.1.9-alpha - 2005-11-15
15940 o Usability improvements:
15941 - Start calling it FooListenAddress rather than FooBindAddress,
15942 since few of our users know what it means to bind an address
15944 - Reduce clutter in server logs. We're going to try to make
15945 them actually usable now. New config option ProtocolWarnings that
15946 lets you hear about how _other Tors_ are breaking the protocol. Off
15948 - Divide log messages into logging domains. Once we put some sort
15949 of interface on this, it will let people looking at more verbose
15950 log levels specify the topics they want to hear more about.
15951 - Make directory servers return better http 404 error messages
15952 instead of a generic "Servers unavailable".
15953 - Check for even more Windows version flags when writing the platform
15954 string in server descriptors, and note any we don't recognize.
15955 - Clean up more of the OpenSSL memory when exiting, so we can detect
15956 memory leaks better.
15957 - Make directory authorities be non-versioning, non-naming by
15958 default. Now we can add new directory servers without requiring
15959 their operators to pay close attention.
15960 - When logging via syslog, include the pid whenever we provide
15961 a log entry. Suggested by Todd Fries.
15963 o Performance improvements:
15964 - Directory servers now silently throw away new descriptors that
15965 haven't changed much if the timestamps are similar. We do this to
15966 tolerate older Tor servers that upload a new descriptor every 15
15967 minutes. (It seemed like a good idea at the time.)
15968 - Inline bottleneck smartlist functions; use fast versions by default.
15969 - Add a "Map from digest to void*" abstraction digestmap_t so we
15970 can do less hex encoding/decoding. Use it in router_get_by_digest()
15971 to resolve a performance bottleneck.
15972 - Allow tor_gzip_uncompress to extract as much as possible from
15973 truncated compressed data. Try to extract as many
15974 descriptors as possible from truncated http responses (when
15975 DIR_PURPOSE_FETCH_ROUTERDESC).
15976 - Make circ->onionskin a pointer, not a static array. moria2 was using
15977 125000 circuit_t's after it had been up for a few weeks, which
15978 translates to 20+ megs of wasted space.
15979 - The private half of our EDH handshake keys are now chosen out
15980 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
15982 o Security improvements:
15983 - Start making directory caches retain old routerinfos, so soon
15984 clients can start asking by digest of descriptor rather than by
15985 fingerprint of server.
15986 - Add half our entropy from RAND_poll in OpenSSL. This knows how
15987 to use egd (if present), openbsd weirdness (if present), vms/os2
15988 weirdness (if we ever port there), and more in the future.
15990 o Bugfixes on 0.1.0.x:
15991 - Do round-robin writes of at most 16 kB per write. This might be
15992 more fair on loaded Tor servers, and it might resolve our Windows
15993 crash bug. It might also slow things down.
15994 - Our TLS handshakes were generating a single public/private
15995 keypair for the TLS context, rather than making a new one for
15996 each new connections. Oops. (But we were still rotating them
15997 periodically, so it's not so bad.)
15998 - When we were cannibalizing a circuit with a particular exit
15999 node in mind, we weren't checking to see if that exit node was
16000 already present earlier in the circuit. Oops.
16001 - When a Tor server's IP changes (e.g. from a dyndns address),
16002 upload a new descriptor so clients will learn too.
16003 - Really busy servers were keeping enough circuits open on stable
16004 connections that they were wrapping around the circuit_id
16005 space. (It's only two bytes.) This exposed a bug where we would
16006 feel free to reuse a circuit_id even if it still exists but has
16007 been marked for close. Try to fix this bug. Some bug remains.
16008 - If we would close a stream early (e.g. it asks for a .exit that
16009 we know would refuse it) but the LeaveStreamsUnattached config
16010 option is set by the controller, then don't close it.
16012 o Bugfixes on 0.1.1.8-alpha:
16013 - Fix a big pile of memory leaks, some of them serious.
16014 - Do not try to download a routerdesc if we would immediately reject
16016 - Resume inserting a newline between all router descriptors when
16017 generating (old style) signed directories, since our spec says
16019 - When providing content-type application/octet-stream for
16020 server descriptors using .z, we were leaving out the
16021 content-encoding header. Oops. (Everything tolerated this just
16022 fine, but that doesn't mean we need to be part of the problem.)
16023 - Fix a potential seg fault in getconf and getinfo using version 1
16024 of the controller protocol.
16025 - Avoid crash: do not check whether DirPort is reachable when we
16026 are suppressing it because of hibernation.
16027 - Make --hash-password not crash on exit.
16030 Changes in version 0.1.1.8-alpha - 2005-10-07
16031 o New features (major):
16032 - Clients don't download or use the directory anymore. Now they
16033 download and use network-statuses from the trusted dirservers,
16034 and fetch individual server descriptors as needed from mirrors.
16035 See dir-spec.txt for all the gory details.
16036 - Be more conservative about whether to advertise our DirPort.
16037 The main change is to not advertise if we're running at capacity
16038 and either a) we could hibernate or b) our capacity is low and
16039 we're using a default DirPort.
16040 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
16042 o New features (minor):
16043 - Try to be smart about when to retry network-status and
16044 server-descriptor fetches. Still needs some tuning.
16045 - Stop parsing, storing, or using running-routers output (but
16046 mirrors still cache and serve it).
16047 - Consider a threshold of versioning dirservers (dirservers who have
16048 an opinion about which Tor versions are still recommended) before
16049 deciding whether to warn the user that he's obsolete.
16050 - Dirservers can now reject/invalidate by key and IP, with the
16051 config options "AuthDirInvalid" and "AuthDirReject". This is
16052 useful since currently we automatically list servers as running
16053 and usable even if we know they're jerks.
16054 - Provide dire warnings to any users who set DirServer; move it out
16055 of torrc.sample and into torrc.complete.
16056 - Add MyFamily to torrc.sample in the server section.
16057 - Add nicknames to the DirServer line, so we can refer to them
16058 without requiring all our users to memorize their IP addresses.
16059 - When we get an EOF or a timeout on a directory connection, note
16060 how many bytes of serverdesc we are dropping. This will help
16061 us determine whether it is smart to parse incomplete serverdesc
16063 - Add a new function to "change pseudonyms" -- that is, to stop
16064 using any currently-dirty circuits for new streams, so we don't
16065 link new actions to old actions. Currently it's only called on
16066 HUP (or SIGNAL RELOAD).
16067 - On sighup, if UseHelperNodes changed to 1, use new circuits.
16068 - Start using RAND_bytes rather than RAND_pseudo_bytes from
16069 OpenSSL. Also, reseed our entropy every hour, not just at
16070 startup. And entropy in 512-bit chunks, not 160-bit chunks.
16072 o Fixes on 0.1.1.7-alpha:
16073 - Nobody ever implemented EVENT_ADDRMAP for control protocol
16074 version 0, so don't let version 0 controllers ask for it.
16075 - If you requested something with too many newlines via the
16076 v1 controller protocol, you could crash tor.
16077 - Fix a number of memory leaks, including some pretty serious ones.
16078 - Re-enable DirPort testing again, so Tor servers will be willing
16079 to advertise their DirPort if it's reachable.
16080 - On TLS handshake, only check the other router's nickname against
16081 its expected nickname if is_named is set.
16083 o Fixes forward-ported from 0.1.0.15:
16084 - Don't crash when we don't have any spare file descriptors and we
16085 try to spawn a dns or cpu worker.
16086 - Make the numbers in read-history and write-history into uint64s,
16087 so they don't overflow and publish negatives in the descriptor.
16089 o Fixes on 0.1.0.x:
16090 - For the OS X package's modified privoxy config file, comment
16091 out the "logfile" line so we don't log everything passed
16093 - We were whining about using socks4 or socks5-with-local-lookup
16094 even when it's an IP in the "virtual" range we designed exactly
16096 - We were leaking some memory every time the client changes IPs.
16097 - Never call free() on tor_malloc()d memory. This will help us
16098 use dmalloc to detect memory leaks.
16099 - Check for named servers when looking them up by nickname;
16100 warn when we'recalling a non-named server by its nickname;
16101 don't warn twice about the same name.
16102 - Try to list MyFamily elements by key, not by nickname, and warn
16103 if we've not heard of the server.
16104 - Make windows platform detection (uname equivalent) smarter.
16105 - It turns out sparc64 doesn't like unaligned access either.
16108 Changes in version 0.1.0.15 - 2005-09-23
16109 o Bugfixes on 0.1.0.x:
16110 - Reject ports 465 and 587 (spam targets) in default exit policy.
16111 - Don't crash when we don't have any spare file descriptors and we
16112 try to spawn a dns or cpu worker.
16113 - Get rid of IgnoreVersion undocumented config option, and make us
16114 only warn, never exit, when we're running an obsolete version.
16115 - Don't try to print a null string when your server finds itself to
16116 be unreachable and the Address config option is empty.
16117 - Make the numbers in read-history and write-history into uint64s,
16118 so they don't overflow and publish negatives in the descriptor.
16119 - Fix a minor memory leak in smartlist_string_remove().
16120 - We were only allowing ourselves to upload a server descriptor at
16121 most every 20 minutes, even if it changed earlier than that.
16122 - Clean up log entries that pointed to old URLs.
16125 Changes in version 0.1.1.7-alpha - 2005-09-14
16126 o Fixes on 0.1.1.6-alpha:
16127 - Exit servers were crashing when people asked them to make a
16128 connection to an address not in their exit policy.
16129 - Looking up a non-existent stream for a v1 control connection would
16131 - Fix a seg fault if we ask a dirserver for a descriptor by
16132 fingerprint but he doesn't know about him.
16133 - SETCONF was appending items to linelists, not clearing them.
16134 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
16135 out and refuse the setconf if it would fail.
16136 - Downgrade the dirserver log messages when whining about
16140 - Add Peter Palfrader's check-tor script to tor/contrib/
16141 It lets you easily check whether a given server (referenced by
16142 nickname) is reachable by you.
16143 - Numerous changes to move towards client-side v2 directories. Not
16146 o Fixes on 0.1.0.x:
16147 - If the user gave tor an odd number of command-line arguments,
16148 we were silently ignoring the last one. Now we complain and fail.
16149 [This wins the oldest-bug prize -- this bug has been present since
16150 November 2002, as released in Tor 0.0.0.]
16151 - Do not use unaligned memory access on alpha, mips, or mipsel.
16152 It *works*, but is very slow, so we treat them as if it doesn't.
16153 - Retry directory requests if we fail to get an answer we like
16154 from a given dirserver (we were retrying before, but only if
16155 we fail to connect).
16156 - When writing the RecommendedVersions line, sort them first.
16157 - When the client asked for a rendezvous port that the hidden
16158 service didn't want to provide, we were sending an IP address
16159 back along with the end cell. Fortunately, it was zero. But stop
16161 - Correct "your server is reachable" log entries to indicate that
16162 it was self-testing that told us so.
16165 Changes in version 0.1.1.6-alpha - 2005-09-09
16166 o Fixes on 0.1.1.5-alpha:
16167 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
16168 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
16169 - Fix bug with tor_memmem finding a match at the end of the string.
16170 - Make unit tests run without segfaulting.
16171 - Resolve some solaris x86 compile warnings.
16172 - Handle duplicate lines in approved-routers files without warning.
16173 - Fix bug where as soon as a server refused any requests due to his
16174 exit policy (e.g. when we ask for localhost and he tells us that's
16175 127.0.0.1 and he won't do it), we decided he wasn't obeying his
16176 exit policy using him for any exits.
16177 - Only do openssl hardware accelerator stuff if openssl version is
16180 o New controller features/fixes:
16181 - Add a "RESETCONF" command so you can set config options like
16182 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
16183 a config option in the torrc with no value, then it clears it
16184 entirely (rather than setting it to its default).
16185 - Add a "GETINFO config-file" to tell us where torrc is.
16186 - Avoid sending blank lines when GETINFO replies should be empty.
16187 - Add a QUIT command for the controller (for using it manually).
16188 - Fix a bug in SAVECONF that was adding default dirservers and
16189 other redundant entries to the torrc file.
16191 o Start on the new directory design:
16192 - Generate, publish, cache, serve new network-status format.
16193 - Publish individual descriptors (by fingerprint, by "all", and by
16195 - Publish client and server recommended versions separately.
16196 - Allow tor_gzip_uncompress() to handle multiple concatenated
16197 compressed strings. Serve compressed groups of router
16198 descriptors. The compression logic here could be more
16200 - Distinguish v1 authorities (all currently trusted directories)
16201 from v2 authorities (all trusted directories).
16202 - Change DirServers config line to note which dirs are v1 authorities.
16203 - Add configuration option "V1AuthoritativeDirectory 1" which
16204 moria1, moria2, and tor26 should set.
16205 - Remove option when getting directory cache to see whether they
16206 support running-routers; they all do now. Replace it with one
16207 to see whether caches support v2 stuff.
16210 - Dirservers now do their own external reachability testing of each
16211 Tor server, and only list them as running if they've been found to
16212 be reachable. We also send back warnings to the server's logs if
16213 it uploads a descriptor that we already believe is unreachable.
16214 - Implement exit enclaves: if we know an IP address for the
16215 destination, and there's a running Tor server at that address
16216 which allows exit to the destination, then extend the circuit to
16217 that exit first. This provides end-to-end encryption and end-to-end
16218 authentication. Also, if the user wants a .exit address or enclave,
16219 use 4 hops rather than 3, and cannibalize a general circ for it
16221 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
16222 controller. Also, rotate dns and cpu workers if the controller
16223 changes options that will affect them; and initialize the dns
16224 worker cache tree whether or not we start out as a server.
16225 - Only upload a new server descriptor when options change, 18
16226 hours have passed, uptime is reset, or bandwidth changes a lot.
16227 - Check [X-]Forwarded-For headers in HTTP requests when generating
16228 log messages. This lets people run dirservers (and caches) behind
16229 Apache but still know which IP addresses are causing warnings.
16231 o Config option changes:
16232 - Replace (Fascist)Firewall* config options with a new
16233 ReachableAddresses option that understands address policies.
16234 For example, "ReachableAddresses *:80,*:443"
16235 - Get rid of IgnoreVersion undocumented config option, and make us
16236 only warn, never exit, when we're running an obsolete version.
16237 - Make MonthlyAccountingStart config option truly obsolete now.
16239 o Fixes on 0.1.0.x:
16240 - Reject ports 465 and 587 in the default exit policy, since
16241 people have started using them for spam too.
16242 - It turns out we couldn't bootstrap a network since we added
16243 reachability detection in 0.1.0.1-rc. Good thing the Tor network
16244 has never gone down. Add an AssumeReachable config option to let
16245 servers and dirservers bootstrap. When we're trying to build a
16246 high-uptime or high-bandwidth circuit but there aren't enough
16247 suitable servers, try being less picky rather than simply failing.
16248 - Our logic to decide if the OR we connected to was the right guy
16249 was brittle and maybe open to a mitm for unverified routers.
16250 - We weren't cannibalizing circuits correctly for
16251 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
16252 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
16253 build those from scratch. This should make hidden services faster.
16254 - Predict required circuits better, with an eye toward making hidden
16255 services faster on the service end.
16256 - Retry streams if the exit node sends back a 'misc' failure. This
16257 should result in fewer random failures. Also, after failing
16258 from resolve failed or misc, reset the num failures, so we give
16259 it a fair shake next time we try.
16260 - Clean up the rendezvous warn log msgs, and downgrade some to info.
16261 - Reduce severity on logs about dns worker spawning and culling.
16262 - When we're shutting down and we do something like try to post a
16263 server descriptor or rendezvous descriptor, don't complain that
16264 we seem to be unreachable. Of course we are, we're shutting down.
16265 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
16266 We don't use them yet, but maybe one day our DNS resolver will be
16267 able to discover them.
16268 - Make ContactInfo mandatory for authoritative directory servers.
16269 - Require server descriptors to list IPv4 addresses -- hostnames
16270 are no longer allowed. This also fixes some potential security
16271 problems with people providing hostnames as their address and then
16272 preferentially resolving them to partition users.
16273 - Change log line for unreachability to explicitly suggest /etc/hosts
16274 as the culprit. Also make it clearer what IP address and ports we're
16275 testing for reachability.
16276 - Put quotes around user-supplied strings when logging so users are
16277 more likely to realize if they add bad characters (like quotes)
16279 - Let auth dir servers start without specifying an Address config
16281 - Make unit tests (and other invocations that aren't the real Tor)
16282 run without launching listeners, creating subdirectories, and so on.
16285 Changes in version 0.1.1.5-alpha - 2005-08-08
16286 o Bugfixes included in 0.1.0.14.
16288 o Bugfixes on 0.1.0.x:
16289 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
16290 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
16291 it would silently using ignore the 6668.
16294 Changes in version 0.1.0.14 - 2005-08-08
16295 o Bugfixes on 0.1.0.x:
16296 - Fix the other half of the bug with crypto handshakes
16298 - Fix an assert trigger if you send a 'signal term' via the
16299 controller when it's listening for 'event info' messages.
16302 Changes in version 0.1.1.4-alpha - 2005-08-04
16303 o Bugfixes included in 0.1.0.13.
16306 - Improve tor_gettimeofday() granularity on windows.
16307 - Make clients regenerate their keys when their IP address changes.
16308 - Implement some more GETINFO goodness: expose helper nodes, config
16309 options, getinfo keys.
16312 Changes in version 0.1.0.13 - 2005-08-04
16313 o Bugfixes on 0.1.0.x:
16314 - Fix a critical bug in the security of our crypto handshakes.
16315 - Fix a size_t underflow in smartlist_join_strings2() that made
16316 it do bad things when you hand it an empty smartlist.
16317 - Fix Windows installer to ship Tor license (thanks to Aphex for
16318 pointing out this oversight) and put a link to the doc directory
16320 - Explicitly set no-unaligned-access for sparc: it turns out the
16321 new gcc's let you compile broken code, but that doesn't make it
16325 Changes in version 0.1.1.3-alpha - 2005-07-23
16326 o Bugfixes on 0.1.1.2-alpha:
16327 - Fix a bug in handling the controller's "post descriptor"
16329 - Fix several bugs in handling the controller's "extend circuit"
16331 - Fix a bug in handling the controller's "stream status" event.
16332 - Fix an assert failure if we have a controller listening for
16333 circuit events and we go offline.
16334 - Re-allow hidden service descriptors to publish 0 intro points.
16335 - Fix a crash when generating your hidden service descriptor if
16336 you don't have enough intro points already.
16338 o New features on 0.1.1.2-alpha:
16339 - New controller function "getinfo accounting", to ask how
16340 many bytes we've used in this time period.
16341 - Experimental support for helper nodes: a lot of the risk from
16342 a small static adversary comes because users pick new random
16343 nodes every time they rebuild a circuit. Now users will try to
16344 stick to the same small set of entry nodes if they can. Not
16345 enabled by default yet.
16347 o Bugfixes on 0.1.0.12:
16348 - If you're an auth dir server, always publish your dirport,
16349 even if you haven't yet found yourself to be reachable.
16350 - Fix a size_t underflow in smartlist_join_strings2() that made
16351 it do bad things when you hand it an empty smartlist.
16354 Changes in version 0.1.0.12 - 2005-07-18
16355 o New directory servers:
16356 - tor26 has changed IP address.
16358 o Bugfixes on 0.1.0.x:
16359 - Fix a possible double-free in tor_gzip_uncompress().
16360 - When --disable-threads is set, do not search for or link against
16361 pthreads libraries.
16362 - Don't trigger an assert if an authoritative directory server
16363 claims its dirport is 0.
16364 - Fix bug with removing Tor as an NT service: some people were
16365 getting "The service did not return an error." Thanks to Matt
16369 Changes in version 0.1.1.2-alpha - 2005-07-15
16370 o New directory servers:
16371 - tor26 has changed IP address.
16373 o Bugfixes on 0.1.0.x, crashes/leaks:
16374 - Port the servers-not-obeying-their-exit-policies fix from
16376 - Fix an fd leak in start_daemon().
16377 - On Windows, you can't always reopen a port right after you've
16378 closed it. So change retry_listeners() to only close and re-open
16379 ports that have changed.
16380 - Fix a possible double-free in tor_gzip_uncompress().
16382 o Bugfixes on 0.1.0.x, usability:
16383 - When tor_socketpair() fails in Windows, give a reasonable
16384 Windows-style errno back.
16385 - Let people type "tor --install" as well as "tor -install" when
16387 want to make it an NT service.
16388 - NT service patch from Matt Edman to improve error messages.
16389 - When the controller asks for a config option with an abbreviated
16390 name, give the full name in our response.
16391 - Correct the man page entry on TrackHostExitsExpire.
16392 - Looks like we were never delivering deflated (i.e. compressed)
16393 running-routers lists, even when asked. Oops.
16394 - When --disable-threads is set, do not search for or link against
16395 pthreads libraries.
16397 o Bugfixes on 0.1.1.x:
16398 - Fix a seg fault with autodetecting which controller version is
16402 - New hidden service descriptor format: put a version in it, and
16403 let people specify introduction/rendezvous points that aren't
16404 in "the directory" (which is subjective anyway).
16405 - Allow the DEBUG controller event to work again. Mark certain log
16406 entries as "don't tell this to controllers", so we avoid cycles.
16409 Changes in version 0.1.0.11 - 2005-06-30
16410 o Bugfixes on 0.1.0.x:
16411 - Fix major security bug: servers were disregarding their
16412 exit policies if clients behaved unexpectedly.
16413 - Make OS X init script check for missing argument, so we don't
16414 confuse users who invoke it incorrectly.
16415 - Fix a seg fault in "tor --hash-password foo".
16416 - The MAPADDRESS control command was broken.
16419 Changes in version 0.1.1.1-alpha - 2005-06-29
16421 - Make OS X init script check for missing argument, so we don't
16422 confuse users who invoke it incorrectly.
16423 - Fix a seg fault in "tor --hash-password foo".
16424 - Fix a possible way to DoS dirservers.
16425 - When we complain that your exit policy implicitly allows local or
16426 private address spaces, name them explicitly so operators can
16428 - Make the log message less scary when all the dirservers are
16429 temporarily unreachable.
16430 - We were printing the number of idle dns workers incorrectly when
16434 - Revised controller protocol (version 1) that uses ascii rather
16435 than binary. Add supporting libraries in python and java so you
16436 can use the controller from your applications without caring how
16437 our protocol works.
16438 - Spiffy new support for crypto hardware accelerators. Can somebody
16442 Changes in version 0.0.9.10 - 2005-06-16
16443 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
16444 - Refuse relay cells that claim to have a length larger than the
16445 maximum allowed. This prevents a potential attack that could read
16446 arbitrary memory (e.g. keys) from an exit server's process
16450 Changes in version 0.1.0.10 - 2005-06-14
16451 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
16452 libevent before 1.1a.
16455 Changes in version 0.1.0.9-rc - 2005-06-09
16457 - Reset buf->highwater every time buf_shrink() is called, not just on
16458 a successful shrink. This was causing significant memory bloat.
16459 - Fix buffer overflow when checking hashed passwords.
16460 - Security fix: if seeding the RNG on Win32 fails, quit.
16461 - Allow seeding the RNG on Win32 even when you're not running as
16463 - Disable threading on Solaris too. Something is wonky with it,
16464 cpuworkers, and reentrant libs.
16465 - Reenable the part of the code that tries to flush as soon as an
16466 OR outbuf has a full TLS record available. Perhaps this will make
16467 OR outbufs not grow as huge except in rare cases, thus saving lots
16468 of CPU time plus memory.
16469 - Reject malformed .onion addresses rather then passing them on as
16470 normal web requests.
16471 - Adapt patch from Adam Langley: fix possible memory leak in
16472 tor_lookup_hostname().
16473 - Initialize libevent later in the startup process, so the logs are
16474 already established by the time we start logging libevent warns.
16475 - Use correct errno on win32 if libevent fails.
16476 - Check and warn about known-bad/slow libevent versions.
16477 - Pay more attention to the ClientOnly config option.
16478 - Have torctl.in/tor.sh.in check for location of su binary (needed
16480 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
16481 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
16482 HttpProxyAuthenticator
16483 - Stop warning about sigpipes in the logs. We're going to
16484 pretend that getting these occassionally is normal and fine.
16485 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
16487 installer screens; and don't put stuff into StartupItems unless
16488 the user asks you to.
16489 - Require servers that use the default dirservers to have public IP
16490 addresses. We have too many servers that are configured with private
16491 IPs and their admins never notice the log entries complaining that
16492 their descriptors are being rejected.
16493 - Add OSX uninstall instructions. An actual uninstall script will
16497 Changes in version 0.1.0.8-rc - 2005-05-23
16499 - It turns out that kqueue on OS X 10.3.9 was causing kernel
16500 panics. Disable kqueue on all OS X Tors.
16501 - Fix RPM: remove duplicate line accidentally added to the rpm
16503 - Disable threads on openbsd too, since its gethostaddr is not
16505 - Tolerate libevent 0.8 since it still works, even though it's
16507 - Enable building on Red Hat 9.0 again.
16508 - Allow the middle hop of the testing circuit to be running any
16509 version, now that most of them have the bugfix to let them connect
16510 to unknown servers. This will allow reachability testing to work
16511 even when 0.0.9.7-0.0.9.9 become obsolete.
16512 - Handle relay cells with rh.length too large. This prevents
16513 a potential attack that could read arbitrary memory (maybe even
16514 keys) from the exit server's process.
16515 - We screwed up the dirport reachability testing when we don't yet
16516 have a cached version of the directory. Hopefully now fixed.
16517 - Clean up router_load_single_router() (used by the controller),
16518 so it doesn't seg fault on error.
16519 - Fix a minor memory leak when somebody establishes an introduction
16520 point at your Tor server.
16521 - If a socks connection ends because read fails, don't warn that
16522 you're not sending a socks reply back.
16525 - Add HttpProxyAuthenticator config option too, that works like
16526 the HttpsProxyAuthenticator config option.
16527 - Encode hashed controller passwords in hex instead of base64,
16528 to make it easier to write controllers.
16531 Changes in version 0.1.0.7-rc - 2005-05-17
16533 - Fix a bug in the OS X package installer that prevented it from
16534 installing on Tiger.
16535 - Fix a script bug in the OS X package installer that made it
16536 complain during installation.
16537 - Find libevent even if it's hiding in /usr/local/ and your
16538 CFLAGS and LDFLAGS don't tell you to look there.
16539 - Be able to link with libevent as a shared library (the default
16540 after 1.0d), even if it's hiding in /usr/local/lib and even
16541 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
16542 assuming you're running gcc. Otherwise fail and give a useful
16544 - Fix a bug in the RPM packager: set home directory for _tor to
16545 something more reasonable when first installing.
16546 - Free a minor amount of memory that is still reachable on exit.
16549 Changes in version 0.1.0.6-rc - 2005-05-14
16551 - Implement --disable-threads configure option. Disable threads on
16552 netbsd by default, because it appears to have no reentrant resolver
16554 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
16555 release (1.1) detects and disables kqueue if it's broken.
16556 - Append default exit policy before checking for implicit internal
16557 addresses. Now we don't log a bunch of complaints on startup
16558 when using the default exit policy.
16559 - Some people were putting "Address " in their torrc, and they had
16560 a buggy resolver that resolved " " to 0.0.0.0. Oops.
16561 - If DataDir is ~/.tor, and that expands to /.tor, then default to
16562 LOCALSTATEDIR/tor instead.
16563 - Fix fragmented-message bug in TorControl.py.
16564 - Resolve a minor bug which would prevent unreachable dirports
16565 from getting suppressed in the published descriptor.
16566 - When the controller gave us a new descriptor, we weren't resolving
16567 it immediately, so Tor would think its address was 0.0.0.0 until
16568 we fetched a new directory.
16569 - Fix an uppercase/lowercase case error in suppressing a bogus
16570 libevent warning on some Linuxes.
16573 - Begin scrubbing sensitive strings from logs by default. Turn off
16574 the config option SafeLogging if you need to do debugging.
16575 - Switch to a new buffer management algorithm, which tries to avoid
16576 reallocing and copying quite as much. In first tests it looks like
16577 it uses *more* memory on average, but less cpu.
16578 - First cut at support for "create-fast" cells. Clients can use
16579 these when extending to their first hop, since the TLS already
16580 provides forward secrecy and authentication. Not enabled on
16582 - When dirservers refuse a router descriptor, we now log its
16583 contactinfo, platform, and the poster's IP address.
16584 - Call tor_free_all instead of connections_free_all after forking, to
16585 save memory on systems that need to fork.
16586 - Whine at you if you're a server and you don't set your contactinfo.
16587 - Implement --verify-config command-line option to check if your torrc
16588 is valid without actually launching Tor.
16589 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
16590 rather than just rejecting it.
16593 Changes in version 0.1.0.5-rc - 2005-04-27
16595 - Stop trying to print a null pointer if an OR conn fails because
16596 we didn't like its cert.
16598 - Switch our internal buffers implementation to use a ring buffer,
16599 to hopefully improve performance for fast servers a lot.
16600 - Add HttpsProxyAuthenticator support (basic auth only), based
16601 on patch from Adam Langley.
16602 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
16603 the fast servers that have been joining lately.
16604 - Give hidden service accesses extra time on the first attempt,
16605 since 60 seconds is often only barely enough. This might improve
16607 - Improve performance for dirservers: stop re-parsing the whole
16608 directory every time you regenerate it.
16609 - Add more debugging info to help us find the weird dns freebsd
16610 pthreads bug; cleaner debug messages to help track future issues.
16613 Changes in version 0.0.9.9 - 2005-04-23
16614 o Bugfixes on 0.0.9.x:
16615 - If unofficial Tor clients connect and send weird TLS certs, our
16616 Tor server triggers an assert. This release contains a minimal
16617 backport from the broader fix that we put into 0.1.0.4-rc.
16620 Changes in version 0.1.0.4-rc - 2005-04-23
16622 - If unofficial Tor clients connect and send weird TLS certs, our
16623 Tor server triggers an assert. Stop asserting, and start handling
16624 TLS errors better in other situations too.
16625 - When the controller asks us to tell it about all the debug-level
16626 logs, it turns out we were generating debug-level logs while
16627 telling it about them, which turns into a bad loop. Now keep
16628 track of whether you're sending a debug log to the controller,
16629 and don't log when you are.
16630 - Fix the "postdescriptor" feature of the controller interface: on
16631 non-complete success, only say "done" once.
16633 - Clients are now willing to load balance over up to 2mB, not 1mB,
16634 of advertised bandwidth capacity.
16635 - Add a NoPublish config option, so you can be a server (e.g. for
16636 testing running Tor servers in other Tor networks) without
16637 publishing your descriptor to the primary dirservers.
16640 Changes in version 0.1.0.3-rc - 2005-04-08
16641 o Improvements on 0.1.0.2-rc:
16642 - Client now retries when streams end early for 'hibernating' or
16643 'resource limit' reasons, rather than failing them.
16644 - More automated handling for dirserver operators:
16645 - Automatically approve nodes running 0.1.0.2-rc or later,
16646 now that the the reachability detection stuff is working.
16647 - Now we allow two unverified servers with the same nickname
16648 but different keys. But if a nickname is verified, only that
16649 nickname+key are allowed.
16650 - If you're an authdirserver connecting to an address:port,
16651 and it's not the OR you were expecting, forget about that
16652 descriptor. If he *was* the one you were expecting, then forget
16653 about all other descriptors for that address:port.
16654 - Allow servers to publish descriptors from 12 hours in the future.
16655 Corollary: only whine about clock skew from the dirserver if
16656 he's a trusted dirserver (since now even verified servers could
16657 have quite wrong clocks).
16658 - Adjust maximum skew and age for rendezvous descriptors: let skew
16659 be 48 hours rather than 90 minutes.
16660 - Efficiency improvements:
16661 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
16662 it much faster to look up a circuit for each relay cell.
16663 - Remove most calls to assert_all_pending_dns_resolves_ok(),
16664 since they're eating our cpu on exit nodes.
16665 - Stop wasting time doing a case insensitive comparison for every
16666 dns name every time we do any lookup. Canonicalize the names to
16667 lowercase and be done with it.
16668 - Start sending 'truncated' cells back rather than destroy cells,
16669 if the circuit closes in front of you. This means we won't have
16670 to abandon partially built circuits.
16671 - Only warn once per nickname from add_nickname_list_to_smartlist
16672 per failure, so an entrynode or exitnode choice that's down won't
16674 - Put a note in the torrc about abuse potential with the default
16676 - Revise control spec and implementation to allow all log messages to
16677 be sent to controller with their severities intact (suggested by
16678 Matt Edman). Update TorControl to handle new log event types.
16679 - Provide better explanation messages when controller's POSTDESCRIPTOR
16681 - Stop putting nodename in the Platform string in server descriptors.
16682 It doesn't actually help, and it is confusing/upsetting some people.
16684 o Bugfixes on 0.1.0.2-rc:
16685 - We were printing the host mask wrong in exit policies in server
16686 descriptors. This isn't a critical bug though, since we were still
16687 obeying the exit policy internally.
16688 - Fix Tor when compiled with libevent but without pthreads: move
16689 connection_unregister() from _connection_free() to
16691 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
16692 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
16693 when we look through the connection array, we'll find any of the
16694 cpu/dnsworkers. This is no good.
16696 o Bugfixes on 0.0.9.8:
16697 - Fix possible bug on threading platforms (e.g. win32) which was
16698 leaking a file descriptor whenever a cpuworker or dnsworker died.
16699 - When using preferred entry or exit nodes, ignore whether the
16700 circuit wants uptime or capacity. They asked for the nodes, they
16702 - chdir() to your datadirectory at the *end* of the daemonize process,
16703 not the beginning. This was a problem because the first time you
16704 run tor, if your datadir isn't there, and you have runasdaemon set
16705 to 1, it will try to chdir to it before it tries to create it. Oops.
16706 - Handle changed router status correctly when dirserver reloads
16707 fingerprint file. We used to be dropping all unverified descriptors
16708 right then. The bug was hidden because we would immediately
16709 fetch a directory from another dirserver, which would include the
16710 descriptors we just dropped.
16711 - When we're connecting to an OR and he's got a different nickname/key
16712 than we were expecting, only complain loudly if we're an OP or a
16713 dirserver. Complaining loudly to the OR admins just confuses them.
16714 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
16715 artificially capped at 500kB.
16718 Changes in version 0.0.9.8 - 2005-04-07
16719 o Bugfixes on 0.0.9.x:
16720 - We have a bug that I haven't found yet. Sometimes, very rarely,
16721 cpuworkers get stuck in the 'busy' state, even though the cpuworker
16722 thinks of itself as idle. This meant that no new circuits ever got
16723 established. Here's a workaround to kill any cpuworker that's been
16724 busy for more than 100 seconds.
16727 Changes in version 0.1.0.2-rc - 2005-04-01
16728 o Bugfixes on 0.1.0.1-rc:
16729 - Fixes on reachability detection:
16730 - Don't check for reachability while hibernating.
16731 - If ORPort is reachable but DirPort isn't, still publish the
16732 descriptor, but zero out DirPort until it's found reachable.
16733 - When building testing circs for ORPort testing, use only
16734 high-bandwidth nodes, so fewer circuits fail.
16735 - Complain about unreachable ORPort separately from unreachable
16736 DirPort, so the user knows what's going on.
16737 - Make sure we only conclude ORPort reachability if we didn't
16738 initiate the conn. Otherwise we could falsely conclude that
16739 we're reachable just because we connected to the guy earlier
16740 and he used that same pipe to extend to us.
16741 - Authdirservers shouldn't do ORPort reachability detection,
16742 since they're in clique mode, so it will be rare to find a
16743 server not already connected to them.
16744 - When building testing circuits, always pick middle hops running
16745 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
16746 bug. (This is a kludge; it will go away when 0.0.9.x becomes
16748 - When we decide we're reachable, actually publish our descriptor
16750 - Fix bug in redirectstream in the controller.
16751 - Fix the state descriptor strings so logs don't claim edge streams
16752 are in a different state than they actually are.
16753 - Use recent libevent features when possible (this only really affects
16754 win32 and osx right now, because the new libevent with these
16755 features hasn't been released yet). Add code to suppress spurious
16757 - Prevent possible segfault in connection_close_unattached_ap().
16758 - Fix newlines on torrc in win32.
16759 - Improve error msgs when tor-resolve fails.
16761 o Improvements on 0.0.9.x:
16762 - New experimental script tor/contrib/ExerciseServer.py (needs more
16763 work) that uses the controller interface to build circuits and
16764 fetch pages over them. This will help us bootstrap servers that
16765 have lots of capacity but haven't noticed it yet.
16766 - New experimental script tor/contrib/PathDemo.py (needs more work)
16767 that uses the controller interface to let you choose whole paths
16769 "<hostname>.<path,separated by dots>.<length of path>.path"
16770 - When we've connected to an OR and handshaked but didn't like
16771 the result, we were closing the conn without sending destroy
16772 cells back for pending circuits. Now send those destroys.
16775 Changes in version 0.0.9.7 - 2005-04-01
16776 o Bugfixes on 0.0.9.x:
16777 - Fix another race crash bug (thanks to Glenn Fink for reporting).
16778 - Compare identity to identity, not to nickname, when extending to
16779 a router not already in the directory. This was preventing us from
16780 extending to unknown routers. Oops.
16781 - Make sure to create OS X Tor user in <500 range, so we aren't
16782 creating actual system users.
16783 - Note where connection-that-hasn't-sent-end was marked, and fix
16784 a few really loud instances of this harmless bug (it's fixed more
16788 Changes in version 0.1.0.1-rc - 2005-03-28
16790 - Add reachability testing. Your Tor server will automatically try
16791 to see if its ORPort and DirPort are reachable from the outside,
16792 and it won't upload its descriptor until it decides they are.
16793 - Handle unavailable hidden services better. Handle slow or busy
16794 hidden services better.
16795 - Add support for CONNECTing through https proxies, with "HttpsProxy"
16797 - New exit policy: accept most low-numbered ports, rather than
16798 rejecting most low-numbered ports.
16799 - More Tor controller support (still experimental). See
16800 http://tor.eff.org/doc/control-spec.txt for all the new features,
16801 including signals to emulate unix signals from any platform;
16802 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
16803 closestream; closecircuit; etc.
16804 - Make nt services work and start on startup on win32 (based on
16805 patch by Matt Edman).
16806 - Add a new AddressMap config directive to rewrite incoming socks
16807 addresses. This lets you, for example, declare an implicit
16808 required exit node for certain sites.
16809 - Add a new TrackHostExits config directive to trigger addressmaps
16810 for certain incoming socks addresses -- for sites that break when
16811 your exit keeps changing (based on patch by Mike Perry).
16812 - Redo the client-side dns cache so it's just an addressmap too.
16813 - Notice when our IP changes, and reset stats/uptime/reachability.
16814 - When an application is using socks5, give him the whole variety of
16815 potential socks5 responses (connect refused, host unreachable, etc),
16816 rather than just "success" or "failure".
16817 - A more sane version numbering system. See
16818 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
16819 - New contributed script "exitlist": a simple python script to
16820 parse directories and find Tor nodes that exit to listed
16822 - New contributed script "privoxy-tor-toggle" to toggle whether
16823 Privoxy uses Tor. Seems to be configured for Debian by default.
16824 - Report HTTP reasons to client when getting a response from directory
16825 servers -- so you can actually know what went wrong.
16826 - New config option MaxAdvertisedBandwidth which lets you advertise
16827 a low bandwidthrate (to not attract as many circuits) while still
16828 allowing a higher bandwidthrate in reality.
16830 o Robustness/stability fixes:
16831 - Make Tor use Niels Provos's libevent instead of its current
16832 poll-but-sometimes-select mess. This will let us use faster async
16833 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
16835 - pthread support now too. This was forced because when we forked,
16836 we ended up wasting a lot of duplicate ram over time. Also switch
16837 to foo_r versions of some library calls to allow reentry and
16839 - Better handling for heterogeneous / unreliable nodes:
16840 - Annotate circuits w/ whether they aim to contain high uptime nodes
16841 and/or high capacity nodes. When building circuits, choose
16843 - This means that every single node in an intro rend circuit,
16844 not just the last one, will have a minimum uptime.
16845 - New config option LongLivedPorts to indicate application streams
16846 that will want high uptime circuits.
16847 - Servers reset uptime when a dir fetch entirely fails. This
16848 hopefully reflects stability of the server's network connectivity.
16849 - If somebody starts his tor server in Jan 2004 and then fixes his
16850 clock, don't make his published uptime be a year.
16851 - Reset published uptime when you wake up from hibernation.
16852 - Introduce a notion of 'internal' circs, which are chosen without
16853 regard to the exit policy of the last hop. Intro and rendezvous
16854 circs must be internal circs, to avoid leaking information. Resolve
16855 and connect streams can use internal circs if they want.
16856 - New circuit pooling algorithm: make sure to have enough circs around
16857 to satisfy any predicted ports, and also make sure to have 2 internal
16858 circs around if we've required internal circs lately (and with high
16859 uptime if we've seen that lately too).
16860 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
16861 which describes how often we retry making new circuits if current
16862 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
16863 how long we're willing to make use of an already-dirty circuit.
16864 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
16865 circ as necessary, if there are any completed ones lying around
16866 when we try to launch one.
16867 - Make hidden services try to establish a rendezvous for 30 seconds,
16868 rather than for n (where n=3) attempts to build a circuit.
16869 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
16870 "ShutdownWaitLength".
16871 - Try to be more zealous about calling connection_edge_end when
16872 things go bad with edge conns in connection.c.
16873 - Revise tor-spec to add more/better stream end reasons.
16874 - Revise all calls to connection_edge_end to avoid sending "misc",
16875 and to take errno into account where possible.
16878 - Fix a race condition that can trigger an assert, when we have a
16879 pending create cell and an OR connection fails right then.
16880 - Fix several double-mark-for-close bugs, e.g. where we were finding
16881 a conn for a cell even if that conn is already marked for close.
16882 - Make sequence of log messages when starting on win32 with no config
16883 file more reasonable.
16884 - When choosing an exit node for a new non-internal circ, don't take
16885 into account whether it'll be useful for any pending x.onion
16886 addresses -- it won't.
16887 - Turn addr_policy_compare from a tristate to a quadstate; this should
16888 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
16889 for google.com" problem.
16890 - Make "platform" string in descriptor more accurate for Win32 servers,
16891 so it's not just "unknown platform".
16892 - Fix an edge case in parsing config options (thanks weasel).
16893 If they say "--" on the commandline, it's not an option.
16894 - Reject odd-looking addresses at the client (e.g. addresses that
16895 contain a colon), rather than having the server drop them because
16897 - tor-resolve requests were ignoring .exit if there was a working circuit
16898 they could use instead.
16899 - REUSEADDR on normal platforms means you can rebind to the port
16900 right after somebody else has let it go. But REUSEADDR on win32
16901 means to let you bind to the port _even when somebody else
16902 already has it bound_! So, don't do that on Win32.
16903 - Change version parsing logic: a version is "obsolete" if it is not
16904 recommended and (1) there is a newer recommended version in the
16905 same series, or (2) there are no recommended versions in the same
16906 series, but there are some recommended versions in a newer series.
16907 A version is "new" if it is newer than any recommended version in
16909 - Stop most cases of hanging up on a socks connection without sending
16913 - Require BandwidthRate to be at least 20kB/s for servers.
16914 - When a dirserver causes you to give a warn, mention which dirserver
16916 - New config option DirAllowPrivateAddresses for authdirservers.
16917 Now by default they refuse router descriptors that have non-IP or
16918 private-IP addresses.
16919 - Stop publishing socksport in the directory, since it's not
16920 actually meant to be public. For compatibility, publish a 0 there
16922 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
16923 smart" value, that is low for servers and high for clients.
16924 - If our clock jumps forward by 100 seconds or more, assume something
16925 has gone wrong with our network and abandon all not-yet-used circs.
16926 - Warn when exit policy implicitly allows local addresses.
16927 - If we get an incredibly skewed timestamp from a dirserver mirror
16928 that isn't a verified OR, don't warn -- it's probably him that's
16930 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
16931 cookies to disk and doesn't log each web request to disk. (Thanks
16932 to Brett Carrington for pointing this out.)
16933 - When a client asks us for a dir mirror and we don't have one,
16934 launch an attempt to get a fresh one.
16935 - If we're hibernating and we get a SIGINT, exit immediately.
16936 - Add --with-dmalloc ./configure option, to track memory leaks.
16937 - And try to free all memory on closing, so we can detect what
16939 - Cache local dns resolves correctly even when they're .exit
16941 - Give a better warning when some other server advertises an
16942 ORPort that is actually an apache running ssl.
16943 - Add "opt hibernating 1" to server descriptor to make it clearer
16944 whether the server is hibernating.
16947 Changes in version 0.0.9.6 - 2005-03-24
16948 o Bugfixes on 0.0.9.x (crashes and asserts):
16949 - Add new end stream reasons to maintainance branch. Fix bug where
16950 reason (8) could trigger an assert. Prevent bug from recurring.
16951 - Apparently win32 stat wants paths to not end with a slash.
16952 - Fix assert triggers in assert_cpath_layer_ok(), where we were
16953 blowing away the circuit that conn->cpath_layer points to, then
16954 checking to see if the circ is well-formed. Backport check to make
16955 sure we dont use the cpath on a closed connection.
16956 - Prevent circuit_resume_edge_reading_helper() from trying to package
16957 inbufs for marked-for-close streams.
16958 - Don't crash on hup if your options->address has become unresolvable.
16959 - Some systems (like OS X) sometimes accept() a connection and tell
16960 you the remote host is 0.0.0.0:0. If this happens, due to some
16961 other mis-features, we get confused; so refuse the conn for now.
16963 o Bugfixes on 0.0.9.x (other):
16964 - Fix harmless but scary "Unrecognized content encoding" warn message.
16965 - Add new stream error reason: TORPROTOCOL reason means "you are not
16966 speaking a version of Tor I understand; say bye-bye to your stream."
16967 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
16968 into the future, now that we are more tolerant of skew. This
16969 resolves a bug where a Tor server would refuse to cache a directory
16970 because all the directories it gets are too far in the future;
16971 yet the Tor server never logs any complaints about clock skew.
16972 - Mac packaging magic: make man pages useable, and do not overwrite
16973 existing torrc files.
16974 - Make OS X log happily to /var/log/tor/tor.log
16977 Changes in version 0.0.9.5 - 2005-02-22
16978 o Bugfixes on 0.0.9.x:
16979 - Fix an assert race at exit nodes when resolve requests fail.
16980 - Stop picking unverified dir mirrors--it only leads to misery.
16981 - Patch from Matt Edman to make NT services work better. Service
16982 support is still not compiled into the executable by default.
16983 - Patch from Dmitri Bely so the Tor service runs better under
16984 the win32 SYSTEM account.
16985 - Make tor-resolve actually work (?) on Win32.
16986 - Fix a sign bug when getrlimit claims to have 4+ billion
16987 file descriptors available.
16988 - Stop refusing to start when bandwidthburst == bandwidthrate.
16989 - When create cells have been on the onion queue more than five
16990 seconds, just send back a destroy and take them off the list.
16993 Changes in version 0.0.9.4 - 2005-02-03
16994 o Bugfixes on 0.0.9:
16995 - Fix an assert bug that took down most of our servers: when
16996 a server claims to have 1 GB of bandwidthburst, don't
16998 - Don't crash as badly if we have spawned the max allowed number
16999 of dnsworkers, or we're out of file descriptors.
17000 - Block more file-sharing ports in the default exit policy.
17001 - MaxConn is now automatically set to the hard limit of max
17002 file descriptors we're allowed (ulimit -n), minus a few for
17004 - Give a clearer message when servers need to raise their
17005 ulimit -n when they start running out of file descriptors.
17006 - SGI Compatibility patches from Jan Schaumann.
17007 - Tolerate a corrupt cached directory better.
17008 - When a dirserver hasn't approved your server, list which one.
17009 - Go into soft hibernation after 95% of the bandwidth is used,
17010 not 99%. This is especially important for daily hibernators who
17011 have a small accounting max. Hopefully it will result in fewer
17012 cut connections when the hard hibernation starts.
17013 - Load-balance better when using servers that claim more than
17014 800kB/s of capacity.
17015 - Make NT services work (experimental, only used if compiled in).
17018 Changes in version 0.0.9.3 - 2005-01-21
17019 o Bugfixes on 0.0.9:
17020 - Backport the cpu use fixes from main branch, so busy servers won't
17021 need as much processor time.
17022 - Work better when we go offline and then come back, or when we
17023 run Tor at boot before the network is up. We do this by
17024 optimistically trying to fetch a new directory whenever an
17025 application request comes in and we think we're offline -- the
17026 human is hopefully a good measure of when the network is back.
17027 - Backport some minimal hidserv bugfixes: keep rend circuits open as
17028 long as you keep using them; actually publish hidserv descriptors
17029 shortly after they change, rather than waiting 20-40 minutes.
17030 - Enable Mac startup script by default.
17031 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
17032 - When you update AllowUnverifiedNodes or FirewallPorts via the
17033 controller's setconf feature, we were always appending, never
17035 - When you update HiddenServiceDir via setconf, it was screwing up
17036 the order of reading the lines, making it fail.
17037 - Do not rewrite a cached directory back to the cache; otherwise we
17038 will think it is recent and not fetch a newer one on startup.
17039 - Workaround for webservers that lie about Content-Encoding: Tor
17040 now tries to autodetect compressed directories and compression
17041 itself. This lets us Proxypass dir fetches through apache.
17044 Changes in version 0.0.9.2 - 2005-01-04
17045 o Bugfixes on 0.0.9 (crashes and asserts):
17046 - Fix an assert on startup when the disk is full and you're logging
17048 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
17049 style address, then we'd crash.
17050 - Fix an assert trigger when the running-routers string we get from
17051 a dirserver is broken.
17052 - Make worker threads start and run on win32. Now win32 servers
17054 - Bandaid (not actually fix, but now it doesn't crash) an assert
17055 where the dns worker dies mysteriously and the main Tor process
17056 doesn't remember anything about the address it was resolving.
17058 o Bugfixes on 0.0.9 (Win32):
17059 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
17060 name out of the warning/assert messages.
17061 - Fix a superficial "unhandled error on read" bug on win32.
17062 - The win32 installer no longer requires a click-through for our
17063 license, since our Free Software license grants rights but does not
17065 - Win32: When connecting to a dirserver fails, try another one
17066 immediately. (This was already working for non-win32 Tors.)
17067 - Stop trying to parse $HOME on win32 when hunting for default
17069 - Make tor-resolve.c work on win32 by calling network_init().
17071 o Bugfixes on 0.0.9 (other):
17072 - Make 0.0.9.x build on Solaris again.
17073 - Due to a fencepost error, we were blowing away the \n when reporting
17074 confvalue items in the controller. So asking for multiple config
17075 values at once couldn't work.
17076 - When listing circuits that are pending on an opening OR connection,
17077 if we're an OR we were listing circuits that *end* at us as
17078 being pending on every listener, dns/cpu worker, etc. Stop that.
17079 - Dirservers were failing to create 'running-routers' or 'directory'
17080 strings if we had more than some threshold of routers. Fix them so
17081 they can handle any number of routers.
17082 - Fix a superficial "Duplicate mark for close" bug.
17083 - Stop checking for clock skew for OR connections, even for servers.
17084 - Fix a fencepost error that was chopping off the last letter of any
17085 nickname that is the maximum allowed nickname length.
17086 - Update URLs in log messages so they point to the new website.
17087 - Fix a potential problem in mangling server private keys while
17088 writing to disk (not triggered yet, as far as we know).
17089 - Include the licenses for other free software we include in Tor,
17090 now that we're shipping binary distributions more regularly.
17093 Changes in version 0.0.9.1 - 2004-12-15
17094 o Bugfixes on 0.0.9:
17095 - Make hibernation actually work.
17096 - Make HashedControlPassword config option work.
17097 - When we're reporting event circuit status to a controller,
17098 don't use the stream status code.
17101 Changes in version 0.0.9 - 2004-12-12
17103 - Clean up manpage and torrc.sample file.
17104 - Clean up severities and text of log warnings.
17106 - Make servers trigger an assert when they enter hibernation.
17109 Changes in version 0.0.9rc7 - 2004-12-08
17110 o Bugfixes on 0.0.9rc:
17111 - Fix a stack-trashing crash when an exit node begins hibernating.
17112 - Avoid looking at unallocated memory while considering which
17113 ports we need to build circuits to cover.
17114 - Stop a sigpipe: when an 'end' cell races with eof from the app,
17115 we shouldn't hold-open-until-flush if the eof arrived first.
17116 - Fix a bug with init_cookie_authentication() in the controller.
17117 - When recommending new-format log lines, if the upper bound is
17118 LOG_ERR, leave it implicit.
17120 o Bugfixes on 0.0.8.1:
17121 - Fix a whole slew of memory leaks.
17122 - Fix isspace() and friends so they still make Solaris happy
17123 but also so they don't trigger asserts on win32.
17124 - Fix parse_iso_time on platforms without strptime (eg win32).
17125 - win32: tolerate extra "readable" events better.
17126 - win32: when being multithreaded, leave parent fdarray open.
17127 - Make unit tests work on win32.
17130 Changes in version 0.0.9rc6 - 2004-12-06
17131 o Bugfixes on 0.0.9pre:
17132 - Clean up some more integer underflow opportunities (not exploitable
17134 - While hibernating, hup should not regrow our listeners.
17135 - Send an end to the streams we close when we hibernate, rather
17136 than just chopping them off.
17137 - React to eof immediately on non-open edge connections.
17139 o Bugfixes on 0.0.8.1:
17140 - Calculate timeout for waiting for a connected cell from the time
17141 we sent the begin cell, not from the time the stream started. If
17142 it took a long time to establish the circuit, we would time out
17143 right after sending the begin cell.
17144 - Fix router_compare_addr_to_addr_policy: it was not treating a port
17145 of * as always matching, so we were picking reject *:* nodes as
17146 exit nodes too. Oops.
17149 - New circuit building strategy: keep a list of ports that we've
17150 used in the past 6 hours, and always try to have 2 circuits open
17151 or on the way that will handle each such port. Seed us with port
17152 80 so web users won't complain that Tor is "slow to start up".
17153 - Make kill -USR1 dump more useful stats about circuits.
17154 - When warning about retrying or giving up, print the address, so
17155 the user knows which one it's talking about.
17156 - If you haven't used a clean circuit in an hour, throw it away,
17157 just to be on the safe side. (This means after 6 hours a totally
17158 unused Tor client will have no circuits open.)
17161 Changes in version 0.0.9rc5 - 2004-12-01
17162 o Bugfixes on 0.0.8.1:
17163 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
17164 - Let resolve conns retry/expire also, rather than sticking around
17166 - If we are using select, make sure we stay within FD_SETSIZE.
17168 o Bugfixes on 0.0.9pre:
17169 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
17170 but doesn't seem to be currently; thanks to Ilja van Sprundel for
17172 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
17173 instead. Impose minima and maxima for all *Period options; impose
17174 even tighter maxima for fetching if we are a caching dirserver.
17175 Clip rather than rejecting.
17176 - Fetch cached running-routers from servers that serve it (that is,
17177 authdirservers and servers running 0.0.9rc5-cvs or later.)
17180 - Accept *:706 (silc) in default exit policy.
17181 - Implement new versioning format for post 0.1.
17182 - Support "foo.nickname.exit" addresses, to let Alice request the
17183 address "foo" as viewed by exit node "nickname". Based on a patch
17185 - Make tor --version --version dump the cvs Id of every file.
17188 Changes in version 0.0.9rc4 - 2004-11-28
17189 o Bugfixes on 0.0.8.1:
17190 - Make windows sockets actually non-blocking (oops), and handle
17191 win32 socket errors better.
17193 o Bugfixes on 0.0.9rc1:
17194 - Actually catch the -USR2 signal.
17197 Changes in version 0.0.9rc3 - 2004-11-25
17198 o Bugfixes on 0.0.8.1:
17199 - Flush the log file descriptor after we print "Tor opening log file",
17200 so we don't see those messages days later.
17202 o Bugfixes on 0.0.9rc1:
17203 - Make tor-resolve work again.
17204 - Avoid infinite loop in tor-resolve if tor hangs up on it.
17205 - Fix an assert trigger for clients/servers handling resolves.
17208 Changes in version 0.0.9rc2 - 2004-11-24
17209 o Bugfixes on 0.0.9rc1:
17210 - I broke socks5 support while fixing the eof bug.
17211 - Allow unitless bandwidths and intervals; they default to bytes
17213 - New servers don't start out hibernating; they are active until
17214 they run out of bytes, so they have a better estimate of how
17215 long it takes, and so their operators can know they're working.
17218 Changes in version 0.0.9rc1 - 2004-11-23
17219 o Bugfixes on 0.0.8.1:
17220 - Finally fix a bug that's been plaguing us for a year:
17221 With high load, circuit package window was reaching 0. Whenever
17222 we got a circuit-level sendme, we were reading a lot on each
17223 socket, but only writing out a bit. So we would eventually reach
17224 eof. This would be noticed and acted on even when there were still
17225 bytes sitting in the inbuf.
17226 - When poll() is interrupted, we shouldn't believe the revents values.
17228 o Bugfixes on 0.0.9pre6:
17229 - Fix hibernate bug that caused pre6 to be broken.
17230 - Don't keep rephist info for routers that haven't had activity for
17231 24 hours. (This matters now that clients have keys, since we track
17233 - Never call close_temp_logs while validating log options.
17234 - Fix backslash-escaping on tor.sh.in and torctl.in.
17237 - Implement weekly/monthly/daily accounting: now you specify your
17238 hibernation properties by
17239 AccountingMax N bytes|KB|MB|GB|TB
17240 AccountingStart day|week|month [day] HH:MM
17241 Defaults to "month 1 0:00".
17242 - Let bandwidth and interval config options be specified as 5 bytes,
17243 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
17244 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
17245 get back to normal.)
17246 - If your requested entry or exit node has advertised bandwidth 0,
17248 - Be more greedy about filling up relay cells -- we try reading again
17249 once we've processed the stuff we read, in case enough has arrived
17250 to fill the last cell completely.
17251 - Apply NT service patch from Osamu Fujino. Still needs more work.
17254 Changes in version 0.0.9pre6 - 2004-11-15
17255 o Bugfixes on 0.0.8.1:
17256 - Fix assert failure on malformed socks4a requests.
17257 - Use identity comparison, not nickname comparison, to choose which
17258 half of circuit-ID-space each side gets to use. This is needed
17259 because sometimes we think of a router as a nickname, and sometimes
17260 as a hex ID, and we can't predict what the other side will do.
17261 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
17262 write() call will fail and we handle it there.
17263 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
17264 and smartlist_len, which are two major profiling offenders.
17266 o Bugfixes on 0.0.9pre5:
17267 - Fix a bug in read_all that was corrupting config files on windows.
17268 - When we're raising the max number of open file descriptors to
17269 'unlimited', don't log that we just raised it to '-1'.
17270 - Include event code with events, as required by control-spec.txt.
17271 - Don't give a fingerprint when clients do --list-fingerprint:
17272 it's misleading, because it will never be the same again.
17273 - Stop using strlcpy in tor_strndup, since it was slowing us
17275 - Remove warn on startup about missing cached-directory file.
17276 - Make kill -USR1 work again.
17277 - Hibernate if we start tor during the "wait for wakeup-time" phase
17278 of an accounting interval. Log our hibernation plans better.
17279 - Authoritative dirservers now also cache their directory, so they
17280 have it on start-up.
17283 - Fetch running-routers; cache running-routers; compress
17284 running-routers; serve compressed running-routers.z
17285 - Add NSI installer script contributed by J Doe.
17286 - Commit VC6 and VC7 workspace/project files.
17287 - Commit a tor.spec for making RPM files, with help from jbash.
17288 - Add contrib/torctl.in contributed by Glenn Fink.
17289 - Implement the control-spec's SAVECONF command, to write your
17290 configuration to torrc.
17291 - Get cookie authentication for the controller closer to working.
17292 - Include control-spec.txt in the tarball.
17293 - When set_conf changes our server descriptor, upload a new copy.
17294 But don't upload it too often if there are frequent changes.
17295 - Document authentication config in man page, and document signals
17297 - Clean up confusing parts of man page and torrc.sample.
17298 - Make expand_filename handle ~ and ~username.
17299 - Use autoconf to enable largefile support where necessary. Use
17300 ftello where available, since ftell can fail at 2GB.
17301 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
17302 log more informatively.
17303 - Give a slightly more useful output for "tor -h".
17304 - Refuse application socks connections to port 0.
17305 - Check clock skew for verified servers, but allow unverified
17306 servers and clients to have any clock skew.
17307 - Break DirFetchPostPeriod into:
17308 - DirFetchPeriod for fetching full directory,
17309 - StatusFetchPeriod for fetching running-routers,
17310 - DirPostPeriod for posting server descriptor,
17311 - RendPostPeriod for posting hidden service descriptors.
17312 - Make sure the hidden service descriptors are at a random offset
17313 from each other, to hinder linkability.
17316 Changes in version 0.0.9pre5 - 2004-11-09
17317 o Bugfixes on 0.0.9pre4:
17318 - Fix a seg fault in unit tests (doesn't affect main program).
17319 - Fix an assert bug where a hidden service provider would fail if
17320 the first hop of his rendezvous circuit was down.
17321 - Hidden service operators now correctly handle version 1 style
17322 INTRODUCE1 cells (nobody generates them still, so not a critical
17324 - If do_hup fails, actually notice.
17325 - Handle more errnos from accept() without closing the listener.
17326 Some OpenBSD machines were closing their listeners because
17327 they ran out of file descriptors.
17328 - Send resolve cells to exit routers that are running a new
17329 enough version of the resolve code to work right.
17330 - Better handling of winsock includes on non-MSV win32 compilers.
17331 - Some people had wrapped their tor client/server in a script
17332 that would restart it whenever it died. This did not play well
17333 with our "shut down if your version is obsolete" code. Now people
17334 don't fetch a new directory if their local cached version is
17336 - Make our autogen.sh work on ksh as well as bash.
17339 - Hibernation: New config option "AccountingMaxKB" lets you
17340 set how many KBytes per month you want to allow your server to
17341 consume. Rather than spreading those bytes out evenly over the
17342 month, we instead hibernate for some of the month and pop up
17343 at a deterministic time, work until the bytes are consumed, then
17344 hibernate again. Config option "MonthlyAccountingStart" lets you
17345 specify which day of the month your billing cycle starts on.
17346 - Control interface: a separate program can now talk to your
17347 client/server over a socket, and get/set config options, receive
17348 notifications of circuits and streams starting/finishing/dying,
17349 bandwidth used, etc. The next step is to get some GUIs working.
17350 Let us know if you want to help out. See doc/control-spec.txt .
17351 - Ship a contrib/tor-control.py as an example script to interact
17352 with the control port.
17353 - "tor --hash-password zzyxz" will output a salted password for
17354 use in authenticating to the control interface.
17355 - New log format in config:
17356 "Log minsev[-maxsev] stdout|stderr|syslog" or
17357 "Log minsev[-maxsev] file /var/foo"
17360 - DirPolicy config option, to let people reject incoming addresses
17361 from their dirserver.
17362 - "tor --list-fingerprint" will list your identity key fingerprint
17364 - Add "pass" target for RedirectExit, to make it easier to break
17365 out of a sequence of RedirectExit rules.
17366 - Clients now generate a TLS cert too, in preparation for having
17367 them act more like real nodes.
17368 - Ship src/win32/ in the tarball, so people can use it to build.
17369 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
17371 - New "router-status" line in directory, to better bind each verified
17372 nickname to its identity key.
17373 - Deprecate unofficial config option abbreviations, and abbreviations
17374 not on the command line.
17375 - Add a pure-C tor-resolve implementation.
17376 - Use getrlimit and friends to ensure we can reach MaxConn (currently
17377 1024) file descriptors.
17379 o Code security improvements, inspired by Ilja:
17380 - Replace sprintf with snprintf. (I think they were all safe, but
17382 - Replace strcpy/strncpy with strlcpy in more places.
17383 - Avoid strcat; use snprintf or strlcat instead.
17384 - snprintf wrapper with consistent (though not C99) overflow behavior.
17387 Changes in version 0.0.9pre4 - 2004-10-17
17388 o Bugfixes on 0.0.9pre3:
17389 - If the server doesn't specify an exit policy, use the real default
17390 exit policy, not reject *:*.
17391 - Ignore fascistfirewall when uploading/downloading hidden service
17392 descriptors, since we go through Tor for those; and when using
17393 an HttpProxy, since we assume it can reach them all.
17394 - When looking for an authoritative dirserver, use only the ones
17395 configured at boot. Don't bother looking in the directory.
17396 - The rest of the fix for get_default_conf_file() on older win32.
17397 - Make 'Routerfile' config option obsolete.
17400 - New 'MyFamily nick1,...' config option for a server to
17401 specify other servers that shouldn't be used in the same circuit
17402 with it. Only believed if nick1 also specifies us.
17403 - New 'NodeFamily nick1,nick2,...' config option for a client to
17404 specify nodes that it doesn't want to use in the same circuit.
17405 - New 'Redirectexit pattern address:port' config option for a
17406 server to redirect exit connections, e.g. to a local squid.
17409 Changes in version 0.0.9pre3 - 2004-10-13
17410 o Bugfixes on 0.0.8.1:
17411 - Better torrc example lines for dirbindaddress and orbindaddress.
17412 - Improved bounds checking on parsed ints (e.g. config options and
17413 the ones we find in directories.)
17414 - Better handling of size_t vs int, so we're more robust on 64
17416 - Fix the rest of the bug where a newly started OR would appear
17417 as unverified even after we've added his fingerprint and hupped
17419 - Fix a bug from 0.0.7: when read() failed on a stream, we would
17420 close it without sending back an end. So 'connection refused'
17421 would simply be ignored and the user would get no response.
17423 o Bugfixes on 0.0.9pre2:
17424 - Serving the cached-on-disk directory to people is bad. We now
17425 provide no directory until we've fetched a fresh one.
17426 - Workaround for bug on windows where cached-directories get crlf
17428 - Make get_default_conf_file() work on older windows too.
17429 - If we write a *:* exit policy line in the descriptor, don't write
17430 any more exit policy lines.
17433 - Use only 0.0.9pre1 and later servers for resolve cells.
17434 - Make the dirservers file obsolete.
17435 - Include a dir-signing-key token in directories to tell the
17436 parsing entity which key is being used to sign.
17437 - Remove the built-in bulky default dirservers string.
17438 - New config option "Dirserver %s:%d [fingerprint]", which can be
17439 repeated as many times as needed. If no dirservers specified,
17440 default to moria1,moria2,tor26.
17441 - Make moria2 advertise a dirport of 80, so people behind firewalls
17442 will be able to get a directory.
17443 - Http proxy support
17444 - Dirservers translate requests for http://%s:%d/x to /x
17445 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
17446 be routed through this host.
17447 - Clients ask for /tor/x rather than /x for new enough dirservers.
17448 This way we can one day coexist peacefully with apache.
17449 - Clients specify a "Host: %s%d" http header, to be compatible
17450 with more proxies, and so running squid on an exit node can work.
17453 Changes in version 0.0.8.1 - 2004-10-13
17455 - Fix a seg fault that can be triggered remotely for Tor
17456 clients/servers with an open dirport.
17457 - Fix a rare assert trigger, where routerinfos for entries in
17458 our cpath would expire while we're building the path.
17459 - Fix a bug in OutboundBindAddress so it (hopefully) works.
17460 - Fix a rare seg fault for people running hidden services on
17461 intermittent connections.
17462 - Fix a bug in parsing opt keywords with objects.
17463 - Fix a stale pointer assert bug when a stream detaches and
17465 - Fix a string format vulnerability (probably not exploitable)
17466 in reporting stats locally.
17467 - Fix an assert trigger: sometimes launching circuits can fail
17468 immediately, e.g. because too many circuits have failed recently.
17469 - Fix a compile warning on 64 bit platforms.
17472 Changes in version 0.0.9pre2 - 2004-10-03
17474 - Make fetching a cached directory work for 64-bit platforms too.
17475 - Make zlib.h a required header, not an optional header.
17478 Changes in version 0.0.9pre1 - 2004-10-01
17480 - Stop using separate defaults for no-config-file and
17481 empty-config-file. Now you have to explicitly turn off SocksPort,
17482 if you don't want it open.
17483 - Fix a bug in OutboundBindAddress so it (hopefully) works.
17484 - Improve man page to mention more of the 0.0.8 features.
17485 - Fix a rare seg fault for people running hidden services on
17486 intermittent connections.
17487 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
17489 - Fix more dns related bugs: send back resolve_failed and end cells
17490 more reliably when the resolve fails, rather than closing the
17491 circuit and then trying to send the cell. Also attach dummy resolve
17492 connections to a circuit *before* calling dns_resolve(), to fix
17493 a bug where cached answers would never be sent in RESOLVED cells.
17494 - When we run out of disk space, or other log writing error, don't
17495 crash. Just stop logging to that log and continue.
17496 - We were starting to daemonize before we opened our logs, so if
17497 there were any problems opening logs, we would complain to stderr,
17498 which wouldn't work, and then mysteriously exit.
17499 - Fix a rare bug where sometimes a verified OR would connect to us
17500 before he'd uploaded his descriptor, which would cause us to
17501 assign conn->nickname as though he's unverified. Now we look through
17502 the fingerprint list to see if he's there.
17503 - Fix a rare assert trigger, where routerinfos for entries in
17504 our cpath would expire while we're building the path.
17507 - Clients can ask dirservers for /dir.z to get a compressed version
17508 of the directory. Only works for servers running 0.0.9, of course.
17509 - Make clients cache directories and use them to seed their router
17510 lists at startup. This means clients have a datadir again.
17511 - Configuration infrastructure support for warning on obsolete
17513 - Respond to content-encoding headers by trying to uncompress as
17515 - Reply with a deflated directory when a client asks for "dir.z".
17516 We could use allow-encodings instead, but allow-encodings isn't
17517 specified in HTTP 1.0.
17518 - Raise the max dns workers from 50 to 100.
17519 - Discourage people from setting their dirfetchpostperiod more often
17520 than once per minute.
17521 - Protect dirservers from overzealous descriptor uploading -- wait
17522 10 seconds after directory gets dirty, before regenerating.
17525 Changes in version 0.0.8 - 2004-08-25
17526 o Port it to SunOS 5.9 / Athena
17529 Changes in version 0.0.8rc2 - 2004-08-20
17530 o Make it compile on cygwin again.
17531 o When picking unverified routers, skip those with low uptime and/or
17532 low bandwidth, depending on what properties you care about.
17535 Changes in version 0.0.8rc1 - 2004-08-18
17536 o Changes from 0.0.7.3:
17538 - Fix assert triggers: if the other side returns an address 0.0.0.0,
17539 don't put it into the client dns cache.
17540 - If a begin failed due to exit policy, but we believe the IP address
17541 should have been allowed, switch that router to exitpolicy reject *:*
17542 until we get our next directory.
17544 - Clients choose nodes proportional to advertised bandwidth.
17545 - Avoid using nodes with low uptime as introduction points.
17546 - Handle servers with dynamic IP addresses: don't replace
17547 options->Address with the resolved one at startup, and
17548 detect our address right before we make a routerinfo each time.
17549 - 'FascistFirewall' option to pick dirservers and ORs on specific
17550 ports; plus 'FirewallPorts' config option to tell FascistFirewall
17551 which ports are open. (Defaults to 80,443)
17552 - Be more aggressive about trying to make circuits when the network
17553 has changed (e.g. when you unsuspend your laptop).
17554 - Check for time skew on http headers; report date in response to
17556 - If the entrynode config line has only one node, don't pick it as
17558 - Add strict{entry|exit}nodes config options. If set to 1, then
17559 we refuse to build circuits that don't include the specified entry
17561 - OutboundBindAddress config option, to bind to a specific
17562 IP address for outgoing connect()s.
17563 - End truncated log entries (e.g. directories) with "[truncated]".
17565 o Patches to 0.0.8preX:
17567 - Patches to compile and run on win32 again (maybe)?
17568 - Fix crash when looking for ~/.torrc with no $HOME set.
17569 - Fix a race bug in the unit tests.
17570 - Handle verified/unverified name collisions better when new
17571 routerinfo's arrive in a directory.
17572 - Sometimes routers were getting entered into the stats before
17573 we'd assigned their identity_digest. Oops.
17574 - Only pick and establish intro points after we've gotten a
17577 - AllowUnverifiedNodes config option to let circuits choose no-name
17578 routers in entry,middle,exit,introduction,rendezvous positions.
17579 Allow middle and rendezvous positions by default.
17580 - Add a man page for tor-resolve.
17583 Changes in version 0.0.7.3 - 2004-08-12
17584 o Stop dnsworkers from triggering an assert failure when you
17585 ask them to resolve the host "".
17588 Changes in version 0.0.8pre3 - 2004-08-09
17589 o Changes from 0.0.7.2:
17590 - Allow multiple ORs with same nickname in routerlist -- now when
17591 people give us one identity key for a nickname, then later
17592 another, we don't constantly complain until the first expires.
17593 - Remember used bandwidth (both in and out), and publish 15-minute
17594 snapshots for the past day into our descriptor.
17595 - You can now fetch $DIRURL/running-routers to get just the
17596 running-routers line, not the whole descriptor list. (But
17597 clients don't use this yet.)
17598 - When people mistakenly use Tor as an http proxy, point them
17599 at the tor-doc.html rather than the INSTALL.
17600 - Remove our mostly unused -- and broken -- hex_encode()
17601 function. Use base16_encode() instead. (Thanks to Timo Lindfors
17602 for pointing out this bug.)
17603 - Rotate onion keys every 12 hours, not every 2 hours, so we have
17604 fewer problems with people using the wrong key.
17605 - Change the default exit policy to reject the default edonkey,
17606 kazaa, gnutella ports.
17607 - Add replace_file() to util.[ch] to handle win32's rename().
17609 o Changes from 0.0.8preX:
17610 - Fix two bugs in saving onion keys to disk when rotating, so
17611 hopefully we'll get fewer people using old onion keys.
17612 - Fix an assert error that was making SocksPolicy not work.
17613 - Be willing to expire routers that have an open dirport -- it's
17614 just the authoritative dirservers we want to not forget.
17615 - Reject tor-resolve requests for .onion addresses early, so we
17616 don't build a whole rendezvous circuit and then fail.
17617 - When you're warning a server that he's unverified, don't cry
17618 wolf unpredictably.
17619 - Fix a race condition: don't try to extend onto a connection
17620 that's still handshaking.
17621 - For servers in clique mode, require the conn to be open before
17622 you'll choose it for your path.
17623 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
17624 end relay cell, etc.
17625 - Measure bandwidth capacity over the last 24 hours, not just 12
17626 - Bugfix: authoritative dirservers were making and signing a new
17627 directory for each client, rather than reusing the cached one.
17630 Changes in version 0.0.8pre2 - 2004-08-04
17631 o Changes from 0.0.7.2:
17633 - Check directory signature _before_ you decide whether you're
17634 you're running an obsolete version and should exit.
17635 - Check directory signature _before_ you parse the running-routers
17636 list to decide who's running or verified.
17637 - Bugfixes and features:
17638 - Check return value of fclose while writing to disk, so we don't
17639 end up with broken files when servers run out of disk space.
17640 - Log a warning if the user uses an unsafe socks variant, so people
17641 are more likely to learn about privoxy or socat.
17642 - Dirservers now include RFC1123-style dates in the HTTP headers,
17643 which one day we will use to better detect clock skew.
17645 o Changes from 0.0.8pre1:
17646 - Make it compile without warnings again on win32.
17647 - Log a warning if you're running an unverified server, to let you
17648 know you might want to get it verified.
17649 - Only pick a default nickname if you plan to be a server.
17652 Changes in version 0.0.8pre1 - 2004-07-23
17654 - Made our unit tests compile again on OpenBSD 3.5, and tor
17655 itself compile again on OpenBSD on a sparc64.
17656 - We were neglecting milliseconds when logging on win32, so
17657 everything appeared to happen at the beginning of each second.
17659 o Protocol changes:
17660 - 'Extend' relay cell payloads now include the digest of the
17661 intended next hop's identity key. Now we can verify that we're
17662 extending to the right router, and also extend to routers we
17663 hadn't heard of before.
17666 - Tor nodes can now act as relays (with an advertised ORPort)
17667 without being manually verified by the dirserver operators.
17668 - Uploaded descriptors of unverified routers are now accepted
17669 by the dirservers, and included in the directory.
17670 - Verified routers are listed by nickname in the running-routers
17671 list; unverified routers are listed as "$<fingerprint>".
17672 - We now use hash-of-identity-key in most places rather than
17673 nickname or addr:port, for improved security/flexibility.
17674 - To avoid Sybil attacks, paths still use only verified servers.
17675 But now we have a chance to play around with hybrid approaches.
17676 - Nodes track bandwidth usage to estimate capacity (not used yet).
17677 - ClientOnly option for nodes that never want to become servers.
17678 - Directory caching.
17679 - "AuthoritativeDir 1" option for the official dirservers.
17680 - Now other nodes (clients and servers) will cache the latest
17681 directory they've pulled down.
17682 - They can enable their DirPort to serve it to others.
17683 - Clients will pull down a directory from any node with an open
17684 DirPort, and check the signature/timestamp correctly.
17685 - Authoritative dirservers now fetch directories from other
17686 authdirservers, to stay better synced.
17687 - Running-routers list tells who's down also, along with noting
17688 if they're verified (listed by nickname) or unverified (listed
17690 - Allow dirservers to serve running-router list separately.
17691 This isn't used yet.
17692 - ORs connect-on-demand to other ORs
17693 - If you get an extend cell to an OR you're not connected to,
17694 connect, handshake, and forward the create cell.
17695 - The authoritative dirservers stay connected to everybody,
17696 and everybody stays connected to 0.0.7 servers, but otherwise
17697 clients/servers expire unused connections after 5 minutes.
17698 - When servers get a sigint, they delay 30 seconds (refusing new
17699 connections) then exit. A second sigint causes immediate exit.
17700 - File and name management:
17701 - Look for .torrc if no CONFDIR "torrc" is found.
17702 - If no datadir is defined, then choose, make, and secure ~/.tor
17704 - If torrc not found, exitpolicy reject *:*.
17705 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
17706 - If no nickname is defined, derive default from hostname.
17707 - Rename secret key files, e.g. identity.key -> secret_id_key,
17708 to discourage people from mailing their identity key to tor-ops.
17709 - Refuse to build a circuit before the directory has arrived --
17710 it won't work anyway, since you won't know the right onion keys
17712 - Try other dirservers immediately if the one you try is down. This
17713 should tolerate down dirservers better now.
17714 - Parse tor version numbers so we can do an is-newer-than check
17715 rather than an is-in-the-list check.
17716 - New socks command 'resolve', to let us shim gethostbyname()
17718 - A 'tor_resolve' script to access the socks resolve functionality.
17719 - A new socks-extensions.txt doc file to describe our
17720 interpretation and extensions to the socks protocols.
17721 - Add a ContactInfo option, which gets published in descriptor.
17722 - Publish OR uptime in descriptor (and thus in directory) too.
17723 - Write tor version at the top of each log file
17724 - New docs in the tarball:
17726 - Document that you should proxy your SSL traffic too.
17729 Changes in version 0.0.7.2 - 2004-07-07
17730 o A better fix for the 0.0.0.0 problem, that will hopefully
17731 eliminate the remaining related assertion failures.
17734 Changes in version 0.0.7.1 - 2004-07-04
17735 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
17736 since internally we use 0.0.0.0 to signify "not yet resolved".
17739 Changes in version 0.0.7 - 2004-06-07
17740 o Updated the man page to reflect the new features.
17743 Changes in version 0.0.7rc2 - 2004-06-06
17744 o Changes from 0.0.7rc1:
17745 - Make it build on Win32 again.
17746 o Changes from 0.0.6.2:
17747 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
17751 Changes in version 0.0.7rc1 - 2004-06-02
17753 - On sighup, we were adding another log without removing the first
17754 one. So log messages would get duplicated n times for n sighups.
17755 - Several cases of using a connection after we'd freed it. The
17756 problem was that connections that are pending resolve are in both
17757 the pending_resolve tree, and also the circuit's resolving_streams
17758 list. When you want to remove one, you must remove it from both.
17759 - Fix a double-mark-for-close where an end cell arrived for a
17760 resolving stream, and then the resolve failed.
17761 - Check directory signatures based on name of signer, not on whom
17762 we got the directory from. This will let us cache directories more
17765 - Crank up some of our constants to handle more users.
17768 Changes in version 0.0.7pre1 - 2004-06-02
17769 o Fixes for crashes and other obnoxious bugs:
17770 - Fix an epipe bug: sometimes when directory connections failed
17771 to connect, we would give them a chance to flush before closing
17773 - When we detached from a circuit because of resolvefailed, we
17774 would immediately try the same circuit twice more, and then
17775 give up on the resolve thinking we'd tried three different
17777 - Limit the number of intro circuits we'll attempt to build for a
17778 hidden service per 15-minute period.
17779 - Check recommended-software string *early*, before actually parsing
17780 the directory. Thus we can detect an obsolete version and exit,
17781 even if the new directory format doesn't parse.
17782 o Fixes for security bugs:
17783 - Remember which nodes are dirservers when you startup, and if a
17784 random OR enables his dirport, don't automatically assume he's
17785 a trusted dirserver.
17787 - Directory connections were asking the wrong poll socket to
17788 start writing, and not asking themselves to start writing.
17789 - When we detached from a circuit because we sent a begin but
17790 didn't get a connected, we would use it again the first time;
17791 but after that we would correctly switch to a different one.
17792 - Stop warning when the first onion decrypt attempt fails; they
17793 will sometimes legitimately fail now that we rotate keys.
17794 - Override unaligned-access-ok check when $host_cpu is ia64 or
17795 arm. Apparently they allow it but the kernel whines.
17796 - Dirservers try to reconnect periodically too, in case connections
17798 - Fix some memory leaks in directory servers.
17799 - Allow backslash in Win32 filenames.
17800 - Made Tor build complain-free on FreeBSD, hopefully without
17801 breaking other BSD builds. We'll see.
17803 - Doxygen markup on all functions and global variables.
17804 - Make directory functions update routerlist, not replace it. So
17805 now directory disagreements are not so critical a problem.
17806 - Remove the upper limit on number of descriptors in a dirserver's
17807 directory (not that we were anywhere close).
17808 - Allow multiple logfiles at different severity ranges.
17809 - Allow *BindAddress to specify ":port" rather than setting *Port
17810 separately. Allow multiple instances of each BindAddress config
17811 option, so you can bind to multiple interfaces if you want.
17812 - Allow multiple exit policy lines, which are processed in order.
17813 Now we don't need that huge line with all the commas in it.
17814 - Enable accept/reject policies on SOCKS connections, so you can bind
17815 to 0.0.0.0 but still control who can use your OP.
17818 Changes in version 0.0.6.2 - 2004-05-16
17819 o Our integrity-checking digest was checking only the most recent cell,
17820 not the previous cells like we'd thought.
17821 Thanks to Stefan Mark for finding the flaw!
17824 Changes in version 0.0.6.1 - 2004-05-06
17825 o Fix two bugs in our AES counter-mode implementation (this affected
17826 onion-level stream encryption, but not TLS-level). It turns
17827 out we were doing something much more akin to a 16-character
17828 polyalphabetic cipher. Oops.
17829 Thanks to Stefan Mark for finding the flaw!
17830 o Retire moria3 as a directory server, and add tor26 as a directory
17834 Changes in version 0.0.6 - 2004-05-02
17835 [version bump only]
17838 Changes in version 0.0.6rc4 - 2004-05-01
17839 o Update the built-in dirservers list to use the new directory format
17840 o Fix a rare seg fault: if a node offering a hidden service attempts
17841 to build a circuit to Alice's rendezvous point and fails before it
17842 reaches the last hop, it retries with a different circuit, but
17844 o Handle windows socket errors correctly.
17847 Changes in version 0.0.6rc3 - 2004-04-28
17848 o Don't expire non-general excess circuits (if we had enough
17849 circuits open, we were expiring rendezvous circuits -- even
17850 when they had a stream attached. oops.)
17851 o Fetch randomness from /dev/urandom better (not via fopen/fread)
17852 o Better debugging for tls errors
17853 o Some versions of openssl have an SSL_pending function that erroneously
17854 returns bytes when there is a non-application record pending.
17855 o Set Content-Type on the directory and hidserv descriptor.
17856 o Remove IVs from cipher code, since AES-ctr has none.
17857 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
17858 o We were using an array of length zero in a few places.
17859 o win32's gethostbyname can't resolve an IP to an IP.
17860 o win32's close can't close a socket.
17863 Changes in version 0.0.6rc2 - 2004-04-26
17864 o Fix a bug where we were closing tls connections intermittently.
17865 It turns out openssl keeps its errors around -- so if an error
17866 happens, and you don't ask about it, and then another openssl
17867 operation happens and succeeds, and you ask if there was an error,
17868 it tells you about the first error. Fun fun.
17869 o Fix a bug that's been lurking since 27 may 03 (!)
17870 When passing back a destroy cell, we would use the wrong circ id.
17871 'Mostly harmless', but still worth fixing.
17872 o Since we don't support truncateds much, don't bother sending them;
17873 just close the circ.
17874 o check for <machine/limits.h> so we build on NetBSD again (I hope).
17875 o don't crash if a conn that sent a begin has suddenly lost its circuit
17876 (this was quite rare).
17879 Changes in version 0.0.6rc1 - 2004-04-25
17880 o We now rotate link (tls context) keys and onion keys.
17881 o CREATE cells now include oaep padding, so you can tell
17882 if you decrypted them correctly.
17883 o Add bandwidthburst to server descriptor.
17884 o Directories now say which dirserver signed them.
17885 o Use a tor_assert macro that logs failed assertions too.
17888 Changes in version 0.0.6pre5 - 2004-04-18
17889 o changes from 0.0.6pre4:
17890 - make tor build on broken freebsd 5.2 installs
17891 - fix a failed assert when you try an intro point, get a nack, and try
17892 a second one and it works.
17893 - when alice uses a port that the hidden service doesn't accept,
17894 it now sends back an end cell (denied by exit policy). otherwise
17895 alice would just have to wait to time out.
17896 - fix another rare bug: when we had tried all the intro
17897 points for a hidden service, we fetched the descriptor
17898 again, but we left our introcirc thinking it had already
17899 sent an intro, so it kept waiting for a response...
17900 - bugfix: when you sleep your hidden-service laptop, as soon
17901 as it wakes up it tries to upload a service descriptor, but
17902 socketpair fails for some reason (localhost not up yet?).
17903 now we simply give up on that upload, and we'll try again later.
17904 i'd still like to find the bug though.
17905 - if an intro circ waiting for an ack dies before getting one, then
17907 - we were reusing stale service descriptors and refetching usable
17911 Changes in version 0.0.6pre4 - 2004-04-14
17912 o changes from 0.0.6pre3:
17913 - when bob fails to connect to the rendezvous point, and his
17914 circ didn't fail because of the rendezvous point itself, then
17915 he retries a couple of times
17916 - we expire introduction and rendezvous circs more thoroughly
17917 (sometimes they were hanging around forever)
17918 - we expire unattached rendezvous streams that have been around
17919 too long (they were sticking around forever).
17920 - fix a measly fencepost error that was crashing everybody with
17924 Changes in version 0.0.6pre3 - 2004-04-14
17925 o changes from 0.0.6pre2:
17926 - make hup work again
17927 - fix some memory leaks for dirservers
17928 - allow more skew in rendezvous descriptor timestamps, to help
17929 handle people like blanu who don't know what time it is
17930 - normal circs are 3 hops, but some rend/intro circs are 4, if
17931 the initiator doesn't get to choose the last hop
17932 - send acks for introductions, so alice can know whether to try
17934 - bob publishes intro points more correctly
17935 o changes from 0.0.5:
17936 - fix an assert trigger that's been plaguing us since the days
17937 of 0.0.2prexx (thanks weasel!)
17938 - retry stream correctly when we fail to connect because of
17939 exit-policy-reject (should try another) or can't-resolve-address
17940 (also should try another, because dns on random internet servers
17942 - when we hup a dirserver and we've *removed* a server from the
17943 approved-routers list, now we remove that server from the
17944 in-memory directories too
17947 Changes in version 0.0.6pre2 - 2004-04-08
17948 o We fixed our base32 implementation. Now it works on all architectures.
17951 Changes in version 0.0.6pre1 - 2004-04-08
17953 - Hidden services and rendezvous points are implemented. Go to
17954 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
17955 hidden services. (This only works via a socks4a proxy such as
17956 Privoxy, and currently it's quite slow.)
17959 Changes in version 0.0.5 - 2004-03-30
17960 [version bump only]
17963 Changes in version 0.0.5rc3 - 2004-03-29
17964 o Install torrc as torrc.sample -- we no longer clobber your
17966 o Re-enable recommendedversion checking (we broke it in rc2, oops)
17967 o Add in a 'notice' log level for things the operator should hear
17968 but that aren't warnings
17971 Changes in version 0.0.5rc2 - 2004-03-29
17972 o Hold socks connection open until reply is flushed (if possible)
17973 o Make exit nodes resolve IPs to IPs immediately, rather than asking
17974 the dns farm to do it.
17975 o Fix c99 aliasing warnings in rephist.c
17976 o Don't include server descriptors that are older than 24 hours in the
17978 o Give socks 'reject' replies their whole 15s to attempt to flush,
17979 rather than seeing the 60s timeout and assuming the flush had failed.
17980 o Clean automake droppings from the cvs repository
17983 Changes in version 0.0.5rc1 - 2004-03-28
17984 o Fix mangled-state bug in directory fetching (was causing sigpipes).
17985 o Only build circuits after we've fetched the directory: clients were
17986 using only the directory servers before they'd fetched a directory.
17987 This also means longer startup time; so it goes.
17988 o Fix an assert trigger where an OP would fail to handshake, and we'd
17989 expect it to have a nickname.
17990 o Work around a tsocks bug: do a socks reject when AP connection dies
17991 early, else tsocks goes into an infinite loop.
17994 Changes in version 0.0.4 - 2004-03-26
17995 o When connecting to a dirserver or OR and the network is down,
17999 Changes in version 0.0.3 - 2004-03-26
18000 o Warn and fail if server chose a nickname with illegal characters
18001 o Port to Solaris and Sparc:
18002 - include missing header fcntl.h
18003 - have autoconf find -lsocket -lnsl automatically
18004 - deal with hardware word alignment
18005 - make uname() work (solaris has a different return convention)
18006 - switch from using signal() to sigaction()
18007 o Preliminary work on reputation system:
18008 - Keep statistics on success/fail of connect attempts; they're published
18009 by kill -USR1 currently.
18010 - Add a RunTesting option to try to learn link state by creating test
18011 circuits, even when SocksPort is off.
18012 - Remove unused open circuits when there are too many.
18015 Changes in version 0.0.2 - 2004-03-19
18016 - Include strlcpy and strlcat for safer string ops
18017 - define INADDR_NONE so we compile (but still not run) on solaris
18020 Changes in version 0.0.2pre27 - 2004-03-14
18022 - Allow internal tor networks (we were rejecting internal IPs,
18023 now we allow them if they're set explicitly).
18024 - And fix a few endian issues.
18027 Changes in version 0.0.2pre26 - 2004-03-14
18029 - If a stream times out after 15s without a connected cell, don't
18030 try that circuit again: try a new one.
18031 - Retry streams at most 4 times. Then give up.
18032 - When a dirserver gets a descriptor from an unknown router, it
18033 logs its fingerprint (so the dirserver operator can choose to
18034 accept it even without mail from the server operator).
18035 - Inform unapproved servers when we reject their descriptors.
18036 - Make tor build on Windows again. It works as a client, who knows
18038 - Clearer instructions in the torrc for how to set up a server.
18039 - Be more efficient about reading fd's when our global token bucket
18040 (used for rate limiting) becomes empty.
18042 - Stop asserting that computers always go forward in time. It's
18044 - When we sent a cell (e.g. destroy) and then marked an OR connection
18045 expired, we might close it before finishing a flush if the other
18046 side isn't reading right then.
18047 - Don't allow dirservers to start if they haven't defined
18048 RecommendedVersions
18049 - We were caching transient dns failures. Oops.
18050 - Prevent servers from publishing an internal IP as their address.
18051 - Address a strcat vulnerability in circuit.c
18054 Changes in version 0.0.2pre25 - 2004-03-04
18056 - Put the OR's IP in its router descriptor, not its fqdn. That way
18057 we'll stop being stalled by gethostbyname for nodes with flaky dns,
18060 - If the user typed in an address that didn't resolve, the server
18064 Changes in version 0.0.2pre24 - 2004-03-03
18066 - Fix an assertion failure in dns.c, where we were trying to dequeue
18067 a pending dns resolve even if it wasn't pending
18068 - Fix a spurious socks5 warning about still trying to write after the
18069 connection is finished.
18070 - Hold certain marked_for_close connections open until they're finished
18071 flushing, rather than losing bytes by closing them too early.
18072 - Correctly report the reason for ending a stream
18073 - Remove some duplicate calls to connection_mark_for_close
18074 - Put switch_id and start_daemon earlier in the boot sequence, so it
18075 will actually try to chdir() to options.DataDirectory
18076 - Make 'make test' exit(1) if a test fails; fix some unit tests
18077 - Make tor fail when you use a config option it doesn't know about,
18078 rather than warn and continue.
18079 - Make --version work
18080 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
18083 Changes in version 0.0.2pre23 - 2004-02-29
18085 - Print a statement when the first circ is finished, so the user
18086 knows it's working.
18087 - If a relay cell is unrecognized at the end of the circuit,
18088 send back a destroy. (So attacks to mutate cells are more
18090 - New config option 'excludenodes' to avoid certain nodes for circuits.
18091 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
18092 so you can collect coredumps there.
18094 - Fix a bug in tls flushing where sometimes data got wedged and
18095 didn't flush until more data got sent. Hopefully this bug was
18096 a big factor in the random delays we were seeing.
18097 - Make 'connected' cells include the resolved IP, so the client
18098 dns cache actually gets populated.
18099 - Disallow changing from ORPort=0 to ORPort>0 on hup.
18100 - When we time-out on a stream and detach from the circuit, send an
18101 end cell down it first.
18102 - Only warn about an unknown router (in exitnodes, entrynodes,
18103 excludenodes) after we've fetched a directory.
18106 Changes in version 0.0.2pre22 - 2004-02-26
18108 - Servers publish less revealing uname information in descriptors.
18109 - More memory tracking and assertions, to crash more usefully when
18111 - If the default torrc isn't there, just use some default defaults.
18112 Plus provide an internal dirservers file if they don't have one.
18113 - When the user tries to use Tor as an http proxy, give them an http
18114 501 failure explaining that we're a socks proxy.
18115 - Dump a new router.desc on hup, to help confused people who change
18116 their exit policies and then wonder why router.desc doesn't reflect
18118 - Clean up the generic tor.sh init script that we ship with.
18120 - If the exit stream is pending on the resolve, and a destroy arrives,
18121 then the stream wasn't getting removed from the pending list. I
18122 think this was the one causing recent server crashes.
18123 - Use a more robust poll on OSX 10.3, since their poll is flaky.
18124 - When it couldn't resolve any dirservers, it was useless from then on.
18125 Now it reloads the RouterFile (or default dirservers) if it has no
18127 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
18128 many users don't even *have* a /usr/local/sbin/.
18131 Changes in version 0.0.2pre21 - 2004-02-18
18133 - There's a ChangeLog file that actually reflects the changelog.
18134 - There's a 'torify' wrapper script, with an accompanying
18135 tor-tsocks.conf, that simplifies the process of using tsocks for
18136 tor. It even has a man page.
18137 - The tor binary gets installed to sbin rather than bin now.
18138 - Retry streams where the connected cell hasn't arrived in 15 seconds
18139 - Clean up exit policy handling -- get the default out of the torrc,
18140 so we can update it without forcing each server operator to fix
18142 - Allow imaps and pop3s in default exit policy
18144 - Prevent picking middleman nodes as the last node in the circuit
18147 Changes in version 0.0.2pre20 - 2004-01-30
18149 - We now have a deb package, and it's in debian unstable. Go to
18150 it, apt-getters. :)
18151 - I've split the TotalBandwidth option into BandwidthRate (how many
18152 bytes per second you want to allow, long-term) and
18153 BandwidthBurst (how many bytes you will allow at once before the cap
18154 kicks in). This better token bucket approach lets you, say, set
18155 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
18156 performance while not exceeding your monthly bandwidth quota.
18157 - Push out a tls record's worth of data once you've got it, rather
18158 than waiting until you've read everything waiting to be read. This
18159 may improve performance by pipelining better. We'll see.
18160 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
18161 from failed circuits (if they haven't been connected yet) and attach
18163 - Expire old streams that haven't managed to connect. Some day we'll
18164 have them reattach to new circuits instead.
18167 - Fix several memory leaks that were causing servers to become bloated
18169 - Fix a few very rare assert triggers. A few more remain.
18170 - Setuid to User _before_ complaining about running as root.
18173 Changes in version 0.0.2pre19 - 2004-01-07
18175 - Fix deadlock condition in dns farm. We were telling a child to die by
18176 closing the parent's file descriptor to him. But newer children were
18177 inheriting the open file descriptor from the parent, and since they
18178 weren't closing it, the socket never closed, so the child never read
18179 eof, so he never knew to exit. Similarly, dns workers were holding
18180 open other sockets, leading to all sorts of chaos.
18181 - New cleaner daemon() code for forking and backgrounding.
18182 - If you log to a file, it now prints an entry at the top of the
18183 logfile so you know it's working.
18184 - The onionskin challenge length was 30 bytes longer than necessary.
18185 - Started to patch up the spec so it's not quite so out of date.
18188 Changes in version 0.0.2pre18 - 2004-01-02
18190 - Fix endian issues with the 'integrity' field in the relay header.
18191 - Fix a potential bug where connections in state
18192 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
18195 Changes in version 0.0.2pre17 - 2003-12-30
18197 - Made --debuglogfile (or any second log file, actually) work.
18198 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
18199 adversary could force us into an infinite loop.
18202 - Each onionskin handshake now includes a hash of the computed key,
18203 to prove the server's identity and help perfect forward secrecy.
18204 - Changed cell size from 256 to 512 bytes (working toward compatibility
18206 - Changed cell length to 2 bytes, and moved it to the relay header.
18207 - Implemented end-to-end integrity checking for the payloads of
18209 - Separated streamid from 'recognized' (otherwise circuits will get
18210 messed up when we try to have streams exit from the middle). We
18211 use the integrity-checking to confirm that a cell is addressed to
18213 - Randomize the initial circid and streamid values, so an adversary who
18214 breaks into a node can't learn how many circuits or streams have
18218 Changes in version 0.0.2pre16 - 2003-12-14
18220 - Fixed a bug that made HUP trigger an assert
18221 - Fixed a bug where a circuit that immediately failed wasn't being
18222 counted as a failed circuit in counting retries.
18225 - Now we close the circuit when we get a truncated cell: otherwise we're
18226 open to an anonymity attack where a bad node in the path truncates
18227 the circuit and then we open streams at him.
18228 - Add port ranges to exit policies
18229 - Add a conservative default exit policy
18230 - Warn if you're running tor as root
18231 - on HUP, retry OR connections and close/rebind listeners
18232 - options.EntryNodes: try these nodes first when picking the first node
18233 - options.ExitNodes: if your best choices happen to include any of
18234 your preferred exit nodes, you choose among just those preferred
18236 - options.ExcludedNodes: nodes that are never picked in path building
18239 Changes in version 0.0.2pre15 - 2003-12-03
18240 o Robustness and bugfixes:
18241 - Sometimes clients would cache incorrect DNS resolves, which would
18242 really screw things up.
18243 - An OP that goes offline would slowly leak all its sockets and stop
18245 - A wide variety of bugfixes in exit node selection, exit policy
18246 handling, and processing pending streams when a new circuit is
18248 - Pick nodes for a path only from those the directory says are up
18249 - Choose randomly from all running dirservers, not always the first one
18250 - Increase allowed http header size for directory fetch.
18251 - Stop writing to stderr (if we're daemonized it will be closed).
18252 - Enable -g always, so cores will be more useful to me.
18253 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
18256 - Wrote a man page. It lists commonly used options.
18259 - Change default loglevel to warn.
18260 - Make PidFile default to null rather than littering in your CWD.
18261 - OnionRouter config option is now obsolete. Instead it just checks
18263 - Moved to a single unified torrc file for both clients and servers.
18266 Changes in version 0.0.2pre14 - 2003-11-29
18267 o Robustness and bugfixes:
18268 - Force the admin to make the DataDirectory himself
18269 - to get ownership/permissions right
18270 - so clients no longer make a DataDirectory and then never use it
18271 - fix bug where a client who was offline for 45 minutes would never
18272 pull down a directory again
18273 - fix (or at least hide really well) the dns assert bug that was
18274 causing server crashes
18275 - warnings and improved robustness wrt clockskew for certs
18276 - use the native daemon(3) to daemonize, when available
18277 - exit if bind() fails
18278 - exit if neither socksport nor orport is defined
18279 - include our own tor_timegm (Win32 doesn't have its own)
18280 - bugfix for win32 with lots of connections
18281 - fix minor bias in PRNG
18282 - make dirserver more robust to corrupt cached directory
18285 - Wrote the design document (woo)
18287 o Circuit building and exit policies:
18288 - Circuits no longer try to use nodes that the directory has told them
18290 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
18291 bitcounts (18.0.0.0/8).
18292 - Make AP connections standby for a circuit if no suitable circuit
18293 exists, rather than failing
18294 - Circuits choose exit node based on addr/port, exit policies, and
18295 which AP connections are standing by
18296 - Bump min pathlen from 2 to 3
18297 - Relay end cells have a payload to describe why the stream ended.
18298 - If the stream failed because of exit policy, try again with a new
18300 - Clients have a dns cache to remember resolved addresses.
18301 - Notice more quickly when we have no working circuits
18304 - APPort is now called SocksPort
18305 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
18307 - RecommendedVersions is now a config variable rather than
18308 hardcoded (for dirservers)
18309 - Reloads config on HUP
18310 - Usage info on -h or --help
18311 - If you set User and Group config vars, it'll setu/gid to them.
18314 Changes in version 0.0.2pre13 - 2003-10-19
18315 o General stability:
18316 - SSL_write no longer fails when it returns WANTWRITE and the number
18317 of bytes in the buf has changed by the next SSL_write call.
18318 - Fix segfault fetching directory when network is down
18319 - Fix a variety of minor memory leaks
18320 - Dirservers reload the fingerprints file on HUP, so I don't have
18321 to take down the network when I approve a new router
18322 - Default server config file has explicit Address line to specify fqdn
18325 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
18326 - Make listener connections not ever alloc bufs
18328 o Autoconf improvements:
18329 - don't clobber an external CFLAGS in ./configure
18330 - Make install now works
18331 - create var/lib/tor on make install
18332 - autocreate a tor.sh initscript to help distribs
18333 - autocreate the torrc and sample-server-torrc with correct paths
18335 o Log files and Daemonizing now work:
18336 - If --DebugLogFile is specified, log to it at -l debug
18337 - If --LogFile is specified, use it instead of commandline
18338 - If --RunAsDaemon is set, tor forks and backgrounds on startup