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