1 Changes in version 0.2.2.6-alpha - 2009-10-??
2 o Code simplifications and refactorings:
3 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
4 to help Tor build correctly for Android phones.
7 Changes in version 0.2.2.5-alpha - 2009-10-11
9 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
11 o New directory authorities:
12 - Move dizum to an alternate IP address.
15 Changes in version 0.2.2.4-alpha - 2009-10-10
17 - Fix several more asserts in the circuit_build_times code, for
18 example one that causes Tor to fail to start once we have
19 accumulated 5000 build times in the state file. Bugfixes on
20 0.2.2.2-alpha; fixes bug 1108.
22 o New directory authorities:
23 - Move moria1 and Tonga to alternate IP addresses.
26 - Log SSL state transitions at debug level during handshake, and
27 include SSL states in error messages. This may help debug future
29 - Add a new "Handshake" log domain for activities that happen
30 during the TLS handshake.
31 - Revert to the "June 3 2009" ip-to-country file. The September one
32 seems to have removed most US IP addresses.
33 - Directory authorities now reject Tor relays with versions less than
34 0.1.2.14. This step cuts out four relays from the current network,
35 none of which are very big.
38 - Fix a couple of smaller issues with gathering statistics. Bugfixes
40 - Fix two memory leaks in the error case of
41 circuit_build_times_parse_state. Bugfix on 0.2.2.2-alpha.
42 - Don't count one-hop circuits when we're estimating how long it
43 takes circuits to build on average. Otherwise we'll set our circuit
44 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
45 - Directory authorities no longer change their opinion of, or vote on,
46 whether a router is Running, unless they have themselves been
47 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
50 o Code simplifications and refactoring:
51 - Revise our unit tests to use the "tinytest" framework, so we
52 can run tests in their own processes, have smarter setup/teardown
53 code, and so on. The unit test code has moved to its own
54 subdirectory, and has been split into multiple modules.
57 Changes in version 0.2.2.3-alpha - 2009-09-23
58 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
61 - Fix an overzealous assert in our new circuit build timeout code.
62 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
65 - If the networkstatus consensus tells us that we should use a
66 negative circuit package window, ignore it. Otherwise we'll
67 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
70 Changes in version 0.2.2.2-alpha - 2009-09-21
71 Tor 0.2.2.2-alpha introduces our latest performance improvement for
72 clients: Tor tracks the average time it takes to build a circuit, and
73 avoids using circuits that take too long to build. For fast connections,
74 this feature can cut your expected latency in half. For slow or flaky
75 connections, it could ruin your Tor experience. Let us know if it does!
78 - Tor now tracks how long it takes to build client-side circuits
79 over time, and adapts its timeout to local network performance.
80 Since a circuit that takes a long time to build will also provide
81 bad performance, we get significant latency improvements by
82 discarding the slowest 20% of circuits. Specifically, Tor creates
83 circuits more aggressively than usual until it has enough data
84 points for a good timeout estimate. Implements proposal 151.
85 We are especially looking for reports (good and bad) from users with
86 both EDGE and broadband connections that can move from broadband
87 to EDGE and find out if the build-time data in the .tor/state gets
88 reset without loss of Tor usability. You should also see a notice
89 log message telling you that Tor has reset its timeout.
90 - Directory authorities can now vote on arbitary integer values as
91 part of the consensus process. This is designed to help set
92 network-wide parameters. Implements proposal 167.
93 - Tor now reads the "circwindow" parameter out of the consensus,
94 and uses that value for its circuit package window rather than the
95 default of 1000 cells. Begins the implementation of proposal 168.
98 - Fix a remotely triggerable memory leak when a consensus document
99 contains more than one signature from the same voter. Bugfix on
103 - Fix an extremely rare infinite recursion bug that could occur if
104 we tried to log a message after shutting down the log subsystem.
105 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
106 - Fix parsing for memory or time units given without a space between
107 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
108 - A networkstatus vote must contain exactly one signature. Spec
109 conformance issue. Bugfix on 0.2.0.3-alpha.
110 - Fix an obscure bug where hidden services on 64-bit big-endian
111 systems might mis-read the timestamp in v3 introduce cells, and
112 refuse to connect back to the client. Discovered by "rotor".
113 Bugfix on 0.2.1.6-alpha.
114 - We were triggering a CLOCK_SKEW controller status event whenever
115 we connect via the v2 connection protocol to any relay that has
116 a wrong clock. Instead, we should only inform the controller when
117 it's a trusted authority that claims our clock is wrong. Bugfix
118 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
119 - We were telling the controller about CHECKING_REACHABILITY and
120 REACHABILITY_FAILED status events whenever we launch a testing
121 circuit or notice that one has failed. Instead, only tell the
122 controller when we want to inform the user of overall success or
123 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
125 - Don't warn when we're using a circuit that ends with a node
126 excluded in ExcludeExitNodes, but the circuit is not used to access
127 the outside world. This should help fix bug 1090, but more problems
128 remain. Bugfix on 0.2.1.6-alpha.
129 - Work around a small memory leak in some versions of OpenSSL that
130 stopped the memory used by the hostname TLS extension from being
132 - Make our 'torify' script more portable; if we have only one of
133 'torsocks' or 'tsocks' installed, don't complain to the user;
134 and explain our warning about tsocks better.
137 - Add a "getinfo status/accepted-server-descriptor" controller
138 command, which is the recommended way for controllers to learn
139 whether our server descriptor has been successfully received by at
140 least on directory authority. Un-recommend good-server-descriptor
141 getinfo and status events until we have a better design for them.
142 - Update to the "September 4 2009" ip-to-country file.
145 Changes in version 0.2.2.1-alpha - 2009-08-26
146 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
147 Tor clients to bootstrap on networks where only port 80 is reachable,
148 makes it more straightforward to support hardware crypto accelerators,
149 and starts the groundwork for gathering stats safely at relays.
152 - Start the process of disabling ".exit" address notation, since it
153 can be used for a variety of esoteric application-level attacks
154 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
157 o New directory authorities:
158 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
162 - New AccelName and AccelDir options add support for dynamic OpenSSL
163 hardware crypto acceleration engines.
164 - Tor now supports tunneling all of its outgoing connections over
165 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
166 configuration options. Code by Christopher Davis.
169 - Send circuit or stream sendme cells when our window has decreased
170 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
171 by Karsten when testing the "reduce circuit window" performance
172 patch. Bugfix on the 54th commit on Tor -- from July 2002,
173 before the release of Tor 0.0.0. This is the new winner of the
176 o New options for gathering stats safely:
177 - Directories that set "DirReqStatistics 1" write statistics on
178 directory request to disk every 24 hours. As compared to the
179 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
180 1) stats are written to disk exactly every 24 hours; 2) estimated
181 shares of v2 and v3 requests are determined as mean values, not at
182 the end of a measurement period; 3) unresolved requests are listed
183 with country code '??'; 4) directories also measure download times.
184 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
185 number of exit streams and transferred bytes per port to disk every
187 - Relays that set "CellStatistics 1" write statistics on how long
188 cells spend in their circuit queues to disk every 24 hours.
189 - Entry nodes that set "EntryStatistics 1" write statistics on the
190 rough number and origins of connecting clients to disk every 24
192 - Relays that write any of the above statistics to disk and set
193 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
194 their extra-info documents.
197 - New --digests command-line switch to output the digests of the
198 source files Tor was built with.
199 - The "torify" script now uses torsocks where available.
200 - The memarea code now uses a sentinel value at the end of each area
201 to make sure nothing writes beyond the end of an area. This might
202 help debug some conceivable causes of bug 930.
203 - Time and memory units in the configuration file can now be set to
204 fractional units. For example, "2.5 GB" is now a valid value for
206 - Certain Tor clients (such as those behind check.torproject.org) may
207 want to fetch the consensus in an extra early manner. To enable this
208 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
209 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
210 as only certain clients who must have this information sooner should
212 - Instead of adding the svn revision to the Tor version string, report
213 the git commit (when we're building from a git checkout).
216 - If any the v3 certs we download are unparseable, we should actually
217 notice the failure so we don't retry indefinitely. Bugfix on
218 0.2.0.x; reported by "rotator".
219 - If the cached cert file is unparseable, warn but don't exit.
220 - Fix possible segmentation fault on directory authorities. Bugfix on
222 - When Tor fails to parse a descriptor of any kind, dump it to disk.
223 Might help diagnosing bug 1051.
225 o Deprecated and removed features:
226 - The controller no longer accepts the old obsolete "addr-mappings/"
227 or "unregistered-servers-" GETINFO values.
228 - Hidden services no longer publish version 0 descriptors, and clients
229 do not request or use version 0 descriptors. However, the old hidden
230 service authorities still accept and serve version 0 descriptors
231 when contacted by older hidden services/clients.
232 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
233 always on; using them is necessary for correct forward-compatible
235 - Remove support for .noconnect style addresses. Nobody was using
236 them, and they provided another avenue for detecting Tor users
237 via application-level web tricks.
240 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
241 installer bundles. See
242 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
243 for details of what's new in Vidalia 0.2.3.
244 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
245 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
246 configuration file, rather than the old Privoxy.
247 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
248 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
249 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
250 better compatibility with OS X 10.6, aka Snow Leopard.
251 - OS X Vidalia Bundle: The multi-package installer is now replaced
252 by a simple drag and drop to the /Applications folder. This change
253 occurred with the upgrade to Vidalia 0.2.3.
256 Changes in version 0.2.1.20 - 2009-??-??
258 - Send circuit or stream sendme cells when our window has decreased
259 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
260 by Karsten when testing the "reduce circuit window" performance
261 patch. Bugfix on the 54th commit on Tor -- from July 2002,
262 before the release of Tor 0.0.0. This is the new winner of the
264 - Fix a remotely triggerable memory leak when a consensus document
265 contains more than one signature from the same voter. Bugfix on
268 o New directory authorities:
269 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
273 - Fix a signed/unsigned compile warning in 0.2.1.19.
274 - Fix possible segmentation fault on directory authorities. Bugfix on
276 - Fix an extremely rare infinite recursion bug that could occur if
277 we tried to log a message after shutting down the log subsystem.
278 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
279 - Fix an obscure bug where hidden services on 64-bit big-endian
280 systems might mis-read the timestamp in v3 introduce cells, and
281 refuse to connect back to the client. Discovered by "rotor".
282 Bugfix on 0.2.1.6-alpha.
283 - We were triggering a CLOCK_SKEW controller status event whenever
284 we connect via the v2 connection protocol to any relay that has
285 a wrong clock. Instead, we should only inform the controller when
286 it's a trusted authority that claims our clock is wrong. Bugfix
287 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
288 - We were telling the controller about CHECKING_REACHABILITY and
289 REACHABILITY_FAILED status events whenever we launch a testing
290 circuit or notice that one has failed. Instead, only tell the
291 controller when we want to inform the user of overall success or
292 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
294 - Don't warn when we're using a circuit that ends with a node
295 excluded in ExcludeExitNodes, but the circuit is not used to access
296 the outside world. This should help fix bug 1090. Bugfix on
298 - Avoid segfault in rare cases when finishing an introduction circuit
299 as a client and finding out that we don't have an introduction key
300 for it. Fixes bug 1073. Reported by Aaron Swartz.
301 - Work around a small memory leak in some versions of OpenSSL that
302 stopped the memory used by the hostname TLS extension from being
306 - Add a "getinfo status/accepted-server-descriptor" controller
307 command, which is the recommended way for controllers to learn
308 whether our server descriptor has been successfully received by at
309 least on directory authority. Un-recommend good-server-descriptor
310 getinfo and status events until we have a better design for them.
313 Changes in version 0.2.1.19 - 2009-07-28
314 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
315 services on Tor 0.2.1.3-alpha through 0.2.1.18.
318 - Make accessing hidden services on 0.2.1.x work right again.
319 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
320 part of patch provided by "optimist".
323 - When a relay/bridge is writing out its identity key fingerprint to
324 the "fingerprint" file and to its logs, write it without spaces. Now
325 it will look like the fingerprints in our bridges documentation,
326 and confuse fewer users.
329 - Relays no longer publish a new server descriptor if they change
330 their MaxAdvertisedBandwidth config option but it doesn't end up
331 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
332 fixes bug 1026. Patch from Sebastian.
333 - Avoid leaking memory every time we get a create cell but we have
334 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
335 fixes bug 1034. Reported by BarkerJr.
338 Changes in version 0.2.1.18 - 2009-07-24
339 Tor 0.2.1.18 lays the foundations for performance improvements,
340 adds status events to help users diagnose bootstrap problems, adds
341 optional authentication/authorization for hidden services, fixes a
342 variety of potential anonymity problems, and includes a huge pile of
343 other features and bug fixes.
346 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
349 Changes in version 0.2.1.17-rc - 2009-07-07
350 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
351 candidate for the 0.2.1.x series. It lays the groundwork for further
352 client performance improvements, and also fixes a big bug with directory
353 authorities that were causing them to assign Guard and Stable flags
356 The Windows bundles also finally include the geoip database that we
357 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
358 should actually install Torbutton rather than giving you a cryptic
359 failure message (oops).
362 - Clients now use the bandwidth values in the consensus, rather than
363 the bandwidth values in each relay descriptor. This approach opens
364 the door to more accurate bandwidth estimates once the directory
365 authorities start doing active measurements. Implements more of
369 - When Tor clients restart after 1-5 days, they discard all their
370 cached descriptors as too old, but they still use the cached
371 consensus document. This approach is good for robustness, but
372 bad for performance: since they don't know any bandwidths, they
373 end up choosing at random rather than weighting their choice by
374 speed. Fixed by the above feature of putting bandwidths in the
375 consensus. Bugfix on 0.2.0.x.
376 - Directory authorities were neglecting to mark relays down in their
377 internal histories if the relays fall off the routerlist without
378 ever being found unreachable. So there were relays in the histories
379 that haven't been seen for eight months, and are listed as being
380 up for eight months. This wreaked havoc on the "median wfu"
381 and "median mtbf" calculations, in turn making Guard and Stable
382 flags very wrong, hurting network performance. Fixes bugs 696 and
383 969. Bugfix on 0.2.0.6-alpha.
386 - Serve the DirPortFrontPage page even when we have been approaching
387 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
388 - The control port would close the connection before flushing long
389 replies, such as the network consensus, if a QUIT command was issued
390 before the reply had completed. Now, the control port flushes all
391 pending replies before closing the connection. Also fixed a spurious
392 warning when a QUIT command is issued after a malformed or rejected
393 AUTHENTICATE command, but before the connection was closed. Patch
394 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
395 - When we can't find an intro key for a v2 hidden service descriptor,
396 fall back to the v0 hidden service descriptor and log a bug message.
397 Workaround for bug 1024.
398 - Fix a log message that did not respect the SafeLogging option.
402 - If we're a relay and we change our IP address, be more verbose
403 about the reason that made us change. Should help track down
404 further bugs for relays on dynamic IP addresses.
407 Changes in version 0.2.0.35 - 2009-06-24
409 - Avoid crashing in the presence of certain malformed descriptors.
410 Found by lark, and by automated fuzzing.
411 - Fix an edge case where a malicious exit relay could convince a
412 controller that the client's DNS question resolves to an internal IP
413 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
416 - Finally fix the bug where dynamic-IP relays disappear when their
417 IP address changes: directory mirrors were mistakenly telling
418 them their old address if they asked via begin_dir, so they
419 never got an accurate answer about their new address, so they
420 just vanished after a day. For belt-and-suspenders, relays that
421 don't set Address in their config now avoid using begin_dir for
422 all direct connections. Should fix bugs 827, 883, and 900.
423 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
424 that would occur on some exit nodes when DNS failures and timeouts
425 occurred in certain patterns. Fix for bug 957.
428 - When starting with a cache over a few days old, do not leak
429 memory for the obsolete router descriptors in it. Bugfix on
430 0.2.0.33; fixes bug 672.
431 - Hidden service clients didn't use a cached service descriptor that
432 was older than 15 minutes, but wouldn't fetch a new one either,
433 because there was already one in the cache. Now, fetch a v2
434 descriptor unless the same descriptor was added to the cache within
435 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
438 Changes in version 0.2.1.16-rc - 2009-06-20
439 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
440 a bunch of minor bugs.
443 - Fix an edge case where a malicious exit relay could convince a
444 controller that the client's DNS question resolves to an internal IP
445 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
447 o Major performance improvements (on 0.2.0.x):
448 - Disable and refactor some debugging checks that forced a linear scan
449 over the whole server-side DNS cache. These accounted for over 50%
450 of CPU time on a relatively busy exit node's gprof profile. Found
452 - Disable some debugging checks that appeared in exit node profile
456 - Update to the "June 3 2009" ip-to-country file.
457 - Do not have tor-resolve automatically refuse all .onion addresses;
458 if AutomapHostsOnResolve is set in your torrc, this will work fine.
460 o Minor bugfixes (on 0.2.0.x):
461 - Log correct error messages for DNS-related network errors on
463 - Fix a race condition that could cause crashes or memory corruption
464 when running as a server with a controller listening for log
466 - Avoid crashing when we have a policy specified in a DirPolicy or
467 SocksPolicy or ReachableAddresses option with ports set on it,
468 and we re-load the policy. May fix bug 996.
469 - Hidden service clients didn't use a cached service descriptor that
470 was older than 15 minutes, but wouldn't fetch a new one either,
471 because there was already one in the cache. Now, fetch a v2
472 descriptor unless the same descriptor was added to the cache within
473 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
475 o Minor bugfixes (on 0.2.1.x):
476 - Don't warn users about low port and hibernation mix when they
477 provide a *ListenAddress directive to fix that. Bugfix on
479 - When switching back and forth between bridge mode, do not start
480 gathering GeoIP data until two hours have passed.
481 - Do not complain that the user has requested an excluded node as
482 an exit when the node is not really an exit. This could happen
483 because the circuit was for testing, or an introduction point.
487 Changes in version 0.2.1.15-rc - 2009-05-25
488 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
489 series. It fixes a major bug on fast exit relays, as well as a variety
492 o Major bugfixes (on 0.2.0.x):
493 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
494 that would occur on some exit nodes when DNS failures and timeouts
495 occurred in certain patterns. Fix for bug 957.
497 o Minor bugfixes (on 0.2.0.x):
498 - Actually return -1 in the error case for read_bandwidth_usage().
499 Harmless bug, since we currently don't care about the return value
500 anywhere. Bugfix on 0.2.0.9-alpha.
501 - Provide a more useful log message if bug 977 (related to buffer
502 freelists) ever reappears, and do not crash right away.
503 - Fix an assertion failure on 64-bit platforms when we allocated
504 memory right up to the end of a memarea, then realigned the memory
505 one step beyond the end. Fixes a possible cause of bug 930.
506 - Protect the count of open sockets with a mutex, so we can't
507 corrupt it when two threads are closing or opening sockets at once.
508 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
509 - Don't allow a bridge to publish its router descriptor to a
510 non-bridge directory authority. Fixes part of bug 932.
511 - When we change to or from being a bridge, reset our counts of
512 client usage by country. Fixes bug 932.
513 - Fix a bug that made stream bandwidth get misreported to the
515 - Stop using malloc_usable_size() to use more area than we had
516 actually allocated: it was safe, but made valgrind really unhappy.
517 - Fix a memory leak when v3 directory authorities load their keys
518 and cert from disk. Bugfix on 0.2.0.1-alpha.
520 o Minor bugfixes (on 0.2.1.x):
521 - Fix use of freed memory when deciding to mark a non-addable
522 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
525 Changes in version 0.2.1.14-rc - 2009-04-12
526 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
527 series. It begins fixing some major performance problems, and also
528 finally addresses the bug that was causing relays on dynamic IP
529 addresses to fall out of the directory.
532 - Clients replace entry guards that were chosen more than a few months
533 ago. This change should significantly improve client performance,
534 especially once more people upgrade, since relays that have been
535 a guard for a long time are currently overloaded.
537 o Major bugfixes (on 0.2.0):
538 - Finally fix the bug where dynamic-IP relays disappear when their
539 IP address changes: directory mirrors were mistakenly telling
540 them their old address if they asked via begin_dir, so they
541 never got an accurate answer about their new address, so they
542 just vanished after a day. For belt-and-suspenders, relays that
543 don't set Address in their config now avoid using begin_dir for
544 all direct connections. Should fix bugs 827, 883, and 900.
545 - Relays were falling out of the networkstatus consensus for
546 part of a day if they changed their local config but the
547 authorities discarded their new descriptor as "not sufficiently
548 different". Now directory authorities accept a descriptor as changed
549 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
551 - Avoid crashing in the presence of certain malformed descriptors.
552 Found by lark, and by automated fuzzing.
555 - When generating circuit events with verbose nicknames for
556 controllers, try harder to look up nicknames for routers on a
557 circuit. (Previously, we would look in the router descriptors we had
558 for nicknames, but not in the consensus.) Partial fix for bug 941.
559 - If the bridge config line doesn't specify a port, assume 443.
560 This makes bridge lines a bit smaller and easier for users to
562 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
563 bytes (aka 20KB/s), to match our documentation. Also update
564 directory authorities so they always assign the Fast flag to relays
565 with 20KB/s of capacity. Now people running relays won't suddenly
566 find themselves not seeing any use, if the network gets faster
568 - Update to the "April 3 2009" ip-to-country file.
571 - Avoid trying to print raw memory to the logs when we decide to
572 give up on downloading a given relay descriptor. Bugfix on
574 - In tor-resolve, when the Tor client to use is specified by
575 <hostname>:<port>, actually use the specified port rather than
576 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
577 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
578 - When starting with a cache over a few days old, do not leak
579 memory for the obsolete router descriptors in it. Bugfix on
581 - Avoid double-free on list of successfully uploaded hidden
582 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
583 - Change memarea_strndup() implementation to work even when
584 duplicating a string at the end of a page. This bug was
585 harmless for now, but could have meant crashes later. Fix by
586 lark. Bugfix on 0.2.1.1-alpha.
587 - Limit uploaded directory documents to be 16M rather than 500K.
588 The directory authorities were refusing v3 consensus votes from
589 other authorities, since the votes are now 504K. Fixes bug 959;
590 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
591 - Directory authorities should never send a 503 "busy" response to
592 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
596 Changes in version 0.2.1.13-alpha - 2009-03-09
597 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
598 cleanups. We're finally getting close to a release candidate.
601 - Correctly update the list of which countries we exclude as
602 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
603 lark. Bugfix on 0.2.1.6-alpha.
605 o Minor bugfixes (on 0.2.0.x and earlier):
606 - Automatically detect MacOSX versions earlier than 10.4.0, and
607 disable kqueue from inside Tor when running with these versions.
608 We previously did this from the startup script, but that was no
609 help to people who didn't use the startup script. Resolves bug 863.
610 - When we had picked an exit node for a connection, but marked it as
611 "optional", and it turned out we had no onion key for the exit,
612 stop wanting that exit and try again. This situation may not
613 be possible now, but will probably become feasible with proposal
614 158. Spotted by rovv. Fixes another case of bug 752.
615 - Clients no longer cache certificates for authorities they do not
616 recognize. Bugfix on 0.2.0.9-alpha.
617 - When we can't transmit a DNS request due to a network error, retry
618 it after a while, and eventually transmit a failing response to
619 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
620 - If the controller claimed responsibility for a stream, but that
621 stream never finished making its connection, it would live
622 forever in circuit_wait state. Now we close it after SocksTimeout
623 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
624 - Drop begin cells to a hidden service if they come from the middle
625 of a circuit. Patch from lark.
626 - When we erroneously receive two EXTEND cells for the same circuit
627 ID on the same connection, drop the second. Patch from lark.
628 - Fix a crash that occurs on exit nodes when a nameserver request
629 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
630 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
632 - Do not assume that a stack-allocated character array will be
633 64-bit aligned on platforms that demand that uint64_t access is
634 aligned. Possible fix for bug 604.
635 - Parse dates and IPv4 addresses in a locale- and libc-independent
636 manner, to avoid platform-dependent behavior on malformed input.
637 - Build correctly when configured to build outside the main source
638 path. Patch from Michael Gold.
639 - We were already rejecting relay begin cells with destination port
640 of 0. Now also reject extend cells with destination port or address
641 of 0. Suggested by lark.
643 o Minor bugfixes (on 0.2.1.x):
644 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
645 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
646 - If we're an exit node, scrub the IP address to which we are exiting
647 in the logs. Bugfix on 0.2.1.8-alpha.
650 - On Linux, use the prctl call to re-enable core dumps when the user
652 - New controller event NEWCONSENSUS that lists the networkstatus
653 lines for every recommended relay. Now controllers like Torflow
654 can keep up-to-date on which relays they should be using.
655 - Update to the "February 26 2009" ip-to-country file.
658 Changes in version 0.2.0.34 - 2009-02-08
659 Tor 0.2.0.34 features several more security-related fixes. You should
660 upgrade, especially if you run an exit relay (remote crash) or a
661 directory authority (remote infinite loop), or you're on an older
662 (pre-XP) or not-recently-patched Windows (remote exploit).
664 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
665 have many known flaws, and nobody should be using them. You should
666 upgrade. If you're using a Linux or BSD and its packages are obsolete,
667 stop using those packages and upgrade anyway.
670 - Fix an infinite-loop bug on handling corrupt votes under certain
671 circumstances. Bugfix on 0.2.0.8-alpha.
672 - Fix a temporary DoS vulnerability that could be performed by
673 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
674 - Avoid a potential crash on exit nodes when processing malformed
675 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
676 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
677 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
680 - Fix compilation on systems where time_t is a 64-bit integer.
681 Patch from Matthias Drochner.
682 - Don't consider expiring already-closed client connections. Fixes
683 bug 893. Bugfix on 0.0.2pre20.
686 Changes in version 0.2.1.12-alpha - 2009-02-08
687 Tor 0.2.1.12-alpha features several more security-related fixes. You
688 should upgrade, especially if you run an exit relay (remote crash) or
689 a directory authority (remote infinite loop), or you're on an older
690 (pre-XP) or not-recently-patched Windows (remote exploit). It also
691 includes a big pile of minor bugfixes and cleanups.
694 - Fix an infinite-loop bug on handling corrupt votes under certain
695 circumstances. Bugfix on 0.2.0.8-alpha.
696 - Fix a temporary DoS vulnerability that could be performed by
697 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
698 - Avoid a potential crash on exit nodes when processing malformed
699 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
702 - Let controllers actually ask for the "clients_seen" event for
703 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
704 reported by Matt Edman.
705 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
707 - Fix a bug in address parsing that was preventing bridges or hidden
708 service targets from being at IPv6 addresses.
709 - Solve a bug that kept hardware crypto acceleration from getting
710 enabled when accounting was turned on. Fixes bug 907. Bugfix on
712 - Remove a bash-ism from configure.in to build properly on non-Linux
713 platforms. Bugfix on 0.2.1.1-alpha.
714 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
715 headers. Bugfix on 0.2.0.10-alpha.
716 - Don't consider expiring already-closed client connections. Fixes
717 bug 893. Bugfix on 0.0.2pre20.
718 - Fix another interesting corner-case of bug 891 spotted by rovv:
719 Previously, if two hosts had different amounts of clock drift, and
720 one of them created a new connection with just the wrong timing,
721 the other might decide to deprecate the new connection erroneously.
722 Bugfix on 0.1.1.13-alpha.
723 - Resolve a very rare crash bug that could occur when the user forced
724 a nameserver reconfiguration during the middle of a nameserver
725 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
726 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
727 Bugfix on 0.2.1.7-alpha.
728 - If we're using bridges and our network goes away, be more willing
729 to forgive our bridges and try again when we get an application
730 request. Bugfix on 0.2.0.x.
733 - Support platforms where time_t is 64 bits long. (Congratulations,
734 NetBSD!) Patch from Matthias Drochner.
735 - Add a 'getinfo status/clients-seen' controller command, in case
736 controllers want to hear clients_seen events but connect late.
739 - Disable GCC's strict alias optimization by default, to avoid the
740 likelihood of its introducing subtle bugs whenever our code violates
741 the letter of C99's alias rules.
744 Changes in version 0.2.0.33 - 2009-01-21
745 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
746 useful to users. It also finally fixes a bug where a relay or client
747 that's been off for many days would take a long time to bootstrap.
749 This update also fixes an important security-related bug reported by
750 Ilja van Sprundel. You should upgrade. (We'll send out more details
751 about the bug once people have had some time to upgrade.)
754 - Fix a heap-corruption bug that may be remotely triggerable on
755 some platforms. Reported by Ilja van Sprundel.
758 - When a stream at an exit relay is in state "resolving" or
759 "connecting" and it receives an "end" relay cell, the exit relay
760 would silently ignore the end cell and not close the stream. If
761 the client never closes the circuit, then the exit relay never
762 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
764 - When sending CREATED cells back for a given circuit, use a 64-bit
765 connection ID to find the right connection, rather than an addr:port
766 combination. Now that we can have multiple OR connections between
767 the same ORs, it is no longer possible to use addr:port to uniquely
768 identify a connection.
769 - Bridge relays that had DirPort set to 0 would stop fetching
770 descriptors shortly after startup, and then briefly resume
771 after a new bandwidth test and/or after publishing a new bridge
772 descriptor. Bridge users that try to bootstrap from them would
773 get a recent networkstatus but would get descriptors from up to
774 18 hours earlier, meaning most of the descriptors were obsolete
775 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
776 - Prevent bridge relays from serving their 'extrainfo' document
777 to anybody who asks, now that extrainfo docs include potentially
778 sensitive aggregated client geoip summaries. Bugfix on
780 - If the cached networkstatus consensus is more than five days old,
781 discard it rather than trying to use it. In theory it could be
782 useful because it lists alternate directory mirrors, but in practice
783 it just means we spend many minutes trying directory mirrors that
784 are long gone from the network. Also discard router descriptors as
785 we load them if they are more than five days old, since the onion
786 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
789 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
790 could make gcc generate non-functional binary search code. Bugfix
792 - Build correctly on platforms without socklen_t.
793 - Compile without warnings on solaris.
794 - Avoid potential crash on internal error during signature collection.
795 Fixes bug 864. Patch from rovv.
796 - Correct handling of possible malformed authority signing key
797 certificates with internal signature types. Fixes bug 880.
798 Bugfix on 0.2.0.3-alpha.
799 - Fix a hard-to-trigger resource leak when logging credential status.
801 - When we can't initialize DNS because the network is down, do not
802 automatically stop Tor from starting. Instead, we retry failed
803 dns_init() every 10 minutes, and change the exit policy to reject
804 *:* until one succeeds. Fixes bug 691.
805 - Use 64 bits instead of 32 bits for connection identifiers used with
806 the controller protocol, to greatly reduce risk of identifier reuse.
807 - When we're choosing an exit node for a circuit, and we have
808 no pending streams, choose a good general exit rather than one that
809 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
810 - Fix another case of assuming, when a specific exit is requested,
811 that we know more than the user about what hosts it allows.
812 Fixes one case of bug 752. Patch from rovv.
813 - Clip the MaxCircuitDirtiness config option to a minimum of 10
814 seconds. Warn the user if lower values are given in the
815 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
816 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
817 user if lower values are given in the configuration. Bugfix on
818 0.1.1.17-rc. Patch by Sebastian.
819 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
820 the cache because we already had a v0 descriptor with the same ID.
821 Bugfix on 0.2.0.18-alpha.
822 - Fix a race condition when freeing keys shared between main thread
823 and CPU workers that could result in a memory leak. Bugfix on
824 0.1.0.1-rc. Fixes bug 889.
825 - Send a valid END cell back when a client tries to connect to a
826 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
827 840. Patch from rovv.
828 - Check which hops rendezvous stream cells are associated with to
829 prevent possible guess-the-streamid injection attacks from
830 intermediate hops. Fixes another case of bug 446. Based on patch
832 - If a broken client asks a non-exit router to connect somewhere,
833 do not even do the DNS lookup before rejecting the connection.
834 Fixes another case of bug 619. Patch from rovv.
835 - When a relay gets a create cell it can't decrypt (e.g. because it's
836 using the wrong onion key), we were dropping it and letting the
837 client time out. Now actually answer with a destroy cell. Fixes
838 bug 904. Bugfix on 0.0.2pre8.
840 o Minor bugfixes (hidden services):
841 - Do not throw away existing introduction points on SIGHUP. Bugfix on
842 0.0.6pre1. Patch by Karsten. Fixes bug 874.
845 - Report the case where all signatures in a detached set are rejected
846 differently than the case where there is an error handling the
848 - When we realize that another process has modified our cached
849 descriptors, print out a more useful error message rather than
850 triggering an assertion. Fixes bug 885. Patch from Karsten.
851 - Implement the 0x20 hack to better resist DNS poisoning: set the
852 case on outgoing DNS requests randomly, and reject responses that do
853 not match the case correctly. This logic can be disabled with the
854 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
855 of servers that do not reliably preserve case in replies. See
856 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
858 - Check DNS replies for more matching fields to better resist DNS
860 - Never use OpenSSL compression: it wastes RAM and CPU trying to
861 compress cells, which are basically all encrypted, compressed, or
865 Changes in version 0.2.1.11-alpha - 2009-01-20
866 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
867 week it will take a long time to bootstrap again" bug. It also fixes
868 an important security-related bug reported by Ilja van Sprundel. You
869 should upgrade. (We'll send out more details about the bug once people
870 have had some time to upgrade.)
873 - Fix a heap-corruption bug that may be remotely triggerable on
874 some platforms. Reported by Ilja van Sprundel.
877 - Discard router descriptors as we load them if they are more than
878 five days old. Otherwise if Tor is off for a long time and then
879 starts with cached descriptors, it will try to use the onion
880 keys in those obsolete descriptors when building circuits. Bugfix
881 on 0.2.0.x. Fixes bug 887.
884 - Try to make sure that the version of Libevent we're running with
885 is binary-compatible with the one we built with. May address bug
887 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
888 for bug 905. Bugfix on 0.2.1.7-alpha.
889 - Add a new --enable-local-appdata configuration switch to change
890 the default location of the datadir on win32 from APPDATA to
891 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
892 entirely. Patch from coderman.
895 - Make outbound DNS packets respect the OutboundBindAddress setting.
896 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
897 - When our circuit fails at the first hop (e.g. we get a destroy
898 cell back), avoid using that OR connection anymore, and also
899 tell all the one-hop directory requests waiting for it that they
900 should fail. Bugfix on 0.2.1.3-alpha.
901 - In the torify(1) manpage, mention that tsocks will leak your
905 Changes in version 0.2.1.10-alpha - 2009-01-06
906 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
907 would make the bridge relay not so useful if it had DirPort set to 0,
908 and one that could let an attacker learn a little bit of information
909 about the bridge's users), and a bug that would cause your Tor relay
910 to ignore a circuit create request it can't decrypt (rather than reply
911 with an error). It also fixes a wide variety of other bugs.
914 - If the cached networkstatus consensus is more than five days old,
915 discard it rather than trying to use it. In theory it could
916 be useful because it lists alternate directory mirrors, but in
917 practice it just means we spend many minutes trying directory
918 mirrors that are long gone from the network. Helps bug 887 a bit;
920 - Bridge relays that had DirPort set to 0 would stop fetching
921 descriptors shortly after startup, and then briefly resume
922 after a new bandwidth test and/or after publishing a new bridge
923 descriptor. Bridge users that try to bootstrap from them would
924 get a recent networkstatus but would get descriptors from up to
925 18 hours earlier, meaning most of the descriptors were obsolete
926 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
927 - Prevent bridge relays from serving their 'extrainfo' document
928 to anybody who asks, now that extrainfo docs include potentially
929 sensitive aggregated client geoip summaries. Bugfix on
933 - New controller event "clients_seen" to report a geoip-based summary
934 of which countries we've seen clients from recently. Now controllers
935 like Vidalia can show bridge operators that they're actually making
937 - Build correctly against versions of OpenSSL 0.9.8 or later built
938 without support for deprecated functions.
939 - Update to the "December 19 2008" ip-to-country file.
941 o Minor bugfixes (on 0.2.0.x):
942 - Authorities now vote for the Stable flag for any router whose
943 weighted MTBF is at least 5 days, regardless of the mean MTBF.
944 - Do not remove routers as too old if we do not have any consensus
945 document. Bugfix on 0.2.0.7-alpha.
946 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
947 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
948 - When an exit relay resolves a stream address to a local IP address,
949 do not just keep retrying that same exit relay over and
950 over. Instead, just close the stream. Addresses bug 872. Bugfix
951 on 0.2.0.32. Patch from rovv.
952 - If a hidden service sends us an END cell, do not consider
953 retrying the connection; just close it. Patch from rovv.
954 - When we made bridge authorities stop serving bridge descriptors over
955 unencrypted links, we also broke DirPort reachability testing for
956 bridges. So bridges with a non-zero DirPort were printing spurious
957 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
958 - When a relay gets a create cell it can't decrypt (e.g. because it's
959 using the wrong onion key), we were dropping it and letting the
960 client time out. Now actually answer with a destroy cell. Fixes
961 bug 904. Bugfix on 0.0.2pre8.
962 - Squeeze 2-5% out of client performance (according to oprofile) by
963 improving the implementation of some policy-manipulation functions.
965 o Minor bugfixes (on 0.2.1.x):
966 - Make get_interface_address() function work properly again; stop
967 guessing the wrong parts of our address as our address.
968 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
969 send on that circuit. Otherwise we might violate the proposal-110
970 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
972 - When we're sending non-EXTEND cells to the first hop in a circuit,
973 for example to use an encrypted directory connection, we don't need
974 to use RELAY_EARLY cells: the first hop knows what kind of cell
975 it is, and nobody else can even see the cell type. Conserving
976 RELAY_EARLY cells makes it easier to cannibalize circuits like
978 - Stop logging nameserver addresses in reverse order.
979 - If we are retrying a directory download slowly over and over, do
980 not automatically give up after the 254th failure. Bugfix on
982 - Resume reporting accurate "stream end" reasons to the local control
983 port. They were lost in the changes for Proposal 148. Bugfix on
986 o Deprecated and removed features:
987 - The old "tor --version --version" command, which would print out
988 the subversion "Id" of most of the source files, is now removed. It
989 turned out to be less useful than we'd expected, and harder to
992 o Code simplifications and refactoring:
993 - Change our header file guard macros to be less likely to conflict
994 with system headers. Adam Langley noticed that we were conflicting
995 with log.h on Android.
996 - Tool-assisted documentation cleanup. Nearly every function or
997 static variable in Tor should have its own documentation now.
1000 Changes in version 0.2.1.9-alpha - 2008-12-25
1001 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
1003 o New directory authorities:
1004 - gabelmoo (the authority run by Karsten Loesing) now has a new
1008 - Never use a connection with a mismatched address to extend a
1009 circuit, unless that connection is canonical. A canonical
1010 connection is one whose address is authenticated by the router's
1011 identity key, either in a NETINFO cell or in a router descriptor.
1012 - Avoid a possible memory corruption bug when receiving hidden service
1013 descriptors. Bugfix on 0.2.1.6-alpha.
1016 - Fix a logic error that would automatically reject all but the first
1017 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
1018 part of bug 813/868. Bug spotted by coderman.
1019 - When a stream at an exit relay is in state "resolving" or
1020 "connecting" and it receives an "end" relay cell, the exit relay
1021 would silently ignore the end cell and not close the stream. If
1022 the client never closes the circuit, then the exit relay never
1023 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
1025 - When we can't initialize DNS because the network is down, do not
1026 automatically stop Tor from starting. Instead, retry failed
1027 dns_init() every 10 minutes, and change the exit policy to reject
1028 *:* until one succeeds. Fixes bug 691.
1031 - Give a better error message when an overzealous init script says
1032 "sudo -u username tor --user username". Makes Bug 882 easier for
1034 - When a directory authority gives us a new guess for our IP address,
1035 log which authority we used. Hopefully this will help us debug
1036 the recent complaints about bad IP address guesses.
1037 - Detect svn revision properly when we're using git-svn.
1038 - Try not to open more than one descriptor-downloading connection
1039 to an authority at once. This should reduce load on directory
1040 authorities. Fixes bug 366.
1041 - Add cross-certification to newly generated certificates, so that
1042 a signing key is enough information to look up a certificate.
1043 Partial implementation of proposal 157.
1044 - Start serving certificates by <identity digest, signing key digest>
1045 pairs. Partial implementation of proposal 157.
1046 - Clients now never report any stream end reason except 'MISC'.
1047 Implements proposal 148.
1048 - On platforms with a maximum syslog string length, truncate syslog
1049 messages to that length ourselves, rather than relying on the
1050 system to do it for us.
1051 - Optimize out calls to time(NULL) that occur for every IO operation,
1052 or for every cell. On systems where time() is a slow syscall,
1053 this fix will be slightly helpful.
1054 - Exit servers can now answer resolve requests for ip6.arpa addresses.
1055 - When we download a descriptor that we then immediately (as
1056 a directory authority) reject, do not retry downloading it right
1057 away. Should save some bandwidth on authorities. Fix for bug
1058 888. Patch by Sebastian Hahn.
1059 - When a download gets us zero good descriptors, do not notify
1060 Tor that new directory information has arrived.
1061 - Avoid some nasty corner cases in the logic for marking connections
1062 as too old or obsolete or noncanonical for circuits. Partial
1065 o Minor features (controller):
1066 - New CONSENSUS_ARRIVED event to note when a new consensus has
1067 been fetched and validated.
1068 - When we realize that another process has modified our cached
1069 descriptors file, print out a more useful error message rather
1070 than triggering an assertion. Fixes bug 885. Patch from Karsten.
1071 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
1072 controllers to prevent SIGHUP from reloading the
1073 configuration. Fixes bug 856.
1076 - Resume using the correct "REASON=" stream when telling the
1077 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
1078 - When a canonical connection appears later in our internal list
1079 than a noncanonical one for a given OR ID, always use the
1080 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
1082 - Clip the MaxCircuitDirtiness config option to a minimum of 10
1083 seconds. Warn the user if lower values are given in the
1084 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
1085 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
1086 user if lower values are given in the configuration. Bugfix on
1087 0.1.1.17-rc. Patch by Sebastian.
1088 - Fix a race condition when freeing keys shared between main thread
1089 and CPU workers that could result in a memory leak. Bugfix on
1090 0.1.0.1-rc. Fixes bug 889.
1092 o Minor bugfixes (hidden services):
1093 - Do not throw away existing introduction points on SIGHUP (bugfix on
1094 0.0.6pre1); also, do not stall hidden services because we're
1095 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
1096 by John Brooks. Patch by Karsten. Fixes bug 874.
1097 - Fix a memory leak when we decline to add a v2 rendezvous
1098 descriptor to the cache because we already had a v0 descriptor
1099 with the same ID. Bugfix on 0.2.0.18-alpha.
1101 o Deprecated and removed features:
1102 - RedirectExits has been removed. It was deprecated since
1104 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
1105 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
1106 - Cell pools are now always enabled; --disable-cell-pools is ignored.
1108 o Code simplifications and refactoring:
1109 - Rename the confusing or_is_obsolete field to the more appropriate
1110 is_bad_for_new_circs, and move it to or_connection_t where it
1112 - Move edge-only flags from connection_t to edge_connection_t: not
1113 only is this better coding, but on machines of plausible alignment,
1114 it should save 4-8 bytes per connection_t. "Every little bit helps."
1115 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
1116 for consistency; keep old option working for backward compatibility.
1117 - Simplify the code for finding connections to use for a circuit.
1120 Changes in version 0.2.1.8-alpha - 2008-12-08
1121 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
1122 builds better on unusual platforms like Solaris and old OS X, and
1123 fixes a variety of other issues.
1126 - New DirPortFrontPage option that takes an html file and publishes
1127 it as "/" on the DirPort. Now relay operators can provide a
1128 disclaimer without needing to set up a separate webserver. There's
1129 a sample disclaimer in contrib/tor-exit-notice.html.
1132 - When the client is choosing entry guards, now it selects at most
1133 one guard from a given relay family. Otherwise we could end up with
1134 all of our entry points into the network run by the same operator.
1135 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
1138 - Fix a DOS opportunity during the voting signature collection process
1139 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
1140 - Fix a possible segfault when establishing an exit connection. Bugfix
1144 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
1146 - Made Tor a little less aggressive about deleting expired
1147 certificates. Partial fix for bug 854.
1148 - Stop doing unaligned memory access that generated bus errors on
1149 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
1150 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
1151 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
1152 - Make USR2 log-level switch take effect immediately. Bugfix on
1154 - If one win32 nameserver fails to get added, continue adding the
1155 rest, and don't automatically fail.
1156 - Use fcntl() for locking when flock() is not available. Should fix
1157 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
1158 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
1159 could make gcc generate non-functional binary search code. Bugfix
1161 - Build correctly on platforms without socklen_t.
1162 - Avoid potential crash on internal error during signature collection.
1163 Fixes bug 864. Patch from rovv.
1164 - Do not use C's stdio library for writing to log files. This will
1165 improve logging performance by a minute amount, and will stop
1166 leaking fds when our disk is full. Fixes bug 861.
1167 - Stop erroneous use of O_APPEND in cases where we did not in fact
1168 want to re-seek to the end of a file before every last write().
1169 - Correct handling of possible malformed authority signing key
1170 certificates with internal signature types. Fixes bug 880. Bugfix
1172 - Fix a hard-to-trigger resource leak when logging credential status.
1176 - Directory mirrors no longer fetch the v1 directory or
1177 running-routers files. They are obsolete, and nobody asks for them
1178 anymore. This is the first step to making v1 authorities obsolete.
1180 o Minor features (controller):
1181 - Return circuit purposes in response to GETINFO circuit-status. Fixes
1185 Changes in version 0.2.0.32 - 2008-11-20
1186 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
1187 packages (and maybe other packages) noticed by Theo de Raadt, fixes
1188 a smaller security flaw that might allow an attacker to access local
1189 services, further improves hidden service performance, and fixes a
1190 variety of other issues.
1193 - The "User" and "Group" config options did not clear the
1194 supplementary group entries for the Tor process. The "User" option
1195 is now more robust, and we now set the groups to the specified
1196 user's primary group. The "Group" option is now ignored. For more
1197 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
1198 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
1199 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
1200 - The "ClientDNSRejectInternalAddresses" config option wasn't being
1201 consistently obeyed: if an exit relay refuses a stream because its
1202 exit policy doesn't allow it, we would remember what IP address
1203 the relay said the destination address resolves to, even if it's
1204 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
1207 - Fix a DOS opportunity during the voting signature collection process
1208 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
1210 o Major bugfixes (hidden services):
1211 - When fetching v0 and v2 rendezvous service descriptors in parallel,
1212 we were failing the whole hidden service request when the v0
1213 descriptor fetch fails, even if the v2 fetch is still pending and
1214 might succeed. Similarly, if the last v2 fetch fails, we were
1215 failing the whole hidden service request even if a v0 fetch is
1216 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
1217 - When extending a circuit to a hidden service directory to upload a
1218 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
1219 requests failed, because the router descriptor has not been
1220 downloaded yet. In these cases, do not attempt to upload the
1221 rendezvous descriptor, but wait until the router descriptor is
1222 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
1223 descriptor from a hidden service directory for which the router
1224 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
1228 - Fix several infrequent memory leaks spotted by Coverity.
1229 - When testing for libevent functions, set the LDFLAGS variable
1230 correctly. Found by Riastradh.
1231 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
1232 bootstrapping with tunneled directory connections. Bugfix on
1233 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
1234 - When asked to connect to A.B.exit:80, if we don't know the IP for A
1235 and we know that server B rejects most-but-not all connections to
1236 port 80, we would previously reject the connection. Now, we assume
1237 the user knows what they were asking for. Fixes bug 752. Bugfix
1238 on 0.0.9rc5. Diagnosed by BarkerJr.
1239 - If we overrun our per-second write limits a little, count this as
1240 having used up our write allocation for the second, and choke
1241 outgoing directory writes. Previously, we had only counted this when
1242 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
1243 Bugfix on 0.2.0.x (??).
1244 - Remove the old v2 directory authority 'lefkada' from the default
1245 list. It has been gone for many months.
1246 - Stop doing unaligned memory access that generated bus errors on
1247 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
1248 - Make USR2 log-level switch take effect immediately. Bugfix on
1251 o Minor bugfixes (controller):
1252 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
1253 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
1256 Changes in version 0.2.1.7-alpha - 2008-11-08
1257 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
1258 packages (and maybe other packages) noticed by Theo de Raadt, fixes
1259 a smaller security flaw that might allow an attacker to access local
1260 services, adds better defense against DNS poisoning attacks on exit
1261 relays, further improves hidden service performance, and fixes a
1262 variety of other issues.
1265 - The "ClientDNSRejectInternalAddresses" config option wasn't being
1266 consistently obeyed: if an exit relay refuses a stream because its
1267 exit policy doesn't allow it, we would remember what IP address
1268 the relay said the destination address resolves to, even if it's
1269 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
1270 - The "User" and "Group" config options did not clear the
1271 supplementary group entries for the Tor process. The "User" option
1272 is now more robust, and we now set the groups to the specified
1273 user's primary group. The "Group" option is now ignored. For more
1274 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
1275 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
1276 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
1277 - Do not use or believe expired v3 authority certificates. Patch
1278 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
1281 - Now NodeFamily and MyFamily config options allow spaces in
1282 identity fingerprints, so it's easier to paste them in.
1283 Suggested by Lucky Green.
1284 - Implement the 0x20 hack to better resist DNS poisoning: set the
1285 case on outgoing DNS requests randomly, and reject responses that do
1286 not match the case correctly. This logic can be disabled with the
1287 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
1288 of servers that do not reliably preserve case in replies. See
1289 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
1291 - Preserve case in replies to DNSPort requests in order to support
1292 the 0x20 hack for resisting DNS poisoning attacks.
1294 o Hidden service performance improvements:
1295 - When the client launches an introduction circuit, retry with a
1296 new circuit after 30 seconds rather than 60 seconds.
1297 - Launch a second client-side introduction circuit in parallel
1298 after a delay of 15 seconds (based on work by Christian Wilms).
1299 - Hidden services start out building five intro circuits rather
1300 than three, and when the first three finish they publish a service
1301 descriptor using those. Now we publish our service descriptor much
1302 faster after restart.
1305 - Minor fix in the warning messages when you're having problems
1306 bootstrapping; also, be more forgiving of bootstrap problems when
1307 we're still making incremental progress on a given bootstrap phase.
1308 - When we're choosing an exit node for a circuit, and we have
1309 no pending streams, choose a good general exit rather than one that
1310 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
1311 - Send a valid END cell back when a client tries to connect to a
1312 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
1313 840. Patch from rovv.
1314 - If a broken client asks a non-exit router to connect somewhere,
1315 do not even do the DNS lookup before rejecting the connection.
1316 Fixes another case of bug 619. Patch from rovv.
1317 - Fix another case of assuming, when a specific exit is requested,
1318 that we know more than the user about what hosts it allows.
1319 Fixes another case of bug 752. Patch from rovv.
1320 - Check which hops rendezvous stream cells are associated with to
1321 prevent possible guess-the-streamid injection attacks from
1322 intermediate hops. Fixes another case of bug 446. Based on patch
1324 - Avoid using a negative right-shift when comparing 32-bit
1325 addresses. Possible fix for bug 845 and bug 811.
1326 - Make the assert_circuit_ok() function work correctly on circuits that
1327 have already been marked for close.
1328 - Fix read-off-the-end-of-string error in unit tests when decoding
1329 introduction points.
1330 - Fix uninitialized size field for memory area allocation: may improve
1331 memory performance during directory parsing.
1332 - Treat duplicate certificate fetches as failures, so that we do
1333 not try to re-fetch an expired certificate over and over and over.
1334 - Do not say we're fetching a certificate when we'll in fact skip it
1335 because of a pending download.
1338 Changes in version 0.2.1.6-alpha - 2008-09-30
1339 Tor 0.2.1.6-alpha further improves performance and robustness of
1340 hidden services, starts work on supporting per-country relay selection,
1341 and fixes a variety of smaller issues.
1344 - Implement proposal 121: make it possible to build hidden services
1345 that only certain clients are allowed to connect to. This is
1346 enforced at several points, so that unauthorized clients are unable
1347 to send INTRODUCE cells to the service, or even (depending on the
1348 type of authentication) to learn introduction points. This feature
1349 raises the bar for certain kinds of active attacks against hidden
1350 services. Code by Karsten Loesing.
1351 - Relays now store and serve v2 hidden service descriptors by default,
1352 i.e., the new default value for HidServDirectoryV2 is 1. This is
1353 the last step in proposal 114, which aims to make hidden service
1354 lookups more reliable.
1355 - Start work to allow node restrictions to include country codes. The
1356 syntax to exclude nodes in a country with country code XX is
1357 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
1358 refinement to decide what config options should take priority if
1359 you ask to both use a particular node and exclude it.
1360 - Allow ExitNodes list to include IP ranges and country codes, just
1361 like the Exclude*Nodes lists. Patch from Robert Hogan.
1364 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
1365 Tor to fail to start if you had it configured to use a bridge
1366 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
1367 - When extending a circuit to a hidden service directory to upload a
1368 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
1369 requests failed, because the router descriptor had not been
1370 downloaded yet. In these cases, we now wait until the router
1371 descriptor is downloaded, and then retry. Likewise, clients
1372 now skip over a hidden service directory if they don't yet have
1373 its router descriptor, rather than futilely requesting it and
1374 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
1376 - When fetching v0 and v2 rendezvous service descriptors in parallel,
1377 we were failing the whole hidden service request when the v0
1378 descriptor fetch fails, even if the v2 fetch is still pending and
1379 might succeed. Similarly, if the last v2 fetch fails, we were
1380 failing the whole hidden service request even if a v0 fetch is
1381 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
1382 - DNS replies need to have names matching their requests, but
1383 these names should be in the questions section, not necessarily
1384 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
1387 - Update to the "September 1 2008" ip-to-country file.
1388 - Allow ports 465 and 587 in the default exit policy again. We had
1389 rejected them in 0.1.0.15, because back in 2005 they were commonly
1390 misconfigured and ended up as spam targets. We hear they are better
1391 locked down these days.
1392 - Use a lockfile to make sure that two Tor processes are not
1393 simultaneously running with the same datadir.
1394 - Serve the latest v3 networkstatus consensus via the control
1395 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
1396 - Better logging about stability/reliability calculations on directory
1398 - Drop the requirement to have an open dir port for storing and
1399 serving v2 hidden service descriptors.
1400 - Directory authorities now serve a /tor/dbg-stability.txt URL to
1401 help debug WFU and MTBF calculations.
1402 - Implement most of Proposal 152: allow specialized servers to permit
1403 single-hop circuits, and clients to use those servers to build
1404 single-hop circuits when using a specialized controller. Patch
1405 from Josh Albrecht. Resolves feature request 768.
1406 - Add a -p option to tor-resolve for specifying the SOCKS port: some
1407 people find host:port too confusing.
1408 - Make TrackHostExit mappings expire a while after their last use, not
1409 after their creation. Patch from Robert Hogan.
1410 - Provide circuit purposes along with circuit events to the controller.
1413 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
1415 - Fixed some memory leaks -- some quite frequent, some almost
1416 impossible to trigger -- based on results from Coverity.
1417 - When testing for libevent functions, set the LDFLAGS variable
1418 correctly. Found by Riastradh.
1419 - Fix an assertion bug in parsing policy-related options; possible fix
1421 - Catch and report a few more bootstrapping failure cases when Tor
1422 fails to establish a TCP connection. Cleanup on 0.2.1.x.
1423 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
1424 bootstrapping with tunneled directory connections. Bugfix on
1425 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
1426 - When asked to connect to A.B.exit:80, if we don't know the IP for A
1427 and we know that server B rejects most-but-not all connections to
1428 port 80, we would previously reject the connection. Now, we assume
1429 the user knows what they were asking for. Fixes bug 752. Bugfix
1430 on 0.0.9rc5. Diagnosed by BarkerJr.
1431 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
1432 service directories if they have no advertised dir port. Bugfix
1434 - If we overrun our per-second write limits a little, count this as
1435 having used up our write allocation for the second, and choke
1436 outgoing directory writes. Previously, we had only counted this when
1437 we had met our limits precisely. Fixes bug 824. Patch by rovv.
1438 Bugfix on 0.2.0.x (??).
1439 - Avoid a "0 divided by 0" calculation when calculating router uptime
1440 at directory authorities. Bugfix on 0.2.0.8-alpha.
1441 - Make DNS resolved controller events into "CLOSED", not
1442 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
1444 - Fix a bug where an unreachable relay would establish enough
1445 reachability testing circuits to do a bandwidth test -- if
1446 we already have a connection to the middle hop of the testing
1447 circuit, then it could establish the last hop by using the existing
1448 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
1449 circuits no longer use entry guards in 0.2.1.3-alpha.
1450 - If we have correct permissions on $datadir, we complain to stdout
1451 and fail to start. But dangerous permissions on
1452 $datadir/cached-status/ would cause us to open a log and complain
1453 there. Now complain to stdout and fail to start in both cases. Fixes
1454 bug 820, reported by seeess.
1455 - Remove the old v2 directory authority 'lefkada' from the default
1456 list. It has been gone for many months.
1458 o Code simplifications and refactoring:
1459 - Revise the connection_new functions so that a more typesafe variant
1460 exists. This will work better with Coverity, and let us find any
1461 actual mistakes we're making here.
1462 - Refactor unit testing logic so that dmalloc can be used sensibly
1463 with unit tests to check for memory leaks.
1464 - Move all hidden-service related fields from connection and circuit
1465 structure to substructures: this way they won't eat so much memory.
1468 Changes in version 0.2.0.31 - 2008-09-03
1469 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
1470 a big bug we're seeing where in rare cases traffic from one Tor stream
1471 gets mixed into another stream, and fixes a variety of smaller issues.
1474 - Make sure that two circuits can never exist on the same connection
1475 with the same circuit ID, even if one is marked for close. This
1476 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
1477 - Relays now reject risky extend cells: if the extend cell includes
1478 a digest of all zeroes, or asks to extend back to the relay that
1479 sent the extend cell, tear down the circuit. Ideas suggested
1481 - If not enough of our entry guards are available so we add a new
1482 one, we might use the new one even if it overlapped with the
1483 current circuit's exit relay (or its family). Anonymity bugfix
1484 pointed out by rovv.
1487 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
1488 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
1489 - Correctly detect the presence of the linux/netfilter_ipv4.h header
1490 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
1491 - Pick size of default geoip filename string correctly on windows.
1492 Fixes bug 806. Bugfix on 0.2.0.30.
1493 - Make the autoconf script accept the obsolete --with-ssl-dir
1494 option as an alias for the actually-working --with-openssl-dir
1495 option. Fix the help documentation to recommend --with-openssl-dir.
1496 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
1497 - When using the TransPort option on OpenBSD, and using the User
1498 option to change UID and drop privileges, make sure to open
1499 /dev/pf before dropping privileges. Fixes bug 782. Patch from
1500 Christopher Davis. Bugfix on 0.1.2.1-alpha.
1501 - Try to attach connections immediately upon receiving a RENDEZVOUS2
1502 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
1503 on the client side when connecting to a hidden service. Bugfix
1504 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
1505 - When closing an application-side connection because its circuit is
1506 getting torn down, generate the stream event correctly. Bugfix on
1507 0.1.2.x. Anonymous patch.
1510 Changes in version 0.2.1.5-alpha - 2008-08-31
1511 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
1512 in a lot of the infrastructure for adding authorization to hidden
1513 services, lays the groundwork for having clients read their load
1514 balancing information out of the networkstatus consensus rather than
1515 the individual router descriptors, addresses two potential anonymity
1516 issues, and fixes a variety of smaller issues.
1519 - Convert many internal address representations to optionally hold
1521 - Generate and accept IPv6 addresses in many protocol elements.
1522 - Make resolver code handle nameservers located at ipv6 addresses.
1523 - Begin implementation of proposal 121 ("Client authorization for
1524 hidden services"): configure hidden services with client
1525 authorization, publish descriptors for them, and configure
1526 authorization data for hidden services at clients. The next
1527 step is to actually access hidden services that perform client
1529 - More progress toward proposal 141: Network status consensus
1530 documents and votes now contain bandwidth information for each
1531 router and a summary of that router's exit policy. Eventually this
1532 will be used by clients so that they do not have to download every
1533 known descriptor before building circuits.
1535 o Major bugfixes (on 0.2.0.x and before):
1536 - When sending CREATED cells back for a given circuit, use a 64-bit
1537 connection ID to find the right connection, rather than an addr:port
1538 combination. Now that we can have multiple OR connections between
1539 the same ORs, it is no longer possible to use addr:port to uniquely
1540 identify a connection.
1541 - Relays now reject risky extend cells: if the extend cell includes
1542 a digest of all zeroes, or asks to extend back to the relay that
1543 sent the extend cell, tear down the circuit. Ideas suggested
1545 - If not enough of our entry guards are available so we add a new
1546 one, we might use the new one even if it overlapped with the
1547 current circuit's exit relay (or its family). Anonymity bugfix
1548 pointed out by rovv.
1551 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
1552 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
1553 - When using the TransPort option on OpenBSD, and using the User
1554 option to change UID and drop privileges, make sure to open /dev/pf
1555 before dropping privileges. Fixes bug 782. Patch from Christopher
1556 Davis. Bugfix on 0.1.2.1-alpha.
1557 - Correctly detect the presence of the linux/netfilter_ipv4.h header
1558 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
1559 - Add a missing safe_str() call for a debug log message.
1560 - Use 64 bits instead of 32 bits for connection identifiers used with
1561 the controller protocol, to greatly reduce risk of identifier reuse.
1562 - Make the autoconf script accept the obsolete --with-ssl-dir
1563 option as an alias for the actually-working --with-openssl-dir
1564 option. Fix the help documentation to recommend --with-openssl-dir.
1565 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
1568 - Rate-limit too-many-sockets messages: when they happen, they happen
1569 a lot. Resolves bug 748.
1570 - Resist DNS poisoning a little better by making sure that names in
1571 answer sections match.
1572 - Print the SOCKS5 error message string as well as the error code
1573 when a tor-resolve request fails. Patch from Jacob.
1576 Changes in version 0.2.1.4-alpha - 2008-08-04
1577 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
1580 - The address part of exit policies was not correctly written
1581 to router descriptors. This generated router descriptors that failed
1582 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
1584 - Tor triggered a false assert when extending a circuit to a relay
1585 but we already have a connection open to that relay. Noticed by
1586 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
1589 - Fix a hidden service logging bug: in some edge cases, the router
1590 descriptor of a previously picked introduction point becomes
1591 obsolete and we need to give up on it rather than continually
1592 complaining that it has become obsolete. Observed by xiando. Bugfix
1596 - Take out the TestVia config option, since it was a workaround for
1597 a bug that was fixed in Tor 0.1.1.21.
1600 Changes in version 0.2.1.3-alpha - 2008-08-03
1601 Tor 0.2.1.3-alpha implements most of the pieces to prevent
1602 infinite-length circuit attacks (see proposal 110); fixes a bug that
1603 might cause exit relays to corrupt streams they send back; allows
1604 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
1605 ExcludeExitNodes config options; and fixes a big pile of bugs.
1607 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
1608 - Send a bootstrap problem "warn" event on the first problem if the
1609 reason is NO_ROUTE (that is, our network is down).
1612 - Implement most of proposal 110: The first K cells to be sent
1613 along a circuit are marked as special "early" cells; only K "early"
1614 cells will be allowed. Once this code is universal, we can block
1615 certain kinds of DOS attack by requiring that EXTEND commands must
1616 be sent using an "early" cell.
1619 - Try to attach connections immediately upon receiving a RENDEZVOUS2
1620 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
1621 on the client side when connecting to a hidden service. Bugfix
1622 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
1623 - Ensure that two circuits can never exist on the same connection
1624 with the same circuit ID, even if one is marked for close. This
1625 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
1628 - When relays do their initial bandwidth measurement, don't limit
1629 to just our entry guards for the test circuits. Otherwise we tend
1630 to have multiple test circuits going through a single entry guard,
1631 which makes our bandwidth test less accurate. Fixes part of bug 654;
1632 patch contributed by Josh Albrecht.
1633 - Add an ExcludeExitNodes option so users can list a set of nodes
1634 that should be be excluded from the exit node position, but
1635 allowed elsewhere. Implements proposal 151.
1636 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
1637 ExcludeNodes and ExcludeExitNodes lists.
1638 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
1639 be more efficient. Formerly it was quadratic in the number of
1640 servers; now it should be linear. Fixes bug 509.
1641 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
1642 and n_conn_id_digest fields into a separate structure that's
1643 only needed when the circuit has not yet attached to an n_conn.
1646 - Change the contrib/tor.logrotate script so it makes the new
1647 logs as "_tor:_tor" rather than the default, which is generally
1648 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
1649 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
1650 warnings (occasionally), but it can also cause the compiler to
1651 eliminate error-checking code. Suggested by Peter Gutmann.
1652 - When a hidden service is giving up on an introduction point candidate
1653 that was not included in the last published rendezvous descriptor,
1654 don't reschedule publication of the next descriptor. Fixes bug 763.
1656 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
1657 HiddenServiceExcludeNodes as obsolete: they never worked properly,
1658 and nobody claims to be using them. Fixes bug 754. Bugfix on
1659 0.1.0.1-rc. Patch from Christian Wilms.
1660 - Fix a small alignment and memory-wasting bug on buffer chunks.
1663 o Minor bugfixes (controller):
1664 - When closing an application-side connection because its circuit
1665 is getting torn down, generate the stream event correctly.
1666 Bugfix on 0.1.2.x. Anonymous patch.
1669 - Remove all backward-compatibility code to support relays running
1670 versions of Tor so old that they no longer work at all on the
1674 Changes in version 0.2.0.30 - 2008-07-15
1676 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
1677 warnings (occasionally), but it can also cause the compiler to
1678 eliminate error-checking code. Suggested by Peter Gutmann.
1681 Changes in version 0.2.0.29-rc - 2008-07-08
1682 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
1683 hidden-service performance bugs, and fixes a bunch of smaller bugs.
1686 - If you have more than one bridge but don't know their keys,
1687 you would only launch a request for the descriptor of the first one
1688 on your list. (Tor considered launching requests for the others, but
1689 found that it already had a connection on the way for $0000...0000
1690 so it didn't open another.) Bugfix on 0.2.0.x.
1691 - If you have more than one bridge but don't know their keys, and the
1692 connection to one of the bridges failed, you would cancel all
1693 pending bridge connections. (After all, they all have the same
1694 digest.) Bugfix on 0.2.0.x.
1695 - When a hidden service was trying to establish an introduction point,
1696 and Tor had built circuits preemptively for such purposes, we
1697 were ignoring all the preemptive circuits and launching a new one
1698 instead. Bugfix on 0.2.0.14-alpha.
1699 - When a hidden service was trying to establish an introduction point,
1700 and Tor *did* manage to reuse one of the preemptively built
1701 circuits, it didn't correctly remember which one it used,
1702 so it asked for another one soon after, until there were no
1703 more preemptive circuits, at which point it launched one from
1704 scratch. Bugfix on 0.0.9.x.
1705 - Make directory servers include the X-Your-Address-Is: http header in
1706 their responses even for begin_dir conns. Now clients who only
1707 ever use begin_dir connections still have a way to learn their IP
1708 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
1711 - Fix a macro/CPP interaction that was confusing some compilers:
1712 some GCCs don't like #if/#endif pairs inside macro arguments.
1714 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
1715 Fixes bug 704; fix from Steven Murdoch.
1716 - When opening /dev/null in finish_daemonize(), do not pass the
1717 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
1718 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
1719 - Correctly detect transparent proxy support on Linux hosts that
1720 require in.h to be included before netfilter_ipv4.h. Patch
1722 - Disallow session resumption attempts during the renegotiation
1723 stage of the v2 handshake protocol. Clients should never be trying
1724 session resumption at this point, but apparently some did, in
1725 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
1726 found by Geoff Goodell.
1729 Changes in version 0.2.1.2-alpha - 2008-06-20
1730 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
1731 make it easier to set up your own private Tor network; fixes several
1732 big bugs with using more than one bridge relay; fixes a big bug with
1733 offering hidden services quickly after Tor starts; and uses a better
1734 API for reporting potential bootstrapping problems to the controller.
1737 - New TestingTorNetwork config option to allow adjustment of
1738 previously constant values that, while reasonable, could slow
1739 bootstrapping. Implements proposal 135. Patch from Karsten.
1742 - If you have more than one bridge but don't know their digests,
1743 you would only learn a request for the descriptor of the first one
1744 on your list. (Tor considered launching requests for the others, but
1745 found that it already had a connection on the way for $0000...0000
1746 so it didn't open another.) Bugfix on 0.2.0.x.
1747 - If you have more than one bridge but don't know their digests,
1748 and the connection to one of the bridges failed, you would cancel
1749 all pending bridge connections. (After all, they all have the
1750 same digest.) Bugfix on 0.2.0.x.
1751 - When establishing a hidden service, introduction points that
1752 originate from cannibalized circuits are completely ignored and not
1753 included in rendezvous service descriptors. This might be another
1754 reason for delay in making a hidden service available. Bugfix
1755 from long ago (0.0.9.x?)
1758 - Allow OpenSSL to use dynamic locks if it wants.
1759 - When building a consensus, do not include routers that are down.
1760 This will cut down 30% to 40% on consensus size. Implements
1762 - In directory authorities' approved-routers files, allow
1763 fingerprints with or without space.
1764 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
1765 controller can query our current bootstrap state in case it attaches
1766 partway through and wants to catch up.
1767 - Send an initial "Starting" bootstrap status event, so we have a
1768 state to start out in.
1771 - Asking for a conditional consensus at .../consensus/<fingerprints>
1772 would crash a dirserver if it did not already have a
1773 consensus. Bugfix on 0.2.1.1-alpha.
1774 - Clean up some macro/CPP interactions: some GCC versions don't like
1775 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
1778 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
1779 - Directory authorities shouldn't complain about bootstrapping
1780 problems just because they do a lot of reachability testing and
1781 some of the connection attempts fail.
1782 - Start sending "count" and "recommendation" key/value pairs in
1783 bootstrap problem status events, so the controller can hear about
1784 problems even before Tor decides they're worth reporting for sure.
1785 - If you're using bridges, generate "bootstrap problem" warnings
1786 as soon as you run out of working bridges, rather than waiting
1787 for ten failures -- which will never happen if you have less than
1789 - If we close our OR connection because there's been a circuit
1790 pending on it for too long, we were telling our bootstrap status
1791 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
1794 Changes in version 0.2.1.1-alpha - 2008-06-13
1795 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
1796 were making the Tor process bloat especially on Linux; makes our TLS
1797 handshake blend in better; sends "bootstrap phase" status events to
1798 the controller, so it can keep the user informed of progress (and
1799 problems) fetching directory information and establishing circuits;
1800 and adds a variety of smaller features.
1803 - More work on making our TLS handshake blend in: modify the list
1804 of ciphers advertised by OpenSSL in client mode to even more
1805 closely resemble a common web browser. We cheat a little so that
1806 we can advertise ciphers that the locally installed OpenSSL doesn't
1808 - Start sending "bootstrap phase" status events to the controller,
1809 so it can keep the user informed of progress fetching directory
1810 information and establishing circuits. Also inform the controller
1811 if we think we're stuck at a particular bootstrap phase. Implements
1813 - Resume using OpenSSL's RAND_poll() for better (and more portable)
1814 cross-platform entropy collection again. We used to use it, then
1815 stopped using it because of a bug that could crash systems that
1816 called RAND_poll when they had a lot of fds open. It looks like the
1817 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
1818 at startup, and to call RAND_poll() when we reseed later only if
1819 we have a non-buggy OpenSSL version.
1822 - When we choose to abandon a new entry guard because we think our
1823 older ones might be better, close any circuits pending on that
1824 new entry guard connection. This fix should make us recover much
1825 faster when our network is down and then comes back. Bugfix on
1826 0.1.2.8-beta; found by lodger.
1828 o Memory fixes and improvements:
1829 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
1830 to avoid unused RAM in buffer chunks and memory pools.
1831 - Speed up parsing and cut down on memory fragmentation by using
1832 stack-style allocations for parsing directory objects. Previously,
1833 this accounted for over 40% of allocations from within Tor's code
1834 on a typical directory cache.
1835 - Use a Bloom filter rather than a digest-based set to track which
1836 descriptors we need to keep around when we're cleaning out old
1837 router descriptors. This speeds up the computation significantly,
1838 and may reduce fragmentation.
1839 - Reduce the default smartlist size from 32 to 16; it turns out that
1840 most smartlists hold around 8-12 elements tops.
1841 - Make dumpstats() log the fullness and size of openssl-internal
1843 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
1844 patch to their OpenSSL, turn it on to save memory on servers. This
1845 patch will (with any luck) get included in a mainline distribution
1847 - Never use OpenSSL compression: it wastes RAM and CPU trying to
1848 compress cells, which are basically all encrypted, compressed,
1852 - Stop reloading the router list from disk for no reason when we
1853 run out of reachable directory mirrors. Once upon a time reloading
1854 it would set the 'is_running' flag back to 1 for them. It hasn't
1855 done that for a long time.
1856 - In very rare situations new hidden service descriptors were
1857 published earlier than 30 seconds after the last change to the
1858 service. (We currently think that a hidden service descriptor
1859 that's been stable for 30 seconds is worth publishing.)
1862 - Allow separate log levels to be configured for different logging
1863 domains. For example, this allows one to log all notices, warnings,
1864 or errors, plus all memory management messages of level debug or
1865 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
1866 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
1867 and stop using a warning that had become unfixably verbose under
1869 - New --hush command-line option similar to --quiet. While --quiet
1870 disables all logging to the console on startup, --hush limits the
1871 output to messages of warning and error severity.
1872 - Servers support a new URL scheme for consensus downloads that
1873 allows the client to specify which authorities are trusted.
1874 The server then only sends the consensus if the client will trust
1875 it. Otherwise a 404 error is sent back. Clients use this
1876 new scheme when the server supports it (meaning it's running
1877 0.2.1.1-alpha or later). Implements proposal 134.
1878 - New configure/torrc options (--enable-geoip-stats,
1879 DirRecordUsageByCountry) to record how many IPs we've served
1880 directory info to in each country code, how many status documents
1881 total we've sent to each country code, and what share of the total
1882 directory requests we should expect to see.
1883 - Use the TLS1 hostname extension to more closely resemble browser
1885 - Lots of new unit tests.
1886 - Add a macro to implement the common pattern of iterating through
1887 two parallel lists in lockstep.
1890 Changes in version 0.2.0.28-rc - 2008-06-13
1891 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
1892 performance bug, and fixes a bunch of smaller bugs.
1895 - Fix a bug where, when we were choosing the 'end stream reason' to
1896 put in our relay end cell that we send to the exit relay, Tor
1897 clients on Windows were sometimes sending the wrong 'reason'. The
1898 anonymity problem is that exit relays may be able to guess whether
1899 the client is running Windows, thus helping partition the anonymity
1900 set. Down the road we should stop sending reasons to exit relays,
1901 or otherwise prevent future versions of this bug.
1904 - While setting up a hidden service, some valid introduction circuits
1905 were overlooked and abandoned. This might be the reason for
1906 the long delay in making a hidden service available. Bugfix on
1910 - Update to the "June 9 2008" ip-to-country file.
1911 - Run 'make test' as part of 'make dist', so we stop releasing so
1912 many development snapshots that fail their unit tests.
1915 - When we're checking if we have enough dir info for each relay
1916 to begin establishing circuits, make sure that we actually have
1917 the descriptor listed in the consensus, not just any descriptor.
1919 - Bridge relays no longer print "xx=0" in their extrainfo document
1920 for every single country code in the geoip db. Bugfix on
1922 - Only warn when we fail to load the geoip file if we were planning to
1923 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
1924 - If we change our MaxAdvertisedBandwidth and then reload torrc,
1925 Tor won't realize it should publish a new relay descriptor. Fixes
1926 bug 688, reported by mfr. Bugfix on 0.1.2.x.
1927 - When we haven't had any application requests lately, don't bother
1928 logging that we have expired a bunch of descriptors. Bugfix
1930 - Make relay cells written on a connection count as non-padding when
1931 tracking how long a connection has been in use. Bugfix on
1932 0.2.0.1-alpha. Spotted by lodger.
1933 - Fix unit tests in 0.2.0.27-rc.
1934 - Fix compile on Windows.
1937 Changes in version 0.2.0.27-rc - 2008-06-03
1938 Tor 0.2.0.27-rc adds a few features we left out of the earlier
1939 release candidates. In particular, we now include an IP-to-country
1940 GeoIP database, so controllers can easily look up what country a
1941 given relay is in, and so bridge relays can give us some sanitized
1942 summaries about which countries are making use of bridges. (See proposal
1943 126-geoip-fetching.txt for details.)
1946 - Include an IP-to-country GeoIP file in the tarball, so bridge
1947 relays can report sanitized summaries of the usage they're seeing.
1950 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
1951 Robert Hogan. Fixes the first part of bug 681.
1952 - Make bridge authorities never serve extrainfo docs.
1953 - Add support to detect Libevent versions in the 1.4.x series
1955 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
1956 - Include a new contrib/tor-exit-notice.html file that exit relay
1957 operators can put on their website to help reduce abuse queries.
1960 - When tunneling an encrypted directory connection, and its first
1961 circuit fails, do not leave it unattached and ask the controller
1962 to deal. Fixes the second part of bug 681.
1963 - Make bridge authorities correctly expire old extrainfo documents
1967 Changes in version 0.2.0.26-rc - 2008-05-13
1968 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
1969 in Debian's OpenSSL packages. All users running any 0.2.0.x version
1970 should upgrade, whether they're running Debian or not.
1972 o Major security fixes:
1973 - Use new V3 directory authority keys on the tor26, gabelmoo, and
1974 moria1 V3 directory authorities. The old keys were generated with
1975 a vulnerable version of Debian's OpenSSL package, and must be
1976 considered compromised. Other authorities' keys were not generated
1977 with an affected version of OpenSSL.
1980 - List authority signatures as "unrecognized" based on DirServer
1981 lines, not on cert cache. Bugfix on 0.2.0.x.
1984 - Add a new V3AuthUseLegacyKey option to make it easier for
1985 authorities to change their identity keys if they have to.
1988 Changes in version 0.2.0.25-rc - 2008-04-23
1989 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
1992 - Remember to initialize threading before initializing logging.
1993 Otherwise, many BSD-family implementations will crash hard on
1994 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
1997 - Authorities correctly free policies on bad servers on
1998 exit. Fixes bug 672. Bugfix on 0.2.0.x.
2001 Changes in version 0.2.0.24-rc - 2008-04-22
2002 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
2003 v3 directory authority, makes relays with dynamic IP addresses and no
2004 DirPort notice more quickly when their IP address changes, fixes a few
2005 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
2007 o New directory authorities:
2008 - Take lefkada out of the list of v3 directory authorities, since
2009 it has been down for months.
2010 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
2014 - Detect address changes more quickly on non-directory mirror
2015 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
2017 o Minor features (security):
2018 - Reject requests for reverse-dns lookup of names that are in
2019 a private address space. Patch from lodger.
2020 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
2023 o Minor bugfixes (crashes):
2024 - Avoid a rare assert that can trigger when Tor doesn't have much
2025 directory information yet and it tries to fetch a v2 hidden
2026 service descriptor. Fixes bug 651, reported by nwf.
2027 - Initialize log mutex before initializing dmalloc. Otherwise,
2028 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
2029 - Use recursive pthread mutexes in order to avoid deadlock when
2030 logging debug-level messages to a controller. Bug spotted by nwf,
2031 bugfix on 0.2.0.16-alpha.
2033 o Minor bugfixes (resource management):
2034 - Keep address policies from leaking memory: start their refcount
2035 at 1, not 2. Bugfix on 0.2.0.16-alpha.
2036 - Free authority certificates on exit, so they don't look like memory
2037 leaks. Bugfix on 0.2.0.19-alpha.
2038 - Free static hashtables for policy maps and for TLS connections on
2039 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
2040 - Avoid allocating extra space when computing consensuses on 64-bit
2041 platforms. Bug spotted by aakova.
2043 o Minor bugfixes (misc):
2044 - Do not read the configuration file when we've only been told to
2045 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
2046 based on patch from Sebastian Hahn.
2047 - Exit relays that are used as a client can now reach themselves
2048 using the .exit notation, rather than just launching an infinite
2049 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
2050 - When attempting to open a logfile fails, tell us why.
2051 - Fix a dumb bug that was preventing us from knowing that we should
2052 preemptively build circuits to handle expected directory requests.
2053 Fixes bug 660. Bugfix on 0.1.2.x.
2054 - Warn less verbosely about clock skew from netinfo cells from
2055 untrusted sources. Fixes bug 663.
2056 - Make controller stream events for DNS requests more consistent,
2057 by adding "new stream" events for DNS requests, and removing
2058 spurious "stream closed" events" for cached reverse resolves.
2059 Patch from mwenge. Fixes bug 646.
2060 - Correctly notify one-hop connections when a circuit build has
2061 failed. Possible fix for bug 669. Found by lodger.
2064 Changes in version 0.2.0.23-rc - 2008-03-24
2065 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
2066 makes bootstrapping faster if the first directory mirror you contact
2067 is down. The bundles also include the new Vidalia 0.1.2 release.
2070 - When a tunneled directory request is made to a directory server
2071 that's down, notice after 30 seconds rather than 120 seconds. Also,
2072 fail any begindir streams that are pending on it, so they can
2073 retry elsewhere. This was causing multi-minute delays on bootstrap.
2076 Changes in version 0.2.0.22-rc - 2008-03-18
2077 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
2078 enables encrypted directory connections by default for non-relays, fixes
2079 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
2080 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
2083 - Enable encrypted directory connections by default for non-relays,
2084 so censor tools that block Tor directory connections based on their
2085 plaintext patterns will no longer work. This means Tor works in
2086 certain censored countries by default again.
2089 - Make sure servers always request certificates from clients during
2090 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
2091 - Do not enter a CPU-eating loop when a connection is closed in
2092 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
2093 diagnosed by lodger; bugfix on 0.2.0.20-rc.
2094 - Fix assertion failure that could occur when a blocked circuit
2095 became unblocked, and it had pending client DNS requests. Bugfix
2096 on 0.2.0.1-alpha. Fixes bug 632.
2098 o Minor bugfixes (on 0.1.2.x):
2099 - Generate "STATUS_SERVER" events rather than misspelled
2100 "STATUS_SEVER" events. Caught by mwenge.
2101 - When counting the number of bytes written on a TLS connection,
2102 look at the BIO actually used for writing to the network, not
2103 at the BIO used (sometimes) to buffer data for the network.
2104 Looking at different BIOs could result in write counts on the
2105 order of ULONG_MAX. Fixes bug 614.
2106 - On Windows, correctly detect errors when listing the contents of
2107 a directory. Fix from lodger.
2109 o Minor bugfixes (on 0.2.0.x):
2110 - Downgrade "sslv3 alert handshake failure" message to INFO.
2111 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
2112 left BandwidthRate and BandwidthBurst at the default, we would be
2113 silently limited by those defaults. Now raise them to match the
2114 RelayBandwidth* values.
2115 - Fix the SVK version detection logic to work correctly on a branch.
2116 - Make --enable-openbsd-malloc work correctly on Linux with alpha
2117 CPUs. Fixes bug 625.
2118 - Logging functions now check that the passed severity is sane.
2119 - Use proper log levels in the testsuite call of
2120 get_interface_address6().
2121 - When using a nonstandard malloc, do not use the platform values for
2122 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
2123 - Make the openbsd malloc code use 8k pages on alpha CPUs and
2125 - Detect mismatched page sizes when using --enable-openbsd-malloc.
2126 - Avoid double-marked-for-close warning when certain kinds of invalid
2127 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
2128 for bug 617. Bugfix on 0.2.0.1-alpha.
2129 - Make sure that the "NULL-means-reject *:*" convention is followed by
2130 all the policy manipulation functions, avoiding some possible crash
2131 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
2132 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
2133 actually works, and doesn't warn about every single reverse lookup.
2134 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
2137 - Only log guard node status when guard node status has changed.
2138 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
2139 make "INFO" 75% less verbose.
2142 Changes in version 0.2.0.21-rc - 2008-03-02
2143 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
2144 makes Tor work well with Vidalia again, fixes a rare assert bug,
2145 and fixes a pair of more minor bugs. The bundles also include Vidalia
2146 0.1.0 and Torbutton 1.1.16.
2149 - The control port should declare that it requires password auth
2150 when HashedControlSessionPassword is set too. Patch from Matt Edman;
2151 bugfix on 0.2.0.20-rc. Fixes bug 615.
2152 - Downgrade assert in connection_buckets_decrement() to a log message.
2153 This may help us solve bug 614, and in any case will make its
2154 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
2155 - We were sometimes miscounting the number of bytes read from the
2156 network, causing our rate limiting to not be followed exactly.
2157 Bugfix on 0.2.0.16-alpha. Reported by lodger.
2160 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
2161 OpenSSL versions should have been working fine. Diagnosis and patch
2162 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
2163 Bugfix on 0.2.0.20-rc.
2166 Changes in version 0.2.0.20-rc - 2008-02-24
2167 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
2168 makes more progress towards normalizing Tor's TLS handshake, makes
2169 hidden services work better again, helps relays bootstrap if they don't
2170 know their IP address, adds optional support for linking in openbsd's
2171 allocator or tcmalloc, allows really fast relays to scale past 15000
2172 sockets, and fixes a bunch of minor bugs reported by Veracode.
2175 - Enable the revised TLS handshake based on the one designed by
2176 Steven Murdoch in proposal 124, as revised in proposal 130. It
2177 includes version negotiation for OR connections as described in
2178 proposal 105. The new handshake is meant to be harder for censors
2179 to fingerprint, and it adds the ability to detect certain kinds of
2180 man-in-the-middle traffic analysis attacks. The version negotiation
2181 feature will allow us to improve Tor's link protocol more safely
2183 - Choose which bridge to use proportional to its advertised bandwidth,
2184 rather than uniformly at random. This should speed up Tor for
2185 bridge users. Also do this for people who set StrictEntryNodes.
2186 - When a TrackHostExits-chosen exit fails too many times in a row,
2187 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
2190 - Resolved problems with (re-)fetching hidden service descriptors.
2191 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
2193 - If we only ever used Tor for hidden service lookups or posts, we
2194 would stop building circuits and start refusing connections after
2195 24 hours, since we falsely believed that Tor was dormant. Reported
2196 by nwf; bugfix on 0.1.2.x.
2197 - Servers that don't know their own IP address should go to the
2198 authorities for their first directory fetch, even if their DirPort
2199 is off or if they don't know they're reachable yet. This will help
2200 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
2201 - When counting the number of open sockets, count not only the number
2202 of sockets we have received from the socket() call, but also
2203 the number we've gotten from accept() and socketpair(). This bug
2204 made us fail to count all sockets that we were using for incoming
2205 connections. Bugfix on 0.2.0.x.
2206 - Fix code used to find strings within buffers, when those strings
2207 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
2208 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
2209 - Add a new __HashedControlSessionPassword option for controllers
2210 to use for one-off session password hashes that shouldn't get
2211 saved to disk by SAVECONF --- Vidalia users were accumulating a
2212 pile of HashedControlPassword lines in their torrc files, one for
2213 each time they had restarted Tor and then clicked Save. Make Tor
2214 automatically convert "HashedControlPassword" to this new option but
2215 only when it's given on the command line. Partial fix for bug 586.
2217 o Minor features (performance):
2218 - Tune parameters for cell pool allocation to minimize amount of
2220 - Add OpenBSD malloc code from phk as an optional malloc
2221 replacement on Linux: some glibc libraries do very poorly
2222 with Tor's memory allocation patterns. Pass
2223 --enable-openbsd-malloc to get the replacement malloc code.
2224 - Add a --with-tcmalloc option to the configure script to link
2225 against tcmalloc (if present). Does not yet search for
2226 non-system include paths.
2227 - Stop imposing an arbitrary maximum on the number of file descriptors
2228 used for busy servers. Bug reported by Olaf Selke; patch from
2231 o Minor features (other):
2232 - When SafeLogging is disabled, log addresses along with all TLS
2234 - When building with --enable-gcc-warnings, check for whether Apple's
2235 warning "-Wshorten-64-to-32" is available.
2236 - Add a --passphrase-fd argument to the tor-gencert command for
2239 o Minor bugfixes (memory leaks and code problems):
2240 - We were leaking a file descriptor if Tor started with a zero-length
2241 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
2242 - Detect size overflow in zlib code. Reported by Justin Ferguson and
2244 - We were comparing the raw BridgePassword entry with a base64'ed
2245 version of it, when handling a "/tor/networkstatus-bridges"
2246 directory request. Now compare correctly. Noticed by Veracode.
2247 - Recover from bad tracked-since value in MTBF-history file.
2249 - Alter the code that tries to recover from unhandled write
2250 errors, to not try to flush onto a socket that's given us
2251 unhandled errors. Bugfix on 0.1.2.x.
2252 - Make Unix controlsockets work correctly on OpenBSD. Patch from
2253 tup. Bugfix on 0.2.0.3-alpha.
2255 o Minor bugfixes (other):
2256 - If we have an extra-info document for our server, always make
2257 it available on the control port, even if we haven't gotten
2258 a copy of it from an authority yet. Patch from mwenge.
2259 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
2260 - Directory mirrors no longer include a guess at the client's IP
2261 address if the connection appears to be coming from the same /24
2262 network; it was producing too many wrong guesses.
2263 - Make the new hidden service code respect the SafeLogging setting.
2264 Bugfix on 0.2.0.x. Patch from Karsten.
2265 - When starting as an authority, do not overwrite all certificates
2266 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
2267 - If we're trying to flush the last bytes on a connection (for
2268 example, when answering a directory request), reset the
2269 time-to-give-up timeout every time we manage to write something
2270 on the socket. Bugfix on 0.1.2.x.
2271 - Change the behavior of "getinfo status/good-server-descriptor"
2272 so it doesn't return failure when any authority disappears.
2273 - Even though the man page said that "TrackHostExits ." should
2274 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
2275 - Report TLS "zero return" case as a "clean close" and "IO error"
2276 as a "close". Stop calling closes "unexpected closes": existing
2277 Tors don't use SSL_close(), so having a connection close without
2278 the TLS shutdown handshake is hardly unexpected.
2279 - Send NAMESERVER_STATUS messages for a single failed nameserver
2282 o Code simplifications and refactoring:
2283 - Remove the tor_strpartition function: its logic was confused,
2284 and it was only used for one thing that could be implemented far
2288 Changes in version 0.2.0.19-alpha - 2008-02-09
2289 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
2290 handshake, makes path selection for relays more secure and IP address
2291 guessing more robust, and generally fixes a lot of bugs in preparation
2292 for calling the 0.2.0 branch stable.
2295 - Do not include recognizeable strings in the commonname part of
2296 Tor's x509 certificates.
2299 - If we're a relay, avoid picking ourselves as an introduction point,
2300 a rendezvous point, or as the final hop for internal circuits. Bug
2301 reported by taranis and lodger. Bugfix on 0.1.2.x.
2302 - Patch from "Andrew S. Lists" to catch when we contact a directory
2303 mirror at IP address X and he says we look like we're coming from
2304 IP address X. Bugfix on 0.1.2.x.
2306 o Minor features (security):
2307 - Be more paranoid about overwriting sensitive memory on free(),
2308 as a defensive programming tactic to ensure forward secrecy.
2310 o Minor features (directory authority):
2311 - Actually validate the options passed to AuthDirReject,
2312 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
2313 - Reject router descriptors with out-of-range bandwidthcapacity or
2314 bandwidthburst values.
2316 o Minor features (controller):
2317 - Reject controller commands over 1MB in length. This keeps rogue
2318 processes from running us out of memory.
2320 o Minor features (misc):
2321 - Give more descriptive well-formedness errors for out-of-range
2322 hidden service descriptor/protocol versions.
2323 - Make memory debugging information describe more about history
2324 of cell allocation, so we can help reduce our memory use.
2326 o Deprecated features (controller):
2327 - The status/version/num-versioning and status/version/num-concurring
2328 GETINFO options are no longer useful in the v3 directory protocol:
2329 treat them as deprecated, and warn when they're used.
2332 - When our consensus networkstatus has been expired for a while, stop
2333 being willing to build circuits using it. Fixes bug 401. Bugfix
2335 - Directory caches now fetch certificates from all authorities
2336 listed in a networkstatus consensus, even when they do not
2337 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
2338 - When connecting to a bridge without specifying its key, insert
2339 the connection into the identity-to-connection map as soon as
2340 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
2341 - Detect versions of OS X where malloc_good_size() is present in the
2342 library but never actually declared. Resolves bug 587. Bugfix
2344 - Stop incorrectly truncating zlib responses to directory authority
2345 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
2346 - Stop recommending that every server operator send mail to tor-ops.
2347 Resolves bug 597. Bugfix on 0.1.2.x.
2348 - Don't trigger an assert if we start a directory authority with a
2349 private IP address (like 127.0.0.1).
2350 - Avoid possible failures when generating a directory with routers
2351 with over-long versions strings, or too many flags set. Bugfix
2353 - If an attempt to launch a DNS resolve request over the control
2354 port fails because we have overrun the limit on the number of
2355 connections, tell the controller that the request has failed.
2356 - Avoid using too little bandwidth when our clock skips a few
2357 seconds. Bugfix on 0.1.2.x.
2358 - Fix shell error when warning about missing packages in configure
2359 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
2360 - Do not become confused when receiving a spurious VERSIONS-like
2361 cell from a confused v1 client. Bugfix on 0.2.0.x.
2362 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
2363 introduction points for a hidden service have failed. Patch from
2364 Karsten Loesing. Bugfix on 0.2.0.x.
2366 o Code simplifications and refactoring:
2367 - Remove some needless generality from cpuworker code, for improved
2369 - Stop overloading the circuit_t.onionskin field for both "onionskin
2370 from a CREATE cell that we are waiting for a cpuworker to be
2371 assigned" and "onionskin from an EXTEND cell that we are going to
2372 send to an OR as soon as we are connected". Might help with bug 600.
2373 - Add an in-place version of aes_crypt() so that we can avoid doing a
2374 needless memcpy() call on each cell payload.
2377 Changes in version 0.2.0.18-alpha - 2008-01-25
2378 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
2379 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
2380 that can warn or reject connections to ports generally associated with
2381 vulnerable-plaintext protocols.
2383 o New directory authorities:
2384 - Set up dannenberg (run by CCC) as the sixth v3 directory
2388 - Fix a major memory leak when attempting to use the v2 TLS
2389 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
2390 - We accidentally enabled the under-development v2 TLS handshake
2391 code, which was causing log entries like "TLS error while
2392 renegotiating handshake". Disable it again. Resolves bug 590.
2393 - We were computing the wrong Content-Length: header for directory
2394 responses that need to be compressed on the fly, causing clients
2395 asking for those items to always fail. Bugfix on 0.2.0.x; partially
2399 - Avoid going directly to the directory authorities even if you're a
2400 relay, if you haven't found yourself reachable yet or if you've
2401 decided not to advertise your dirport yet. Addresses bug 556.
2402 - If we've gone 12 hours since our last bandwidth check, and we
2403 estimate we have less than 50KB bandwidth capacity but we could
2404 handle more, do another bandwidth test.
2405 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
2406 Tor can warn and/or refuse connections to ports commonly used with
2407 vulnerable-plaintext protocols. Currently we warn on ports 23,
2408 109, 110, and 143, but we don't reject any.
2411 - When we setconf ClientOnly to 1, close any current OR and Dir
2412 listeners. Reported by mwenge.
2413 - When we get a consensus that's been signed by more people than
2414 we expect, don't log about it; it's not a big deal. Reported
2418 - Don't answer "/tor/networkstatus-bridges" directory requests if
2419 the request isn't encrypted.
2420 - Make "ClientOnly 1" config option disable directory ports too.
2421 - Patches from Karsten Loesing to make v2 hidden services more
2422 robust: work even when there aren't enough HSDir relays available;
2423 retry when a v2 rend desc fetch fails; but don't retry if we
2424 already have a usable v0 rend desc.
2427 Changes in version 0.2.0.17-alpha - 2008-01-17
2428 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
2431 - Make the tor-gencert man page get included correctly in the tarball.
2434 Changes in version 0.2.0.16-alpha - 2008-01-17
2435 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
2436 Loesing, and generally cleans up a lot of features and minor bugs.
2438 o New directory authorities:
2439 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
2442 o Major performance improvements:
2443 - Switch our old ring buffer implementation for one more like that
2444 used by free Unix kernels. The wasted space in a buffer with 1mb
2445 of data will now be more like 8k than 1mb. The new implementation
2446 also avoids realloc();realloc(); patterns that can contribute to
2447 memory fragmentation.
2450 - Configuration files now accept C-style strings as values. This
2451 helps encode characters not allowed in the current configuration
2452 file format, such as newline or #. Addresses bug 557.
2453 - Although we fixed bug 539 (where servers would send HTTP status 503
2454 responses _and_ send a body too), there are still servers out
2455 there that haven't upgraded. Therefore, make clients parse such
2456 bodies when they receive them.
2457 - When we're not serving v2 directory information, there is no reason
2458 to actually keep any around. Remove the obsolete files and directory
2459 on startup if they are very old and we aren't going to serve them.
2461 o Minor performance improvements:
2462 - Reference-count and share copies of address policy entries; only 5%
2463 of them were actually distinct.
2464 - Never walk through the list of logs if we know that no log is
2465 interested in a given message.
2468 - When an authority has not signed a consensus, do not try to
2469 download a nonexistent "certificate with key 00000000". Bugfix
2470 on 0.2.0.x. Fixes bug 569.
2471 - Fix a rare assert error when we're closing one of our threads:
2472 use a mutex to protect the list of logs, so we never write to the
2473 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
2474 bug 575, which is kind of the revenge of bug 222.
2475 - Patch from Karsten Loesing to complain less at both the client
2476 and the relay when a relay used to have the HSDir flag but doesn't
2477 anymore, and we try to upload a hidden service descriptor.
2478 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
2480 - Do not try to download missing certificates until we have tried
2481 to check our fallback consensus. Fixes bug 583.
2482 - Make bridges round reported GeoIP stats info up to the nearest
2483 estimate, not down. Now we can distinguish between "0 people from
2484 this country" and "1 person from this country".
2485 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
2486 - Avoid possible segfault if key generation fails in
2487 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
2488 - Avoid segfault in the case where a badly behaved v2 versioning
2489 directory sends a signed networkstatus with missing client-versions.
2491 - Avoid segfaults on certain complex invocations of
2492 router_get_by_hexdigest(). Bugfix on 0.1.2.
2493 - Correct bad index on array access in parse_http_time(). Bugfix
2495 - Fix possible bug in vote generation when server versions are present
2496 but client versions are not.
2497 - Fix rare bug on REDIRECTSTREAM control command when called with no
2498 port set: it could erroneously report an error when none had
2500 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
2501 compressing large objects and find ourselves with more than 4k
2502 left over. Bugfix on 0.2.0.
2503 - Fix a small memory leak when setting up a hidden service.
2504 - Fix a few memory leaks that could in theory happen under bizarre
2506 - Fix an assert if we post a general-purpose descriptor via the
2507 control port but that descriptor isn't mentioned in our current
2508 network consensus. Bug reported by Jon McLachlan; bugfix on
2511 o Minor features (controller):
2512 - Get NS events working again. Patch from tup.
2513 - The GETCONF command now escapes and quotes configuration values
2514 that don't otherwise fit into the torrc file.
2515 - The SETCONF command now handles quoted values correctly.
2517 o Minor features (directory authorities):
2518 - New configuration options to override default maximum number of
2519 servers allowed on a single IP address. This is important for
2520 running a test network on a single host.
2521 - Actually implement the -s option to tor-gencert.
2522 - Add a manual page for tor-gencert.
2524 o Minor features (bridges):
2525 - Bridge authorities no longer serve bridge descriptors over
2526 unencrypted connections.
2528 o Minor features (other):
2529 - Add hidden services and DNSPorts to the list of things that make
2530 Tor accept that it has running ports. Change starting Tor with no
2531 ports from a fatal error to a warning; we might change it back if
2532 this turns out to confuse anybody. Fixes bug 579.
2535 Changes in version 0.1.2.19 - 2008-01-17
2536 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
2537 exit policy a little bit more conservative so it's safer to run an
2538 exit relay on a home system, and fixes a variety of smaller issues.
2541 - Exit policies now reject connections that are addressed to a
2542 relay's public (external) IP address too, unless
2543 ExitPolicyRejectPrivate is turned off. We do this because too
2544 many relays are running nearby to services that trust them based
2548 - When the clock jumps forward a lot, do not allow the bandwidth
2549 buckets to become negative. Fixes bug 544.
2550 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
2551 on every successful resolve. Reported by Mike Perry.
2552 - Purge old entries from the "rephist" database and the hidden
2553 service descriptor database even when DirPort is zero.
2554 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
2555 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
2556 crashing or mis-answering these requests.
2557 - When we decide to send a 503 response to a request for servers, do
2558 not then also send the server descriptors: this defeats the whole
2559 purpose. Fixes bug 539.
2562 - Changing the ExitPolicyRejectPrivate setting should cause us to
2563 rebuild our server descriptor.
2564 - Fix handling of hex nicknames when answering controller requests for
2565 networkstatus by name, or when deciding whether to warn about
2566 unknown routers in a config option. (Patch from mwenge.)
2567 - Fix a couple of hard-to-trigger autoconf problems that could result
2568 in really weird results on platforms whose sys/types.h files define
2569 nonstandard integer types.
2570 - Don't try to create the datadir when running --verify-config or
2571 --hash-password. Resolves bug 540.
2572 - If we were having problems getting a particular descriptor from the
2573 directory caches, and then we learned about a new descriptor for
2574 that router, we weren't resetting our failure count. Reported
2576 - Although we fixed bug 539 (where servers would send HTTP status 503
2577 responses _and_ send a body too), there are still servers out there
2578 that haven't upgraded. Therefore, make clients parse such bodies
2579 when they receive them.
2580 - Run correctly on systems where rlim_t is larger than unsigned long.
2581 This includes some 64-bit systems.
2582 - Run correctly on platforms (like some versions of OS X 10.5) where
2583 the real limit for number of open files is OPEN_FILES, not rlim_max
2584 from getrlimit(RLIMIT_NOFILES).
2585 - Avoid a spurious free on base64 failure.
2586 - Avoid segfaults on certain complex invocations of
2587 router_get_by_hexdigest().
2588 - Fix rare bug on REDIRECTSTREAM control command when called with no
2589 port set: it could erroneously report an error when none had
2593 Changes in version 0.2.0.15-alpha - 2007-12-25
2594 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
2595 features added in 0.2.0.13-alpha.
2598 - Fix several remotely triggerable asserts based on DirPort requests
2599 for a v2 or v3 networkstatus object before we were prepared. This
2600 was particularly bad for 0.2.0.13 and later bridge relays, who
2601 would never have a v2 networkstatus and would thus always crash
2602 when used. Bugfixes on 0.2.0.x.
2603 - Estimate the v3 networkstatus size more accurately, rather than
2604 estimating it at zero bytes and giving it artificially high priority
2605 compared to other directory requests. Bugfix on 0.2.0.x.
2608 - Fix configure.in logic for cross-compilation.
2609 - When we load a bridge descriptor from the cache, and it was
2610 previously unreachable, mark it as retriable so we won't just
2611 ignore it. Also, try fetching a new copy immediately. Bugfixes
2613 - The bridge GeoIP stats were counting other relays, for example
2614 self-reachability and authority-reachability tests.
2617 - Support compilation to target iPhone; patch from cjacker huang.
2618 To build for iPhone, pass the --enable-iphone option to configure.
2621 Changes in version 0.2.0.14-alpha - 2007-12-23
2623 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
2624 without a datadirectory from a previous Tor install. Reported
2626 - Fix a crash when we fetch a descriptor that turns out to be
2627 unexpected (it used to be in our networkstatus when we started
2628 fetching it, but it isn't in our current networkstatus), and we
2629 aren't using bridges. Bugfix on 0.2.0.x.
2630 - Fix a crash when accessing hidden services: it would work the first
2631 time you use a given introduction point for your service, but
2632 on subsequent requests we'd be using garbage memory. Fixed by
2633 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
2634 - Fix a crash when we load a bridge descriptor from disk but we don't
2635 currently have a Bridge line for it in our torrc. Bugfix on
2639 - If bridge authorities set BridgePassword, they will serve a
2640 snapshot of known bridge routerstatuses from their DirPort to
2641 anybody who knows that password. Unset by default.
2644 - Make the unit tests build again.
2645 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
2646 - Make PublishServerDescriptor default to 1, so the default doesn't
2647 have to change as we invent new directory protocol versions.
2648 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
2649 be included unless sys/time.h is already included. Fixes
2650 bug 553. Bugfix on 0.2.0.x.
2651 - If we receive a general-purpose descriptor and then receive an
2652 identical bridge-purpose descriptor soon after, don't discard
2653 the next one as a duplicate.
2656 - If BridgeRelay is set to 1, then the default for
2657 PublishServerDescriptor is now "bridge" rather than "v2,v3".
2658 - If the user sets RelayBandwidthRate but doesn't set
2659 RelayBandwidthBurst, then make them equal rather than erroring out.
2662 Changes in version 0.2.0.13-alpha - 2007-12-21
2663 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
2664 Goodell, fixes many more bugs, and adds a lot of infrastructure for
2667 o New directory authorities:
2668 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
2672 - Only update guard status (usable / not usable) once we have
2673 enough directory information. This was causing us to always pick
2674 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
2675 causing us to discard all our guards on startup if we hadn't been
2676 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
2677 - Purge old entries from the "rephist" database and the hidden
2678 service descriptor databases even when DirPort is zero. Bugfix
2680 - We were ignoring our RelayBandwidthRate for the first 30 seconds
2681 after opening a circuit -- even a relayed circuit. Bugfix on
2683 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
2684 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
2685 crashing or mis-answering these types of requests.
2686 - Relays were publishing their server descriptor to v1 and v2
2687 directory authorities, but they didn't try publishing to v3-only
2688 authorities. Fix this; and also stop publishing to v1 authorities.
2690 - When we were reading router descriptors from cache, we were ignoring
2691 the annotations -- so for example we were reading in bridge-purpose
2692 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
2693 - When we decided to send a 503 response to a request for servers, we
2694 were then also sending the server descriptors: this defeats the
2695 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
2698 - Bridge relays now behave like clients with respect to time
2699 intervals for downloading new consensus documents -- otherwise they
2700 stand out. Bridge users now wait until the end of the interval,
2701 so their bridge relay will be sure to have a new consensus document.
2702 - Three new config options (AlternateDirAuthority,
2703 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
2704 user selectively replace the default directory authorities by type,
2705 rather than the all-or-nothing replacement that DirServer offers.
2706 - Tor can now be configured to read a GeoIP file from disk in one
2707 of two formats. This can be used by controllers to map IP addresses
2708 to countries. Eventually, it may support exit-by-country.
2709 - When possible, bridge relays remember which countries users
2710 are coming from, and report aggregate information in their
2711 extra-info documents, so that the bridge authorities can learn
2712 where Tor is blocked.
2713 - Bridge directory authorities now do reachability testing on the
2714 bridges they know. They provide router status summaries to the
2715 controller via "getinfo ns/purpose/bridge", and also dump summaries
2716 to a file periodically.
2717 - Stop fetching directory info so aggressively if your DirPort is
2718 on but your ORPort is off; stop fetching v2 dir info entirely.
2719 You can override these choices with the new FetchDirInfoEarly
2723 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
2724 consensus documents when there are too many relays at a single
2725 IP address. Now clear it in v2 network status documents too, and
2726 also clear it in routerinfo_t when the relay is no longer listed
2727 in the relevant networkstatus document.
2728 - Don't crash if we get an unexpected value for the
2729 PublishServerDescriptor config option. Reported by Matt Edman;
2730 bugfix on 0.2.0.9-alpha.
2731 - Our new v2 hidden service descriptor format allows descriptors
2732 that have no introduction points. But Tor crashed when we tried
2733 to build a descriptor with no intro points (and it would have
2734 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
2736 - Fix building with dmalloc 5.5.2 with glibc.
2737 - Reject uploaded descriptors and extrainfo documents if they're
2738 huge. Otherwise we'll cache them all over the network and it'll
2739 clog everything up. Reported by Aljosha Judmayer.
2740 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
2741 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
2742 - When the DANGEROUS_VERSION controller status event told us we're
2743 running an obsolete version, it used the string "OLD" to describe
2744 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
2745 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
2746 - If we can't expand our list of entry guards (e.g. because we're
2747 using bridges or we have StrictEntryNodes set), don't mark relays
2748 down when they fail a directory request. Otherwise we're too quick
2749 to mark all our entry points down. Bugfix on 0.1.2.x.
2750 - Fix handling of hex nicknames when answering controller requests for
2751 networkstatus by name, or when deciding whether to warn about unknown
2752 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
2753 - Fix a couple of hard-to-trigger autoconf problems that could result
2754 in really weird results on platforms whose sys/types.h files define
2755 nonstandard integer types. Bugfix on 0.1.2.x.
2756 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
2757 - Don't crash on name lookup when we have no current consensus. Fixes
2758 bug 538; bugfix on 0.2.0.x.
2759 - Only Tors that want to mirror the v2 directory info should
2760 create the "cached-status" directory in their datadir. (All Tors
2761 used to create it.) Bugfix on 0.2.0.9-alpha.
2762 - Directory authorities should only automatically download Extra Info
2763 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
2766 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
2767 consumers. (We already do this on HUP.)
2768 - Authorities and caches fetch the v2 networkstatus documents
2769 less often, now that v3 is encouraged.
2770 - Add a new config option BridgeRelay that specifies you want to
2771 be a bridge relay. Right now the only difference is that it makes
2772 you answer begin_dir requests, and it makes you cache dir info,
2773 even if your DirPort isn't on.
2774 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
2775 ask about source, timestamp of arrival, purpose, etc. We need
2776 something like this to help Vidalia not do GeoIP lookups on bridge
2778 - Allow multiple HashedControlPassword config lines, to support
2779 multiple controller passwords.
2780 - Authorities now decide whether they're authoritative for a given
2781 router based on the router's purpose.
2782 - New config options AuthDirBadDir and AuthDirListBadDirs for
2783 authorities to mark certain relays as "bad directories" in the
2784 networkstatus documents. Also supports the "!baddir" directive in
2785 the approved-routers file.
2788 Changes in version 0.2.0.12-alpha - 2007-11-16
2789 This twelfth development snapshot fixes some more build problems as
2790 well as a few minor bugs.
2793 - Make it build on OpenBSD again. Patch from tup.
2794 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
2795 package-building for Red Hat, OS X, etc.
2797 o Minor bugfixes (on 0.1.2.x):
2798 - Changing the ExitPolicyRejectPrivate setting should cause us to
2799 rebuild our server descriptor.
2801 o Minor bugfixes (on 0.2.0.x):
2802 - When we're lacking a consensus, don't try to perform rendezvous
2803 operations. Reported by Karsten Loesing.
2804 - Fix a small memory leak whenever we decide against using a
2805 newly picked entry guard. Reported by Mike Perry.
2806 - When authorities detected more than two relays running on the same
2807 IP address, they were clearing all the status flags but forgetting
2808 to clear the "hsdir" flag. So clients were being told that a
2809 given relay was the right choice for a v2 hsdir lookup, yet they
2810 never had its descriptor because it was marked as 'not running'
2812 - If we're trying to fetch a bridge descriptor and there's no way
2813 the bridge authority could help us (for example, we don't know
2814 a digest, or there is no bridge authority), don't be so eager to
2815 fall back to asking the bridge authority.
2816 - If we're using bridges or have strictentrynodes set, and our
2817 chosen exit is in the same family as all our bridges/entry guards,
2818 then be flexible about families.
2821 - When we negotiate a v2 link-layer connection (not yet implemented),
2822 accept RELAY_EARLY cells and turn them into RELAY cells if we've
2823 negotiated a v1 connection for their next step. Initial code for
2827 Changes in version 0.2.0.11-alpha - 2007-11-12
2828 This eleventh development snapshot fixes some build problems with
2829 the previous snapshot. It also includes a more secure-by-default exit
2830 policy for relays, fixes an enormous memory leak for exit relays, and
2831 fixes another bug where servers were falling out of the directory list.
2834 - Exit policies now reject connections that are addressed to a
2835 relay's public (external) IP address too, unless
2836 ExitPolicyRejectPrivate is turned off. We do this because too
2837 many relays are running nearby to services that trust them based
2838 on network address. Bugfix on 0.1.2.x.
2841 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
2842 on every successful resolve. Reported by Mike Perry; bugfix
2844 - On authorities, never downgrade to old router descriptors simply
2845 because they're listed in the consensus. This created a catch-22
2846 where we wouldn't list a new descriptor because there was an
2847 old one in the consensus, and we couldn't get the new one in the
2848 consensus because we wouldn't list it. Possible fix for bug 548.
2849 Also, this might cause bug 543 to appear on authorities; if so,
2850 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
2852 o Packaging fixes on 0.2.0.10-alpha:
2853 - We were including instructions about what to do with the
2854 src/config/fallback-consensus file, but we weren't actually
2855 including it in the tarball. Disable all of that for now.
2858 - Allow people to say PreferTunnelledDirConns rather than
2859 PreferTunneledDirConns, for those alternate-spellers out there.
2862 - Don't reevaluate all the information from our consensus document
2863 just because we've downloaded a v2 networkstatus that we intend
2864 to cache. Fixes bug 545; bugfix on 0.2.0.x.
2867 Changes in version 0.2.0.10-alpha - 2007-11-10
2868 This tenth development snapshot adds a third v3 directory authority
2869 run by Mike Perry, adds most of Karsten Loesing's new hidden service
2870 descriptor format, fixes a bad crash bug and new bridge bugs introduced
2871 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
2872 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
2873 addresses many more minor issues.
2875 o New directory authorities:
2876 - Set up ides (run by Mike Perry) as the third v3 directory authority.
2879 - Allow tunnelled directory connections to ask for an encrypted
2880 "begin_dir" connection or an anonymized "uses a full Tor circuit"
2881 connection independently. Now we can make anonymized begin_dir
2882 connections for (e.g.) more secure hidden service posting and
2884 - More progress on proposal 114: code from Karsten Loesing to
2885 implement new hidden service descriptor format.
2886 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
2887 accommodate the growing number of servers that use the default
2888 and are reaching it.
2889 - Directory authorities use a new formula for selecting which nodes
2890 to advertise as Guards: they must be in the top 7/8 in terms of
2891 how long we have known about them, and above the median of those
2892 nodes in terms of weighted fractional uptime.
2893 - Make "not enough dir info yet" warnings describe *why* Tor feels
2894 it doesn't have enough directory info yet.
2897 - Stop servers from crashing if they set a Family option (or
2898 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
2900 - Make bridge users work again -- the move to v3 directories in
2901 0.2.0.9-alpha had introduced a number of bugs that made bridges
2902 no longer work for clients.
2903 - When the clock jumps forward a lot, do not allow the bandwidth
2904 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
2906 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
2907 - When the consensus lists a router descriptor that we previously were
2908 mirroring, but that we considered non-canonical, reload the
2909 descriptor as canonical. This fixes bug 543 where Tor servers
2910 would start complaining after a few days that they don't have
2911 enough directory information to build a circuit.
2912 - Consider replacing the current consensus when certificates arrive
2913 that make the pending consensus valid. Previously, we were only
2914 considering replacement when the new certs _didn't_ help.
2915 - Fix an assert error on startup if we didn't already have the
2916 consensus and certs cached in our datadirectory: we were caching
2917 the consensus in consensus_waiting_for_certs but then free'ing it
2919 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
2920 Request) if we need more v3 certs but we've already got pending
2921 requests for all of them.
2922 - Correctly back off from failing certificate downloads. Fixes
2924 - Authorities don't vote on the Running flag if they have been running
2925 for less than 30 minutes themselves. Fixes bug 547, where a newly
2926 started authority would vote that everyone was down.
2929 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
2930 it, it had no AES, and it hasn't seen any security patches since
2934 - Clients now hold circuitless TLS connections open for 1.5 times
2935 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
2936 rebuild a new circuit over them within that timeframe. Previously,
2937 they held them open only for KeepalivePeriod (5 minutes).
2938 - Use "If-Modified-Since" to avoid retrieving consensus
2939 networkstatuses that we already have.
2940 - When we have no consensus, check FallbackNetworkstatusFile (defaults
2941 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
2942 we start knowing some directory caches.
2943 - When we receive a consensus from the future, warn about skew.
2944 - Improve skew reporting: try to give the user a better log message
2945 about how skewed they are, and how much this matters.
2946 - When we have a certificate for an authority, believe that
2947 certificate's claims about the authority's IP address.
2948 - New --quiet command-line option to suppress the default console log.
2949 Good in combination with --hash-password.
2950 - Authorities send back an X-Descriptor-Not-New header in response to
2951 an accepted-but-discarded descriptor upload. Partially implements
2953 - Make the log message for "tls error. breaking." more useful.
2954 - Better log messages about certificate downloads, to attempt to
2955 track down the second incarnation of bug 546.
2957 o Minor features (bridges):
2958 - If bridge users set UpdateBridgesFromAuthority, but the digest
2959 they ask for is a 404 from the bridge authority, they now fall
2960 back to trying the bridge directly.
2961 - Bridges now use begin_dir to publish their server descriptor to
2962 the bridge authority, even when they haven't set TunnelDirConns.
2964 o Minor features (controller):
2965 - When reporting clock skew, and we know that the clock is _at least
2966 as skewed_ as some value, but we don't know the actual value,
2967 report the value as a "minimum skew."
2970 - Update linux-tor-prio.sh script to allow QoS based on the uid of
2971 the Tor process. Patch from Marco Bonetti with tweaks from Mike
2975 - Refuse to start if both ORPort and UseBridges are set. Bugfix
2976 on 0.2.0.x, suggested by Matt Edman.
2977 - Don't stop fetching descriptors when FetchUselessDescriptors is
2978 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
2979 reported by tup and ioerror.
2980 - Better log message on vote from unknown authority.
2981 - Don't log "Launching 0 request for 0 router" message.
2983 o Minor bugfixes (memory leaks):
2984 - Stop leaking memory every time we parse a v3 certificate. Bugfix
2986 - Stop leaking memory every time we load a v3 certificate. Bugfix
2987 on 0.2.0.1-alpha. Fixes bug 536.
2988 - Stop leaking a cached networkstatus on exit. Bugfix on
2990 - Stop leaking voter information every time we free a consensus.
2991 Bugfix on 0.2.0.3-alpha.
2992 - Stop leaking signed data every time we check a voter signature.
2993 Bugfix on 0.2.0.3-alpha.
2994 - Stop leaking a signature every time we fail to parse a consensus or
2995 a vote. Bugfix on 0.2.0.3-alpha.
2996 - Stop leaking v2_download_status_map on shutdown. Bugfix on
2998 - Stop leaking conn->nickname every time we make a connection to a
2999 Tor relay without knowing its expected identity digest (e.g. when
3000 using bridges). Bugfix on 0.2.0.3-alpha.
3002 - Minor bugfixes (portability):
3003 - Run correctly on platforms where rlim_t is larger than unsigned
3004 long, and/or where the real limit for number of open files is
3005 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
3006 particular, these may be needed for OS X 10.5.
3009 Changes in version 0.1.2.18 - 2007-10-28
3010 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
3011 hidden service introduction that were causing huge delays, and a big
3012 bug that was causing some servers to disappear from the network status
3013 lists for a few hours each day.
3015 o Major bugfixes (crashes):
3016 - If a connection is shut down abruptly because of something that
3017 happened inside connection_flushed_some(), do not call
3018 connection_finished_flushing(). Should fix bug 451:
3019 "connection_stop_writing: Assertion conn->write_event failed"
3020 Bugfix on 0.1.2.7-alpha.
3021 - Fix possible segfaults in functions called from
3022 rend_process_relay_cell().
3024 o Major bugfixes (hidden services):
3025 - Hidden services were choosing introduction points uniquely by
3026 hexdigest, but when constructing the hidden service descriptor
3027 they merely wrote the (potentially ambiguous) nickname.
3028 - Clients now use the v2 intro format for hidden service
3029 connections: they specify their chosen rendezvous point by identity
3030 digest rather than by (potentially ambiguous) nickname. These
3031 changes could speed up hidden service connections dramatically.
3033 o Major bugfixes (other):
3034 - Stop publishing a new server descriptor just because we get a
3035 HUP signal. This led (in a roundabout way) to some servers getting
3036 dropped from the networkstatus lists for a few hours each day.
3037 - When looking for a circuit to cannibalize, consider family as well
3038 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
3039 circuit cannibalization).
3040 - When a router wasn't listed in a new networkstatus, we were leaving
3041 the flags for that router alone -- meaning it remained Named,
3042 Running, etc -- even though absence from the networkstatus means
3043 that it shouldn't be considered to exist at all anymore. Now we
3044 clear all the flags for routers that fall out of the networkstatus
3045 consensus. Fixes bug 529.
3048 - Don't try to access (or alter) the state file when running
3049 --list-fingerprint or --verify-config or --hash-password. Resolves
3051 - When generating information telling us how to extend to a given
3052 router, do not try to include the nickname if it is
3053 absent. Resolves bug 467.
3054 - Fix a user-triggerable segfault in expand_filename(). (There isn't
3055 a way to trigger this remotely.)
3056 - When sending a status event to the controller telling it that an
3057 OR address is reachable, set the port correctly. (Previously we
3058 were reporting the dir port.)
3059 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
3060 command. Bugfix on 0.1.2.17.
3061 - When loading bandwidth history, do not believe any information in
3062 the future. Fixes bug 434.
3063 - When loading entry guard information, do not believe any information
3065 - When we have our clock set far in the future and generate an
3066 onion key, then re-set our clock to be correct, we should not stop
3067 the onion key from getting rotated.
3068 - On some platforms, accept() can return a broken address. Detect
3069 this more quietly, and deal accordingly. Fixes bug 483.
3070 - It's not actually an error to find a non-pending entry in the DNS
3071 cache when canceling a pending resolve. Don't log unless stuff
3072 is fishy. Resolves bug 463.
3073 - Don't reset trusted dir server list when we set a configuration
3074 option. Patch from Robert Hogan.
3075 - Don't try to create the datadir when running --verify-config or
3076 --hash-password. Resolves bug 540.
3079 Changes in version 0.2.0.9-alpha - 2007-10-24
3080 This ninth development snapshot switches clients to the new v3 directory
3081 system; allows servers to be listed in the network status even when they
3082 have the same nickname as a registered server; and fixes many other
3083 bugs including a big one that was causing some servers to disappear
3084 from the network status lists for a few hours each day.
3086 o Major features (directory system):
3087 - Clients now download v3 consensus networkstatus documents instead
3088 of v2 networkstatus documents. Clients and caches now base their
3089 opinions about routers on these consensus documents. Clients only
3090 download router descriptors listed in the consensus.
3091 - Authorities now list servers who have the same nickname as
3092 a different named server, but list them with a new flag,
3093 "Unnamed". Now we can list servers that happen to pick the same
3094 nickname as a server that registered two years ago and then
3095 disappeared. Partially implements proposal 122.
3096 - If the consensus lists a router as "Unnamed", the name is assigned
3097 to a different router: do not identify the router by that name.
3098 Partially implements proposal 122.
3099 - Authorities can now come to a consensus on which method to use to
3100 compute the consensus. This gives us forward compatibility.
3103 - Stop publishing a new server descriptor just because we HUP or
3104 when we find our DirPort to be reachable but won't actually publish
3105 it. New descriptors without any real changes are dropped by the
3106 authorities, and can screw up our "publish every 18 hours" schedule.
3108 - When a router wasn't listed in a new networkstatus, we were leaving
3109 the flags for that router alone -- meaning it remained Named,
3110 Running, etc -- even though absence from the networkstatus means
3111 that it shouldn't be considered to exist at all anymore. Now we
3112 clear all the flags for routers that fall out of the networkstatus
3113 consensus. Fixes bug 529; bugfix on 0.1.2.x.
3114 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
3115 extrainfo documents and then discard them immediately for not
3116 matching the latest router. Bugfix on 0.2.0.1-alpha.
3118 o Minor features (v3 directory protocol):
3119 - Allow tor-gencert to generate a new certificate without replacing
3121 - Allow certificates to include an address.
3122 - When we change our directory-cache settings, reschedule all voting
3123 and download operations.
3124 - Reattempt certificate downloads immediately on failure, as long as
3125 we haven't failed a threshold number of times yet.
3126 - Delay retrying consensus downloads while we're downloading
3127 certificates to verify the one we just got. Also, count getting a
3128 consensus that we already have (or one that isn't valid) as a failure,
3129 and count failing to get the certificates after 20 minutes as a
3131 - Build circuits and download descriptors even if our consensus is a
3132 little expired. (This feature will go away once authorities are
3135 o Minor features (router descriptor cache):
3136 - If we find a cached-routers file that's been sitting around for more
3137 than 28 days unmodified, then most likely it's a leftover from
3138 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
3140 - When we (as a cache) download a descriptor because it was listed
3141 in a consensus, remember when the consensus was supposed to expire,
3142 and don't expire the descriptor until then.
3144 o Minor features (performance):
3145 - Call routerlist_remove_old_routers() much less often. This should
3146 speed startup, especially on directory caches.
3147 - Don't try to launch new descriptor downloads quite so often when we
3148 already have enough directory information to build circuits.
3149 - Base64 decoding was actually showing up on our profile when parsing
3150 the initial descriptor file; switch to an in-process all-at-once
3151 implementation that's about 3.5x times faster than calling out to
3154 o Minor features (compilation):
3155 - Detect non-ASCII platforms (if any still exist) and refuse to
3156 build there: some of our code assumes that 'A' is 65 and so on.
3158 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
3159 - Make the "next period" votes into "current period" votes immediately
3160 after publishing the consensus; avoid a heisenbug that made them
3161 stick around indefinitely.
3162 - When we discard a vote as a duplicate, do not report this as
3164 - Treat missing v3 keys or certificates as an error when running as a
3165 v3 directory authority.
3166 - When we're configured to be a v3 authority, but we're only listed
3167 as a non-v3 authority in our DirServer line for ourself, correct
3169 - If an authority doesn't have a qualified hostname, just put
3170 its address in the vote. This fixes the problem where we referred to
3171 "moria on moria:9031."
3172 - Distinguish between detached signatures for the wrong period, and
3173 detached signatures for a divergent vote.
3174 - Fix a small memory leak when computing a consensus.
3175 - When there's no concensus, we were forming a vote every 30
3176 minutes, but writing the "valid-after" line in our vote based
3177 on our configured V3AuthVotingInterval: so unless the intervals
3178 matched up, we immediately rejected our own vote because it didn't
3179 start at the voting interval that caused us to construct a vote.
3181 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
3182 - Delete unverified-consensus when the real consensus is set.
3183 - Consider retrying a consensus networkstatus fetch immediately
3184 after one fails: don't wait 60 seconds to notice.
3185 - When fetching a consensus as a cache, wait until a newer consensus
3186 should exist before trying to replace the current one.
3187 - Use a more forgiving schedule for retrying failed consensus
3188 downloads than for other types.
3190 o Minor bugfixes (other directory issues):
3191 - Correct the implementation of "download votes by digest." Bugfix on
3193 - Authorities no longer send back "400 you're unreachable please fix
3194 it" errors to Tor servers that aren't online all the time. We're
3195 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
3197 o Minor bugfixes (controller):
3198 - Don't reset trusted dir server list when we set a configuration
3199 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
3200 - Respond to INT and TERM SIGNAL commands before we execute the
3201 signal, in case the signal shuts us down. We had a patch in
3202 0.1.2.1-alpha that tried to do this by queueing the response on
3203 the connection's buffer before shutting down, but that really
3204 isn't the same thing at all. Bug located by Matt Edman.
3206 o Minor bugfixes (misc):
3207 - Correctly check for bad options to the "PublishServerDescriptor"
3208 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
3209 - Stop leaking memory on failing case of base32_decode, and make
3210 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
3211 - Don't try to download extrainfo documents when we're trying to
3212 fetch enough directory info to build a circuit: having enough
3213 info should get priority. Bugfix on 0.2.0.x.
3214 - Don't complain that "your server has not managed to confirm that its
3215 ports are reachable" if we haven't been able to build any circuits
3216 yet. Bug found by spending four hours without a v3 consensus. Bugfix
3218 - Detect the reason for failing to mmap a descriptor file we just
3219 wrote, and give a more useful log message. Fixes bug 533. Bugfix
3222 o Code simplifications and refactoring:
3223 - Remove support for the old bw_accounting file: we've been storing
3224 bandwidth accounting information in the state file since
3225 0.1.2.5-alpha. This may result in bandwidth accounting errors
3226 if you try to upgrade from 0.1.1.x or earlier, or if you try to
3227 downgrade to 0.1.1.x or earlier.
3228 - New convenience code to locate a file within the DataDirectory.
3229 - Move non-authority functionality out of dirvote.c.
3230 - Refactor the arguments for router_pick_{directory_|trusteddir}server
3231 so that they all take the same named flags.
3234 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
3235 Unix users an easy way to script their Tor process (e.g. by
3236 adjusting bandwidth based on the time of the day).
3239 Changes in version 0.2.0.8-alpha - 2007-10-12
3240 This eighth development snapshot fixes a crash bug that's been bothering
3241 us since February 2007, lets bridge authorities store a list of bridge
3242 descriptors they've seen, gets v3 directory voting closer to working,
3243 starts caching v3 directory consensus documents on directory mirrors,
3244 and fixes a variety of smaller issues including some minor memory leaks.
3246 o Major features (router descriptor cache):
3247 - Store routers in a file called cached-descriptors instead of in
3248 cached-routers. Initialize cached-descriptors from cached-routers
3249 if the old format is around. The new format allows us to store
3250 annotations along with descriptors.
3251 - Use annotations to record the time we received each descriptor, its
3252 source, and its purpose.
3253 - Disable the SETROUTERPURPOSE controller command: it is now
3255 - Controllers should now specify cache=no or cache=yes when using
3256 the +POSTDESCRIPTOR command.
3257 - Bridge authorities now write bridge descriptors to disk, meaning
3258 we can export them to other programs and begin distributing them
3261 o Major features (directory authorities):
3262 - When a v3 authority is missing votes or signatures, it now tries
3264 - Directory authorities track weighted fractional uptime as well as
3265 weighted mean-time-between failures. WFU is suitable for deciding
3266 whether a node is "usually up", while MTBF is suitable for deciding
3267 whether a node is "likely to stay up." We need both, because
3268 "usually up" is a good requirement for guards, while "likely to
3269 stay up" is a good requirement for long-lived connections.
3271 o Major features (v3 directory system):
3272 - Caches now download v3 network status documents as needed,
3273 and download the descriptors listed in them.
3274 - All hosts now attempt to download and keep fresh v3 authority
3275 certificates, and re-attempt after failures.
3276 - More internal-consistency checks for vote parsing.
3278 o Major bugfixes (crashes):
3279 - If a connection is shut down abruptly because of something that
3280 happened inside connection_flushed_some(), do not call
3281 connection_finished_flushing(). Should fix bug 451. Bugfix on
3284 o Major bugfixes (performance):
3285 - Fix really bad O(n^2) performance when parsing a long list of
3286 routers: Instead of searching the entire list for an "extra-info "
3287 string which usually wasn't there, once for every routerinfo
3288 we read, just scan lines forward until we find one we like.
3290 - When we add data to a write buffer in response to the data on that
3291 write buffer getting low because of a flush, do not consider the
3292 newly added data as a candidate for immediate flushing, but rather
3293 make it wait until the next round of writing. Otherwise, we flush
3294 and refill recursively, and a single greedy TLS connection can
3295 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
3297 o Minor features (v3 authority system):
3298 - Add more ways for tools to download the votes that lead to the
3300 - Send a 503 when low on bandwidth and a vote, consensus, or
3301 certificate is requested.
3302 - If-modified-since is now implemented properly for all kinds of
3303 certificate requests.
3305 o Minor bugfixes (network statuses):
3306 - Tweak the implementation of proposal 109 slightly: allow at most
3307 two Tor servers on the same IP address, except if it's the location
3308 of a directory authority, in which case allow five. Bugfix on
3311 o Minor bugfixes (controller):
3312 - When sending a status event to the controller telling it that an
3313 OR address is reachable, set the port correctly. (Previously we
3314 were reporting the dir port.) Bugfix on 0.1.2.x.
3316 o Minor bugfixes (v3 directory system):
3317 - Fix logic to look up a cert by its signing key digest. Bugfix on
3319 - Only change the reply to a vote to "OK" if it's not already
3320 set. This gets rid of annoying "400 OK" log messages, which may
3321 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
3322 - When we get a valid consensus, recompute the voting schedule.
3323 - Base the valid-after time of a vote on the consensus voting
3324 schedule, not on our preferred schedule.
3325 - Make the return values and messages from signature uploads and
3326 downloads more sensible.
3327 - Fix a memory leak when serving votes and consensus documents, and
3328 another when serving certificates.
3330 o Minor bugfixes (performance):
3331 - Use a slightly simpler string hashing algorithm (copying Python's
3332 instead of Java's) and optimize our digest hashing algorithm to take
3333 advantage of 64-bit platforms and to remove some possibly-costly
3335 - Fix a minor memory leak whenever we parse guards from our state
3336 file. Bugfix on 0.2.0.7-alpha.
3337 - Fix a minor memory leak whenever we write out a file. Bugfix on
3339 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
3340 command. Bugfix on 0.2.0.5-alpha.
3342 o Minor bugfixes (portability):
3343 - On some platforms, accept() can return a broken address. Detect
3344 this more quietly, and deal accordingly. Fixes bug 483.
3345 - Stop calling tor_strlower() on uninitialized memory in some cases.
3346 Bugfix in 0.2.0.7-alpha.
3348 o Minor bugfixes (usability):
3349 - Treat some 403 responses from directory servers as INFO rather than
3350 WARN-severity events.
3351 - It's not actually an error to find a non-pending entry in the DNS
3352 cache when canceling a pending resolve. Don't log unless stuff is
3353 fishy. Resolves bug 463.
3355 o Minor bugfixes (anonymity):
3356 - Never report that we've used more bandwidth than we're willing to
3357 relay: it leaks how much non-relay traffic we're using. Resolves
3359 - When looking for a circuit to cannibalize, consider family as well
3360 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
3361 circuit cannibalization).
3363 o Code simplifications and refactoring:
3364 - Make a bunch of functions static. Remove some dead code.
3365 - Pull out about a third of the really big routerlist.c; put it in a
3366 new module, networkstatus.c.
3367 - Merge the extra fields in local_routerstatus_t back into
3368 routerstatus_t: we used to need one routerstatus_t for each
3369 authority's opinion, plus a local_routerstatus_t for the locally
3370 computed consensus opinion. To save space, we put the locally
3371 modified fields into local_routerstatus_t, and only the common
3372 stuff into routerstatus_t. But once v3 directories are in use,
3373 clients and caches will no longer need to hold authority opinions;
3374 thus, the rationale for keeping the types separate is now gone.
3375 - Make the code used to reschedule and reattempt downloads more
3377 - Turn all 'Are we a directory server/mirror?' logic into a call to
3379 - Remove the code to generate the oldest (v1) directory format.
3380 The code has been disabled since 0.2.0.5-alpha.
3383 Changes in version 0.2.0.7-alpha - 2007-09-21
3384 This seventh development snapshot makes bridges work again, makes bridge
3385 authorities work for the first time, fixes two huge performance flaws
3386 in hidden services, and fixes a variety of minor issues.
3388 o New directory authorities:
3389 - Set up moria1 and tor26 as the first v3 directory authorities. See
3390 doc/spec/dir-spec.txt for details on the new directory design.
3392 o Major bugfixes (crashes):
3393 - Fix possible segfaults in functions called from
3394 rend_process_relay_cell(). Bugfix on 0.1.2.x.
3396 o Major bugfixes (bridges):
3397 - Fix a bug that made servers send a "404 Not found" in response to
3398 attempts to fetch their server descriptor. This caused Tor servers
3399 to take many minutes to establish reachability for their DirPort,
3400 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
3401 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
3402 users configure that and specify a bridge with an identity
3403 fingerprint, now they will lookup the bridge descriptor at the
3404 default bridge authority via a one-hop tunnel, but once circuits
3405 are established they will switch to a three-hop tunnel for later
3406 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
3408 o Major bugfixes (hidden services):
3409 - Hidden services were choosing introduction points uniquely by
3410 hexdigest, but when constructing the hidden service descriptor
3411 they merely wrote the (potentially ambiguous) nickname.
3412 - Clients now use the v2 intro format for hidden service
3413 connections: they specify their chosen rendezvous point by identity
3414 digest rather than by (potentially ambiguous) nickname. Both
3415 are bugfixes on 0.1.2.x, and they could speed up hidden service
3416 connections dramatically. Thanks to Karsten Loesing.
3418 o Minor features (security):
3419 - As a client, do not believe any server that tells us that an
3420 address maps to an internal address space.
3421 - Make it possible to enable HashedControlPassword and
3422 CookieAuthentication at the same time.
3424 o Minor features (guard nodes):
3425 - Tag every guard node in our state file with the version that
3426 we believe added it, or with our own version if we add it. This way,
3427 if a user temporarily runs an old version of Tor and then switches
3428 back to a new one, she doesn't automatically lose her guards.
3430 o Minor features (speed):
3431 - When implementing AES counter mode, update only the portions of the
3432 counter buffer that need to change, and don't keep separate
3433 network-order and host-order counters when they are the same (i.e.,
3434 on big-endian hosts.)
3436 o Minor features (controller):
3437 - Accept LF instead of CRLF on controller, since some software has a
3438 hard time generating real Internet newlines.
3439 - Add GETINFO values for the server status events
3440 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
3444 - Routers no longer include bandwidth-history lines in their
3445 descriptors; this information is already available in extra-info
3446 documents, and including it in router descriptors took up 60%
3447 (!) of compressed router descriptor downloads. Completes
3448 implementation of proposal 104.
3449 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
3450 and TorControl.py, as they use the old v0 controller protocol,
3451 and are obsoleted by TorFlow anyway.
3452 - Drop support for v1 rendezvous descriptors, since we never used
3453 them anyway, and the code has probably rotted by now. Based on
3454 patch from Karsten Loesing.
3455 - On OSX, stop warning the user that kqueue support in libevent is
3456 "experimental", since it seems to have worked fine for ages.
3459 - When generating information telling us how to extend to a given
3460 router, do not try to include the nickname if it is absent. Fixes
3461 bug 467. Bugfix on 0.2.0.3-alpha.
3462 - Fix a user-triggerable (but not remotely-triggerable) segfault
3463 in expand_filename(). Bugfix on 0.1.2.x.
3464 - Fix a memory leak when freeing incomplete requests from DNSPort.
3465 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
3466 - Don't try to access (or alter) the state file when running
3467 --list-fingerprint or --verify-config or --hash-password. (Resolves
3468 bug 499.) Bugfix on 0.1.2.x.
3469 - Servers used to decline to publish their DirPort if their
3470 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
3471 were below a threshold. Now they only look at BandwidthRate and
3472 RelayBandwidthRate. Bugfix on 0.1.2.x.
3473 - Remove an optimization in the AES counter-mode code that assumed
3474 that the counter never exceeded 2^68. When the counter can be set
3475 arbitrarily as an IV (as it is by Karsten's new hidden services
3476 code), this assumption no longer holds. Bugfix on 0.1.2.x.
3477 - Resume listing "AUTHORITY" flag for authorities in network status.
3478 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
3480 o Code simplifications and refactoring:
3481 - Revamp file-writing logic so we don't need to have the entire
3482 contents of a file in memory at once before we write to disk. Tor,
3484 - Turn "descriptor store" into a full-fledged type.
3485 - Move all NT services code into a separate source file.
3486 - Unify all code that computes medians, percentile elements, etc.
3487 - Get rid of a needless malloc when parsing address policies.
3490 Changes in version 0.1.2.17 - 2007-08-30
3491 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
3492 X bundles. Vidalia 0.0.14 makes authentication required for the
3493 ControlPort in the default configuration, which addresses important
3494 security risks. Everybody who uses Vidalia (or another controller)
3497 In addition, this Tor update fixes major load balancing problems with
3498 path selection, which should speed things up a lot once many people
3501 o Major bugfixes (security):
3502 - We removed support for the old (v0) control protocol. It has been
3503 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
3504 become more of a headache than it's worth.
3506 o Major bugfixes (load balancing):
3507 - When choosing nodes for non-guard positions, weight guards
3508 proportionally less, since they already have enough load. Patch
3510 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
3511 will allow fast Tor servers to get more attention.
3512 - When we're upgrading from an old Tor version, forget our current
3513 guards and pick new ones according to the new weightings. These
3514 three load balancing patches could raise effective network capacity
3515 by a factor of four. Thanks to Mike Perry for measurements.
3517 o Major bugfixes (stream expiration):
3518 - Expire not-yet-successful application streams in all cases if
3519 they've been around longer than SocksTimeout. Right now there are
3520 some cases where the stream will live forever, demanding a new
3521 circuit every 15 seconds. Fixes bug 454; reported by lodger.
3523 o Minor features (controller):
3524 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
3525 is valid before any authentication has been received. It tells
3526 a controller what kind of authentication is expected, and what
3527 protocol is spoken. Implements proposal 119.
3529 o Minor bugfixes (performance):
3530 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
3531 greatly speeding up loading cached-routers from disk on startup.
3532 - Disable sentinel-based debugging for buffer code: we squashed all
3533 the bugs that this was supposed to detect a long time ago, and now
3534 its only effect is to change our buffer sizes from nice powers of
3535 two (which platform mallocs tend to like) to values slightly over
3536 powers of two (which make some platform mallocs sad).
3538 o Minor bugfixes (misc):
3539 - If exit bandwidth ever exceeds one third of total bandwidth, then
3540 use the correct formula to weight exit nodes when choosing paths.
3541 Based on patch from Mike Perry.
3542 - Choose perfectly fairly among routers when choosing by bandwidth and
3543 weighting by fraction of bandwidth provided by exits. Previously, we
3544 would choose with only approximate fairness, and correct ourselves
3545 if we ran off the end of the list.
3546 - If we require CookieAuthentication but we fail to write the
3547 cookie file, we would warn but not exit, and end up in a state
3548 where no controller could authenticate. Now we exit.
3549 - If we require CookieAuthentication, stop generating a new cookie
3550 every time we change any piece of our config.
3551 - Refuse to start with certain directory authority keys, and
3552 encourage people using them to stop.
3553 - Terminate multi-line control events properly. Original patch
3555 - Fix a minor memory leak when we fail to find enough suitable
3556 servers to choose a circuit.
3557 - Stop leaking part of the descriptor when we run into a particularly
3558 unparseable piece of it.
3561 Changes in version 0.2.0.6-alpha - 2007-08-26
3562 This sixth development snapshot features a new Vidalia version in the
3563 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
3564 the ControlPort in the default configuration, which addresses important
3567 In addition, this snapshot fixes major load balancing problems
3568 with path selection, which should speed things up a lot once many
3569 people have upgraded. The directory authorities also use a new
3570 mean-time-between-failure approach to tracking which servers are stable,
3571 rather than just looking at the most recent uptime.
3573 o New directory authorities:
3574 - Set up Tonga as the default bridge directory authority.
3577 - Directory authorities now track servers by weighted
3578 mean-times-between-failures. When we have 4 or more days of data,
3579 use measured MTBF rather than declared uptime to decide whether
3580 to call a router Stable. Implements proposal 108.
3582 o Major bugfixes (load balancing):
3583 - When choosing nodes for non-guard positions, weight guards
3584 proportionally less, since they already have enough load. Patch
3586 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
3587 will allow fast Tor servers to get more attention.
3588 - When we're upgrading from an old Tor version, forget our current
3589 guards and pick new ones according to the new weightings. These
3590 three load balancing patches could raise effective network capacity
3591 by a factor of four. Thanks to Mike Perry for measurements.
3593 o Major bugfixes (descriptor parsing):
3594 - Handle unexpected whitespace better in malformed descriptors. Bug
3595 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
3598 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
3599 GETINFO for Torstat to use until it can switch to using extrainfos.
3600 - Optionally (if built with -DEXPORTMALLINFO) export the output
3601 of mallinfo via http, as tor/mallinfo.txt. Only accessible
3605 - Do not intermix bridge routers with controller-added
3606 routers. (Bugfix on 0.2.0.x)
3607 - Do not fail with an assert when accept() returns an unexpected
3608 address family. Addresses but does not wholly fix bug 483. (Bugfix
3610 - Let directory authorities startup even when they can't generate
3611 a descriptor immediately, e.g. because they don't know their
3613 - Stop putting the authentication cookie in a file called "0"
3614 in your working directory if you don't specify anything for the
3615 new CookieAuthFile option. Reported by Matt Edman.
3616 - Make it possible to read the PROTOCOLINFO response in a way that
3617 conforms to our control-spec. Reported by Matt Edman.
3618 - Fix a minor memory leak when we fail to find enough suitable
3619 servers to choose a circuit. Bugfix on 0.1.2.x.
3620 - Stop leaking part of the descriptor when we run into a particularly
3621 unparseable piece of it. Bugfix on 0.1.2.x.
3622 - Unmap the extrainfo cache file on exit.
3625 Changes in version 0.2.0.5-alpha - 2007-08-19
3626 This fifth development snapshot fixes compilation on Windows again;
3627 fixes an obnoxious client-side bug that slowed things down and put
3628 extra load on the network; gets us closer to using the v3 directory
3629 voting scheme; makes it easier for Tor controllers to use cookie-based
3630 authentication; and fixes a variety of other bugs.
3633 - Version 1 directories are no longer generated in full. Instead,
3634 authorities generate and serve "stub" v1 directories that list
3635 no servers. This will stop Tor versions 0.1.0.x and earlier from
3636 working, but (for security reasons) nobody should be running those
3639 o Major bugfixes (compilation, 0.2.0.x):
3640 - Try to fix Win32 compilation again: improve checking for IPv6 types.
3641 - Try to fix MSVC compilation: build correctly on platforms that do
3642 not define s6_addr16 or s6_addr32.
3643 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
3646 o Major bugfixes (stream expiration):
3647 - Expire not-yet-successful application streams in all cases if
3648 they've been around longer than SocksTimeout. Right now there are
3649 some cases where the stream will live forever, demanding a new
3650 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
3653 o Minor features (directory servers):
3654 - When somebody requests a list of statuses or servers, and we have
3655 none of those, return a 404 rather than an empty 200.
3657 o Minor features (directory voting):
3658 - Store v3 consensus status consensuses on disk, and reload them
3661 o Minor features (security):
3662 - Warn about unsafe ControlPort configurations.
3663 - Refuse to start with certain directory authority keys, and
3664 encourage people using them to stop.
3666 o Minor features (controller):
3667 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
3668 is valid before any authentication has been received. It tells
3669 a controller what kind of authentication is expected, and what
3670 protocol is spoken. Implements proposal 119.
3671 - New config option CookieAuthFile to choose a new location for the
3672 cookie authentication file, and config option
3673 CookieAuthFileGroupReadable to make it group-readable.
3675 o Minor features (unit testing):
3676 - Add command-line arguments to unit-test executable so that we can
3677 invoke any chosen test from the command line rather than having
3678 to run the whole test suite at once; and so that we can turn on
3679 logging for the unit tests.
3681 o Minor bugfixes (on 0.1.2.x):
3682 - If we require CookieAuthentication but we fail to write the
3683 cookie file, we would warn but not exit, and end up in a state
3684 where no controller could authenticate. Now we exit.
3685 - If we require CookieAuthentication, stop generating a new cookie
3686 every time we change any piece of our config.
3687 - When loading bandwidth history, do not believe any information in
3688 the future. Fixes bug 434.
3689 - When loading entry guard information, do not believe any information
3691 - When we have our clock set far in the future and generate an
3692 onion key, then re-set our clock to be correct, we should not stop
3693 the onion key from getting rotated.
3694 - Clean up torrc sample config file.
3695 - Do not automatically run configure from autogen.sh. This
3696 non-standard behavior tended to annoy people who have built other
3699 o Minor bugfixes (on 0.2.0.x):
3700 - Fix a bug with AutomapHostsOnResolve that would always cause
3701 the second request to fail. Bug reported by Kate. Bugfix on
3703 - Fix a bug in ADDRMAP controller replies that would sometimes
3704 try to print a NULL. Patch from tup.
3705 - Read v3 directory authority keys from the right location.
3706 - Numerous bugfixes to directory voting code.
3709 Changes in version 0.1.2.16 - 2007-08-01
3710 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
3711 remote attacker in certain situations to rewrite the user's torrc
3712 configuration file. This can completely compromise anonymity of users
3713 in most configurations, including those running the Vidalia bundles,
3714 TorK, etc. Or worse.
3716 o Major security fixes:
3717 - Close immediately after missing authentication on control port;
3718 do not allow multiple authentication attempts.
3721 Changes in version 0.2.0.4-alpha - 2007-08-01
3722 This fourth development snapshot fixes a critical security vulnerability
3723 for most users, specifically those running Vidalia, TorK, etc. Everybody
3724 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
3726 o Major security fixes:
3727 - Close immediately after missing authentication on control port;
3728 do not allow multiple authentication attempts.
3730 o Major bugfixes (compilation):
3731 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
3734 o Minor features (performance):
3735 - Be even more aggressive about releasing RAM from small
3736 empty buffers. Thanks to our free-list code, this shouldn't be too
3737 performance-intensive.
3738 - Disable sentinel-based debugging for buffer code: we squashed all
3739 the bugs that this was supposed to detect a long time ago, and
3740 now its only effect is to change our buffer sizes from nice
3741 powers of two (which platform mallocs tend to like) to values
3742 slightly over powers of two (which make some platform mallocs sad).
3743 - Log malloc statistics from mallinfo() on platforms where it
3747 Changes in version 0.2.0.3-alpha - 2007-07-29
3748 This third development snapshot introduces new experimental
3749 blocking-resistance features and a preliminary version of the v3
3750 directory voting design, and includes many other smaller features
3754 - The first pieces of our "bridge" design for blocking-resistance
3755 are implemented. People can run bridge directory authorities;
3756 people can run bridges; and people can configure their Tor clients
3757 with a set of bridges to use as the first hop into the Tor network.
3758 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
3760 - Create listener connections before we setuid to the configured
3761 User and Group. Now non-Windows users can choose port values
3762 under 1024, start Tor as root, and have Tor bind those ports
3763 before it changes to another UID. (Windows users could already
3765 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
3766 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
3767 on "vserver" accounts. (Patch from coderman.)
3768 - Be even more aggressive about separating local traffic from relayed
3769 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
3771 o Major features (experimental):
3772 - First cut of code for "v3 dir voting": directory authorities will
3773 vote on a common network status document rather than each publishing
3774 their own opinion. This code needs more testing and more corner-case
3775 handling before it's ready for use.
3778 - Directory authorities now call routers Fast if their bandwidth is
3779 at least 100KB/s, and consider their bandwidth adequate to be a
3780 Guard if it is at least 250KB/s, no matter the medians. This fix
3781 complements proposal 107. [Bugfix on 0.1.2.x]
3782 - Directory authorities now never mark more than 3 servers per IP as
3783 Valid and Running. (Implements proposal 109, by Kevin Bauer and
3785 - Minor change to organizationName and commonName generation
3786 procedures in TLS certificates during Tor handshakes, to invalidate
3787 some earlier censorware approaches. This is not a long-term
3788 solution, but applying it will give us a bit of time to look into
3789 the epidemiology of countermeasures as they spread.
3791 o Major bugfixes (directory):
3792 - Rewrite directory tokenization code to never run off the end of
3793 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
3795 o Minor features (controller):
3796 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
3797 match requests to applications. (Patch from Robert Hogan.)
3798 - Report address and port correctly on connections to DNSPort. (Patch
3800 - Add a RESOLVE command to launch hostname lookups. (Original patch
3802 - Add GETINFO status/enough-dir-info to let controllers tell whether
3803 Tor has downloaded sufficient directory information. (Patch
3805 - You can now use the ControlSocket option to tell Tor to listen for
3806 controller connections on Unix domain sockets on systems that
3807 support them. (Patch from Peter Palfrader.)
3808 - STREAM NEW events are generated for DNSPort requests and for
3809 tunneled directory connections. (Patch from Robert Hogan.)
3810 - New "GETINFO address-mappings/*" command to get address mappings
3811 with expiry information. "addr-mappings/*" is now deprecated.
3814 o Minor features (misc):
3815 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
3817 - The tor-gencert tool for v3 directory authorities now creates all
3818 files as readable to the file creator only, and write-protects
3819 the authority identity key.
3820 - When dumping memory usage, list bytes used in buffer memory
3822 - When running with dmalloc, dump more stats on hup and on exit.
3823 - Directory authorities now fail quickly and (relatively) harmlessly
3824 if they generate a network status document that is somehow
3827 o Traffic load balancing improvements:
3828 - If exit bandwidth ever exceeds one third of total bandwidth, then
3829 use the correct formula to weight exit nodes when choosing paths.
3830 (Based on patch from Mike Perry.)
3831 - Choose perfectly fairly among routers when choosing by bandwidth and
3832 weighting by fraction of bandwidth provided by exits. Previously, we
3833 would choose with only approximate fairness, and correct ourselves
3834 if we ran off the end of the list. [Bugfix on 0.1.2.x]
3836 o Performance improvements:
3837 - Be more aggressive with freeing buffer RAM or putting it on the
3839 - Use Critical Sections rather than Mutexes for synchronizing threads
3840 on win32; Mutexes are heavier-weight, and designed for synchronizing
3843 o Deprecated and removed features:
3844 - RedirectExits is now deprecated.
3845 - Stop allowing address masks that do not correspond to bit prefixes.
3846 We have warned about these for a really long time; now it's time
3847 to reject them. (Patch from croup.)
3849 o Minor bugfixes (directory):
3850 - Fix another crash bug related to extra-info caching. (Bug found by
3851 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
3852 - Directories no longer return a "304 not modified" when they don't
3853 have the networkstatus the client asked for. Also fix a memory
3854 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
3855 - We had accidentally labelled 0.1.2.x directory servers as not
3856 suitable for begin_dir requests, and had labelled no directory
3857 servers as suitable for uploading extra-info documents. [Bugfix
3860 o Minor bugfixes (dns):
3861 - Fix a crash when DNSPort is set more than once. (Patch from Robert
3862 Hogan.) [Bugfix on 0.2.0.2-alpha]
3863 - Add DNSPort connections to the global connection list, so that we
3864 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
3866 - Fix a dangling reference that could lead to a crash when DNSPort is
3867 changed or closed (Patch from Robert Hogan.) [Bugfix on
3870 o Minor bugfixes (controller):
3871 - Provide DNS expiry times in GMT, not in local time. For backward
3872 compatibility, ADDRMAP events only provide GMT expiry in an extended
3873 field. "GETINFO address-mappings" always does the right thing.
3874 - Use CRLF line endings properly in NS events.
3875 - Terminate multi-line control events properly. (Original patch
3876 from tup.) [Bugfix on 0.1.2.x-alpha]
3877 - Do not include spaces in SOURCE_ADDR fields in STREAM
3878 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
3881 Changes in version 0.1.2.15 - 2007-07-17
3882 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
3883 problems, fixes compilation on BSD, and fixes a variety of other
3884 bugs. Everybody should upgrade.
3886 o Major bugfixes (compilation):
3887 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
3889 o Major bugfixes (crashes):
3890 - Try even harder not to dereference the first character after
3891 an mmap(). Reported by lodger.
3892 - Fix a crash bug in directory authorities when we re-number the
3893 routerlist while inserting a new router.
3894 - When the cached-routers file is an even multiple of the page size,
3895 don't run off the end and crash. (Fixes bug 455; based on idea
3897 - Fix eventdns.c behavior on Solaris: It is critical to include
3898 orconfig.h _before_ sys/types.h, so that we can get the expected
3899 definition of _FILE_OFFSET_BITS.
3901 o Major bugfixes (security):
3902 - Fix a possible buffer overrun when using BSD natd support. Bug
3904 - When sending destroy cells from a circuit's origin, don't include
3905 the reason for tearing down the circuit. The spec says we didn't,
3906 and now we actually don't. Reported by lodger.
3907 - Keep streamids from different exits on a circuit separate. This
3908 bug may have allowed other routers on a given circuit to inject
3909 cells into streams. Reported by lodger; fixes bug 446.
3910 - If there's a never-before-connected-to guard node in our list,
3911 never choose any guards past it. This way we don't expand our
3912 guard list unless we need to.
3914 o Minor bugfixes (guard nodes):
3915 - Weight guard selection by bandwidth, so that low-bandwidth nodes
3916 don't get overused as guards.
3918 o Minor bugfixes (directory):
3919 - Correctly count the number of authorities that recommend each
3920 version. Previously, we were under-counting by 1.
3921 - Fix a potential crash bug when we load many server descriptors at
3922 once and some of them make others of them obsolete. Fixes bug 458.
3924 o Minor bugfixes (hidden services):
3925 - Stop tearing down the whole circuit when the user asks for a
3926 connection to a port that the hidden service didn't configure.
3929 o Minor bugfixes (misc):
3930 - On Windows, we were preventing other processes from reading
3931 cached-routers while Tor was running. Reported by janbar.
3932 - Fix a possible (but very unlikely) bug in picking routers by
3933 bandwidth. Add a log message to confirm that it is in fact
3934 unlikely. Patch from lodger.
3935 - Backport a couple of memory leak fixes.
3936 - Backport miscellaneous cosmetic bugfixes.
3939 Changes in version 0.2.0.2-alpha - 2007-06-02
3940 o Major bugfixes on 0.2.0.1-alpha:
3941 - Fix an assertion failure related to servers without extra-info digests.
3942 Resolves bugs 441 and 442.
3944 o Minor features (directory):
3945 - Support "If-Modified-Since" when answering HTTP requests for
3946 directories, running-routers documents, and network-status documents.
3947 (There's no need to support it for router descriptors, since those
3948 are downloaded by descriptor digest.)
3950 o Minor build issues:
3951 - Clear up some MIPSPro compiler warnings.
3952 - When building from a tarball on a machine that happens to have SVK
3953 installed, report the micro-revision as whatever version existed
3954 in the tarball, not as "x".
3957 Changes in version 0.2.0.1-alpha - 2007-06-01
3958 This early development snapshot provides new features for people running
3959 Tor as both a client and a server (check out the new RelayBandwidth
3960 config options); lets Tor run as a DNS proxy; and generally moves us
3961 forward on a lot of fronts.
3963 o Major features, server usability:
3964 - New config options RelayBandwidthRate and RelayBandwidthBurst:
3965 a separate set of token buckets for relayed traffic. Right now
3966 relayed traffic is defined as answers to directory requests, and
3967 OR connections that don't have any local circuits on them.
3969 o Major features, client usability:
3970 - A client-side DNS proxy feature to replace the need for
3971 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
3972 for DNS requests on port 9999, use the Tor network to resolve them
3973 anonymously, and send the reply back like a regular DNS server.
3974 The code still only implements a subset of DNS.
3975 - Make PreferTunneledDirConns and TunnelDirConns work even when
3976 we have no cached directory info. This means Tor clients can now
3977 do all of their connections protected by TLS.
3979 o Major features, performance and efficiency:
3980 - Directory authorities accept and serve "extra info" documents for
3981 routers. These documents contain fields from router descriptors
3982 that aren't usually needed, and that use a lot of excess
3983 bandwidth. Once these fields are removed from router descriptors,
3984 the bandwidth savings should be about 60%. [Partially implements
3986 - Servers upload extra-info documents to any authority that accepts
3987 them. Authorities (and caches that have been configured to download
3988 extra-info documents) download them as needed. [Partially implements
3990 - Change the way that Tor buffers data that it is waiting to write.
3991 Instead of queueing data cells in an enormous ring buffer for each
3992 client->OR or OR->OR connection, we now queue cells on a separate
3993 queue for each circuit. This lets us use less slack memory, and
3994 will eventually let us be smarter about prioritizing different kinds
3996 - Use memory pools to allocate cells with better speed and memory
3997 efficiency, especially on platforms where malloc() is inefficient.
3998 - Stop reading on edge connections when their corresponding circuit
3999 buffers are full; start again as the circuits empty out.
4001 o Major features, other:
4002 - Add an HSAuthorityRecordStats option that hidden service authorities
4003 can use to track statistics of overall hidden service usage without
4004 logging information that would be very useful to an attacker.
4005 - Start work implementing multi-level keys for directory authorities:
4006 Add a standalone tool to generate key certificates. (Proposal 103.)
4009 - Directory authorities now call routers Stable if they have an
4010 uptime of at least 30 days, even if that's not the median uptime
4011 in the network. Implements proposal 107, suggested by Kevin Bauer
4014 o Minor fixes (resource management):
4015 - Count the number of open sockets separately from the number
4016 of active connection_t objects. This will let us avoid underusing
4017 our allocated connection limit.
4018 - We no longer use socket pairs to link an edge connection to an
4019 anonymous directory connection or a DirPort test connection.
4020 Instead, we track the link internally and transfer the data
4021 in-process. This saves two sockets per "linked" connection (at the
4022 client and at the server), and avoids the nasty Windows socketpair()
4024 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
4025 for every single inactive connection_t. Free items from the
4026 4k/16k-buffer free lists when they haven't been used for a while.
4028 o Minor features (build):
4029 - Make autoconf search for libevent, openssl, and zlib consistently.
4030 - Update deprecated macros in configure.in.
4031 - When warning about missing headers, tell the user to let us
4032 know if the compile succeeds anyway, so we can downgrade the
4034 - Include the current subversion revision as part of the version
4035 string: either fetch it directly if we're in an SVN checkout, do
4036 some magic to guess it if we're in an SVK checkout, or use
4037 the last-detected version if we're building from a .tar.gz.
4038 Use this version consistently in log messages.
4040 o Minor features (logging):
4041 - Always prepend "Bug: " to any log message about a bug.
4042 - Put a platform string (e.g. "Linux i686") in the startup log
4043 message, so when people paste just their logs, we know if it's
4044 OpenBSD or Windows or what.
4045 - When logging memory usage, break down memory used in buffers by
4048 o Minor features (directory system):
4049 - New config option V2AuthoritativeDirectory that all directory
4050 authorities should set. This will let future authorities choose
4051 not to serve V2 directory information.
4052 - Directory authorities allow multiple router descriptors and/or extra
4053 info documents to be uploaded in a single go. This will make
4054 implementing proposal 104 simpler.
4056 o Minor features (controller):
4057 - Add a new config option __DisablePredictedCircuits designed for
4058 use by the controller, when we don't want Tor to build any circuits
4060 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
4061 so we can exit from the middle of the circuit.
4062 - Implement "getinfo status/circuit-established".
4063 - Implement "getinfo status/version/..." so a controller can tell
4064 whether the current version is recommended, and whether any versions
4065 are good, and how many authorities agree. (Patch from shibz.)
4067 o Minor features (hidden services):
4068 - Allow multiple HiddenServicePort directives with the same virtual
4069 port; when they occur, the user is sent round-robin to one
4070 of the target ports chosen at random. Partially fixes bug 393 by
4071 adding limited ad-hoc round-robining.
4073 o Minor features (other):
4075 - Add a new AutomapHostsOnResolve option: when it is enabled, any
4076 resolve request for hosts matching a given pattern causes Tor to
4077 generate an internal virtual address mapping for that host. This
4078 allows DNSPort to work sensibly with hidden service users. By
4079 default, .exit and .onion addresses are remapped; the list of
4080 patterns can be reconfigured with AutomapHostsSuffixes.
4081 - Add an "-F" option to tor-resolve to force a resolve for a .onion
4082 address. Thanks to the AutomapHostsOnResolve option, this is no
4083 longer a completely silly thing to do.
4084 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
4085 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
4086 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
4087 minus 1 byte: the actual maximum declared bandwidth.
4090 - Removed support for the old binary "version 0" controller protocol.
4091 This has been deprecated since 0.1.1, and warnings have been issued
4092 since 0.1.2. When we encounter a v0 control message, we now send
4093 back an error and close the connection.
4094 - Remove the old "dns worker" server DNS code: it hasn't been default
4095 since 0.1.2.2-alpha, and all the servers seem to be using the new
4098 o Minor bugfixes (portability):
4099 - Even though Windows is equally happy with / and \ as path separators,
4100 try to use \ consistently on Windows and / consistently on Unix: it
4101 makes the log messages nicer.
4102 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
4103 - Read resolv.conf files correctly on platforms where read() returns
4104 partial results on small file reads.
4106 o Minor bugfixes (directory):
4107 - Correctly enforce that elements of directory objects do not appear
4108 more often than they are allowed to appear.
4109 - When we are reporting the DirServer line we just parsed, we were
4110 logging the second stanza of the key fingerprint, not the first.
4112 o Minor bugfixes (logging):
4113 - When we hit an EOF on a log (probably because we're shutting down),
4114 don't try to remove the log from the list: just mark it as
4115 unusable. (Bulletproofs against bug 222.)
4117 o Minor bugfixes (other):
4118 - In the exitlist script, only consider the most recently published
4119 server descriptor for each server. Also, when the user requests
4120 a list of servers that _reject_ connections to a given address,
4121 explicitly exclude the IPs that also have servers that accept
4122 connections to that address. (Resolves bug 405.)
4123 - Stop allowing hibernating servers to be "stable" or "fast".
4124 - On Windows, we were preventing other processes from reading
4125 cached-routers while Tor was running. (Reported by janbar)
4126 - Make the NodeFamilies config option work. (Reported by
4127 lodger -- it has never actually worked, even though we added it
4129 - Check return values from pthread_mutex functions.
4130 - Don't save non-general-purpose router descriptors to the disk cache,
4131 because we have no way of remembering what their purpose was when
4133 - Add even more asserts to hunt down bug 417.
4134 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
4135 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
4136 Add a log message to confirm that it is in fact unlikely.
4138 o Minor bugfixes (controller):
4139 - Make 'getinfo fingerprint' return a 551 error if we're not a
4140 server, so we match what the control spec claims we do. Reported
4142 - Fix a typo in an error message when extendcircuit fails that
4143 caused us to not follow the \r\n-based delimiter protocol. Reported
4146 o Code simplifications and refactoring:
4147 - Stop passing around circuit_t and crypt_path_t pointers that are
4148 implicit in other procedure arguments.
4149 - Drop the old code to choke directory connections when the
4150 corresponding OR connections got full: thanks to the cell queue
4151 feature, OR conns don't get full any more.
4152 - Make dns_resolve() handle attaching connections to circuits
4153 properly, so the caller doesn't have to.
4154 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
4155 - Keep the connection array as a dynamic smartlist_t, rather than as
4156 a fixed-sized array. This is important, as the number of connections
4157 is becoming increasingly decoupled from the number of sockets.
4160 Changes in version 0.1.2.14 - 2007-05-25
4161 Tor 0.1.2.14 changes the addresses of two directory authorities (this
4162 change especially affects those who serve or use hidden services),
4163 and fixes several other crash- and security-related bugs.
4165 o Directory authority changes:
4166 - Two directory authorities (moria1 and moria2) just moved to new
4167 IP addresses. This change will particularly affect those who serve
4168 or use hidden services.
4170 o Major bugfixes (crashes):
4171 - If a directory server runs out of space in the connection table
4172 as it's processing a begin_dir request, it will free the exit stream
4173 but leave it attached to the circuit, leading to unpredictable
4174 behavior. (Reported by seeess, fixes bug 425.)
4175 - Fix a bug in dirserv_remove_invalid() that would cause authorities
4176 to corrupt memory under some really unlikely scenarios.
4177 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
4178 - Avoid segfaults when reading from mmaped descriptor file. (Reported
4181 o Major bugfixes (security):
4182 - When choosing an entry guard for a circuit, avoid using guards
4183 that are in the same family as the chosen exit -- not just guards
4184 that are exactly the chosen exit. (Reported by lodger.)
4186 o Major bugfixes (resource management):
4187 - If a directory authority is down, skip it when deciding where to get
4188 networkstatus objects or descriptors. Otherwise we keep asking
4189 every 10 seconds forever. Fixes bug 384.
4190 - Count it as a failure if we fetch a valid network-status but we
4191 don't want to keep it. Otherwise we'll keep fetching it and keep
4192 not wanting to keep it. Fixes part of bug 422.
4193 - If all of our dirservers have given us bad or no networkstatuses
4194 lately, then stop hammering them once per minute even when we
4195 think they're failed. Fixes another part of bug 422.
4198 - Actually set the purpose correctly for descriptors inserted with
4200 - When we have k non-v2 authorities in our DirServer config,
4201 we ignored the last k authorities in the list when updating our
4203 - Correctly back-off from requesting router descriptors that we are
4204 having a hard time downloading.
4205 - Read resolv.conf files correctly on platforms where read() returns
4206 partial results on small file reads.
4207 - Don't rebuild the entire router store every time we get 32K of
4208 routers: rebuild it when the journal gets very large, or when
4209 the gaps in the store get very large.
4212 - When routers publish SVN revisions in their router descriptors,
4213 authorities now include those versions correctly in networkstatus
4215 - Warn when using a version of libevent before 1.3b to run a server on
4216 OSX or BSD: these versions interact badly with userspace threads.
4219 Changes in version 0.1.2.13 - 2007-04-24
4220 This release features some major anonymity fixes, such as safer path
4221 selection; better client performance; faster bootstrapping, better
4222 address detection, and better DNS support for servers; write limiting as
4223 well as read limiting to make servers easier to run; and a huge pile of
4224 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
4226 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
4227 of the Freenode IRC network, remembering his patience and vision for
4228 free speech on the Internet.
4231 - Fix a memory leak when we ask for "all" networkstatuses and we
4232 get one we don't recognize.
4233 - Add more asserts to hunt down bug 417.
4234 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
4237 Changes in version 0.1.2.12-rc - 2007-03-16
4239 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
4240 directory information requested inside Tor connections (i.e. via
4241 begin_dir cells). It only triggered when the same connection was
4242 serving other data at the same time. Reported by seeess.
4245 - When creating a circuit via the controller, send a 'launched'
4246 event when we're done, so we follow the spec better.
4249 Changes in version 0.1.2.11-rc - 2007-03-15
4250 o Minor bugfixes (controller), reported by daejees:
4251 - Correct the control spec to match how the code actually responds
4252 to 'getinfo addr-mappings/*'.
4253 - The control spec described a GUARDS event, but the code
4254 implemented a GUARD event. Standardize on GUARD, but let people
4258 Changes in version 0.1.2.10-rc - 2007-03-07
4259 o Major bugfixes (Windows):
4260 - Do not load the NT services library functions (which may not exist)
4261 just to detect if we're a service trying to shut down. Now we run
4262 on Win98 and friends again.
4264 o Minor bugfixes (other):
4265 - Clarify a couple of log messages.
4266 - Fix a misleading socks5 error number.
4269 Changes in version 0.1.2.9-rc - 2007-03-02
4270 o Major bugfixes (Windows):
4271 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
4272 of the usual GCC "%llu". This prevents a bug when saving 64-bit
4273 int configuration values: the high-order 32 bits would get
4274 truncated. In particular, we were being bitten by the default
4275 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
4276 and maybe also bug 397.)
4278 o Minor bugfixes (performance):
4279 - Use OpenSSL's AES implementation on platforms where it's faster.
4280 This could save us as much as 10% CPU usage.
4282 o Minor bugfixes (server):
4283 - Do not rotate onion key immediately after setting it for the first
4286 o Minor bugfixes (directory authorities):
4287 - Stop calling servers that have been hibernating for a long time
4288 "stable". Also, stop letting hibernating or obsolete servers affect
4289 uptime and bandwidth cutoffs.
4290 - Stop listing hibernating servers in the v1 directory.
4292 o Minor bugfixes (hidden services):
4293 - Upload hidden service descriptors slightly less often, to reduce
4294 load on authorities.
4296 o Minor bugfixes (other):
4297 - Fix an assert that could trigger if a controller quickly set then
4298 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
4299 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
4301 - Fix a potential race condition in the rpm installer. Found by
4303 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
4304 of 2 as indicating that the server is completely bad; it sometimes
4305 means that the server is just bad for the request in question. (may fix
4306 the last of bug 326.)
4307 - Disable encrypted directory connections when we don't have a server
4308 descriptor for the destination. We'll get this working again in
4312 Changes in version 0.1.2.8-beta - 2007-02-26
4313 o Major bugfixes (crashes):
4314 - Stop crashing when the controller asks us to resetconf more than
4315 one config option at once. (Vidalia 0.0.11 does this.)
4316 - Fix a crash that happened on Win98 when we're given command-line
4317 arguments: don't try to load NT service functions from advapi32.dll
4318 except when we need them. (Bug introduced in 0.1.2.7-alpha;
4320 - Fix a longstanding obscure crash bug that could occur when
4321 we run out of DNS worker processes. (Resolves bug 390.)
4323 o Major bugfixes (hidden services):
4324 - Correctly detect whether hidden service descriptor downloads are
4325 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
4327 o Major bugfixes (accounting):
4328 - When we start during an accounting interval before it's time to wake
4329 up, remember to wake up at the correct time. (May fix bug 342.)
4331 o Minor bugfixes (controller):
4332 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
4333 clear the corresponding on_circuit variable, and remember later
4334 that we don't need to send a redundant CLOSED event. (Resolves part
4336 - Report events where a resolve succeeded or where we got a socks
4337 protocol error correctly, rather than calling both of them
4339 - Change reported stream target addresses to IP consistently when
4340 we finally get the IP from an exit node.
4341 - Send log messages to the controller even if they happen to be very
4344 o Minor bugfixes (other):
4345 - Display correct results when reporting which versions are
4346 recommended, and how recommended they are. (Resolves bug 383.)
4347 - Improve our estimates for directory bandwidth to be less random:
4348 guess that an unrecognized directory will have the average bandwidth
4349 from all known directories, not that it will have the average
4350 bandwidth from those directories earlier than it on the list.
4351 - If we start a server with ClientOnly 1, then set ClientOnly to 0
4352 and hup, stop triggering an assert based on an empty onion_key.
4353 - On platforms with no working mmap() equivalent, don't warn the
4354 user when cached-routers doesn't exist.
4355 - Warn the user when mmap() [or its equivalent] fails for some reason
4356 other than file-not-found.
4357 - Don't warn the user when cached-routers.new doesn't exist: that's
4358 perfectly fine when starting up for the first time.
4359 - When EntryNodes are configured, rebuild the guard list to contain,
4360 in order: the EntryNodes that were guards before; the rest of the
4361 EntryNodes; the nodes that were guards before.
4362 - Mask out all signals in sub-threads; only the libevent signal
4363 handler should be processing them. This should prevent some crashes
4364 on some machines using pthreads. (Patch from coderman.)
4365 - Fix switched arguments on memset in the implementation of
4366 tor_munmap() for systems with no mmap() call.
4367 - When Tor receives a router descriptor that it asked for, but
4368 no longer wants (because it has received fresh networkstatuses
4369 in the meantime), do not warn the user. Cache the descriptor if
4370 we're a cache; drop it if we aren't.
4371 - Make earlier entry guards _really_ get retried when the network
4373 - On a malformed DNS reply, always give an error to the corresponding
4375 - Build with recent libevents on platforms that do not define the
4376 nonstandard types "u_int8_t" and friends.
4378 o Minor features (controller):
4379 - Warn the user when an application uses the obsolete binary v0
4380 control protocol. We're planning to remove support for it during
4381 the next development series, so it's good to give people some
4383 - Add STREAM_BW events to report per-entry-stream bandwidth
4384 use. (Patch from Robert Hogan.)
4385 - Rate-limit SIGNEWNYM signals in response to controllers that
4386 impolitely generate them for every single stream. (Patch from
4387 mwenge; closes bug 394.)
4388 - Make REMAP stream events have a SOURCE (cache or exit), and
4389 make them generated in every case where we get a successful
4390 connected or resolved cell.
4392 o Minor bugfixes (performance):
4393 - Call router_have_min_dir_info half as often. (This is showing up in
4394 some profiles, but not others.)
4395 - When using GCC, make log_debug never get called at all, and its
4396 arguments never get evaluated, when no debug logs are configured.
4397 (This is showing up in some profiles, but not others.)
4400 - Remove some never-implemented options. Mark PathlenCoinWeight as
4402 - Implement proposal 106: Stop requiring clients to have well-formed
4403 certificates; stop checking nicknames in certificates. (Clients
4404 have certificates so that they can look like Tor servers, but in
4405 the future we might want to allow them to look like regular TLS
4406 clients instead. Nicknames in certificates serve no purpose other
4407 than making our protocol easier to recognize on the wire.)
4408 - Revise messages on handshake failure again to be even more clear about
4409 which are incoming connections and which are outgoing.
4410 - Discard any v1 directory info that's over 1 month old (for
4411 directories) or over 1 week old (for running-routers lists).
4412 - Do not warn when individual nodes in the configuration's EntryNodes,
4413 ExitNodes, etc are down: warn only when all possible nodes
4414 are down. (Fixes bug 348.)
4415 - Always remove expired routers and networkstatus docs before checking
4416 whether we have enough information to build circuits. (Fixes
4418 - Put a lower-bound on MaxAdvertisedBandwidth.
4421 Changes in version 0.1.2.7-alpha - 2007-02-06
4422 o Major bugfixes (rate limiting):
4423 - Servers decline directory requests much more aggressively when
4424 they're low on bandwidth. Otherwise they end up queueing more and
4425 more directory responses, which can't be good for latency.
4426 - But never refuse directory requests from local addresses.
4427 - Fix a memory leak when sending a 503 response for a networkstatus
4429 - Be willing to read or write on local connections (e.g. controller
4430 connections) even when the global rate limiting buckets are empty.
4431 - If our system clock jumps back in time, don't publish a negative
4432 uptime in the descriptor. Also, don't let the global rate limiting
4433 buckets go absurdly negative.
4434 - Flush local controller connection buffers periodically as we're
4435 writing to them, so we avoid queueing 4+ megabytes of data before
4438 o Major bugfixes (NT services):
4439 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
4440 command-line flag so that admins can override the default by saying
4441 "tor --service install --user "SomeUser"". This will not affect
4442 existing installed services. Also, warn the user that the service
4443 will look for its configuration file in the service user's
4444 %appdata% directory. (We can't do the 'hardwire the user's appdata
4445 directory' trick any more, since we may not have read access to that
4448 o Major bugfixes (other):
4449 - Previously, we would cache up to 16 old networkstatus documents
4450 indefinitely, if they came from nontrusted authorities. Now we
4451 discard them if they are more than 10 days old.
4452 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
4454 - Detect and reject malformed DNS responses containing circular
4456 - If exits are rare enough that we're not marking exits as guards,
4457 ignore exit bandwidth when we're deciding the required bandwidth
4459 - When we're handling a directory connection tunneled over Tor,
4460 don't fill up internal memory buffers with all the data we want
4461 to tunnel; instead, only add it if the OR connection that will
4462 eventually receive it has some room for it. (This can lead to
4463 slowdowns in tunneled dir connections; a better solution will have
4466 o Minor bugfixes (dns):
4467 - Add some defensive programming to eventdns.c in an attempt to catch
4468 possible memory-stomping bugs.
4469 - Detect and reject DNS replies containing IPv4 or IPv6 records with
4470 an incorrect number of bytes. (Previously, we would ignore the
4472 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
4473 in the correct order, and doesn't crash.
4474 - Free memory held in recently-completed DNS lookup attempts on exit.
4475 This was not a memory leak, but may have been hiding memory leaks.
4476 - Handle TTL values correctly on reverse DNS lookups.
4477 - Treat failure to parse resolv.conf as an error.
4479 o Minor bugfixes (other):
4480 - Fix crash with "tor --list-fingerprint" (reported by seeess).
4481 - When computing clock skew from directory HTTP headers, consider what
4482 time it was when we finished asking for the directory, not what
4484 - Expire socks connections if they spend too long waiting for the
4485 handshake to finish. Previously we would let them sit around for
4486 days, if the connecting application didn't close them either.
4487 - And if the socks handshake hasn't started, don't send a
4488 "DNS resolve socks failed" handshake reply; just close it.
4489 - Stop using C functions that OpenBSD's linker doesn't like.
4490 - Don't launch requests for descriptors unless we have networkstatuses
4491 from at least half of the authorities. This delays the first
4492 download slightly under pathological circumstances, but can prevent
4493 us from downloading a bunch of descriptors we don't need.
4494 - Do not log IPs with TLS failures for incoming TLS
4495 connections. (Fixes bug 382.)
4496 - If the user asks to use invalid exit nodes, be willing to use
4498 - Stop using the reserved ac_cv namespace in our configure script.
4499 - Call stat() slightly less often; use fstat() when possible.
4500 - Refactor the way we handle pending circuits when an OR connection
4501 completes or fails, in an attempt to fix a rare crash bug.
4502 - Only rewrite a conn's address based on X-Forwarded-For: headers
4503 if it's a parseable public IP address; and stop adding extra quotes
4504 to the resulting address.
4507 - Weight directory requests by advertised bandwidth. Now we can
4508 let servers enable write limiting but still allow most clients to
4509 succeed at their directory requests. (We still ignore weights when
4510 choosing a directory authority; I hope this is a feature.)
4513 - Create a new file ReleaseNotes which was the old ChangeLog. The
4514 new ChangeLog file now includes the summaries for all development
4516 - Check for addresses with invalid characters at the exit as well
4517 as at the client, and warn less verbosely when they fail. You can
4518 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
4519 - Adapt a patch from goodell to let the contrib/exitlist script
4520 take arguments rather than require direct editing.
4521 - Inform the server operator when we decide not to advertise a
4522 DirPort due to AccountingMax enabled or a low BandwidthRate. It
4523 was confusing Zax, so now we're hopefully more helpful.
4524 - Bring us one step closer to being able to establish an encrypted
4525 directory tunnel without knowing a descriptor first. Still not
4526 ready yet. As part of the change, now assume we can use a
4527 create_fast cell if we don't know anything about a router.
4528 - Allow exit nodes to use nameservers running on ports other than 53.
4529 - Servers now cache reverse DNS replies.
4530 - Add an --ignore-missing-torrc command-line option so that we can
4531 get the "use sensible defaults if the configuration file doesn't
4532 exist" behavior even when specifying a torrc location on the command
4535 o Minor features (controller):
4536 - Track reasons for OR connection failure; make these reasons
4537 available via the controller interface. (Patch from Mike Perry.)
4538 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
4539 can learn when clients are sending malformed hostnames to Tor.
4540 - Clean up documentation for controller status events.
4541 - Add a REMAP status to stream events to note that a stream's
4542 address has changed because of a cached address or a MapAddress
4546 Changes in version 0.1.2.6-alpha - 2007-01-09
4548 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
4549 connection handles more than 4 gigs in either direction, we crash.
4550 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
4551 advertised exit node, somebody might try to exit from us when
4552 we're bootstrapping and before we've built our descriptor yet.
4553 Refuse the connection rather than crashing.
4556 - Warn if we (as a server) find that we've resolved an address that we
4557 weren't planning to resolve.
4558 - Warn that using select() on any libevent version before 1.1 will be
4559 unnecessarily slow (even for select()).
4560 - Flush ERR-level controller status events just like we currently
4561 flush ERR-level log events, so that a Tor shutdown doesn't prevent
4562 the controller from learning about current events.
4564 o Minor features (more controller status events):
4565 - Implement EXTERNAL_ADDRESS server status event so controllers can
4566 learn when our address changes.
4567 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
4568 can learn when directories reject our descriptor.
4569 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
4570 can learn when a client application is speaking a non-socks protocol
4572 - Implement DANGEROUS_SOCKS client status event so controllers
4573 can learn when a client application is leaking DNS addresses.
4574 - Implement BUG general status event so controllers can learn when
4575 Tor is unhappy about its internal invariants.
4576 - Implement CLOCK_SKEW general status event so controllers can learn
4577 when Tor thinks the system clock is set incorrectly.
4578 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
4579 server status events so controllers can learn when their descriptors
4580 are accepted by a directory.
4581 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
4582 server status events so controllers can learn about Tor's progress in
4583 deciding whether it's reachable from the outside.
4584 - Implement BAD_LIBEVENT general status event so controllers can learn
4585 when we have a version/method combination in libevent that needs to
4587 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
4588 and DNS_USELESS server status events so controllers can learn
4589 about changes to DNS server status.
4591 o Minor features (directory):
4592 - Authorities no longer recommend exits as guards if this would shift
4593 too much load to the exit nodes.
4596 Changes in version 0.1.2.5-alpha - 2007-01-06
4598 - Enable write limiting as well as read limiting. Now we sacrifice
4599 capacity if we're pushing out lots of directory traffic, rather
4600 than overrunning the user's intended bandwidth limits.
4601 - Include TLS overhead when counting bandwidth usage; previously, we
4602 would count only the bytes sent over TLS, but not the bytes used
4604 - Support running the Tor service with a torrc not in the same
4605 directory as tor.exe and default to using the torrc located in
4606 the %appdata%\Tor\ of the user who installed the service. Patch
4608 - Servers now check for the case when common DNS requests are going to
4609 wildcarded addresses (i.e. all getting the same answer), and change
4610 their exit policy to reject *:* if it's happening.
4611 - Implement BEGIN_DIR cells, so we can connect to the directory
4612 server via TLS to do encrypted directory requests rather than
4613 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
4614 config options if you like.
4616 o Minor features (config and docs):
4617 - Start using the state file to store bandwidth accounting data:
4618 the bw_accounting file is now obsolete. We'll keep generating it
4619 for a while for people who are still using 0.1.2.4-alpha.
4620 - Try to batch changes to the state file so that we do as few
4621 disk writes as possible while still storing important things in
4623 - The state file and the bw_accounting file get saved less often when
4624 the AvoidDiskWrites config option is set.
4625 - Make PIDFile work on Windows (untested).
4626 - Add internal descriptions for a bunch of configuration options:
4627 accessible via controller interface and in comments in saved
4629 - Reject *:563 (NNTPS) in the default exit policy. We already reject
4630 NNTP by default, so this seems like a sensible addition.
4631 - Clients now reject hostnames with invalid characters. This should
4632 avoid some inadvertent info leaks. Add an option
4633 AllowNonRFC953Hostnames to disable this behavior, in case somebody
4634 is running a private network with hosts called @, !, and #.
4635 - Add a maintainer script to tell us which options are missing
4636 documentation: "make check-docs".
4637 - Add a new address-spec.txt document to describe our special-case
4638 addresses: .exit, .onion, and .noconnnect.
4640 o Minor features (DNS):
4641 - Ongoing work on eventdns infrastructure: now it has dns server
4642 and ipv6 support. One day Tor will make use of it.
4643 - Add client-side caching for reverse DNS lookups.
4644 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
4645 - When we change nameservers or IP addresses, reset and re-launch
4646 our tests for DNS hijacking.
4648 o Minor features (directory):
4649 - Authorities now specify server versions in networkstatus. This adds
4650 about 2% to the size of compressed networkstatus docs, and allows
4651 clients to tell which servers support BEGIN_DIR and which don't.
4652 The implementation is forward-compatible with a proposed future
4653 protocol version scheme not tied to Tor versions.
4654 - DirServer configuration lines now have an orport= option so
4655 clients can open encrypted tunnels to the authorities without
4656 having downloaded their descriptors yet. Enabled for moria1,
4657 moria2, tor26, and lefkada now in the default configuration.
4658 - Directory servers are more willing to send a 503 "busy" if they
4659 are near their write limit, especially for v1 directory requests.
4660 Now they can use their limited bandwidth for actual Tor traffic.
4661 - Clients track responses with status 503 from dirservers. After a
4662 dirserver has given us a 503, we try not to use it until an hour has
4663 gone by, or until we have no dirservers that haven't given us a 503.
4664 - When we get a 503 from a directory, and we're not a server, we don't
4665 count the failure against the total number of failures allowed
4666 for the thing we're trying to download.
4667 - Report X-Your-Address-Is correctly from tunneled directory
4668 connections; don't report X-Your-Address-Is when it's an internal
4669 address; and never believe reported remote addresses when they're
4671 - Protect against an unlikely DoS attack on directory servers.
4672 - Add a BadDirectory flag to network status docs so that authorities
4673 can (eventually) tell clients about caches they believe to be
4676 o Minor features (controller):
4677 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
4678 - Reimplement GETINFO so that info/names stays in sync with the
4680 - Implement "GETINFO fingerprint".
4681 - Implement "SETEVENTS GUARD" so controllers can get updates on
4682 entry guard status as it changes.
4684 o Minor features (clean up obsolete pieces):
4685 - Remove some options that have been deprecated since at least
4686 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
4687 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
4689 - We no longer look for identity and onion keys in "identity.key" and
4690 "onion.key" -- these were replaced by secret_id_key and
4691 secret_onion_key in 0.0.8pre1.
4692 - We no longer require unrecognized directory entries to be
4695 o Major bugfixes (security):
4696 - Stop sending the HttpProxyAuthenticator string to directory
4697 servers when directory connections are tunnelled through Tor.
4698 - Clients no longer store bandwidth history in the state file.
4699 - Do not log introduction points for hidden services if SafeLogging
4701 - When generating bandwidth history, round down to the nearest
4702 1k. When storing accounting data, round up to the nearest 1k.
4703 - When we're running as a server, remember when we last rotated onion
4704 keys, so that we will rotate keys once they're a week old even if
4705 we never stay up for a week ourselves.
4707 o Major bugfixes (other):
4708 - Fix a longstanding bug in eventdns that prevented the count of
4709 timed-out resolves from ever being reset. This bug caused us to
4710 give up on a nameserver the third time it timed out, and try it
4711 10 seconds later... and to give up on it every time it timed out
4713 - Take out the '5 second' timeout from the connection retry
4714 schedule. Now the first connect attempt will wait a full 10
4715 seconds before switching to a new circuit. Perhaps this will help
4716 a lot. Based on observations from Mike Perry.
4717 - Fix a bug on the Windows implementation of tor_mmap_file() that
4718 would prevent the cached-routers file from ever loading. Reported
4722 - Fix an assert failure when a directory authority sets
4723 AuthDirRejectUnlisted and then receives a descriptor from an
4724 unlisted router. Reported by seeess.
4725 - Avoid a double-free when parsing malformed DirServer lines.
4726 - Fix a bug when a BSD-style PF socket is first used. Patch from
4728 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
4729 to resolve an address at a given exit node even when they ask for
4731 - Servers no longer ever list themselves in their "family" line,
4732 even if configured to do so. This makes it easier to configure
4733 family lists conveniently.
4734 - When running as a server, don't fall back to 127.0.0.1 when no
4735 nameservers are configured in /etc/resolv.conf; instead, make the
4736 user fix resolv.conf or specify nameservers explicitly. (Resolves
4738 - Stop accepting certain malformed ports in configured exit policies.
4739 - Don't re-write the fingerprint file every restart, unless it has
4741 - Stop warning when a single nameserver fails: only warn when _all_ of
4742 our nameservers have failed. Also, when we only have one nameserver,
4743 raise the threshold for deciding that the nameserver is dead.
4744 - Directory authorities now only decide that routers are reachable
4745 if their identity keys are as expected.
4746 - When the user uses bad syntax in the Log config line, stop
4747 suggesting other bad syntax as a replacement.
4748 - Correctly detect ipv6 DNS capability on OpenBSD.
4750 o Minor bugfixes (controller):
4751 - Report the circuit number correctly in STREAM CLOSED events. Bug
4752 reported by Mike Perry.
4753 - Do not report bizarre values for results of accounting GETINFOs
4754 when the last second's write or read exceeds the allotted bandwidth.
4755 - Report "unrecognized key" rather than an empty string when the
4756 controller tries to fetch a networkstatus that doesn't exist.
4759 Changes in version 0.1.1.26 - 2006-12-14
4760 o Security bugfixes:
4761 - Stop sending the HttpProxyAuthenticator string to directory
4762 servers when directory connections are tunnelled through Tor.
4763 - Clients no longer store bandwidth history in the state file.
4764 - Do not log introduction points for hidden services if SafeLogging
4768 - Fix an assert failure when a directory authority sets
4769 AuthDirRejectUnlisted and then receives a descriptor from an
4770 unlisted router (reported by seeess).
4773 Changes in version 0.1.2.4-alpha - 2006-12-03
4775 - Add support for using natd; this allows FreeBSDs earlier than
4776 5.1.2 to have ipfw send connections through Tor without using
4777 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
4780 - Make all connections to addresses of the form ".noconnect"
4781 immediately get closed. This lets application/controller combos
4782 successfully test whether they're talking to the same Tor by
4783 watching for STREAM events.
4784 - Make cross.sh cross-compilation script work even when autogen.sh
4785 hasn't been run. (Patch from Michael Mohr.)
4786 - Statistics dumped by -USR2 now include a breakdown of public key
4787 operations, for profiling.
4790 - Fix a major leak when directory authorities parse their
4791 approved-routers list, a minor memory leak when we fail to pick
4792 an exit node, and a few rare leaks on errors.
4793 - Handle TransPort connections even when the server sends data before
4794 the client sends data. Previously, the connection would just hang
4795 until the client sent data. (Patch from tup based on patch from
4797 - Avoid assert failure when our cached-routers file is empty on
4801 - Don't log spurious warnings when we see a circuit close reason we
4802 don't recognize; it's probably just from a newer version of Tor.
4803 - Have directory authorities allow larger amounts of drift in uptime
4804 without replacing the server descriptor: previously, a server that
4805 restarted every 30 minutes could have 48 "interesting" descriptors
4807 - Start linking to the Tor specification and Tor reference manual
4808 correctly in the Windows installer.
4809 - Add Vidalia to the OS X uninstaller script, so when we uninstall
4810 Tor/Privoxy we also uninstall Vidalia.
4811 - Resume building on Irix64, and fix a lot of warnings from its
4813 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
4814 when we're running as a client.
4817 Changes in version 0.1.1.25 - 2006-11-04
4819 - When a client asks us to resolve (rather than connect to)
4820 an address, and we have a cached answer, give them the cached
4821 answer. Previously, we would give them no answer at all.
4822 - We were building exactly the wrong circuits when we predict
4823 hidden service requirements, meaning Tor would have to build all
4824 its circuits on demand.
4825 - If none of our live entry guards have a high uptime, but we
4826 require a guard with a high uptime, try adding a new guard before
4827 we give up on the requirement. This patch should make long-lived
4828 connections more stable on average.
4829 - When testing reachability of our DirPort, don't launch new
4830 tests when there's already one in progress -- unreachable
4831 servers were stacking up dozens of testing streams.
4833 o Security bugfixes:
4834 - When the user sends a NEWNYM signal, clear the client-side DNS
4835 cache too. Otherwise we continue to act on previous information.
4838 - Avoid a memory corruption bug when creating a hash table for
4840 - Avoid possibility of controller-triggered crash when misusing
4841 certain commands from a v0 controller on platforms that do not
4842 handle printf("%s",NULL) gracefully.
4843 - Avoid infinite loop on unexpected controller input.
4844 - Don't log spurious warnings when we see a circuit close reason we
4845 don't recognize; it's probably just from a newer version of Tor.
4846 - Add Vidalia to the OS X uninstaller script, so when we uninstall
4847 Tor/Privoxy we also uninstall Vidalia.
4850 Changes in version 0.1.2.3-alpha - 2006-10-29
4852 - Prepare for servers to publish descriptors less often: never
4853 discard a descriptor simply for being too old until either it is
4854 recommended by no authorities, or until we get a better one for
4855 the same router. Make caches consider retaining old recommended
4856 routers for even longer.
4857 - If most authorities set a BadExit flag for a server, clients
4858 don't think of it as a general-purpose exit. Clients only consider
4859 authorities that advertise themselves as listing bad exits.
4860 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
4861 headers for content, so that we can work better in the presence of
4862 caching HTTP proxies.
4863 - Allow authorities to list nodes as bad exits by fingerprint or by
4866 o Minor features, controller:
4867 - Add a REASON field to CIRC events; for backward compatibility, this
4868 field is sent only to controllers that have enabled the extended
4869 event format. Also, add additional reason codes to explain why
4870 a given circuit has been destroyed or truncated. (Patches from
4872 - Add a REMOTE_REASON field to extended CIRC events to tell the
4873 controller about why a remote OR told us to close a circuit.
4874 - Stream events also now have REASON and REMOTE_REASON fields,
4875 working much like those for circuit events.
4876 - There's now a GETINFO ns/... field so that controllers can ask Tor
4877 about the current status of a router.
4878 - A new event type "NS" to inform a controller when our opinion of
4879 a router's status has changed.
4880 - Add a GETINFO events/names and GETINFO features/names so controllers
4881 can tell which events and features are supported.
4882 - A new CLEARDNSCACHE signal to allow controllers to clear the
4883 client-side DNS cache without expiring circuits.
4885 o Security bugfixes:
4886 - When the user sends a NEWNYM signal, clear the client-side DNS
4887 cache too. Otherwise we continue to act on previous information.
4890 - Avoid sending junk to controllers or segfaulting when a controller
4891 uses EVENT_NEW_DESC with verbose nicknames.
4892 - Stop triggering asserts if the controller tries to extend hidden
4893 service circuits (reported by mwenge).
4894 - Avoid infinite loop on unexpected controller input.
4895 - When the controller does a "GETINFO network-status", tell it
4896 about even those routers whose descriptors are very old, and use
4897 long nicknames where appropriate.
4898 - Change NT service functions to be loaded on demand. This lets us
4899 build with MinGW without breaking Tor for Windows 98 users.
4900 - Do DirPort reachability tests less often, since a single test
4901 chews through many circuits before giving up.
4902 - In the hidden service example in torrc.sample, stop recommending
4903 esoteric and discouraged hidden service options.
4904 - When stopping an NT service, wait up to 10 sec for it to actually
4905 stop. (Patch from Matt Edman; resolves bug 295.)
4906 - Fix handling of verbose nicknames with ORCONN controller events:
4907 make them show up exactly when requested, rather than exactly when
4909 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
4910 printing a duplicate "$" in the keys we send (reported by mwenge).
4911 - Correctly set maximum connection limit on Cygwin. (This time
4913 - Try to detect Windows correctly when cross-compiling.
4914 - Detect the size of the routers file correctly even if it is
4915 corrupted (on systems without mmap) or not page-aligned (on systems
4916 with mmap). This bug was harmless.
4917 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
4918 to open a stream fails; now we do in more cases. This should
4919 make clients able to find a good exit faster in some cases, since
4920 unhandleable requests will now get an error rather than timing out.
4921 - Resolve two memory leaks when rebuilding the on-disk router cache
4922 (reported by fookoowa).
4923 - Clean up minor code warnings suggested by the MIPSpro C compiler,
4924 and reported by some Centos users.
4925 - Controller signals now work on non-Unix platforms that don't define
4926 SIGUSR1 and SIGUSR2 the way we expect.
4927 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
4928 values before failing, and always enables eventdns.
4929 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
4930 Try to fix this in configure.in by checking for most functions
4931 before we check for libevent.
4934 Changes in version 0.1.2.2-alpha - 2006-10-07
4936 - Make our async eventdns library on-by-default for Tor servers,
4937 and plan to deprecate the separate dnsworker threads.
4938 - Add server-side support for "reverse" DNS lookups (using PTR
4939 records so clients can determine the canonical hostname for a given
4940 IPv4 address). Only supported by servers using eventdns; servers
4941 now announce in their descriptors whether they support eventdns.
4942 - Specify and implement client-side SOCKS5 interface for reverse DNS
4943 lookups (see doc/socks-extensions.txt).
4944 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
4945 connect to directory servers through Tor. Previously, clients needed
4946 to find Tor exits to make private connections to directory servers.
4947 - Avoid choosing Exit nodes for entry or middle hops when the
4948 total bandwidth available from non-Exit nodes is much higher than
4949 the total bandwidth available from Exit nodes.
4950 - Workaround for name servers (like Earthlink's) that hijack failing
4951 DNS requests and replace the no-such-server answer with a "helpful"
4952 redirect to an advertising-driven search portal. Also work around
4953 DNS hijackers who "helpfully" decline to hijack known-invalid
4954 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
4955 lets you turn it off.
4956 - Send out a burst of long-range padding cells once we've established
4957 that we're reachable. Spread them over 4 circuits, so hopefully
4958 a few will be fast. This exercises our bandwidth and bootstraps
4959 us into the directory more quickly.
4961 o New/improved config options:
4962 - Add new config option "ResolvConf" to let the server operator
4963 choose an alternate resolve.conf file when using eventdns.
4964 - Add an "EnforceDistinctSubnets" option to control our "exclude
4965 servers on the same /16" behavior. It's still on by default; this
4966 is mostly for people who want to operate private test networks with
4967 all the machines on the same subnet.
4968 - If one of our entry guards is on the ExcludeNodes list, or the
4969 directory authorities don't think it's a good guard, treat it as
4970 if it were unlisted: stop using it as a guard, and throw it off
4971 the guards list if it stays that way for a long time.
4972 - Allow directory authorities to be marked separately as authorities
4973 for the v1 directory protocol, the v2 directory protocol, and
4974 as hidden service directories, to make it easier to retire old
4975 authorities. V1 authorities should set "HSAuthoritativeDir 1"
4976 to continue being hidden service authorities too.
4977 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
4979 o Minor features, controller:
4980 - Fix CIRC controller events so that controllers can learn the
4981 identity digests of non-Named servers used in circuit paths.
4982 - Let controllers ask for more useful identifiers for servers. Instead
4983 of learning identity digests for un-Named servers and nicknames
4984 for Named servers, the new identifiers include digest, nickname,
4985 and indication of Named status. Off by default; see control-spec.txt
4986 for more information.
4987 - Add a "getinfo address" controller command so it can display Tor's
4988 best guess to the user.
4989 - New controller event to alert the controller when our server
4990 descriptor has changed.
4991 - Give more meaningful errors on controller authentication failure.
4993 o Minor features, other:
4994 - When asked to resolve a hostname, don't use non-exit servers unless
4995 requested to do so. This allows servers with broken DNS to be
4996 useful to the network.
4997 - Divide eventdns log messages into warn and info messages.
4998 - Reserve the nickname "Unnamed" for routers that can't pick
4999 a hostname: any router can call itself Unnamed; directory
5000 authorities will never allocate Unnamed to any particular router;
5001 clients won't believe that any router is the canonical Unnamed.
5002 - Only include function names in log messages for info/debug messages.
5003 For notice/warn/err, the content of the message should be clear on
5004 its own, and printing the function name only confuses users.
5005 - Avoid some false positives during reachability testing: don't try
5006 to test via a server that's on the same /24 as us.
5007 - If we fail to build a circuit to an intended enclave, and it's
5008 not mandatory that we use that enclave, stop wanting it.
5009 - When eventdns is enabled, allow multithreaded builds on NetBSD and
5010 OpenBSD. (We had previously disabled threads on these platforms
5011 because they didn't have working thread-safe resolver functions.)
5013 o Major bugfixes, anonymity/security:
5014 - If a client asked for a server by name, and there's a named server
5015 in our network-status but we don't have its descriptor yet, we
5016 could return an unnamed server instead.
5017 - Fix NetBSD bug that could allow someone to force uninitialized RAM
5018 to be sent to a server's DNS resolver. This only affects NetBSD
5019 and other platforms that do not bounds-check tolower().
5020 - Reject (most) attempts to use Tor circuits with length one. (If
5021 many people start using Tor as a one-hop proxy, exit nodes become
5022 a more attractive target for compromise.)
5023 - Just because your DirPort is open doesn't mean people should be
5024 able to remotely teach you about hidden service descriptors. Now
5025 only accept rendezvous posts if you've got HSAuthoritativeDir set.
5027 o Major bugfixes, other:
5028 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
5029 - When a client asks the server to resolve (not connect to)
5030 an address, and it has a cached answer, give them the cached answer.
5031 Previously, the server would give them no answer at all.
5032 - Allow really slow clients to not hang up five minutes into their
5033 directory downloads (suggested by Adam J. Richter).
5034 - We were building exactly the wrong circuits when we anticipated
5035 hidden service requirements, meaning Tor would have to build all
5036 its circuits on demand.
5037 - Avoid crashing when we mmap a router cache file of size 0.
5038 - When testing reachability of our DirPort, don't launch new
5039 tests when there's already one in progress -- unreachable
5040 servers were stacking up dozens of testing streams.
5042 o Minor bugfixes, correctness:
5043 - If we're a directory mirror and we ask for "all" network status
5044 documents, we would discard status documents from authorities
5046 - Avoid a memory corruption bug when creating a hash table for
5048 - Avoid controller-triggered crash when misusing certain commands
5049 from a v0 controller on platforms that do not handle
5050 printf("%s",NULL) gracefully.
5051 - Don't crash when a controller sends a third argument to an
5052 "extendcircuit" request.
5053 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
5054 response; fix error code when "getinfo dir/status/" fails.
5055 - Avoid crash when telling controller stream-status and a stream
5057 - Patch from Adam Langley to fix assert() in eventdns.c.
5058 - Fix a debug log message in eventdns to say "X resolved to Y"
5059 instead of "X resolved to X".
5060 - Make eventdns give strings for DNS errors, not just error numbers.
5061 - Track unreachable entry guards correctly: don't conflate
5062 'unreachable by us right now' with 'listed as down by the directory
5063 authorities'. With the old code, if a guard was unreachable by
5064 us but listed as running, it would clog our guard list forever.
5065 - Behave correctly in case we ever have a network with more than
5066 2GB/s total advertised capacity.
5067 - Make TrackExitHosts case-insensitive, and fix the behavior of
5068 ".suffix" TrackExitHosts items to avoid matching in the middle of
5070 - Finally fix the openssl warnings from newer gccs that believe that
5071 ignoring a return value is okay, but casting a return value and
5072 then ignoring it is a sign of madness.
5073 - Prevent the contrib/exitlist script from printing the same
5074 result more than once.
5075 - Patch from Steve Hildrey: Generate network status correctly on
5076 non-versioning dirservers.
5077 - Don't listen to the X-Your-Address-Is hint if you did the lookup
5078 via Tor; otherwise you'll think you're the exit node's IP address.
5080 o Minor bugfixes, performance:
5081 - Two small performance improvements on parsing descriptors.
5082 - Major performance improvement on inserting descriptors: change
5083 algorithm from O(n^2) to O(n).
5084 - Make the common memory allocation path faster on machines where
5085 malloc(0) returns a pointer.
5086 - Start remembering X-Your-Address-Is directory hints even if you're
5087 a client, so you can become a server more smoothly.
5088 - Avoid duplicate entries on MyFamily line in server descriptor.
5090 o Packaging, features:
5091 - Remove architecture from OS X builds. The official builds are
5092 now universal binaries.
5093 - The Debian package now uses --verify-config when (re)starting,
5094 to distinguish configuration errors from other errors.
5095 - Update RPMs to require libevent 1.1b.
5097 o Packaging, bugfixes:
5098 - Patches so Tor builds with MinGW on Windows.
5099 - Patches so Tor might run on Cygwin again.
5100 - Resume building on non-gcc compilers and ancient gcc. Resume
5101 building with the -O0 compile flag. Resume building cleanly on
5103 - Run correctly on OS X platforms with case-sensitive filesystems.
5104 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
5105 - Add autoconf checks so Tor can build on Solaris x86 again.
5108 - Documented (and renamed) ServerDNSSearchDomains and
5109 ServerDNSResolvConfFile options.
5110 - Be clearer that the *ListenAddress directives can be repeated
5114 Changes in version 0.1.1.24 - 2006-09-29
5116 - Allow really slow clients to not hang up five minutes into their
5117 directory downloads (suggested by Adam J. Richter).
5118 - Fix major performance regression from 0.1.0.x: instead of checking
5119 whether we have enough directory information every time we want to
5120 do something, only check when the directory information has changed.
5121 This should improve client CPU usage by 25-50%.
5122 - Don't crash if, after a server has been running for a while,
5123 it can't resolve its hostname.
5126 - Allow Tor to start when RunAsDaemon is set but no logs are set.
5127 - Don't crash when the controller receives a third argument to an
5128 "extendcircuit" request.
5129 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
5130 response; fix error code when "getinfo dir/status/" fails.
5131 - Fix configure.in to not produce broken configure files with
5132 more recent versions of autoconf. Thanks to Clint for his auto*
5134 - Fix security bug on NetBSD that could allow someone to force
5135 uninitialized RAM to be sent to a server's DNS resolver. This
5136 only affects NetBSD and other platforms that do not bounds-check
5138 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
5139 methods: these are known to be buggy.
5140 - If we're a directory mirror and we ask for "all" network status
5141 documents, we would discard status documents from authorities
5145 Changes in version 0.1.2.1-alpha - 2006-08-27
5147 - Add "eventdns" async dns library from Adam Langley, tweaked to
5148 build on OSX and Windows. Only enabled if you pass the
5149 --enable-eventdns argument to configure.
5150 - Allow servers with no hostname or IP address to learn their
5151 IP address by asking the directory authorities. This code only
5152 kicks in when you would normally have exited with a "no address"
5153 error. Nothing's authenticated, so use with care.
5154 - Rather than waiting a fixed amount of time between retrying
5155 application connections, we wait only 5 seconds for the first,
5156 10 seconds for the second, and 15 seconds for each retry after
5157 that. Hopefully this will improve the expected user experience.
5158 - Patch from Tup to add support for transparent AP connections:
5159 this basically bundles the functionality of trans-proxy-tor
5160 into the Tor mainline. Now hosts with compliant pf/netfilter
5161 implementations can redirect TCP connections straight to Tor
5162 without diverting through SOCKS. Needs docs.
5163 - Busy directory servers save lots of memory by spooling server
5164 descriptors, v1 directories, and v2 networkstatus docs to buffers
5165 as needed rather than en masse. Also mmap the cached-routers
5166 files, so we don't need to keep the whole thing in memory too.
5167 - Automatically avoid picking more than one node from the same
5168 /16 network when constructing a circuit.
5169 - Revise and clean up the torrc.sample that we ship with; add
5170 a section for BandwidthRate and BandwidthBurst.
5173 - Split circuit_t into origin_circuit_t and or_circuit_t, and
5174 split connection_t into edge, or, dir, control, and base structs.
5175 These will save quite a bit of memory on busy servers, and they'll
5176 also help us track down bugs in the code and bugs in the spec.
5177 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
5178 or later. Log when we are doing this, so we can diagnose it when
5179 it fails. (Also, recommend libevent 1.1b for kqueue and
5180 win32 methods; deprecate libevent 1.0b harder; make libevent
5181 recommendation system saner.)
5182 - Start being able to build universal binaries on OS X (thanks
5184 - Export the default exit policy via the control port, so controllers
5185 don't need to guess what it is / will be later.
5186 - Add a man page entry for ProtocolWarnings.
5187 - Add TestVia config option to the man page.
5188 - Remove even more protocol-related warnings from Tor server logs,
5189 such as bad TLS handshakes and malformed begin cells.
5190 - Stop fetching descriptors if you're not a dir mirror and you
5191 haven't tried to establish any circuits lately. [This currently
5192 causes some dangerous behavior, because when you start up again
5193 you'll use your ancient server descriptors.]
5194 - New DirPort behavior: if you have your dirport set, you download
5195 descriptors aggressively like a directory mirror, whether or not
5197 - Get rid of the router_retry_connections notion. Now routers
5198 no longer try to rebuild long-term connections to directory
5199 authorities, and directory authorities no longer try to rebuild
5200 long-term connections to all servers. We still don't hang up
5201 connections in these two cases though -- we need to look at it
5202 more carefully to avoid flapping, and we likely need to wait til
5203 0.1.1.x is obsolete.
5204 - Drop compatibility with obsolete Tors that permit create cells
5205 to have the wrong circ_id_type.
5206 - Re-enable per-connection rate limiting. Get rid of the "OP
5207 bandwidth" concept. Lay groundwork for "bandwidth classes" --
5208 separate global buckets that apply depending on what sort of conn
5210 - Start publishing one minute or so after we find our ORPort
5211 to be reachable. This will help reduce the number of descriptors
5212 we have for ourselves floating around, since it's quite likely
5213 other things (e.g. DirPort) will change during that minute too.
5214 - Fork the v1 directory protocol into its own spec document,
5215 and mark dir-spec.txt as the currently correct (v2) spec.
5218 - When we find our DirPort to be reachable, publish a new descriptor
5219 so we'll tell the world (reported by pnx).
5220 - Publish a new descriptor after we hup/reload. This is important
5221 if our config has changed such that we'll want to start advertising
5222 our DirPort now, etc.
5223 - Allow Tor to start when RunAsDaemon is set but no logs are set.
5224 - When we have a state file we cannot parse, tell the user and
5225 move it aside. Now we avoid situations where the user starts
5226 Tor in 1904, Tor writes a state file with that timestamp in it,
5227 the user fixes her clock, and Tor refuses to start.
5228 - Fix configure.in to not produce broken configure files with
5229 more recent versions of autoconf. Thanks to Clint for his auto*
5231 - "tor --verify-config" now exits with -1(255) or 0 depending on
5232 whether the config options are bad or good.
5233 - Resolve bug 321 when using dnsworkers: append a period to every
5234 address we resolve at the exit node, so that we do not accidentally
5235 pick up local addresses, and so that failing searches are retried
5236 in the resolver search domains. (This is already solved for
5237 eventdns.) (This breaks Blossom servers for now.)
5238 - If we are using an exit enclave and we can't connect, e.g. because
5239 its webserver is misconfigured to not listen on localhost, then
5240 back off and try connecting from somewhere else before we fail.
5243 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
5244 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
5245 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
5246 when the IP address is mapped through MapAddress to a hostname.
5247 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
5248 useless IPv6 DNS resolves.
5249 - Patch suggested by Karsten Loesing: respond to SIGNAL command
5250 before we execute the signal, in case the signal shuts us down.
5251 - Clean up AllowInvalidNodes man page entry.
5252 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
5253 - Add more asserts to track down an assert error on a windows Tor
5254 server with connection_add being called with socket == -1.
5255 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
5256 - Fix misleading log messages: an entry guard that is "unlisted",
5257 as well as not known to be "down" (because we've never heard
5258 of it), is not therefore "up".
5259 - Remove code to special-case "-cvs" ending, since it has not
5260 actually mattered since 0.0.9.
5261 - Make our socks5 handling more robust to broken socks clients:
5262 throw out everything waiting on the buffer in between socks
5263 handshake phases, since they can't possibly (so the theory
5264 goes) have predicted what we plan to respond to them.
5267 Changes in version 0.1.1.23 - 2006-07-30
5269 - Fast Tor servers, especially exit nodes, were triggering asserts
5270 due to a bug in handling the list of pending DNS resolves. Some
5271 bugs still remain here; we're hunting them.
5272 - Entry guards could crash clients by sending unexpected input.
5273 - More fixes on reachability testing: if you find yourself reachable,
5274 then don't ever make any client requests (so you stop predicting
5275 circuits), then hup or have your clock jump, then later your IP
5276 changes, you won't think circuits are working, so you won't try to
5277 test reachability, so you won't publish.
5280 - Avoid a crash if the controller does a resetconf firewallports
5281 and then a setconf fascistfirewall=1.
5282 - Avoid an integer underflow when the dir authority decides whether
5283 a router is stable: we might wrongly label it stable, and compute
5284 a slightly wrong median stability, when a descriptor is published
5286 - Fix a place where we might trigger an assert if we can't build our
5287 own server descriptor yet.
5290 Changes in version 0.1.1.22 - 2006-07-05
5292 - Fix a big bug that was causing servers to not find themselves
5293 reachable if they changed IP addresses. Since only 0.1.1.22+
5294 servers can do reachability testing correctly, now we automatically
5295 make sure to test via one of these.
5296 - Fix to allow clients and mirrors to learn directory info from
5297 descriptor downloads that get cut off partway through.
5298 - Directory authorities had a bug in deciding if a newly published
5299 descriptor was novel enough to make everybody want a copy -- a few
5300 servers seem to be publishing new descriptors many times a minute.
5302 - Fix a rare bug that was causing some servers to complain about
5303 "closing wedged cpuworkers" and skip some circuit create requests.
5304 - Make the Exit flag in directory status documents actually work.
5307 Changes in version 0.1.1.21 - 2006-06-10
5308 o Crash and assert fixes from 0.1.1.20:
5309 - Fix a rare crash on Tor servers that have enabled hibernation.
5310 - Fix a seg fault on startup for Tor networks that use only one
5311 directory authority.
5312 - Fix an assert from a race condition that occurs on Tor servers
5313 while exiting, where various threads are trying to log that they're
5314 exiting, and delete the logs, at the same time.
5315 - Make our unit tests pass again on certain obscure platforms.
5318 - Add support for building SUSE RPM packages.
5319 - Speed up initial bootstrapping for clients: if we are making our
5320 first ever connection to any entry guard, then don't mark it down
5322 - When only one Tor server in the network is labelled as a guard,
5323 and we've already picked him, we would cycle endlessly picking him
5324 again, being unhappy about it, etc. Now we specifically exclude
5325 current guards when picking a new guard.
5326 - Servers send create cells more reliably after the TLS connection
5327 is established: we were sometimes forgetting to send half of them
5328 when we had more than one pending.
5329 - If we get a create cell that asks us to extend somewhere, but the
5330 Tor server there doesn't match the expected digest, we now send
5331 a destroy cell back, rather than silently doing nothing.
5332 - Make options->RedirectExit work again.
5333 - Make cookie authentication for the controller work again.
5334 - Stop being picky about unusual characters in the arguments to
5335 mapaddress. It's none of our business.
5336 - Add a new config option "TestVia" that lets you specify preferred
5337 middle hops to use for test circuits. Perhaps this will let me
5338 debug the reachability problems better.
5340 o Log / documentation fixes:
5341 - If we're a server and some peer has a broken TLS certificate, don't
5342 log about it unless ProtocolWarnings is set, i.e., we want to hear
5343 about protocol violations by others.
5344 - Fix spelling of VirtualAddrNetwork in man page.
5345 - Add a better explanation at the top of the autogenerated torrc file
5346 about what happened to our old torrc.
5349 Changes in version 0.1.1.20 - 2006-05-23
5351 - Downgrade a log severity where servers complain that they're
5353 - Avoid a compile warning on FreeBSD.
5354 - Remove string size limit on NEWDESC messages; solve bug 291.
5355 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
5356 more thoroughly when we're running on windows.
5359 Changes in version 0.1.1.19-rc - 2006-05-03
5361 - Regenerate our local descriptor if it's dirty and we try to use
5362 it locally (e.g. if it changes during reachability detection).
5363 - If we setconf our ORPort to 0, we continued to listen on the
5364 old ORPort and receive connections.
5365 - Avoid a second warning about machine/limits.h on Debian
5367 - Be willing to add our own routerinfo into the routerlist.
5368 Now authorities will include themselves in their directories
5369 and network-statuses.
5370 - Stop trying to upload rendezvous descriptors to every
5371 directory authority: only try the v1 authorities.
5372 - Servers no longer complain when they think they're not
5373 registered with the directory authorities. There were too many
5375 - Backport dist-rpm changes so rpms can be built without errors.
5378 - Implement an option, VirtualAddrMask, to set which addresses
5379 get handed out in response to mapaddress requests. This works
5380 around a bug in tsocks where 127.0.0.0/8 is never socksified.
5383 Changes in version 0.1.1.18-rc - 2006-04-10
5385 - Work harder to download live network-statuses from all the
5386 directory authorities we know about. Improve the threshold
5387 decision logic so we're more robust to edge cases.
5388 - When fetching rendezvous descriptors, we were willing to ask
5389 v2 authorities too, which would always return 404.
5392 - Stop listing down or invalid nodes in the v1 directory. This will
5393 reduce its bulk by about 1/3, and reduce load on directory
5395 - When deciding whether a router is Fast or Guard-worthy, consider
5396 his advertised BandwidthRate and not just the BandwidthCapacity.
5397 - No longer ship INSTALL and README files -- they are useless now.
5398 - Force rpmbuild to behave and honor target_cpu.
5399 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
5400 - Start to include translated versions of the tor-doc-*.html
5401 files, along with the screenshots. Still needs more work.
5402 - Start sending back 512 and 451 errors if mapaddress fails,
5403 rather than not sending anything back at all.
5404 - When we fail to bind or listen on an incoming or outgoing
5405 socket, we should close it before failing. otherwise we just
5406 leak it. (thanks to weasel for finding.)
5407 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
5408 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
5409 - Make NoPublish (even though deprecated) work again.
5410 - Fix a minor security flaw where a versioning auth dirserver
5411 could list a recommended version many times in a row to make
5412 clients more convinced that it's recommended.
5413 - Fix crash bug if there are two unregistered servers running
5414 with the same nickname, one of them is down, and you ask for
5415 them by nickname in your EntryNodes or ExitNodes. Also, try
5416 to pick the one that's running rather than an arbitrary one.
5417 - Fix an infinite loop we could hit if we go offline for too long.
5418 - Complain when we hit WSAENOBUFS on recv() or write() too.
5419 Perhaps this will help us hunt the bug.
5420 - If you're not a versioning dirserver, don't put the string
5421 "client-versions \nserver-versions \n" in your network-status.
5422 - Lower the minimum required number of file descriptors to 1000,
5423 so we can have some overhead for Valgrind on Linux, where the
5424 default ulimit -n is 1024.
5427 - Add tor.dizum.com as the fifth authoritative directory server.
5428 - Add a new config option FetchUselessDescriptors, off by default,
5429 for when you plan to run "exitlist" on your client and you want
5430 to know about even the non-running descriptors.
5433 Changes in version 0.1.1.17-rc - 2006-03-28
5435 - Clients and servers since 0.1.1.10-alpha have been expiring
5436 connections whenever they are idle for 5 minutes and they *do*
5437 have circuits on them. Oops. With this new version, clients will
5438 discard their previous entry guard choices and avoid choosing
5439 entry guards running these flawed versions.
5440 - Fix memory leak when uncompressing concatenated zlib streams. This
5441 was causing substantial leaks over time on Tor servers.
5442 - The v1 directory was including servers as much as 48 hours old,
5443 because that's how the new routerlist->routers works. Now only
5444 include them if they're 20 hours old or less.
5447 - Resume building on irix64, netbsd 2.0, etc.
5448 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
5450 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
5451 and it is confusing some users.
5452 - Mirrors stop caching the v1 directory so often.
5453 - Make the max number of old descriptors that a cache will hold
5454 rise with the number of directory authorities, so we can scale.
5455 - Change our win32 uname() hack to be more forgiving about what
5456 win32 versions it thinks it's found.
5459 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
5461 - When the controller's *setconf commands fail, collect an error
5462 message in a string and hand it back to the controller.
5463 - Make the v2 dir's "Fast" flag based on relative capacity, just
5464 like "Stable" is based on median uptime. Name everything in the
5465 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
5466 - Log server fingerprint on startup, so new server operators don't
5467 have to go hunting around their filesystem for it.
5468 - Return a robots.txt on our dirport to discourage google indexing.
5469 - Let the controller ask for GETINFO dir/status/foo so it can ask
5470 directly rather than connecting to the dir port. Only works when
5471 dirport is set for now.
5473 o New config options rather than constants in the code:
5474 - SocksTimeout: How long do we let a socks connection wait
5475 unattached before we fail it?
5476 - CircuitBuildTimeout: Cull non-open circuits that were born
5477 at least this many seconds ago.
5478 - CircuitIdleTimeout: Cull open clean circuits that were born
5479 at least this many seconds ago.
5482 Changes in version 0.1.1.16-rc - 2006-03-18
5483 o Bugfixes on 0.1.1.15-rc:
5484 - Fix assert when the controller asks to attachstream a connect-wait
5485 or resolve-wait stream.
5486 - Now do address rewriting when the controller asks us to attach
5487 to a particular circuit too. This will let Blossom specify
5488 "moria2.exit" without having to learn what moria2's IP address is.
5489 - Make the "tor --verify-config" command-line work again, so people
5490 can automatically check if their torrc will parse.
5491 - Authoritative dirservers no longer require an open connection from
5492 a server to consider him "reachable". We need this change because
5493 when we add new auth dirservers, old servers won't know not to
5495 - Let Tor build on Sun CC again.
5496 - Fix an off-by-one buffer size in dirserv.c that magically never
5497 hit our three authorities but broke sjmurdoch's own tor network.
5498 - If we as a directory mirror don't know of any v1 directory
5499 authorities, then don't try to cache any v1 directories.
5500 - Stop warning about unknown servers in our family when they are
5501 given as hex digests.
5502 - Stop complaining as quickly to the server operator that he
5503 hasn't registered his nickname/key binding.
5504 - Various cleanups so we can add new V2 Auth Dirservers.
5505 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
5506 reflect the updated flags in our v2 dir protocol.
5507 - Resume allowing non-printable characters for exit streams (both
5508 for connecting and for resolving). Now we tolerate applications
5509 that don't follow the RFCs. But continue to block malformed names
5512 o Bugfixes on 0.1.0.x:
5513 - Fix assert bug in close_logs(): when we close and delete logs,
5514 remove them all from the global "logfiles" list.
5515 - Fix minor integer overflow in calculating when we expect to use up
5516 our bandwidth allocation before hibernating.
5517 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
5518 there are multiple SSLs installed with different versions.
5519 - When we try to be a server and Address is not explicitly set and
5520 our hostname resolves to a private IP address, try to use an
5521 interface address if it has a public address. Now Windows machines
5522 that think of themselves as localhost can work by default.
5525 - Let the controller ask for GETINFO dir/server/foo so it can ask
5526 directly rather than connecting to the dir port.
5527 - Let the controller tell us about certain router descriptors
5528 that it doesn't want Tor to use in circuits. Implement
5529 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
5530 - New config option SafeSocks to reject all application connections
5531 using unsafe socks protocols. Defaults to off.
5534 Changes in version 0.1.1.15-rc - 2006-03-11
5535 o Bugfixes and cleanups:
5536 - When we're printing strings from the network, don't try to print
5537 non-printable characters. This protects us against shell escape
5538 sequence exploits, and also against attacks to fool humans into
5539 misreading their logs.
5540 - Fix a bug where Tor would fail to establish any connections if you
5541 left it off for 24 hours and then started it: we were happy with
5542 the obsolete network statuses, but they all referred to router
5543 descriptors that were too old to fetch, so we ended up with no
5544 valid router descriptors.
5545 - Fix a seg fault in the controller's "getinfo orconn-status"
5546 command while listing status on incoming handshaking connections.
5547 Introduce a status name "NEW" for these connections.
5548 - If we get a linelist or linelist_s config option from the torrc
5549 (e.g. ExitPolicy) and it has no value, warn and skip rather than
5550 silently resetting it to its default.
5551 - Don't abandon entry guards until they've been down or gone for
5553 - Cleaner and quieter log messages.
5556 - New controller signal NEWNYM that makes new application requests
5558 - Add a new circuit purpose 'controller' to let the controller ask
5559 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
5560 controller command to let you specify the purpose if you're
5561 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
5562 command to let you change a circuit's purpose after it's been
5564 - Accept "private:*" in routerdesc exit policies; not generated yet
5565 because older Tors do not understand it.
5566 - Add BSD-style contributed startup script "rc.subr" from Peter
5570 Changes in version 0.1.1.14-alpha - 2006-02-20
5571 o Bugfixes on 0.1.1.x:
5572 - Don't die if we ask for a stdout or stderr log (even implicitly)
5573 and we're set to RunAsDaemon -- just warn.
5574 - We still had a few bugs in the OR connection rotation code that
5575 caused directory servers to slowly aggregate connections to other
5576 fast Tor servers. This time for sure!
5577 - Make log entries on Win32 include the name of the function again.
5578 - We were treating a pair of exit policies if they were equal even
5579 if one said accept and the other said reject -- causing us to
5580 not always publish a new descriptor since we thought nothing
5582 - Retry pending server downloads as well as pending networkstatus
5583 downloads when we unexpectedly get a socks request.
5584 - We were ignoring the IS_FAST flag in the directory status,
5585 meaning we were willing to pick trivial-bandwidth nodes for "fast"
5587 - If the controller's SAVECONF command fails (e.g. due to file
5588 permissions), let the controller know that it failed.
5591 - If we're trying to be a Tor server and running Windows 95/98/ME
5592 as a server, explain that we'll likely crash.
5593 - When we're a server, a client asks for an old-style directory,
5594 and our write bucket is empty, don't give it to him. This way
5595 small servers can continue to serve the directory *sometimes*,
5596 without getting overloaded.
5597 - Compress exit policies even more -- look for duplicate lines
5599 - Clients now honor the "guard" flag in the router status when
5600 picking entry guards, rather than looking at is_fast or is_stable.
5601 - Retain unrecognized lines in $DATADIR/state file, so that we can
5602 be forward-compatible.
5603 - Generate 18.0.0.0/8 address policy format in descs when we can;
5604 warn when the mask is not reducible to a bit-prefix.
5605 - Let the user set ControlListenAddress in the torrc. This can be
5606 dangerous, but there are some cases (like a secured LAN) where it
5608 - Split ReachableAddresses into ReachableDirAddresses and
5609 ReachableORAddresses, so we can restrict Dir conns to port 80
5610 and OR conns to port 443.
5611 - Now we can target arch and OS in rpm builds (contributed by
5612 Phobos). Also make the resulting dist-rpm filename match the
5614 - New config options to help controllers: FetchServerDescriptors
5615 and FetchHidServDescriptors for whether to fetch server
5616 info and hidserv info or let the controller do it, and
5617 PublishServerDescriptor and PublishHidServDescriptors.
5618 - Also let the controller set the __AllDirActionsPrivate config
5619 option if you want all directory fetches/publishes to happen via
5620 Tor (it assumes your controller bootstraps your circuits).
5623 Changes in version 0.1.0.17 - 2006-02-17
5624 o Crash bugfixes on 0.1.0.x:
5625 - When servers with a non-zero DirPort came out of hibernation,
5626 sometimes they would trigger an assert.
5628 o Other important bugfixes:
5629 - On platforms that don't have getrlimit (like Windows), we were
5630 artificially constraining ourselves to a max of 1024
5631 connections. Now just assume that we can handle as many as 15000
5632 connections. Hopefully this won't cause other problems.
5634 o Backported features:
5635 - When we're a server, a client asks for an old-style directory,
5636 and our write bucket is empty, don't give it to him. This way
5637 small servers can continue to serve the directory *sometimes*,
5638 without getting overloaded.
5639 - Whenever you get a 503 in response to a directory fetch, try
5640 once more. This will become important once servers start sending
5641 503's whenever they feel busy.
5642 - Fetch a new directory every 120 minutes, not every 40 minutes.
5643 Now that we have hundreds of thousands of users running the old
5644 directory algorithm, it's starting to hurt a lot.
5645 - Bump up the period for forcing a hidden service descriptor upload
5646 from 20 minutes to 1 hour.
5649 Changes in version 0.1.1.13-alpha - 2006-02-09
5650 o Crashes in 0.1.1.x:
5651 - When you tried to setconf ORPort via the controller, Tor would
5652 crash. So people using TorCP to become a server were sad.
5653 - Solve (I hope) the stack-smashing bug that we were seeing on fast
5654 servers. The problem appears to be something do with OpenSSL's
5655 random number generation, or how we call it, or something. Let me
5656 know if the crashes continue.
5657 - Turn crypto hardware acceleration off by default, until we find
5658 somebody smart who can test it for us. (It appears to produce
5659 seg faults in at least some cases.)
5660 - Fix a rare assert error when we've tried all intro points for
5661 a hidden service and we try fetching the service descriptor again:
5662 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
5665 - Fix a major load balance bug: we were round-robining in 16 KB
5666 chunks, and servers with bandwidthrate of 20 KB, while downloading
5667 a 600 KB directory, would starve their other connections. Now we
5668 try to be a bit more fair.
5669 - Dir authorities and mirrors were never expiring the newest
5670 descriptor for each server, causing memory and directory bloat.
5671 - Fix memory-bloating and connection-bloating bug on servers: We
5672 were never closing any connection that had ever had a circuit on
5673 it, because we were checking conn->n_circuits == 0, yet we had a
5674 bug that let it go negative.
5675 - Make Tor work using squid as your http proxy again -- squid
5676 returns an error if you ask for a URL that's too long, and it uses
5677 a really generic error message. Plus, many people are behind a
5678 transparent squid so they don't even realize it.
5679 - On platforms that don't have getrlimit (like Windows), we were
5680 artificially constraining ourselves to a max of 1024
5681 connections. Now just assume that we can handle as many as 15000
5682 connections. Hopefully this won't cause other problems.
5683 - Add a new config option ExitPolicyRejectPrivate which defaults to
5684 1. This means all exit policies will begin with rejecting private
5685 addresses, unless the server operator explicitly turns it off.
5688 - Clients no longer download descriptors for non-running
5690 - Before we add new directory authorities, we should make it
5691 clear that only v1 authorities should receive/publish hidden
5692 service descriptors.
5695 - As soon as we've fetched some more directory info, immediately
5696 try to download more server descriptors. This way we don't have
5697 a 10 second pause during initial bootstrapping.
5698 - Remove even more loud log messages that the server operator can't
5700 - When we're running an obsolete or un-recommended version, make
5701 the log message more clear about what the problem is and what
5702 versions *are* still recommended.
5703 - Provide a more useful warn message when our onion queue gets full:
5704 the CPU is too slow or the exit policy is too liberal.
5705 - Don't warn when we receive a 503 from a dirserver/cache -- this
5706 will pave the way for them being able to refuse if they're busy.
5707 - When we fail to bind a listener, try to provide a more useful
5708 log message: e.g., "Is Tor already running?"
5709 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
5710 Goldberg can prove things about our handshake protocol more
5712 - MaxConn has been obsolete for a while now. Document the ConnLimit
5713 config option, which is a *minimum* number of file descriptors
5714 that must be available else Tor refuses to start.
5715 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
5716 if you log to syslog and want something other than LOG_DAEMON.
5717 - Make dirservers generate a separate "guard" flag to mean,
5718 "would make a good entry guard". Make clients parse it and vote
5719 on it. Not used by clients yet.
5720 - Implement --with-libevent-dir option to ./configure. Also, improve
5721 search techniques to find libevent, and use those for openssl too.
5722 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
5723 - Only start testing reachability once we've established a
5724 circuit. This will make startup on dirservers less noisy.
5725 - Don't try to upload hidden service descriptors until we have
5726 established a circuit.
5727 - Fix the controller's "attachstream 0" command to treat conn like
5728 it just connected, doing address remapping, handling .exit and
5729 .onion idioms, and so on. Now we're more uniform in making sure
5730 that the controller hears about new and closing connections.
5733 Changes in version 0.1.1.12-alpha - 2006-01-11
5734 o Bugfixes on 0.1.1.x:
5735 - The fix to close duplicate server connections was closing all
5736 Tor client connections if they didn't establish a circuit
5737 quickly enough. Oops.
5738 - Fix minor memory issue (double-free) that happened on exit.
5740 o Bugfixes on 0.1.0.x:
5741 - Tor didn't warn when it failed to open a log file.
5744 Changes in version 0.1.1.11-alpha - 2006-01-10
5745 o Crashes in 0.1.1.x:
5746 - Include all the assert/crash fixes from 0.1.0.16.
5747 - If you start Tor and then quit very quickly, there were some
5748 races that tried to free things that weren't allocated yet.
5749 - Fix a rare memory stomp if you're running hidden services.
5750 - Fix segfault when specifying DirServer in config without nickname.
5751 - Fix a seg fault when you finish connecting to a server but at
5752 that moment you dump his server descriptor.
5753 - Extendcircuit and Attachstream controller commands would
5754 assert/crash if you don't give them enough arguments.
5755 - Fix an assert error when we're out of space in the connection_list
5756 and we try to post a hidden service descriptor (reported by weasel).
5757 - If you specify a relative torrc path and you set RunAsDaemon in
5758 your torrc, then it chdir()'s to the new directory. If you HUP,
5759 it tries to load the new torrc location, fails, and exits.
5760 The fix: no longer allow a relative path to torrc using -f.
5763 - Implement "entry guards": automatically choose a handful of entry
5764 nodes and stick with them for all circuits. Only pick new guards
5765 when the ones you have are unsuitable, and if the old guards
5766 become suitable again, switch back. This will increase security
5767 dramatically against certain end-point attacks. The EntryNodes
5768 config option now provides some hints about which entry guards you
5769 want to use most; and StrictEntryNodes means to only use those.
5770 - New directory logic: download by descriptor digest, not by
5771 fingerprint. Caches try to download all listed digests from
5772 authorities; clients try to download "best" digests from caches.
5773 This avoids partitioning and isolating attacks better.
5774 - Make the "stable" router flag in network-status be the median of
5775 the uptimes of running valid servers, and make clients pay
5776 attention to the network-status flags. Thus the cutoff adapts
5777 to the stability of the network as a whole, making IRC, IM, etc
5778 connections more reliable.
5781 - Tor servers with dynamic IP addresses were needing to wait 18
5782 hours before they could start doing reachability testing using
5783 the new IP address and ports. This is because they were using
5784 the internal descriptor to learn what to test, yet they were only
5785 rebuilding the descriptor once they decided they were reachable.
5786 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
5787 to download certain server descriptors, throw them away, and then
5788 fetch them again after 30 minutes. Now mirrors throw away these
5789 server descriptors so clients can't get them.
5790 - We were leaving duplicate connections to other ORs open for a week,
5791 rather than closing them once we detect a duplicate. This only
5792 really affected authdirservers, but it affected them a lot.
5793 - Spread the authdirservers' reachability testing over the entire
5794 testing interval, so we don't try to do 500 TLS's at once every
5798 - If the network is down, and we try to connect to a conn because
5799 we have a circuit in mind, and we timeout (30 seconds) because the
5800 network never answers, we were expiring the circuit, but we weren't
5801 obsoleting the connection or telling the entry_guards functions.
5802 - Some Tor servers process billions of cells per day. These statistics
5803 need to be uint64_t's.
5804 - Check for integer overflows in more places, when adding elements
5805 to smartlists. This could possibly prevent a buffer overflow
5806 on malicious huge inputs. I don't see any, but I haven't looked
5808 - ReachableAddresses kept growing new "reject *:*" lines on every
5810 - When you "setconf log" via the controller, it should remove all
5811 logs. We were automatically adding back in a "log notice stdout".
5812 - Newly bootstrapped Tor networks couldn't establish hidden service
5813 circuits until they had nodes with high uptime. Be more tolerant.
5814 - We were marking servers down when they could not answer every piece
5815 of the directory request we sent them. This was far too harsh.
5816 - Fix the torify (tsocks) config file to not use Tor for localhost
5818 - Directory authorities now go to the proper authority when asking for
5819 a networkstatus, even when they want a compressed one.
5820 - Fix a harmless bug that was causing Tor servers to log
5821 "Got an end because of misc error, but we're not an AP. Closing."
5822 - Authorities were treating their own descriptor changes as cosmetic,
5823 meaning the descriptor available in the network-status and the
5824 descriptor that clients downloaded were different.
5825 - The OS X installer was adding a symlink for tor_resolve but
5826 the binary was called tor-resolve (reported by Thomas Hardly).
5827 - Workaround a problem with some http proxies where they refuse GET
5828 requests that specify "Content-Length: 0" (reported by Adrian).
5829 - Fix wrong log message when you add a "HiddenServiceNodes" config
5830 line without any HiddenServiceDir line (reported by Chris Thomas).
5833 - Write the TorVersion into the state file so we have a prayer of
5834 keeping forward and backward compatibility.
5835 - Revive the FascistFirewall config option rather than eliminating it:
5836 now it's a synonym for ReachableAddresses *:80,*:443.
5837 - Clients choose directory servers from the network status lists,
5838 not from their internal list of router descriptors. Now they can
5839 go to caches directly rather than needing to go to authorities
5841 - Directory authorities ignore router descriptors that have only
5842 cosmetic differences: do this for 0.1.0.x servers now too.
5843 - Add a new flag to network-status indicating whether the server
5844 can answer v2 directory requests too.
5845 - Authdirs now stop whining so loudly about bad descriptors that
5846 they fetch from other dirservers. So when there's a log complaint,
5847 it's for sure from a freshly uploaded descriptor.
5848 - Reduce memory requirements in our structs by changing the order
5850 - There used to be two ways to specify your listening ports in a
5851 server descriptor: on the "router" line and with a separate "ports"
5852 line. Remove support for the "ports" line.
5853 - New config option "AuthDirRejectUnlisted" for auth dirservers as
5854 a panic button: if we get flooded with unusable servers we can
5855 revert to only listing servers in the approved-routers file.
5856 - Auth dir servers can now mark a fingerprint as "!reject" or
5857 "!invalid" in the approved-routers file (as its nickname), to
5858 refuse descriptors outright or include them but marked as invalid.
5859 - Servers store bandwidth history across restarts/crashes.
5860 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
5861 get a better idea of why their circuits failed. Not used yet.
5862 - Directory mirrors now cache up to 16 unrecognized network-status
5863 docs. Now we can add new authdirservers and they'll be cached too.
5864 - When picking a random directory, prefer non-authorities if any
5866 - New controller option "getinfo desc/all-recent" to fetch the
5867 latest server descriptor for every router that Tor knows about.
5870 Changes in version 0.1.0.16 - 2006-01-02
5871 o Crash bugfixes on 0.1.0.x:
5872 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
5873 corrupting the heap, losing FDs, or crashing when we need to resize
5874 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
5875 - It turns out sparc64 platforms crash on unaligned memory access
5876 too -- so detect and avoid this.
5877 - Handle truncated compressed data correctly (by detecting it and
5879 - Fix possible-but-unlikely free(NULL) in control.c.
5880 - When we were closing connections, there was a rare case that
5881 stomped on memory, triggering seg faults and asserts.
5882 - Avoid potential infinite recursion when building a descriptor. (We
5883 don't know that it ever happened, but better to fix it anyway.)
5884 - We were neglecting to unlink marked circuits from soon-to-close OR
5885 connections, which caused some rare scribbling on freed memory.
5886 - Fix a memory stomping race bug when closing the joining point of two
5887 rendezvous circuits.
5888 - Fix an assert in time parsing found by Steven Murdoch.
5890 o Other bugfixes on 0.1.0.x:
5891 - When we're doing reachability testing, provide more useful log
5892 messages so the operator knows what to expect.
5893 - Do not check whether DirPort is reachable when we are suppressing
5894 advertising it because of hibernation.
5895 - When building with -static or on Solaris, we sometimes needed -ldl.
5896 - When we're deciding whether a stream has enough circuits around
5897 that can handle it, count the freshly dirty ones and not the ones
5898 that are so dirty they won't be able to handle it.
5899 - When we're expiring old circuits, we had a logic error that caused
5900 us to close new rendezvous circuits rather than old ones.
5901 - Give a more helpful log message when you try to change ORPort via
5902 the controller: you should upgrade Tor if you want that to work.
5903 - We were failing to parse Tor versions that start with "Tor ".
5904 - Tolerate faulty streams better: when a stream fails for reason
5905 exitpolicy, stop assuming that the router is lying about his exit
5906 policy. When a stream fails for reason misc, allow it to retry just
5907 as if it was resolvefailed. When a stream has failed three times,
5908 reset its failure count so we can try again and get all three tries.
5911 Changes in version 0.1.1.10-alpha - 2005-12-11
5912 o Correctness bugfixes on 0.1.0.x:
5913 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
5914 corrupting the heap, losing FDs, or crashing when we need to resize
5915 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
5916 - Stop doing the complex voodoo overkill checking for insecure
5917 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
5918 - When we were closing connections, there was a rare case that
5919 stomped on memory, triggering seg faults and asserts.
5920 - We were neglecting to unlink marked circuits from soon-to-close OR
5921 connections, which caused some rare scribbling on freed memory.
5922 - When we're deciding whether a stream has enough circuits around
5923 that can handle it, count the freshly dirty ones and not the ones
5924 that are so dirty they won't be able to handle it.
5925 - Recover better from TCP connections to Tor servers that are
5926 broken but don't tell you (it happens!); and rotate TLS
5927 connections once a week.
5928 - When we're expiring old circuits, we had a logic error that caused
5929 us to close new rendezvous circuits rather than old ones.
5930 - Fix a scary-looking but apparently harmless bug where circuits
5931 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
5932 servers, and never switch to state CIRCUIT_STATE_OPEN.
5933 - When building with -static or on Solaris, we sometimes needed to
5935 - Give a useful message when people run Tor as the wrong user,
5936 rather than telling them to start chowning random directories.
5937 - We were failing to inform the controller about new .onion streams.
5939 o Security bugfixes on 0.1.0.x:
5940 - Refuse server descriptors if the fingerprint line doesn't match
5941 the included identity key. Tor doesn't care, but other apps (and
5942 humans) might actually be trusting the fingerprint line.
5943 - We used to kill the circuit when we receive a relay command we
5944 don't recognize. Now we just drop it.
5945 - Start obeying our firewall options more rigorously:
5946 . If we can't get to a dirserver directly, try going via Tor.
5947 . Don't ever try to connect (as a client) to a place our
5948 firewall options forbid.
5949 . If we specify a proxy and also firewall options, obey the
5950 firewall options even when we're using the proxy: some proxies
5951 can only proxy to certain destinations.
5952 - Fix a bug found by Lasse Overlier: when we were making internal
5953 circuits (intended to be cannibalized later for rendezvous and
5954 introduction circuits), we were picking them so that they had
5955 useful exit nodes. There was no need for this, and it actually
5956 aids some statistical attacks.
5957 - Start treating internal circuits and exit circuits separately.
5958 It's important to keep them separate because internal circuits
5959 have their last hops picked like middle hops, rather than like
5960 exit hops. So exiting on them will break the user's expectations.
5962 o Bugfixes on 0.1.1.x:
5963 - Take out the mis-feature where we tried to detect IP address
5964 flapping for people with DynDNS, and chose not to upload a new
5965 server descriptor sometimes.
5966 - Try to be compatible with OpenSSL 0.9.6 again.
5967 - Log fix: when the controller is logging about .onion addresses,
5968 sometimes it didn't include the ".onion" part of the address.
5969 - Don't try to modify options->DirServers internally -- if the
5970 user didn't specify any, just add the default ones directly to
5971 the trusted dirserver list. This fixes a bug where people running
5972 controllers would use SETCONF on some totally unrelated config
5973 option, and Tor would start yelling at them about changing their
5975 - Let the controller's redirectstream command specify a port, in
5976 case the controller wants to change that too.
5977 - When we requested a pile of server descriptors, we sometimes
5978 accidentally launched a duplicate request for the first one.
5979 - Bugfix for trackhostexits: write down the fingerprint of the
5980 chosen exit, not its nickname, because the chosen exit might not
5982 - When parsing foo.exit, if foo is unknown, and we are leaving
5983 circuits unattached, set the chosen_exit field and leave the
5984 address empty. This matters because controllers got confused
5986 - Directory authorities no longer try to download server
5987 descriptors that they know they will reject.
5989 o Features and updates:
5990 - Replace balanced trees with hash tables: this should make stuff
5991 significantly faster.
5992 - Resume using the AES counter-mode implementation that we ship,
5993 rather than OpenSSL's. Ours is significantly faster.
5994 - Many other CPU and memory improvements.
5995 - Add a new config option FastFirstHopPK (on by default) so clients
5996 do a trivial crypto handshake for their first hop, since TLS has
5997 already taken care of confidentiality and authentication.
5998 - Add a new config option TestSocks so people can see if their
5999 applications are using socks4, socks4a, socks5-with-ip, or
6000 socks5-with-hostname. This way they don't have to keep mucking
6001 with tcpdump and wondering if something got cached somewhere.
6002 - Warn when listening on a public address for socks. I suspect a
6003 lot of people are setting themselves up as open socks proxies,
6004 and they have no idea that jerks on the Internet are using them,
6005 since they simply proxy the traffic into the Tor network.
6006 - Add "private:*" as an alias in configuration for policies. Now
6007 you can simplify your exit policy rather than needing to list
6008 every single internal or nonroutable network space.
6009 - Add a new controller event type that allows controllers to get
6010 all server descriptors that were uploaded to a router in its role
6011 as authoritative dirserver.
6012 - Start shipping socks-extensions.txt, tor-doc-unix.html,
6013 tor-doc-server.html, and stylesheet.css in the tarball.
6014 - Stop shipping tor-doc.html in the tarball.
6017 Changes in version 0.1.1.9-alpha - 2005-11-15
6018 o Usability improvements:
6019 - Start calling it FooListenAddress rather than FooBindAddress,
6020 since few of our users know what it means to bind an address
6022 - Reduce clutter in server logs. We're going to try to make
6023 them actually usable now. New config option ProtocolWarnings that
6024 lets you hear about how _other Tors_ are breaking the protocol. Off
6026 - Divide log messages into logging domains. Once we put some sort
6027 of interface on this, it will let people looking at more verbose
6028 log levels specify the topics they want to hear more about.
6029 - Make directory servers return better http 404 error messages
6030 instead of a generic "Servers unavailable".
6031 - Check for even more Windows version flags when writing the platform
6032 string in server descriptors, and note any we don't recognize.
6033 - Clean up more of the OpenSSL memory when exiting, so we can detect
6034 memory leaks better.
6035 - Make directory authorities be non-versioning, non-naming by
6036 default. Now we can add new directory servers without requiring
6037 their operators to pay close attention.
6038 - When logging via syslog, include the pid whenever we provide
6039 a log entry. Suggested by Todd Fries.
6041 o Performance improvements:
6042 - Directory servers now silently throw away new descriptors that
6043 haven't changed much if the timestamps are similar. We do this to
6044 tolerate older Tor servers that upload a new descriptor every 15
6045 minutes. (It seemed like a good idea at the time.)
6046 - Inline bottleneck smartlist functions; use fast versions by default.
6047 - Add a "Map from digest to void*" abstraction digestmap_t so we
6048 can do less hex encoding/decoding. Use it in router_get_by_digest()
6049 to resolve a performance bottleneck.
6050 - Allow tor_gzip_uncompress to extract as much as possible from
6051 truncated compressed data. Try to extract as many
6052 descriptors as possible from truncated http responses (when
6053 DIR_PURPOSE_FETCH_ROUTERDESC).
6054 - Make circ->onionskin a pointer, not a static array. moria2 was using
6055 125000 circuit_t's after it had been up for a few weeks, which
6056 translates to 20+ megs of wasted space.
6057 - The private half of our EDH handshake keys are now chosen out
6058 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
6060 o Security improvements:
6061 - Start making directory caches retain old routerinfos, so soon
6062 clients can start asking by digest of descriptor rather than by
6063 fingerprint of server.
6064 - Add half our entropy from RAND_poll in OpenSSL. This knows how
6065 to use egd (if present), openbsd weirdness (if present), vms/os2
6066 weirdness (if we ever port there), and more in the future.
6068 o Bugfixes on 0.1.0.x:
6069 - Do round-robin writes of at most 16 kB per write. This might be
6070 more fair on loaded Tor servers, and it might resolve our Windows
6071 crash bug. It might also slow things down.
6072 - Our TLS handshakes were generating a single public/private
6073 keypair for the TLS context, rather than making a new one for
6074 each new connections. Oops. (But we were still rotating them
6075 periodically, so it's not so bad.)
6076 - When we were cannibalizing a circuit with a particular exit
6077 node in mind, we weren't checking to see if that exit node was
6078 already present earlier in the circuit. Oops.
6079 - When a Tor server's IP changes (e.g. from a dyndns address),
6080 upload a new descriptor so clients will learn too.
6081 - Really busy servers were keeping enough circuits open on stable
6082 connections that they were wrapping around the circuit_id
6083 space. (It's only two bytes.) This exposed a bug where we would
6084 feel free to reuse a circuit_id even if it still exists but has
6085 been marked for close. Try to fix this bug. Some bug remains.
6086 - If we would close a stream early (e.g. it asks for a .exit that
6087 we know would refuse it) but the LeaveStreamsUnattached config
6088 option is set by the controller, then don't close it.
6090 o Bugfixes on 0.1.1.8-alpha:
6091 - Fix a big pile of memory leaks, some of them serious.
6092 - Do not try to download a routerdesc if we would immediately reject
6094 - Resume inserting a newline between all router descriptors when
6095 generating (old style) signed directories, since our spec says
6097 - When providing content-type application/octet-stream for
6098 server descriptors using .z, we were leaving out the
6099 content-encoding header. Oops. (Everything tolerated this just
6100 fine, but that doesn't mean we need to be part of the problem.)
6101 - Fix a potential seg fault in getconf and getinfo using version 1
6102 of the controller protocol.
6103 - Avoid crash: do not check whether DirPort is reachable when we
6104 are suppressing it because of hibernation.
6105 - Make --hash-password not crash on exit.
6108 Changes in version 0.1.1.8-alpha - 2005-10-07
6109 o New features (major):
6110 - Clients don't download or use the directory anymore. Now they
6111 download and use network-statuses from the trusted dirservers,
6112 and fetch individual server descriptors as needed from mirrors.
6113 See dir-spec.txt for all the gory details.
6114 - Be more conservative about whether to advertise our DirPort.
6115 The main change is to not advertise if we're running at capacity
6116 and either a) we could hibernate or b) our capacity is low and
6117 we're using a default DirPort.
6118 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
6120 o New features (minor):
6121 - Try to be smart about when to retry network-status and
6122 server-descriptor fetches. Still needs some tuning.
6123 - Stop parsing, storing, or using running-routers output (but
6124 mirrors still cache and serve it).
6125 - Consider a threshold of versioning dirservers (dirservers who have
6126 an opinion about which Tor versions are still recommended) before
6127 deciding whether to warn the user that he's obsolete.
6128 - Dirservers can now reject/invalidate by key and IP, with the
6129 config options "AuthDirInvalid" and "AuthDirReject". This is
6130 useful since currently we automatically list servers as running
6131 and usable even if we know they're jerks.
6132 - Provide dire warnings to any users who set DirServer; move it out
6133 of torrc.sample and into torrc.complete.
6134 - Add MyFamily to torrc.sample in the server section.
6135 - Add nicknames to the DirServer line, so we can refer to them
6136 without requiring all our users to memorize their IP addresses.
6137 - When we get an EOF or a timeout on a directory connection, note
6138 how many bytes of serverdesc we are dropping. This will help
6139 us determine whether it is smart to parse incomplete serverdesc
6141 - Add a new function to "change pseudonyms" -- that is, to stop
6142 using any currently-dirty circuits for new streams, so we don't
6143 link new actions to old actions. Currently it's only called on
6144 HUP (or SIGNAL RELOAD).
6145 - On sighup, if UseHelperNodes changed to 1, use new circuits.
6146 - Start using RAND_bytes rather than RAND_pseudo_bytes from
6147 OpenSSL. Also, reseed our entropy every hour, not just at
6148 startup. And entropy in 512-bit chunks, not 160-bit chunks.
6150 o Fixes on 0.1.1.7-alpha:
6151 - Nobody ever implemented EVENT_ADDRMAP for control protocol
6152 version 0, so don't let version 0 controllers ask for it.
6153 - If you requested something with too many newlines via the
6154 v1 controller protocol, you could crash tor.
6155 - Fix a number of memory leaks, including some pretty serious ones.
6156 - Re-enable DirPort testing again, so Tor servers will be willing
6157 to advertise their DirPort if it's reachable.
6158 - On TLS handshake, only check the other router's nickname against
6159 its expected nickname if is_named is set.
6161 o Fixes forward-ported from 0.1.0.15:
6162 - Don't crash when we don't have any spare file descriptors and we
6163 try to spawn a dns or cpu worker.
6164 - Make the numbers in read-history and write-history into uint64s,
6165 so they don't overflow and publish negatives in the descriptor.
6168 - For the OS X package's modified privoxy config file, comment
6169 out the "logfile" line so we don't log everything passed
6171 - We were whining about using socks4 or socks5-with-local-lookup
6172 even when it's an IP in the "virtual" range we designed exactly
6174 - We were leaking some memory every time the client changes IPs.
6175 - Never call free() on tor_malloc()d memory. This will help us
6176 use dmalloc to detect memory leaks.
6177 - Check for named servers when looking them up by nickname;
6178 warn when we'recalling a non-named server by its nickname;
6179 don't warn twice about the same name.
6180 - Try to list MyFamily elements by key, not by nickname, and warn
6181 if we've not heard of the server.
6182 - Make windows platform detection (uname equivalent) smarter.
6183 - It turns out sparc64 doesn't like unaligned access either.
6186 Changes in version 0.1.0.15 - 2005-09-23
6187 o Bugfixes on 0.1.0.x:
6188 - Reject ports 465 and 587 (spam targets) in default exit policy.
6189 - Don't crash when we don't have any spare file descriptors and we
6190 try to spawn a dns or cpu worker.
6191 - Get rid of IgnoreVersion undocumented config option, and make us
6192 only warn, never exit, when we're running an obsolete version.
6193 - Don't try to print a null string when your server finds itself to
6194 be unreachable and the Address config option is empty.
6195 - Make the numbers in read-history and write-history into uint64s,
6196 so they don't overflow and publish negatives in the descriptor.
6197 - Fix a minor memory leak in smartlist_string_remove().
6198 - We were only allowing ourselves to upload a server descriptor at
6199 most every 20 minutes, even if it changed earlier than that.
6200 - Clean up log entries that pointed to old URLs.
6203 Changes in version 0.1.1.7-alpha - 2005-09-14
6204 o Fixes on 0.1.1.6-alpha:
6205 - Exit servers were crashing when people asked them to make a
6206 connection to an address not in their exit policy.
6207 - Looking up a non-existent stream for a v1 control connection would
6209 - Fix a seg fault if we ask a dirserver for a descriptor by
6210 fingerprint but he doesn't know about him.
6211 - SETCONF was appending items to linelists, not clearing them.
6212 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
6213 out and refuse the setconf if it would fail.
6214 - Downgrade the dirserver log messages when whining about
6218 - Add Peter Palfrader's check-tor script to tor/contrib/
6219 It lets you easily check whether a given server (referenced by
6220 nickname) is reachable by you.
6221 - Numerous changes to move towards client-side v2 directories. Not
6225 - If the user gave tor an odd number of command-line arguments,
6226 we were silently ignoring the last one. Now we complain and fail.
6227 [This wins the oldest-bug prize -- this bug has been present since
6228 November 2002, as released in Tor 0.0.0.]
6229 - Do not use unaligned memory access on alpha, mips, or mipsel.
6230 It *works*, but is very slow, so we treat them as if it doesn't.
6231 - Retry directory requests if we fail to get an answer we like
6232 from a given dirserver (we were retrying before, but only if
6233 we fail to connect).
6234 - When writing the RecommendedVersions line, sort them first.
6235 - When the client asked for a rendezvous port that the hidden
6236 service didn't want to provide, we were sending an IP address
6237 back along with the end cell. Fortunately, it was zero. But stop
6239 - Correct "your server is reachable" log entries to indicate that
6240 it was self-testing that told us so.
6243 Changes in version 0.1.1.6-alpha - 2005-09-09
6244 o Fixes on 0.1.1.5-alpha:
6245 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
6246 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
6247 - Fix bug with tor_memmem finding a match at the end of the string.
6248 - Make unit tests run without segfaulting.
6249 - Resolve some solaris x86 compile warnings.
6250 - Handle duplicate lines in approved-routers files without warning.
6251 - Fix bug where as soon as a server refused any requests due to his
6252 exit policy (e.g. when we ask for localhost and he tells us that's
6253 127.0.0.1 and he won't do it), we decided he wasn't obeying his
6254 exit policy using him for any exits.
6255 - Only do openssl hardware accelerator stuff if openssl version is
6258 o New controller features/fixes:
6259 - Add a "RESETCONF" command so you can set config options like
6260 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
6261 a config option in the torrc with no value, then it clears it
6262 entirely (rather than setting it to its default).
6263 - Add a "GETINFO config-file" to tell us where torrc is.
6264 - Avoid sending blank lines when GETINFO replies should be empty.
6265 - Add a QUIT command for the controller (for using it manually).
6266 - Fix a bug in SAVECONF that was adding default dirservers and
6267 other redundant entries to the torrc file.
6269 o Start on the new directory design:
6270 - Generate, publish, cache, serve new network-status format.
6271 - Publish individual descriptors (by fingerprint, by "all", and by
6273 - Publish client and server recommended versions separately.
6274 - Allow tor_gzip_uncompress() to handle multiple concatenated
6275 compressed strings. Serve compressed groups of router
6276 descriptors. The compression logic here could be more
6278 - Distinguish v1 authorities (all currently trusted directories)
6279 from v2 authorities (all trusted directories).
6280 - Change DirServers config line to note which dirs are v1 authorities.
6281 - Add configuration option "V1AuthoritativeDirectory 1" which
6282 moria1, moria2, and tor26 should set.
6283 - Remove option when getting directory cache to see whether they
6284 support running-routers; they all do now. Replace it with one
6285 to see whether caches support v2 stuff.
6288 - Dirservers now do their own external reachability testing of each
6289 Tor server, and only list them as running if they've been found to
6290 be reachable. We also send back warnings to the server's logs if
6291 it uploads a descriptor that we already believe is unreachable.
6292 - Implement exit enclaves: if we know an IP address for the
6293 destination, and there's a running Tor server at that address
6294 which allows exit to the destination, then extend the circuit to
6295 that exit first. This provides end-to-end encryption and end-to-end
6296 authentication. Also, if the user wants a .exit address or enclave,
6297 use 4 hops rather than 3, and cannibalize a general circ for it
6299 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
6300 controller. Also, rotate dns and cpu workers if the controller
6301 changes options that will affect them; and initialize the dns
6302 worker cache tree whether or not we start out as a server.
6303 - Only upload a new server descriptor when options change, 18
6304 hours have passed, uptime is reset, or bandwidth changes a lot.
6305 - Check [X-]Forwarded-For headers in HTTP requests when generating
6306 log messages. This lets people run dirservers (and caches) behind
6307 Apache but still know which IP addresses are causing warnings.
6309 o Config option changes:
6310 - Replace (Fascist)Firewall* config options with a new
6311 ReachableAddresses option that understands address policies.
6312 For example, "ReachableAddresses *:80,*:443"
6313 - Get rid of IgnoreVersion undocumented config option, and make us
6314 only warn, never exit, when we're running an obsolete version.
6315 - Make MonthlyAccountingStart config option truly obsolete now.
6318 - Reject ports 465 and 587 in the default exit policy, since
6319 people have started using them for spam too.
6320 - It turns out we couldn't bootstrap a network since we added
6321 reachability detection in 0.1.0.1-rc. Good thing the Tor network
6322 has never gone down. Add an AssumeReachable config option to let
6323 servers and dirservers bootstrap. When we're trying to build a
6324 high-uptime or high-bandwidth circuit but there aren't enough
6325 suitable servers, try being less picky rather than simply failing.
6326 - Our logic to decide if the OR we connected to was the right guy
6327 was brittle and maybe open to a mitm for unverified routers.
6328 - We weren't cannibalizing circuits correctly for
6329 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
6330 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
6331 build those from scratch. This should make hidden services faster.
6332 - Predict required circuits better, with an eye toward making hidden
6333 services faster on the service end.
6334 - Retry streams if the exit node sends back a 'misc' failure. This
6335 should result in fewer random failures. Also, after failing
6336 from resolve failed or misc, reset the num failures, so we give
6337 it a fair shake next time we try.
6338 - Clean up the rendezvous warn log msgs, and downgrade some to info.
6339 - Reduce severity on logs about dns worker spawning and culling.
6340 - When we're shutting down and we do something like try to post a
6341 server descriptor or rendezvous descriptor, don't complain that
6342 we seem to be unreachable. Of course we are, we're shutting down.
6343 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
6344 We don't use them yet, but maybe one day our DNS resolver will be
6345 able to discover them.
6346 - Make ContactInfo mandatory for authoritative directory servers.
6347 - Require server descriptors to list IPv4 addresses -- hostnames
6348 are no longer allowed. This also fixes some potential security
6349 problems with people providing hostnames as their address and then
6350 preferentially resolving them to partition users.
6351 - Change log line for unreachability to explicitly suggest /etc/hosts
6352 as the culprit. Also make it clearer what IP address and ports we're
6353 testing for reachability.
6354 - Put quotes around user-supplied strings when logging so users are
6355 more likely to realize if they add bad characters (like quotes)
6357 - Let auth dir servers start without specifying an Address config
6359 - Make unit tests (and other invocations that aren't the real Tor)
6360 run without launching listeners, creating subdirectories, and so on.
6363 Changes in version 0.1.1.5-alpha - 2005-08-08
6364 o Bugfixes included in 0.1.0.14.
6366 o Bugfixes on 0.1.0.x:
6367 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
6368 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
6369 it would silently using ignore the 6668.
6372 Changes in version 0.1.0.14 - 2005-08-08
6373 o Bugfixes on 0.1.0.x:
6374 - Fix the other half of the bug with crypto handshakes
6376 - Fix an assert trigger if you send a 'signal term' via the
6377 controller when it's listening for 'event info' messages.
6380 Changes in version 0.1.1.4-alpha - 2005-08-04
6381 o Bugfixes included in 0.1.0.13.
6384 - Improve tor_gettimeofday() granularity on windows.
6385 - Make clients regenerate their keys when their IP address changes.
6386 - Implement some more GETINFO goodness: expose helper nodes, config
6387 options, getinfo keys.
6390 Changes in version 0.1.0.13 - 2005-08-04
6391 o Bugfixes on 0.1.0.x:
6392 - Fix a critical bug in the security of our crypto handshakes.
6393 - Fix a size_t underflow in smartlist_join_strings2() that made
6394 it do bad things when you hand it an empty smartlist.
6395 - Fix Windows installer to ship Tor license (thanks to Aphex for
6396 pointing out this oversight) and put a link to the doc directory
6398 - Explicitly set no-unaligned-access for sparc: it turns out the
6399 new gcc's let you compile broken code, but that doesn't make it
6403 Changes in version 0.1.1.3-alpha - 2005-07-23
6404 o Bugfixes on 0.1.1.2-alpha:
6405 - Fix a bug in handling the controller's "post descriptor"
6407 - Fix several bugs in handling the controller's "extend circuit"
6409 - Fix a bug in handling the controller's "stream status" event.
6410 - Fix an assert failure if we have a controller listening for
6411 circuit events and we go offline.
6412 - Re-allow hidden service descriptors to publish 0 intro points.
6413 - Fix a crash when generating your hidden service descriptor if
6414 you don't have enough intro points already.
6416 o New features on 0.1.1.2-alpha:
6417 - New controller function "getinfo accounting", to ask how
6418 many bytes we've used in this time period.
6419 - Experimental support for helper nodes: a lot of the risk from
6420 a small static adversary comes because users pick new random
6421 nodes every time they rebuild a circuit. Now users will try to
6422 stick to the same small set of entry nodes if they can. Not
6423 enabled by default yet.
6425 o Bugfixes on 0.1.0.12:
6426 - If you're an auth dir server, always publish your dirport,
6427 even if you haven't yet found yourself to be reachable.
6428 - Fix a size_t underflow in smartlist_join_strings2() that made
6429 it do bad things when you hand it an empty smartlist.
6432 Changes in version 0.1.0.12 - 2005-07-18
6433 o New directory servers:
6434 - tor26 has changed IP address.
6436 o Bugfixes on 0.1.0.x:
6437 - Fix a possible double-free in tor_gzip_uncompress().
6438 - When --disable-threads is set, do not search for or link against
6440 - Don't trigger an assert if an authoritative directory server
6441 claims its dirport is 0.
6442 - Fix bug with removing Tor as an NT service: some people were
6443 getting "The service did not return an error." Thanks to Matt
6447 Changes in version 0.1.1.2-alpha - 2005-07-15
6448 o New directory servers:
6449 - tor26 has changed IP address.
6451 o Bugfixes on 0.1.0.x, crashes/leaks:
6452 - Port the servers-not-obeying-their-exit-policies fix from
6454 - Fix an fd leak in start_daemon().
6455 - On Windows, you can't always reopen a port right after you've
6456 closed it. So change retry_listeners() to only close and re-open
6457 ports that have changed.
6458 - Fix a possible double-free in tor_gzip_uncompress().
6460 o Bugfixes on 0.1.0.x, usability:
6461 - When tor_socketpair() fails in Windows, give a reasonable
6462 Windows-style errno back.
6463 - Let people type "tor --install" as well as "tor -install" when
6465 want to make it an NT service.
6466 - NT service patch from Matt Edman to improve error messages.
6467 - When the controller asks for a config option with an abbreviated
6468 name, give the full name in our response.
6469 - Correct the man page entry on TrackHostExitsExpire.
6470 - Looks like we were never delivering deflated (i.e. compressed)
6471 running-routers lists, even when asked. Oops.
6472 - When --disable-threads is set, do not search for or link against
6475 o Bugfixes on 0.1.1.x:
6476 - Fix a seg fault with autodetecting which controller version is
6480 - New hidden service descriptor format: put a version in it, and
6481 let people specify introduction/rendezvous points that aren't
6482 in "the directory" (which is subjective anyway).
6483 - Allow the DEBUG controller event to work again. Mark certain log
6484 entries as "don't tell this to controllers", so we avoid cycles.
6487 Changes in version 0.1.0.11 - 2005-06-30
6488 o Bugfixes on 0.1.0.x:
6489 - Fix major security bug: servers were disregarding their
6490 exit policies if clients behaved unexpectedly.
6491 - Make OS X init script check for missing argument, so we don't
6492 confuse users who invoke it incorrectly.
6493 - Fix a seg fault in "tor --hash-password foo".
6494 - The MAPADDRESS control command was broken.
6497 Changes in version 0.1.1.1-alpha - 2005-06-29
6499 - Make OS X init script check for missing argument, so we don't
6500 confuse users who invoke it incorrectly.
6501 - Fix a seg fault in "tor --hash-password foo".
6502 - Fix a possible way to DoS dirservers.
6503 - When we complain that your exit policy implicitly allows local or
6504 private address spaces, name them explicitly so operators can
6506 - Make the log message less scary when all the dirservers are
6507 temporarily unreachable.
6508 - We were printing the number of idle dns workers incorrectly when
6512 - Revised controller protocol (version 1) that uses ascii rather
6513 than binary. Add supporting libraries in python and java so you
6514 can use the controller from your applications without caring how
6516 - Spiffy new support for crypto hardware accelerators. Can somebody
6520 Changes in version 0.0.9.10 - 2005-06-16
6521 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
6522 - Refuse relay cells that claim to have a length larger than the
6523 maximum allowed. This prevents a potential attack that could read
6524 arbitrary memory (e.g. keys) from an exit server's process
6528 Changes in version 0.1.0.10 - 2005-06-14
6529 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
6530 libevent before 1.1a.
6533 Changes in version 0.1.0.9-rc - 2005-06-09
6535 - Reset buf->highwater every time buf_shrink() is called, not just on
6536 a successful shrink. This was causing significant memory bloat.
6537 - Fix buffer overflow when checking hashed passwords.
6538 - Security fix: if seeding the RNG on Win32 fails, quit.
6539 - Allow seeding the RNG on Win32 even when you're not running as
6541 - Disable threading on Solaris too. Something is wonky with it,
6542 cpuworkers, and reentrant libs.
6543 - Reenable the part of the code that tries to flush as soon as an
6544 OR outbuf has a full TLS record available. Perhaps this will make
6545 OR outbufs not grow as huge except in rare cases, thus saving lots
6546 of CPU time plus memory.
6547 - Reject malformed .onion addresses rather then passing them on as
6548 normal web requests.
6549 - Adapt patch from Adam Langley: fix possible memory leak in
6550 tor_lookup_hostname().
6551 - Initialize libevent later in the startup process, so the logs are
6552 already established by the time we start logging libevent warns.
6553 - Use correct errno on win32 if libevent fails.
6554 - Check and warn about known-bad/slow libevent versions.
6555 - Pay more attention to the ClientOnly config option.
6556 - Have torctl.in/tor.sh.in check for location of su binary (needed
6558 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
6559 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
6560 HttpProxyAuthenticator
6561 - Stop warning about sigpipes in the logs. We're going to
6562 pretend that getting these occassionally is normal and fine.
6563 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
6565 installer screens; and don't put stuff into StartupItems unless
6566 the user asks you to.
6567 - Require servers that use the default dirservers to have public IP
6568 addresses. We have too many servers that are configured with private
6569 IPs and their admins never notice the log entries complaining that
6570 their descriptors are being rejected.
6571 - Add OSX uninstall instructions. An actual uninstall script will
6575 Changes in version 0.1.0.8-rc - 2005-05-23
6577 - It turns out that kqueue on OS X 10.3.9 was causing kernel
6578 panics. Disable kqueue on all OS X Tors.
6579 - Fix RPM: remove duplicate line accidentally added to the rpm
6581 - Disable threads on openbsd too, since its gethostaddr is not
6583 - Tolerate libevent 0.8 since it still works, even though it's
6585 - Enable building on Red Hat 9.0 again.
6586 - Allow the middle hop of the testing circuit to be running any
6587 version, now that most of them have the bugfix to let them connect
6588 to unknown servers. This will allow reachability testing to work
6589 even when 0.0.9.7-0.0.9.9 become obsolete.
6590 - Handle relay cells with rh.length too large. This prevents
6591 a potential attack that could read arbitrary memory (maybe even
6592 keys) from the exit server's process.
6593 - We screwed up the dirport reachability testing when we don't yet
6594 have a cached version of the directory. Hopefully now fixed.
6595 - Clean up router_load_single_router() (used by the controller),
6596 so it doesn't seg fault on error.
6597 - Fix a minor memory leak when somebody establishes an introduction
6598 point at your Tor server.
6599 - If a socks connection ends because read fails, don't warn that
6600 you're not sending a socks reply back.
6603 - Add HttpProxyAuthenticator config option too, that works like
6604 the HttpsProxyAuthenticator config option.
6605 - Encode hashed controller passwords in hex instead of base64,
6606 to make it easier to write controllers.
6609 Changes in version 0.1.0.7-rc - 2005-05-17
6611 - Fix a bug in the OS X package installer that prevented it from
6612 installing on Tiger.
6613 - Fix a script bug in the OS X package installer that made it
6614 complain during installation.
6615 - Find libevent even if it's hiding in /usr/local/ and your
6616 CFLAGS and LDFLAGS don't tell you to look there.
6617 - Be able to link with libevent as a shared library (the default
6618 after 1.0d), even if it's hiding in /usr/local/lib and even
6619 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
6620 assuming you're running gcc. Otherwise fail and give a useful
6622 - Fix a bug in the RPM packager: set home directory for _tor to
6623 something more reasonable when first installing.
6624 - Free a minor amount of memory that is still reachable on exit.
6627 Changes in version 0.1.0.6-rc - 2005-05-14
6629 - Implement --disable-threads configure option. Disable threads on
6630 netbsd by default, because it appears to have no reentrant resolver
6632 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
6633 release (1.1) detects and disables kqueue if it's broken.
6634 - Append default exit policy before checking for implicit internal
6635 addresses. Now we don't log a bunch of complaints on startup
6636 when using the default exit policy.
6637 - Some people were putting "Address " in their torrc, and they had
6638 a buggy resolver that resolved " " to 0.0.0.0. Oops.
6639 - If DataDir is ~/.tor, and that expands to /.tor, then default to
6640 LOCALSTATEDIR/tor instead.
6641 - Fix fragmented-message bug in TorControl.py.
6642 - Resolve a minor bug which would prevent unreachable dirports
6643 from getting suppressed in the published descriptor.
6644 - When the controller gave us a new descriptor, we weren't resolving
6645 it immediately, so Tor would think its address was 0.0.0.0 until
6646 we fetched a new directory.
6647 - Fix an uppercase/lowercase case error in suppressing a bogus
6648 libevent warning on some Linuxes.
6651 - Begin scrubbing sensitive strings from logs by default. Turn off
6652 the config option SafeLogging if you need to do debugging.
6653 - Switch to a new buffer management algorithm, which tries to avoid
6654 reallocing and copying quite as much. In first tests it looks like
6655 it uses *more* memory on average, but less cpu.
6656 - First cut at support for "create-fast" cells. Clients can use
6657 these when extending to their first hop, since the TLS already
6658 provides forward secrecy and authentication. Not enabled on
6660 - When dirservers refuse a router descriptor, we now log its
6661 contactinfo, platform, and the poster's IP address.
6662 - Call tor_free_all instead of connections_free_all after forking, to
6663 save memory on systems that need to fork.
6664 - Whine at you if you're a server and you don't set your contactinfo.
6665 - Implement --verify-config command-line option to check if your torrc
6666 is valid without actually launching Tor.
6667 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
6668 rather than just rejecting it.
6671 Changes in version 0.1.0.5-rc - 2005-04-27
6673 - Stop trying to print a null pointer if an OR conn fails because
6674 we didn't like its cert.
6676 - Switch our internal buffers implementation to use a ring buffer,
6677 to hopefully improve performance for fast servers a lot.
6678 - Add HttpsProxyAuthenticator support (basic auth only), based
6679 on patch from Adam Langley.
6680 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
6681 the fast servers that have been joining lately.
6682 - Give hidden service accesses extra time on the first attempt,
6683 since 60 seconds is often only barely enough. This might improve
6685 - Improve performance for dirservers: stop re-parsing the whole
6686 directory every time you regenerate it.
6687 - Add more debugging info to help us find the weird dns freebsd
6688 pthreads bug; cleaner debug messages to help track future issues.
6691 Changes in version 0.0.9.9 - 2005-04-23
6692 o Bugfixes on 0.0.9.x:
6693 - If unofficial Tor clients connect and send weird TLS certs, our
6694 Tor server triggers an assert. This release contains a minimal
6695 backport from the broader fix that we put into 0.1.0.4-rc.
6698 Changes in version 0.1.0.4-rc - 2005-04-23
6700 - If unofficial Tor clients connect and send weird TLS certs, our
6701 Tor server triggers an assert. Stop asserting, and start handling
6702 TLS errors better in other situations too.
6703 - When the controller asks us to tell it about all the debug-level
6704 logs, it turns out we were generating debug-level logs while
6705 telling it about them, which turns into a bad loop. Now keep
6706 track of whether you're sending a debug log to the controller,
6707 and don't log when you are.
6708 - Fix the "postdescriptor" feature of the controller interface: on
6709 non-complete success, only say "done" once.
6711 - Clients are now willing to load balance over up to 2mB, not 1mB,
6712 of advertised bandwidth capacity.
6713 - Add a NoPublish config option, so you can be a server (e.g. for
6714 testing running Tor servers in other Tor networks) without
6715 publishing your descriptor to the primary dirservers.
6718 Changes in version 0.1.0.3-rc - 2005-04-08
6719 o Improvements on 0.1.0.2-rc:
6720 - Client now retries when streams end early for 'hibernating' or
6721 'resource limit' reasons, rather than failing them.
6722 - More automated handling for dirserver operators:
6723 - Automatically approve nodes running 0.1.0.2-rc or later,
6724 now that the the reachability detection stuff is working.
6725 - Now we allow two unverified servers with the same nickname
6726 but different keys. But if a nickname is verified, only that
6727 nickname+key are allowed.
6728 - If you're an authdirserver connecting to an address:port,
6729 and it's not the OR you were expecting, forget about that
6730 descriptor. If he *was* the one you were expecting, then forget
6731 about all other descriptors for that address:port.
6732 - Allow servers to publish descriptors from 12 hours in the future.
6733 Corollary: only whine about clock skew from the dirserver if
6734 he's a trusted dirserver (since now even verified servers could
6735 have quite wrong clocks).
6736 - Adjust maximum skew and age for rendezvous descriptors: let skew
6737 be 48 hours rather than 90 minutes.
6738 - Efficiency improvements:
6739 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
6740 it much faster to look up a circuit for each relay cell.
6741 - Remove most calls to assert_all_pending_dns_resolves_ok(),
6742 since they're eating our cpu on exit nodes.
6743 - Stop wasting time doing a case insensitive comparison for every
6744 dns name every time we do any lookup. Canonicalize the names to
6745 lowercase and be done with it.
6746 - Start sending 'truncated' cells back rather than destroy cells,
6747 if the circuit closes in front of you. This means we won't have
6748 to abandon partially built circuits.
6749 - Only warn once per nickname from add_nickname_list_to_smartlist
6750 per failure, so an entrynode or exitnode choice that's down won't
6752 - Put a note in the torrc about abuse potential with the default
6754 - Revise control spec and implementation to allow all log messages to
6755 be sent to controller with their severities intact (suggested by
6756 Matt Edman). Update TorControl to handle new log event types.
6757 - Provide better explanation messages when controller's POSTDESCRIPTOR
6759 - Stop putting nodename in the Platform string in server descriptors.
6760 It doesn't actually help, and it is confusing/upsetting some people.
6762 o Bugfixes on 0.1.0.2-rc:
6763 - We were printing the host mask wrong in exit policies in server
6764 descriptors. This isn't a critical bug though, since we were still
6765 obeying the exit policy internally.
6766 - Fix Tor when compiled with libevent but without pthreads: move
6767 connection_unregister() from _connection_free() to
6769 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
6770 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
6771 when we look through the connection array, we'll find any of the
6772 cpu/dnsworkers. This is no good.
6774 o Bugfixes on 0.0.9.8:
6775 - Fix possible bug on threading platforms (e.g. win32) which was
6776 leaking a file descriptor whenever a cpuworker or dnsworker died.
6777 - When using preferred entry or exit nodes, ignore whether the
6778 circuit wants uptime or capacity. They asked for the nodes, they
6780 - chdir() to your datadirectory at the *end* of the daemonize process,
6781 not the beginning. This was a problem because the first time you
6782 run tor, if your datadir isn't there, and you have runasdaemon set
6783 to 1, it will try to chdir to it before it tries to create it. Oops.
6784 - Handle changed router status correctly when dirserver reloads
6785 fingerprint file. We used to be dropping all unverified descriptors
6786 right then. The bug was hidden because we would immediately
6787 fetch a directory from another dirserver, which would include the
6788 descriptors we just dropped.
6789 - When we're connecting to an OR and he's got a different nickname/key
6790 than we were expecting, only complain loudly if we're an OP or a
6791 dirserver. Complaining loudly to the OR admins just confuses them.
6792 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
6793 artificially capped at 500kB.
6796 Changes in version 0.0.9.8 - 2005-04-07
6797 o Bugfixes on 0.0.9.x:
6798 - We have a bug that I haven't found yet. Sometimes, very rarely,
6799 cpuworkers get stuck in the 'busy' state, even though the cpuworker
6800 thinks of itself as idle. This meant that no new circuits ever got
6801 established. Here's a workaround to kill any cpuworker that's been
6802 busy for more than 100 seconds.
6805 Changes in version 0.1.0.2-rc - 2005-04-01
6806 o Bugfixes on 0.1.0.1-rc:
6807 - Fixes on reachability detection:
6808 - Don't check for reachability while hibernating.
6809 - If ORPort is reachable but DirPort isn't, still publish the
6810 descriptor, but zero out DirPort until it's found reachable.
6811 - When building testing circs for ORPort testing, use only
6812 high-bandwidth nodes, so fewer circuits fail.
6813 - Complain about unreachable ORPort separately from unreachable
6814 DirPort, so the user knows what's going on.
6815 - Make sure we only conclude ORPort reachability if we didn't
6816 initiate the conn. Otherwise we could falsely conclude that
6817 we're reachable just because we connected to the guy earlier
6818 and he used that same pipe to extend to us.
6819 - Authdirservers shouldn't do ORPort reachability detection,
6820 since they're in clique mode, so it will be rare to find a
6821 server not already connected to them.
6822 - When building testing circuits, always pick middle hops running
6823 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
6824 bug. (This is a kludge; it will go away when 0.0.9.x becomes
6826 - When we decide we're reachable, actually publish our descriptor
6828 - Fix bug in redirectstream in the controller.
6829 - Fix the state descriptor strings so logs don't claim edge streams
6830 are in a different state than they actually are.
6831 - Use recent libevent features when possible (this only really affects
6832 win32 and osx right now, because the new libevent with these
6833 features hasn't been released yet). Add code to suppress spurious
6835 - Prevent possible segfault in connection_close_unattached_ap().
6836 - Fix newlines on torrc in win32.
6837 - Improve error msgs when tor-resolve fails.
6839 o Improvements on 0.0.9.x:
6840 - New experimental script tor/contrib/ExerciseServer.py (needs more
6841 work) that uses the controller interface to build circuits and
6842 fetch pages over them. This will help us bootstrap servers that
6843 have lots of capacity but haven't noticed it yet.
6844 - New experimental script tor/contrib/PathDemo.py (needs more work)
6845 that uses the controller interface to let you choose whole paths
6847 "<hostname>.<path,separated by dots>.<length of path>.path"
6848 - When we've connected to an OR and handshaked but didn't like
6849 the result, we were closing the conn without sending destroy
6850 cells back for pending circuits. Now send those destroys.
6853 Changes in version 0.0.9.7 - 2005-04-01
6854 o Bugfixes on 0.0.9.x:
6855 - Fix another race crash bug (thanks to Glenn Fink for reporting).
6856 - Compare identity to identity, not to nickname, when extending to
6857 a router not already in the directory. This was preventing us from
6858 extending to unknown routers. Oops.
6859 - Make sure to create OS X Tor user in <500 range, so we aren't
6860 creating actual system users.
6861 - Note where connection-that-hasn't-sent-end was marked, and fix
6862 a few really loud instances of this harmless bug (it's fixed more
6866 Changes in version 0.1.0.1-rc - 2005-03-28
6868 - Add reachability testing. Your Tor server will automatically try
6869 to see if its ORPort and DirPort are reachable from the outside,
6870 and it won't upload its descriptor until it decides they are.
6871 - Handle unavailable hidden services better. Handle slow or busy
6872 hidden services better.
6873 - Add support for CONNECTing through https proxies, with "HttpsProxy"
6875 - New exit policy: accept most low-numbered ports, rather than
6876 rejecting most low-numbered ports.
6877 - More Tor controller support (still experimental). See
6878 http://tor.eff.org/doc/control-spec.txt for all the new features,
6879 including signals to emulate unix signals from any platform;
6880 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
6881 closestream; closecircuit; etc.
6882 - Make nt services work and start on startup on win32 (based on
6883 patch by Matt Edman).
6884 - Add a new AddressMap config directive to rewrite incoming socks
6885 addresses. This lets you, for example, declare an implicit
6886 required exit node for certain sites.
6887 - Add a new TrackHostExits config directive to trigger addressmaps
6888 for certain incoming socks addresses -- for sites that break when
6889 your exit keeps changing (based on patch by Mike Perry).
6890 - Redo the client-side dns cache so it's just an addressmap too.
6891 - Notice when our IP changes, and reset stats/uptime/reachability.
6892 - When an application is using socks5, give him the whole variety of
6893 potential socks5 responses (connect refused, host unreachable, etc),
6894 rather than just "success" or "failure".
6895 - A more sane version numbering system. See
6896 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
6897 - New contributed script "exitlist": a simple python script to
6898 parse directories and find Tor nodes that exit to listed
6900 - New contributed script "privoxy-tor-toggle" to toggle whether
6901 Privoxy uses Tor. Seems to be configured for Debian by default.
6902 - Report HTTP reasons to client when getting a response from directory
6903 servers -- so you can actually know what went wrong.
6904 - New config option MaxAdvertisedBandwidth which lets you advertise
6905 a low bandwidthrate (to not attract as many circuits) while still
6906 allowing a higher bandwidthrate in reality.
6908 o Robustness/stability fixes:
6909 - Make Tor use Niels Provos's libevent instead of its current
6910 poll-but-sometimes-select mess. This will let us use faster async
6911 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
6913 - pthread support now too. This was forced because when we forked,
6914 we ended up wasting a lot of duplicate ram over time. Also switch
6915 to foo_r versions of some library calls to allow reentry and
6917 - Better handling for heterogeneous / unreliable nodes:
6918 - Annotate circuits w/ whether they aim to contain high uptime nodes
6919 and/or high capacity nodes. When building circuits, choose
6921 - This means that every single node in an intro rend circuit,
6922 not just the last one, will have a minimum uptime.
6923 - New config option LongLivedPorts to indicate application streams
6924 that will want high uptime circuits.
6925 - Servers reset uptime when a dir fetch entirely fails. This
6926 hopefully reflects stability of the server's network connectivity.
6927 - If somebody starts his tor server in Jan 2004 and then fixes his
6928 clock, don't make his published uptime be a year.
6929 - Reset published uptime when you wake up from hibernation.
6930 - Introduce a notion of 'internal' circs, which are chosen without
6931 regard to the exit policy of the last hop. Intro and rendezvous
6932 circs must be internal circs, to avoid leaking information. Resolve
6933 and connect streams can use internal circs if they want.
6934 - New circuit pooling algorithm: make sure to have enough circs around
6935 to satisfy any predicted ports, and also make sure to have 2 internal
6936 circs around if we've required internal circs lately (and with high
6937 uptime if we've seen that lately too).
6938 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
6939 which describes how often we retry making new circuits if current
6940 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
6941 how long we're willing to make use of an already-dirty circuit.
6942 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
6943 circ as necessary, if there are any completed ones lying around
6944 when we try to launch one.
6945 - Make hidden services try to establish a rendezvous for 30 seconds,
6946 rather than for n (where n=3) attempts to build a circuit.
6947 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
6948 "ShutdownWaitLength".
6949 - Try to be more zealous about calling connection_edge_end when
6950 things go bad with edge conns in connection.c.
6951 - Revise tor-spec to add more/better stream end reasons.
6952 - Revise all calls to connection_edge_end to avoid sending "misc",
6953 and to take errno into account where possible.
6956 - Fix a race condition that can trigger an assert, when we have a
6957 pending create cell and an OR connection fails right then.
6958 - Fix several double-mark-for-close bugs, e.g. where we were finding
6959 a conn for a cell even if that conn is already marked for close.
6960 - Make sequence of log messages when starting on win32 with no config
6961 file more reasonable.
6962 - When choosing an exit node for a new non-internal circ, don't take
6963 into account whether it'll be useful for any pending x.onion
6964 addresses -- it won't.
6965 - Turn addr_policy_compare from a tristate to a quadstate; this should
6966 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
6967 for google.com" problem.
6968 - Make "platform" string in descriptor more accurate for Win32 servers,
6969 so it's not just "unknown platform".
6970 - Fix an edge case in parsing config options (thanks weasel).
6971 If they say "--" on the commandline, it's not an option.
6972 - Reject odd-looking addresses at the client (e.g. addresses that
6973 contain a colon), rather than having the server drop them because
6975 - tor-resolve requests were ignoring .exit if there was a working circuit
6976 they could use instead.
6977 - REUSEADDR on normal platforms means you can rebind to the port
6978 right after somebody else has let it go. But REUSEADDR on win32
6979 means to let you bind to the port _even when somebody else
6980 already has it bound_! So, don't do that on Win32.
6981 - Change version parsing logic: a version is "obsolete" if it is not
6982 recommended and (1) there is a newer recommended version in the
6983 same series, or (2) there are no recommended versions in the same
6984 series, but there are some recommended versions in a newer series.
6985 A version is "new" if it is newer than any recommended version in
6987 - Stop most cases of hanging up on a socks connection without sending
6991 - Require BandwidthRate to be at least 20kB/s for servers.
6992 - When a dirserver causes you to give a warn, mention which dirserver
6994 - New config option DirAllowPrivateAddresses for authdirservers.
6995 Now by default they refuse router descriptors that have non-IP or
6996 private-IP addresses.
6997 - Stop publishing socksport in the directory, since it's not
6998 actually meant to be public. For compatibility, publish a 0 there
7000 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
7001 smart" value, that is low for servers and high for clients.
7002 - If our clock jumps forward by 100 seconds or more, assume something
7003 has gone wrong with our network and abandon all not-yet-used circs.
7004 - Warn when exit policy implicitly allows local addresses.
7005 - If we get an incredibly skewed timestamp from a dirserver mirror
7006 that isn't a verified OR, don't warn -- it's probably him that's
7008 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
7009 cookies to disk and doesn't log each web request to disk. (Thanks
7010 to Brett Carrington for pointing this out.)
7011 - When a client asks us for a dir mirror and we don't have one,
7012 launch an attempt to get a fresh one.
7013 - If we're hibernating and we get a SIGINT, exit immediately.
7014 - Add --with-dmalloc ./configure option, to track memory leaks.
7015 - And try to free all memory on closing, so we can detect what
7017 - Cache local dns resolves correctly even when they're .exit
7019 - Give a better warning when some other server advertises an
7020 ORPort that is actually an apache running ssl.
7021 - Add "opt hibernating 1" to server descriptor to make it clearer
7022 whether the server is hibernating.
7025 Changes in version 0.0.9.6 - 2005-03-24
7026 o Bugfixes on 0.0.9.x (crashes and asserts):
7027 - Add new end stream reasons to maintainance branch. Fix bug where
7028 reason (8) could trigger an assert. Prevent bug from recurring.
7029 - Apparently win32 stat wants paths to not end with a slash.
7030 - Fix assert triggers in assert_cpath_layer_ok(), where we were
7031 blowing away the circuit that conn->cpath_layer points to, then
7032 checking to see if the circ is well-formed. Backport check to make
7033 sure we dont use the cpath on a closed connection.
7034 - Prevent circuit_resume_edge_reading_helper() from trying to package
7035 inbufs for marked-for-close streams.
7036 - Don't crash on hup if your options->address has become unresolvable.
7037 - Some systems (like OS X) sometimes accept() a connection and tell
7038 you the remote host is 0.0.0.0:0. If this happens, due to some
7039 other mis-features, we get confused; so refuse the conn for now.
7041 o Bugfixes on 0.0.9.x (other):
7042 - Fix harmless but scary "Unrecognized content encoding" warn message.
7043 - Add new stream error reason: TORPROTOCOL reason means "you are not
7044 speaking a version of Tor I understand; say bye-bye to your stream."
7045 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
7046 into the future, now that we are more tolerant of skew. This
7047 resolves a bug where a Tor server would refuse to cache a directory
7048 because all the directories it gets are too far in the future;
7049 yet the Tor server never logs any complaints about clock skew.
7050 - Mac packaging magic: make man pages useable, and do not overwrite
7051 existing torrc files.
7052 - Make OS X log happily to /var/log/tor/tor.log
7055 Changes in version 0.0.9.5 - 2005-02-22
7056 o Bugfixes on 0.0.9.x:
7057 - Fix an assert race at exit nodes when resolve requests fail.
7058 - Stop picking unverified dir mirrors--it only leads to misery.
7059 - Patch from Matt Edman to make NT services work better. Service
7060 support is still not compiled into the executable by default.
7061 - Patch from Dmitri Bely so the Tor service runs better under
7062 the win32 SYSTEM account.
7063 - Make tor-resolve actually work (?) on Win32.
7064 - Fix a sign bug when getrlimit claims to have 4+ billion
7065 file descriptors available.
7066 - Stop refusing to start when bandwidthburst == bandwidthrate.
7067 - When create cells have been on the onion queue more than five
7068 seconds, just send back a destroy and take them off the list.
7071 Changes in version 0.0.9.4 - 2005-02-03
7072 o Bugfixes on 0.0.9:
7073 - Fix an assert bug that took down most of our servers: when
7074 a server claims to have 1 GB of bandwidthburst, don't
7076 - Don't crash as badly if we have spawned the max allowed number
7077 of dnsworkers, or we're out of file descriptors.
7078 - Block more file-sharing ports in the default exit policy.
7079 - MaxConn is now automatically set to the hard limit of max
7080 file descriptors we're allowed (ulimit -n), minus a few for
7082 - Give a clearer message when servers need to raise their
7083 ulimit -n when they start running out of file descriptors.
7084 - SGI Compatibility patches from Jan Schaumann.
7085 - Tolerate a corrupt cached directory better.
7086 - When a dirserver hasn't approved your server, list which one.
7087 - Go into soft hibernation after 95% of the bandwidth is used,
7088 not 99%. This is especially important for daily hibernators who
7089 have a small accounting max. Hopefully it will result in fewer
7090 cut connections when the hard hibernation starts.
7091 - Load-balance better when using servers that claim more than
7092 800kB/s of capacity.
7093 - Make NT services work (experimental, only used if compiled in).
7096 Changes in version 0.0.9.3 - 2005-01-21
7097 o Bugfixes on 0.0.9:
7098 - Backport the cpu use fixes from main branch, so busy servers won't
7099 need as much processor time.
7100 - Work better when we go offline and then come back, or when we
7101 run Tor at boot before the network is up. We do this by
7102 optimistically trying to fetch a new directory whenever an
7103 application request comes in and we think we're offline -- the
7104 human is hopefully a good measure of when the network is back.
7105 - Backport some minimal hidserv bugfixes: keep rend circuits open as
7106 long as you keep using them; actually publish hidserv descriptors
7107 shortly after they change, rather than waiting 20-40 minutes.
7108 - Enable Mac startup script by default.
7109 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
7110 - When you update AllowUnverifiedNodes or FirewallPorts via the
7111 controller's setconf feature, we were always appending, never
7113 - When you update HiddenServiceDir via setconf, it was screwing up
7114 the order of reading the lines, making it fail.
7115 - Do not rewrite a cached directory back to the cache; otherwise we
7116 will think it is recent and not fetch a newer one on startup.
7117 - Workaround for webservers that lie about Content-Encoding: Tor
7118 now tries to autodetect compressed directories and compression
7119 itself. This lets us Proxypass dir fetches through apache.
7122 Changes in version 0.0.9.2 - 2005-01-04
7123 o Bugfixes on 0.0.9 (crashes and asserts):
7124 - Fix an assert on startup when the disk is full and you're logging
7126 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
7127 style address, then we'd crash.
7128 - Fix an assert trigger when the running-routers string we get from
7129 a dirserver is broken.
7130 - Make worker threads start and run on win32. Now win32 servers
7132 - Bandaid (not actually fix, but now it doesn't crash) an assert
7133 where the dns worker dies mysteriously and the main Tor process
7134 doesn't remember anything about the address it was resolving.
7136 o Bugfixes on 0.0.9 (Win32):
7137 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
7138 name out of the warning/assert messages.
7139 - Fix a superficial "unhandled error on read" bug on win32.
7140 - The win32 installer no longer requires a click-through for our
7141 license, since our Free Software license grants rights but does not
7143 - Win32: When connecting to a dirserver fails, try another one
7144 immediately. (This was already working for non-win32 Tors.)
7145 - Stop trying to parse $HOME on win32 when hunting for default
7147 - Make tor-resolve.c work on win32 by calling network_init().
7149 o Bugfixes on 0.0.9 (other):
7150 - Make 0.0.9.x build on Solaris again.
7151 - Due to a fencepost error, we were blowing away the \n when reporting
7152 confvalue items in the controller. So asking for multiple config
7153 values at once couldn't work.
7154 - When listing circuits that are pending on an opening OR connection,
7155 if we're an OR we were listing circuits that *end* at us as
7156 being pending on every listener, dns/cpu worker, etc. Stop that.
7157 - Dirservers were failing to create 'running-routers' or 'directory'
7158 strings if we had more than some threshold of routers. Fix them so
7159 they can handle any number of routers.
7160 - Fix a superficial "Duplicate mark for close" bug.
7161 - Stop checking for clock skew for OR connections, even for servers.
7162 - Fix a fencepost error that was chopping off the last letter of any
7163 nickname that is the maximum allowed nickname length.
7164 - Update URLs in log messages so they point to the new website.
7165 - Fix a potential problem in mangling server private keys while
7166 writing to disk (not triggered yet, as far as we know).
7167 - Include the licenses for other free software we include in Tor,
7168 now that we're shipping binary distributions more regularly.
7171 Changes in version 0.0.9.1 - 2004-12-15
7172 o Bugfixes on 0.0.9:
7173 - Make hibernation actually work.
7174 - Make HashedControlPassword config option work.
7175 - When we're reporting event circuit status to a controller,
7176 don't use the stream status code.
7179 Changes in version 0.0.9 - 2004-12-12
7181 - Clean up manpage and torrc.sample file.
7182 - Clean up severities and text of log warnings.
7184 - Make servers trigger an assert when they enter hibernation.
7187 Changes in version 0.0.9rc7 - 2004-12-08
7188 o Bugfixes on 0.0.9rc:
7189 - Fix a stack-trashing crash when an exit node begins hibernating.
7190 - Avoid looking at unallocated memory while considering which
7191 ports we need to build circuits to cover.
7192 - Stop a sigpipe: when an 'end' cell races with eof from the app,
7193 we shouldn't hold-open-until-flush if the eof arrived first.
7194 - Fix a bug with init_cookie_authentication() in the controller.
7195 - When recommending new-format log lines, if the upper bound is
7196 LOG_ERR, leave it implicit.
7198 o Bugfixes on 0.0.8.1:
7199 - Fix a whole slew of memory leaks.
7200 - Fix isspace() and friends so they still make Solaris happy
7201 but also so they don't trigger asserts on win32.
7202 - Fix parse_iso_time on platforms without strptime (eg win32).
7203 - win32: tolerate extra "readable" events better.
7204 - win32: when being multithreaded, leave parent fdarray open.
7205 - Make unit tests work on win32.
7208 Changes in version 0.0.9rc6 - 2004-12-06
7209 o Bugfixes on 0.0.9pre:
7210 - Clean up some more integer underflow opportunities (not exploitable
7212 - While hibernating, hup should not regrow our listeners.
7213 - Send an end to the streams we close when we hibernate, rather
7214 than just chopping them off.
7215 - React to eof immediately on non-open edge connections.
7217 o Bugfixes on 0.0.8.1:
7218 - Calculate timeout for waiting for a connected cell from the time
7219 we sent the begin cell, not from the time the stream started. If
7220 it took a long time to establish the circuit, we would time out
7221 right after sending the begin cell.
7222 - Fix router_compare_addr_to_addr_policy: it was not treating a port
7223 of * as always matching, so we were picking reject *:* nodes as
7224 exit nodes too. Oops.
7227 - New circuit building strategy: keep a list of ports that we've
7228 used in the past 6 hours, and always try to have 2 circuits open
7229 or on the way that will handle each such port. Seed us with port
7230 80 so web users won't complain that Tor is "slow to start up".
7231 - Make kill -USR1 dump more useful stats about circuits.
7232 - When warning about retrying or giving up, print the address, so
7233 the user knows which one it's talking about.
7234 - If you haven't used a clean circuit in an hour, throw it away,
7235 just to be on the safe side. (This means after 6 hours a totally
7236 unused Tor client will have no circuits open.)
7239 Changes in version 0.0.9rc5 - 2004-12-01
7240 o Bugfixes on 0.0.8.1:
7241 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
7242 - Let resolve conns retry/expire also, rather than sticking around
7244 - If we are using select, make sure we stay within FD_SETSIZE.
7246 o Bugfixes on 0.0.9pre:
7247 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
7248 but doesn't seem to be currently; thanks to Ilja van Sprundel for
7250 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
7251 instead. Impose minima and maxima for all *Period options; impose
7252 even tighter maxima for fetching if we are a caching dirserver.
7253 Clip rather than rejecting.
7254 - Fetch cached running-routers from servers that serve it (that is,
7255 authdirservers and servers running 0.0.9rc5-cvs or later.)
7258 - Accept *:706 (silc) in default exit policy.
7259 - Implement new versioning format for post 0.1.
7260 - Support "foo.nickname.exit" addresses, to let Alice request the
7261 address "foo" as viewed by exit node "nickname". Based on a patch
7263 - Make tor --version --version dump the cvs Id of every file.
7266 Changes in version 0.0.9rc4 - 2004-11-28
7267 o Bugfixes on 0.0.8.1:
7268 - Make windows sockets actually non-blocking (oops), and handle
7269 win32 socket errors better.
7271 o Bugfixes on 0.0.9rc1:
7272 - Actually catch the -USR2 signal.
7275 Changes in version 0.0.9rc3 - 2004-11-25
7276 o Bugfixes on 0.0.8.1:
7277 - Flush the log file descriptor after we print "Tor opening log file",
7278 so we don't see those messages days later.
7280 o Bugfixes on 0.0.9rc1:
7281 - Make tor-resolve work again.
7282 - Avoid infinite loop in tor-resolve if tor hangs up on it.
7283 - Fix an assert trigger for clients/servers handling resolves.
7286 Changes in version 0.0.9rc2 - 2004-11-24
7287 o Bugfixes on 0.0.9rc1:
7288 - I broke socks5 support while fixing the eof bug.
7289 - Allow unitless bandwidths and intervals; they default to bytes
7291 - New servers don't start out hibernating; they are active until
7292 they run out of bytes, so they have a better estimate of how
7293 long it takes, and so their operators can know they're working.
7296 Changes in version 0.0.9rc1 - 2004-11-23
7297 o Bugfixes on 0.0.8.1:
7298 - Finally fix a bug that's been plaguing us for a year:
7299 With high load, circuit package window was reaching 0. Whenever
7300 we got a circuit-level sendme, we were reading a lot on each
7301 socket, but only writing out a bit. So we would eventually reach
7302 eof. This would be noticed and acted on even when there were still
7303 bytes sitting in the inbuf.
7304 - When poll() is interrupted, we shouldn't believe the revents values.
7306 o Bugfixes on 0.0.9pre6:
7307 - Fix hibernate bug that caused pre6 to be broken.
7308 - Don't keep rephist info for routers that haven't had activity for
7309 24 hours. (This matters now that clients have keys, since we track
7311 - Never call close_temp_logs while validating log options.
7312 - Fix backslash-escaping on tor.sh.in and torctl.in.
7315 - Implement weekly/monthly/daily accounting: now you specify your
7316 hibernation properties by
7317 AccountingMax N bytes|KB|MB|GB|TB
7318 AccountingStart day|week|month [day] HH:MM
7319 Defaults to "month 1 0:00".
7320 - Let bandwidth and interval config options be specified as 5 bytes,
7321 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
7322 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
7323 get back to normal.)
7324 - If your requested entry or exit node has advertised bandwidth 0,
7326 - Be more greedy about filling up relay cells -- we try reading again
7327 once we've processed the stuff we read, in case enough has arrived
7328 to fill the last cell completely.
7329 - Apply NT service patch from Osamu Fujino. Still needs more work.
7332 Changes in version 0.0.9pre6 - 2004-11-15
7333 o Bugfixes on 0.0.8.1:
7334 - Fix assert failure on malformed socks4a requests.
7335 - Use identity comparison, not nickname comparison, to choose which
7336 half of circuit-ID-space each side gets to use. This is needed
7337 because sometimes we think of a router as a nickname, and sometimes
7338 as a hex ID, and we can't predict what the other side will do.
7339 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
7340 write() call will fail and we handle it there.
7341 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
7342 and smartlist_len, which are two major profiling offenders.
7344 o Bugfixes on 0.0.9pre5:
7345 - Fix a bug in read_all that was corrupting config files on windows.
7346 - When we're raising the max number of open file descriptors to
7347 'unlimited', don't log that we just raised it to '-1'.
7348 - Include event code with events, as required by control-spec.txt.
7349 - Don't give a fingerprint when clients do --list-fingerprint:
7350 it's misleading, because it will never be the same again.
7351 - Stop using strlcpy in tor_strndup, since it was slowing us
7353 - Remove warn on startup about missing cached-directory file.
7354 - Make kill -USR1 work again.
7355 - Hibernate if we start tor during the "wait for wakeup-time" phase
7356 of an accounting interval. Log our hibernation plans better.
7357 - Authoritative dirservers now also cache their directory, so they
7358 have it on start-up.
7361 - Fetch running-routers; cache running-routers; compress
7362 running-routers; serve compressed running-routers.z
7363 - Add NSI installer script contributed by J Doe.
7364 - Commit VC6 and VC7 workspace/project files.
7365 - Commit a tor.spec for making RPM files, with help from jbash.
7366 - Add contrib/torctl.in contributed by Glenn Fink.
7367 - Implement the control-spec's SAVECONF command, to write your
7368 configuration to torrc.
7369 - Get cookie authentication for the controller closer to working.
7370 - Include control-spec.txt in the tarball.
7371 - When set_conf changes our server descriptor, upload a new copy.
7372 But don't upload it too often if there are frequent changes.
7373 - Document authentication config in man page, and document signals
7375 - Clean up confusing parts of man page and torrc.sample.
7376 - Make expand_filename handle ~ and ~username.
7377 - Use autoconf to enable largefile support where necessary. Use
7378 ftello where available, since ftell can fail at 2GB.
7379 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
7380 log more informatively.
7381 - Give a slightly more useful output for "tor -h".
7382 - Refuse application socks connections to port 0.
7383 - Check clock skew for verified servers, but allow unverified
7384 servers and clients to have any clock skew.
7385 - Break DirFetchPostPeriod into:
7386 - DirFetchPeriod for fetching full directory,
7387 - StatusFetchPeriod for fetching running-routers,
7388 - DirPostPeriod for posting server descriptor,
7389 - RendPostPeriod for posting hidden service descriptors.
7390 - Make sure the hidden service descriptors are at a random offset
7391 from each other, to hinder linkability.
7394 Changes in version 0.0.9pre5 - 2004-11-09
7395 o Bugfixes on 0.0.9pre4:
7396 - Fix a seg fault in unit tests (doesn't affect main program).
7397 - Fix an assert bug where a hidden service provider would fail if
7398 the first hop of his rendezvous circuit was down.
7399 - Hidden service operators now correctly handle version 1 style
7400 INTRODUCE1 cells (nobody generates them still, so not a critical
7402 - If do_hup fails, actually notice.
7403 - Handle more errnos from accept() without closing the listener.
7404 Some OpenBSD machines were closing their listeners because
7405 they ran out of file descriptors.
7406 - Send resolve cells to exit routers that are running a new
7407 enough version of the resolve code to work right.
7408 - Better handling of winsock includes on non-MSV win32 compilers.
7409 - Some people had wrapped their tor client/server in a script
7410 that would restart it whenever it died. This did not play well
7411 with our "shut down if your version is obsolete" code. Now people
7412 don't fetch a new directory if their local cached version is
7414 - Make our autogen.sh work on ksh as well as bash.
7417 - Hibernation: New config option "AccountingMaxKB" lets you
7418 set how many KBytes per month you want to allow your server to
7419 consume. Rather than spreading those bytes out evenly over the
7420 month, we instead hibernate for some of the month and pop up
7421 at a deterministic time, work until the bytes are consumed, then
7422 hibernate again. Config option "MonthlyAccountingStart" lets you
7423 specify which day of the month your billing cycle starts on.
7424 - Control interface: a separate program can now talk to your
7425 client/server over a socket, and get/set config options, receive
7426 notifications of circuits and streams starting/finishing/dying,
7427 bandwidth used, etc. The next step is to get some GUIs working.
7428 Let us know if you want to help out. See doc/control-spec.txt .
7429 - Ship a contrib/tor-control.py as an example script to interact
7430 with the control port.
7431 - "tor --hash-password zzyxz" will output a salted password for
7432 use in authenticating to the control interface.
7433 - New log format in config:
7434 "Log minsev[-maxsev] stdout|stderr|syslog" or
7435 "Log minsev[-maxsev] file /var/foo"
7438 - DirPolicy config option, to let people reject incoming addresses
7439 from their dirserver.
7440 - "tor --list-fingerprint" will list your identity key fingerprint
7442 - Add "pass" target for RedirectExit, to make it easier to break
7443 out of a sequence of RedirectExit rules.
7444 - Clients now generate a TLS cert too, in preparation for having
7445 them act more like real nodes.
7446 - Ship src/win32/ in the tarball, so people can use it to build.
7447 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
7449 - New "router-status" line in directory, to better bind each verified
7450 nickname to its identity key.
7451 - Deprecate unofficial config option abbreviations, and abbreviations
7452 not on the command line.
7453 - Add a pure-C tor-resolve implementation.
7454 - Use getrlimit and friends to ensure we can reach MaxConn (currently
7455 1024) file descriptors.
7457 o Code security improvements, inspired by Ilja:
7458 - Replace sprintf with snprintf. (I think they were all safe, but
7460 - Replace strcpy/strncpy with strlcpy in more places.
7461 - Avoid strcat; use snprintf or strlcat instead.
7462 - snprintf wrapper with consistent (though not C99) overflow behavior.
7465 Changes in version 0.0.9pre4 - 2004-10-17
7466 o Bugfixes on 0.0.9pre3:
7467 - If the server doesn't specify an exit policy, use the real default
7468 exit policy, not reject *:*.
7469 - Ignore fascistfirewall when uploading/downloading hidden service
7470 descriptors, since we go through Tor for those; and when using
7471 an HttpProxy, since we assume it can reach them all.
7472 - When looking for an authoritative dirserver, use only the ones
7473 configured at boot. Don't bother looking in the directory.
7474 - The rest of the fix for get_default_conf_file() on older win32.
7475 - Make 'Routerfile' config option obsolete.
7478 - New 'MyFamily nick1,...' config option for a server to
7479 specify other servers that shouldn't be used in the same circuit
7480 with it. Only believed if nick1 also specifies us.
7481 - New 'NodeFamily nick1,nick2,...' config option for a client to
7482 specify nodes that it doesn't want to use in the same circuit.
7483 - New 'Redirectexit pattern address:port' config option for a
7484 server to redirect exit connections, e.g. to a local squid.
7487 Changes in version 0.0.9pre3 - 2004-10-13
7488 o Bugfixes on 0.0.8.1:
7489 - Better torrc example lines for dirbindaddress and orbindaddress.
7490 - Improved bounds checking on parsed ints (e.g. config options and
7491 the ones we find in directories.)
7492 - Better handling of size_t vs int, so we're more robust on 64
7494 - Fix the rest of the bug where a newly started OR would appear
7495 as unverified even after we've added his fingerprint and hupped
7497 - Fix a bug from 0.0.7: when read() failed on a stream, we would
7498 close it without sending back an end. So 'connection refused'
7499 would simply be ignored and the user would get no response.
7501 o Bugfixes on 0.0.9pre2:
7502 - Serving the cached-on-disk directory to people is bad. We now
7503 provide no directory until we've fetched a fresh one.
7504 - Workaround for bug on windows where cached-directories get crlf
7506 - Make get_default_conf_file() work on older windows too.
7507 - If we write a *:* exit policy line in the descriptor, don't write
7508 any more exit policy lines.
7511 - Use only 0.0.9pre1 and later servers for resolve cells.
7512 - Make the dirservers file obsolete.
7513 - Include a dir-signing-key token in directories to tell the
7514 parsing entity which key is being used to sign.
7515 - Remove the built-in bulky default dirservers string.
7516 - New config option "Dirserver %s:%d [fingerprint]", which can be
7517 repeated as many times as needed. If no dirservers specified,
7518 default to moria1,moria2,tor26.
7519 - Make moria2 advertise a dirport of 80, so people behind firewalls
7520 will be able to get a directory.
7521 - Http proxy support
7522 - Dirservers translate requests for http://%s:%d/x to /x
7523 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
7524 be routed through this host.
7525 - Clients ask for /tor/x rather than /x for new enough dirservers.
7526 This way we can one day coexist peacefully with apache.
7527 - Clients specify a "Host: %s%d" http header, to be compatible
7528 with more proxies, and so running squid on an exit node can work.
7531 Changes in version 0.0.8.1 - 2004-10-13
7533 - Fix a seg fault that can be triggered remotely for Tor
7534 clients/servers with an open dirport.
7535 - Fix a rare assert trigger, where routerinfos for entries in
7536 our cpath would expire while we're building the path.
7537 - Fix a bug in OutboundBindAddress so it (hopefully) works.
7538 - Fix a rare seg fault for people running hidden services on
7539 intermittent connections.
7540 - Fix a bug in parsing opt keywords with objects.
7541 - Fix a stale pointer assert bug when a stream detaches and
7543 - Fix a string format vulnerability (probably not exploitable)
7544 in reporting stats locally.
7545 - Fix an assert trigger: sometimes launching circuits can fail
7546 immediately, e.g. because too many circuits have failed recently.
7547 - Fix a compile warning on 64 bit platforms.
7550 Changes in version 0.0.9pre2 - 2004-10-03
7552 - Make fetching a cached directory work for 64-bit platforms too.
7553 - Make zlib.h a required header, not an optional header.
7556 Changes in version 0.0.9pre1 - 2004-10-01
7558 - Stop using separate defaults for no-config-file and
7559 empty-config-file. Now you have to explicitly turn off SocksPort,
7560 if you don't want it open.
7561 - Fix a bug in OutboundBindAddress so it (hopefully) works.
7562 - Improve man page to mention more of the 0.0.8 features.
7563 - Fix a rare seg fault for people running hidden services on
7564 intermittent connections.
7565 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
7567 - Fix more dns related bugs: send back resolve_failed and end cells
7568 more reliably when the resolve fails, rather than closing the
7569 circuit and then trying to send the cell. Also attach dummy resolve
7570 connections to a circuit *before* calling dns_resolve(), to fix
7571 a bug where cached answers would never be sent in RESOLVED cells.
7572 - When we run out of disk space, or other log writing error, don't
7573 crash. Just stop logging to that log and continue.
7574 - We were starting to daemonize before we opened our logs, so if
7575 there were any problems opening logs, we would complain to stderr,
7576 which wouldn't work, and then mysteriously exit.
7577 - Fix a rare bug where sometimes a verified OR would connect to us
7578 before he'd uploaded his descriptor, which would cause us to
7579 assign conn->nickname as though he's unverified. Now we look through
7580 the fingerprint list to see if he's there.
7581 - Fix a rare assert trigger, where routerinfos for entries in
7582 our cpath would expire while we're building the path.
7585 - Clients can ask dirservers for /dir.z to get a compressed version
7586 of the directory. Only works for servers running 0.0.9, of course.
7587 - Make clients cache directories and use them to seed their router
7588 lists at startup. This means clients have a datadir again.
7589 - Configuration infrastructure support for warning on obsolete
7591 - Respond to content-encoding headers by trying to uncompress as
7593 - Reply with a deflated directory when a client asks for "dir.z".
7594 We could use allow-encodings instead, but allow-encodings isn't
7595 specified in HTTP 1.0.
7596 - Raise the max dns workers from 50 to 100.
7597 - Discourage people from setting their dirfetchpostperiod more often
7598 than once per minute.
7599 - Protect dirservers from overzealous descriptor uploading -- wait
7600 10 seconds after directory gets dirty, before regenerating.
7603 Changes in version 0.0.8 - 2004-08-25
7604 o Port it to SunOS 5.9 / Athena
7607 Changes in version 0.0.8rc2 - 2004-08-20
7608 o Make it compile on cygwin again.
7609 o When picking unverified routers, skip those with low uptime and/or
7610 low bandwidth, depending on what properties you care about.
7613 Changes in version 0.0.8rc1 - 2004-08-18
7614 o Changes from 0.0.7.3:
7616 - Fix assert triggers: if the other side returns an address 0.0.0.0,
7617 don't put it into the client dns cache.
7618 - If a begin failed due to exit policy, but we believe the IP address
7619 should have been allowed, switch that router to exitpolicy reject *:*
7620 until we get our next directory.
7622 - Clients choose nodes proportional to advertised bandwidth.
7623 - Avoid using nodes with low uptime as introduction points.
7624 - Handle servers with dynamic IP addresses: don't replace
7625 options->Address with the resolved one at startup, and
7626 detect our address right before we make a routerinfo each time.
7627 - 'FascistFirewall' option to pick dirservers and ORs on specific
7628 ports; plus 'FirewallPorts' config option to tell FascistFirewall
7629 which ports are open. (Defaults to 80,443)
7630 - Be more aggressive about trying to make circuits when the network
7631 has changed (e.g. when you unsuspend your laptop).
7632 - Check for time skew on http headers; report date in response to
7634 - If the entrynode config line has only one node, don't pick it as
7636 - Add strict{entry|exit}nodes config options. If set to 1, then
7637 we refuse to build circuits that don't include the specified entry
7639 - OutboundBindAddress config option, to bind to a specific
7640 IP address for outgoing connect()s.
7641 - End truncated log entries (e.g. directories) with "[truncated]".
7643 o Patches to 0.0.8preX:
7645 - Patches to compile and run on win32 again (maybe)?
7646 - Fix crash when looking for ~/.torrc with no $HOME set.
7647 - Fix a race bug in the unit tests.
7648 - Handle verified/unverified name collisions better when new
7649 routerinfo's arrive in a directory.
7650 - Sometimes routers were getting entered into the stats before
7651 we'd assigned their identity_digest. Oops.
7652 - Only pick and establish intro points after we've gotten a
7655 - AllowUnverifiedNodes config option to let circuits choose no-name
7656 routers in entry,middle,exit,introduction,rendezvous positions.
7657 Allow middle and rendezvous positions by default.
7658 - Add a man page for tor-resolve.
7661 Changes in version 0.0.7.3 - 2004-08-12
7662 o Stop dnsworkers from triggering an assert failure when you
7663 ask them to resolve the host "".
7666 Changes in version 0.0.8pre3 - 2004-08-09
7667 o Changes from 0.0.7.2:
7668 - Allow multiple ORs with same nickname in routerlist -- now when
7669 people give us one identity key for a nickname, then later
7670 another, we don't constantly complain until the first expires.
7671 - Remember used bandwidth (both in and out), and publish 15-minute
7672 snapshots for the past day into our descriptor.
7673 - You can now fetch $DIRURL/running-routers to get just the
7674 running-routers line, not the whole descriptor list. (But
7675 clients don't use this yet.)
7676 - When people mistakenly use Tor as an http proxy, point them
7677 at the tor-doc.html rather than the INSTALL.
7678 - Remove our mostly unused -- and broken -- hex_encode()
7679 function. Use base16_encode() instead. (Thanks to Timo Lindfors
7680 for pointing out this bug.)
7681 - Rotate onion keys every 12 hours, not every 2 hours, so we have
7682 fewer problems with people using the wrong key.
7683 - Change the default exit policy to reject the default edonkey,
7684 kazaa, gnutella ports.
7685 - Add replace_file() to util.[ch] to handle win32's rename().
7687 o Changes from 0.0.8preX:
7688 - Fix two bugs in saving onion keys to disk when rotating, so
7689 hopefully we'll get fewer people using old onion keys.
7690 - Fix an assert error that was making SocksPolicy not work.
7691 - Be willing to expire routers that have an open dirport -- it's
7692 just the authoritative dirservers we want to not forget.
7693 - Reject tor-resolve requests for .onion addresses early, so we
7694 don't build a whole rendezvous circuit and then fail.
7695 - When you're warning a server that he's unverified, don't cry
7697 - Fix a race condition: don't try to extend onto a connection
7698 that's still handshaking.
7699 - For servers in clique mode, require the conn to be open before
7700 you'll choose it for your path.
7701 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
7702 end relay cell, etc.
7703 - Measure bandwidth capacity over the last 24 hours, not just 12
7704 - Bugfix: authoritative dirservers were making and signing a new
7705 directory for each client, rather than reusing the cached one.
7708 Changes in version 0.0.8pre2 - 2004-08-04
7709 o Changes from 0.0.7.2:
7711 - Check directory signature _before_ you decide whether you're
7712 you're running an obsolete version and should exit.
7713 - Check directory signature _before_ you parse the running-routers
7714 list to decide who's running or verified.
7715 - Bugfixes and features:
7716 - Check return value of fclose while writing to disk, so we don't
7717 end up with broken files when servers run out of disk space.
7718 - Log a warning if the user uses an unsafe socks variant, so people
7719 are more likely to learn about privoxy or socat.
7720 - Dirservers now include RFC1123-style dates in the HTTP headers,
7721 which one day we will use to better detect clock skew.
7723 o Changes from 0.0.8pre1:
7724 - Make it compile without warnings again on win32.
7725 - Log a warning if you're running an unverified server, to let you
7726 know you might want to get it verified.
7727 - Only pick a default nickname if you plan to be a server.
7730 Changes in version 0.0.8pre1 - 2004-07-23
7732 - Made our unit tests compile again on OpenBSD 3.5, and tor
7733 itself compile again on OpenBSD on a sparc64.
7734 - We were neglecting milliseconds when logging on win32, so
7735 everything appeared to happen at the beginning of each second.
7738 - 'Extend' relay cell payloads now include the digest of the
7739 intended next hop's identity key. Now we can verify that we're
7740 extending to the right router, and also extend to routers we
7741 hadn't heard of before.
7744 - Tor nodes can now act as relays (with an advertised ORPort)
7745 without being manually verified by the dirserver operators.
7746 - Uploaded descriptors of unverified routers are now accepted
7747 by the dirservers, and included in the directory.
7748 - Verified routers are listed by nickname in the running-routers
7749 list; unverified routers are listed as "$<fingerprint>".
7750 - We now use hash-of-identity-key in most places rather than
7751 nickname or addr:port, for improved security/flexibility.
7752 - To avoid Sybil attacks, paths still use only verified servers.
7753 But now we have a chance to play around with hybrid approaches.
7754 - Nodes track bandwidth usage to estimate capacity (not used yet).
7755 - ClientOnly option for nodes that never want to become servers.
7756 - Directory caching.
7757 - "AuthoritativeDir 1" option for the official dirservers.
7758 - Now other nodes (clients and servers) will cache the latest
7759 directory they've pulled down.
7760 - They can enable their DirPort to serve it to others.
7761 - Clients will pull down a directory from any node with an open
7762 DirPort, and check the signature/timestamp correctly.
7763 - Authoritative dirservers now fetch directories from other
7764 authdirservers, to stay better synced.
7765 - Running-routers list tells who's down also, along with noting
7766 if they're verified (listed by nickname) or unverified (listed
7768 - Allow dirservers to serve running-router list separately.
7769 This isn't used yet.
7770 - ORs connect-on-demand to other ORs
7771 - If you get an extend cell to an OR you're not connected to,
7772 connect, handshake, and forward the create cell.
7773 - The authoritative dirservers stay connected to everybody,
7774 and everybody stays connected to 0.0.7 servers, but otherwise
7775 clients/servers expire unused connections after 5 minutes.
7776 - When servers get a sigint, they delay 30 seconds (refusing new
7777 connections) then exit. A second sigint causes immediate exit.
7778 - File and name management:
7779 - Look for .torrc if no CONFDIR "torrc" is found.
7780 - If no datadir is defined, then choose, make, and secure ~/.tor
7782 - If torrc not found, exitpolicy reject *:*.
7783 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
7784 - If no nickname is defined, derive default from hostname.
7785 - Rename secret key files, e.g. identity.key -> secret_id_key,
7786 to discourage people from mailing their identity key to tor-ops.
7787 - Refuse to build a circuit before the directory has arrived --
7788 it won't work anyway, since you won't know the right onion keys
7790 - Try other dirservers immediately if the one you try is down. This
7791 should tolerate down dirservers better now.
7792 - Parse tor version numbers so we can do an is-newer-than check
7793 rather than an is-in-the-list check.
7794 - New socks command 'resolve', to let us shim gethostbyname()
7796 - A 'tor_resolve' script to access the socks resolve functionality.
7797 - A new socks-extensions.txt doc file to describe our
7798 interpretation and extensions to the socks protocols.
7799 - Add a ContactInfo option, which gets published in descriptor.
7800 - Publish OR uptime in descriptor (and thus in directory) too.
7801 - Write tor version at the top of each log file
7802 - New docs in the tarball:
7804 - Document that you should proxy your SSL traffic too.
7807 Changes in version 0.0.7.2 - 2004-07-07
7808 o A better fix for the 0.0.0.0 problem, that will hopefully
7809 eliminate the remaining related assertion failures.
7812 Changes in version 0.0.7.1 - 2004-07-04
7813 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
7814 since internally we use 0.0.0.0 to signify "not yet resolved".
7817 Changes in version 0.0.7 - 2004-06-07
7818 o Updated the man page to reflect the new features.
7821 Changes in version 0.0.7rc2 - 2004-06-06
7822 o Changes from 0.0.7rc1:
7823 - Make it build on Win32 again.
7824 o Changes from 0.0.6.2:
7825 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
7829 Changes in version 0.0.7rc1 - 2004-06-02
7831 - On sighup, we were adding another log without removing the first
7832 one. So log messages would get duplicated n times for n sighups.
7833 - Several cases of using a connection after we'd freed it. The
7834 problem was that connections that are pending resolve are in both
7835 the pending_resolve tree, and also the circuit's resolving_streams
7836 list. When you want to remove one, you must remove it from both.
7837 - Fix a double-mark-for-close where an end cell arrived for a
7838 resolving stream, and then the resolve failed.
7839 - Check directory signatures based on name of signer, not on whom
7840 we got the directory from. This will let us cache directories more
7843 - Crank up some of our constants to handle more users.
7846 Changes in version 0.0.7pre1 - 2004-06-02
7847 o Fixes for crashes and other obnoxious bugs:
7848 - Fix an epipe bug: sometimes when directory connections failed
7849 to connect, we would give them a chance to flush before closing
7851 - When we detached from a circuit because of resolvefailed, we
7852 would immediately try the same circuit twice more, and then
7853 give up on the resolve thinking we'd tried three different
7855 - Limit the number of intro circuits we'll attempt to build for a
7856 hidden service per 15-minute period.
7857 - Check recommended-software string *early*, before actually parsing
7858 the directory. Thus we can detect an obsolete version and exit,
7859 even if the new directory format doesn't parse.
7860 o Fixes for security bugs:
7861 - Remember which nodes are dirservers when you startup, and if a
7862 random OR enables his dirport, don't automatically assume he's
7863 a trusted dirserver.
7865 - Directory connections were asking the wrong poll socket to
7866 start writing, and not asking themselves to start writing.
7867 - When we detached from a circuit because we sent a begin but
7868 didn't get a connected, we would use it again the first time;
7869 but after that we would correctly switch to a different one.
7870 - Stop warning when the first onion decrypt attempt fails; they
7871 will sometimes legitimately fail now that we rotate keys.
7872 - Override unaligned-access-ok check when $host_cpu is ia64 or
7873 arm. Apparently they allow it but the kernel whines.
7874 - Dirservers try to reconnect periodically too, in case connections
7876 - Fix some memory leaks in directory servers.
7877 - Allow backslash in Win32 filenames.
7878 - Made Tor build complain-free on FreeBSD, hopefully without
7879 breaking other BSD builds. We'll see.
7881 - Doxygen markup on all functions and global variables.
7882 - Make directory functions update routerlist, not replace it. So
7883 now directory disagreements are not so critical a problem.
7884 - Remove the upper limit on number of descriptors in a dirserver's
7885 directory (not that we were anywhere close).
7886 - Allow multiple logfiles at different severity ranges.
7887 - Allow *BindAddress to specify ":port" rather than setting *Port
7888 separately. Allow multiple instances of each BindAddress config
7889 option, so you can bind to multiple interfaces if you want.
7890 - Allow multiple exit policy lines, which are processed in order.
7891 Now we don't need that huge line with all the commas in it.
7892 - Enable accept/reject policies on SOCKS connections, so you can bind
7893 to 0.0.0.0 but still control who can use your OP.
7896 Changes in version 0.0.6.2 - 2004-05-16
7897 o Our integrity-checking digest was checking only the most recent cell,
7898 not the previous cells like we'd thought.
7899 Thanks to Stefan Mark for finding the flaw!
7902 Changes in version 0.0.6.1 - 2004-05-06
7903 o Fix two bugs in our AES counter-mode implementation (this affected
7904 onion-level stream encryption, but not TLS-level). It turns
7905 out we were doing something much more akin to a 16-character
7906 polyalphabetic cipher. Oops.
7907 Thanks to Stefan Mark for finding the flaw!
7908 o Retire moria3 as a directory server, and add tor26 as a directory
7912 Changes in version 0.0.6 - 2004-05-02
7916 Changes in version 0.0.6rc4 - 2004-05-01
7917 o Update the built-in dirservers list to use the new directory format
7918 o Fix a rare seg fault: if a node offering a hidden service attempts
7919 to build a circuit to Alice's rendezvous point and fails before it
7920 reaches the last hop, it retries with a different circuit, but
7922 o Handle windows socket errors correctly.
7925 Changes in version 0.0.6rc3 - 2004-04-28
7926 o Don't expire non-general excess circuits (if we had enough
7927 circuits open, we were expiring rendezvous circuits -- even
7928 when they had a stream attached. oops.)
7929 o Fetch randomness from /dev/urandom better (not via fopen/fread)
7930 o Better debugging for tls errors
7931 o Some versions of openssl have an SSL_pending function that erroneously
7932 returns bytes when there is a non-application record pending.
7933 o Set Content-Type on the directory and hidserv descriptor.
7934 o Remove IVs from cipher code, since AES-ctr has none.
7935 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
7936 o We were using an array of length zero in a few places.
7937 o win32's gethostbyname can't resolve an IP to an IP.
7938 o win32's close can't close a socket.
7941 Changes in version 0.0.6rc2 - 2004-04-26
7942 o Fix a bug where we were closing tls connections intermittently.
7943 It turns out openssl keeps its errors around -- so if an error
7944 happens, and you don't ask about it, and then another openssl
7945 operation happens and succeeds, and you ask if there was an error,
7946 it tells you about the first error. Fun fun.
7947 o Fix a bug that's been lurking since 27 may 03 (!)
7948 When passing back a destroy cell, we would use the wrong circ id.
7949 'Mostly harmless', but still worth fixing.
7950 o Since we don't support truncateds much, don't bother sending them;
7951 just close the circ.
7952 o check for <machine/limits.h> so we build on NetBSD again (I hope).
7953 o don't crash if a conn that sent a begin has suddenly lost its circuit
7954 (this was quite rare).
7957 Changes in version 0.0.6rc1 - 2004-04-25
7958 o We now rotate link (tls context) keys and onion keys.
7959 o CREATE cells now include oaep padding, so you can tell
7960 if you decrypted them correctly.
7961 o Add bandwidthburst to server descriptor.
7962 o Directories now say which dirserver signed them.
7963 o Use a tor_assert macro that logs failed assertions too.
7966 Changes in version 0.0.6pre5 - 2004-04-18
7967 o changes from 0.0.6pre4:
7968 - make tor build on broken freebsd 5.2 installs
7969 - fix a failed assert when you try an intro point, get a nack, and try
7970 a second one and it works.
7971 - when alice uses a port that the hidden service doesn't accept,
7972 it now sends back an end cell (denied by exit policy). otherwise
7973 alice would just have to wait to time out.
7974 - fix another rare bug: when we had tried all the intro
7975 points for a hidden service, we fetched the descriptor
7976 again, but we left our introcirc thinking it had already
7977 sent an intro, so it kept waiting for a response...
7978 - bugfix: when you sleep your hidden-service laptop, as soon
7979 as it wakes up it tries to upload a service descriptor, but
7980 socketpair fails for some reason (localhost not up yet?).
7981 now we simply give up on that upload, and we'll try again later.
7982 i'd still like to find the bug though.
7983 - if an intro circ waiting for an ack dies before getting one, then
7985 - we were reusing stale service descriptors and refetching usable
7989 Changes in version 0.0.6pre4 - 2004-04-14
7990 o changes from 0.0.6pre3:
7991 - when bob fails to connect to the rendezvous point, and his
7992 circ didn't fail because of the rendezvous point itself, then
7993 he retries a couple of times
7994 - we expire introduction and rendezvous circs more thoroughly
7995 (sometimes they were hanging around forever)
7996 - we expire unattached rendezvous streams that have been around
7997 too long (they were sticking around forever).
7998 - fix a measly fencepost error that was crashing everybody with
8002 Changes in version 0.0.6pre3 - 2004-04-14
8003 o changes from 0.0.6pre2:
8004 - make hup work again
8005 - fix some memory leaks for dirservers
8006 - allow more skew in rendezvous descriptor timestamps, to help
8007 handle people like blanu who don't know what time it is
8008 - normal circs are 3 hops, but some rend/intro circs are 4, if
8009 the initiator doesn't get to choose the last hop
8010 - send acks for introductions, so alice can know whether to try
8012 - bob publishes intro points more correctly
8013 o changes from 0.0.5:
8014 - fix an assert trigger that's been plaguing us since the days
8015 of 0.0.2prexx (thanks weasel!)
8016 - retry stream correctly when we fail to connect because of
8017 exit-policy-reject (should try another) or can't-resolve-address
8018 (also should try another, because dns on random internet servers
8020 - when we hup a dirserver and we've *removed* a server from the
8021 approved-routers list, now we remove that server from the
8022 in-memory directories too
8025 Changes in version 0.0.6pre2 - 2004-04-08
8026 o We fixed our base32 implementation. Now it works on all architectures.
8029 Changes in version 0.0.6pre1 - 2004-04-08
8031 - Hidden services and rendezvous points are implemented. Go to
8032 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
8033 hidden services. (This only works via a socks4a proxy such as
8034 Privoxy, and currently it's quite slow.)
8037 Changes in version 0.0.5 - 2004-03-30
8041 Changes in version 0.0.5rc3 - 2004-03-29
8042 o Install torrc as torrc.sample -- we no longer clobber your
8044 o Re-enable recommendedversion checking (we broke it in rc2, oops)
8045 o Add in a 'notice' log level for things the operator should hear
8046 but that aren't warnings
8049 Changes in version 0.0.5rc2 - 2004-03-29
8050 o Hold socks connection open until reply is flushed (if possible)
8051 o Make exit nodes resolve IPs to IPs immediately, rather than asking
8052 the dns farm to do it.
8053 o Fix c99 aliasing warnings in rephist.c
8054 o Don't include server descriptors that are older than 24 hours in the
8056 o Give socks 'reject' replies their whole 15s to attempt to flush,
8057 rather than seeing the 60s timeout and assuming the flush had failed.
8058 o Clean automake droppings from the cvs repository
8061 Changes in version 0.0.5rc1 - 2004-03-28
8062 o Fix mangled-state bug in directory fetching (was causing sigpipes).
8063 o Only build circuits after we've fetched the directory: clients were
8064 using only the directory servers before they'd fetched a directory.
8065 This also means longer startup time; so it goes.
8066 o Fix an assert trigger where an OP would fail to handshake, and we'd
8067 expect it to have a nickname.
8068 o Work around a tsocks bug: do a socks reject when AP connection dies
8069 early, else tsocks goes into an infinite loop.
8072 Changes in version 0.0.4 - 2004-03-26
8073 o When connecting to a dirserver or OR and the network is down,
8077 Changes in version 0.0.3 - 2004-03-26
8078 o Warn and fail if server chose a nickname with illegal characters
8079 o Port to Solaris and Sparc:
8080 - include missing header fcntl.h
8081 - have autoconf find -lsocket -lnsl automatically
8082 - deal with hardware word alignment
8083 - make uname() work (solaris has a different return convention)
8084 - switch from using signal() to sigaction()
8085 o Preliminary work on reputation system:
8086 - Keep statistics on success/fail of connect attempts; they're published
8087 by kill -USR1 currently.
8088 - Add a RunTesting option to try to learn link state by creating test
8089 circuits, even when SocksPort is off.
8090 - Remove unused open circuits when there are too many.
8093 Changes in version 0.0.2 - 2004-03-19
8094 - Include strlcpy and strlcat for safer string ops
8095 - define INADDR_NONE so we compile (but still not run) on solaris
8098 Changes in version 0.0.2pre27 - 2004-03-14
8100 - Allow internal tor networks (we were rejecting internal IPs,
8101 now we allow them if they're set explicitly).
8102 - And fix a few endian issues.
8105 Changes in version 0.0.2pre26 - 2004-03-14
8107 - If a stream times out after 15s without a connected cell, don't
8108 try that circuit again: try a new one.
8109 - Retry streams at most 4 times. Then give up.
8110 - When a dirserver gets a descriptor from an unknown router, it
8111 logs its fingerprint (so the dirserver operator can choose to
8112 accept it even without mail from the server operator).
8113 - Inform unapproved servers when we reject their descriptors.
8114 - Make tor build on Windows again. It works as a client, who knows
8116 - Clearer instructions in the torrc for how to set up a server.
8117 - Be more efficient about reading fd's when our global token bucket
8118 (used for rate limiting) becomes empty.
8120 - Stop asserting that computers always go forward in time. It's
8122 - When we sent a cell (e.g. destroy) and then marked an OR connection
8123 expired, we might close it before finishing a flush if the other
8124 side isn't reading right then.
8125 - Don't allow dirservers to start if they haven't defined
8127 - We were caching transient dns failures. Oops.
8128 - Prevent servers from publishing an internal IP as their address.
8129 - Address a strcat vulnerability in circuit.c
8132 Changes in version 0.0.2pre25 - 2004-03-04
8134 - Put the OR's IP in its router descriptor, not its fqdn. That way
8135 we'll stop being stalled by gethostbyname for nodes with flaky dns,
8138 - If the user typed in an address that didn't resolve, the server
8142 Changes in version 0.0.2pre24 - 2004-03-03
8144 - Fix an assertion failure in dns.c, where we were trying to dequeue
8145 a pending dns resolve even if it wasn't pending
8146 - Fix a spurious socks5 warning about still trying to write after the
8147 connection is finished.
8148 - Hold certain marked_for_close connections open until they're finished
8149 flushing, rather than losing bytes by closing them too early.
8150 - Correctly report the reason for ending a stream
8151 - Remove some duplicate calls to connection_mark_for_close
8152 - Put switch_id and start_daemon earlier in the boot sequence, so it
8153 will actually try to chdir() to options.DataDirectory
8154 - Make 'make test' exit(1) if a test fails; fix some unit tests
8155 - Make tor fail when you use a config option it doesn't know about,
8156 rather than warn and continue.
8157 - Make --version work
8158 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
8161 Changes in version 0.0.2pre23 - 2004-02-29
8163 - Print a statement when the first circ is finished, so the user
8165 - If a relay cell is unrecognized at the end of the circuit,
8166 send back a destroy. (So attacks to mutate cells are more
8168 - New config option 'excludenodes' to avoid certain nodes for circuits.
8169 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
8170 so you can collect coredumps there.
8172 - Fix a bug in tls flushing where sometimes data got wedged and
8173 didn't flush until more data got sent. Hopefully this bug was
8174 a big factor in the random delays we were seeing.
8175 - Make 'connected' cells include the resolved IP, so the client
8176 dns cache actually gets populated.
8177 - Disallow changing from ORPort=0 to ORPort>0 on hup.
8178 - When we time-out on a stream and detach from the circuit, send an
8179 end cell down it first.
8180 - Only warn about an unknown router (in exitnodes, entrynodes,
8181 excludenodes) after we've fetched a directory.
8184 Changes in version 0.0.2pre22 - 2004-02-26
8186 - Servers publish less revealing uname information in descriptors.
8187 - More memory tracking and assertions, to crash more usefully when
8189 - If the default torrc isn't there, just use some default defaults.
8190 Plus provide an internal dirservers file if they don't have one.
8191 - When the user tries to use Tor as an http proxy, give them an http
8192 501 failure explaining that we're a socks proxy.
8193 - Dump a new router.desc on hup, to help confused people who change
8194 their exit policies and then wonder why router.desc doesn't reflect
8196 - Clean up the generic tor.sh init script that we ship with.
8198 - If the exit stream is pending on the resolve, and a destroy arrives,
8199 then the stream wasn't getting removed from the pending list. I
8200 think this was the one causing recent server crashes.
8201 - Use a more robust poll on OSX 10.3, since their poll is flaky.
8202 - When it couldn't resolve any dirservers, it was useless from then on.
8203 Now it reloads the RouterFile (or default dirservers) if it has no
8205 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
8206 many users don't even *have* a /usr/local/sbin/.
8209 Changes in version 0.0.2pre21 - 2004-02-18
8211 - There's a ChangeLog file that actually reflects the changelog.
8212 - There's a 'torify' wrapper script, with an accompanying
8213 tor-tsocks.conf, that simplifies the process of using tsocks for
8214 tor. It even has a man page.
8215 - The tor binary gets installed to sbin rather than bin now.
8216 - Retry streams where the connected cell hasn't arrived in 15 seconds
8217 - Clean up exit policy handling -- get the default out of the torrc,
8218 so we can update it without forcing each server operator to fix
8220 - Allow imaps and pop3s in default exit policy
8222 - Prevent picking middleman nodes as the last node in the circuit
8225 Changes in version 0.0.2pre20 - 2004-01-30
8227 - We now have a deb package, and it's in debian unstable. Go to
8229 - I've split the TotalBandwidth option into BandwidthRate (how many
8230 bytes per second you want to allow, long-term) and
8231 BandwidthBurst (how many bytes you will allow at once before the cap
8232 kicks in). This better token bucket approach lets you, say, set
8233 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
8234 performance while not exceeding your monthly bandwidth quota.
8235 - Push out a tls record's worth of data once you've got it, rather
8236 than waiting until you've read everything waiting to be read. This
8237 may improve performance by pipelining better. We'll see.
8238 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
8239 from failed circuits (if they haven't been connected yet) and attach
8241 - Expire old streams that haven't managed to connect. Some day we'll
8242 have them reattach to new circuits instead.
8245 - Fix several memory leaks that were causing servers to become bloated
8247 - Fix a few very rare assert triggers. A few more remain.
8248 - Setuid to User _before_ complaining about running as root.
8251 Changes in version 0.0.2pre19 - 2004-01-07
8253 - Fix deadlock condition in dns farm. We were telling a child to die by
8254 closing the parent's file descriptor to him. But newer children were
8255 inheriting the open file descriptor from the parent, and since they
8256 weren't closing it, the socket never closed, so the child never read
8257 eof, so he never knew to exit. Similarly, dns workers were holding
8258 open other sockets, leading to all sorts of chaos.
8259 - New cleaner daemon() code for forking and backgrounding.
8260 - If you log to a file, it now prints an entry at the top of the
8261 logfile so you know it's working.
8262 - The onionskin challenge length was 30 bytes longer than necessary.
8263 - Started to patch up the spec so it's not quite so out of date.
8266 Changes in version 0.0.2pre18 - 2004-01-02
8268 - Fix endian issues with the 'integrity' field in the relay header.
8269 - Fix a potential bug where connections in state
8270 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
8273 Changes in version 0.0.2pre17 - 2003-12-30
8275 - Made --debuglogfile (or any second log file, actually) work.
8276 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
8277 adversary could force us into an infinite loop.
8280 - Each onionskin handshake now includes a hash of the computed key,
8281 to prove the server's identity and help perfect forward secrecy.
8282 - Changed cell size from 256 to 512 bytes (working toward compatibility
8284 - Changed cell length to 2 bytes, and moved it to the relay header.
8285 - Implemented end-to-end integrity checking for the payloads of
8287 - Separated streamid from 'recognized' (otherwise circuits will get
8288 messed up when we try to have streams exit from the middle). We
8289 use the integrity-checking to confirm that a cell is addressed to
8291 - Randomize the initial circid and streamid values, so an adversary who
8292 breaks into a node can't learn how many circuits or streams have
8296 Changes in version 0.0.2pre16 - 2003-12-14
8298 - Fixed a bug that made HUP trigger an assert
8299 - Fixed a bug where a circuit that immediately failed wasn't being
8300 counted as a failed circuit in counting retries.
8303 - Now we close the circuit when we get a truncated cell: otherwise we're
8304 open to an anonymity attack where a bad node in the path truncates
8305 the circuit and then we open streams at him.
8306 - Add port ranges to exit policies
8307 - Add a conservative default exit policy
8308 - Warn if you're running tor as root
8309 - on HUP, retry OR connections and close/rebind listeners
8310 - options.EntryNodes: try these nodes first when picking the first node
8311 - options.ExitNodes: if your best choices happen to include any of
8312 your preferred exit nodes, you choose among just those preferred
8314 - options.ExcludedNodes: nodes that are never picked in path building
8317 Changes in version 0.0.2pre15 - 2003-12-03
8318 o Robustness and bugfixes:
8319 - Sometimes clients would cache incorrect DNS resolves, which would
8320 really screw things up.
8321 - An OP that goes offline would slowly leak all its sockets and stop
8323 - A wide variety of bugfixes in exit node selection, exit policy
8324 handling, and processing pending streams when a new circuit is
8326 - Pick nodes for a path only from those the directory says are up
8327 - Choose randomly from all running dirservers, not always the first one
8328 - Increase allowed http header size for directory fetch.
8329 - Stop writing to stderr (if we're daemonized it will be closed).
8330 - Enable -g always, so cores will be more useful to me.
8331 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
8334 - Wrote a man page. It lists commonly used options.
8337 - Change default loglevel to warn.
8338 - Make PidFile default to null rather than littering in your CWD.
8339 - OnionRouter config option is now obsolete. Instead it just checks
8341 - Moved to a single unified torrc file for both clients and servers.
8344 Changes in version 0.0.2pre14 - 2003-11-29
8345 o Robustness and bugfixes:
8346 - Force the admin to make the DataDirectory himself
8347 - to get ownership/permissions right
8348 - so clients no longer make a DataDirectory and then never use it
8349 - fix bug where a client who was offline for 45 minutes would never
8350 pull down a directory again
8351 - fix (or at least hide really well) the dns assert bug that was
8352 causing server crashes
8353 - warnings and improved robustness wrt clockskew for certs
8354 - use the native daemon(3) to daemonize, when available
8355 - exit if bind() fails
8356 - exit if neither socksport nor orport is defined
8357 - include our own tor_timegm (Win32 doesn't have its own)
8358 - bugfix for win32 with lots of connections
8359 - fix minor bias in PRNG
8360 - make dirserver more robust to corrupt cached directory
8363 - Wrote the design document (woo)
8365 o Circuit building and exit policies:
8366 - Circuits no longer try to use nodes that the directory has told them
8368 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
8369 bitcounts (18.0.0.0/8).
8370 - Make AP connections standby for a circuit if no suitable circuit
8371 exists, rather than failing
8372 - Circuits choose exit node based on addr/port, exit policies, and
8373 which AP connections are standing by
8374 - Bump min pathlen from 2 to 3
8375 - Relay end cells have a payload to describe why the stream ended.
8376 - If the stream failed because of exit policy, try again with a new
8378 - Clients have a dns cache to remember resolved addresses.
8379 - Notice more quickly when we have no working circuits
8382 - APPort is now called SocksPort
8383 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
8385 - RecommendedVersions is now a config variable rather than
8386 hardcoded (for dirservers)
8387 - Reloads config on HUP
8388 - Usage info on -h or --help
8389 - If you set User and Group config vars, it'll setu/gid to them.
8392 Changes in version 0.0.2pre13 - 2003-10-19
8393 o General stability:
8394 - SSL_write no longer fails when it returns WANTWRITE and the number
8395 of bytes in the buf has changed by the next SSL_write call.
8396 - Fix segfault fetching directory when network is down
8397 - Fix a variety of minor memory leaks
8398 - Dirservers reload the fingerprints file on HUP, so I don't have
8399 to take down the network when I approve a new router
8400 - Default server config file has explicit Address line to specify fqdn
8403 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
8404 - Make listener connections not ever alloc bufs
8406 o Autoconf improvements:
8407 - don't clobber an external CFLAGS in ./configure
8408 - Make install now works
8409 - create var/lib/tor on make install
8410 - autocreate a tor.sh initscript to help distribs
8411 - autocreate the torrc and sample-server-torrc with correct paths
8413 o Log files and Daemonizing now work:
8414 - If --DebugLogFile is specified, log to it at -l debug
8415 - If --LogFile is specified, use it instead of commandline
8416 - If --RunAsDaemon is set, tor forks and backgrounds on startup