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