1 Changes in version 0.2.2.1-alpha - 2009-0?-??
3 - Add support for dynamic OpenSSL hardware crypto acceleration engines
4 via new AccelName and AccelDir options.
6 o New options for gathering stats safely:
7 - Directories that configure with --enable-dirreq-stats and set
8 "DirReqStatistics 1" write directory request stats to disk every
9 24 hours. As compared to the --enable-geoip-stats flag in 0.2.1.x,
10 there are a few improvements: 1) stats are written to disk exactly
11 every 24 hours; 2) estimated shares of v2 and v3 requests are
12 determined as mean values, not at the end of a measurement period;
13 3) unresolved requests are listed with country code '??';
14 4) directories also measure download times.
15 - Exit nodes that configure with --enable-exit-stats and set
16 "ExitPortStatistics 1" write statistics on the number of exit
17 streams and transferred bytes per port to disk every 24 hours.
18 - Relays that configure with --enable-buffer-stats and set
19 "CellStatistics 1" write statistics to disk every 24 hours on how
20 long cells spend in their circuit queues.
21 - Entry nodes that configure with --enable-entry-stats and set
22 "EntryStatistics 1" write statistics to disk every 24 hours on
23 the rough number and origins of connecting clients.
26 - New --digests command-line switch to output the digests of the
27 source files Tor was built with.
28 - The "torify" script now uses torsocks where available.
29 - The memarea code now uses a sentinel value at the end of each area
30 to make sure nothing writes beyond the end of an area. This might
31 help debug some conceivable causes of bug 930.
32 - Time and memory units in the configuration file can now be set to
33 fractional units. For example, "2.5 MB" is now a valid value for
35 - Certain Tor clients (such as those behind check.torproject.org) may
36 want to fetch the consensus in an extra early manner. To enable this
37 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
38 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
39 as only certain clients who must have this information sooner should
42 o Deprecated and removed features:
43 - The controller no longer accepts the old obsolete "addr-mappings/"
44 or "unregistered-servers-" GETINFO values.
45 - Hidden services no longer publish version 0 descriptors, and clients
46 do not request or use version 0 descriptors. However, the authorities
47 still accept and serve version 0 descriptors when contacted by older
48 hidden services/clients.
49 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
50 always on; using them is necessary for correct forward-compatible
52 - Removal of support for .noconnect style addresses.
55 Changes in version 0.2.1.20 - 2009-??-??
57 - Send circuit or stream sendme cells when our window has decreased
58 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
59 by Karsten when testing the "reduce circuit window" performance
60 patch. Bugfix on the 54th commit on Tor -- from July 2002,
61 before the release of Tor 0.0.0. This is the new winner of the
64 o New directory authorities:
65 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
69 - Fix a signed/unsigned compile warning in 0.2.1.19.
70 - Fix possible segmentation fault on directory authorities. Bugfix on
74 Changes in version 0.2.1.19 - 2009-07-28
75 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
76 services on Tor 0.2.1.3-alpha through 0.2.1.18.
79 - Make accessing hidden services on 0.2.1.x work right again.
80 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
81 part of patch provided by "optimist".
84 - When a relay/bridge is writing out its identity key fingerprint to
85 the "fingerprint" file and to its logs, write it without spaces. Now
86 it will look like the fingerprints in our bridges documentation,
87 and confuse fewer users.
90 - Relays no longer publish a new server descriptor if they change
91 their MaxAdvertisedBandwidth config option but it doesn't end up
92 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
93 fixes bug 1026. Patch from Sebastian.
94 - Avoid leaking memory every time we get a create cell but we have
95 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
96 fixes bug 1034. Reported by BarkerJr.
99 Changes in version 0.2.1.18 - 2009-07-24
100 Tor 0.2.1.18 lays the foundations for performance improvements,
101 adds status events to help users diagnose bootstrap problems, adds
102 optional authentication/authorization for hidden services, fixes a
103 variety of potential anonymity problems, and includes a huge pile of
104 other features and bug fixes.
107 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
110 Changes in version 0.2.1.17-rc - 2009-07-07
111 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
112 candidate for the 0.2.1.x series. It lays the groundwork for further
113 client performance improvements, and also fixes a big bug with directory
114 authorities that were causing them to assign Guard and Stable flags
117 The Windows bundles also finally include the geoip database that we
118 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
119 should actually install Torbutton rather than giving you a cryptic
120 failure message (oops).
123 - Clients now use the bandwidth values in the consensus, rather than
124 the bandwidth values in each relay descriptor. This approach opens
125 the door to more accurate bandwidth estimates once the directory
126 authorities start doing active measurements. Implements more of
130 - When Tor clients restart after 1-5 days, they discard all their
131 cached descriptors as too old, but they still use the cached
132 consensus document. This approach is good for robustness, but
133 bad for performance: since they don't know any bandwidths, they
134 end up choosing at random rather than weighting their choice by
135 speed. Fixed by the above feature of putting bandwidths in the
136 consensus. Bugfix on 0.2.0.x.
137 - Directory authorities were neglecting to mark relays down in their
138 internal histories if the relays fall off the routerlist without
139 ever being found unreachable. So there were relays in the histories
140 that haven't been seen for eight months, and are listed as being
141 up for eight months. This wreaked havoc on the "median wfu"
142 and "median mtbf" calculations, in turn making Guard and Stable
143 flags very wrong, hurting network performance. Fixes bugs 696 and
144 969. Bugfix on 0.2.0.6-alpha.
147 - Serve the DirPortFrontPage page even when we have been approaching
148 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
149 - The control port would close the connection before flushing long
150 replies, such as the network consensus, if a QUIT command was issued
151 before the reply had completed. Now, the control port flushes all
152 pending replies before closing the connection. Also fixed a spurious
153 warning when a QUIT command is issued after a malformed or rejected
154 AUTHENTICATE command, but before the connection was closed. Patch
155 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
156 - When we can't find an intro key for a v2 hidden service descriptor,
157 fall back to the v0 hidden service descriptor and log a bug message.
158 Workaround for bug 1024.
159 - Fix a log message that did not respect the SafeLogging option.
163 - If we're a relay and we change our IP address, be more verbose
164 about the reason that made us change. Should help track down
165 further bugs for relays on dynamic IP addresses.
168 Changes in version 0.2.1.16-rc - 2009-06-20
169 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
170 a bunch of minor bugs.
173 - Fix an edge case where a malicious exit relay could convince a
174 controller that the client's DNS question resolves to an internal IP
175 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
177 o Major performance improvements (on 0.2.0.x):
178 - Disable and refactor some debugging checks that forced a linear scan
179 over the whole server-side DNS cache. These accounted for over 50%
180 of CPU time on a relatively busy exit node's gprof profile. Found
182 - Disable some debugging checks that appeared in exit node profile
186 - Update to the "June 3 2009" ip-to-country file.
187 - Do not have tor-resolve automatically refuse all .onion addresses;
188 if AutomapHostsOnResolve is set in your torrc, this will work fine.
190 o Minor bugfixes (on 0.2.0.x):
191 - Log correct error messages for DNS-related network errors on
193 - Fix a race condition that could cause crashes or memory corruption
194 when running as a server with a controller listening for log
196 - Avoid crashing when we have a policy specified in a DirPolicy or
197 SocksPolicy or ReachableAddresses option with ports set on it,
198 and we re-load the policy. May fix bug 996.
199 - Hidden service clients didn't use a cached service descriptor that
200 was older than 15 minutes, but wouldn't fetch a new one either,
201 because there was already one in the cache. Now, fetch a v2
202 descriptor unless the same descriptor was added to the cache within
203 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
205 o Minor bugfixes (on 0.2.1.x):
206 - Don't warn users about low port and hibernation mix when they
207 provide a *ListenAddress directive to fix that. Bugfix on
209 - When switching back and forth between bridge mode, do not start
210 gathering GeoIP data until two hours have passed.
211 - Do not complain that the user has requested an excluded node as
212 an exit when the node is not really an exit. This could happen
213 because the circuit was for testing, or an introduction point.
217 Changes in version 0.2.1.15-rc - 2009-05-25
218 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
219 series. It fixes a major bug on fast exit relays, as well as a variety
222 o Major bugfixes (on 0.2.0.x):
223 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
224 that would occur on some exit nodes when DNS failures and timeouts
225 occurred in certain patterns. Fix for bug 957.
227 o Minor bugfixes (on 0.2.0.x):
228 - Actually return -1 in the error case for read_bandwidth_usage().
229 Harmless bug, since we currently don't care about the return value
230 anywhere. Bugfix on 0.2.0.9-alpha.
231 - Provide a more useful log message if bug 977 (related to buffer
232 freelists) ever reappears, and do not crash right away.
233 - Fix an assertion failure on 64-bit platforms when we allocated
234 memory right up to the end of a memarea, then realigned the memory
235 one step beyond the end. Fixes a possible cause of bug 930.
236 - Protect the count of open sockets with a mutex, so we can't
237 corrupt it when two threads are closing or opening sockets at once.
238 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
239 - Don't allow a bridge to publish its router descriptor to a
240 non-bridge directory authority. Fixes part of bug 932.
241 - When we change to or from being a bridge, reset our counts of
242 client usage by country. Fixes bug 932.
243 - Fix a bug that made stream bandwidth get misreported to the
245 - Stop using malloc_usable_size() to use more area than we had
246 actually allocated: it was safe, but made valgrind really unhappy.
247 - Fix a memory leak when v3 directory authorities load their keys
248 and cert from disk. Bugfix on 0.2.0.1-alpha.
250 o Minor bugfixes (on 0.2.1.x):
251 - Fix use of freed memory when deciding to mark a non-addable
252 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
255 Changes in version 0.2.1.14-rc - 2009-04-12
256 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
257 series. It begins fixing some major performance problems, and also
258 finally addresses the bug that was causing relays on dynamic IP
259 addresses to fall out of the directory.
262 - Clients replace entry guards that were chosen more than a few months
263 ago. This change should significantly improve client performance,
264 especially once more people upgrade, since relays that have been
265 a guard for a long time are currently overloaded.
267 o Major bugfixes (on 0.2.0):
268 - Finally fix the bug where dynamic-IP relays disappear when their
269 IP address changes: directory mirrors were mistakenly telling
270 them their old address if they asked via begin_dir, so they
271 never got an accurate answer about their new address, so they
272 just vanished after a day. For belt-and-suspenders, relays that
273 don't set Address in their config now avoid using begin_dir for
274 all direct connections. Should fix bugs 827, 883, and 900.
275 - Relays were falling out of the networkstatus consensus for
276 part of a day if they changed their local config but the
277 authorities discarded their new descriptor as "not sufficiently
278 different". Now directory authorities accept a descriptor as changed
279 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
281 - Avoid crashing in the presence of certain malformed descriptors.
282 Found by lark, and by automated fuzzing.
285 - When generating circuit events with verbose nicknames for
286 controllers, try harder to look up nicknames for routers on a
287 circuit. (Previously, we would look in the router descriptors we had
288 for nicknames, but not in the consensus.) Partial fix for bug 941.
289 - If the bridge config line doesn't specify a port, assume 443.
290 This makes bridge lines a bit smaller and easier for users to
292 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
293 bytes (aka 20KB/s), to match our documentation. Also update
294 directory authorities so they always assign the Fast flag to relays
295 with 20KB/s of capacity. Now people running relays won't suddenly
296 find themselves not seeing any use, if the network gets faster
298 - Update to the "April 3 2009" ip-to-country file.
301 - Avoid trying to print raw memory to the logs when we decide to
302 give up on downloading a given relay descriptor. Bugfix on
304 - In tor-resolve, when the Tor client to use is specified by
305 <hostname>:<port>, actually use the specified port rather than
306 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
307 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
308 - When starting with a cache over a few days old, do not leak
309 memory for the obsolete router descriptors in it. Bugfix on
311 - Avoid double-free on list of successfully uploaded hidden
312 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
313 - Change memarea_strndup() implementation to work even when
314 duplicating a string at the end of a page. This bug was
315 harmless for now, but could have meant crashes later. Fix by
316 lark. Bugfix on 0.2.1.1-alpha.
317 - Limit uploaded directory documents to be 16M rather than 500K.
318 The directory authorities were refusing v3 consensus votes from
319 other authorities, since the votes are now 504K. Fixes bug 959;
320 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
321 - Directory authorities should never send a 503 "busy" response to
322 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
326 Changes in version 0.2.1.13-alpha - 2009-03-09
327 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
328 cleanups. We're finally getting close to a release candidate.
331 - Correctly update the list of which countries we exclude as
332 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
333 lark. Bugfix on 0.2.1.6-alpha.
335 o Minor bugfixes (on 0.2.0.x and earlier):
336 - Automatically detect MacOSX versions earlier than 10.4.0, and
337 disable kqueue from inside Tor when running with these versions.
338 We previously did this from the startup script, but that was no
339 help to people who didn't use the startup script. Resolves bug 863.
340 - When we had picked an exit node for a connection, but marked it as
341 "optional", and it turned out we had no onion key for the exit,
342 stop wanting that exit and try again. This situation may not
343 be possible now, but will probably become feasible with proposal
344 158. Spotted by rovv. Fixes another case of bug 752.
345 - Clients no longer cache certificates for authorities they do not
346 recognize. Bugfix on 0.2.0.9-alpha.
347 - When we can't transmit a DNS request due to a network error, retry
348 it after a while, and eventually transmit a failing response to
349 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
350 - If the controller claimed responsibility for a stream, but that
351 stream never finished making its connection, it would live
352 forever in circuit_wait state. Now we close it after SocksTimeout
353 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
354 - Drop begin cells to a hidden service if they come from the middle
355 of a circuit. Patch from lark.
356 - When we erroneously receive two EXTEND cells for the same circuit
357 ID on the same connection, drop the second. Patch from lark.
358 - Fix a crash that occurs on exit nodes when a nameserver request
359 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
360 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
362 - Do not assume that a stack-allocated character array will be
363 64-bit aligned on platforms that demand that uint64_t access is
364 aligned. Possible fix for bug 604.
365 - Parse dates and IPv4 addresses in a locale- and libc-independent
366 manner, to avoid platform-dependent behavior on malformed input.
367 - Build correctly when configured to build outside the main source
368 path. Patch from Michael Gold.
369 - We were already rejecting relay begin cells with destination port
370 of 0. Now also reject extend cells with destination port or address
371 of 0. Suggested by lark.
373 o Minor bugfixes (on 0.2.1.x):
374 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
375 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
376 - If we're an exit node, scrub the IP address to which we are exiting
377 in the logs. Bugfix on 0.2.1.8-alpha.
380 - On Linux, use the prctl call to re-enable core dumps when the user
382 - New controller event NEWCONSENSUS that lists the networkstatus
383 lines for every recommended relay. Now controllers like Torflow
384 can keep up-to-date on which relays they should be using.
385 - Update to the "February 26 2009" ip-to-country file.
388 Changes in version 0.2.0.34 - 2009-02-08
389 Tor 0.2.0.34 features several more security-related fixes. You should
390 upgrade, especially if you run an exit relay (remote crash) or a
391 directory authority (remote infinite loop), or you're on an older
392 (pre-XP) or not-recently-patched Windows (remote exploit).
394 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
395 have many known flaws, and nobody should be using them. You should
396 upgrade. If you're using a Linux or BSD and its packages are obsolete,
397 stop using those packages and upgrade anyway.
400 - Fix an infinite-loop bug on handling corrupt votes under certain
401 circumstances. Bugfix on 0.2.0.8-alpha.
402 - Fix a temporary DoS vulnerability that could be performed by
403 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
404 - Avoid a potential crash on exit nodes when processing malformed
405 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
406 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
407 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
410 - Fix compilation on systems where time_t is a 64-bit integer.
411 Patch from Matthias Drochner.
412 - Don't consider expiring already-closed client connections. Fixes
413 bug 893. Bugfix on 0.0.2pre20.
416 Changes in version 0.2.1.12-alpha - 2009-02-08
417 Tor 0.2.1.12-alpha features several more security-related fixes. You
418 should upgrade, especially if you run an exit relay (remote crash) or
419 a directory authority (remote infinite loop), or you're on an older
420 (pre-XP) or not-recently-patched Windows (remote exploit). It also
421 includes a big pile of minor bugfixes and cleanups.
424 - Fix an infinite-loop bug on handling corrupt votes under certain
425 circumstances. Bugfix on 0.2.0.8-alpha.
426 - Fix a temporary DoS vulnerability that could be performed by
427 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
428 - Avoid a potential crash on exit nodes when processing malformed
429 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
432 - Let controllers actually ask for the "clients_seen" event for
433 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
434 reported by Matt Edman.
435 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
437 - Fix a bug in address parsing that was preventing bridges or hidden
438 service targets from being at IPv6 addresses.
439 - Solve a bug that kept hardware crypto acceleration from getting
440 enabled when accounting was turned on. Fixes bug 907. Bugfix on
442 - Remove a bash-ism from configure.in to build properly on non-Linux
443 platforms. Bugfix on 0.2.1.1-alpha.
444 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
445 headers. Bugfix on 0.2.0.10-alpha.
446 - Don't consider expiring already-closed client connections. Fixes
447 bug 893. Bugfix on 0.0.2pre20.
448 - Fix another interesting corner-case of bug 891 spotted by rovv:
449 Previously, if two hosts had different amounts of clock drift, and
450 one of them created a new connection with just the wrong timing,
451 the other might decide to deprecate the new connection erroneously.
452 Bugfix on 0.1.1.13-alpha.
453 - Resolve a very rare crash bug that could occur when the user forced
454 a nameserver reconfiguration during the middle of a nameserver
455 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
456 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
457 Bugfix on 0.2.1.7-alpha.
458 - If we're using bridges and our network goes away, be more willing
459 to forgive our bridges and try again when we get an application
460 request. Bugfix on 0.2.0.x.
463 - Support platforms where time_t is 64 bits long. (Congratulations,
464 NetBSD!) Patch from Matthias Drochner.
465 - Add a 'getinfo status/clients-seen' controller command, in case
466 controllers want to hear clients_seen events but connect late.
469 - Disable GCC's strict alias optimization by default, to avoid the
470 likelihood of its introducing subtle bugs whenever our code violates
471 the letter of C99's alias rules.
474 Changes in version 0.2.0.33 - 2009-01-21
475 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
476 useful to users. It also finally fixes a bug where a relay or client
477 that's been off for many days would take a long time to bootstrap.
479 This update also fixes an important security-related bug reported by
480 Ilja van Sprundel. You should upgrade. (We'll send out more details
481 about the bug once people have had some time to upgrade.)
484 - Fix a heap-corruption bug that may be remotely triggerable on
485 some platforms. Reported by Ilja van Sprundel.
488 - When a stream at an exit relay is in state "resolving" or
489 "connecting" and it receives an "end" relay cell, the exit relay
490 would silently ignore the end cell and not close the stream. If
491 the client never closes the circuit, then the exit relay never
492 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
494 - When sending CREATED cells back for a given circuit, use a 64-bit
495 connection ID to find the right connection, rather than an addr:port
496 combination. Now that we can have multiple OR connections between
497 the same ORs, it is no longer possible to use addr:port to uniquely
498 identify a connection.
499 - Bridge relays that had DirPort set to 0 would stop fetching
500 descriptors shortly after startup, and then briefly resume
501 after a new bandwidth test and/or after publishing a new bridge
502 descriptor. Bridge users that try to bootstrap from them would
503 get a recent networkstatus but would get descriptors from up to
504 18 hours earlier, meaning most of the descriptors were obsolete
505 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
506 - Prevent bridge relays from serving their 'extrainfo' document
507 to anybody who asks, now that extrainfo docs include potentially
508 sensitive aggregated client geoip summaries. Bugfix on
510 - If the cached networkstatus consensus is more than five days old,
511 discard it rather than trying to use it. In theory it could be
512 useful because it lists alternate directory mirrors, but in practice
513 it just means we spend many minutes trying directory mirrors that
514 are long gone from the network. Also discard router descriptors as
515 we load them if they are more than five days old, since the onion
516 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
519 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
520 could make gcc generate non-functional binary search code. Bugfix
522 - Build correctly on platforms without socklen_t.
523 - Compile without warnings on solaris.
524 - Avoid potential crash on internal error during signature collection.
525 Fixes bug 864. Patch from rovv.
526 - Correct handling of possible malformed authority signing key
527 certificates with internal signature types. Fixes bug 880.
528 Bugfix on 0.2.0.3-alpha.
529 - Fix a hard-to-trigger resource leak when logging credential status.
531 - When we can't initialize DNS because the network is down, do not
532 automatically stop Tor from starting. Instead, we retry failed
533 dns_init() every 10 minutes, and change the exit policy to reject
534 *:* until one succeeds. Fixes bug 691.
535 - Use 64 bits instead of 32 bits for connection identifiers used with
536 the controller protocol, to greatly reduce risk of identifier reuse.
537 - When we're choosing an exit node for a circuit, and we have
538 no pending streams, choose a good general exit rather than one that
539 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
540 - Fix another case of assuming, when a specific exit is requested,
541 that we know more than the user about what hosts it allows.
542 Fixes one case of bug 752. Patch from rovv.
543 - Clip the MaxCircuitDirtiness config option to a minimum of 10
544 seconds. Warn the user if lower values are given in the
545 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
546 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
547 user if lower values are given in the configuration. Bugfix on
548 0.1.1.17-rc. Patch by Sebastian.
549 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
550 the cache because we already had a v0 descriptor with the same ID.
551 Bugfix on 0.2.0.18-alpha.
552 - Fix a race condition when freeing keys shared between main thread
553 and CPU workers that could result in a memory leak. Bugfix on
554 0.1.0.1-rc. Fixes bug 889.
555 - Send a valid END cell back when a client tries to connect to a
556 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
557 840. Patch from rovv.
558 - Check which hops rendezvous stream cells are associated with to
559 prevent possible guess-the-streamid injection attacks from
560 intermediate hops. Fixes another case of bug 446. Based on patch
562 - If a broken client asks a non-exit router to connect somewhere,
563 do not even do the DNS lookup before rejecting the connection.
564 Fixes another case of bug 619. Patch from rovv.
565 - When a relay gets a create cell it can't decrypt (e.g. because it's
566 using the wrong onion key), we were dropping it and letting the
567 client time out. Now actually answer with a destroy cell. Fixes
568 bug 904. Bugfix on 0.0.2pre8.
570 o Minor bugfixes (hidden services):
571 - Do not throw away existing introduction points on SIGHUP. Bugfix on
572 0.0.6pre1. Patch by Karsten. Fixes bug 874.
575 - Report the case where all signatures in a detached set are rejected
576 differently than the case where there is an error handling the
578 - When we realize that another process has modified our cached
579 descriptors, print out a more useful error message rather than
580 triggering an assertion. Fixes bug 885. Patch from Karsten.
581 - Implement the 0x20 hack to better resist DNS poisoning: set the
582 case on outgoing DNS requests randomly, and reject responses that do
583 not match the case correctly. This logic can be disabled with the
584 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
585 of servers that do not reliably preserve case in replies. See
586 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
588 - Check DNS replies for more matching fields to better resist DNS
590 - Never use OpenSSL compression: it wastes RAM and CPU trying to
591 compress cells, which are basically all encrypted, compressed, or
595 Changes in version 0.2.1.11-alpha - 2009-01-20
596 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
597 week it will take a long time to bootstrap again" bug. It also fixes
598 an important security-related bug reported by Ilja van Sprundel. You
599 should upgrade. (We'll send out more details about the bug once people
600 have had some time to upgrade.)
603 - Fix a heap-corruption bug that may be remotely triggerable on
604 some platforms. Reported by Ilja van Sprundel.
607 - Discard router descriptors as we load them if they are more than
608 five days old. Otherwise if Tor is off for a long time and then
609 starts with cached descriptors, it will try to use the onion
610 keys in those obsolete descriptors when building circuits. Bugfix
611 on 0.2.0.x. Fixes bug 887.
614 - Try to make sure that the version of Libevent we're running with
615 is binary-compatible with the one we built with. May address bug
617 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
618 for bug 905. Bugfix on 0.2.1.7-alpha.
619 - Add a new --enable-local-appdata configuration switch to change
620 the default location of the datadir on win32 from APPDATA to
621 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
622 entirely. Patch from coderman.
625 - Make outbound DNS packets respect the OutboundBindAddress setting.
626 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
627 - When our circuit fails at the first hop (e.g. we get a destroy
628 cell back), avoid using that OR connection anymore, and also
629 tell all the one-hop directory requests waiting for it that they
630 should fail. Bugfix on 0.2.1.3-alpha.
631 - In the torify(1) manpage, mention that tsocks will leak your
635 Changes in version 0.2.1.10-alpha - 2009-01-06
636 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
637 would make the bridge relay not so useful if it had DirPort set to 0,
638 and one that could let an attacker learn a little bit of information
639 about the bridge's users), and a bug that would cause your Tor relay
640 to ignore a circuit create request it can't decrypt (rather than reply
641 with an error). It also fixes a wide variety of other bugs.
644 - If the cached networkstatus consensus is more than five days old,
645 discard it rather than trying to use it. In theory it could
646 be useful because it lists alternate directory mirrors, but in
647 practice it just means we spend many minutes trying directory
648 mirrors that are long gone from the network. Helps bug 887 a bit;
650 - Bridge relays that had DirPort set to 0 would stop fetching
651 descriptors shortly after startup, and then briefly resume
652 after a new bandwidth test and/or after publishing a new bridge
653 descriptor. Bridge users that try to bootstrap from them would
654 get a recent networkstatus but would get descriptors from up to
655 18 hours earlier, meaning most of the descriptors were obsolete
656 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
657 - Prevent bridge relays from serving their 'extrainfo' document
658 to anybody who asks, now that extrainfo docs include potentially
659 sensitive aggregated client geoip summaries. Bugfix on
663 - New controller event "clients_seen" to report a geoip-based summary
664 of which countries we've seen clients from recently. Now controllers
665 like Vidalia can show bridge operators that they're actually making
667 - Build correctly against versions of OpenSSL 0.9.8 or later built
668 without support for deprecated functions.
669 - Update to the "December 19 2008" ip-to-country file.
671 o Minor bugfixes (on 0.2.0.x):
672 - Authorities now vote for the Stable flag for any router whose
673 weighted MTBF is at least 5 days, regardless of the mean MTBF.
674 - Do not remove routers as too old if we do not have any consensus
675 document. Bugfix on 0.2.0.7-alpha.
676 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
677 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
678 - When an exit relay resolves a stream address to a local IP address,
679 do not just keep retrying that same exit relay over and
680 over. Instead, just close the stream. Addresses bug 872. Bugfix
681 on 0.2.0.32. Patch from rovv.
682 - If a hidden service sends us an END cell, do not consider
683 retrying the connection; just close it. Patch from rovv.
684 - When we made bridge authorities stop serving bridge descriptors over
685 unencrypted links, we also broke DirPort reachability testing for
686 bridges. So bridges with a non-zero DirPort were printing spurious
687 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
688 - When a relay gets a create cell it can't decrypt (e.g. because it's
689 using the wrong onion key), we were dropping it and letting the
690 client time out. Now actually answer with a destroy cell. Fixes
691 bug 904. Bugfix on 0.0.2pre8.
692 - Squeeze 2-5% out of client performance (according to oprofile) by
693 improving the implementation of some policy-manipulation functions.
695 o Minor bugfixes (on 0.2.1.x):
696 - Make get_interface_address() function work properly again; stop
697 guessing the wrong parts of our address as our address.
698 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
699 send on that circuit. Otherwise we might violate the proposal-110
700 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
702 - When we're sending non-EXTEND cells to the first hop in a circuit,
703 for example to use an encrypted directory connection, we don't need
704 to use RELAY_EARLY cells: the first hop knows what kind of cell
705 it is, and nobody else can even see the cell type. Conserving
706 RELAY_EARLY cells makes it easier to cannibalize circuits like
708 - Stop logging nameserver addresses in reverse order.
709 - If we are retrying a directory download slowly over and over, do
710 not automatically give up after the 254th failure. Bugfix on
712 - Resume reporting accurate "stream end" reasons to the local control
713 port. They were lost in the changes for Proposal 148. Bugfix on
716 o Deprecated and removed features:
717 - The old "tor --version --version" command, which would print out
718 the subversion "Id" of most of the source files, is now removed. It
719 turned out to be less useful than we'd expected, and harder to
722 o Code simplifications and refactoring:
723 - Change our header file guard macros to be less likely to conflict
724 with system headers. Adam Langley noticed that we were conflicting
725 with log.h on Android.
726 - Tool-assisted documentation cleanup. Nearly every function or
727 static variable in Tor should have its own documentation now.
730 Changes in version 0.2.1.9-alpha - 2008-12-25
731 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
733 o New directory authorities:
734 - gabelmoo (the authority run by Karsten Loesing) now has a new
738 - Never use a connection with a mismatched address to extend a
739 circuit, unless that connection is canonical. A canonical
740 connection is one whose address is authenticated by the router's
741 identity key, either in a NETINFO cell or in a router descriptor.
742 - Avoid a possible memory corruption bug when receiving hidden service
743 descriptors. Bugfix on 0.2.1.6-alpha.
746 - Fix a logic error that would automatically reject all but the first
747 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
748 part of bug 813/868. Bug spotted by coderman.
749 - When a stream at an exit relay is in state "resolving" or
750 "connecting" and it receives an "end" relay cell, the exit relay
751 would silently ignore the end cell and not close the stream. If
752 the client never closes the circuit, then the exit relay never
753 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
755 - When we can't initialize DNS because the network is down, do not
756 automatically stop Tor from starting. Instead, retry failed
757 dns_init() every 10 minutes, and change the exit policy to reject
758 *:* until one succeeds. Fixes bug 691.
761 - Give a better error message when an overzealous init script says
762 "sudo -u username tor --user username". Makes Bug 882 easier for
764 - When a directory authority gives us a new guess for our IP address,
765 log which authority we used. Hopefully this will help us debug
766 the recent complaints about bad IP address guesses.
767 - Detect svn revision properly when we're using git-svn.
768 - Try not to open more than one descriptor-downloading connection
769 to an authority at once. This should reduce load on directory
770 authorities. Fixes bug 366.
771 - Add cross-certification to newly generated certificates, so that
772 a signing key is enough information to look up a certificate.
773 Partial implementation of proposal 157.
774 - Start serving certificates by <identity digest, signing key digest>
775 pairs. Partial implementation of proposal 157.
776 - Clients now never report any stream end reason except 'MISC'.
777 Implements proposal 148.
778 - On platforms with a maximum syslog string length, truncate syslog
779 messages to that length ourselves, rather than relying on the
780 system to do it for us.
781 - Optimize out calls to time(NULL) that occur for every IO operation,
782 or for every cell. On systems where time() is a slow syscall,
783 this fix will be slightly helpful.
784 - Exit servers can now answer resolve requests for ip6.arpa addresses.
785 - When we download a descriptor that we then immediately (as
786 a directory authority) reject, do not retry downloading it right
787 away. Should save some bandwidth on authorities. Fix for bug
788 888. Patch by Sebastian Hahn.
789 - When a download gets us zero good descriptors, do not notify
790 Tor that new directory information has arrived.
791 - Avoid some nasty corner cases in the logic for marking connections
792 as too old or obsolete or noncanonical for circuits. Partial
795 o Minor features (controller):
796 - New CONSENSUS_ARRIVED event to note when a new consensus has
797 been fetched and validated.
798 - When we realize that another process has modified our cached
799 descriptors file, print out a more useful error message rather
800 than triggering an assertion. Fixes bug 885. Patch from Karsten.
801 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
802 controllers to prevent SIGHUP from reloading the
803 configuration. Fixes bug 856.
806 - Resume using the correct "REASON=" stream when telling the
807 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
808 - When a canonical connection appears later in our internal list
809 than a noncanonical one for a given OR ID, always use the
810 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
812 - Clip the MaxCircuitDirtiness config option to a minimum of 10
813 seconds. Warn the user if lower values are given in the
814 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
815 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
816 user if lower values are given in the configuration. Bugfix on
817 0.1.1.17-rc. Patch by Sebastian.
818 - Fix a race condition when freeing keys shared between main thread
819 and CPU workers that could result in a memory leak. Bugfix on
820 0.1.0.1-rc. Fixes bug 889.
822 o Minor bugfixes (hidden services):
823 - Do not throw away existing introduction points on SIGHUP (bugfix on
824 0.0.6pre1); also, do not stall hidden services because we're
825 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
826 by John Brooks. Patch by Karsten. Fixes bug 874.
827 - Fix a memory leak when we decline to add a v2 rendezvous
828 descriptor to the cache because we already had a v0 descriptor
829 with the same ID. Bugfix on 0.2.0.18-alpha.
831 o Deprecated and removed features:
832 - RedirectExits has been removed. It was deprecated since
834 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
835 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
836 - Cell pools are now always enabled; --disable-cell-pools is ignored.
838 o Code simplifications and refactoring:
839 - Rename the confusing or_is_obsolete field to the more appropriate
840 is_bad_for_new_circs, and move it to or_connection_t where it
842 - Move edge-only flags from connection_t to edge_connection_t: not
843 only is this better coding, but on machines of plausible alignment,
844 it should save 4-8 bytes per connection_t. "Every little bit helps."
845 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
846 for consistency; keep old option working for backward compatibility.
847 - Simplify the code for finding connections to use for a circuit.
850 Changes in version 0.2.1.8-alpha - 2008-12-08
851 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
852 builds better on unusual platforms like Solaris and old OS X, and
853 fixes a variety of other issues.
856 - New DirPortFrontPage option that takes an html file and publishes
857 it as "/" on the DirPort. Now relay operators can provide a
858 disclaimer without needing to set up a separate webserver. There's
859 a sample disclaimer in contrib/tor-exit-notice.html.
862 - When the client is choosing entry guards, now it selects at most
863 one guard from a given relay family. Otherwise we could end up with
864 all of our entry points into the network run by the same operator.
865 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
868 - Fix a DOS opportunity during the voting signature collection process
869 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
870 - Fix a possible segfault when establishing an exit connection. Bugfix
874 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
876 - Made Tor a little less aggressive about deleting expired
877 certificates. Partial fix for bug 854.
878 - Stop doing unaligned memory access that generated bus errors on
879 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
880 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
881 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
882 - Make USR2 log-level switch take effect immediately. Bugfix on
884 - If one win32 nameserver fails to get added, continue adding the
885 rest, and don't automatically fail.
886 - Use fcntl() for locking when flock() is not available. Should fix
887 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
888 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
889 could make gcc generate non-functional binary search code. Bugfix
891 - Build correctly on platforms without socklen_t.
892 - Avoid potential crash on internal error during signature collection.
893 Fixes bug 864. Patch from rovv.
894 - Do not use C's stdio library for writing to log files. This will
895 improve logging performance by a minute amount, and will stop
896 leaking fds when our disk is full. Fixes bug 861.
897 - Stop erroneous use of O_APPEND in cases where we did not in fact
898 want to re-seek to the end of a file before every last write().
899 - Correct handling of possible malformed authority signing key
900 certificates with internal signature types. Fixes bug 880. Bugfix
902 - Fix a hard-to-trigger resource leak when logging credential status.
906 - Directory mirrors no longer fetch the v1 directory or
907 running-routers files. They are obsolete, and nobody asks for them
908 anymore. This is the first step to making v1 authorities obsolete.
910 o Minor features (controller):
911 - Return circuit purposes in response to GETINFO circuit-status. Fixes
915 Changes in version 0.2.0.32 - 2008-11-20
916 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
917 packages (and maybe other packages) noticed by Theo de Raadt, fixes
918 a smaller security flaw that might allow an attacker to access local
919 services, further improves hidden service performance, and fixes a
920 variety of other issues.
923 - The "User" and "Group" config options did not clear the
924 supplementary group entries for the Tor process. The "User" option
925 is now more robust, and we now set the groups to the specified
926 user's primary group. The "Group" option is now ignored. For more
927 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
928 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
929 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
930 - The "ClientDNSRejectInternalAddresses" config option wasn't being
931 consistently obeyed: if an exit relay refuses a stream because its
932 exit policy doesn't allow it, we would remember what IP address
933 the relay said the destination address resolves to, even if it's
934 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
937 - Fix a DOS opportunity during the voting signature collection process
938 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
940 o Major bugfixes (hidden services):
941 - When fetching v0 and v2 rendezvous service descriptors in parallel,
942 we were failing the whole hidden service request when the v0
943 descriptor fetch fails, even if the v2 fetch is still pending and
944 might succeed. Similarly, if the last v2 fetch fails, we were
945 failing the whole hidden service request even if a v0 fetch is
946 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
947 - When extending a circuit to a hidden service directory to upload a
948 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
949 requests failed, because the router descriptor has not been
950 downloaded yet. In these cases, do not attempt to upload the
951 rendezvous descriptor, but wait until the router descriptor is
952 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
953 descriptor from a hidden service directory for which the router
954 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
958 - Fix several infrequent memory leaks spotted by Coverity.
959 - When testing for libevent functions, set the LDFLAGS variable
960 correctly. Found by Riastradh.
961 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
962 bootstrapping with tunneled directory connections. Bugfix on
963 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
964 - When asked to connect to A.B.exit:80, if we don't know the IP for A
965 and we know that server B rejects most-but-not all connections to
966 port 80, we would previously reject the connection. Now, we assume
967 the user knows what they were asking for. Fixes bug 752. Bugfix
968 on 0.0.9rc5. Diagnosed by BarkerJr.
969 - If we overrun our per-second write limits a little, count this as
970 having used up our write allocation for the second, and choke
971 outgoing directory writes. Previously, we had only counted this when
972 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
973 Bugfix on 0.2.0.x (??).
974 - Remove the old v2 directory authority 'lefkada' from the default
975 list. It has been gone for many months.
976 - Stop doing unaligned memory access that generated bus errors on
977 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
978 - Make USR2 log-level switch take effect immediately. Bugfix on
981 o Minor bugfixes (controller):
982 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
983 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
986 Changes in version 0.2.1.7-alpha - 2008-11-08
987 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
988 packages (and maybe other packages) noticed by Theo de Raadt, fixes
989 a smaller security flaw that might allow an attacker to access local
990 services, adds better defense against DNS poisoning attacks on exit
991 relays, further improves hidden service performance, and fixes a
992 variety of other issues.
995 - The "ClientDNSRejectInternalAddresses" config option wasn't being
996 consistently obeyed: if an exit relay refuses a stream because its
997 exit policy doesn't allow it, we would remember what IP address
998 the relay said the destination address resolves to, even if it's
999 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
1000 - The "User" and "Group" config options did not clear the
1001 supplementary group entries for the Tor process. The "User" option
1002 is now more robust, and we now set the groups to the specified
1003 user's primary group. The "Group" option is now ignored. For more
1004 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
1005 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
1006 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
1007 - Do not use or believe expired v3 authority certificates. Patch
1008 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
1011 - Now NodeFamily and MyFamily config options allow spaces in
1012 identity fingerprints, so it's easier to paste them in.
1013 Suggested by Lucky Green.
1014 - Implement the 0x20 hack to better resist DNS poisoning: set the
1015 case on outgoing DNS requests randomly, and reject responses that do
1016 not match the case correctly. This logic can be disabled with the
1017 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
1018 of servers that do not reliably preserve case in replies. See
1019 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
1021 - Preserve case in replies to DNSPort requests in order to support
1022 the 0x20 hack for resisting DNS poisoning attacks.
1024 o Hidden service performance improvements:
1025 - When the client launches an introduction circuit, retry with a
1026 new circuit after 30 seconds rather than 60 seconds.
1027 - Launch a second client-side introduction circuit in parallel
1028 after a delay of 15 seconds (based on work by Christian Wilms).
1029 - Hidden services start out building five intro circuits rather
1030 than three, and when the first three finish they publish a service
1031 descriptor using those. Now we publish our service descriptor much
1032 faster after restart.
1035 - Minor fix in the warning messages when you're having problems
1036 bootstrapping; also, be more forgiving of bootstrap problems when
1037 we're still making incremental progress on a given bootstrap phase.
1038 - When we're choosing an exit node for a circuit, and we have
1039 no pending streams, choose a good general exit rather than one that
1040 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
1041 - Send a valid END cell back when a client tries to connect to a
1042 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
1043 840. Patch from rovv.
1044 - If a broken client asks a non-exit router to connect somewhere,
1045 do not even do the DNS lookup before rejecting the connection.
1046 Fixes another case of bug 619. Patch from rovv.
1047 - Fix another case of assuming, when a specific exit is requested,
1048 that we know more than the user about what hosts it allows.
1049 Fixes another case of bug 752. Patch from rovv.
1050 - Check which hops rendezvous stream cells are associated with to
1051 prevent possible guess-the-streamid injection attacks from
1052 intermediate hops. Fixes another case of bug 446. Based on patch
1054 - Avoid using a negative right-shift when comparing 32-bit
1055 addresses. Possible fix for bug 845 and bug 811.
1056 - Make the assert_circuit_ok() function work correctly on circuits that
1057 have already been marked for close.
1058 - Fix read-off-the-end-of-string error in unit tests when decoding
1059 introduction points.
1060 - Fix uninitialized size field for memory area allocation: may improve
1061 memory performance during directory parsing.
1062 - Treat duplicate certificate fetches as failures, so that we do
1063 not try to re-fetch an expired certificate over and over and over.
1064 - Do not say we're fetching a certificate when we'll in fact skip it
1065 because of a pending download.
1068 Changes in version 0.2.1.6-alpha - 2008-09-30
1069 Tor 0.2.1.6-alpha further improves performance and robustness of
1070 hidden services, starts work on supporting per-country relay selection,
1071 and fixes a variety of smaller issues.
1074 - Implement proposal 121: make it possible to build hidden services
1075 that only certain clients are allowed to connect to. This is
1076 enforced at several points, so that unauthorized clients are unable
1077 to send INTRODUCE cells to the service, or even (depending on the
1078 type of authentication) to learn introduction points. This feature
1079 raises the bar for certain kinds of active attacks against hidden
1080 services. Code by Karsten Loesing.
1081 - Relays now store and serve v2 hidden service descriptors by default,
1082 i.e., the new default value for HidServDirectoryV2 is 1. This is
1083 the last step in proposal 114, which aims to make hidden service
1084 lookups more reliable.
1085 - Start work to allow node restrictions to include country codes. The
1086 syntax to exclude nodes in a country with country code XX is
1087 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
1088 refinement to decide what config options should take priority if
1089 you ask to both use a particular node and exclude it.
1090 - Allow ExitNodes list to include IP ranges and country codes, just
1091 like the Exclude*Nodes lists. Patch from Robert Hogan.
1094 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
1095 Tor to fail to start if you had it configured to use a bridge
1096 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
1097 - When extending a circuit to a hidden service directory to upload a
1098 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
1099 requests failed, because the router descriptor had not been
1100 downloaded yet. In these cases, we now wait until the router
1101 descriptor is downloaded, and then retry. Likewise, clients
1102 now skip over a hidden service directory if they don't yet have
1103 its router descriptor, rather than futilely requesting it and
1104 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
1106 - When fetching v0 and v2 rendezvous service descriptors in parallel,
1107 we were failing the whole hidden service request when the v0
1108 descriptor fetch fails, even if the v2 fetch is still pending and
1109 might succeed. Similarly, if the last v2 fetch fails, we were
1110 failing the whole hidden service request even if a v0 fetch is
1111 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
1112 - DNS replies need to have names matching their requests, but
1113 these names should be in the questions section, not necessarily
1114 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
1117 - Update to the "September 1 2008" ip-to-country file.
1118 - Allow ports 465 and 587 in the default exit policy again. We had
1119 rejected them in 0.1.0.15, because back in 2005 they were commonly
1120 misconfigured and ended up as spam targets. We hear they are better
1121 locked down these days.
1122 - Use a lockfile to make sure that two Tor processes are not
1123 simultaneously running with the same datadir.
1124 - Serve the latest v3 networkstatus consensus via the control
1125 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
1126 - Better logging about stability/reliability calculations on directory
1128 - Drop the requirement to have an open dir port for storing and
1129 serving v2 hidden service descriptors.
1130 - Directory authorities now serve a /tor/dbg-stability.txt URL to
1131 help debug WFU and MTBF calculations.
1132 - Implement most of Proposal 152: allow specialized servers to permit
1133 single-hop circuits, and clients to use those servers to build
1134 single-hop circuits when using a specialized controller. Patch
1135 from Josh Albrecht. Resolves feature request 768.
1136 - Add a -p option to tor-resolve for specifying the SOCKS port: some
1137 people find host:port too confusing.
1138 - Make TrackHostExit mappings expire a while after their last use, not
1139 after their creation. Patch from Robert Hogan.
1140 - Provide circuit purposes along with circuit events to the controller.
1143 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
1145 - Fixed some memory leaks -- some quite frequent, some almost
1146 impossible to trigger -- based on results from Coverity.
1147 - When testing for libevent functions, set the LDFLAGS variable
1148 correctly. Found by Riastradh.
1149 - Fix an assertion bug in parsing policy-related options; possible fix
1151 - Catch and report a few more bootstrapping failure cases when Tor
1152 fails to establish a TCP connection. Cleanup on 0.2.1.x.
1153 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
1154 bootstrapping with tunneled directory connections. Bugfix on
1155 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
1156 - When asked to connect to A.B.exit:80, if we don't know the IP for A
1157 and we know that server B rejects most-but-not all connections to
1158 port 80, we would previously reject the connection. Now, we assume
1159 the user knows what they were asking for. Fixes bug 752. Bugfix
1160 on 0.0.9rc5. Diagnosed by BarkerJr.
1161 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
1162 service directories if they have no advertised dir port. Bugfix
1164 - If we overrun our per-second write limits a little, count this as
1165 having used up our write allocation for the second, and choke
1166 outgoing directory writes. Previously, we had only counted this when
1167 we had met our limits precisely. Fixes bug 824. Patch by rovv.
1168 Bugfix on 0.2.0.x (??).
1169 - Avoid a "0 divided by 0" calculation when calculating router uptime
1170 at directory authorities. Bugfix on 0.2.0.8-alpha.
1171 - Make DNS resolved controller events into "CLOSED", not
1172 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
1174 - Fix a bug where an unreachable relay would establish enough
1175 reachability testing circuits to do a bandwidth test -- if
1176 we already have a connection to the middle hop of the testing
1177 circuit, then it could establish the last hop by using the existing
1178 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
1179 circuits no longer use entry guards in 0.2.1.3-alpha.
1180 - If we have correct permissions on $datadir, we complain to stdout
1181 and fail to start. But dangerous permissions on
1182 $datadir/cached-status/ would cause us to open a log and complain
1183 there. Now complain to stdout and fail to start in both cases. Fixes
1184 bug 820, reported by seeess.
1185 - Remove the old v2 directory authority 'lefkada' from the default
1186 list. It has been gone for many months.
1188 o Code simplifications and refactoring:
1189 - Revise the connection_new functions so that a more typesafe variant
1190 exists. This will work better with Coverity, and let us find any
1191 actual mistakes we're making here.
1192 - Refactor unit testing logic so that dmalloc can be used sensibly
1193 with unit tests to check for memory leaks.
1194 - Move all hidden-service related fields from connection and circuit
1195 structure to substructures: this way they won't eat so much memory.
1198 Changes in version 0.2.0.31 - 2008-09-03
1199 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
1200 a big bug we're seeing where in rare cases traffic from one Tor stream
1201 gets mixed into another stream, and fixes a variety of smaller issues.
1204 - Make sure that two circuits can never exist on the same connection
1205 with the same circuit ID, even if one is marked for close. This
1206 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
1207 - Relays now reject risky extend cells: if the extend cell includes
1208 a digest of all zeroes, or asks to extend back to the relay that
1209 sent the extend cell, tear down the circuit. Ideas suggested
1211 - If not enough of our entry guards are available so we add a new
1212 one, we might use the new one even if it overlapped with the
1213 current circuit's exit relay (or its family). Anonymity bugfix
1214 pointed out by rovv.
1217 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
1218 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
1219 - Correctly detect the presence of the linux/netfilter_ipv4.h header
1220 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
1221 - Pick size of default geoip filename string correctly on windows.
1222 Fixes bug 806. Bugfix on 0.2.0.30.
1223 - Make the autoconf script accept the obsolete --with-ssl-dir
1224 option as an alias for the actually-working --with-openssl-dir
1225 option. Fix the help documentation to recommend --with-openssl-dir.
1226 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
1227 - When using the TransPort option on OpenBSD, and using the User
1228 option to change UID and drop privileges, make sure to open
1229 /dev/pf before dropping privileges. Fixes bug 782. Patch from
1230 Christopher Davis. Bugfix on 0.1.2.1-alpha.
1231 - Try to attach connections immediately upon receiving a RENDEZVOUS2
1232 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
1233 on the client side when connecting to a hidden service. Bugfix
1234 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
1235 - When closing an application-side connection because its circuit is
1236 getting torn down, generate the stream event correctly. Bugfix on
1237 0.1.2.x. Anonymous patch.
1240 Changes in version 0.2.1.5-alpha - 2008-08-31
1241 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
1242 in a lot of the infrastructure for adding authorization to hidden
1243 services, lays the groundwork for having clients read their load
1244 balancing information out of the networkstatus consensus rather than
1245 the individual router descriptors, addresses two potential anonymity
1246 issues, and fixes a variety of smaller issues.
1249 - Convert many internal address representations to optionally hold
1251 - Generate and accept IPv6 addresses in many protocol elements.
1252 - Make resolver code handle nameservers located at ipv6 addresses.
1253 - Begin implementation of proposal 121 ("Client authorization for
1254 hidden services"): configure hidden services with client
1255 authorization, publish descriptors for them, and configure
1256 authorization data for hidden services at clients. The next
1257 step is to actually access hidden services that perform client
1259 - More progress toward proposal 141: Network status consensus
1260 documents and votes now contain bandwidth information for each
1261 router and a summary of that router's exit policy. Eventually this
1262 will be used by clients so that they do not have to download every
1263 known descriptor before building circuits.
1265 o Major bugfixes (on 0.2.0.x and before):
1266 - When sending CREATED cells back for a given circuit, use a 64-bit
1267 connection ID to find the right connection, rather than an addr:port
1268 combination. Now that we can have multiple OR connections between
1269 the same ORs, it is no longer possible to use addr:port to uniquely
1270 identify a connection.
1271 - Relays now reject risky extend cells: if the extend cell includes
1272 a digest of all zeroes, or asks to extend back to the relay that
1273 sent the extend cell, tear down the circuit. Ideas suggested
1275 - If not enough of our entry guards are available so we add a new
1276 one, we might use the new one even if it overlapped with the
1277 current circuit's exit relay (or its family). Anonymity bugfix
1278 pointed out by rovv.
1281 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
1282 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
1283 - When using the TransPort option on OpenBSD, and using the User
1284 option to change UID and drop privileges, make sure to open /dev/pf
1285 before dropping privileges. Fixes bug 782. Patch from Christopher
1286 Davis. Bugfix on 0.1.2.1-alpha.
1287 - Correctly detect the presence of the linux/netfilter_ipv4.h header
1288 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
1289 - Add a missing safe_str() call for a debug log message.
1290 - Use 64 bits instead of 32 bits for connection identifiers used with
1291 the controller protocol, to greatly reduce risk of identifier reuse.
1292 - Make the autoconf script accept the obsolete --with-ssl-dir
1293 option as an alias for the actually-working --with-openssl-dir
1294 option. Fix the help documentation to recommend --with-openssl-dir.
1295 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
1298 - Rate-limit too-many-sockets messages: when they happen, they happen
1299 a lot. Resolves bug 748.
1300 - Resist DNS poisoning a little better by making sure that names in
1301 answer sections match.
1302 - Print the SOCKS5 error message string as well as the error code
1303 when a tor-resolve request fails. Patch from Jacob.
1306 Changes in version 0.2.1.4-alpha - 2008-08-04
1307 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
1310 - The address part of exit policies was not correctly written
1311 to router descriptors. This generated router descriptors that failed
1312 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
1314 - Tor triggered a false assert when extending a circuit to a relay
1315 but we already have a connection open to that relay. Noticed by
1316 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
1319 - Fix a hidden service logging bug: in some edge cases, the router
1320 descriptor of a previously picked introduction point becomes
1321 obsolete and we need to give up on it rather than continually
1322 complaining that it has become obsolete. Observed by xiando. Bugfix
1326 - Take out the TestVia config option, since it was a workaround for
1327 a bug that was fixed in Tor 0.1.1.21.
1330 Changes in version 0.2.1.3-alpha - 2008-08-03
1331 Tor 0.2.1.3-alpha implements most of the pieces to prevent
1332 infinite-length circuit attacks (see proposal 110); fixes a bug that
1333 might cause exit relays to corrupt streams they send back; allows
1334 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
1335 ExcludeExitNodes config options; and fixes a big pile of bugs.
1337 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
1338 - Send a bootstrap problem "warn" event on the first problem if the
1339 reason is NO_ROUTE (that is, our network is down).
1342 - Implement most of proposal 110: The first K cells to be sent
1343 along a circuit are marked as special "early" cells; only K "early"
1344 cells will be allowed. Once this code is universal, we can block
1345 certain kinds of DOS attack by requiring that EXTEND commands must
1346 be sent using an "early" cell.
1349 - Try to attach connections immediately upon receiving a RENDEZVOUS2
1350 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
1351 on the client side when connecting to a hidden service. Bugfix
1352 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
1353 - Ensure that two circuits can never exist on the same connection
1354 with the same circuit ID, even if one is marked for close. This
1355 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
1358 - When relays do their initial bandwidth measurement, don't limit
1359 to just our entry guards for the test circuits. Otherwise we tend
1360 to have multiple test circuits going through a single entry guard,
1361 which makes our bandwidth test less accurate. Fixes part of bug 654;
1362 patch contributed by Josh Albrecht.
1363 - Add an ExcludeExitNodes option so users can list a set of nodes
1364 that should be be excluded from the exit node position, but
1365 allowed elsewhere. Implements proposal 151.
1366 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
1367 ExcludeNodes and ExcludeExitNodes lists.
1368 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
1369 be more efficient. Formerly it was quadratic in the number of
1370 servers; now it should be linear. Fixes bug 509.
1371 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
1372 and n_conn_id_digest fields into a separate structure that's
1373 only needed when the circuit has not yet attached to an n_conn.
1376 - Change the contrib/tor.logrotate script so it makes the new
1377 logs as "_tor:_tor" rather than the default, which is generally
1378 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
1379 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
1380 warnings (occasionally), but it can also cause the compiler to
1381 eliminate error-checking code. Suggested by Peter Gutmann.
1382 - When a hidden service is giving up on an introduction point candidate
1383 that was not included in the last published rendezvous descriptor,
1384 don't reschedule publication of the next descriptor. Fixes bug 763.
1386 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
1387 HiddenServiceExcludeNodes as obsolete: they never worked properly,
1388 and nobody claims to be using them. Fixes bug 754. Bugfix on
1389 0.1.0.1-rc. Patch from Christian Wilms.
1390 - Fix a small alignment and memory-wasting bug on buffer chunks.
1393 o Minor bugfixes (controller):
1394 - When closing an application-side connection because its circuit
1395 is getting torn down, generate the stream event correctly.
1396 Bugfix on 0.1.2.x. Anonymous patch.
1399 - Remove all backward-compatibility code to support relays running
1400 versions of Tor so old that they no longer work at all on the
1404 Changes in version 0.2.0.30 - 2008-07-15
1406 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
1407 warnings (occasionally), but it can also cause the compiler to
1408 eliminate error-checking code. Suggested by Peter Gutmann.
1411 Changes in version 0.2.0.29-rc - 2008-07-08
1412 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
1413 hidden-service performance bugs, and fixes a bunch of smaller bugs.
1416 - If you have more than one bridge but don't know their keys,
1417 you would only launch a request for the descriptor of the first one
1418 on your list. (Tor considered launching requests for the others, but
1419 found that it already had a connection on the way for $0000...0000
1420 so it didn't open another.) Bugfix on 0.2.0.x.
1421 - If you have more than one bridge but don't know their keys, and the
1422 connection to one of the bridges failed, you would cancel all
1423 pending bridge connections. (After all, they all have the same
1424 digest.) Bugfix on 0.2.0.x.
1425 - When a hidden service was trying to establish an introduction point,
1426 and Tor had built circuits preemptively for such purposes, we
1427 were ignoring all the preemptive circuits and launching a new one
1428 instead. Bugfix on 0.2.0.14-alpha.
1429 - When a hidden service was trying to establish an introduction point,
1430 and Tor *did* manage to reuse one of the preemptively built
1431 circuits, it didn't correctly remember which one it used,
1432 so it asked for another one soon after, until there were no
1433 more preemptive circuits, at which point it launched one from
1434 scratch. Bugfix on 0.0.9.x.
1435 - Make directory servers include the X-Your-Address-Is: http header in
1436 their responses even for begin_dir conns. Now clients who only
1437 ever use begin_dir connections still have a way to learn their IP
1438 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
1441 - Fix a macro/CPP interaction that was confusing some compilers:
1442 some GCCs don't like #if/#endif pairs inside macro arguments.
1444 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
1445 Fixes bug 704; fix from Steven Murdoch.
1446 - When opening /dev/null in finish_daemonize(), do not pass the
1447 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
1448 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
1449 - Correctly detect transparent proxy support on Linux hosts that
1450 require in.h to be included before netfilter_ipv4.h. Patch
1452 - Disallow session resumption attempts during the renegotiation
1453 stage of the v2 handshake protocol. Clients should never be trying
1454 session resumption at this point, but apparently some did, in
1455 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
1456 found by Geoff Goodell.
1459 Changes in version 0.2.1.2-alpha - 2008-06-20
1460 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
1461 make it easier to set up your own private Tor network; fixes several
1462 big bugs with using more than one bridge relay; fixes a big bug with
1463 offering hidden services quickly after Tor starts; and uses a better
1464 API for reporting potential bootstrapping problems to the controller.
1467 - New TestingTorNetwork config option to allow adjustment of
1468 previously constant values that, while reasonable, could slow
1469 bootstrapping. Implements proposal 135. Patch from Karsten.
1472 - If you have more than one bridge but don't know their digests,
1473 you would only learn a request for the descriptor of the first one
1474 on your list. (Tor considered launching requests for the others, but
1475 found that it already had a connection on the way for $0000...0000
1476 so it didn't open another.) Bugfix on 0.2.0.x.
1477 - If you have more than one bridge but don't know their digests,
1478 and the connection to one of the bridges failed, you would cancel
1479 all pending bridge connections. (After all, they all have the
1480 same digest.) Bugfix on 0.2.0.x.
1481 - When establishing a hidden service, introduction points that
1482 originate from cannibalized circuits are completely ignored and not
1483 included in rendezvous service descriptors. This might be another
1484 reason for delay in making a hidden service available. Bugfix
1485 from long ago (0.0.9.x?)
1488 - Allow OpenSSL to use dynamic locks if it wants.
1489 - When building a consensus, do not include routers that are down.
1490 This will cut down 30% to 40% on consensus size. Implements
1492 - In directory authorities' approved-routers files, allow
1493 fingerprints with or without space.
1494 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
1495 controller can query our current bootstrap state in case it attaches
1496 partway through and wants to catch up.
1497 - Send an initial "Starting" bootstrap status event, so we have a
1498 state to start out in.
1501 - Asking for a conditional consensus at .../consensus/<fingerprints>
1502 would crash a dirserver if it did not already have a
1503 consensus. Bugfix on 0.2.1.1-alpha.
1504 - Clean up some macro/CPP interactions: some GCC versions don't like
1505 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
1508 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
1509 - Directory authorities shouldn't complain about bootstrapping
1510 problems just because they do a lot of reachability testing and
1511 some of the connection attempts fail.
1512 - Start sending "count" and "recommendation" key/value pairs in
1513 bootstrap problem status events, so the controller can hear about
1514 problems even before Tor decides they're worth reporting for sure.
1515 - If you're using bridges, generate "bootstrap problem" warnings
1516 as soon as you run out of working bridges, rather than waiting
1517 for ten failures -- which will never happen if you have less than
1519 - If we close our OR connection because there's been a circuit
1520 pending on it for too long, we were telling our bootstrap status
1521 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
1524 Changes in version 0.2.1.1-alpha - 2008-06-13
1525 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
1526 were making the Tor process bloat especially on Linux; makes our TLS
1527 handshake blend in better; sends "bootstrap phase" status events to
1528 the controller, so it can keep the user informed of progress (and
1529 problems) fetching directory information and establishing circuits;
1530 and adds a variety of smaller features.
1533 - More work on making our TLS handshake blend in: modify the list
1534 of ciphers advertised by OpenSSL in client mode to even more
1535 closely resemble a common web browser. We cheat a little so that
1536 we can advertise ciphers that the locally installed OpenSSL doesn't
1538 - Start sending "bootstrap phase" status events to the controller,
1539 so it can keep the user informed of progress fetching directory
1540 information and establishing circuits. Also inform the controller
1541 if we think we're stuck at a particular bootstrap phase. Implements
1543 - Resume using OpenSSL's RAND_poll() for better (and more portable)
1544 cross-platform entropy collection again. We used to use it, then
1545 stopped using it because of a bug that could crash systems that
1546 called RAND_poll when they had a lot of fds open. It looks like the
1547 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
1548 at startup, and to call RAND_poll() when we reseed later only if
1549 we have a non-buggy OpenSSL version.
1552 - When we choose to abandon a new entry guard because we think our
1553 older ones might be better, close any circuits pending on that
1554 new entry guard connection. This fix should make us recover much
1555 faster when our network is down and then comes back. Bugfix on
1556 0.1.2.8-beta; found by lodger.
1558 o Memory fixes and improvements:
1559 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
1560 to avoid unused RAM in buffer chunks and memory pools.
1561 - Speed up parsing and cut down on memory fragmentation by using
1562 stack-style allocations for parsing directory objects. Previously,
1563 this accounted for over 40% of allocations from within Tor's code
1564 on a typical directory cache.
1565 - Use a Bloom filter rather than a digest-based set to track which
1566 descriptors we need to keep around when we're cleaning out old
1567 router descriptors. This speeds up the computation significantly,
1568 and may reduce fragmentation.
1569 - Reduce the default smartlist size from 32 to 16; it turns out that
1570 most smartlists hold around 8-12 elements tops.
1571 - Make dumpstats() log the fullness and size of openssl-internal
1573 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
1574 patch to their OpenSSL, turn it on to save memory on servers. This
1575 patch will (with any luck) get included in a mainline distribution
1577 - Never use OpenSSL compression: it wastes RAM and CPU trying to
1578 compress cells, which are basically all encrypted, compressed,
1582 - Stop reloading the router list from disk for no reason when we
1583 run out of reachable directory mirrors. Once upon a time reloading
1584 it would set the 'is_running' flag back to 1 for them. It hasn't
1585 done that for a long time.
1586 - In very rare situations new hidden service descriptors were
1587 published earlier than 30 seconds after the last change to the
1588 service. (We currently think that a hidden service descriptor
1589 that's been stable for 30 seconds is worth publishing.)
1592 - Allow separate log levels to be configured for different logging
1593 domains. For example, this allows one to log all notices, warnings,
1594 or errors, plus all memory management messages of level debug or
1595 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
1596 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
1597 and stop using a warning that had become unfixably verbose under
1599 - New --hush command-line option similar to --quiet. While --quiet
1600 disables all logging to the console on startup, --hush limits the
1601 output to messages of warning and error severity.
1602 - Servers support a new URL scheme for consensus downloads that
1603 allows the client to specify which authorities are trusted.
1604 The server then only sends the consensus if the client will trust
1605 it. Otherwise a 404 error is sent back. Clients use this
1606 new scheme when the server supports it (meaning it's running
1607 0.2.1.1-alpha or later). Implements proposal 134.
1608 - New configure/torrc options (--enable-geoip-stats,
1609 DirRecordUsageByCountry) to record how many IPs we've served
1610 directory info to in each country code, how many status documents
1611 total we've sent to each country code, and what share of the total
1612 directory requests we should expect to see.
1613 - Use the TLS1 hostname extension to more closely resemble browser
1615 - Lots of new unit tests.
1616 - Add a macro to implement the common pattern of iterating through
1617 two parallel lists in lockstep.
1620 Changes in version 0.2.0.28-rc - 2008-06-13
1621 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
1622 performance bug, and fixes a bunch of smaller bugs.
1625 - Fix a bug where, when we were choosing the 'end stream reason' to
1626 put in our relay end cell that we send to the exit relay, Tor
1627 clients on Windows were sometimes sending the wrong 'reason'. The
1628 anonymity problem is that exit relays may be able to guess whether
1629 the client is running Windows, thus helping partition the anonymity
1630 set. Down the road we should stop sending reasons to exit relays,
1631 or otherwise prevent future versions of this bug.
1634 - While setting up a hidden service, some valid introduction circuits
1635 were overlooked and abandoned. This might be the reason for
1636 the long delay in making a hidden service available. Bugfix on
1640 - Update to the "June 9 2008" ip-to-country file.
1641 - Run 'make test' as part of 'make dist', so we stop releasing so
1642 many development snapshots that fail their unit tests.
1645 - When we're checking if we have enough dir info for each relay
1646 to begin establishing circuits, make sure that we actually have
1647 the descriptor listed in the consensus, not just any descriptor.
1649 - Bridge relays no longer print "xx=0" in their extrainfo document
1650 for every single country code in the geoip db. Bugfix on
1652 - Only warn when we fail to load the geoip file if we were planning to
1653 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
1654 - If we change our MaxAdvertisedBandwidth and then reload torrc,
1655 Tor won't realize it should publish a new relay descriptor. Fixes
1656 bug 688, reported by mfr. Bugfix on 0.1.2.x.
1657 - When we haven't had any application requests lately, don't bother
1658 logging that we have expired a bunch of descriptors. Bugfix
1660 - Make relay cells written on a connection count as non-padding when
1661 tracking how long a connection has been in use. Bugfix on
1662 0.2.0.1-alpha. Spotted by lodger.
1663 - Fix unit tests in 0.2.0.27-rc.
1664 - Fix compile on Windows.
1667 Changes in version 0.2.0.27-rc - 2008-06-03
1668 Tor 0.2.0.27-rc adds a few features we left out of the earlier
1669 release candidates. In particular, we now include an IP-to-country
1670 GeoIP database, so controllers can easily look up what country a
1671 given relay is in, and so bridge relays can give us some sanitized
1672 summaries about which countries are making use of bridges. (See proposal
1673 126-geoip-fetching.txt for details.)
1676 - Include an IP-to-country GeoIP file in the tarball, so bridge
1677 relays can report sanitized summaries of the usage they're seeing.
1680 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
1681 Robert Hogan. Fixes the first part of bug 681.
1682 - Make bridge authorities never serve extrainfo docs.
1683 - Add support to detect Libevent versions in the 1.4.x series
1685 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
1686 - Include a new contrib/tor-exit-notice.html file that exit relay
1687 operators can put on their website to help reduce abuse queries.
1690 - When tunneling an encrypted directory connection, and its first
1691 circuit fails, do not leave it unattached and ask the controller
1692 to deal. Fixes the second part of bug 681.
1693 - Make bridge authorities correctly expire old extrainfo documents
1697 Changes in version 0.2.0.26-rc - 2008-05-13
1698 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
1699 in Debian's OpenSSL packages. All users running any 0.2.0.x version
1700 should upgrade, whether they're running Debian or not.
1702 o Major security fixes:
1703 - Use new V3 directory authority keys on the tor26, gabelmoo, and
1704 moria1 V3 directory authorities. The old keys were generated with
1705 a vulnerable version of Debian's OpenSSL package, and must be
1706 considered compromised. Other authorities' keys were not generated
1707 with an affected version of OpenSSL.
1710 - List authority signatures as "unrecognized" based on DirServer
1711 lines, not on cert cache. Bugfix on 0.2.0.x.
1714 - Add a new V3AuthUseLegacyKey option to make it easier for
1715 authorities to change their identity keys if they have to.
1718 Changes in version 0.2.0.25-rc - 2008-04-23
1719 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
1722 - Remember to initialize threading before initializing logging.
1723 Otherwise, many BSD-family implementations will crash hard on
1724 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
1727 - Authorities correctly free policies on bad servers on
1728 exit. Fixes bug 672. Bugfix on 0.2.0.x.
1731 Changes in version 0.2.0.24-rc - 2008-04-22
1732 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
1733 v3 directory authority, makes relays with dynamic IP addresses and no
1734 DirPort notice more quickly when their IP address changes, fixes a few
1735 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
1737 o New directory authorities:
1738 - Take lefkada out of the list of v3 directory authorities, since
1739 it has been down for months.
1740 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
1744 - Detect address changes more quickly on non-directory mirror
1745 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
1747 o Minor features (security):
1748 - Reject requests for reverse-dns lookup of names that are in
1749 a private address space. Patch from lodger.
1750 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
1753 o Minor bugfixes (crashes):
1754 - Avoid a rare assert that can trigger when Tor doesn't have much
1755 directory information yet and it tries to fetch a v2 hidden
1756 service descriptor. Fixes bug 651, reported by nwf.
1757 - Initialize log mutex before initializing dmalloc. Otherwise,
1758 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
1759 - Use recursive pthread mutexes in order to avoid deadlock when
1760 logging debug-level messages to a controller. Bug spotted by nwf,
1761 bugfix on 0.2.0.16-alpha.
1763 o Minor bugfixes (resource management):
1764 - Keep address policies from leaking memory: start their refcount
1765 at 1, not 2. Bugfix on 0.2.0.16-alpha.
1766 - Free authority certificates on exit, so they don't look like memory
1767 leaks. Bugfix on 0.2.0.19-alpha.
1768 - Free static hashtables for policy maps and for TLS connections on
1769 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
1770 - Avoid allocating extra space when computing consensuses on 64-bit
1771 platforms. Bug spotted by aakova.
1773 o Minor bugfixes (misc):
1774 - Do not read the configuration file when we've only been told to
1775 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
1776 based on patch from Sebastian Hahn.
1777 - Exit relays that are used as a client can now reach themselves
1778 using the .exit notation, rather than just launching an infinite
1779 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
1780 - When attempting to open a logfile fails, tell us why.
1781 - Fix a dumb bug that was preventing us from knowing that we should
1782 preemptively build circuits to handle expected directory requests.
1783 Fixes bug 660. Bugfix on 0.1.2.x.
1784 - Warn less verbosely about clock skew from netinfo cells from
1785 untrusted sources. Fixes bug 663.
1786 - Make controller stream events for DNS requests more consistent,
1787 by adding "new stream" events for DNS requests, and removing
1788 spurious "stream closed" events" for cached reverse resolves.
1789 Patch from mwenge. Fixes bug 646.
1790 - Correctly notify one-hop connections when a circuit build has
1791 failed. Possible fix for bug 669. Found by lodger.
1794 Changes in version 0.2.0.23-rc - 2008-03-24
1795 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
1796 makes bootstrapping faster if the first directory mirror you contact
1797 is down. The bundles also include the new Vidalia 0.1.2 release.
1800 - When a tunneled directory request is made to a directory server
1801 that's down, notice after 30 seconds rather than 120 seconds. Also,
1802 fail any begindir streams that are pending on it, so they can
1803 retry elsewhere. This was causing multi-minute delays on bootstrap.
1806 Changes in version 0.2.0.22-rc - 2008-03-18
1807 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
1808 enables encrypted directory connections by default for non-relays, fixes
1809 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
1810 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
1813 - Enable encrypted directory connections by default for non-relays,
1814 so censor tools that block Tor directory connections based on their
1815 plaintext patterns will no longer work. This means Tor works in
1816 certain censored countries by default again.
1819 - Make sure servers always request certificates from clients during
1820 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
1821 - Do not enter a CPU-eating loop when a connection is closed in
1822 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
1823 diagnosed by lodger; bugfix on 0.2.0.20-rc.
1824 - Fix assertion failure that could occur when a blocked circuit
1825 became unblocked, and it had pending client DNS requests. Bugfix
1826 on 0.2.0.1-alpha. Fixes bug 632.
1828 o Minor bugfixes (on 0.1.2.x):
1829 - Generate "STATUS_SERVER" events rather than misspelled
1830 "STATUS_SEVER" events. Caught by mwenge.
1831 - When counting the number of bytes written on a TLS connection,
1832 look at the BIO actually used for writing to the network, not
1833 at the BIO used (sometimes) to buffer data for the network.
1834 Looking at different BIOs could result in write counts on the
1835 order of ULONG_MAX. Fixes bug 614.
1836 - On Windows, correctly detect errors when listing the contents of
1837 a directory. Fix from lodger.
1839 o Minor bugfixes (on 0.2.0.x):
1840 - Downgrade "sslv3 alert handshake failure" message to INFO.
1841 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
1842 left BandwidthRate and BandwidthBurst at the default, we would be
1843 silently limited by those defaults. Now raise them to match the
1844 RelayBandwidth* values.
1845 - Fix the SVK version detection logic to work correctly on a branch.
1846 - Make --enable-openbsd-malloc work correctly on Linux with alpha
1847 CPUs. Fixes bug 625.
1848 - Logging functions now check that the passed severity is sane.
1849 - Use proper log levels in the testsuite call of
1850 get_interface_address6().
1851 - When using a nonstandard malloc, do not use the platform values for
1852 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
1853 - Make the openbsd malloc code use 8k pages on alpha CPUs and
1855 - Detect mismatched page sizes when using --enable-openbsd-malloc.
1856 - Avoid double-marked-for-close warning when certain kinds of invalid
1857 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
1858 for bug 617. Bugfix on 0.2.0.1-alpha.
1859 - Make sure that the "NULL-means-reject *:*" convention is followed by
1860 all the policy manipulation functions, avoiding some possible crash
1861 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
1862 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
1863 actually works, and doesn't warn about every single reverse lookup.
1864 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
1867 - Only log guard node status when guard node status has changed.
1868 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
1869 make "INFO" 75% less verbose.
1872 Changes in version 0.2.0.21-rc - 2008-03-02
1873 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
1874 makes Tor work well with Vidalia again, fixes a rare assert bug,
1875 and fixes a pair of more minor bugs. The bundles also include Vidalia
1876 0.1.0 and Torbutton 1.1.16.
1879 - The control port should declare that it requires password auth
1880 when HashedControlSessionPassword is set too. Patch from Matt Edman;
1881 bugfix on 0.2.0.20-rc. Fixes bug 615.
1882 - Downgrade assert in connection_buckets_decrement() to a log message.
1883 This may help us solve bug 614, and in any case will make its
1884 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
1885 - We were sometimes miscounting the number of bytes read from the
1886 network, causing our rate limiting to not be followed exactly.
1887 Bugfix on 0.2.0.16-alpha. Reported by lodger.
1890 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
1891 OpenSSL versions should have been working fine. Diagnosis and patch
1892 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
1893 Bugfix on 0.2.0.20-rc.
1896 Changes in version 0.2.0.20-rc - 2008-02-24
1897 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
1898 makes more progress towards normalizing Tor's TLS handshake, makes
1899 hidden services work better again, helps relays bootstrap if they don't
1900 know their IP address, adds optional support for linking in openbsd's
1901 allocator or tcmalloc, allows really fast relays to scale past 15000
1902 sockets, and fixes a bunch of minor bugs reported by Veracode.
1905 - Enable the revised TLS handshake based on the one designed by
1906 Steven Murdoch in proposal 124, as revised in proposal 130. It
1907 includes version negotiation for OR connections as described in
1908 proposal 105. The new handshake is meant to be harder for censors
1909 to fingerprint, and it adds the ability to detect certain kinds of
1910 man-in-the-middle traffic analysis attacks. The version negotiation
1911 feature will allow us to improve Tor's link protocol more safely
1913 - Choose which bridge to use proportional to its advertised bandwidth,
1914 rather than uniformly at random. This should speed up Tor for
1915 bridge users. Also do this for people who set StrictEntryNodes.
1916 - When a TrackHostExits-chosen exit fails too many times in a row,
1917 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
1920 - Resolved problems with (re-)fetching hidden service descriptors.
1921 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
1923 - If we only ever used Tor for hidden service lookups or posts, we
1924 would stop building circuits and start refusing connections after
1925 24 hours, since we falsely believed that Tor was dormant. Reported
1926 by nwf; bugfix on 0.1.2.x.
1927 - Servers that don't know their own IP address should go to the
1928 authorities for their first directory fetch, even if their DirPort
1929 is off or if they don't know they're reachable yet. This will help
1930 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
1931 - When counting the number of open sockets, count not only the number
1932 of sockets we have received from the socket() call, but also
1933 the number we've gotten from accept() and socketpair(). This bug
1934 made us fail to count all sockets that we were using for incoming
1935 connections. Bugfix on 0.2.0.x.
1936 - Fix code used to find strings within buffers, when those strings
1937 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
1938 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
1939 - Add a new __HashedControlSessionPassword option for controllers
1940 to use for one-off session password hashes that shouldn't get
1941 saved to disk by SAVECONF --- Vidalia users were accumulating a
1942 pile of HashedControlPassword lines in their torrc files, one for
1943 each time they had restarted Tor and then clicked Save. Make Tor
1944 automatically convert "HashedControlPassword" to this new option but
1945 only when it's given on the command line. Partial fix for bug 586.
1947 o Minor features (performance):
1948 - Tune parameters for cell pool allocation to minimize amount of
1950 - Add OpenBSD malloc code from phk as an optional malloc
1951 replacement on Linux: some glibc libraries do very poorly
1952 with Tor's memory allocation patterns. Pass
1953 --enable-openbsd-malloc to get the replacement malloc code.
1954 - Add a --with-tcmalloc option to the configure script to link
1955 against tcmalloc (if present). Does not yet search for
1956 non-system include paths.
1957 - Stop imposing an arbitrary maximum on the number of file descriptors
1958 used for busy servers. Bug reported by Olaf Selke; patch from
1961 o Minor features (other):
1962 - When SafeLogging is disabled, log addresses along with all TLS
1964 - When building with --enable-gcc-warnings, check for whether Apple's
1965 warning "-Wshorten-64-to-32" is available.
1966 - Add a --passphrase-fd argument to the tor-gencert command for
1969 o Minor bugfixes (memory leaks and code problems):
1970 - We were leaking a file descriptor if Tor started with a zero-length
1971 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
1972 - Detect size overflow in zlib code. Reported by Justin Ferguson and
1974 - We were comparing the raw BridgePassword entry with a base64'ed
1975 version of it, when handling a "/tor/networkstatus-bridges"
1976 directory request. Now compare correctly. Noticed by Veracode.
1977 - Recover from bad tracked-since value in MTBF-history file.
1979 - Alter the code that tries to recover from unhandled write
1980 errors, to not try to flush onto a socket that's given us
1981 unhandled errors. Bugfix on 0.1.2.x.
1982 - Make Unix controlsockets work correctly on OpenBSD. Patch from
1983 tup. Bugfix on 0.2.0.3-alpha.
1985 o Minor bugfixes (other):
1986 - If we have an extra-info document for our server, always make
1987 it available on the control port, even if we haven't gotten
1988 a copy of it from an authority yet. Patch from mwenge.
1989 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
1990 - Directory mirrors no longer include a guess at the client's IP
1991 address if the connection appears to be coming from the same /24
1992 network; it was producing too many wrong guesses.
1993 - Make the new hidden service code respect the SafeLogging setting.
1994 Bugfix on 0.2.0.x. Patch from Karsten.
1995 - When starting as an authority, do not overwrite all certificates
1996 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
1997 - If we're trying to flush the last bytes on a connection (for
1998 example, when answering a directory request), reset the
1999 time-to-give-up timeout every time we manage to write something
2000 on the socket. Bugfix on 0.1.2.x.
2001 - Change the behavior of "getinfo status/good-server-descriptor"
2002 so it doesn't return failure when any authority disappears.
2003 - Even though the man page said that "TrackHostExits ." should
2004 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
2005 - Report TLS "zero return" case as a "clean close" and "IO error"
2006 as a "close". Stop calling closes "unexpected closes": existing
2007 Tors don't use SSL_close(), so having a connection close without
2008 the TLS shutdown handshake is hardly unexpected.
2009 - Send NAMESERVER_STATUS messages for a single failed nameserver
2012 o Code simplifications and refactoring:
2013 - Remove the tor_strpartition function: its logic was confused,
2014 and it was only used for one thing that could be implemented far
2018 Changes in version 0.2.0.19-alpha - 2008-02-09
2019 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
2020 handshake, makes path selection for relays more secure and IP address
2021 guessing more robust, and generally fixes a lot of bugs in preparation
2022 for calling the 0.2.0 branch stable.
2025 - Do not include recognizeable strings in the commonname part of
2026 Tor's x509 certificates.
2029 - If we're a relay, avoid picking ourselves as an introduction point,
2030 a rendezvous point, or as the final hop for internal circuits. Bug
2031 reported by taranis and lodger. Bugfix on 0.1.2.x.
2032 - Patch from "Andrew S. Lists" to catch when we contact a directory
2033 mirror at IP address X and he says we look like we're coming from
2034 IP address X. Bugfix on 0.1.2.x.
2036 o Minor features (security):
2037 - Be more paranoid about overwriting sensitive memory on free(),
2038 as a defensive programming tactic to ensure forward secrecy.
2040 o Minor features (directory authority):
2041 - Actually validate the options passed to AuthDirReject,
2042 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
2043 - Reject router descriptors with out-of-range bandwidthcapacity or
2044 bandwidthburst values.
2046 o Minor features (controller):
2047 - Reject controller commands over 1MB in length. This keeps rogue
2048 processes from running us out of memory.
2050 o Minor features (misc):
2051 - Give more descriptive well-formedness errors for out-of-range
2052 hidden service descriptor/protocol versions.
2053 - Make memory debugging information describe more about history
2054 of cell allocation, so we can help reduce our memory use.
2056 o Deprecated features (controller):
2057 - The status/version/num-versioning and status/version/num-concurring
2058 GETINFO options are no longer useful in the v3 directory protocol:
2059 treat them as deprecated, and warn when they're used.
2062 - When our consensus networkstatus has been expired for a while, stop
2063 being willing to build circuits using it. Fixes bug 401. Bugfix
2065 - Directory caches now fetch certificates from all authorities
2066 listed in a networkstatus consensus, even when they do not
2067 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
2068 - When connecting to a bridge without specifying its key, insert
2069 the connection into the identity-to-connection map as soon as
2070 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
2071 - Detect versions of OS X where malloc_good_size() is present in the
2072 library but never actually declared. Resolves bug 587. Bugfix
2074 - Stop incorrectly truncating zlib responses to directory authority
2075 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
2076 - Stop recommending that every server operator send mail to tor-ops.
2077 Resolves bug 597. Bugfix on 0.1.2.x.
2078 - Don't trigger an assert if we start a directory authority with a
2079 private IP address (like 127.0.0.1).
2080 - Avoid possible failures when generating a directory with routers
2081 with over-long versions strings, or too many flags set. Bugfix
2083 - If an attempt to launch a DNS resolve request over the control
2084 port fails because we have overrun the limit on the number of
2085 connections, tell the controller that the request has failed.
2086 - Avoid using too little bandwidth when our clock skips a few
2087 seconds. Bugfix on 0.1.2.x.
2088 - Fix shell error when warning about missing packages in configure
2089 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
2090 - Do not become confused when receiving a spurious VERSIONS-like
2091 cell from a confused v1 client. Bugfix on 0.2.0.x.
2092 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
2093 introduction points for a hidden service have failed. Patch from
2094 Karsten Loesing. Bugfix on 0.2.0.x.
2096 o Code simplifications and refactoring:
2097 - Remove some needless generality from cpuworker code, for improved
2099 - Stop overloading the circuit_t.onionskin field for both "onionskin
2100 from a CREATE cell that we are waiting for a cpuworker to be
2101 assigned" and "onionskin from an EXTEND cell that we are going to
2102 send to an OR as soon as we are connected". Might help with bug 600.
2103 - Add an in-place version of aes_crypt() so that we can avoid doing a
2104 needless memcpy() call on each cell payload.
2107 Changes in version 0.2.0.18-alpha - 2008-01-25
2108 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
2109 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
2110 that can warn or reject connections to ports generally associated with
2111 vulnerable-plaintext protocols.
2113 o New directory authorities:
2114 - Set up dannenberg (run by CCC) as the sixth v3 directory
2118 - Fix a major memory leak when attempting to use the v2 TLS
2119 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
2120 - We accidentally enabled the under-development v2 TLS handshake
2121 code, which was causing log entries like "TLS error while
2122 renegotiating handshake". Disable it again. Resolves bug 590.
2123 - We were computing the wrong Content-Length: header for directory
2124 responses that need to be compressed on the fly, causing clients
2125 asking for those items to always fail. Bugfix on 0.2.0.x; partially
2129 - Avoid going directly to the directory authorities even if you're a
2130 relay, if you haven't found yourself reachable yet or if you've
2131 decided not to advertise your dirport yet. Addresses bug 556.
2132 - If we've gone 12 hours since our last bandwidth check, and we
2133 estimate we have less than 50KB bandwidth capacity but we could
2134 handle more, do another bandwidth test.
2135 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
2136 Tor can warn and/or refuse connections to ports commonly used with
2137 vulnerable-plaintext protocols. Currently we warn on ports 23,
2138 109, 110, and 143, but we don't reject any.
2141 - When we setconf ClientOnly to 1, close any current OR and Dir
2142 listeners. Reported by mwenge.
2143 - When we get a consensus that's been signed by more people than
2144 we expect, don't log about it; it's not a big deal. Reported
2148 - Don't answer "/tor/networkstatus-bridges" directory requests if
2149 the request isn't encrypted.
2150 - Make "ClientOnly 1" config option disable directory ports too.
2151 - Patches from Karsten Loesing to make v2 hidden services more
2152 robust: work even when there aren't enough HSDir relays available;
2153 retry when a v2 rend desc fetch fails; but don't retry if we
2154 already have a usable v0 rend desc.
2157 Changes in version 0.2.0.17-alpha - 2008-01-17
2158 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
2161 - Make the tor-gencert man page get included correctly in the tarball.
2164 Changes in version 0.2.0.16-alpha - 2008-01-17
2165 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
2166 Loesing, and generally cleans up a lot of features and minor bugs.
2168 o New directory authorities:
2169 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
2172 o Major performance improvements:
2173 - Switch our old ring buffer implementation for one more like that
2174 used by free Unix kernels. The wasted space in a buffer with 1mb
2175 of data will now be more like 8k than 1mb. The new implementation
2176 also avoids realloc();realloc(); patterns that can contribute to
2177 memory fragmentation.
2180 - Configuration files now accept C-style strings as values. This
2181 helps encode characters not allowed in the current configuration
2182 file format, such as newline or #. Addresses bug 557.
2183 - Although we fixed bug 539 (where servers would send HTTP status 503
2184 responses _and_ send a body too), there are still servers out
2185 there that haven't upgraded. Therefore, make clients parse such
2186 bodies when they receive them.
2187 - When we're not serving v2 directory information, there is no reason
2188 to actually keep any around. Remove the obsolete files and directory
2189 on startup if they are very old and we aren't going to serve them.
2191 o Minor performance improvements:
2192 - Reference-count and share copies of address policy entries; only 5%
2193 of them were actually distinct.
2194 - Never walk through the list of logs if we know that no log is
2195 interested in a given message.
2198 - When an authority has not signed a consensus, do not try to
2199 download a nonexistent "certificate with key 00000000". Bugfix
2200 on 0.2.0.x. Fixes bug 569.
2201 - Fix a rare assert error when we're closing one of our threads:
2202 use a mutex to protect the list of logs, so we never write to the
2203 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
2204 bug 575, which is kind of the revenge of bug 222.
2205 - Patch from Karsten Loesing to complain less at both the client
2206 and the relay when a relay used to have the HSDir flag but doesn't
2207 anymore, and we try to upload a hidden service descriptor.
2208 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
2210 - Do not try to download missing certificates until we have tried
2211 to check our fallback consensus. Fixes bug 583.
2212 - Make bridges round reported GeoIP stats info up to the nearest
2213 estimate, not down. Now we can distinguish between "0 people from
2214 this country" and "1 person from this country".
2215 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
2216 - Avoid possible segfault if key generation fails in
2217 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
2218 - Avoid segfault in the case where a badly behaved v2 versioning
2219 directory sends a signed networkstatus with missing client-versions.
2221 - Avoid segfaults on certain complex invocations of
2222 router_get_by_hexdigest(). Bugfix on 0.1.2.
2223 - Correct bad index on array access in parse_http_time(). Bugfix
2225 - Fix possible bug in vote generation when server versions are present
2226 but client versions are not.
2227 - Fix rare bug on REDIRECTSTREAM control command when called with no
2228 port set: it could erroneously report an error when none had
2230 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
2231 compressing large objects and find ourselves with more than 4k
2232 left over. Bugfix on 0.2.0.
2233 - Fix a small memory leak when setting up a hidden service.
2234 - Fix a few memory leaks that could in theory happen under bizarre
2236 - Fix an assert if we post a general-purpose descriptor via the
2237 control port but that descriptor isn't mentioned in our current
2238 network consensus. Bug reported by Jon McLachlan; bugfix on
2241 o Minor features (controller):
2242 - Get NS events working again. Patch from tup.
2243 - The GETCONF command now escapes and quotes configuration values
2244 that don't otherwise fit into the torrc file.
2245 - The SETCONF command now handles quoted values correctly.
2247 o Minor features (directory authorities):
2248 - New configuration options to override default maximum number of
2249 servers allowed on a single IP address. This is important for
2250 running a test network on a single host.
2251 - Actually implement the -s option to tor-gencert.
2252 - Add a manual page for tor-gencert.
2254 o Minor features (bridges):
2255 - Bridge authorities no longer serve bridge descriptors over
2256 unencrypted connections.
2258 o Minor features (other):
2259 - Add hidden services and DNSPorts to the list of things that make
2260 Tor accept that it has running ports. Change starting Tor with no
2261 ports from a fatal error to a warning; we might change it back if
2262 this turns out to confuse anybody. Fixes bug 579.
2265 Changes in version 0.1.2.19 - 2008-01-17
2266 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
2267 exit policy a little bit more conservative so it's safer to run an
2268 exit relay on a home system, and fixes a variety of smaller issues.
2271 - Exit policies now reject connections that are addressed to a
2272 relay's public (external) IP address too, unless
2273 ExitPolicyRejectPrivate is turned off. We do this because too
2274 many relays are running nearby to services that trust them based
2278 - When the clock jumps forward a lot, do not allow the bandwidth
2279 buckets to become negative. Fixes bug 544.
2280 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
2281 on every successful resolve. Reported by Mike Perry.
2282 - Purge old entries from the "rephist" database and the hidden
2283 service descriptor database even when DirPort is zero.
2284 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
2285 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
2286 crashing or mis-answering these requests.
2287 - When we decide to send a 503 response to a request for servers, do
2288 not then also send the server descriptors: this defeats the whole
2289 purpose. Fixes bug 539.
2292 - Changing the ExitPolicyRejectPrivate setting should cause us to
2293 rebuild our server descriptor.
2294 - Fix handling of hex nicknames when answering controller requests for
2295 networkstatus by name, or when deciding whether to warn about
2296 unknown routers in a config option. (Patch from mwenge.)
2297 - Fix a couple of hard-to-trigger autoconf problems that could result
2298 in really weird results on platforms whose sys/types.h files define
2299 nonstandard integer types.
2300 - Don't try to create the datadir when running --verify-config or
2301 --hash-password. Resolves bug 540.
2302 - If we were having problems getting a particular descriptor from the
2303 directory caches, and then we learned about a new descriptor for
2304 that router, we weren't resetting our failure count. Reported
2306 - Although we fixed bug 539 (where servers would send HTTP status 503
2307 responses _and_ send a body too), there are still servers out there
2308 that haven't upgraded. Therefore, make clients parse such bodies
2309 when they receive them.
2310 - Run correctly on systems where rlim_t is larger than unsigned long.
2311 This includes some 64-bit systems.
2312 - Run correctly on platforms (like some versions of OS X 10.5) where
2313 the real limit for number of open files is OPEN_FILES, not rlim_max
2314 from getrlimit(RLIMIT_NOFILES).
2315 - Avoid a spurious free on base64 failure.
2316 - Avoid segfaults on certain complex invocations of
2317 router_get_by_hexdigest().
2318 - Fix rare bug on REDIRECTSTREAM control command when called with no
2319 port set: it could erroneously report an error when none had
2323 Changes in version 0.2.0.15-alpha - 2007-12-25
2324 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
2325 features added in 0.2.0.13-alpha.
2328 - Fix several remotely triggerable asserts based on DirPort requests
2329 for a v2 or v3 networkstatus object before we were prepared. This
2330 was particularly bad for 0.2.0.13 and later bridge relays, who
2331 would never have a v2 networkstatus and would thus always crash
2332 when used. Bugfixes on 0.2.0.x.
2333 - Estimate the v3 networkstatus size more accurately, rather than
2334 estimating it at zero bytes and giving it artificially high priority
2335 compared to other directory requests. Bugfix on 0.2.0.x.
2338 - Fix configure.in logic for cross-compilation.
2339 - When we load a bridge descriptor from the cache, and it was
2340 previously unreachable, mark it as retriable so we won't just
2341 ignore it. Also, try fetching a new copy immediately. Bugfixes
2343 - The bridge GeoIP stats were counting other relays, for example
2344 self-reachability and authority-reachability tests.
2347 - Support compilation to target iPhone; patch from cjacker huang.
2348 To build for iPhone, pass the --enable-iphone option to configure.
2351 Changes in version 0.2.0.14-alpha - 2007-12-23
2353 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
2354 without a datadirectory from a previous Tor install. Reported
2356 - Fix a crash when we fetch a descriptor that turns out to be
2357 unexpected (it used to be in our networkstatus when we started
2358 fetching it, but it isn't in our current networkstatus), and we
2359 aren't using bridges. Bugfix on 0.2.0.x.
2360 - Fix a crash when accessing hidden services: it would work the first
2361 time you use a given introduction point for your service, but
2362 on subsequent requests we'd be using garbage memory. Fixed by
2363 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
2364 - Fix a crash when we load a bridge descriptor from disk but we don't
2365 currently have a Bridge line for it in our torrc. Bugfix on
2369 - If bridge authorities set BridgePassword, they will serve a
2370 snapshot of known bridge routerstatuses from their DirPort to
2371 anybody who knows that password. Unset by default.
2374 - Make the unit tests build again.
2375 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
2376 - Make PublishServerDescriptor default to 1, so the default doesn't
2377 have to change as we invent new directory protocol versions.
2378 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
2379 be included unless sys/time.h is already included. Fixes
2380 bug 553. Bugfix on 0.2.0.x.
2381 - If we receive a general-purpose descriptor and then receive an
2382 identical bridge-purpose descriptor soon after, don't discard
2383 the next one as a duplicate.
2386 - If BridgeRelay is set to 1, then the default for
2387 PublishServerDescriptor is now "bridge" rather than "v2,v3".
2388 - If the user sets RelayBandwidthRate but doesn't set
2389 RelayBandwidthBurst, then make them equal rather than erroring out.
2392 Changes in version 0.2.0.13-alpha - 2007-12-21
2393 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
2394 Goodell, fixes many more bugs, and adds a lot of infrastructure for
2397 o New directory authorities:
2398 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
2402 - Only update guard status (usable / not usable) once we have
2403 enough directory information. This was causing us to always pick
2404 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
2405 causing us to discard all our guards on startup if we hadn't been
2406 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
2407 - Purge old entries from the "rephist" database and the hidden
2408 service descriptor databases even when DirPort is zero. Bugfix
2410 - We were ignoring our RelayBandwidthRate for the first 30 seconds
2411 after opening a circuit -- even a relayed circuit. Bugfix on
2413 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
2414 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
2415 crashing or mis-answering these types of requests.
2416 - Relays were publishing their server descriptor to v1 and v2
2417 directory authorities, but they didn't try publishing to v3-only
2418 authorities. Fix this; and also stop publishing to v1 authorities.
2420 - When we were reading router descriptors from cache, we were ignoring
2421 the annotations -- so for example we were reading in bridge-purpose
2422 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
2423 - When we decided to send a 503 response to a request for servers, we
2424 were then also sending the server descriptors: this defeats the
2425 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
2428 - Bridge relays now behave like clients with respect to time
2429 intervals for downloading new consensus documents -- otherwise they
2430 stand out. Bridge users now wait until the end of the interval,
2431 so their bridge relay will be sure to have a new consensus document.
2432 - Three new config options (AlternateDirAuthority,
2433 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
2434 user selectively replace the default directory authorities by type,
2435 rather than the all-or-nothing replacement that DirServer offers.
2436 - Tor can now be configured to read a GeoIP file from disk in one
2437 of two formats. This can be used by controllers to map IP addresses
2438 to countries. Eventually, it may support exit-by-country.
2439 - When possible, bridge relays remember which countries users
2440 are coming from, and report aggregate information in their
2441 extra-info documents, so that the bridge authorities can learn
2442 where Tor is blocked.
2443 - Bridge directory authorities now do reachability testing on the
2444 bridges they know. They provide router status summaries to the
2445 controller via "getinfo ns/purpose/bridge", and also dump summaries
2446 to a file periodically.
2447 - Stop fetching directory info so aggressively if your DirPort is
2448 on but your ORPort is off; stop fetching v2 dir info entirely.
2449 You can override these choices with the new FetchDirInfoEarly
2453 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
2454 consensus documents when there are too many relays at a single
2455 IP address. Now clear it in v2 network status documents too, and
2456 also clear it in routerinfo_t when the relay is no longer listed
2457 in the relevant networkstatus document.
2458 - Don't crash if we get an unexpected value for the
2459 PublishServerDescriptor config option. Reported by Matt Edman;
2460 bugfix on 0.2.0.9-alpha.
2461 - Our new v2 hidden service descriptor format allows descriptors
2462 that have no introduction points. But Tor crashed when we tried
2463 to build a descriptor with no intro points (and it would have
2464 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
2466 - Fix building with dmalloc 5.5.2 with glibc.
2467 - Reject uploaded descriptors and extrainfo documents if they're
2468 huge. Otherwise we'll cache them all over the network and it'll
2469 clog everything up. Reported by Aljosha Judmayer.
2470 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
2471 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
2472 - When the DANGEROUS_VERSION controller status event told us we're
2473 running an obsolete version, it used the string "OLD" to describe
2474 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
2475 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
2476 - If we can't expand our list of entry guards (e.g. because we're
2477 using bridges or we have StrictEntryNodes set), don't mark relays
2478 down when they fail a directory request. Otherwise we're too quick
2479 to mark all our entry points down. Bugfix on 0.1.2.x.
2480 - Fix handling of hex nicknames when answering controller requests for
2481 networkstatus by name, or when deciding whether to warn about unknown
2482 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
2483 - Fix a couple of hard-to-trigger autoconf problems that could result
2484 in really weird results on platforms whose sys/types.h files define
2485 nonstandard integer types. Bugfix on 0.1.2.x.
2486 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
2487 - Don't crash on name lookup when we have no current consensus. Fixes
2488 bug 538; bugfix on 0.2.0.x.
2489 - Only Tors that want to mirror the v2 directory info should
2490 create the "cached-status" directory in their datadir. (All Tors
2491 used to create it.) Bugfix on 0.2.0.9-alpha.
2492 - Directory authorities should only automatically download Extra Info
2493 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
2496 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
2497 consumers. (We already do this on HUP.)
2498 - Authorities and caches fetch the v2 networkstatus documents
2499 less often, now that v3 is encouraged.
2500 - Add a new config option BridgeRelay that specifies you want to
2501 be a bridge relay. Right now the only difference is that it makes
2502 you answer begin_dir requests, and it makes you cache dir info,
2503 even if your DirPort isn't on.
2504 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
2505 ask about source, timestamp of arrival, purpose, etc. We need
2506 something like this to help Vidalia not do GeoIP lookups on bridge
2508 - Allow multiple HashedControlPassword config lines, to support
2509 multiple controller passwords.
2510 - Authorities now decide whether they're authoritative for a given
2511 router based on the router's purpose.
2512 - New config options AuthDirBadDir and AuthDirListBadDirs for
2513 authorities to mark certain relays as "bad directories" in the
2514 networkstatus documents. Also supports the "!baddir" directive in
2515 the approved-routers file.
2518 Changes in version 0.2.0.12-alpha - 2007-11-16
2519 This twelfth development snapshot fixes some more build problems as
2520 well as a few minor bugs.
2523 - Make it build on OpenBSD again. Patch from tup.
2524 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
2525 package-building for Red Hat, OS X, etc.
2527 o Minor bugfixes (on 0.1.2.x):
2528 - Changing the ExitPolicyRejectPrivate setting should cause us to
2529 rebuild our server descriptor.
2531 o Minor bugfixes (on 0.2.0.x):
2532 - When we're lacking a consensus, don't try to perform rendezvous
2533 operations. Reported by Karsten Loesing.
2534 - Fix a small memory leak whenever we decide against using a
2535 newly picked entry guard. Reported by Mike Perry.
2536 - When authorities detected more than two relays running on the same
2537 IP address, they were clearing all the status flags but forgetting
2538 to clear the "hsdir" flag. So clients were being told that a
2539 given relay was the right choice for a v2 hsdir lookup, yet they
2540 never had its descriptor because it was marked as 'not running'
2542 - If we're trying to fetch a bridge descriptor and there's no way
2543 the bridge authority could help us (for example, we don't know
2544 a digest, or there is no bridge authority), don't be so eager to
2545 fall back to asking the bridge authority.
2546 - If we're using bridges or have strictentrynodes set, and our
2547 chosen exit is in the same family as all our bridges/entry guards,
2548 then be flexible about families.
2551 - When we negotiate a v2 link-layer connection (not yet implemented),
2552 accept RELAY_EARLY cells and turn them into RELAY cells if we've
2553 negotiated a v1 connection for their next step. Initial code for
2557 Changes in version 0.2.0.11-alpha - 2007-11-12
2558 This eleventh development snapshot fixes some build problems with
2559 the previous snapshot. It also includes a more secure-by-default exit
2560 policy for relays, fixes an enormous memory leak for exit relays, and
2561 fixes another bug where servers were falling out of the directory list.
2564 - Exit policies now reject connections that are addressed to a
2565 relay's public (external) IP address too, unless
2566 ExitPolicyRejectPrivate is turned off. We do this because too
2567 many relays are running nearby to services that trust them based
2568 on network address. Bugfix on 0.1.2.x.
2571 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
2572 on every successful resolve. Reported by Mike Perry; bugfix
2574 - On authorities, never downgrade to old router descriptors simply
2575 because they're listed in the consensus. This created a catch-22
2576 where we wouldn't list a new descriptor because there was an
2577 old one in the consensus, and we couldn't get the new one in the
2578 consensus because we wouldn't list it. Possible fix for bug 548.
2579 Also, this might cause bug 543 to appear on authorities; if so,
2580 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
2582 o Packaging fixes on 0.2.0.10-alpha:
2583 - We were including instructions about what to do with the
2584 src/config/fallback-consensus file, but we weren't actually
2585 including it in the tarball. Disable all of that for now.
2588 - Allow people to say PreferTunnelledDirConns rather than
2589 PreferTunneledDirConns, for those alternate-spellers out there.
2592 - Don't reevaluate all the information from our consensus document
2593 just because we've downloaded a v2 networkstatus that we intend
2594 to cache. Fixes bug 545; bugfix on 0.2.0.x.
2597 Changes in version 0.2.0.10-alpha - 2007-11-10
2598 This tenth development snapshot adds a third v3 directory authority
2599 run by Mike Perry, adds most of Karsten Loesing's new hidden service
2600 descriptor format, fixes a bad crash bug and new bridge bugs introduced
2601 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
2602 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
2603 addresses many more minor issues.
2605 o New directory authorities:
2606 - Set up ides (run by Mike Perry) as the third v3 directory authority.
2609 - Allow tunnelled directory connections to ask for an encrypted
2610 "begin_dir" connection or an anonymized "uses a full Tor circuit"
2611 connection independently. Now we can make anonymized begin_dir
2612 connections for (e.g.) more secure hidden service posting and
2614 - More progress on proposal 114: code from Karsten Loesing to
2615 implement new hidden service descriptor format.
2616 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
2617 accommodate the growing number of servers that use the default
2618 and are reaching it.
2619 - Directory authorities use a new formula for selecting which nodes
2620 to advertise as Guards: they must be in the top 7/8 in terms of
2621 how long we have known about them, and above the median of those
2622 nodes in terms of weighted fractional uptime.
2623 - Make "not enough dir info yet" warnings describe *why* Tor feels
2624 it doesn't have enough directory info yet.
2627 - Stop servers from crashing if they set a Family option (or
2628 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
2630 - Make bridge users work again -- the move to v3 directories in
2631 0.2.0.9-alpha had introduced a number of bugs that made bridges
2632 no longer work for clients.
2633 - When the clock jumps forward a lot, do not allow the bandwidth
2634 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
2636 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
2637 - When the consensus lists a router descriptor that we previously were
2638 mirroring, but that we considered non-canonical, reload the
2639 descriptor as canonical. This fixes bug 543 where Tor servers
2640 would start complaining after a few days that they don't have
2641 enough directory information to build a circuit.
2642 - Consider replacing the current consensus when certificates arrive
2643 that make the pending consensus valid. Previously, we were only
2644 considering replacement when the new certs _didn't_ help.
2645 - Fix an assert error on startup if we didn't already have the
2646 consensus and certs cached in our datadirectory: we were caching
2647 the consensus in consensus_waiting_for_certs but then free'ing it
2649 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
2650 Request) if we need more v3 certs but we've already got pending
2651 requests for all of them.
2652 - Correctly back off from failing certificate downloads. Fixes
2654 - Authorities don't vote on the Running flag if they have been running
2655 for less than 30 minutes themselves. Fixes bug 547, where a newly
2656 started authority would vote that everyone was down.
2659 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
2660 it, it had no AES, and it hasn't seen any security patches since
2664 - Clients now hold circuitless TLS connections open for 1.5 times
2665 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
2666 rebuild a new circuit over them within that timeframe. Previously,
2667 they held them open only for KeepalivePeriod (5 minutes).
2668 - Use "If-Modified-Since" to avoid retrieving consensus
2669 networkstatuses that we already have.
2670 - When we have no consensus, check FallbackNetworkstatusFile (defaults
2671 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
2672 we start knowing some directory caches.
2673 - When we receive a consensus from the future, warn about skew.
2674 - Improve skew reporting: try to give the user a better log message
2675 about how skewed they are, and how much this matters.
2676 - When we have a certificate for an authority, believe that
2677 certificate's claims about the authority's IP address.
2678 - New --quiet command-line option to suppress the default console log.
2679 Good in combination with --hash-password.
2680 - Authorities send back an X-Descriptor-Not-New header in response to
2681 an accepted-but-discarded descriptor upload. Partially implements
2683 - Make the log message for "tls error. breaking." more useful.
2684 - Better log messages about certificate downloads, to attempt to
2685 track down the second incarnation of bug 546.
2687 o Minor features (bridges):
2688 - If bridge users set UpdateBridgesFromAuthority, but the digest
2689 they ask for is a 404 from the bridge authority, they now fall
2690 back to trying the bridge directly.
2691 - Bridges now use begin_dir to publish their server descriptor to
2692 the bridge authority, even when they haven't set TunnelDirConns.
2694 o Minor features (controller):
2695 - When reporting clock skew, and we know that the clock is _at least
2696 as skewed_ as some value, but we don't know the actual value,
2697 report the value as a "minimum skew."
2700 - Update linux-tor-prio.sh script to allow QoS based on the uid of
2701 the Tor process. Patch from Marco Bonetti with tweaks from Mike
2705 - Refuse to start if both ORPort and UseBridges are set. Bugfix
2706 on 0.2.0.x, suggested by Matt Edman.
2707 - Don't stop fetching descriptors when FetchUselessDescriptors is
2708 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
2709 reported by tup and ioerror.
2710 - Better log message on vote from unknown authority.
2711 - Don't log "Launching 0 request for 0 router" message.
2713 o Minor bugfixes (memory leaks):
2714 - Stop leaking memory every time we parse a v3 certificate. Bugfix
2716 - Stop leaking memory every time we load a v3 certificate. Bugfix
2717 on 0.2.0.1-alpha. Fixes bug 536.
2718 - Stop leaking a cached networkstatus on exit. Bugfix on
2720 - Stop leaking voter information every time we free a consensus.
2721 Bugfix on 0.2.0.3-alpha.
2722 - Stop leaking signed data every time we check a voter signature.
2723 Bugfix on 0.2.0.3-alpha.
2724 - Stop leaking a signature every time we fail to parse a consensus or
2725 a vote. Bugfix on 0.2.0.3-alpha.
2726 - Stop leaking v2_download_status_map on shutdown. Bugfix on
2728 - Stop leaking conn->nickname every time we make a connection to a
2729 Tor relay without knowing its expected identity digest (e.g. when
2730 using bridges). Bugfix on 0.2.0.3-alpha.
2732 - Minor bugfixes (portability):
2733 - Run correctly on platforms where rlim_t is larger than unsigned
2734 long, and/or where the real limit for number of open files is
2735 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
2736 particular, these may be needed for OS X 10.5.
2739 Changes in version 0.1.2.18 - 2007-10-28
2740 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
2741 hidden service introduction that were causing huge delays, and a big
2742 bug that was causing some servers to disappear from the network status
2743 lists for a few hours each day.
2745 o Major bugfixes (crashes):
2746 - If a connection is shut down abruptly because of something that
2747 happened inside connection_flushed_some(), do not call
2748 connection_finished_flushing(). Should fix bug 451:
2749 "connection_stop_writing: Assertion conn->write_event failed"
2750 Bugfix on 0.1.2.7-alpha.
2751 - Fix possible segfaults in functions called from
2752 rend_process_relay_cell().
2754 o Major bugfixes (hidden services):
2755 - Hidden services were choosing introduction points uniquely by
2756 hexdigest, but when constructing the hidden service descriptor
2757 they merely wrote the (potentially ambiguous) nickname.
2758 - Clients now use the v2 intro format for hidden service
2759 connections: they specify their chosen rendezvous point by identity
2760 digest rather than by (potentially ambiguous) nickname. These
2761 changes could speed up hidden service connections dramatically.
2763 o Major bugfixes (other):
2764 - Stop publishing a new server descriptor just because we get a
2765 HUP signal. This led (in a roundabout way) to some servers getting
2766 dropped from the networkstatus lists for a few hours each day.
2767 - When looking for a circuit to cannibalize, consider family as well
2768 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
2769 circuit cannibalization).
2770 - When a router wasn't listed in a new networkstatus, we were leaving
2771 the flags for that router alone -- meaning it remained Named,
2772 Running, etc -- even though absence from the networkstatus means
2773 that it shouldn't be considered to exist at all anymore. Now we
2774 clear all the flags for routers that fall out of the networkstatus
2775 consensus. Fixes bug 529.
2778 - Don't try to access (or alter) the state file when running
2779 --list-fingerprint or --verify-config or --hash-password. Resolves
2781 - When generating information telling us how to extend to a given
2782 router, do not try to include the nickname if it is
2783 absent. Resolves bug 467.
2784 - Fix a user-triggerable segfault in expand_filename(). (There isn't
2785 a way to trigger this remotely.)
2786 - When sending a status event to the controller telling it that an
2787 OR address is reachable, set the port correctly. (Previously we
2788 were reporting the dir port.)
2789 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
2790 command. Bugfix on 0.1.2.17.
2791 - When loading bandwidth history, do not believe any information in
2792 the future. Fixes bug 434.
2793 - When loading entry guard information, do not believe any information
2795 - When we have our clock set far in the future and generate an
2796 onion key, then re-set our clock to be correct, we should not stop
2797 the onion key from getting rotated.
2798 - On some platforms, accept() can return a broken address. Detect
2799 this more quietly, and deal accordingly. Fixes bug 483.
2800 - It's not actually an error to find a non-pending entry in the DNS
2801 cache when canceling a pending resolve. Don't log unless stuff
2802 is fishy. Resolves bug 463.
2803 - Don't reset trusted dir server list when we set a configuration
2804 option. Patch from Robert Hogan.
2805 - Don't try to create the datadir when running --verify-config or
2806 --hash-password. Resolves bug 540.
2809 Changes in version 0.2.0.9-alpha - 2007-10-24
2810 This ninth development snapshot switches clients to the new v3 directory
2811 system; allows servers to be listed in the network status even when they
2812 have the same nickname as a registered server; and fixes many other
2813 bugs including a big one that was causing some servers to disappear
2814 from the network status lists for a few hours each day.
2816 o Major features (directory system):
2817 - Clients now download v3 consensus networkstatus documents instead
2818 of v2 networkstatus documents. Clients and caches now base their
2819 opinions about routers on these consensus documents. Clients only
2820 download router descriptors listed in the consensus.
2821 - Authorities now list servers who have the same nickname as
2822 a different named server, but list them with a new flag,
2823 "Unnamed". Now we can list servers that happen to pick the same
2824 nickname as a server that registered two years ago and then
2825 disappeared. Partially implements proposal 122.
2826 - If the consensus lists a router as "Unnamed", the name is assigned
2827 to a different router: do not identify the router by that name.
2828 Partially implements proposal 122.
2829 - Authorities can now come to a consensus on which method to use to
2830 compute the consensus. This gives us forward compatibility.
2833 - Stop publishing a new server descriptor just because we HUP or
2834 when we find our DirPort to be reachable but won't actually publish
2835 it. New descriptors without any real changes are dropped by the
2836 authorities, and can screw up our "publish every 18 hours" schedule.
2838 - When a router wasn't listed in a new networkstatus, we were leaving
2839 the flags for that router alone -- meaning it remained Named,
2840 Running, etc -- even though absence from the networkstatus means
2841 that it shouldn't be considered to exist at all anymore. Now we
2842 clear all the flags for routers that fall out of the networkstatus
2843 consensus. Fixes bug 529; bugfix on 0.1.2.x.
2844 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
2845 extrainfo documents and then discard them immediately for not
2846 matching the latest router. Bugfix on 0.2.0.1-alpha.
2848 o Minor features (v3 directory protocol):
2849 - Allow tor-gencert to generate a new certificate without replacing
2851 - Allow certificates to include an address.
2852 - When we change our directory-cache settings, reschedule all voting
2853 and download operations.
2854 - Reattempt certificate downloads immediately on failure, as long as
2855 we haven't failed a threshold number of times yet.
2856 - Delay retrying consensus downloads while we're downloading
2857 certificates to verify the one we just got. Also, count getting a
2858 consensus that we already have (or one that isn't valid) as a failure,
2859 and count failing to get the certificates after 20 minutes as a
2861 - Build circuits and download descriptors even if our consensus is a
2862 little expired. (This feature will go away once authorities are
2865 o Minor features (router descriptor cache):
2866 - If we find a cached-routers file that's been sitting around for more
2867 than 28 days unmodified, then most likely it's a leftover from
2868 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
2870 - When we (as a cache) download a descriptor because it was listed
2871 in a consensus, remember when the consensus was supposed to expire,
2872 and don't expire the descriptor until then.
2874 o Minor features (performance):
2875 - Call routerlist_remove_old_routers() much less often. This should
2876 speed startup, especially on directory caches.
2877 - Don't try to launch new descriptor downloads quite so often when we
2878 already have enough directory information to build circuits.
2879 - Base64 decoding was actually showing up on our profile when parsing
2880 the initial descriptor file; switch to an in-process all-at-once
2881 implementation that's about 3.5x times faster than calling out to
2884 o Minor features (compilation):
2885 - Detect non-ASCII platforms (if any still exist) and refuse to
2886 build there: some of our code assumes that 'A' is 65 and so on.
2888 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
2889 - Make the "next period" votes into "current period" votes immediately
2890 after publishing the consensus; avoid a heisenbug that made them
2891 stick around indefinitely.
2892 - When we discard a vote as a duplicate, do not report this as
2894 - Treat missing v3 keys or certificates as an error when running as a
2895 v3 directory authority.
2896 - When we're configured to be a v3 authority, but we're only listed
2897 as a non-v3 authority in our DirServer line for ourself, correct
2899 - If an authority doesn't have a qualified hostname, just put
2900 its address in the vote. This fixes the problem where we referred to
2901 "moria on moria:9031."
2902 - Distinguish between detached signatures for the wrong period, and
2903 detached signatures for a divergent vote.
2904 - Fix a small memory leak when computing a consensus.
2905 - When there's no concensus, we were forming a vote every 30
2906 minutes, but writing the "valid-after" line in our vote based
2907 on our configured V3AuthVotingInterval: so unless the intervals
2908 matched up, we immediately rejected our own vote because it didn't
2909 start at the voting interval that caused us to construct a vote.
2911 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
2912 - Delete unverified-consensus when the real consensus is set.
2913 - Consider retrying a consensus networkstatus fetch immediately
2914 after one fails: don't wait 60 seconds to notice.
2915 - When fetching a consensus as a cache, wait until a newer consensus
2916 should exist before trying to replace the current one.
2917 - Use a more forgiving schedule for retrying failed consensus
2918 downloads than for other types.
2920 o Minor bugfixes (other directory issues):
2921 - Correct the implementation of "download votes by digest." Bugfix on
2923 - Authorities no longer send back "400 you're unreachable please fix
2924 it" errors to Tor servers that aren't online all the time. We're
2925 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
2927 o Minor bugfixes (controller):
2928 - Don't reset trusted dir server list when we set a configuration
2929 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
2930 - Respond to INT and TERM SIGNAL commands before we execute the
2931 signal, in case the signal shuts us down. We had a patch in
2932 0.1.2.1-alpha that tried to do this by queueing the response on
2933 the connection's buffer before shutting down, but that really
2934 isn't the same thing at all. Bug located by Matt Edman.
2936 o Minor bugfixes (misc):
2937 - Correctly check for bad options to the "PublishServerDescriptor"
2938 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
2939 - Stop leaking memory on failing case of base32_decode, and make
2940 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
2941 - Don't try to download extrainfo documents when we're trying to
2942 fetch enough directory info to build a circuit: having enough
2943 info should get priority. Bugfix on 0.2.0.x.
2944 - Don't complain that "your server has not managed to confirm that its
2945 ports are reachable" if we haven't been able to build any circuits
2946 yet. Bug found by spending four hours without a v3 consensus. Bugfix
2948 - Detect the reason for failing to mmap a descriptor file we just
2949 wrote, and give a more useful log message. Fixes bug 533. Bugfix
2952 o Code simplifications and refactoring:
2953 - Remove support for the old bw_accounting file: we've been storing
2954 bandwidth accounting information in the state file since
2955 0.1.2.5-alpha. This may result in bandwidth accounting errors
2956 if you try to upgrade from 0.1.1.x or earlier, or if you try to
2957 downgrade to 0.1.1.x or earlier.
2958 - New convenience code to locate a file within the DataDirectory.
2959 - Move non-authority functionality out of dirvote.c.
2960 - Refactor the arguments for router_pick_{directory_|trusteddir}server
2961 so that they all take the same named flags.
2964 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
2965 Unix users an easy way to script their Tor process (e.g. by
2966 adjusting bandwidth based on the time of the day).
2969 Changes in version 0.2.0.8-alpha - 2007-10-12
2970 This eighth development snapshot fixes a crash bug that's been bothering
2971 us since February 2007, lets bridge authorities store a list of bridge
2972 descriptors they've seen, gets v3 directory voting closer to working,
2973 starts caching v3 directory consensus documents on directory mirrors,
2974 and fixes a variety of smaller issues including some minor memory leaks.
2976 o Major features (router descriptor cache):
2977 - Store routers in a file called cached-descriptors instead of in
2978 cached-routers. Initialize cached-descriptors from cached-routers
2979 if the old format is around. The new format allows us to store
2980 annotations along with descriptors.
2981 - Use annotations to record the time we received each descriptor, its
2982 source, and its purpose.
2983 - Disable the SETROUTERPURPOSE controller command: it is now
2985 - Controllers should now specify cache=no or cache=yes when using
2986 the +POSTDESCRIPTOR command.
2987 - Bridge authorities now write bridge descriptors to disk, meaning
2988 we can export them to other programs and begin distributing them
2991 o Major features (directory authorities):
2992 - When a v3 authority is missing votes or signatures, it now tries
2994 - Directory authorities track weighted fractional uptime as well as
2995 weighted mean-time-between failures. WFU is suitable for deciding
2996 whether a node is "usually up", while MTBF is suitable for deciding
2997 whether a node is "likely to stay up." We need both, because
2998 "usually up" is a good requirement for guards, while "likely to
2999 stay up" is a good requirement for long-lived connections.
3001 o Major features (v3 directory system):
3002 - Caches now download v3 network status documents as needed,
3003 and download the descriptors listed in them.
3004 - All hosts now attempt to download and keep fresh v3 authority
3005 certificates, and re-attempt after failures.
3006 - More internal-consistency checks for vote parsing.
3008 o Major bugfixes (crashes):
3009 - If a connection is shut down abruptly because of something that
3010 happened inside connection_flushed_some(), do not call
3011 connection_finished_flushing(). Should fix bug 451. Bugfix on
3014 o Major bugfixes (performance):
3015 - Fix really bad O(n^2) performance when parsing a long list of
3016 routers: Instead of searching the entire list for an "extra-info "
3017 string which usually wasn't there, once for every routerinfo
3018 we read, just scan lines forward until we find one we like.
3020 - When we add data to a write buffer in response to the data on that
3021 write buffer getting low because of a flush, do not consider the
3022 newly added data as a candidate for immediate flushing, but rather
3023 make it wait until the next round of writing. Otherwise, we flush
3024 and refill recursively, and a single greedy TLS connection can
3025 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
3027 o Minor features (v3 authority system):
3028 - Add more ways for tools to download the votes that lead to the
3030 - Send a 503 when low on bandwidth and a vote, consensus, or
3031 certificate is requested.
3032 - If-modified-since is now implemented properly for all kinds of
3033 certificate requests.
3035 o Minor bugfixes (network statuses):
3036 - Tweak the implementation of proposal 109 slightly: allow at most
3037 two Tor servers on the same IP address, except if it's the location
3038 of a directory authority, in which case allow five. Bugfix on
3041 o Minor bugfixes (controller):
3042 - When sending a status event to the controller telling it that an
3043 OR address is reachable, set the port correctly. (Previously we
3044 were reporting the dir port.) Bugfix on 0.1.2.x.
3046 o Minor bugfixes (v3 directory system):
3047 - Fix logic to look up a cert by its signing key digest. Bugfix on
3049 - Only change the reply to a vote to "OK" if it's not already
3050 set. This gets rid of annoying "400 OK" log messages, which may
3051 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
3052 - When we get a valid consensus, recompute the voting schedule.
3053 - Base the valid-after time of a vote on the consensus voting
3054 schedule, not on our preferred schedule.
3055 - Make the return values and messages from signature uploads and
3056 downloads more sensible.
3057 - Fix a memory leak when serving votes and consensus documents, and
3058 another when serving certificates.
3060 o Minor bugfixes (performance):
3061 - Use a slightly simpler string hashing algorithm (copying Python's
3062 instead of Java's) and optimize our digest hashing algorithm to take
3063 advantage of 64-bit platforms and to remove some possibly-costly
3065 - Fix a minor memory leak whenever we parse guards from our state
3066 file. Bugfix on 0.2.0.7-alpha.
3067 - Fix a minor memory leak whenever we write out a file. Bugfix on
3069 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
3070 command. Bugfix on 0.2.0.5-alpha.
3072 o Minor bugfixes (portability):
3073 - On some platforms, accept() can return a broken address. Detect
3074 this more quietly, and deal accordingly. Fixes bug 483.
3075 - Stop calling tor_strlower() on uninitialized memory in some cases.
3076 Bugfix in 0.2.0.7-alpha.
3078 o Minor bugfixes (usability):
3079 - Treat some 403 responses from directory servers as INFO rather than
3080 WARN-severity events.
3081 - It's not actually an error to find a non-pending entry in the DNS
3082 cache when canceling a pending resolve. Don't log unless stuff is
3083 fishy. Resolves bug 463.
3085 o Minor bugfixes (anonymity):
3086 - Never report that we've used more bandwidth than we're willing to
3087 relay: it leaks how much non-relay traffic we're using. Resolves
3089 - When looking for a circuit to cannibalize, consider family as well
3090 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
3091 circuit cannibalization).
3093 o Code simplifications and refactoring:
3094 - Make a bunch of functions static. Remove some dead code.
3095 - Pull out about a third of the really big routerlist.c; put it in a
3096 new module, networkstatus.c.
3097 - Merge the extra fields in local_routerstatus_t back into
3098 routerstatus_t: we used to need one routerstatus_t for each
3099 authority's opinion, plus a local_routerstatus_t for the locally
3100 computed consensus opinion. To save space, we put the locally
3101 modified fields into local_routerstatus_t, and only the common
3102 stuff into routerstatus_t. But once v3 directories are in use,
3103 clients and caches will no longer need to hold authority opinions;
3104 thus, the rationale for keeping the types separate is now gone.
3105 - Make the code used to reschedule and reattempt downloads more
3107 - Turn all 'Are we a directory server/mirror?' logic into a call to
3109 - Remove the code to generate the oldest (v1) directory format.
3110 The code has been disabled since 0.2.0.5-alpha.
3113 Changes in version 0.2.0.7-alpha - 2007-09-21
3114 This seventh development snapshot makes bridges work again, makes bridge
3115 authorities work for the first time, fixes two huge performance flaws
3116 in hidden services, and fixes a variety of minor issues.
3118 o New directory authorities:
3119 - Set up moria1 and tor26 as the first v3 directory authorities. See
3120 doc/spec/dir-spec.txt for details on the new directory design.
3122 o Major bugfixes (crashes):
3123 - Fix possible segfaults in functions called from
3124 rend_process_relay_cell(). Bugfix on 0.1.2.x.
3126 o Major bugfixes (bridges):
3127 - Fix a bug that made servers send a "404 Not found" in response to
3128 attempts to fetch their server descriptor. This caused Tor servers
3129 to take many minutes to establish reachability for their DirPort,
3130 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
3131 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
3132 users configure that and specify a bridge with an identity
3133 fingerprint, now they will lookup the bridge descriptor at the
3134 default bridge authority via a one-hop tunnel, but once circuits
3135 are established they will switch to a three-hop tunnel for later
3136 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
3138 o Major bugfixes (hidden services):
3139 - Hidden services were choosing introduction points uniquely by
3140 hexdigest, but when constructing the hidden service descriptor
3141 they merely wrote the (potentially ambiguous) nickname.
3142 - Clients now use the v2 intro format for hidden service
3143 connections: they specify their chosen rendezvous point by identity
3144 digest rather than by (potentially ambiguous) nickname. Both
3145 are bugfixes on 0.1.2.x, and they could speed up hidden service
3146 connections dramatically. Thanks to Karsten Loesing.
3148 o Minor features (security):
3149 - As a client, do not believe any server that tells us that an
3150 address maps to an internal address space.
3151 - Make it possible to enable HashedControlPassword and
3152 CookieAuthentication at the same time.
3154 o Minor features (guard nodes):
3155 - Tag every guard node in our state file with the version that
3156 we believe added it, or with our own version if we add it. This way,
3157 if a user temporarily runs an old version of Tor and then switches
3158 back to a new one, she doesn't automatically lose her guards.
3160 o Minor features (speed):
3161 - When implementing AES counter mode, update only the portions of the
3162 counter buffer that need to change, and don't keep separate
3163 network-order and host-order counters when they are the same (i.e.,
3164 on big-endian hosts.)
3166 o Minor features (controller):
3167 - Accept LF instead of CRLF on controller, since some software has a
3168 hard time generating real Internet newlines.
3169 - Add GETINFO values for the server status events
3170 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
3174 - Routers no longer include bandwidth-history lines in their
3175 descriptors; this information is already available in extra-info
3176 documents, and including it in router descriptors took up 60%
3177 (!) of compressed router descriptor downloads. Completes
3178 implementation of proposal 104.
3179 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
3180 and TorControl.py, as they use the old v0 controller protocol,
3181 and are obsoleted by TorFlow anyway.
3182 - Drop support for v1 rendezvous descriptors, since we never used
3183 them anyway, and the code has probably rotted by now. Based on
3184 patch from Karsten Loesing.
3185 - On OSX, stop warning the user that kqueue support in libevent is
3186 "experimental", since it seems to have worked fine for ages.
3189 - When generating information telling us how to extend to a given
3190 router, do not try to include the nickname if it is absent. Fixes
3191 bug 467. Bugfix on 0.2.0.3-alpha.
3192 - Fix a user-triggerable (but not remotely-triggerable) segfault
3193 in expand_filename(). Bugfix on 0.1.2.x.
3194 - Fix a memory leak when freeing incomplete requests from DNSPort.
3195 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
3196 - Don't try to access (or alter) the state file when running
3197 --list-fingerprint or --verify-config or --hash-password. (Resolves
3198 bug 499.) Bugfix on 0.1.2.x.
3199 - Servers used to decline to publish their DirPort if their
3200 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
3201 were below a threshold. Now they only look at BandwidthRate and
3202 RelayBandwidthRate. Bugfix on 0.1.2.x.
3203 - Remove an optimization in the AES counter-mode code that assumed
3204 that the counter never exceeded 2^68. When the counter can be set
3205 arbitrarily as an IV (as it is by Karsten's new hidden services
3206 code), this assumption no longer holds. Bugfix on 0.1.2.x.
3207 - Resume listing "AUTHORITY" flag for authorities in network status.
3208 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
3210 o Code simplifications and refactoring:
3211 - Revamp file-writing logic so we don't need to have the entire
3212 contents of a file in memory at once before we write to disk. Tor,
3214 - Turn "descriptor store" into a full-fledged type.
3215 - Move all NT services code into a separate source file.
3216 - Unify all code that computes medians, percentile elements, etc.
3217 - Get rid of a needless malloc when parsing address policies.
3220 Changes in version 0.1.2.17 - 2007-08-30
3221 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
3222 X bundles. Vidalia 0.0.14 makes authentication required for the
3223 ControlPort in the default configuration, which addresses important
3224 security risks. Everybody who uses Vidalia (or another controller)
3227 In addition, this Tor update fixes major load balancing problems with
3228 path selection, which should speed things up a lot once many people
3231 o Major bugfixes (security):
3232 - We removed support for the old (v0) control protocol. It has been
3233 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
3234 become more of a headache than it's worth.
3236 o Major bugfixes (load balancing):
3237 - When choosing nodes for non-guard positions, weight guards
3238 proportionally less, since they already have enough load. Patch
3240 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
3241 will allow fast Tor servers to get more attention.
3242 - When we're upgrading from an old Tor version, forget our current
3243 guards and pick new ones according to the new weightings. These
3244 three load balancing patches could raise effective network capacity
3245 by a factor of four. Thanks to Mike Perry for measurements.
3247 o Major bugfixes (stream expiration):
3248 - Expire not-yet-successful application streams in all cases if
3249 they've been around longer than SocksTimeout. Right now there are
3250 some cases where the stream will live forever, demanding a new
3251 circuit every 15 seconds. Fixes bug 454; reported by lodger.
3253 o Minor features (controller):
3254 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
3255 is valid before any authentication has been received. It tells
3256 a controller what kind of authentication is expected, and what
3257 protocol is spoken. Implements proposal 119.
3259 o Minor bugfixes (performance):
3260 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
3261 greatly speeding up loading cached-routers from disk on startup.
3262 - Disable sentinel-based debugging for buffer code: we squashed all
3263 the bugs that this was supposed to detect a long time ago, and now
3264 its only effect is to change our buffer sizes from nice powers of
3265 two (which platform mallocs tend to like) to values slightly over
3266 powers of two (which make some platform mallocs sad).
3268 o Minor bugfixes (misc):
3269 - If exit bandwidth ever exceeds one third of total bandwidth, then
3270 use the correct formula to weight exit nodes when choosing paths.
3271 Based on patch from Mike Perry.
3272 - Choose perfectly fairly among routers when choosing by bandwidth and
3273 weighting by fraction of bandwidth provided by exits. Previously, we
3274 would choose with only approximate fairness, and correct ourselves
3275 if we ran off the end of the list.
3276 - If we require CookieAuthentication but we fail to write the
3277 cookie file, we would warn but not exit, and end up in a state
3278 where no controller could authenticate. Now we exit.
3279 - If we require CookieAuthentication, stop generating a new cookie
3280 every time we change any piece of our config.
3281 - Refuse to start with certain directory authority keys, and
3282 encourage people using them to stop.
3283 - Terminate multi-line control events properly. Original patch
3285 - Fix a minor memory leak when we fail to find enough suitable
3286 servers to choose a circuit.
3287 - Stop leaking part of the descriptor when we run into a particularly
3288 unparseable piece of it.
3291 Changes in version 0.2.0.6-alpha - 2007-08-26
3292 This sixth development snapshot features a new Vidalia version in the
3293 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
3294 the ControlPort in the default configuration, which addresses important
3297 In addition, this snapshot fixes major load balancing problems
3298 with path selection, which should speed things up a lot once many
3299 people have upgraded. The directory authorities also use a new
3300 mean-time-between-failure approach to tracking which servers are stable,
3301 rather than just looking at the most recent uptime.
3303 o New directory authorities:
3304 - Set up Tonga as the default bridge directory authority.
3307 - Directory authorities now track servers by weighted
3308 mean-times-between-failures. When we have 4 or more days of data,
3309 use measured MTBF rather than declared uptime to decide whether
3310 to call a router Stable. Implements proposal 108.
3312 o Major bugfixes (load balancing):
3313 - When choosing nodes for non-guard positions, weight guards
3314 proportionally less, since they already have enough load. Patch
3316 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
3317 will allow fast Tor servers to get more attention.
3318 - When we're upgrading from an old Tor version, forget our current
3319 guards and pick new ones according to the new weightings. These
3320 three load balancing patches could raise effective network capacity
3321 by a factor of four. Thanks to Mike Perry for measurements.
3323 o Major bugfixes (descriptor parsing):
3324 - Handle unexpected whitespace better in malformed descriptors. Bug
3325 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
3328 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
3329 GETINFO for Torstat to use until it can switch to using extrainfos.
3330 - Optionally (if built with -DEXPORTMALLINFO) export the output
3331 of mallinfo via http, as tor/mallinfo.txt. Only accessible
3335 - Do not intermix bridge routers with controller-added
3336 routers. (Bugfix on 0.2.0.x)
3337 - Do not fail with an assert when accept() returns an unexpected
3338 address family. Addresses but does not wholly fix bug 483. (Bugfix
3340 - Let directory authorities startup even when they can't generate
3341 a descriptor immediately, e.g. because they don't know their
3343 - Stop putting the authentication cookie in a file called "0"
3344 in your working directory if you don't specify anything for the
3345 new CookieAuthFile option. Reported by Matt Edman.
3346 - Make it possible to read the PROTOCOLINFO response in a way that
3347 conforms to our control-spec. Reported by Matt Edman.
3348 - Fix a minor memory leak when we fail to find enough suitable
3349 servers to choose a circuit. Bugfix on 0.1.2.x.
3350 - Stop leaking part of the descriptor when we run into a particularly
3351 unparseable piece of it. Bugfix on 0.1.2.x.
3352 - Unmap the extrainfo cache file on exit.
3355 Changes in version 0.2.0.5-alpha - 2007-08-19
3356 This fifth development snapshot fixes compilation on Windows again;
3357 fixes an obnoxious client-side bug that slowed things down and put
3358 extra load on the network; gets us closer to using the v3 directory
3359 voting scheme; makes it easier for Tor controllers to use cookie-based
3360 authentication; and fixes a variety of other bugs.
3363 - Version 1 directories are no longer generated in full. Instead,
3364 authorities generate and serve "stub" v1 directories that list
3365 no servers. This will stop Tor versions 0.1.0.x and earlier from
3366 working, but (for security reasons) nobody should be running those
3369 o Major bugfixes (compilation, 0.2.0.x):
3370 - Try to fix Win32 compilation again: improve checking for IPv6 types.
3371 - Try to fix MSVC compilation: build correctly on platforms that do
3372 not define s6_addr16 or s6_addr32.
3373 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
3376 o Major bugfixes (stream expiration):
3377 - Expire not-yet-successful application streams in all cases if
3378 they've been around longer than SocksTimeout. Right now there are
3379 some cases where the stream will live forever, demanding a new
3380 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
3383 o Minor features (directory servers):
3384 - When somebody requests a list of statuses or servers, and we have
3385 none of those, return a 404 rather than an empty 200.
3387 o Minor features (directory voting):
3388 - Store v3 consensus status consensuses on disk, and reload them
3391 o Minor features (security):
3392 - Warn about unsafe ControlPort configurations.
3393 - Refuse to start with certain directory authority keys, and
3394 encourage people using them to stop.
3396 o Minor features (controller):
3397 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
3398 is valid before any authentication has been received. It tells
3399 a controller what kind of authentication is expected, and what
3400 protocol is spoken. Implements proposal 119.
3401 - New config option CookieAuthFile to choose a new location for the
3402 cookie authentication file, and config option
3403 CookieAuthFileGroupReadable to make it group-readable.
3405 o Minor features (unit testing):
3406 - Add command-line arguments to unit-test executable so that we can
3407 invoke any chosen test from the command line rather than having
3408 to run the whole test suite at once; and so that we can turn on
3409 logging for the unit tests.
3411 o Minor bugfixes (on 0.1.2.x):
3412 - If we require CookieAuthentication but we fail to write the
3413 cookie file, we would warn but not exit, and end up in a state
3414 where no controller could authenticate. Now we exit.
3415 - If we require CookieAuthentication, stop generating a new cookie
3416 every time we change any piece of our config.
3417 - When loading bandwidth history, do not believe any information in
3418 the future. Fixes bug 434.
3419 - When loading entry guard information, do not believe any information
3421 - When we have our clock set far in the future and generate an
3422 onion key, then re-set our clock to be correct, we should not stop
3423 the onion key from getting rotated.
3424 - Clean up torrc sample config file.
3425 - Do not automatically run configure from autogen.sh. This
3426 non-standard behavior tended to annoy people who have built other
3429 o Minor bugfixes (on 0.2.0.x):
3430 - Fix a bug with AutomapHostsOnResolve that would always cause
3431 the second request to fail. Bug reported by Kate. Bugfix on
3433 - Fix a bug in ADDRMAP controller replies that would sometimes
3434 try to print a NULL. Patch from tup.
3435 - Read v3 directory authority keys from the right location.
3436 - Numerous bugfixes to directory voting code.
3439 Changes in version 0.1.2.16 - 2007-08-01
3440 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
3441 remote attacker in certain situations to rewrite the user's torrc
3442 configuration file. This can completely compromise anonymity of users
3443 in most configurations, including those running the Vidalia bundles,
3444 TorK, etc. Or worse.
3446 o Major security fixes:
3447 - Close immediately after missing authentication on control port;
3448 do not allow multiple authentication attempts.
3451 Changes in version 0.2.0.4-alpha - 2007-08-01
3452 This fourth development snapshot fixes a critical security vulnerability
3453 for most users, specifically those running Vidalia, TorK, etc. Everybody
3454 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
3456 o Major security fixes:
3457 - Close immediately after missing authentication on control port;
3458 do not allow multiple authentication attempts.
3460 o Major bugfixes (compilation):
3461 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
3464 o Minor features (performance):
3465 - Be even more aggressive about releasing RAM from small
3466 empty buffers. Thanks to our free-list code, this shouldn't be too
3467 performance-intensive.
3468 - Disable sentinel-based debugging for buffer code: we squashed all
3469 the bugs that this was supposed to detect a long time ago, and
3470 now its only effect is to change our buffer sizes from nice
3471 powers of two (which platform mallocs tend to like) to values
3472 slightly over powers of two (which make some platform mallocs sad).
3473 - Log malloc statistics from mallinfo() on platforms where it
3477 Changes in version 0.2.0.3-alpha - 2007-07-29
3478 This third development snapshot introduces new experimental
3479 blocking-resistance features and a preliminary version of the v3
3480 directory voting design, and includes many other smaller features
3484 - The first pieces of our "bridge" design for blocking-resistance
3485 are implemented. People can run bridge directory authorities;
3486 people can run bridges; and people can configure their Tor clients
3487 with a set of bridges to use as the first hop into the Tor network.
3488 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
3490 - Create listener connections before we setuid to the configured
3491 User and Group. Now non-Windows users can choose port values
3492 under 1024, start Tor as root, and have Tor bind those ports
3493 before it changes to another UID. (Windows users could already
3495 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
3496 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
3497 on "vserver" accounts. (Patch from coderman.)
3498 - Be even more aggressive about separating local traffic from relayed
3499 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
3501 o Major features (experimental):
3502 - First cut of code for "v3 dir voting": directory authorities will
3503 vote on a common network status document rather than each publishing
3504 their own opinion. This code needs more testing and more corner-case
3505 handling before it's ready for use.
3508 - Directory authorities now call routers Fast if their bandwidth is
3509 at least 100KB/s, and consider their bandwidth adequate to be a
3510 Guard if it is at least 250KB/s, no matter the medians. This fix
3511 complements proposal 107. [Bugfix on 0.1.2.x]
3512 - Directory authorities now never mark more than 3 servers per IP as
3513 Valid and Running. (Implements proposal 109, by Kevin Bauer and
3515 - Minor change to organizationName and commonName generation
3516 procedures in TLS certificates during Tor handshakes, to invalidate
3517 some earlier censorware approaches. This is not a long-term
3518 solution, but applying it will give us a bit of time to look into
3519 the epidemiology of countermeasures as they spread.
3521 o Major bugfixes (directory):
3522 - Rewrite directory tokenization code to never run off the end of
3523 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
3525 o Minor features (controller):
3526 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
3527 match requests to applications. (Patch from Robert Hogan.)
3528 - Report address and port correctly on connections to DNSPort. (Patch
3530 - Add a RESOLVE command to launch hostname lookups. (Original patch
3532 - Add GETINFO status/enough-dir-info to let controllers tell whether
3533 Tor has downloaded sufficient directory information. (Patch
3535 - You can now use the ControlSocket option to tell Tor to listen for
3536 controller connections on Unix domain sockets on systems that
3537 support them. (Patch from Peter Palfrader.)
3538 - STREAM NEW events are generated for DNSPort requests and for
3539 tunneled directory connections. (Patch from Robert Hogan.)
3540 - New "GETINFO address-mappings/*" command to get address mappings
3541 with expiry information. "addr-mappings/*" is now deprecated.
3544 o Minor features (misc):
3545 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
3547 - The tor-gencert tool for v3 directory authorities now creates all
3548 files as readable to the file creator only, and write-protects
3549 the authority identity key.
3550 - When dumping memory usage, list bytes used in buffer memory
3552 - When running with dmalloc, dump more stats on hup and on exit.
3553 - Directory authorities now fail quickly and (relatively) harmlessly
3554 if they generate a network status document that is somehow
3557 o Traffic load balancing improvements:
3558 - If exit bandwidth ever exceeds one third of total bandwidth, then
3559 use the correct formula to weight exit nodes when choosing paths.
3560 (Based on patch from Mike Perry.)
3561 - Choose perfectly fairly among routers when choosing by bandwidth and
3562 weighting by fraction of bandwidth provided by exits. Previously, we
3563 would choose with only approximate fairness, and correct ourselves
3564 if we ran off the end of the list. [Bugfix on 0.1.2.x]
3566 o Performance improvements:
3567 - Be more aggressive with freeing buffer RAM or putting it on the
3569 - Use Critical Sections rather than Mutexes for synchronizing threads
3570 on win32; Mutexes are heavier-weight, and designed for synchronizing
3573 o Deprecated and removed features:
3574 - RedirectExits is now deprecated.
3575 - Stop allowing address masks that do not correspond to bit prefixes.
3576 We have warned about these for a really long time; now it's time
3577 to reject them. (Patch from croup.)
3579 o Minor bugfixes (directory):
3580 - Fix another crash bug related to extra-info caching. (Bug found by
3581 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
3582 - Directories no longer return a "304 not modified" when they don't
3583 have the networkstatus the client asked for. Also fix a memory
3584 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
3585 - We had accidentally labelled 0.1.2.x directory servers as not
3586 suitable for begin_dir requests, and had labelled no directory
3587 servers as suitable for uploading extra-info documents. [Bugfix
3590 o Minor bugfixes (dns):
3591 - Fix a crash when DNSPort is set more than once. (Patch from Robert
3592 Hogan.) [Bugfix on 0.2.0.2-alpha]
3593 - Add DNSPort connections to the global connection list, so that we
3594 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
3596 - Fix a dangling reference that could lead to a crash when DNSPort is
3597 changed or closed (Patch from Robert Hogan.) [Bugfix on
3600 o Minor bugfixes (controller):
3601 - Provide DNS expiry times in GMT, not in local time. For backward
3602 compatibility, ADDRMAP events only provide GMT expiry in an extended
3603 field. "GETINFO address-mappings" always does the right thing.
3604 - Use CRLF line endings properly in NS events.
3605 - Terminate multi-line control events properly. (Original patch
3606 from tup.) [Bugfix on 0.1.2.x-alpha]
3607 - Do not include spaces in SOURCE_ADDR fields in STREAM
3608 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
3611 Changes in version 0.1.2.15 - 2007-07-17
3612 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
3613 problems, fixes compilation on BSD, and fixes a variety of other
3614 bugs. Everybody should upgrade.
3616 o Major bugfixes (compilation):
3617 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
3619 o Major bugfixes (crashes):
3620 - Try even harder not to dereference the first character after
3621 an mmap(). Reported by lodger.
3622 - Fix a crash bug in directory authorities when we re-number the
3623 routerlist while inserting a new router.
3624 - When the cached-routers file is an even multiple of the page size,
3625 don't run off the end and crash. (Fixes bug 455; based on idea
3627 - Fix eventdns.c behavior on Solaris: It is critical to include
3628 orconfig.h _before_ sys/types.h, so that we can get the expected
3629 definition of _FILE_OFFSET_BITS.
3631 o Major bugfixes (security):
3632 - Fix a possible buffer overrun when using BSD natd support. Bug
3634 - When sending destroy cells from a circuit's origin, don't include
3635 the reason for tearing down the circuit. The spec says we didn't,
3636 and now we actually don't. Reported by lodger.
3637 - Keep streamids from different exits on a circuit separate. This
3638 bug may have allowed other routers on a given circuit to inject
3639 cells into streams. Reported by lodger; fixes bug 446.
3640 - If there's a never-before-connected-to guard node in our list,
3641 never choose any guards past it. This way we don't expand our
3642 guard list unless we need to.
3644 o Minor bugfixes (guard nodes):
3645 - Weight guard selection by bandwidth, so that low-bandwidth nodes
3646 don't get overused as guards.
3648 o Minor bugfixes (directory):
3649 - Correctly count the number of authorities that recommend each
3650 version. Previously, we were under-counting by 1.
3651 - Fix a potential crash bug when we load many server descriptors at
3652 once and some of them make others of them obsolete. Fixes bug 458.
3654 o Minor bugfixes (hidden services):
3655 - Stop tearing down the whole circuit when the user asks for a
3656 connection to a port that the hidden service didn't configure.
3659 o Minor bugfixes (misc):
3660 - On Windows, we were preventing other processes from reading
3661 cached-routers while Tor was running. Reported by janbar.
3662 - Fix a possible (but very unlikely) bug in picking routers by
3663 bandwidth. Add a log message to confirm that it is in fact
3664 unlikely. Patch from lodger.
3665 - Backport a couple of memory leak fixes.
3666 - Backport miscellaneous cosmetic bugfixes.
3669 Changes in version 0.2.0.2-alpha - 2007-06-02
3670 o Major bugfixes on 0.2.0.1-alpha:
3671 - Fix an assertion failure related to servers without extra-info digests.
3672 Resolves bugs 441 and 442.
3674 o Minor features (directory):
3675 - Support "If-Modified-Since" when answering HTTP requests for
3676 directories, running-routers documents, and network-status documents.
3677 (There's no need to support it for router descriptors, since those
3678 are downloaded by descriptor digest.)
3680 o Minor build issues:
3681 - Clear up some MIPSPro compiler warnings.
3682 - When building from a tarball on a machine that happens to have SVK
3683 installed, report the micro-revision as whatever version existed
3684 in the tarball, not as "x".
3687 Changes in version 0.2.0.1-alpha - 2007-06-01
3688 This early development snapshot provides new features for people running
3689 Tor as both a client and a server (check out the new RelayBandwidth
3690 config options); lets Tor run as a DNS proxy; and generally moves us
3691 forward on a lot of fronts.
3693 o Major features, server usability:
3694 - New config options RelayBandwidthRate and RelayBandwidthBurst:
3695 a separate set of token buckets for relayed traffic. Right now
3696 relayed traffic is defined as answers to directory requests, and
3697 OR connections that don't have any local circuits on them.
3699 o Major features, client usability:
3700 - A client-side DNS proxy feature to replace the need for
3701 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
3702 for DNS requests on port 9999, use the Tor network to resolve them
3703 anonymously, and send the reply back like a regular DNS server.
3704 The code still only implements a subset of DNS.
3705 - Make PreferTunneledDirConns and TunnelDirConns work even when
3706 we have no cached directory info. This means Tor clients can now
3707 do all of their connections protected by TLS.
3709 o Major features, performance and efficiency:
3710 - Directory authorities accept and serve "extra info" documents for
3711 routers. These documents contain fields from router descriptors
3712 that aren't usually needed, and that use a lot of excess
3713 bandwidth. Once these fields are removed from router descriptors,
3714 the bandwidth savings should be about 60%. [Partially implements
3716 - Servers upload extra-info documents to any authority that accepts
3717 them. Authorities (and caches that have been configured to download
3718 extra-info documents) download them as needed. [Partially implements
3720 - Change the way that Tor buffers data that it is waiting to write.
3721 Instead of queueing data cells in an enormous ring buffer for each
3722 client->OR or OR->OR connection, we now queue cells on a separate
3723 queue for each circuit. This lets us use less slack memory, and
3724 will eventually let us be smarter about prioritizing different kinds
3726 - Use memory pools to allocate cells with better speed and memory
3727 efficiency, especially on platforms where malloc() is inefficient.
3728 - Stop reading on edge connections when their corresponding circuit
3729 buffers are full; start again as the circuits empty out.
3731 o Major features, other:
3732 - Add an HSAuthorityRecordStats option that hidden service authorities
3733 can use to track statistics of overall hidden service usage without
3734 logging information that would be very useful to an attacker.
3735 - Start work implementing multi-level keys for directory authorities:
3736 Add a standalone tool to generate key certificates. (Proposal 103.)
3739 - Directory authorities now call routers Stable if they have an
3740 uptime of at least 30 days, even if that's not the median uptime
3741 in the network. Implements proposal 107, suggested by Kevin Bauer
3744 o Minor fixes (resource management):
3745 - Count the number of open sockets separately from the number
3746 of active connection_t objects. This will let us avoid underusing
3747 our allocated connection limit.
3748 - We no longer use socket pairs to link an edge connection to an
3749 anonymous directory connection or a DirPort test connection.
3750 Instead, we track the link internally and transfer the data
3751 in-process. This saves two sockets per "linked" connection (at the
3752 client and at the server), and avoids the nasty Windows socketpair()
3754 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
3755 for every single inactive connection_t. Free items from the
3756 4k/16k-buffer free lists when they haven't been used for a while.
3758 o Minor features (build):
3759 - Make autoconf search for libevent, openssl, and zlib consistently.
3760 - Update deprecated macros in configure.in.
3761 - When warning about missing headers, tell the user to let us
3762 know if the compile succeeds anyway, so we can downgrade the
3764 - Include the current subversion revision as part of the version
3765 string: either fetch it directly if we're in an SVN checkout, do
3766 some magic to guess it if we're in an SVK checkout, or use
3767 the last-detected version if we're building from a .tar.gz.
3768 Use this version consistently in log messages.
3770 o Minor features (logging):
3771 - Always prepend "Bug: " to any log message about a bug.
3772 - Put a platform string (e.g. "Linux i686") in the startup log
3773 message, so when people paste just their logs, we know if it's
3774 OpenBSD or Windows or what.
3775 - When logging memory usage, break down memory used in buffers by
3778 o Minor features (directory system):
3779 - New config option V2AuthoritativeDirectory that all directory
3780 authorities should set. This will let future authorities choose
3781 not to serve V2 directory information.
3782 - Directory authorities allow multiple router descriptors and/or extra
3783 info documents to be uploaded in a single go. This will make
3784 implementing proposal 104 simpler.
3786 o Minor features (controller):
3787 - Add a new config option __DisablePredictedCircuits designed for
3788 use by the controller, when we don't want Tor to build any circuits
3790 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
3791 so we can exit from the middle of the circuit.
3792 - Implement "getinfo status/circuit-established".
3793 - Implement "getinfo status/version/..." so a controller can tell
3794 whether the current version is recommended, and whether any versions
3795 are good, and how many authorities agree. (Patch from shibz.)
3797 o Minor features (hidden services):
3798 - Allow multiple HiddenServicePort directives with the same virtual
3799 port; when they occur, the user is sent round-robin to one
3800 of the target ports chosen at random. Partially fixes bug 393 by
3801 adding limited ad-hoc round-robining.
3803 o Minor features (other):
3805 - Add a new AutomapHostsOnResolve option: when it is enabled, any
3806 resolve request for hosts matching a given pattern causes Tor to
3807 generate an internal virtual address mapping for that host. This
3808 allows DNSPort to work sensibly with hidden service users. By
3809 default, .exit and .onion addresses are remapped; the list of
3810 patterns can be reconfigured with AutomapHostsSuffixes.
3811 - Add an "-F" option to tor-resolve to force a resolve for a .onion
3812 address. Thanks to the AutomapHostsOnResolve option, this is no
3813 longer a completely silly thing to do.
3814 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
3815 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
3816 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
3817 minus 1 byte: the actual maximum declared bandwidth.
3820 - Removed support for the old binary "version 0" controller protocol.
3821 This has been deprecated since 0.1.1, and warnings have been issued
3822 since 0.1.2. When we encounter a v0 control message, we now send
3823 back an error and close the connection.
3824 - Remove the old "dns worker" server DNS code: it hasn't been default
3825 since 0.1.2.2-alpha, and all the servers seem to be using the new
3828 o Minor bugfixes (portability):
3829 - Even though Windows is equally happy with / and \ as path separators,
3830 try to use \ consistently on Windows and / consistently on Unix: it
3831 makes the log messages nicer.
3832 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
3833 - Read resolv.conf files correctly on platforms where read() returns
3834 partial results on small file reads.
3836 o Minor bugfixes (directory):
3837 - Correctly enforce that elements of directory objects do not appear
3838 more often than they are allowed to appear.
3839 - When we are reporting the DirServer line we just parsed, we were
3840 logging the second stanza of the key fingerprint, not the first.
3842 o Minor bugfixes (logging):
3843 - When we hit an EOF on a log (probably because we're shutting down),
3844 don't try to remove the log from the list: just mark it as
3845 unusable. (Bulletproofs against bug 222.)
3847 o Minor bugfixes (other):
3848 - In the exitlist script, only consider the most recently published
3849 server descriptor for each server. Also, when the user requests
3850 a list of servers that _reject_ connections to a given address,
3851 explicitly exclude the IPs that also have servers that accept
3852 connections to that address. (Resolves bug 405.)
3853 - Stop allowing hibernating servers to be "stable" or "fast".
3854 - On Windows, we were preventing other processes from reading
3855 cached-routers while Tor was running. (Reported by janbar)
3856 - Make the NodeFamilies config option work. (Reported by
3857 lodger -- it has never actually worked, even though we added it
3859 - Check return values from pthread_mutex functions.
3860 - Don't save non-general-purpose router descriptors to the disk cache,
3861 because we have no way of remembering what their purpose was when
3863 - Add even more asserts to hunt down bug 417.
3864 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
3865 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
3866 Add a log message to confirm that it is in fact unlikely.
3868 o Minor bugfixes (controller):
3869 - Make 'getinfo fingerprint' return a 551 error if we're not a
3870 server, so we match what the control spec claims we do. Reported
3872 - Fix a typo in an error message when extendcircuit fails that
3873 caused us to not follow the \r\n-based delimiter protocol. Reported
3876 o Code simplifications and refactoring:
3877 - Stop passing around circuit_t and crypt_path_t pointers that are
3878 implicit in other procedure arguments.
3879 - Drop the old code to choke directory connections when the
3880 corresponding OR connections got full: thanks to the cell queue
3881 feature, OR conns don't get full any more.
3882 - Make dns_resolve() handle attaching connections to circuits
3883 properly, so the caller doesn't have to.
3884 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
3885 - Keep the connection array as a dynamic smartlist_t, rather than as
3886 a fixed-sized array. This is important, as the number of connections
3887 is becoming increasingly decoupled from the number of sockets.
3890 Changes in version 0.1.2.14 - 2007-05-25
3891 Tor 0.1.2.14 changes the addresses of two directory authorities (this
3892 change especially affects those who serve or use hidden services),
3893 and fixes several other crash- and security-related bugs.
3895 o Directory authority changes:
3896 - Two directory authorities (moria1 and moria2) just moved to new
3897 IP addresses. This change will particularly affect those who serve
3898 or use hidden services.
3900 o Major bugfixes (crashes):
3901 - If a directory server runs out of space in the connection table
3902 as it's processing a begin_dir request, it will free the exit stream
3903 but leave it attached to the circuit, leading to unpredictable
3904 behavior. (Reported by seeess, fixes bug 425.)
3905 - Fix a bug in dirserv_remove_invalid() that would cause authorities
3906 to corrupt memory under some really unlikely scenarios.
3907 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
3908 - Avoid segfaults when reading from mmaped descriptor file. (Reported
3911 o Major bugfixes (security):
3912 - When choosing an entry guard for a circuit, avoid using guards
3913 that are in the same family as the chosen exit -- not just guards
3914 that are exactly the chosen exit. (Reported by lodger.)
3916 o Major bugfixes (resource management):
3917 - If a directory authority is down, skip it when deciding where to get
3918 networkstatus objects or descriptors. Otherwise we keep asking
3919 every 10 seconds forever. Fixes bug 384.
3920 - Count it as a failure if we fetch a valid network-status but we
3921 don't want to keep it. Otherwise we'll keep fetching it and keep
3922 not wanting to keep it. Fixes part of bug 422.
3923 - If all of our dirservers have given us bad or no networkstatuses
3924 lately, then stop hammering them once per minute even when we
3925 think they're failed. Fixes another part of bug 422.
3928 - Actually set the purpose correctly for descriptors inserted with
3930 - When we have k non-v2 authorities in our DirServer config,
3931 we ignored the last k authorities in the list when updating our
3933 - Correctly back-off from requesting router descriptors that we are
3934 having a hard time downloading.
3935 - Read resolv.conf files correctly on platforms where read() returns
3936 partial results on small file reads.
3937 - Don't rebuild the entire router store every time we get 32K of
3938 routers: rebuild it when the journal gets very large, or when
3939 the gaps in the store get very large.
3942 - When routers publish SVN revisions in their router descriptors,
3943 authorities now include those versions correctly in networkstatus
3945 - Warn when using a version of libevent before 1.3b to run a server on
3946 OSX or BSD: these versions interact badly with userspace threads.
3949 Changes in version 0.1.2.13 - 2007-04-24
3950 This release features some major anonymity fixes, such as safer path
3951 selection; better client performance; faster bootstrapping, better
3952 address detection, and better DNS support for servers; write limiting as
3953 well as read limiting to make servers easier to run; and a huge pile of
3954 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
3956 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
3957 of the Freenode IRC network, remembering his patience and vision for
3958 free speech on the Internet.
3961 - Fix a memory leak when we ask for "all" networkstatuses and we
3962 get one we don't recognize.
3963 - Add more asserts to hunt down bug 417.
3964 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
3967 Changes in version 0.1.2.12-rc - 2007-03-16
3969 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
3970 directory information requested inside Tor connections (i.e. via
3971 begin_dir cells). It only triggered when the same connection was
3972 serving other data at the same time. Reported by seeess.
3975 - When creating a circuit via the controller, send a 'launched'
3976 event when we're done, so we follow the spec better.
3979 Changes in version 0.1.2.11-rc - 2007-03-15
3980 o Minor bugfixes (controller), reported by daejees:
3981 - Correct the control spec to match how the code actually responds
3982 to 'getinfo addr-mappings/*'.
3983 - The control spec described a GUARDS event, but the code
3984 implemented a GUARD event. Standardize on GUARD, but let people
3988 Changes in version 0.1.2.10-rc - 2007-03-07
3989 o Major bugfixes (Windows):
3990 - Do not load the NT services library functions (which may not exist)
3991 just to detect if we're a service trying to shut down. Now we run
3992 on Win98 and friends again.
3994 o Minor bugfixes (other):
3995 - Clarify a couple of log messages.
3996 - Fix a misleading socks5 error number.
3999 Changes in version 0.1.2.9-rc - 2007-03-02
4000 o Major bugfixes (Windows):
4001 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
4002 of the usual GCC "%llu". This prevents a bug when saving 64-bit
4003 int configuration values: the high-order 32 bits would get
4004 truncated. In particular, we were being bitten by the default
4005 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
4006 and maybe also bug 397.)
4008 o Minor bugfixes (performance):
4009 - Use OpenSSL's AES implementation on platforms where it's faster.
4010 This could save us as much as 10% CPU usage.
4012 o Minor bugfixes (server):
4013 - Do not rotate onion key immediately after setting it for the first
4016 o Minor bugfixes (directory authorities):
4017 - Stop calling servers that have been hibernating for a long time
4018 "stable". Also, stop letting hibernating or obsolete servers affect
4019 uptime and bandwidth cutoffs.
4020 - Stop listing hibernating servers in the v1 directory.
4022 o Minor bugfixes (hidden services):
4023 - Upload hidden service descriptors slightly less often, to reduce
4024 load on authorities.
4026 o Minor bugfixes (other):
4027 - Fix an assert that could trigger if a controller quickly set then
4028 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
4029 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
4031 - Fix a potential race condition in the rpm installer. Found by
4033 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
4034 of 2 as indicating that the server is completely bad; it sometimes
4035 means that the server is just bad for the request in question. (may fix
4036 the last of bug 326.)
4037 - Disable encrypted directory connections when we don't have a server
4038 descriptor for the destination. We'll get this working again in
4042 Changes in version 0.1.2.8-beta - 2007-02-26
4043 o Major bugfixes (crashes):
4044 - Stop crashing when the controller asks us to resetconf more than
4045 one config option at once. (Vidalia 0.0.11 does this.)
4046 - Fix a crash that happened on Win98 when we're given command-line
4047 arguments: don't try to load NT service functions from advapi32.dll
4048 except when we need them. (Bug introduced in 0.1.2.7-alpha;
4050 - Fix a longstanding obscure crash bug that could occur when
4051 we run out of DNS worker processes. (Resolves bug 390.)
4053 o Major bugfixes (hidden services):
4054 - Correctly detect whether hidden service descriptor downloads are
4055 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
4057 o Major bugfixes (accounting):
4058 - When we start during an accounting interval before it's time to wake
4059 up, remember to wake up at the correct time. (May fix bug 342.)
4061 o Minor bugfixes (controller):
4062 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
4063 clear the corresponding on_circuit variable, and remember later
4064 that we don't need to send a redundant CLOSED event. (Resolves part
4066 - Report events where a resolve succeeded or where we got a socks
4067 protocol error correctly, rather than calling both of them
4069 - Change reported stream target addresses to IP consistently when
4070 we finally get the IP from an exit node.
4071 - Send log messages to the controller even if they happen to be very
4074 o Minor bugfixes (other):
4075 - Display correct results when reporting which versions are
4076 recommended, and how recommended they are. (Resolves bug 383.)
4077 - Improve our estimates for directory bandwidth to be less random:
4078 guess that an unrecognized directory will have the average bandwidth
4079 from all known directories, not that it will have the average
4080 bandwidth from those directories earlier than it on the list.
4081 - If we start a server with ClientOnly 1, then set ClientOnly to 0
4082 and hup, stop triggering an assert based on an empty onion_key.
4083 - On platforms with no working mmap() equivalent, don't warn the
4084 user when cached-routers doesn't exist.
4085 - Warn the user when mmap() [or its equivalent] fails for some reason
4086 other than file-not-found.
4087 - Don't warn the user when cached-routers.new doesn't exist: that's
4088 perfectly fine when starting up for the first time.
4089 - When EntryNodes are configured, rebuild the guard list to contain,
4090 in order: the EntryNodes that were guards before; the rest of the
4091 EntryNodes; the nodes that were guards before.
4092 - Mask out all signals in sub-threads; only the libevent signal
4093 handler should be processing them. This should prevent some crashes
4094 on some machines using pthreads. (Patch from coderman.)
4095 - Fix switched arguments on memset in the implementation of
4096 tor_munmap() for systems with no mmap() call.
4097 - When Tor receives a router descriptor that it asked for, but
4098 no longer wants (because it has received fresh networkstatuses
4099 in the meantime), do not warn the user. Cache the descriptor if
4100 we're a cache; drop it if we aren't.
4101 - Make earlier entry guards _really_ get retried when the network
4103 - On a malformed DNS reply, always give an error to the corresponding
4105 - Build with recent libevents on platforms that do not define the
4106 nonstandard types "u_int8_t" and friends.
4108 o Minor features (controller):
4109 - Warn the user when an application uses the obsolete binary v0
4110 control protocol. We're planning to remove support for it during
4111 the next development series, so it's good to give people some
4113 - Add STREAM_BW events to report per-entry-stream bandwidth
4114 use. (Patch from Robert Hogan.)
4115 - Rate-limit SIGNEWNYM signals in response to controllers that
4116 impolitely generate them for every single stream. (Patch from
4117 mwenge; closes bug 394.)
4118 - Make REMAP stream events have a SOURCE (cache or exit), and
4119 make them generated in every case where we get a successful
4120 connected or resolved cell.
4122 o Minor bugfixes (performance):
4123 - Call router_have_min_dir_info half as often. (This is showing up in
4124 some profiles, but not others.)
4125 - When using GCC, make log_debug never get called at all, and its
4126 arguments never get evaluated, when no debug logs are configured.
4127 (This is showing up in some profiles, but not others.)
4130 - Remove some never-implemented options. Mark PathlenCoinWeight as
4132 - Implement proposal 106: Stop requiring clients to have well-formed
4133 certificates; stop checking nicknames in certificates. (Clients
4134 have certificates so that they can look like Tor servers, but in
4135 the future we might want to allow them to look like regular TLS
4136 clients instead. Nicknames in certificates serve no purpose other
4137 than making our protocol easier to recognize on the wire.)
4138 - Revise messages on handshake failure again to be even more clear about
4139 which are incoming connections and which are outgoing.
4140 - Discard any v1 directory info that's over 1 month old (for
4141 directories) or over 1 week old (for running-routers lists).
4142 - Do not warn when individual nodes in the configuration's EntryNodes,
4143 ExitNodes, etc are down: warn only when all possible nodes
4144 are down. (Fixes bug 348.)
4145 - Always remove expired routers and networkstatus docs before checking
4146 whether we have enough information to build circuits. (Fixes
4148 - Put a lower-bound on MaxAdvertisedBandwidth.
4151 Changes in version 0.1.2.7-alpha - 2007-02-06
4152 o Major bugfixes (rate limiting):
4153 - Servers decline directory requests much more aggressively when
4154 they're low on bandwidth. Otherwise they end up queueing more and
4155 more directory responses, which can't be good for latency.
4156 - But never refuse directory requests from local addresses.
4157 - Fix a memory leak when sending a 503 response for a networkstatus
4159 - Be willing to read or write on local connections (e.g. controller
4160 connections) even when the global rate limiting buckets are empty.
4161 - If our system clock jumps back in time, don't publish a negative
4162 uptime in the descriptor. Also, don't let the global rate limiting
4163 buckets go absurdly negative.
4164 - Flush local controller connection buffers periodically as we're
4165 writing to them, so we avoid queueing 4+ megabytes of data before
4168 o Major bugfixes (NT services):
4169 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
4170 command-line flag so that admins can override the default by saying
4171 "tor --service install --user "SomeUser"". This will not affect
4172 existing installed services. Also, warn the user that the service
4173 will look for its configuration file in the service user's
4174 %appdata% directory. (We can't do the 'hardwire the user's appdata
4175 directory' trick any more, since we may not have read access to that
4178 o Major bugfixes (other):
4179 - Previously, we would cache up to 16 old networkstatus documents
4180 indefinitely, if they came from nontrusted authorities. Now we
4181 discard them if they are more than 10 days old.
4182 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
4184 - Detect and reject malformed DNS responses containing circular
4186 - If exits are rare enough that we're not marking exits as guards,
4187 ignore exit bandwidth when we're deciding the required bandwidth
4189 - When we're handling a directory connection tunneled over Tor,
4190 don't fill up internal memory buffers with all the data we want
4191 to tunnel; instead, only add it if the OR connection that will
4192 eventually receive it has some room for it. (This can lead to
4193 slowdowns in tunneled dir connections; a better solution will have
4196 o Minor bugfixes (dns):
4197 - Add some defensive programming to eventdns.c in an attempt to catch
4198 possible memory-stomping bugs.
4199 - Detect and reject DNS replies containing IPv4 or IPv6 records with
4200 an incorrect number of bytes. (Previously, we would ignore the
4202 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
4203 in the correct order, and doesn't crash.
4204 - Free memory held in recently-completed DNS lookup attempts on exit.
4205 This was not a memory leak, but may have been hiding memory leaks.
4206 - Handle TTL values correctly on reverse DNS lookups.
4207 - Treat failure to parse resolv.conf as an error.
4209 o Minor bugfixes (other):
4210 - Fix crash with "tor --list-fingerprint" (reported by seeess).
4211 - When computing clock skew from directory HTTP headers, consider what
4212 time it was when we finished asking for the directory, not what
4214 - Expire socks connections if they spend too long waiting for the
4215 handshake to finish. Previously we would let them sit around for
4216 days, if the connecting application didn't close them either.
4217 - And if the socks handshake hasn't started, don't send a
4218 "DNS resolve socks failed" handshake reply; just close it.
4219 - Stop using C functions that OpenBSD's linker doesn't like.
4220 - Don't launch requests for descriptors unless we have networkstatuses
4221 from at least half of the authorities. This delays the first
4222 download slightly under pathological circumstances, but can prevent
4223 us from downloading a bunch of descriptors we don't need.
4224 - Do not log IPs with TLS failures for incoming TLS
4225 connections. (Fixes bug 382.)
4226 - If the user asks to use invalid exit nodes, be willing to use
4228 - Stop using the reserved ac_cv namespace in our configure script.
4229 - Call stat() slightly less often; use fstat() when possible.
4230 - Refactor the way we handle pending circuits when an OR connection
4231 completes or fails, in an attempt to fix a rare crash bug.
4232 - Only rewrite a conn's address based on X-Forwarded-For: headers
4233 if it's a parseable public IP address; and stop adding extra quotes
4234 to the resulting address.
4237 - Weight directory requests by advertised bandwidth. Now we can
4238 let servers enable write limiting but still allow most clients to
4239 succeed at their directory requests. (We still ignore weights when
4240 choosing a directory authority; I hope this is a feature.)
4243 - Create a new file ReleaseNotes which was the old ChangeLog. The
4244 new ChangeLog file now includes the summaries for all development
4246 - Check for addresses with invalid characters at the exit as well
4247 as at the client, and warn less verbosely when they fail. You can
4248 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
4249 - Adapt a patch from goodell to let the contrib/exitlist script
4250 take arguments rather than require direct editing.
4251 - Inform the server operator when we decide not to advertise a
4252 DirPort due to AccountingMax enabled or a low BandwidthRate. It
4253 was confusing Zax, so now we're hopefully more helpful.
4254 - Bring us one step closer to being able to establish an encrypted
4255 directory tunnel without knowing a descriptor first. Still not
4256 ready yet. As part of the change, now assume we can use a
4257 create_fast cell if we don't know anything about a router.
4258 - Allow exit nodes to use nameservers running on ports other than 53.
4259 - Servers now cache reverse DNS replies.
4260 - Add an --ignore-missing-torrc command-line option so that we can
4261 get the "use sensible defaults if the configuration file doesn't
4262 exist" behavior even when specifying a torrc location on the command
4265 o Minor features (controller):
4266 - Track reasons for OR connection failure; make these reasons
4267 available via the controller interface. (Patch from Mike Perry.)
4268 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
4269 can learn when clients are sending malformed hostnames to Tor.
4270 - Clean up documentation for controller status events.
4271 - Add a REMAP status to stream events to note that a stream's
4272 address has changed because of a cached address or a MapAddress
4276 Changes in version 0.1.2.6-alpha - 2007-01-09
4278 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
4279 connection handles more than 4 gigs in either direction, we crash.
4280 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
4281 advertised exit node, somebody might try to exit from us when
4282 we're bootstrapping and before we've built our descriptor yet.
4283 Refuse the connection rather than crashing.
4286 - Warn if we (as a server) find that we've resolved an address that we
4287 weren't planning to resolve.
4288 - Warn that using select() on any libevent version before 1.1 will be
4289 unnecessarily slow (even for select()).
4290 - Flush ERR-level controller status events just like we currently
4291 flush ERR-level log events, so that a Tor shutdown doesn't prevent
4292 the controller from learning about current events.
4294 o Minor features (more controller status events):
4295 - Implement EXTERNAL_ADDRESS server status event so controllers can
4296 learn when our address changes.
4297 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
4298 can learn when directories reject our descriptor.
4299 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
4300 can learn when a client application is speaking a non-socks protocol
4302 - Implement DANGEROUS_SOCKS client status event so controllers
4303 can learn when a client application is leaking DNS addresses.
4304 - Implement BUG general status event so controllers can learn when
4305 Tor is unhappy about its internal invariants.
4306 - Implement CLOCK_SKEW general status event so controllers can learn
4307 when Tor thinks the system clock is set incorrectly.
4308 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
4309 server status events so controllers can learn when their descriptors
4310 are accepted by a directory.
4311 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
4312 server status events so controllers can learn about Tor's progress in
4313 deciding whether it's reachable from the outside.
4314 - Implement BAD_LIBEVENT general status event so controllers can learn
4315 when we have a version/method combination in libevent that needs to
4317 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
4318 and DNS_USELESS server status events so controllers can learn
4319 about changes to DNS server status.
4321 o Minor features (directory):
4322 - Authorities no longer recommend exits as guards if this would shift
4323 too much load to the exit nodes.
4326 Changes in version 0.1.2.5-alpha - 2007-01-06
4328 - Enable write limiting as well as read limiting. Now we sacrifice
4329 capacity if we're pushing out lots of directory traffic, rather
4330 than overrunning the user's intended bandwidth limits.
4331 - Include TLS overhead when counting bandwidth usage; previously, we
4332 would count only the bytes sent over TLS, but not the bytes used
4334 - Support running the Tor service with a torrc not in the same
4335 directory as tor.exe and default to using the torrc located in
4336 the %appdata%\Tor\ of the user who installed the service. Patch
4338 - Servers now check for the case when common DNS requests are going to
4339 wildcarded addresses (i.e. all getting the same answer), and change
4340 their exit policy to reject *:* if it's happening.
4341 - Implement BEGIN_DIR cells, so we can connect to the directory
4342 server via TLS to do encrypted directory requests rather than
4343 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
4344 config options if you like.
4346 o Minor features (config and docs):
4347 - Start using the state file to store bandwidth accounting data:
4348 the bw_accounting file is now obsolete. We'll keep generating it
4349 for a while for people who are still using 0.1.2.4-alpha.
4350 - Try to batch changes to the state file so that we do as few
4351 disk writes as possible while still storing important things in
4353 - The state file and the bw_accounting file get saved less often when
4354 the AvoidDiskWrites config option is set.
4355 - Make PIDFile work on Windows (untested).
4356 - Add internal descriptions for a bunch of configuration options:
4357 accessible via controller interface and in comments in saved
4359 - Reject *:563 (NNTPS) in the default exit policy. We already reject
4360 NNTP by default, so this seems like a sensible addition.
4361 - Clients now reject hostnames with invalid characters. This should
4362 avoid some inadvertent info leaks. Add an option
4363 AllowNonRFC953Hostnames to disable this behavior, in case somebody
4364 is running a private network with hosts called @, !, and #.
4365 - Add a maintainer script to tell us which options are missing
4366 documentation: "make check-docs".
4367 - Add a new address-spec.txt document to describe our special-case
4368 addresses: .exit, .onion, and .noconnnect.
4370 o Minor features (DNS):
4371 - Ongoing work on eventdns infrastructure: now it has dns server
4372 and ipv6 support. One day Tor will make use of it.
4373 - Add client-side caching for reverse DNS lookups.
4374 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
4375 - When we change nameservers or IP addresses, reset and re-launch
4376 our tests for DNS hijacking.
4378 o Minor features (directory):
4379 - Authorities now specify server versions in networkstatus. This adds
4380 about 2% to the size of compressed networkstatus docs, and allows
4381 clients to tell which servers support BEGIN_DIR and which don't.
4382 The implementation is forward-compatible with a proposed future
4383 protocol version scheme not tied to Tor versions.
4384 - DirServer configuration lines now have an orport= option so
4385 clients can open encrypted tunnels to the authorities without
4386 having downloaded their descriptors yet. Enabled for moria1,
4387 moria2, tor26, and lefkada now in the default configuration.
4388 - Directory servers are more willing to send a 503 "busy" if they
4389 are near their write limit, especially for v1 directory requests.
4390 Now they can use their limited bandwidth for actual Tor traffic.
4391 - Clients track responses with status 503 from dirservers. After a
4392 dirserver has given us a 503, we try not to use it until an hour has
4393 gone by, or until we have no dirservers that haven't given us a 503.
4394 - When we get a 503 from a directory, and we're not a server, we don't
4395 count the failure against the total number of failures allowed
4396 for the thing we're trying to download.
4397 - Report X-Your-Address-Is correctly from tunneled directory
4398 connections; don't report X-Your-Address-Is when it's an internal
4399 address; and never believe reported remote addresses when they're
4401 - Protect against an unlikely DoS attack on directory servers.
4402 - Add a BadDirectory flag to network status docs so that authorities
4403 can (eventually) tell clients about caches they believe to be
4406 o Minor features (controller):
4407 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
4408 - Reimplement GETINFO so that info/names stays in sync with the
4410 - Implement "GETINFO fingerprint".
4411 - Implement "SETEVENTS GUARD" so controllers can get updates on
4412 entry guard status as it changes.
4414 o Minor features (clean up obsolete pieces):
4415 - Remove some options that have been deprecated since at least
4416 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
4417 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
4419 - We no longer look for identity and onion keys in "identity.key" and
4420 "onion.key" -- these were replaced by secret_id_key and
4421 secret_onion_key in 0.0.8pre1.
4422 - We no longer require unrecognized directory entries to be
4425 o Major bugfixes (security):
4426 - Stop sending the HttpProxyAuthenticator string to directory
4427 servers when directory connections are tunnelled through Tor.
4428 - Clients no longer store bandwidth history in the state file.
4429 - Do not log introduction points for hidden services if SafeLogging
4431 - When generating bandwidth history, round down to the nearest
4432 1k. When storing accounting data, round up to the nearest 1k.
4433 - When we're running as a server, remember when we last rotated onion
4434 keys, so that we will rotate keys once they're a week old even if
4435 we never stay up for a week ourselves.
4437 o Major bugfixes (other):
4438 - Fix a longstanding bug in eventdns that prevented the count of
4439 timed-out resolves from ever being reset. This bug caused us to
4440 give up on a nameserver the third time it timed out, and try it
4441 10 seconds later... and to give up on it every time it timed out
4443 - Take out the '5 second' timeout from the connection retry
4444 schedule. Now the first connect attempt will wait a full 10
4445 seconds before switching to a new circuit. Perhaps this will help
4446 a lot. Based on observations from Mike Perry.
4447 - Fix a bug on the Windows implementation of tor_mmap_file() that
4448 would prevent the cached-routers file from ever loading. Reported
4452 - Fix an assert failure when a directory authority sets
4453 AuthDirRejectUnlisted and then receives a descriptor from an
4454 unlisted router. Reported by seeess.
4455 - Avoid a double-free when parsing malformed DirServer lines.
4456 - Fix a bug when a BSD-style PF socket is first used. Patch from
4458 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
4459 to resolve an address at a given exit node even when they ask for
4461 - Servers no longer ever list themselves in their "family" line,
4462 even if configured to do so. This makes it easier to configure
4463 family lists conveniently.
4464 - When running as a server, don't fall back to 127.0.0.1 when no
4465 nameservers are configured in /etc/resolv.conf; instead, make the
4466 user fix resolv.conf or specify nameservers explicitly. (Resolves
4468 - Stop accepting certain malformed ports in configured exit policies.
4469 - Don't re-write the fingerprint file every restart, unless it has
4471 - Stop warning when a single nameserver fails: only warn when _all_ of
4472 our nameservers have failed. Also, when we only have one nameserver,
4473 raise the threshold for deciding that the nameserver is dead.
4474 - Directory authorities now only decide that routers are reachable
4475 if their identity keys are as expected.
4476 - When the user uses bad syntax in the Log config line, stop
4477 suggesting other bad syntax as a replacement.
4478 - Correctly detect ipv6 DNS capability on OpenBSD.
4480 o Minor bugfixes (controller):
4481 - Report the circuit number correctly in STREAM CLOSED events. Bug
4482 reported by Mike Perry.
4483 - Do not report bizarre values for results of accounting GETINFOs
4484 when the last second's write or read exceeds the allotted bandwidth.
4485 - Report "unrecognized key" rather than an empty string when the
4486 controller tries to fetch a networkstatus that doesn't exist.
4489 Changes in version 0.1.1.26 - 2006-12-14
4490 o Security bugfixes:
4491 - Stop sending the HttpProxyAuthenticator string to directory
4492 servers when directory connections are tunnelled through Tor.
4493 - Clients no longer store bandwidth history in the state file.
4494 - Do not log introduction points for hidden services if SafeLogging
4498 - Fix an assert failure when a directory authority sets
4499 AuthDirRejectUnlisted and then receives a descriptor from an
4500 unlisted router (reported by seeess).
4503 Changes in version 0.1.2.4-alpha - 2006-12-03
4505 - Add support for using natd; this allows FreeBSDs earlier than
4506 5.1.2 to have ipfw send connections through Tor without using
4507 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
4510 - Make all connections to addresses of the form ".noconnect"
4511 immediately get closed. This lets application/controller combos
4512 successfully test whether they're talking to the same Tor by
4513 watching for STREAM events.
4514 - Make cross.sh cross-compilation script work even when autogen.sh
4515 hasn't been run. (Patch from Michael Mohr.)
4516 - Statistics dumped by -USR2 now include a breakdown of public key
4517 operations, for profiling.
4520 - Fix a major leak when directory authorities parse their
4521 approved-routers list, a minor memory leak when we fail to pick
4522 an exit node, and a few rare leaks on errors.
4523 - Handle TransPort connections even when the server sends data before
4524 the client sends data. Previously, the connection would just hang
4525 until the client sent data. (Patch from tup based on patch from
4527 - Avoid assert failure when our cached-routers file is empty on
4531 - Don't log spurious warnings when we see a circuit close reason we
4532 don't recognize; it's probably just from a newer version of Tor.
4533 - Have directory authorities allow larger amounts of drift in uptime
4534 without replacing the server descriptor: previously, a server that
4535 restarted every 30 minutes could have 48 "interesting" descriptors
4537 - Start linking to the Tor specification and Tor reference manual
4538 correctly in the Windows installer.
4539 - Add Vidalia to the OS X uninstaller script, so when we uninstall
4540 Tor/Privoxy we also uninstall Vidalia.
4541 - Resume building on Irix64, and fix a lot of warnings from its
4543 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
4544 when we're running as a client.
4547 Changes in version 0.1.1.25 - 2006-11-04
4549 - When a client asks us to resolve (rather than connect to)
4550 an address, and we have a cached answer, give them the cached
4551 answer. Previously, we would give them no answer at all.
4552 - We were building exactly the wrong circuits when we predict
4553 hidden service requirements, meaning Tor would have to build all
4554 its circuits on demand.
4555 - If none of our live entry guards have a high uptime, but we
4556 require a guard with a high uptime, try adding a new guard before
4557 we give up on the requirement. This patch should make long-lived
4558 connections more stable on average.
4559 - When testing reachability of our DirPort, don't launch new
4560 tests when there's already one in progress -- unreachable
4561 servers were stacking up dozens of testing streams.
4563 o Security bugfixes:
4564 - When the user sends a NEWNYM signal, clear the client-side DNS
4565 cache too. Otherwise we continue to act on previous information.
4568 - Avoid a memory corruption bug when creating a hash table for
4570 - Avoid possibility of controller-triggered crash when misusing
4571 certain commands from a v0 controller on platforms that do not
4572 handle printf("%s",NULL) gracefully.
4573 - Avoid infinite loop on unexpected controller input.
4574 - Don't log spurious warnings when we see a circuit close reason we
4575 don't recognize; it's probably just from a newer version of Tor.
4576 - Add Vidalia to the OS X uninstaller script, so when we uninstall
4577 Tor/Privoxy we also uninstall Vidalia.
4580 Changes in version 0.1.2.3-alpha - 2006-10-29
4582 - Prepare for servers to publish descriptors less often: never
4583 discard a descriptor simply for being too old until either it is
4584 recommended by no authorities, or until we get a better one for
4585 the same router. Make caches consider retaining old recommended
4586 routers for even longer.
4587 - If most authorities set a BadExit flag for a server, clients
4588 don't think of it as a general-purpose exit. Clients only consider
4589 authorities that advertise themselves as listing bad exits.
4590 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
4591 headers for content, so that we can work better in the presence of
4592 caching HTTP proxies.
4593 - Allow authorities to list nodes as bad exits by fingerprint or by
4596 o Minor features, controller:
4597 - Add a REASON field to CIRC events; for backward compatibility, this
4598 field is sent only to controllers that have enabled the extended
4599 event format. Also, add additional reason codes to explain why
4600 a given circuit has been destroyed or truncated. (Patches from
4602 - Add a REMOTE_REASON field to extended CIRC events to tell the
4603 controller about why a remote OR told us to close a circuit.
4604 - Stream events also now have REASON and REMOTE_REASON fields,
4605 working much like those for circuit events.
4606 - There's now a GETINFO ns/... field so that controllers can ask Tor
4607 about the current status of a router.
4608 - A new event type "NS" to inform a controller when our opinion of
4609 a router's status has changed.
4610 - Add a GETINFO events/names and GETINFO features/names so controllers
4611 can tell which events and features are supported.
4612 - A new CLEARDNSCACHE signal to allow controllers to clear the
4613 client-side DNS cache without expiring circuits.
4615 o Security bugfixes:
4616 - When the user sends a NEWNYM signal, clear the client-side DNS
4617 cache too. Otherwise we continue to act on previous information.
4620 - Avoid sending junk to controllers or segfaulting when a controller
4621 uses EVENT_NEW_DESC with verbose nicknames.
4622 - Stop triggering asserts if the controller tries to extend hidden
4623 service circuits (reported by mwenge).
4624 - Avoid infinite loop on unexpected controller input.
4625 - When the controller does a "GETINFO network-status", tell it
4626 about even those routers whose descriptors are very old, and use
4627 long nicknames where appropriate.
4628 - Change NT service functions to be loaded on demand. This lets us
4629 build with MinGW without breaking Tor for Windows 98 users.
4630 - Do DirPort reachability tests less often, since a single test
4631 chews through many circuits before giving up.
4632 - In the hidden service example in torrc.sample, stop recommending
4633 esoteric and discouraged hidden service options.
4634 - When stopping an NT service, wait up to 10 sec for it to actually
4635 stop. (Patch from Matt Edman; resolves bug 295.)
4636 - Fix handling of verbose nicknames with ORCONN controller events:
4637 make them show up exactly when requested, rather than exactly when
4639 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
4640 printing a duplicate "$" in the keys we send (reported by mwenge).
4641 - Correctly set maximum connection limit on Cygwin. (This time
4643 - Try to detect Windows correctly when cross-compiling.
4644 - Detect the size of the routers file correctly even if it is
4645 corrupted (on systems without mmap) or not page-aligned (on systems
4646 with mmap). This bug was harmless.
4647 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
4648 to open a stream fails; now we do in more cases. This should
4649 make clients able to find a good exit faster in some cases, since
4650 unhandleable requests will now get an error rather than timing out.
4651 - Resolve two memory leaks when rebuilding the on-disk router cache
4652 (reported by fookoowa).
4653 - Clean up minor code warnings suggested by the MIPSpro C compiler,
4654 and reported by some Centos users.
4655 - Controller signals now work on non-Unix platforms that don't define
4656 SIGUSR1 and SIGUSR2 the way we expect.
4657 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
4658 values before failing, and always enables eventdns.
4659 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
4660 Try to fix this in configure.in by checking for most functions
4661 before we check for libevent.
4664 Changes in version 0.1.2.2-alpha - 2006-10-07
4666 - Make our async eventdns library on-by-default for Tor servers,
4667 and plan to deprecate the separate dnsworker threads.
4668 - Add server-side support for "reverse" DNS lookups (using PTR
4669 records so clients can determine the canonical hostname for a given
4670 IPv4 address). Only supported by servers using eventdns; servers
4671 now announce in their descriptors whether they support eventdns.
4672 - Specify and implement client-side SOCKS5 interface for reverse DNS
4673 lookups (see doc/socks-extensions.txt).
4674 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
4675 connect to directory servers through Tor. Previously, clients needed
4676 to find Tor exits to make private connections to directory servers.
4677 - Avoid choosing Exit nodes for entry or middle hops when the
4678 total bandwidth available from non-Exit nodes is much higher than
4679 the total bandwidth available from Exit nodes.
4680 - Workaround for name servers (like Earthlink's) that hijack failing
4681 DNS requests and replace the no-such-server answer with a "helpful"
4682 redirect to an advertising-driven search portal. Also work around
4683 DNS hijackers who "helpfully" decline to hijack known-invalid
4684 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
4685 lets you turn it off.
4686 - Send out a burst of long-range padding cells once we've established
4687 that we're reachable. Spread them over 4 circuits, so hopefully
4688 a few will be fast. This exercises our bandwidth and bootstraps
4689 us into the directory more quickly.
4691 o New/improved config options:
4692 - Add new config option "ResolvConf" to let the server operator
4693 choose an alternate resolve.conf file when using eventdns.
4694 - Add an "EnforceDistinctSubnets" option to control our "exclude
4695 servers on the same /16" behavior. It's still on by default; this
4696 is mostly for people who want to operate private test networks with
4697 all the machines on the same subnet.
4698 - If one of our entry guards is on the ExcludeNodes list, or the
4699 directory authorities don't think it's a good guard, treat it as
4700 if it were unlisted: stop using it as a guard, and throw it off
4701 the guards list if it stays that way for a long time.
4702 - Allow directory authorities to be marked separately as authorities
4703 for the v1 directory protocol, the v2 directory protocol, and
4704 as hidden service directories, to make it easier to retire old
4705 authorities. V1 authorities should set "HSAuthoritativeDir 1"
4706 to continue being hidden service authorities too.
4707 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
4709 o Minor features, controller:
4710 - Fix CIRC controller events so that controllers can learn the
4711 identity digests of non-Named servers used in circuit paths.
4712 - Let controllers ask for more useful identifiers for servers. Instead
4713 of learning identity digests for un-Named servers and nicknames
4714 for Named servers, the new identifiers include digest, nickname,
4715 and indication of Named status. Off by default; see control-spec.txt
4716 for more information.
4717 - Add a "getinfo address" controller command so it can display Tor's
4718 best guess to the user.
4719 - New controller event to alert the controller when our server
4720 descriptor has changed.
4721 - Give more meaningful errors on controller authentication failure.
4723 o Minor features, other:
4724 - When asked to resolve a hostname, don't use non-exit servers unless
4725 requested to do so. This allows servers with broken DNS to be
4726 useful to the network.
4727 - Divide eventdns log messages into warn and info messages.
4728 - Reserve the nickname "Unnamed" for routers that can't pick
4729 a hostname: any router can call itself Unnamed; directory
4730 authorities will never allocate Unnamed to any particular router;
4731 clients won't believe that any router is the canonical Unnamed.
4732 - Only include function names in log messages for info/debug messages.
4733 For notice/warn/err, the content of the message should be clear on
4734 its own, and printing the function name only confuses users.
4735 - Avoid some false positives during reachability testing: don't try
4736 to test via a server that's on the same /24 as us.
4737 - If we fail to build a circuit to an intended enclave, and it's
4738 not mandatory that we use that enclave, stop wanting it.
4739 - When eventdns is enabled, allow multithreaded builds on NetBSD and
4740 OpenBSD. (We had previously disabled threads on these platforms
4741 because they didn't have working thread-safe resolver functions.)
4743 o Major bugfixes, anonymity/security:
4744 - If a client asked for a server by name, and there's a named server
4745 in our network-status but we don't have its descriptor yet, we
4746 could return an unnamed server instead.
4747 - Fix NetBSD bug that could allow someone to force uninitialized RAM
4748 to be sent to a server's DNS resolver. This only affects NetBSD
4749 and other platforms that do not bounds-check tolower().
4750 - Reject (most) attempts to use Tor circuits with length one. (If
4751 many people start using Tor as a one-hop proxy, exit nodes become
4752 a more attractive target for compromise.)
4753 - Just because your DirPort is open doesn't mean people should be
4754 able to remotely teach you about hidden service descriptors. Now
4755 only accept rendezvous posts if you've got HSAuthoritativeDir set.
4757 o Major bugfixes, other:
4758 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
4759 - When a client asks the server to resolve (not connect to)
4760 an address, and it has a cached answer, give them the cached answer.
4761 Previously, the server would give them no answer at all.
4762 - Allow really slow clients to not hang up five minutes into their
4763 directory downloads (suggested by Adam J. Richter).
4764 - We were building exactly the wrong circuits when we anticipated
4765 hidden service requirements, meaning Tor would have to build all
4766 its circuits on demand.
4767 - Avoid crashing when we mmap a router cache file of size 0.
4768 - When testing reachability of our DirPort, don't launch new
4769 tests when there's already one in progress -- unreachable
4770 servers were stacking up dozens of testing streams.
4772 o Minor bugfixes, correctness:
4773 - If we're a directory mirror and we ask for "all" network status
4774 documents, we would discard status documents from authorities
4776 - Avoid a memory corruption bug when creating a hash table for
4778 - Avoid controller-triggered crash when misusing certain commands
4779 from a v0 controller on platforms that do not handle
4780 printf("%s",NULL) gracefully.
4781 - Don't crash when a controller sends a third argument to an
4782 "extendcircuit" request.
4783 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
4784 response; fix error code when "getinfo dir/status/" fails.
4785 - Avoid crash when telling controller stream-status and a stream
4787 - Patch from Adam Langley to fix assert() in eventdns.c.
4788 - Fix a debug log message in eventdns to say "X resolved to Y"
4789 instead of "X resolved to X".
4790 - Make eventdns give strings for DNS errors, not just error numbers.
4791 - Track unreachable entry guards correctly: don't conflate
4792 'unreachable by us right now' with 'listed as down by the directory
4793 authorities'. With the old code, if a guard was unreachable by
4794 us but listed as running, it would clog our guard list forever.
4795 - Behave correctly in case we ever have a network with more than
4796 2GB/s total advertised capacity.
4797 - Make TrackExitHosts case-insensitive, and fix the behavior of
4798 ".suffix" TrackExitHosts items to avoid matching in the middle of
4800 - Finally fix the openssl warnings from newer gccs that believe that
4801 ignoring a return value is okay, but casting a return value and
4802 then ignoring it is a sign of madness.
4803 - Prevent the contrib/exitlist script from printing the same
4804 result more than once.
4805 - Patch from Steve Hildrey: Generate network status correctly on
4806 non-versioning dirservers.
4807 - Don't listen to the X-Your-Address-Is hint if you did the lookup
4808 via Tor; otherwise you'll think you're the exit node's IP address.
4810 o Minor bugfixes, performance:
4811 - Two small performance improvements on parsing descriptors.
4812 - Major performance improvement on inserting descriptors: change
4813 algorithm from O(n^2) to O(n).
4814 - Make the common memory allocation path faster on machines where
4815 malloc(0) returns a pointer.
4816 - Start remembering X-Your-Address-Is directory hints even if you're
4817 a client, so you can become a server more smoothly.
4818 - Avoid duplicate entries on MyFamily line in server descriptor.
4820 o Packaging, features:
4821 - Remove architecture from OS X builds. The official builds are
4822 now universal binaries.
4823 - The Debian package now uses --verify-config when (re)starting,
4824 to distinguish configuration errors from other errors.
4825 - Update RPMs to require libevent 1.1b.
4827 o Packaging, bugfixes:
4828 - Patches so Tor builds with MinGW on Windows.
4829 - Patches so Tor might run on Cygwin again.
4830 - Resume building on non-gcc compilers and ancient gcc. Resume
4831 building with the -O0 compile flag. Resume building cleanly on
4833 - Run correctly on OS X platforms with case-sensitive filesystems.
4834 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
4835 - Add autoconf checks so Tor can build on Solaris x86 again.
4838 - Documented (and renamed) ServerDNSSearchDomains and
4839 ServerDNSResolvConfFile options.
4840 - Be clearer that the *ListenAddress directives can be repeated
4844 Changes in version 0.1.1.24 - 2006-09-29
4846 - Allow really slow clients to not hang up five minutes into their
4847 directory downloads (suggested by Adam J. Richter).
4848 - Fix major performance regression from 0.1.0.x: instead of checking
4849 whether we have enough directory information every time we want to
4850 do something, only check when the directory information has changed.
4851 This should improve client CPU usage by 25-50%.
4852 - Don't crash if, after a server has been running for a while,
4853 it can't resolve its hostname.
4856 - Allow Tor to start when RunAsDaemon is set but no logs are set.
4857 - Don't crash when the controller receives a third argument to an
4858 "extendcircuit" request.
4859 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
4860 response; fix error code when "getinfo dir/status/" fails.
4861 - Fix configure.in to not produce broken configure files with
4862 more recent versions of autoconf. Thanks to Clint for his auto*
4864 - Fix security bug on NetBSD that could allow someone to force
4865 uninitialized RAM to be sent to a server's DNS resolver. This
4866 only affects NetBSD and other platforms that do not bounds-check
4868 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
4869 methods: these are known to be buggy.
4870 - If we're a directory mirror and we ask for "all" network status
4871 documents, we would discard status documents from authorities
4875 Changes in version 0.1.2.1-alpha - 2006-08-27
4877 - Add "eventdns" async dns library from Adam Langley, tweaked to
4878 build on OSX and Windows. Only enabled if you pass the
4879 --enable-eventdns argument to configure.
4880 - Allow servers with no hostname or IP address to learn their
4881 IP address by asking the directory authorities. This code only
4882 kicks in when you would normally have exited with a "no address"
4883 error. Nothing's authenticated, so use with care.
4884 - Rather than waiting a fixed amount of time between retrying
4885 application connections, we wait only 5 seconds for the first,
4886 10 seconds for the second, and 15 seconds for each retry after
4887 that. Hopefully this will improve the expected user experience.
4888 - Patch from Tup to add support for transparent AP connections:
4889 this basically bundles the functionality of trans-proxy-tor
4890 into the Tor mainline. Now hosts with compliant pf/netfilter
4891 implementations can redirect TCP connections straight to Tor
4892 without diverting through SOCKS. Needs docs.
4893 - Busy directory servers save lots of memory by spooling server
4894 descriptors, v1 directories, and v2 networkstatus docs to buffers
4895 as needed rather than en masse. Also mmap the cached-routers
4896 files, so we don't need to keep the whole thing in memory too.
4897 - Automatically avoid picking more than one node from the same
4898 /16 network when constructing a circuit.
4899 - Revise and clean up the torrc.sample that we ship with; add
4900 a section for BandwidthRate and BandwidthBurst.
4903 - Split circuit_t into origin_circuit_t and or_circuit_t, and
4904 split connection_t into edge, or, dir, control, and base structs.
4905 These will save quite a bit of memory on busy servers, and they'll
4906 also help us track down bugs in the code and bugs in the spec.
4907 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
4908 or later. Log when we are doing this, so we can diagnose it when
4909 it fails. (Also, recommend libevent 1.1b for kqueue and
4910 win32 methods; deprecate libevent 1.0b harder; make libevent
4911 recommendation system saner.)
4912 - Start being able to build universal binaries on OS X (thanks
4914 - Export the default exit policy via the control port, so controllers
4915 don't need to guess what it is / will be later.
4916 - Add a man page entry for ProtocolWarnings.
4917 - Add TestVia config option to the man page.
4918 - Remove even more protocol-related warnings from Tor server logs,
4919 such as bad TLS handshakes and malformed begin cells.
4920 - Stop fetching descriptors if you're not a dir mirror and you
4921 haven't tried to establish any circuits lately. [This currently
4922 causes some dangerous behavior, because when you start up again
4923 you'll use your ancient server descriptors.]
4924 - New DirPort behavior: if you have your dirport set, you download
4925 descriptors aggressively like a directory mirror, whether or not
4927 - Get rid of the router_retry_connections notion. Now routers
4928 no longer try to rebuild long-term connections to directory
4929 authorities, and directory authorities no longer try to rebuild
4930 long-term connections to all servers. We still don't hang up
4931 connections in these two cases though -- we need to look at it
4932 more carefully to avoid flapping, and we likely need to wait til
4933 0.1.1.x is obsolete.
4934 - Drop compatibility with obsolete Tors that permit create cells
4935 to have the wrong circ_id_type.
4936 - Re-enable per-connection rate limiting. Get rid of the "OP
4937 bandwidth" concept. Lay groundwork for "bandwidth classes" --
4938 separate global buckets that apply depending on what sort of conn
4940 - Start publishing one minute or so after we find our ORPort
4941 to be reachable. This will help reduce the number of descriptors
4942 we have for ourselves floating around, since it's quite likely
4943 other things (e.g. DirPort) will change during that minute too.
4944 - Fork the v1 directory protocol into its own spec document,
4945 and mark dir-spec.txt as the currently correct (v2) spec.
4948 - When we find our DirPort to be reachable, publish a new descriptor
4949 so we'll tell the world (reported by pnx).
4950 - Publish a new descriptor after we hup/reload. This is important
4951 if our config has changed such that we'll want to start advertising
4952 our DirPort now, etc.
4953 - Allow Tor to start when RunAsDaemon is set but no logs are set.
4954 - When we have a state file we cannot parse, tell the user and
4955 move it aside. Now we avoid situations where the user starts
4956 Tor in 1904, Tor writes a state file with that timestamp in it,
4957 the user fixes her clock, and Tor refuses to start.
4958 - Fix configure.in to not produce broken configure files with
4959 more recent versions of autoconf. Thanks to Clint for his auto*
4961 - "tor --verify-config" now exits with -1(255) or 0 depending on
4962 whether the config options are bad or good.
4963 - Resolve bug 321 when using dnsworkers: append a period to every
4964 address we resolve at the exit node, so that we do not accidentally
4965 pick up local addresses, and so that failing searches are retried
4966 in the resolver search domains. (This is already solved for
4967 eventdns.) (This breaks Blossom servers for now.)
4968 - If we are using an exit enclave and we can't connect, e.g. because
4969 its webserver is misconfigured to not listen on localhost, then
4970 back off and try connecting from somewhere else before we fail.
4973 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
4974 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
4975 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
4976 when the IP address is mapped through MapAddress to a hostname.
4977 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
4978 useless IPv6 DNS resolves.
4979 - Patch suggested by Karsten Loesing: respond to SIGNAL command
4980 before we execute the signal, in case the signal shuts us down.
4981 - Clean up AllowInvalidNodes man page entry.
4982 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
4983 - Add more asserts to track down an assert error on a windows Tor
4984 server with connection_add being called with socket == -1.
4985 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
4986 - Fix misleading log messages: an entry guard that is "unlisted",
4987 as well as not known to be "down" (because we've never heard
4988 of it), is not therefore "up".
4989 - Remove code to special-case "-cvs" ending, since it has not
4990 actually mattered since 0.0.9.
4991 - Make our socks5 handling more robust to broken socks clients:
4992 throw out everything waiting on the buffer in between socks
4993 handshake phases, since they can't possibly (so the theory
4994 goes) have predicted what we plan to respond to them.
4997 Changes in version 0.1.1.23 - 2006-07-30
4999 - Fast Tor servers, especially exit nodes, were triggering asserts
5000 due to a bug in handling the list of pending DNS resolves. Some
5001 bugs still remain here; we're hunting them.
5002 - Entry guards could crash clients by sending unexpected input.
5003 - More fixes on reachability testing: if you find yourself reachable,
5004 then don't ever make any client requests (so you stop predicting
5005 circuits), then hup or have your clock jump, then later your IP
5006 changes, you won't think circuits are working, so you won't try to
5007 test reachability, so you won't publish.
5010 - Avoid a crash if the controller does a resetconf firewallports
5011 and then a setconf fascistfirewall=1.
5012 - Avoid an integer underflow when the dir authority decides whether
5013 a router is stable: we might wrongly label it stable, and compute
5014 a slightly wrong median stability, when a descriptor is published
5016 - Fix a place where we might trigger an assert if we can't build our
5017 own server descriptor yet.
5020 Changes in version 0.1.1.22 - 2006-07-05
5022 - Fix a big bug that was causing servers to not find themselves
5023 reachable if they changed IP addresses. Since only 0.1.1.22+
5024 servers can do reachability testing correctly, now we automatically
5025 make sure to test via one of these.
5026 - Fix to allow clients and mirrors to learn directory info from
5027 descriptor downloads that get cut off partway through.
5028 - Directory authorities had a bug in deciding if a newly published
5029 descriptor was novel enough to make everybody want a copy -- a few
5030 servers seem to be publishing new descriptors many times a minute.
5032 - Fix a rare bug that was causing some servers to complain about
5033 "closing wedged cpuworkers" and skip some circuit create requests.
5034 - Make the Exit flag in directory status documents actually work.
5037 Changes in version 0.1.1.21 - 2006-06-10
5038 o Crash and assert fixes from 0.1.1.20:
5039 - Fix a rare crash on Tor servers that have enabled hibernation.
5040 - Fix a seg fault on startup for Tor networks that use only one
5041 directory authority.
5042 - Fix an assert from a race condition that occurs on Tor servers
5043 while exiting, where various threads are trying to log that they're
5044 exiting, and delete the logs, at the same time.
5045 - Make our unit tests pass again on certain obscure platforms.
5048 - Add support for building SUSE RPM packages.
5049 - Speed up initial bootstrapping for clients: if we are making our
5050 first ever connection to any entry guard, then don't mark it down
5052 - When only one Tor server in the network is labelled as a guard,
5053 and we've already picked him, we would cycle endlessly picking him
5054 again, being unhappy about it, etc. Now we specifically exclude
5055 current guards when picking a new guard.
5056 - Servers send create cells more reliably after the TLS connection
5057 is established: we were sometimes forgetting to send half of them
5058 when we had more than one pending.
5059 - If we get a create cell that asks us to extend somewhere, but the
5060 Tor server there doesn't match the expected digest, we now send
5061 a destroy cell back, rather than silently doing nothing.
5062 - Make options->RedirectExit work again.
5063 - Make cookie authentication for the controller work again.
5064 - Stop being picky about unusual characters in the arguments to
5065 mapaddress. It's none of our business.
5066 - Add a new config option "TestVia" that lets you specify preferred
5067 middle hops to use for test circuits. Perhaps this will let me
5068 debug the reachability problems better.
5070 o Log / documentation fixes:
5071 - If we're a server and some peer has a broken TLS certificate, don't
5072 log about it unless ProtocolWarnings is set, i.e., we want to hear
5073 about protocol violations by others.
5074 - Fix spelling of VirtualAddrNetwork in man page.
5075 - Add a better explanation at the top of the autogenerated torrc file
5076 about what happened to our old torrc.
5079 Changes in version 0.1.1.20 - 2006-05-23
5081 - Downgrade a log severity where servers complain that they're
5083 - Avoid a compile warning on FreeBSD.
5084 - Remove string size limit on NEWDESC messages; solve bug 291.
5085 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
5086 more thoroughly when we're running on windows.
5089 Changes in version 0.1.1.19-rc - 2006-05-03
5091 - Regenerate our local descriptor if it's dirty and we try to use
5092 it locally (e.g. if it changes during reachability detection).
5093 - If we setconf our ORPort to 0, we continued to listen on the
5094 old ORPort and receive connections.
5095 - Avoid a second warning about machine/limits.h on Debian
5097 - Be willing to add our own routerinfo into the routerlist.
5098 Now authorities will include themselves in their directories
5099 and network-statuses.
5100 - Stop trying to upload rendezvous descriptors to every
5101 directory authority: only try the v1 authorities.
5102 - Servers no longer complain when they think they're not
5103 registered with the directory authorities. There were too many
5105 - Backport dist-rpm changes so rpms can be built without errors.
5108 - Implement an option, VirtualAddrMask, to set which addresses
5109 get handed out in response to mapaddress requests. This works
5110 around a bug in tsocks where 127.0.0.0/8 is never socksified.
5113 Changes in version 0.1.1.18-rc - 2006-04-10
5115 - Work harder to download live network-statuses from all the
5116 directory authorities we know about. Improve the threshold
5117 decision logic so we're more robust to edge cases.
5118 - When fetching rendezvous descriptors, we were willing to ask
5119 v2 authorities too, which would always return 404.
5122 - Stop listing down or invalid nodes in the v1 directory. This will
5123 reduce its bulk by about 1/3, and reduce load on directory
5125 - When deciding whether a router is Fast or Guard-worthy, consider
5126 his advertised BandwidthRate and not just the BandwidthCapacity.
5127 - No longer ship INSTALL and README files -- they are useless now.
5128 - Force rpmbuild to behave and honor target_cpu.
5129 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
5130 - Start to include translated versions of the tor-doc-*.html
5131 files, along with the screenshots. Still needs more work.
5132 - Start sending back 512 and 451 errors if mapaddress fails,
5133 rather than not sending anything back at all.
5134 - When we fail to bind or listen on an incoming or outgoing
5135 socket, we should close it before failing. otherwise we just
5136 leak it. (thanks to weasel for finding.)
5137 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
5138 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
5139 - Make NoPublish (even though deprecated) work again.
5140 - Fix a minor security flaw where a versioning auth dirserver
5141 could list a recommended version many times in a row to make
5142 clients more convinced that it's recommended.
5143 - Fix crash bug if there are two unregistered servers running
5144 with the same nickname, one of them is down, and you ask for
5145 them by nickname in your EntryNodes or ExitNodes. Also, try
5146 to pick the one that's running rather than an arbitrary one.
5147 - Fix an infinite loop we could hit if we go offline for too long.
5148 - Complain when we hit WSAENOBUFS on recv() or write() too.
5149 Perhaps this will help us hunt the bug.
5150 - If you're not a versioning dirserver, don't put the string
5151 "client-versions \nserver-versions \n" in your network-status.
5152 - Lower the minimum required number of file descriptors to 1000,
5153 so we can have some overhead for Valgrind on Linux, where the
5154 default ulimit -n is 1024.
5157 - Add tor.dizum.com as the fifth authoritative directory server.
5158 - Add a new config option FetchUselessDescriptors, off by default,
5159 for when you plan to run "exitlist" on your client and you want
5160 to know about even the non-running descriptors.
5163 Changes in version 0.1.1.17-rc - 2006-03-28
5165 - Clients and servers since 0.1.1.10-alpha have been expiring
5166 connections whenever they are idle for 5 minutes and they *do*
5167 have circuits on them. Oops. With this new version, clients will
5168 discard their previous entry guard choices and avoid choosing
5169 entry guards running these flawed versions.
5170 - Fix memory leak when uncompressing concatenated zlib streams. This
5171 was causing substantial leaks over time on Tor servers.
5172 - The v1 directory was including servers as much as 48 hours old,
5173 because that's how the new routerlist->routers works. Now only
5174 include them if they're 20 hours old or less.
5177 - Resume building on irix64, netbsd 2.0, etc.
5178 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
5180 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
5181 and it is confusing some users.
5182 - Mirrors stop caching the v1 directory so often.
5183 - Make the max number of old descriptors that a cache will hold
5184 rise with the number of directory authorities, so we can scale.
5185 - Change our win32 uname() hack to be more forgiving about what
5186 win32 versions it thinks it's found.
5189 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
5191 - When the controller's *setconf commands fail, collect an error
5192 message in a string and hand it back to the controller.
5193 - Make the v2 dir's "Fast" flag based on relative capacity, just
5194 like "Stable" is based on median uptime. Name everything in the
5195 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
5196 - Log server fingerprint on startup, so new server operators don't
5197 have to go hunting around their filesystem for it.
5198 - Return a robots.txt on our dirport to discourage google indexing.
5199 - Let the controller ask for GETINFO dir/status/foo so it can ask
5200 directly rather than connecting to the dir port. Only works when
5201 dirport is set for now.
5203 o New config options rather than constants in the code:
5204 - SocksTimeout: How long do we let a socks connection wait
5205 unattached before we fail it?
5206 - CircuitBuildTimeout: Cull non-open circuits that were born
5207 at least this many seconds ago.
5208 - CircuitIdleTimeout: Cull open clean circuits that were born
5209 at least this many seconds ago.
5212 Changes in version 0.1.1.16-rc - 2006-03-18
5213 o Bugfixes on 0.1.1.15-rc:
5214 - Fix assert when the controller asks to attachstream a connect-wait
5215 or resolve-wait stream.
5216 - Now do address rewriting when the controller asks us to attach
5217 to a particular circuit too. This will let Blossom specify
5218 "moria2.exit" without having to learn what moria2's IP address is.
5219 - Make the "tor --verify-config" command-line work again, so people
5220 can automatically check if their torrc will parse.
5221 - Authoritative dirservers no longer require an open connection from
5222 a server to consider him "reachable". We need this change because
5223 when we add new auth dirservers, old servers won't know not to
5225 - Let Tor build on Sun CC again.
5226 - Fix an off-by-one buffer size in dirserv.c that magically never
5227 hit our three authorities but broke sjmurdoch's own tor network.
5228 - If we as a directory mirror don't know of any v1 directory
5229 authorities, then don't try to cache any v1 directories.
5230 - Stop warning about unknown servers in our family when they are
5231 given as hex digests.
5232 - Stop complaining as quickly to the server operator that he
5233 hasn't registered his nickname/key binding.
5234 - Various cleanups so we can add new V2 Auth Dirservers.
5235 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
5236 reflect the updated flags in our v2 dir protocol.
5237 - Resume allowing non-printable characters for exit streams (both
5238 for connecting and for resolving). Now we tolerate applications
5239 that don't follow the RFCs. But continue to block malformed names
5242 o Bugfixes on 0.1.0.x:
5243 - Fix assert bug in close_logs(): when we close and delete logs,
5244 remove them all from the global "logfiles" list.
5245 - Fix minor integer overflow in calculating when we expect to use up
5246 our bandwidth allocation before hibernating.
5247 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
5248 there are multiple SSLs installed with different versions.
5249 - When we try to be a server and Address is not explicitly set and
5250 our hostname resolves to a private IP address, try to use an
5251 interface address if it has a public address. Now Windows machines
5252 that think of themselves as localhost can work by default.
5255 - Let the controller ask for GETINFO dir/server/foo so it can ask
5256 directly rather than connecting to the dir port.
5257 - Let the controller tell us about certain router descriptors
5258 that it doesn't want Tor to use in circuits. Implement
5259 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
5260 - New config option SafeSocks to reject all application connections
5261 using unsafe socks protocols. Defaults to off.
5264 Changes in version 0.1.1.15-rc - 2006-03-11
5265 o Bugfixes and cleanups:
5266 - When we're printing strings from the network, don't try to print
5267 non-printable characters. This protects us against shell escape
5268 sequence exploits, and also against attacks to fool humans into
5269 misreading their logs.
5270 - Fix a bug where Tor would fail to establish any connections if you
5271 left it off for 24 hours and then started it: we were happy with
5272 the obsolete network statuses, but they all referred to router
5273 descriptors that were too old to fetch, so we ended up with no
5274 valid router descriptors.
5275 - Fix a seg fault in the controller's "getinfo orconn-status"
5276 command while listing status on incoming handshaking connections.
5277 Introduce a status name "NEW" for these connections.
5278 - If we get a linelist or linelist_s config option from the torrc
5279 (e.g. ExitPolicy) and it has no value, warn and skip rather than
5280 silently resetting it to its default.
5281 - Don't abandon entry guards until they've been down or gone for
5283 - Cleaner and quieter log messages.
5286 - New controller signal NEWNYM that makes new application requests
5288 - Add a new circuit purpose 'controller' to let the controller ask
5289 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
5290 controller command to let you specify the purpose if you're
5291 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
5292 command to let you change a circuit's purpose after it's been
5294 - Accept "private:*" in routerdesc exit policies; not generated yet
5295 because older Tors do not understand it.
5296 - Add BSD-style contributed startup script "rc.subr" from Peter
5300 Changes in version 0.1.1.14-alpha - 2006-02-20
5301 o Bugfixes on 0.1.1.x:
5302 - Don't die if we ask for a stdout or stderr log (even implicitly)
5303 and we're set to RunAsDaemon -- just warn.
5304 - We still had a few bugs in the OR connection rotation code that
5305 caused directory servers to slowly aggregate connections to other
5306 fast Tor servers. This time for sure!
5307 - Make log entries on Win32 include the name of the function again.
5308 - We were treating a pair of exit policies if they were equal even
5309 if one said accept and the other said reject -- causing us to
5310 not always publish a new descriptor since we thought nothing
5312 - Retry pending server downloads as well as pending networkstatus
5313 downloads when we unexpectedly get a socks request.
5314 - We were ignoring the IS_FAST flag in the directory status,
5315 meaning we were willing to pick trivial-bandwidth nodes for "fast"
5317 - If the controller's SAVECONF command fails (e.g. due to file
5318 permissions), let the controller know that it failed.
5321 - If we're trying to be a Tor server and running Windows 95/98/ME
5322 as a server, explain that we'll likely crash.
5323 - When we're a server, a client asks for an old-style directory,
5324 and our write bucket is empty, don't give it to him. This way
5325 small servers can continue to serve the directory *sometimes*,
5326 without getting overloaded.
5327 - Compress exit policies even more -- look for duplicate lines
5329 - Clients now honor the "guard" flag in the router status when
5330 picking entry guards, rather than looking at is_fast or is_stable.
5331 - Retain unrecognized lines in $DATADIR/state file, so that we can
5332 be forward-compatible.
5333 - Generate 18.0.0.0/8 address policy format in descs when we can;
5334 warn when the mask is not reducible to a bit-prefix.
5335 - Let the user set ControlListenAddress in the torrc. This can be
5336 dangerous, but there are some cases (like a secured LAN) where it
5338 - Split ReachableAddresses into ReachableDirAddresses and
5339 ReachableORAddresses, so we can restrict Dir conns to port 80
5340 and OR conns to port 443.
5341 - Now we can target arch and OS in rpm builds (contributed by
5342 Phobos). Also make the resulting dist-rpm filename match the
5344 - New config options to help controllers: FetchServerDescriptors
5345 and FetchHidServDescriptors for whether to fetch server
5346 info and hidserv info or let the controller do it, and
5347 PublishServerDescriptor and PublishHidServDescriptors.
5348 - Also let the controller set the __AllDirActionsPrivate config
5349 option if you want all directory fetches/publishes to happen via
5350 Tor (it assumes your controller bootstraps your circuits).
5353 Changes in version 0.1.0.17 - 2006-02-17
5354 o Crash bugfixes on 0.1.0.x:
5355 - When servers with a non-zero DirPort came out of hibernation,
5356 sometimes they would trigger an assert.
5358 o Other important bugfixes:
5359 - On platforms that don't have getrlimit (like Windows), we were
5360 artificially constraining ourselves to a max of 1024
5361 connections. Now just assume that we can handle as many as 15000
5362 connections. Hopefully this won't cause other problems.
5364 o Backported features:
5365 - When we're a server, a client asks for an old-style directory,
5366 and our write bucket is empty, don't give it to him. This way
5367 small servers can continue to serve the directory *sometimes*,
5368 without getting overloaded.
5369 - Whenever you get a 503 in response to a directory fetch, try
5370 once more. This will become important once servers start sending
5371 503's whenever they feel busy.
5372 - Fetch a new directory every 120 minutes, not every 40 minutes.
5373 Now that we have hundreds of thousands of users running the old
5374 directory algorithm, it's starting to hurt a lot.
5375 - Bump up the period for forcing a hidden service descriptor upload
5376 from 20 minutes to 1 hour.
5379 Changes in version 0.1.1.13-alpha - 2006-02-09
5380 o Crashes in 0.1.1.x:
5381 - When you tried to setconf ORPort via the controller, Tor would
5382 crash. So people using TorCP to become a server were sad.
5383 - Solve (I hope) the stack-smashing bug that we were seeing on fast
5384 servers. The problem appears to be something do with OpenSSL's
5385 random number generation, or how we call it, or something. Let me
5386 know if the crashes continue.
5387 - Turn crypto hardware acceleration off by default, until we find
5388 somebody smart who can test it for us. (It appears to produce
5389 seg faults in at least some cases.)
5390 - Fix a rare assert error when we've tried all intro points for
5391 a hidden service and we try fetching the service descriptor again:
5392 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
5395 - Fix a major load balance bug: we were round-robining in 16 KB
5396 chunks, and servers with bandwidthrate of 20 KB, while downloading
5397 a 600 KB directory, would starve their other connections. Now we
5398 try to be a bit more fair.
5399 - Dir authorities and mirrors were never expiring the newest
5400 descriptor for each server, causing memory and directory bloat.
5401 - Fix memory-bloating and connection-bloating bug on servers: We
5402 were never closing any connection that had ever had a circuit on
5403 it, because we were checking conn->n_circuits == 0, yet we had a
5404 bug that let it go negative.
5405 - Make Tor work using squid as your http proxy again -- squid
5406 returns an error if you ask for a URL that's too long, and it uses
5407 a really generic error message. Plus, many people are behind a
5408 transparent squid so they don't even realize it.
5409 - On platforms that don't have getrlimit (like Windows), we were
5410 artificially constraining ourselves to a max of 1024
5411 connections. Now just assume that we can handle as many as 15000
5412 connections. Hopefully this won't cause other problems.
5413 - Add a new config option ExitPolicyRejectPrivate which defaults to
5414 1. This means all exit policies will begin with rejecting private
5415 addresses, unless the server operator explicitly turns it off.
5418 - Clients no longer download descriptors for non-running
5420 - Before we add new directory authorities, we should make it
5421 clear that only v1 authorities should receive/publish hidden
5422 service descriptors.
5425 - As soon as we've fetched some more directory info, immediately
5426 try to download more server descriptors. This way we don't have
5427 a 10 second pause during initial bootstrapping.
5428 - Remove even more loud log messages that the server operator can't
5430 - When we're running an obsolete or un-recommended version, make
5431 the log message more clear about what the problem is and what
5432 versions *are* still recommended.
5433 - Provide a more useful warn message when our onion queue gets full:
5434 the CPU is too slow or the exit policy is too liberal.
5435 - Don't warn when we receive a 503 from a dirserver/cache -- this
5436 will pave the way for them being able to refuse if they're busy.
5437 - When we fail to bind a listener, try to provide a more useful
5438 log message: e.g., "Is Tor already running?"
5439 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
5440 Goldberg can prove things about our handshake protocol more
5442 - MaxConn has been obsolete for a while now. Document the ConnLimit
5443 config option, which is a *minimum* number of file descriptors
5444 that must be available else Tor refuses to start.
5445 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
5446 if you log to syslog and want something other than LOG_DAEMON.
5447 - Make dirservers generate a separate "guard" flag to mean,
5448 "would make a good entry guard". Make clients parse it and vote
5449 on it. Not used by clients yet.
5450 - Implement --with-libevent-dir option to ./configure. Also, improve
5451 search techniques to find libevent, and use those for openssl too.
5452 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
5453 - Only start testing reachability once we've established a
5454 circuit. This will make startup on dirservers less noisy.
5455 - Don't try to upload hidden service descriptors until we have
5456 established a circuit.
5457 - Fix the controller's "attachstream 0" command to treat conn like
5458 it just connected, doing address remapping, handling .exit and
5459 .onion idioms, and so on. Now we're more uniform in making sure
5460 that the controller hears about new and closing connections.
5463 Changes in version 0.1.1.12-alpha - 2006-01-11
5464 o Bugfixes on 0.1.1.x:
5465 - The fix to close duplicate server connections was closing all
5466 Tor client connections if they didn't establish a circuit
5467 quickly enough. Oops.
5468 - Fix minor memory issue (double-free) that happened on exit.
5470 o Bugfixes on 0.1.0.x:
5471 - Tor didn't warn when it failed to open a log file.
5474 Changes in version 0.1.1.11-alpha - 2006-01-10
5475 o Crashes in 0.1.1.x:
5476 - Include all the assert/crash fixes from 0.1.0.16.
5477 - If you start Tor and then quit very quickly, there were some
5478 races that tried to free things that weren't allocated yet.
5479 - Fix a rare memory stomp if you're running hidden services.
5480 - Fix segfault when specifying DirServer in config without nickname.
5481 - Fix a seg fault when you finish connecting to a server but at
5482 that moment you dump his server descriptor.
5483 - Extendcircuit and Attachstream controller commands would
5484 assert/crash if you don't give them enough arguments.
5485 - Fix an assert error when we're out of space in the connection_list
5486 and we try to post a hidden service descriptor (reported by weasel).
5487 - If you specify a relative torrc path and you set RunAsDaemon in
5488 your torrc, then it chdir()'s to the new directory. If you HUP,
5489 it tries to load the new torrc location, fails, and exits.
5490 The fix: no longer allow a relative path to torrc using -f.
5493 - Implement "entry guards": automatically choose a handful of entry
5494 nodes and stick with them for all circuits. Only pick new guards
5495 when the ones you have are unsuitable, and if the old guards
5496 become suitable again, switch back. This will increase security
5497 dramatically against certain end-point attacks. The EntryNodes
5498 config option now provides some hints about which entry guards you
5499 want to use most; and StrictEntryNodes means to only use those.
5500 - New directory logic: download by descriptor digest, not by
5501 fingerprint. Caches try to download all listed digests from
5502 authorities; clients try to download "best" digests from caches.
5503 This avoids partitioning and isolating attacks better.
5504 - Make the "stable" router flag in network-status be the median of
5505 the uptimes of running valid servers, and make clients pay
5506 attention to the network-status flags. Thus the cutoff adapts
5507 to the stability of the network as a whole, making IRC, IM, etc
5508 connections more reliable.
5511 - Tor servers with dynamic IP addresses were needing to wait 18
5512 hours before they could start doing reachability testing using
5513 the new IP address and ports. This is because they were using
5514 the internal descriptor to learn what to test, yet they were only
5515 rebuilding the descriptor once they decided they were reachable.
5516 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
5517 to download certain server descriptors, throw them away, and then
5518 fetch them again after 30 minutes. Now mirrors throw away these
5519 server descriptors so clients can't get them.
5520 - We were leaving duplicate connections to other ORs open for a week,
5521 rather than closing them once we detect a duplicate. This only
5522 really affected authdirservers, but it affected them a lot.
5523 - Spread the authdirservers' reachability testing over the entire
5524 testing interval, so we don't try to do 500 TLS's at once every
5528 - If the network is down, and we try to connect to a conn because
5529 we have a circuit in mind, and we timeout (30 seconds) because the
5530 network never answers, we were expiring the circuit, but we weren't
5531 obsoleting the connection or telling the entry_guards functions.
5532 - Some Tor servers process billions of cells per day. These statistics
5533 need to be uint64_t's.
5534 - Check for integer overflows in more places, when adding elements
5535 to smartlists. This could possibly prevent a buffer overflow
5536 on malicious huge inputs. I don't see any, but I haven't looked
5538 - ReachableAddresses kept growing new "reject *:*" lines on every
5540 - When you "setconf log" via the controller, it should remove all
5541 logs. We were automatically adding back in a "log notice stdout".
5542 - Newly bootstrapped Tor networks couldn't establish hidden service
5543 circuits until they had nodes with high uptime. Be more tolerant.
5544 - We were marking servers down when they could not answer every piece
5545 of the directory request we sent them. This was far too harsh.
5546 - Fix the torify (tsocks) config file to not use Tor for localhost
5548 - Directory authorities now go to the proper authority when asking for
5549 a networkstatus, even when they want a compressed one.
5550 - Fix a harmless bug that was causing Tor servers to log
5551 "Got an end because of misc error, but we're not an AP. Closing."
5552 - Authorities were treating their own descriptor changes as cosmetic,
5553 meaning the descriptor available in the network-status and the
5554 descriptor that clients downloaded were different.
5555 - The OS X installer was adding a symlink for tor_resolve but
5556 the binary was called tor-resolve (reported by Thomas Hardly).
5557 - Workaround a problem with some http proxies where they refuse GET
5558 requests that specify "Content-Length: 0" (reported by Adrian).
5559 - Fix wrong log message when you add a "HiddenServiceNodes" config
5560 line without any HiddenServiceDir line (reported by Chris Thomas).
5563 - Write the TorVersion into the state file so we have a prayer of
5564 keeping forward and backward compatibility.
5565 - Revive the FascistFirewall config option rather than eliminating it:
5566 now it's a synonym for ReachableAddresses *:80,*:443.
5567 - Clients choose directory servers from the network status lists,
5568 not from their internal list of router descriptors. Now they can
5569 go to caches directly rather than needing to go to authorities
5571 - Directory authorities ignore router descriptors that have only
5572 cosmetic differences: do this for 0.1.0.x servers now too.
5573 - Add a new flag to network-status indicating whether the server
5574 can answer v2 directory requests too.
5575 - Authdirs now stop whining so loudly about bad descriptors that
5576 they fetch from other dirservers. So when there's a log complaint,
5577 it's for sure from a freshly uploaded descriptor.
5578 - Reduce memory requirements in our structs by changing the order
5580 - There used to be two ways to specify your listening ports in a
5581 server descriptor: on the "router" line and with a separate "ports"
5582 line. Remove support for the "ports" line.
5583 - New config option "AuthDirRejectUnlisted" for auth dirservers as
5584 a panic button: if we get flooded with unusable servers we can
5585 revert to only listing servers in the approved-routers file.
5586 - Auth dir servers can now mark a fingerprint as "!reject" or
5587 "!invalid" in the approved-routers file (as its nickname), to
5588 refuse descriptors outright or include them but marked as invalid.
5589 - Servers store bandwidth history across restarts/crashes.
5590 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
5591 get a better idea of why their circuits failed. Not used yet.
5592 - Directory mirrors now cache up to 16 unrecognized network-status
5593 docs. Now we can add new authdirservers and they'll be cached too.
5594 - When picking a random directory, prefer non-authorities if any
5596 - New controller option "getinfo desc/all-recent" to fetch the
5597 latest server descriptor for every router that Tor knows about.
5600 Changes in version 0.1.0.16 - 2006-01-02
5601 o Crash bugfixes on 0.1.0.x:
5602 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
5603 corrupting the heap, losing FDs, or crashing when we need to resize
5604 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
5605 - It turns out sparc64 platforms crash on unaligned memory access
5606 too -- so detect and avoid this.
5607 - Handle truncated compressed data correctly (by detecting it and
5609 - Fix possible-but-unlikely free(NULL) in control.c.
5610 - When we were closing connections, there was a rare case that
5611 stomped on memory, triggering seg faults and asserts.
5612 - Avoid potential infinite recursion when building a descriptor. (We
5613 don't know that it ever happened, but better to fix it anyway.)
5614 - We were neglecting to unlink marked circuits from soon-to-close OR
5615 connections, which caused some rare scribbling on freed memory.
5616 - Fix a memory stomping race bug when closing the joining point of two
5617 rendezvous circuits.
5618 - Fix an assert in time parsing found by Steven Murdoch.
5620 o Other bugfixes on 0.1.0.x:
5621 - When we're doing reachability testing, provide more useful log
5622 messages so the operator knows what to expect.
5623 - Do not check whether DirPort is reachable when we are suppressing
5624 advertising it because of hibernation.
5625 - When building with -static or on Solaris, we sometimes needed -ldl.
5626 - When we're deciding whether a stream has enough circuits around
5627 that can handle it, count the freshly dirty ones and not the ones
5628 that are so dirty they won't be able to handle it.
5629 - When we're expiring old circuits, we had a logic error that caused
5630 us to close new rendezvous circuits rather than old ones.
5631 - Give a more helpful log message when you try to change ORPort via
5632 the controller: you should upgrade Tor if you want that to work.
5633 - We were failing to parse Tor versions that start with "Tor ".
5634 - Tolerate faulty streams better: when a stream fails for reason
5635 exitpolicy, stop assuming that the router is lying about his exit
5636 policy. When a stream fails for reason misc, allow it to retry just
5637 as if it was resolvefailed. When a stream has failed three times,
5638 reset its failure count so we can try again and get all three tries.
5641 Changes in version 0.1.1.10-alpha - 2005-12-11
5642 o Correctness bugfixes on 0.1.0.x:
5643 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
5644 corrupting the heap, losing FDs, or crashing when we need to resize
5645 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
5646 - Stop doing the complex voodoo overkill checking for insecure
5647 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
5648 - When we were closing connections, there was a rare case that
5649 stomped on memory, triggering seg faults and asserts.
5650 - We were neglecting to unlink marked circuits from soon-to-close OR
5651 connections, which caused some rare scribbling on freed memory.
5652 - When we're deciding whether a stream has enough circuits around
5653 that can handle it, count the freshly dirty ones and not the ones
5654 that are so dirty they won't be able to handle it.
5655 - Recover better from TCP connections to Tor servers that are
5656 broken but don't tell you (it happens!); and rotate TLS
5657 connections once a week.
5658 - When we're expiring old circuits, we had a logic error that caused
5659 us to close new rendezvous circuits rather than old ones.
5660 - Fix a scary-looking but apparently harmless bug where circuits
5661 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
5662 servers, and never switch to state CIRCUIT_STATE_OPEN.
5663 - When building with -static or on Solaris, we sometimes needed to
5665 - Give a useful message when people run Tor as the wrong user,
5666 rather than telling them to start chowning random directories.
5667 - We were failing to inform the controller about new .onion streams.
5669 o Security bugfixes on 0.1.0.x:
5670 - Refuse server descriptors if the fingerprint line doesn't match
5671 the included identity key. Tor doesn't care, but other apps (and
5672 humans) might actually be trusting the fingerprint line.
5673 - We used to kill the circuit when we receive a relay command we
5674 don't recognize. Now we just drop it.
5675 - Start obeying our firewall options more rigorously:
5676 . If we can't get to a dirserver directly, try going via Tor.
5677 . Don't ever try to connect (as a client) to a place our
5678 firewall options forbid.
5679 . If we specify a proxy and also firewall options, obey the
5680 firewall options even when we're using the proxy: some proxies
5681 can only proxy to certain destinations.
5682 - Fix a bug found by Lasse Overlier: when we were making internal
5683 circuits (intended to be cannibalized later for rendezvous and
5684 introduction circuits), we were picking them so that they had
5685 useful exit nodes. There was no need for this, and it actually
5686 aids some statistical attacks.
5687 - Start treating internal circuits and exit circuits separately.
5688 It's important to keep them separate because internal circuits
5689 have their last hops picked like middle hops, rather than like
5690 exit hops. So exiting on them will break the user's expectations.
5692 o Bugfixes on 0.1.1.x:
5693 - Take out the mis-feature where we tried to detect IP address
5694 flapping for people with DynDNS, and chose not to upload a new
5695 server descriptor sometimes.
5696 - Try to be compatible with OpenSSL 0.9.6 again.
5697 - Log fix: when the controller is logging about .onion addresses,
5698 sometimes it didn't include the ".onion" part of the address.
5699 - Don't try to modify options->DirServers internally -- if the
5700 user didn't specify any, just add the default ones directly to
5701 the trusted dirserver list. This fixes a bug where people running
5702 controllers would use SETCONF on some totally unrelated config
5703 option, and Tor would start yelling at them about changing their
5705 - Let the controller's redirectstream command specify a port, in
5706 case the controller wants to change that too.
5707 - When we requested a pile of server descriptors, we sometimes
5708 accidentally launched a duplicate request for the first one.
5709 - Bugfix for trackhostexits: write down the fingerprint of the
5710 chosen exit, not its nickname, because the chosen exit might not
5712 - When parsing foo.exit, if foo is unknown, and we are leaving
5713 circuits unattached, set the chosen_exit field and leave the
5714 address empty. This matters because controllers got confused
5716 - Directory authorities no longer try to download server
5717 descriptors that they know they will reject.
5719 o Features and updates:
5720 - Replace balanced trees with hash tables: this should make stuff
5721 significantly faster.
5722 - Resume using the AES counter-mode implementation that we ship,
5723 rather than OpenSSL's. Ours is significantly faster.
5724 - Many other CPU and memory improvements.
5725 - Add a new config option FastFirstHopPK (on by default) so clients
5726 do a trivial crypto handshake for their first hop, since TLS has
5727 already taken care of confidentiality and authentication.
5728 - Add a new config option TestSocks so people can see if their
5729 applications are using socks4, socks4a, socks5-with-ip, or
5730 socks5-with-hostname. This way they don't have to keep mucking
5731 with tcpdump and wondering if something got cached somewhere.
5732 - Warn when listening on a public address for socks. I suspect a
5733 lot of people are setting themselves up as open socks proxies,
5734 and they have no idea that jerks on the Internet are using them,
5735 since they simply proxy the traffic into the Tor network.
5736 - Add "private:*" as an alias in configuration for policies. Now
5737 you can simplify your exit policy rather than needing to list
5738 every single internal or nonroutable network space.
5739 - Add a new controller event type that allows controllers to get
5740 all server descriptors that were uploaded to a router in its role
5741 as authoritative dirserver.
5742 - Start shipping socks-extensions.txt, tor-doc-unix.html,
5743 tor-doc-server.html, and stylesheet.css in the tarball.
5744 - Stop shipping tor-doc.html in the tarball.
5747 Changes in version 0.1.1.9-alpha - 2005-11-15
5748 o Usability improvements:
5749 - Start calling it FooListenAddress rather than FooBindAddress,
5750 since few of our users know what it means to bind an address
5752 - Reduce clutter in server logs. We're going to try to make
5753 them actually usable now. New config option ProtocolWarnings that
5754 lets you hear about how _other Tors_ are breaking the protocol. Off
5756 - Divide log messages into logging domains. Once we put some sort
5757 of interface on this, it will let people looking at more verbose
5758 log levels specify the topics they want to hear more about.
5759 - Make directory servers return better http 404 error messages
5760 instead of a generic "Servers unavailable".
5761 - Check for even more Windows version flags when writing the platform
5762 string in server descriptors, and note any we don't recognize.
5763 - Clean up more of the OpenSSL memory when exiting, so we can detect
5764 memory leaks better.
5765 - Make directory authorities be non-versioning, non-naming by
5766 default. Now we can add new directory servers without requiring
5767 their operators to pay close attention.
5768 - When logging via syslog, include the pid whenever we provide
5769 a log entry. Suggested by Todd Fries.
5771 o Performance improvements:
5772 - Directory servers now silently throw away new descriptors that
5773 haven't changed much if the timestamps are similar. We do this to
5774 tolerate older Tor servers that upload a new descriptor every 15
5775 minutes. (It seemed like a good idea at the time.)
5776 - Inline bottleneck smartlist functions; use fast versions by default.
5777 - Add a "Map from digest to void*" abstraction digestmap_t so we
5778 can do less hex encoding/decoding. Use it in router_get_by_digest()
5779 to resolve a performance bottleneck.
5780 - Allow tor_gzip_uncompress to extract as much as possible from
5781 truncated compressed data. Try to extract as many
5782 descriptors as possible from truncated http responses (when
5783 DIR_PURPOSE_FETCH_ROUTERDESC).
5784 - Make circ->onionskin a pointer, not a static array. moria2 was using
5785 125000 circuit_t's after it had been up for a few weeks, which
5786 translates to 20+ megs of wasted space.
5787 - The private half of our EDH handshake keys are now chosen out
5788 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
5790 o Security improvements:
5791 - Start making directory caches retain old routerinfos, so soon
5792 clients can start asking by digest of descriptor rather than by
5793 fingerprint of server.
5794 - Add half our entropy from RAND_poll in OpenSSL. This knows how
5795 to use egd (if present), openbsd weirdness (if present), vms/os2
5796 weirdness (if we ever port there), and more in the future.
5798 o Bugfixes on 0.1.0.x:
5799 - Do round-robin writes of at most 16 kB per write. This might be
5800 more fair on loaded Tor servers, and it might resolve our Windows
5801 crash bug. It might also slow things down.
5802 - Our TLS handshakes were generating a single public/private
5803 keypair for the TLS context, rather than making a new one for
5804 each new connections. Oops. (But we were still rotating them
5805 periodically, so it's not so bad.)
5806 - When we were cannibalizing a circuit with a particular exit
5807 node in mind, we weren't checking to see if that exit node was
5808 already present earlier in the circuit. Oops.
5809 - When a Tor server's IP changes (e.g. from a dyndns address),
5810 upload a new descriptor so clients will learn too.
5811 - Really busy servers were keeping enough circuits open on stable
5812 connections that they were wrapping around the circuit_id
5813 space. (It's only two bytes.) This exposed a bug where we would
5814 feel free to reuse a circuit_id even if it still exists but has
5815 been marked for close. Try to fix this bug. Some bug remains.
5816 - If we would close a stream early (e.g. it asks for a .exit that
5817 we know would refuse it) but the LeaveStreamsUnattached config
5818 option is set by the controller, then don't close it.
5820 o Bugfixes on 0.1.1.8-alpha:
5821 - Fix a big pile of memory leaks, some of them serious.
5822 - Do not try to download a routerdesc if we would immediately reject
5824 - Resume inserting a newline between all router descriptors when
5825 generating (old style) signed directories, since our spec says
5827 - When providing content-type application/octet-stream for
5828 server descriptors using .z, we were leaving out the
5829 content-encoding header. Oops. (Everything tolerated this just
5830 fine, but that doesn't mean we need to be part of the problem.)
5831 - Fix a potential seg fault in getconf and getinfo using version 1
5832 of the controller protocol.
5833 - Avoid crash: do not check whether DirPort is reachable when we
5834 are suppressing it because of hibernation.
5835 - Make --hash-password not crash on exit.
5838 Changes in version 0.1.1.8-alpha - 2005-10-07
5839 o New features (major):
5840 - Clients don't download or use the directory anymore. Now they
5841 download and use network-statuses from the trusted dirservers,
5842 and fetch individual server descriptors as needed from mirrors.
5843 See dir-spec.txt for all the gory details.
5844 - Be more conservative about whether to advertise our DirPort.
5845 The main change is to not advertise if we're running at capacity
5846 and either a) we could hibernate or b) our capacity is low and
5847 we're using a default DirPort.
5848 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
5850 o New features (minor):
5851 - Try to be smart about when to retry network-status and
5852 server-descriptor fetches. Still needs some tuning.
5853 - Stop parsing, storing, or using running-routers output (but
5854 mirrors still cache and serve it).
5855 - Consider a threshold of versioning dirservers (dirservers who have
5856 an opinion about which Tor versions are still recommended) before
5857 deciding whether to warn the user that he's obsolete.
5858 - Dirservers can now reject/invalidate by key and IP, with the
5859 config options "AuthDirInvalid" and "AuthDirReject". This is
5860 useful since currently we automatically list servers as running
5861 and usable even if we know they're jerks.
5862 - Provide dire warnings to any users who set DirServer; move it out
5863 of torrc.sample and into torrc.complete.
5864 - Add MyFamily to torrc.sample in the server section.
5865 - Add nicknames to the DirServer line, so we can refer to them
5866 without requiring all our users to memorize their IP addresses.
5867 - When we get an EOF or a timeout on a directory connection, note
5868 how many bytes of serverdesc we are dropping. This will help
5869 us determine whether it is smart to parse incomplete serverdesc
5871 - Add a new function to "change pseudonyms" -- that is, to stop
5872 using any currently-dirty circuits for new streams, so we don't
5873 link new actions to old actions. Currently it's only called on
5874 HUP (or SIGNAL RELOAD).
5875 - On sighup, if UseHelperNodes changed to 1, use new circuits.
5876 - Start using RAND_bytes rather than RAND_pseudo_bytes from
5877 OpenSSL. Also, reseed our entropy every hour, not just at
5878 startup. And entropy in 512-bit chunks, not 160-bit chunks.
5880 o Fixes on 0.1.1.7-alpha:
5881 - Nobody ever implemented EVENT_ADDRMAP for control protocol
5882 version 0, so don't let version 0 controllers ask for it.
5883 - If you requested something with too many newlines via the
5884 v1 controller protocol, you could crash tor.
5885 - Fix a number of memory leaks, including some pretty serious ones.
5886 - Re-enable DirPort testing again, so Tor servers will be willing
5887 to advertise their DirPort if it's reachable.
5888 - On TLS handshake, only check the other router's nickname against
5889 its expected nickname if is_named is set.
5891 o Fixes forward-ported from 0.1.0.15:
5892 - Don't crash when we don't have any spare file descriptors and we
5893 try to spawn a dns or cpu worker.
5894 - Make the numbers in read-history and write-history into uint64s,
5895 so they don't overflow and publish negatives in the descriptor.
5898 - For the OS X package's modified privoxy config file, comment
5899 out the "logfile" line so we don't log everything passed
5901 - We were whining about using socks4 or socks5-with-local-lookup
5902 even when it's an IP in the "virtual" range we designed exactly
5904 - We were leaking some memory every time the client changes IPs.
5905 - Never call free() on tor_malloc()d memory. This will help us
5906 use dmalloc to detect memory leaks.
5907 - Check for named servers when looking them up by nickname;
5908 warn when we'recalling a non-named server by its nickname;
5909 don't warn twice about the same name.
5910 - Try to list MyFamily elements by key, not by nickname, and warn
5911 if we've not heard of the server.
5912 - Make windows platform detection (uname equivalent) smarter.
5913 - It turns out sparc64 doesn't like unaligned access either.
5916 Changes in version 0.1.0.15 - 2005-09-23
5917 o Bugfixes on 0.1.0.x:
5918 - Reject ports 465 and 587 (spam targets) in default exit policy.
5919 - Don't crash when we don't have any spare file descriptors and we
5920 try to spawn a dns or cpu worker.
5921 - Get rid of IgnoreVersion undocumented config option, and make us
5922 only warn, never exit, when we're running an obsolete version.
5923 - Don't try to print a null string when your server finds itself to
5924 be unreachable and the Address config option is empty.
5925 - Make the numbers in read-history and write-history into uint64s,
5926 so they don't overflow and publish negatives in the descriptor.
5927 - Fix a minor memory leak in smartlist_string_remove().
5928 - We were only allowing ourselves to upload a server descriptor at
5929 most every 20 minutes, even if it changed earlier than that.
5930 - Clean up log entries that pointed to old URLs.
5933 Changes in version 0.1.1.7-alpha - 2005-09-14
5934 o Fixes on 0.1.1.6-alpha:
5935 - Exit servers were crashing when people asked them to make a
5936 connection to an address not in their exit policy.
5937 - Looking up a non-existent stream for a v1 control connection would
5939 - Fix a seg fault if we ask a dirserver for a descriptor by
5940 fingerprint but he doesn't know about him.
5941 - SETCONF was appending items to linelists, not clearing them.
5942 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
5943 out and refuse the setconf if it would fail.
5944 - Downgrade the dirserver log messages when whining about
5948 - Add Peter Palfrader's check-tor script to tor/contrib/
5949 It lets you easily check whether a given server (referenced by
5950 nickname) is reachable by you.
5951 - Numerous changes to move towards client-side v2 directories. Not
5955 - If the user gave tor an odd number of command-line arguments,
5956 we were silently ignoring the last one. Now we complain and fail.
5957 [This wins the oldest-bug prize -- this bug has been present since
5958 November 2002, as released in Tor 0.0.0.]
5959 - Do not use unaligned memory access on alpha, mips, or mipsel.
5960 It *works*, but is very slow, so we treat them as if it doesn't.
5961 - Retry directory requests if we fail to get an answer we like
5962 from a given dirserver (we were retrying before, but only if
5963 we fail to connect).
5964 - When writing the RecommendedVersions line, sort them first.
5965 - When the client asked for a rendezvous port that the hidden
5966 service didn't want to provide, we were sending an IP address
5967 back along with the end cell. Fortunately, it was zero. But stop
5969 - Correct "your server is reachable" log entries to indicate that
5970 it was self-testing that told us so.
5973 Changes in version 0.1.1.6-alpha - 2005-09-09
5974 o Fixes on 0.1.1.5-alpha:
5975 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
5976 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
5977 - Fix bug with tor_memmem finding a match at the end of the string.
5978 - Make unit tests run without segfaulting.
5979 - Resolve some solaris x86 compile warnings.
5980 - Handle duplicate lines in approved-routers files without warning.
5981 - Fix bug where as soon as a server refused any requests due to his
5982 exit policy (e.g. when we ask for localhost and he tells us that's
5983 127.0.0.1 and he won't do it), we decided he wasn't obeying his
5984 exit policy using him for any exits.
5985 - Only do openssl hardware accelerator stuff if openssl version is
5988 o New controller features/fixes:
5989 - Add a "RESETCONF" command so you can set config options like
5990 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
5991 a config option in the torrc with no value, then it clears it
5992 entirely (rather than setting it to its default).
5993 - Add a "GETINFO config-file" to tell us where torrc is.
5994 - Avoid sending blank lines when GETINFO replies should be empty.
5995 - Add a QUIT command for the controller (for using it manually).
5996 - Fix a bug in SAVECONF that was adding default dirservers and
5997 other redundant entries to the torrc file.
5999 o Start on the new directory design:
6000 - Generate, publish, cache, serve new network-status format.
6001 - Publish individual descriptors (by fingerprint, by "all", and by
6003 - Publish client and server recommended versions separately.
6004 - Allow tor_gzip_uncompress() to handle multiple concatenated
6005 compressed strings. Serve compressed groups of router
6006 descriptors. The compression logic here could be more
6008 - Distinguish v1 authorities (all currently trusted directories)
6009 from v2 authorities (all trusted directories).
6010 - Change DirServers config line to note which dirs are v1 authorities.
6011 - Add configuration option "V1AuthoritativeDirectory 1" which
6012 moria1, moria2, and tor26 should set.
6013 - Remove option when getting directory cache to see whether they
6014 support running-routers; they all do now. Replace it with one
6015 to see whether caches support v2 stuff.
6018 - Dirservers now do their own external reachability testing of each
6019 Tor server, and only list them as running if they've been found to
6020 be reachable. We also send back warnings to the server's logs if
6021 it uploads a descriptor that we already believe is unreachable.
6022 - Implement exit enclaves: if we know an IP address for the
6023 destination, and there's a running Tor server at that address
6024 which allows exit to the destination, then extend the circuit to
6025 that exit first. This provides end-to-end encryption and end-to-end
6026 authentication. Also, if the user wants a .exit address or enclave,
6027 use 4 hops rather than 3, and cannibalize a general circ for it
6029 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
6030 controller. Also, rotate dns and cpu workers if the controller
6031 changes options that will affect them; and initialize the dns
6032 worker cache tree whether or not we start out as a server.
6033 - Only upload a new server descriptor when options change, 18
6034 hours have passed, uptime is reset, or bandwidth changes a lot.
6035 - Check [X-]Forwarded-For headers in HTTP requests when generating
6036 log messages. This lets people run dirservers (and caches) behind
6037 Apache but still know which IP addresses are causing warnings.
6039 o Config option changes:
6040 - Replace (Fascist)Firewall* config options with a new
6041 ReachableAddresses option that understands address policies.
6042 For example, "ReachableAddresses *:80,*:443"
6043 - Get rid of IgnoreVersion undocumented config option, and make us
6044 only warn, never exit, when we're running an obsolete version.
6045 - Make MonthlyAccountingStart config option truly obsolete now.
6048 - Reject ports 465 and 587 in the default exit policy, since
6049 people have started using them for spam too.
6050 - It turns out we couldn't bootstrap a network since we added
6051 reachability detection in 0.1.0.1-rc. Good thing the Tor network
6052 has never gone down. Add an AssumeReachable config option to let
6053 servers and dirservers bootstrap. When we're trying to build a
6054 high-uptime or high-bandwidth circuit but there aren't enough
6055 suitable servers, try being less picky rather than simply failing.
6056 - Our logic to decide if the OR we connected to was the right guy
6057 was brittle and maybe open to a mitm for unverified routers.
6058 - We weren't cannibalizing circuits correctly for
6059 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
6060 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
6061 build those from scratch. This should make hidden services faster.
6062 - Predict required circuits better, with an eye toward making hidden
6063 services faster on the service end.
6064 - Retry streams if the exit node sends back a 'misc' failure. This
6065 should result in fewer random failures. Also, after failing
6066 from resolve failed or misc, reset the num failures, so we give
6067 it a fair shake next time we try.
6068 - Clean up the rendezvous warn log msgs, and downgrade some to info.
6069 - Reduce severity on logs about dns worker spawning and culling.
6070 - When we're shutting down and we do something like try to post a
6071 server descriptor or rendezvous descriptor, don't complain that
6072 we seem to be unreachable. Of course we are, we're shutting down.
6073 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
6074 We don't use them yet, but maybe one day our DNS resolver will be
6075 able to discover them.
6076 - Make ContactInfo mandatory for authoritative directory servers.
6077 - Require server descriptors to list IPv4 addresses -- hostnames
6078 are no longer allowed. This also fixes some potential security
6079 problems with people providing hostnames as their address and then
6080 preferentially resolving them to partition users.
6081 - Change log line for unreachability to explicitly suggest /etc/hosts
6082 as the culprit. Also make it clearer what IP address and ports we're
6083 testing for reachability.
6084 - Put quotes around user-supplied strings when logging so users are
6085 more likely to realize if they add bad characters (like quotes)
6087 - Let auth dir servers start without specifying an Address config
6089 - Make unit tests (and other invocations that aren't the real Tor)
6090 run without launching listeners, creating subdirectories, and so on.
6093 Changes in version 0.1.1.5-alpha - 2005-08-08
6094 o Bugfixes included in 0.1.0.14.
6096 o Bugfixes on 0.1.0.x:
6097 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
6098 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
6099 it would silently using ignore the 6668.
6102 Changes in version 0.1.0.14 - 2005-08-08
6103 o Bugfixes on 0.1.0.x:
6104 - Fix the other half of the bug with crypto handshakes
6106 - Fix an assert trigger if you send a 'signal term' via the
6107 controller when it's listening for 'event info' messages.
6110 Changes in version 0.1.1.4-alpha - 2005-08-04
6111 o Bugfixes included in 0.1.0.13.
6114 - Improve tor_gettimeofday() granularity on windows.
6115 - Make clients regenerate their keys when their IP address changes.
6116 - Implement some more GETINFO goodness: expose helper nodes, config
6117 options, getinfo keys.
6120 Changes in version 0.1.0.13 - 2005-08-04
6121 o Bugfixes on 0.1.0.x:
6122 - Fix a critical bug in the security of our crypto handshakes.
6123 - Fix a size_t underflow in smartlist_join_strings2() that made
6124 it do bad things when you hand it an empty smartlist.
6125 - Fix Windows installer to ship Tor license (thanks to Aphex for
6126 pointing out this oversight) and put a link to the doc directory
6128 - Explicitly set no-unaligned-access for sparc: it turns out the
6129 new gcc's let you compile broken code, but that doesn't make it
6133 Changes in version 0.1.1.3-alpha - 2005-07-23
6134 o Bugfixes on 0.1.1.2-alpha:
6135 - Fix a bug in handling the controller's "post descriptor"
6137 - Fix several bugs in handling the controller's "extend circuit"
6139 - Fix a bug in handling the controller's "stream status" event.
6140 - Fix an assert failure if we have a controller listening for
6141 circuit events and we go offline.
6142 - Re-allow hidden service descriptors to publish 0 intro points.
6143 - Fix a crash when generating your hidden service descriptor if
6144 you don't have enough intro points already.
6146 o New features on 0.1.1.2-alpha:
6147 - New controller function "getinfo accounting", to ask how
6148 many bytes we've used in this time period.
6149 - Experimental support for helper nodes: a lot of the risk from
6150 a small static adversary comes because users pick new random
6151 nodes every time they rebuild a circuit. Now users will try to
6152 stick to the same small set of entry nodes if they can. Not
6153 enabled by default yet.
6155 o Bugfixes on 0.1.0.12:
6156 - If you're an auth dir server, always publish your dirport,
6157 even if you haven't yet found yourself to be reachable.
6158 - Fix a size_t underflow in smartlist_join_strings2() that made
6159 it do bad things when you hand it an empty smartlist.
6162 Changes in version 0.1.0.12 - 2005-07-18
6163 o New directory servers:
6164 - tor26 has changed IP address.
6166 o Bugfixes on 0.1.0.x:
6167 - Fix a possible double-free in tor_gzip_uncompress().
6168 - When --disable-threads is set, do not search for or link against
6170 - Don't trigger an assert if an authoritative directory server
6171 claims its dirport is 0.
6172 - Fix bug with removing Tor as an NT service: some people were
6173 getting "The service did not return an error." Thanks to Matt
6177 Changes in version 0.1.1.2-alpha - 2005-07-15
6178 o New directory servers:
6179 - tor26 has changed IP address.
6181 o Bugfixes on 0.1.0.x, crashes/leaks:
6182 - Port the servers-not-obeying-their-exit-policies fix from
6184 - Fix an fd leak in start_daemon().
6185 - On Windows, you can't always reopen a port right after you've
6186 closed it. So change retry_listeners() to only close and re-open
6187 ports that have changed.
6188 - Fix a possible double-free in tor_gzip_uncompress().
6190 o Bugfixes on 0.1.0.x, usability:
6191 - When tor_socketpair() fails in Windows, give a reasonable
6192 Windows-style errno back.
6193 - Let people type "tor --install" as well as "tor -install" when
6195 want to make it an NT service.
6196 - NT service patch from Matt Edman to improve error messages.
6197 - When the controller asks for a config option with an abbreviated
6198 name, give the full name in our response.
6199 - Correct the man page entry on TrackHostExitsExpire.
6200 - Looks like we were never delivering deflated (i.e. compressed)
6201 running-routers lists, even when asked. Oops.
6202 - When --disable-threads is set, do not search for or link against
6205 o Bugfixes on 0.1.1.x:
6206 - Fix a seg fault with autodetecting which controller version is
6210 - New hidden service descriptor format: put a version in it, and
6211 let people specify introduction/rendezvous points that aren't
6212 in "the directory" (which is subjective anyway).
6213 - Allow the DEBUG controller event to work again. Mark certain log
6214 entries as "don't tell this to controllers", so we avoid cycles.
6217 Changes in version 0.1.0.11 - 2005-06-30
6218 o Bugfixes on 0.1.0.x:
6219 - Fix major security bug: servers were disregarding their
6220 exit policies if clients behaved unexpectedly.
6221 - Make OS X init script check for missing argument, so we don't
6222 confuse users who invoke it incorrectly.
6223 - Fix a seg fault in "tor --hash-password foo".
6224 - The MAPADDRESS control command was broken.
6227 Changes in version 0.1.1.1-alpha - 2005-06-29
6229 - Make OS X init script check for missing argument, so we don't
6230 confuse users who invoke it incorrectly.
6231 - Fix a seg fault in "tor --hash-password foo".
6232 - Fix a possible way to DoS dirservers.
6233 - When we complain that your exit policy implicitly allows local or
6234 private address spaces, name them explicitly so operators can
6236 - Make the log message less scary when all the dirservers are
6237 temporarily unreachable.
6238 - We were printing the number of idle dns workers incorrectly when
6242 - Revised controller protocol (version 1) that uses ascii rather
6243 than binary. Add supporting libraries in python and java so you
6244 can use the controller from your applications without caring how
6246 - Spiffy new support for crypto hardware accelerators. Can somebody
6250 Changes in version 0.0.9.10 - 2005-06-16
6251 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
6252 - Refuse relay cells that claim to have a length larger than the
6253 maximum allowed. This prevents a potential attack that could read
6254 arbitrary memory (e.g. keys) from an exit server's process
6258 Changes in version 0.1.0.10 - 2005-06-14
6259 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
6260 libevent before 1.1a.
6263 Changes in version 0.1.0.9-rc - 2005-06-09
6265 - Reset buf->highwater every time buf_shrink() is called, not just on
6266 a successful shrink. This was causing significant memory bloat.
6267 - Fix buffer overflow when checking hashed passwords.
6268 - Security fix: if seeding the RNG on Win32 fails, quit.
6269 - Allow seeding the RNG on Win32 even when you're not running as
6271 - Disable threading on Solaris too. Something is wonky with it,
6272 cpuworkers, and reentrant libs.
6273 - Reenable the part of the code that tries to flush as soon as an
6274 OR outbuf has a full TLS record available. Perhaps this will make
6275 OR outbufs not grow as huge except in rare cases, thus saving lots
6276 of CPU time plus memory.
6277 - Reject malformed .onion addresses rather then passing them on as
6278 normal web requests.
6279 - Adapt patch from Adam Langley: fix possible memory leak in
6280 tor_lookup_hostname().
6281 - Initialize libevent later in the startup process, so the logs are
6282 already established by the time we start logging libevent warns.
6283 - Use correct errno on win32 if libevent fails.
6284 - Check and warn about known-bad/slow libevent versions.
6285 - Pay more attention to the ClientOnly config option.
6286 - Have torctl.in/tor.sh.in check for location of su binary (needed
6288 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
6289 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
6290 HttpProxyAuthenticator
6291 - Stop warning about sigpipes in the logs. We're going to
6292 pretend that getting these occassionally is normal and fine.
6293 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
6295 installer screens; and don't put stuff into StartupItems unless
6296 the user asks you to.
6297 - Require servers that use the default dirservers to have public IP
6298 addresses. We have too many servers that are configured with private
6299 IPs and their admins never notice the log entries complaining that
6300 their descriptors are being rejected.
6301 - Add OSX uninstall instructions. An actual uninstall script will
6305 Changes in version 0.1.0.8-rc - 2005-05-23
6307 - It turns out that kqueue on OS X 10.3.9 was causing kernel
6308 panics. Disable kqueue on all OS X Tors.
6309 - Fix RPM: remove duplicate line accidentally added to the rpm
6311 - Disable threads on openbsd too, since its gethostaddr is not
6313 - Tolerate libevent 0.8 since it still works, even though it's
6315 - Enable building on Red Hat 9.0 again.
6316 - Allow the middle hop of the testing circuit to be running any
6317 version, now that most of them have the bugfix to let them connect
6318 to unknown servers. This will allow reachability testing to work
6319 even when 0.0.9.7-0.0.9.9 become obsolete.
6320 - Handle relay cells with rh.length too large. This prevents
6321 a potential attack that could read arbitrary memory (maybe even
6322 keys) from the exit server's process.
6323 - We screwed up the dirport reachability testing when we don't yet
6324 have a cached version of the directory. Hopefully now fixed.
6325 - Clean up router_load_single_router() (used by the controller),
6326 so it doesn't seg fault on error.
6327 - Fix a minor memory leak when somebody establishes an introduction
6328 point at your Tor server.
6329 - If a socks connection ends because read fails, don't warn that
6330 you're not sending a socks reply back.
6333 - Add HttpProxyAuthenticator config option too, that works like
6334 the HttpsProxyAuthenticator config option.
6335 - Encode hashed controller passwords in hex instead of base64,
6336 to make it easier to write controllers.
6339 Changes in version 0.1.0.7-rc - 2005-05-17
6341 - Fix a bug in the OS X package installer that prevented it from
6342 installing on Tiger.
6343 - Fix a script bug in the OS X package installer that made it
6344 complain during installation.
6345 - Find libevent even if it's hiding in /usr/local/ and your
6346 CFLAGS and LDFLAGS don't tell you to look there.
6347 - Be able to link with libevent as a shared library (the default
6348 after 1.0d), even if it's hiding in /usr/local/lib and even
6349 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
6350 assuming you're running gcc. Otherwise fail and give a useful
6352 - Fix a bug in the RPM packager: set home directory for _tor to
6353 something more reasonable when first installing.
6354 - Free a minor amount of memory that is still reachable on exit.
6357 Changes in version 0.1.0.6-rc - 2005-05-14
6359 - Implement --disable-threads configure option. Disable threads on
6360 netbsd by default, because it appears to have no reentrant resolver
6362 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
6363 release (1.1) detects and disables kqueue if it's broken.
6364 - Append default exit policy before checking for implicit internal
6365 addresses. Now we don't log a bunch of complaints on startup
6366 when using the default exit policy.
6367 - Some people were putting "Address " in their torrc, and they had
6368 a buggy resolver that resolved " " to 0.0.0.0. Oops.
6369 - If DataDir is ~/.tor, and that expands to /.tor, then default to
6370 LOCALSTATEDIR/tor instead.
6371 - Fix fragmented-message bug in TorControl.py.
6372 - Resolve a minor bug which would prevent unreachable dirports
6373 from getting suppressed in the published descriptor.
6374 - When the controller gave us a new descriptor, we weren't resolving
6375 it immediately, so Tor would think its address was 0.0.0.0 until
6376 we fetched a new directory.
6377 - Fix an uppercase/lowercase case error in suppressing a bogus
6378 libevent warning on some Linuxes.
6381 - Begin scrubbing sensitive strings from logs by default. Turn off
6382 the config option SafeLogging if you need to do debugging.
6383 - Switch to a new buffer management algorithm, which tries to avoid
6384 reallocing and copying quite as much. In first tests it looks like
6385 it uses *more* memory on average, but less cpu.
6386 - First cut at support for "create-fast" cells. Clients can use
6387 these when extending to their first hop, since the TLS already
6388 provides forward secrecy and authentication. Not enabled on
6390 - When dirservers refuse a router descriptor, we now log its
6391 contactinfo, platform, and the poster's IP address.
6392 - Call tor_free_all instead of connections_free_all after forking, to
6393 save memory on systems that need to fork.
6394 - Whine at you if you're a server and you don't set your contactinfo.
6395 - Implement --verify-config command-line option to check if your torrc
6396 is valid without actually launching Tor.
6397 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
6398 rather than just rejecting it.
6401 Changes in version 0.1.0.5-rc - 2005-04-27
6403 - Stop trying to print a null pointer if an OR conn fails because
6404 we didn't like its cert.
6406 - Switch our internal buffers implementation to use a ring buffer,
6407 to hopefully improve performance for fast servers a lot.
6408 - Add HttpsProxyAuthenticator support (basic auth only), based
6409 on patch from Adam Langley.
6410 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
6411 the fast servers that have been joining lately.
6412 - Give hidden service accesses extra time on the first attempt,
6413 since 60 seconds is often only barely enough. This might improve
6415 - Improve performance for dirservers: stop re-parsing the whole
6416 directory every time you regenerate it.
6417 - Add more debugging info to help us find the weird dns freebsd
6418 pthreads bug; cleaner debug messages to help track future issues.
6421 Changes in version 0.0.9.9 - 2005-04-23
6422 o Bugfixes on 0.0.9.x:
6423 - If unofficial Tor clients connect and send weird TLS certs, our
6424 Tor server triggers an assert. This release contains a minimal
6425 backport from the broader fix that we put into 0.1.0.4-rc.
6428 Changes in version 0.1.0.4-rc - 2005-04-23
6430 - If unofficial Tor clients connect and send weird TLS certs, our
6431 Tor server triggers an assert. Stop asserting, and start handling
6432 TLS errors better in other situations too.
6433 - When the controller asks us to tell it about all the debug-level
6434 logs, it turns out we were generating debug-level logs while
6435 telling it about them, which turns into a bad loop. Now keep
6436 track of whether you're sending a debug log to the controller,
6437 and don't log when you are.
6438 - Fix the "postdescriptor" feature of the controller interface: on
6439 non-complete success, only say "done" once.
6441 - Clients are now willing to load balance over up to 2mB, not 1mB,
6442 of advertised bandwidth capacity.
6443 - Add a NoPublish config option, so you can be a server (e.g. for
6444 testing running Tor servers in other Tor networks) without
6445 publishing your descriptor to the primary dirservers.
6448 Changes in version 0.1.0.3-rc - 2005-04-08
6449 o Improvements on 0.1.0.2-rc:
6450 - Client now retries when streams end early for 'hibernating' or
6451 'resource limit' reasons, rather than failing them.
6452 - More automated handling for dirserver operators:
6453 - Automatically approve nodes running 0.1.0.2-rc or later,
6454 now that the the reachability detection stuff is working.
6455 - Now we allow two unverified servers with the same nickname
6456 but different keys. But if a nickname is verified, only that
6457 nickname+key are allowed.
6458 - If you're an authdirserver connecting to an address:port,
6459 and it's not the OR you were expecting, forget about that
6460 descriptor. If he *was* the one you were expecting, then forget
6461 about all other descriptors for that address:port.
6462 - Allow servers to publish descriptors from 12 hours in the future.
6463 Corollary: only whine about clock skew from the dirserver if
6464 he's a trusted dirserver (since now even verified servers could
6465 have quite wrong clocks).
6466 - Adjust maximum skew and age for rendezvous descriptors: let skew
6467 be 48 hours rather than 90 minutes.
6468 - Efficiency improvements:
6469 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
6470 it much faster to look up a circuit for each relay cell.
6471 - Remove most calls to assert_all_pending_dns_resolves_ok(),
6472 since they're eating our cpu on exit nodes.
6473 - Stop wasting time doing a case insensitive comparison for every
6474 dns name every time we do any lookup. Canonicalize the names to
6475 lowercase and be done with it.
6476 - Start sending 'truncated' cells back rather than destroy cells,
6477 if the circuit closes in front of you. This means we won't have
6478 to abandon partially built circuits.
6479 - Only warn once per nickname from add_nickname_list_to_smartlist
6480 per failure, so an entrynode or exitnode choice that's down won't
6482 - Put a note in the torrc about abuse potential with the default
6484 - Revise control spec and implementation to allow all log messages to
6485 be sent to controller with their severities intact (suggested by
6486 Matt Edman). Update TorControl to handle new log event types.
6487 - Provide better explanation messages when controller's POSTDESCRIPTOR
6489 - Stop putting nodename in the Platform string in server descriptors.
6490 It doesn't actually help, and it is confusing/upsetting some people.
6492 o Bugfixes on 0.1.0.2-rc:
6493 - We were printing the host mask wrong in exit policies in server
6494 descriptors. This isn't a critical bug though, since we were still
6495 obeying the exit policy internally.
6496 - Fix Tor when compiled with libevent but without pthreads: move
6497 connection_unregister() from _connection_free() to
6499 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
6500 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
6501 when we look through the connection array, we'll find any of the
6502 cpu/dnsworkers. This is no good.
6504 o Bugfixes on 0.0.9.8:
6505 - Fix possible bug on threading platforms (e.g. win32) which was
6506 leaking a file descriptor whenever a cpuworker or dnsworker died.
6507 - When using preferred entry or exit nodes, ignore whether the
6508 circuit wants uptime or capacity. They asked for the nodes, they
6510 - chdir() to your datadirectory at the *end* of the daemonize process,
6511 not the beginning. This was a problem because the first time you
6512 run tor, if your datadir isn't there, and you have runasdaemon set
6513 to 1, it will try to chdir to it before it tries to create it. Oops.
6514 - Handle changed router status correctly when dirserver reloads
6515 fingerprint file. We used to be dropping all unverified descriptors
6516 right then. The bug was hidden because we would immediately
6517 fetch a directory from another dirserver, which would include the
6518 descriptors we just dropped.
6519 - When we're connecting to an OR and he's got a different nickname/key
6520 than we were expecting, only complain loudly if we're an OP or a
6521 dirserver. Complaining loudly to the OR admins just confuses them.
6522 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
6523 artificially capped at 500kB.
6526 Changes in version 0.0.9.8 - 2005-04-07
6527 o Bugfixes on 0.0.9.x:
6528 - We have a bug that I haven't found yet. Sometimes, very rarely,
6529 cpuworkers get stuck in the 'busy' state, even though the cpuworker
6530 thinks of itself as idle. This meant that no new circuits ever got
6531 established. Here's a workaround to kill any cpuworker that's been
6532 busy for more than 100 seconds.
6535 Changes in version 0.1.0.2-rc - 2005-04-01
6536 o Bugfixes on 0.1.0.1-rc:
6537 - Fixes on reachability detection:
6538 - Don't check for reachability while hibernating.
6539 - If ORPort is reachable but DirPort isn't, still publish the
6540 descriptor, but zero out DirPort until it's found reachable.
6541 - When building testing circs for ORPort testing, use only
6542 high-bandwidth nodes, so fewer circuits fail.
6543 - Complain about unreachable ORPort separately from unreachable
6544 DirPort, so the user knows what's going on.
6545 - Make sure we only conclude ORPort reachability if we didn't
6546 initiate the conn. Otherwise we could falsely conclude that
6547 we're reachable just because we connected to the guy earlier
6548 and he used that same pipe to extend to us.
6549 - Authdirservers shouldn't do ORPort reachability detection,
6550 since they're in clique mode, so it will be rare to find a
6551 server not already connected to them.
6552 - When building testing circuits, always pick middle hops running
6553 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
6554 bug. (This is a kludge; it will go away when 0.0.9.x becomes
6556 - When we decide we're reachable, actually publish our descriptor
6558 - Fix bug in redirectstream in the controller.
6559 - Fix the state descriptor strings so logs don't claim edge streams
6560 are in a different state than they actually are.
6561 - Use recent libevent features when possible (this only really affects
6562 win32 and osx right now, because the new libevent with these
6563 features hasn't been released yet). Add code to suppress spurious
6565 - Prevent possible segfault in connection_close_unattached_ap().
6566 - Fix newlines on torrc in win32.
6567 - Improve error msgs when tor-resolve fails.
6569 o Improvements on 0.0.9.x:
6570 - New experimental script tor/contrib/ExerciseServer.py (needs more
6571 work) that uses the controller interface to build circuits and
6572 fetch pages over them. This will help us bootstrap servers that
6573 have lots of capacity but haven't noticed it yet.
6574 - New experimental script tor/contrib/PathDemo.py (needs more work)
6575 that uses the controller interface to let you choose whole paths
6577 "<hostname>.<path,separated by dots>.<length of path>.path"
6578 - When we've connected to an OR and handshaked but didn't like
6579 the result, we were closing the conn without sending destroy
6580 cells back for pending circuits. Now send those destroys.
6583 Changes in version 0.0.9.7 - 2005-04-01
6584 o Bugfixes on 0.0.9.x:
6585 - Fix another race crash bug (thanks to Glenn Fink for reporting).
6586 - Compare identity to identity, not to nickname, when extending to
6587 a router not already in the directory. This was preventing us from
6588 extending to unknown routers. Oops.
6589 - Make sure to create OS X Tor user in <500 range, so we aren't
6590 creating actual system users.
6591 - Note where connection-that-hasn't-sent-end was marked, and fix
6592 a few really loud instances of this harmless bug (it's fixed more
6596 Changes in version 0.1.0.1-rc - 2005-03-28
6598 - Add reachability testing. Your Tor server will automatically try
6599 to see if its ORPort and DirPort are reachable from the outside,
6600 and it won't upload its descriptor until it decides they are.
6601 - Handle unavailable hidden services better. Handle slow or busy
6602 hidden services better.
6603 - Add support for CONNECTing through https proxies, with "HttpsProxy"
6605 - New exit policy: accept most low-numbered ports, rather than
6606 rejecting most low-numbered ports.
6607 - More Tor controller support (still experimental). See
6608 http://tor.eff.org/doc/control-spec.txt for all the new features,
6609 including signals to emulate unix signals from any platform;
6610 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
6611 closestream; closecircuit; etc.
6612 - Make nt services work and start on startup on win32 (based on
6613 patch by Matt Edman).
6614 - Add a new AddressMap config directive to rewrite incoming socks
6615 addresses. This lets you, for example, declare an implicit
6616 required exit node for certain sites.
6617 - Add a new TrackHostExits config directive to trigger addressmaps
6618 for certain incoming socks addresses -- for sites that break when
6619 your exit keeps changing (based on patch by Mike Perry).
6620 - Redo the client-side dns cache so it's just an addressmap too.
6621 - Notice when our IP changes, and reset stats/uptime/reachability.
6622 - When an application is using socks5, give him the whole variety of
6623 potential socks5 responses (connect refused, host unreachable, etc),
6624 rather than just "success" or "failure".
6625 - A more sane version numbering system. See
6626 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
6627 - New contributed script "exitlist": a simple python script to
6628 parse directories and find Tor nodes that exit to listed
6630 - New contributed script "privoxy-tor-toggle" to toggle whether
6631 Privoxy uses Tor. Seems to be configured for Debian by default.
6632 - Report HTTP reasons to client when getting a response from directory
6633 servers -- so you can actually know what went wrong.
6634 - New config option MaxAdvertisedBandwidth which lets you advertise
6635 a low bandwidthrate (to not attract as many circuits) while still
6636 allowing a higher bandwidthrate in reality.
6638 o Robustness/stability fixes:
6639 - Make Tor use Niels Provos's libevent instead of its current
6640 poll-but-sometimes-select mess. This will let us use faster async
6641 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
6643 - pthread support now too. This was forced because when we forked,
6644 we ended up wasting a lot of duplicate ram over time. Also switch
6645 to foo_r versions of some library calls to allow reentry and
6647 - Better handling for heterogeneous / unreliable nodes:
6648 - Annotate circuits w/ whether they aim to contain high uptime nodes
6649 and/or high capacity nodes. When building circuits, choose
6651 - This means that every single node in an intro rend circuit,
6652 not just the last one, will have a minimum uptime.
6653 - New config option LongLivedPorts to indicate application streams
6654 that will want high uptime circuits.
6655 - Servers reset uptime when a dir fetch entirely fails. This
6656 hopefully reflects stability of the server's network connectivity.
6657 - If somebody starts his tor server in Jan 2004 and then fixes his
6658 clock, don't make his published uptime be a year.
6659 - Reset published uptime when you wake up from hibernation.
6660 - Introduce a notion of 'internal' circs, which are chosen without
6661 regard to the exit policy of the last hop. Intro and rendezvous
6662 circs must be internal circs, to avoid leaking information. Resolve
6663 and connect streams can use internal circs if they want.
6664 - New circuit pooling algorithm: make sure to have enough circs around
6665 to satisfy any predicted ports, and also make sure to have 2 internal
6666 circs around if we've required internal circs lately (and with high
6667 uptime if we've seen that lately too).
6668 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
6669 which describes how often we retry making new circuits if current
6670 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
6671 how long we're willing to make use of an already-dirty circuit.
6672 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
6673 circ as necessary, if there are any completed ones lying around
6674 when we try to launch one.
6675 - Make hidden services try to establish a rendezvous for 30 seconds,
6676 rather than for n (where n=3) attempts to build a circuit.
6677 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
6678 "ShutdownWaitLength".
6679 - Try to be more zealous about calling connection_edge_end when
6680 things go bad with edge conns in connection.c.
6681 - Revise tor-spec to add more/better stream end reasons.
6682 - Revise all calls to connection_edge_end to avoid sending "misc",
6683 and to take errno into account where possible.
6686 - Fix a race condition that can trigger an assert, when we have a
6687 pending create cell and an OR connection fails right then.
6688 - Fix several double-mark-for-close bugs, e.g. where we were finding
6689 a conn for a cell even if that conn is already marked for close.
6690 - Make sequence of log messages when starting on win32 with no config
6691 file more reasonable.
6692 - When choosing an exit node for a new non-internal circ, don't take
6693 into account whether it'll be useful for any pending x.onion
6694 addresses -- it won't.
6695 - Turn addr_policy_compare from a tristate to a quadstate; this should
6696 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
6697 for google.com" problem.
6698 - Make "platform" string in descriptor more accurate for Win32 servers,
6699 so it's not just "unknown platform".
6700 - Fix an edge case in parsing config options (thanks weasel).
6701 If they say "--" on the commandline, it's not an option.
6702 - Reject odd-looking addresses at the client (e.g. addresses that
6703 contain a colon), rather than having the server drop them because
6705 - tor-resolve requests were ignoring .exit if there was a working circuit
6706 they could use instead.
6707 - REUSEADDR on normal platforms means you can rebind to the port
6708 right after somebody else has let it go. But REUSEADDR on win32
6709 means to let you bind to the port _even when somebody else
6710 already has it bound_! So, don't do that on Win32.
6711 - Change version parsing logic: a version is "obsolete" if it is not
6712 recommended and (1) there is a newer recommended version in the
6713 same series, or (2) there are no recommended versions in the same
6714 series, but there are some recommended versions in a newer series.
6715 A version is "new" if it is newer than any recommended version in
6717 - Stop most cases of hanging up on a socks connection without sending
6721 - Require BandwidthRate to be at least 20kB/s for servers.
6722 - When a dirserver causes you to give a warn, mention which dirserver
6724 - New config option DirAllowPrivateAddresses for authdirservers.
6725 Now by default they refuse router descriptors that have non-IP or
6726 private-IP addresses.
6727 - Stop publishing socksport in the directory, since it's not
6728 actually meant to be public. For compatibility, publish a 0 there
6730 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
6731 smart" value, that is low for servers and high for clients.
6732 - If our clock jumps forward by 100 seconds or more, assume something
6733 has gone wrong with our network and abandon all not-yet-used circs.
6734 - Warn when exit policy implicitly allows local addresses.
6735 - If we get an incredibly skewed timestamp from a dirserver mirror
6736 that isn't a verified OR, don't warn -- it's probably him that's
6738 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
6739 cookies to disk and doesn't log each web request to disk. (Thanks
6740 to Brett Carrington for pointing this out.)
6741 - When a client asks us for a dir mirror and we don't have one,
6742 launch an attempt to get a fresh one.
6743 - If we're hibernating and we get a SIGINT, exit immediately.
6744 - Add --with-dmalloc ./configure option, to track memory leaks.
6745 - And try to free all memory on closing, so we can detect what
6747 - Cache local dns resolves correctly even when they're .exit
6749 - Give a better warning when some other server advertises an
6750 ORPort that is actually an apache running ssl.
6751 - Add "opt hibernating 1" to server descriptor to make it clearer
6752 whether the server is hibernating.
6755 Changes in version 0.0.9.6 - 2005-03-24
6756 o Bugfixes on 0.0.9.x (crashes and asserts):
6757 - Add new end stream reasons to maintainance branch. Fix bug where
6758 reason (8) could trigger an assert. Prevent bug from recurring.
6759 - Apparently win32 stat wants paths to not end with a slash.
6760 - Fix assert triggers in assert_cpath_layer_ok(), where we were
6761 blowing away the circuit that conn->cpath_layer points to, then
6762 checking to see if the circ is well-formed. Backport check to make
6763 sure we dont use the cpath on a closed connection.
6764 - Prevent circuit_resume_edge_reading_helper() from trying to package
6765 inbufs for marked-for-close streams.
6766 - Don't crash on hup if your options->address has become unresolvable.
6767 - Some systems (like OS X) sometimes accept() a connection and tell
6768 you the remote host is 0.0.0.0:0. If this happens, due to some
6769 other mis-features, we get confused; so refuse the conn for now.
6771 o Bugfixes on 0.0.9.x (other):
6772 - Fix harmless but scary "Unrecognized content encoding" warn message.
6773 - Add new stream error reason: TORPROTOCOL reason means "you are not
6774 speaking a version of Tor I understand; say bye-bye to your stream."
6775 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
6776 into the future, now that we are more tolerant of skew. This
6777 resolves a bug where a Tor server would refuse to cache a directory
6778 because all the directories it gets are too far in the future;
6779 yet the Tor server never logs any complaints about clock skew.
6780 - Mac packaging magic: make man pages useable, and do not overwrite
6781 existing torrc files.
6782 - Make OS X log happily to /var/log/tor/tor.log
6785 Changes in version 0.0.9.5 - 2005-02-22
6786 o Bugfixes on 0.0.9.x:
6787 - Fix an assert race at exit nodes when resolve requests fail.
6788 - Stop picking unverified dir mirrors--it only leads to misery.
6789 - Patch from Matt Edman to make NT services work better. Service
6790 support is still not compiled into the executable by default.
6791 - Patch from Dmitri Bely so the Tor service runs better under
6792 the win32 SYSTEM account.
6793 - Make tor-resolve actually work (?) on Win32.
6794 - Fix a sign bug when getrlimit claims to have 4+ billion
6795 file descriptors available.
6796 - Stop refusing to start when bandwidthburst == bandwidthrate.
6797 - When create cells have been on the onion queue more than five
6798 seconds, just send back a destroy and take them off the list.
6801 Changes in version 0.0.9.4 - 2005-02-03
6802 o Bugfixes on 0.0.9:
6803 - Fix an assert bug that took down most of our servers: when
6804 a server claims to have 1 GB of bandwidthburst, don't
6806 - Don't crash as badly if we have spawned the max allowed number
6807 of dnsworkers, or we're out of file descriptors.
6808 - Block more file-sharing ports in the default exit policy.
6809 - MaxConn is now automatically set to the hard limit of max
6810 file descriptors we're allowed (ulimit -n), minus a few for
6812 - Give a clearer message when servers need to raise their
6813 ulimit -n when they start running out of file descriptors.
6814 - SGI Compatibility patches from Jan Schaumann.
6815 - Tolerate a corrupt cached directory better.
6816 - When a dirserver hasn't approved your server, list which one.
6817 - Go into soft hibernation after 95% of the bandwidth is used,
6818 not 99%. This is especially important for daily hibernators who
6819 have a small accounting max. Hopefully it will result in fewer
6820 cut connections when the hard hibernation starts.
6821 - Load-balance better when using servers that claim more than
6822 800kB/s of capacity.
6823 - Make NT services work (experimental, only used if compiled in).
6826 Changes in version 0.0.9.3 - 2005-01-21
6827 o Bugfixes on 0.0.9:
6828 - Backport the cpu use fixes from main branch, so busy servers won't
6829 need as much processor time.
6830 - Work better when we go offline and then come back, or when we
6831 run Tor at boot before the network is up. We do this by
6832 optimistically trying to fetch a new directory whenever an
6833 application request comes in and we think we're offline -- the
6834 human is hopefully a good measure of when the network is back.
6835 - Backport some minimal hidserv bugfixes: keep rend circuits open as
6836 long as you keep using them; actually publish hidserv descriptors
6837 shortly after they change, rather than waiting 20-40 minutes.
6838 - Enable Mac startup script by default.
6839 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
6840 - When you update AllowUnverifiedNodes or FirewallPorts via the
6841 controller's setconf feature, we were always appending, never
6843 - When you update HiddenServiceDir via setconf, it was screwing up
6844 the order of reading the lines, making it fail.
6845 - Do not rewrite a cached directory back to the cache; otherwise we
6846 will think it is recent and not fetch a newer one on startup.
6847 - Workaround for webservers that lie about Content-Encoding: Tor
6848 now tries to autodetect compressed directories and compression
6849 itself. This lets us Proxypass dir fetches through apache.
6852 Changes in version 0.0.9.2 - 2005-01-04
6853 o Bugfixes on 0.0.9 (crashes and asserts):
6854 - Fix an assert on startup when the disk is full and you're logging
6856 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
6857 style address, then we'd crash.
6858 - Fix an assert trigger when the running-routers string we get from
6859 a dirserver is broken.
6860 - Make worker threads start and run on win32. Now win32 servers
6862 - Bandaid (not actually fix, but now it doesn't crash) an assert
6863 where the dns worker dies mysteriously and the main Tor process
6864 doesn't remember anything about the address it was resolving.
6866 o Bugfixes on 0.0.9 (Win32):
6867 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
6868 name out of the warning/assert messages.
6869 - Fix a superficial "unhandled error on read" bug on win32.
6870 - The win32 installer no longer requires a click-through for our
6871 license, since our Free Software license grants rights but does not
6873 - Win32: When connecting to a dirserver fails, try another one
6874 immediately. (This was already working for non-win32 Tors.)
6875 - Stop trying to parse $HOME on win32 when hunting for default
6877 - Make tor-resolve.c work on win32 by calling network_init().
6879 o Bugfixes on 0.0.9 (other):
6880 - Make 0.0.9.x build on Solaris again.
6881 - Due to a fencepost error, we were blowing away the \n when reporting
6882 confvalue items in the controller. So asking for multiple config
6883 values at once couldn't work.
6884 - When listing circuits that are pending on an opening OR connection,
6885 if we're an OR we were listing circuits that *end* at us as
6886 being pending on every listener, dns/cpu worker, etc. Stop that.
6887 - Dirservers were failing to create 'running-routers' or 'directory'
6888 strings if we had more than some threshold of routers. Fix them so
6889 they can handle any number of routers.
6890 - Fix a superficial "Duplicate mark for close" bug.
6891 - Stop checking for clock skew for OR connections, even for servers.
6892 - Fix a fencepost error that was chopping off the last letter of any
6893 nickname that is the maximum allowed nickname length.
6894 - Update URLs in log messages so they point to the new website.
6895 - Fix a potential problem in mangling server private keys while
6896 writing to disk (not triggered yet, as far as we know).
6897 - Include the licenses for other free software we include in Tor,
6898 now that we're shipping binary distributions more regularly.
6901 Changes in version 0.0.9.1 - 2004-12-15
6902 o Bugfixes on 0.0.9:
6903 - Make hibernation actually work.
6904 - Make HashedControlPassword config option work.
6905 - When we're reporting event circuit status to a controller,
6906 don't use the stream status code.
6909 Changes in version 0.0.9 - 2004-12-12
6911 - Clean up manpage and torrc.sample file.
6912 - Clean up severities and text of log warnings.
6914 - Make servers trigger an assert when they enter hibernation.
6917 Changes in version 0.0.9rc7 - 2004-12-08
6918 o Bugfixes on 0.0.9rc:
6919 - Fix a stack-trashing crash when an exit node begins hibernating.
6920 - Avoid looking at unallocated memory while considering which
6921 ports we need to build circuits to cover.
6922 - Stop a sigpipe: when an 'end' cell races with eof from the app,
6923 we shouldn't hold-open-until-flush if the eof arrived first.
6924 - Fix a bug with init_cookie_authentication() in the controller.
6925 - When recommending new-format log lines, if the upper bound is
6926 LOG_ERR, leave it implicit.
6928 o Bugfixes on 0.0.8.1:
6929 - Fix a whole slew of memory leaks.
6930 - Fix isspace() and friends so they still make Solaris happy
6931 but also so they don't trigger asserts on win32.
6932 - Fix parse_iso_time on platforms without strptime (eg win32).
6933 - win32: tolerate extra "readable" events better.
6934 - win32: when being multithreaded, leave parent fdarray open.
6935 - Make unit tests work on win32.
6938 Changes in version 0.0.9rc6 - 2004-12-06
6939 o Bugfixes on 0.0.9pre:
6940 - Clean up some more integer underflow opportunities (not exploitable
6942 - While hibernating, hup should not regrow our listeners.
6943 - Send an end to the streams we close when we hibernate, rather
6944 than just chopping them off.
6945 - React to eof immediately on non-open edge connections.
6947 o Bugfixes on 0.0.8.1:
6948 - Calculate timeout for waiting for a connected cell from the time
6949 we sent the begin cell, not from the time the stream started. If
6950 it took a long time to establish the circuit, we would time out
6951 right after sending the begin cell.
6952 - Fix router_compare_addr_to_addr_policy: it was not treating a port
6953 of * as always matching, so we were picking reject *:* nodes as
6954 exit nodes too. Oops.
6957 - New circuit building strategy: keep a list of ports that we've
6958 used in the past 6 hours, and always try to have 2 circuits open
6959 or on the way that will handle each such port. Seed us with port
6960 80 so web users won't complain that Tor is "slow to start up".
6961 - Make kill -USR1 dump more useful stats about circuits.
6962 - When warning about retrying or giving up, print the address, so
6963 the user knows which one it's talking about.
6964 - If you haven't used a clean circuit in an hour, throw it away,
6965 just to be on the safe side. (This means after 6 hours a totally
6966 unused Tor client will have no circuits open.)
6969 Changes in version 0.0.9rc5 - 2004-12-01
6970 o Bugfixes on 0.0.8.1:
6971 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
6972 - Let resolve conns retry/expire also, rather than sticking around
6974 - If we are using select, make sure we stay within FD_SETSIZE.
6976 o Bugfixes on 0.0.9pre:
6977 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
6978 but doesn't seem to be currently; thanks to Ilja van Sprundel for
6980 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
6981 instead. Impose minima and maxima for all *Period options; impose
6982 even tighter maxima for fetching if we are a caching dirserver.
6983 Clip rather than rejecting.
6984 - Fetch cached running-routers from servers that serve it (that is,
6985 authdirservers and servers running 0.0.9rc5-cvs or later.)
6988 - Accept *:706 (silc) in default exit policy.
6989 - Implement new versioning format for post 0.1.
6990 - Support "foo.nickname.exit" addresses, to let Alice request the
6991 address "foo" as viewed by exit node "nickname". Based on a patch
6993 - Make tor --version --version dump the cvs Id of every file.
6996 Changes in version 0.0.9rc4 - 2004-11-28
6997 o Bugfixes on 0.0.8.1:
6998 - Make windows sockets actually non-blocking (oops), and handle
6999 win32 socket errors better.
7001 o Bugfixes on 0.0.9rc1:
7002 - Actually catch the -USR2 signal.
7005 Changes in version 0.0.9rc3 - 2004-11-25
7006 o Bugfixes on 0.0.8.1:
7007 - Flush the log file descriptor after we print "Tor opening log file",
7008 so we don't see those messages days later.
7010 o Bugfixes on 0.0.9rc1:
7011 - Make tor-resolve work again.
7012 - Avoid infinite loop in tor-resolve if tor hangs up on it.
7013 - Fix an assert trigger for clients/servers handling resolves.
7016 Changes in version 0.0.9rc2 - 2004-11-24
7017 o Bugfixes on 0.0.9rc1:
7018 - I broke socks5 support while fixing the eof bug.
7019 - Allow unitless bandwidths and intervals; they default to bytes
7021 - New servers don't start out hibernating; they are active until
7022 they run out of bytes, so they have a better estimate of how
7023 long it takes, and so their operators can know they're working.
7026 Changes in version 0.0.9rc1 - 2004-11-23
7027 o Bugfixes on 0.0.8.1:
7028 - Finally fix a bug that's been plaguing us for a year:
7029 With high load, circuit package window was reaching 0. Whenever
7030 we got a circuit-level sendme, we were reading a lot on each
7031 socket, but only writing out a bit. So we would eventually reach
7032 eof. This would be noticed and acted on even when there were still
7033 bytes sitting in the inbuf.
7034 - When poll() is interrupted, we shouldn't believe the revents values.
7036 o Bugfixes on 0.0.9pre6:
7037 - Fix hibernate bug that caused pre6 to be broken.
7038 - Don't keep rephist info for routers that haven't had activity for
7039 24 hours. (This matters now that clients have keys, since we track
7041 - Never call close_temp_logs while validating log options.
7042 - Fix backslash-escaping on tor.sh.in and torctl.in.
7045 - Implement weekly/monthly/daily accounting: now you specify your
7046 hibernation properties by
7047 AccountingMax N bytes|KB|MB|GB|TB
7048 AccountingStart day|week|month [day] HH:MM
7049 Defaults to "month 1 0:00".
7050 - Let bandwidth and interval config options be specified as 5 bytes,
7051 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
7052 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
7053 get back to normal.)
7054 - If your requested entry or exit node has advertised bandwidth 0,
7056 - Be more greedy about filling up relay cells -- we try reading again
7057 once we've processed the stuff we read, in case enough has arrived
7058 to fill the last cell completely.
7059 - Apply NT service patch from Osamu Fujino. Still needs more work.
7062 Changes in version 0.0.9pre6 - 2004-11-15
7063 o Bugfixes on 0.0.8.1:
7064 - Fix assert failure on malformed socks4a requests.
7065 - Use identity comparison, not nickname comparison, to choose which
7066 half of circuit-ID-space each side gets to use. This is needed
7067 because sometimes we think of a router as a nickname, and sometimes
7068 as a hex ID, and we can't predict what the other side will do.
7069 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
7070 write() call will fail and we handle it there.
7071 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
7072 and smartlist_len, which are two major profiling offenders.
7074 o Bugfixes on 0.0.9pre5:
7075 - Fix a bug in read_all that was corrupting config files on windows.
7076 - When we're raising the max number of open file descriptors to
7077 'unlimited', don't log that we just raised it to '-1'.
7078 - Include event code with events, as required by control-spec.txt.
7079 - Don't give a fingerprint when clients do --list-fingerprint:
7080 it's misleading, because it will never be the same again.
7081 - Stop using strlcpy in tor_strndup, since it was slowing us
7083 - Remove warn on startup about missing cached-directory file.
7084 - Make kill -USR1 work again.
7085 - Hibernate if we start tor during the "wait for wakeup-time" phase
7086 of an accounting interval. Log our hibernation plans better.
7087 - Authoritative dirservers now also cache their directory, so they
7088 have it on start-up.
7091 - Fetch running-routers; cache running-routers; compress
7092 running-routers; serve compressed running-routers.z
7093 - Add NSI installer script contributed by J Doe.
7094 - Commit VC6 and VC7 workspace/project files.
7095 - Commit a tor.spec for making RPM files, with help from jbash.
7096 - Add contrib/torctl.in contributed by Glenn Fink.
7097 - Implement the control-spec's SAVECONF command, to write your
7098 configuration to torrc.
7099 - Get cookie authentication for the controller closer to working.
7100 - Include control-spec.txt in the tarball.
7101 - When set_conf changes our server descriptor, upload a new copy.
7102 But don't upload it too often if there are frequent changes.
7103 - Document authentication config in man page, and document signals
7105 - Clean up confusing parts of man page and torrc.sample.
7106 - Make expand_filename handle ~ and ~username.
7107 - Use autoconf to enable largefile support where necessary. Use
7108 ftello where available, since ftell can fail at 2GB.
7109 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
7110 log more informatively.
7111 - Give a slightly more useful output for "tor -h".
7112 - Refuse application socks connections to port 0.
7113 - Check clock skew for verified servers, but allow unverified
7114 servers and clients to have any clock skew.
7115 - Break DirFetchPostPeriod into:
7116 - DirFetchPeriod for fetching full directory,
7117 - StatusFetchPeriod for fetching running-routers,
7118 - DirPostPeriod for posting server descriptor,
7119 - RendPostPeriod for posting hidden service descriptors.
7120 - Make sure the hidden service descriptors are at a random offset
7121 from each other, to hinder linkability.
7124 Changes in version 0.0.9pre5 - 2004-11-09
7125 o Bugfixes on 0.0.9pre4:
7126 - Fix a seg fault in unit tests (doesn't affect main program).
7127 - Fix an assert bug where a hidden service provider would fail if
7128 the first hop of his rendezvous circuit was down.
7129 - Hidden service operators now correctly handle version 1 style
7130 INTRODUCE1 cells (nobody generates them still, so not a critical
7132 - If do_hup fails, actually notice.
7133 - Handle more errnos from accept() without closing the listener.
7134 Some OpenBSD machines were closing their listeners because
7135 they ran out of file descriptors.
7136 - Send resolve cells to exit routers that are running a new
7137 enough version of the resolve code to work right.
7138 - Better handling of winsock includes on non-MSV win32 compilers.
7139 - Some people had wrapped their tor client/server in a script
7140 that would restart it whenever it died. This did not play well
7141 with our "shut down if your version is obsolete" code. Now people
7142 don't fetch a new directory if their local cached version is
7144 - Make our autogen.sh work on ksh as well as bash.
7147 - Hibernation: New config option "AccountingMaxKB" lets you
7148 set how many KBytes per month you want to allow your server to
7149 consume. Rather than spreading those bytes out evenly over the
7150 month, we instead hibernate for some of the month and pop up
7151 at a deterministic time, work until the bytes are consumed, then
7152 hibernate again. Config option "MonthlyAccountingStart" lets you
7153 specify which day of the month your billing cycle starts on.
7154 - Control interface: a separate program can now talk to your
7155 client/server over a socket, and get/set config options, receive
7156 notifications of circuits and streams starting/finishing/dying,
7157 bandwidth used, etc. The next step is to get some GUIs working.
7158 Let us know if you want to help out. See doc/control-spec.txt .
7159 - Ship a contrib/tor-control.py as an example script to interact
7160 with the control port.
7161 - "tor --hash-password zzyxz" will output a salted password for
7162 use in authenticating to the control interface.
7163 - New log format in config:
7164 "Log minsev[-maxsev] stdout|stderr|syslog" or
7165 "Log minsev[-maxsev] file /var/foo"
7168 - DirPolicy config option, to let people reject incoming addresses
7169 from their dirserver.
7170 - "tor --list-fingerprint" will list your identity key fingerprint
7172 - Add "pass" target for RedirectExit, to make it easier to break
7173 out of a sequence of RedirectExit rules.
7174 - Clients now generate a TLS cert too, in preparation for having
7175 them act more like real nodes.
7176 - Ship src/win32/ in the tarball, so people can use it to build.
7177 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
7179 - New "router-status" line in directory, to better bind each verified
7180 nickname to its identity key.
7181 - Deprecate unofficial config option abbreviations, and abbreviations
7182 not on the command line.
7183 - Add a pure-C tor-resolve implementation.
7184 - Use getrlimit and friends to ensure we can reach MaxConn (currently
7185 1024) file descriptors.
7187 o Code security improvements, inspired by Ilja:
7188 - Replace sprintf with snprintf. (I think they were all safe, but
7190 - Replace strcpy/strncpy with strlcpy in more places.
7191 - Avoid strcat; use snprintf or strlcat instead.
7192 - snprintf wrapper with consistent (though not C99) overflow behavior.
7195 Changes in version 0.0.9pre4 - 2004-10-17
7196 o Bugfixes on 0.0.9pre3:
7197 - If the server doesn't specify an exit policy, use the real default
7198 exit policy, not reject *:*.
7199 - Ignore fascistfirewall when uploading/downloading hidden service
7200 descriptors, since we go through Tor for those; and when using
7201 an HttpProxy, since we assume it can reach them all.
7202 - When looking for an authoritative dirserver, use only the ones
7203 configured at boot. Don't bother looking in the directory.
7204 - The rest of the fix for get_default_conf_file() on older win32.
7205 - Make 'Routerfile' config option obsolete.
7208 - New 'MyFamily nick1,...' config option for a server to
7209 specify other servers that shouldn't be used in the same circuit
7210 with it. Only believed if nick1 also specifies us.
7211 - New 'NodeFamily nick1,nick2,...' config option for a client to
7212 specify nodes that it doesn't want to use in the same circuit.
7213 - New 'Redirectexit pattern address:port' config option for a
7214 server to redirect exit connections, e.g. to a local squid.
7217 Changes in version 0.0.9pre3 - 2004-10-13
7218 o Bugfixes on 0.0.8.1:
7219 - Better torrc example lines for dirbindaddress and orbindaddress.
7220 - Improved bounds checking on parsed ints (e.g. config options and
7221 the ones we find in directories.)
7222 - Better handling of size_t vs int, so we're more robust on 64
7224 - Fix the rest of the bug where a newly started OR would appear
7225 as unverified even after we've added his fingerprint and hupped
7227 - Fix a bug from 0.0.7: when read() failed on a stream, we would
7228 close it without sending back an end. So 'connection refused'
7229 would simply be ignored and the user would get no response.
7231 o Bugfixes on 0.0.9pre2:
7232 - Serving the cached-on-disk directory to people is bad. We now
7233 provide no directory until we've fetched a fresh one.
7234 - Workaround for bug on windows where cached-directories get crlf
7236 - Make get_default_conf_file() work on older windows too.
7237 - If we write a *:* exit policy line in the descriptor, don't write
7238 any more exit policy lines.
7241 - Use only 0.0.9pre1 and later servers for resolve cells.
7242 - Make the dirservers file obsolete.
7243 - Include a dir-signing-key token in directories to tell the
7244 parsing entity which key is being used to sign.
7245 - Remove the built-in bulky default dirservers string.
7246 - New config option "Dirserver %s:%d [fingerprint]", which can be
7247 repeated as many times as needed. If no dirservers specified,
7248 default to moria1,moria2,tor26.
7249 - Make moria2 advertise a dirport of 80, so people behind firewalls
7250 will be able to get a directory.
7251 - Http proxy support
7252 - Dirservers translate requests for http://%s:%d/x to /x
7253 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
7254 be routed through this host.
7255 - Clients ask for /tor/x rather than /x for new enough dirservers.
7256 This way we can one day coexist peacefully with apache.
7257 - Clients specify a "Host: %s%d" http header, to be compatible
7258 with more proxies, and so running squid on an exit node can work.
7261 Changes in version 0.0.8.1 - 2004-10-13
7263 - Fix a seg fault that can be triggered remotely for Tor
7264 clients/servers with an open dirport.
7265 - Fix a rare assert trigger, where routerinfos for entries in
7266 our cpath would expire while we're building the path.
7267 - Fix a bug in OutboundBindAddress so it (hopefully) works.
7268 - Fix a rare seg fault for people running hidden services on
7269 intermittent connections.
7270 - Fix a bug in parsing opt keywords with objects.
7271 - Fix a stale pointer assert bug when a stream detaches and
7273 - Fix a string format vulnerability (probably not exploitable)
7274 in reporting stats locally.
7275 - Fix an assert trigger: sometimes launching circuits can fail
7276 immediately, e.g. because too many circuits have failed recently.
7277 - Fix a compile warning on 64 bit platforms.
7280 Changes in version 0.0.9pre2 - 2004-10-03
7282 - Make fetching a cached directory work for 64-bit platforms too.
7283 - Make zlib.h a required header, not an optional header.
7286 Changes in version 0.0.9pre1 - 2004-10-01
7288 - Stop using separate defaults for no-config-file and
7289 empty-config-file. Now you have to explicitly turn off SocksPort,
7290 if you don't want it open.
7291 - Fix a bug in OutboundBindAddress so it (hopefully) works.
7292 - Improve man page to mention more of the 0.0.8 features.
7293 - Fix a rare seg fault for people running hidden services on
7294 intermittent connections.
7295 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
7297 - Fix more dns related bugs: send back resolve_failed and end cells
7298 more reliably when the resolve fails, rather than closing the
7299 circuit and then trying to send the cell. Also attach dummy resolve
7300 connections to a circuit *before* calling dns_resolve(), to fix
7301 a bug where cached answers would never be sent in RESOLVED cells.
7302 - When we run out of disk space, or other log writing error, don't
7303 crash. Just stop logging to that log and continue.
7304 - We were starting to daemonize before we opened our logs, so if
7305 there were any problems opening logs, we would complain to stderr,
7306 which wouldn't work, and then mysteriously exit.
7307 - Fix a rare bug where sometimes a verified OR would connect to us
7308 before he'd uploaded his descriptor, which would cause us to
7309 assign conn->nickname as though he's unverified. Now we look through
7310 the fingerprint list to see if he's there.
7311 - Fix a rare assert trigger, where routerinfos for entries in
7312 our cpath would expire while we're building the path.
7315 - Clients can ask dirservers for /dir.z to get a compressed version
7316 of the directory. Only works for servers running 0.0.9, of course.
7317 - Make clients cache directories and use them to seed their router
7318 lists at startup. This means clients have a datadir again.
7319 - Configuration infrastructure support for warning on obsolete
7321 - Respond to content-encoding headers by trying to uncompress as
7323 - Reply with a deflated directory when a client asks for "dir.z".
7324 We could use allow-encodings instead, but allow-encodings isn't
7325 specified in HTTP 1.0.
7326 - Raise the max dns workers from 50 to 100.
7327 - Discourage people from setting their dirfetchpostperiod more often
7328 than once per minute.
7329 - Protect dirservers from overzealous descriptor uploading -- wait
7330 10 seconds after directory gets dirty, before regenerating.
7333 Changes in version 0.0.8 - 2004-08-25
7334 o Port it to SunOS 5.9 / Athena
7337 Changes in version 0.0.8rc2 - 2004-08-20
7338 o Make it compile on cygwin again.
7339 o When picking unverified routers, skip those with low uptime and/or
7340 low bandwidth, depending on what properties you care about.
7343 Changes in version 0.0.8rc1 - 2004-08-18
7344 o Changes from 0.0.7.3:
7346 - Fix assert triggers: if the other side returns an address 0.0.0.0,
7347 don't put it into the client dns cache.
7348 - If a begin failed due to exit policy, but we believe the IP address
7349 should have been allowed, switch that router to exitpolicy reject *:*
7350 until we get our next directory.
7352 - Clients choose nodes proportional to advertised bandwidth.
7353 - Avoid using nodes with low uptime as introduction points.
7354 - Handle servers with dynamic IP addresses: don't replace
7355 options->Address with the resolved one at startup, and
7356 detect our address right before we make a routerinfo each time.
7357 - 'FascistFirewall' option to pick dirservers and ORs on specific
7358 ports; plus 'FirewallPorts' config option to tell FascistFirewall
7359 which ports are open. (Defaults to 80,443)
7360 - Be more aggressive about trying to make circuits when the network
7361 has changed (e.g. when you unsuspend your laptop).
7362 - Check for time skew on http headers; report date in response to
7364 - If the entrynode config line has only one node, don't pick it as
7366 - Add strict{entry|exit}nodes config options. If set to 1, then
7367 we refuse to build circuits that don't include the specified entry
7369 - OutboundBindAddress config option, to bind to a specific
7370 IP address for outgoing connect()s.
7371 - End truncated log entries (e.g. directories) with "[truncated]".
7373 o Patches to 0.0.8preX:
7375 - Patches to compile and run on win32 again (maybe)?
7376 - Fix crash when looking for ~/.torrc with no $HOME set.
7377 - Fix a race bug in the unit tests.
7378 - Handle verified/unverified name collisions better when new
7379 routerinfo's arrive in a directory.
7380 - Sometimes routers were getting entered into the stats before
7381 we'd assigned their identity_digest. Oops.
7382 - Only pick and establish intro points after we've gotten a
7385 - AllowUnverifiedNodes config option to let circuits choose no-name
7386 routers in entry,middle,exit,introduction,rendezvous positions.
7387 Allow middle and rendezvous positions by default.
7388 - Add a man page for tor-resolve.
7391 Changes in version 0.0.7.3 - 2004-08-12
7392 o Stop dnsworkers from triggering an assert failure when you
7393 ask them to resolve the host "".
7396 Changes in version 0.0.8pre3 - 2004-08-09
7397 o Changes from 0.0.7.2:
7398 - Allow multiple ORs with same nickname in routerlist -- now when
7399 people give us one identity key for a nickname, then later
7400 another, we don't constantly complain until the first expires.
7401 - Remember used bandwidth (both in and out), and publish 15-minute
7402 snapshots for the past day into our descriptor.
7403 - You can now fetch $DIRURL/running-routers to get just the
7404 running-routers line, not the whole descriptor list. (But
7405 clients don't use this yet.)
7406 - When people mistakenly use Tor as an http proxy, point them
7407 at the tor-doc.html rather than the INSTALL.
7408 - Remove our mostly unused -- and broken -- hex_encode()
7409 function. Use base16_encode() instead. (Thanks to Timo Lindfors
7410 for pointing out this bug.)
7411 - Rotate onion keys every 12 hours, not every 2 hours, so we have
7412 fewer problems with people using the wrong key.
7413 - Change the default exit policy to reject the default edonkey,
7414 kazaa, gnutella ports.
7415 - Add replace_file() to util.[ch] to handle win32's rename().
7417 o Changes from 0.0.8preX:
7418 - Fix two bugs in saving onion keys to disk when rotating, so
7419 hopefully we'll get fewer people using old onion keys.
7420 - Fix an assert error that was making SocksPolicy not work.
7421 - Be willing to expire routers that have an open dirport -- it's
7422 just the authoritative dirservers we want to not forget.
7423 - Reject tor-resolve requests for .onion addresses early, so we
7424 don't build a whole rendezvous circuit and then fail.
7425 - When you're warning a server that he's unverified, don't cry
7427 - Fix a race condition: don't try to extend onto a connection
7428 that's still handshaking.
7429 - For servers in clique mode, require the conn to be open before
7430 you'll choose it for your path.
7431 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
7432 end relay cell, etc.
7433 - Measure bandwidth capacity over the last 24 hours, not just 12
7434 - Bugfix: authoritative dirservers were making and signing a new
7435 directory for each client, rather than reusing the cached one.
7438 Changes in version 0.0.8pre2 - 2004-08-04
7439 o Changes from 0.0.7.2:
7441 - Check directory signature _before_ you decide whether you're
7442 you're running an obsolete version and should exit.
7443 - Check directory signature _before_ you parse the running-routers
7444 list to decide who's running or verified.
7445 - Bugfixes and features:
7446 - Check return value of fclose while writing to disk, so we don't
7447 end up with broken files when servers run out of disk space.
7448 - Log a warning if the user uses an unsafe socks variant, so people
7449 are more likely to learn about privoxy or socat.
7450 - Dirservers now include RFC1123-style dates in the HTTP headers,
7451 which one day we will use to better detect clock skew.
7453 o Changes from 0.0.8pre1:
7454 - Make it compile without warnings again on win32.
7455 - Log a warning if you're running an unverified server, to let you
7456 know you might want to get it verified.
7457 - Only pick a default nickname if you plan to be a server.
7460 Changes in version 0.0.8pre1 - 2004-07-23
7462 - Made our unit tests compile again on OpenBSD 3.5, and tor
7463 itself compile again on OpenBSD on a sparc64.
7464 - We were neglecting milliseconds when logging on win32, so
7465 everything appeared to happen at the beginning of each second.
7468 - 'Extend' relay cell payloads now include the digest of the
7469 intended next hop's identity key. Now we can verify that we're
7470 extending to the right router, and also extend to routers we
7471 hadn't heard of before.
7474 - Tor nodes can now act as relays (with an advertised ORPort)
7475 without being manually verified by the dirserver operators.
7476 - Uploaded descriptors of unverified routers are now accepted
7477 by the dirservers, and included in the directory.
7478 - Verified routers are listed by nickname in the running-routers
7479 list; unverified routers are listed as "$<fingerprint>".
7480 - We now use hash-of-identity-key in most places rather than
7481 nickname or addr:port, for improved security/flexibility.
7482 - To avoid Sybil attacks, paths still use only verified servers.
7483 But now we have a chance to play around with hybrid approaches.
7484 - Nodes track bandwidth usage to estimate capacity (not used yet).
7485 - ClientOnly option for nodes that never want to become servers.
7486 - Directory caching.
7487 - "AuthoritativeDir 1" option for the official dirservers.
7488 - Now other nodes (clients and servers) will cache the latest
7489 directory they've pulled down.
7490 - They can enable their DirPort to serve it to others.
7491 - Clients will pull down a directory from any node with an open
7492 DirPort, and check the signature/timestamp correctly.
7493 - Authoritative dirservers now fetch directories from other
7494 authdirservers, to stay better synced.
7495 - Running-routers list tells who's down also, along with noting
7496 if they're verified (listed by nickname) or unverified (listed
7498 - Allow dirservers to serve running-router list separately.
7499 This isn't used yet.
7500 - ORs connect-on-demand to other ORs
7501 - If you get an extend cell to an OR you're not connected to,
7502 connect, handshake, and forward the create cell.
7503 - The authoritative dirservers stay connected to everybody,
7504 and everybody stays connected to 0.0.7 servers, but otherwise
7505 clients/servers expire unused connections after 5 minutes.
7506 - When servers get a sigint, they delay 30 seconds (refusing new
7507 connections) then exit. A second sigint causes immediate exit.
7508 - File and name management:
7509 - Look for .torrc if no CONFDIR "torrc" is found.
7510 - If no datadir is defined, then choose, make, and secure ~/.tor
7512 - If torrc not found, exitpolicy reject *:*.
7513 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
7514 - If no nickname is defined, derive default from hostname.
7515 - Rename secret key files, e.g. identity.key -> secret_id_key,
7516 to discourage people from mailing their identity key to tor-ops.
7517 - Refuse to build a circuit before the directory has arrived --
7518 it won't work anyway, since you won't know the right onion keys
7520 - Try other dirservers immediately if the one you try is down. This
7521 should tolerate down dirservers better now.
7522 - Parse tor version numbers so we can do an is-newer-than check
7523 rather than an is-in-the-list check.
7524 - New socks command 'resolve', to let us shim gethostbyname()
7526 - A 'tor_resolve' script to access the socks resolve functionality.
7527 - A new socks-extensions.txt doc file to describe our
7528 interpretation and extensions to the socks protocols.
7529 - Add a ContactInfo option, which gets published in descriptor.
7530 - Publish OR uptime in descriptor (and thus in directory) too.
7531 - Write tor version at the top of each log file
7532 - New docs in the tarball:
7534 - Document that you should proxy your SSL traffic too.
7537 Changes in version 0.0.7.2 - 2004-07-07
7538 o A better fix for the 0.0.0.0 problem, that will hopefully
7539 eliminate the remaining related assertion failures.
7542 Changes in version 0.0.7.1 - 2004-07-04
7543 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
7544 since internally we use 0.0.0.0 to signify "not yet resolved".
7547 Changes in version 0.0.7 - 2004-06-07
7548 o Updated the man page to reflect the new features.
7551 Changes in version 0.0.7rc2 - 2004-06-06
7552 o Changes from 0.0.7rc1:
7553 - Make it build on Win32 again.
7554 o Changes from 0.0.6.2:
7555 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
7559 Changes in version 0.0.7rc1 - 2004-06-02
7561 - On sighup, we were adding another log without removing the first
7562 one. So log messages would get duplicated n times for n sighups.
7563 - Several cases of using a connection after we'd freed it. The
7564 problem was that connections that are pending resolve are in both
7565 the pending_resolve tree, and also the circuit's resolving_streams
7566 list. When you want to remove one, you must remove it from both.
7567 - Fix a double-mark-for-close where an end cell arrived for a
7568 resolving stream, and then the resolve failed.
7569 - Check directory signatures based on name of signer, not on whom
7570 we got the directory from. This will let us cache directories more
7573 - Crank up some of our constants to handle more users.
7576 Changes in version 0.0.7pre1 - 2004-06-02
7577 o Fixes for crashes and other obnoxious bugs:
7578 - Fix an epipe bug: sometimes when directory connections failed
7579 to connect, we would give them a chance to flush before closing
7581 - When we detached from a circuit because of resolvefailed, we
7582 would immediately try the same circuit twice more, and then
7583 give up on the resolve thinking we'd tried three different
7585 - Limit the number of intro circuits we'll attempt to build for a
7586 hidden service per 15-minute period.
7587 - Check recommended-software string *early*, before actually parsing
7588 the directory. Thus we can detect an obsolete version and exit,
7589 even if the new directory format doesn't parse.
7590 o Fixes for security bugs:
7591 - Remember which nodes are dirservers when you startup, and if a
7592 random OR enables his dirport, don't automatically assume he's
7593 a trusted dirserver.
7595 - Directory connections were asking the wrong poll socket to
7596 start writing, and not asking themselves to start writing.
7597 - When we detached from a circuit because we sent a begin but
7598 didn't get a connected, we would use it again the first time;
7599 but after that we would correctly switch to a different one.
7600 - Stop warning when the first onion decrypt attempt fails; they
7601 will sometimes legitimately fail now that we rotate keys.
7602 - Override unaligned-access-ok check when $host_cpu is ia64 or
7603 arm. Apparently they allow it but the kernel whines.
7604 - Dirservers try to reconnect periodically too, in case connections
7606 - Fix some memory leaks in directory servers.
7607 - Allow backslash in Win32 filenames.
7608 - Made Tor build complain-free on FreeBSD, hopefully without
7609 breaking other BSD builds. We'll see.
7611 - Doxygen markup on all functions and global variables.
7612 - Make directory functions update routerlist, not replace it. So
7613 now directory disagreements are not so critical a problem.
7614 - Remove the upper limit on number of descriptors in a dirserver's
7615 directory (not that we were anywhere close).
7616 - Allow multiple logfiles at different severity ranges.
7617 - Allow *BindAddress to specify ":port" rather than setting *Port
7618 separately. Allow multiple instances of each BindAddress config
7619 option, so you can bind to multiple interfaces if you want.
7620 - Allow multiple exit policy lines, which are processed in order.
7621 Now we don't need that huge line with all the commas in it.
7622 - Enable accept/reject policies on SOCKS connections, so you can bind
7623 to 0.0.0.0 but still control who can use your OP.
7626 Changes in version 0.0.6.2 - 2004-05-16
7627 o Our integrity-checking digest was checking only the most recent cell,
7628 not the previous cells like we'd thought.
7629 Thanks to Stefan Mark for finding the flaw!
7632 Changes in version 0.0.6.1 - 2004-05-06
7633 o Fix two bugs in our AES counter-mode implementation (this affected
7634 onion-level stream encryption, but not TLS-level). It turns
7635 out we were doing something much more akin to a 16-character
7636 polyalphabetic cipher. Oops.
7637 Thanks to Stefan Mark for finding the flaw!
7638 o Retire moria3 as a directory server, and add tor26 as a directory
7642 Changes in version 0.0.6 - 2004-05-02
7646 Changes in version 0.0.6rc4 - 2004-05-01
7647 o Update the built-in dirservers list to use the new directory format
7648 o Fix a rare seg fault: if a node offering a hidden service attempts
7649 to build a circuit to Alice's rendezvous point and fails before it
7650 reaches the last hop, it retries with a different circuit, but
7652 o Handle windows socket errors correctly.
7655 Changes in version 0.0.6rc3 - 2004-04-28
7656 o Don't expire non-general excess circuits (if we had enough
7657 circuits open, we were expiring rendezvous circuits -- even
7658 when they had a stream attached. oops.)
7659 o Fetch randomness from /dev/urandom better (not via fopen/fread)
7660 o Better debugging for tls errors
7661 o Some versions of openssl have an SSL_pending function that erroneously
7662 returns bytes when there is a non-application record pending.
7663 o Set Content-Type on the directory and hidserv descriptor.
7664 o Remove IVs from cipher code, since AES-ctr has none.
7665 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
7666 o We were using an array of length zero in a few places.
7667 o win32's gethostbyname can't resolve an IP to an IP.
7668 o win32's close can't close a socket.
7671 Changes in version 0.0.6rc2 - 2004-04-26
7672 o Fix a bug where we were closing tls connections intermittently.
7673 It turns out openssl keeps its errors around -- so if an error
7674 happens, and you don't ask about it, and then another openssl
7675 operation happens and succeeds, and you ask if there was an error,
7676 it tells you about the first error. Fun fun.
7677 o Fix a bug that's been lurking since 27 may 03 (!)
7678 When passing back a destroy cell, we would use the wrong circ id.
7679 'Mostly harmless', but still worth fixing.
7680 o Since we don't support truncateds much, don't bother sending them;
7681 just close the circ.
7682 o check for <machine/limits.h> so we build on NetBSD again (I hope).
7683 o don't crash if a conn that sent a begin has suddenly lost its circuit
7684 (this was quite rare).
7687 Changes in version 0.0.6rc1 - 2004-04-25
7688 o We now rotate link (tls context) keys and onion keys.
7689 o CREATE cells now include oaep padding, so you can tell
7690 if you decrypted them correctly.
7691 o Add bandwidthburst to server descriptor.
7692 o Directories now say which dirserver signed them.
7693 o Use a tor_assert macro that logs failed assertions too.
7696 Changes in version 0.0.6pre5 - 2004-04-18
7697 o changes from 0.0.6pre4:
7698 - make tor build on broken freebsd 5.2 installs
7699 - fix a failed assert when you try an intro point, get a nack, and try
7700 a second one and it works.
7701 - when alice uses a port that the hidden service doesn't accept,
7702 it now sends back an end cell (denied by exit policy). otherwise
7703 alice would just have to wait to time out.
7704 - fix another rare bug: when we had tried all the intro
7705 points for a hidden service, we fetched the descriptor
7706 again, but we left our introcirc thinking it had already
7707 sent an intro, so it kept waiting for a response...
7708 - bugfix: when you sleep your hidden-service laptop, as soon
7709 as it wakes up it tries to upload a service descriptor, but
7710 socketpair fails for some reason (localhost not up yet?).
7711 now we simply give up on that upload, and we'll try again later.
7712 i'd still like to find the bug though.
7713 - if an intro circ waiting for an ack dies before getting one, then
7715 - we were reusing stale service descriptors and refetching usable
7719 Changes in version 0.0.6pre4 - 2004-04-14
7720 o changes from 0.0.6pre3:
7721 - when bob fails to connect to the rendezvous point, and his
7722 circ didn't fail because of the rendezvous point itself, then
7723 he retries a couple of times
7724 - we expire introduction and rendezvous circs more thoroughly
7725 (sometimes they were hanging around forever)
7726 - we expire unattached rendezvous streams that have been around
7727 too long (they were sticking around forever).
7728 - fix a measly fencepost error that was crashing everybody with
7732 Changes in version 0.0.6pre3 - 2004-04-14
7733 o changes from 0.0.6pre2:
7734 - make hup work again
7735 - fix some memory leaks for dirservers
7736 - allow more skew in rendezvous descriptor timestamps, to help
7737 handle people like blanu who don't know what time it is
7738 - normal circs are 3 hops, but some rend/intro circs are 4, if
7739 the initiator doesn't get to choose the last hop
7740 - send acks for introductions, so alice can know whether to try
7742 - bob publishes intro points more correctly
7743 o changes from 0.0.5:
7744 - fix an assert trigger that's been plaguing us since the days
7745 of 0.0.2prexx (thanks weasel!)
7746 - retry stream correctly when we fail to connect because of
7747 exit-policy-reject (should try another) or can't-resolve-address
7748 (also should try another, because dns on random internet servers
7750 - when we hup a dirserver and we've *removed* a server from the
7751 approved-routers list, now we remove that server from the
7752 in-memory directories too
7755 Changes in version 0.0.6pre2 - 2004-04-08
7756 o We fixed our base32 implementation. Now it works on all architectures.
7759 Changes in version 0.0.6pre1 - 2004-04-08
7761 - Hidden services and rendezvous points are implemented. Go to
7762 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
7763 hidden services. (This only works via a socks4a proxy such as
7764 Privoxy, and currently it's quite slow.)
7767 Changes in version 0.0.5 - 2004-03-30
7771 Changes in version 0.0.5rc3 - 2004-03-29
7772 o Install torrc as torrc.sample -- we no longer clobber your
7774 o Re-enable recommendedversion checking (we broke it in rc2, oops)
7775 o Add in a 'notice' log level for things the operator should hear
7776 but that aren't warnings
7779 Changes in version 0.0.5rc2 - 2004-03-29
7780 o Hold socks connection open until reply is flushed (if possible)
7781 o Make exit nodes resolve IPs to IPs immediately, rather than asking
7782 the dns farm to do it.
7783 o Fix c99 aliasing warnings in rephist.c
7784 o Don't include server descriptors that are older than 24 hours in the
7786 o Give socks 'reject' replies their whole 15s to attempt to flush,
7787 rather than seeing the 60s timeout and assuming the flush had failed.
7788 o Clean automake droppings from the cvs repository
7791 Changes in version 0.0.5rc1 - 2004-03-28
7792 o Fix mangled-state bug in directory fetching (was causing sigpipes).
7793 o Only build circuits after we've fetched the directory: clients were
7794 using only the directory servers before they'd fetched a directory.
7795 This also means longer startup time; so it goes.
7796 o Fix an assert trigger where an OP would fail to handshake, and we'd
7797 expect it to have a nickname.
7798 o Work around a tsocks bug: do a socks reject when AP connection dies
7799 early, else tsocks goes into an infinite loop.
7802 Changes in version 0.0.4 - 2004-03-26
7803 o When connecting to a dirserver or OR and the network is down,
7807 Changes in version 0.0.3 - 2004-03-26
7808 o Warn and fail if server chose a nickname with illegal characters
7809 o Port to Solaris and Sparc:
7810 - include missing header fcntl.h
7811 - have autoconf find -lsocket -lnsl automatically
7812 - deal with hardware word alignment
7813 - make uname() work (solaris has a different return convention)
7814 - switch from using signal() to sigaction()
7815 o Preliminary work on reputation system:
7816 - Keep statistics on success/fail of connect attempts; they're published
7817 by kill -USR1 currently.
7818 - Add a RunTesting option to try to learn link state by creating test
7819 circuits, even when SocksPort is off.
7820 - Remove unused open circuits when there are too many.
7823 Changes in version 0.0.2 - 2004-03-19
7824 - Include strlcpy and strlcat for safer string ops
7825 - define INADDR_NONE so we compile (but still not run) on solaris
7828 Changes in version 0.0.2pre27 - 2004-03-14
7830 - Allow internal tor networks (we were rejecting internal IPs,
7831 now we allow them if they're set explicitly).
7832 - And fix a few endian issues.
7835 Changes in version 0.0.2pre26 - 2004-03-14
7837 - If a stream times out after 15s without a connected cell, don't
7838 try that circuit again: try a new one.
7839 - Retry streams at most 4 times. Then give up.
7840 - When a dirserver gets a descriptor from an unknown router, it
7841 logs its fingerprint (so the dirserver operator can choose to
7842 accept it even without mail from the server operator).
7843 - Inform unapproved servers when we reject their descriptors.
7844 - Make tor build on Windows again. It works as a client, who knows
7846 - Clearer instructions in the torrc for how to set up a server.
7847 - Be more efficient about reading fd's when our global token bucket
7848 (used for rate limiting) becomes empty.
7850 - Stop asserting that computers always go forward in time. It's
7852 - When we sent a cell (e.g. destroy) and then marked an OR connection
7853 expired, we might close it before finishing a flush if the other
7854 side isn't reading right then.
7855 - Don't allow dirservers to start if they haven't defined
7857 - We were caching transient dns failures. Oops.
7858 - Prevent servers from publishing an internal IP as their address.
7859 - Address a strcat vulnerability in circuit.c
7862 Changes in version 0.0.2pre25 - 2004-03-04
7864 - Put the OR's IP in its router descriptor, not its fqdn. That way
7865 we'll stop being stalled by gethostbyname for nodes with flaky dns,
7868 - If the user typed in an address that didn't resolve, the server
7872 Changes in version 0.0.2pre24 - 2004-03-03
7874 - Fix an assertion failure in dns.c, where we were trying to dequeue
7875 a pending dns resolve even if it wasn't pending
7876 - Fix a spurious socks5 warning about still trying to write after the
7877 connection is finished.
7878 - Hold certain marked_for_close connections open until they're finished
7879 flushing, rather than losing bytes by closing them too early.
7880 - Correctly report the reason for ending a stream
7881 - Remove some duplicate calls to connection_mark_for_close
7882 - Put switch_id and start_daemon earlier in the boot sequence, so it
7883 will actually try to chdir() to options.DataDirectory
7884 - Make 'make test' exit(1) if a test fails; fix some unit tests
7885 - Make tor fail when you use a config option it doesn't know about,
7886 rather than warn and continue.
7887 - Make --version work
7888 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
7891 Changes in version 0.0.2pre23 - 2004-02-29
7893 - Print a statement when the first circ is finished, so the user
7895 - If a relay cell is unrecognized at the end of the circuit,
7896 send back a destroy. (So attacks to mutate cells are more
7898 - New config option 'excludenodes' to avoid certain nodes for circuits.
7899 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
7900 so you can collect coredumps there.
7902 - Fix a bug in tls flushing where sometimes data got wedged and
7903 didn't flush until more data got sent. Hopefully this bug was
7904 a big factor in the random delays we were seeing.
7905 - Make 'connected' cells include the resolved IP, so the client
7906 dns cache actually gets populated.
7907 - Disallow changing from ORPort=0 to ORPort>0 on hup.
7908 - When we time-out on a stream and detach from the circuit, send an
7909 end cell down it first.
7910 - Only warn about an unknown router (in exitnodes, entrynodes,
7911 excludenodes) after we've fetched a directory.
7914 Changes in version 0.0.2pre22 - 2004-02-26
7916 - Servers publish less revealing uname information in descriptors.
7917 - More memory tracking and assertions, to crash more usefully when
7919 - If the default torrc isn't there, just use some default defaults.
7920 Plus provide an internal dirservers file if they don't have one.
7921 - When the user tries to use Tor as an http proxy, give them an http
7922 501 failure explaining that we're a socks proxy.
7923 - Dump a new router.desc on hup, to help confused people who change
7924 their exit policies and then wonder why router.desc doesn't reflect
7926 - Clean up the generic tor.sh init script that we ship with.
7928 - If the exit stream is pending on the resolve, and a destroy arrives,
7929 then the stream wasn't getting removed from the pending list. I
7930 think this was the one causing recent server crashes.
7931 - Use a more robust poll on OSX 10.3, since their poll is flaky.
7932 - When it couldn't resolve any dirservers, it was useless from then on.
7933 Now it reloads the RouterFile (or default dirservers) if it has no
7935 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
7936 many users don't even *have* a /usr/local/sbin/.
7939 Changes in version 0.0.2pre21 - 2004-02-18
7941 - There's a ChangeLog file that actually reflects the changelog.
7942 - There's a 'torify' wrapper script, with an accompanying
7943 tor-tsocks.conf, that simplifies the process of using tsocks for
7944 tor. It even has a man page.
7945 - The tor binary gets installed to sbin rather than bin now.
7946 - Retry streams where the connected cell hasn't arrived in 15 seconds
7947 - Clean up exit policy handling -- get the default out of the torrc,
7948 so we can update it without forcing each server operator to fix
7950 - Allow imaps and pop3s in default exit policy
7952 - Prevent picking middleman nodes as the last node in the circuit
7955 Changes in version 0.0.2pre20 - 2004-01-30
7957 - We now have a deb package, and it's in debian unstable. Go to
7959 - I've split the TotalBandwidth option into BandwidthRate (how many
7960 bytes per second you want to allow, long-term) and
7961 BandwidthBurst (how many bytes you will allow at once before the cap
7962 kicks in). This better token bucket approach lets you, say, set
7963 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
7964 performance while not exceeding your monthly bandwidth quota.
7965 - Push out a tls record's worth of data once you've got it, rather
7966 than waiting until you've read everything waiting to be read. This
7967 may improve performance by pipelining better. We'll see.
7968 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
7969 from failed circuits (if they haven't been connected yet) and attach
7971 - Expire old streams that haven't managed to connect. Some day we'll
7972 have them reattach to new circuits instead.
7975 - Fix several memory leaks that were causing servers to become bloated
7977 - Fix a few very rare assert triggers. A few more remain.
7978 - Setuid to User _before_ complaining about running as root.
7981 Changes in version 0.0.2pre19 - 2004-01-07
7983 - Fix deadlock condition in dns farm. We were telling a child to die by
7984 closing the parent's file descriptor to him. But newer children were
7985 inheriting the open file descriptor from the parent, and since they
7986 weren't closing it, the socket never closed, so the child never read
7987 eof, so he never knew to exit. Similarly, dns workers were holding
7988 open other sockets, leading to all sorts of chaos.
7989 - New cleaner daemon() code for forking and backgrounding.
7990 - If you log to a file, it now prints an entry at the top of the
7991 logfile so you know it's working.
7992 - The onionskin challenge length was 30 bytes longer than necessary.
7993 - Started to patch up the spec so it's not quite so out of date.
7996 Changes in version 0.0.2pre18 - 2004-01-02
7998 - Fix endian issues with the 'integrity' field in the relay header.
7999 - Fix a potential bug where connections in state
8000 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
8003 Changes in version 0.0.2pre17 - 2003-12-30
8005 - Made --debuglogfile (or any second log file, actually) work.
8006 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
8007 adversary could force us into an infinite loop.
8010 - Each onionskin handshake now includes a hash of the computed key,
8011 to prove the server's identity and help perfect forward secrecy.
8012 - Changed cell size from 256 to 512 bytes (working toward compatibility
8014 - Changed cell length to 2 bytes, and moved it to the relay header.
8015 - Implemented end-to-end integrity checking for the payloads of
8017 - Separated streamid from 'recognized' (otherwise circuits will get
8018 messed up when we try to have streams exit from the middle). We
8019 use the integrity-checking to confirm that a cell is addressed to
8021 - Randomize the initial circid and streamid values, so an adversary who
8022 breaks into a node can't learn how many circuits or streams have
8026 Changes in version 0.0.2pre16 - 2003-12-14
8028 - Fixed a bug that made HUP trigger an assert
8029 - Fixed a bug where a circuit that immediately failed wasn't being
8030 counted as a failed circuit in counting retries.
8033 - Now we close the circuit when we get a truncated cell: otherwise we're
8034 open to an anonymity attack where a bad node in the path truncates
8035 the circuit and then we open streams at him.
8036 - Add port ranges to exit policies
8037 - Add a conservative default exit policy
8038 - Warn if you're running tor as root
8039 - on HUP, retry OR connections and close/rebind listeners
8040 - options.EntryNodes: try these nodes first when picking the first node
8041 - options.ExitNodes: if your best choices happen to include any of
8042 your preferred exit nodes, you choose among just those preferred
8044 - options.ExcludedNodes: nodes that are never picked in path building
8047 Changes in version 0.0.2pre15 - 2003-12-03
8048 o Robustness and bugfixes:
8049 - Sometimes clients would cache incorrect DNS resolves, which would
8050 really screw things up.
8051 - An OP that goes offline would slowly leak all its sockets and stop
8053 - A wide variety of bugfixes in exit node selection, exit policy
8054 handling, and processing pending streams when a new circuit is
8056 - Pick nodes for a path only from those the directory says are up
8057 - Choose randomly from all running dirservers, not always the first one
8058 - Increase allowed http header size for directory fetch.
8059 - Stop writing to stderr (if we're daemonized it will be closed).
8060 - Enable -g always, so cores will be more useful to me.
8061 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
8064 - Wrote a man page. It lists commonly used options.
8067 - Change default loglevel to warn.
8068 - Make PidFile default to null rather than littering in your CWD.
8069 - OnionRouter config option is now obsolete. Instead it just checks
8071 - Moved to a single unified torrc file for both clients and servers.
8074 Changes in version 0.0.2pre14 - 2003-11-29
8075 o Robustness and bugfixes:
8076 - Force the admin to make the DataDirectory himself
8077 - to get ownership/permissions right
8078 - so clients no longer make a DataDirectory and then never use it
8079 - fix bug where a client who was offline for 45 minutes would never
8080 pull down a directory again
8081 - fix (or at least hide really well) the dns assert bug that was
8082 causing server crashes
8083 - warnings and improved robustness wrt clockskew for certs
8084 - use the native daemon(3) to daemonize, when available
8085 - exit if bind() fails
8086 - exit if neither socksport nor orport is defined
8087 - include our own tor_timegm (Win32 doesn't have its own)
8088 - bugfix for win32 with lots of connections
8089 - fix minor bias in PRNG
8090 - make dirserver more robust to corrupt cached directory
8093 - Wrote the design document (woo)
8095 o Circuit building and exit policies:
8096 - Circuits no longer try to use nodes that the directory has told them
8098 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
8099 bitcounts (18.0.0.0/8).
8100 - Make AP connections standby for a circuit if no suitable circuit
8101 exists, rather than failing
8102 - Circuits choose exit node based on addr/port, exit policies, and
8103 which AP connections are standing by
8104 - Bump min pathlen from 2 to 3
8105 - Relay end cells have a payload to describe why the stream ended.
8106 - If the stream failed because of exit policy, try again with a new
8108 - Clients have a dns cache to remember resolved addresses.
8109 - Notice more quickly when we have no working circuits
8112 - APPort is now called SocksPort
8113 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
8115 - RecommendedVersions is now a config variable rather than
8116 hardcoded (for dirservers)
8117 - Reloads config on HUP
8118 - Usage info on -h or --help
8119 - If you set User and Group config vars, it'll setu/gid to them.
8122 Changes in version 0.0.2pre13 - 2003-10-19
8123 o General stability:
8124 - SSL_write no longer fails when it returns WANTWRITE and the number
8125 of bytes in the buf has changed by the next SSL_write call.
8126 - Fix segfault fetching directory when network is down
8127 - Fix a variety of minor memory leaks
8128 - Dirservers reload the fingerprints file on HUP, so I don't have
8129 to take down the network when I approve a new router
8130 - Default server config file has explicit Address line to specify fqdn
8133 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
8134 - Make listener connections not ever alloc bufs
8136 o Autoconf improvements:
8137 - don't clobber an external CFLAGS in ./configure
8138 - Make install now works
8139 - create var/lib/tor on make install
8140 - autocreate a tor.sh initscript to help distribs
8141 - autocreate the torrc and sample-server-torrc with correct paths
8143 o Log files and Daemonizing now work:
8144 - If --DebugLogFile is specified, log to it at -l debug
8145 - If --LogFile is specified, use it instead of commandline
8146 - If --RunAsDaemon is set, tor forks and backgrounds on startup