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