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