1 Changes in version 0.2.1.15??? - ????-??-??
3 - Actually return -1 in the error case for read_bandwidth_usage. Bug
4 was harmless, we currently don't care for the return value anywhere.
5 Bugfix on 0.2.0.9-alpha.
6 - Provide a more useful log message if bug 977 (related to buffer
7 freelists) ever reappears, and do not crash right away.
10 Changes in version 0.2.1.14-rc - 2009-04-12
12 - Clients replace entry guards that were chosen more than a few months
13 ago. This change should significantly improve client performance,
14 especially once more people upgrade, since relays that have been
15 a guard for a long time are currently overloaded.
17 o Major bugfixes (on 0.2.0):
18 - Finally fix the bug where dynamic-IP relays disappear when their
19 IP address changes: directory mirrors were mistakenly telling
20 them their old address if they asked via begin_dir, so they
21 never got an accurate answer about their new address, so they
22 just vanished after a day. For belt-and-suspenders, relays that
23 don't set Address in their config now avoid using begin_dir for
24 all direct connections. Should fix bugs 827, 883, and 900.
25 - Relays were falling out of the networkstatus consensus for
26 part of a day if they changed their local config but the
27 authorities discarded their new descriptor as "not sufficiently
28 different". Now directory authorities accept a descriptor as changed
29 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
31 - Avoid crashing in the presence of certain malformed descriptors.
32 Found by lark, and by automated fuzzing.
35 - When generating circuit events with verbose nicknames for
36 controllers, try harder to look up nicknames for routers on a
37 circuit. (Previously, we would look in the router descriptors we had
38 for nicknames, but not in the consensus.) Partial fix for bug 941.
39 - If the bridge config line doesn't specify a port, assume 443.
40 This makes bridge lines a bit smaller and easier for users to
42 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
43 bytes (aka 20KB/s), to match our documentation. Also update
44 directory authorities so they always assign the Fast flag to relays
45 with 20KB/s of capacity. Now people running relays won't suddenly
46 find themselves not seeing any use, if the network gets faster
48 - Update to the "April 3 2009" ip-to-country file.
51 - Avoid trying to print raw memory to the logs when we decide to
52 give up on downloading a given relay descriptor. Bugfix on
54 - In tor-resolve, when the Tor client to use is specified by
55 <hostname>:<port>, actually use the specified port rather than
56 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
57 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
58 - When starting with a cache over a few days old, do not leak
59 memory for the obsolete router descriptors in it. Bugfix on
61 - Avoid double-free on list of successfully uploaded hidden
62 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
63 - Change memarea_strndup() implementation to work even when
64 duplicating a string at the end of a page. This bug was
65 harmless for now, but could have meant crashes later. Fix by
66 lark. Bugfix on 0.2.1.1-alpha.
67 - Limit uploaded directory documents to be 16M rather than 500K.
68 The directory authorities were refusing v3 consensus votes from
69 other authorities, since the votes are now 504K. Fixes bug 959;
70 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
71 - Directory authorities should never send a 503 "busy" response to
72 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
76 Changes in version 0.2.1.13-alpha - 2009-03-09
77 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
78 cleanups. We're finally getting close to a release candidate.
81 - Correctly update the list of which countries we exclude as
82 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
83 lark. Bugfix on 0.2.1.6-alpha.
85 o Minor bugfixes (on 0.2.0.x and earlier):
86 - Automatically detect MacOSX versions earlier than 10.4.0, and
87 disable kqueue from inside Tor when running with these versions.
88 We previously did this from the startup script, but that was no
89 help to people who didn't use the startup script. Resolves bug 863.
90 - When we had picked an exit node for a connection, but marked it as
91 "optional", and it turned out we had no onion key for the exit,
92 stop wanting that exit and try again. This situation may not
93 be possible now, but will probably become feasible with proposal
94 158. Spotted by rovv. Fixes another case of bug 752.
95 - Clients no longer cache certificates for authorities they do not
96 recognize. Bugfix on 0.2.0.9-alpha.
97 - When we can't transmit a DNS request due to a network error, retry
98 it after a while, and eventually transmit a failing response to
99 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
100 - If the controller claimed responsibility for a stream, but that
101 stream never finished making its connection, it would live
102 forever in circuit_wait state. Now we close it after SocksTimeout
103 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
104 - Drop begin cells to a hidden service if they come from the middle
105 of a circuit. Patch from lark.
106 - When we erroneously receive two EXTEND cells for the same circuit
107 ID on the same connection, drop the second. Patch from lark.
108 - Fix a crash that occurs on exit nodes when a nameserver request
109 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
110 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
112 - Do not assume that a stack-allocated character array will be
113 64-bit aligned on platforms that demand that uint64_t access is
114 aligned. Possible fix for bug 604.
115 - Parse dates and IPv4 addresses in a locale- and libc-independent
116 manner, to avoid platform-dependent behavior on malformed input.
117 - Build correctly when configured to build outside the main source
118 path. Patch from Michael Gold.
119 - We were already rejecting relay begin cells with destination port
120 of 0. Now also reject extend cells with destination port or address
121 of 0. Suggested by lark.
123 o Minor bugfixes (on 0.2.1.x):
124 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
125 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
126 - If we're an exit node, scrub the IP address to which we are exiting
127 in the logs. Bugfix on 0.2.1.8-alpha.
130 - On Linux, use the prctl call to re-enable core dumps when the user
132 - New controller event NEWCONSENSUS that lists the networkstatus
133 lines for every recommended relay. Now controllers like Torflow
134 can keep up-to-date on which relays they should be using.
135 - Update to the "February 26 2009" ip-to-country file.
138 Changes in version 0.2.0.34 - 2009-02-08
139 Tor 0.2.0.34 features several more security-related fixes. You should
140 upgrade, especially if you run an exit relay (remote crash) or a
141 directory authority (remote infinite loop), or you're on an older
142 (pre-XP) or not-recently-patched Windows (remote exploit).
144 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
145 have many known flaws, and nobody should be using them. You should
146 upgrade. If you're using a Linux or BSD and its packages are obsolete,
147 stop using those packages and upgrade anyway.
150 - Fix an infinite-loop bug on handling corrupt votes under certain
151 circumstances. Bugfix on 0.2.0.8-alpha.
152 - Fix a temporary DoS vulnerability that could be performed by
153 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
154 - Avoid a potential crash on exit nodes when processing malformed
155 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
156 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
157 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
160 - Fix compilation on systems where time_t is a 64-bit integer.
161 Patch from Matthias Drochner.
162 - Don't consider expiring already-closed client connections. Fixes
163 bug 893. Bugfix on 0.0.2pre20.
166 Changes in version 0.2.1.12-alpha - 2009-02-08
167 Tor 0.2.1.12-alpha features several more security-related fixes. You
168 should upgrade, especially if you run an exit relay (remote crash) or
169 a directory authority (remote infinite loop), or you're on an older
170 (pre-XP) or not-recently-patched Windows (remote exploit). It also
171 includes a big pile of minor bugfixes and cleanups.
174 - Fix an infinite-loop bug on handling corrupt votes under certain
175 circumstances. Bugfix on 0.2.0.8-alpha.
176 - Fix a temporary DoS vulnerability that could be performed by
177 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
178 - Avoid a potential crash on exit nodes when processing malformed
179 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
182 - Let controllers actually ask for the "clients_seen" event for
183 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
184 reported by Matt Edman.
185 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
187 - Fix a bug in address parsing that was preventing bridges or hidden
188 service targets from being at IPv6 addresses.
189 - Solve a bug that kept hardware crypto acceleration from getting
190 enabled when accounting was turned on. Fixes bug 907. Bugfix on
192 - Remove a bash-ism from configure.in to build properly on non-Linux
193 platforms. Bugfix on 0.2.1.1-alpha.
194 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
195 headers. Bugfix on 0.2.0.10-alpha.
196 - Don't consider expiring already-closed client connections. Fixes
197 bug 893. Bugfix on 0.0.2pre20.
198 - Fix another interesting corner-case of bug 891 spotted by rovv:
199 Previously, if two hosts had different amounts of clock drift, and
200 one of them created a new connection with just the wrong timing,
201 the other might decide to deprecate the new connection erroneously.
202 Bugfix on 0.1.1.13-alpha.
203 - Resolve a very rare crash bug that could occur when the user forced
204 a nameserver reconfiguration during the middle of a nameserver
205 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
206 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
207 Bugfix on 0.2.1.7-alpha.
208 - If we're using bridges and our network goes away, be more willing
209 to forgive our bridges and try again when we get an application
210 request. Bugfix on 0.2.0.x.
213 - Support platforms where time_t is 64 bits long. (Congratulations,
214 NetBSD!) Patch from Matthias Drochner.
215 - Add a 'getinfo status/clients-seen' controller command, in case
216 controllers want to hear clients_seen events but connect late.
219 - Disable GCC's strict alias optimization by default, to avoid the
220 likelihood of its introducing subtle bugs whenever our code violates
221 the letter of C99's alias rules.
224 Changes in version 0.2.0.33 - 2009-01-21
225 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
226 useful to users. It also finally fixes a bug where a relay or client
227 that's been off for many days would take a long time to bootstrap.
229 This update also fixes an important security-related bug reported by
230 Ilja van Sprundel. You should upgrade. (We'll send out more details
231 about the bug once people have had some time to upgrade.)
234 - Fix a heap-corruption bug that may be remotely triggerable on
235 some platforms. Reported by Ilja van Sprundel.
238 - When a stream at an exit relay is in state "resolving" or
239 "connecting" and it receives an "end" relay cell, the exit relay
240 would silently ignore the end cell and not close the stream. If
241 the client never closes the circuit, then the exit relay never
242 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
244 - When sending CREATED cells back for a given circuit, use a 64-bit
245 connection ID to find the right connection, rather than an addr:port
246 combination. Now that we can have multiple OR connections between
247 the same ORs, it is no longer possible to use addr:port to uniquely
248 identify a connection.
249 - Bridge relays that had DirPort set to 0 would stop fetching
250 descriptors shortly after startup, and then briefly resume
251 after a new bandwidth test and/or after publishing a new bridge
252 descriptor. Bridge users that try to bootstrap from them would
253 get a recent networkstatus but would get descriptors from up to
254 18 hours earlier, meaning most of the descriptors were obsolete
255 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
256 - Prevent bridge relays from serving their 'extrainfo' document
257 to anybody who asks, now that extrainfo docs include potentially
258 sensitive aggregated client geoip summaries. Bugfix on
260 - If the cached networkstatus consensus is more than five days old,
261 discard it rather than trying to use it. In theory it could be
262 useful because it lists alternate directory mirrors, but in practice
263 it just means we spend many minutes trying directory mirrors that
264 are long gone from the network. Also discard router descriptors as
265 we load them if they are more than five days old, since the onion
266 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
269 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
270 could make gcc generate non-functional binary search code. Bugfix
272 - Build correctly on platforms without socklen_t.
273 - Compile without warnings on solaris.
274 - Avoid potential crash on internal error during signature collection.
275 Fixes bug 864. Patch from rovv.
276 - Correct handling of possible malformed authority signing key
277 certificates with internal signature types. Fixes bug 880.
278 Bugfix on 0.2.0.3-alpha.
279 - Fix a hard-to-trigger resource leak when logging credential status.
281 - When we can't initialize DNS because the network is down, do not
282 automatically stop Tor from starting. Instead, we retry failed
283 dns_init() every 10 minutes, and change the exit policy to reject
284 *:* until one succeeds. Fixes bug 691.
285 - Use 64 bits instead of 32 bits for connection identifiers used with
286 the controller protocol, to greatly reduce risk of identifier reuse.
287 - When we're choosing an exit node for a circuit, and we have
288 no pending streams, choose a good general exit rather than one that
289 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
290 - Fix another case of assuming, when a specific exit is requested,
291 that we know more than the user about what hosts it allows.
292 Fixes one case of bug 752. Patch from rovv.
293 - Clip the MaxCircuitDirtiness config option to a minimum of 10
294 seconds. Warn the user if lower values are given in the
295 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
296 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
297 user if lower values are given in the configuration. Bugfix on
298 0.1.1.17-rc. Patch by Sebastian.
299 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
300 the cache because we already had a v0 descriptor with the same ID.
301 Bugfix on 0.2.0.18-alpha.
302 - Fix a race condition when freeing keys shared between main thread
303 and CPU workers that could result in a memory leak. Bugfix on
304 0.1.0.1-rc. Fixes bug 889.
305 - Send a valid END cell back when a client tries to connect to a
306 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
307 840. Patch from rovv.
308 - Check which hops rendezvous stream cells are associated with to
309 prevent possible guess-the-streamid injection attacks from
310 intermediate hops. Fixes another case of bug 446. Based on patch
312 - If a broken client asks a non-exit router to connect somewhere,
313 do not even do the DNS lookup before rejecting the connection.
314 Fixes another case of bug 619. Patch from rovv.
315 - When a relay gets a create cell it can't decrypt (e.g. because it's
316 using the wrong onion key), we were dropping it and letting the
317 client time out. Now actually answer with a destroy cell. Fixes
318 bug 904. Bugfix on 0.0.2pre8.
320 o Minor bugfixes (hidden services):
321 - Do not throw away existing introduction points on SIGHUP. Bugfix on
322 0.0.6pre1. Patch by Karsten. Fixes bug 874.
325 - Report the case where all signatures in a detached set are rejected
326 differently than the case where there is an error handling the
328 - When we realize that another process has modified our cached
329 descriptors, print out a more useful error message rather than
330 triggering an assertion. Fixes bug 885. Patch from Karsten.
331 - Implement the 0x20 hack to better resist DNS poisoning: set the
332 case on outgoing DNS requests randomly, and reject responses that do
333 not match the case correctly. This logic can be disabled with the
334 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
335 of servers that do not reliably preserve case in replies. See
336 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
338 - Check DNS replies for more matching fields to better resist DNS
340 - Never use OpenSSL compression: it wastes RAM and CPU trying to
341 compress cells, which are basically all encrypted, compressed, or
345 Changes in version 0.2.1.11-alpha - 2009-01-20
346 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
347 week it will take a long time to bootstrap again" bug. It also fixes
348 an important security-related bug reported by Ilja van Sprundel. You
349 should upgrade. (We'll send out more details about the bug once people
350 have had some time to upgrade.)
353 - Fix a heap-corruption bug that may be remotely triggerable on
354 some platforms. Reported by Ilja van Sprundel.
357 - Discard router descriptors as we load them if they are more than
358 five days old. Otherwise if Tor is off for a long time and then
359 starts with cached descriptors, it will try to use the onion
360 keys in those obsolete descriptors when building circuits. Bugfix
361 on 0.2.0.x. Fixes bug 887.
364 - Try to make sure that the version of Libevent we're running with
365 is binary-compatible with the one we built with. May address bug
367 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
368 for bug 905. Bugfix on 0.2.1.7-alpha.
369 - Add a new --enable-local-appdata configuration switch to change
370 the default location of the datadir on win32 from APPDATA to
371 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
372 entirely. Patch from coderman.
375 - Make outbound DNS packets respect the OutboundBindAddress setting.
376 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
377 - When our circuit fails at the first hop (e.g. we get a destroy
378 cell back), avoid using that OR connection anymore, and also
379 tell all the one-hop directory requests waiting for it that they
380 should fail. Bugfix on 0.2.1.3-alpha.
381 - In the torify(1) manpage, mention that tsocks will leak your
385 Changes in version 0.2.1.10-alpha - 2009-01-06
386 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
387 would make the bridge relay not so useful if it had DirPort set to 0,
388 and one that could let an attacker learn a little bit of information
389 about the bridge's users), and a bug that would cause your Tor relay
390 to ignore a circuit create request it can't decrypt (rather than reply
391 with an error). It also fixes a wide variety of other bugs.
394 - If the cached networkstatus consensus is more than five days old,
395 discard it rather than trying to use it. In theory it could
396 be useful because it lists alternate directory mirrors, but in
397 practice it just means we spend many minutes trying directory
398 mirrors that are long gone from the network. Helps bug 887 a bit;
400 - Bridge relays that had DirPort set to 0 would stop fetching
401 descriptors shortly after startup, and then briefly resume
402 after a new bandwidth test and/or after publishing a new bridge
403 descriptor. Bridge users that try to bootstrap from them would
404 get a recent networkstatus but would get descriptors from up to
405 18 hours earlier, meaning most of the descriptors were obsolete
406 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
407 - Prevent bridge relays from serving their 'extrainfo' document
408 to anybody who asks, now that extrainfo docs include potentially
409 sensitive aggregated client geoip summaries. Bugfix on
413 - New controller event "clients_seen" to report a geoip-based summary
414 of which countries we've seen clients from recently. Now controllers
415 like Vidalia can show bridge operators that they're actually making
417 - Build correctly against versions of OpenSSL 0.9.8 or later built
418 without support for deprecated functions.
419 - Update to the "December 19 2008" ip-to-country file.
421 o Minor bugfixes (on 0.2.0.x):
422 - Authorities now vote for the Stable flag for any router whose
423 weighted MTBF is at least 5 days, regardless of the mean MTBF.
424 - Do not remove routers as too old if we do not have any consensus
425 document. Bugfix on 0.2.0.7-alpha.
426 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
427 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
428 - When an exit relay resolves a stream address to a local IP address,
429 do not just keep retrying that same exit relay over and
430 over. Instead, just close the stream. Addresses bug 872. Bugfix
431 on 0.2.0.32. Patch from rovv.
432 - If a hidden service sends us an END cell, do not consider
433 retrying the connection; just close it. Patch from rovv.
434 - When we made bridge authorities stop serving bridge descriptors over
435 unencrypted links, we also broke DirPort reachability testing for
436 bridges. So bridges with a non-zero DirPort were printing spurious
437 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
438 - When a relay gets a create cell it can't decrypt (e.g. because it's
439 using the wrong onion key), we were dropping it and letting the
440 client time out. Now actually answer with a destroy cell. Fixes
441 bug 904. Bugfix on 0.0.2pre8.
442 - Squeeze 2-5% out of client performance (according to oprofile) by
443 improving the implementation of some policy-manipulation functions.
445 o Minor bugfixes (on 0.2.1.x):
446 - Make get_interface_address() function work properly again; stop
447 guessing the wrong parts of our address as our address.
448 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
449 send on that circuit. Otherwise we might violate the proposal-110
450 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
452 - When we're sending non-EXTEND cells to the first hop in a circuit,
453 for example to use an encrypted directory connection, we don't need
454 to use RELAY_EARLY cells: the first hop knows what kind of cell
455 it is, and nobody else can even see the cell type. Conserving
456 RELAY_EARLY cells makes it easier to cannibalize circuits like
458 - Stop logging nameserver addresses in reverse order.
459 - If we are retrying a directory download slowly over and over, do
460 not automatically give up after the 254th failure. Bugfix on
462 - Resume reporting accurate "stream end" reasons to the local control
463 port. They were lost in the changes for Proposal 148. Bugfix on
466 o Deprecated and removed features:
467 - The old "tor --version --version" command, which would print out
468 the subversion "Id" of most of the source files, is now removed. It
469 turned out to be less useful than we'd expected, and harder to
472 o Code simplifications and refactoring:
473 - Change our header file guard macros to be less likely to conflict
474 with system headers. Adam Langley noticed that we were conflicting
475 with log.h on Android.
476 - Tool-assisted documentation cleanup. Nearly every function or
477 static variable in Tor should have its own documentation now.
480 Changes in version 0.2.1.9-alpha - 2008-12-25
481 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
483 o New directory authorities:
484 - gabelmoo (the authority run by Karsten Loesing) now has a new
488 - Never use a connection with a mismatched address to extend a
489 circuit, unless that connection is canonical. A canonical
490 connection is one whose address is authenticated by the router's
491 identity key, either in a NETINFO cell or in a router descriptor.
492 - Avoid a possible memory corruption bug when receiving hidden service
493 descriptors. Bugfix on 0.2.1.6-alpha.
496 - Fix a logic error that would automatically reject all but the first
497 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
498 part of bug 813/868. Bug spotted by coderman.
499 - When a stream at an exit relay is in state "resolving" or
500 "connecting" and it receives an "end" relay cell, the exit relay
501 would silently ignore the end cell and not close the stream. If
502 the client never closes the circuit, then the exit relay never
503 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
505 - When we can't initialize DNS because the network is down, do not
506 automatically stop Tor from starting. Instead, retry failed
507 dns_init() every 10 minutes, and change the exit policy to reject
508 *:* until one succeeds. Fixes bug 691.
511 - Give a better error message when an overzealous init script says
512 "sudo -u username tor --user username". Makes Bug 882 easier for
514 - When a directory authority gives us a new guess for our IP address,
515 log which authority we used. Hopefully this will help us debug
516 the recent complaints about bad IP address guesses.
517 - Detect svn revision properly when we're using git-svn.
518 - Try not to open more than one descriptor-downloading connection
519 to an authority at once. This should reduce load on directory
520 authorities. Fixes bug 366.
521 - Add cross-certification to newly generated certificates, so that
522 a signing key is enough information to look up a certificate.
523 Partial implementation of proposal 157.
524 - Start serving certificates by <identity digest, signing key digest>
525 pairs. Partial implementation of proposal 157.
526 - Clients now never report any stream end reason except 'MISC'.
527 Implements proposal 148.
528 - On platforms with a maximum syslog string length, truncate syslog
529 messages to that length ourselves, rather than relying on the
530 system to do it for us.
531 - Optimize out calls to time(NULL) that occur for every IO operation,
532 or for every cell. On systems where time() is a slow syscall,
533 this fix will be slightly helpful.
534 - Exit servers can now answer resolve requests for ip6.arpa addresses.
535 - When we download a descriptor that we then immediately (as
536 a directory authority) reject, do not retry downloading it right
537 away. Should save some bandwidth on authorities. Fix for bug
538 888. Patch by Sebastian Hahn.
539 - When a download gets us zero good descriptors, do not notify
540 Tor that new directory information has arrived.
541 - Avoid some nasty corner cases in the logic for marking connections
542 as too old or obsolete or noncanonical for circuits. Partial
545 o Minor features (controller):
546 - New CONSENSUS_ARRIVED event to note when a new consensus has
547 been fetched and validated.
548 - When we realize that another process has modified our cached
549 descriptors file, print out a more useful error message rather
550 than triggering an assertion. Fixes bug 885. Patch from Karsten.
551 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
552 controllers to prevent SIGHUP from reloading the
553 configuration. Fixes bug 856.
556 - Resume using the correct "REASON=" stream when telling the
557 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
558 - When a canonical connection appears later in our internal list
559 than a noncanonical one for a given OR ID, always use the
560 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
562 - Clip the MaxCircuitDirtiness config option to a minimum of 10
563 seconds. Warn the user if lower values are given in the
564 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
565 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
566 user if lower values are given in the configuration. Bugfix on
567 0.1.1.17-rc. Patch by Sebastian.
568 - Fix a race condition when freeing keys shared between main thread
569 and CPU workers that could result in a memory leak. Bugfix on
570 0.1.0.1-rc. Fixes bug 889.
572 o Minor bugfixes (hidden services):
573 - Do not throw away existing introduction points on SIGHUP (bugfix on
574 0.0.6pre1); also, do not stall hidden services because we're
575 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
576 by John Brooks. Patch by Karsten. Fixes bug 874.
577 - Fix a memory leak when we decline to add a v2 rendezvous
578 descriptor to the cache because we already had a v0 descriptor
579 with the same ID. Bugfix on 0.2.0.18-alpha.
581 o Deprecated and removed features:
582 - RedirectExits has been removed. It was deprecated since
584 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
585 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
586 - Cell pools are now always enabled; --disable-cell-pools is ignored.
588 o Code simplifications and refactoring:
589 - Rename the confusing or_is_obsolete field to the more appropriate
590 is_bad_for_new_circs, and move it to or_connection_t where it
592 - Move edge-only flags from connection_t to edge_connection_t: not
593 only is this better coding, but on machines of plausible alignment,
594 it should save 4-8 bytes per connection_t. "Every little bit helps."
595 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
596 for consistency; keep old option working for backward compatibility.
597 - Simplify the code for finding connections to use for a circuit.
600 Changes in version 0.2.1.8-alpha - 2008-12-08
601 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
602 builds better on unusual platforms like Solaris and old OS X, and
603 fixes a variety of other issues.
606 - New DirPortFrontPage option that takes an html file and publishes
607 it as "/" on the DirPort. Now relay operators can provide a
608 disclaimer without needing to set up a separate webserver. There's
609 a sample disclaimer in contrib/tor-exit-notice.html.
612 - When the client is choosing entry guards, now it selects at most
613 one guard from a given relay family. Otherwise we could end up with
614 all of our entry points into the network run by the same operator.
615 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
618 - Fix a DOS opportunity during the voting signature collection process
619 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
620 - Fix a possible segfault when establishing an exit connection. Bugfix
624 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
626 - Made Tor a little less aggressive about deleting expired
627 certificates. Partial fix for bug 854.
628 - Stop doing unaligned memory access that generated bus errors on
629 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
630 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
631 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
632 - Make USR2 log-level switch take effect immediately. Bugfix on
634 - If one win32 nameserver fails to get added, continue adding the
635 rest, and don't automatically fail.
636 - Use fcntl() for locking when flock() is not available. Should fix
637 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
638 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
639 could make gcc generate non-functional binary search code. Bugfix
641 - Build correctly on platforms without socklen_t.
642 - Avoid potential crash on internal error during signature collection.
643 Fixes bug 864. Patch from rovv.
644 - Do not use C's stdio library for writing to log files. This will
645 improve logging performance by a minute amount, and will stop
646 leaking fds when our disk is full. Fixes bug 861.
647 - Stop erroneous use of O_APPEND in cases where we did not in fact
648 want to re-seek to the end of a file before every last write().
649 - Correct handling of possible malformed authority signing key
650 certificates with internal signature types. Fixes bug 880. Bugfix
652 - Fix a hard-to-trigger resource leak when logging credential status.
656 - Directory mirrors no longer fetch the v1 directory or
657 running-routers files. They are obsolete, and nobody asks for them
658 anymore. This is the first step to making v1 authorities obsolete.
660 o Minor features (controller):
661 - Return circuit purposes in response to GETINFO circuit-status. Fixes
665 Changes in version 0.2.0.32 - 2008-11-20
666 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
667 packages (and maybe other packages) noticed by Theo de Raadt, fixes
668 a smaller security flaw that might allow an attacker to access local
669 services, further improves hidden service performance, and fixes a
670 variety of other issues.
673 - The "User" and "Group" config options did not clear the
674 supplementary group entries for the Tor process. The "User" option
675 is now more robust, and we now set the groups to the specified
676 user's primary group. The "Group" option is now ignored. For more
677 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
678 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
679 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
680 - The "ClientDNSRejectInternalAddresses" config option wasn't being
681 consistently obeyed: if an exit relay refuses a stream because its
682 exit policy doesn't allow it, we would remember what IP address
683 the relay said the destination address resolves to, even if it's
684 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
687 - Fix a DOS opportunity during the voting signature collection process
688 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
690 o Major bugfixes (hidden services):
691 - When fetching v0 and v2 rendezvous service descriptors in parallel,
692 we were failing the whole hidden service request when the v0
693 descriptor fetch fails, even if the v2 fetch is still pending and
694 might succeed. Similarly, if the last v2 fetch fails, we were
695 failing the whole hidden service request even if a v0 fetch is
696 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
697 - When extending a circuit to a hidden service directory to upload a
698 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
699 requests failed, because the router descriptor has not been
700 downloaded yet. In these cases, do not attempt to upload the
701 rendezvous descriptor, but wait until the router descriptor is
702 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
703 descriptor from a hidden service directory for which the router
704 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
708 - Fix several infrequent memory leaks spotted by Coverity.
709 - When testing for libevent functions, set the LDFLAGS variable
710 correctly. Found by Riastradh.
711 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
712 bootstrapping with tunneled directory connections. Bugfix on
713 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
714 - When asked to connect to A.B.exit:80, if we don't know the IP for A
715 and we know that server B rejects most-but-not all connections to
716 port 80, we would previously reject the connection. Now, we assume
717 the user knows what they were asking for. Fixes bug 752. Bugfix
718 on 0.0.9rc5. Diagnosed by BarkerJr.
719 - If we overrun our per-second write limits a little, count this as
720 having used up our write allocation for the second, and choke
721 outgoing directory writes. Previously, we had only counted this when
722 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
723 Bugfix on 0.2.0.x (??).
724 - Remove the old v2 directory authority 'lefkada' from the default
725 list. It has been gone for many months.
726 - Stop doing unaligned memory access that generated bus errors on
727 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
728 - Make USR2 log-level switch take effect immediately. Bugfix on
731 o Minor bugfixes (controller):
732 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
733 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
736 Changes in version 0.2.1.7-alpha - 2008-11-08
737 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
738 packages (and maybe other packages) noticed by Theo de Raadt, fixes
739 a smaller security flaw that might allow an attacker to access local
740 services, adds better defense against DNS poisoning attacks on exit
741 relays, further improves hidden service performance, and fixes a
742 variety of other issues.
745 - The "ClientDNSRejectInternalAddresses" config option wasn't being
746 consistently obeyed: if an exit relay refuses a stream because its
747 exit policy doesn't allow it, we would remember what IP address
748 the relay said the destination address resolves to, even if it's
749 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
750 - The "User" and "Group" config options did not clear the
751 supplementary group entries for the Tor process. The "User" option
752 is now more robust, and we now set the groups to the specified
753 user's primary group. The "Group" option is now ignored. For more
754 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
755 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
756 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
757 - Do not use or believe expired v3 authority certificates. Patch
758 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
761 - Now NodeFamily and MyFamily config options allow spaces in
762 identity fingerprints, so it's easier to paste them in.
763 Suggested by Lucky Green.
764 - Implement the 0x20 hack to better resist DNS poisoning: set the
765 case on outgoing DNS requests randomly, and reject responses that do
766 not match the case correctly. This logic can be disabled with the
767 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
768 of servers that do not reliably preserve case in replies. See
769 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
771 - Preserve case in replies to DNSPort requests in order to support
772 the 0x20 hack for resisting DNS poisoning attacks.
774 o Hidden service performance improvements:
775 - When the client launches an introduction circuit, retry with a
776 new circuit after 30 seconds rather than 60 seconds.
777 - Launch a second client-side introduction circuit in parallel
778 after a delay of 15 seconds (based on work by Christian Wilms).
779 - Hidden services start out building five intro circuits rather
780 than three, and when the first three finish they publish a service
781 descriptor using those. Now we publish our service descriptor much
782 faster after restart.
785 - Minor fix in the warning messages when you're having problems
786 bootstrapping; also, be more forgiving of bootstrap problems when
787 we're still making incremental progress on a given bootstrap phase.
788 - When we're choosing an exit node for a circuit, and we have
789 no pending streams, choose a good general exit rather than one that
790 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
791 - Send a valid END cell back when a client tries to connect to a
792 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
793 840. Patch from rovv.
794 - If a broken client asks a non-exit router to connect somewhere,
795 do not even do the DNS lookup before rejecting the connection.
796 Fixes another case of bug 619. Patch from rovv.
797 - Fix another case of assuming, when a specific exit is requested,
798 that we know more than the user about what hosts it allows.
799 Fixes another case of bug 752. Patch from rovv.
800 - Check which hops rendezvous stream cells are associated with to
801 prevent possible guess-the-streamid injection attacks from
802 intermediate hops. Fixes another case of bug 446. Based on patch
804 - Avoid using a negative right-shift when comparing 32-bit
805 addresses. Possible fix for bug 845 and bug 811.
806 - Make the assert_circuit_ok() function work correctly on circuits that
807 have already been marked for close.
808 - Fix read-off-the-end-of-string error in unit tests when decoding
810 - Fix uninitialized size field for memory area allocation: may improve
811 memory performance during directory parsing.
812 - Treat duplicate certificate fetches as failures, so that we do
813 not try to re-fetch an expired certificate over and over and over.
814 - Do not say we're fetching a certificate when we'll in fact skip it
815 because of a pending download.
818 Changes in version 0.2.1.6-alpha - 2008-09-30
819 Tor 0.2.1.6-alpha further improves performance and robustness of
820 hidden services, starts work on supporting per-country relay selection,
821 and fixes a variety of smaller issues.
824 - Implement proposal 121: make it possible to build hidden services
825 that only certain clients are allowed to connect to. This is
826 enforced at several points, so that unauthorized clients are unable
827 to send INTRODUCE cells to the service, or even (depending on the
828 type of authentication) to learn introduction points. This feature
829 raises the bar for certain kinds of active attacks against hidden
830 services. Code by Karsten Loesing.
831 - Relays now store and serve v2 hidden service descriptors by default,
832 i.e., the new default value for HidServDirectoryV2 is 1. This is
833 the last step in proposal 114, which aims to make hidden service
834 lookups more reliable.
835 - Start work to allow node restrictions to include country codes. The
836 syntax to exclude nodes in a country with country code XX is
837 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
838 refinement to decide what config options should take priority if
839 you ask to both use a particular node and exclude it.
840 - Allow ExitNodes list to include IP ranges and country codes, just
841 like the Exclude*Nodes lists. Patch from Robert Hogan.
844 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
845 Tor to fail to start if you had it configured to use a bridge
846 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
847 - When extending a circuit to a hidden service directory to upload a
848 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
849 requests failed, because the router descriptor had not been
850 downloaded yet. In these cases, we now wait until the router
851 descriptor is downloaded, and then retry. Likewise, clients
852 now skip over a hidden service directory if they don't yet have
853 its router descriptor, rather than futilely requesting it and
854 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
856 - When fetching v0 and v2 rendezvous service descriptors in parallel,
857 we were failing the whole hidden service request when the v0
858 descriptor fetch fails, even if the v2 fetch is still pending and
859 might succeed. Similarly, if the last v2 fetch fails, we were
860 failing the whole hidden service request even if a v0 fetch is
861 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
862 - DNS replies need to have names matching their requests, but
863 these names should be in the questions section, not necessarily
864 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
867 - Update to the "September 1 2008" ip-to-country file.
868 - Allow ports 465 and 587 in the default exit policy again. We had
869 rejected them in 0.1.0.15, because back in 2005 they were commonly
870 misconfigured and ended up as spam targets. We hear they are better
871 locked down these days.
872 - Use a lockfile to make sure that two Tor processes are not
873 simultaneously running with the same datadir.
874 - Serve the latest v3 networkstatus consensus via the control
875 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
876 - Better logging about stability/reliability calculations on directory
878 - Drop the requirement to have an open dir port for storing and
879 serving v2 hidden service descriptors.
880 - Directory authorities now serve a /tor/dbg-stability.txt URL to
881 help debug WFU and MTBF calculations.
882 - Implement most of Proposal 152: allow specialized servers to permit
883 single-hop circuits, and clients to use those servers to build
884 single-hop circuits when using a specialized controller. Patch
885 from Josh Albrecht. Resolves feature request 768.
886 - Add a -p option to tor-resolve for specifying the SOCKS port: some
887 people find host:port too confusing.
888 - Make TrackHostExit mappings expire a while after their last use, not
889 after their creation. Patch from Robert Hogan.
890 - Provide circuit purposes along with circuit events to the controller.
893 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
895 - Fixed some memory leaks -- some quite frequent, some almost
896 impossible to trigger -- based on results from Coverity.
897 - When testing for libevent functions, set the LDFLAGS variable
898 correctly. Found by Riastradh.
899 - Fix an assertion bug in parsing policy-related options; possible fix
901 - Catch and report a few more bootstrapping failure cases when Tor
902 fails to establish a TCP connection. Cleanup on 0.2.1.x.
903 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
904 bootstrapping with tunneled directory connections. Bugfix on
905 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
906 - When asked to connect to A.B.exit:80, if we don't know the IP for A
907 and we know that server B rejects most-but-not all connections to
908 port 80, we would previously reject the connection. Now, we assume
909 the user knows what they were asking for. Fixes bug 752. Bugfix
910 on 0.0.9rc5. Diagnosed by BarkerJr.
911 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
912 service directories if they have no advertised dir port. Bugfix
914 - If we overrun our per-second write limits a little, count this as
915 having used up our write allocation for the second, and choke
916 outgoing directory writes. Previously, we had only counted this when
917 we had met our limits precisely. Fixes bug 824. Patch by rovv.
918 Bugfix on 0.2.0.x (??).
919 - Avoid a "0 divided by 0" calculation when calculating router uptime
920 at directory authorities. Bugfix on 0.2.0.8-alpha.
921 - Make DNS resolved controller events into "CLOSED", not
922 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
924 - Fix a bug where an unreachable relay would establish enough
925 reachability testing circuits to do a bandwidth test -- if
926 we already have a connection to the middle hop of the testing
927 circuit, then it could establish the last hop by using the existing
928 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
929 circuits no longer use entry guards in 0.2.1.3-alpha.
930 - If we have correct permissions on $datadir, we complain to stdout
931 and fail to start. But dangerous permissions on
932 $datadir/cached-status/ would cause us to open a log and complain
933 there. Now complain to stdout and fail to start in both cases. Fixes
934 bug 820, reported by seeess.
935 - Remove the old v2 directory authority 'lefkada' from the default
936 list. It has been gone for many months.
938 o Code simplifications and refactoring:
939 - Revise the connection_new functions so that a more typesafe variant
940 exists. This will work better with Coverity, and let us find any
941 actual mistakes we're making here.
942 - Refactor unit testing logic so that dmalloc can be used sensibly
943 with unit tests to check for memory leaks.
944 - Move all hidden-service related fields from connection and circuit
945 structure to substructures: this way they won't eat so much memory.
948 Changes in version 0.2.0.31 - 2008-09-03
949 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
950 a big bug we're seeing where in rare cases traffic from one Tor stream
951 gets mixed into another stream, and fixes a variety of smaller issues.
954 - Make sure that two circuits can never exist on the same connection
955 with the same circuit ID, even if one is marked for close. This
956 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
957 - Relays now reject risky extend cells: if the extend cell includes
958 a digest of all zeroes, or asks to extend back to the relay that
959 sent the extend cell, tear down the circuit. Ideas suggested
961 - If not enough of our entry guards are available so we add a new
962 one, we might use the new one even if it overlapped with the
963 current circuit's exit relay (or its family). Anonymity bugfix
967 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
968 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
969 - Correctly detect the presence of the linux/netfilter_ipv4.h header
970 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
971 - Pick size of default geoip filename string correctly on windows.
972 Fixes bug 806. Bugfix on 0.2.0.30.
973 - Make the autoconf script accept the obsolete --with-ssl-dir
974 option as an alias for the actually-working --with-openssl-dir
975 option. Fix the help documentation to recommend --with-openssl-dir.
976 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
977 - When using the TransPort option on OpenBSD, and using the User
978 option to change UID and drop privileges, make sure to open
979 /dev/pf before dropping privileges. Fixes bug 782. Patch from
980 Christopher Davis. Bugfix on 0.1.2.1-alpha.
981 - Try to attach connections immediately upon receiving a RENDEZVOUS2
982 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
983 on the client side when connecting to a hidden service. Bugfix
984 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
985 - When closing an application-side connection because its circuit is
986 getting torn down, generate the stream event correctly. Bugfix on
987 0.1.2.x. Anonymous patch.
990 Changes in version 0.2.1.5-alpha - 2008-08-31
991 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
992 in a lot of the infrastructure for adding authorization to hidden
993 services, lays the groundwork for having clients read their load
994 balancing information out of the networkstatus consensus rather than
995 the individual router descriptors, addresses two potential anonymity
996 issues, and fixes a variety of smaller issues.
999 - Convert many internal address representations to optionally hold
1001 - Generate and accept IPv6 addresses in many protocol elements.
1002 - Make resolver code handle nameservers located at ipv6 addresses.
1003 - Begin implementation of proposal 121 ("Client authorization for
1004 hidden services"): configure hidden services with client
1005 authorization, publish descriptors for them, and configure
1006 authorization data for hidden services at clients. The next
1007 step is to actually access hidden services that perform client
1009 - More progress toward proposal 141: Network status consensus
1010 documents and votes now contain bandwidth information for each
1011 router and a summary of that router's exit policy. Eventually this
1012 will be used by clients so that they do not have to download every
1013 known descriptor before building circuits.
1015 o Major bugfixes (on 0.2.0.x and before):
1016 - When sending CREATED cells back for a given circuit, use a 64-bit
1017 connection ID to find the right connection, rather than an addr:port
1018 combination. Now that we can have multiple OR connections between
1019 the same ORs, it is no longer possible to use addr:port to uniquely
1020 identify a connection.
1021 - Relays now reject risky extend cells: if the extend cell includes
1022 a digest of all zeroes, or asks to extend back to the relay that
1023 sent the extend cell, tear down the circuit. Ideas suggested
1025 - If not enough of our entry guards are available so we add a new
1026 one, we might use the new one even if it overlapped with the
1027 current circuit's exit relay (or its family). Anonymity bugfix
1028 pointed out by rovv.
1031 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
1032 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
1033 - When using the TransPort option on OpenBSD, and using the User
1034 option to change UID and drop privileges, make sure to open /dev/pf
1035 before dropping privileges. Fixes bug 782. Patch from Christopher
1036 Davis. Bugfix on 0.1.2.1-alpha.
1037 - Correctly detect the presence of the linux/netfilter_ipv4.h header
1038 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
1039 - Add a missing safe_str() call for a debug log message.
1040 - Use 64 bits instead of 32 bits for connection identifiers used with
1041 the controller protocol, to greatly reduce risk of identifier reuse.
1042 - Make the autoconf script accept the obsolete --with-ssl-dir
1043 option as an alias for the actually-working --with-openssl-dir
1044 option. Fix the help documentation to recommend --with-openssl-dir.
1045 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
1048 - Rate-limit too-many-sockets messages: when they happen, they happen
1049 a lot. Resolves bug 748.
1050 - Resist DNS poisoning a little better by making sure that names in
1051 answer sections match.
1052 - Print the SOCKS5 error message string as well as the error code
1053 when a tor-resolve request fails. Patch from Jacob.
1056 Changes in version 0.2.1.4-alpha - 2008-08-04
1057 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
1060 - The address part of exit policies was not correctly written
1061 to router descriptors. This generated router descriptors that failed
1062 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
1064 - Tor triggered a false assert when extending a circuit to a relay
1065 but we already have a connection open to that relay. Noticed by
1066 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
1069 - Fix a hidden service logging bug: in some edge cases, the router
1070 descriptor of a previously picked introduction point becomes
1071 obsolete and we need to give up on it rather than continually
1072 complaining that it has become obsolete. Observed by xiando. Bugfix
1076 - Take out the TestVia config option, since it was a workaround for
1077 a bug that was fixed in Tor 0.1.1.21.
1080 Changes in version 0.2.1.3-alpha - 2008-08-03
1081 Tor 0.2.1.3-alpha implements most of the pieces to prevent
1082 infinite-length circuit attacks (see proposal 110); fixes a bug that
1083 might cause exit relays to corrupt streams they send back; allows
1084 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
1085 ExcludeExitNodes config options; and fixes a big pile of bugs.
1087 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
1088 - Send a bootstrap problem "warn" event on the first problem if the
1089 reason is NO_ROUTE (that is, our network is down).
1092 - Implement most of proposal 110: The first K cells to be sent
1093 along a circuit are marked as special "early" cells; only K "early"
1094 cells will be allowed. Once this code is universal, we can block
1095 certain kinds of DOS attack by requiring that EXTEND commands must
1096 be sent using an "early" cell.
1099 - Try to attach connections immediately upon receiving a RENDEZVOUS2
1100 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
1101 on the client side when connecting to a hidden service. Bugfix
1102 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
1103 - Ensure that two circuits can never exist on the same connection
1104 with the same circuit ID, even if one is marked for close. This
1105 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
1108 - When relays do their initial bandwidth measurement, don't limit
1109 to just our entry guards for the test circuits. Otherwise we tend
1110 to have multiple test circuits going through a single entry guard,
1111 which makes our bandwidth test less accurate. Fixes part of bug 654;
1112 patch contributed by Josh Albrecht.
1113 - Add an ExcludeExitNodes option so users can list a set of nodes
1114 that should be be excluded from the exit node position, but
1115 allowed elsewhere. Implements proposal 151.
1116 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
1117 ExcludeNodes and ExcludeExitNodes lists.
1118 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
1119 be more efficient. Formerly it was quadratic in the number of
1120 servers; now it should be linear. Fixes bug 509.
1121 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
1122 and n_conn_id_digest fields into a separate structure that's
1123 only needed when the circuit has not yet attached to an n_conn.
1126 - Change the contrib/tor.logrotate script so it makes the new
1127 logs as "_tor:_tor" rather than the default, which is generally
1128 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
1129 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
1130 warnings (occasionally), but it can also cause the compiler to
1131 eliminate error-checking code. Suggested by Peter Gutmann.
1132 - When a hidden service is giving up on an introduction point candidate
1133 that was not included in the last published rendezvous descriptor,
1134 don't reschedule publication of the next descriptor. Fixes bug 763.
1136 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
1137 HiddenServiceExcludeNodes as obsolete: they never worked properly,
1138 and nobody claims to be using them. Fixes bug 754. Bugfix on
1139 0.1.0.1-rc. Patch from Christian Wilms.
1140 - Fix a small alignment and memory-wasting bug on buffer chunks.
1143 o Minor bugfixes (controller):
1144 - When closing an application-side connection because its circuit
1145 is getting torn down, generate the stream event correctly.
1146 Bugfix on 0.1.2.x. Anonymous patch.
1149 - Remove all backward-compatibility code to support relays running
1150 versions of Tor so old that they no longer work at all on the
1154 Changes in version 0.2.0.30 - 2008-07-15
1156 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
1157 warnings (occasionally), but it can also cause the compiler to
1158 eliminate error-checking code. Suggested by Peter Gutmann.
1161 Changes in version 0.2.0.29-rc - 2008-07-08
1162 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
1163 hidden-service performance bugs, and fixes a bunch of smaller bugs.
1166 - If you have more than one bridge but don't know their keys,
1167 you would only launch a request for the descriptor of the first one
1168 on your list. (Tor considered launching requests for the others, but
1169 found that it already had a connection on the way for $0000...0000
1170 so it didn't open another.) Bugfix on 0.2.0.x.
1171 - If you have more than one bridge but don't know their keys, and the
1172 connection to one of the bridges failed, you would cancel all
1173 pending bridge connections. (After all, they all have the same
1174 digest.) Bugfix on 0.2.0.x.
1175 - When a hidden service was trying to establish an introduction point,
1176 and Tor had built circuits preemptively for such purposes, we
1177 were ignoring all the preemptive circuits and launching a new one
1178 instead. Bugfix on 0.2.0.14-alpha.
1179 - When a hidden service was trying to establish an introduction point,
1180 and Tor *did* manage to reuse one of the preemptively built
1181 circuits, it didn't correctly remember which one it used,
1182 so it asked for another one soon after, until there were no
1183 more preemptive circuits, at which point it launched one from
1184 scratch. Bugfix on 0.0.9.x.
1185 - Make directory servers include the X-Your-Address-Is: http header in
1186 their responses even for begin_dir conns. Now clients who only
1187 ever use begin_dir connections still have a way to learn their IP
1188 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
1191 - Fix a macro/CPP interaction that was confusing some compilers:
1192 some GCCs don't like #if/#endif pairs inside macro arguments.
1194 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
1195 Fixes bug 704; fix from Steven Murdoch.
1196 - When opening /dev/null in finish_daemonize(), do not pass the
1197 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
1198 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
1199 - Correctly detect transparent proxy support on Linux hosts that
1200 require in.h to be included before netfilter_ipv4.h. Patch
1202 - Disallow session resumption attempts during the renegotiation
1203 stage of the v2 handshake protocol. Clients should never be trying
1204 session resumption at this point, but apparently some did, in
1205 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
1206 found by Geoff Goodell.
1209 Changes in version 0.2.1.2-alpha - 2008-06-20
1210 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
1211 make it easier to set up your own private Tor network; fixes several
1212 big bugs with using more than one bridge relay; fixes a big bug with
1213 offering hidden services quickly after Tor starts; and uses a better
1214 API for reporting potential bootstrapping problems to the controller.
1217 - New TestingTorNetwork config option to allow adjustment of
1218 previously constant values that, while reasonable, could slow
1219 bootstrapping. Implements proposal 135. Patch from Karsten.
1222 - If you have more than one bridge but don't know their digests,
1223 you would only learn a request for the descriptor of the first one
1224 on your list. (Tor considered launching requests for the others, but
1225 found that it already had a connection on the way for $0000...0000
1226 so it didn't open another.) Bugfix on 0.2.0.x.
1227 - If you have more than one bridge but don't know their digests,
1228 and the connection to one of the bridges failed, you would cancel
1229 all pending bridge connections. (After all, they all have the
1230 same digest.) Bugfix on 0.2.0.x.
1231 - When establishing a hidden service, introduction points that
1232 originate from cannibalized circuits are completely ignored and not
1233 included in rendezvous service descriptors. This might be another
1234 reason for delay in making a hidden service available. Bugfix
1235 from long ago (0.0.9.x?)
1238 - Allow OpenSSL to use dynamic locks if it wants.
1239 - When building a consensus, do not include routers that are down.
1240 This will cut down 30% to 40% on consensus size. Implements
1242 - In directory authorities' approved-routers files, allow
1243 fingerprints with or without space.
1244 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
1245 controller can query our current bootstrap state in case it attaches
1246 partway through and wants to catch up.
1247 - Send an initial "Starting" bootstrap status event, so we have a
1248 state to start out in.
1251 - Asking for a conditional consensus at .../consensus/<fingerprints>
1252 would crash a dirserver if it did not already have a
1253 consensus. Bugfix on 0.2.1.1-alpha.
1254 - Clean up some macro/CPP interactions: some GCC versions don't like
1255 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
1258 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
1259 - Directory authorities shouldn't complain about bootstrapping
1260 problems just because they do a lot of reachability testing and
1261 some of the connection attempts fail.
1262 - Start sending "count" and "recommendation" key/value pairs in
1263 bootstrap problem status events, so the controller can hear about
1264 problems even before Tor decides they're worth reporting for sure.
1265 - If you're using bridges, generate "bootstrap problem" warnings
1266 as soon as you run out of working bridges, rather than waiting
1267 for ten failures -- which will never happen if you have less than
1269 - If we close our OR connection because there's been a circuit
1270 pending on it for too long, we were telling our bootstrap status
1271 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
1274 Changes in version 0.2.1.1-alpha - 2008-06-13
1275 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
1276 were making the Tor process bloat especially on Linux; makes our TLS
1277 handshake blend in better; sends "bootstrap phase" status events to
1278 the controller, so it can keep the user informed of progress (and
1279 problems) fetching directory information and establishing circuits;
1280 and adds a variety of smaller features.
1283 - More work on making our TLS handshake blend in: modify the list
1284 of ciphers advertised by OpenSSL in client mode to even more
1285 closely resemble a common web browser. We cheat a little so that
1286 we can advertise ciphers that the locally installed OpenSSL doesn't
1288 - Start sending "bootstrap phase" status events to the controller,
1289 so it can keep the user informed of progress fetching directory
1290 information and establishing circuits. Also inform the controller
1291 if we think we're stuck at a particular bootstrap phase. Implements
1293 - Resume using OpenSSL's RAND_poll() for better (and more portable)
1294 cross-platform entropy collection again. We used to use it, then
1295 stopped using it because of a bug that could crash systems that
1296 called RAND_poll when they had a lot of fds open. It looks like the
1297 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
1298 at startup, and to call RAND_poll() when we reseed later only if
1299 we have a non-buggy OpenSSL version.
1302 - When we choose to abandon a new entry guard because we think our
1303 older ones might be better, close any circuits pending on that
1304 new entry guard connection. This fix should make us recover much
1305 faster when our network is down and then comes back. Bugfix on
1306 0.1.2.8-beta; found by lodger.
1308 o Memory fixes and improvements:
1309 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
1310 to avoid unused RAM in buffer chunks and memory pools.
1311 - Speed up parsing and cut down on memory fragmentation by using
1312 stack-style allocations for parsing directory objects. Previously,
1313 this accounted for over 40% of allocations from within Tor's code
1314 on a typical directory cache.
1315 - Use a Bloom filter rather than a digest-based set to track which
1316 descriptors we need to keep around when we're cleaning out old
1317 router descriptors. This speeds up the computation significantly,
1318 and may reduce fragmentation.
1319 - Reduce the default smartlist size from 32 to 16; it turns out that
1320 most smartlists hold around 8-12 elements tops.
1321 - Make dumpstats() log the fullness and size of openssl-internal
1323 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
1324 patch to their OpenSSL, turn it on to save memory on servers. This
1325 patch will (with any luck) get included in a mainline distribution
1327 - Never use OpenSSL compression: it wastes RAM and CPU trying to
1328 compress cells, which are basically all encrypted, compressed,
1332 - Stop reloading the router list from disk for no reason when we
1333 run out of reachable directory mirrors. Once upon a time reloading
1334 it would set the 'is_running' flag back to 1 for them. It hasn't
1335 done that for a long time.
1336 - In very rare situations new hidden service descriptors were
1337 published earlier than 30 seconds after the last change to the
1338 service. (We currently think that a hidden service descriptor
1339 that's been stable for 30 seconds is worth publishing.)
1342 - Allow separate log levels to be configured for different logging
1343 domains. For example, this allows one to log all notices, warnings,
1344 or errors, plus all memory management messages of level debug or
1345 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
1346 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
1347 and stop using a warning that had become unfixably verbose under
1349 - New --hush command-line option similar to --quiet. While --quiet
1350 disables all logging to the console on startup, --hush limits the
1351 output to messages of warning and error severity.
1352 - Servers support a new URL scheme for consensus downloads that
1353 allows the client to specify which authorities are trusted.
1354 The server then only sends the consensus if the client will trust
1355 it. Otherwise a 404 error is sent back. Clients use this
1356 new scheme when the server supports it (meaning it's running
1357 0.2.1.1-alpha or later). Implements proposal 134.
1358 - New configure/torrc options (--enable-geoip-stats,
1359 DirRecordUsageByCountry) to record how many IPs we've served
1360 directory info to in each country code, how many status documents
1361 total we've sent to each country code, and what share of the total
1362 directory requests we should expect to see.
1363 - Use the TLS1 hostname extension to more closely resemble browser
1365 - Lots of new unit tests.
1366 - Add a macro to implement the common pattern of iterating through
1367 two parallel lists in lockstep.
1370 Changes in version 0.2.0.28-rc - 2008-06-13
1371 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
1372 performance bug, and fixes a bunch of smaller bugs.
1375 - Fix a bug where, when we were choosing the 'end stream reason' to
1376 put in our relay end cell that we send to the exit relay, Tor
1377 clients on Windows were sometimes sending the wrong 'reason'. The
1378 anonymity problem is that exit relays may be able to guess whether
1379 the client is running Windows, thus helping partition the anonymity
1380 set. Down the road we should stop sending reasons to exit relays,
1381 or otherwise prevent future versions of this bug.
1384 - While setting up a hidden service, some valid introduction circuits
1385 were overlooked and abandoned. This might be the reason for
1386 the long delay in making a hidden service available. Bugfix on
1390 - Update to the "June 9 2008" ip-to-country file.
1391 - Run 'make test' as part of 'make dist', so we stop releasing so
1392 many development snapshots that fail their unit tests.
1395 - When we're checking if we have enough dir info for each relay
1396 to begin establishing circuits, make sure that we actually have
1397 the descriptor listed in the consensus, not just any descriptor.
1399 - Bridge relays no longer print "xx=0" in their extrainfo document
1400 for every single country code in the geoip db. Bugfix on
1402 - Only warn when we fail to load the geoip file if we were planning to
1403 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
1404 - If we change our MaxAdvertisedBandwidth and then reload torrc,
1405 Tor won't realize it should publish a new relay descriptor. Fixes
1406 bug 688, reported by mfr. Bugfix on 0.1.2.x.
1407 - When we haven't had any application requests lately, don't bother
1408 logging that we have expired a bunch of descriptors. Bugfix
1410 - Make relay cells written on a connection count as non-padding when
1411 tracking how long a connection has been in use. Bugfix on
1412 0.2.0.1-alpha. Spotted by lodger.
1413 - Fix unit tests in 0.2.0.27-rc.
1414 - Fix compile on Windows.
1417 Changes in version 0.2.0.27-rc - 2008-06-03
1418 Tor 0.2.0.27-rc adds a few features we left out of the earlier
1419 release candidates. In particular, we now include an IP-to-country
1420 GeoIP database, so controllers can easily look up what country a
1421 given relay is in, and so bridge relays can give us some sanitized
1422 summaries about which countries are making use of bridges. (See proposal
1423 126-geoip-fetching.txt for details.)
1426 - Include an IP-to-country GeoIP file in the tarball, so bridge
1427 relays can report sanitized summaries of the usage they're seeing.
1430 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
1431 Robert Hogan. Fixes the first part of bug 681.
1432 - Make bridge authorities never serve extrainfo docs.
1433 - Add support to detect Libevent versions in the 1.4.x series
1435 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
1436 - Include a new contrib/tor-exit-notice.html file that exit relay
1437 operators can put on their website to help reduce abuse queries.
1440 - When tunneling an encrypted directory connection, and its first
1441 circuit fails, do not leave it unattached and ask the controller
1442 to deal. Fixes the second part of bug 681.
1443 - Make bridge authorities correctly expire old extrainfo documents
1447 Changes in version 0.2.0.26-rc - 2008-05-13
1448 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
1449 in Debian's OpenSSL packages. All users running any 0.2.0.x version
1450 should upgrade, whether they're running Debian or not.
1452 o Major security fixes:
1453 - Use new V3 directory authority keys on the tor26, gabelmoo, and
1454 moria1 V3 directory authorities. The old keys were generated with
1455 a vulnerable version of Debian's OpenSSL package, and must be
1456 considered compromised. Other authorities' keys were not generated
1457 with an affected version of OpenSSL.
1460 - List authority signatures as "unrecognized" based on DirServer
1461 lines, not on cert cache. Bugfix on 0.2.0.x.
1464 - Add a new V3AuthUseLegacyKey option to make it easier for
1465 authorities to change their identity keys if they have to.
1468 Changes in version 0.2.0.25-rc - 2008-04-23
1469 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
1472 - Remember to initialize threading before initializing logging.
1473 Otherwise, many BSD-family implementations will crash hard on
1474 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
1477 - Authorities correctly free policies on bad servers on
1478 exit. Fixes bug 672. Bugfix on 0.2.0.x.
1481 Changes in version 0.2.0.24-rc - 2008-04-22
1482 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
1483 v3 directory authority, makes relays with dynamic IP addresses and no
1484 DirPort notice more quickly when their IP address changes, fixes a few
1485 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
1487 o New directory authorities:
1488 - Take lefkada out of the list of v3 directory authorities, since
1489 it has been down for months.
1490 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
1494 - Detect address changes more quickly on non-directory mirror
1495 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
1497 o Minor features (security):
1498 - Reject requests for reverse-dns lookup of names that are in
1499 a private address space. Patch from lodger.
1500 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
1503 o Minor bugfixes (crashes):
1504 - Avoid a rare assert that can trigger when Tor doesn't have much
1505 directory information yet and it tries to fetch a v2 hidden
1506 service descriptor. Fixes bug 651, reported by nwf.
1507 - Initialize log mutex before initializing dmalloc. Otherwise,
1508 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
1509 - Use recursive pthread mutexes in order to avoid deadlock when
1510 logging debug-level messages to a controller. Bug spotted by nwf,
1511 bugfix on 0.2.0.16-alpha.
1513 o Minor bugfixes (resource management):
1514 - Keep address policies from leaking memory: start their refcount
1515 at 1, not 2. Bugfix on 0.2.0.16-alpha.
1516 - Free authority certificates on exit, so they don't look like memory
1517 leaks. Bugfix on 0.2.0.19-alpha.
1518 - Free static hashtables for policy maps and for TLS connections on
1519 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
1520 - Avoid allocating extra space when computing consensuses on 64-bit
1521 platforms. Bug spotted by aakova.
1523 o Minor bugfixes (misc):
1524 - Do not read the configuration file when we've only been told to
1525 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
1526 based on patch from Sebastian Hahn.
1527 - Exit relays that are used as a client can now reach themselves
1528 using the .exit notation, rather than just launching an infinite
1529 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
1530 - When attempting to open a logfile fails, tell us why.
1531 - Fix a dumb bug that was preventing us from knowing that we should
1532 preemptively build circuits to handle expected directory requests.
1533 Fixes bug 660. Bugfix on 0.1.2.x.
1534 - Warn less verbosely about clock skew from netinfo cells from
1535 untrusted sources. Fixes bug 663.
1536 - Make controller stream events for DNS requests more consistent,
1537 by adding "new stream" events for DNS requests, and removing
1538 spurious "stream closed" events" for cached reverse resolves.
1539 Patch from mwenge. Fixes bug 646.
1540 - Correctly notify one-hop connections when a circuit build has
1541 failed. Possible fix for bug 669. Found by lodger.
1544 Changes in version 0.2.0.23-rc - 2008-03-24
1545 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
1546 makes bootstrapping faster if the first directory mirror you contact
1547 is down. The bundles also include the new Vidalia 0.1.2 release.
1550 - When a tunneled directory request is made to a directory server
1551 that's down, notice after 30 seconds rather than 120 seconds. Also,
1552 fail any begindir streams that are pending on it, so they can
1553 retry elsewhere. This was causing multi-minute delays on bootstrap.
1556 Changes in version 0.2.0.22-rc - 2008-03-18
1557 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
1558 enables encrypted directory connections by default for non-relays, fixes
1559 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
1560 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
1563 - Enable encrypted directory connections by default for non-relays,
1564 so censor tools that block Tor directory connections based on their
1565 plaintext patterns will no longer work. This means Tor works in
1566 certain censored countries by default again.
1569 - Make sure servers always request certificates from clients during
1570 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
1571 - Do not enter a CPU-eating loop when a connection is closed in
1572 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
1573 diagnosed by lodger; bugfix on 0.2.0.20-rc.
1574 - Fix assertion failure that could occur when a blocked circuit
1575 became unblocked, and it had pending client DNS requests. Bugfix
1576 on 0.2.0.1-alpha. Fixes bug 632.
1578 o Minor bugfixes (on 0.1.2.x):
1579 - Generate "STATUS_SERVER" events rather than misspelled
1580 "STATUS_SEVER" events. Caught by mwenge.
1581 - When counting the number of bytes written on a TLS connection,
1582 look at the BIO actually used for writing to the network, not
1583 at the BIO used (sometimes) to buffer data for the network.
1584 Looking at different BIOs could result in write counts on the
1585 order of ULONG_MAX. Fixes bug 614.
1586 - On Windows, correctly detect errors when listing the contents of
1587 a directory. Fix from lodger.
1589 o Minor bugfixes (on 0.2.0.x):
1590 - Downgrade "sslv3 alert handshake failure" message to INFO.
1591 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
1592 left BandwidthRate and BandwidthBurst at the default, we would be
1593 silently limited by those defaults. Now raise them to match the
1594 RelayBandwidth* values.
1595 - Fix the SVK version detection logic to work correctly on a branch.
1596 - Make --enable-openbsd-malloc work correctly on Linux with alpha
1597 CPUs. Fixes bug 625.
1598 - Logging functions now check that the passed severity is sane.
1599 - Use proper log levels in the testsuite call of
1600 get_interface_address6().
1601 - When using a nonstandard malloc, do not use the platform values for
1602 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
1603 - Make the openbsd malloc code use 8k pages on alpha CPUs and
1605 - Detect mismatched page sizes when using --enable-openbsd-malloc.
1606 - Avoid double-marked-for-close warning when certain kinds of invalid
1607 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
1608 for bug 617. Bugfix on 0.2.0.1-alpha.
1609 - Make sure that the "NULL-means-reject *:*" convention is followed by
1610 all the policy manipulation functions, avoiding some possible crash
1611 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
1612 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
1613 actually works, and doesn't warn about every single reverse lookup.
1614 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
1617 - Only log guard node status when guard node status has changed.
1618 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
1619 make "INFO" 75% less verbose.
1622 Changes in version 0.2.0.21-rc - 2008-03-02
1623 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
1624 makes Tor work well with Vidalia again, fixes a rare assert bug,
1625 and fixes a pair of more minor bugs. The bundles also include Vidalia
1626 0.1.0 and Torbutton 1.1.16.
1629 - The control port should declare that it requires password auth
1630 when HashedControlSessionPassword is set too. Patch from Matt Edman;
1631 bugfix on 0.2.0.20-rc. Fixes bug 615.
1632 - Downgrade assert in connection_buckets_decrement() to a log message.
1633 This may help us solve bug 614, and in any case will make its
1634 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
1635 - We were sometimes miscounting the number of bytes read from the
1636 network, causing our rate limiting to not be followed exactly.
1637 Bugfix on 0.2.0.16-alpha. Reported by lodger.
1640 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
1641 OpenSSL versions should have been working fine. Diagnosis and patch
1642 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
1643 Bugfix on 0.2.0.20-rc.
1646 Changes in version 0.2.0.20-rc - 2008-02-24
1647 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
1648 makes more progress towards normalizing Tor's TLS handshake, makes
1649 hidden services work better again, helps relays bootstrap if they don't
1650 know their IP address, adds optional support for linking in openbsd's
1651 allocator or tcmalloc, allows really fast relays to scale past 15000
1652 sockets, and fixes a bunch of minor bugs reported by Veracode.
1655 - Enable the revised TLS handshake based on the one designed by
1656 Steven Murdoch in proposal 124, as revised in proposal 130. It
1657 includes version negotiation for OR connections as described in
1658 proposal 105. The new handshake is meant to be harder for censors
1659 to fingerprint, and it adds the ability to detect certain kinds of
1660 man-in-the-middle traffic analysis attacks. The version negotiation
1661 feature will allow us to improve Tor's link protocol more safely
1663 - Choose which bridge to use proportional to its advertised bandwidth,
1664 rather than uniformly at random. This should speed up Tor for
1665 bridge users. Also do this for people who set StrictEntryNodes.
1666 - When a TrackHostExits-chosen exit fails too many times in a row,
1667 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
1670 - Resolved problems with (re-)fetching hidden service descriptors.
1671 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
1673 - If we only ever used Tor for hidden service lookups or posts, we
1674 would stop building circuits and start refusing connections after
1675 24 hours, since we falsely believed that Tor was dormant. Reported
1676 by nwf; bugfix on 0.1.2.x.
1677 - Servers that don't know their own IP address should go to the
1678 authorities for their first directory fetch, even if their DirPort
1679 is off or if they don't know they're reachable yet. This will help
1680 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
1681 - When counting the number of open sockets, count not only the number
1682 of sockets we have received from the socket() call, but also
1683 the number we've gotten from accept() and socketpair(). This bug
1684 made us fail to count all sockets that we were using for incoming
1685 connections. Bugfix on 0.2.0.x.
1686 - Fix code used to find strings within buffers, when those strings
1687 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
1688 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
1689 - Add a new __HashedControlSessionPassword option for controllers
1690 to use for one-off session password hashes that shouldn't get
1691 saved to disk by SAVECONF --- Vidalia users were accumulating a
1692 pile of HashedControlPassword lines in their torrc files, one for
1693 each time they had restarted Tor and then clicked Save. Make Tor
1694 automatically convert "HashedControlPassword" to this new option but
1695 only when it's given on the command line. Partial fix for bug 586.
1697 o Minor features (performance):
1698 - Tune parameters for cell pool allocation to minimize amount of
1700 - Add OpenBSD malloc code from phk as an optional malloc
1701 replacement on Linux: some glibc libraries do very poorly
1702 with Tor's memory allocation patterns. Pass
1703 --enable-openbsd-malloc to get the replacement malloc code.
1704 - Add a --with-tcmalloc option to the configure script to link
1705 against tcmalloc (if present). Does not yet search for
1706 non-system include paths.
1707 - Stop imposing an arbitrary maximum on the number of file descriptors
1708 used for busy servers. Bug reported by Olaf Selke; patch from
1711 o Minor features (other):
1712 - When SafeLogging is disabled, log addresses along with all TLS
1714 - When building with --enable-gcc-warnings, check for whether Apple's
1715 warning "-Wshorten-64-to-32" is available.
1716 - Add a --passphrase-fd argument to the tor-gencert command for
1719 o Minor bugfixes (memory leaks and code problems):
1720 - We were leaking a file descriptor if Tor started with a zero-length
1721 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
1722 - Detect size overflow in zlib code. Reported by Justin Ferguson and
1724 - We were comparing the raw BridgePassword entry with a base64'ed
1725 version of it, when handling a "/tor/networkstatus-bridges"
1726 directory request. Now compare correctly. Noticed by Veracode.
1727 - Recover from bad tracked-since value in MTBF-history file.
1729 - Alter the code that tries to recover from unhandled write
1730 errors, to not try to flush onto a socket that's given us
1731 unhandled errors. Bugfix on 0.1.2.x.
1732 - Make Unix controlsockets work correctly on OpenBSD. Patch from
1733 tup. Bugfix on 0.2.0.3-alpha.
1735 o Minor bugfixes (other):
1736 - If we have an extra-info document for our server, always make
1737 it available on the control port, even if we haven't gotten
1738 a copy of it from an authority yet. Patch from mwenge.
1739 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
1740 - Directory mirrors no longer include a guess at the client's IP
1741 address if the connection appears to be coming from the same /24
1742 network; it was producing too many wrong guesses.
1743 - Make the new hidden service code respect the SafeLogging setting.
1744 Bugfix on 0.2.0.x. Patch from Karsten.
1745 - When starting as an authority, do not overwrite all certificates
1746 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
1747 - If we're trying to flush the last bytes on a connection (for
1748 example, when answering a directory request), reset the
1749 time-to-give-up timeout every time we manage to write something
1750 on the socket. Bugfix on 0.1.2.x.
1751 - Change the behavior of "getinfo status/good-server-descriptor"
1752 so it doesn't return failure when any authority disappears.
1753 - Even though the man page said that "TrackHostExits ." should
1754 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
1755 - Report TLS "zero return" case as a "clean close" and "IO error"
1756 as a "close". Stop calling closes "unexpected closes": existing
1757 Tors don't use SSL_close(), so having a connection close without
1758 the TLS shutdown handshake is hardly unexpected.
1759 - Send NAMESERVER_STATUS messages for a single failed nameserver
1762 o Code simplifications and refactoring:
1763 - Remove the tor_strpartition function: its logic was confused,
1764 and it was only used for one thing that could be implemented far
1768 Changes in version 0.2.0.19-alpha - 2008-02-09
1769 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
1770 handshake, makes path selection for relays more secure and IP address
1771 guessing more robust, and generally fixes a lot of bugs in preparation
1772 for calling the 0.2.0 branch stable.
1775 - Do not include recognizeable strings in the commonname part of
1776 Tor's x509 certificates.
1779 - If we're a relay, avoid picking ourselves as an introduction point,
1780 a rendezvous point, or as the final hop for internal circuits. Bug
1781 reported by taranis and lodger. Bugfix on 0.1.2.x.
1782 - Patch from "Andrew S. Lists" to catch when we contact a directory
1783 mirror at IP address X and he says we look like we're coming from
1784 IP address X. Bugfix on 0.1.2.x.
1786 o Minor features (security):
1787 - Be more paranoid about overwriting sensitive memory on free(),
1788 as a defensive programming tactic to ensure forward secrecy.
1790 o Minor features (directory authority):
1791 - Actually validate the options passed to AuthDirReject,
1792 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
1793 - Reject router descriptors with out-of-range bandwidthcapacity or
1794 bandwidthburst values.
1796 o Minor features (controller):
1797 - Reject controller commands over 1MB in length. This keeps rogue
1798 processes from running us out of memory.
1800 o Minor features (misc):
1801 - Give more descriptive well-formedness errors for out-of-range
1802 hidden service descriptor/protocol versions.
1803 - Make memory debugging information describe more about history
1804 of cell allocation, so we can help reduce our memory use.
1806 o Deprecated features (controller):
1807 - The status/version/num-versioning and status/version/num-concurring
1808 GETINFO options are no longer useful in the v3 directory protocol:
1809 treat them as deprecated, and warn when they're used.
1812 - When our consensus networkstatus has been expired for a while, stop
1813 being willing to build circuits using it. Fixes bug 401. Bugfix
1815 - Directory caches now fetch certificates from all authorities
1816 listed in a networkstatus consensus, even when they do not
1817 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
1818 - When connecting to a bridge without specifying its key, insert
1819 the connection into the identity-to-connection map as soon as
1820 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
1821 - Detect versions of OS X where malloc_good_size() is present in the
1822 library but never actually declared. Resolves bug 587. Bugfix
1824 - Stop incorrectly truncating zlib responses to directory authority
1825 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
1826 - Stop recommending that every server operator send mail to tor-ops.
1827 Resolves bug 597. Bugfix on 0.1.2.x.
1828 - Don't trigger an assert if we start a directory authority with a
1829 private IP address (like 127.0.0.1).
1830 - Avoid possible failures when generating a directory with routers
1831 with over-long versions strings, or too many flags set. Bugfix
1833 - If an attempt to launch a DNS resolve request over the control
1834 port fails because we have overrun the limit on the number of
1835 connections, tell the controller that the request has failed.
1836 - Avoid using too little bandwidth when our clock skips a few
1837 seconds. Bugfix on 0.1.2.x.
1838 - Fix shell error when warning about missing packages in configure
1839 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
1840 - Do not become confused when receiving a spurious VERSIONS-like
1841 cell from a confused v1 client. Bugfix on 0.2.0.x.
1842 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
1843 introduction points for a hidden service have failed. Patch from
1844 Karsten Loesing. Bugfix on 0.2.0.x.
1846 o Code simplifications and refactoring:
1847 - Remove some needless generality from cpuworker code, for improved
1849 - Stop overloading the circuit_t.onionskin field for both "onionskin
1850 from a CREATE cell that we are waiting for a cpuworker to be
1851 assigned" and "onionskin from an EXTEND cell that we are going to
1852 send to an OR as soon as we are connected". Might help with bug 600.
1853 - Add an in-place version of aes_crypt() so that we can avoid doing a
1854 needless memcpy() call on each cell payload.
1857 Changes in version 0.2.0.18-alpha - 2008-01-25
1858 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
1859 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
1860 that can warn or reject connections to ports generally associated with
1861 vulnerable-plaintext protocols.
1863 o New directory authorities:
1864 - Set up dannenberg (run by CCC) as the sixth v3 directory
1868 - Fix a major memory leak when attempting to use the v2 TLS
1869 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
1870 - We accidentally enabled the under-development v2 TLS handshake
1871 code, which was causing log entries like "TLS error while
1872 renegotiating handshake". Disable it again. Resolves bug 590.
1873 - We were computing the wrong Content-Length: header for directory
1874 responses that need to be compressed on the fly, causing clients
1875 asking for those items to always fail. Bugfix on 0.2.0.x; partially
1879 - Avoid going directly to the directory authorities even if you're a
1880 relay, if you haven't found yourself reachable yet or if you've
1881 decided not to advertise your dirport yet. Addresses bug 556.
1882 - If we've gone 12 hours since our last bandwidth check, and we
1883 estimate we have less than 50KB bandwidth capacity but we could
1884 handle more, do another bandwidth test.
1885 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
1886 Tor can warn and/or refuse connections to ports commonly used with
1887 vulnerable-plaintext protocols. Currently we warn on ports 23,
1888 109, 110, and 143, but we don't reject any.
1891 - When we setconf ClientOnly to 1, close any current OR and Dir
1892 listeners. Reported by mwenge.
1893 - When we get a consensus that's been signed by more people than
1894 we expect, don't log about it; it's not a big deal. Reported
1898 - Don't answer "/tor/networkstatus-bridges" directory requests if
1899 the request isn't encrypted.
1900 - Make "ClientOnly 1" config option disable directory ports too.
1901 - Patches from Karsten Loesing to make v2 hidden services more
1902 robust: work even when there aren't enough HSDir relays available;
1903 retry when a v2 rend desc fetch fails; but don't retry if we
1904 already have a usable v0 rend desc.
1907 Changes in version 0.2.0.17-alpha - 2008-01-17
1908 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
1911 - Make the tor-gencert man page get included correctly in the tarball.
1914 Changes in version 0.2.0.16-alpha - 2008-01-17
1915 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
1916 Loesing, and generally cleans up a lot of features and minor bugs.
1918 o New directory authorities:
1919 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
1922 o Major performance improvements:
1923 - Switch our old ring buffer implementation for one more like that
1924 used by free Unix kernels. The wasted space in a buffer with 1mb
1925 of data will now be more like 8k than 1mb. The new implementation
1926 also avoids realloc();realloc(); patterns that can contribute to
1927 memory fragmentation.
1930 - Configuration files now accept C-style strings as values. This
1931 helps encode characters not allowed in the current configuration
1932 file format, such as newline or #. Addresses bug 557.
1933 - Although we fixed bug 539 (where servers would send HTTP status 503
1934 responses _and_ send a body too), there are still servers out
1935 there that haven't upgraded. Therefore, make clients parse such
1936 bodies when they receive them.
1937 - When we're not serving v2 directory information, there is no reason
1938 to actually keep any around. Remove the obsolete files and directory
1939 on startup if they are very old and we aren't going to serve them.
1941 o Minor performance improvements:
1942 - Reference-count and share copies of address policy entries; only 5%
1943 of them were actually distinct.
1944 - Never walk through the list of logs if we know that no log is
1945 interested in a given message.
1948 - When an authority has not signed a consensus, do not try to
1949 download a nonexistent "certificate with key 00000000". Bugfix
1950 on 0.2.0.x. Fixes bug 569.
1951 - Fix a rare assert error when we're closing one of our threads:
1952 use a mutex to protect the list of logs, so we never write to the
1953 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
1954 bug 575, which is kind of the revenge of bug 222.
1955 - Patch from Karsten Loesing to complain less at both the client
1956 and the relay when a relay used to have the HSDir flag but doesn't
1957 anymore, and we try to upload a hidden service descriptor.
1958 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
1960 - Do not try to download missing certificates until we have tried
1961 to check our fallback consensus. Fixes bug 583.
1962 - Make bridges round reported GeoIP stats info up to the nearest
1963 estimate, not down. Now we can distinguish between "0 people from
1964 this country" and "1 person from this country".
1965 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
1966 - Avoid possible segfault if key generation fails in
1967 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
1968 - Avoid segfault in the case where a badly behaved v2 versioning
1969 directory sends a signed networkstatus with missing client-versions.
1971 - Avoid segfaults on certain complex invocations of
1972 router_get_by_hexdigest(). Bugfix on 0.1.2.
1973 - Correct bad index on array access in parse_http_time(). Bugfix
1975 - Fix possible bug in vote generation when server versions are present
1976 but client versions are not.
1977 - Fix rare bug on REDIRECTSTREAM control command when called with no
1978 port set: it could erroneously report an error when none had
1980 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
1981 compressing large objects and find ourselves with more than 4k
1982 left over. Bugfix on 0.2.0.
1983 - Fix a small memory leak when setting up a hidden service.
1984 - Fix a few memory leaks that could in theory happen under bizarre
1986 - Fix an assert if we post a general-purpose descriptor via the
1987 control port but that descriptor isn't mentioned in our current
1988 network consensus. Bug reported by Jon McLachlan; bugfix on
1991 o Minor features (controller):
1992 - Get NS events working again. Patch from tup.
1993 - The GETCONF command now escapes and quotes configuration values
1994 that don't otherwise fit into the torrc file.
1995 - The SETCONF command now handles quoted values correctly.
1997 o Minor features (directory authorities):
1998 - New configuration options to override default maximum number of
1999 servers allowed on a single IP address. This is important for
2000 running a test network on a single host.
2001 - Actually implement the -s option to tor-gencert.
2002 - Add a manual page for tor-gencert.
2004 o Minor features (bridges):
2005 - Bridge authorities no longer serve bridge descriptors over
2006 unencrypted connections.
2008 o Minor features (other):
2009 - Add hidden services and DNSPorts to the list of things that make
2010 Tor accept that it has running ports. Change starting Tor with no
2011 ports from a fatal error to a warning; we might change it back if
2012 this turns out to confuse anybody. Fixes bug 579.
2015 Changes in version 0.1.2.19 - 2008-01-17
2016 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
2017 exit policy a little bit more conservative so it's safer to run an
2018 exit relay on a home system, and fixes a variety of smaller issues.
2021 - Exit policies now reject connections that are addressed to a
2022 relay's public (external) IP address too, unless
2023 ExitPolicyRejectPrivate is turned off. We do this because too
2024 many relays are running nearby to services that trust them based
2028 - When the clock jumps forward a lot, do not allow the bandwidth
2029 buckets to become negative. Fixes bug 544.
2030 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
2031 on every successful resolve. Reported by Mike Perry.
2032 - Purge old entries from the "rephist" database and the hidden
2033 service descriptor database even when DirPort is zero.
2034 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
2035 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
2036 crashing or mis-answering these requests.
2037 - When we decide to send a 503 response to a request for servers, do
2038 not then also send the server descriptors: this defeats the whole
2039 purpose. Fixes bug 539.
2042 - Changing the ExitPolicyRejectPrivate setting should cause us to
2043 rebuild our server descriptor.
2044 - Fix handling of hex nicknames when answering controller requests for
2045 networkstatus by name, or when deciding whether to warn about
2046 unknown routers in a config option. (Patch from mwenge.)
2047 - Fix a couple of hard-to-trigger autoconf problems that could result
2048 in really weird results on platforms whose sys/types.h files define
2049 nonstandard integer types.
2050 - Don't try to create the datadir when running --verify-config or
2051 --hash-password. Resolves bug 540.
2052 - If we were having problems getting a particular descriptor from the
2053 directory caches, and then we learned about a new descriptor for
2054 that router, we weren't resetting our failure count. Reported
2056 - Although we fixed bug 539 (where servers would send HTTP status 503
2057 responses _and_ send a body too), there are still servers out there
2058 that haven't upgraded. Therefore, make clients parse such bodies
2059 when they receive them.
2060 - Run correctly on systems where rlim_t is larger than unsigned long.
2061 This includes some 64-bit systems.
2062 - Run correctly on platforms (like some versions of OS X 10.5) where
2063 the real limit for number of open files is OPEN_FILES, not rlim_max
2064 from getrlimit(RLIMIT_NOFILES).
2065 - Avoid a spurious free on base64 failure.
2066 - Avoid segfaults on certain complex invocations of
2067 router_get_by_hexdigest().
2068 - Fix rare bug on REDIRECTSTREAM control command when called with no
2069 port set: it could erroneously report an error when none had
2073 Changes in version 0.2.0.15-alpha - 2007-12-25
2074 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
2075 features added in 0.2.0.13-alpha.
2078 - Fix several remotely triggerable asserts based on DirPort requests
2079 for a v2 or v3 networkstatus object before we were prepared. This
2080 was particularly bad for 0.2.0.13 and later bridge relays, who
2081 would never have a v2 networkstatus and would thus always crash
2082 when used. Bugfixes on 0.2.0.x.
2083 - Estimate the v3 networkstatus size more accurately, rather than
2084 estimating it at zero bytes and giving it artificially high priority
2085 compared to other directory requests. Bugfix on 0.2.0.x.
2088 - Fix configure.in logic for cross-compilation.
2089 - When we load a bridge descriptor from the cache, and it was
2090 previously unreachable, mark it as retriable so we won't just
2091 ignore it. Also, try fetching a new copy immediately. Bugfixes
2093 - The bridge GeoIP stats were counting other relays, for example
2094 self-reachability and authority-reachability tests.
2097 - Support compilation to target iPhone; patch from cjacker huang.
2098 To build for iPhone, pass the --enable-iphone option to configure.
2101 Changes in version 0.2.0.14-alpha - 2007-12-23
2103 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
2104 without a datadirectory from a previous Tor install. Reported
2106 - Fix a crash when we fetch a descriptor that turns out to be
2107 unexpected (it used to be in our networkstatus when we started
2108 fetching it, but it isn't in our current networkstatus), and we
2109 aren't using bridges. Bugfix on 0.2.0.x.
2110 - Fix a crash when accessing hidden services: it would work the first
2111 time you use a given introduction point for your service, but
2112 on subsequent requests we'd be using garbage memory. Fixed by
2113 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
2114 - Fix a crash when we load a bridge descriptor from disk but we don't
2115 currently have a Bridge line for it in our torrc. Bugfix on
2119 - If bridge authorities set BridgePassword, they will serve a
2120 snapshot of known bridge routerstatuses from their DirPort to
2121 anybody who knows that password. Unset by default.
2124 - Make the unit tests build again.
2125 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
2126 - Make PublishServerDescriptor default to 1, so the default doesn't
2127 have to change as we invent new directory protocol versions.
2128 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
2129 be included unless sys/time.h is already included. Fixes
2130 bug 553. Bugfix on 0.2.0.x.
2131 - If we receive a general-purpose descriptor and then receive an
2132 identical bridge-purpose descriptor soon after, don't discard
2133 the next one as a duplicate.
2136 - If BridgeRelay is set to 1, then the default for
2137 PublishServerDescriptor is now "bridge" rather than "v2,v3".
2138 - If the user sets RelayBandwidthRate but doesn't set
2139 RelayBandwidthBurst, then make them equal rather than erroring out.
2142 Changes in version 0.2.0.13-alpha - 2007-12-21
2143 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
2144 Goodell, fixes many more bugs, and adds a lot of infrastructure for
2147 o New directory authorities:
2148 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
2152 - Only update guard status (usable / not usable) once we have
2153 enough directory information. This was causing us to always pick
2154 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
2155 causing us to discard all our guards on startup if we hadn't been
2156 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
2157 - Purge old entries from the "rephist" database and the hidden
2158 service descriptor databases even when DirPort is zero. Bugfix
2160 - We were ignoring our RelayBandwidthRate for the first 30 seconds
2161 after opening a circuit -- even a relayed circuit. Bugfix on
2163 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
2164 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
2165 crashing or mis-answering these types of requests.
2166 - Relays were publishing their server descriptor to v1 and v2
2167 directory authorities, but they didn't try publishing to v3-only
2168 authorities. Fix this; and also stop publishing to v1 authorities.
2170 - When we were reading router descriptors from cache, we were ignoring
2171 the annotations -- so for example we were reading in bridge-purpose
2172 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
2173 - When we decided to send a 503 response to a request for servers, we
2174 were then also sending the server descriptors: this defeats the
2175 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
2178 - Bridge relays now behave like clients with respect to time
2179 intervals for downloading new consensus documents -- otherwise they
2180 stand out. Bridge users now wait until the end of the interval,
2181 so their bridge relay will be sure to have a new consensus document.
2182 - Three new config options (AlternateDirAuthority,
2183 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
2184 user selectively replace the default directory authorities by type,
2185 rather than the all-or-nothing replacement that DirServer offers.
2186 - Tor can now be configured to read a GeoIP file from disk in one
2187 of two formats. This can be used by controllers to map IP addresses
2188 to countries. Eventually, it may support exit-by-country.
2189 - When possible, bridge relays remember which countries users
2190 are coming from, and report aggregate information in their
2191 extra-info documents, so that the bridge authorities can learn
2192 where Tor is blocked.
2193 - Bridge directory authorities now do reachability testing on the
2194 bridges they know. They provide router status summaries to the
2195 controller via "getinfo ns/purpose/bridge", and also dump summaries
2196 to a file periodically.
2197 - Stop fetching directory info so aggressively if your DirPort is
2198 on but your ORPort is off; stop fetching v2 dir info entirely.
2199 You can override these choices with the new FetchDirInfoEarly
2203 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
2204 consensus documents when there are too many relays at a single
2205 IP address. Now clear it in v2 network status documents too, and
2206 also clear it in routerinfo_t when the relay is no longer listed
2207 in the relevant networkstatus document.
2208 - Don't crash if we get an unexpected value for the
2209 PublishServerDescriptor config option. Reported by Matt Edman;
2210 bugfix on 0.2.0.9-alpha.
2211 - Our new v2 hidden service descriptor format allows descriptors
2212 that have no introduction points. But Tor crashed when we tried
2213 to build a descriptor with no intro points (and it would have
2214 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
2216 - Fix building with dmalloc 5.5.2 with glibc.
2217 - Reject uploaded descriptors and extrainfo documents if they're
2218 huge. Otherwise we'll cache them all over the network and it'll
2219 clog everything up. Reported by Aljosha Judmayer.
2220 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
2221 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
2222 - When the DANGEROUS_VERSION controller status event told us we're
2223 running an obsolete version, it used the string "OLD" to describe
2224 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
2225 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
2226 - If we can't expand our list of entry guards (e.g. because we're
2227 using bridges or we have StrictEntryNodes set), don't mark relays
2228 down when they fail a directory request. Otherwise we're too quick
2229 to mark all our entry points down. Bugfix on 0.1.2.x.
2230 - Fix handling of hex nicknames when answering controller requests for
2231 networkstatus by name, or when deciding whether to warn about unknown
2232 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
2233 - Fix a couple of hard-to-trigger autoconf problems that could result
2234 in really weird results on platforms whose sys/types.h files define
2235 nonstandard integer types. Bugfix on 0.1.2.x.
2236 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
2237 - Don't crash on name lookup when we have no current consensus. Fixes
2238 bug 538; bugfix on 0.2.0.x.
2239 - Only Tors that want to mirror the v2 directory info should
2240 create the "cached-status" directory in their datadir. (All Tors
2241 used to create it.) Bugfix on 0.2.0.9-alpha.
2242 - Directory authorities should only automatically download Extra Info
2243 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
2246 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
2247 consumers. (We already do this on HUP.)
2248 - Authorities and caches fetch the v2 networkstatus documents
2249 less often, now that v3 is encouraged.
2250 - Add a new config option BridgeRelay that specifies you want to
2251 be a bridge relay. Right now the only difference is that it makes
2252 you answer begin_dir requests, and it makes you cache dir info,
2253 even if your DirPort isn't on.
2254 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
2255 ask about source, timestamp of arrival, purpose, etc. We need
2256 something like this to help Vidalia not do GeoIP lookups on bridge
2258 - Allow multiple HashedControlPassword config lines, to support
2259 multiple controller passwords.
2260 - Authorities now decide whether they're authoritative for a given
2261 router based on the router's purpose.
2262 - New config options AuthDirBadDir and AuthDirListBadDirs for
2263 authorities to mark certain relays as "bad directories" in the
2264 networkstatus documents. Also supports the "!baddir" directive in
2265 the approved-routers file.
2268 Changes in version 0.2.0.12-alpha - 2007-11-16
2269 This twelfth development snapshot fixes some more build problems as
2270 well as a few minor bugs.
2273 - Make it build on OpenBSD again. Patch from tup.
2274 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
2275 package-building for Red Hat, OS X, etc.
2277 o Minor bugfixes (on 0.1.2.x):
2278 - Changing the ExitPolicyRejectPrivate setting should cause us to
2279 rebuild our server descriptor.
2281 o Minor bugfixes (on 0.2.0.x):
2282 - When we're lacking a consensus, don't try to perform rendezvous
2283 operations. Reported by Karsten Loesing.
2284 - Fix a small memory leak whenever we decide against using a
2285 newly picked entry guard. Reported by Mike Perry.
2286 - When authorities detected more than two relays running on the same
2287 IP address, they were clearing all the status flags but forgetting
2288 to clear the "hsdir" flag. So clients were being told that a
2289 given relay was the right choice for a v2 hsdir lookup, yet they
2290 never had its descriptor because it was marked as 'not running'
2292 - If we're trying to fetch a bridge descriptor and there's no way
2293 the bridge authority could help us (for example, we don't know
2294 a digest, or there is no bridge authority), don't be so eager to
2295 fall back to asking the bridge authority.
2296 - If we're using bridges or have strictentrynodes set, and our
2297 chosen exit is in the same family as all our bridges/entry guards,
2298 then be flexible about families.
2301 - When we negotiate a v2 link-layer connection (not yet implemented),
2302 accept RELAY_EARLY cells and turn them into RELAY cells if we've
2303 negotiated a v1 connection for their next step. Initial code for
2307 Changes in version 0.2.0.11-alpha - 2007-11-12
2308 This eleventh development snapshot fixes some build problems with
2309 the previous snapshot. It also includes a more secure-by-default exit
2310 policy for relays, fixes an enormous memory leak for exit relays, and
2311 fixes another bug where servers were falling out of the directory list.
2314 - Exit policies now reject connections that are addressed to a
2315 relay's public (external) IP address too, unless
2316 ExitPolicyRejectPrivate is turned off. We do this because too
2317 many relays are running nearby to services that trust them based
2318 on network address. Bugfix on 0.1.2.x.
2321 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
2322 on every successful resolve. Reported by Mike Perry; bugfix
2324 - On authorities, never downgrade to old router descriptors simply
2325 because they're listed in the consensus. This created a catch-22
2326 where we wouldn't list a new descriptor because there was an
2327 old one in the consensus, and we couldn't get the new one in the
2328 consensus because we wouldn't list it. Possible fix for bug 548.
2329 Also, this might cause bug 543 to appear on authorities; if so,
2330 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
2332 o Packaging fixes on 0.2.0.10-alpha:
2333 - We were including instructions about what to do with the
2334 src/config/fallback-consensus file, but we weren't actually
2335 including it in the tarball. Disable all of that for now.
2338 - Allow people to say PreferTunnelledDirConns rather than
2339 PreferTunneledDirConns, for those alternate-spellers out there.
2342 - Don't reevaluate all the information from our consensus document
2343 just because we've downloaded a v2 networkstatus that we intend
2344 to cache. Fixes bug 545; bugfix on 0.2.0.x.
2347 Changes in version 0.2.0.10-alpha - 2007-11-10
2348 This tenth development snapshot adds a third v3 directory authority
2349 run by Mike Perry, adds most of Karsten Loesing's new hidden service
2350 descriptor format, fixes a bad crash bug and new bridge bugs introduced
2351 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
2352 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
2353 addresses many more minor issues.
2355 o New directory authorities:
2356 - Set up ides (run by Mike Perry) as the third v3 directory authority.
2359 - Allow tunnelled directory connections to ask for an encrypted
2360 "begin_dir" connection or an anonymized "uses a full Tor circuit"
2361 connection independently. Now we can make anonymized begin_dir
2362 connections for (e.g.) more secure hidden service posting and
2364 - More progress on proposal 114: code from Karsten Loesing to
2365 implement new hidden service descriptor format.
2366 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
2367 accommodate the growing number of servers that use the default
2368 and are reaching it.
2369 - Directory authorities use a new formula for selecting which nodes
2370 to advertise as Guards: they must be in the top 7/8 in terms of
2371 how long we have known about them, and above the median of those
2372 nodes in terms of weighted fractional uptime.
2373 - Make "not enough dir info yet" warnings describe *why* Tor feels
2374 it doesn't have enough directory info yet.
2377 - Stop servers from crashing if they set a Family option (or
2378 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
2380 - Make bridge users work again -- the move to v3 directories in
2381 0.2.0.9-alpha had introduced a number of bugs that made bridges
2382 no longer work for clients.
2383 - When the clock jumps forward a lot, do not allow the bandwidth
2384 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
2386 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
2387 - When the consensus lists a router descriptor that we previously were
2388 mirroring, but that we considered non-canonical, reload the
2389 descriptor as canonical. This fixes bug 543 where Tor servers
2390 would start complaining after a few days that they don't have
2391 enough directory information to build a circuit.
2392 - Consider replacing the current consensus when certificates arrive
2393 that make the pending consensus valid. Previously, we were only
2394 considering replacement when the new certs _didn't_ help.
2395 - Fix an assert error on startup if we didn't already have the
2396 consensus and certs cached in our datadirectory: we were caching
2397 the consensus in consensus_waiting_for_certs but then free'ing it
2399 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
2400 Request) if we need more v3 certs but we've already got pending
2401 requests for all of them.
2402 - Correctly back off from failing certificate downloads. Fixes
2404 - Authorities don't vote on the Running flag if they have been running
2405 for less than 30 minutes themselves. Fixes bug 547, where a newly
2406 started authority would vote that everyone was down.
2409 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
2410 it, it had no AES, and it hasn't seen any security patches since
2414 - Clients now hold circuitless TLS connections open for 1.5 times
2415 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
2416 rebuild a new circuit over them within that timeframe. Previously,
2417 they held them open only for KeepalivePeriod (5 minutes).
2418 - Use "If-Modified-Since" to avoid retrieving consensus
2419 networkstatuses that we already have.
2420 - When we have no consensus, check FallbackNetworkstatusFile (defaults
2421 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
2422 we start knowing some directory caches.
2423 - When we receive a consensus from the future, warn about skew.
2424 - Improve skew reporting: try to give the user a better log message
2425 about how skewed they are, and how much this matters.
2426 - When we have a certificate for an authority, believe that
2427 certificate's claims about the authority's IP address.
2428 - New --quiet command-line option to suppress the default console log.
2429 Good in combination with --hash-password.
2430 - Authorities send back an X-Descriptor-Not-New header in response to
2431 an accepted-but-discarded descriptor upload. Partially implements
2433 - Make the log message for "tls error. breaking." more useful.
2434 - Better log messages about certificate downloads, to attempt to
2435 track down the second incarnation of bug 546.
2437 o Minor features (bridges):
2438 - If bridge users set UpdateBridgesFromAuthority, but the digest
2439 they ask for is a 404 from the bridge authority, they now fall
2440 back to trying the bridge directly.
2441 - Bridges now use begin_dir to publish their server descriptor to
2442 the bridge authority, even when they haven't set TunnelDirConns.
2444 o Minor features (controller):
2445 - When reporting clock skew, and we know that the clock is _at least
2446 as skewed_ as some value, but we don't know the actual value,
2447 report the value as a "minimum skew."
2450 - Update linux-tor-prio.sh script to allow QoS based on the uid of
2451 the Tor process. Patch from Marco Bonetti with tweaks from Mike
2455 - Refuse to start if both ORPort and UseBridges are set. Bugfix
2456 on 0.2.0.x, suggested by Matt Edman.
2457 - Don't stop fetching descriptors when FetchUselessDescriptors is
2458 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
2459 reported by tup and ioerror.
2460 - Better log message on vote from unknown authority.
2461 - Don't log "Launching 0 request for 0 router" message.
2463 o Minor bugfixes (memory leaks):
2464 - Stop leaking memory every time we parse a v3 certificate. Bugfix
2466 - Stop leaking memory every time we load a v3 certificate. Bugfix
2467 on 0.2.0.1-alpha. Fixes bug 536.
2468 - Stop leaking a cached networkstatus on exit. Bugfix on
2470 - Stop leaking voter information every time we free a consensus.
2471 Bugfix on 0.2.0.3-alpha.
2472 - Stop leaking signed data every time we check a voter signature.
2473 Bugfix on 0.2.0.3-alpha.
2474 - Stop leaking a signature every time we fail to parse a consensus or
2475 a vote. Bugfix on 0.2.0.3-alpha.
2476 - Stop leaking v2_download_status_map on shutdown. Bugfix on
2478 - Stop leaking conn->nickname every time we make a connection to a
2479 Tor relay without knowing its expected identity digest (e.g. when
2480 using bridges). Bugfix on 0.2.0.3-alpha.
2482 - Minor bugfixes (portability):
2483 - Run correctly on platforms where rlim_t is larger than unsigned
2484 long, and/or where the real limit for number of open files is
2485 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
2486 particular, these may be needed for OS X 10.5.
2489 Changes in version 0.1.2.18 - 2007-10-28
2490 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
2491 hidden service introduction that were causing huge delays, and a big
2492 bug that was causing some servers to disappear from the network status
2493 lists for a few hours each day.
2495 o Major bugfixes (crashes):
2496 - If a connection is shut down abruptly because of something that
2497 happened inside connection_flushed_some(), do not call
2498 connection_finished_flushing(). Should fix bug 451:
2499 "connection_stop_writing: Assertion conn->write_event failed"
2500 Bugfix on 0.1.2.7-alpha.
2501 - Fix possible segfaults in functions called from
2502 rend_process_relay_cell().
2504 o Major bugfixes (hidden services):
2505 - Hidden services were choosing introduction points uniquely by
2506 hexdigest, but when constructing the hidden service descriptor
2507 they merely wrote the (potentially ambiguous) nickname.
2508 - Clients now use the v2 intro format for hidden service
2509 connections: they specify their chosen rendezvous point by identity
2510 digest rather than by (potentially ambiguous) nickname. These
2511 changes could speed up hidden service connections dramatically.
2513 o Major bugfixes (other):
2514 - Stop publishing a new server descriptor just because we get a
2515 HUP signal. This led (in a roundabout way) to some servers getting
2516 dropped from the networkstatus lists for a few hours each day.
2517 - When looking for a circuit to cannibalize, consider family as well
2518 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
2519 circuit cannibalization).
2520 - When a router wasn't listed in a new networkstatus, we were leaving
2521 the flags for that router alone -- meaning it remained Named,
2522 Running, etc -- even though absence from the networkstatus means
2523 that it shouldn't be considered to exist at all anymore. Now we
2524 clear all the flags for routers that fall out of the networkstatus
2525 consensus. Fixes bug 529.
2528 - Don't try to access (or alter) the state file when running
2529 --list-fingerprint or --verify-config or --hash-password. Resolves
2531 - When generating information telling us how to extend to a given
2532 router, do not try to include the nickname if it is
2533 absent. Resolves bug 467.
2534 - Fix a user-triggerable segfault in expand_filename(). (There isn't
2535 a way to trigger this remotely.)
2536 - When sending a status event to the controller telling it that an
2537 OR address is reachable, set the port correctly. (Previously we
2538 were reporting the dir port.)
2539 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
2540 command. Bugfix on 0.1.2.17.
2541 - When loading bandwidth history, do not believe any information in
2542 the future. Fixes bug 434.
2543 - When loading entry guard information, do not believe any information
2545 - When we have our clock set far in the future and generate an
2546 onion key, then re-set our clock to be correct, we should not stop
2547 the onion key from getting rotated.
2548 - On some platforms, accept() can return a broken address. Detect
2549 this more quietly, and deal accordingly. Fixes bug 483.
2550 - It's not actually an error to find a non-pending entry in the DNS
2551 cache when canceling a pending resolve. Don't log unless stuff
2552 is fishy. Resolves bug 463.
2553 - Don't reset trusted dir server list when we set a configuration
2554 option. Patch from Robert Hogan.
2555 - Don't try to create the datadir when running --verify-config or
2556 --hash-password. Resolves bug 540.
2559 Changes in version 0.2.0.9-alpha - 2007-10-24
2560 This ninth development snapshot switches clients to the new v3 directory
2561 system; allows servers to be listed in the network status even when they
2562 have the same nickname as a registered server; and fixes many other
2563 bugs including a big one that was causing some servers to disappear
2564 from the network status lists for a few hours each day.
2566 o Major features (directory system):
2567 - Clients now download v3 consensus networkstatus documents instead
2568 of v2 networkstatus documents. Clients and caches now base their
2569 opinions about routers on these consensus documents. Clients only
2570 download router descriptors listed in the consensus.
2571 - Authorities now list servers who have the same nickname as
2572 a different named server, but list them with a new flag,
2573 "Unnamed". Now we can list servers that happen to pick the same
2574 nickname as a server that registered two years ago and then
2575 disappeared. Partially implements proposal 122.
2576 - If the consensus lists a router as "Unnamed", the name is assigned
2577 to a different router: do not identify the router by that name.
2578 Partially implements proposal 122.
2579 - Authorities can now come to a consensus on which method to use to
2580 compute the consensus. This gives us forward compatibility.
2583 - Stop publishing a new server descriptor just because we HUP or
2584 when we find our DirPort to be reachable but won't actually publish
2585 it. New descriptors without any real changes are dropped by the
2586 authorities, and can screw up our "publish every 18 hours" schedule.
2588 - When a router wasn't listed in a new networkstatus, we were leaving
2589 the flags for that router alone -- meaning it remained Named,
2590 Running, etc -- even though absence from the networkstatus means
2591 that it shouldn't be considered to exist at all anymore. Now we
2592 clear all the flags for routers that fall out of the networkstatus
2593 consensus. Fixes bug 529; bugfix on 0.1.2.x.
2594 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
2595 extrainfo documents and then discard them immediately for not
2596 matching the latest router. Bugfix on 0.2.0.1-alpha.
2598 o Minor features (v3 directory protocol):
2599 - Allow tor-gencert to generate a new certificate without replacing
2601 - Allow certificates to include an address.
2602 - When we change our directory-cache settings, reschedule all voting
2603 and download operations.
2604 - Reattempt certificate downloads immediately on failure, as long as
2605 we haven't failed a threshold number of times yet.
2606 - Delay retrying consensus downloads while we're downloading
2607 certificates to verify the one we just got. Also, count getting a
2608 consensus that we already have (or one that isn't valid) as a failure,
2609 and count failing to get the certificates after 20 minutes as a
2611 - Build circuits and download descriptors even if our consensus is a
2612 little expired. (This feature will go away once authorities are
2615 o Minor features (router descriptor cache):
2616 - If we find a cached-routers file that's been sitting around for more
2617 than 28 days unmodified, then most likely it's a leftover from
2618 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
2620 - When we (as a cache) download a descriptor because it was listed
2621 in a consensus, remember when the consensus was supposed to expire,
2622 and don't expire the descriptor until then.
2624 o Minor features (performance):
2625 - Call routerlist_remove_old_routers() much less often. This should
2626 speed startup, especially on directory caches.
2627 - Don't try to launch new descriptor downloads quite so often when we
2628 already have enough directory information to build circuits.
2629 - Base64 decoding was actually showing up on our profile when parsing
2630 the initial descriptor file; switch to an in-process all-at-once
2631 implementation that's about 3.5x times faster than calling out to
2634 o Minor features (compilation):
2635 - Detect non-ASCII platforms (if any still exist) and refuse to
2636 build there: some of our code assumes that 'A' is 65 and so on.
2638 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
2639 - Make the "next period" votes into "current period" votes immediately
2640 after publishing the consensus; avoid a heisenbug that made them
2641 stick around indefinitely.
2642 - When we discard a vote as a duplicate, do not report this as
2644 - Treat missing v3 keys or certificates as an error when running as a
2645 v3 directory authority.
2646 - When we're configured to be a v3 authority, but we're only listed
2647 as a non-v3 authority in our DirServer line for ourself, correct
2649 - If an authority doesn't have a qualified hostname, just put
2650 its address in the vote. This fixes the problem where we referred to
2651 "moria on moria:9031."
2652 - Distinguish between detached signatures for the wrong period, and
2653 detached signatures for a divergent vote.
2654 - Fix a small memory leak when computing a consensus.
2655 - When there's no concensus, we were forming a vote every 30
2656 minutes, but writing the "valid-after" line in our vote based
2657 on our configured V3AuthVotingInterval: so unless the intervals
2658 matched up, we immediately rejected our own vote because it didn't
2659 start at the voting interval that caused us to construct a vote.
2661 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
2662 - Delete unverified-consensus when the real consensus is set.
2663 - Consider retrying a consensus networkstatus fetch immediately
2664 after one fails: don't wait 60 seconds to notice.
2665 - When fetching a consensus as a cache, wait until a newer consensus
2666 should exist before trying to replace the current one.
2667 - Use a more forgiving schedule for retrying failed consensus
2668 downloads than for other types.
2670 o Minor bugfixes (other directory issues):
2671 - Correct the implementation of "download votes by digest." Bugfix on
2673 - Authorities no longer send back "400 you're unreachable please fix
2674 it" errors to Tor servers that aren't online all the time. We're
2675 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
2677 o Minor bugfixes (controller):
2678 - Don't reset trusted dir server list when we set a configuration
2679 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
2680 - Respond to INT and TERM SIGNAL commands before we execute the
2681 signal, in case the signal shuts us down. We had a patch in
2682 0.1.2.1-alpha that tried to do this by queueing the response on
2683 the connection's buffer before shutting down, but that really
2684 isn't the same thing at all. Bug located by Matt Edman.
2686 o Minor bugfixes (misc):
2687 - Correctly check for bad options to the "PublishServerDescriptor"
2688 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
2689 - Stop leaking memory on failing case of base32_decode, and make
2690 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
2691 - Don't try to download extrainfo documents when we're trying to
2692 fetch enough directory info to build a circuit: having enough
2693 info should get priority. Bugfix on 0.2.0.x.
2694 - Don't complain that "your server has not managed to confirm that its
2695 ports are reachable" if we haven't been able to build any circuits
2696 yet. Bug found by spending four hours without a v3 consensus. Bugfix
2698 - Detect the reason for failing to mmap a descriptor file we just
2699 wrote, and give a more useful log message. Fixes bug 533. Bugfix
2702 o Code simplifications and refactoring:
2703 - Remove support for the old bw_accounting file: we've been storing
2704 bandwidth accounting information in the state file since
2705 0.1.2.5-alpha. This may result in bandwidth accounting errors
2706 if you try to upgrade from 0.1.1.x or earlier, or if you try to
2707 downgrade to 0.1.1.x or earlier.
2708 - New convenience code to locate a file within the DataDirectory.
2709 - Move non-authority functionality out of dirvote.c.
2710 - Refactor the arguments for router_pick_{directory_|trusteddir}server
2711 so that they all take the same named flags.
2714 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
2715 Unix users an easy way to script their Tor process (e.g. by
2716 adjusting bandwidth based on the time of the day).
2719 Changes in version 0.2.0.8-alpha - 2007-10-12
2720 This eighth development snapshot fixes a crash bug that's been bothering
2721 us since February 2007, lets bridge authorities store a list of bridge
2722 descriptors they've seen, gets v3 directory voting closer to working,
2723 starts caching v3 directory consensus documents on directory mirrors,
2724 and fixes a variety of smaller issues including some minor memory leaks.
2726 o Major features (router descriptor cache):
2727 - Store routers in a file called cached-descriptors instead of in
2728 cached-routers. Initialize cached-descriptors from cached-routers
2729 if the old format is around. The new format allows us to store
2730 annotations along with descriptors.
2731 - Use annotations to record the time we received each descriptor, its
2732 source, and its purpose.
2733 - Disable the SETROUTERPURPOSE controller command: it is now
2735 - Controllers should now specify cache=no or cache=yes when using
2736 the +POSTDESCRIPTOR command.
2737 - Bridge authorities now write bridge descriptors to disk, meaning
2738 we can export them to other programs and begin distributing them
2741 o Major features (directory authorities):
2742 - When a v3 authority is missing votes or signatures, it now tries
2744 - Directory authorities track weighted fractional uptime as well as
2745 weighted mean-time-between failures. WFU is suitable for deciding
2746 whether a node is "usually up", while MTBF is suitable for deciding
2747 whether a node is "likely to stay up." We need both, because
2748 "usually up" is a good requirement for guards, while "likely to
2749 stay up" is a good requirement for long-lived connections.
2751 o Major features (v3 directory system):
2752 - Caches now download v3 network status documents as needed,
2753 and download the descriptors listed in them.
2754 - All hosts now attempt to download and keep fresh v3 authority
2755 certificates, and re-attempt after failures.
2756 - More internal-consistency checks for vote parsing.
2758 o Major bugfixes (crashes):
2759 - If a connection is shut down abruptly because of something that
2760 happened inside connection_flushed_some(), do not call
2761 connection_finished_flushing(). Should fix bug 451. Bugfix on
2764 o Major bugfixes (performance):
2765 - Fix really bad O(n^2) performance when parsing a long list of
2766 routers: Instead of searching the entire list for an "extra-info "
2767 string which usually wasn't there, once for every routerinfo
2768 we read, just scan lines forward until we find one we like.
2770 - When we add data to a write buffer in response to the data on that
2771 write buffer getting low because of a flush, do not consider the
2772 newly added data as a candidate for immediate flushing, but rather
2773 make it wait until the next round of writing. Otherwise, we flush
2774 and refill recursively, and a single greedy TLS connection can
2775 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
2777 o Minor features (v3 authority system):
2778 - Add more ways for tools to download the votes that lead to the
2780 - Send a 503 when low on bandwidth and a vote, consensus, or
2781 certificate is requested.
2782 - If-modified-since is now implemented properly for all kinds of
2783 certificate requests.
2785 o Minor bugfixes (network statuses):
2786 - Tweak the implementation of proposal 109 slightly: allow at most
2787 two Tor servers on the same IP address, except if it's the location
2788 of a directory authority, in which case allow five. Bugfix on
2791 o Minor bugfixes (controller):
2792 - When sending a status event to the controller telling it that an
2793 OR address is reachable, set the port correctly. (Previously we
2794 were reporting the dir port.) Bugfix on 0.1.2.x.
2796 o Minor bugfixes (v3 directory system):
2797 - Fix logic to look up a cert by its signing key digest. Bugfix on
2799 - Only change the reply to a vote to "OK" if it's not already
2800 set. This gets rid of annoying "400 OK" log messages, which may
2801 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
2802 - When we get a valid consensus, recompute the voting schedule.
2803 - Base the valid-after time of a vote on the consensus voting
2804 schedule, not on our preferred schedule.
2805 - Make the return values and messages from signature uploads and
2806 downloads more sensible.
2807 - Fix a memory leak when serving votes and consensus documents, and
2808 another when serving certificates.
2810 o Minor bugfixes (performance):
2811 - Use a slightly simpler string hashing algorithm (copying Python's
2812 instead of Java's) and optimize our digest hashing algorithm to take
2813 advantage of 64-bit platforms and to remove some possibly-costly
2815 - Fix a minor memory leak whenever we parse guards from our state
2816 file. Bugfix on 0.2.0.7-alpha.
2817 - Fix a minor memory leak whenever we write out a file. Bugfix on
2819 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
2820 command. Bugfix on 0.2.0.5-alpha.
2822 o Minor bugfixes (portability):
2823 - On some platforms, accept() can return a broken address. Detect
2824 this more quietly, and deal accordingly. Fixes bug 483.
2825 - Stop calling tor_strlower() on uninitialized memory in some cases.
2826 Bugfix in 0.2.0.7-alpha.
2828 o Minor bugfixes (usability):
2829 - Treat some 403 responses from directory servers as INFO rather than
2830 WARN-severity events.
2831 - It's not actually an error to find a non-pending entry in the DNS
2832 cache when canceling a pending resolve. Don't log unless stuff is
2833 fishy. Resolves bug 463.
2835 o Minor bugfixes (anonymity):
2836 - Never report that we've used more bandwidth than we're willing to
2837 relay: it leaks how much non-relay traffic we're using. Resolves
2839 - When looking for a circuit to cannibalize, consider family as well
2840 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
2841 circuit cannibalization).
2843 o Code simplifications and refactoring:
2844 - Make a bunch of functions static. Remove some dead code.
2845 - Pull out about a third of the really big routerlist.c; put it in a
2846 new module, networkstatus.c.
2847 - Merge the extra fields in local_routerstatus_t back into
2848 routerstatus_t: we used to need one routerstatus_t for each
2849 authority's opinion, plus a local_routerstatus_t for the locally
2850 computed consensus opinion. To save space, we put the locally
2851 modified fields into local_routerstatus_t, and only the common
2852 stuff into routerstatus_t. But once v3 directories are in use,
2853 clients and caches will no longer need to hold authority opinions;
2854 thus, the rationale for keeping the types separate is now gone.
2855 - Make the code used to reschedule and reattempt downloads more
2857 - Turn all 'Are we a directory server/mirror?' logic into a call to
2859 - Remove the code to generate the oldest (v1) directory format.
2860 The code has been disabled since 0.2.0.5-alpha.
2863 Changes in version 0.2.0.7-alpha - 2007-09-21
2864 This seventh development snapshot makes bridges work again, makes bridge
2865 authorities work for the first time, fixes two huge performance flaws
2866 in hidden services, and fixes a variety of minor issues.
2868 o New directory authorities:
2869 - Set up moria1 and tor26 as the first v3 directory authorities. See
2870 doc/spec/dir-spec.txt for details on the new directory design.
2872 o Major bugfixes (crashes):
2873 - Fix possible segfaults in functions called from
2874 rend_process_relay_cell(). Bugfix on 0.1.2.x.
2876 o Major bugfixes (bridges):
2877 - Fix a bug that made servers send a "404 Not found" in response to
2878 attempts to fetch their server descriptor. This caused Tor servers
2879 to take many minutes to establish reachability for their DirPort,
2880 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
2881 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
2882 users configure that and specify a bridge with an identity
2883 fingerprint, now they will lookup the bridge descriptor at the
2884 default bridge authority via a one-hop tunnel, but once circuits
2885 are established they will switch to a three-hop tunnel for later
2886 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
2888 o Major bugfixes (hidden services):
2889 - Hidden services were choosing introduction points uniquely by
2890 hexdigest, but when constructing the hidden service descriptor
2891 they merely wrote the (potentially ambiguous) nickname.
2892 - Clients now use the v2 intro format for hidden service
2893 connections: they specify their chosen rendezvous point by identity
2894 digest rather than by (potentially ambiguous) nickname. Both
2895 are bugfixes on 0.1.2.x, and they could speed up hidden service
2896 connections dramatically. Thanks to Karsten Loesing.
2898 o Minor features (security):
2899 - As a client, do not believe any server that tells us that an
2900 address maps to an internal address space.
2901 - Make it possible to enable HashedControlPassword and
2902 CookieAuthentication at the same time.
2904 o Minor features (guard nodes):
2905 - Tag every guard node in our state file with the version that
2906 we believe added it, or with our own version if we add it. This way,
2907 if a user temporarily runs an old version of Tor and then switches
2908 back to a new one, she doesn't automatically lose her guards.
2910 o Minor features (speed):
2911 - When implementing AES counter mode, update only the portions of the
2912 counter buffer that need to change, and don't keep separate
2913 network-order and host-order counters when they are the same (i.e.,
2914 on big-endian hosts.)
2916 o Minor features (controller):
2917 - Accept LF instead of CRLF on controller, since some software has a
2918 hard time generating real Internet newlines.
2919 - Add GETINFO values for the server status events
2920 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
2924 - Routers no longer include bandwidth-history lines in their
2925 descriptors; this information is already available in extra-info
2926 documents, and including it in router descriptors took up 60%
2927 (!) of compressed router descriptor downloads. Completes
2928 implementation of proposal 104.
2929 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
2930 and TorControl.py, as they use the old v0 controller protocol,
2931 and are obsoleted by TorFlow anyway.
2932 - Drop support for v1 rendezvous descriptors, since we never used
2933 them anyway, and the code has probably rotted by now. Based on
2934 patch from Karsten Loesing.
2935 - On OSX, stop warning the user that kqueue support in libevent is
2936 "experimental", since it seems to have worked fine for ages.
2939 - When generating information telling us how to extend to a given
2940 router, do not try to include the nickname if it is absent. Fixes
2941 bug 467. Bugfix on 0.2.0.3-alpha.
2942 - Fix a user-triggerable (but not remotely-triggerable) segfault
2943 in expand_filename(). Bugfix on 0.1.2.x.
2944 - Fix a memory leak when freeing incomplete requests from DNSPort.
2945 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
2946 - Don't try to access (or alter) the state file when running
2947 --list-fingerprint or --verify-config or --hash-password. (Resolves
2948 bug 499.) Bugfix on 0.1.2.x.
2949 - Servers used to decline to publish their DirPort if their
2950 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
2951 were below a threshold. Now they only look at BandwidthRate and
2952 RelayBandwidthRate. Bugfix on 0.1.2.x.
2953 - Remove an optimization in the AES counter-mode code that assumed
2954 that the counter never exceeded 2^68. When the counter can be set
2955 arbitrarily as an IV (as it is by Karsten's new hidden services
2956 code), this assumption no longer holds. Bugfix on 0.1.2.x.
2957 - Resume listing "AUTHORITY" flag for authorities in network status.
2958 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
2960 o Code simplifications and refactoring:
2961 - Revamp file-writing logic so we don't need to have the entire
2962 contents of a file in memory at once before we write to disk. Tor,
2964 - Turn "descriptor store" into a full-fledged type.
2965 - Move all NT services code into a separate source file.
2966 - Unify all code that computes medians, percentile elements, etc.
2967 - Get rid of a needless malloc when parsing address policies.
2970 Changes in version 0.1.2.17 - 2007-08-30
2971 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
2972 X bundles. Vidalia 0.0.14 makes authentication required for the
2973 ControlPort in the default configuration, which addresses important
2974 security risks. Everybody who uses Vidalia (or another controller)
2977 In addition, this Tor update fixes major load balancing problems with
2978 path selection, which should speed things up a lot once many people
2981 o Major bugfixes (security):
2982 - We removed support for the old (v0) control protocol. It has been
2983 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
2984 become more of a headache than it's worth.
2986 o Major bugfixes (load balancing):
2987 - When choosing nodes for non-guard positions, weight guards
2988 proportionally less, since they already have enough load. Patch
2990 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
2991 will allow fast Tor servers to get more attention.
2992 - When we're upgrading from an old Tor version, forget our current
2993 guards and pick new ones according to the new weightings. These
2994 three load balancing patches could raise effective network capacity
2995 by a factor of four. Thanks to Mike Perry for measurements.
2997 o Major bugfixes (stream expiration):
2998 - Expire not-yet-successful application streams in all cases if
2999 they've been around longer than SocksTimeout. Right now there are
3000 some cases where the stream will live forever, demanding a new
3001 circuit every 15 seconds. Fixes bug 454; reported by lodger.
3003 o Minor features (controller):
3004 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
3005 is valid before any authentication has been received. It tells
3006 a controller what kind of authentication is expected, and what
3007 protocol is spoken. Implements proposal 119.
3009 o Minor bugfixes (performance):
3010 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
3011 greatly speeding up loading cached-routers from disk on startup.
3012 - Disable sentinel-based debugging for buffer code: we squashed all
3013 the bugs that this was supposed to detect a long time ago, and now
3014 its only effect is to change our buffer sizes from nice powers of
3015 two (which platform mallocs tend to like) to values slightly over
3016 powers of two (which make some platform mallocs sad).
3018 o Minor bugfixes (misc):
3019 - If exit bandwidth ever exceeds one third of total bandwidth, then
3020 use the correct formula to weight exit nodes when choosing paths.
3021 Based on patch from Mike Perry.
3022 - Choose perfectly fairly among routers when choosing by bandwidth and
3023 weighting by fraction of bandwidth provided by exits. Previously, we
3024 would choose with only approximate fairness, and correct ourselves
3025 if we ran off the end of the list.
3026 - If we require CookieAuthentication but we fail to write the
3027 cookie file, we would warn but not exit, and end up in a state
3028 where no controller could authenticate. Now we exit.
3029 - If we require CookieAuthentication, stop generating a new cookie
3030 every time we change any piece of our config.
3031 - Refuse to start with certain directory authority keys, and
3032 encourage people using them to stop.
3033 - Terminate multi-line control events properly. Original patch
3035 - Fix a minor memory leak when we fail to find enough suitable
3036 servers to choose a circuit.
3037 - Stop leaking part of the descriptor when we run into a particularly
3038 unparseable piece of it.
3041 Changes in version 0.2.0.6-alpha - 2007-08-26
3042 This sixth development snapshot features a new Vidalia version in the
3043 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
3044 the ControlPort in the default configuration, which addresses important
3047 In addition, this snapshot fixes major load balancing problems
3048 with path selection, which should speed things up a lot once many
3049 people have upgraded. The directory authorities also use a new
3050 mean-time-between-failure approach to tracking which servers are stable,
3051 rather than just looking at the most recent uptime.
3053 o New directory authorities:
3054 - Set up Tonga as the default bridge directory authority.
3057 - Directory authorities now track servers by weighted
3058 mean-times-between-failures. When we have 4 or more days of data,
3059 use measured MTBF rather than declared uptime to decide whether
3060 to call a router Stable. Implements proposal 108.
3062 o Major bugfixes (load balancing):
3063 - When choosing nodes for non-guard positions, weight guards
3064 proportionally less, since they already have enough load. Patch
3066 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
3067 will allow fast Tor servers to get more attention.
3068 - When we're upgrading from an old Tor version, forget our current
3069 guards and pick new ones according to the new weightings. These
3070 three load balancing patches could raise effective network capacity
3071 by a factor of four. Thanks to Mike Perry for measurements.
3073 o Major bugfixes (descriptor parsing):
3074 - Handle unexpected whitespace better in malformed descriptors. Bug
3075 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
3078 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
3079 GETINFO for Torstat to use until it can switch to using extrainfos.
3080 - Optionally (if built with -DEXPORTMALLINFO) export the output
3081 of mallinfo via http, as tor/mallinfo.txt. Only accessible
3085 - Do not intermix bridge routers with controller-added
3086 routers. (Bugfix on 0.2.0.x)
3087 - Do not fail with an assert when accept() returns an unexpected
3088 address family. Addresses but does not wholly fix bug 483. (Bugfix
3090 - Let directory authorities startup even when they can't generate
3091 a descriptor immediately, e.g. because they don't know their
3093 - Stop putting the authentication cookie in a file called "0"
3094 in your working directory if you don't specify anything for the
3095 new CookieAuthFile option. Reported by Matt Edman.
3096 - Make it possible to read the PROTOCOLINFO response in a way that
3097 conforms to our control-spec. Reported by Matt Edman.
3098 - Fix a minor memory leak when we fail to find enough suitable
3099 servers to choose a circuit. Bugfix on 0.1.2.x.
3100 - Stop leaking part of the descriptor when we run into a particularly
3101 unparseable piece of it. Bugfix on 0.1.2.x.
3102 - Unmap the extrainfo cache file on exit.
3105 Changes in version 0.2.0.5-alpha - 2007-08-19
3106 This fifth development snapshot fixes compilation on Windows again;
3107 fixes an obnoxious client-side bug that slowed things down and put
3108 extra load on the network; gets us closer to using the v3 directory
3109 voting scheme; makes it easier for Tor controllers to use cookie-based
3110 authentication; and fixes a variety of other bugs.
3113 - Version 1 directories are no longer generated in full. Instead,
3114 authorities generate and serve "stub" v1 directories that list
3115 no servers. This will stop Tor versions 0.1.0.x and earlier from
3116 working, but (for security reasons) nobody should be running those
3119 o Major bugfixes (compilation, 0.2.0.x):
3120 - Try to fix Win32 compilation again: improve checking for IPv6 types.
3121 - Try to fix MSVC compilation: build correctly on platforms that do
3122 not define s6_addr16 or s6_addr32.
3123 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
3126 o Major bugfixes (stream expiration):
3127 - Expire not-yet-successful application streams in all cases if
3128 they've been around longer than SocksTimeout. Right now there are
3129 some cases where the stream will live forever, demanding a new
3130 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
3133 o Minor features (directory servers):
3134 - When somebody requests a list of statuses or servers, and we have
3135 none of those, return a 404 rather than an empty 200.
3137 o Minor features (directory voting):
3138 - Store v3 consensus status consensuses on disk, and reload them
3141 o Minor features (security):
3142 - Warn about unsafe ControlPort configurations.
3143 - Refuse to start with certain directory authority keys, and
3144 encourage people using them to stop.
3146 o Minor features (controller):
3147 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
3148 is valid before any authentication has been received. It tells
3149 a controller what kind of authentication is expected, and what
3150 protocol is spoken. Implements proposal 119.
3151 - New config option CookieAuthFile to choose a new location for the
3152 cookie authentication file, and config option
3153 CookieAuthFileGroupReadable to make it group-readable.
3155 o Minor features (unit testing):
3156 - Add command-line arguments to unit-test executable so that we can
3157 invoke any chosen test from the command line rather than having
3158 to run the whole test suite at once; and so that we can turn on
3159 logging for the unit tests.
3161 o Minor bugfixes (on 0.1.2.x):
3162 - If we require CookieAuthentication but we fail to write the
3163 cookie file, we would warn but not exit, and end up in a state
3164 where no controller could authenticate. Now we exit.
3165 - If we require CookieAuthentication, stop generating a new cookie
3166 every time we change any piece of our config.
3167 - When loading bandwidth history, do not believe any information in
3168 the future. Fixes bug 434.
3169 - When loading entry guard information, do not believe any information
3171 - When we have our clock set far in the future and generate an
3172 onion key, then re-set our clock to be correct, we should not stop
3173 the onion key from getting rotated.
3174 - Clean up torrc sample config file.
3175 - Do not automatically run configure from autogen.sh. This
3176 non-standard behavior tended to annoy people who have built other
3179 o Minor bugfixes (on 0.2.0.x):
3180 - Fix a bug with AutomapHostsOnResolve that would always cause
3181 the second request to fail. Bug reported by Kate. Bugfix on
3183 - Fix a bug in ADDRMAP controller replies that would sometimes
3184 try to print a NULL. Patch from tup.
3185 - Read v3 directory authority keys from the right location.
3186 - Numerous bugfixes to directory voting code.
3189 Changes in version 0.1.2.16 - 2007-08-01
3190 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
3191 remote attacker in certain situations to rewrite the user's torrc
3192 configuration file. This can completely compromise anonymity of users
3193 in most configurations, including those running the Vidalia bundles,
3194 TorK, etc. Or worse.
3196 o Major security fixes:
3197 - Close immediately after missing authentication on control port;
3198 do not allow multiple authentication attempts.
3201 Changes in version 0.2.0.4-alpha - 2007-08-01
3202 This fourth development snapshot fixes a critical security vulnerability
3203 for most users, specifically those running Vidalia, TorK, etc. Everybody
3204 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
3206 o Major security fixes:
3207 - Close immediately after missing authentication on control port;
3208 do not allow multiple authentication attempts.
3210 o Major bugfixes (compilation):
3211 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
3214 o Minor features (performance):
3215 - Be even more aggressive about releasing RAM from small
3216 empty buffers. Thanks to our free-list code, this shouldn't be too
3217 performance-intensive.
3218 - Disable sentinel-based debugging for buffer code: we squashed all
3219 the bugs that this was supposed to detect a long time ago, and
3220 now its only effect is to change our buffer sizes from nice
3221 powers of two (which platform mallocs tend to like) to values
3222 slightly over powers of two (which make some platform mallocs sad).
3223 - Log malloc statistics from mallinfo() on platforms where it
3227 Changes in version 0.2.0.3-alpha - 2007-07-29
3228 This third development snapshot introduces new experimental
3229 blocking-resistance features and a preliminary version of the v3
3230 directory voting design, and includes many other smaller features
3234 - The first pieces of our "bridge" design for blocking-resistance
3235 are implemented. People can run bridge directory authorities;
3236 people can run bridges; and people can configure their Tor clients
3237 with a set of bridges to use as the first hop into the Tor network.
3238 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
3240 - Create listener connections before we setuid to the configured
3241 User and Group. Now non-Windows users can choose port values
3242 under 1024, start Tor as root, and have Tor bind those ports
3243 before it changes to another UID. (Windows users could already
3245 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
3246 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
3247 on "vserver" accounts. (Patch from coderman.)
3248 - Be even more aggressive about separating local traffic from relayed
3249 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
3251 o Major features (experimental):
3252 - First cut of code for "v3 dir voting": directory authorities will
3253 vote on a common network status document rather than each publishing
3254 their own opinion. This code needs more testing and more corner-case
3255 handling before it's ready for use.
3258 - Directory authorities now call routers Fast if their bandwidth is
3259 at least 100KB/s, and consider their bandwidth adequate to be a
3260 Guard if it is at least 250KB/s, no matter the medians. This fix
3261 complements proposal 107. [Bugfix on 0.1.2.x]
3262 - Directory authorities now never mark more than 3 servers per IP as
3263 Valid and Running. (Implements proposal 109, by Kevin Bauer and
3265 - Minor change to organizationName and commonName generation
3266 procedures in TLS certificates during Tor handshakes, to invalidate
3267 some earlier censorware approaches. This is not a long-term
3268 solution, but applying it will give us a bit of time to look into
3269 the epidemiology of countermeasures as they spread.
3271 o Major bugfixes (directory):
3272 - Rewrite directory tokenization code to never run off the end of
3273 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
3275 o Minor features (controller):
3276 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
3277 match requests to applications. (Patch from Robert Hogan.)
3278 - Report address and port correctly on connections to DNSPort. (Patch
3280 - Add a RESOLVE command to launch hostname lookups. (Original patch
3282 - Add GETINFO status/enough-dir-info to let controllers tell whether
3283 Tor has downloaded sufficient directory information. (Patch
3285 - You can now use the ControlSocket option to tell Tor to listen for
3286 controller connections on Unix domain sockets on systems that
3287 support them. (Patch from Peter Palfrader.)
3288 - STREAM NEW events are generated for DNSPort requests and for
3289 tunneled directory connections. (Patch from Robert Hogan.)
3290 - New "GETINFO address-mappings/*" command to get address mappings
3291 with expiry information. "addr-mappings/*" is now deprecated.
3294 o Minor features (misc):
3295 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
3297 - The tor-gencert tool for v3 directory authorities now creates all
3298 files as readable to the file creator only, and write-protects
3299 the authority identity key.
3300 - When dumping memory usage, list bytes used in buffer memory
3302 - When running with dmalloc, dump more stats on hup and on exit.
3303 - Directory authorities now fail quickly and (relatively) harmlessly
3304 if they generate a network status document that is somehow
3307 o Traffic load balancing improvements:
3308 - If exit bandwidth ever exceeds one third of total bandwidth, then
3309 use the correct formula to weight exit nodes when choosing paths.
3310 (Based on patch from Mike Perry.)
3311 - Choose perfectly fairly among routers when choosing by bandwidth and
3312 weighting by fraction of bandwidth provided by exits. Previously, we
3313 would choose with only approximate fairness, and correct ourselves
3314 if we ran off the end of the list. [Bugfix on 0.1.2.x]
3316 o Performance improvements:
3317 - Be more aggressive with freeing buffer RAM or putting it on the
3319 - Use Critical Sections rather than Mutexes for synchronizing threads
3320 on win32; Mutexes are heavier-weight, and designed for synchronizing
3323 o Deprecated and removed features:
3324 - RedirectExits is now deprecated.
3325 - Stop allowing address masks that do not correspond to bit prefixes.
3326 We have warned about these for a really long time; now it's time
3327 to reject them. (Patch from croup.)
3329 o Minor bugfixes (directory):
3330 - Fix another crash bug related to extra-info caching. (Bug found by
3331 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
3332 - Directories no longer return a "304 not modified" when they don't
3333 have the networkstatus the client asked for. Also fix a memory
3334 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
3335 - We had accidentally labelled 0.1.2.x directory servers as not
3336 suitable for begin_dir requests, and had labelled no directory
3337 servers as suitable for uploading extra-info documents. [Bugfix
3340 o Minor bugfixes (dns):
3341 - Fix a crash when DNSPort is set more than once. (Patch from Robert
3342 Hogan.) [Bugfix on 0.2.0.2-alpha]
3343 - Add DNSPort connections to the global connection list, so that we
3344 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
3346 - Fix a dangling reference that could lead to a crash when DNSPort is
3347 changed or closed (Patch from Robert Hogan.) [Bugfix on
3350 o Minor bugfixes (controller):
3351 - Provide DNS expiry times in GMT, not in local time. For backward
3352 compatibility, ADDRMAP events only provide GMT expiry in an extended
3353 field. "GETINFO address-mappings" always does the right thing.
3354 - Use CRLF line endings properly in NS events.
3355 - Terminate multi-line control events properly. (Original patch
3356 from tup.) [Bugfix on 0.1.2.x-alpha]
3357 - Do not include spaces in SOURCE_ADDR fields in STREAM
3358 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
3361 Changes in version 0.1.2.15 - 2007-07-17
3362 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
3363 problems, fixes compilation on BSD, and fixes a variety of other
3364 bugs. Everybody should upgrade.
3366 o Major bugfixes (compilation):
3367 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
3369 o Major bugfixes (crashes):
3370 - Try even harder not to dereference the first character after
3371 an mmap(). Reported by lodger.
3372 - Fix a crash bug in directory authorities when we re-number the
3373 routerlist while inserting a new router.
3374 - When the cached-routers file is an even multiple of the page size,
3375 don't run off the end and crash. (Fixes bug 455; based on idea
3377 - Fix eventdns.c behavior on Solaris: It is critical to include
3378 orconfig.h _before_ sys/types.h, so that we can get the expected
3379 definition of _FILE_OFFSET_BITS.
3381 o Major bugfixes (security):
3382 - Fix a possible buffer overrun when using BSD natd support. Bug
3384 - When sending destroy cells from a circuit's origin, don't include
3385 the reason for tearing down the circuit. The spec says we didn't,
3386 and now we actually don't. Reported by lodger.
3387 - Keep streamids from different exits on a circuit separate. This
3388 bug may have allowed other routers on a given circuit to inject
3389 cells into streams. Reported by lodger; fixes bug 446.
3390 - If there's a never-before-connected-to guard node in our list,
3391 never choose any guards past it. This way we don't expand our
3392 guard list unless we need to.
3394 o Minor bugfixes (guard nodes):
3395 - Weight guard selection by bandwidth, so that low-bandwidth nodes
3396 don't get overused as guards.
3398 o Minor bugfixes (directory):
3399 - Correctly count the number of authorities that recommend each
3400 version. Previously, we were under-counting by 1.
3401 - Fix a potential crash bug when we load many server descriptors at
3402 once and some of them make others of them obsolete. Fixes bug 458.
3404 o Minor bugfixes (hidden services):
3405 - Stop tearing down the whole circuit when the user asks for a
3406 connection to a port that the hidden service didn't configure.
3409 o Minor bugfixes (misc):
3410 - On Windows, we were preventing other processes from reading
3411 cached-routers while Tor was running. Reported by janbar.
3412 - Fix a possible (but very unlikely) bug in picking routers by
3413 bandwidth. Add a log message to confirm that it is in fact
3414 unlikely. Patch from lodger.
3415 - Backport a couple of memory leak fixes.
3416 - Backport miscellaneous cosmetic bugfixes.
3419 Changes in version 0.2.0.2-alpha - 2007-06-02
3420 o Major bugfixes on 0.2.0.1-alpha:
3421 - Fix an assertion failure related to servers without extra-info digests.
3422 Resolves bugs 441 and 442.
3424 o Minor features (directory):
3425 - Support "If-Modified-Since" when answering HTTP requests for
3426 directories, running-routers documents, and network-status documents.
3427 (There's no need to support it for router descriptors, since those
3428 are downloaded by descriptor digest.)
3430 o Minor build issues:
3431 - Clear up some MIPSPro compiler warnings.
3432 - When building from a tarball on a machine that happens to have SVK
3433 installed, report the micro-revision as whatever version existed
3434 in the tarball, not as "x".
3437 Changes in version 0.2.0.1-alpha - 2007-06-01
3438 This early development snapshot provides new features for people running
3439 Tor as both a client and a server (check out the new RelayBandwidth
3440 config options); lets Tor run as a DNS proxy; and generally moves us
3441 forward on a lot of fronts.
3443 o Major features, server usability:
3444 - New config options RelayBandwidthRate and RelayBandwidthBurst:
3445 a separate set of token buckets for relayed traffic. Right now
3446 relayed traffic is defined as answers to directory requests, and
3447 OR connections that don't have any local circuits on them.
3449 o Major features, client usability:
3450 - A client-side DNS proxy feature to replace the need for
3451 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
3452 for DNS requests on port 9999, use the Tor network to resolve them
3453 anonymously, and send the reply back like a regular DNS server.
3454 The code still only implements a subset of DNS.
3455 - Make PreferTunneledDirConns and TunnelDirConns work even when
3456 we have no cached directory info. This means Tor clients can now
3457 do all of their connections protected by TLS.
3459 o Major features, performance and efficiency:
3460 - Directory authorities accept and serve "extra info" documents for
3461 routers. These documents contain fields from router descriptors
3462 that aren't usually needed, and that use a lot of excess
3463 bandwidth. Once these fields are removed from router descriptors,
3464 the bandwidth savings should be about 60%. [Partially implements
3466 - Servers upload extra-info documents to any authority that accepts
3467 them. Authorities (and caches that have been configured to download
3468 extra-info documents) download them as needed. [Partially implements
3470 - Change the way that Tor buffers data that it is waiting to write.
3471 Instead of queueing data cells in an enormous ring buffer for each
3472 client->OR or OR->OR connection, we now queue cells on a separate
3473 queue for each circuit. This lets us use less slack memory, and
3474 will eventually let us be smarter about prioritizing different kinds
3476 - Use memory pools to allocate cells with better speed and memory
3477 efficiency, especially on platforms where malloc() is inefficient.
3478 - Stop reading on edge connections when their corresponding circuit
3479 buffers are full; start again as the circuits empty out.
3481 o Major features, other:
3482 - Add an HSAuthorityRecordStats option that hidden service authorities
3483 can use to track statistics of overall hidden service usage without
3484 logging information that would be very useful to an attacker.
3485 - Start work implementing multi-level keys for directory authorities:
3486 Add a standalone tool to generate key certificates. (Proposal 103.)
3489 - Directory authorities now call routers Stable if they have an
3490 uptime of at least 30 days, even if that's not the median uptime
3491 in the network. Implements proposal 107, suggested by Kevin Bauer
3494 o Minor fixes (resource management):
3495 - Count the number of open sockets separately from the number
3496 of active connection_t objects. This will let us avoid underusing
3497 our allocated connection limit.
3498 - We no longer use socket pairs to link an edge connection to an
3499 anonymous directory connection or a DirPort test connection.
3500 Instead, we track the link internally and transfer the data
3501 in-process. This saves two sockets per "linked" connection (at the
3502 client and at the server), and avoids the nasty Windows socketpair()
3504 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
3505 for every single inactive connection_t. Free items from the
3506 4k/16k-buffer free lists when they haven't been used for a while.
3508 o Minor features (build):
3509 - Make autoconf search for libevent, openssl, and zlib consistently.
3510 - Update deprecated macros in configure.in.
3511 - When warning about missing headers, tell the user to let us
3512 know if the compile succeeds anyway, so we can downgrade the
3514 - Include the current subversion revision as part of the version
3515 string: either fetch it directly if we're in an SVN checkout, do
3516 some magic to guess it if we're in an SVK checkout, or use
3517 the last-detected version if we're building from a .tar.gz.
3518 Use this version consistently in log messages.
3520 o Minor features (logging):
3521 - Always prepend "Bug: " to any log message about a bug.
3522 - Put a platform string (e.g. "Linux i686") in the startup log
3523 message, so when people paste just their logs, we know if it's
3524 OpenBSD or Windows or what.
3525 - When logging memory usage, break down memory used in buffers by
3528 o Minor features (directory system):
3529 - New config option V2AuthoritativeDirectory that all directory
3530 authorities should set. This will let future authorities choose
3531 not to serve V2 directory information.
3532 - Directory authorities allow multiple router descriptors and/or extra
3533 info documents to be uploaded in a single go. This will make
3534 implementing proposal 104 simpler.
3536 o Minor features (controller):
3537 - Add a new config option __DisablePredictedCircuits designed for
3538 use by the controller, when we don't want Tor to build any circuits
3540 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
3541 so we can exit from the middle of the circuit.
3542 - Implement "getinfo status/circuit-established".
3543 - Implement "getinfo status/version/..." so a controller can tell
3544 whether the current version is recommended, and whether any versions
3545 are good, and how many authorities agree. (Patch from shibz.)
3547 o Minor features (hidden services):
3548 - Allow multiple HiddenServicePort directives with the same virtual
3549 port; when they occur, the user is sent round-robin to one
3550 of the target ports chosen at random. Partially fixes bug 393 by
3551 adding limited ad-hoc round-robining.
3553 o Minor features (other):
3555 - Add a new AutomapHostsOnResolve option: when it is enabled, any
3556 resolve request for hosts matching a given pattern causes Tor to
3557 generate an internal virtual address mapping for that host. This
3558 allows DNSPort to work sensibly with hidden service users. By
3559 default, .exit and .onion addresses are remapped; the list of
3560 patterns can be reconfigured with AutomapHostsSuffixes.
3561 - Add an "-F" option to tor-resolve to force a resolve for a .onion
3562 address. Thanks to the AutomapHostsOnResolve option, this is no
3563 longer a completely silly thing to do.
3564 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
3565 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
3566 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
3567 minus 1 byte: the actual maximum declared bandwidth.
3570 - Removed support for the old binary "version 0" controller protocol.
3571 This has been deprecated since 0.1.1, and warnings have been issued
3572 since 0.1.2. When we encounter a v0 control message, we now send
3573 back an error and close the connection.
3574 - Remove the old "dns worker" server DNS code: it hasn't been default
3575 since 0.1.2.2-alpha, and all the servers seem to be using the new
3578 o Minor bugfixes (portability):
3579 - Even though Windows is equally happy with / and \ as path separators,
3580 try to use \ consistently on Windows and / consistently on Unix: it
3581 makes the log messages nicer.
3582 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
3583 - Read resolv.conf files correctly on platforms where read() returns
3584 partial results on small file reads.
3586 o Minor bugfixes (directory):
3587 - Correctly enforce that elements of directory objects do not appear
3588 more often than they are allowed to appear.
3589 - When we are reporting the DirServer line we just parsed, we were
3590 logging the second stanza of the key fingerprint, not the first.
3592 o Minor bugfixes (logging):
3593 - When we hit an EOF on a log (probably because we're shutting down),
3594 don't try to remove the log from the list: just mark it as
3595 unusable. (Bulletproofs against bug 222.)
3597 o Minor bugfixes (other):
3598 - In the exitlist script, only consider the most recently published
3599 server descriptor for each server. Also, when the user requests
3600 a list of servers that _reject_ connections to a given address,
3601 explicitly exclude the IPs that also have servers that accept
3602 connections to that address. (Resolves bug 405.)
3603 - Stop allowing hibernating servers to be "stable" or "fast".
3604 - On Windows, we were preventing other processes from reading
3605 cached-routers while Tor was running. (Reported by janbar)
3606 - Make the NodeFamilies config option work. (Reported by
3607 lodger -- it has never actually worked, even though we added it
3609 - Check return values from pthread_mutex functions.
3610 - Don't save non-general-purpose router descriptors to the disk cache,
3611 because we have no way of remembering what their purpose was when
3613 - Add even more asserts to hunt down bug 417.
3614 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
3615 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
3616 Add a log message to confirm that it is in fact unlikely.
3618 o Minor bugfixes (controller):
3619 - Make 'getinfo fingerprint' return a 551 error if we're not a
3620 server, so we match what the control spec claims we do. Reported
3622 - Fix a typo in an error message when extendcircuit fails that
3623 caused us to not follow the \r\n-based delimiter protocol. Reported
3626 o Code simplifications and refactoring:
3627 - Stop passing around circuit_t and crypt_path_t pointers that are
3628 implicit in other procedure arguments.
3629 - Drop the old code to choke directory connections when the
3630 corresponding OR connections got full: thanks to the cell queue
3631 feature, OR conns don't get full any more.
3632 - Make dns_resolve() handle attaching connections to circuits
3633 properly, so the caller doesn't have to.
3634 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
3635 - Keep the connection array as a dynamic smartlist_t, rather than as
3636 a fixed-sized array. This is important, as the number of connections
3637 is becoming increasingly decoupled from the number of sockets.
3640 Changes in version 0.1.2.14 - 2007-05-25
3641 Tor 0.1.2.14 changes the addresses of two directory authorities (this
3642 change especially affects those who serve or use hidden services),
3643 and fixes several other crash- and security-related bugs.
3645 o Directory authority changes:
3646 - Two directory authorities (moria1 and moria2) just moved to new
3647 IP addresses. This change will particularly affect those who serve
3648 or use hidden services.
3650 o Major bugfixes (crashes):
3651 - If a directory server runs out of space in the connection table
3652 as it's processing a begin_dir request, it will free the exit stream
3653 but leave it attached to the circuit, leading to unpredictable
3654 behavior. (Reported by seeess, fixes bug 425.)
3655 - Fix a bug in dirserv_remove_invalid() that would cause authorities
3656 to corrupt memory under some really unlikely scenarios.
3657 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
3658 - Avoid segfaults when reading from mmaped descriptor file. (Reported
3661 o Major bugfixes (security):
3662 - When choosing an entry guard for a circuit, avoid using guards
3663 that are in the same family as the chosen exit -- not just guards
3664 that are exactly the chosen exit. (Reported by lodger.)
3666 o Major bugfixes (resource management):
3667 - If a directory authority is down, skip it when deciding where to get
3668 networkstatus objects or descriptors. Otherwise we keep asking
3669 every 10 seconds forever. Fixes bug 384.
3670 - Count it as a failure if we fetch a valid network-status but we
3671 don't want to keep it. Otherwise we'll keep fetching it and keep
3672 not wanting to keep it. Fixes part of bug 422.
3673 - If all of our dirservers have given us bad or no networkstatuses
3674 lately, then stop hammering them once per minute even when we
3675 think they're failed. Fixes another part of bug 422.
3678 - Actually set the purpose correctly for descriptors inserted with
3680 - When we have k non-v2 authorities in our DirServer config,
3681 we ignored the last k authorities in the list when updating our
3683 - Correctly back-off from requesting router descriptors that we are
3684 having a hard time downloading.
3685 - Read resolv.conf files correctly on platforms where read() returns
3686 partial results on small file reads.
3687 - Don't rebuild the entire router store every time we get 32K of
3688 routers: rebuild it when the journal gets very large, or when
3689 the gaps in the store get very large.
3692 - When routers publish SVN revisions in their router descriptors,
3693 authorities now include those versions correctly in networkstatus
3695 - Warn when using a version of libevent before 1.3b to run a server on
3696 OSX or BSD: these versions interact badly with userspace threads.
3699 Changes in version 0.1.2.13 - 2007-04-24
3700 This release features some major anonymity fixes, such as safer path
3701 selection; better client performance; faster bootstrapping, better
3702 address detection, and better DNS support for servers; write limiting as
3703 well as read limiting to make servers easier to run; and a huge pile of
3704 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
3706 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
3707 of the Freenode IRC network, remembering his patience and vision for
3708 free speech on the Internet.
3711 - Fix a memory leak when we ask for "all" networkstatuses and we
3712 get one we don't recognize.
3713 - Add more asserts to hunt down bug 417.
3714 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
3717 Changes in version 0.1.2.12-rc - 2007-03-16
3719 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
3720 directory information requested inside Tor connections (i.e. via
3721 begin_dir cells). It only triggered when the same connection was
3722 serving other data at the same time. Reported by seeess.
3725 - When creating a circuit via the controller, send a 'launched'
3726 event when we're done, so we follow the spec better.
3729 Changes in version 0.1.2.11-rc - 2007-03-15
3730 o Minor bugfixes (controller), reported by daejees:
3731 - Correct the control spec to match how the code actually responds
3732 to 'getinfo addr-mappings/*'.
3733 - The control spec described a GUARDS event, but the code
3734 implemented a GUARD event. Standardize on GUARD, but let people
3738 Changes in version 0.1.2.10-rc - 2007-03-07
3739 o Major bugfixes (Windows):
3740 - Do not load the NT services library functions (which may not exist)
3741 just to detect if we're a service trying to shut down. Now we run
3742 on Win98 and friends again.
3744 o Minor bugfixes (other):
3745 - Clarify a couple of log messages.
3746 - Fix a misleading socks5 error number.
3749 Changes in version 0.1.2.9-rc - 2007-03-02
3750 o Major bugfixes (Windows):
3751 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
3752 of the usual GCC "%llu". This prevents a bug when saving 64-bit
3753 int configuration values: the high-order 32 bits would get
3754 truncated. In particular, we were being bitten by the default
3755 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
3756 and maybe also bug 397.)
3758 o Minor bugfixes (performance):
3759 - Use OpenSSL's AES implementation on platforms where it's faster.
3760 This could save us as much as 10% CPU usage.
3762 o Minor bugfixes (server):
3763 - Do not rotate onion key immediately after setting it for the first
3766 o Minor bugfixes (directory authorities):
3767 - Stop calling servers that have been hibernating for a long time
3768 "stable". Also, stop letting hibernating or obsolete servers affect
3769 uptime and bandwidth cutoffs.
3770 - Stop listing hibernating servers in the v1 directory.
3772 o Minor bugfixes (hidden services):
3773 - Upload hidden service descriptors slightly less often, to reduce
3774 load on authorities.
3776 o Minor bugfixes (other):
3777 - Fix an assert that could trigger if a controller quickly set then
3778 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
3779 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
3781 - Fix a potential race condition in the rpm installer. Found by
3783 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
3784 of 2 as indicating that the server is completely bad; it sometimes
3785 means that the server is just bad for the request in question. (may fix
3786 the last of bug 326.)
3787 - Disable encrypted directory connections when we don't have a server
3788 descriptor for the destination. We'll get this working again in
3792 Changes in version 0.1.2.8-beta - 2007-02-26
3793 o Major bugfixes (crashes):
3794 - Stop crashing when the controller asks us to resetconf more than
3795 one config option at once. (Vidalia 0.0.11 does this.)
3796 - Fix a crash that happened on Win98 when we're given command-line
3797 arguments: don't try to load NT service functions from advapi32.dll
3798 except when we need them. (Bug introduced in 0.1.2.7-alpha;
3800 - Fix a longstanding obscure crash bug that could occur when
3801 we run out of DNS worker processes. (Resolves bug 390.)
3803 o Major bugfixes (hidden services):
3804 - Correctly detect whether hidden service descriptor downloads are
3805 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
3807 o Major bugfixes (accounting):
3808 - When we start during an accounting interval before it's time to wake
3809 up, remember to wake up at the correct time. (May fix bug 342.)
3811 o Minor bugfixes (controller):
3812 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
3813 clear the corresponding on_circuit variable, and remember later
3814 that we don't need to send a redundant CLOSED event. (Resolves part
3816 - Report events where a resolve succeeded or where we got a socks
3817 protocol error correctly, rather than calling both of them
3819 - Change reported stream target addresses to IP consistently when
3820 we finally get the IP from an exit node.
3821 - Send log messages to the controller even if they happen to be very
3824 o Minor bugfixes (other):
3825 - Display correct results when reporting which versions are
3826 recommended, and how recommended they are. (Resolves bug 383.)
3827 - Improve our estimates for directory bandwidth to be less random:
3828 guess that an unrecognized directory will have the average bandwidth
3829 from all known directories, not that it will have the average
3830 bandwidth from those directories earlier than it on the list.
3831 - If we start a server with ClientOnly 1, then set ClientOnly to 0
3832 and hup, stop triggering an assert based on an empty onion_key.
3833 - On platforms with no working mmap() equivalent, don't warn the
3834 user when cached-routers doesn't exist.
3835 - Warn the user when mmap() [or its equivalent] fails for some reason
3836 other than file-not-found.
3837 - Don't warn the user when cached-routers.new doesn't exist: that's
3838 perfectly fine when starting up for the first time.
3839 - When EntryNodes are configured, rebuild the guard list to contain,
3840 in order: the EntryNodes that were guards before; the rest of the
3841 EntryNodes; the nodes that were guards before.
3842 - Mask out all signals in sub-threads; only the libevent signal
3843 handler should be processing them. This should prevent some crashes
3844 on some machines using pthreads. (Patch from coderman.)
3845 - Fix switched arguments on memset in the implementation of
3846 tor_munmap() for systems with no mmap() call.
3847 - When Tor receives a router descriptor that it asked for, but
3848 no longer wants (because it has received fresh networkstatuses
3849 in the meantime), do not warn the user. Cache the descriptor if
3850 we're a cache; drop it if we aren't.
3851 - Make earlier entry guards _really_ get retried when the network
3853 - On a malformed DNS reply, always give an error to the corresponding
3855 - Build with recent libevents on platforms that do not define the
3856 nonstandard types "u_int8_t" and friends.
3858 o Minor features (controller):
3859 - Warn the user when an application uses the obsolete binary v0
3860 control protocol. We're planning to remove support for it during
3861 the next development series, so it's good to give people some
3863 - Add STREAM_BW events to report per-entry-stream bandwidth
3864 use. (Patch from Robert Hogan.)
3865 - Rate-limit SIGNEWNYM signals in response to controllers that
3866 impolitely generate them for every single stream. (Patch from
3867 mwenge; closes bug 394.)
3868 - Make REMAP stream events have a SOURCE (cache or exit), and
3869 make them generated in every case where we get a successful
3870 connected or resolved cell.
3872 o Minor bugfixes (performance):
3873 - Call router_have_min_dir_info half as often. (This is showing up in
3874 some profiles, but not others.)
3875 - When using GCC, make log_debug never get called at all, and its
3876 arguments never get evaluated, when no debug logs are configured.
3877 (This is showing up in some profiles, but not others.)
3880 - Remove some never-implemented options. Mark PathlenCoinWeight as
3882 - Implement proposal 106: Stop requiring clients to have well-formed
3883 certificates; stop checking nicknames in certificates. (Clients
3884 have certificates so that they can look like Tor servers, but in
3885 the future we might want to allow them to look like regular TLS
3886 clients instead. Nicknames in certificates serve no purpose other
3887 than making our protocol easier to recognize on the wire.)
3888 - Revise messages on handshake failure again to be even more clear about
3889 which are incoming connections and which are outgoing.
3890 - Discard any v1 directory info that's over 1 month old (for
3891 directories) or over 1 week old (for running-routers lists).
3892 - Do not warn when individual nodes in the configuration's EntryNodes,
3893 ExitNodes, etc are down: warn only when all possible nodes
3894 are down. (Fixes bug 348.)
3895 - Always remove expired routers and networkstatus docs before checking
3896 whether we have enough information to build circuits. (Fixes
3898 - Put a lower-bound on MaxAdvertisedBandwidth.
3901 Changes in version 0.1.2.7-alpha - 2007-02-06
3902 o Major bugfixes (rate limiting):
3903 - Servers decline directory requests much more aggressively when
3904 they're low on bandwidth. Otherwise they end up queueing more and
3905 more directory responses, which can't be good for latency.
3906 - But never refuse directory requests from local addresses.
3907 - Fix a memory leak when sending a 503 response for a networkstatus
3909 - Be willing to read or write on local connections (e.g. controller
3910 connections) even when the global rate limiting buckets are empty.
3911 - If our system clock jumps back in time, don't publish a negative
3912 uptime in the descriptor. Also, don't let the global rate limiting
3913 buckets go absurdly negative.
3914 - Flush local controller connection buffers periodically as we're
3915 writing to them, so we avoid queueing 4+ megabytes of data before
3918 o Major bugfixes (NT services):
3919 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
3920 command-line flag so that admins can override the default by saying
3921 "tor --service install --user "SomeUser"". This will not affect
3922 existing installed services. Also, warn the user that the service
3923 will look for its configuration file in the service user's
3924 %appdata% directory. (We can't do the 'hardwire the user's appdata
3925 directory' trick any more, since we may not have read access to that
3928 o Major bugfixes (other):
3929 - Previously, we would cache up to 16 old networkstatus documents
3930 indefinitely, if they came from nontrusted authorities. Now we
3931 discard them if they are more than 10 days old.
3932 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
3934 - Detect and reject malformed DNS responses containing circular
3936 - If exits are rare enough that we're not marking exits as guards,
3937 ignore exit bandwidth when we're deciding the required bandwidth
3939 - When we're handling a directory connection tunneled over Tor,
3940 don't fill up internal memory buffers with all the data we want
3941 to tunnel; instead, only add it if the OR connection that will
3942 eventually receive it has some room for it. (This can lead to
3943 slowdowns in tunneled dir connections; a better solution will have
3946 o Minor bugfixes (dns):
3947 - Add some defensive programming to eventdns.c in an attempt to catch
3948 possible memory-stomping bugs.
3949 - Detect and reject DNS replies containing IPv4 or IPv6 records with
3950 an incorrect number of bytes. (Previously, we would ignore the
3952 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
3953 in the correct order, and doesn't crash.
3954 - Free memory held in recently-completed DNS lookup attempts on exit.
3955 This was not a memory leak, but may have been hiding memory leaks.
3956 - Handle TTL values correctly on reverse DNS lookups.
3957 - Treat failure to parse resolv.conf as an error.
3959 o Minor bugfixes (other):
3960 - Fix crash with "tor --list-fingerprint" (reported by seeess).
3961 - When computing clock skew from directory HTTP headers, consider what
3962 time it was when we finished asking for the directory, not what
3964 - Expire socks connections if they spend too long waiting for the
3965 handshake to finish. Previously we would let them sit around for
3966 days, if the connecting application didn't close them either.
3967 - And if the socks handshake hasn't started, don't send a
3968 "DNS resolve socks failed" handshake reply; just close it.
3969 - Stop using C functions that OpenBSD's linker doesn't like.
3970 - Don't launch requests for descriptors unless we have networkstatuses
3971 from at least half of the authorities. This delays the first
3972 download slightly under pathological circumstances, but can prevent
3973 us from downloading a bunch of descriptors we don't need.
3974 - Do not log IPs with TLS failures for incoming TLS
3975 connections. (Fixes bug 382.)
3976 - If the user asks to use invalid exit nodes, be willing to use
3978 - Stop using the reserved ac_cv namespace in our configure script.
3979 - Call stat() slightly less often; use fstat() when possible.
3980 - Refactor the way we handle pending circuits when an OR connection
3981 completes or fails, in an attempt to fix a rare crash bug.
3982 - Only rewrite a conn's address based on X-Forwarded-For: headers
3983 if it's a parseable public IP address; and stop adding extra quotes
3984 to the resulting address.
3987 - Weight directory requests by advertised bandwidth. Now we can
3988 let servers enable write limiting but still allow most clients to
3989 succeed at their directory requests. (We still ignore weights when
3990 choosing a directory authority; I hope this is a feature.)
3993 - Create a new file ReleaseNotes which was the old ChangeLog. The
3994 new ChangeLog file now includes the summaries for all development
3996 - Check for addresses with invalid characters at the exit as well
3997 as at the client, and warn less verbosely when they fail. You can
3998 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
3999 - Adapt a patch from goodell to let the contrib/exitlist script
4000 take arguments rather than require direct editing.
4001 - Inform the server operator when we decide not to advertise a
4002 DirPort due to AccountingMax enabled or a low BandwidthRate. It
4003 was confusing Zax, so now we're hopefully more helpful.
4004 - Bring us one step closer to being able to establish an encrypted
4005 directory tunnel without knowing a descriptor first. Still not
4006 ready yet. As part of the change, now assume we can use a
4007 create_fast cell if we don't know anything about a router.
4008 - Allow exit nodes to use nameservers running on ports other than 53.
4009 - Servers now cache reverse DNS replies.
4010 - Add an --ignore-missing-torrc command-line option so that we can
4011 get the "use sensible defaults if the configuration file doesn't
4012 exist" behavior even when specifying a torrc location on the command
4015 o Minor features (controller):
4016 - Track reasons for OR connection failure; make these reasons
4017 available via the controller interface. (Patch from Mike Perry.)
4018 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
4019 can learn when clients are sending malformed hostnames to Tor.
4020 - Clean up documentation for controller status events.
4021 - Add a REMAP status to stream events to note that a stream's
4022 address has changed because of a cached address or a MapAddress
4026 Changes in version 0.1.2.6-alpha - 2007-01-09
4028 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
4029 connection handles more than 4 gigs in either direction, we crash.
4030 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
4031 advertised exit node, somebody might try to exit from us when
4032 we're bootstrapping and before we've built our descriptor yet.
4033 Refuse the connection rather than crashing.
4036 - Warn if we (as a server) find that we've resolved an address that we
4037 weren't planning to resolve.
4038 - Warn that using select() on any libevent version before 1.1 will be
4039 unnecessarily slow (even for select()).
4040 - Flush ERR-level controller status events just like we currently
4041 flush ERR-level log events, so that a Tor shutdown doesn't prevent
4042 the controller from learning about current events.
4044 o Minor features (more controller status events):
4045 - Implement EXTERNAL_ADDRESS server status event so controllers can
4046 learn when our address changes.
4047 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
4048 can learn when directories reject our descriptor.
4049 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
4050 can learn when a client application is speaking a non-socks protocol
4052 - Implement DANGEROUS_SOCKS client status event so controllers
4053 can learn when a client application is leaking DNS addresses.
4054 - Implement BUG general status event so controllers can learn when
4055 Tor is unhappy about its internal invariants.
4056 - Implement CLOCK_SKEW general status event so controllers can learn
4057 when Tor thinks the system clock is set incorrectly.
4058 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
4059 server status events so controllers can learn when their descriptors
4060 are accepted by a directory.
4061 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
4062 server status events so controllers can learn about Tor's progress in
4063 deciding whether it's reachable from the outside.
4064 - Implement BAD_LIBEVENT general status event so controllers can learn
4065 when we have a version/method combination in libevent that needs to
4067 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
4068 and DNS_USELESS server status events so controllers can learn
4069 about changes to DNS server status.
4071 o Minor features (directory):
4072 - Authorities no longer recommend exits as guards if this would shift
4073 too much load to the exit nodes.
4076 Changes in version 0.1.2.5-alpha - 2007-01-06
4078 - Enable write limiting as well as read limiting. Now we sacrifice
4079 capacity if we're pushing out lots of directory traffic, rather
4080 than overrunning the user's intended bandwidth limits.
4081 - Include TLS overhead when counting bandwidth usage; previously, we
4082 would count only the bytes sent over TLS, but not the bytes used
4084 - Support running the Tor service with a torrc not in the same
4085 directory as tor.exe and default to using the torrc located in
4086 the %appdata%\Tor\ of the user who installed the service. Patch
4088 - Servers now check for the case when common DNS requests are going to
4089 wildcarded addresses (i.e. all getting the same answer), and change
4090 their exit policy to reject *:* if it's happening.
4091 - Implement BEGIN_DIR cells, so we can connect to the directory
4092 server via TLS to do encrypted directory requests rather than
4093 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
4094 config options if you like.
4096 o Minor features (config and docs):
4097 - Start using the state file to store bandwidth accounting data:
4098 the bw_accounting file is now obsolete. We'll keep generating it
4099 for a while for people who are still using 0.1.2.4-alpha.
4100 - Try to batch changes to the state file so that we do as few
4101 disk writes as possible while still storing important things in
4103 - The state file and the bw_accounting file get saved less often when
4104 the AvoidDiskWrites config option is set.
4105 - Make PIDFile work on Windows (untested).
4106 - Add internal descriptions for a bunch of configuration options:
4107 accessible via controller interface and in comments in saved
4109 - Reject *:563 (NNTPS) in the default exit policy. We already reject
4110 NNTP by default, so this seems like a sensible addition.
4111 - Clients now reject hostnames with invalid characters. This should
4112 avoid some inadvertent info leaks. Add an option
4113 AllowNonRFC953Hostnames to disable this behavior, in case somebody
4114 is running a private network with hosts called @, !, and #.
4115 - Add a maintainer script to tell us which options are missing
4116 documentation: "make check-docs".
4117 - Add a new address-spec.txt document to describe our special-case
4118 addresses: .exit, .onion, and .noconnnect.
4120 o Minor features (DNS):
4121 - Ongoing work on eventdns infrastructure: now it has dns server
4122 and ipv6 support. One day Tor will make use of it.
4123 - Add client-side caching for reverse DNS lookups.
4124 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
4125 - When we change nameservers or IP addresses, reset and re-launch
4126 our tests for DNS hijacking.
4128 o Minor features (directory):
4129 - Authorities now specify server versions in networkstatus. This adds
4130 about 2% to the size of compressed networkstatus docs, and allows
4131 clients to tell which servers support BEGIN_DIR and which don't.
4132 The implementation is forward-compatible with a proposed future
4133 protocol version scheme not tied to Tor versions.
4134 - DirServer configuration lines now have an orport= option so
4135 clients can open encrypted tunnels to the authorities without
4136 having downloaded their descriptors yet. Enabled for moria1,
4137 moria2, tor26, and lefkada now in the default configuration.
4138 - Directory servers are more willing to send a 503 "busy" if they
4139 are near their write limit, especially for v1 directory requests.
4140 Now they can use their limited bandwidth for actual Tor traffic.
4141 - Clients track responses with status 503 from dirservers. After a
4142 dirserver has given us a 503, we try not to use it until an hour has
4143 gone by, or until we have no dirservers that haven't given us a 503.
4144 - When we get a 503 from a directory, and we're not a server, we don't
4145 count the failure against the total number of failures allowed
4146 for the thing we're trying to download.
4147 - Report X-Your-Address-Is correctly from tunneled directory
4148 connections; don't report X-Your-Address-Is when it's an internal
4149 address; and never believe reported remote addresses when they're
4151 - Protect against an unlikely DoS attack on directory servers.
4152 - Add a BadDirectory flag to network status docs so that authorities
4153 can (eventually) tell clients about caches they believe to be
4156 o Minor features (controller):
4157 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
4158 - Reimplement GETINFO so that info/names stays in sync with the
4160 - Implement "GETINFO fingerprint".
4161 - Implement "SETEVENTS GUARD" so controllers can get updates on
4162 entry guard status as it changes.
4164 o Minor features (clean up obsolete pieces):
4165 - Remove some options that have been deprecated since at least
4166 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
4167 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
4169 - We no longer look for identity and onion keys in "identity.key" and
4170 "onion.key" -- these were replaced by secret_id_key and
4171 secret_onion_key in 0.0.8pre1.
4172 - We no longer require unrecognized directory entries to be
4175 o Major bugfixes (security):
4176 - Stop sending the HttpProxyAuthenticator string to directory
4177 servers when directory connections are tunnelled through Tor.
4178 - Clients no longer store bandwidth history in the state file.
4179 - Do not log introduction points for hidden services if SafeLogging
4181 - When generating bandwidth history, round down to the nearest
4182 1k. When storing accounting data, round up to the nearest 1k.
4183 - When we're running as a server, remember when we last rotated onion
4184 keys, so that we will rotate keys once they're a week old even if
4185 we never stay up for a week ourselves.
4187 o Major bugfixes (other):
4188 - Fix a longstanding bug in eventdns that prevented the count of
4189 timed-out resolves from ever being reset. This bug caused us to
4190 give up on a nameserver the third time it timed out, and try it
4191 10 seconds later... and to give up on it every time it timed out
4193 - Take out the '5 second' timeout from the connection retry
4194 schedule. Now the first connect attempt will wait a full 10
4195 seconds before switching to a new circuit. Perhaps this will help
4196 a lot. Based on observations from Mike Perry.
4197 - Fix a bug on the Windows implementation of tor_mmap_file() that
4198 would prevent the cached-routers file from ever loading. Reported
4202 - Fix an assert failure when a directory authority sets
4203 AuthDirRejectUnlisted and then receives a descriptor from an
4204 unlisted router. Reported by seeess.
4205 - Avoid a double-free when parsing malformed DirServer lines.
4206 - Fix a bug when a BSD-style PF socket is first used. Patch from
4208 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
4209 to resolve an address at a given exit node even when they ask for
4211 - Servers no longer ever list themselves in their "family" line,
4212 even if configured to do so. This makes it easier to configure
4213 family lists conveniently.
4214 - When running as a server, don't fall back to 127.0.0.1 when no
4215 nameservers are configured in /etc/resolv.conf; instead, make the
4216 user fix resolv.conf or specify nameservers explicitly. (Resolves
4218 - Stop accepting certain malformed ports in configured exit policies.
4219 - Don't re-write the fingerprint file every restart, unless it has
4221 - Stop warning when a single nameserver fails: only warn when _all_ of
4222 our nameservers have failed. Also, when we only have one nameserver,
4223 raise the threshold for deciding that the nameserver is dead.
4224 - Directory authorities now only decide that routers are reachable
4225 if their identity keys are as expected.
4226 - When the user uses bad syntax in the Log config line, stop
4227 suggesting other bad syntax as a replacement.
4228 - Correctly detect ipv6 DNS capability on OpenBSD.
4230 o Minor bugfixes (controller):
4231 - Report the circuit number correctly in STREAM CLOSED events. Bug
4232 reported by Mike Perry.
4233 - Do not report bizarre values for results of accounting GETINFOs
4234 when the last second's write or read exceeds the allotted bandwidth.
4235 - Report "unrecognized key" rather than an empty string when the
4236 controller tries to fetch a networkstatus that doesn't exist.
4239 Changes in version 0.1.1.26 - 2006-12-14
4240 o Security bugfixes:
4241 - Stop sending the HttpProxyAuthenticator string to directory
4242 servers when directory connections are tunnelled through Tor.
4243 - Clients no longer store bandwidth history in the state file.
4244 - Do not log introduction points for hidden services if SafeLogging
4248 - Fix an assert failure when a directory authority sets
4249 AuthDirRejectUnlisted and then receives a descriptor from an
4250 unlisted router (reported by seeess).
4253 Changes in version 0.1.2.4-alpha - 2006-12-03
4255 - Add support for using natd; this allows FreeBSDs earlier than
4256 5.1.2 to have ipfw send connections through Tor without using
4257 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
4260 - Make all connections to addresses of the form ".noconnect"
4261 immediately get closed. This lets application/controller combos
4262 successfully test whether they're talking to the same Tor by
4263 watching for STREAM events.
4264 - Make cross.sh cross-compilation script work even when autogen.sh
4265 hasn't been run. (Patch from Michael Mohr.)
4266 - Statistics dumped by -USR2 now include a breakdown of public key
4267 operations, for profiling.
4270 - Fix a major leak when directory authorities parse their
4271 approved-routers list, a minor memory leak when we fail to pick
4272 an exit node, and a few rare leaks on errors.
4273 - Handle TransPort connections even when the server sends data before
4274 the client sends data. Previously, the connection would just hang
4275 until the client sent data. (Patch from tup based on patch from
4277 - Avoid assert failure when our cached-routers file is empty on
4281 - Don't log spurious warnings when we see a circuit close reason we
4282 don't recognize; it's probably just from a newer version of Tor.
4283 - Have directory authorities allow larger amounts of drift in uptime
4284 without replacing the server descriptor: previously, a server that
4285 restarted every 30 minutes could have 48 "interesting" descriptors
4287 - Start linking to the Tor specification and Tor reference manual
4288 correctly in the Windows installer.
4289 - Add Vidalia to the OS X uninstaller script, so when we uninstall
4290 Tor/Privoxy we also uninstall Vidalia.
4291 - Resume building on Irix64, and fix a lot of warnings from its
4293 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
4294 when we're running as a client.
4297 Changes in version 0.1.1.25 - 2006-11-04
4299 - When a client asks us to resolve (rather than connect to)
4300 an address, and we have a cached answer, give them the cached
4301 answer. Previously, we would give them no answer at all.
4302 - We were building exactly the wrong circuits when we predict
4303 hidden service requirements, meaning Tor would have to build all
4304 its circuits on demand.
4305 - If none of our live entry guards have a high uptime, but we
4306 require a guard with a high uptime, try adding a new guard before
4307 we give up on the requirement. This patch should make long-lived
4308 connections more stable on average.
4309 - When testing reachability of our DirPort, don't launch new
4310 tests when there's already one in progress -- unreachable
4311 servers were stacking up dozens of testing streams.
4313 o Security bugfixes:
4314 - When the user sends a NEWNYM signal, clear the client-side DNS
4315 cache too. Otherwise we continue to act on previous information.
4318 - Avoid a memory corruption bug when creating a hash table for
4320 - Avoid possibility of controller-triggered crash when misusing
4321 certain commands from a v0 controller on platforms that do not
4322 handle printf("%s",NULL) gracefully.
4323 - Avoid infinite loop on unexpected controller input.
4324 - Don't log spurious warnings when we see a circuit close reason we
4325 don't recognize; it's probably just from a newer version of Tor.
4326 - Add Vidalia to the OS X uninstaller script, so when we uninstall
4327 Tor/Privoxy we also uninstall Vidalia.
4330 Changes in version 0.1.2.3-alpha - 2006-10-29
4332 - Prepare for servers to publish descriptors less often: never
4333 discard a descriptor simply for being too old until either it is
4334 recommended by no authorities, or until we get a better one for
4335 the same router. Make caches consider retaining old recommended
4336 routers for even longer.
4337 - If most authorities set a BadExit flag for a server, clients
4338 don't think of it as a general-purpose exit. Clients only consider
4339 authorities that advertise themselves as listing bad exits.
4340 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
4341 headers for content, so that we can work better in the presence of
4342 caching HTTP proxies.
4343 - Allow authorities to list nodes as bad exits by fingerprint or by
4346 o Minor features, controller:
4347 - Add a REASON field to CIRC events; for backward compatibility, this
4348 field is sent only to controllers that have enabled the extended
4349 event format. Also, add additional reason codes to explain why
4350 a given circuit has been destroyed or truncated. (Patches from
4352 - Add a REMOTE_REASON field to extended CIRC events to tell the
4353 controller about why a remote OR told us to close a circuit.
4354 - Stream events also now have REASON and REMOTE_REASON fields,
4355 working much like those for circuit events.
4356 - There's now a GETINFO ns/... field so that controllers can ask Tor
4357 about the current status of a router.
4358 - A new event type "NS" to inform a controller when our opinion of
4359 a router's status has changed.
4360 - Add a GETINFO events/names and GETINFO features/names so controllers
4361 can tell which events and features are supported.
4362 - A new CLEARDNSCACHE signal to allow controllers to clear the
4363 client-side DNS cache without expiring circuits.
4365 o Security bugfixes:
4366 - When the user sends a NEWNYM signal, clear the client-side DNS
4367 cache too. Otherwise we continue to act on previous information.
4370 - Avoid sending junk to controllers or segfaulting when a controller
4371 uses EVENT_NEW_DESC with verbose nicknames.
4372 - Stop triggering asserts if the controller tries to extend hidden
4373 service circuits (reported by mwenge).
4374 - Avoid infinite loop on unexpected controller input.
4375 - When the controller does a "GETINFO network-status", tell it
4376 about even those routers whose descriptors are very old, and use
4377 long nicknames where appropriate.
4378 - Change NT service functions to be loaded on demand. This lets us
4379 build with MinGW without breaking Tor for Windows 98 users.
4380 - Do DirPort reachability tests less often, since a single test
4381 chews through many circuits before giving up.
4382 - In the hidden service example in torrc.sample, stop recommending
4383 esoteric and discouraged hidden service options.
4384 - When stopping an NT service, wait up to 10 sec for it to actually
4385 stop. (Patch from Matt Edman; resolves bug 295.)
4386 - Fix handling of verbose nicknames with ORCONN controller events:
4387 make them show up exactly when requested, rather than exactly when
4389 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
4390 printing a duplicate "$" in the keys we send (reported by mwenge).
4391 - Correctly set maximum connection limit on Cygwin. (This time
4393 - Try to detect Windows correctly when cross-compiling.
4394 - Detect the size of the routers file correctly even if it is
4395 corrupted (on systems without mmap) or not page-aligned (on systems
4396 with mmap). This bug was harmless.
4397 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
4398 to open a stream fails; now we do in more cases. This should
4399 make clients able to find a good exit faster in some cases, since
4400 unhandleable requests will now get an error rather than timing out.
4401 - Resolve two memory leaks when rebuilding the on-disk router cache
4402 (reported by fookoowa).
4403 - Clean up minor code warnings suggested by the MIPSpro C compiler,
4404 and reported by some Centos users.
4405 - Controller signals now work on non-Unix platforms that don't define
4406 SIGUSR1 and SIGUSR2 the way we expect.
4407 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
4408 values before failing, and always enables eventdns.
4409 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
4410 Try to fix this in configure.in by checking for most functions
4411 before we check for libevent.
4414 Changes in version 0.1.2.2-alpha - 2006-10-07
4416 - Make our async eventdns library on-by-default for Tor servers,
4417 and plan to deprecate the separate dnsworker threads.
4418 - Add server-side support for "reverse" DNS lookups (using PTR
4419 records so clients can determine the canonical hostname for a given
4420 IPv4 address). Only supported by servers using eventdns; servers
4421 now announce in their descriptors whether they support eventdns.
4422 - Specify and implement client-side SOCKS5 interface for reverse DNS
4423 lookups (see doc/socks-extensions.txt).
4424 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
4425 connect to directory servers through Tor. Previously, clients needed
4426 to find Tor exits to make private connections to directory servers.
4427 - Avoid choosing Exit nodes for entry or middle hops when the
4428 total bandwidth available from non-Exit nodes is much higher than
4429 the total bandwidth available from Exit nodes.
4430 - Workaround for name servers (like Earthlink's) that hijack failing
4431 DNS requests and replace the no-such-server answer with a "helpful"
4432 redirect to an advertising-driven search portal. Also work around
4433 DNS hijackers who "helpfully" decline to hijack known-invalid
4434 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
4435 lets you turn it off.
4436 - Send out a burst of long-range padding cells once we've established
4437 that we're reachable. Spread them over 4 circuits, so hopefully
4438 a few will be fast. This exercises our bandwidth and bootstraps
4439 us into the directory more quickly.
4441 o New/improved config options:
4442 - Add new config option "ResolvConf" to let the server operator
4443 choose an alternate resolve.conf file when using eventdns.
4444 - Add an "EnforceDistinctSubnets" option to control our "exclude
4445 servers on the same /16" behavior. It's still on by default; this
4446 is mostly for people who want to operate private test networks with
4447 all the machines on the same subnet.
4448 - If one of our entry guards is on the ExcludeNodes list, or the
4449 directory authorities don't think it's a good guard, treat it as
4450 if it were unlisted: stop using it as a guard, and throw it off
4451 the guards list if it stays that way for a long time.
4452 - Allow directory authorities to be marked separately as authorities
4453 for the v1 directory protocol, the v2 directory protocol, and
4454 as hidden service directories, to make it easier to retire old
4455 authorities. V1 authorities should set "HSAuthoritativeDir 1"
4456 to continue being hidden service authorities too.
4457 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
4459 o Minor features, controller:
4460 - Fix CIRC controller events so that controllers can learn the
4461 identity digests of non-Named servers used in circuit paths.
4462 - Let controllers ask for more useful identifiers for servers. Instead
4463 of learning identity digests for un-Named servers and nicknames
4464 for Named servers, the new identifiers include digest, nickname,
4465 and indication of Named status. Off by default; see control-spec.txt
4466 for more information.
4467 - Add a "getinfo address" controller command so it can display Tor's
4468 best guess to the user.
4469 - New controller event to alert the controller when our server
4470 descriptor has changed.
4471 - Give more meaningful errors on controller authentication failure.
4473 o Minor features, other:
4474 - When asked to resolve a hostname, don't use non-exit servers unless
4475 requested to do so. This allows servers with broken DNS to be
4476 useful to the network.
4477 - Divide eventdns log messages into warn and info messages.
4478 - Reserve the nickname "Unnamed" for routers that can't pick
4479 a hostname: any router can call itself Unnamed; directory
4480 authorities will never allocate Unnamed to any particular router;
4481 clients won't believe that any router is the canonical Unnamed.
4482 - Only include function names in log messages for info/debug messages.
4483 For notice/warn/err, the content of the message should be clear on
4484 its own, and printing the function name only confuses users.
4485 - Avoid some false positives during reachability testing: don't try
4486 to test via a server that's on the same /24 as us.
4487 - If we fail to build a circuit to an intended enclave, and it's
4488 not mandatory that we use that enclave, stop wanting it.
4489 - When eventdns is enabled, allow multithreaded builds on NetBSD and
4490 OpenBSD. (We had previously disabled threads on these platforms
4491 because they didn't have working thread-safe resolver functions.)
4493 o Major bugfixes, anonymity/security:
4494 - If a client asked for a server by name, and there's a named server
4495 in our network-status but we don't have its descriptor yet, we
4496 could return an unnamed server instead.
4497 - Fix NetBSD bug that could allow someone to force uninitialized RAM
4498 to be sent to a server's DNS resolver. This only affects NetBSD
4499 and other platforms that do not bounds-check tolower().
4500 - Reject (most) attempts to use Tor circuits with length one. (If
4501 many people start using Tor as a one-hop proxy, exit nodes become
4502 a more attractive target for compromise.)
4503 - Just because your DirPort is open doesn't mean people should be
4504 able to remotely teach you about hidden service descriptors. Now
4505 only accept rendezvous posts if you've got HSAuthoritativeDir set.
4507 o Major bugfixes, other:
4508 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
4509 - When a client asks the server to resolve (not connect to)
4510 an address, and it has a cached answer, give them the cached answer.
4511 Previously, the server would give them no answer at all.
4512 - Allow really slow clients to not hang up five minutes into their
4513 directory downloads (suggested by Adam J. Richter).
4514 - We were building exactly the wrong circuits when we anticipated
4515 hidden service requirements, meaning Tor would have to build all
4516 its circuits on demand.
4517 - Avoid crashing when we mmap a router cache file of size 0.
4518 - When testing reachability of our DirPort, don't launch new
4519 tests when there's already one in progress -- unreachable
4520 servers were stacking up dozens of testing streams.
4522 o Minor bugfixes, correctness:
4523 - If we're a directory mirror and we ask for "all" network status
4524 documents, we would discard status documents from authorities
4526 - Avoid a memory corruption bug when creating a hash table for
4528 - Avoid controller-triggered crash when misusing certain commands
4529 from a v0 controller on platforms that do not handle
4530 printf("%s",NULL) gracefully.
4531 - Don't crash when a controller sends a third argument to an
4532 "extendcircuit" request.
4533 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
4534 response; fix error code when "getinfo dir/status/" fails.
4535 - Avoid crash when telling controller stream-status and a stream
4537 - Patch from Adam Langley to fix assert() in eventdns.c.
4538 - Fix a debug log message in eventdns to say "X resolved to Y"
4539 instead of "X resolved to X".
4540 - Make eventdns give strings for DNS errors, not just error numbers.
4541 - Track unreachable entry guards correctly: don't conflate
4542 'unreachable by us right now' with 'listed as down by the directory
4543 authorities'. With the old code, if a guard was unreachable by
4544 us but listed as running, it would clog our guard list forever.
4545 - Behave correctly in case we ever have a network with more than
4546 2GB/s total advertised capacity.
4547 - Make TrackExitHosts case-insensitive, and fix the behavior of
4548 ".suffix" TrackExitHosts items to avoid matching in the middle of
4550 - Finally fix the openssl warnings from newer gccs that believe that
4551 ignoring a return value is okay, but casting a return value and
4552 then ignoring it is a sign of madness.
4553 - Prevent the contrib/exitlist script from printing the same
4554 result more than once.
4555 - Patch from Steve Hildrey: Generate network status correctly on
4556 non-versioning dirservers.
4557 - Don't listen to the X-Your-Address-Is hint if you did the lookup
4558 via Tor; otherwise you'll think you're the exit node's IP address.
4560 o Minor bugfixes, performance:
4561 - Two small performance improvements on parsing descriptors.
4562 - Major performance improvement on inserting descriptors: change
4563 algorithm from O(n^2) to O(n).
4564 - Make the common memory allocation path faster on machines where
4565 malloc(0) returns a pointer.
4566 - Start remembering X-Your-Address-Is directory hints even if you're
4567 a client, so you can become a server more smoothly.
4568 - Avoid duplicate entries on MyFamily line in server descriptor.
4570 o Packaging, features:
4571 - Remove architecture from OS X builds. The official builds are
4572 now universal binaries.
4573 - The Debian package now uses --verify-config when (re)starting,
4574 to distinguish configuration errors from other errors.
4575 - Update RPMs to require libevent 1.1b.
4577 o Packaging, bugfixes:
4578 - Patches so Tor builds with MinGW on Windows.
4579 - Patches so Tor might run on Cygwin again.
4580 - Resume building on non-gcc compilers and ancient gcc. Resume
4581 building with the -O0 compile flag. Resume building cleanly on
4583 - Run correctly on OS X platforms with case-sensitive filesystems.
4584 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
4585 - Add autoconf checks so Tor can build on Solaris x86 again.
4588 - Documented (and renamed) ServerDNSSearchDomains and
4589 ServerDNSResolvConfFile options.
4590 - Be clearer that the *ListenAddress directives can be repeated
4594 Changes in version 0.1.1.24 - 2006-09-29
4596 - Allow really slow clients to not hang up five minutes into their
4597 directory downloads (suggested by Adam J. Richter).
4598 - Fix major performance regression from 0.1.0.x: instead of checking
4599 whether we have enough directory information every time we want to
4600 do something, only check when the directory information has changed.
4601 This should improve client CPU usage by 25-50%.
4602 - Don't crash if, after a server has been running for a while,
4603 it can't resolve its hostname.
4606 - Allow Tor to start when RunAsDaemon is set but no logs are set.
4607 - Don't crash when the controller receives a third argument to an
4608 "extendcircuit" request.
4609 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
4610 response; fix error code when "getinfo dir/status/" fails.
4611 - Fix configure.in to not produce broken configure files with
4612 more recent versions of autoconf. Thanks to Clint for his auto*
4614 - Fix security bug on NetBSD that could allow someone to force
4615 uninitialized RAM to be sent to a server's DNS resolver. This
4616 only affects NetBSD and other platforms that do not bounds-check
4618 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
4619 methods: these are known to be buggy.
4620 - If we're a directory mirror and we ask for "all" network status
4621 documents, we would discard status documents from authorities
4625 Changes in version 0.1.2.1-alpha - 2006-08-27
4627 - Add "eventdns" async dns library from Adam Langley, tweaked to
4628 build on OSX and Windows. Only enabled if you pass the
4629 --enable-eventdns argument to configure.
4630 - Allow servers with no hostname or IP address to learn their
4631 IP address by asking the directory authorities. This code only
4632 kicks in when you would normally have exited with a "no address"
4633 error. Nothing's authenticated, so use with care.
4634 - Rather than waiting a fixed amount of time between retrying
4635 application connections, we wait only 5 seconds for the first,
4636 10 seconds for the second, and 15 seconds for each retry after
4637 that. Hopefully this will improve the expected user experience.
4638 - Patch from Tup to add support for transparent AP connections:
4639 this basically bundles the functionality of trans-proxy-tor
4640 into the Tor mainline. Now hosts with compliant pf/netfilter
4641 implementations can redirect TCP connections straight to Tor
4642 without diverting through SOCKS. Needs docs.
4643 - Busy directory servers save lots of memory by spooling server
4644 descriptors, v1 directories, and v2 networkstatus docs to buffers
4645 as needed rather than en masse. Also mmap the cached-routers
4646 files, so we don't need to keep the whole thing in memory too.
4647 - Automatically avoid picking more than one node from the same
4648 /16 network when constructing a circuit.
4649 - Revise and clean up the torrc.sample that we ship with; add
4650 a section for BandwidthRate and BandwidthBurst.
4653 - Split circuit_t into origin_circuit_t and or_circuit_t, and
4654 split connection_t into edge, or, dir, control, and base structs.
4655 These will save quite a bit of memory on busy servers, and they'll
4656 also help us track down bugs in the code and bugs in the spec.
4657 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
4658 or later. Log when we are doing this, so we can diagnose it when
4659 it fails. (Also, recommend libevent 1.1b for kqueue and
4660 win32 methods; deprecate libevent 1.0b harder; make libevent
4661 recommendation system saner.)
4662 - Start being able to build universal binaries on OS X (thanks
4664 - Export the default exit policy via the control port, so controllers
4665 don't need to guess what it is / will be later.
4666 - Add a man page entry for ProtocolWarnings.
4667 - Add TestVia config option to the man page.
4668 - Remove even more protocol-related warnings from Tor server logs,
4669 such as bad TLS handshakes and malformed begin cells.
4670 - Stop fetching descriptors if you're not a dir mirror and you
4671 haven't tried to establish any circuits lately. [This currently
4672 causes some dangerous behavior, because when you start up again
4673 you'll use your ancient server descriptors.]
4674 - New DirPort behavior: if you have your dirport set, you download
4675 descriptors aggressively like a directory mirror, whether or not
4677 - Get rid of the router_retry_connections notion. Now routers
4678 no longer try to rebuild long-term connections to directory
4679 authorities, and directory authorities no longer try to rebuild
4680 long-term connections to all servers. We still don't hang up
4681 connections in these two cases though -- we need to look at it
4682 more carefully to avoid flapping, and we likely need to wait til
4683 0.1.1.x is obsolete.
4684 - Drop compatibility with obsolete Tors that permit create cells
4685 to have the wrong circ_id_type.
4686 - Re-enable per-connection rate limiting. Get rid of the "OP
4687 bandwidth" concept. Lay groundwork for "bandwidth classes" --
4688 separate global buckets that apply depending on what sort of conn
4690 - Start publishing one minute or so after we find our ORPort
4691 to be reachable. This will help reduce the number of descriptors
4692 we have for ourselves floating around, since it's quite likely
4693 other things (e.g. DirPort) will change during that minute too.
4694 - Fork the v1 directory protocol into its own spec document,
4695 and mark dir-spec.txt as the currently correct (v2) spec.
4698 - When we find our DirPort to be reachable, publish a new descriptor
4699 so we'll tell the world (reported by pnx).
4700 - Publish a new descriptor after we hup/reload. This is important
4701 if our config has changed such that we'll want to start advertising
4702 our DirPort now, etc.
4703 - Allow Tor to start when RunAsDaemon is set but no logs are set.
4704 - When we have a state file we cannot parse, tell the user and
4705 move it aside. Now we avoid situations where the user starts
4706 Tor in 1904, Tor writes a state file with that timestamp in it,
4707 the user fixes her clock, and Tor refuses to start.
4708 - Fix configure.in to not produce broken configure files with
4709 more recent versions of autoconf. Thanks to Clint for his auto*
4711 - "tor --verify-config" now exits with -1(255) or 0 depending on
4712 whether the config options are bad or good.
4713 - Resolve bug 321 when using dnsworkers: append a period to every
4714 address we resolve at the exit node, so that we do not accidentally
4715 pick up local addresses, and so that failing searches are retried
4716 in the resolver search domains. (This is already solved for
4717 eventdns.) (This breaks Blossom servers for now.)
4718 - If we are using an exit enclave and we can't connect, e.g. because
4719 its webserver is misconfigured to not listen on localhost, then
4720 back off and try connecting from somewhere else before we fail.
4723 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
4724 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
4725 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
4726 when the IP address is mapped through MapAddress to a hostname.
4727 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
4728 useless IPv6 DNS resolves.
4729 - Patch suggested by Karsten Loesing: respond to SIGNAL command
4730 before we execute the signal, in case the signal shuts us down.
4731 - Clean up AllowInvalidNodes man page entry.
4732 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
4733 - Add more asserts to track down an assert error on a windows Tor
4734 server with connection_add being called with socket == -1.
4735 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
4736 - Fix misleading log messages: an entry guard that is "unlisted",
4737 as well as not known to be "down" (because we've never heard
4738 of it), is not therefore "up".
4739 - Remove code to special-case "-cvs" ending, since it has not
4740 actually mattered since 0.0.9.
4741 - Make our socks5 handling more robust to broken socks clients:
4742 throw out everything waiting on the buffer in between socks
4743 handshake phases, since they can't possibly (so the theory
4744 goes) have predicted what we plan to respond to them.
4747 Changes in version 0.1.1.23 - 2006-07-30
4749 - Fast Tor servers, especially exit nodes, were triggering asserts
4750 due to a bug in handling the list of pending DNS resolves. Some
4751 bugs still remain here; we're hunting them.
4752 - Entry guards could crash clients by sending unexpected input.
4753 - More fixes on reachability testing: if you find yourself reachable,
4754 then don't ever make any client requests (so you stop predicting
4755 circuits), then hup or have your clock jump, then later your IP
4756 changes, you won't think circuits are working, so you won't try to
4757 test reachability, so you won't publish.
4760 - Avoid a crash if the controller does a resetconf firewallports
4761 and then a setconf fascistfirewall=1.
4762 - Avoid an integer underflow when the dir authority decides whether
4763 a router is stable: we might wrongly label it stable, and compute
4764 a slightly wrong median stability, when a descriptor is published
4766 - Fix a place where we might trigger an assert if we can't build our
4767 own server descriptor yet.
4770 Changes in version 0.1.1.22 - 2006-07-05
4772 - Fix a big bug that was causing servers to not find themselves
4773 reachable if they changed IP addresses. Since only 0.1.1.22+
4774 servers can do reachability testing correctly, now we automatically
4775 make sure to test via one of these.
4776 - Fix to allow clients and mirrors to learn directory info from
4777 descriptor downloads that get cut off partway through.
4778 - Directory authorities had a bug in deciding if a newly published
4779 descriptor was novel enough to make everybody want a copy -- a few
4780 servers seem to be publishing new descriptors many times a minute.
4782 - Fix a rare bug that was causing some servers to complain about
4783 "closing wedged cpuworkers" and skip some circuit create requests.
4784 - Make the Exit flag in directory status documents actually work.
4787 Changes in version 0.1.1.21 - 2006-06-10
4788 o Crash and assert fixes from 0.1.1.20:
4789 - Fix a rare crash on Tor servers that have enabled hibernation.
4790 - Fix a seg fault on startup for Tor networks that use only one
4791 directory authority.
4792 - Fix an assert from a race condition that occurs on Tor servers
4793 while exiting, where various threads are trying to log that they're
4794 exiting, and delete the logs, at the same time.
4795 - Make our unit tests pass again on certain obscure platforms.
4798 - Add support for building SUSE RPM packages.
4799 - Speed up initial bootstrapping for clients: if we are making our
4800 first ever connection to any entry guard, then don't mark it down
4802 - When only one Tor server in the network is labelled as a guard,
4803 and we've already picked him, we would cycle endlessly picking him
4804 again, being unhappy about it, etc. Now we specifically exclude
4805 current guards when picking a new guard.
4806 - Servers send create cells more reliably after the TLS connection
4807 is established: we were sometimes forgetting to send half of them
4808 when we had more than one pending.
4809 - If we get a create cell that asks us to extend somewhere, but the
4810 Tor server there doesn't match the expected digest, we now send
4811 a destroy cell back, rather than silently doing nothing.
4812 - Make options->RedirectExit work again.
4813 - Make cookie authentication for the controller work again.
4814 - Stop being picky about unusual characters in the arguments to
4815 mapaddress. It's none of our business.
4816 - Add a new config option "TestVia" that lets you specify preferred
4817 middle hops to use for test circuits. Perhaps this will let me
4818 debug the reachability problems better.
4820 o Log / documentation fixes:
4821 - If we're a server and some peer has a broken TLS certificate, don't
4822 log about it unless ProtocolWarnings is set, i.e., we want to hear
4823 about protocol violations by others.
4824 - Fix spelling of VirtualAddrNetwork in man page.
4825 - Add a better explanation at the top of the autogenerated torrc file
4826 about what happened to our old torrc.
4829 Changes in version 0.1.1.20 - 2006-05-23
4831 - Downgrade a log severity where servers complain that they're
4833 - Avoid a compile warning on FreeBSD.
4834 - Remove string size limit on NEWDESC messages; solve bug 291.
4835 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
4836 more thoroughly when we're running on windows.
4839 Changes in version 0.1.1.19-rc - 2006-05-03
4841 - Regenerate our local descriptor if it's dirty and we try to use
4842 it locally (e.g. if it changes during reachability detection).
4843 - If we setconf our ORPort to 0, we continued to listen on the
4844 old ORPort and receive connections.
4845 - Avoid a second warning about machine/limits.h on Debian
4847 - Be willing to add our own routerinfo into the routerlist.
4848 Now authorities will include themselves in their directories
4849 and network-statuses.
4850 - Stop trying to upload rendezvous descriptors to every
4851 directory authority: only try the v1 authorities.
4852 - Servers no longer complain when they think they're not
4853 registered with the directory authorities. There were too many
4855 - Backport dist-rpm changes so rpms can be built without errors.
4858 - Implement an option, VirtualAddrMask, to set which addresses
4859 get handed out in response to mapaddress requests. This works
4860 around a bug in tsocks where 127.0.0.0/8 is never socksified.
4863 Changes in version 0.1.1.18-rc - 2006-04-10
4865 - Work harder to download live network-statuses from all the
4866 directory authorities we know about. Improve the threshold
4867 decision logic so we're more robust to edge cases.
4868 - When fetching rendezvous descriptors, we were willing to ask
4869 v2 authorities too, which would always return 404.
4872 - Stop listing down or invalid nodes in the v1 directory. This will
4873 reduce its bulk by about 1/3, and reduce load on directory
4875 - When deciding whether a router is Fast or Guard-worthy, consider
4876 his advertised BandwidthRate and not just the BandwidthCapacity.
4877 - No longer ship INSTALL and README files -- they are useless now.
4878 - Force rpmbuild to behave and honor target_cpu.
4879 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
4880 - Start to include translated versions of the tor-doc-*.html
4881 files, along with the screenshots. Still needs more work.
4882 - Start sending back 512 and 451 errors if mapaddress fails,
4883 rather than not sending anything back at all.
4884 - When we fail to bind or listen on an incoming or outgoing
4885 socket, we should close it before failing. otherwise we just
4886 leak it. (thanks to weasel for finding.)
4887 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
4888 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
4889 - Make NoPublish (even though deprecated) work again.
4890 - Fix a minor security flaw where a versioning auth dirserver
4891 could list a recommended version many times in a row to make
4892 clients more convinced that it's recommended.
4893 - Fix crash bug if there are two unregistered servers running
4894 with the same nickname, one of them is down, and you ask for
4895 them by nickname in your EntryNodes or ExitNodes. Also, try
4896 to pick the one that's running rather than an arbitrary one.
4897 - Fix an infinite loop we could hit if we go offline for too long.
4898 - Complain when we hit WSAENOBUFS on recv() or write() too.
4899 Perhaps this will help us hunt the bug.
4900 - If you're not a versioning dirserver, don't put the string
4901 "client-versions \nserver-versions \n" in your network-status.
4902 - Lower the minimum required number of file descriptors to 1000,
4903 so we can have some overhead for Valgrind on Linux, where the
4904 default ulimit -n is 1024.
4907 - Add tor.dizum.com as the fifth authoritative directory server.
4908 - Add a new config option FetchUselessDescriptors, off by default,
4909 for when you plan to run "exitlist" on your client and you want
4910 to know about even the non-running descriptors.
4913 Changes in version 0.1.1.17-rc - 2006-03-28
4915 - Clients and servers since 0.1.1.10-alpha have been expiring
4916 connections whenever they are idle for 5 minutes and they *do*
4917 have circuits on them. Oops. With this new version, clients will
4918 discard their previous entry guard choices and avoid choosing
4919 entry guards running these flawed versions.
4920 - Fix memory leak when uncompressing concatenated zlib streams. This
4921 was causing substantial leaks over time on Tor servers.
4922 - The v1 directory was including servers as much as 48 hours old,
4923 because that's how the new routerlist->routers works. Now only
4924 include them if they're 20 hours old or less.
4927 - Resume building on irix64, netbsd 2.0, etc.
4928 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
4930 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
4931 and it is confusing some users.
4932 - Mirrors stop caching the v1 directory so often.
4933 - Make the max number of old descriptors that a cache will hold
4934 rise with the number of directory authorities, so we can scale.
4935 - Change our win32 uname() hack to be more forgiving about what
4936 win32 versions it thinks it's found.
4939 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
4941 - When the controller's *setconf commands fail, collect an error
4942 message in a string and hand it back to the controller.
4943 - Make the v2 dir's "Fast" flag based on relative capacity, just
4944 like "Stable" is based on median uptime. Name everything in the
4945 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
4946 - Log server fingerprint on startup, so new server operators don't
4947 have to go hunting around their filesystem for it.
4948 - Return a robots.txt on our dirport to discourage google indexing.
4949 - Let the controller ask for GETINFO dir/status/foo so it can ask
4950 directly rather than connecting to the dir port. Only works when
4951 dirport is set for now.
4953 o New config options rather than constants in the code:
4954 - SocksTimeout: How long do we let a socks connection wait
4955 unattached before we fail it?
4956 - CircuitBuildTimeout: Cull non-open circuits that were born
4957 at least this many seconds ago.
4958 - CircuitIdleTimeout: Cull open clean circuits that were born
4959 at least this many seconds ago.
4962 Changes in version 0.1.1.16-rc - 2006-03-18
4963 o Bugfixes on 0.1.1.15-rc:
4964 - Fix assert when the controller asks to attachstream a connect-wait
4965 or resolve-wait stream.
4966 - Now do address rewriting when the controller asks us to attach
4967 to a particular circuit too. This will let Blossom specify
4968 "moria2.exit" without having to learn what moria2's IP address is.
4969 - Make the "tor --verify-config" command-line work again, so people
4970 can automatically check if their torrc will parse.
4971 - Authoritative dirservers no longer require an open connection from
4972 a server to consider him "reachable". We need this change because
4973 when we add new auth dirservers, old servers won't know not to
4975 - Let Tor build on Sun CC again.
4976 - Fix an off-by-one buffer size in dirserv.c that magically never
4977 hit our three authorities but broke sjmurdoch's own tor network.
4978 - If we as a directory mirror don't know of any v1 directory
4979 authorities, then don't try to cache any v1 directories.
4980 - Stop warning about unknown servers in our family when they are
4981 given as hex digests.
4982 - Stop complaining as quickly to the server operator that he
4983 hasn't registered his nickname/key binding.
4984 - Various cleanups so we can add new V2 Auth Dirservers.
4985 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
4986 reflect the updated flags in our v2 dir protocol.
4987 - Resume allowing non-printable characters for exit streams (both
4988 for connecting and for resolving). Now we tolerate applications
4989 that don't follow the RFCs. But continue to block malformed names
4992 o Bugfixes on 0.1.0.x:
4993 - Fix assert bug in close_logs(): when we close and delete logs,
4994 remove them all from the global "logfiles" list.
4995 - Fix minor integer overflow in calculating when we expect to use up
4996 our bandwidth allocation before hibernating.
4997 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
4998 there are multiple SSLs installed with different versions.
4999 - When we try to be a server and Address is not explicitly set and
5000 our hostname resolves to a private IP address, try to use an
5001 interface address if it has a public address. Now Windows machines
5002 that think of themselves as localhost can work by default.
5005 - Let the controller ask for GETINFO dir/server/foo so it can ask
5006 directly rather than connecting to the dir port.
5007 - Let the controller tell us about certain router descriptors
5008 that it doesn't want Tor to use in circuits. Implement
5009 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
5010 - New config option SafeSocks to reject all application connections
5011 using unsafe socks protocols. Defaults to off.
5014 Changes in version 0.1.1.15-rc - 2006-03-11
5015 o Bugfixes and cleanups:
5016 - When we're printing strings from the network, don't try to print
5017 non-printable characters. This protects us against shell escape
5018 sequence exploits, and also against attacks to fool humans into
5019 misreading their logs.
5020 - Fix a bug where Tor would fail to establish any connections if you
5021 left it off for 24 hours and then started it: we were happy with
5022 the obsolete network statuses, but they all referred to router
5023 descriptors that were too old to fetch, so we ended up with no
5024 valid router descriptors.
5025 - Fix a seg fault in the controller's "getinfo orconn-status"
5026 command while listing status on incoming handshaking connections.
5027 Introduce a status name "NEW" for these connections.
5028 - If we get a linelist or linelist_s config option from the torrc
5029 (e.g. ExitPolicy) and it has no value, warn and skip rather than
5030 silently resetting it to its default.
5031 - Don't abandon entry guards until they've been down or gone for
5033 - Cleaner and quieter log messages.
5036 - New controller signal NEWNYM that makes new application requests
5038 - Add a new circuit purpose 'controller' to let the controller ask
5039 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
5040 controller command to let you specify the purpose if you're
5041 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
5042 command to let you change a circuit's purpose after it's been
5044 - Accept "private:*" in routerdesc exit policies; not generated yet
5045 because older Tors do not understand it.
5046 - Add BSD-style contributed startup script "rc.subr" from Peter
5050 Changes in version 0.1.1.14-alpha - 2006-02-20
5051 o Bugfixes on 0.1.1.x:
5052 - Don't die if we ask for a stdout or stderr log (even implicitly)
5053 and we're set to RunAsDaemon -- just warn.
5054 - We still had a few bugs in the OR connection rotation code that
5055 caused directory servers to slowly aggregate connections to other
5056 fast Tor servers. This time for sure!
5057 - Make log entries on Win32 include the name of the function again.
5058 - We were treating a pair of exit policies if they were equal even
5059 if one said accept and the other said reject -- causing us to
5060 not always publish a new descriptor since we thought nothing
5062 - Retry pending server downloads as well as pending networkstatus
5063 downloads when we unexpectedly get a socks request.
5064 - We were ignoring the IS_FAST flag in the directory status,
5065 meaning we were willing to pick trivial-bandwidth nodes for "fast"
5067 - If the controller's SAVECONF command fails (e.g. due to file
5068 permissions), let the controller know that it failed.
5071 - If we're trying to be a Tor server and running Windows 95/98/ME
5072 as a server, explain that we'll likely crash.
5073 - When we're a server, a client asks for an old-style directory,
5074 and our write bucket is empty, don't give it to him. This way
5075 small servers can continue to serve the directory *sometimes*,
5076 without getting overloaded.
5077 - Compress exit policies even more -- look for duplicate lines
5079 - Clients now honor the "guard" flag in the router status when
5080 picking entry guards, rather than looking at is_fast or is_stable.
5081 - Retain unrecognized lines in $DATADIR/state file, so that we can
5082 be forward-compatible.
5083 - Generate 18.0.0.0/8 address policy format in descs when we can;
5084 warn when the mask is not reducible to a bit-prefix.
5085 - Let the user set ControlListenAddress in the torrc. This can be
5086 dangerous, but there are some cases (like a secured LAN) where it
5088 - Split ReachableAddresses into ReachableDirAddresses and
5089 ReachableORAddresses, so we can restrict Dir conns to port 80
5090 and OR conns to port 443.
5091 - Now we can target arch and OS in rpm builds (contributed by
5092 Phobos). Also make the resulting dist-rpm filename match the
5094 - New config options to help controllers: FetchServerDescriptors
5095 and FetchHidServDescriptors for whether to fetch server
5096 info and hidserv info or let the controller do it, and
5097 PublishServerDescriptor and PublishHidServDescriptors.
5098 - Also let the controller set the __AllDirActionsPrivate config
5099 option if you want all directory fetches/publishes to happen via
5100 Tor (it assumes your controller bootstraps your circuits).
5103 Changes in version 0.1.0.17 - 2006-02-17
5104 o Crash bugfixes on 0.1.0.x:
5105 - When servers with a non-zero DirPort came out of hibernation,
5106 sometimes they would trigger an assert.
5108 o Other important bugfixes:
5109 - On platforms that don't have getrlimit (like Windows), we were
5110 artificially constraining ourselves to a max of 1024
5111 connections. Now just assume that we can handle as many as 15000
5112 connections. Hopefully this won't cause other problems.
5114 o Backported features:
5115 - When we're a server, a client asks for an old-style directory,
5116 and our write bucket is empty, don't give it to him. This way
5117 small servers can continue to serve the directory *sometimes*,
5118 without getting overloaded.
5119 - Whenever you get a 503 in response to a directory fetch, try
5120 once more. This will become important once servers start sending
5121 503's whenever they feel busy.
5122 - Fetch a new directory every 120 minutes, not every 40 minutes.
5123 Now that we have hundreds of thousands of users running the old
5124 directory algorithm, it's starting to hurt a lot.
5125 - Bump up the period for forcing a hidden service descriptor upload
5126 from 20 minutes to 1 hour.
5129 Changes in version 0.1.1.13-alpha - 2006-02-09
5130 o Crashes in 0.1.1.x:
5131 - When you tried to setconf ORPort via the controller, Tor would
5132 crash. So people using TorCP to become a server were sad.
5133 - Solve (I hope) the stack-smashing bug that we were seeing on fast
5134 servers. The problem appears to be something do with OpenSSL's
5135 random number generation, or how we call it, or something. Let me
5136 know if the crashes continue.
5137 - Turn crypto hardware acceleration off by default, until we find
5138 somebody smart who can test it for us. (It appears to produce
5139 seg faults in at least some cases.)
5140 - Fix a rare assert error when we've tried all intro points for
5141 a hidden service and we try fetching the service descriptor again:
5142 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
5145 - Fix a major load balance bug: we were round-robining in 16 KB
5146 chunks, and servers with bandwidthrate of 20 KB, while downloading
5147 a 600 KB directory, would starve their other connections. Now we
5148 try to be a bit more fair.
5149 - Dir authorities and mirrors were never expiring the newest
5150 descriptor for each server, causing memory and directory bloat.
5151 - Fix memory-bloating and connection-bloating bug on servers: We
5152 were never closing any connection that had ever had a circuit on
5153 it, because we were checking conn->n_circuits == 0, yet we had a
5154 bug that let it go negative.
5155 - Make Tor work using squid as your http proxy again -- squid
5156 returns an error if you ask for a URL that's too long, and it uses
5157 a really generic error message. Plus, many people are behind a
5158 transparent squid so they don't even realize it.
5159 - On platforms that don't have getrlimit (like Windows), we were
5160 artificially constraining ourselves to a max of 1024
5161 connections. Now just assume that we can handle as many as 15000
5162 connections. Hopefully this won't cause other problems.
5163 - Add a new config option ExitPolicyRejectPrivate which defaults to
5164 1. This means all exit policies will begin with rejecting private
5165 addresses, unless the server operator explicitly turns it off.
5168 - Clients no longer download descriptors for non-running
5170 - Before we add new directory authorities, we should make it
5171 clear that only v1 authorities should receive/publish hidden
5172 service descriptors.
5175 - As soon as we've fetched some more directory info, immediately
5176 try to download more server descriptors. This way we don't have
5177 a 10 second pause during initial bootstrapping.
5178 - Remove even more loud log messages that the server operator can't
5180 - When we're running an obsolete or un-recommended version, make
5181 the log message more clear about what the problem is and what
5182 versions *are* still recommended.
5183 - Provide a more useful warn message when our onion queue gets full:
5184 the CPU is too slow or the exit policy is too liberal.
5185 - Don't warn when we receive a 503 from a dirserver/cache -- this
5186 will pave the way for them being able to refuse if they're busy.
5187 - When we fail to bind a listener, try to provide a more useful
5188 log message: e.g., "Is Tor already running?"
5189 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
5190 Goldberg can prove things about our handshake protocol more
5192 - MaxConn has been obsolete for a while now. Document the ConnLimit
5193 config option, which is a *minimum* number of file descriptors
5194 that must be available else Tor refuses to start.
5195 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
5196 if you log to syslog and want something other than LOG_DAEMON.
5197 - Make dirservers generate a separate "guard" flag to mean,
5198 "would make a good entry guard". Make clients parse it and vote
5199 on it. Not used by clients yet.
5200 - Implement --with-libevent-dir option to ./configure. Also, improve
5201 search techniques to find libevent, and use those for openssl too.
5202 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
5203 - Only start testing reachability once we've established a
5204 circuit. This will make startup on dirservers less noisy.
5205 - Don't try to upload hidden service descriptors until we have
5206 established a circuit.
5207 - Fix the controller's "attachstream 0" command to treat conn like
5208 it just connected, doing address remapping, handling .exit and
5209 .onion idioms, and so on. Now we're more uniform in making sure
5210 that the controller hears about new and closing connections.
5213 Changes in version 0.1.1.12-alpha - 2006-01-11
5214 o Bugfixes on 0.1.1.x:
5215 - The fix to close duplicate server connections was closing all
5216 Tor client connections if they didn't establish a circuit
5217 quickly enough. Oops.
5218 - Fix minor memory issue (double-free) that happened on exit.
5220 o Bugfixes on 0.1.0.x:
5221 - Tor didn't warn when it failed to open a log file.
5224 Changes in version 0.1.1.11-alpha - 2006-01-10
5225 o Crashes in 0.1.1.x:
5226 - Include all the assert/crash fixes from 0.1.0.16.
5227 - If you start Tor and then quit very quickly, there were some
5228 races that tried to free things that weren't allocated yet.
5229 - Fix a rare memory stomp if you're running hidden services.
5230 - Fix segfault when specifying DirServer in config without nickname.
5231 - Fix a seg fault when you finish connecting to a server but at
5232 that moment you dump his server descriptor.
5233 - Extendcircuit and Attachstream controller commands would
5234 assert/crash if you don't give them enough arguments.
5235 - Fix an assert error when we're out of space in the connection_list
5236 and we try to post a hidden service descriptor (reported by weasel).
5237 - If you specify a relative torrc path and you set RunAsDaemon in
5238 your torrc, then it chdir()'s to the new directory. If you HUP,
5239 it tries to load the new torrc location, fails, and exits.
5240 The fix: no longer allow a relative path to torrc using -f.
5243 - Implement "entry guards": automatically choose a handful of entry
5244 nodes and stick with them for all circuits. Only pick new guards
5245 when the ones you have are unsuitable, and if the old guards
5246 become suitable again, switch back. This will increase security
5247 dramatically against certain end-point attacks. The EntryNodes
5248 config option now provides some hints about which entry guards you
5249 want to use most; and StrictEntryNodes means to only use those.
5250 - New directory logic: download by descriptor digest, not by
5251 fingerprint. Caches try to download all listed digests from
5252 authorities; clients try to download "best" digests from caches.
5253 This avoids partitioning and isolating attacks better.
5254 - Make the "stable" router flag in network-status be the median of
5255 the uptimes of running valid servers, and make clients pay
5256 attention to the network-status flags. Thus the cutoff adapts
5257 to the stability of the network as a whole, making IRC, IM, etc
5258 connections more reliable.
5261 - Tor servers with dynamic IP addresses were needing to wait 18
5262 hours before they could start doing reachability testing using
5263 the new IP address and ports. This is because they were using
5264 the internal descriptor to learn what to test, yet they were only
5265 rebuilding the descriptor once they decided they were reachable.
5266 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
5267 to download certain server descriptors, throw them away, and then
5268 fetch them again after 30 minutes. Now mirrors throw away these
5269 server descriptors so clients can't get them.
5270 - We were leaving duplicate connections to other ORs open for a week,
5271 rather than closing them once we detect a duplicate. This only
5272 really affected authdirservers, but it affected them a lot.
5273 - Spread the authdirservers' reachability testing over the entire
5274 testing interval, so we don't try to do 500 TLS's at once every
5278 - If the network is down, and we try to connect to a conn because
5279 we have a circuit in mind, and we timeout (30 seconds) because the
5280 network never answers, we were expiring the circuit, but we weren't
5281 obsoleting the connection or telling the entry_guards functions.
5282 - Some Tor servers process billions of cells per day. These statistics
5283 need to be uint64_t's.
5284 - Check for integer overflows in more places, when adding elements
5285 to smartlists. This could possibly prevent a buffer overflow
5286 on malicious huge inputs. I don't see any, but I haven't looked
5288 - ReachableAddresses kept growing new "reject *:*" lines on every
5290 - When you "setconf log" via the controller, it should remove all
5291 logs. We were automatically adding back in a "log notice stdout".
5292 - Newly bootstrapped Tor networks couldn't establish hidden service
5293 circuits until they had nodes with high uptime. Be more tolerant.
5294 - We were marking servers down when they could not answer every piece
5295 of the directory request we sent them. This was far too harsh.
5296 - Fix the torify (tsocks) config file to not use Tor for localhost
5298 - Directory authorities now go to the proper authority when asking for
5299 a networkstatus, even when they want a compressed one.
5300 - Fix a harmless bug that was causing Tor servers to log
5301 "Got an end because of misc error, but we're not an AP. Closing."
5302 - Authorities were treating their own descriptor changes as cosmetic,
5303 meaning the descriptor available in the network-status and the
5304 descriptor that clients downloaded were different.
5305 - The OS X installer was adding a symlink for tor_resolve but
5306 the binary was called tor-resolve (reported by Thomas Hardly).
5307 - Workaround a problem with some http proxies where they refuse GET
5308 requests that specify "Content-Length: 0" (reported by Adrian).
5309 - Fix wrong log message when you add a "HiddenServiceNodes" config
5310 line without any HiddenServiceDir line (reported by Chris Thomas).
5313 - Write the TorVersion into the state file so we have a prayer of
5314 keeping forward and backward compatibility.
5315 - Revive the FascistFirewall config option rather than eliminating it:
5316 now it's a synonym for ReachableAddresses *:80,*:443.
5317 - Clients choose directory servers from the network status lists,
5318 not from their internal list of router descriptors. Now they can
5319 go to caches directly rather than needing to go to authorities
5321 - Directory authorities ignore router descriptors that have only
5322 cosmetic differences: do this for 0.1.0.x servers now too.
5323 - Add a new flag to network-status indicating whether the server
5324 can answer v2 directory requests too.
5325 - Authdirs now stop whining so loudly about bad descriptors that
5326 they fetch from other dirservers. So when there's a log complaint,
5327 it's for sure from a freshly uploaded descriptor.
5328 - Reduce memory requirements in our structs by changing the order
5330 - There used to be two ways to specify your listening ports in a
5331 server descriptor: on the "router" line and with a separate "ports"
5332 line. Remove support for the "ports" line.
5333 - New config option "AuthDirRejectUnlisted" for auth dirservers as
5334 a panic button: if we get flooded with unusable servers we can
5335 revert to only listing servers in the approved-routers file.
5336 - Auth dir servers can now mark a fingerprint as "!reject" or
5337 "!invalid" in the approved-routers file (as its nickname), to
5338 refuse descriptors outright or include them but marked as invalid.
5339 - Servers store bandwidth history across restarts/crashes.
5340 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
5341 get a better idea of why their circuits failed. Not used yet.
5342 - Directory mirrors now cache up to 16 unrecognized network-status
5343 docs. Now we can add new authdirservers and they'll be cached too.
5344 - When picking a random directory, prefer non-authorities if any
5346 - New controller option "getinfo desc/all-recent" to fetch the
5347 latest server descriptor for every router that Tor knows about.
5350 Changes in version 0.1.0.16 - 2006-01-02
5351 o Crash bugfixes on 0.1.0.x:
5352 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
5353 corrupting the heap, losing FDs, or crashing when we need to resize
5354 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
5355 - It turns out sparc64 platforms crash on unaligned memory access
5356 too -- so detect and avoid this.
5357 - Handle truncated compressed data correctly (by detecting it and
5359 - Fix possible-but-unlikely free(NULL) in control.c.
5360 - When we were closing connections, there was a rare case that
5361 stomped on memory, triggering seg faults and asserts.
5362 - Avoid potential infinite recursion when building a descriptor. (We
5363 don't know that it ever happened, but better to fix it anyway.)
5364 - We were neglecting to unlink marked circuits from soon-to-close OR
5365 connections, which caused some rare scribbling on freed memory.
5366 - Fix a memory stomping race bug when closing the joining point of two
5367 rendezvous circuits.
5368 - Fix an assert in time parsing found by Steven Murdoch.
5370 o Other bugfixes on 0.1.0.x:
5371 - When we're doing reachability testing, provide more useful log
5372 messages so the operator knows what to expect.
5373 - Do not check whether DirPort is reachable when we are suppressing
5374 advertising it because of hibernation.
5375 - When building with -static or on Solaris, we sometimes needed -ldl.
5376 - When we're deciding whether a stream has enough circuits around
5377 that can handle it, count the freshly dirty ones and not the ones
5378 that are so dirty they won't be able to handle it.
5379 - When we're expiring old circuits, we had a logic error that caused
5380 us to close new rendezvous circuits rather than old ones.
5381 - Give a more helpful log message when you try to change ORPort via
5382 the controller: you should upgrade Tor if you want that to work.
5383 - We were failing to parse Tor versions that start with "Tor ".
5384 - Tolerate faulty streams better: when a stream fails for reason
5385 exitpolicy, stop assuming that the router is lying about his exit
5386 policy. When a stream fails for reason misc, allow it to retry just
5387 as if it was resolvefailed. When a stream has failed three times,
5388 reset its failure count so we can try again and get all three tries.
5391 Changes in version 0.1.1.10-alpha - 2005-12-11
5392 o Correctness bugfixes on 0.1.0.x:
5393 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
5394 corrupting the heap, losing FDs, or crashing when we need to resize
5395 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
5396 - Stop doing the complex voodoo overkill checking for insecure
5397 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
5398 - When we were closing connections, there was a rare case that
5399 stomped on memory, triggering seg faults and asserts.
5400 - We were neglecting to unlink marked circuits from soon-to-close OR
5401 connections, which caused some rare scribbling on freed memory.
5402 - When we're deciding whether a stream has enough circuits around
5403 that can handle it, count the freshly dirty ones and not the ones
5404 that are so dirty they won't be able to handle it.
5405 - Recover better from TCP connections to Tor servers that are
5406 broken but don't tell you (it happens!); and rotate TLS
5407 connections once a week.
5408 - When we're expiring old circuits, we had a logic error that caused
5409 us to close new rendezvous circuits rather than old ones.
5410 - Fix a scary-looking but apparently harmless bug where circuits
5411 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
5412 servers, and never switch to state CIRCUIT_STATE_OPEN.
5413 - When building with -static or on Solaris, we sometimes needed to
5415 - Give a useful message when people run Tor as the wrong user,
5416 rather than telling them to start chowning random directories.
5417 - We were failing to inform the controller about new .onion streams.
5419 o Security bugfixes on 0.1.0.x:
5420 - Refuse server descriptors if the fingerprint line doesn't match
5421 the included identity key. Tor doesn't care, but other apps (and
5422 humans) might actually be trusting the fingerprint line.
5423 - We used to kill the circuit when we receive a relay command we
5424 don't recognize. Now we just drop it.
5425 - Start obeying our firewall options more rigorously:
5426 . If we can't get to a dirserver directly, try going via Tor.
5427 . Don't ever try to connect (as a client) to a place our
5428 firewall options forbid.
5429 . If we specify a proxy and also firewall options, obey the
5430 firewall options even when we're using the proxy: some proxies
5431 can only proxy to certain destinations.
5432 - Fix a bug found by Lasse Overlier: when we were making internal
5433 circuits (intended to be cannibalized later for rendezvous and
5434 introduction circuits), we were picking them so that they had
5435 useful exit nodes. There was no need for this, and it actually
5436 aids some statistical attacks.
5437 - Start treating internal circuits and exit circuits separately.
5438 It's important to keep them separate because internal circuits
5439 have their last hops picked like middle hops, rather than like
5440 exit hops. So exiting on them will break the user's expectations.
5442 o Bugfixes on 0.1.1.x:
5443 - Take out the mis-feature where we tried to detect IP address
5444 flapping for people with DynDNS, and chose not to upload a new
5445 server descriptor sometimes.
5446 - Try to be compatible with OpenSSL 0.9.6 again.
5447 - Log fix: when the controller is logging about .onion addresses,
5448 sometimes it didn't include the ".onion" part of the address.
5449 - Don't try to modify options->DirServers internally -- if the
5450 user didn't specify any, just add the default ones directly to
5451 the trusted dirserver list. This fixes a bug where people running
5452 controllers would use SETCONF on some totally unrelated config
5453 option, and Tor would start yelling at them about changing their
5455 - Let the controller's redirectstream command specify a port, in
5456 case the controller wants to change that too.
5457 - When we requested a pile of server descriptors, we sometimes
5458 accidentally launched a duplicate request for the first one.
5459 - Bugfix for trackhostexits: write down the fingerprint of the
5460 chosen exit, not its nickname, because the chosen exit might not
5462 - When parsing foo.exit, if foo is unknown, and we are leaving
5463 circuits unattached, set the chosen_exit field and leave the
5464 address empty. This matters because controllers got confused
5466 - Directory authorities no longer try to download server
5467 descriptors that they know they will reject.
5469 o Features and updates:
5470 - Replace balanced trees with hash tables: this should make stuff
5471 significantly faster.
5472 - Resume using the AES counter-mode implementation that we ship,
5473 rather than OpenSSL's. Ours is significantly faster.
5474 - Many other CPU and memory improvements.
5475 - Add a new config option FastFirstHopPK (on by default) so clients
5476 do a trivial crypto handshake for their first hop, since TLS has
5477 already taken care of confidentiality and authentication.
5478 - Add a new config option TestSocks so people can see if their
5479 applications are using socks4, socks4a, socks5-with-ip, or
5480 socks5-with-hostname. This way they don't have to keep mucking
5481 with tcpdump and wondering if something got cached somewhere.
5482 - Warn when listening on a public address for socks. I suspect a
5483 lot of people are setting themselves up as open socks proxies,
5484 and they have no idea that jerks on the Internet are using them,
5485 since they simply proxy the traffic into the Tor network.
5486 - Add "private:*" as an alias in configuration for policies. Now
5487 you can simplify your exit policy rather than needing to list
5488 every single internal or nonroutable network space.
5489 - Add a new controller event type that allows controllers to get
5490 all server descriptors that were uploaded to a router in its role
5491 as authoritative dirserver.
5492 - Start shipping socks-extensions.txt, tor-doc-unix.html,
5493 tor-doc-server.html, and stylesheet.css in the tarball.
5494 - Stop shipping tor-doc.html in the tarball.
5497 Changes in version 0.1.1.9-alpha - 2005-11-15
5498 o Usability improvements:
5499 - Start calling it FooListenAddress rather than FooBindAddress,
5500 since few of our users know what it means to bind an address
5502 - Reduce clutter in server logs. We're going to try to make
5503 them actually usable now. New config option ProtocolWarnings that
5504 lets you hear about how _other Tors_ are breaking the protocol. Off
5506 - Divide log messages into logging domains. Once we put some sort
5507 of interface on this, it will let people looking at more verbose
5508 log levels specify the topics they want to hear more about.
5509 - Make directory servers return better http 404 error messages
5510 instead of a generic "Servers unavailable".
5511 - Check for even more Windows version flags when writing the platform
5512 string in server descriptors, and note any we don't recognize.
5513 - Clean up more of the OpenSSL memory when exiting, so we can detect
5514 memory leaks better.
5515 - Make directory authorities be non-versioning, non-naming by
5516 default. Now we can add new directory servers without requiring
5517 their operators to pay close attention.
5518 - When logging via syslog, include the pid whenever we provide
5519 a log entry. Suggested by Todd Fries.
5521 o Performance improvements:
5522 - Directory servers now silently throw away new descriptors that
5523 haven't changed much if the timestamps are similar. We do this to
5524 tolerate older Tor servers that upload a new descriptor every 15
5525 minutes. (It seemed like a good idea at the time.)
5526 - Inline bottleneck smartlist functions; use fast versions by default.
5527 - Add a "Map from digest to void*" abstraction digestmap_t so we
5528 can do less hex encoding/decoding. Use it in router_get_by_digest()
5529 to resolve a performance bottleneck.
5530 - Allow tor_gzip_uncompress to extract as much as possible from
5531 truncated compressed data. Try to extract as many
5532 descriptors as possible from truncated http responses (when
5533 DIR_PURPOSE_FETCH_ROUTERDESC).
5534 - Make circ->onionskin a pointer, not a static array. moria2 was using
5535 125000 circuit_t's after it had been up for a few weeks, which
5536 translates to 20+ megs of wasted space.
5537 - The private half of our EDH handshake keys are now chosen out
5538 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
5540 o Security improvements:
5541 - Start making directory caches retain old routerinfos, so soon
5542 clients can start asking by digest of descriptor rather than by
5543 fingerprint of server.
5544 - Add half our entropy from RAND_poll in OpenSSL. This knows how
5545 to use egd (if present), openbsd weirdness (if present), vms/os2
5546 weirdness (if we ever port there), and more in the future.
5548 o Bugfixes on 0.1.0.x:
5549 - Do round-robin writes of at most 16 kB per write. This might be
5550 more fair on loaded Tor servers, and it might resolve our Windows
5551 crash bug. It might also slow things down.
5552 - Our TLS handshakes were generating a single public/private
5553 keypair for the TLS context, rather than making a new one for
5554 each new connections. Oops. (But we were still rotating them
5555 periodically, so it's not so bad.)
5556 - When we were cannibalizing a circuit with a particular exit
5557 node in mind, we weren't checking to see if that exit node was
5558 already present earlier in the circuit. Oops.
5559 - When a Tor server's IP changes (e.g. from a dyndns address),
5560 upload a new descriptor so clients will learn too.
5561 - Really busy servers were keeping enough circuits open on stable
5562 connections that they were wrapping around the circuit_id
5563 space. (It's only two bytes.) This exposed a bug where we would
5564 feel free to reuse a circuit_id even if it still exists but has
5565 been marked for close. Try to fix this bug. Some bug remains.
5566 - If we would close a stream early (e.g. it asks for a .exit that
5567 we know would refuse it) but the LeaveStreamsUnattached config
5568 option is set by the controller, then don't close it.
5570 o Bugfixes on 0.1.1.8-alpha:
5571 - Fix a big pile of memory leaks, some of them serious.
5572 - Do not try to download a routerdesc if we would immediately reject
5574 - Resume inserting a newline between all router descriptors when
5575 generating (old style) signed directories, since our spec says
5577 - When providing content-type application/octet-stream for
5578 server descriptors using .z, we were leaving out the
5579 content-encoding header. Oops. (Everything tolerated this just
5580 fine, but that doesn't mean we need to be part of the problem.)
5581 - Fix a potential seg fault in getconf and getinfo using version 1
5582 of the controller protocol.
5583 - Avoid crash: do not check whether DirPort is reachable when we
5584 are suppressing it because of hibernation.
5585 - Make --hash-password not crash on exit.
5588 Changes in version 0.1.1.8-alpha - 2005-10-07
5589 o New features (major):
5590 - Clients don't download or use the directory anymore. Now they
5591 download and use network-statuses from the trusted dirservers,
5592 and fetch individual server descriptors as needed from mirrors.
5593 See dir-spec.txt for all the gory details.
5594 - Be more conservative about whether to advertise our DirPort.
5595 The main change is to not advertise if we're running at capacity
5596 and either a) we could hibernate or b) our capacity is low and
5597 we're using a default DirPort.
5598 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
5600 o New features (minor):
5601 - Try to be smart about when to retry network-status and
5602 server-descriptor fetches. Still needs some tuning.
5603 - Stop parsing, storing, or using running-routers output (but
5604 mirrors still cache and serve it).
5605 - Consider a threshold of versioning dirservers (dirservers who have
5606 an opinion about which Tor versions are still recommended) before
5607 deciding whether to warn the user that he's obsolete.
5608 - Dirservers can now reject/invalidate by key and IP, with the
5609 config options "AuthDirInvalid" and "AuthDirReject". This is
5610 useful since currently we automatically list servers as running
5611 and usable even if we know they're jerks.
5612 - Provide dire warnings to any users who set DirServer; move it out
5613 of torrc.sample and into torrc.complete.
5614 - Add MyFamily to torrc.sample in the server section.
5615 - Add nicknames to the DirServer line, so we can refer to them
5616 without requiring all our users to memorize their IP addresses.
5617 - When we get an EOF or a timeout on a directory connection, note
5618 how many bytes of serverdesc we are dropping. This will help
5619 us determine whether it is smart to parse incomplete serverdesc
5621 - Add a new function to "change pseudonyms" -- that is, to stop
5622 using any currently-dirty circuits for new streams, so we don't
5623 link new actions to old actions. Currently it's only called on
5624 HUP (or SIGNAL RELOAD).
5625 - On sighup, if UseHelperNodes changed to 1, use new circuits.
5626 - Start using RAND_bytes rather than RAND_pseudo_bytes from
5627 OpenSSL. Also, reseed our entropy every hour, not just at
5628 startup. And entropy in 512-bit chunks, not 160-bit chunks.
5630 o Fixes on 0.1.1.7-alpha:
5631 - Nobody ever implemented EVENT_ADDRMAP for control protocol
5632 version 0, so don't let version 0 controllers ask for it.
5633 - If you requested something with too many newlines via the
5634 v1 controller protocol, you could crash tor.
5635 - Fix a number of memory leaks, including some pretty serious ones.
5636 - Re-enable DirPort testing again, so Tor servers will be willing
5637 to advertise their DirPort if it's reachable.
5638 - On TLS handshake, only check the other router's nickname against
5639 its expected nickname if is_named is set.
5641 o Fixes forward-ported from 0.1.0.15:
5642 - Don't crash when we don't have any spare file descriptors and we
5643 try to spawn a dns or cpu worker.
5644 - Make the numbers in read-history and write-history into uint64s,
5645 so they don't overflow and publish negatives in the descriptor.
5648 - For the OS X package's modified privoxy config file, comment
5649 out the "logfile" line so we don't log everything passed
5651 - We were whining about using socks4 or socks5-with-local-lookup
5652 even when it's an IP in the "virtual" range we designed exactly
5654 - We were leaking some memory every time the client changes IPs.
5655 - Never call free() on tor_malloc()d memory. This will help us
5656 use dmalloc to detect memory leaks.
5657 - Check for named servers when looking them up by nickname;
5658 warn when we'recalling a non-named server by its nickname;
5659 don't warn twice about the same name.
5660 - Try to list MyFamily elements by key, not by nickname, and warn
5661 if we've not heard of the server.
5662 - Make windows platform detection (uname equivalent) smarter.
5663 - It turns out sparc64 doesn't like unaligned access either.
5666 Changes in version 0.1.0.15 - 2005-09-23
5667 o Bugfixes on 0.1.0.x:
5668 - Reject ports 465 and 587 (spam targets) in default exit policy.
5669 - Don't crash when we don't have any spare file descriptors and we
5670 try to spawn a dns or cpu worker.
5671 - Get rid of IgnoreVersion undocumented config option, and make us
5672 only warn, never exit, when we're running an obsolete version.
5673 - Don't try to print a null string when your server finds itself to
5674 be unreachable and the Address config option is empty.
5675 - Make the numbers in read-history and write-history into uint64s,
5676 so they don't overflow and publish negatives in the descriptor.
5677 - Fix a minor memory leak in smartlist_string_remove().
5678 - We were only allowing ourselves to upload a server descriptor at
5679 most every 20 minutes, even if it changed earlier than that.
5680 - Clean up log entries that pointed to old URLs.
5683 Changes in version 0.1.1.7-alpha - 2005-09-14
5684 o Fixes on 0.1.1.6-alpha:
5685 - Exit servers were crashing when people asked them to make a
5686 connection to an address not in their exit policy.
5687 - Looking up a non-existent stream for a v1 control connection would
5689 - Fix a seg fault if we ask a dirserver for a descriptor by
5690 fingerprint but he doesn't know about him.
5691 - SETCONF was appending items to linelists, not clearing them.
5692 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
5693 out and refuse the setconf if it would fail.
5694 - Downgrade the dirserver log messages when whining about
5698 - Add Peter Palfrader's check-tor script to tor/contrib/
5699 It lets you easily check whether a given server (referenced by
5700 nickname) is reachable by you.
5701 - Numerous changes to move towards client-side v2 directories. Not
5705 - If the user gave tor an odd number of command-line arguments,
5706 we were silently ignoring the last one. Now we complain and fail.
5707 [This wins the oldest-bug prize -- this bug has been present since
5708 November 2002, as released in Tor 0.0.0.]
5709 - Do not use unaligned memory access on alpha, mips, or mipsel.
5710 It *works*, but is very slow, so we treat them as if it doesn't.
5711 - Retry directory requests if we fail to get an answer we like
5712 from a given dirserver (we were retrying before, but only if
5713 we fail to connect).
5714 - When writing the RecommendedVersions line, sort them first.
5715 - When the client asked for a rendezvous port that the hidden
5716 service didn't want to provide, we were sending an IP address
5717 back along with the end cell. Fortunately, it was zero. But stop
5719 - Correct "your server is reachable" log entries to indicate that
5720 it was self-testing that told us so.
5723 Changes in version 0.1.1.6-alpha - 2005-09-09
5724 o Fixes on 0.1.1.5-alpha:
5725 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
5726 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
5727 - Fix bug with tor_memmem finding a match at the end of the string.
5728 - Make unit tests run without segfaulting.
5729 - Resolve some solaris x86 compile warnings.
5730 - Handle duplicate lines in approved-routers files without warning.
5731 - Fix bug where as soon as a server refused any requests due to his
5732 exit policy (e.g. when we ask for localhost and he tells us that's
5733 127.0.0.1 and he won't do it), we decided he wasn't obeying his
5734 exit policy using him for any exits.
5735 - Only do openssl hardware accelerator stuff if openssl version is
5738 o New controller features/fixes:
5739 - Add a "RESETCONF" command so you can set config options like
5740 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
5741 a config option in the torrc with no value, then it clears it
5742 entirely (rather than setting it to its default).
5743 - Add a "GETINFO config-file" to tell us where torrc is.
5744 - Avoid sending blank lines when GETINFO replies should be empty.
5745 - Add a QUIT command for the controller (for using it manually).
5746 - Fix a bug in SAVECONF that was adding default dirservers and
5747 other redundant entries to the torrc file.
5749 o Start on the new directory design:
5750 - Generate, publish, cache, serve new network-status format.
5751 - Publish individual descriptors (by fingerprint, by "all", and by
5753 - Publish client and server recommended versions separately.
5754 - Allow tor_gzip_uncompress() to handle multiple concatenated
5755 compressed strings. Serve compressed groups of router
5756 descriptors. The compression logic here could be more
5758 - Distinguish v1 authorities (all currently trusted directories)
5759 from v2 authorities (all trusted directories).
5760 - Change DirServers config line to note which dirs are v1 authorities.
5761 - Add configuration option "V1AuthoritativeDirectory 1" which
5762 moria1, moria2, and tor26 should set.
5763 - Remove option when getting directory cache to see whether they
5764 support running-routers; they all do now. Replace it with one
5765 to see whether caches support v2 stuff.
5768 - Dirservers now do their own external reachability testing of each
5769 Tor server, and only list them as running if they've been found to
5770 be reachable. We also send back warnings to the server's logs if
5771 it uploads a descriptor that we already believe is unreachable.
5772 - Implement exit enclaves: if we know an IP address for the
5773 destination, and there's a running Tor server at that address
5774 which allows exit to the destination, then extend the circuit to
5775 that exit first. This provides end-to-end encryption and end-to-end
5776 authentication. Also, if the user wants a .exit address or enclave,
5777 use 4 hops rather than 3, and cannibalize a general circ for it
5779 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
5780 controller. Also, rotate dns and cpu workers if the controller
5781 changes options that will affect them; and initialize the dns
5782 worker cache tree whether or not we start out as a server.
5783 - Only upload a new server descriptor when options change, 18
5784 hours have passed, uptime is reset, or bandwidth changes a lot.
5785 - Check [X-]Forwarded-For headers in HTTP requests when generating
5786 log messages. This lets people run dirservers (and caches) behind
5787 Apache but still know which IP addresses are causing warnings.
5789 o Config option changes:
5790 - Replace (Fascist)Firewall* config options with a new
5791 ReachableAddresses option that understands address policies.
5792 For example, "ReachableAddresses *:80,*:443"
5793 - Get rid of IgnoreVersion undocumented config option, and make us
5794 only warn, never exit, when we're running an obsolete version.
5795 - Make MonthlyAccountingStart config option truly obsolete now.
5798 - Reject ports 465 and 587 in the default exit policy, since
5799 people have started using them for spam too.
5800 - It turns out we couldn't bootstrap a network since we added
5801 reachability detection in 0.1.0.1-rc. Good thing the Tor network
5802 has never gone down. Add an AssumeReachable config option to let
5803 servers and dirservers bootstrap. When we're trying to build a
5804 high-uptime or high-bandwidth circuit but there aren't enough
5805 suitable servers, try being less picky rather than simply failing.
5806 - Our logic to decide if the OR we connected to was the right guy
5807 was brittle and maybe open to a mitm for unverified routers.
5808 - We weren't cannibalizing circuits correctly for
5809 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
5810 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
5811 build those from scratch. This should make hidden services faster.
5812 - Predict required circuits better, with an eye toward making hidden
5813 services faster on the service end.
5814 - Retry streams if the exit node sends back a 'misc' failure. This
5815 should result in fewer random failures. Also, after failing
5816 from resolve failed or misc, reset the num failures, so we give
5817 it a fair shake next time we try.
5818 - Clean up the rendezvous warn log msgs, and downgrade some to info.
5819 - Reduce severity on logs about dns worker spawning and culling.
5820 - When we're shutting down and we do something like try to post a
5821 server descriptor or rendezvous descriptor, don't complain that
5822 we seem to be unreachable. Of course we are, we're shutting down.
5823 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
5824 We don't use them yet, but maybe one day our DNS resolver will be
5825 able to discover them.
5826 - Make ContactInfo mandatory for authoritative directory servers.
5827 - Require server descriptors to list IPv4 addresses -- hostnames
5828 are no longer allowed. This also fixes some potential security
5829 problems with people providing hostnames as their address and then
5830 preferentially resolving them to partition users.
5831 - Change log line for unreachability to explicitly suggest /etc/hosts
5832 as the culprit. Also make it clearer what IP address and ports we're
5833 testing for reachability.
5834 - Put quotes around user-supplied strings when logging so users are
5835 more likely to realize if they add bad characters (like quotes)
5837 - Let auth dir servers start without specifying an Address config
5839 - Make unit tests (and other invocations that aren't the real Tor)
5840 run without launching listeners, creating subdirectories, and so on.
5843 Changes in version 0.1.1.5-alpha - 2005-08-08
5844 o Bugfixes included in 0.1.0.14.
5846 o Bugfixes on 0.1.0.x:
5847 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
5848 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
5849 it would silently using ignore the 6668.
5852 Changes in version 0.1.0.14 - 2005-08-08
5853 o Bugfixes on 0.1.0.x:
5854 - Fix the other half of the bug with crypto handshakes
5856 - Fix an assert trigger if you send a 'signal term' via the
5857 controller when it's listening for 'event info' messages.
5860 Changes in version 0.1.1.4-alpha - 2005-08-04
5861 o Bugfixes included in 0.1.0.13.
5864 - Improve tor_gettimeofday() granularity on windows.
5865 - Make clients regenerate their keys when their IP address changes.
5866 - Implement some more GETINFO goodness: expose helper nodes, config
5867 options, getinfo keys.
5870 Changes in version 0.1.0.13 - 2005-08-04
5871 o Bugfixes on 0.1.0.x:
5872 - Fix a critical bug in the security of our crypto handshakes.
5873 - Fix a size_t underflow in smartlist_join_strings2() that made
5874 it do bad things when you hand it an empty smartlist.
5875 - Fix Windows installer to ship Tor license (thanks to Aphex for
5876 pointing out this oversight) and put a link to the doc directory
5878 - Explicitly set no-unaligned-access for sparc: it turns out the
5879 new gcc's let you compile broken code, but that doesn't make it
5883 Changes in version 0.1.1.3-alpha - 2005-07-23
5884 o Bugfixes on 0.1.1.2-alpha:
5885 - Fix a bug in handling the controller's "post descriptor"
5887 - Fix several bugs in handling the controller's "extend circuit"
5889 - Fix a bug in handling the controller's "stream status" event.
5890 - Fix an assert failure if we have a controller listening for
5891 circuit events and we go offline.
5892 - Re-allow hidden service descriptors to publish 0 intro points.
5893 - Fix a crash when generating your hidden service descriptor if
5894 you don't have enough intro points already.
5896 o New features on 0.1.1.2-alpha:
5897 - New controller function "getinfo accounting", to ask how
5898 many bytes we've used in this time period.
5899 - Experimental support for helper nodes: a lot of the risk from
5900 a small static adversary comes because users pick new random
5901 nodes every time they rebuild a circuit. Now users will try to
5902 stick to the same small set of entry nodes if they can. Not
5903 enabled by default yet.
5905 o Bugfixes on 0.1.0.12:
5906 - If you're an auth dir server, always publish your dirport,
5907 even if you haven't yet found yourself to be reachable.
5908 - Fix a size_t underflow in smartlist_join_strings2() that made
5909 it do bad things when you hand it an empty smartlist.
5912 Changes in version 0.1.0.12 - 2005-07-18
5913 o New directory servers:
5914 - tor26 has changed IP address.
5916 o Bugfixes on 0.1.0.x:
5917 - Fix a possible double-free in tor_gzip_uncompress().
5918 - When --disable-threads is set, do not search for or link against
5920 - Don't trigger an assert if an authoritative directory server
5921 claims its dirport is 0.
5922 - Fix bug with removing Tor as an NT service: some people were
5923 getting "The service did not return an error." Thanks to Matt
5927 Changes in version 0.1.1.2-alpha - 2005-07-15
5928 o New directory servers:
5929 - tor26 has changed IP address.
5931 o Bugfixes on 0.1.0.x, crashes/leaks:
5932 - Port the servers-not-obeying-their-exit-policies fix from
5934 - Fix an fd leak in start_daemon().
5935 - On Windows, you can't always reopen a port right after you've
5936 closed it. So change retry_listeners() to only close and re-open
5937 ports that have changed.
5938 - Fix a possible double-free in tor_gzip_uncompress().
5940 o Bugfixes on 0.1.0.x, usability:
5941 - When tor_socketpair() fails in Windows, give a reasonable
5942 Windows-style errno back.
5943 - Let people type "tor --install" as well as "tor -install" when
5945 want to make it an NT service.
5946 - NT service patch from Matt Edman to improve error messages.
5947 - When the controller asks for a config option with an abbreviated
5948 name, give the full name in our response.
5949 - Correct the man page entry on TrackHostExitsExpire.
5950 - Looks like we were never delivering deflated (i.e. compressed)
5951 running-routers lists, even when asked. Oops.
5952 - When --disable-threads is set, do not search for or link against
5955 o Bugfixes on 0.1.1.x:
5956 - Fix a seg fault with autodetecting which controller version is
5960 - New hidden service descriptor format: put a version in it, and
5961 let people specify introduction/rendezvous points that aren't
5962 in "the directory" (which is subjective anyway).
5963 - Allow the DEBUG controller event to work again. Mark certain log
5964 entries as "don't tell this to controllers", so we avoid cycles.
5967 Changes in version 0.1.0.11 - 2005-06-30
5968 o Bugfixes on 0.1.0.x:
5969 - Fix major security bug: servers were disregarding their
5970 exit policies if clients behaved unexpectedly.
5971 - Make OS X init script check for missing argument, so we don't
5972 confuse users who invoke it incorrectly.
5973 - Fix a seg fault in "tor --hash-password foo".
5974 - The MAPADDRESS control command was broken.
5977 Changes in version 0.1.1.1-alpha - 2005-06-29
5979 - Make OS X init script check for missing argument, so we don't
5980 confuse users who invoke it incorrectly.
5981 - Fix a seg fault in "tor --hash-password foo".
5982 - Fix a possible way to DoS dirservers.
5983 - When we complain that your exit policy implicitly allows local or
5984 private address spaces, name them explicitly so operators can
5986 - Make the log message less scary when all the dirservers are
5987 temporarily unreachable.
5988 - We were printing the number of idle dns workers incorrectly when
5992 - Revised controller protocol (version 1) that uses ascii rather
5993 than binary. Add supporting libraries in python and java so you
5994 can use the controller from your applications without caring how
5996 - Spiffy new support for crypto hardware accelerators. Can somebody
6000 Changes in version 0.0.9.10 - 2005-06-16
6001 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
6002 - Refuse relay cells that claim to have a length larger than the
6003 maximum allowed. This prevents a potential attack that could read
6004 arbitrary memory (e.g. keys) from an exit server's process
6008 Changes in version 0.1.0.10 - 2005-06-14
6009 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
6010 libevent before 1.1a.
6013 Changes in version 0.1.0.9-rc - 2005-06-09
6015 - Reset buf->highwater every time buf_shrink() is called, not just on
6016 a successful shrink. This was causing significant memory bloat.
6017 - Fix buffer overflow when checking hashed passwords.
6018 - Security fix: if seeding the RNG on Win32 fails, quit.
6019 - Allow seeding the RNG on Win32 even when you're not running as
6021 - Disable threading on Solaris too. Something is wonky with it,
6022 cpuworkers, and reentrant libs.
6023 - Reenable the part of the code that tries to flush as soon as an
6024 OR outbuf has a full TLS record available. Perhaps this will make
6025 OR outbufs not grow as huge except in rare cases, thus saving lots
6026 of CPU time plus memory.
6027 - Reject malformed .onion addresses rather then passing them on as
6028 normal web requests.
6029 - Adapt patch from Adam Langley: fix possible memory leak in
6030 tor_lookup_hostname().
6031 - Initialize libevent later in the startup process, so the logs are
6032 already established by the time we start logging libevent warns.
6033 - Use correct errno on win32 if libevent fails.
6034 - Check and warn about known-bad/slow libevent versions.
6035 - Pay more attention to the ClientOnly config option.
6036 - Have torctl.in/tor.sh.in check for location of su binary (needed
6038 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
6039 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
6040 HttpProxyAuthenticator
6041 - Stop warning about sigpipes in the logs. We're going to
6042 pretend that getting these occassionally is normal and fine.
6043 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
6045 installer screens; and don't put stuff into StartupItems unless
6046 the user asks you to.
6047 - Require servers that use the default dirservers to have public IP
6048 addresses. We have too many servers that are configured with private
6049 IPs and their admins never notice the log entries complaining that
6050 their descriptors are being rejected.
6051 - Add OSX uninstall instructions. An actual uninstall script will
6055 Changes in version 0.1.0.8-rc - 2005-05-23
6057 - It turns out that kqueue on OS X 10.3.9 was causing kernel
6058 panics. Disable kqueue on all OS X Tors.
6059 - Fix RPM: remove duplicate line accidentally added to the rpm
6061 - Disable threads on openbsd too, since its gethostaddr is not
6063 - Tolerate libevent 0.8 since it still works, even though it's
6065 - Enable building on Red Hat 9.0 again.
6066 - Allow the middle hop of the testing circuit to be running any
6067 version, now that most of them have the bugfix to let them connect
6068 to unknown servers. This will allow reachability testing to work
6069 even when 0.0.9.7-0.0.9.9 become obsolete.
6070 - Handle relay cells with rh.length too large. This prevents
6071 a potential attack that could read arbitrary memory (maybe even
6072 keys) from the exit server's process.
6073 - We screwed up the dirport reachability testing when we don't yet
6074 have a cached version of the directory. Hopefully now fixed.
6075 - Clean up router_load_single_router() (used by the controller),
6076 so it doesn't seg fault on error.
6077 - Fix a minor memory leak when somebody establishes an introduction
6078 point at your Tor server.
6079 - If a socks connection ends because read fails, don't warn that
6080 you're not sending a socks reply back.
6083 - Add HttpProxyAuthenticator config option too, that works like
6084 the HttpsProxyAuthenticator config option.
6085 - Encode hashed controller passwords in hex instead of base64,
6086 to make it easier to write controllers.
6089 Changes in version 0.1.0.7-rc - 2005-05-17
6091 - Fix a bug in the OS X package installer that prevented it from
6092 installing on Tiger.
6093 - Fix a script bug in the OS X package installer that made it
6094 complain during installation.
6095 - Find libevent even if it's hiding in /usr/local/ and your
6096 CFLAGS and LDFLAGS don't tell you to look there.
6097 - Be able to link with libevent as a shared library (the default
6098 after 1.0d), even if it's hiding in /usr/local/lib and even
6099 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
6100 assuming you're running gcc. Otherwise fail and give a useful
6102 - Fix a bug in the RPM packager: set home directory for _tor to
6103 something more reasonable when first installing.
6104 - Free a minor amount of memory that is still reachable on exit.
6107 Changes in version 0.1.0.6-rc - 2005-05-14
6109 - Implement --disable-threads configure option. Disable threads on
6110 netbsd by default, because it appears to have no reentrant resolver
6112 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
6113 release (1.1) detects and disables kqueue if it's broken.
6114 - Append default exit policy before checking for implicit internal
6115 addresses. Now we don't log a bunch of complaints on startup
6116 when using the default exit policy.
6117 - Some people were putting "Address " in their torrc, and they had
6118 a buggy resolver that resolved " " to 0.0.0.0. Oops.
6119 - If DataDir is ~/.tor, and that expands to /.tor, then default to
6120 LOCALSTATEDIR/tor instead.
6121 - Fix fragmented-message bug in TorControl.py.
6122 - Resolve a minor bug which would prevent unreachable dirports
6123 from getting suppressed in the published descriptor.
6124 - When the controller gave us a new descriptor, we weren't resolving
6125 it immediately, so Tor would think its address was 0.0.0.0 until
6126 we fetched a new directory.
6127 - Fix an uppercase/lowercase case error in suppressing a bogus
6128 libevent warning on some Linuxes.
6131 - Begin scrubbing sensitive strings from logs by default. Turn off
6132 the config option SafeLogging if you need to do debugging.
6133 - Switch to a new buffer management algorithm, which tries to avoid
6134 reallocing and copying quite as much. In first tests it looks like
6135 it uses *more* memory on average, but less cpu.
6136 - First cut at support for "create-fast" cells. Clients can use
6137 these when extending to their first hop, since the TLS already
6138 provides forward secrecy and authentication. Not enabled on
6140 - When dirservers refuse a router descriptor, we now log its
6141 contactinfo, platform, and the poster's IP address.
6142 - Call tor_free_all instead of connections_free_all after forking, to
6143 save memory on systems that need to fork.
6144 - Whine at you if you're a server and you don't set your contactinfo.
6145 - Implement --verify-config command-line option to check if your torrc
6146 is valid without actually launching Tor.
6147 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
6148 rather than just rejecting it.
6151 Changes in version 0.1.0.5-rc - 2005-04-27
6153 - Stop trying to print a null pointer if an OR conn fails because
6154 we didn't like its cert.
6156 - Switch our internal buffers implementation to use a ring buffer,
6157 to hopefully improve performance for fast servers a lot.
6158 - Add HttpsProxyAuthenticator support (basic auth only), based
6159 on patch from Adam Langley.
6160 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
6161 the fast servers that have been joining lately.
6162 - Give hidden service accesses extra time on the first attempt,
6163 since 60 seconds is often only barely enough. This might improve
6165 - Improve performance for dirservers: stop re-parsing the whole
6166 directory every time you regenerate it.
6167 - Add more debugging info to help us find the weird dns freebsd
6168 pthreads bug; cleaner debug messages to help track future issues.
6171 Changes in version 0.0.9.9 - 2005-04-23
6172 o Bugfixes on 0.0.9.x:
6173 - If unofficial Tor clients connect and send weird TLS certs, our
6174 Tor server triggers an assert. This release contains a minimal
6175 backport from the broader fix that we put into 0.1.0.4-rc.
6178 Changes in version 0.1.0.4-rc - 2005-04-23
6180 - If unofficial Tor clients connect and send weird TLS certs, our
6181 Tor server triggers an assert. Stop asserting, and start handling
6182 TLS errors better in other situations too.
6183 - When the controller asks us to tell it about all the debug-level
6184 logs, it turns out we were generating debug-level logs while
6185 telling it about them, which turns into a bad loop. Now keep
6186 track of whether you're sending a debug log to the controller,
6187 and don't log when you are.
6188 - Fix the "postdescriptor" feature of the controller interface: on
6189 non-complete success, only say "done" once.
6191 - Clients are now willing to load balance over up to 2mB, not 1mB,
6192 of advertised bandwidth capacity.
6193 - Add a NoPublish config option, so you can be a server (e.g. for
6194 testing running Tor servers in other Tor networks) without
6195 publishing your descriptor to the primary dirservers.
6198 Changes in version 0.1.0.3-rc - 2005-04-08
6199 o Improvements on 0.1.0.2-rc:
6200 - Client now retries when streams end early for 'hibernating' or
6201 'resource limit' reasons, rather than failing them.
6202 - More automated handling for dirserver operators:
6203 - Automatically approve nodes running 0.1.0.2-rc or later,
6204 now that the the reachability detection stuff is working.
6205 - Now we allow two unverified servers with the same nickname
6206 but different keys. But if a nickname is verified, only that
6207 nickname+key are allowed.
6208 - If you're an authdirserver connecting to an address:port,
6209 and it's not the OR you were expecting, forget about that
6210 descriptor. If he *was* the one you were expecting, then forget
6211 about all other descriptors for that address:port.
6212 - Allow servers to publish descriptors from 12 hours in the future.
6213 Corollary: only whine about clock skew from the dirserver if
6214 he's a trusted dirserver (since now even verified servers could
6215 have quite wrong clocks).
6216 - Adjust maximum skew and age for rendezvous descriptors: let skew
6217 be 48 hours rather than 90 minutes.
6218 - Efficiency improvements:
6219 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
6220 it much faster to look up a circuit for each relay cell.
6221 - Remove most calls to assert_all_pending_dns_resolves_ok(),
6222 since they're eating our cpu on exit nodes.
6223 - Stop wasting time doing a case insensitive comparison for every
6224 dns name every time we do any lookup. Canonicalize the names to
6225 lowercase and be done with it.
6226 - Start sending 'truncated' cells back rather than destroy cells,
6227 if the circuit closes in front of you. This means we won't have
6228 to abandon partially built circuits.
6229 - Only warn once per nickname from add_nickname_list_to_smartlist
6230 per failure, so an entrynode or exitnode choice that's down won't
6232 - Put a note in the torrc about abuse potential with the default
6234 - Revise control spec and implementation to allow all log messages to
6235 be sent to controller with their severities intact (suggested by
6236 Matt Edman). Update TorControl to handle new log event types.
6237 - Provide better explanation messages when controller's POSTDESCRIPTOR
6239 - Stop putting nodename in the Platform string in server descriptors.
6240 It doesn't actually help, and it is confusing/upsetting some people.
6242 o Bugfixes on 0.1.0.2-rc:
6243 - We were printing the host mask wrong in exit policies in server
6244 descriptors. This isn't a critical bug though, since we were still
6245 obeying the exit policy internally.
6246 - Fix Tor when compiled with libevent but without pthreads: move
6247 connection_unregister() from _connection_free() to
6249 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
6250 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
6251 when we look through the connection array, we'll find any of the
6252 cpu/dnsworkers. This is no good.
6254 o Bugfixes on 0.0.9.8:
6255 - Fix possible bug on threading platforms (e.g. win32) which was
6256 leaking a file descriptor whenever a cpuworker or dnsworker died.
6257 - When using preferred entry or exit nodes, ignore whether the
6258 circuit wants uptime or capacity. They asked for the nodes, they
6260 - chdir() to your datadirectory at the *end* of the daemonize process,
6261 not the beginning. This was a problem because the first time you
6262 run tor, if your datadir isn't there, and you have runasdaemon set
6263 to 1, it will try to chdir to it before it tries to create it. Oops.
6264 - Handle changed router status correctly when dirserver reloads
6265 fingerprint file. We used to be dropping all unverified descriptors
6266 right then. The bug was hidden because we would immediately
6267 fetch a directory from another dirserver, which would include the
6268 descriptors we just dropped.
6269 - When we're connecting to an OR and he's got a different nickname/key
6270 than we were expecting, only complain loudly if we're an OP or a
6271 dirserver. Complaining loudly to the OR admins just confuses them.
6272 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
6273 artificially capped at 500kB.
6276 Changes in version 0.0.9.8 - 2005-04-07
6277 o Bugfixes on 0.0.9.x:
6278 - We have a bug that I haven't found yet. Sometimes, very rarely,
6279 cpuworkers get stuck in the 'busy' state, even though the cpuworker
6280 thinks of itself as idle. This meant that no new circuits ever got
6281 established. Here's a workaround to kill any cpuworker that's been
6282 busy for more than 100 seconds.
6285 Changes in version 0.1.0.2-rc - 2005-04-01
6286 o Bugfixes on 0.1.0.1-rc:
6287 - Fixes on reachability detection:
6288 - Don't check for reachability while hibernating.
6289 - If ORPort is reachable but DirPort isn't, still publish the
6290 descriptor, but zero out DirPort until it's found reachable.
6291 - When building testing circs for ORPort testing, use only
6292 high-bandwidth nodes, so fewer circuits fail.
6293 - Complain about unreachable ORPort separately from unreachable
6294 DirPort, so the user knows what's going on.
6295 - Make sure we only conclude ORPort reachability if we didn't
6296 initiate the conn. Otherwise we could falsely conclude that
6297 we're reachable just because we connected to the guy earlier
6298 and he used that same pipe to extend to us.
6299 - Authdirservers shouldn't do ORPort reachability detection,
6300 since they're in clique mode, so it will be rare to find a
6301 server not already connected to them.
6302 - When building testing circuits, always pick middle hops running
6303 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
6304 bug. (This is a kludge; it will go away when 0.0.9.x becomes
6306 - When we decide we're reachable, actually publish our descriptor
6308 - Fix bug in redirectstream in the controller.
6309 - Fix the state descriptor strings so logs don't claim edge streams
6310 are in a different state than they actually are.
6311 - Use recent libevent features when possible (this only really affects
6312 win32 and osx right now, because the new libevent with these
6313 features hasn't been released yet). Add code to suppress spurious
6315 - Prevent possible segfault in connection_close_unattached_ap().
6316 - Fix newlines on torrc in win32.
6317 - Improve error msgs when tor-resolve fails.
6319 o Improvements on 0.0.9.x:
6320 - New experimental script tor/contrib/ExerciseServer.py (needs more
6321 work) that uses the controller interface to build circuits and
6322 fetch pages over them. This will help us bootstrap servers that
6323 have lots of capacity but haven't noticed it yet.
6324 - New experimental script tor/contrib/PathDemo.py (needs more work)
6325 that uses the controller interface to let you choose whole paths
6327 "<hostname>.<path,separated by dots>.<length of path>.path"
6328 - When we've connected to an OR and handshaked but didn't like
6329 the result, we were closing the conn without sending destroy
6330 cells back for pending circuits. Now send those destroys.
6333 Changes in version 0.0.9.7 - 2005-04-01
6334 o Bugfixes on 0.0.9.x:
6335 - Fix another race crash bug (thanks to Glenn Fink for reporting).
6336 - Compare identity to identity, not to nickname, when extending to
6337 a router not already in the directory. This was preventing us from
6338 extending to unknown routers. Oops.
6339 - Make sure to create OS X Tor user in <500 range, so we aren't
6340 creating actual system users.
6341 - Note where connection-that-hasn't-sent-end was marked, and fix
6342 a few really loud instances of this harmless bug (it's fixed more
6346 Changes in version 0.1.0.1-rc - 2005-03-28
6348 - Add reachability testing. Your Tor server will automatically try
6349 to see if its ORPort and DirPort are reachable from the outside,
6350 and it won't upload its descriptor until it decides they are.
6351 - Handle unavailable hidden services better. Handle slow or busy
6352 hidden services better.
6353 - Add support for CONNECTing through https proxies, with "HttpsProxy"
6355 - New exit policy: accept most low-numbered ports, rather than
6356 rejecting most low-numbered ports.
6357 - More Tor controller support (still experimental). See
6358 http://tor.eff.org/doc/control-spec.txt for all the new features,
6359 including signals to emulate unix signals from any platform;
6360 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
6361 closestream; closecircuit; etc.
6362 - Make nt services work and start on startup on win32 (based on
6363 patch by Matt Edman).
6364 - Add a new AddressMap config directive to rewrite incoming socks
6365 addresses. This lets you, for example, declare an implicit
6366 required exit node for certain sites.
6367 - Add a new TrackHostExits config directive to trigger addressmaps
6368 for certain incoming socks addresses -- for sites that break when
6369 your exit keeps changing (based on patch by Mike Perry).
6370 - Redo the client-side dns cache so it's just an addressmap too.
6371 - Notice when our IP changes, and reset stats/uptime/reachability.
6372 - When an application is using socks5, give him the whole variety of
6373 potential socks5 responses (connect refused, host unreachable, etc),
6374 rather than just "success" or "failure".
6375 - A more sane version numbering system. See
6376 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
6377 - New contributed script "exitlist": a simple python script to
6378 parse directories and find Tor nodes that exit to listed
6380 - New contributed script "privoxy-tor-toggle" to toggle whether
6381 Privoxy uses Tor. Seems to be configured for Debian by default.
6382 - Report HTTP reasons to client when getting a response from directory
6383 servers -- so you can actually know what went wrong.
6384 - New config option MaxAdvertisedBandwidth which lets you advertise
6385 a low bandwidthrate (to not attract as many circuits) while still
6386 allowing a higher bandwidthrate in reality.
6388 o Robustness/stability fixes:
6389 - Make Tor use Niels Provos's libevent instead of its current
6390 poll-but-sometimes-select mess. This will let us use faster async
6391 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
6393 - pthread support now too. This was forced because when we forked,
6394 we ended up wasting a lot of duplicate ram over time. Also switch
6395 to foo_r versions of some library calls to allow reentry and
6397 - Better handling for heterogeneous / unreliable nodes:
6398 - Annotate circuits w/ whether they aim to contain high uptime nodes
6399 and/or high capacity nodes. When building circuits, choose
6401 - This means that every single node in an intro rend circuit,
6402 not just the last one, will have a minimum uptime.
6403 - New config option LongLivedPorts to indicate application streams
6404 that will want high uptime circuits.
6405 - Servers reset uptime when a dir fetch entirely fails. This
6406 hopefully reflects stability of the server's network connectivity.
6407 - If somebody starts his tor server in Jan 2004 and then fixes his
6408 clock, don't make his published uptime be a year.
6409 - Reset published uptime when you wake up from hibernation.
6410 - Introduce a notion of 'internal' circs, which are chosen without
6411 regard to the exit policy of the last hop. Intro and rendezvous
6412 circs must be internal circs, to avoid leaking information. Resolve
6413 and connect streams can use internal circs if they want.
6414 - New circuit pooling algorithm: make sure to have enough circs around
6415 to satisfy any predicted ports, and also make sure to have 2 internal
6416 circs around if we've required internal circs lately (and with high
6417 uptime if we've seen that lately too).
6418 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
6419 which describes how often we retry making new circuits if current
6420 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
6421 how long we're willing to make use of an already-dirty circuit.
6422 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
6423 circ as necessary, if there are any completed ones lying around
6424 when we try to launch one.
6425 - Make hidden services try to establish a rendezvous for 30 seconds,
6426 rather than for n (where n=3) attempts to build a circuit.
6427 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
6428 "ShutdownWaitLength".
6429 - Try to be more zealous about calling connection_edge_end when
6430 things go bad with edge conns in connection.c.
6431 - Revise tor-spec to add more/better stream end reasons.
6432 - Revise all calls to connection_edge_end to avoid sending "misc",
6433 and to take errno into account where possible.
6436 - Fix a race condition that can trigger an assert, when we have a
6437 pending create cell and an OR connection fails right then.
6438 - Fix several double-mark-for-close bugs, e.g. where we were finding
6439 a conn for a cell even if that conn is already marked for close.
6440 - Make sequence of log messages when starting on win32 with no config
6441 file more reasonable.
6442 - When choosing an exit node for a new non-internal circ, don't take
6443 into account whether it'll be useful for any pending x.onion
6444 addresses -- it won't.
6445 - Turn addr_policy_compare from a tristate to a quadstate; this should
6446 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
6447 for google.com" problem.
6448 - Make "platform" string in descriptor more accurate for Win32 servers,
6449 so it's not just "unknown platform".
6450 - Fix an edge case in parsing config options (thanks weasel).
6451 If they say "--" on the commandline, it's not an option.
6452 - Reject odd-looking addresses at the client (e.g. addresses that
6453 contain a colon), rather than having the server drop them because
6455 - tor-resolve requests were ignoring .exit if there was a working circuit
6456 they could use instead.
6457 - REUSEADDR on normal platforms means you can rebind to the port
6458 right after somebody else has let it go. But REUSEADDR on win32
6459 means to let you bind to the port _even when somebody else
6460 already has it bound_! So, don't do that on Win32.
6461 - Change version parsing logic: a version is "obsolete" if it is not
6462 recommended and (1) there is a newer recommended version in the
6463 same series, or (2) there are no recommended versions in the same
6464 series, but there are some recommended versions in a newer series.
6465 A version is "new" if it is newer than any recommended version in
6467 - Stop most cases of hanging up on a socks connection without sending
6471 - Require BandwidthRate to be at least 20kB/s for servers.
6472 - When a dirserver causes you to give a warn, mention which dirserver
6474 - New config option DirAllowPrivateAddresses for authdirservers.
6475 Now by default they refuse router descriptors that have non-IP or
6476 private-IP addresses.
6477 - Stop publishing socksport in the directory, since it's not
6478 actually meant to be public. For compatibility, publish a 0 there
6480 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
6481 smart" value, that is low for servers and high for clients.
6482 - If our clock jumps forward by 100 seconds or more, assume something
6483 has gone wrong with our network and abandon all not-yet-used circs.
6484 - Warn when exit policy implicitly allows local addresses.
6485 - If we get an incredibly skewed timestamp from a dirserver mirror
6486 that isn't a verified OR, don't warn -- it's probably him that's
6488 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
6489 cookies to disk and doesn't log each web request to disk. (Thanks
6490 to Brett Carrington for pointing this out.)
6491 - When a client asks us for a dir mirror and we don't have one,
6492 launch an attempt to get a fresh one.
6493 - If we're hibernating and we get a SIGINT, exit immediately.
6494 - Add --with-dmalloc ./configure option, to track memory leaks.
6495 - And try to free all memory on closing, so we can detect what
6497 - Cache local dns resolves correctly even when they're .exit
6499 - Give a better warning when some other server advertises an
6500 ORPort that is actually an apache running ssl.
6501 - Add "opt hibernating 1" to server descriptor to make it clearer
6502 whether the server is hibernating.
6505 Changes in version 0.0.9.6 - 2005-03-24
6506 o Bugfixes on 0.0.9.x (crashes and asserts):
6507 - Add new end stream reasons to maintainance branch. Fix bug where
6508 reason (8) could trigger an assert. Prevent bug from recurring.
6509 - Apparently win32 stat wants paths to not end with a slash.
6510 - Fix assert triggers in assert_cpath_layer_ok(), where we were
6511 blowing away the circuit that conn->cpath_layer points to, then
6512 checking to see if the circ is well-formed. Backport check to make
6513 sure we dont use the cpath on a closed connection.
6514 - Prevent circuit_resume_edge_reading_helper() from trying to package
6515 inbufs for marked-for-close streams.
6516 - Don't crash on hup if your options->address has become unresolvable.
6517 - Some systems (like OS X) sometimes accept() a connection and tell
6518 you the remote host is 0.0.0.0:0. If this happens, due to some
6519 other mis-features, we get confused; so refuse the conn for now.
6521 o Bugfixes on 0.0.9.x (other):
6522 - Fix harmless but scary "Unrecognized content encoding" warn message.
6523 - Add new stream error reason: TORPROTOCOL reason means "you are not
6524 speaking a version of Tor I understand; say bye-bye to your stream."
6525 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
6526 into the future, now that we are more tolerant of skew. This
6527 resolves a bug where a Tor server would refuse to cache a directory
6528 because all the directories it gets are too far in the future;
6529 yet the Tor server never logs any complaints about clock skew.
6530 - Mac packaging magic: make man pages useable, and do not overwrite
6531 existing torrc files.
6532 - Make OS X log happily to /var/log/tor/tor.log
6535 Changes in version 0.0.9.5 - 2005-02-22
6536 o Bugfixes on 0.0.9.x:
6537 - Fix an assert race at exit nodes when resolve requests fail.
6538 - Stop picking unverified dir mirrors--it only leads to misery.
6539 - Patch from Matt Edman to make NT services work better. Service
6540 support is still not compiled into the executable by default.
6541 - Patch from Dmitri Bely so the Tor service runs better under
6542 the win32 SYSTEM account.
6543 - Make tor-resolve actually work (?) on Win32.
6544 - Fix a sign bug when getrlimit claims to have 4+ billion
6545 file descriptors available.
6546 - Stop refusing to start when bandwidthburst == bandwidthrate.
6547 - When create cells have been on the onion queue more than five
6548 seconds, just send back a destroy and take them off the list.
6551 Changes in version 0.0.9.4 - 2005-02-03
6552 o Bugfixes on 0.0.9:
6553 - Fix an assert bug that took down most of our servers: when
6554 a server claims to have 1 GB of bandwidthburst, don't
6556 - Don't crash as badly if we have spawned the max allowed number
6557 of dnsworkers, or we're out of file descriptors.
6558 - Block more file-sharing ports in the default exit policy.
6559 - MaxConn is now automatically set to the hard limit of max
6560 file descriptors we're allowed (ulimit -n), minus a few for
6562 - Give a clearer message when servers need to raise their
6563 ulimit -n when they start running out of file descriptors.
6564 - SGI Compatibility patches from Jan Schaumann.
6565 - Tolerate a corrupt cached directory better.
6566 - When a dirserver hasn't approved your server, list which one.
6567 - Go into soft hibernation after 95% of the bandwidth is used,
6568 not 99%. This is especially important for daily hibernators who
6569 have a small accounting max. Hopefully it will result in fewer
6570 cut connections when the hard hibernation starts.
6571 - Load-balance better when using servers that claim more than
6572 800kB/s of capacity.
6573 - Make NT services work (experimental, only used if compiled in).
6576 Changes in version 0.0.9.3 - 2005-01-21
6577 o Bugfixes on 0.0.9:
6578 - Backport the cpu use fixes from main branch, so busy servers won't
6579 need as much processor time.
6580 - Work better when we go offline and then come back, or when we
6581 run Tor at boot before the network is up. We do this by
6582 optimistically trying to fetch a new directory whenever an
6583 application request comes in and we think we're offline -- the
6584 human is hopefully a good measure of when the network is back.
6585 - Backport some minimal hidserv bugfixes: keep rend circuits open as
6586 long as you keep using them; actually publish hidserv descriptors
6587 shortly after they change, rather than waiting 20-40 minutes.
6588 - Enable Mac startup script by default.
6589 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
6590 - When you update AllowUnverifiedNodes or FirewallPorts via the
6591 controller's setconf feature, we were always appending, never
6593 - When you update HiddenServiceDir via setconf, it was screwing up
6594 the order of reading the lines, making it fail.
6595 - Do not rewrite a cached directory back to the cache; otherwise we
6596 will think it is recent and not fetch a newer one on startup.
6597 - Workaround for webservers that lie about Content-Encoding: Tor
6598 now tries to autodetect compressed directories and compression
6599 itself. This lets us Proxypass dir fetches through apache.
6602 Changes in version 0.0.9.2 - 2005-01-04
6603 o Bugfixes on 0.0.9 (crashes and asserts):
6604 - Fix an assert on startup when the disk is full and you're logging
6606 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
6607 style address, then we'd crash.
6608 - Fix an assert trigger when the running-routers string we get from
6609 a dirserver is broken.
6610 - Make worker threads start and run on win32. Now win32 servers
6612 - Bandaid (not actually fix, but now it doesn't crash) an assert
6613 where the dns worker dies mysteriously and the main Tor process
6614 doesn't remember anything about the address it was resolving.
6616 o Bugfixes on 0.0.9 (Win32):
6617 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
6618 name out of the warning/assert messages.
6619 - Fix a superficial "unhandled error on read" bug on win32.
6620 - The win32 installer no longer requires a click-through for our
6621 license, since our Free Software license grants rights but does not
6623 - Win32: When connecting to a dirserver fails, try another one
6624 immediately. (This was already working for non-win32 Tors.)
6625 - Stop trying to parse $HOME on win32 when hunting for default
6627 - Make tor-resolve.c work on win32 by calling network_init().
6629 o Bugfixes on 0.0.9 (other):
6630 - Make 0.0.9.x build on Solaris again.
6631 - Due to a fencepost error, we were blowing away the \n when reporting
6632 confvalue items in the controller. So asking for multiple config
6633 values at once couldn't work.
6634 - When listing circuits that are pending on an opening OR connection,
6635 if we're an OR we were listing circuits that *end* at us as
6636 being pending on every listener, dns/cpu worker, etc. Stop that.
6637 - Dirservers were failing to create 'running-routers' or 'directory'
6638 strings if we had more than some threshold of routers. Fix them so
6639 they can handle any number of routers.
6640 - Fix a superficial "Duplicate mark for close" bug.
6641 - Stop checking for clock skew for OR connections, even for servers.
6642 - Fix a fencepost error that was chopping off the last letter of any
6643 nickname that is the maximum allowed nickname length.
6644 - Update URLs in log messages so they point to the new website.
6645 - Fix a potential problem in mangling server private keys while
6646 writing to disk (not triggered yet, as far as we know).
6647 - Include the licenses for other free software we include in Tor,
6648 now that we're shipping binary distributions more regularly.
6651 Changes in version 0.0.9.1 - 2004-12-15
6652 o Bugfixes on 0.0.9:
6653 - Make hibernation actually work.
6654 - Make HashedControlPassword config option work.
6655 - When we're reporting event circuit status to a controller,
6656 don't use the stream status code.
6659 Changes in version 0.0.9 - 2004-12-12
6661 - Clean up manpage and torrc.sample file.
6662 - Clean up severities and text of log warnings.
6664 - Make servers trigger an assert when they enter hibernation.
6667 Changes in version 0.0.9rc7 - 2004-12-08
6668 o Bugfixes on 0.0.9rc:
6669 - Fix a stack-trashing crash when an exit node begins hibernating.
6670 - Avoid looking at unallocated memory while considering which
6671 ports we need to build circuits to cover.
6672 - Stop a sigpipe: when an 'end' cell races with eof from the app,
6673 we shouldn't hold-open-until-flush if the eof arrived first.
6674 - Fix a bug with init_cookie_authentication() in the controller.
6675 - When recommending new-format log lines, if the upper bound is
6676 LOG_ERR, leave it implicit.
6678 o Bugfixes on 0.0.8.1:
6679 - Fix a whole slew of memory leaks.
6680 - Fix isspace() and friends so they still make Solaris happy
6681 but also so they don't trigger asserts on win32.
6682 - Fix parse_iso_time on platforms without strptime (eg win32).
6683 - win32: tolerate extra "readable" events better.
6684 - win32: when being multithreaded, leave parent fdarray open.
6685 - Make unit tests work on win32.
6688 Changes in version 0.0.9rc6 - 2004-12-06
6689 o Bugfixes on 0.0.9pre:
6690 - Clean up some more integer underflow opportunities (not exploitable
6692 - While hibernating, hup should not regrow our listeners.
6693 - Send an end to the streams we close when we hibernate, rather
6694 than just chopping them off.
6695 - React to eof immediately on non-open edge connections.
6697 o Bugfixes on 0.0.8.1:
6698 - Calculate timeout for waiting for a connected cell from the time
6699 we sent the begin cell, not from the time the stream started. If
6700 it took a long time to establish the circuit, we would time out
6701 right after sending the begin cell.
6702 - Fix router_compare_addr_to_addr_policy: it was not treating a port
6703 of * as always matching, so we were picking reject *:* nodes as
6704 exit nodes too. Oops.
6707 - New circuit building strategy: keep a list of ports that we've
6708 used in the past 6 hours, and always try to have 2 circuits open
6709 or on the way that will handle each such port. Seed us with port
6710 80 so web users won't complain that Tor is "slow to start up".
6711 - Make kill -USR1 dump more useful stats about circuits.
6712 - When warning about retrying or giving up, print the address, so
6713 the user knows which one it's talking about.
6714 - If you haven't used a clean circuit in an hour, throw it away,
6715 just to be on the safe side. (This means after 6 hours a totally
6716 unused Tor client will have no circuits open.)
6719 Changes in version 0.0.9rc5 - 2004-12-01
6720 o Bugfixes on 0.0.8.1:
6721 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
6722 - Let resolve conns retry/expire also, rather than sticking around
6724 - If we are using select, make sure we stay within FD_SETSIZE.
6726 o Bugfixes on 0.0.9pre:
6727 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
6728 but doesn't seem to be currently; thanks to Ilja van Sprundel for
6730 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
6731 instead. Impose minima and maxima for all *Period options; impose
6732 even tighter maxima for fetching if we are a caching dirserver.
6733 Clip rather than rejecting.
6734 - Fetch cached running-routers from servers that serve it (that is,
6735 authdirservers and servers running 0.0.9rc5-cvs or later.)
6738 - Accept *:706 (silc) in default exit policy.
6739 - Implement new versioning format for post 0.1.
6740 - Support "foo.nickname.exit" addresses, to let Alice request the
6741 address "foo" as viewed by exit node "nickname". Based on a patch
6743 - Make tor --version --version dump the cvs Id of every file.
6746 Changes in version 0.0.9rc4 - 2004-11-28
6747 o Bugfixes on 0.0.8.1:
6748 - Make windows sockets actually non-blocking (oops), and handle
6749 win32 socket errors better.
6751 o Bugfixes on 0.0.9rc1:
6752 - Actually catch the -USR2 signal.
6755 Changes in version 0.0.9rc3 - 2004-11-25
6756 o Bugfixes on 0.0.8.1:
6757 - Flush the log file descriptor after we print "Tor opening log file",
6758 so we don't see those messages days later.
6760 o Bugfixes on 0.0.9rc1:
6761 - Make tor-resolve work again.
6762 - Avoid infinite loop in tor-resolve if tor hangs up on it.
6763 - Fix an assert trigger for clients/servers handling resolves.
6766 Changes in version 0.0.9rc2 - 2004-11-24
6767 o Bugfixes on 0.0.9rc1:
6768 - I broke socks5 support while fixing the eof bug.
6769 - Allow unitless bandwidths and intervals; they default to bytes
6771 - New servers don't start out hibernating; they are active until
6772 they run out of bytes, so they have a better estimate of how
6773 long it takes, and so their operators can know they're working.
6776 Changes in version 0.0.9rc1 - 2004-11-23
6777 o Bugfixes on 0.0.8.1:
6778 - Finally fix a bug that's been plaguing us for a year:
6779 With high load, circuit package window was reaching 0. Whenever
6780 we got a circuit-level sendme, we were reading a lot on each
6781 socket, but only writing out a bit. So we would eventually reach
6782 eof. This would be noticed and acted on even when there were still
6783 bytes sitting in the inbuf.
6784 - When poll() is interrupted, we shouldn't believe the revents values.
6786 o Bugfixes on 0.0.9pre6:
6787 - Fix hibernate bug that caused pre6 to be broken.
6788 - Don't keep rephist info for routers that haven't had activity for
6789 24 hours. (This matters now that clients have keys, since we track
6791 - Never call close_temp_logs while validating log options.
6792 - Fix backslash-escaping on tor.sh.in and torctl.in.
6795 - Implement weekly/monthly/daily accounting: now you specify your
6796 hibernation properties by
6797 AccountingMax N bytes|KB|MB|GB|TB
6798 AccountingStart day|week|month [day] HH:MM
6799 Defaults to "month 1 0:00".
6800 - Let bandwidth and interval config options be specified as 5 bytes,
6801 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
6802 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
6803 get back to normal.)
6804 - If your requested entry or exit node has advertised bandwidth 0,
6806 - Be more greedy about filling up relay cells -- we try reading again
6807 once we've processed the stuff we read, in case enough has arrived
6808 to fill the last cell completely.
6809 - Apply NT service patch from Osamu Fujino. Still needs more work.
6812 Changes in version 0.0.9pre6 - 2004-11-15
6813 o Bugfixes on 0.0.8.1:
6814 - Fix assert failure on malformed socks4a requests.
6815 - Use identity comparison, not nickname comparison, to choose which
6816 half of circuit-ID-space each side gets to use. This is needed
6817 because sometimes we think of a router as a nickname, and sometimes
6818 as a hex ID, and we can't predict what the other side will do.
6819 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
6820 write() call will fail and we handle it there.
6821 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
6822 and smartlist_len, which are two major profiling offenders.
6824 o Bugfixes on 0.0.9pre5:
6825 - Fix a bug in read_all that was corrupting config files on windows.
6826 - When we're raising the max number of open file descriptors to
6827 'unlimited', don't log that we just raised it to '-1'.
6828 - Include event code with events, as required by control-spec.txt.
6829 - Don't give a fingerprint when clients do --list-fingerprint:
6830 it's misleading, because it will never be the same again.
6831 - Stop using strlcpy in tor_strndup, since it was slowing us
6833 - Remove warn on startup about missing cached-directory file.
6834 - Make kill -USR1 work again.
6835 - Hibernate if we start tor during the "wait for wakeup-time" phase
6836 of an accounting interval. Log our hibernation plans better.
6837 - Authoritative dirservers now also cache their directory, so they
6838 have it on start-up.
6841 - Fetch running-routers; cache running-routers; compress
6842 running-routers; serve compressed running-routers.z
6843 - Add NSI installer script contributed by J Doe.
6844 - Commit VC6 and VC7 workspace/project files.
6845 - Commit a tor.spec for making RPM files, with help from jbash.
6846 - Add contrib/torctl.in contributed by Glenn Fink.
6847 - Implement the control-spec's SAVECONF command, to write your
6848 configuration to torrc.
6849 - Get cookie authentication for the controller closer to working.
6850 - Include control-spec.txt in the tarball.
6851 - When set_conf changes our server descriptor, upload a new copy.
6852 But don't upload it too often if there are frequent changes.
6853 - Document authentication config in man page, and document signals
6855 - Clean up confusing parts of man page and torrc.sample.
6856 - Make expand_filename handle ~ and ~username.
6857 - Use autoconf to enable largefile support where necessary. Use
6858 ftello where available, since ftell can fail at 2GB.
6859 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
6860 log more informatively.
6861 - Give a slightly more useful output for "tor -h".
6862 - Refuse application socks connections to port 0.
6863 - Check clock skew for verified servers, but allow unverified
6864 servers and clients to have any clock skew.
6865 - Break DirFetchPostPeriod into:
6866 - DirFetchPeriod for fetching full directory,
6867 - StatusFetchPeriod for fetching running-routers,
6868 - DirPostPeriod for posting server descriptor,
6869 - RendPostPeriod for posting hidden service descriptors.
6870 - Make sure the hidden service descriptors are at a random offset
6871 from each other, to hinder linkability.
6874 Changes in version 0.0.9pre5 - 2004-11-09
6875 o Bugfixes on 0.0.9pre4:
6876 - Fix a seg fault in unit tests (doesn't affect main program).
6877 - Fix an assert bug where a hidden service provider would fail if
6878 the first hop of his rendezvous circuit was down.
6879 - Hidden service operators now correctly handle version 1 style
6880 INTRODUCE1 cells (nobody generates them still, so not a critical
6882 - If do_hup fails, actually notice.
6883 - Handle more errnos from accept() without closing the listener.
6884 Some OpenBSD machines were closing their listeners because
6885 they ran out of file descriptors.
6886 - Send resolve cells to exit routers that are running a new
6887 enough version of the resolve code to work right.
6888 - Better handling of winsock includes on non-MSV win32 compilers.
6889 - Some people had wrapped their tor client/server in a script
6890 that would restart it whenever it died. This did not play well
6891 with our "shut down if your version is obsolete" code. Now people
6892 don't fetch a new directory if their local cached version is
6894 - Make our autogen.sh work on ksh as well as bash.
6897 - Hibernation: New config option "AccountingMaxKB" lets you
6898 set how many KBytes per month you want to allow your server to
6899 consume. Rather than spreading those bytes out evenly over the
6900 month, we instead hibernate for some of the month and pop up
6901 at a deterministic time, work until the bytes are consumed, then
6902 hibernate again. Config option "MonthlyAccountingStart" lets you
6903 specify which day of the month your billing cycle starts on.
6904 - Control interface: a separate program can now talk to your
6905 client/server over a socket, and get/set config options, receive
6906 notifications of circuits and streams starting/finishing/dying,
6907 bandwidth used, etc. The next step is to get some GUIs working.
6908 Let us know if you want to help out. See doc/control-spec.txt .
6909 - Ship a contrib/tor-control.py as an example script to interact
6910 with the control port.
6911 - "tor --hash-password zzyxz" will output a salted password for
6912 use in authenticating to the control interface.
6913 - New log format in config:
6914 "Log minsev[-maxsev] stdout|stderr|syslog" or
6915 "Log minsev[-maxsev] file /var/foo"
6918 - DirPolicy config option, to let people reject incoming addresses
6919 from their dirserver.
6920 - "tor --list-fingerprint" will list your identity key fingerprint
6922 - Add "pass" target for RedirectExit, to make it easier to break
6923 out of a sequence of RedirectExit rules.
6924 - Clients now generate a TLS cert too, in preparation for having
6925 them act more like real nodes.
6926 - Ship src/win32/ in the tarball, so people can use it to build.
6927 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
6929 - New "router-status" line in directory, to better bind each verified
6930 nickname to its identity key.
6931 - Deprecate unofficial config option abbreviations, and abbreviations
6932 not on the command line.
6933 - Add a pure-C tor-resolve implementation.
6934 - Use getrlimit and friends to ensure we can reach MaxConn (currently
6935 1024) file descriptors.
6937 o Code security improvements, inspired by Ilja:
6938 - Replace sprintf with snprintf. (I think they were all safe, but
6940 - Replace strcpy/strncpy with strlcpy in more places.
6941 - Avoid strcat; use snprintf or strlcat instead.
6942 - snprintf wrapper with consistent (though not C99) overflow behavior.
6945 Changes in version 0.0.9pre4 - 2004-10-17
6946 o Bugfixes on 0.0.9pre3:
6947 - If the server doesn't specify an exit policy, use the real default
6948 exit policy, not reject *:*.
6949 - Ignore fascistfirewall when uploading/downloading hidden service
6950 descriptors, since we go through Tor for those; and when using
6951 an HttpProxy, since we assume it can reach them all.
6952 - When looking for an authoritative dirserver, use only the ones
6953 configured at boot. Don't bother looking in the directory.
6954 - The rest of the fix for get_default_conf_file() on older win32.
6955 - Make 'Routerfile' config option obsolete.
6958 - New 'MyFamily nick1,...' config option for a server to
6959 specify other servers that shouldn't be used in the same circuit
6960 with it. Only believed if nick1 also specifies us.
6961 - New 'NodeFamily nick1,nick2,...' config option for a client to
6962 specify nodes that it doesn't want to use in the same circuit.
6963 - New 'Redirectexit pattern address:port' config option for a
6964 server to redirect exit connections, e.g. to a local squid.
6967 Changes in version 0.0.9pre3 - 2004-10-13
6968 o Bugfixes on 0.0.8.1:
6969 - Better torrc example lines for dirbindaddress and orbindaddress.
6970 - Improved bounds checking on parsed ints (e.g. config options and
6971 the ones we find in directories.)
6972 - Better handling of size_t vs int, so we're more robust on 64
6974 - Fix the rest of the bug where a newly started OR would appear
6975 as unverified even after we've added his fingerprint and hupped
6977 - Fix a bug from 0.0.7: when read() failed on a stream, we would
6978 close it without sending back an end. So 'connection refused'
6979 would simply be ignored and the user would get no response.
6981 o Bugfixes on 0.0.9pre2:
6982 - Serving the cached-on-disk directory to people is bad. We now
6983 provide no directory until we've fetched a fresh one.
6984 - Workaround for bug on windows where cached-directories get crlf
6986 - Make get_default_conf_file() work on older windows too.
6987 - If we write a *:* exit policy line in the descriptor, don't write
6988 any more exit policy lines.
6991 - Use only 0.0.9pre1 and later servers for resolve cells.
6992 - Make the dirservers file obsolete.
6993 - Include a dir-signing-key token in directories to tell the
6994 parsing entity which key is being used to sign.
6995 - Remove the built-in bulky default dirservers string.
6996 - New config option "Dirserver %s:%d [fingerprint]", which can be
6997 repeated as many times as needed. If no dirservers specified,
6998 default to moria1,moria2,tor26.
6999 - Make moria2 advertise a dirport of 80, so people behind firewalls
7000 will be able to get a directory.
7001 - Http proxy support
7002 - Dirservers translate requests for http://%s:%d/x to /x
7003 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
7004 be routed through this host.
7005 - Clients ask for /tor/x rather than /x for new enough dirservers.
7006 This way we can one day coexist peacefully with apache.
7007 - Clients specify a "Host: %s%d" http header, to be compatible
7008 with more proxies, and so running squid on an exit node can work.
7011 Changes in version 0.0.8.1 - 2004-10-13
7013 - Fix a seg fault that can be triggered remotely for Tor
7014 clients/servers with an open dirport.
7015 - Fix a rare assert trigger, where routerinfos for entries in
7016 our cpath would expire while we're building the path.
7017 - Fix a bug in OutboundBindAddress so it (hopefully) works.
7018 - Fix a rare seg fault for people running hidden services on
7019 intermittent connections.
7020 - Fix a bug in parsing opt keywords with objects.
7021 - Fix a stale pointer assert bug when a stream detaches and
7023 - Fix a string format vulnerability (probably not exploitable)
7024 in reporting stats locally.
7025 - Fix an assert trigger: sometimes launching circuits can fail
7026 immediately, e.g. because too many circuits have failed recently.
7027 - Fix a compile warning on 64 bit platforms.
7030 Changes in version 0.0.9pre2 - 2004-10-03
7032 - Make fetching a cached directory work for 64-bit platforms too.
7033 - Make zlib.h a required header, not an optional header.
7036 Changes in version 0.0.9pre1 - 2004-10-01
7038 - Stop using separate defaults for no-config-file and
7039 empty-config-file. Now you have to explicitly turn off SocksPort,
7040 if you don't want it open.
7041 - Fix a bug in OutboundBindAddress so it (hopefully) works.
7042 - Improve man page to mention more of the 0.0.8 features.
7043 - Fix a rare seg fault for people running hidden services on
7044 intermittent connections.
7045 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
7047 - Fix more dns related bugs: send back resolve_failed and end cells
7048 more reliably when the resolve fails, rather than closing the
7049 circuit and then trying to send the cell. Also attach dummy resolve
7050 connections to a circuit *before* calling dns_resolve(), to fix
7051 a bug where cached answers would never be sent in RESOLVED cells.
7052 - When we run out of disk space, or other log writing error, don't
7053 crash. Just stop logging to that log and continue.
7054 - We were starting to daemonize before we opened our logs, so if
7055 there were any problems opening logs, we would complain to stderr,
7056 which wouldn't work, and then mysteriously exit.
7057 - Fix a rare bug where sometimes a verified OR would connect to us
7058 before he'd uploaded his descriptor, which would cause us to
7059 assign conn->nickname as though he's unverified. Now we look through
7060 the fingerprint list to see if he's there.
7061 - Fix a rare assert trigger, where routerinfos for entries in
7062 our cpath would expire while we're building the path.
7065 - Clients can ask dirservers for /dir.z to get a compressed version
7066 of the directory. Only works for servers running 0.0.9, of course.
7067 - Make clients cache directories and use them to seed their router
7068 lists at startup. This means clients have a datadir again.
7069 - Configuration infrastructure support for warning on obsolete
7071 - Respond to content-encoding headers by trying to uncompress as
7073 - Reply with a deflated directory when a client asks for "dir.z".
7074 We could use allow-encodings instead, but allow-encodings isn't
7075 specified in HTTP 1.0.
7076 - Raise the max dns workers from 50 to 100.
7077 - Discourage people from setting their dirfetchpostperiod more often
7078 than once per minute.
7079 - Protect dirservers from overzealous descriptor uploading -- wait
7080 10 seconds after directory gets dirty, before regenerating.
7083 Changes in version 0.0.8 - 2004-08-25
7084 o Port it to SunOS 5.9 / Athena
7087 Changes in version 0.0.8rc2 - 2004-08-20
7088 o Make it compile on cygwin again.
7089 o When picking unverified routers, skip those with low uptime and/or
7090 low bandwidth, depending on what properties you care about.
7093 Changes in version 0.0.8rc1 - 2004-08-18
7094 o Changes from 0.0.7.3:
7096 - Fix assert triggers: if the other side returns an address 0.0.0.0,
7097 don't put it into the client dns cache.
7098 - If a begin failed due to exit policy, but we believe the IP address
7099 should have been allowed, switch that router to exitpolicy reject *:*
7100 until we get our next directory.
7102 - Clients choose nodes proportional to advertised bandwidth.
7103 - Avoid using nodes with low uptime as introduction points.
7104 - Handle servers with dynamic IP addresses: don't replace
7105 options->Address with the resolved one at startup, and
7106 detect our address right before we make a routerinfo each time.
7107 - 'FascistFirewall' option to pick dirservers and ORs on specific
7108 ports; plus 'FirewallPorts' config option to tell FascistFirewall
7109 which ports are open. (Defaults to 80,443)
7110 - Be more aggressive about trying to make circuits when the network
7111 has changed (e.g. when you unsuspend your laptop).
7112 - Check for time skew on http headers; report date in response to
7114 - If the entrynode config line has only one node, don't pick it as
7116 - Add strict{entry|exit}nodes config options. If set to 1, then
7117 we refuse to build circuits that don't include the specified entry
7119 - OutboundBindAddress config option, to bind to a specific
7120 IP address for outgoing connect()s.
7121 - End truncated log entries (e.g. directories) with "[truncated]".
7123 o Patches to 0.0.8preX:
7125 - Patches to compile and run on win32 again (maybe)?
7126 - Fix crash when looking for ~/.torrc with no $HOME set.
7127 - Fix a race bug in the unit tests.
7128 - Handle verified/unverified name collisions better when new
7129 routerinfo's arrive in a directory.
7130 - Sometimes routers were getting entered into the stats before
7131 we'd assigned their identity_digest. Oops.
7132 - Only pick and establish intro points after we've gotten a
7135 - AllowUnverifiedNodes config option to let circuits choose no-name
7136 routers in entry,middle,exit,introduction,rendezvous positions.
7137 Allow middle and rendezvous positions by default.
7138 - Add a man page for tor-resolve.
7141 Changes in version 0.0.7.3 - 2004-08-12
7142 o Stop dnsworkers from triggering an assert failure when you
7143 ask them to resolve the host "".
7146 Changes in version 0.0.8pre3 - 2004-08-09
7147 o Changes from 0.0.7.2:
7148 - Allow multiple ORs with same nickname in routerlist -- now when
7149 people give us one identity key for a nickname, then later
7150 another, we don't constantly complain until the first expires.
7151 - Remember used bandwidth (both in and out), and publish 15-minute
7152 snapshots for the past day into our descriptor.
7153 - You can now fetch $DIRURL/running-routers to get just the
7154 running-routers line, not the whole descriptor list. (But
7155 clients don't use this yet.)
7156 - When people mistakenly use Tor as an http proxy, point them
7157 at the tor-doc.html rather than the INSTALL.
7158 - Remove our mostly unused -- and broken -- hex_encode()
7159 function. Use base16_encode() instead. (Thanks to Timo Lindfors
7160 for pointing out this bug.)
7161 - Rotate onion keys every 12 hours, not every 2 hours, so we have
7162 fewer problems with people using the wrong key.
7163 - Change the default exit policy to reject the default edonkey,
7164 kazaa, gnutella ports.
7165 - Add replace_file() to util.[ch] to handle win32's rename().
7167 o Changes from 0.0.8preX:
7168 - Fix two bugs in saving onion keys to disk when rotating, so
7169 hopefully we'll get fewer people using old onion keys.
7170 - Fix an assert error that was making SocksPolicy not work.
7171 - Be willing to expire routers that have an open dirport -- it's
7172 just the authoritative dirservers we want to not forget.
7173 - Reject tor-resolve requests for .onion addresses early, so we
7174 don't build a whole rendezvous circuit and then fail.
7175 - When you're warning a server that he's unverified, don't cry
7177 - Fix a race condition: don't try to extend onto a connection
7178 that's still handshaking.
7179 - For servers in clique mode, require the conn to be open before
7180 you'll choose it for your path.
7181 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
7182 end relay cell, etc.
7183 - Measure bandwidth capacity over the last 24 hours, not just 12
7184 - Bugfix: authoritative dirservers were making and signing a new
7185 directory for each client, rather than reusing the cached one.
7188 Changes in version 0.0.8pre2 - 2004-08-04
7189 o Changes from 0.0.7.2:
7191 - Check directory signature _before_ you decide whether you're
7192 you're running an obsolete version and should exit.
7193 - Check directory signature _before_ you parse the running-routers
7194 list to decide who's running or verified.
7195 - Bugfixes and features:
7196 - Check return value of fclose while writing to disk, so we don't
7197 end up with broken files when servers run out of disk space.
7198 - Log a warning if the user uses an unsafe socks variant, so people
7199 are more likely to learn about privoxy or socat.
7200 - Dirservers now include RFC1123-style dates in the HTTP headers,
7201 which one day we will use to better detect clock skew.
7203 o Changes from 0.0.8pre1:
7204 - Make it compile without warnings again on win32.
7205 - Log a warning if you're running an unverified server, to let you
7206 know you might want to get it verified.
7207 - Only pick a default nickname if you plan to be a server.
7210 Changes in version 0.0.8pre1 - 2004-07-23
7212 - Made our unit tests compile again on OpenBSD 3.5, and tor
7213 itself compile again on OpenBSD on a sparc64.
7214 - We were neglecting milliseconds when logging on win32, so
7215 everything appeared to happen at the beginning of each second.
7218 - 'Extend' relay cell payloads now include the digest of the
7219 intended next hop's identity key. Now we can verify that we're
7220 extending to the right router, and also extend to routers we
7221 hadn't heard of before.
7224 - Tor nodes can now act as relays (with an advertised ORPort)
7225 without being manually verified by the dirserver operators.
7226 - Uploaded descriptors of unverified routers are now accepted
7227 by the dirservers, and included in the directory.
7228 - Verified routers are listed by nickname in the running-routers
7229 list; unverified routers are listed as "$<fingerprint>".
7230 - We now use hash-of-identity-key in most places rather than
7231 nickname or addr:port, for improved security/flexibility.
7232 - To avoid Sybil attacks, paths still use only verified servers.
7233 But now we have a chance to play around with hybrid approaches.
7234 - Nodes track bandwidth usage to estimate capacity (not used yet).
7235 - ClientOnly option for nodes that never want to become servers.
7236 - Directory caching.
7237 - "AuthoritativeDir 1" option for the official dirservers.
7238 - Now other nodes (clients and servers) will cache the latest
7239 directory they've pulled down.
7240 - They can enable their DirPort to serve it to others.
7241 - Clients will pull down a directory from any node with an open
7242 DirPort, and check the signature/timestamp correctly.
7243 - Authoritative dirservers now fetch directories from other
7244 authdirservers, to stay better synced.
7245 - Running-routers list tells who's down also, along with noting
7246 if they're verified (listed by nickname) or unverified (listed
7248 - Allow dirservers to serve running-router list separately.
7249 This isn't used yet.
7250 - ORs connect-on-demand to other ORs
7251 - If you get an extend cell to an OR you're not connected to,
7252 connect, handshake, and forward the create cell.
7253 - The authoritative dirservers stay connected to everybody,
7254 and everybody stays connected to 0.0.7 servers, but otherwise
7255 clients/servers expire unused connections after 5 minutes.
7256 - When servers get a sigint, they delay 30 seconds (refusing new
7257 connections) then exit. A second sigint causes immediate exit.
7258 - File and name management:
7259 - Look for .torrc if no CONFDIR "torrc" is found.
7260 - If no datadir is defined, then choose, make, and secure ~/.tor
7262 - If torrc not found, exitpolicy reject *:*.
7263 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
7264 - If no nickname is defined, derive default from hostname.
7265 - Rename secret key files, e.g. identity.key -> secret_id_key,
7266 to discourage people from mailing their identity key to tor-ops.
7267 - Refuse to build a circuit before the directory has arrived --
7268 it won't work anyway, since you won't know the right onion keys
7270 - Try other dirservers immediately if the one you try is down. This
7271 should tolerate down dirservers better now.
7272 - Parse tor version numbers so we can do an is-newer-than check
7273 rather than an is-in-the-list check.
7274 - New socks command 'resolve', to let us shim gethostbyname()
7276 - A 'tor_resolve' script to access the socks resolve functionality.
7277 - A new socks-extensions.txt doc file to describe our
7278 interpretation and extensions to the socks protocols.
7279 - Add a ContactInfo option, which gets published in descriptor.
7280 - Publish OR uptime in descriptor (and thus in directory) too.
7281 - Write tor version at the top of each log file
7282 - New docs in the tarball:
7284 - Document that you should proxy your SSL traffic too.
7287 Changes in version 0.0.7.2 - 2004-07-07
7288 o A better fix for the 0.0.0.0 problem, that will hopefully
7289 eliminate the remaining related assertion failures.
7292 Changes in version 0.0.7.1 - 2004-07-04
7293 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
7294 since internally we use 0.0.0.0 to signify "not yet resolved".
7297 Changes in version 0.0.7 - 2004-06-07
7298 o Updated the man page to reflect the new features.
7301 Changes in version 0.0.7rc2 - 2004-06-06
7302 o Changes from 0.0.7rc1:
7303 - Make it build on Win32 again.
7304 o Changes from 0.0.6.2:
7305 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
7309 Changes in version 0.0.7rc1 - 2004-06-02
7311 - On sighup, we were adding another log without removing the first
7312 one. So log messages would get duplicated n times for n sighups.
7313 - Several cases of using a connection after we'd freed it. The
7314 problem was that connections that are pending resolve are in both
7315 the pending_resolve tree, and also the circuit's resolving_streams
7316 list. When you want to remove one, you must remove it from both.
7317 - Fix a double-mark-for-close where an end cell arrived for a
7318 resolving stream, and then the resolve failed.
7319 - Check directory signatures based on name of signer, not on whom
7320 we got the directory from. This will let us cache directories more
7323 - Crank up some of our constants to handle more users.
7326 Changes in version 0.0.7pre1 - 2004-06-02
7327 o Fixes for crashes and other obnoxious bugs:
7328 - Fix an epipe bug: sometimes when directory connections failed
7329 to connect, we would give them a chance to flush before closing
7331 - When we detached from a circuit because of resolvefailed, we
7332 would immediately try the same circuit twice more, and then
7333 give up on the resolve thinking we'd tried three different
7335 - Limit the number of intro circuits we'll attempt to build for a
7336 hidden service per 15-minute period.
7337 - Check recommended-software string *early*, before actually parsing
7338 the directory. Thus we can detect an obsolete version and exit,
7339 even if the new directory format doesn't parse.
7340 o Fixes for security bugs:
7341 - Remember which nodes are dirservers when you startup, and if a
7342 random OR enables his dirport, don't automatically assume he's
7343 a trusted dirserver.
7345 - Directory connections were asking the wrong poll socket to
7346 start writing, and not asking themselves to start writing.
7347 - When we detached from a circuit because we sent a begin but
7348 didn't get a connected, we would use it again the first time;
7349 but after that we would correctly switch to a different one.
7350 - Stop warning when the first onion decrypt attempt fails; they
7351 will sometimes legitimately fail now that we rotate keys.
7352 - Override unaligned-access-ok check when $host_cpu is ia64 or
7353 arm. Apparently they allow it but the kernel whines.
7354 - Dirservers try to reconnect periodically too, in case connections
7356 - Fix some memory leaks in directory servers.
7357 - Allow backslash in Win32 filenames.
7358 - Made Tor build complain-free on FreeBSD, hopefully without
7359 breaking other BSD builds. We'll see.
7361 - Doxygen markup on all functions and global variables.
7362 - Make directory functions update routerlist, not replace it. So
7363 now directory disagreements are not so critical a problem.
7364 - Remove the upper limit on number of descriptors in a dirserver's
7365 directory (not that we were anywhere close).
7366 - Allow multiple logfiles at different severity ranges.
7367 - Allow *BindAddress to specify ":port" rather than setting *Port
7368 separately. Allow multiple instances of each BindAddress config
7369 option, so you can bind to multiple interfaces if you want.
7370 - Allow multiple exit policy lines, which are processed in order.
7371 Now we don't need that huge line with all the commas in it.
7372 - Enable accept/reject policies on SOCKS connections, so you can bind
7373 to 0.0.0.0 but still control who can use your OP.
7376 Changes in version 0.0.6.2 - 2004-05-16
7377 o Our integrity-checking digest was checking only the most recent cell,
7378 not the previous cells like we'd thought.
7379 Thanks to Stefan Mark for finding the flaw!
7382 Changes in version 0.0.6.1 - 2004-05-06
7383 o Fix two bugs in our AES counter-mode implementation (this affected
7384 onion-level stream encryption, but not TLS-level). It turns
7385 out we were doing something much more akin to a 16-character
7386 polyalphabetic cipher. Oops.
7387 Thanks to Stefan Mark for finding the flaw!
7388 o Retire moria3 as a directory server, and add tor26 as a directory
7392 Changes in version 0.0.6 - 2004-05-02
7396 Changes in version 0.0.6rc4 - 2004-05-01
7397 o Update the built-in dirservers list to use the new directory format
7398 o Fix a rare seg fault: if a node offering a hidden service attempts
7399 to build a circuit to Alice's rendezvous point and fails before it
7400 reaches the last hop, it retries with a different circuit, but
7402 o Handle windows socket errors correctly.
7405 Changes in version 0.0.6rc3 - 2004-04-28
7406 o Don't expire non-general excess circuits (if we had enough
7407 circuits open, we were expiring rendezvous circuits -- even
7408 when they had a stream attached. oops.)
7409 o Fetch randomness from /dev/urandom better (not via fopen/fread)
7410 o Better debugging for tls errors
7411 o Some versions of openssl have an SSL_pending function that erroneously
7412 returns bytes when there is a non-application record pending.
7413 o Set Content-Type on the directory and hidserv descriptor.
7414 o Remove IVs from cipher code, since AES-ctr has none.
7415 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
7416 o We were using an array of length zero in a few places.
7417 o win32's gethostbyname can't resolve an IP to an IP.
7418 o win32's close can't close a socket.
7421 Changes in version 0.0.6rc2 - 2004-04-26
7422 o Fix a bug where we were closing tls connections intermittently.
7423 It turns out openssl keeps its errors around -- so if an error
7424 happens, and you don't ask about it, and then another openssl
7425 operation happens and succeeds, and you ask if there was an error,
7426 it tells you about the first error. Fun fun.
7427 o Fix a bug that's been lurking since 27 may 03 (!)
7428 When passing back a destroy cell, we would use the wrong circ id.
7429 'Mostly harmless', but still worth fixing.
7430 o Since we don't support truncateds much, don't bother sending them;
7431 just close the circ.
7432 o check for <machine/limits.h> so we build on NetBSD again (I hope).
7433 o don't crash if a conn that sent a begin has suddenly lost its circuit
7434 (this was quite rare).
7437 Changes in version 0.0.6rc1 - 2004-04-25
7438 o We now rotate link (tls context) keys and onion keys.
7439 o CREATE cells now include oaep padding, so you can tell
7440 if you decrypted them correctly.
7441 o Add bandwidthburst to server descriptor.
7442 o Directories now say which dirserver signed them.
7443 o Use a tor_assert macro that logs failed assertions too.
7446 Changes in version 0.0.6pre5 - 2004-04-18
7447 o changes from 0.0.6pre4:
7448 - make tor build on broken freebsd 5.2 installs
7449 - fix a failed assert when you try an intro point, get a nack, and try
7450 a second one and it works.
7451 - when alice uses a port that the hidden service doesn't accept,
7452 it now sends back an end cell (denied by exit policy). otherwise
7453 alice would just have to wait to time out.
7454 - fix another rare bug: when we had tried all the intro
7455 points for a hidden service, we fetched the descriptor
7456 again, but we left our introcirc thinking it had already
7457 sent an intro, so it kept waiting for a response...
7458 - bugfix: when you sleep your hidden-service laptop, as soon
7459 as it wakes up it tries to upload a service descriptor, but
7460 socketpair fails for some reason (localhost not up yet?).
7461 now we simply give up on that upload, and we'll try again later.
7462 i'd still like to find the bug though.
7463 - if an intro circ waiting for an ack dies before getting one, then
7465 - we were reusing stale service descriptors and refetching usable
7469 Changes in version 0.0.6pre4 - 2004-04-14
7470 o changes from 0.0.6pre3:
7471 - when bob fails to connect to the rendezvous point, and his
7472 circ didn't fail because of the rendezvous point itself, then
7473 he retries a couple of times
7474 - we expire introduction and rendezvous circs more thoroughly
7475 (sometimes they were hanging around forever)
7476 - we expire unattached rendezvous streams that have been around
7477 too long (they were sticking around forever).
7478 - fix a measly fencepost error that was crashing everybody with
7482 Changes in version 0.0.6pre3 - 2004-04-14
7483 o changes from 0.0.6pre2:
7484 - make hup work again
7485 - fix some memory leaks for dirservers
7486 - allow more skew in rendezvous descriptor timestamps, to help
7487 handle people like blanu who don't know what time it is
7488 - normal circs are 3 hops, but some rend/intro circs are 4, if
7489 the initiator doesn't get to choose the last hop
7490 - send acks for introductions, so alice can know whether to try
7492 - bob publishes intro points more correctly
7493 o changes from 0.0.5:
7494 - fix an assert trigger that's been plaguing us since the days
7495 of 0.0.2prexx (thanks weasel!)
7496 - retry stream correctly when we fail to connect because of
7497 exit-policy-reject (should try another) or can't-resolve-address
7498 (also should try another, because dns on random internet servers
7500 - when we hup a dirserver and we've *removed* a server from the
7501 approved-routers list, now we remove that server from the
7502 in-memory directories too
7505 Changes in version 0.0.6pre2 - 2004-04-08
7506 o We fixed our base32 implementation. Now it works on all architectures.
7509 Changes in version 0.0.6pre1 - 2004-04-08
7511 - Hidden services and rendezvous points are implemented. Go to
7512 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
7513 hidden services. (This only works via a socks4a proxy such as
7514 Privoxy, and currently it's quite slow.)
7517 Changes in version 0.0.5 - 2004-03-30
7521 Changes in version 0.0.5rc3 - 2004-03-29
7522 o Install torrc as torrc.sample -- we no longer clobber your
7524 o Re-enable recommendedversion checking (we broke it in rc2, oops)
7525 o Add in a 'notice' log level for things the operator should hear
7526 but that aren't warnings
7529 Changes in version 0.0.5rc2 - 2004-03-29
7530 o Hold socks connection open until reply is flushed (if possible)
7531 o Make exit nodes resolve IPs to IPs immediately, rather than asking
7532 the dns farm to do it.
7533 o Fix c99 aliasing warnings in rephist.c
7534 o Don't include server descriptors that are older than 24 hours in the
7536 o Give socks 'reject' replies their whole 15s to attempt to flush,
7537 rather than seeing the 60s timeout and assuming the flush had failed.
7538 o Clean automake droppings from the cvs repository
7541 Changes in version 0.0.5rc1 - 2004-03-28
7542 o Fix mangled-state bug in directory fetching (was causing sigpipes).
7543 o Only build circuits after we've fetched the directory: clients were
7544 using only the directory servers before they'd fetched a directory.
7545 This also means longer startup time; so it goes.
7546 o Fix an assert trigger where an OP would fail to handshake, and we'd
7547 expect it to have a nickname.
7548 o Work around a tsocks bug: do a socks reject when AP connection dies
7549 early, else tsocks goes into an infinite loop.
7552 Changes in version 0.0.4 - 2004-03-26
7553 o When connecting to a dirserver or OR and the network is down,
7557 Changes in version 0.0.3 - 2004-03-26
7558 o Warn and fail if server chose a nickname with illegal characters
7559 o Port to Solaris and Sparc:
7560 - include missing header fcntl.h
7561 - have autoconf find -lsocket -lnsl automatically
7562 - deal with hardware word alignment
7563 - make uname() work (solaris has a different return convention)
7564 - switch from using signal() to sigaction()
7565 o Preliminary work on reputation system:
7566 - Keep statistics on success/fail of connect attempts; they're published
7567 by kill -USR1 currently.
7568 - Add a RunTesting option to try to learn link state by creating test
7569 circuits, even when SocksPort is off.
7570 - Remove unused open circuits when there are too many.
7573 Changes in version 0.0.2 - 2004-03-19
7574 - Include strlcpy and strlcat for safer string ops
7575 - define INADDR_NONE so we compile (but still not run) on solaris
7578 Changes in version 0.0.2pre27 - 2004-03-14
7580 - Allow internal tor networks (we were rejecting internal IPs,
7581 now we allow them if they're set explicitly).
7582 - And fix a few endian issues.
7585 Changes in version 0.0.2pre26 - 2004-03-14
7587 - If a stream times out after 15s without a connected cell, don't
7588 try that circuit again: try a new one.
7589 - Retry streams at most 4 times. Then give up.
7590 - When a dirserver gets a descriptor from an unknown router, it
7591 logs its fingerprint (so the dirserver operator can choose to
7592 accept it even without mail from the server operator).
7593 - Inform unapproved servers when we reject their descriptors.
7594 - Make tor build on Windows again. It works as a client, who knows
7596 - Clearer instructions in the torrc for how to set up a server.
7597 - Be more efficient about reading fd's when our global token bucket
7598 (used for rate limiting) becomes empty.
7600 - Stop asserting that computers always go forward in time. It's
7602 - When we sent a cell (e.g. destroy) and then marked an OR connection
7603 expired, we might close it before finishing a flush if the other
7604 side isn't reading right then.
7605 - Don't allow dirservers to start if they haven't defined
7607 - We were caching transient dns failures. Oops.
7608 - Prevent servers from publishing an internal IP as their address.
7609 - Address a strcat vulnerability in circuit.c
7612 Changes in version 0.0.2pre25 - 2004-03-04
7614 - Put the OR's IP in its router descriptor, not its fqdn. That way
7615 we'll stop being stalled by gethostbyname for nodes with flaky dns,
7618 - If the user typed in an address that didn't resolve, the server
7622 Changes in version 0.0.2pre24 - 2004-03-03
7624 - Fix an assertion failure in dns.c, where we were trying to dequeue
7625 a pending dns resolve even if it wasn't pending
7626 - Fix a spurious socks5 warning about still trying to write after the
7627 connection is finished.
7628 - Hold certain marked_for_close connections open until they're finished
7629 flushing, rather than losing bytes by closing them too early.
7630 - Correctly report the reason for ending a stream
7631 - Remove some duplicate calls to connection_mark_for_close
7632 - Put switch_id and start_daemon earlier in the boot sequence, so it
7633 will actually try to chdir() to options.DataDirectory
7634 - Make 'make test' exit(1) if a test fails; fix some unit tests
7635 - Make tor fail when you use a config option it doesn't know about,
7636 rather than warn and continue.
7637 - Make --version work
7638 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
7641 Changes in version 0.0.2pre23 - 2004-02-29
7643 - Print a statement when the first circ is finished, so the user
7645 - If a relay cell is unrecognized at the end of the circuit,
7646 send back a destroy. (So attacks to mutate cells are more
7648 - New config option 'excludenodes' to avoid certain nodes for circuits.
7649 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
7650 so you can collect coredumps there.
7652 - Fix a bug in tls flushing where sometimes data got wedged and
7653 didn't flush until more data got sent. Hopefully this bug was
7654 a big factor in the random delays we were seeing.
7655 - Make 'connected' cells include the resolved IP, so the client
7656 dns cache actually gets populated.
7657 - Disallow changing from ORPort=0 to ORPort>0 on hup.
7658 - When we time-out on a stream and detach from the circuit, send an
7659 end cell down it first.
7660 - Only warn about an unknown router (in exitnodes, entrynodes,
7661 excludenodes) after we've fetched a directory.
7664 Changes in version 0.0.2pre22 - 2004-02-26
7666 - Servers publish less revealing uname information in descriptors.
7667 - More memory tracking and assertions, to crash more usefully when
7669 - If the default torrc isn't there, just use some default defaults.
7670 Plus provide an internal dirservers file if they don't have one.
7671 - When the user tries to use Tor as an http proxy, give them an http
7672 501 failure explaining that we're a socks proxy.
7673 - Dump a new router.desc on hup, to help confused people who change
7674 their exit policies and then wonder why router.desc doesn't reflect
7676 - Clean up the generic tor.sh init script that we ship with.
7678 - If the exit stream is pending on the resolve, and a destroy arrives,
7679 then the stream wasn't getting removed from the pending list. I
7680 think this was the one causing recent server crashes.
7681 - Use a more robust poll on OSX 10.3, since their poll is flaky.
7682 - When it couldn't resolve any dirservers, it was useless from then on.
7683 Now it reloads the RouterFile (or default dirservers) if it has no
7685 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
7686 many users don't even *have* a /usr/local/sbin/.
7689 Changes in version 0.0.2pre21 - 2004-02-18
7691 - There's a ChangeLog file that actually reflects the changelog.
7692 - There's a 'torify' wrapper script, with an accompanying
7693 tor-tsocks.conf, that simplifies the process of using tsocks for
7694 tor. It even has a man page.
7695 - The tor binary gets installed to sbin rather than bin now.
7696 - Retry streams where the connected cell hasn't arrived in 15 seconds
7697 - Clean up exit policy handling -- get the default out of the torrc,
7698 so we can update it without forcing each server operator to fix
7700 - Allow imaps and pop3s in default exit policy
7702 - Prevent picking middleman nodes as the last node in the circuit
7705 Changes in version 0.0.2pre20 - 2004-01-30
7707 - We now have a deb package, and it's in debian unstable. Go to
7709 - I've split the TotalBandwidth option into BandwidthRate (how many
7710 bytes per second you want to allow, long-term) and
7711 BandwidthBurst (how many bytes you will allow at once before the cap
7712 kicks in). This better token bucket approach lets you, say, set
7713 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
7714 performance while not exceeding your monthly bandwidth quota.
7715 - Push out a tls record's worth of data once you've got it, rather
7716 than waiting until you've read everything waiting to be read. This
7717 may improve performance by pipelining better. We'll see.
7718 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
7719 from failed circuits (if they haven't been connected yet) and attach
7721 - Expire old streams that haven't managed to connect. Some day we'll
7722 have them reattach to new circuits instead.
7725 - Fix several memory leaks that were causing servers to become bloated
7727 - Fix a few very rare assert triggers. A few more remain.
7728 - Setuid to User _before_ complaining about running as root.
7731 Changes in version 0.0.2pre19 - 2004-01-07
7733 - Fix deadlock condition in dns farm. We were telling a child to die by
7734 closing the parent's file descriptor to him. But newer children were
7735 inheriting the open file descriptor from the parent, and since they
7736 weren't closing it, the socket never closed, so the child never read
7737 eof, so he never knew to exit. Similarly, dns workers were holding
7738 open other sockets, leading to all sorts of chaos.
7739 - New cleaner daemon() code for forking and backgrounding.
7740 - If you log to a file, it now prints an entry at the top of the
7741 logfile so you know it's working.
7742 - The onionskin challenge length was 30 bytes longer than necessary.
7743 - Started to patch up the spec so it's not quite so out of date.
7746 Changes in version 0.0.2pre18 - 2004-01-02
7748 - Fix endian issues with the 'integrity' field in the relay header.
7749 - Fix a potential bug where connections in state
7750 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
7753 Changes in version 0.0.2pre17 - 2003-12-30
7755 - Made --debuglogfile (or any second log file, actually) work.
7756 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
7757 adversary could force us into an infinite loop.
7760 - Each onionskin handshake now includes a hash of the computed key,
7761 to prove the server's identity and help perfect forward secrecy.
7762 - Changed cell size from 256 to 512 bytes (working toward compatibility
7764 - Changed cell length to 2 bytes, and moved it to the relay header.
7765 - Implemented end-to-end integrity checking for the payloads of
7767 - Separated streamid from 'recognized' (otherwise circuits will get
7768 messed up when we try to have streams exit from the middle). We
7769 use the integrity-checking to confirm that a cell is addressed to
7771 - Randomize the initial circid and streamid values, so an adversary who
7772 breaks into a node can't learn how many circuits or streams have
7776 Changes in version 0.0.2pre16 - 2003-12-14
7778 - Fixed a bug that made HUP trigger an assert
7779 - Fixed a bug where a circuit that immediately failed wasn't being
7780 counted as a failed circuit in counting retries.
7783 - Now we close the circuit when we get a truncated cell: otherwise we're
7784 open to an anonymity attack where a bad node in the path truncates
7785 the circuit and then we open streams at him.
7786 - Add port ranges to exit policies
7787 - Add a conservative default exit policy
7788 - Warn if you're running tor as root
7789 - on HUP, retry OR connections and close/rebind listeners
7790 - options.EntryNodes: try these nodes first when picking the first node
7791 - options.ExitNodes: if your best choices happen to include any of
7792 your preferred exit nodes, you choose among just those preferred
7794 - options.ExcludedNodes: nodes that are never picked in path building
7797 Changes in version 0.0.2pre15 - 2003-12-03
7798 o Robustness and bugfixes:
7799 - Sometimes clients would cache incorrect DNS resolves, which would
7800 really screw things up.
7801 - An OP that goes offline would slowly leak all its sockets and stop
7803 - A wide variety of bugfixes in exit node selection, exit policy
7804 handling, and processing pending streams when a new circuit is
7806 - Pick nodes for a path only from those the directory says are up
7807 - Choose randomly from all running dirservers, not always the first one
7808 - Increase allowed http header size for directory fetch.
7809 - Stop writing to stderr (if we're daemonized it will be closed).
7810 - Enable -g always, so cores will be more useful to me.
7811 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
7814 - Wrote a man page. It lists commonly used options.
7817 - Change default loglevel to warn.
7818 - Make PidFile default to null rather than littering in your CWD.
7819 - OnionRouter config option is now obsolete. Instead it just checks
7821 - Moved to a single unified torrc file for both clients and servers.
7824 Changes in version 0.0.2pre14 - 2003-11-29
7825 o Robustness and bugfixes:
7826 - Force the admin to make the DataDirectory himself
7827 - to get ownership/permissions right
7828 - so clients no longer make a DataDirectory and then never use it
7829 - fix bug where a client who was offline for 45 minutes would never
7830 pull down a directory again
7831 - fix (or at least hide really well) the dns assert bug that was
7832 causing server crashes
7833 - warnings and improved robustness wrt clockskew for certs
7834 - use the native daemon(3) to daemonize, when available
7835 - exit if bind() fails
7836 - exit if neither socksport nor orport is defined
7837 - include our own tor_timegm (Win32 doesn't have its own)
7838 - bugfix for win32 with lots of connections
7839 - fix minor bias in PRNG
7840 - make dirserver more robust to corrupt cached directory
7843 - Wrote the design document (woo)
7845 o Circuit building and exit policies:
7846 - Circuits no longer try to use nodes that the directory has told them
7848 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
7849 bitcounts (18.0.0.0/8).
7850 - Make AP connections standby for a circuit if no suitable circuit
7851 exists, rather than failing
7852 - Circuits choose exit node based on addr/port, exit policies, and
7853 which AP connections are standing by
7854 - Bump min pathlen from 2 to 3
7855 - Relay end cells have a payload to describe why the stream ended.
7856 - If the stream failed because of exit policy, try again with a new
7858 - Clients have a dns cache to remember resolved addresses.
7859 - Notice more quickly when we have no working circuits
7862 - APPort is now called SocksPort
7863 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
7865 - RecommendedVersions is now a config variable rather than
7866 hardcoded (for dirservers)
7867 - Reloads config on HUP
7868 - Usage info on -h or --help
7869 - If you set User and Group config vars, it'll setu/gid to them.
7872 Changes in version 0.0.2pre13 - 2003-10-19
7873 o General stability:
7874 - SSL_write no longer fails when it returns WANTWRITE and the number
7875 of bytes in the buf has changed by the next SSL_write call.
7876 - Fix segfault fetching directory when network is down
7877 - Fix a variety of minor memory leaks
7878 - Dirservers reload the fingerprints file on HUP, so I don't have
7879 to take down the network when I approve a new router
7880 - Default server config file has explicit Address line to specify fqdn
7883 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
7884 - Make listener connections not ever alloc bufs
7886 o Autoconf improvements:
7887 - don't clobber an external CFLAGS in ./configure
7888 - Make install now works
7889 - create var/lib/tor on make install
7890 - autocreate a tor.sh initscript to help distribs
7891 - autocreate the torrc and sample-server-torrc with correct paths
7893 o Log files and Daemonizing now work:
7894 - If --DebugLogFile is specified, log to it at -l debug
7895 - If --LogFile is specified, use it instead of commandline
7896 - If --RunAsDaemon is set, tor forks and backgrounds on startup