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