1 Changes in version 0.2.4.18-rc - 2013-10-??
2 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
6 - Always call circuit_n_chan_done(chan, 0) from channel_closed(),
7 so we can't leak pending circuits in some cases where
8 run_connection_housekeeping() calls connection_or_close_normally().
9 Fixes bug 9776; bugfix on 0.2.4.17.
12 - Clients no longer send timestamps in their NETINFO cells. These were
13 not used for anything, and they provided one small way for clients
14 to be distinguished from each other as they moved from network to
15 network or behind NAT. Implements part of proposal 222.
16 - Clients now round timestamps in INTRODUCE cells down to the nearest
17 10 minutes. If a new Support022HiddenServices option is set to 0, or
18 if it's set to "auto" and the feature is disabled in the consensus,
19 the timestamp is sent as 0 instead. Implements part of proposal 222.
20 - Stop sending timestamps in AUTHENTICATE cells. This is not such
21 a big deal from a security point of view, but it achieves no actual
22 good purpose, and isn't needed. Implements part of proposal 222.
23 - Reduce down accuracy of timestamps in hidden service descriptors.
24 Implements part of proposal 222.
25 - Update to the September 4 2013 Maxmind GeoLite Country database.
28 Changes in version 0.2.4.17-rc - 2013-09-05
29 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
30 series. It adds an emergency step to help us tolerate the massive
31 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
32 circuit-level handshakes now effectively jump the queue compared to
33 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
34 big bug hindering bridge reachability tests.
37 - Relays now process the new "NTor" circuit-level handshake requests
38 with higher priority than the old "TAP" circuit-level handshake
39 requests. We still process some TAP requests to not totally starve
40 0.2.3 clients when NTor becomes popular. A new consensus parameter
41 "NumNTorsPerTAP" lets us tune the balance later if we need to.
42 Implements ticket 9574.
45 - If the circuit build timeout logic is disabled (via the consensus,
46 or because we are an authority), then don't build testing circuits.
47 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
48 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
49 previously they did not, which prevented them from receiving
50 successful connections from relays for self-test or bandwidth
51 testing. Also, when a relay is extending a circuit to a bridge,
52 it needs to send a NETINFO cell, even when the bridge hasn't sent
53 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
54 - If the time to download the next old-style networkstatus is in
55 the future, do not decline to consider whether to download the
56 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
60 - Avoid double-closing the listener socket in our socketpair()
61 replacement (used on Windows) in the case where the addresses on
62 our opened sockets don't match what we expected. Fixes bug 9400;
63 bugfix on 0.0.2pre7. Found by Coverity.
65 o Minor fixes (config options):
66 - Avoid overflows when the user sets MaxCircuitDirtiness to a
67 ridiculously high value, by imposing a (ridiculously high) 30-day
68 maximum on MaxCircuitDirtiness.
69 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
70 message is logged at notice, not at info.
71 - Warn and fail if a server is configured not to advertise any
72 ORPorts at all. (We need *something* to put in our descriptor,
73 or we just won't work.)
76 - Track how many "TAP" and "NTor" circuit handshake requests we get,
77 and how many we complete, and log it every hour to help relay
78 operators follow trends in network load. Addresses ticket 9658.
79 - Update to the August 7 2013 Maxmind GeoLite Country database.
82 Changes in version 0.2.4.16-rc - 2013-08-10
83 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
84 series. It fixes several crash bugs in the 0.2.4 branch.
87 - Fix a bug in the voting algorithm that could yield incorrect results
88 when a non-naming authority declared too many flags. Fixes bug 9200;
89 bugfix on 0.2.0.3-alpha.
90 - Fix an uninitialized read that could in some cases lead to a remote
91 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
92 Anybody running a hidden service on the experimental 0.2.4.x
93 branch should upgrade. (This is, so far as we know, unrelated to
95 - Avoid an assertion failure when processing DNS replies without the
96 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
97 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
98 0.2.4.15-rc. Found by stem integration tests.
101 - Fix an invalid memory read that occured when a pluggable
102 transport proxy failed its configuration protocol.
103 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
104 - When evaluating whether to use a connection that we haven't
105 decided is canonical using a recent link protocol version,
106 decide that it's canonical only if it used address _does_
107 match the desired address. Fixes bug 9309; bugfix on
108 0.2.4.4-alpha. Reported by skruffy.
109 - Make the default behavior of NumDirectoryGuards be to track
110 NumEntryGuards. Now a user who changes only NumEntryGuards will get
111 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
112 - Fix a spurious compilation warning with some older versions of
113 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
116 - Update to the July 3 2013 Maxmind GeoLite Country database.
119 Changes in version 0.2.4.15-rc - 2013-07-01
120 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
121 series. It fixes a few smaller bugs, but generally appears stable.
122 Please test it and let us know whether it is!
125 - When receiving a new configuration file via the control port's
126 LOADCONF command, do not treat the defaults file as absent.
127 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
130 - Issue a warning when running with the bufferevents backend enabled.
131 It's still not stable, and people should know that they're likely
132 to hit unexpected problems. Closes ticket 9147.
135 Changes in version 0.2.4.14-alpha - 2013-06-18
136 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
137 present in 0.2.4.13-alpha.
140 - When we have too much memory queued in circuits (according to a new
141 MaxMemInCellQueues option), close the circuits consuming the most
142 memory. This prevents us from running out of memory as a relay if
143 circuits fill up faster than they can be drained. Fixes bug 9063;
144 bugfix on the 54th commit of Tor. This bug is a further fix beyond
145 bug 6252, whose fix was merged into 0.2.3.21-rc.
147 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
148 where we tried to solve this issue simply by imposing an upper limit
149 on the number of queued cells for a single circuit. That approach
150 proved to be problematic, since there are ways to provoke clients to
151 send a number of cells in excess of any such reasonable limit. Fixes
152 bug 9072; bugfix on 0.2.4.13-alpha.
154 - Limit hidden service descriptors to at most ten introduction
155 points, to slow one kind of guard enumeration. Fixes bug 9002;
156 bugfix on 0.1.1.11-alpha.
159 Changes in version 0.2.4.13-alpha - 2013-06-14
160 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
161 vulnerabilities, makes socks5 username/password circuit isolation
162 actually actually work (this time for sure!), and cleans up a bunch
163 of other issues in preparation for a release candidate.
165 o Major bugfixes (robustness):
166 - Close any circuit that has too many cells queued on it. Fixes
167 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
168 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
169 - Prevent the get_freelists() function from running off the end of
170 the list of freelists if it somehow gets an unrecognized
171 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
173 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
174 when an exit connection with optimistic data succeeds immediately
175 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
177 - Fix a directory authority crash bug when building a consensus
178 using an older consensus as its basis. Fixes bug 8833. Bugfix
182 - Avoid a memory leak where we would leak a consensus body when we
183 find that a consensus which we couldn't previously verify due to
184 missing certificates is now verifiable. Fixes bug 8719; bugfix
186 - We used to always request authority certificates by identity digest,
187 meaning we'd get the newest one even when we wanted one with a
188 different signing key. Then we would complain about being given
189 a certificate we already had, and never get the one we really
190 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
191 resource to request the one we want. Fixes bug 5595; bugfix on
193 - Follow the socks5 protocol when offering username/password
194 authentication. The fix for bug 8117 exposed this bug, and it
195 turns out real-world applications like Pidgin do care. Bugfix on
196 0.2.3.2-alpha; fixes bug 8879.
197 - Prevent failures on Windows Vista and later when rebuilding the
198 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
199 bugfix on 0.2.4.12-alpha.
202 - Fix an impossible buffer overrun in the AES unit tests. Fixes
203 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
204 - If for some reason we fail to write a microdescriptor while
205 rebuilding the cache, do not let the annotations from that
206 microdescriptor linger in the cache file, and do not let the
207 microdescriptor stay recorded as present in its old location.
208 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
209 - Fix a memory leak that would occur whenever a configuration
210 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
211 - Paste the description for PathBias parameters from the man
212 page into or.h, so the code documents them too. Fixes bug 7982;
213 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
214 - Relays now treat a changed IPv6 ORPort as sufficient reason to
215 publish an updated descriptor. Fixes bug 6026; bugfix on
217 - When launching a resolve request on behalf of an AF_UNIX control
218 socket, omit the address field of the new entry connection, used in
219 subsequent controller events, rather than letting tor_dup_addr()
220 set it to "<unknown address type>". Fixes bug 8639; bugfix on
223 o Minor bugfixes (log messages):
224 - Fix a scaling issue in the path bias accounting code that
225 resulted in "Bug:" log messages from either
226 pathbias_scale_close_rates() or pathbias_count_build_success().
227 This represents a bugfix on a previous bugfix: the original fix
228 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
230 - Give a less useless error message when the user asks for an IPv4
231 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
235 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
236 to tolerate bug 8093 for now.
237 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
238 in directory authority votes to describe whether they have enough
239 measured bandwidths to ignore advertised (relay descriptor)
240 bandwidth claims. Resolves ticket 8711.
241 - Update to the June 5 2013 Maxmind GeoLite Country database.
243 o Removed documentation:
244 - Remove some of the older contents of doc/ as obsolete; move others
245 to torspec.git. Fixes bug 8965.
247 o Code simplification and refactoring:
248 - Avoid using character buffers when constructing most directory
249 objects: this approach was unwieldy and error-prone. Instead,
250 build smartlists of strings, and concatenate them when done.
253 Changes in version 0.2.4.12-alpha - 2013-04-18
254 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
255 process for lengthening the guard rotation period, makes directory
256 authority opinions in the consensus a bit less gameable, makes socks5
257 username/password circuit isolation actually work, and fixes a wide
258 variety of other issues.
261 - Raise the default time that a client keeps an entry guard from
262 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
263 2012 paper. (We would make it even longer, but we need better client
264 load balancing first.) Also, make the guard lifetime controllable
265 via a new GuardLifetime torrc option and a GuardLifetime consensus
266 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
267 - Directory authorities now prefer using measured bandwidths to
268 advertised ones when computing flags and thresholds. Resolves
270 - Directory authorities that have more than a threshold number
271 of relays with measured bandwidths now treat relays with unmeasured
272 bandwidths as having bandwidth 0. Resolves ticket 8435.
274 o Major bugfixes (assert / resource use):
275 - Avoid a bug where our response to TLS renegotiation under certain
276 network conditions could lead to a busy-loop, with 100% CPU
277 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
278 - Avoid an assertion when we discover that we'd like to write a cell
279 onto a closing connection: just discard the cell. Fixes another
280 case of bug 7350; bugfix on 0.2.4.4-alpha.
282 o Major bugfixes (client-side privacy):
283 - When we mark a circuit as unusable for new circuits, have it
284 continue to be unusable for new circuits even if MaxCircuitDirtiness
285 is increased too much at the wrong time, or the system clock jumps
286 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
287 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
288 which have resolved to internal addresses") is set, apply that
289 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
290 - When an exit relay rejects a stream with reason "exit policy", but
291 we only know an exit policy summary (e.g. from the microdesc
292 consensus) for it, do not mark the relay as useless for all exiting.
293 Instead, mark just the circuit as unsuitable for that particular
294 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
295 - Allow applications to get proper stream isolation with
296 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
297 username/password authentication also offer "no authentication". Tor
298 had previously preferred "no authentication", so the applications
299 never actually sent Tor their auth details. Now Tor selects
300 username/password authentication if it's offered. You can disable
301 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
302 bug 8117; bugfix on 0.2.3.3-alpha.
304 o Major bugfixes (other):
305 - When unable to find any working directory nodes to use as a
306 directory guard, give up rather than adding the same non-working
307 nodes to the directory guard list over and over. Fixes bug 8231;
308 bugfix on 0.2.4.8-alpha.
311 - Reject as invalid most directory objects containing a NUL.
312 Belt-and-suspender fix for bug 8037.
313 - In our testsuite, create temporary directories with a bit more
314 entropy in their name to make name collisions less likely. Fixes
316 - Add CACHED keyword to ADDRMAP events in the control protocol
317 to indicate whether a DNS result will be cached or not. Resolves
319 - Update to the April 3 2013 Maxmind GeoLite Country database.
321 o Minor features (build):
322 - Detect and reject attempts to build Tor with threading support
323 when OpenSSL has been compiled without threading support.
325 - Clarify that when autoconf is checking for nacl, it is checking
326 specifically for nacl with a fast curve25519 implementation.
328 - Warn if building on a platform with an unsigned time_t: there
329 are too many places where Tor currently assumes that time_t can
330 hold negative values. We'd like to fix them all, but probably
333 o Minor bugfixes (build):
334 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
335 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
336 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
337 - Add the old src/or/micro-revision.i filename to CLEANFILES.
338 On the off chance that somebody has one, it will go away as soon
339 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
340 - Build Tor correctly on 32-bit platforms where the compiler can build
341 but not run code using the "uint128_t" construction. Fixes bug 8587;
342 bugfix on 0.2.4.8-alpha.
343 - Fix compilation warning with some versions of clang that would
344 prefer the -Wswitch-enum compiler flag to warn about switch
345 statements with missing enum values, even if those switch
346 statements have a "default:" statement. Fixes bug 8598; bugfix
349 o Minor bugfixes (protocol):
350 - Fix the handling of a TRUNCATE cell when it arrives while the
351 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
352 - Fix a misframing issue when reading the version numbers in a
353 VERSIONS cell. Previously we would recognize [00 01 00 02] as
354 'version 1, version 2, and version 0x100', when it should have
355 only included versions 1 and 2. Fixes bug 8059; bugfix on
356 0.2.0.10-alpha. Reported pseudonymously.
357 - Make the format and order of STREAM events for DNS lookups
358 consistent among the various ways to launch DNS lookups. Fixes
359 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
360 - Correct our check for which versions of Tor support the EXTEND2
361 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
362 later, when support was really added in version 0.2.4.8-alpha.
363 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
365 o Minor bugfixes (other):
366 - Correctly store microdescriptors and extrainfo descriptors with
367 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
368 Bug reported by "cypherpunks".
369 - Increase the width of the field used to remember a connection's
370 link protocol version to two bytes. Harmless for now, since the
371 only currently recognized versions are one byte long. Reported
372 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
373 - If the state file's path bias counts are invalid (presumably from a
374 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
375 additional checks and log messages to the scaling of Path Bias
376 counts, in case there still are remaining issues with scaling.
377 Should help resolve bug 8235.
378 - Eliminate several instances where we use "Nickname=ID" to refer to
379 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
380 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
381 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
383 o Minor bugfixes (syscalls):
384 - Always check the return values of functions fcntl() and
385 setsockopt(). We don't believe these are ever actually failing in
386 practice, but better safe than sorry. Also, checking these return
387 values should please analysis tools like Coverity. Patch from
388 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
389 - Use direct writes rather than stdio when building microdescriptor
390 caches, in an attempt to mitigate bug 8031, or at least make it
393 o Minor bugfixes (config):
394 - When rejecting a configuration because we were unable to parse a
395 quoted string, log an actual error message. Fixes bug 7950; bugfix
397 - Behave correctly when the user disables LearnCircuitBuildTimeout
398 but doesn't tell us what they would like the timeout to be. Fixes
399 bug 6304; bugfix on 0.2.2.14-alpha.
400 - When autodetecting the number of CPUs, use the number of available
401 CPUs in preference to the number of configured CPUs. Inform the
402 user if this reduces the number of available CPUs. Fixes bug 8002;
403 bugfix on 0.2.3.1-alpha.
404 - Make it an error when you set EntryNodes but disable UseGuardNodes,
405 since it will (surprisingly to some users) ignore EntryNodes. Fixes
406 bug 8180; bugfix on 0.2.3.11-alpha.
407 - Allow TestingTorNetworks to override the 4096-byte minimum for
408 the Fast threshold. Otherwise they can't bootstrap until they've
409 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
410 - Fix some logic errors when the user manually overrides the
411 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
414 o Minor bugfixes (log messages to help diagnose bugs):
415 - If we fail to free a microdescriptor because of bug 7164, log
416 the filename and line number from which we tried to free it.
417 - Add another diagnostic to the heartbeat message: track and log
418 overhead that TLS is adding to the data we write. If this is
419 high, we are sending too little data to SSL_write at a time.
420 Diagnostic for bug 7707.
421 - Add more detail to a log message about relaxed timeouts, to help
423 - Warn more aggressively when flushing microdescriptors to a
424 microdescriptor cache fails, in an attempt to mitigate bug 8031,
425 or at least make it more diagnosable.
426 - Improve debugging output to help track down bug 8185 ("Bug:
427 outgoing relay cell has n_chan==NULL. Dropping.")
428 - Log the purpose of a path-bias testing circuit correctly.
429 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
431 o Minor bugfixes (0.2.4.x log messages that were too noisy):
432 - Don't attempt to relax the timeout of already opened 1-hop circuits.
433 They might never timeout. This should eliminate some/all cases of
434 the relaxed timeout log message.
435 - Use circuit creation time for network liveness evaluation. This
436 should eliminate warning log messages about liveness caused
437 by changes in timeout evaluation. Fixes bug 6572; bugfix on
439 - Reduce a path bias length check from notice to info. The message
440 is triggered when creating controller circuits. Fixes bug 8196;
441 bugfix on 0.2.4.8-alpha.
442 - Fix a path state issue that triggered a notice during relay startup.
443 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
444 - Reduce occurrences of warns about circuit purpose in
445 connection_ap_expire_building(). Fixes bug 8477; bugfix on
448 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
449 - If we encounter a write failure on a SOCKS connection before we
450 finish our SOCKS handshake, don't warn that we closed the
451 connection before we could send a SOCKS reply. Fixes bug 8427;
452 bugfix on 0.1.0.1-rc.
453 - Correctly recognize that [::1] is a loopback address. Fixes
454 bug 8377; bugfix on 0.2.1.3-alpha.
455 - Fix a directory authority warn caused when we have a large amount
456 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
457 - Don't log inappropriate heartbeat messages when hibernating: a
458 hibernating node is _expected_ to drop out of the consensus,
459 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
460 bugfix on 0.2.3.1-alpha.
461 - Don't complain about bootstrapping problems while hibernating.
462 These complaints reflect a general code problem, but not one
463 with any problematic effects (no connections are actually
464 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
466 o Documentation fixes:
467 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
468 names match. Fixes bug 7768.
469 - Make the torify manpage no longer refer to tsocks; torify hasn't
470 supported tsocks since 0.2.3.14-alpha.
471 - Make the tor manpage no longer reference tsocks.
472 - Fix the GeoIPExcludeUnknown documentation to refer to
473 ExcludeExitNodes rather than the currently nonexistent
474 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
477 - The tor-tsocks.conf is no longer distributed or installed. We
478 recommend that tsocks users use torsocks instead. Resolves
482 Changes in version 0.2.4.11-alpha - 2013-03-11
483 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
484 more robust, makes hidden service authentication work again, and
485 resolves a DPI fingerprint for Tor's SSL transport.
487 o Major features (directory authorities):
488 - Directory authorities now support a new consensus method (17)
489 where they cap the published bandwidth of servers for which
490 insufficient bandwidth measurements exist. Fixes part of bug 2286.
491 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
492 serve any v2 directory information. Now we can test disabling the
493 old deprecated v2 directory format, and see whether doing so has
494 any effect on network load. Begins to fix bug 6783.
495 - Directory authorities now include inside each vote a statement of
496 the performance thresholds they used when assigning flags.
497 Implements ticket 8151.
499 o Major bugfixes (directory authorities):
500 - Stop marking every relay as having been down for one hour every
501 time we restart a directory authority. These artificial downtimes
502 were messing with our Stable and Guard flag calculations. Fixes
503 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
505 o Major bugfixes (hidden services):
506 - Allow hidden service authentication to succeed again. When we
507 refactored the hidden service introduction code back
508 in 0.2.4.1-alpha, we didn't update the code that checks
509 whether authentication information is present, causing all
510 authentication checks to return "false". Fix for bug 8207; bugfix
511 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
513 o Minor features (relays, bridges):
514 - Make bridge relays check once a minute for whether their IP
515 address has changed, rather than only every 15 minutes. Resolves
517 - Refactor resolve_my_address() so it returns the method by which we
518 decided our public IP address (explicitly configured, resolved from
519 explicit hostname, guessed from interfaces, learned by gethostname).
520 Now we can provide more helpful log messages when a relay guesses
521 its IP address incorrectly (e.g. due to unexpected lines in
522 /etc/hosts). Resolves ticket 2267.
523 - Teach bridge-using clients to avoid 0.2.2 bridges when making
524 microdescriptor-related dir requests, and only fall back to normal
525 descriptors if none of their bridges can handle microdescriptors
526 (as opposed to the fix in ticket 4013, which caused them to fall
527 back to normal descriptors if *any* of their bridges preferred
528 them). Resolves ticket 4994.
529 - Randomize the lifetime of our SSL link certificate, so censors can't
530 use the static value for filtering Tor flows. Resolves ticket 8443;
531 related to ticket 4014 which was included in 0.2.2.33.
533 o Minor features (portability):
534 - Tweak the curve25519-donna*.c implementations to tolerate systems
535 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
536 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
537 the signs of types during autoconf. This is better than our old
538 approach, which didn't work when cross-compiling.
539 - Detect the sign of enum values, rather than assuming that MSC is the
540 only compiler where enum types are all signed. Fixes bug 7727;
541 bugfix on 0.2.4.10-alpha.
543 o Minor features (other):
544 - Say "KBytes" rather than "KB" in the man page (for various values
545 of K), to further reduce confusion about whether Tor counts in
546 units of memory or fractions of units of memory. Resolves ticket 7054.
547 - Clear the high bit on curve25519 public keys before passing them to
548 our backend, in case we ever wind up using a backend that doesn't do
549 so itself. If we used such a backend, and *didn't* clear the high bit,
550 we could wind up in a situation where users with such backends would
551 be distinguishable from users without. Fixes bug 8121; bugfix on
553 - Update to the March 6 2013 Maxmind GeoLite Country database.
555 o Minor bugfixes (clients):
556 - When we receive a RELAY_END cell with the reason DONE, or with no
557 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
558 status as "connection refused". Previously we reported these cases
559 as success but then immediately closed the connection. Fixes bug
560 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
561 - Downgrade an assertion in connection_ap_expire_beginning to an
562 LD_BUG message. The fix for bug 8024 should prevent this message
563 from displaying, but just in case, a warn that we can diagnose
564 is better than more assert crashes. Fixes bug 8065; bugfix on
566 - Lower path use bias thresholds to .80 for notice and .60 for warn.
567 Also make the rate limiting flags for the path use bias log messages
568 independent from the original path bias flags. Fixes bug 8161;
569 bugfix on 0.2.4.10-alpha.
571 o Minor bugfixes (relays):
572 - Stop trying to resolve our hostname so often (e.g. every time we
573 think about doing a directory fetch). Now we reuse the cached
574 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
575 and 2410 (bugfix on 0.1.2.2-alpha).
576 - Stop sending a stray "(null)" in some cases for the server status
577 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
579 - When choosing which stream on a formerly stalled circuit to wake
580 first, make better use of the platform's weak RNG. Previously,
581 we had been using the % ("modulo") operator to try to generate a
582 1/N chance of picking each stream, but this behaves badly with
583 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
585 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
586 Irix's random() only return 15 bits; Solaris's random() returns more
587 bits but its RAND_MAX says it only returns 15, and so on. Motivated
588 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
590 o Minor bugfixes (directory authorities):
591 - Directory authorities now use less space when formatting identical
592 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
595 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
596 - Avoid leaking memory if we fail to compute a consensus signature
597 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
598 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
600 - Fix a memory leak during safe-cookie controller authentication.
601 Bugfix on 0.2.3.13-alpha.
602 - Avoid memory leak of IPv6 policy content if we fail to format it into
603 a router descriptor. Bugfix on 0.2.4.7-alpha.
605 o Minor bugfixes (other code correctness issues):
606 - Avoid a crash if we fail to generate an extrainfo descriptor.
607 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
609 - When detecting the largest possible file descriptor (in order to
610 close all file descriptors when launching a new program), actually
611 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
612 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
614 - Fix a copy-and-paste error when adding a missing A1 to a routerset
615 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
616 Bugfix on 0.2.4.10-alpha.
617 - Fix an impossible-to-trigger integer overflow when estimating how
618 long our onionskin queue would take. (This overflow would require us
619 to accept 4 million onionskins before processing 100 of them.) Fixes
620 bug 8210; bugfix on 0.2.4.10-alpha.
622 o Code simplification and refactoring:
623 - Add a wrapper function for the common "log a message with a
627 Changes in version 0.2.4.10-alpha - 2013-02-04
628 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
629 certain attacks that flood the network with relays; changes the queue
630 for circuit create requests from a sized-based limit to a time-based
631 limit; resumes building with MSVC on Windows; and fixes a wide variety
634 o Major bugfixes (directory authority):
635 - When computing directory thresholds, ignore any rejected-as-sybil
636 nodes during the computation so that they can't influence Fast,
637 Guard, etc. (We should have done this for proposal 109.) Fixes
639 - When marking a node as a likely sybil, reset its uptime metrics
640 to zero, so that it cannot time towards getting marked as Guard,
641 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
645 - When a TLS write is partially successful but incomplete, remember
646 that the flushed part has been flushed, and notice that bytes were
647 actually written. Reported and fixed pseudonymously. Fixes bug
648 7708; bugfix on Tor 0.1.0.5-rc.
649 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
650 ID: these could be used to create unexpected streams and circuits
651 which would count as "present" to some parts of Tor but "absent"
652 to others, leading to zombie circuits and streams or to a bandwidth
653 denial-of-service. Fixes bug 7889; bugfix on every released version
654 of Tor. Reported by "oftc_must_be_destroyed".
655 - Rename all macros in our local copy of queue.h to begin with "TOR_".
656 This change seems the only good way to permanently prevent conflicts
657 with queue.h on various operating systems. Fixes bug 8107; bugfix
660 o Major features (relay):
661 - Instead of limiting the number of queued onionskins (aka circuit
662 create requests) to a fixed, hard-to-configure number, we limit
663 the size of the queue based on how many we expect to be able to
664 process in a given amount of time. We estimate the time it will
665 take to process an onionskin based on average processing time
666 of previous onionskins. Closes ticket 7291. You'll never have to
667 configure MaxOnionsPending again.
669 o Major features (portability):
670 - Resume building correctly with MSVC and Makefile.nmake. This patch
671 resolves numerous bugs and fixes reported by ultramage, including
672 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
673 - Make the ntor and curve25519 code build correctly with MSVC.
674 Fix on 0.2.4.8-alpha.
677 - When directory authorities are computing thresholds for flags,
678 never let the threshold for the Fast flag fall below 4096
679 bytes. Also, do not consider nodes with extremely low bandwidths
680 when deciding thresholds for various directory flags. This change
681 should raise our threshold for Fast relays, possibly in turn
682 improving overall network performance; see ticket 1854. Resolves
684 - The Tor client now ignores sub-domain components of a .onion
685 address. This change makes HTTP "virtual" hosting
686 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
687 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
688 hosted on the same hidden service. Implements proposal 204.
689 - We compute the overhead from passing onionskins back and forth to
690 cpuworkers, and report it when dumping statistics in response to
691 SIGUSR1. Supports ticket 7291.
693 o Minor features (path selection):
694 - When deciding whether we have enough descriptors to build circuits,
695 instead of looking at raw relay counts, look at which fraction
696 of (bandwidth-weighted) paths we're able to build. This approach
697 keeps clients from building circuits if their paths are likely to
698 stand out statistically. The default fraction of paths needed is
699 taken from the consensus directory; you can override it with the
700 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
701 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
702 and we have GeoIP information, also exclude all nodes with unknown
703 countries "??" and "A1". This behavior is controlled by the
704 new GeoIPExcludeUnknown option: you can make such nodes always
705 excluded with "GeoIPExcludeUnknown 1", and disable the feature
706 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
707 gets you the default behavior. Implements feature 7706.
708 - Path Use Bias: Perform separate accounting for successful circuit
709 use. Keep separate statistics on stream attempt rates versus stream
710 success rates for each guard. Provide configurable thresholds to
711 determine when to emit log messages or disable use of guards that
712 fail too many stream attempts. Resolves ticket 7802.
714 o Minor features (log messages):
715 - When learning a fingerprint for a bridge, log its corresponding
716 transport type. Implements ticket 7896.
717 - Improve the log message when "Bug/attack: unexpected sendme cell
718 from client" occurs, to help us track bug 8093.
721 - Remove a couple of extraneous semicolons that were upsetting the
722 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
723 bugfix on 0.2.2.1-alpha.
724 - Remove a source of rounding error during path bias count scaling;
725 don't count cannibalized circuits as used for path bias until we
726 actually try to use them; and fix a circuit_package_relay_cell()
727 warning message about n_chan==NULL. Fixes bug 7802.
728 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
729 actually link against nacl when we're configured to use it. Fixes
730 bug 7972; bugfix on 0.2.4.8-alpha.
731 - Compile correctly with the --disable-curve25519 option. Fixes
732 bug 8153; bugfix on 0.2.4.8-alpha.
734 o Build improvements:
735 - Do not report status verbosely from autogen.sh unless the -v flag
736 is specified. Fixes issue 4664. Patch from Onizuka.
737 - Replace all calls to snprintf() outside of src/ext with
738 tor_snprintf(). Also remove the #define to replace snprintf with
739 _snprintf on Windows; they have different semantics, and all of
740 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
741 - Try to detect if we are ever building on a platform where
742 memset(...,0,...) does not set the value of a double to 0.0. Such
743 platforms are permitted by the C standard, though in practice
744 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
745 currently support them, but it's better to detect them and fail
746 than to perform erroneously.
749 - Stop exporting estimates of v2 and v3 directory traffic shares
750 in extrainfo documents. They were unneeded and sometimes inaccurate.
751 Also stop exporting any v2 directory request statistics. Resolves
753 - Drop support for detecting and warning about versions of Libevent
754 before 1.3e. Nothing reasonable ships with them any longer;
755 warning the user about them shouldn't be needed. Resolves ticket
758 o Code simplifications and refactoring:
759 - Rename "isin" functions to "contains", for grammar. Resolves
761 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
762 with the natural logarithm function from the system libm. Resolves
766 Changes in version 0.2.4.9-alpha - 2013-01-15
767 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
771 - Fix backward compatibility logic when receiving an embedded ntor
772 handshake tunneled in a CREATE cell. This clears up the "Bug:
773 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
777 Changes in version 0.2.4.8-alpha - 2013-01-14
778 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
779 risks, adds a new stronger and faster circuit handshake, and offers
780 stronger and faster link encryption when both sides support it.
783 - Preliminary support for directory guards (proposal 207): when
784 possible, clients now use their entry guards for non-anonymous
785 directory requests. This can help prevent client enumeration. Note
786 that this behavior only works when we have a usable consensus
787 directory, and when options about what to download are more or less
788 standard. In the future we should re-bootstrap from our guards,
789 rather than re-bootstrapping from the preconfigured list of
790 directory sources that ships with Tor. Resolves ticket 6526.
791 - Tor relays and clients now support a better CREATE/EXTEND cell
792 format, allowing the sender to specify multiple address, identity,
793 and handshake types. Implements Robert Ransom's proposal 200;
796 o Major features (new circuit handshake):
797 - Tor now supports a new circuit extension handshake designed by Ian
798 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
799 circuit extension handshake, later called "TAP", was a bit slow
800 (especially on the relay side), had a fragile security proof, and
801 used weaker keys than we'd now prefer. The new circuit handshake
802 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
803 function, making it significantly more secure than the older
804 handshake, and significantly faster. Tor can use one of two built-in
805 pure-C curve25519-donna implementations by Adam Langley, or it
806 can link against the "nacl" library for a tuned version if present.
808 The built-in version is very fast for 64-bit systems when building
809 with GCC. The built-in 32-bit version is still faster than the
810 old TAP protocol, but using libnacl is better on most such hosts.
812 Clients don't currently use this protocol by default, since
813 comparatively few clients support it so far. To try it, set
814 UseNTorHandshake to 1.
816 Implements proposal 216; closes ticket 7202.
818 o Major features (better link encryption):
819 - Relays can now enable the ECDHE TLS ciphersuites when available
820 and appropriate. These ciphersuites let us negotiate forward-secure
821 TLS secret keys more safely and more efficiently than with our
822 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
823 public relays prefer the (faster) P224 group, and bridges prefer
824 the (more common) P256 group; you can override this with the
827 Enabling these ciphers was a little tricky, since for a long time,
828 clients had been claiming to support them without actually doing
829 so, in order to foil fingerprinting. But with the client-side
830 implementation of proposal 198 in 0.2.3.17-beta, clients can now
831 match the ciphers from recent Firefox versions *and* list the
832 ciphers they actually mean, so relays can believe such clients
833 when they advertise ECDHE support in their TLS ClientHello messages.
835 This feature requires clients running 0.2.3.17-beta or later,
836 and requires both sides to be running OpenSSL 1.0.0 or later
837 with ECC support. OpenSSL 1.0.1, with the compile-time option
838 "enable-ec_nistp_64_gcc_128", is highly recommended.
840 Implements the relay side of proposal 198; closes ticket 7200.
843 - Avoid crashing when, as a relay without IPv6-exit support, a
844 client insists on getting an IPv6 address or nothing. Fixes bug
845 7814; bugfix on 0.2.4.7-alpha.
848 - Improve circuit build timeout handling for hidden services.
849 In particular: adjust build timeouts more accurately depending
850 upon the number of hop-RTTs that a particular circuit type
851 undergoes. Additionally, launch intro circuits in parallel
852 if they timeout, and take the first one to reply as valid.
853 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
854 separate error codes; or at least, don't break for that reason.
855 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
856 - Update to the January 2 2013 Maxmind GeoLite Country database.
858 o Minor features (testing):
859 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
860 (P-256) Diffie-Hellman handshakes to src/or/bench.
861 - Add benchmark functions to test onion handshake performance.
863 o Minor features (path bias detection):
864 - Alter the Path Bias log messages to be more descriptive in terms
865 of reporting timeouts and other statistics.
866 - Create three levels of Path Bias log messages, as opposed to just
867 two. These are configurable via consensus as well as via the torrc
868 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
869 The default values are 0.70, 0.50, and 0.30 respectively.
870 - Separate the log message levels from the decision to drop guards,
871 which also is available via torrc option PathBiasDropGuards.
872 PathBiasDropGuards still defaults to 0 (off).
873 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
874 in combination with PathBiasExtremeRate.
875 - Increase the default values for PathBiasScaleThreshold and
876 PathBiasCircThreshold from (200, 20) to (300, 150).
877 - Add in circuit usage accounting to path bias. If we try to use a
878 built circuit but fail for any reason, it counts as path bias.
879 Certain classes of circuits where the adversary gets to pick your
880 destination node are exempt from this accounting. Usage accounting
881 can be specifically disabled via consensus parameter or torrc.
882 - Convert all internal path bias state to double-precision floating
883 point, to avoid roundoff error and other issues.
884 - Only record path bias information for circuits that have completed
885 *two* hops. Assuming end-to-end tagging is the attack vector, this
886 makes us more resilient to ambient circuit failure without any
887 detection capability loss.
889 o Minor bugfixes (log messages):
890 - Rate-limit the "No circuits are opened. Relaxed timeout for a
891 circuit with channel state open..." message to once per hour to
892 keep it from filling the notice logs. Mitigates bug 7799 but does
893 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
894 - Avoid spurious warnings when configuring multiple client ports of
895 which only some are nonlocal. Previously, we had claimed that some
896 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
899 o Code simplifications and refactoring:
900 - Get rid of a couple of harmless clang warnings, where we compared
901 enums to ints. These warnings are newly introduced in clang 3.2.
902 - Split the onion.c file into separate modules for the onion queue
903 and the different handshakes it supports.
904 - Remove the marshalling/unmarshalling code for sending requests to
905 cpuworkers over a socket, and instead just send structs. The
906 recipient will always be the same Tor binary as the sender, so
907 any encoding is overkill.
910 Changes in version 0.2.4.7-alpha - 2012-12-24
911 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
912 directory mirrors for more robust bootstrapping; fixes more issues where
913 clients with changing network conditions refuse to make any circuits;
914 adds initial support for exiting to IPv6 addresses; resumes being able
915 to update our GeoIP database, and includes the geoip6 file this time;
916 turns off the client-side DNS cache by default due to privacy risks;
917 and fixes a variety of other issues.
919 o Major features (client resilience):
920 - Add a new "FallbackDir" torrc option to use when we can't use
921 a directory mirror from the consensus (either because we lack a
922 consensus, or because they're all down). Currently, all authorities
923 are fallbacks by default, and there are no other default fallbacks,
924 but that will change. This option will allow us to give clients a
925 longer list of servers to try to get a consensus from when first
926 connecting to the Tor network, and thereby reduce load on the
927 directory authorities. Implements proposal 206, "Preconfigured
928 directory sources for bootstrapping". We also removed the old
929 "FallbackNetworkstatus" option, since we never got it working well
930 enough to use it. Closes bug 572.
931 - If we have no circuits open, use a relaxed timeout (the
932 95-percentile cutoff) until a circuit succeeds. This heuristic
933 should allow Tor to succeed at building circuits even when the
934 network connection drastically changes. Should help with bug 3443.
936 o Major features (IPv6):
937 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
938 connectivity, then set the IPv6Exit flag to 1. Also make sure your
939 exit policy reads as you would like: the address * applies to all
940 address families, whereas *4 is IPv4 address only, and *6 is IPv6
941 addresses only. On the client side, you'll need to wait until the
942 authorities have upgraded, wait for enough exits to support IPv6,
943 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
944 ticket 5547, implements proposal 117 as revised in proposal 208.
946 We DO NOT recommend that clients with actual anonymity needs start
947 using IPv6 over Tor yet, since not enough exits support it yet.
949 o Major features (geoip database):
950 - Maxmind began labelling Tor relays as being in country "A1",
951 which breaks by-country node selection inside Tor. Now we use a
952 script to replace "A1" ("Anonymous Proxy") entries in our geoip
953 file with real country codes. This script fixes about 90% of "A1"
954 entries automatically and uses manual country code assignments to
955 fix the remaining 10%. See src/config/README.geoip for details.
956 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
957 Country database, as modified above.
959 o Major bugfixes (client-side DNS):
960 - Turn off the client-side DNS cache by default. Updating and using
961 the DNS cache is now configurable on a per-client-port
962 level. SOCKSPort, DNSPort, etc lines may now contain
963 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
964 cache these types of DNS answers when we receive them from an
965 exit node in response to an application request on this port, and
966 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
967 cached DNS answers of these types, we shouldn't use them. It's
968 potentially risky to use cached DNS answers at the client, since
969 doing so can indicate to one exit what answers we've gotten
970 for DNS lookups in the past. With IPv6, this becomes especially
971 problematic. Using cached DNS answers for requests on the same
972 circuit would present less linkability risk, since all traffic
973 on a circuit is already linkable, but it would also provide
974 little performance benefit: the exit node caches DNS replies
975 too. Implements a simplified version of Proposal 205. Implements
978 o Major bugfixes (other):
979 - Alter circuit build timeout measurement to start at the point
980 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
981 initialization). This should make our timeout measurements more
982 uniform. Previously, we were sometimes including ORconn setup time
983 in our circuit build time measurements. Should resolve bug 3443.
984 - Fix an assertion that could trigger in hibernate_go_dormant() when
985 closing an or_connection_t: call channel_mark_for_close() rather
986 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
988 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
989 7655; bugfix on 0.2.4.6-alpha.
992 - Add a new torrc option "ServerTransportListenAddr" to let bridge
993 operators select the address where their pluggable transports will
994 listen for connections. Resolves ticket 7013.
995 - Allow an optional $ before the node identity digest in the
996 controller command GETINFO ns/id/<identity>, for consistency with
997 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
998 - Log packaged cell fullness as part of the heartbeat message.
999 Diagnosis to try to determine the extent of bug 7743.
1001 o Minor features (IPv6):
1002 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
1003 prefer to hand out virtual IPv6 addresses, since there are more of
1004 them and we can't run out. To override this behavior and make IPv4
1005 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
1006 or DNSPort you're using for resolving. Implements ticket 7571.
1007 - AutomapHostsOnResolve responses are now randomized, to avoid
1008 annoying situations where Tor is restarted and applications
1009 connect to the wrong addresses.
1010 - Never try more than 1000 times to pick a new virtual address when
1011 AutomapHostsOnResolve is set. That's good enough so long as we
1012 aren't close to handing out our entire virtual address space;
1013 if you're getting there, it's best to switch to IPv6 virtual
1017 - The ADDRMAP command can no longer generate an ill-formed error
1018 code on a failed MAPADDRESS. It now says "internal" rather than
1019 an English sentence fragment with spaces in the middle. Bugfix on
1021 - Fix log messages and comments to avoid saying "GMT" when we mean
1022 "UTC". Fixes bug 6113.
1023 - Compile on win64 using mingw64. Fixes bug 7260; patches from
1025 - Fix a crash when debugging unit tests on Windows: deallocate a
1026 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
1027 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
1030 - The DirServer option is now DirAuthority, for consistency with
1031 current naming patterns. You can still use the old DirServer form.
1033 o Code simplification and refactoring:
1034 - Move the client-side address-map/virtual-address/DNS-cache code
1035 out of connection_edge.c into a new addressmap.c module.
1036 - Remove unused code for parsing v1 directories and "running routers"
1037 documents. Fixes bug 6887.
1040 Changes in version 0.2.3.25 - 2012-11-19
1041 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
1042 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
1043 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
1044 programmer, and friend. Unstinting in his dedication to the cause of
1045 freedom, he inspired and helped many of us as we began our work on
1046 anonymity, and inspires us still. Please honor his memory by writing
1047 software to protect people's freedoms, and by helping others to do so.
1049 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
1050 significantly reduced directory overhead (via microdescriptors),
1051 enormous crypto performance improvements for fast relays on new
1052 enough hardware, a new v3 TLS handshake protocol that can better
1053 resist fingerprinting, support for protocol obfuscation plugins (aka
1054 pluggable transports), better scalability for hidden services, IPv6
1055 support for bridges, performance improvements like allowing clients
1056 to skip the first round-trip on the circuit ("optimistic data") and
1057 refilling token buckets more often, a new "stream isolation" design
1058 to isolate different applications on different circuits, and many
1059 stability, security, and privacy fixes.
1062 - Tor tries to wipe potentially sensitive data after using it, so
1063 that if some subsequent security failure exposes Tor's memory,
1064 the damage will be limited. But we had a bug where the compiler
1065 was eliminating these wipe operations when it decided that the
1066 memory was no longer visible to a (correctly running) program,
1067 hence defeating our attempt at defense in depth. We fix that
1068 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1069 is unlikely to optimize away. Future versions of Tor may use
1070 a less ridiculously heavy approach for this. Fixes bug 7352.
1071 Reported in an article by Andrey Karpov.
1074 - Fix a harmless bug when opting against publishing a relay descriptor
1075 because DisableNetwork is set. Fixes bug 7464; bugfix on
1079 Changes in version 0.2.4.6-alpha - 2012-11-13
1080 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
1081 makes our defense-in-depth memory wiping more reliable, and begins to
1082 count IPv6 addresses in bridge statistics,
1085 - Fix an assertion failure that could occur when closing a connection
1086 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
1088 - Tor tries to wipe potentially sensitive data after using it, so
1089 that if some subsequent security failure exposes Tor's memory,
1090 the damage will be limited. But we had a bug where the compiler
1091 was eliminating these wipe operations when it decided that the
1092 memory was no longer visible to a (correctly running) program,
1093 hence defeating our attempt at defense in depth. We fix that
1094 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1095 is unlikely to optimize away. Future versions of Tor may use
1096 a less ridiculously heavy approach for this. Fixes bug 7352.
1097 Reported in an article by Andrey Karpov.
1100 - Add GeoIP database for IPv6 addresses. The new config option
1102 - Bridge statistics now count bridge clients connecting over IPv6:
1103 bridge statistics files now list "bridge-ip-versions" and
1104 extra-info documents list "geoip6-db-digest". The control protocol
1105 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
1106 implementation by "shkoo", addressing ticket 5055.
1109 - Warn when we are binding low ports when hibernation is enabled;
1110 previously we had warned when we were _advertising_ low ports with
1111 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
1112 - Fix a harmless bug when opting against publishing a relay descriptor
1113 because DisableNetwork is set. Fixes bug 7464; bugfix on
1115 - Add warning message when a managed proxy dies during configuration.
1116 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
1117 - Fix a linking error when building tor-fw-helper without miniupnp.
1118 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
1119 - Check for closing an or_connection_t without going through correct
1120 channel functions; emit a warning and then call
1121 connection_or_close_for_error() so we don't assert as in bugs 7212
1123 - Compile correctly on compilers without C99 designated initializer
1124 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
1125 - Avoid a possible assert that can occur when channel_send_destroy() is
1126 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
1127 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
1128 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
1129 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
1130 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
1132 o Code simplification and refactoring:
1133 - Start using OpenBSD's implementation of queue.h, so that we don't
1134 need to hand-roll our own pointer and list structures whenever we
1135 need them. (We can't rely on a sys/queue.h, since some operating
1136 systems don't have them, and the ones that do have them don't all
1137 present the same extensions.)
1140 Changes in version 0.2.4.5-alpha - 2012-10-25
1141 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
1142 two important security vulnerabilities that could lead to remotely
1143 triggerable relay crashes, fix a major bug that was preventing clients
1144 from choosing suitable exit nodes, and refactor some of our code.
1146 o Major bugfixes (security, also in 0.2.3.24-rc):
1147 - Fix a group of remotely triggerable assertion failures related to
1148 incorrect link protocol negotiation. Found, diagnosed, and fixed
1149 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1151 - Fix a denial of service attack by which any directory authority
1152 could crash all the others, or by which a single v2 directory
1153 authority could crash everybody downloading v2 directory
1154 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1156 o Major bugfixes (also in 0.2.3.24-rc):
1157 - When parsing exit policy summaries from microdescriptors, we had
1158 previously been ignoring the last character in each one, so that
1159 "accept 80,443,8080" would be treated by clients as indicating
1160 a node that allows access to ports 80, 443, and 808. That would
1161 lead to clients attempting connections that could never work,
1162 and ignoring exit nodes that would support their connections. Now
1163 clients parse these exit policy summaries correctly. Fixes bug 7192;
1164 bugfix on 0.2.3.1-alpha.
1166 o Minor bugfixes (also in 0.2.3.24-rc):
1167 - Clients now consider the ClientRejectInternalAddresses config option
1168 when using a microdescriptor consensus stanza to decide whether
1169 an exit relay would allow exiting to an internal address. Fixes
1170 bug 7190; bugfix on 0.2.3.1-alpha.
1173 - Only disable TLS session ticket support when running as a TLS
1174 server. Now clients will blend better with regular Firefox
1175 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
1177 o Code simplification and refactoring:
1178 - Start using OpenBSD's implementation of queue.h (originally by
1180 - Move the entry node code from circuitbuild.c to its own file.
1181 - Move the circuit build timeout tracking code from circuitbuild.c
1185 Changes in version 0.2.3.24-rc - 2012-10-25
1186 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
1187 could lead to remotely triggerable relay crashes, and fixes
1188 a major bug that was preventing clients from choosing suitable exit
1191 o Major bugfixes (security):
1192 - Fix a group of remotely triggerable assertion failures related to
1193 incorrect link protocol negotiation. Found, diagnosed, and fixed
1194 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1196 - Fix a denial of service attack by which any directory authority
1197 could crash all the others, or by which a single v2 directory
1198 authority could crash everybody downloading v2 directory
1199 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1202 - When parsing exit policy summaries from microdescriptors, we had
1203 previously been ignoring the last character in each one, so that
1204 "accept 80,443,8080" would be treated by clients as indicating
1205 a node that allows access to ports 80, 443, and 808. That would
1206 lead to clients attempting connections that could never work,
1207 and ignoring exit nodes that would support their connections. Now
1208 clients parse these exit policy summaries correctly. Fixes bug 7192;
1209 bugfix on 0.2.3.1-alpha.
1212 - Clients now consider the ClientRejectInternalAddresses config option
1213 when using a microdescriptor consensus stanza to decide whether
1214 an exit relay would allow exiting to an internal address. Fixes
1215 bug 7190; bugfix on 0.2.3.1-alpha.
1218 Changes in version 0.2.4.4-alpha - 2012-10-20
1219 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
1220 vulnerability introduced by a change in OpenSSL, fixes a remotely
1221 triggerable assert, and adds new channel_t and circuitmux_t abstractions
1222 that will make it easier to test new connection transport and cell
1223 scheduling algorithms.
1225 o New directory authorities (also in 0.2.3.23-rc):
1226 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1227 authority. Closes ticket 5749.
1229 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
1230 - Disable TLS session tickets. OpenSSL's implementation was giving
1231 our TLS session keys the lifetime of our TLS context objects, when
1232 perfect forward secrecy would want us to discard anything that
1233 could decrypt a link connection as soon as the link connection
1234 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1235 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1236 - Discard extraneous renegotiation attempts once the V3 link
1237 protocol has been initiated. Failure to do so left us open to
1238 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1239 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1241 o Internal abstraction features:
1242 - Introduce new channel_t abstraction between circuits and
1243 or_connection_t to allow for implementing alternate OR-to-OR
1244 transports. A channel_t is an abstract object which can either be a
1245 cell-bearing channel, which is responsible for authenticating and
1246 handshaking with the remote OR and transmitting cells to and from
1247 it, or a listening channel, which spawns new cell-bearing channels
1248 at the request of remote ORs. Implements part of ticket 6465.
1249 - Also new is the channel_tls_t subclass of channel_t, adapting it
1250 to the existing or_connection_t code. The V2/V3 protocol handshaking
1251 code which formerly resided in command.c has been moved below the
1252 channel_t abstraction layer and may be found in channeltls.c now.
1253 Implements the rest of ticket 6465.
1254 - Introduce new circuitmux_t storing the queue of circuits for
1255 a channel; this encapsulates and abstracts the queue logic and
1256 circuit selection policy, and allows the latter to be overridden
1257 easily by switching out a policy object. The existing EWMA behavior
1258 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
1260 o Required libraries:
1261 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
1262 strongly recommended.
1265 - Warn users who run hidden services on a Tor client with
1266 UseEntryGuards disabled that their hidden services will be
1267 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
1268 attack which motivated Tor to support entry guards in the first
1269 place). Resolves ticket 6889.
1270 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
1271 dhill. Resolves ticket 6982.
1272 - Option OutboundBindAddress can be specified multiple times and
1273 accepts IPv6 addresses. Resolves ticket 6876.
1275 o Minor bugfixes (also in 0.2.3.23-rc):
1276 - Don't serve or accept v2 hidden service descriptors over a
1277 relay's DirPort. It's never correct to do so, and disabling it
1278 might make it more annoying to exploit any bugs that turn up in the
1279 descriptor-parsing code. Fixes bug 7149.
1280 - Fix two cases in src/or/transports.c where we were calling
1281 fmt_addr() twice in a parameter list. Bug found by David
1282 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1283 - Fix memory leaks whenever we logged any message about the "path
1284 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1285 - When relays refuse a "create" cell because their queue of pending
1286 create cells is too big (typically because their cpu can't keep up
1287 with the arrival rate), send back reason "resource limit" rather
1288 than reason "internal", so network measurement scripts can get a
1289 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
1292 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
1293 - Free some more still-in-use memory at exit, to make hunting for
1294 memory leaks easier. Resolves bug 7029.
1295 - When a Tor client gets a "truncated" relay cell, the first byte of
1296 its payload specifies why the circuit was truncated. We were
1297 ignoring this 'reason' byte when tearing down the circuit, resulting
1298 in the controller not being told why the circuit closed. Now we
1299 pass the reason from the truncated cell to the controller. Bugfix
1300 on 0.1.2.3-alpha; fixes bug 7039.
1301 - Downgrade "Failed to hand off onionskin" messages to "debug"
1302 severity, since they're typically redundant with the "Your computer
1303 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
1304 - Make clients running with IPv6 bridges connect over IPv6 again,
1305 even without setting new config options ClientUseIPv6 and
1306 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
1307 - Use square brackets around IPv6 addresses in numerous places
1308 that needed them, including log messages, HTTPS CONNECT proxy
1309 requests, TransportProxy statefile entries, and pluggable transport
1310 extra-info lines. Fixes bug 7011; patch by David Fifield.
1312 o Code refactoring and cleanup:
1313 - Source files taken from other packages now reside in src/ext;
1314 previously they were scattered around the rest of Tor.
1315 - Avoid use of reserved identifiers in our C code. The C standard
1316 doesn't like us declaring anything that starts with an
1317 underscore, so let's knock it off before we get in trouble. Fix
1318 for bug 1031; bugfix on the first Tor commit.
1321 Changes in version 0.2.3.23-rc - 2012-10-20
1322 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
1323 vulnerability introduced by a change in OpenSSL, and fixes a variety
1324 of smaller bugs in preparation for the release.
1326 o New directory authorities:
1327 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1328 authority. Closes ticket 5749.
1330 o Major bugfixes (security/privacy):
1331 - Disable TLS session tickets. OpenSSL's implementation was giving
1332 our TLS session keys the lifetime of our TLS context objects, when
1333 perfect forward secrecy would want us to discard anything that
1334 could decrypt a link connection as soon as the link connection
1335 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1336 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1337 - Discard extraneous renegotiation attempts once the V3 link
1338 protocol has been initiated. Failure to do so left us open to
1339 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1340 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1343 - Fix a possible crash bug when checking for deactivated circuits
1344 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1345 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1347 o Minor bugfixes (on 0.2.3.x):
1348 - Fix two cases in src/or/transports.c where we were calling
1349 fmt_addr() twice in a parameter list. Bug found by David
1350 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1351 - Convert an assert in the pathbias code to a log message. The assert
1352 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1353 bugfix on 0.2.3.17-beta.
1354 - Fix memory leaks whenever we logged any message about the "path
1355 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1357 o Minor bugfixes (on 0.2.2.x and earlier):
1358 - Don't serve or accept v2 hidden service descriptors over a relay's
1359 DirPort. It's never correct to do so, and disabling it might
1360 make it more annoying to exploit any bugs that turn up in the
1361 descriptor-parsing code. Fixes bug 7149.
1362 - When relays refuse a "create" cell because their queue of pending
1363 create cells is too big (typically because their cpu can't keep up
1364 with the arrival rate), send back reason "resource limit" rather
1365 than reason "internal", so network measurement scripts can get a
1366 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
1367 - Correct file sizes when reading binary files on Cygwin, to avoid
1368 a bug where Tor would fail to read its state file. Fixes bug 6844;
1369 bugfix on 0.1.2.7-alpha.
1370 - Avoid undefined behaviour when parsing the list of supported
1371 rendezvous/introduction protocols in a hidden service descriptor.
1372 Previously, Tor would have confused (as-yet-unused) protocol version
1373 numbers greater than 32 with lower ones on many platforms. Fixes
1374 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1376 o Documentation fixes:
1377 - Clarify that hidden services are TCP only. Fixes bug 6024.
1380 Changes in version 0.2.4.3-alpha - 2012-09-22
1381 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
1382 assertion, resumes letting relays test reachability of their DirPort,
1383 and cleans up a bunch of smaller bugs.
1386 - Fix an assertion failure in tor_timegm() that could be triggered
1387 by a badly formatted directory object. Bug found by fuzzing with
1388 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1391 - Fix a possible crash bug when checking for deactivated circuits
1392 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1393 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1394 - Allow routers to detect that their own DirPorts are running. When
1395 we removed support for versions_supports_begindir, we also
1396 accidentally removed the mechanism we used to self-test our
1397 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
1398 bugfix on 0.2.4.2-alpha.
1400 o Security features:
1401 - Switch to a completely time-invariant approach for picking nodes
1402 weighted by bandwidth. Our old approach would run through the
1403 part of the loop after it had made its choice slightly slower
1404 than it ran through the part of the loop before it had made its
1405 choice. Addresses ticket 6538.
1406 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
1407 by tor2web clients allows hidden services to identify tor2web
1408 clients through their repeated selection of the same rendezvous
1409 and introduction point circuit endpoints (their guards). Resolves
1413 - Enable Tor to read configuration, state, and key information from
1414 a FIFO. Previously Tor would only read from files with a positive
1415 stat.st_size. Code from meejah; fixes bug 6044.
1418 - Correct file sizes when reading binary files on Cygwin, to avoid
1419 a bug where Tor would fail to read its state file. Fixes bug 6844;
1420 bugfix on 0.1.2.7-alpha.
1421 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
1422 bugfix on 0.2.0.3-alpha.
1423 - When complaining about a client port on a public address, log
1424 which address we're complaining about. Fixes bug 4020; bugfix on
1425 0.2.3.3-alpha. Patch by Tom Fitzhenry.
1426 - Convert an assert in the pathbias code to a log message. The assert
1427 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1428 bugfix on 0.2.3.17-beta.
1429 - Our new buildsystem was overzealous about rebuilding manpages: it
1430 would rebuild them all whenever any one of them changed. Now our
1431 dependency checking should be correct. Fixes bug 6843; bugfix on
1433 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
1434 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
1435 - Correct log printout about which address family is preferred
1436 when connecting to a bridge with both an IPv4 and IPv6 OR port.
1437 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
1439 o Minor bugfixes (code cleanliness):
1440 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
1441 with large values. This situation was untriggered, but nevertheless
1442 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
1443 - Reject consensus votes with more than 64 known-flags. We aren't even
1444 close to that limit yet, and our code doesn't handle it correctly.
1445 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
1446 - Avoid undefined behaviour when parsing the list of supported
1447 rendezvous/introduction protocols in a hidden service descriptor.
1448 Previously, Tor would have confused (as-yet-unused) protocol version
1449 numbers greater than 32 with lower ones on many platforms. Fixes
1450 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1451 - Fix handling of rendezvous client authorization types over 8.
1452 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
1453 - Fix building with older versions of GCC (2.95, for one) that don't
1454 like preprocessor directives inside macro arguments. Found by
1455 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
1456 - Switch weighted node selection rule from using a list of doubles
1457 to using a list of int64_t. This change should make the process
1458 slightly easier to debug and maintain. Needed to finish ticket 6538.
1460 o Code simplification and refactoring:
1461 - Move the generic "config" code into a new file, and have "config.c"
1462 hold only torrc- and state-related code. Resolves ticket 6823.
1463 - Move the core of our "choose a weighted element at random" logic
1464 into its own function, and give it unit tests. Now the logic is
1465 testable, and a little less fragile too.
1466 - Removed the testing_since field of node_t, which hasn't been used
1467 for anything since 0.2.0.9-alpha.
1469 o Documentation fixes:
1470 - Clarify that hidden services are TCP only. Fixes bug 6024.
1471 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
1475 Changes in version 0.2.3.22-rc - 2012-09-11
1476 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
1480 - Fix an assertion failure in tor_timegm() that could be triggered
1481 by a badly formatted directory object. Bug found by fuzzing with
1482 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1485 - Avoid segfault when starting up having run with an extremely old
1486 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1490 Changes in version 0.2.2.39 - 2012-09-11
1491 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
1495 - Fix an assertion failure in tor_timegm() that could be triggered
1496 by a badly formatted directory object. Bug found by fuzzing with
1497 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1498 - Do not crash when comparing an address with port value 0 to an
1499 address policy. This bug could have been used to cause a remote
1500 assertion failure by or against directory authorities, or to
1501 allow some applications to crash clients. Fixes bug 6690; bugfix
1505 Changes in version 0.2.4.2-alpha - 2012-09-10
1506 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
1507 raises the default rate limiting even more, and makes the bootstrapping
1508 log messages less noisy.
1511 - Automatically forward the TCP ports of pluggable transport
1512 proxies using tor-fw-helper if PortForwarding is enabled. Implements
1516 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
1517 to 1GB/1GB. The previous defaults were intended to be "basically
1518 infinite", but it turns out they're now limiting our 100mbit+
1519 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
1520 last time we raised it).
1523 - Detect when we're running with a version of OpenSSL other than the
1524 one we compiled with. This has occasionally given people hard-to-
1526 - Log fewer lines at level "notice" about our OpenSSL and Libevent
1527 versions and capabilities when everything is going right. Resolves
1528 part of ticket 6736.
1529 - Directory authorities no long accept descriptors for any version of
1530 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
1531 These versions are insecure, unsupported, or both. Implements
1535 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
1536 to start with a triple-underscore so the controller won't touch it.
1537 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
1538 - Avoid segfault when starting up having run with an extremely old
1539 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1541 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
1542 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
1543 - Don't follow the NULL pointer if microdescriptor generation fails.
1544 (This does not appear to be triggerable, but it's best to be safe.)
1545 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
1546 - Fix mis-declared dependencies on src/common/crypto.c and
1547 src/or/tor_main.c that could break out-of-tree builds under some
1548 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
1549 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
1550 6778; bugfix on 0.2.4.1-alpha.
1551 - Fix a harmless (in this case) build warning for implicitly
1552 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
1555 - Now that all versions before 0.2.2.x are disallowed, we no longer
1556 need to work around their missing features. Thus we can remove a
1557 bunch of compatibility code.
1560 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
1561 TCP ports to forward. In the past it only accepted two ports:
1562 the ORPort and the DirPort.
1565 Changes in version 0.2.4.1-alpha - 2012-09-05
1566 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
1567 bridgedb; lets relays use IPv6 addresses and directory authorities
1568 advertise them; and switches to a cleaner build interface.
1570 This is the first alpha release in a new series, so expect there to
1571 be bugs. Users who would rather test out a more stable branch should
1572 stay with 0.2.3.x for now.
1574 o Major features (bridges):
1575 - Bridges now report the pluggable transports they support to the
1576 bridge authority, so it can pass the supported transports on to
1577 bridgedb and/or eventually do reachability testing. Implements
1580 o Major features (IPv6):
1581 - Bridge authorities now accept IPv6 bridge addresses and include
1582 them in network status documents. Implements ticket 5534.
1583 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
1584 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
1585 to happen. Implements ticket 5535.
1586 - All kind of relays, not just bridges, can now advertise an IPv6
1587 OR port. Implements ticket 6362.
1588 - Directory authorities vote on IPv6 OR ports using the new consensus
1589 method 14. Implements ticket 6363.
1591 o Major features (build):
1592 - Switch to a nonrecursive Makefile structure. Now instead of each
1593 Makefile.am invoking other Makefile.am's, there is a master
1594 Makefile.am that includes the others. This change makes our build
1595 process slightly more maintainable, and improves parallelism for
1596 building with make -j. Original patch by Stewart Smith; various
1597 fixes by Jim Meyering.
1598 - Where available, we now use automake's "silent" make rules by
1599 default, so that warnings are easier to spot. You can get the old
1600 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
1602 o Minor features (code security and spec conformance):
1603 - Clear keys and key-derived material left on the stack in
1604 rendservice.c and rendclient.c. Check return value of
1605 crypto_pk_write_private_key_to_string() in end_service_load_keys().
1606 These fixes should make us more forward-secure against cold-boot
1607 attacks and the like. Fixes bug 2385.
1608 - Reject EXTEND cells sent to nonexistent streams. According to the
1609 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
1610 we were only checking for stream IDs that were currently in use.
1611 Found while hunting for more instances of bug 6271. Bugfix on
1612 0.0.2pre8, which introduced incremental circuit construction.
1614 o Minor features (streamlining);
1615 - No longer include the "opt" prefix when generating routerinfos
1616 or v2 directories: it has been needless since Tor 0.1.2. Closes
1618 - Remove some now-needless code that tried to aggressively flush
1619 OR connections as data was added to them. Since 0.2.0.1-alpha, our
1620 cell queue logic has saved us from the failure mode that this code
1621 was supposed to prevent. Removing this code will limit the number
1622 of baroque control flow paths through Tor's network logic. Reported
1623 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
1625 o Minor features (controller):
1626 - Add a "GETINFO signal/names" control port command. Implements
1628 - Provide default values for all options via "GETINFO config/defaults".
1629 Implements ticket 4971.
1631 o Minor features (IPv6):
1632 - New config option "AuthDirHasIPv6Connectivity 1" that directory
1633 authorities should set if they have IPv6 connectivity and want to
1634 do reachability tests for IPv6 relays. Implements feature 5974.
1635 - A relay with an IPv6 OR port now sends that address in NETINFO
1636 cells (in addition to its other address). Implements ticket 6364.
1638 o Minor features (log messages):
1639 - Omit the first heartbeat log message, because it never has anything
1640 useful to say, and it clutters up the bootstrapping messages.
1641 Resolves ticket 6758.
1642 - Don't log about reloading the microdescriptor cache at startup. Our
1643 bootstrap warnings are supposed to tell the user when there's a
1644 problem, and our bootstrap notices say when there isn't. Resolves
1645 ticket 6759; bugfix on 0.2.2.6-alpha.
1646 - Don't log "I learned some more directory information" when we're
1647 reading cached directory information. Reserve it for when new
1648 directory information arrives in response to a fetch. Resolves
1650 - Prevent rounding error in path bias counts when scaling
1651 them down, and use the correct scale factor default. Also demote
1652 some path bias related log messages down a level and make others
1653 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
1654 - We no longer warn so much when generating manpages from their
1657 o Code simplifications and refactoring:
1658 - Enhance our internal sscanf replacement so that we can eliminate
1659 the last remaining uses of the system sscanf. (Though those uses
1660 of sscanf were safe, sscanf itself is generally error prone, so
1661 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
1663 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
1664 - Move last_reachable and testing_since from routerinfo_t to node_t.
1665 Implements ticket 5529.
1666 - Add replaycache_t structure, functions and unit tests, then refactor
1667 rend_service_introduce() to be more clear to read, improve, debug,
1668 and test. Resolves bug 6177.
1669 - Finally remove support for malloc_good_size and malloc_usable_size.
1670 We had hoped that these functions would let us eke a little more
1671 memory out of our malloc implementation. Unfortunately, the only
1672 implementations that provided these functions are also ones that
1673 are already efficient about not overallocation: they never got us
1674 more than 7 or so bytes per allocation. Removing them saves us a
1675 little code complexity and a nontrivial amount of build complexity.
1678 - Tor maintainers now require Automake version 1.9 or later to build
1679 Tor from the Git repository. (Automake is not required when building
1680 from a source distribution.)
1683 Changes in version 0.2.3.21-rc - 2012-09-05
1684 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
1685 series. It fixes a trio of potential security bugs, fixes a bug where
1686 we were leaving some of the fast relays out of the microdescriptor
1687 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
1688 and cleans up other smaller issues.
1690 o Major bugfixes (security):
1691 - Tear down the circuit if we get an unexpected SENDME cell. Clients
1692 could use this trick to make their circuits receive cells faster
1693 than our flow control would have allowed, or to gum up the network,
1694 or possibly to do targeted memory denial-of-service attacks on
1695 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
1696 from July 2002, before the release of Tor 0.0.0. We had committed
1697 this patch previously, but we had to revert it because of bug 6271.
1698 Now that 6271 is fixed, this patch appears to work.
1699 - Reject any attempt to extend to an internal address. Without
1700 this fix, a router could be used to probe addresses on an internal
1701 network to see whether they were accepting connections. Fixes bug
1702 6710; bugfix on 0.0.8pre1.
1703 - Do not crash when comparing an address with port value 0 to an
1704 address policy. This bug could have been used to cause a remote
1705 assertion failure by or against directory authorities, or to
1706 allow some applications to crash clients. Fixes bug 6690; bugfix
1710 - Remove the upper bound on microdescriptor length. We were hitting
1711 the limit for routers with complex exit policies or family
1712 declarations, causing clients to not use them. Fixes the first
1713 piece of bug 6404; fix on 0.2.2.6-alpha.
1714 - Detect "ORPort 0" as meaning, uniformly, that we're not running
1715 as a relay. Previously, some of our code would treat the presence
1716 of any ORPort line as meaning that we should act like a relay,
1717 even though our new listener code would correctly not open any
1718 ORPorts for ORPort 0. Similar bugs in other Port options are also
1719 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
1722 - Avoid a pair of double-free and use-after-mark bugs that can
1723 occur with certain timings in canceled and re-received DNS
1724 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
1725 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
1726 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
1727 - Allow one-hop directory fetching circuits the full "circuit build
1728 timeout" period, rather than just half of it, before failing them
1729 and marking the relay down. This fix should help reduce cases where
1730 clients declare relays (or worse, bridges) unreachable because
1731 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
1732 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
1734 - Authorities no longer include any router in their microdescriptor
1735 consensuses for which they couldn't generate or agree on a
1736 microdescriptor. Fixes the second piece of bug 6404; fix on
1738 - Detect and reject attempts to specify both "FooPort" and
1739 "FooPort 0" in the same configuration domain. (It's still okay
1740 to have a FooPort in your configuration file, and use "FooPort 0"
1741 on the command line to disable it.) Fixes the second half of bug
1742 6507; bugfix on 0.2.3.3-alpha.
1743 - Make wildcarded addresses (that is, ones beginning with "*.") work
1744 when provided via the controller's MapAddress command. Previously,
1745 they were accepted, but we never actually noticed that they were
1746 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
1747 - Avoid crashing on a malformed state file where EntryGuardPathBias
1748 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
1749 - Add a (probably redundant) memory clear between iterations of
1750 the router status voting loop, to prevent future coding errors
1751 where data might leak between iterations of the loop. Resolves
1754 o Minor bugfixes (log messages):
1755 - Downgrade "set buildtimeout to low value" messages to "info"
1756 severity; they were never an actual problem, there was never
1757 anything reasonable to do about them, and they tended to spam logs
1758 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
1759 - Downgrade path-bias warning messages to "info". We'll try to get
1760 them working better in 0.2.4. Add internal circuit construction
1761 state to protect against the noisy warn message "Unexpectedly high
1762 circuit_successes". Also add some additional rate-limited notice
1763 messages to help determine the root cause of the warn. Fixes bug
1764 6475. Bugfix against 0.2.3.17-beta.
1765 - Move log message when unable to find a microdesc in a routerstatus
1766 entry to parse time. Previously we'd spam this warning every time
1767 we tried to figure out which microdescriptors to download. Fixes
1768 the third piece of bug 6404; fix on 0.2.3.18-rc.
1771 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
1772 change when the authority is deciding whether to accept a newly
1773 uploaded descriptor. Implements ticket 6423.
1774 - Add missing documentation for consensus and microdesc files.
1775 Resolves ticket 6732.
1778 Changes in version 0.2.2.38 - 2012-08-12
1779 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
1780 attack that could in theory leak path information.
1783 - Avoid an uninitialized memory read when reading a vote or consensus
1784 document that has an unrecognized flavor name. This read could
1785 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1786 - Try to leak less information about what relays a client is
1787 choosing to a side-channel attacker. Previously, a Tor client would
1788 stop iterating through the list of available relays as soon as it
1789 had chosen one, thus finishing a little earlier when it picked
1790 a router earlier in the list. If an attacker can recover this
1791 timing information (nontrivial but not proven to be impossible),
1792 they could learn some coarse-grained information about which relays
1793 a client was picking (middle nodes in particular are likelier to
1794 be affected than exits). The timing attack might be mitigated by
1795 other factors (see bug 6537 for some discussion), but it's best
1796 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
1799 Changes in version 0.2.3.20-rc - 2012-08-05
1800 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
1801 series. It fixes a pair of code security bugs and a potential anonymity
1802 issue, updates our RPM spec files, and cleans up other smaller issues.
1805 - Avoid read-from-freed-memory and double-free bugs that could occur
1806 when a DNS request fails while launching it. Fixes bug 6480;
1807 bugfix on 0.2.0.1-alpha.
1808 - Avoid an uninitialized memory read when reading a vote or consensus
1809 document that has an unrecognized flavor name. This read could
1810 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1811 - Try to leak less information about what relays a client is
1812 choosing to a side-channel attacker. Previously, a Tor client would
1813 stop iterating through the list of available relays as soon as it
1814 had chosen one, thus finishing a little earlier when it picked
1815 a router earlier in the list. If an attacker can recover this
1816 timing information (nontrivial but not proven to be impossible),
1817 they could learn some coarse-grained information about which relays
1818 a client was picking (middle nodes in particular are likelier to
1819 be affected than exits). The timing attack might be mitigated by
1820 other factors (see bug 6537 for some discussion), but it's best
1821 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
1824 - Try to make the warning when giving an obsolete SOCKSListenAddress
1825 a little more useful.
1826 - Terminate active server managed proxies if Tor stops being a
1827 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
1828 - Provide a better error message about possible OSX Asciidoc failure
1829 reasons. Fixes bug 6436.
1830 - Warn when Tor is configured to use accounting in a way that can
1831 link a hidden service to some other hidden service or public
1832 address. Resolves ticket 6490.
1835 - Check return value of fputs() when writing authority certificate
1836 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
1837 - Ignore ServerTransportPlugin lines when Tor is not configured as
1838 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
1839 - When disabling guards for having too high a proportion of failed
1840 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
1844 - Update our default RPM spec files to work with mock and rpmbuild
1845 on RHEL/Fedora. They have an updated set of dependencies and
1846 conflicts, a fix for an ancient typo when creating the "_tor"
1847 user, and better instructions. Thanks to Ondrej Mikle for the
1848 patch series. Fixes bug 6043.
1851 - Make it possible to set the TestingTorNetwork configuration
1852 option using AlternateDirAuthority and AlternateBridgeAuthority
1853 as an alternative to setting DirServer. Addresses ticket 6377.
1856 - Clarify the documentation for the Alternate*Authority options.
1858 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
1860 o Code simplification and refactoring:
1861 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
1862 10 lines. Also, don't nest them. Doing so in the past has
1863 led to hard-to-debug code. The new style is to use the
1864 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
1867 Changes in version 0.2.3.19-rc - 2012-07-06
1868 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
1869 series. It fixes the compile on Windows, reverts to a GeoIP database
1870 that isn't as broken, and fixes a flow control bug that has been around
1871 since the beginning of Tor.
1874 - Fix a bug handling SENDME cells on nonexistent streams that could
1875 result in bizarre window values. Report and patch contributed
1876 pseudonymously. Fixes part of bug 6271. This bug was introduced
1877 before the first Tor release, in svn commit r152.
1878 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
1879 June 2012 database, Maxmind marked many Tor relays as country "A1",
1880 which will cause risky behavior for clients that set EntryNodes
1881 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
1882 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
1883 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
1886 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
1887 bugfix on 0.2.1.10-alpha.
1890 Changes in version 0.2.3.18-rc - 2012-06-28
1891 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
1892 series. It fixes a few smaller bugs, but generally appears stable.
1893 Please test it and let us know whether it is!
1896 - Allow wildcarded mapaddress targets to be specified on the
1897 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
1898 - Make our linker option detection code more robust against linkers
1899 such as on FreeBSD 8, where a bad combination of options completes
1900 successfully but makes an unrunnable binary. Fixes bug 6173;
1901 bugfix on 0.2.3.17-beta.
1903 o Minor bugfixes (on 0.2.2.x and earlier):
1904 - Avoid a false positive in the util/threads unit test by increasing
1905 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
1906 - Replace "Sending publish request" log messages with "Launching
1907 upload", so that they no longer confusingly imply that we're
1908 sending something to a directory we might not even be connected
1909 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
1910 - Make sure to set *socket_error in all error cases in
1911 connection_connect(), so it can't produce a warning about
1912 errno being zero from errno_to_orconn_end_reason(). Bugfix on
1913 0.2.1.1-alpha; resolves ticket 6028.
1914 - Downgrade "Got a certificate, but we already have it" log messages
1915 from warning to info, except when we're a dirauth. Fixes bug 5238;
1916 bugfix on 0.2.1.7-alpha.
1917 - When checking for requested signatures on the latest consensus
1918 before serving it to a client, make sure to check the right
1919 consensus flavor. Bugfix on 0.2.2.6-alpha.
1920 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
1921 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
1923 o Minor bugfixes (on 0.2.3.x):
1924 - Make format_helper_exit_status() avoid unnecessary space padding
1925 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
1927 - Downgrade a message about cleaning the microdescriptor cache to
1928 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
1929 - Log a BUG message at severity INFO if we have a networkstatus with
1930 a missing entry for some microdescriptor. Continues on a patch
1932 - Improve the log message when a managed proxy fails to launch. Fixes
1933 bug 5099; bugfix on 0.2.3.6-alpha.
1934 - Don't do DNS lookups when parsing corrupted managed proxy protocol
1935 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
1936 - When formatting wildcarded address mappings for the controller,
1937 be sure to include "*." as appropriate. Partially fixes bug 6244;
1938 bugfix on 0.2.3.9-alpha.
1939 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
1940 Bugfix on 0.2.3.13-alpha.
1941 - Stop logging messages about running with circuit timeout learning
1942 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
1943 - Disable a spurious warning about reading on a marked and flushing
1944 connection. We shouldn't be doing that, but apparently we
1945 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
1946 - Fix a bug that stopped AllowDotExit from working on addresses
1947 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
1950 o Code simplification, refactoring, unit tests:
1951 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
1952 Libevent's notion of cached time when possible.
1953 - Remove duplicate code for invoking getrlimit() from control.c.
1954 - Add a unit test for the environment_variable_names_equal function.
1957 - Document the --defaults-torrc option, and the new (in 0.2.3)
1958 semantics for overriding, extending, and clearing lists of
1959 options. Closes bug 4748.
1962 Changes in version 0.2.3.17-beta - 2012-06-15
1963 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
1964 gets our TLS handshake back on track for being able to blend in with
1965 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
1966 with Vidalia, and otherwise continues to get us closer to a release
1970 - Enable gcc and ld hardening by default. Resolves ticket 5210.
1971 - Update TLS cipher list to match Firefox 8 and later. Resolves
1973 - Implement the client side of proposal 198: remove support for
1974 clients falsely claiming to support standard ciphersuites that
1975 they can actually provide. As of modern OpenSSL versions, it's not
1976 necessary to fake any standard ciphersuite, and doing so prevents
1977 us from using better ciphersuites in the future, since servers
1978 can't know whether an advertised ciphersuite is really supported or
1979 not. Some hosts -- notably, ones with very old versions of OpenSSL
1980 or where OpenSSL has been built with ECC disabled -- will stand
1981 out because of this change; TBB users should not be affected.
1984 - Change the default value for DynamicDHGroups (introduced in
1985 0.2.3.9-alpha) to 0. This feature can make Tor relays less
1986 identifiable by their use of the mod_ssl DH group, but at
1987 the cost of some usability (#4721) and bridge tracing (#6087)
1988 regressions. Resolves ticket 5598.
1989 - Send a CRLF at the end of each STATUS_* control protocol event. This
1990 bug tickled a bug in Vidalia which would make it freeze. Fixes
1991 bug 6094; bugfix on 0.2.3.16-alpha.
1994 - Disable writing on marked-for-close connections when they are
1995 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
1996 bug 5263; bugfix on 0.0.2pre13, where we first added a special
1997 case for flushing marked connections.
1998 - Detect SSL handshake even when the initial attempt to write the
1999 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
2000 - Change the AllowDotExit rules so they should actually work.
2001 We now enforce AllowDotExit only immediately after receiving an
2002 address via SOCKS or DNSPort: other sources are free to provide
2003 .exit addresses after the resolution occurs. Fixes bug 3940;
2004 bugfix on 0.2.2.1-alpha.
2005 - Fix a (harmless) integer overflow in cell statistics reported by
2006 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
2007 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
2008 right places and never depends on the consensus parameters or
2009 computes adaptive timeouts when it is disabled. Fixes bug 5049;
2010 bugfix on 0.2.2.14-alpha.
2011 - When building Tor on Windows with -DUNICODE (not default), ensure
2012 that error messages, filenames, and DNS server names are always
2013 NUL-terminated when we convert them to a single-byte encoding.
2014 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
2015 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
2016 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
2017 - Fix an edge case where TestingTorNetwork is set but the authorities
2018 and relays all have an uptime of zero, where the private Tor network
2019 could briefly lack support for hidden services. Fixes bug 3886;
2020 bugfix on 0.2.2.18-alpha.
2021 - Correct the manpage's descriptions for the default values of
2022 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
2024 - Fix the documentation for the --hush and --quiet command line
2025 options, which changed their behavior back in 0.2.3.3-alpha.
2026 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
2030 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
2031 more information to it, so that we can track it down in case it
2032 returns again. Mitigates bug 5235.
2033 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
2034 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
2035 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
2036 - Warn the user when HTTPProxy, but no other proxy type, is
2037 configured. This can cause surprising behavior: it doesn't send
2038 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
2039 directory traffic only. Resolves ticket 4663.
2040 - Issue a notice if a guard completes less than 40% of your circuits.
2041 Threshold is configurable by torrc option PathBiasNoticeRate and
2042 consensus parameter pb_noticepct. There is additional, off-by-
2043 default code to disable guards which fail too many circuits.
2044 Addresses ticket 5458.
2045 - Update to the June 6 2012 Maxmind GeoLite Country database.
2047 o Code simplifications and refactoring:
2048 - Remove validate_pluggable_transports_config(): its warning
2049 message is now handled by connection_or_connect().
2052 Changes in version 0.2.2.37 - 2012-06-06
2053 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
2054 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2058 - Work around a bug in OpenSSL that broke renegotiation with TLS
2059 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2060 the v2 Tor connection protocol when both sides were using OpenSSL
2061 1.0.1 would fail. Resolves ticket 6033.
2062 - When waiting for a client to renegotiate, don't allow it to add
2063 any bytes to the input buffer. This fixes a potential DoS issue.
2064 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2065 - Fix an edge case where if we fetch or publish a hidden service
2066 descriptor, we might build a 4-hop circuit and then use that circuit
2067 for exiting afterwards -- even if the new last hop doesn't obey our
2068 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2071 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2072 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2075 - Tell GCC and Clang to check for any errors in format strings passed
2076 to the tor_v*(print|scan)f functions.
2079 Changes in version 0.2.3.16-alpha - 2012-06-05
2080 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
2081 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2082 currently). It also fixes a variety of smaller bugs and other cleanups
2083 that get us closer to a release candidate.
2085 o Major bugfixes (general):
2086 - Work around a bug in OpenSSL that broke renegotiation with TLS
2087 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2088 the v2 Tor connection protocol when both sides were using OpenSSL
2089 1.0.1 would fail. Resolves ticket 6033.
2090 - When waiting for a client to renegotiate, don't allow it to add
2091 any bytes to the input buffer. This fixes a potential DoS issue.
2092 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2093 - Pass correct OR address to managed proxies (like obfsproxy),
2094 even when ORListenAddress is used. Fixes bug 4865; bugfix on
2096 - The advertised platform of a router now includes only its operating
2097 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
2098 service pack level (for Windows) or its CPU architecture (for Unix).
2099 We also no longer include the "git-XYZ" tag in the version. Resolves
2102 o Major bugfixes (clients):
2103 - If we are unable to find any exit that supports our predicted ports,
2104 stop calling them predicted, so that we don't loop and build
2105 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
2106 which introduced predicted ports.
2107 - Fix an edge case where if we fetch or publish a hidden service
2108 descriptor, we might build a 4-hop circuit and then use that circuit
2109 for exiting afterwards -- even if the new last hop doesn't obey our
2110 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2111 - Check at each new consensus whether our entry guards were picked
2112 long enough ago that we should rotate them. Previously, we only
2113 did this check at startup, which could lead to us holding a guard
2114 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
2115 - When fetching a bridge descriptor from a bridge authority,
2116 always do so anonymously, whether we have been able to open
2117 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
2118 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
2119 but we'll need to wait for bug 6010 before it's actually usable.
2121 o Major bugfixes (directory authorities):
2122 - When computing weight parameters, behave more robustly in the
2123 presence of a bad bwweightscale value. Previously, the authorities
2124 would crash if they agreed on a sufficiently broken weight_scale
2125 value: now, they use a reasonable default and carry on. Partial
2126 fix for 5786; bugfix on 0.2.2.17-alpha.
2127 - Check more thoroughly to prevent a rogue authority from
2128 double-voting on any consensus directory parameter. Previously,
2129 authorities would crash in this case if the total number of
2130 votes for any parameter exceeded the number of active voters,
2131 but would let it pass otherwise. Partial fix for bug 5786; bugfix
2135 - Rate-limit log messages when asked to connect anonymously to
2136 a private address. When these hit, they tended to hit fast and
2137 often. Also, don't bother trying to connect to addresses that we
2138 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
2139 reply makes us think we have been lied to, even when the address the
2140 client tried to connect to was "localhost." Resolves ticket 2822.
2141 - Allow packagers to insert an extra string in server descriptor
2142 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
2143 Resolves the rest of ticket 2988.
2144 - Raise the threshold of server descriptors needed (75%) and exit
2145 server descriptors needed (50%) before we will declare ourselves
2146 bootstrapped. This will make clients start building circuits a
2147 little later, but makes the initially constructed circuits less
2148 skewed and less in conflict with further directory fetches. Fixes
2150 - Close any connection that sends unrecognized junk before the
2151 handshake. Solves an issue noted in bug 4369.
2152 - Improve log messages about managed transports. Resolves ticket 5070.
2153 - Tag a bridge's descriptor as "never to be sent unencrypted".
2154 This shouldn't matter, since bridges don't open non-anonymous
2155 connections to the bridge authority and don't allow unencrypted
2156 directory connections from clients, but we might as well make
2157 sure. Closes bug 5139.
2158 - Expose our view of whether we have gone dormant to the controller,
2159 via a new "GETINFO dormant" value. Torbutton and other controllers
2160 can use this to avoid doing periodic requests through Tor while
2161 it's dormant (bug 4718). Fixes bug 5954.
2162 - Tell GCC and Clang to check for any errors in format strings passed
2163 to the tor_v*(print|scan)f functions.
2164 - Update to the May 1 2012 Maxmind GeoLite Country database.
2166 o Minor bugfixes (already included in 0.2.2.36):
2167 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2168 Fixes bug 5346; bugfix on 0.0.8pre3.
2169 - Correct parsing of certain date types in parse_http_time().
2170 Without this patch, If-Modified-Since would behave
2171 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2172 Esteban Manchado Velázques.
2173 - Make our number-parsing functions always treat too-large values
2174 as an error, even when those values exceed the width of the
2175 underlying type. Previously, if the caller provided these
2176 functions with minima or maxima set to the extreme values of the
2177 underlying integer type, these functions would return those
2178 values on overflow rather than treating overflow as an error.
2179 Fixes part of bug 5786; bugfix on 0.0.9.
2180 - If we hit the error case where routerlist_insert() replaces an
2181 existing (old) server descriptor, make sure to remove that
2182 server descriptor from the old_routers list. Fix related to bug
2183 1776. Bugfix on 0.2.2.18-alpha.
2184 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2185 circuits. Fixes issue 5259.
2187 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
2188 - Prevent a null-pointer dereference when receiving a data cell
2189 for a nonexistent stream when the circuit in question has an
2190 empty deliver window. We don't believe this is triggerable,
2191 since we don't currently allow deliver windows to become empty,
2192 but the logic is tricky enough that it's better to make the code
2193 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
2194 - Fix a memory leak when trying to launch a DNS request when the
2195 network is disabled or the nameservers are unconfigurable. Fixes
2196 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
2197 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
2198 - Don't hold a Windows file handle open for every file mapping;
2199 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
2201 - Avoid O(n^2) performance characteristics when parsing a large
2202 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
2203 - Format more doubles with %f, not %lf. Patch from grarpamp to make
2204 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
2206 - Make our replacement implementation of strtok_r() compatible with
2207 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
2208 bugfix on 0.2.2.1-alpha.
2209 - Fix a NULL-pointer dereference on a badly formed
2210 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
2211 bugfix on 0.2.2.9-alpha.
2212 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2213 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2214 - Defensively refactor rend_mid_rendezvous() so that protocol
2215 violations and length checks happen in the beginning. Fixes
2217 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
2218 that IPv6 stuff will compile on MSVC, and compilation issues
2219 will be easier to track down. Fixes bug 5861.
2221 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
2222 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
2223 resource exhaustion, so that clients can adjust their load to
2224 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
2225 started using END_STREAM_REASON_RESOURCELIMIT.
2226 - Don't check for whether the address we're using for outbound
2227 connections has changed until after the outbound connection has
2228 completed. On Windows, getsockname() doesn't succeed until the
2229 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
2230 - If the configuration tries to set MyFamily on a bridge, refuse to
2231 do so, and warn about the security implications. Fixes bug 4657;
2232 bugfix on 0.2.0.3-alpha.
2233 - If the client fails to set a reasonable set of ciphersuites
2234 during its v2 handshake renegotiation, allow the renegotiation to
2235 continue nevertheless (i.e. send all the required certificates).
2236 Fixes bug 4591; bugfix on 0.2.0.20-rc.
2237 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
2238 option is set to 0 (which Vidalia version 0.2.16 now does when
2239 a SAVECONF attempt fails), perform other actions that SIGHUP
2240 usually causes (like reopening the logs). Fixes bug 5095; bugfix
2242 - If we fail to write a microdescriptor to the disk cache, do not
2243 continue replacing the old microdescriptor file. Fixes bug 2954;
2244 bugfix on 0.2.2.6-alpha.
2245 - Exit nodes don't need to fetch certificates for authorities that
2246 they don't recognize; only directory authorities, bridges,
2247 and caches need to do that. Fixes part of bug 2297; bugfix on
2249 - Correctly handle checking the permissions on the parent
2250 directory of a control socket in the root directory. Bug found
2251 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
2253 - When told to add a bridge with the same digest as a preexisting
2254 bridge but a different addr:port, change the addr:port as
2255 requested. Previously we would not notice the change. Fixes half
2256 of bug 5603; fix on 0.2.2.26-beta.
2257 - End AUTHCHALLENGE error messages (in the control protocol) with
2258 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
2260 o Minor bugfixes (on 0.2.3.x):
2261 - Turn an assertion (that the number of handshakes received as a
2262 server is not < 1) into a warning. Fixes bug 4873; bugfix on
2264 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
2265 we had reversed them when the answer was cached.) Fixes bug
2266 5723; bugfix on 0.2.3.1-alpha.
2267 - Work correctly on Linux systems with accept4 support advertised in
2268 their headers, but without accept4 support in the kernel. Fix
2269 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
2270 - When told to add a bridge with the same addr:port as a preexisting
2271 bridge but a different transport, change the transport as
2272 requested. Previously we would not notice the change. Fixes half
2273 of bug 5603; fix on 0.2.3.2-alpha.
2274 - Avoid a "double-reply" warning when replying to a SOCKS request
2275 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
2276 bugfix on 0.2.3.4-alpha.
2277 - Fix a bug where a bridge authority crashes if it has seen no
2278 directory requests when it's time to write statistics to disk.
2279 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
2281 - Don't try to open non-control listeners when DisableNetwork is set.
2282 Previously, we'd open all listeners, then immediately close them.
2283 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
2284 - Don't abort the managed proxy protocol if the managed proxy
2285 sends us an unrecognized line; ignore it instead. Fixes bug
2286 5910; bugfix on 0.2.3.9-alpha.
2287 - Fix a compile warning in crypto.c when compiling with clang 3.1.
2288 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
2289 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
2290 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
2291 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
2292 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
2293 - Resolve numerous small warnings and build issues with MSVC. Resolves
2296 o Documentation fixes:
2297 - Improve the manual's documentation for the NT Service command-line
2298 options. Addresses ticket 3964.
2299 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
2300 - Document the changes to the ORPort and DirPort options, and the
2301 fact that {OR/Dir}ListenAddress is now unnecessary (and
2302 therefore deprecated). Resolves ticket 5597.
2305 - Remove the torrc.bridge file: we don't use it for anything, and
2306 it had become badly desynchronized from torrc.sample. Resolves
2310 Changes in version 0.2.2.36 - 2012-05-24
2311 Tor 0.2.2.36 updates the addresses for two of the eight directory
2312 authorities, fixes some potential anonymity and security issues,
2313 and fixes several crash bugs.
2315 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
2316 known flaws, and nobody should be using them. You should upgrade. If
2317 you're using a Linux or BSD and its packages are obsolete, stop using
2318 those packages and upgrade anyway.
2320 o Directory authority changes:
2321 - Change IP address for maatuska (v3 directory authority).
2322 - Change IP address for ides (v3 directory authority), and rename
2326 - When building or running with any version of OpenSSL earlier
2327 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2328 versions have a bug (CVE-2011-4576) in which their block cipher
2329 padding includes uninitialized data, potentially leaking sensitive
2330 information to any peer with whom they make a SSLv3 connection. Tor
2331 does not use SSL v3 by default, but a hostile client or server
2332 could force an SSLv3 connection in order to gain information that
2333 they shouldn't have been able to get. The best solution here is to
2334 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2335 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2336 to make sure that the bug can't happen.
2337 - Never use a bridge or a controller-supplied node as an exit, even
2338 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2339 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2340 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2341 - Only build circuits if we have a sufficient threshold of the total
2342 descriptors that are marked in the consensus with the "Exit"
2343 flag. This mitigates an attack proposed by wanoskarnet, in which
2344 all of a client's bridges collude to restrict the exit nodes that
2345 the client knows about. Fixes bug 5343.
2346 - Provide controllers with a safer way to implement the cookie
2347 authentication mechanism. With the old method, if another locally
2348 running program could convince a controller that it was the Tor
2349 process, then that program could trick the controller into telling
2350 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2351 authentication method uses a challenge-response approach to prevent
2352 this attack. Fixes bug 5185; implements proposal 193.
2355 - Avoid logging uninitialized data when unable to decode a hidden
2356 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2357 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2358 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2360 - Fix builds when the path to sed, openssl, or sha1sum contains
2361 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2363 - Correct our replacements for the timeradd() and timersub() functions
2364 on platforms that lack them (for example, Windows). The timersub()
2365 function is used when expiring circuits, while timeradd() is
2366 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2367 bugfix on 0.2.2.24-alpha.
2368 - Fix the SOCKET_OK test that we use to tell when socket
2369 creation fails so that it works on Win64. Fixes part of bug 4533;
2370 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2373 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2374 Fixes bug 5346; bugfix on 0.0.8pre3.
2375 - Make our number-parsing functions always treat too-large values
2376 as an error, even when those values exceed the width of the
2377 underlying type. Previously, if the caller provided these
2378 functions with minima or maxima set to the extreme values of the
2379 underlying integer type, these functions would return those
2380 values on overflow rather than treating overflow as an error.
2381 Fixes part of bug 5786; bugfix on 0.0.9.
2382 - Older Linux kernels erroneously respond to strange nmap behavior
2383 by having accept() return successfully with a zero-length
2384 socket. When this happens, just close the connection. Previously,
2385 we would try harder to learn the remote address: but there was
2386 no such remote address to learn, and our method for trying to
2387 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2388 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2389 - Correct parsing of certain date types in parse_http_time().
2390 Without this patch, If-Modified-Since would behave
2391 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2392 Esteban Manchado Velázques.
2393 - Change the BridgePassword feature (part of the "bridge community"
2394 design, which is not yet implemented) to use a time-independent
2395 comparison. The old behavior might have allowed an adversary
2396 to use timing to guess the BridgePassword value. Fixes bug 5543;
2397 bugfix on 0.2.0.14-alpha.
2398 - Detect and reject certain misformed escape sequences in
2399 configuration values. Previously, these values would cause us
2400 to crash if received in a torrc file or over an authenticated
2401 control port. Bug found by Esteban Manchado Velázquez, and
2402 independently by Robert Connolly from Matta Consulting who further
2403 noted that it allows a post-authentication heap overflow. Patch
2404 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2405 bugfix on 0.2.0.16-alpha.
2406 - Fix a compile warning when using the --enable-openbsd-malloc
2407 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2408 - During configure, detect when we're building with clang version
2409 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2410 CFLAGS. clang doesn't support them yet.
2411 - When sending an HTTP/1.1 proxy request, include a Host header.
2412 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2413 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
2414 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
2415 - If we hit the error case where routerlist_insert() replaces an
2416 existing (old) server descriptor, make sure to remove that
2417 server descriptor from the old_routers list. Fix related to bug
2418 1776. Bugfix on 0.2.2.18-alpha.
2420 o Minor bugfixes (documentation and log messages):
2421 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2422 Fixes bug 4856; bugfix on Tor 0.0.6.
2423 - Update "ClientOnly" man page entry to explain that there isn't
2424 really any point to messing with it. Resolves ticket 5005.
2425 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2426 directory authority option (introduced in Tor 0.2.2.34).
2427 - Downgrade the "We're missing a certificate" message from notice
2428 to info: people kept mistaking it for a real problem, whereas it
2429 is seldom the problem even when we are failing to bootstrap. Fixes
2430 bug 5067; bugfix on 0.2.0.10-alpha.
2431 - Correctly spell "connect" in a log message on failure to create a
2432 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
2433 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2434 circuits. Fixes issue 5259.
2437 - Directory authorities now reject versions of Tor older than
2438 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2439 inclusive. These versions accounted for only a small fraction of
2440 the Tor network, and have numerous known security issues. Resolves
2442 - Update to the May 1 2012 Maxmind GeoLite Country database.
2445 - When sending or relaying a RELAY_EARLY cell, we used to convert
2446 it to a RELAY cell if the connection was using the v1 link
2447 protocol. This was a workaround for older versions of Tor, which
2448 didn't handle RELAY_EARLY cells properly. Now that all supported
2449 versions can handle RELAY_EARLY cells, and now that we're enforcing
2450 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2451 remove this workaround. Addresses bug 4786.
2454 Changes in version 0.2.3.15-alpha - 2012-04-30
2455 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
2456 the development branch build on Windows again.
2458 o Minor bugfixes (on 0.2.2.x and earlier):
2459 - Make sure that there are no unhandled pending TLS errors before
2460 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
2461 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
2462 Bugfix on 0.1.0.5-rc; fixes bug 4528.
2463 - Fix an assert that directory authorities could trigger on sighup
2464 during some configuration state transitions. We now don't treat
2465 it as a fatal error when the new descriptor we just generated in
2466 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
2467 - After we pick a directory mirror, we would refuse to use it if
2468 it's in our ExcludeExitNodes list, resulting in mysterious failures
2469 to bootstrap for people who just wanted to avoid exiting from
2470 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
2471 - When building with --enable-static-tor on OpenBSD, do not
2472 erroneously attempt to link -lrt. Fixes bug 5103.
2474 o Minor bugfixes (on 0.2.3.x):
2475 - When Tor is built with kernel headers from a recent (last few
2476 years) Linux kernel, do not fail to run on older (pre-2.6.28
2477 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
2478 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
2480 - Fix compilation with miniupnpc version 1.6; patch from
2481 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
2482 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
2483 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
2484 - Fix compilation on platforms without unistd.h, or where environ
2485 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
2488 - Directory authorities are now a little more lenient at accepting
2489 older router descriptors, or newer router descriptors that don't
2490 make big changes. This should help ameliorate past and future
2491 issues where routers think they have uploaded valid descriptors,
2492 but the authorities don't think so. Fix for ticket 2479.
2493 - Make the code that clients use to detect an address change be
2494 IPv6-aware, so that it won't fill clients' logs with error
2495 messages when trying to get the IPv4 address of an IPv6
2496 connection. Implements ticket 5537.
2499 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
2500 authorities needed to use it for a while to keep the network working
2501 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
2502 that was six months ago. As of now, it should no longer be needed
2506 Changes in version 0.2.3.14-alpha - 2012-04-23
2507 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
2508 candidate. It also dramatically speeds up AES: fast relays should
2509 consider switching to the newer OpenSSL library.
2511 o Directory authority changes:
2512 - Change IP address for ides (v3 directory authority), and rename
2516 - Avoid logging uninitialized data when unable to decode a hidden
2517 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2518 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2519 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2521 - If authorities are unable to get a v2 consensus document from other
2522 directory authorities, they no longer fall back to fetching
2523 them from regular directory caches. Fixes bug 5635; bugfix on
2524 0.2.2.26-beta, where routers stopped downloading v2 consensus
2526 - When we start a Tor client with a normal consensus already cached,
2527 be willing to download a microdescriptor consensus. Fixes bug 4011;
2528 fix on 0.2.3.1-alpha.
2530 o Major features (performance):
2531 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
2532 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
2533 vectorized AES implementations as appropriate. These can be much,
2534 much faster than other AES implementations.
2536 o Minor bugfixes (0.2.2.x and earlier):
2537 - Don't launch more than 10 service-side introduction-point circuits
2538 for a hidden service in five minutes. Previously, we would consider
2539 launching more introduction-point circuits if at least one second
2540 had passed without any introduction-point circuits failing. Fixes
2541 bug 4607; bugfix on 0.0.7pre1.
2542 - Change the BridgePassword feature (part of the "bridge community"
2543 design, which is not yet implemented) to use a time-independent
2544 comparison. The old behavior might have allowed an adversary
2545 to use timing to guess the BridgePassword value. Fixes bug 5543;
2546 bugfix on 0.2.0.14-alpha.
2547 - Enforce correct return behavior of tor_vsscanf() when the '%%'
2548 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
2549 - When sending an HTTP/1.1 proxy request, include a Host header.
2550 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2551 - Don't log that we have "decided to publish new relay descriptor"
2552 unless we are actually publishing a descriptor. Fixes bug 3942;
2553 bugfix on 0.2.2.28-beta.
2555 o Minor bugfixes (0.2.3.x):
2556 - Fix a bug where a bridge authority crashes (on a failed assert)
2557 if it has seen no directory requests when it's time to write
2558 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
2559 - Fix bug stomping on ORPort option NoListen and ignoring option
2560 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
2561 - In the testsuite, provide a large enough buffer in the tor_sscanf
2562 unit test. Otherwise we'd overrun that buffer and crash during
2563 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
2565 - Make sure we create the keys directory if it doesn't exist and we're
2566 about to store the dynamic Diffie-Hellman parameters. Fixes bug
2567 5572; bugfix on 0.2.3.13-alpha.
2568 - Fix a small memory leak when trying to decode incorrect base16
2569 authenticator during SAFECOOKIE authentication. Found by
2570 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
2573 - Add more information to a log statement that might help track down
2574 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
2575 non-IP address" messages (or any Bug messages, for that matter!),
2576 please let us know about it.
2577 - Relays now understand an IPv6 address when they get one from a
2578 directory server. Resolves ticket 4875.
2579 - Resolve IPv6 addresses in bridge and entry statistics to country
2580 code "??" which means we at least count them. Resolves ticket 5053;
2581 improves on 0.2.3.9-alpha.
2582 - Update to the April 3 2012 Maxmind GeoLite Country database.
2583 - Begin a doc/state-contents.txt file to explain the contents of
2584 the Tor state file. Fixes bug 2987.
2586 o Default torrc changes:
2587 - Stop listing "socksport 9050" in torrc.sample. We open a socks
2588 port on 9050 by default anyway, so this should not change anything
2590 - Stop mentioning the deprecated *ListenAddress options in
2591 torrc.sample. Fixes bug 5438.
2592 - Document unit of bandwidth related options in sample torrc.
2596 - The "torify" script no longer supports the "tsocks" socksifier
2597 tool, since tsocks doesn't support DNS and UDP right for Tor.
2598 Everyone should be using torsocks instead. Fixes bugs 3530 and
2599 5180. Based on a patch by "ugh".
2602 - Change the symmetric cipher interface so that creating and
2603 initializing a stream cipher are no longer separate functions.
2604 - Remove all internal support for unpadded RSA. We never used it, and
2605 it would be a bad idea to start.
2608 Changes in version 0.2.3.13-alpha - 2012-03-26
2609 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
2610 in managed pluggable transports, as well as providing other cleanups
2611 that get us closer to a release candidate.
2613 o Directory authority changes:
2614 - Change IP address for maatuska (v3 directory authority).
2617 - Provide controllers with a safer way to implement the cookie
2618 authentication mechanism. With the old method, if another locally
2619 running program could convince a controller that it was the Tor
2620 process, then that program could trick the controller into telling
2621 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2622 authentication method uses a challenge-response approach to prevent
2623 this attack. Fixes bug 5185, implements proposal 193.
2624 - Never use a bridge or a controller-supplied node as an exit, even
2625 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2626 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2627 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2628 - Only build circuits if we have a sufficient threshold of the total
2629 descriptors that are marked in the consensus with the "Exit"
2630 flag. This mitigates an attack proposed by wanoskarnet, in which
2631 all of a client's bridges collude to restrict the exit nodes that
2632 the client knows about. Fixes bug 5343.
2634 o Major bugfixes (on Tor 0.2.3.x):
2635 - Avoid an assert when managed proxies like obfsproxy are configured,
2636 and we receive HUP signals or setconf attempts too rapidly. This
2637 situation happens most commonly when Vidalia tries to attach to
2638 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
2639 bugfix on 0.2.3.6-alpha.
2640 - Fix a relay-side pluggable transports bug where managed proxies were
2641 unreachable from the Internet, because Tor asked them to bind on
2642 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
2643 - Stop discarding command-line arguments when TestingTorNetwork
2644 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
2645 0.2.3.9-alpha, where task 4552 added support for two layers of
2647 - Resume allowing the unit tests to run in gdb. This was accidentally
2648 made impossible when the DisableDebuggerAttachment option was
2649 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
2650 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
2651 0.2.3.11-alpha. Reported by Anthony G. Basile.
2653 o Minor bugfixes (on 0.2.2.x and earlier):
2654 - Ensure we don't cannibalize circuits that are longer than three hops
2655 already, so we don't end up making circuits with 5 or more
2656 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
2657 0.1.0.1-rc which introduced cannibalization.
2658 - Detect and reject certain misformed escape sequences in
2659 configuration values. Previously, these values would cause us
2660 to crash if received in a torrc file or over an authenticated
2661 control port. Bug found by Esteban Manchado Velázquez, and
2662 independently by Robert Connolly from Matta Consulting who further
2663 noted that it allows a post-authentication heap overflow. Patch
2664 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2665 bugfix on 0.2.0.16-alpha.
2666 - Fix a compile warning when using the --enable-openbsd-malloc
2667 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2668 - Directory caches no longer refuse to clean out descriptors because
2669 of missing v2 networkstatus documents, unless they're configured
2670 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
2671 0.2.2.26-beta. Patch by Daniel Bryg.
2672 - Update to the latest version of the tinytest unit testing framework.
2673 This includes a couple of bugfixes that can be relevant for
2674 running forked unit tests on Windows, and removes all reserved
2677 o Minor bugfixes (on 0.2.3.x):
2678 - On a failed pipe() call, don't leak file descriptors. Fixes bug
2679 4296; bugfix on 0.2.3.1-alpha.
2680 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
2681 until after we have received a CERTS cell. Fixes bug 4361; bugfix
2682 on 0.2.3.6-alpha. Patch by "frosty".
2683 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
2684 option, so that the IP stack doesn't decide to use it for IPv4
2685 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
2686 - Ensure that variables set in Tor's environment cannot override
2687 environment variables that Tor passes to a managed
2688 pluggable-transport proxy. Previously, Tor would pass every
2689 variable in its environment to managed proxies along with the new
2690 ones, in such a way that on many operating systems, the inherited
2691 environment variables would override those which Tor tried to
2692 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
2693 bugfix on 0.2.3.9-alpha for Windows.
2696 - A wide variety of new unit tests by Esteban Manchado Velázquez.
2697 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
2698 - Update to the March 6 2012 Maxmind GeoLite Country database.
2701 Changes in version 0.2.3.12-alpha - 2012-02-13
2702 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
2703 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
2704 when Tor is configured to use a pluggable transport like obfsproxy.
2707 - Fix builds when the path to sed, openssl, or sha1sum contains
2708 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2710 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
2711 connections. This change should allow busy exit relays to stop
2712 running out of available sockets as quickly. Fixes bug 4950;
2713 bugfix on 0.2.2.26-beta.
2714 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
2715 would ask the bridge for microdescriptors, which are only supported
2716 in 0.2.3.x, and then fail to bootstrap when it didn't get the
2717 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
2718 - Properly set up obfsproxy's environment when in managed mode. The
2719 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
2720 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
2721 5076 and 5082; bugfix on 0.2.3.6-alpha.
2724 - Use the dead_strip option when building Tor on OS X. This reduces
2725 binary size by almost 19% when linking openssl and libevent
2726 statically, which we do for Tor Browser Bundle.
2727 - Fix broken URLs in the sample torrc file, and tell readers about
2728 the OutboundBindAddress, ExitPolicyRejectPrivate, and
2729 PublishServerDescriptor options. Addresses bug 4652.
2730 - Update to the February 7 2012 Maxmind GeoLite Country database.
2733 - Downgrade the "We're missing a certificate" message from notice
2734 to info: people kept mistaking it for a real problem, whereas it
2735 is seldom the problem even when we are failing to bootstrap. Fixes
2736 bug 5067; bugfix on 0.2.0.10-alpha.
2737 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
2738 managed pluggable transport server proxy's environment.
2739 Previously, we would put it there, even though Tor doesn't
2740 implement an 'extended server port' yet, and even though Tor
2741 almost certainly isn't listening at that address. For now, we set
2742 it to an empty string to avoid crashing older obfsproxies. Bugfix
2744 - Log the heartbeat message every HeartbeatPeriod seconds, not every
2745 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
2746 0.2.3.1-alpha. Bug reported by Scott Bennett.
2747 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
2748 bugfix on 0.2.3.11-alpha.
2749 - Update "ClientOnly" man page entry to explain that there isn't
2750 really any point to messing with it. Resolves ticket 5005.
2751 - Use the correct CVE number for CVE-2011-4576 in our comments and
2752 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
2755 o Code simplifications and refactoring:
2756 - Use the _WIN32 macro throughout our code to detect Windows.
2757 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
2761 Changes in version 0.2.3.11-alpha - 2012-01-22
2762 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
2763 the last step of the plan to limit maximum circuit length, includes
2764 a wide variety of hidden service performance and correctness fixes,
2765 works around an OpenSSL security flaw if your distro is too stubborn
2766 to upgrade, and fixes a bunch of smaller issues.
2769 - Now that Tor 0.2.0.x is completely deprecated, enable the final
2770 part of "Proposal 110: Avoiding infinite length circuits" by
2771 refusing all circuit-extend requests that do not use a relay_early
2772 cell. This change helps Tor resist a class of denial-of-service
2773 attacks by limiting the maximum circuit length.
2774 - Adjust the number of introduction points that a hidden service
2775 will try to maintain based on how long its introduction points
2776 remain in use and how many introductions they handle. Fixes
2778 - Try to use system facilities for enumerating local interface
2779 addresses, before falling back to our old approach (which was
2780 binding a UDP socket, and calling getsockname() on it). That
2781 approach was scaring OS X users whose draconian firewall
2782 software warned about binding to UDP sockets, regardless of
2783 whether packets were sent. Now we try to use getifaddrs(),
2784 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
2785 system supports. Resolves ticket 1827.
2787 o Major security workaround:
2788 - When building or running with any version of OpenSSL earlier
2789 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2790 versions have a bug (CVE-2011-4576) in which their block cipher
2791 padding includes uninitialized data, potentially leaking sensitive
2792 information to any peer with whom they make a SSLv3 connection. Tor
2793 does not use SSL v3 by default, but a hostile client or server
2794 could force an SSLv3 connection in order to gain information that
2795 they shouldn't have been able to get. The best solution here is to
2796 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2797 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2798 to make sure that the bug can't happen.
2801 - Fix the SOCKET_OK test that we use to tell when socket
2802 creation fails so that it works on Win64. Fixes part of bug 4533;
2803 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2804 - Correct our replacements for the timeradd() and timersub() functions
2805 on platforms that lack them (for example, Windows). The timersub()
2806 function is used when expiring circuits, while timeradd() is
2807 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2808 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
2809 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
2810 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
2811 bug at runtime, not compile time, because some distributions hack
2812 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
2813 on 0.2.3.9-alpha. Found by Pascal.
2815 o Minor features (controller):
2816 - Use absolute path names when reporting the torrc filename in the
2817 control protocol, so a controller can more easily find the torrc
2818 file. Resolves bug 1101.
2819 - Extend the control protocol to report flags that control a circuit's
2820 path selection in CIRC events and in replies to 'GETINFO
2821 circuit-status'. Implements part of ticket 2411.
2822 - Extend the control protocol to report the hidden service address
2823 and current state of a hidden-service-related circuit in CIRC
2824 events and in replies to 'GETINFO circuit-status'. Implements part
2826 - When reporting the path to the cookie file to the controller,
2827 give an absolute path. Resolves ticket 4881.
2828 - Allow controllers to request an event notification whenever a
2829 circuit is cannibalized or its purpose is changed. Implements
2830 part of ticket 3457.
2831 - Include the creation time of a circuit in CIRC and CIRC2
2832 control-port events and the list produced by the 'GETINFO
2833 circuit-status' control-port command.
2835 o Minor features (directory authorities):
2836 - Directory authorities now reject versions of Tor older than
2837 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2838 inclusive. These versions accounted for only a small fraction of
2839 the Tor network, and have numerous known security issues. Resolves
2841 - Authority operators can now vote for all relays in a given
2842 set of countries to be BadDir/BadExit/Invalid/Rejected.
2843 - Provide two consensus parameters (FastFlagMinThreshold and
2844 FastFlagMaxThreshold) to control the range of allowable bandwidths
2845 for the Fast directory flag. These allow authorities to run
2846 experiments on appropriate requirements for being a "Fast" node.
2847 The AuthDirFastGuarantee config value still applies. Implements
2849 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2850 directory authority option (introduced in Tor 0.2.2.34).
2852 o Minor features (other):
2853 - Don't disable the DirPort when we cannot exceed our AccountingMax
2854 limit during this interval because the effective bandwidthrate is
2855 low enough. This is useful in a situation where AccountMax is only
2856 used as an additional safeguard or to provide statistics.
2857 - Prepend an informative header to generated dynamic_dh_params files.
2858 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
2859 EntryNodes will have no effect. Resolves issue 2571.
2860 - Log more useful messages when we fail to disable debugger
2862 - Log which authority we're missing votes from when we go to fetch
2863 them from the other auths.
2864 - Log (at debug level) whenever a circuit's purpose is changed.
2865 - Add missing documentation for the MaxClientCircuitsPending,
2866 UseMicrodescriptors, UserspaceIOCPBuffers, and
2867 _UseFilteringSSLBufferevents options, all introduced during
2869 - Update to the January 3 2012 Maxmind GeoLite Country database.
2871 o Minor bugfixes (hidden services):
2872 - Don't close hidden service client circuits which have almost
2873 finished connecting to their destination when they reach
2874 the normal circuit-build timeout. Previously, we would close
2875 introduction circuits which are waiting for an acknowledgement
2876 from the introduction point, and rendezvous circuits which have
2877 been specified in an INTRODUCE1 cell sent to a hidden service,
2878 after the normal CBT. Now, we mark them as 'timed out', and launch
2879 another rendezvous attempt in parallel. This behavior change can
2880 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
2881 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
2882 - Don't close hidden-service-side rendezvous circuits when they
2883 reach the normal circuit-build timeout. This behaviour change can
2884 be disabled using the new
2885 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
2886 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
2887 - Make sure we never mark the wrong rendezvous circuit as having
2888 had its introduction cell acknowleged by the introduction-point
2889 relay. Previously, when we received an INTRODUCE_ACK cell on a
2890 client-side hidden-service introduction circuit, we might have
2891 marked a rendezvous circuit other than the one we specified in
2892 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
2893 a warning message and interfered with the hidden service
2894 connection-establishment process. Fixes bug 4759; bugfix on
2895 0.2.3.3-alpha, when we added the stream-isolation feature which
2896 might cause Tor to open multiple rendezvous circuits for the same
2898 - Don't trigger an assertion failure when we mark a new client-side
2899 hidden-service introduction circuit for close during the process
2900 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
2903 o Minor bugfixes (log messages):
2904 - Correctly spell "connect" in a log message on failure to create a
2905 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
2907 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2908 Fixes bug 4856; bugfix on Tor 0.0.6.
2909 - Fix the log message describing how we work around discovering
2910 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
2911 4837; bugfix on 0.2.2.9-alpha.
2912 - When logging about a disallowed .exit name, do not also call it
2913 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
2915 o Minor bugfixes (build fixes):
2916 - During configure, detect when we're building with clang version
2917 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2918 CFLAGS. clang doesn't support them yet.
2919 - During configure, search for library containing cos function as
2920 libm lives in libcore on some platforms (BeOS/Haiku). Linking
2921 against libm was hard-coded before. Fixes the first part of bug
2922 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
2924 - Detect attempts to build Tor on (as yet hypothetical) versions
2925 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
2926 fix for bug 4533. Bugfix on 0.2.2.28-beta.
2927 - Preprocessor directives should not be put inside the arguments
2928 of a macro. This would break compilation with GCC releases prior
2929 to version 3.3. We would never recommend such an old GCC version,
2930 but it is apparently required for binary compatibility on some
2931 platforms (namely, certain builds of Haiku). Fixes the other part
2932 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
2935 o Minor bugfixes (other):
2936 - Older Linux kernels erroneously respond to strange nmap behavior
2937 by having accept() return successfully with a zero-length
2938 socket. When this happens, just close the connection. Previously,
2939 we would try harder to learn the remote address: but there was
2940 no such remote address to learn, and our method for trying to
2941 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2942 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2943 - Fix null-pointer access that could occur if TLS allocation failed.
2944 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
2945 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
2946 accidentally been reverted.
2947 - Fix our implementation of crypto_random_hostname() so it can't
2948 overflow on ridiculously large inputs. (No Tor version has ever
2949 provided this kind of bad inputs, but let's be correct in depth.)
2950 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
2951 - Find more places in the code that should have been testing for
2952 invalid sockets using the SOCKET_OK macro. Required for a fix
2953 for bug 4533. Bugfix on 0.2.2.28-beta.
2954 - Fix an assertion failure when, while running with bufferevents, a
2955 connection finishes connecting after it is marked for close, but
2956 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
2957 - test_util_spawn_background_ok() hardcoded the expected value
2958 for ENOENT to 2. This isn't portable as error numbers are
2959 platform specific, and particularly the hurd has ENOENT at
2960 0x40000002. Construct expected string at runtime, using the correct
2961 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
2962 - Reject attempts to disable DisableDebuggerAttachment while Tor is
2963 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
2964 - Use an appropriate-width type for sockets in tor-fw-helper on
2965 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
2968 - When sending or relaying a RELAY_EARLY cell, we used to convert
2969 it to a RELAY cell if the connection was using the v1 link
2970 protocol. This was a workaround for older versions of Tor, which
2971 didn't handle RELAY_EARLY cells properly. Now that all supported
2972 versions can handle RELAY_EARLY cells, and now that we're enforcing
2973 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2974 remove this workaround. Addresses bug 4786.
2976 o Code simplifications and refactoring:
2977 - Use OpenSSL's built-in SSL_state_string_long() instead of our
2978 own homebrewed ssl_state_to_string() replacement. Patch from
2979 Emile Snyder. Fixes bug 4653.
2980 - Use macros to indicate OpenSSL versions, so we don't need to worry
2981 about accidental hexadecimal bit shifts.
2982 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
2984 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
2985 - Use the smartlist_add_asprintf() alias more consistently.
2986 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
2987 invalid value, rather than just -1.
2988 - Rename a handful of old identifiers, mostly related to crypto
2989 structures and crypto functions. By convention, our "create an
2990 object" functions are called "type_new()", our "free an object"
2991 functions are called "type_free()", and our types indicate that
2992 they are types only with a final "_t". But a handful of older
2993 types and functions broke these rules, with function names like
2994 "type_create" or "subsystem_op_type", or with type names like
2998 Changes in version 0.2.3.10-alpha - 2011-12-16
2999 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
3000 Tor's buffers code. Absolutely everybody should upgrade.
3002 The bug relied on an incorrect calculation when making data continuous
3003 in one of our IO buffers, if the first chunk of the buffer was
3004 misaligned by just the wrong amount. The miscalculation would allow an
3005 attacker to overflow a piece of heap-allocated memory. To mount this
3006 attack, the attacker would need to either open a SOCKS connection to
3007 Tor's SocksPort (usually restricted to localhost), or target a Tor
3008 instance configured to make its connections through a SOCKS proxy
3009 (which Tor does not do by default).
3011 Good security practice requires that all heap-overflow bugs should be
3012 presumed to be exploitable until proven otherwise, so we are treating
3013 this as a potential code execution attack. Please upgrade immediately!
3014 This bug does not affect bufferevents-based builds of Tor. Special
3015 thanks to "Vektor" for reporting this issue to us!
3017 This release also contains a few minor bugfixes for issues discovered
3021 - Fix a heap overflow bug that could occur when trying to pull
3022 data into the first chunk of a buffer, when that chunk had
3023 already had some data drained from it. Fixes CVE-2011-2778;
3024 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3027 - If we can't attach streams to a rendezvous circuit when we
3028 finish connecting to a hidden service, clear the rendezvous
3029 circuit's stream-isolation state and try to attach streams
3030 again. Previously, we cleared rendezvous circuits' isolation
3031 state either too early (if they were freshly built) or not at all
3032 (if they had been built earlier and were cannibalized). Bugfix on
3033 0.2.3.3-alpha; fixes bug 4655.
3034 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
3035 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
3036 - Fix an assertion failure when a relay with accounting enabled
3037 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
3040 - Update to the December 6 2011 Maxmind GeoLite Country database.
3043 Changes in version 0.2.2.35 - 2011-12-16
3044 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
3045 buffers code. Absolutely everybody should upgrade.
3047 The bug relied on an incorrect calculation when making data continuous
3048 in one of our IO buffers, if the first chunk of the buffer was
3049 misaligned by just the wrong amount. The miscalculation would allow an
3050 attacker to overflow a piece of heap-allocated memory. To mount this
3051 attack, the attacker would need to either open a SOCKS connection to
3052 Tor's SocksPort (usually restricted to localhost), or target a Tor
3053 instance configured to make its connections through a SOCKS proxy
3054 (which Tor does not do by default).
3056 Good security practice requires that all heap-overflow bugs should be
3057 presumed to be exploitable until proven otherwise, so we are treating
3058 this as a potential code execution attack. Please upgrade immediately!
3059 This bug does not affect bufferevents-based builds of Tor. Special
3060 thanks to "Vektor" for reporting this issue to us!
3062 Tor 0.2.2.35 also fixes several bugs in previous versions, including
3063 crash bugs for unusual configurations, and a long-term bug that
3064 would prevent Tor from starting on Windows machines with draconian
3067 With this release, we remind everyone that 0.2.0.x has reached its
3068 formal end-of-life. Those Tor versions have many known flaws, and
3069 nobody should be using them. You should upgrade -- ideally to the
3070 0.2.2.x series. If you're using a Linux or BSD and its packages are
3071 obsolete, stop using those packages and upgrade anyway.
3073 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
3074 longer receive support after some time in early 2012.
3077 - Fix a heap overflow bug that could occur when trying to pull
3078 data into the first chunk of a buffer, when that chunk had
3079 already had some data drained from it. Fixes CVE-2011-2778;
3080 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3081 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3082 that it doesn't attempt to allocate a socketpair. This could cause
3083 some problems on Windows systems with overzealous firewalls. Fix for
3084 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3086 - If we mark an OR connection for close based on a cell we process,
3087 don't process any further cells on it. We already avoid further
3088 reads on marked-for-close connections, but now we also discard the
3089 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3090 which was the first version where we might mark a connection for
3091 close based on processing a cell on it.
3092 - Correctly sanity-check that we don't underflow on a memory
3093 allocation (and then assert) for hidden service introduction
3094 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3095 bugfix on 0.2.1.5-alpha.
3096 - Fix a memory leak when we check whether a hidden service
3097 descriptor has any usable introduction points left. Fixes bug
3098 4424. Bugfix on 0.2.2.25-alpha.
3099 - Don't crash when we're running as a relay and don't have a GeoIP
3100 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
3101 we've had in the 0.2.3.x branch already.
3102 - When running as a client, do not print a misleading (and plain
3103 wrong) log message that we're collecting "directory request"
3104 statistics: clients don't collect statistics. Also don't create a
3105 useless (because empty) stats file in the stats/ directory. Fixes
3106 bug 4353; bugfix on 0.2.2.34.
3109 - Detect failure to initialize Libevent. This fix provides better
3110 detection for future instances of bug 4457.
3111 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3112 function. This was eating up hideously large amounts of time on some
3113 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3114 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3115 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3117 - Don't warn about unused log_mutex in log.c when building with
3118 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3119 0.1.0.6-rc which introduced --disable-threads.
3120 - When configuring, starting, or stopping an NT service, stop
3121 immediately after the service configuration attempt has succeeded
3122 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3123 - When sending a NETINFO cell, include the original address
3124 received for the other side, not its canonical address. Found
3125 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3126 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
3127 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3128 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3129 occurred when a client tried to fetch a descriptor for a bridge
3130 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3131 - Backport fixes for a pair of compilation warnings on Windows.
3132 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
3133 - If we had ever tried to call tor_addr_to_str on an address of
3134 unknown type, we would have done a strdup on an uninitialized
3135 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3136 Reported by "troll_un".
3137 - Correctly detect and handle transient lookup failures from
3138 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3139 Reported by "troll_un".
3140 - Fix null-pointer access that could occur if TLS allocation failed.
3141 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3142 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3143 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3146 - Add two new config options for directory authorities:
3147 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3148 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3149 that is always sufficient to satisfy the bandwidth requirement for
3150 the Guard flag. Now it will be easier for researchers to simulate
3151 Tor networks with different values. Resolves ticket 4484.
3152 - When Tor ignores a hidden service specified in its configuration,
3153 include the hidden service's directory in the warning message.
3154 Previously, we would only tell the user that some hidden service
3155 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3156 - Update to the December 6 2011 Maxmind GeoLite Country database.
3158 o Packaging changes:
3159 - Make it easier to automate expert package builds on Windows,
3160 by removing an absolute path from makensis.exe command.
3163 Changes in version 0.2.1.32 - 2011-12-16
3164 Tor 0.2.1.32 backports important security and privacy fixes for
3165 oldstable. This release is intended only for package maintainers and
3166 others who cannot use the 0.2.2 stable series. All others should be
3167 using Tor 0.2.2.x or newer.
3169 The Tor 0.2.1.x series will reach formal end-of-life some time in
3170 early 2012; we will stop releasing patches for it then.
3172 o Major bugfixes (also included in 0.2.2.x):
3173 - Correctly sanity-check that we don't underflow on a memory
3174 allocation (and then assert) for hidden service introduction
3175 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3176 bugfix on 0.2.1.5-alpha.
3177 - Fix a heap overflow bug that could occur when trying to pull
3178 data into the first chunk of a buffer, when that chunk had
3179 already had some data drained from it. Fixes CVE-2011-2778;
3180 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3183 - Update to the December 6 2011 Maxmind GeoLite Country database.
3186 Changes in version 0.2.3.9-alpha - 2011-12-08
3187 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
3188 a "DisableNetwork" security feature that bundles can use to avoid
3189 touching the network until bridges are configured, moves forward on
3190 the pluggable transport design, fixes a flaw in the hidden service
3191 design that unnecessarily prevented clients with wrong clocks from
3192 reaching hidden services, and fixes a wide variety of other issues.
3195 - Clients can now connect to private bridges over IPv6. Bridges
3196 still need at least one IPv4 address in order to connect to
3197 other relays. Note that we don't yet handle the case where the
3198 user has two bridge lines for the same bridge (one IPv4, one
3199 IPv6). Implements parts of proposal 186.
3200 - New "DisableNetwork" config option to prevent Tor from launching any
3201 connections or accepting any connections except on a control port.
3202 Bundles and controllers can set this option before letting Tor talk
3203 to the rest of the network, for example to prevent any connections
3204 to a non-bridge address. Packages like Orbot can also use this
3205 option to instruct Tor to save power when the network is off.
3206 - Clients and bridges can now be configured to use a separate
3207 "transport" proxy. This approach makes the censorship arms race
3208 easier by allowing bridges to use protocol obfuscation plugins. It
3209 implements the "managed proxy" part of proposal 180 (ticket 3472).
3210 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
3211 implementation. It makes AES_CTR about 7% faster than our old one
3212 (which was about 10% faster than the one OpenSSL used to provide).
3213 Resolves ticket 4526.
3214 - Add a "tor2web mode" for clients that want to connect to hidden
3215 services non-anonymously (and possibly more quickly). As a safety
3216 measure to try to keep users from turning this on without knowing
3217 what they are doing, tor2web mode must be explicitly enabled at
3218 compile time, and a copy of Tor compiled to run in tor2web mode
3219 cannot be used as a normal Tor client. Implements feature 2553.
3220 - Add experimental support for running on Windows with IOCP and no
3221 kernel-space socket buffers. This feature is controlled by a new
3222 "UserspaceIOCPBuffers" config option (off by default), which has
3223 no effect unless Tor has been built with support for bufferevents,
3224 is running on Windows, and has enabled IOCP. This may, in the long
3225 run, help solve or mitigate bug 98.
3226 - Use a more secure consensus parameter voting algorithm. Now at
3227 least three directory authorities or a majority of them must
3228 vote on a given parameter before it will be included in the
3229 consensus. Implements proposal 178.
3232 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
3233 They used to check that the timestamp was within 30 minutes
3234 of their system clock, so they could cap the size of their
3235 replay-detection cache, but that approach unnecessarily refused
3236 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
3237 the v3 intro-point protocol (the first one which sent a timestamp
3238 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
3239 - Only use the EVP interface when AES acceleration is enabled,
3240 to avoid a 5-7% performance regression. Resolves issue 4525;
3241 bugfix on 0.2.3.8-alpha.
3243 o Privacy/anonymity features (bridge detection):
3244 - Make bridge SSL certificates a bit more stealthy by using random
3245 serial numbers, in the same fashion as OpenSSL when generating
3246 self-signed certificates. Implements ticket 4584.
3247 - Introduce a new config option "DynamicDHGroups", enabled by
3248 default, which provides each bridge with a unique prime DH modulus
3249 to be used during SSL handshakes. This option attempts to help
3250 against censors who might use the Apache DH modulus as a static
3251 identifier for bridges. Addresses ticket 4548.
3253 o Minor features (new/different config options):
3254 - New configuration option "DisableDebuggerAttachment" (on by default)
3255 to prevent basic debugging attachment attempts by other processes.
3256 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
3257 - Allow MapAddress directives to specify matches against super-domains,
3258 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
3259 Implements issue 933.
3260 - Slightly change behavior of "list" options (that is, config
3261 options that can appear more than once) when they appear both in
3262 torrc and on the command line. Previously, the command-line options
3263 would be appended to the ones from torrc. Now, the command-line
3264 options override the torrc options entirely. This new behavior
3265 allows the user to override list options (like exit policies and
3266 ports to listen on) from the command line, rather than simply
3267 appending to the list.
3268 - You can get the old (appending) command-line behavior for "list"
3269 options by prefixing the option name with a "+".
3270 - You can remove all the values for a "list" option from the command
3271 line without adding any new ones by prefixing the option name
3273 - Add experimental support for a "defaults" torrc file to be parsed
3274 before the regular torrc. Torrc options override the defaults file's
3275 options in the same way that the command line overrides the torrc.
3276 The SAVECONF controller command saves only those options which
3277 differ between the current configuration and the defaults file. HUP
3278 reloads both files. (Note: This is an experimental feature; its
3279 behavior will probably be refined in future 0.2.3.x-alpha versions
3280 to better meet packagers' needs.) Implements task 4552.
3283 - Try to make the introductory warning message that Tor prints on
3284 startup more useful for actually finding help and information.
3285 Resolves ticket 2474.
3286 - Running "make version" now displays the version of Tor that
3287 we're about to build. Idea from katmagic; resolves issue 4400.
3288 - Expire old or over-used hidden service introduction points.
3289 Required by fix for bug 3460.
3290 - Move the replay-detection cache for the RSA-encrypted parts of
3291 INTRODUCE2 cells to the introduction point data structures.
3292 Previously, we would use one replay-detection cache per hidden
3293 service. Required by fix for bug 3460.
3294 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
3295 public key replay-detection cache from 60 minutes to 5 minutes. This
3296 replay-detection cache is now used only to detect multiple
3297 INTRODUCE2 cells specifying the same rendezvous point, so we can
3298 avoid launching multiple simultaneous attempts to connect to it.
3300 o Minor bugfixes (on Tor 0.2.2.x and earlier):
3301 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3302 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3304 - Fix a minor formatting issue in one of tor-gencert's error messages.
3306 - Prevent a false positive from the check-spaces script, by disabling
3307 the "whitespace between function name and (" check for functions
3309 - Fix a log message suggesting that people contact a non-existent
3310 email address. Fixes bug 3448.
3311 - Fix null-pointer access that could occur if TLS allocation failed.
3312 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3313 - Report a real bootstrap problem to the controller on router
3314 identity mismatch. Previously we just said "foo", which probably
3315 made a lot of sense at the time. Fixes bug 4169; bugfix on
3317 - If we had ever tried to call tor_addr_to_str() on an address of
3318 unknown type, we would have done a strdup() on an uninitialized
3319 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3320 Reported by "troll_un".
3321 - Correctly detect and handle transient lookup failures from
3322 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3323 Reported by "troll_un".
3324 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3325 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3326 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
3327 bug 4532; found by "troll_un".
3329 o Minor bugfixes (on Tor 0.2.3.x):
3330 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
3332 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
3333 circuit for use as a hidden service client's rendezvous point.
3334 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
3335 with help from wanoskarnet.
3336 - Restore behavior of overriding SocksPort, ORPort, and similar
3337 options from the command line. Bugfix on 0.2.3.3-alpha.
3340 - Properly handle the case where the build-tree is not the same
3341 as the source tree when generating src/common/common_sha1.i,
3342 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
3343 bugfix on 0.2.0.1-alpha.
3345 o Code simplifications, cleanups, and refactorings:
3346 - Remove the pure attribute from all functions that used it
3347 previously. In many cases we assigned it incorrectly, because the
3348 functions might assert or call impure functions, and we don't have
3349 evidence that keeping the pure attribute is worthwhile. Implements
3350 changes suggested in ticket 4421.
3351 - Remove some dead code spotted by coverity. Fixes cid 432.
3352 Bugfix on 0.2.3.1-alpha, closes bug 4637.
3355 Changes in version 0.2.3.8-alpha - 2011-11-22
3356 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
3357 socketpair-related bug that has been bothering Windows users. It adds
3358 support to serve microdescriptors to controllers, so Vidalia's network
3359 map can resume listing relays (once Vidalia implements its side),
3360 and adds better support for hardware AES acceleration. Finally, it
3361 starts the process of adjusting the bandwidth cutoff for getting the
3362 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
3363 that tiny relays harm performance more than they help network capacity.
3366 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3367 that it doesn't attempt to allocate a socketpair. This could cause
3368 some problems on Windows systems with overzealous firewalls. Fix for
3369 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3371 - Correctly sanity-check that we don't underflow on a memory
3372 allocation (and then assert) for hidden service introduction
3373 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3374 bugfix on 0.2.1.5-alpha.
3375 - Remove the artificially low cutoff of 20KB to guarantee the Fast
3376 flag. In the past few years the average relay speed has picked
3377 up, and while the "top 7/8 of the network get the Fast flag" and
3378 "all relays with 20KB or more of capacity get the Fast flag" rules
3379 used to have the same result, now the top 7/8 of the network has
3380 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
3381 - Fix a rare assertion failure when checking whether a v0 hidden
3382 service descriptor has any usable introduction points left, and
3383 we don't have enough information to build a circuit to the first
3384 intro point named in the descriptor. The HS client code in
3385 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
3386 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
3387 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
3388 - Make bridge authorities not crash when they are asked for their own
3389 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
3390 - When running as a client, do not print a misleading (and plain
3391 wrong) log message that we're collecting "directory request"
3392 statistics: clients don't collect statistics. Also don't create a
3393 useless (because empty) stats file in the stats/ directory. Fixes
3394 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
3397 - Allow Tor controllers like Vidalia to obtain the microdescriptor
3398 for a relay by identity digest or nickname. Previously,
3399 microdescriptors were only available by their own digests, so a
3400 controller would have to ask for and parse the whole microdescriptor
3401 consensus in order to look up a single relay's microdesc. Fixes
3402 bug 3832; bugfix on 0.2.3.1-alpha.
3403 - Use OpenSSL's EVP interface for AES encryption, so that all AES
3404 operations can use hardware acceleration (if present). Resolves
3407 o Minor bugfixes (on 0.2.2.x and earlier):
3408 - Detect failure to initialize Libevent. This fix provides better
3409 detection for future instances of bug 4457.
3410 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3411 function. This was eating up hideously large amounts of time on some
3412 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3413 - Don't warn about unused log_mutex in log.c when building with
3414 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3415 0.1.0.6-rc which introduced --disable-threads.
3416 - Allow manual 'authenticate' commands to the controller interface
3417 from netcat (nc) as well as telnet. We were rejecting them because
3418 they didn't come with the expected whitespace at the end of the
3419 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
3420 - Fix some (not actually triggerable) buffer size checks in usage of
3421 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
3423 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
3424 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
3425 - When configuring, starting, or stopping an NT service, stop
3426 immediately after the service configuration attempt has succeeded
3427 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3428 - When sending a NETINFO cell, include the original address
3429 received for the other side, not its canonical address. Found
3430 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3431 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
3432 can pick them up when the tests aren't disabled. Bugfix on
3433 0.2.2.4-alpha which introduced tinytest.
3434 - Fix a memory leak when we check whether a hidden service
3435 descriptor has any usable introduction points left. Fixes bug
3436 4424. Bugfix on 0.2.2.25-alpha.
3437 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3438 occurred when a client tried to fetch a descriptor for a bridge
3439 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3441 o Minor bugfixes (on 0.2.3.x):
3442 - Make util unit tests build correctly with MSVC. Bugfix on
3443 0.2.3.3-alpha. Patch by Gisle Vanem.
3444 - Successfully detect AUTH_CHALLENGE cells with no recognized
3445 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
3447 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
3448 it should still send a NETINFO cell to allow the connection to
3449 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
3451 - Log less loudly when we get an invalid authentication certificate
3452 from a source other than a directory authority: it's not unusual
3453 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
3455 - Tolerate servers with more clock skew in their authentication
3456 certificates than previously. Fixes bug 4371; bugfix on
3458 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
3459 on 0.2.3.4-alpha and 0.2.3.6-alpha.
3462 - Add two new config options for directory authorities:
3463 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3464 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3465 that is always sufficient to satisfy the bandwidth requirement for
3466 the Guard flag. Now it will be easier for researchers to simulate
3467 Tor networks with different values. Resolves ticket 4484.
3468 - When Tor ignores a hidden service specified in its configuration,
3469 include the hidden service's directory in the warning message.
3470 Previously, we would only tell the user that some hidden service
3471 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3472 - When we fail to initialize Libevent, retry with IOCP disabled so we
3473 don't need to turn on multi-threading support in Libevent, which in
3474 turn requires a working socketpair(). This is a workaround for bug
3475 4457, which affects Libevent versions from 2.0.1-alpha through
3477 - Detect when we try to build on a platform that doesn't define
3478 AF_UNSPEC to 0. We don't work there, so refuse to compile.
3479 - Update to the November 1 2011 Maxmind GeoLite Country database.
3481 o Packaging changes:
3482 - Make it easier to automate expert package builds on Windows,
3483 by removing an absolute path from makensis.exe command.
3485 o Code simplifications and refactoring:
3486 - Remove some redundant #include directives throughout the code.
3487 Patch from Andrea Gelmini.
3488 - Unconditionally use OpenSSL's AES implementation instead of our
3489 old built-in one. OpenSSL's AES has been better for a while, and
3490 relatively few servers should still be on any version of OpenSSL
3491 that doesn't have good optimized assembly AES.
3492 - Use the name "CERTS" consistently to refer to the new cell type;
3493 we were calling it CERT in some places and CERTS in others.
3496 - Numerous new unit tests for functions in util.c and address.c by
3498 - The long-disabled benchmark tests are now split into their own
3499 ./src/test/bench binary.
3500 - The benchmark tests can now use more accurate timers than
3501 gettimeofday() when such timers are available.
3504 Changes in version 0.2.3.7-alpha - 2011-10-30
3505 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
3506 the new v3 handshake. It also resolves yet another bridge address
3510 - If we mark an OR connection for close based on a cell we process,
3511 don't process any further cells on it. We already avoid further
3512 reads on marked-for-close connections, but now we also discard the
3513 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3514 which was the first version where we might mark a connection for
3515 close based on processing a cell on it.
3516 - Fix a double-free bug that would occur when we received an invalid
3517 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
3518 bugfix on 0.2.3.6-alpha.
3519 - Bridges no longer include their address in NETINFO cells on outgoing
3520 OR connections, to allow them to blend in better with clients.
3521 Removes another avenue for enumerating bridges. Reported by
3522 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
3523 cells were introduced.
3526 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
3527 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3530 Changes in version 0.2.3.6-alpha - 2011-10-26
3531 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
3532 anonymity vulnerability where an attacker can deanonymize Tor
3533 users. Everybody should upgrade.
3535 This release also features support for a new v3 connection handshake
3536 protocol, and fixes to make hidden service connections more robust.
3539 - Implement a new handshake protocol (v3) for authenticating Tors to
3540 each other over TLS. It should be more resistant to fingerprinting
3541 than previous protocols, and should require less TLS hacking for
3542 future Tor implementations. Implements proposal 176.
3543 - Allow variable-length padding cells to disguise the length of
3544 Tor's TLS records. Implements part of proposal 184.
3546 o Privacy/anonymity fixes (clients):
3547 - Clients and bridges no longer send TLS certificate chains on
3548 outgoing OR connections. Previously, each client or bridge would
3549 use the same cert chain for all outgoing OR connections until
3550 its IP address changes, which allowed any relay that the client
3551 or bridge contacted to determine which entry guards it is using.
3552 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3553 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3554 no longer considers that connection as suitable for satisfying a
3555 circuit EXTEND request. Now relays can protect clients from the
3556 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3557 - Directory authorities no longer assign the Guard flag to relays
3558 that haven't upgraded to the above "refuse EXTEND requests
3559 to client connections" fix. Now directory authorities can
3560 protect clients from the CVE-2011-2768 issue even if neither
3561 the clients nor the relays have upgraded yet. There's a new
3562 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3563 to let us transition smoothly, else tomorrow there would be no
3566 o Major bugfixes (hidden services):
3567 - Improve hidden service robustness: when an attempt to connect to
3568 a hidden service ends, be willing to refetch its hidden service
3569 descriptors from each of the HSDir relays responsible for them
3570 immediately. Previously, we would not consider refetching the
3571 service's descriptors from each HSDir for 15 minutes after the last
3572 fetch, which was inconvenient if the hidden service was not running
3573 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
3574 - When one of a hidden service's introduction points appears to be
3575 unreachable, stop trying it. Previously, we would keep trying
3576 to build circuits to the introduction point until we lost the
3577 descriptor, usually because the user gave up and restarted Tor.
3578 Partly fixes bug 3825.
3579 - Don't launch a useless circuit after failing to use one of a
3580 hidden service's introduction points. Previously, we would
3581 launch a new introduction circuit, but not set the hidden service
3582 which that circuit was intended to connect to, so it would never
3583 actually be used. A different piece of code would then create a
3584 new introduction circuit correctly. Bug reported by katmagic and
3585 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3587 o Major bugfixes (other):
3588 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3589 that they initiated. Relays could distinguish incoming bridge
3590 connections from client connections, creating another avenue for
3591 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3592 Found by "frosty_un".
3593 - Don't update the AccountingSoftLimitHitAt state file entry whenever
3594 tor gets started. This prevents a wrong average bandwidth
3595 estimate, which would cause relays to always start a new accounting
3596 interval at the earliest possible moment. Fixes bug 2003; bugfix
3597 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
3598 immensely in tracking this bug down.
3599 - Fix a crash bug when changing node restrictions while a DNS lookup
3600 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3603 o Minor bugfixes (on 0.2.2.x and earlier):
3604 - When a hidden service turns an extra service-side introduction
3605 circuit into a general-purpose circuit, free the rend_data and
3606 intro_key fields first, so we won't leak memory if the circuit
3607 is cannibalized for use as another service-side introduction
3608 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3609 - Rephrase the log message emitted if the TestSocks check is
3610 successful. Patch from Fabian Keil; fixes bug 4094.
3611 - Bridges now skip DNS self-tests, to act a little more stealthily.
3612 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3613 bridges. Patch by "warms0x".
3614 - Remove a confusing dollar sign from the example fingerprint in the
3615 man page, and also make the example fingerprint a valid one. Fixes
3616 bug 4309; bugfix on 0.2.1.3-alpha.
3617 - Fix internal bug-checking logic that was supposed to catch
3618 failures in digest generation so that it will fail more robustly
3619 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3620 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3621 - Report any failure in init_keys() calls launched because our
3622 IP address has changed. Spotted by Coverity Scan. Bugfix on
3623 0.1.1.4-alpha; fixes CID 484.
3625 o Minor bugfixes (on 0.2.3.x):
3626 - Fix a bug in configure.in that kept it from building a configure
3627 script with autoconf versions earlier than 2.61. Fixes bug 2430;
3628 bugfix on 0.2.3.1-alpha.
3629 - Don't warn users that they are exposing a client port to the
3630 Internet if they have specified an RFC1918 address. Previously,
3631 we would warn if the user had specified any non-loopback
3632 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
3633 - Fix memory leaks in the failing cases of the new SocksPort and
3634 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
3635 fixes coverity CIDs 485, 486, and 487.
3638 - When a hidden service's introduction point times out, consider
3639 trying it again during the next attempt to connect to the
3640 HS. Previously, we would not try it again unless a newly fetched
3641 descriptor contained it. Required by fixes for bugs 1297 and 3825.
3642 - The next version of Windows will be called Windows 8, and it has
3643 a major version of 6, minor version of 2. Correctly identify that
3644 version instead of calling it "Very recent version". Resolves
3645 ticket 4153; reported by funkstar.
3646 - The Bridge Authority now writes statistics on how many bridge
3647 descriptors it gave out in total, and how many unique descriptors
3648 it gave out. It also lists how often the most and least commonly
3649 fetched descriptors were given out, as well as the median and
3650 25th/75th percentile. Implements tickets 4200 and 4294.
3651 - Update to the October 4 2011 Maxmind GeoLite Country database.
3653 o Code simplifications and refactoring:
3654 - Remove some old code to remember statistics about which descriptors
3655 we've served as a directory mirror. The feature wasn't used and
3656 is outdated now that microdescriptors are around.
3657 - Rename Tor functions that turn strings into addresses, so that
3658 "parse" indicates that no hostname resolution occurs, and
3659 "lookup" indicates that hostname resolution may occur. This
3660 should help prevent mistakes in the future. Fixes bug 3512.
3663 Changes in version 0.2.2.34 - 2011-10-26
3664 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
3665 can deanonymize Tor users. Everybody should upgrade.
3667 The attack relies on four components: 1) Clients reuse their TLS cert
3668 when talking to different relays, so relays can recognize a user by
3669 the identity key in her cert. 2) An attacker who knows the client's
3670 identity key can probe each guard relay to see if that identity key
3671 is connected to that guard relay right now. 3) A variety of active
3672 attacks in the literature (starting from "Low-Cost Traffic Analysis
3673 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
3674 discover the guard relays that a Tor user visiting the website is using.
3675 4) Clients typically pick three guards at random, so the set of guards
3676 for a given user could well be a unique fingerprint for her. This
3677 release fixes components #1 and #2, which is enough to block the attack;
3678 the other two remain as open research problems. Special thanks to
3679 "frosty_un" for reporting the issue to us!
3681 Clients should upgrade so they are no longer recognizable by the TLS
3682 certs they present. Relays should upgrade so they no longer allow a
3683 remote attacker to probe them to test whether unpatched clients are
3684 currently connected to them.
3686 This release also fixes several vulnerabilities that allow an attacker
3687 to enumerate bridge relays. Some bridge enumeration attacks still
3688 remain; see for example proposal 188.
3690 o Privacy/anonymity fixes (clients):
3691 - Clients and bridges no longer send TLS certificate chains on
3692 outgoing OR connections. Previously, each client or bridge would
3693 use the same cert chain for all outgoing OR connections until
3694 its IP address changes, which allowed any relay that the client
3695 or bridge contacted to determine which entry guards it is using.
3696 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3697 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3698 no longer considers that connection as suitable for satisfying a
3699 circuit EXTEND request. Now relays can protect clients from the
3700 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3701 - Directory authorities no longer assign the Guard flag to relays
3702 that haven't upgraded to the above "refuse EXTEND requests
3703 to client connections" fix. Now directory authorities can
3704 protect clients from the CVE-2011-2768 issue even if neither
3705 the clients nor the relays have upgraded yet. There's a new
3706 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3707 to let us transition smoothly, else tomorrow there would be no
3710 o Privacy/anonymity fixes (bridge enumeration):
3711 - Bridge relays now do their directory fetches inside Tor TLS
3712 connections, like all the other clients do, rather than connecting
3713 directly to the DirPort like public relays do. Removes another
3714 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
3715 - Bridges relays now build circuits for themselves in a more similar
3716 way to how clients build them. Removes another avenue for
3717 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
3718 when bridges were introduced.
3719 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3720 that they initiated. Relays could distinguish incoming bridge
3721 connections from client connections, creating another avenue for
3722 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3723 Found by "frosty_un".
3726 - Fix a crash bug when changing node restrictions while a DNS lookup
3727 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3729 - Don't launch a useless circuit after failing to use one of a
3730 hidden service's introduction points. Previously, we would
3731 launch a new introduction circuit, but not set the hidden service
3732 which that circuit was intended to connect to, so it would never
3733 actually be used. A different piece of code would then create a
3734 new introduction circuit correctly. Bug reported by katmagic and
3735 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3738 - Change an integer overflow check in the OpenBSD_Malloc code so
3739 that GCC is less likely to eliminate it as impossible. Patch
3740 from Mansour Moufid. Fixes bug 4059.
3741 - When a hidden service turns an extra service-side introduction
3742 circuit into a general-purpose circuit, free the rend_data and
3743 intro_key fields first, so we won't leak memory if the circuit
3744 is cannibalized for use as another service-side introduction
3745 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3746 - Bridges now skip DNS self-tests, to act a little more stealthily.
3747 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3748 bridges. Patch by "warms0x".
3749 - Fix internal bug-checking logic that was supposed to catch
3750 failures in digest generation so that it will fail more robustly
3751 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3752 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3753 - Report any failure in init_keys() calls launched because our
3754 IP address has changed. Spotted by Coverity Scan. Bugfix on
3755 0.1.1.4-alpha; fixes CID 484.
3757 o Minor bugfixes (log messages and documentation):
3758 - Remove a confusing dollar sign from the example fingerprint in the
3759 man page, and also make the example fingerprint a valid one. Fixes
3760 bug 4309; bugfix on 0.2.1.3-alpha.
3761 - The next version of Windows will be called Windows 8, and it has
3762 a major version of 6, minor version of 2. Correctly identify that
3763 version instead of calling it "Very recent version". Resolves
3764 ticket 4153; reported by funkstar.
3765 - Downgrade log messages about circuit timeout calibration from
3766 "notice" to "info": they don't require or suggest any human
3767 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3768 bugfix on 0.2.2.14-alpha.
3771 - Turn on directory request statistics by default and include them in
3772 extra-info descriptors. Don't break if we have no GeoIP database.
3773 Backported from 0.2.3.1-alpha; implements ticket 3951.
3774 - Update to the October 4 2011 Maxmind GeoLite Country database.
3777 Changes in version 0.2.1.31 - 2011-10-26
3778 Tor 0.2.1.31 backports important security and privacy fixes for
3779 oldstable. This release is intended only for package maintainers and
3780 others who cannot use the 0.2.2 stable series. All others should be
3781 using Tor 0.2.2.x or newer.
3783 o Security fixes (also included in 0.2.2.x):
3784 - Replace all potentially sensitive memory comparison operations
3785 with versions whose runtime does not depend on the data being
3786 compared. This will help resist a class of attacks where an
3787 adversary can use variations in timing information to learn
3788 sensitive data. Fix for one case of bug 3122. (Safe memcmp
3789 implementation by Robert Ransom based partially on code by DJB.)
3790 - Fix an assert in parsing router descriptors containing IPv6
3791 addresses. This one took down the directory authorities when
3792 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3794 o Privacy/anonymity fixes (also included in 0.2.2.x):
3795 - Clients and bridges no longer send TLS certificate chains on
3796 outgoing OR connections. Previously, each client or bridge would
3797 use the same cert chain for all outgoing OR connections until
3798 its IP address changes, which allowed any relay that the client
3799 or bridge contacted to determine which entry guards it is using.
3800 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3801 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3802 no longer considers that connection as suitable for satisfying a
3803 circuit EXTEND request. Now relays can protect clients from the
3804 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3805 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3806 that they initiated. Relays could distinguish incoming bridge
3807 connections from client connections, creating another avenue for
3808 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3809 Found by "frosty_un".
3810 - When receiving a hidden service descriptor, check that it is for
3811 the hidden service we wanted. Previously, Tor would store any
3812 hidden service descriptors that a directory gave it, whether it
3813 wanted them or not. This wouldn't have let an attacker impersonate
3814 a hidden service, but it did let directories pre-seed a client
3815 with descriptors that it didn't want. Bugfix on 0.0.6.
3816 - Avoid linkability based on cached hidden service descriptors: forget
3817 all hidden service descriptors cached as a client when processing a
3818 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3819 - Make the bridge directory authority refuse to answer directory
3820 requests for "all" descriptors. It used to include bridge
3821 descriptors in its answer, which was a major information leak.
3822 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3823 - Don't attach new streams to old rendezvous circuits after SIGNAL
3824 NEWNYM. Previously, we would keep using an existing rendezvous
3825 circuit if it remained open (i.e. if it were kept open by a
3826 long-lived stream, or if a new stream were attached to it before
3827 Tor could notice that it was old and no longer in use). Bugfix on
3828 0.1.1.15-rc; fixes bug 3375.
3830 o Minor bugfixes (also included in 0.2.2.x):
3831 - When we restart our relay, we might get a successful connection
3832 from the outside before we've started our reachability tests,
3833 triggering a warning: "ORPort found reachable, but I have no
3834 routerinfo yet. Failing to inform controller of success." This
3835 bug was harmless unless Tor is running under a controller
3836 like Vidalia, in which case the controller would never get a
3837 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3839 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
3840 enabled. Fixes bug 1526.
3841 - Remove undocumented option "-F" from tor-resolve: it hasn't done
3842 anything since 0.2.1.16-rc.
3843 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3844 None of the cases where we did this before were wrong, but by making
3845 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3846 - Fix a rare crash bug that could occur when a client was configured
3847 with a large number of bridges. Fixes bug 2629; bugfix on
3848 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3849 - Correct the warning displayed when a rendezvous descriptor exceeds
3850 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3852 - Fix an uncommon assertion failure when running with DNSPort under
3853 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3854 - When warning about missing zlib development packages during compile,
3855 give the correct package names. Bugfix on 0.2.0.1-alpha.
3856 - Require that introduction point keys and onion keys have public
3857 exponent 65537. Bugfix on 0.2.0.10-alpha.
3858 - Do not crash when our configuration file becomes unreadable, for
3859 example due to a permissions change, between when we start up
3860 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
3862 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
3864 - Always NUL-terminate the sun_path field of a sockaddr_un before
3865 passing it to the kernel. (Not a security issue: kernels are
3866 smart enough to reject bad sockaddr_uns.) Found by Coverity;
3867 CID #428. Bugfix on Tor 0.2.0.3-alpha.
3868 - Don't stack-allocate the list of supplementary GIDs when we're
3869 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
3870 could take up to 256K, which is way too much stack. Found by
3871 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
3873 o Minor bugfixes (only in 0.2.1.x):
3874 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
3875 rely on them. Bugfix on 0.2.1.30.
3876 - Use git revisions instead of svn revisions when generating our
3877 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
3879 o Minor features (also included in 0.2.2.x):
3880 - Adjust the expiration time on our SSL session certificates to
3881 better match SSL certs seen in the wild. Resolves ticket 4014.
3882 - Allow nameservers with IPv6 address. Resolves bug 2574.
3883 - Update to the October 4 2011 Maxmind GeoLite Country database.
3886 Changes in version 0.2.3.5-alpha - 2011-09-28
3887 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
3888 bridge relays; fixes an assertion error that many users started hitting
3889 today; and adds the ability to refill token buckets more often than
3890 once per second, allowing significant performance improvements.
3893 - Bridge relays now do their directory fetches inside Tor TLS
3894 connections, like all the other clients do, rather than connecting
3895 directly to the DirPort like public relays do. Removes another
3896 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
3897 - Bridges relays now build circuits for themselves in a more similar
3898 way to how clients build them. Removes another avenue for
3899 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
3900 when bridges were introduced.
3903 - Fix an "Assertion md->held_by_node == 1 failed" error that could
3904 occur when the same microdescriptor was referenced by two node_t
3905 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
3907 o Major features (networking):
3908 - Add a new TokenBucketRefillInterval option to refill token buckets
3909 more frequently than once per second. This should improve network
3910 performance, alleviate queueing problems, and make traffic less
3911 bursty. Implements proposal 183; closes ticket 3630. Design by
3912 Florian Tschorsch and Björn Scheuermann; implementation by
3916 - Change an integer overflow check in the OpenBSD_Malloc code so
3917 that GCC is less likely to eliminate it as impossible. Patch
3918 from Mansour Moufid. Fixes bug 4059.
3920 o Minor bugfixes (usability):
3921 - Downgrade log messages about circuit timeout calibration from
3922 "notice" to "info": they don't require or suggest any human
3923 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3924 bugfix on 0.2.2.14-alpha.
3926 o Minor features (diagnostics):
3927 - When the system call to create a listener socket fails, log the
3928 error message explaining why. This may help diagnose bug 4027.
3931 Changes in version 0.2.3.4-alpha - 2011-09-13
3932 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
3933 tweak to Tor's TLS handshake that makes relays and bridges that run
3934 this new version reachable from Iran again. It also fixes a few new
3935 bugs in 0.2.3.x, and teaches relays to recognize when they're not
3936 listed in the network consensus and republish.
3938 o Major bugfixes (also part of 0.2.2.33):
3939 - Avoid an assertion failure when reloading a configuration with
3940 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
3941 3923; bugfix on 0.2.2.25-alpha.
3943 o Minor features (security, also part of 0.2.2.33):
3944 - Check for replays of the public-key encrypted portion of an
3945 INTRODUCE1 cell, in addition to the current check for replays of
3946 the g^x value. This prevents a possible class of active attacks
3947 by an attacker who controls both an introduction point and a
3948 rendezvous point, and who uses the malleability of AES-CTR to
3949 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
3950 that these attacks is infeasible (requiring the attacker to send
3951 on the order of zettabytes of altered cells in a short interval),
3952 but we'd rather block them off in case there are any classes of
3953 this attack that we missed. Reported by Willem Pinckaers.
3955 o Minor features (also part of 0.2.2.33):
3956 - Adjust the expiration time on our SSL session certificates to
3957 better match SSL certs seen in the wild. Resolves ticket 4014.
3958 - Change the default required uptime for a relay to be accepted as
3959 a HSDir (hidden service directory) from 24 hours to 25 hours.
3960 Improves on 0.2.0.10-alpha; resolves ticket 2649.
3961 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
3962 authorities to abstain from voting on assignment of the HSDir
3963 consensus flag. Related to bug 2649.
3964 - Update to the September 6 2011 Maxmind GeoLite Country database.
3966 o Minor bugfixes (also part of 0.2.2.33):
3967 - Demote the 'replay detected' log message emitted when a hidden
3968 service receives the same Diffie-Hellman public key in two different
3969 INTRODUCE2 cells to info level. A normal Tor client can cause that
3970 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
3971 fixes part of bug 2442.
3972 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
3973 level. There is nothing that a hidden service's operator can do
3974 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
3976 - Clarify a log message specifying the characters permitted in
3977 HiddenServiceAuthorizeClient client names. Previously, the log
3978 message said that "[A-Za-z0-9+-_]" were permitted; that could have
3979 given the impression that every ASCII character between "+" and "_"
3980 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
3982 o Build fixes (also part of 0.2.2.33):
3983 - Clean up some code issues that prevented Tor from building on older
3984 BSDs. Fixes bug 3894; reported by "grarpamp".
3985 - Search for a platform-specific version of "ar" when cross-compiling.
3986 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
3989 - Fix a bug where the SocksPort option (for example) would get
3990 ignored and replaced by the default if a SocksListenAddress
3991 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
3995 - Relays now try regenerating and uploading their descriptor more
3996 frequently if they are not listed in the consensus, or if the
3997 version of their descriptor listed in the consensus is too
3998 old. This fix should prevent situations where a server declines
3999 to re-publish itself because it has done so too recently, even
4000 though the authorities decided not to list its recent-enough
4001 descriptor. Fix for bug 3327.
4004 - Relays now include a reason for regenerating their descriptors
4005 in an HTTP header when uploading to the authorities. This will
4006 make it easier to debug descriptor-upload issues in the future.
4007 - When starting as root and then changing our UID via the User
4008 control option, and we have a ControlSocket configured, make sure
4009 that the ControlSocket is owned by the same account that Tor will
4010 run under. Implements ticket 3421; fix by Jérémy Bobbio.
4013 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
4014 utility function used in the control-port code). This shouldn't
4015 ever happen unless Tor is completely out of memory, but if it did
4016 happen and Tor somehow recovered from it, Tor could have sent a log
4017 message to a control port in the middle of a reply to a controller
4018 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
4019 - Make 'FetchUselessDescriptors' cause all descriptor types and
4020 all consensus types (including microdescriptors) to get fetched.
4021 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
4024 - Make a new "entry connection" struct as an internal subtype of "edge
4025 connection", to simplify the code and make exit connections smaller.
4028 Changes in version 0.2.2.33 - 2011-09-13
4029 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
4030 TLS handshake that makes relays and bridges that run this new version
4031 reachable from Iran again.
4034 - Avoid an assertion failure when reloading a configuration with
4035 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
4036 3923; bugfix on 0.2.2.25-alpha.
4038 o Minor features (security):
4039 - Check for replays of the public-key encrypted portion of an
4040 INTRODUCE1 cell, in addition to the current check for replays of
4041 the g^x value. This prevents a possible class of active attacks
4042 by an attacker who controls both an introduction point and a
4043 rendezvous point, and who uses the malleability of AES-CTR to
4044 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
4045 that these attacks are infeasible (requiring the attacker to send
4046 on the order of zettabytes of altered cells in a short interval),
4047 but we'd rather block them off in case there are any classes of
4048 this attack that we missed. Reported by Willem Pinckaers.
4051 - Adjust the expiration time on our SSL session certificates to
4052 better match SSL certs seen in the wild. Resolves ticket 4014.
4053 - Change the default required uptime for a relay to be accepted as
4054 a HSDir (hidden service directory) from 24 hours to 25 hours.
4055 Improves on 0.2.0.10-alpha; resolves ticket 2649.
4056 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
4057 authorities to abstain from voting on assignment of the HSDir
4058 consensus flag. Related to bug 2649.
4059 - Update to the September 6 2011 Maxmind GeoLite Country database.
4061 o Minor bugfixes (documentation and log messages):
4062 - Correct the man page to explain that HashedControlPassword and
4063 CookieAuthentication can both be set, in which case either method
4064 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4065 when we decided to allow these config options to both be set. Issue
4067 - Demote the 'replay detected' log message emitted when a hidden
4068 service receives the same Diffie-Hellman public key in two different
4069 INTRODUCE2 cells to info level. A normal Tor client can cause that
4070 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4071 fixes part of bug 2442.
4072 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4073 level. There is nothing that a hidden service's operator can do
4074 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4076 - Clarify a log message specifying the characters permitted in
4077 HiddenServiceAuthorizeClient client names. Previously, the log
4078 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4079 given the impression that every ASCII character between "+" and "_"
4080 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4083 - Provide a substitute implementation of lround() for MSVC, which
4084 apparently lacks it. Patch from Gisle Vanem.
4085 - Clean up some code issues that prevented Tor from building on older
4086 BSDs. Fixes bug 3894; reported by "grarpamp".
4087 - Search for a platform-specific version of "ar" when cross-compiling.
4088 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4091 Changes in version 0.2.3.3-alpha - 2011-09-01
4092 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
4093 security, and provides client-side support for the microdescriptor
4094 and optimistic data features introduced earlier in the 0.2.3.x
4095 series. It also includes numerous critical bugfixes in the (optional)
4096 bufferevent-based networking backend.
4098 o Major features (stream isolation):
4099 - You can now configure Tor so that streams from different
4100 applications are isolated on different circuits, to prevent an
4101 attacker who sees your streams as they leave an exit node from
4102 linking your sessions to one another. To do this, choose some way
4103 to distinguish the applications: have them connect to different
4104 SocksPorts, or have one of them use SOCKS4 while the other uses
4105 SOCKS5, or have them pass different authentication strings to the
4106 SOCKS proxy. Then, use the new SocksPort syntax to configure the
4107 degree of isolation you need. This implements Proposal 171.
4108 - There's a new syntax for specifying multiple client ports (such as
4109 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
4110 multiple *Port entries with full addr:port syntax on each.
4111 The old *ListenAddress format is still supported, but you can't
4112 mix it with the new *Port syntax.
4114 o Major features (other):
4115 - Enable microdescriptor fetching by default for clients. This allows
4116 clients to download a much smaller amount of directory information.
4117 To disable it (and go back to the old-style consensus and
4118 descriptors), set "UseMicrodescriptors 0" in your torrc file.
4119 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
4120 "PortForwarding" config option), now supports Windows.
4121 - When using an exit relay running 0.2.3.x, clients can now
4122 "optimistically" send data before the exit relay reports that
4123 the stream has opened. This saves a round trip when starting
4124 connections where the client speaks first (such as web browsing).
4125 This behavior is controlled by a consensus parameter (currently
4126 disabled). To turn it on or off manually, use the "OptimisticData"
4127 torrc option. Implements proposal 181; code by Ian Goldberg.
4129 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
4130 - When using IOCP on Windows, we need to enable Libevent windows
4132 - The IOCP backend now works even when the user has not specified
4133 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
4134 Fixes part of bug 3752.
4135 - Correctly record the bytes we've read and written when using
4136 bufferevents, so that we can include them in our bandwidth history
4137 and advertised bandwidth. Fixes bug 3803.
4138 - Apply rate-limiting only at the bottom of a chain of filtering
4139 bufferevents. This prevents us from filling up internal read
4140 buffers and violating rate-limits when filtering bufferevents
4141 are enabled. Fixes part of bug 3804.
4142 - Add high-watermarks to the output buffers for filtered
4143 bufferevents. This prevents us from filling up internal write
4144 buffers and wasting CPU cycles when filtering bufferevents are
4145 enabled. Fixes part of bug 3804.
4146 - Correctly notice when data has been written from a bufferevent
4147 without flushing it completely. Fixes bug 3805.
4148 - Fix a bug where server-side tunneled bufferevent-based directory
4149 streams would get closed prematurely. Fixes bug 3814.
4150 - Fix a use-after-free error with per-connection rate-limiting
4151 buckets. Fixes bug 3888.
4153 o Major bugfixes (also part of 0.2.2.31-rc):
4154 - If we're configured to write our ControlPorts to disk, only write
4155 them after switching UID and creating the data directory. This way,
4156 we don't fail when starting up with a nonexistent DataDirectory
4157 and a ControlPortWriteToFile setting based on that directory. Fixes
4158 bug 3747; bugfix on Tor 0.2.2.26-beta.
4161 - Added a new CONF_CHANGED event so that controllers can be notified
4162 of any configuration changes made by other controllers, or by the
4163 user. Implements ticket 1692.
4164 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
4165 leak when using bufferevents, and lets Libevent worry about how to
4166 best copy data out of a buffer.
4167 - Replace files in stats/ rather than appending to them. Now that we
4168 include statistics in extra-info descriptors, it makes no sense to
4169 keep old statistics forever. Implements ticket 2930.
4171 o Minor features (build compatibility):
4172 - Limited, experimental support for building with nmake and MSVC.
4173 - Provide a substitute implementation of lround() for MSVC, which
4174 apparently lacks it. Patch from Gisle Vanem.
4176 o Minor features (also part of 0.2.2.31-rc):
4177 - Update to the August 2 2011 Maxmind GeoLite Country database.
4179 o Minor bugfixes (on 0.2.3.x-alpha):
4180 - Fix a spurious warning when parsing SOCKS requests with
4181 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
4182 - Get rid of a harmless warning that could happen on relays running
4183 with bufferevents. The warning was caused by someone doing an http
4184 request to a relay's orport. Also don't warn for a few related
4185 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
4187 o Minor bugfixes (on 2.2.x and earlier):
4188 - Correct the man page to explain that HashedControlPassword and
4189 CookieAuthentication can both be set, in which case either method
4190 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4191 when we decided to allow these config options to both be set. Issue
4193 - The "--quiet" and "--hush" options now apply not only to Tor's
4194 behavior before logs are configured, but also to Tor's behavior in
4195 the absense of configured logs. Fixes bug 3550; bugfix on
4198 o Minor bugfixes (also part of 0.2.2.31-rc):
4199 - Write several files in text mode, on OSes that distinguish text
4200 mode from binary mode (namely, Windows). These files are:
4201 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4202 that collect those statistics; 'client_keys' and 'hostname' for
4203 hidden services that use authentication; and (in the tor-gencert
4204 utility) newly generated identity and signing keys. Previously,
4205 we wouldn't specify text mode or binary mode, leading to an
4206 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4207 the DirRecordUsageByCountry option which would have triggered
4208 the assertion failure was added), although this assertion failure
4209 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4210 - Selectively disable deprecation warnings on OS X because Lion
4211 started deprecating the shipped copy of openssl. Fixes bug 3643.
4212 - Remove an extra pair of quotation marks around the error
4213 message in control-port STATUS_GENERAL BUG events. Bugfix on
4214 0.1.2.6-alpha; fixes bug 3732.
4215 - When unable to format an address as a string, report its value
4216 as "???" rather than reusing the last formatted address. Bugfix
4219 o Code simplifications and refactoring:
4220 - Rewrite the listener-selection logic so that parsing which ports
4221 we want to listen on is now separate from binding to the ports
4225 - Building Tor with bufferevent support now requires Libevent
4226 2.0.13-stable or later. Previous versions of Libevent had bugs in
4227 SSL-related bufferevents and related issues that would make Tor
4228 work badly with bufferevents. Requiring 2.0.13-stable also allows
4229 Tor with bufferevents to take advantage of Libevent APIs
4230 introduced after 2.0.8-rc.
4233 Changes in version 0.2.2.32 - 2011-08-27
4234 The Tor 0.2.2 release series is dedicated to the memory of Andreas
4235 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
4236 a founder of the PETS community, a leader in our field, a mentor,
4237 and a friend. He left us with these words: "I had the possibility
4238 to contribute to this world that is not as it should be. I hope I
4239 could help in some areas to make the world a better place, and that
4240 I could also encourage other people to be engaged in improving the
4241 world. Please, stay engaged. This world needs you, your love, your
4242 initiative -- now I cannot be part of that anymore."
4244 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
4245 ready. More than two years in the making, this release features improved
4246 client performance and hidden service reliability, better compatibility
4247 for Android, correct behavior for bridges that listen on more than
4248 one address, more extensible and flexible directory object handling,
4249 better reporting of network statistics, improved code security, and
4250 many many other features and bugfixes.
4253 Changes in version 0.2.2.31-rc - 2011-08-17
4254 Tor 0.2.2.31-rc is the second and hopefully final release candidate
4255 for the Tor 0.2.2.x series.
4258 - Remove an extra pair of quotation marks around the error
4259 message in control-port STATUS_GENERAL BUG events. Bugfix on
4260 0.1.2.6-alpha; fixes bug 3732.
4261 - If we're configured to write our ControlPorts to disk, only write
4262 them after switching UID and creating the data directory. This way,
4263 we don't fail when starting up with a nonexistent DataDirectory
4264 and a ControlPortWriteToFile setting based on that directory. Fixes
4265 bug 3747; bugfix on Tor 0.2.2.26-beta.
4268 - Update to the August 2 2011 Maxmind GeoLite Country database.
4271 - Allow GETINFO fingerprint to return a fingerprint even when
4272 we have not yet built a router descriptor. Fixes bug 3577;
4273 bugfix on 0.2.0.1-alpha.
4274 - Write several files in text mode, on OSes that distinguish text
4275 mode from binary mode (namely, Windows). These files are:
4276 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4277 that collect those statistics; 'client_keys' and 'hostname' for
4278 hidden services that use authentication; and (in the tor-gencert
4279 utility) newly generated identity and signing keys. Previously,
4280 we wouldn't specify text mode or binary mode, leading to an
4281 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4282 the DirRecordUsageByCountry option which would have triggered
4283 the assertion failure was added), although this assertion failure
4284 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4285 - Selectively disable deprecation warnings on OS X because Lion
4286 started deprecating the shipped copy of openssl. Fixes bug 3643.
4287 - When unable to format an address as a string, report its value
4288 as "???" rather than reusing the last formatted address. Bugfix
4292 Changes in version 0.2.3.2-alpha - 2011-07-18
4293 Tor 0.2.3.2-alpha introduces two new experimental features:
4294 microdescriptors and pluggable transports. It also continues cleaning
4295 up a variety of recently introduced features.
4298 - Clients can now use microdescriptors instead of regular descriptors
4299 to build circuits. Microdescriptors are authority-generated
4300 summaries of regular descriptors' contents, designed to change
4301 very rarely (see proposal 158 for details). This feature is
4302 designed to save bandwidth, especially for clients on slow internet
4303 connections. It's off by default for now, since nearly no caches
4304 support it, but it will be on-by-default for clients in a future
4305 version. You can use the UseMicrodescriptors option to turn it on.
4306 - Tor clients using bridges can now be configured to use a separate
4307 'transport' proxy for each bridge. This approach helps to resist
4308 censorship by allowing bridges to use protocol obfuscation
4309 plugins. It implements part of proposal 180. Implements ticket 2841.
4310 - While we're trying to bootstrap, record how many TLS connections
4311 fail in each state, and report which states saw the most failures
4312 in response to any bootstrap failures. This feature may speed up
4313 diagnosis of censorship events. Implements ticket 3116.
4315 o Major bugfixes (on 0.2.3.1-alpha):
4316 - When configuring a large set of nodes in EntryNodes (as with
4317 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
4318 random subset to be guards, and choose them in random
4319 order. Fixes bug 2798.
4320 - Tor could crash when remembering a consensus in a non-used consensus
4321 flavor without having a current consensus set. Fixes bug 3361.
4322 - Comparing an unknown address to a microdescriptor's shortened exit
4323 policy would always give a "rejected" result. Fixes bug 3599.
4324 - Using microdescriptors as a client no longer prevents Tor from
4325 uploading and downloading hidden service descriptors. Fixes
4329 - Allow nameservers with IPv6 address. Resolves bug 2574.
4330 - Accept attempts to include a password authenticator in the
4331 handshake, as supported by SOCKS5. This handles SOCKS clients that
4332 don't know how to omit a password when authenticating. Resolves
4334 - When configuring a large set of nodes in EntryNodes, and there are
4335 enough of them listed as Guard so that we don't need to consider
4336 the non-guard entries, prefer the ones listed with the Guard flag.
4337 - Check for and recover from inconsistency in the microdescriptor
4338 cache. This will make it harder for us to accidentally free a
4339 microdescriptor without removing it from the appropriate data
4340 structures. Fixes issue 3135; issue noted by "wanoskarnet".
4341 - Log SSL state transitions at log level DEBUG, log domain
4342 HANDSHAKE. This can be useful for debugging censorship events.
4343 Implements ticket 3264.
4344 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
4345 implements ticket 3439.
4347 o Minor bugfixes (on 0.2.3.1-alpha):
4348 - Do not free all general-purpose regular descriptors just
4349 because microdescriptor use is enabled. Fixes bug 3113.
4350 - Correctly link libevent_openssl when --enable-static-libevent
4351 is passed to configure. Fixes bug 3118.
4352 - Bridges should not complain during their heartbeat log messages that
4353 they are unlisted in the consensus: that's more or less the point
4354 of being a bridge. Fixes bug 3183.
4355 - Report a SIGNAL event to controllers when acting on a delayed
4356 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
4357 event to the controller if we acted on a SIGNAL NEWNYM command
4358 immediately, and otherwise not report a SIGNAL event for the
4359 command at all. Fixes bug 3349.
4360 - Fix a crash when handling the SIGNAL controller command or
4361 reporting ERR-level status events with bufferevents enabled. Found
4362 by Robert Ransom. Fixes bug 3367.
4363 - Always ship the tor-fw-helper manpage in our release tarballs.
4364 Fixes bug 3389. Reported by Stephen Walker.
4365 - Fix a class of double-mark-for-close bugs when bufferevents
4366 are enabled. Fixes bug 3403.
4367 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
4368 - Add SIGNAL to the list returned by the 'GETINFO events/names'
4369 control-port command. Fixes part of bug 3465.
4370 - Prevent using negative indices during unit test runs when read_all()
4371 fails. Spotted by coverity.
4372 - Fix a rare memory leak when checking the nodelist without it being
4373 present. Found by coverity.
4374 - Only try to download a microdescriptor-flavored consensus from
4375 a directory cache that provides them.
4377 o Minor bugfixes (on 0.2.2.x and earlier):
4378 - Assert that hidden-service-related operations are not performed
4379 using single-hop circuits. Previously, Tor would assert that
4380 client-side streams are not attached to single-hop circuits,
4381 but not that other sensitive operations on the client and service
4382 side are not performed using single-hop circuits. Fixes bug 3332;
4384 - Don't publish a new relay descriptor when we reload our onion key,
4385 unless the onion key has actually changed. Fixes bug 3263 and
4386 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
4387 - Allow GETINFO fingerprint to return a fingerprint even when
4388 we have not yet built a router descriptor. Fixes bug 3577;
4389 bugfix on 0.2.0.1-alpha.
4390 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
4391 on 0.2.2.4-alpha; fixes bug 3427.
4393 o Code simplification and refactoring:
4394 - Use tor_sscanf() in place of scanf() in more places through the
4395 code. This makes us a little more locale-independent, and
4396 should help shut up code-analysis tools that can't tell
4397 a safe sscanf string from a dangerous one.
4398 - Use tt_assert(), not tor_assert(), for checking for test failures.
4399 This makes the unit tests more able to go on in the event that
4401 - Split connection_about_to_close() into separate functions for each
4405 - On Windows, we now define the _WIN32_WINNT macros only if they
4406 are not already defined. This lets the person building Tor decide,
4407 if they want, to require a later version of Windows.
4410 Changes in version 0.2.2.30-rc - 2011-07-07
4411 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
4412 series. It fixes a few smaller bugs, but generally appears stable.
4413 Please test it and let us know whether it is!
4416 - Send a SUCCEEDED stream event to the controller when a reverse
4417 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
4418 discovered by katmagic.
4419 - Always NUL-terminate the sun_path field of a sockaddr_un before
4420 passing it to the kernel. (Not a security issue: kernels are
4421 smart enough to reject bad sockaddr_uns.) Found by Coverity;
4422 CID #428. Bugfix on Tor 0.2.0.3-alpha.
4423 - Don't stack-allocate the list of supplementary GIDs when we're
4424 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4425 could take up to 256K, which is way too much stack. Found by
4426 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4427 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
4428 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
4429 fixes part of bug 3465.
4430 - Fix a memory leak when receiving a descriptor for a hidden
4431 service we didn't ask for. Found by Coverity; CID #30. Bugfix
4435 - Update to the July 1 2011 Maxmind GeoLite Country database.
4438 Changes in version 0.2.2.29-beta - 2011-06-20
4439 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
4440 have bridge lines in their torrc but don't want to use them; gets
4441 us closer to having the control socket feature working on Debian;
4442 and fixes a variety of smaller bugs.
4445 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
4446 When we changed the default behavior to "use bridges if any
4447 are listed in the torrc", we surprised users who had bridges
4448 in their torrc files but who didn't actually want to use them.
4449 Partial resolution for bug 3354.
4452 - Don't attach new streams to old rendezvous circuits after SIGNAL
4453 NEWNYM. Previously, we would keep using an existing rendezvous
4454 circuit if it remained open (i.e. if it were kept open by a
4455 long-lived stream, or if a new stream were attached to it before
4456 Tor could notice that it was old and no longer in use). Bugfix on
4457 0.1.1.15-rc; fixes bug 3375.
4460 - Fix a bug when using ControlSocketsGroupWritable with User. The
4461 directory's group would be checked against the current group, not
4462 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
4463 bugfix on 0.2.2.26-beta.
4464 - Make connection_printf_to_buf()'s behaviour sane. Its callers
4465 expect it to emit a CRLF iff the format string ends with CRLF;
4466 it actually emitted a CRLF iff (a) the format string ended with
4467 CRLF or (b) the resulting string was over 1023 characters long or
4468 (c) the format string did not end with CRLF *and* the resulting
4469 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
4470 fixes part of bug 3407.
4471 - Make send_control_event_impl()'s behaviour sane. Its callers
4472 expect it to always emit a CRLF at the end of the string; it
4473 might have emitted extra control characters as well. Bugfix on
4474 0.1.1.9-alpha; fixes another part of bug 3407.
4475 - Make crypto_rand_int() check the value of its input correctly.
4476 Previously, it accepted values up to UINT_MAX, but could return a
4477 negative number if given a value above INT_MAX+1. Found by George
4478 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
4479 - Avoid a segfault when reading a malformed circuit build state
4480 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
4482 - When asked about a DNS record type we don't support via a
4483 client DNSPort, reply with NOTIMPL rather than an empty
4484 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
4485 - Fix a rare memory leak during stats writing. Found by coverity.
4488 - Update to the June 1 2011 Maxmind GeoLite Country database.
4490 o Code simplifications and refactoring:
4491 - Remove some dead code as indicated by coverity.
4492 - Remove a few dead assignments during router parsing. Found by
4494 - Add some forgotten return value checks during unit tests. Found
4496 - Don't use 1-bit wide signed bit fields. Found by coverity.
4499 Changes in version 0.2.2.28-beta - 2011-06-04
4500 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
4501 fixed a big bug in whether relays stay in the consensus consistently,
4502 we moved closer to handling bridges and hidden services correctly,
4503 and we started the process of better handling the dreaded "my Vidalia
4504 died, and now my Tor demands a password when I try to reconnect to it"
4508 - Don't decide to make a new descriptor when receiving a HUP signal.
4509 This bug has caused a lot of 0.2.2.x relays to disappear from the
4510 consensus periodically. Fixes the most common case of triggering
4511 bug 1810; bugfix on 0.2.2.7-alpha.
4512 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
4513 - Don't try to build descriptors if "ORPort auto" is set and we
4514 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
4516 - Resolve a crash that occurred when setting BridgeRelay to 1 with
4517 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
4518 - Apply circuit timeouts to opened hidden-service-related circuits
4519 based on the correct start time. Previously, we would apply the
4520 circuit build timeout based on time since the circuit's creation;
4521 it was supposed to be applied based on time since the circuit
4522 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
4523 - Use the same circuit timeout for client-side introduction
4524 circuits as for other four-hop circuits, rather than the timeout
4525 for single-hop directory-fetch circuits; the shorter timeout may
4526 have been appropriate with the static circuit build timeout in
4527 0.2.1.x and earlier, but caused many hidden service access attempts
4528 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
4529 on 0.2.2.2-alpha; fixes another part of bug 1297.
4530 - In ticket 2511 we fixed a case where you could use an unconfigured
4531 bridge if you had configured it as a bridge the last time you ran
4532 Tor. Now fix another edge case: if you had configured it as a bridge
4533 but then switched to a different bridge via the controller, you
4534 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
4538 - Add an __OwningControllerProcess configuration option and a
4539 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
4540 that when it exits, Tor will shut down. Implements feature 3049.
4541 - If "UseBridges 1" is set and no bridges are configured, Tor will
4542 now refuse to build any circuits until some bridges are set.
4543 If "UseBridges auto" is set, Tor will use bridges if they are
4544 configured and we are not running as a server, but otherwise will
4545 make circuits as usual. The new default is "auto". Patch by anonym,
4546 so the Tails LiveCD can stop automatically revealing you as a Tor
4550 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4551 - Remove a trailing asterisk from "exit-policy/default" in the
4552 output of the control port command "GETINFO info/names". Bugfix
4554 - Use a wide type to hold sockets when built for 64-bit Windows builds.
4556 - Warn when the user configures two HiddenServiceDir lines that point
4557 to the same directory. Bugfix on 0.0.6 (the version introducing
4558 HiddenServiceDir); fixes bug 3289.
4559 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
4560 part of bug 2748; bugfix on 0.2.0.10-alpha.
4561 - Log malformed requests for rendezvous descriptors as protocol
4562 warnings, not warnings. Also, use a more informative log message
4563 in case someone sees it at log level warning without prior
4564 info-level messages. Fixes the other part of bug 2748; bugfix
4566 - Clear the table recording the time of the last request for each
4567 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
4568 Previously, we would clear our HS descriptor cache on SIGNAL
4569 NEWNYM, but if we had previously retrieved a descriptor (or tried
4570 to) from every directory responsible for it, we would refuse to
4571 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
4573 - Fix a log message that said "bits" while displaying a value in
4574 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
4576 - When checking for 1024-bit keys, check for 1024 bits, not 128
4577 bytes. This allows Tor to correctly discard keys of length 1017
4578 through 1023. Bugfix on 0.0.9pre5.
4581 - Relays now log the reason for publishing a new relay descriptor,
4582 so we have a better chance of hunting down instances of bug 1810.
4583 Resolves ticket 3252.
4584 - Revise most log messages that refer to nodes by nickname to
4585 instead use the "$key=nickname at address" format. This should be
4586 more useful, especially since nicknames are less and less likely
4587 to be unique. Resolves ticket 3045.
4588 - Log (at info level) when purging pieces of hidden-service-client
4589 state because of SIGNAL NEWNYM.
4592 - Remove undocumented option "-F" from tor-resolve: it hasn't done
4593 anything since 0.2.1.16-rc.
4596 Changes in version 0.2.2.27-beta - 2011-05-18
4597 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
4598 release, and also adds a few more general bugfixes.
4601 - Fix a crash bug when changing bridges in a running Tor process.
4602 Fixes bug 3213; bugfix on 0.2.2.26-beta.
4603 - When the controller configures a new bridge, don't wait 10 to 60
4604 seconds before trying to fetch its descriptor. Bugfix on
4605 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
4608 - Require that onion keys have exponent 65537 in microdescriptors too.
4609 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
4610 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
4611 Changed the limit to 512 characters by removing base64 newlines.
4612 Fixes bug 2752. Fix by Michael Yakubovich.
4613 - When a client starts or stops using bridges, never use a circuit
4614 that was built before the configuration change. This behavior could
4615 put at risk a user who uses bridges to ensure that her traffic
4616 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
4620 Changes in version 0.2.2.26-beta - 2011-05-17
4621 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
4622 also introduces a new "socksport auto" approach that should make it
4623 easier to run multiple Tors on the same system, and does a lot of
4624 cleanup to get us closer to a release candidate.
4626 o Security/privacy fixes:
4627 - Replace all potentially sensitive memory comparison operations
4628 with versions whose runtime does not depend on the data being
4629 compared. This will help resist a class of attacks where an
4630 adversary can use variations in timing information to learn
4631 sensitive data. Fix for one case of bug 3122. (Safe memcmp
4632 implementation by Robert Ransom based partially on code by DJB.)
4633 - When receiving a hidden service descriptor, check that it is for
4634 the hidden service we wanted. Previously, Tor would store any
4635 hidden service descriptors that a directory gave it, whether it
4636 wanted them or not. This wouldn't have let an attacker impersonate
4637 a hidden service, but it did let directories pre-seed a client
4638 with descriptors that it didn't want. Bugfix on 0.0.6.
4639 - On SIGHUP, do not clear out all TrackHostExits mappings, client
4640 DNS cache entries, and virtual address mappings: that's what
4641 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
4644 - The options SocksPort, ControlPort, and so on now all accept a
4645 value "auto" that opens a socket on an OS-selected port. A
4646 new ControlPortWriteToFile option tells Tor to write its
4647 actual control port or ports to a chosen file. If the option
4648 ControlPortFileGroupReadable is set, the file is created as
4649 group-readable. Now users can run two Tor clients on the same
4650 system without needing to manually mess with parameters. Resolves
4651 part of ticket 3076.
4652 - Set SO_REUSEADDR on all sockets, not just listeners. This should
4653 help busy exit nodes avoid running out of useable ports just
4654 because all the ports have been used in the near past. Resolves
4658 - New "GETINFO net/listeners/(type)" controller command to return
4659 a list of addresses and ports that are bound for listeners for a
4660 given connection type. This is useful when the user has configured
4661 "SocksPort auto" and the controller needs to know which port got
4662 chosen. Resolves another part of ticket 3076.
4663 - Add a new ControlSocketsGroupWritable configuration option: when
4664 it is turned on, ControlSockets are group-writeable by the default
4665 group of the current user. Patch by Jérémy Bobbio; implements
4667 - Tor now refuses to create a ControlSocket in a directory that is
4668 world-readable (or group-readable if ControlSocketsGroupWritable
4669 is 0). This is necessary because some operating systems do not
4670 enforce permissions on an AF_UNIX sockets. Permissions on the
4671 directory holding the socket, however, seems to work everywhere.
4672 - Rate-limit a warning about failures to download v2 networkstatus
4673 documents. Resolves part of bug 1352.
4674 - Backport code from 0.2.3.x that allows directory authorities to
4675 clean their microdescriptor caches. Needed to resolve bug 2230.
4676 - When an HTTPS proxy reports "403 Forbidden", we now explain
4677 what it means rather than calling it an unexpected status code.
4678 Closes bug 2503. Patch from Michael Yakubovich.
4679 - Update to the May 1 2011 Maxmind GeoLite Country database.
4682 - Authorities now clean their microdesc cache periodically and when
4683 reading from disk initially, not only when adding new descriptors.
4684 This prevents a bug where we could lose microdescriptors. Bugfix
4685 on 0.2.2.6-alpha. Fixes bug 2230.
4686 - Do not crash when our configuration file becomes unreadable, for
4687 example due to a permissions change, between when we start up
4688 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
4690 - Avoid a bug that would keep us from replacing a microdescriptor
4691 cache on Windows. (We would try to replace the file while still
4692 holding it open. That's fine on Unix, but Windows doesn't let us
4693 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
4694 - Add missing explanations for the authority-related torrc options
4695 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
4696 man page. Resolves issue 2379.
4697 - As an authority, do not upload our own vote or signature set to
4698 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
4699 it would get flagged as a duplicate. Resolves bug 3026.
4700 - Accept hidden service descriptors if we think we might be a hidden
4701 service directory, regardless of what our consensus says. This
4702 helps robustness, since clients and hidden services can sometimes
4703 have a more up-to-date view of the network consensus than we do,
4704 and if they think that the directory authorities list us a HSDir,
4705 we might actually be one. Related to bug 2732; bugfix on
4707 - When a controller changes TrackHostExits, remove mappings for
4708 hosts that should no longer have their exits tracked. Bugfix on
4710 - When a controller changes VirtualAddrNetwork, remove any mappings
4711 for hosts that were automapped to the old network. Bugfix on
4713 - When a controller changes one of the AutomapHosts* options, remove
4714 any mappings for hosts that should no longer be automapped. Bugfix
4716 - Do not reset the bridge descriptor download status every time we
4717 re-parse our configuration or get a configuration change. Fixes
4718 bug 3019; bugfix on 0.2.0.3-alpha.
4720 o Minor bugfixes (code cleanup):
4721 - When loading the microdesc journal, remember its current size.
4722 In 0.2.2, this helps prevent the microdesc journal from growing
4723 without limit on authorities (who are the only ones to use it in
4724 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
4725 Fix posted by "cypherpunks."
4726 - The microdesc journal is supposed to get rebuilt only if it is
4727 at least _half_ the length of the store, not _twice_ the length
4728 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
4729 - Fix a potential null-pointer dereference while computing a
4730 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
4732 - Avoid a possible null-pointer dereference when rebuilding the mdesc
4733 cache without actually having any descriptors to cache. Bugfix on
4734 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
4735 - If we fail to compute the identity digest of a v3 legacy keypair,
4736 warn, and don't use a buffer-full of junk instead. Bugfix on
4737 0.2.1.1-alpha; fixes bug 3106.
4738 - Resolve an untriggerable issue in smartlist_string_num_isin(),
4739 where if the function had ever in the future been used to check
4740 for the presence of a too-large number, it would have given an
4741 incorrect result. (Fortunately, we only used it for 16-bit
4742 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
4743 - Require that introduction point keys and onion handshake keys
4744 have a public exponent of 65537. Starts to fix bug 3207; bugfix
4748 - Caches no longer download and serve v2 networkstatus documents
4749 unless FetchV2Networkstatus flag is set: these documents haven't
4750 haven't been used by clients or relays since 0.2.0.x. Resolves
4754 Changes in version 0.2.3.1-alpha - 2011-05-05
4755 Tor 0.2.3.1-alpha adds some new experimental features, including support
4756 for an improved network IO backend, IOCP networking on Windows,
4757 microdescriptor caching, "fast-start" support for streams, and automatic
4758 home router configuration. There are also numerous internal improvements
4759 to try to make the code easier for developers to work with.
4761 This is the first alpha release in a new series, so expect there to be
4762 bugs. Users who would rather test out a more stable branch should
4763 stay with 0.2.2.x for now.
4766 - Tor can now optionally build with the "bufferevents" buffered IO
4767 backend provided by Libevent 2. To use this feature, make sure you
4768 have the latest possible version of Libevent, and pass the
4769 --enable-bufferevents flag to configure when building Tor from
4770 source. This feature will make our networking code more flexible,
4771 let us stack layers on each other, and let us use more efficient
4772 zero-copy transports where available.
4773 - As an experimental feature, Tor can use IOCP for networking on Windows.
4774 Once this code is tuned and optimized, it promises much better
4775 performance than the select-based backend we've used in the past. To
4776 try this feature, you must build Tor with Libevent 2, configure Tor
4777 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
4778 your torrc. There are known bugs here: only try this if you can help
4779 debug it as it breaks.
4780 - The EntryNodes option can now include country codes like {de} or IP
4781 addresses or network masks. Previously we had disallowed these options
4782 because we didn't have an efficient way to keep the list up to
4783 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
4784 - Exit nodes now accept and queue data on not-yet-connected streams.
4785 Previously, the client wasn't allowed to send data until the stream was
4786 connected, which slowed down all connections. This change will enable
4787 clients to perform a "fast-start" on streams and send data without
4788 having to wait for a confirmation that the stream has opened. (Patch
4789 from Ian Goldberg; implements the server side of Proposal 174.)
4790 - Tor now has initial support for automatic port mapping on the many
4791 home routers that support NAT-PMP or UPnP. (Not yet supported on
4792 Windows). To build the support code, you'll need to have libnatpnp
4793 library and/or the libminiupnpc library, and you'll need to enable the
4794 feature specifically by passing "--enable-upnp" and/or
4795 "--enable-natpnp" to configure. To turn it on, use the new
4796 PortForwarding option.
4797 - Caches now download, cache, and serve multiple "flavors" of the
4798 consensus, including a flavor that describes microdescriptors.
4799 - Caches now download, cache, and serve microdescriptors -- small
4800 summaries of router descriptors that are authenticated by all of the
4801 directory authorities. Once enough caches are running this code,
4802 clients will be able to save significant amounts of directory bandwidth
4803 by downloading microdescriptors instead of router descriptors.
4806 - Make logging resolution configurable with a new LogTimeGranularity
4807 option, and change the default from 1 millisecond to 1 second.
4808 Implements enhancement 1668.
4809 - We log which torrc file we're using on startup. Implements ticket
4811 - Ordinarily, Tor does not count traffic from private addresses (like
4812 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
4813 There is now a new option, CountPrivateBandwidth, to disable this
4814 behavior. Patch from Daniel Cagara.
4815 - New --enable-static-tor configure option for building Tor as
4816 statically as possible. Idea, general hackery and thoughts from
4817 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
4819 - If you set the NumCPUs option to 0, Tor will now try to detect how
4820 many CPUs you have. This is the new default behavior.
4821 - Turn on directory request statistics by default and include them in
4822 extra-info descriptors. Don't break if we have no GeoIP database.
4823 - Relays that set "ConnDirectionStatistics 1" write statistics on the
4824 bidirectional use of connections to disk every 24 hours.
4825 - Add a GeoIP file digest to the extra-info descriptor. Implements
4827 - The NodeFamily option -- which let you declare that you want to
4828 consider nodes to be part of a family whether they list themselves
4829 that way or not -- now allows IP address ranges and country codes.
4830 - Add a new 'Heartbeat' log message type to periodically log a message
4831 describing Tor's status at level Notice. This feature is meant for
4832 operators who log at notice, and want to make sure that their Tor
4833 server is still working. Implementation by George Kadianakis.
4835 o Minor bugfixes (on 0.2.2.25-alpha):
4836 - When loading the microdesc journal, remember its current size.
4837 In 0.2.2, this helps prevent the microdesc journal from growing
4838 without limit on authorities (who are the only ones to use it in
4839 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
4840 Fix posted by "cypherpunks."
4841 - The microdesc journal is supposed to get rebuilt only if it is
4842 at least _half_ the length of the store, not _twice_ the length
4843 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
4844 - If as an authority we fail to compute the identity digest of a v3
4845 legacy keypair, warn, and don't use a buffer-full of junk instead.
4846 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
4847 - Authorities now clean their microdesc cache periodically and when
4848 reading from disk initially, not only when adding new descriptors.
4849 This prevents a bug where we could lose microdescriptors. Bugfix
4852 o Minor features (controller):
4853 - Add a new SIGNAL event to the controller interface so that
4854 controllers can be notified when Tor handles a signal. Resolves
4855 issue 1955. Patch by John Brooks.
4856 - Add a new GETINFO option to get total bytes read and written. Patch
4857 from pipe, revised by atagar. Resolves ticket 2345.
4858 - Implement some GETINFO controller fields to provide information about
4859 the Tor process's pid, euid, username, and resource limits.
4862 - Our build system requires automake 1.6 or later to create the
4863 Makefile.in files. Previously, you could have used 1.4.
4864 This only affects developers and people building Tor from git;
4865 people who build Tor from the source distribution without changing
4866 the Makefile.am files should be fine.
4867 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
4868 so on. This is more robust against some of the failure modes
4869 associated with running the autotools pieces on their own.
4871 o Minor packaging issues:
4872 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
4873 already created. Patch from Andreas Stieger. Fixes bug 2573.
4875 o Code simplifications and refactoring:
4876 - A major revision to our internal node-selecting and listing logic.
4877 Tor already had at least two major ways to look at the question of
4878 "which Tor servers do we know about": a list of router descriptors,
4879 and a list of entries in the current consensus. With
4880 microdescriptors, we're adding a third. Having so many systems
4881 without an abstraction layer over them was hurting the codebase.
4882 Now, we have a new "node_t" abstraction that presents a consistent
4883 interface to a client's view of a Tor node, and holds (nearly) all
4884 of the mutable state formerly in routerinfo_t and routerstatus_t.
4885 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
4886 no longer link against Libevent: they never used it, but
4887 our library structure used to force them to link it.
4890 - Remove some old code to work around even older versions of Tor that
4891 used forked processes to handle DNS requests. Such versions of Tor
4892 are no longer in use as servers.
4894 o Documentation fixes:
4895 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
4896 - Add missing documentation for the authority-related torrc options
4897 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
4901 Changes in version 0.2.2.25-alpha - 2011-04-29
4902 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
4903 robust, routers no longer overreport their bandwidth, Win7 should crash
4904 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
4905 now prevents hidden service-related activity from being linkable. It
4906 provides more information to Vidalia so you can see if your bridge is
4907 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
4908 StrictNodes configuration options to make them more reliable, more
4909 understandable, and more regularly applied. If you use those options,
4910 please see the revised documentation for them in the manual page.
4913 - Relays were publishing grossly inflated bandwidth values because
4914 they were writing their state files wrong--now they write the
4915 correct value. Also, resume reading bandwidth history from the
4916 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
4917 - Improve hidden service robustness: When we find that we have
4918 extended a hidden service's introduction circuit to a relay not
4919 listed as an introduction point in the HS descriptor we currently
4920 have, retry with an introduction point from the current
4921 descriptor. Previously we would just give up. Fixes bugs 1024 and
4922 1930; bugfix on 0.2.0.10-alpha.
4923 - Clients now stop trying to use an exit node associated with a given
4924 destination by TrackHostExits if they fail to reach that exit node.
4925 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
4926 - Fix crash bug on platforms where gmtime and localtime can return
4927 NULL. Windows 7 users were running into this one. Fixes part of bug
4928 2077. Bugfix on all versions of Tor. Found by boboper.
4930 o Security and stability fixes:
4931 - Don't double-free a parsable, but invalid, microdescriptor, even if
4932 it is followed in the blob we're parsing by an unparsable
4933 microdescriptor. Fixes an issue reported in a comment on bug 2954.
4934 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
4935 - If the Nickname configuration option isn't given, Tor would pick a
4936 nickname based on the local hostname as the nickname for a relay.
4937 Because nicknames are not very important in today's Tor and the
4938 "Unnamed" nickname has been implemented, this is now problematic
4939 behavior: It leaks information about the hostname without being
4940 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
4941 introduced the Unnamed nickname. Reported by tagnaq.
4942 - Fix an uncommon assertion failure when running with DNSPort under
4943 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
4944 - Avoid linkability based on cached hidden service descriptors: forget
4945 all hidden service descriptors cached as a client when processing a
4946 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
4949 - Export GeoIP information on bridge usage to controllers even if we
4950 have not yet been running for 24 hours. Now Vidalia bridge operators
4951 can get more accurate and immediate feedback about their
4952 contributions to the network.
4954 o Major features and bugfixes (node selection):
4955 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
4956 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
4957 options. Previously, we had been ambiguous in describing what
4958 counted as an "exit" node, and what operations exactly "StrictNodes
4959 0" would permit. This created confusion when people saw nodes built
4960 through unexpected circuits, and made it hard to tell real bugs from
4961 surprises. Now the intended behavior is:
4962 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
4963 a node that delivers user traffic outside the Tor network.
4964 . "Entry", in the context of EntryNodes, means a node used as the
4965 first hop of a multihop circuit. It doesn't include direct
4966 connections to directory servers.
4967 . "ExcludeNodes" applies to all nodes.
4968 . "StrictNodes" changes the behavior of ExcludeNodes only. When
4969 StrictNodes is set, Tor should avoid all nodes listed in
4970 ExcludeNodes, even when it will make user requests fail. When
4971 StrictNodes is *not* set, then Tor should follow ExcludeNodes
4972 whenever it can, except when it must use an excluded node to
4973 perform self-tests, connect to a hidden service, provide a
4974 hidden service, fulfill a .exit request, upload directory
4975 information, or fetch directory information.
4976 Collectively, the changes to implement the behavior fix bug 1090.
4977 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
4978 a node is listed in both, it's treated as excluded.
4979 - ExcludeNodes now applies to directory nodes -- as a preference if
4980 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
4981 Don't exclude all the directory authorities and set StrictNodes to 1
4982 unless you really want your Tor to break.
4983 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
4984 - ExcludeExitNodes now overrides .exit requests.
4985 - We don't use bridges listed in ExcludeNodes.
4986 - When StrictNodes is 1:
4987 . We now apply ExcludeNodes to hidden service introduction points
4988 and to rendezvous points selected by hidden service users. This
4989 can make your hidden service less reliable: use it with caution!
4990 . If we have used ExcludeNodes on ourself, do not try relay
4991 reachability self-tests.
4992 . If we have excluded all the directory authorities, we will not
4993 even try to upload our descriptor if we're a relay.
4994 . Do not honor .exit requests to an excluded node.
4995 - Remove a misfeature that caused us to ignore the Fast/Stable flags
4996 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
4997 - When the set of permitted nodes changes, we now remove any mappings
4998 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
5000 - We never cannibalize a circuit that had excluded nodes on it, even
5001 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
5002 - Revert a change where we would be laxer about attaching streams to
5003 circuits than when building the circuits. This was meant to prevent
5004 a set of bugs where streams were never attachable, but our improved
5005 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
5006 - Keep track of how many times we launch a new circuit to handle a
5007 given stream. Too many launches could indicate an inconsistency
5008 between our "launch a circuit to handle this stream" logic and our
5009 "attach this stream to one of the available circuits" logic.
5010 - Improve log messages related to excluded nodes.
5013 - Fix a spurious warning when moving from a short month to a long
5014 month on relays with month-based BandwidthAccounting. Bugfix on
5015 0.2.2.17-alpha; fixes bug 3020.
5016 - When a client finds that an origin circuit has run out of 16-bit
5017 stream IDs, we now mark it as unusable for new streams. Previously,
5018 we would try to close the entire circuit. Bugfix on 0.0.6.
5019 - Add a forgotten cast that caused a compile warning on OS X 10.6.
5020 Bugfix on 0.2.2.24-alpha.
5021 - Be more careful about reporting the correct error from a failed
5022 connect() system call. Under some circumstances, it was possible to
5023 look at an incorrect value for errno when sending the end reason.
5024 Bugfix on 0.1.0.1-rc.
5025 - Correctly handle an "impossible" overflow cases in connection byte
5026 counting, where we write or read more than 4GB on an edge connection
5027 in a single second. Bugfix on 0.1.2.8-beta.
5028 - Correct the warning displayed when a rendezvous descriptor exceeds
5029 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
5031 - Clients and hidden services now use HSDir-flagged relays for hidden
5032 service descriptor downloads and uploads even if the relays have no
5033 DirPort set and the client has disabled TunnelDirConns. This will
5034 eventually allow us to give the HSDir flag to relays with no
5035 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
5036 - Downgrade "no current certificates known for authority" message from
5037 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
5038 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
5039 2917. Bugfix on 0.1.1.1-alpha.
5040 - Only limit the lengths of single HS descriptors, even when multiple
5041 HS descriptors are published to an HSDir relay in a single POST
5042 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
5043 - Write the current time into the LastWritten line in our state file,
5044 rather than the time from the previous write attempt. Also, stop
5045 trying to use a time of -1 in our log statements. Fixes bug 3039;
5046 bugfix on 0.2.2.14-alpha.
5047 - Be more consistent in our treatment of file system paths. "~" should
5048 get expanded to the user's home directory in the Log config option.
5049 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
5050 feature for the -f and --DataDirectory options.
5053 - Make sure every relay writes a state file at least every 12 hours.
5054 Previously, a relay could go for weeks without writing its state
5055 file, and on a crash could lose its bandwidth history, capacity
5056 estimates, client country statistics, and so on. Addresses bug 3012.
5057 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
5058 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
5059 clients are already deprecated because of security bugs.
5060 - Don't allow v0 hidden service authorities to act as clients.
5061 Required by fix for bug 3000.
5062 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
5063 by fix for bug 3000.
5064 - Ensure that no empty [dirreq-](read|write)-history lines are added
5065 to an extrainfo document. Implements ticket 2497.
5067 o Code simplification and refactoring:
5068 - Remove workaround code to handle directory responses from servers
5069 that had bug 539 (they would send HTTP status 503 responses _and_
5070 send a body too). Since only server versions before
5071 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
5072 keep the workaround in place.
5073 - Remove the old 'fuzzy time' logic. It was supposed to be used for
5074 handling calculations where we have a known amount of clock skew and
5075 an allowed amount of unknown skew. But we only used it in three
5076 places, and we never adjusted the known/unknown skew values. This is
5077 still something we might want to do someday, but if we do, we'll
5078 want to do it differently.
5079 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
5080 None of the cases where we did this before were wrong, but by making
5081 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
5082 - Use GetTempDir to find the proper temporary directory location on
5083 Windows when generating temporary files for the unit tests. Patch by
5087 Changes in version 0.2.2.24-alpha - 2011-04-08
5088 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
5089 prevented Tor clients from effectively using "multihomed" bridges,
5090 that is, bridges that listen on multiple ports or IP addresses so users
5091 can continue to use some of their addresses even if others get blocked.
5094 - Fix a bug where bridge users who configure the non-canonical
5095 address of a bridge automatically switch to its canonical
5096 address. If a bridge listens at more than one address, it should be
5097 able to advertise those addresses independently and any non-blocked
5098 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
5100 - If you configured Tor to use bridge A, and then quit and
5101 configured Tor to use bridge B instead, it would happily continue
5102 to use bridge A if it's still reachable. While this behavior is
5103 a feature if your goal is connectivity, in some scenarios it's a
5104 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
5105 - Directory authorities now use data collected from their own
5106 uptime observations when choosing whether to assign the HSDir flag
5107 to relays, instead of trusting the uptime value the relay reports in
5108 its descriptor. This change helps prevent an attack where a small
5109 set of nodes with frequently-changing identity keys can blackhole
5110 a hidden service. (Only authorities need upgrade; others will be
5111 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
5114 - When we restart our relay, we might get a successful connection
5115 from the outside before we've started our reachability tests,
5116 triggering a warning: "ORPort found reachable, but I have no
5117 routerinfo yet. Failing to inform controller of success." This
5118 bug was harmless unless Tor is running under a controller
5119 like Vidalia, in which case the controller would never get a
5120 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
5122 - Make directory authorities more accurate at recording when
5123 relays that have failed several reachability tests became
5124 unreachable, so we can provide more accuracy at assigning Stable,
5125 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
5126 - Fix an issue that prevented static linking of libevent on
5127 some platforms (notably Linux). Fixes bug 2698; bugfix on
5128 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
5129 the --with-static-libevent configure option).
5130 - We now ask the other side of a stream (the client or the exit)
5131 for more data on that stream when the amount of queued data on
5132 that stream dips low enough. Previously, we wouldn't ask the
5133 other side for more data until either it sent us more data (which
5134 it wasn't supposed to do if it had exhausted its window!) or we
5135 had completely flushed all our queued data. This flow control fix
5136 should improve throughput. Fixes bug 2756; bugfix on the earliest
5137 released versions of Tor (svn commit r152).
5138 - Avoid a double-mark-for-free warning when failing to attach a
5139 transparent proxy connection. (We thought we had fixed this in
5140 0.2.2.23-alpha, but it turns out our fix was checking the wrong
5141 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
5142 bug) and 0.2.2.23-alpha (the incorrect fix).
5143 - When warning about missing zlib development packages during compile,
5144 give the correct package names. Bugfix on 0.2.0.1-alpha.
5147 - Directory authorities now log the source of a rejected POSTed v3
5149 - Make compilation with clang possible when using
5150 --enable-gcc-warnings by removing two warning options that clang
5151 hasn't implemented yet and by fixing a few warnings. Implements
5153 - When expiring circuits, use microsecond timers rather than
5154 one-second timers. This can avoid an unpleasant situation where a
5155 circuit is launched near the end of one second and expired right
5156 near the beginning of the next, and prevent fluctuations in circuit
5158 - Use computed circuit-build timeouts to decide when to launch
5159 parallel introduction circuits for hidden services. (Previously,
5160 we would retry after 15 seconds.)
5161 - Update to the April 1 2011 Maxmind GeoLite Country database.
5164 - Create the /var/run/tor directory on startup on OpenSUSE if it is
5165 not already created. Patch from Andreas Stieger. Fixes bug 2573.
5167 o Documentation changes:
5168 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
5169 - Resolve all doxygen warnings except those for missing documentation.
5171 - Add doxygen documentation for more functions, fields, and types.
5174 Changes in version 0.2.2.23-alpha - 2011-03-08
5175 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
5176 they restart they don't lose their bandwidth capacity estimate. This
5177 release also fixes a diverse set of user-facing bugs, ranging from
5178 relays overrunning their rate limiting to clients falsely warning about
5179 clock skew to bridge descriptor leaks by our bridge directory authority.
5182 - Stop sending a CLOCK_SKEW controller status event whenever
5183 we fetch directory information from a relay that has a wrong clock.
5184 Instead, only inform the controller when it's a trusted authority
5185 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5186 the rest of bug 1074.
5187 - Fix an assert in parsing router descriptors containing IPv6
5188 addresses. This one took down the directory authorities when
5189 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
5190 - Make the bridge directory authority refuse to answer directory
5191 requests for "all" descriptors. It used to include bridge
5192 descriptors in its answer, which was a major information leak.
5193 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
5194 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5195 Tor would ignore their RelayBandwidthBurst setting,
5196 potentially using more bandwidth than expected. Bugfix on
5197 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5198 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5199 hidserv" in her torrc. The 'hidserv' argument never controlled
5200 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5203 - Relays now save observed peak bandwidth throughput rates to their
5204 state file (along with total usage, which was already saved)
5205 so that they can determine their correct estimated bandwidth on
5206 restart. Resolves bug 1863, where Tor relays would reset their
5207 estimated bandwidth to 0 after restarting.
5208 - Directory authorities now take changes in router IP address and
5209 ORPort into account when determining router stability. Previously,
5210 if a router changed its IP or ORPort, the authorities would not
5211 treat it as having any downtime for the purposes of stability
5212 calculation, whereas clients would experience downtime since the
5213 change could take a while to propagate to them. Resolves issue 1035.
5214 - Enable Address Space Layout Randomization (ASLR) and Data Execution
5215 Prevention (DEP) by default on Windows to make it harder for
5216 attackers to exploit vulnerabilities. Patch from John Brooks.
5218 o Minor bugfixes (on 0.2.1.x and earlier):
5219 - Fix a rare crash bug that could occur when a client was configured
5220 with a large number of bridges. Fixes bug 2629; bugfix on
5221 0.2.1.2-alpha. Bugfix by trac user "shitlei".
5222 - Avoid a double mark-for-free warning when failing to attach a
5223 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
5225 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
5226 found by "cypherpunks". This bug was introduced before the first
5227 Tor release, in svn commit r110.
5228 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
5229 don't mention them in the manpage. Fixes bug 2450; issue
5230 spotted by keb and G-Lo.
5231 - Fix a bug in bandwidth history state parsing that could have been
5232 triggered if a future version of Tor ever changed the timing
5233 granularity at which bandwidth history is measured. Bugfix on
5235 - When a relay decides that its DNS is too broken for it to serve
5236 as an exit server, it advertised itself as a non-exit, but
5237 continued to act as an exit. This could create accidental
5238 partitioning opportunities for users. Instead, if a relay is
5239 going to advertise reject *:* as its exit policy, it should
5240 really act with exit policy "reject *:*". Fixes bug 2366.
5241 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
5242 - In the special case where you configure a public exit relay as your
5243 bridge, Tor would be willing to use that exit relay as the last
5244 hop in your circuit as well. Now we fail that circuit instead.
5245 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
5246 - Fix a bug with our locking implementation on Windows that couldn't
5247 correctly detect when a file was already locked. Fixes bug 2504,
5248 bugfix on 0.2.1.6-alpha.
5249 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
5250 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
5252 - Set target port in get_interface_address6() correctly. Bugfix
5253 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
5254 - Directory authorities are now more robust to hops back in time
5255 when calculating router stability. Previously, if a run of uptime
5256 or downtime appeared to be negative, the calculation could give
5257 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
5259 - Fix an assert that got triggered when using the TestingTorNetwork
5260 configuration option and then issuing a GETINFO config-text control
5261 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
5263 o Minor bugfixes (on 0.2.2.x):
5264 - Clients should not weight BadExit nodes as Exits in their node
5265 selection. Similarly, directory authorities should not count BadExit
5266 bandwidth as Exit bandwidth when computing bandwidth-weights.
5267 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
5268 - Correctly clear our dir_read/dir_write history when there is an
5269 error parsing any bw history value from the state file. Bugfix on
5271 - Resolve a bug in verifying signatures of directory objects
5272 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
5273 Fixes bug 2409. Found by "piebeer".
5274 - Bridge authorities no longer crash on SIGHUP when they try to
5275 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
5279 - Log less aggressively about circuit timeout changes, and improve
5280 some other circuit timeout messages. Resolves bug 2004.
5281 - Log a little more clearly about the times at which we're no longer
5282 accepting new connections. Resolves bug 2181.
5283 - Reject attempts at the client side to open connections to private
5284 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
5285 a randomly chosen exit node. Attempts to do so are always
5286 ill-defined, generally prevented by exit policies, and usually
5287 in error. This will also help to detect loops in transparent
5288 proxy configurations. You can disable this feature by setting
5289 "ClientRejectInternalAddresses 0" in your torrc.
5290 - Always treat failure to allocate an RSA key as an unrecoverable
5292 - Update to the March 1 2011 Maxmind GeoLite Country database.
5294 o Minor features (log subsystem):
5295 - Add documentation for configuring logging at different severities in
5296 different log domains. We've had this feature since 0.2.1.1-alpha,
5297 but for some reason it never made it into the manpage. Fixes
5299 - Make it simpler to specify "All log domains except for A and B".
5300 Previously you needed to say "[*,~A,~B]". Now you can just say
5302 - Add a "LogMessageDomains 1" option to include the domains of log
5303 messages along with the messages. Without this, there's no way
5304 to use log domains without reading the source or doing a lot
5307 o Packaging changes:
5308 - Stop shipping the Tor specs files and development proposal documents
5309 in the tarball. They are now in a separate git repository at
5310 git://git.torproject.org/torspec.git
5313 Changes in version 0.2.1.30 - 2011-02-23
5314 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
5315 change is a slight tweak to Tor's TLS handshake that makes relays
5316 and bridges that run this new version reachable from Iran again.
5317 We don't expect this tweak will win the arms race long-term, but it
5318 buys us time until we roll out a better solution.
5321 - Stop sending a CLOCK_SKEW controller status event whenever
5322 we fetch directory information from a relay that has a wrong clock.
5323 Instead, only inform the controller when it's a trusted authority
5324 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5325 the rest of bug 1074.
5326 - Fix a bounds-checking error that could allow an attacker to
5327 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5329 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5330 Tor would ignore their RelayBandwidthBurst setting,
5331 potentially using more bandwidth than expected. Bugfix on
5332 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5333 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5334 hidserv" in her torrc. The 'hidserv' argument never controlled
5335 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5338 - Adjust our TLS Diffie-Hellman parameters to match those used by
5340 - Update to the February 1 2011 Maxmind GeoLite Country database.
5343 - Check for and reject overly long directory certificates and
5344 directory tokens before they have a chance to hit any assertions.
5345 Bugfix on 0.2.1.28. Found by "doorss".
5346 - Bring the logic that gathers routerinfos and assesses the
5347 acceptability of circuits into line. This prevents a Tor OP from
5348 getting locked in a cycle of choosing its local OR as an exit for a
5349 path (due to a .exit request) and then rejecting the circuit because
5350 its OR is not listed yet. It also prevents Tor clients from using an
5351 OR running in the same instance as an exit (due to a .exit request)
5352 if the OR does not meet the same requirements expected of an OR
5353 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5355 o Packaging changes:
5356 - Stop shipping the Tor specs files and development proposal documents
5357 in the tarball. They are now in a separate git repository at
5358 git://git.torproject.org/torspec.git
5359 - Do not include Git version tags as though they are SVN tags when
5360 generating a tarball from inside a repository that has switched
5361 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
5364 Changes in version 0.2.2.22-alpha - 2011-01-25
5365 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
5366 main other change is a slight tweak to Tor's TLS handshake that makes
5367 relays and bridges that run this new version reachable from Iran again.
5368 We don't expect this tweak will win the arms race long-term, but it
5369 will buy us a bit more time until we roll out a better solution.
5372 - Fix a bounds-checking error that could allow an attacker to
5373 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5375 - Don't assert when changing from bridge to relay or vice versa
5376 via the controller. The assert happened because we didn't properly
5377 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
5378 bug 2433. Reported by bastik.
5381 - Adjust our TLS Diffie-Hellman parameters to match those used by
5383 - Provide a log message stating which geoip file we're parsing
5384 instead of just stating that we're parsing the geoip file.
5385 Implements ticket 2432.
5388 - Check for and reject overly long directory certificates and
5389 directory tokens before they have a chance to hit any assertions.
5390 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
5393 Changes in version 0.2.2.21-alpha - 2011-01-15
5394 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
5395 continues our recent code security audit work. The main fix resolves
5396 a remote heap overflow vulnerability that can allow remote code
5397 execution (CVE-2011-0427). Other fixes address a variety of assert
5398 and crash bugs, most of which we think are hard to exploit remotely.
5400 o Major bugfixes (security), also included in 0.2.1.29:
5401 - Fix a heap overflow bug where an adversary could cause heap
5402 corruption. This bug probably allows remote code execution
5403 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5405 - Prevent a denial-of-service attack by disallowing any
5406 zlib-compressed data whose compression factor is implausibly
5407 high. Fixes part of bug 2324; reported by "doorss".
5408 - Zero out a few more keys in memory before freeing them. Fixes
5409 bug 2384 and part of bug 2385. These key instances found by
5410 "cypherpunks", based on Andrew Case's report about being able
5411 to find sensitive data in Tor's memory space if you have enough
5412 permissions. Bugfix on 0.0.2pre9.
5414 o Major bugfixes (crashes), also included in 0.2.1.29:
5415 - Prevent calls to Libevent from inside Libevent log handlers.
5416 This had potential to cause a nasty set of crashes, especially
5417 if running Libevent with debug logging enabled, and running
5418 Tor with a controller watching for low-severity log messages.
5419 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5420 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5421 underflow errors there too. Fixes the other part of bug 2324.
5422 - Fix a bug where we would assert if we ever had a
5423 cached-descriptors.new file (or another file read directly into
5424 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5425 on 0.2.1.25. Found by doorss.
5426 - Fix some potential asserts and parsing issues with grossly
5427 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5430 o Minor bugfixes (other), also included in 0.2.1.29:
5431 - Fix a bug with handling misformed replies to reverse DNS lookup
5432 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5433 bug reported by doorss.
5434 - Fix compilation on mingw when a pthreads compatibility library
5435 has been installed. (We don't want to use it, so we shouldn't
5436 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5437 - Fix a bug where we would declare that we had run out of virtual
5438 addresses when the address space was only half-exhausted. Bugfix
5440 - Correctly handle the case where AutomapHostsOnResolve is set but
5441 no virtual addresses are available. Fixes bug 2328; bugfix on
5442 0.1.2.1-alpha. Bug found by doorss.
5443 - Correctly handle wrapping around when we run out of virtual
5444 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
5446 o Minor features, also included in 0.2.1.29:
5447 - Update to the January 1 2011 Maxmind GeoLite Country database.
5448 - Introduce output size checks on all of our decryption functions.
5450 o Build changes, also included in 0.2.1.29:
5451 - Tor does not build packages correctly with Automake 1.6 and earlier;
5452 added a check to Makefile.am to make sure that we're building with
5453 Automake 1.7 or later.
5454 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5455 because we built it with a too-old version of automake. Thus that
5456 release broke ./configure --enable-openbsd-malloc, which is popular
5457 among really fast exit relays on Linux.
5459 o Major bugfixes, new in 0.2.2.21-alpha:
5460 - Prevent crash/heap corruption when the cbtnummodes consensus
5461 parameter is set to 0 or large values. Fixes bug 2317; bugfix
5464 o Major features, new in 0.2.2.21-alpha:
5465 - Introduce minimum/maximum values that clients will believe
5466 from the consensus. Now we'll have a better chance to avoid crashes
5467 or worse when a consensus param has a weird value.
5469 o Minor features, new in 0.2.2.21-alpha:
5470 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
5471 used on bridges, and it makes bridge scanning somewhat easier.
5472 - If writing the state file to disk fails, wait up to an hour before
5473 retrying again, rather than trying again each second. Fixes bug
5474 2346; bugfix on Tor 0.1.1.3-alpha.
5475 - Make Libevent log messages get delivered to controllers later,
5476 and not from inside the Libevent log handler. This prevents unsafe
5477 reentrant Libevent calls while still letting the log messages
5479 - Detect platforms that brokenly use a signed size_t, and refuse to
5480 build there. Found and analyzed by doorss and rransom.
5481 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
5484 o Minor bugfixes, new in 0.2.2.21-alpha:
5485 - Handle SOCKS messages longer than 128 bytes long correctly, rather
5486 than waiting forever for them to finish. Fixes bug 2330; bugfix
5487 on 0.2.0.16-alpha. Found by doorss.
5488 - Add assertions to check for overflow in arguments to
5489 base32_encode() and base32_decode(); fix a signed-unsigned
5490 comparison there too. These bugs are not actually reachable in Tor,
5491 but it's good to prevent future errors too. Found by doorss.
5492 - Correctly detect failures to create DNS requests when using Libevent
5493 versions before v2. (Before Libevent 2, we used our own evdns
5494 implementation. Its return values for Libevent's evdns_resolve_*()
5495 functions are not consistent with those from Libevent.) Fixes bug
5496 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
5498 o Documentation, new in 0.2.2.21-alpha:
5499 - Document the default socks host and port (127.0.0.1:9050) for
5503 Changes in version 0.2.1.29 - 2011-01-15
5504 Tor 0.2.1.29 continues our recent code security audit work. The main
5505 fix resolves a remote heap overflow vulnerability that can allow remote
5506 code execution. Other fixes address a variety of assert and crash bugs,
5507 most of which we think are hard to exploit remotely.
5509 o Major bugfixes (security):
5510 - Fix a heap overflow bug where an adversary could cause heap
5511 corruption. This bug probably allows remote code execution
5512 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5514 - Prevent a denial-of-service attack by disallowing any
5515 zlib-compressed data whose compression factor is implausibly
5516 high. Fixes part of bug 2324; reported by "doorss".
5517 - Zero out a few more keys in memory before freeing them. Fixes
5518 bug 2384 and part of bug 2385. These key instances found by
5519 "cypherpunks", based on Andrew Case's report about being able
5520 to find sensitive data in Tor's memory space if you have enough
5521 permissions. Bugfix on 0.0.2pre9.
5523 o Major bugfixes (crashes):
5524 - Prevent calls to Libevent from inside Libevent log handlers.
5525 This had potential to cause a nasty set of crashes, especially
5526 if running Libevent with debug logging enabled, and running
5527 Tor with a controller watching for low-severity log messages.
5528 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5529 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5530 underflow errors there too. Fixes the other part of bug 2324.
5531 - Fix a bug where we would assert if we ever had a
5532 cached-descriptors.new file (or another file read directly into
5533 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5534 on 0.2.1.25. Found by doorss.
5535 - Fix some potential asserts and parsing issues with grossly
5536 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5539 o Minor bugfixes (other):
5540 - Fix a bug with handling misformed replies to reverse DNS lookup
5541 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5542 bug reported by doorss.
5543 - Fix compilation on mingw when a pthreads compatibility library
5544 has been installed. (We don't want to use it, so we shouldn't
5545 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5546 - Fix a bug where we would declare that we had run out of virtual
5547 addresses when the address space was only half-exhausted. Bugfix
5549 - Correctly handle the case where AutomapHostsOnResolve is set but
5550 no virtual addresses are available. Fixes bug 2328; bugfix on
5551 0.1.2.1-alpha. Bug found by doorss.
5552 - Correctly handle wrapping around to when we run out of virtual
5553 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
5554 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5555 because we built it with a too-old version of automake. Thus that
5556 release broke ./configure --enable-openbsd-malloc, which is popular
5557 among really fast exit relays on Linux.
5560 - Update to the January 1 2011 Maxmind GeoLite Country database.
5561 - Introduce output size checks on all of our decryption functions.
5564 - Tor does not build packages correctly with Automake 1.6 and earlier;
5565 added a check to Makefile.am to make sure that we're building with
5566 Automake 1.7 or later.
5569 Changes in version 0.2.2.20-alpha - 2010-12-17
5570 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
5571 exploitable bugs. We also fix a variety of other significant bugs,
5572 change the IP address for one of our directory authorities, and update
5573 the minimum version that Tor relays must run to join the network.
5576 - Fix a remotely exploitable bug that could be used to crash instances
5577 of Tor remotely by overflowing on the heap. Remote-code execution
5578 hasn't been confirmed, but can't be ruled out. Everyone should
5579 upgrade. Bugfix on the 0.1.1 series and later.
5580 - Fix a bug that could break accounting on 64-bit systems with large
5581 time_t values, making them hibernate for impossibly long intervals.
5582 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
5583 - Fix a logic error in directory_fetches_from_authorities() that
5584 would cause all _non_-exits refusing single-hop-like circuits
5585 to fetch from authorities, when we wanted to have _exits_ fetch
5586 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
5588 - Fix a stream fairness bug that would cause newer streams on a given
5589 circuit to get preference when reading bytes from the origin or
5590 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
5591 introduced before the first Tor release, in svn revision r152.
5593 o Directory authority changes:
5594 - Change IP address and ports for gabelmoo (v3 directory authority).
5597 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
5598 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
5599 - Fix an off-by-one error in calculating some controller command
5600 argument lengths. Fortunately, this mistake is harmless since
5601 the controller code does redundant NUL termination too. Found by
5602 boboper. Bugfix on 0.1.1.1-alpha.
5603 - Do not dereference NULL if a bridge fails to build its
5604 extra-info descriptor. Found by an anonymous commenter on
5605 Trac. Bugfix on 0.2.2.19-alpha.
5608 - Update to the December 1 2010 Maxmind GeoLite Country database.
5609 - Directory authorities now reject relays running any versions of
5610 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
5611 known bugs that keep RELAY_EARLY cells from working on rendezvous
5612 circuits. Followup to fix for bug 2081.
5613 - Directory authorities now reject relays running any version of Tor
5614 older than 0.2.0.26-rc. That version is the earliest that fetches
5615 current directory information correctly. Fixes bug 2156.
5616 - Report only the top 10 ports in exit-port stats in order not to
5617 exceed the maximum extra-info descriptor length of 50 KB. Implements
5621 Changes in version 0.2.1.28 - 2010-12-17
5622 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
5623 exploitable bugs. We also took this opportunity to change the IP address
5624 for one of our directory authorities, and to update the geoip database
5628 - Fix a remotely exploitable bug that could be used to crash instances
5629 of Tor remotely by overflowing on the heap. Remote-code execution
5630 hasn't been confirmed, but can't be ruled out. Everyone should
5631 upgrade. Bugfix on the 0.1.1 series and later.
5633 o Directory authority changes:
5634 - Change IP address and ports for gabelmoo (v3 directory authority).
5637 - Update to the December 1 2010 Maxmind GeoLite Country database.
5640 Changes in version 0.2.1.27 - 2010-11-23
5641 Yet another OpenSSL security patch broke its compatibility with Tor:
5642 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
5643 also took this opportunity to fix several crash bugs, integrate a new
5644 directory authority, and update the bundled GeoIP database.
5647 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5648 No longer set the tlsext_host_name extension on server SSL objects;
5649 but continue to set it on client SSL objects. Our goal in setting
5650 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5651 bugfix on 0.2.1.1-alpha.
5652 - Do not log messages to the controller while shrinking buffer
5653 freelists. Doing so would sometimes make the controller connection
5654 try to allocate a buffer chunk, which would mess up the internals
5655 of the freelist and cause an assertion failure. Fixes bug 1125;
5656 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5657 - Learn our external IP address when we're a relay or bridge, even if
5658 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5659 where we introduced bridge relays that don't need to publish to
5660 be useful. Fixes bug 2050.
5661 - Do even more to reject (and not just ignore) annotations on
5662 router descriptors received anywhere but from the cache. Previously
5663 we would ignore such annotations at first, but cache them to disk
5664 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5665 - When you're using bridges and your network goes away and your
5666 bridges get marked as down, recover when you attempt a new socks
5667 connection (if the network is back), rather than waiting up to an
5668 hour to try fetching new descriptors for your bridges. Bugfix on
5669 0.2.0.3-alpha; fixes bug 1981.
5672 - Move to the November 2010 Maxmind GeoLite country db (rather
5673 than the June 2009 ip-to-country GeoIP db) for our statistics that
5674 count how many users relays are seeing from each country. Now we'll
5675 have more accurate data, especially for many African countries.
5677 o New directory authorities:
5678 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
5682 - Fix an assertion failure that could occur in directory caches or
5683 bridge users when using a very short voting interval on a testing
5684 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
5686 - Enforce multiplicity rules when parsing annotations. Bugfix on
5687 0.2.0.8-alpha. Found by piebeer.
5688 - Allow handshaking OR connections to take a full KeepalivePeriod
5689 seconds to handshake. Previously, we would close them after
5690 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
5691 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
5693 - When building with --enable-gcc-warnings on OpenBSD, disable
5694 warnings in system headers. This makes --enable-gcc-warnings
5695 pass on OpenBSD 4.8.
5698 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
5699 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
5700 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
5701 Servers can start sending this code when enough clients recognize
5702 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
5703 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
5704 Patch from mingw-san.
5707 - Remove the old debian/ directory from the main Tor distribution.
5708 The official Tor-for-debian git repository lives at the URL
5709 https://git.torproject.org/debian/tor.git
5710 - Stop shipping the old doc/website/ directory in the tarball. We
5711 changed the website format in late 2010, and what we shipped in
5712 0.2.1.26 really wasn't that useful anyway.
5715 Changes in version 0.2.2.19-alpha - 2010-11-22
5716 Yet another OpenSSL security patch broke its compatibility with Tor:
5717 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
5720 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5721 No longer set the tlsext_host_name extension on server SSL objects;
5722 but continue to set it on client SSL objects. Our goal in setting
5723 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5724 bugfix on 0.2.1.1-alpha.
5727 - Try harder not to exceed the maximum length of 50 KB when writing
5728 statistics to extra-info descriptors. This bug was triggered by very
5729 fast relays reporting exit-port, entry, and dirreq statistics.
5730 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
5731 - Publish a router descriptor even if generating an extra-info
5732 descriptor fails. Previously we would not publish a router
5733 descriptor without an extra-info descriptor; this can cause fast
5734 exit relays collecting exit-port statistics to drop from the
5735 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
5738 Changes in version 0.2.2.18-alpha - 2010-11-16
5739 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
5740 us lately, makes unpublished bridge relays able to detect their IP
5741 address, and fixes a wide variety of other bugs to get us much closer
5742 to a stable release.
5745 - Do even more to reject (and not just ignore) annotations on
5746 router descriptors received anywhere but from the cache. Previously
5747 we would ignore such annotations at first, but cache them to disk
5748 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5749 - Do not log messages to the controller while shrinking buffer
5750 freelists. Doing so would sometimes make the controller connection
5751 try to allocate a buffer chunk, which would mess up the internals
5752 of the freelist and cause an assertion failure. Fixes bug 1125;
5753 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5754 - Learn our external IP address when we're a relay or bridge, even if
5755 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5756 where we introduced bridge relays that don't need to publish to
5757 be useful. Fixes bug 2050.
5758 - Maintain separate TLS contexts and certificates for incoming and
5759 outgoing connections in bridge relays. Previously we would use the
5760 same TLS contexts and certs for incoming and outgoing connections.
5761 Bugfix on 0.2.0.3-alpha; addresses bug 988.
5762 - Maintain separate identity keys for incoming and outgoing TLS
5763 contexts in bridge relays. Previously we would use the same
5764 identity keys for incoming and outgoing TLS contexts. Bugfix on
5765 0.2.0.3-alpha; addresses the other half of bug 988.
5766 - Avoid an assertion failure when we as an authority receive a
5767 duplicate upload of a router descriptor that we already have,
5768 but which we previously considered an obsolete descriptor.
5769 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
5770 - Avoid a crash bug triggered by looking at a dangling pointer while
5771 setting the network status consensus. Found by Robert Ransom.
5772 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
5773 - Fix a logic error where servers that _didn't_ act as exits would
5774 try to keep their server lists more aggressively up to date than
5775 exits, when it was supposed to be the other way around. Bugfix
5778 o Minor bugfixes (on Tor 0.2.1.x and earlier):
5779 - When we're trying to guess whether we know our IP address as
5780 a relay, we would log various ways that we failed to guess
5781 our address, but never log that we ended up guessing it
5782 successfully. Now add a log line to help confused and anxious
5783 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
5784 - Bring the logic that gathers routerinfos and assesses the
5785 acceptability of circuits into line. This prevents a Tor OP from
5786 getting locked in a cycle of choosing its local OR as an exit for a
5787 path (due to a .exit request) and then rejecting the circuit because
5788 its OR is not listed yet. It also prevents Tor clients from using an
5789 OR running in the same instance as an exit (due to a .exit request)
5790 if the OR does not meet the same requirements expected of an OR
5791 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5792 - Correctly describe errors that occur when generating a TLS object.
5793 Previously we would attribute them to a failure while generating a
5794 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
5796 - Enforce multiplicity rules when parsing annotations. Bugfix on
5797 0.2.0.8-alpha. Found by piebeer.
5798 - Fix warnings that newer versions of autoconf produced during
5799 ./autogen.sh. These warnings appear to be harmless in our case,
5800 but they were extremely verbose. Fixes bug 2020.
5802 o Minor bugfixes (on Tor 0.2.2.x):
5803 - Enable protection of small arrays whenever we build with gcc
5804 hardening features, not only when also building with warnings
5805 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
5808 - Make hidden services work better in private Tor networks by not
5809 requiring any uptime to join the hidden service descriptor
5810 DHT. Implements ticket 2088.
5811 - Rate-limit the "your application is giving Tor only an IP address"
5812 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
5813 - When AllowSingleHopExits is set, print a warning to explain to the
5814 relay operator why most clients are avoiding her relay.
5815 - Update to the November 1 2010 Maxmind GeoLite Country database.
5817 o Code simplifications and refactoring:
5818 - When we fixed bug 1038 we had to put in a restriction not to send
5819 RELAY_EARLY cells on rend circuits. This was necessary as long
5820 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
5821 active. Now remove this obsolete check. Resolves bug 2081.
5822 - Some options used different conventions for uppercasing of acronyms
5823 when comparing manpage and source. Fix those in favor of the
5824 manpage, as it makes sense to capitalize acronyms.
5825 - Remove the torrc.complete file. It hasn't been kept up to date
5826 and users will have better luck checking out the manpage.
5827 - Remove the obsolete "NoPublish" option; it has been flagged
5828 as obsolete and has produced a warning since 0.1.1.18-rc.
5829 - Remove everything related to building the expert bundle for OS X.
5830 It has confused many users, doesn't work right on OS X 10.6,
5831 and is hard to get rid of once installed. Resolves bug 1274.
5834 Changes in version 0.2.2.17-alpha - 2010-09-30
5835 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
5836 to use one-hop circuits (which can put the exit relays at higher risk,
5837 plus unbalance the network); fixes a big bug in bandwidth accounting
5838 for relays that want to limit their monthly bandwidth use; fixes a
5839 big pile of bugs in how clients tolerate temporary network failure;
5840 and makes our adaptive circuit build timeout feature (which improves
5841 client performance if your network is fast while not breaking things
5842 if your network is slow) better handle bad networks.
5845 - Exit relays now try harder to block exit attempts from unknown
5846 relays, to make it harder for people to use them as one-hop proxies
5847 a la tortunnel. Controlled by the refuseunknownexits consensus
5848 parameter (currently enabled), or you can override it on your
5849 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
5851 o Major bugfixes (0.2.1.x and earlier):
5852 - Fix a bug in bandwidth accounting that could make us use twice
5853 the intended bandwidth when our interval start changes due to
5854 daylight saving time. Now we tolerate skew in stored vs computed
5855 interval starts: if the start of the period changes by no more than
5856 50% of the period's duration, we remember bytes that we transferred
5857 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
5858 - Always search the Windows system directory for system DLLs, and
5859 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
5860 - When you're using bridges and your network goes away and your
5861 bridges get marked as down, recover when you attempt a new socks
5862 connection (if the network is back), rather than waiting up to an
5863 hour to try fetching new descriptors for your bridges. Bugfix on
5864 0.2.0.3-alpha; fixes bug 1981.
5866 o Major bugfixes (on 0.2.2.x):
5867 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
5869 - Fix a segfault that could happen when operating a bridge relay with
5870 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
5871 - The consensus bandwidth-weights (used by clients to choose fast
5872 relays) entered an unexpected edge case in September where
5873 Exits were much scarcer than Guards, resulting in bad weight
5874 recommendations. Now we compute them using new constraints that
5875 should succeed in all cases. Also alter directory authorities to
5876 not include the bandwidth-weights line if they fail to produce
5877 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
5878 - When weighting bridges during path selection, we used to trust
5879 the bandwidths they provided in their descriptor, only capping them
5880 at 10MB/s. This turned out to be problematic for two reasons:
5881 Bridges could claim to handle a lot more traffic then they
5882 actually would, thus making more clients pick them and have a
5883 pretty effective DoS attack. The other issue is that new bridges
5884 that might not have a good estimate for their bw capacity yet
5885 would not get used at all unless no other bridges are available
5886 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
5888 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
5889 - Ignore cannibalized circuits when recording circuit build times.
5890 This should provide for a minor performance improvement for hidden
5891 service users using 0.2.2.14-alpha, and should remove two spurious
5892 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
5893 - Simplify the logic that causes us to decide if the network is
5894 unavailable for purposes of recording circuit build times. If we
5895 receive no cells whatsoever for the entire duration of a circuit's
5896 full measured lifetime, the network is probably down. Also ignore
5897 one-hop directory fetching circuit timeouts when calculating our
5898 circuit build times. These changes should hopefully reduce the
5899 cases where we see ridiculous circuit build timeouts for people
5900 with spotty wireless connections. Fixes part of bug 1772; bugfix
5902 - Prevent the circuit build timeout from becoming larger than
5903 the maximum build time we have ever seen. Also, prevent the time
5904 period for measurement circuits from becoming larger than twice that
5905 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
5908 - When we run out of directory information such that we can't build
5909 circuits, but then get enough that we can build circuits, log when
5910 we actually construct a circuit, so the user has a better chance of
5911 knowing what's going on. Fixes bug 1362.
5912 - Be more generous with how much bandwidth we'd use up (with
5913 accounting enabled) before entering "soft hibernation". Previously,
5914 we'd refuse new connections and circuits once we'd used up 95% of
5915 our allotment. Now, we use up 95% of our allotment, AND make sure
5916 that we have no more than 500MB (or 3 hours of expected traffic,
5917 whichever is lower) remaining before we enter soft hibernation.
5918 - If we've configured EntryNodes and our network goes away and/or all
5919 our entrynodes get marked down, optimistically retry them all when
5920 a new socks application request appears. Fixes bug 1882.
5921 - Add some more defensive programming for architectures that can't
5922 handle unaligned integer accesses. We don't know of any actual bugs
5923 right now, but that's the best time to fix them. Fixes bug 1943.
5924 - Support line continuations in the torrc config file. If a line
5925 ends with a single backslash character, the newline is ignored, and
5926 the configuration value is treated as continuing on the next line.
5929 o Minor bugfixes (on 0.2.1.x and earlier):
5930 - For bandwidth accounting, calculate our expected bandwidth rate
5931 based on the time during which we were active and not in
5932 soft-hibernation during the last interval. Previously, we were
5933 also considering the time spent in soft-hibernation. If this
5934 was a long time, we would wind up underestimating our bandwidth
5935 by a lot, and skewing our wakeup time towards the start of the
5936 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
5938 o Minor bugfixes (on 0.2.2.x):
5939 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
5940 which were disabled by the circuit build timeout changes in
5941 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
5942 - Make sure we don't warn about missing bandwidth weights when
5943 choosing bridges or other relays not in the consensus. Bugfix on
5944 0.2.2.10-alpha; fixes bug 1805.
5945 - In our logs, do not double-report signatures from unrecognized
5946 authorities both as "from unknown authority" and "not
5947 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
5950 Changes in version 0.2.2.16-alpha - 2010-09-17
5951 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
5952 evident at exit relays), and also continues to resolve all the little
5953 bugs that have been filling up trac lately.
5955 o Major bugfixes (stream-level fairness):
5956 - When receiving a circuit-level SENDME for a blocked circuit, try
5957 to package cells fairly from all the streams that had previously
5958 been blocked on that circuit. Previously, we had started with the
5959 oldest stream, and allowed each stream to potentially exhaust
5960 the circuit's package window. This gave older streams on any
5961 given circuit priority over newer ones. Fixes bug 1937. Detected
5962 originally by Camilo Viecco. This bug was introduced before the
5963 first Tor release, in svn commit r152: it is the new winner of
5964 the longest-lived bug prize.
5965 - When the exit relay got a circuit-level sendme cell, it started
5966 reading on the exit streams, even if had 500 cells queued in the
5967 circuit queue already, so the circuit queue just grew and grew in
5968 some cases. We fix this by not re-enabling reading on receipt of a
5969 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
5970 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
5972 - Newly created streams were allowed to read cells onto circuits,
5973 even if the circuit's cell queue was blocked and waiting to drain.
5974 This created potential unfairness, as older streams would be
5975 blocked, but newer streams would gladly fill the queue completely.
5976 We add code to detect this situation and prevent any stream from
5977 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
5981 - Update to the September 1 2010 Maxmind GeoLite Country database.
5982 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
5983 not. This would lead to a cookie that is still not group readable.
5984 Closes bug 1843. Suggested by katmagic.
5985 - When logging a rate-limited warning, we now mention how many messages
5986 got suppressed since the last warning.
5987 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
5988 do individual connection-level rate limiting of clients. The torrc
5989 config options with the same names trump the consensus params, if
5990 both are present. Replaces the old "bwconnrate" and "bwconnburst"
5991 consensus params which were broken from 0.2.2.7-alpha through
5992 0.2.2.14-alpha. Closes bug 1947.
5993 - When a router changes IP address or port, authorities now launch
5994 a new reachability test for it. Implements ticket 1899.
5995 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
5996 2 no signature, 4 required" messages about consensus signatures
5997 easier to read, and make sure they get logged at the same severity
5998 as the messages explaining which keys are which. Fixes bug 1290.
5999 - Don't warn when we have a consensus that we can't verify because
6000 of missing certificates, unless those certificates are ones
6001 that we have been trying and failing to download. Fixes bug 1145.
6002 - If you configure your bridge with a known identity fingerprint,
6003 and the bridge authority is unreachable (as it is in at least
6004 one country now), fall back to directly requesting the descriptor
6005 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
6007 - When building with --enable-gcc-warnings on OpenBSD, disable
6008 warnings in system headers. This makes --enable-gcc-warnings
6009 pass on OpenBSD 4.8.
6011 o Minor bugfixes (on 0.2.1.x and earlier):
6012 - Authorities will now attempt to download consensuses if their
6013 own efforts to make a live consensus have failed. This change
6014 means authorities that restart will fetch a valid consensus, and
6015 it means authorities that didn't agree with the current consensus
6016 will still fetch and serve it if it has enough signatures. Bugfix
6017 on 0.2.0.9-alpha; fixes bug 1300.
6018 - Ensure DNS requests launched by "RESOLVE" commands from the
6019 controller respect the __LeaveStreamsUnattached setconf options. The
6020 same goes for requests launched via DNSPort or transparent
6021 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
6022 - Allow handshaking OR connections to take a full KeepalivePeriod
6023 seconds to handshake. Previously, we would close them after
6024 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
6025 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
6027 - Rate-limit "Failed to hand off onionskin" warnings.
6028 - Never relay a cell for a circuit we have already destroyed.
6029 Between marking a circuit as closeable and finally closing it,
6030 it may have been possible for a few queued cells to get relayed,
6031 even though they would have been immediately dropped by the next
6032 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
6033 - Never queue a cell for a circuit that's already been marked
6035 - Never vote for a server as "Running" if we have a descriptor for
6036 it claiming to be hibernating, and that descriptor was published
6037 more recently than our last contact with the server. Bugfix on
6038 0.2.0.3-alpha; fixes bug 911.
6039 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
6042 o Minor bugfixes (on 0.2.2.x):
6043 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
6044 down if a directory fetch fails and you've configured either
6045 bridges or EntryNodes. The intent was to mark the relay as down
6046 _unless_ you're using bridges or EntryNodes, since if you are
6047 then you could quickly run out of entry points.
6048 - Fix the Windows directory-listing code. A bug introduced in
6049 0.2.2.14-alpha could make Windows directory servers forget to load
6050 some of their cached v2 networkstatus files.
6051 - Really allow clients to use relays as bridges. Fixes bug 1776;
6052 bugfix on 0.2.2.15-alpha.
6053 - Demote a warn to info that happens when the CellStatistics option
6054 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
6055 Reported by Moritz Bartl.
6056 - On Windows, build correctly either with or without Unicode support.
6057 This is necessary so that Tor can support fringe platforms like
6058 Windows 98 (which has no Unicode), or Windows CE (which has no
6059 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
6062 - Add a unit test for cross-platform directory-listing code.
6065 Changes in version 0.2.2.15-alpha - 2010-08-18
6066 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
6067 fixes a variety of other bugs that were preventing performance
6068 experiments from moving forward, fixes several bothersome memory leaks,
6069 and generally closes a lot of smaller bugs that have been filling up
6073 - Stop assigning the HSDir flag to relays that disable their
6074 DirPort (and thus will refuse to answer directory requests). This
6075 fix should dramatically improve the reachability of hidden services:
6076 hidden services and hidden service clients pick six HSDir relays
6077 to store and retrieve the hidden service descriptor, and currently
6078 about half of the HSDir relays will refuse to work. Bugfix on
6079 0.2.0.10-alpha; fixes part of bug 1693.
6080 - The PerConnBWRate and Burst config options, along with the
6081 bwconnrate and bwconnburst consensus params, initialized each conn's
6082 token bucket values only when the connection is established. Now we
6083 update them if the config options change, and update them every time
6084 we get a new consensus. Otherwise we can encounter an ugly edge
6085 case where we initialize an OR conn to client-level bandwidth,
6086 but then later the relay joins the consensus and we leave it
6087 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
6088 - Fix a regression that caused Tor to rebind its ports if it receives
6089 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
6092 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
6093 should give us approximately 40-50% more Guard-flagged nodes,
6094 improving the anonymity the Tor network can provide and also
6095 decreasing the dropoff in throughput that relays experience when
6096 they first get the Guard flag.
6097 - Allow enabling or disabling the *Statistics config options while
6101 - Update to the August 1 2010 Maxmind GeoLite Country database.
6102 - Have the controller interface give a more useful message than
6103 "Internal Error" in response to failed GETINFO requests.
6104 - Warn when the same option is provided more than once in a torrc
6105 file, on the command line, or in a single SETCONF statement, and
6106 the option is one that only accepts a single line. Closes bug 1384.
6107 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
6108 Patch from mingw-san.
6109 - Add support for the country code "{??}" in torrc options like
6110 ExcludeNodes, to indicate all routers of unknown country. Closes
6112 - Relays report the number of bytes spent on answering directory
6113 requests in extra-info descriptors similar to {read,write}-history.
6114 Implements enhancement 1790.
6116 o Minor bugfixes (on 0.2.1.x and earlier):
6117 - Complain if PublishServerDescriptor is given multiple arguments that
6118 include 0 or 1. This configuration will be rejected in the future.
6119 Bugfix on 0.2.0.1-alpha; closes bug 1107.
6120 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
6121 Bugfix on 0.2.0.13-alpha; closes bug 928.
6122 - Change "Application request when we're believed to be offline."
6123 notice to "Application request when we haven't used client
6124 functionality lately.", to clarify that it's not an error. Bugfix
6125 on 0.0.9.3; fixes bug 1222.
6126 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
6127 would return "551 Internal error" rather than "552 Unrecognized key
6128 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
6129 - Users can't configure a regular relay to be their bridge. It didn't
6130 work because when Tor fetched the bridge descriptor, it found
6131 that it already had it, and didn't realize that the purpose of the
6132 descriptor had changed. Now we replace routers with a purpose other
6133 than bridge with bridge descriptors when fetching them. Bugfix on
6134 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
6135 refetch the descriptor with router purpose 'general', disabling
6137 - Fix a rare bug in rend_fn unit tests: we would fail a test when
6138 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
6139 on 0.2.0.10-alpha; fixes bug 1808.
6140 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
6141 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
6142 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
6143 Servers can start sending this code when enough clients recognize
6144 it. Also update the spec to reflect this new reason. Bugfix on
6145 0.1.0.1-rc; fixes part of bug 1793.
6146 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
6147 when we switch from being a public relay to a bridge. Otherwise
6148 there will still be clients that see the relay in their consensus,
6149 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
6151 - Instead of giving an assertion failure on an internal mismatch
6152 on estimated freelist size, just log a BUG warning and try later.
6153 Mitigates but does not fix bug 1125.
6154 - Fix an assertion failure that could occur in caches or bridge users
6155 when using a very short voting interval on a testing network.
6156 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
6158 o Minor bugfixes (on 0.2.2.x):
6159 - Alter directory authorities to always consider Exit-flagged nodes
6160 as potential Guard nodes in their votes. The actual decision to
6161 use Exits as Guards is done in the consensus bandwidth weights.
6162 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
6163 - When the controller is reporting the purpose of circuits that
6164 didn't finish building before the circuit build timeout, it was
6165 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
6166 - Our libevent version parsing code couldn't handle versions like
6167 1.4.14b-stable and incorrectly warned the user about using an
6168 old and broken version of libevent. Treat 1.4.14b-stable like
6169 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
6171 - Don't use substitution references like $(VAR:MOD) when
6172 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
6173 '$(:x)' to 'x' rather than the empty string. This bites us in
6174 doc/ when configured with --disable-asciidoc. Bugfix on
6175 0.2.2.9-alpha; fixes bug 1773.
6176 - Remove a spurious hidden service server-side log notice about
6177 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
6179 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
6181 - Correctly report written bytes on linked connections. Found while
6182 implementing 1790. Bugfix on 0.2.2.4-alpha.
6183 - Fix three memory leaks: one in circuit_build_times_parse_state(),
6184 one in dirvote_add_signatures_to_pending_consensus(), and one every
6185 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
6186 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
6188 o Code simplifications and refactoring:
6189 - Take a first step towards making or.h smaller by splitting out
6190 function definitions for all source files in src/or/. Leave
6191 structures and defines in or.h for now.
6192 - Remove a bunch of unused function declarations as well as a block of
6193 #if 0'd code from the unit tests. Closes bug 1824.
6194 - New unit tests for exit-port history statistics; refactored exit
6195 statistics code to be more easily tested.
6196 - Remove the old debian/ directory from the main Tor distribution.
6197 The official Tor-for-debian git repository lives at the URL
6198 https://git.torproject.org/debian/tor.git
6201 Changes in version 0.2.2.14-alpha - 2010-07-12
6202 Tor 0.2.2.14-alpha greatly improves client-side handling of
6203 circuit build timeouts, which are used to estimate speed and improve
6204 performance. We also move to a much better GeoIP database, port Tor to
6205 Windows CE, introduce new compile flags that improve code security,
6206 add an eighth v3 directory authority, and address a lot of more
6210 - Tor directory authorities no longer crash when started with a
6211 cached-microdesc-consensus file in their data directory. Bugfix
6212 on 0.2.2.6-alpha; fixes bug 1532.
6213 - Treat an unset $HOME like an empty $HOME rather than triggering an
6214 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
6215 - Ignore negative and large circuit build timeout values that can
6216 happen during a suspend or hibernate. These values caused various
6217 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
6218 - Alter calculation of Pareto distribution parameter 'Xm' for
6219 Circuit Build Timeout learning to use the weighted average of the
6220 top N=3 modes (because we have three entry guards). Considering
6221 multiple modes should improve the timeout calculation in some cases,
6222 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
6224 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
6225 right censored distribution model. This approach improves over the
6226 synthetic timeout generation approach that was producing insanely
6227 high timeout values. Now we calculate build timeouts using truncated
6228 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
6229 - Do not close circuits that are under construction when they reach
6230 the circuit build timeout. Instead, leave them building (but do not
6231 use them) for up until the time corresponding to the 95th percentile
6232 on the Pareto CDF or 60 seconds, whichever is greater. This is done
6233 to provide better data for the new Pareto model. This percentile
6234 can be controlled by the consensus.
6237 - Move to the June 2010 Maxmind GeoLite country db (rather than the
6238 June 2009 ip-to-country GeoIP db) for our statistics that count
6239 how many users relays are seeing from each country. Now we have
6240 more accurate data for many African countries.
6241 - Port Tor to build and run correctly on Windows CE systems, using
6242 the wcecompat library. Contributed by Valerio Lupi.
6243 - New "--enable-gcc-hardening" ./configure flag (off by default)
6244 to turn on gcc compile time hardening options. It ensures
6245 that signed ints have defined behavior (-fwrapv), enables
6246 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
6247 with canaries (-fstack-protector-all), turns on ASLR protection if
6248 supported by the kernel (-fPIE, -pie), and adds additional security
6249 related warnings. Verified to work on Mac OS X and Debian Lenny.
6250 - New "--enable-linker-hardening" ./configure flag (off by default)
6251 to turn on ELF specific hardening features (relro, now). This does
6252 not work with Mac OS X or any other non-ELF binary format.
6254 o New directory authorities:
6255 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
6259 - New config option "WarnUnsafeSocks 0" disables the warning that
6260 occurs whenever Tor receives a socks handshake using a version of
6261 the socks protocol that can only provide an IP address (rather
6262 than a hostname). Setups that do DNS locally over Tor are fine,
6263 and we shouldn't spam the logs in that case.
6264 - Convert the HACKING file to asciidoc, and add a few new sections
6265 to it, explaining how we use Git, how we make changelogs, and
6266 what should go in a patch.
6267 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
6268 event, to give information on the current rate of circuit timeouts
6269 over our stored history.
6270 - Add ability to disable circuit build time learning via consensus
6271 parameter and via a LearnCircuitBuildTimeout config option. Also
6272 automatically disable circuit build time calculation if we are
6273 either a AuthoritativeDirectory, or if we fail to write our state
6274 file. Fixes bug 1296.
6275 - More gracefully handle corrupt state files, removing asserts
6276 in favor of saving a backup and resetting state.
6277 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
6281 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
6283 - When a2x fails, mention that the user could disable manpages instead
6284 of trying to fix their asciidoc installation.
6285 - Where available, use Libevent 2.0's periodic timers so that our
6286 once-per-second cleanup code gets called even more closely to
6287 once per second than it would otherwise. Fixes bug 943.
6288 - If you run a bridge that listens on multiple IP addresses, and
6289 some user configures a bridge address that uses a different IP
6290 address than your bridge writes in its router descriptor, and the
6291 user doesn't specify an identity key, their Tor would discard the
6292 descriptor because "it isn't one of our configured bridges", and
6293 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
6294 Bugfix on 0.2.0.3-alpha.
6295 - If OpenSSL fails to make a duplicate of a private or public key, log
6296 an error message and try to exit cleanly. May help with debugging
6297 if bug 1209 ever remanifests.
6298 - Save a couple bytes in memory allocation every time we escape
6299 certain characters in a string. Patch from Florian Zumbiehl.
6300 - Make it explicit that we don't cannibalize one-hop circuits. This
6301 happens in the wild, but doesn't turn out to be a problem because
6302 we fortunately don't use those circuits. Many thanks to outofwords
6303 for the initial analysis and to swissknife who confirmed that
6304 two-hop circuits are actually created.
6305 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
6306 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
6307 - Eliminate a case where a circuit build time warning was displayed
6308 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
6311 Changes in version 0.2.1.26 - 2010-05-02
6312 Tor 0.2.1.26 addresses the recent connection and memory overload
6313 problems we've been seeing on relays, especially relays with their
6314 DirPort open. If your relay has been crashing, or you turned it off
6315 because it used too many resources, give this release a try.
6317 This release also fixes yet another instance of broken OpenSSL libraries
6318 that was causing some relays to drop out of the consensus.
6321 - Teach relays to defend themselves from connection overload. Relays
6322 now close idle circuits early if it looks like they were intended
6323 for directory fetches. Relays are also more aggressive about closing
6324 TLS connections that have no circuits on them. Such circuits are
6325 unlikely to be re-used, and tens of thousands of them were piling
6326 up at the fast relays, causing the relays to run out of sockets
6327 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6328 their directory fetches over TLS).
6329 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6330 that claim to be earlier than 0.9.8m, but which have in reality
6331 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6332 behavior. Possible fix for some cases of bug 1346.
6333 - Directory mirrors were fetching relay descriptors only from v2
6334 directory authorities, rather than v3 authorities like they should.
6335 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6336 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6339 - Finally get rid of the deprecated and now harmful notion of "clique
6340 mode", where directory authorities maintain TLS connections to
6344 - In the util/threads test, no longer free the test_mutex before all
6345 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6346 - The master thread could starve the worker threads quite badly on
6347 certain systems, causing them to run only partially in the allowed
6348 window. This resulted in test failures. Now the master thread sleeps
6349 occasionally for a few microseconds while the two worker-threads
6350 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6353 Changes in version 0.2.2.13-alpha - 2010-04-24
6354 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
6355 problems we've been seeing on relays, especially relays with their
6356 DirPort open. If your relay has been crashing, or you turned it off
6357 because it used too many resources, give this release a try.
6360 - Teach relays to defend themselves from connection overload. Relays
6361 now close idle circuits early if it looks like they were intended
6362 for directory fetches. Relays are also more aggressive about closing
6363 TLS connections that have no circuits on them. Such circuits are
6364 unlikely to be re-used, and tens of thousands of them were piling
6365 up at the fast relays, causing the relays to run out of sockets
6366 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6367 their directory fetches over TLS).
6370 - Finally get rid of the deprecated and now harmful notion of "clique
6371 mode", where directory authorities maintain TLS connections to
6373 - Directory authorities now do an immediate reachability check as soon
6374 as they hear about a new relay. This change should slightly reduce
6375 the time between setting up a relay and getting listed as running
6376 in the consensus. It should also improve the time between setting
6377 up a bridge and seeing use by bridge users.
6378 - Directory authorities no longer launch a TLS connection to every
6379 relay as they startup. Now that we have 2k+ descriptors cached,
6380 the resulting network hiccup is becoming a burden. Besides,
6381 authorities already avoid voting about Running for the first half
6382 hour of their uptime.
6385 Changes in version 0.2.2.12-alpha - 2010-04-20
6386 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
6387 handle and vote on descriptors. It was causing relays to drop out of
6391 - Many relays have been falling out of the consensus lately because
6392 not enough authorities know about their descriptor for them to get
6393 a majority of votes. When we deprecated the v2 directory protocol,
6394 we got rid of the only way that v3 authorities can hear from each
6395 other about other descriptors. Now authorities examine every v3
6396 vote for new descriptors, and fetch them from that authority. Bugfix
6398 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
6399 and a warning in or.h related to bandwidth_weight_rule_t that
6400 prevented clean compile on OS X. Fixes bug 1363; bugfix on
6402 - Fix a segfault on relays when DirReqStatistics is enabled
6403 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
6407 - Demote a confusing TLS warning that relay operators might get when
6408 someone tries to talk to their OrPort. It is neither the operator's
6409 fault nor can they do anything about it. Fixes bug 1364; bugfix
6413 Changes in version 0.2.2.11-alpha - 2010-04-15
6414 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
6415 libraries that was causing some relays to drop out of the consensus.
6418 - Directory mirrors were fetching relay descriptors only from v2
6419 directory authorities, rather than v3 authorities like they should.
6420 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6421 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6422 - Fix a parsing error that made every possible value of
6423 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
6424 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
6425 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
6426 about the option without breaking older ones.
6427 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6428 that claim to be earlier than 0.9.8m, but which have in reality
6429 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6430 behavior. Possible fix for some cases of bug 1346.
6433 - Experiment with a more aggressive approach to preventing clients
6434 from making one-hop exit streams. Exit relays who want to try it
6435 out can set "RefuseUnknownExits 1" in their torrc, and then look
6436 for "Attempt by %s to open a stream" log messages. Let us know
6438 - Add support for statically linking zlib by specifying
6439 --enable-static-zlib, to go with our support for statically linking
6440 openssl and libevent. Resolves bug 1358.
6443 - Fix a segfault that happens whenever a Tor client that is using
6444 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
6446 - When we cleaned up the contrib/tor-exit-notice.html file, we left
6447 out the first line. Fixes bug 1295.
6448 - When building the manpage from a tarball, we required asciidoc, but
6449 the asciidoc -> roff/html conversion was already done for the
6450 tarball. Make 'make' complain only when we need asciidoc (either
6451 because we're compiling directly from git, or because we altered
6452 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
6453 - When none of the directory authorities vote on any params, Tor
6454 segfaulted when trying to make the consensus from the votes. We
6455 didn't trigger the bug in practice, because authorities do include
6456 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
6459 - In the util/threads test, no longer free the test_mutex before all
6460 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6461 - The master thread could starve the worker threads quite badly on
6462 certain systems, causing them to run only partially in the allowed
6463 window. This resulted in test failures. Now the master thread sleeps
6464 occasionally for a few microseconds while the two worker-threads
6465 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6468 Changes in version 0.2.2.10-alpha - 2010-03-07
6469 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
6470 could prevent relays from guessing their IP address correctly. It also
6471 starts the groundwork for another client-side performance boost, since
6472 currently we're not making efficient use of relays that have both the
6473 Guard flag and the Exit flag.
6476 - Fix a regression from our patch for bug 1244 that caused relays
6477 to guess their IP address incorrectly if they didn't set Address
6478 in their torrc and/or their address fails to resolve. Bugfix on
6479 0.2.2.9-alpha; fixes bug 1269.
6481 o Major features (performance):
6482 - Directory authorities now compute consensus weightings that instruct
6483 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
6484 and no flag. Clients that use these weightings will distribute
6485 network load more evenly across these different relay types. The
6486 weightings are in the consensus so we can change them globally in
6487 the future. Extra thanks to "outofwords" for finding some nasty
6488 security bugs in the first implementation of this feature.
6490 o Minor features (performance):
6491 - Always perform router selections using weighted relay bandwidth,
6492 even if we don't need a high capacity circuit at the time. Non-fast
6493 circuits now only differ from fast ones in that they can use relays
6494 not marked with the Fast flag. This "feature" could turn out to
6495 be a horrible bug; we should investigate more before it goes into
6499 - Allow disabling building of the manpages. Skipping the manpage
6500 speeds up the build considerably.
6502 o Minor bugfixes (on 0.2.2.x):
6503 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
6504 Bugfix on 0.2.2.9-alpha.
6505 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
6506 config option. Bugfix on 0.2.2.7-alpha.
6507 - Ship the asciidoc-helper file in the tarball, so that people can
6508 build from source if they want to, and touching the .1.txt files
6509 doesn't break the build. Bugfix on 0.2.2.9-alpha.
6511 o Minor bugfixes (on 0.2.1.x or earlier):
6512 - Fix a dereference-then-NULL-check sequence when publishing
6513 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6515 - Fix another dereference-then-NULL-check sequence. Bugfix on
6516 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6517 - Make sure we treat potentially not NUL-terminated strings correctly.
6518 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6520 o Code simplifications and refactoring:
6521 - Fix some urls in the exit notice file and make it XHTML1.1 strict
6522 compliant. Based on a patch from Christian Kujau.
6523 - Don't use sed in asciidoc-helper anymore.
6524 - Make the build process fail if asciidoc cannot be found and
6525 building with asciidoc isn't disabled.
6528 Changes in version 0.2.2.9-alpha - 2010-02-22
6529 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
6530 location of a directory authority, and cleans up a bunch of small bugs.
6532 o Directory authority changes:
6533 - Change IP address for dannenberg (v3 directory authority), and
6534 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6535 service directory authority) from the list.
6538 - Make Tor work again on the latest OS X: when deciding whether to
6539 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6540 version at run-time, not compile time. We need to do this because
6541 Apple doesn't update its dev-tools headers when it updates its
6542 libraries in a security patch.
6543 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6544 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6545 a memory leak when requesting a hidden service descriptor we've
6546 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6548 - Authorities could be tricked into giving out the Exit flag to relays
6549 that didn't allow exiting to any ports. This bug could screw
6550 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
6551 1238. Bug discovered by Martin Kowalczyk.
6552 - When freeing a session key, zero it out completely. We only zeroed
6553 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6554 patched by ekir. Fixes bug 1254.
6557 - Fix static compilation by listing the openssl libraries in the right
6558 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
6559 - Resume handling .exit hostnames in a special way: originally we
6560 stripped the .exit part and used the requested exit relay. In
6561 0.2.2.1-alpha we stopped treating them in any special way, meaning
6562 if you use a .exit address then Tor will pass it on to the exit
6563 relay. Now we reject the .exit stream outright, since that behavior
6564 might be more expected by the user. Found and diagnosed by Scott
6565 Bennett and Downie on or-talk.
6566 - Don't spam the controller with events when we have no file
6567 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
6568 for log messages was already solved from bug 748.)
6569 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
6571 - Make the DNSPort option work with libevent 2.x. Don't alter the
6572 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
6573 - Emit a GUARD DROPPED controller event for a case we missed.
6574 - Make more fields in the controller protocol case-insensitive, since
6575 control-spec.txt said they were.
6576 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6577 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6578 - Fix a spec conformance issue: the network-status-version token
6579 must be the first token in a v3 consensus or vote. Discovered by
6580 parakeep. Bugfix on 0.2.0.3-alpha.
6582 o Code simplifications and refactoring:
6583 - Generate our manpage and HTML documentation using Asciidoc. This
6584 change should make it easier to maintain the documentation, and
6586 - Remove the --enable-iphone option. According to reports from Marco
6587 Bonetti, Tor builds fine without any special tweaking on recent
6588 iPhone SDK versions.
6589 - Removed some unnecessary files from the source distribution. The
6590 AUTHORS file has now been merged into the people page on the
6591 website. The roadmaps and design doc can now be found in the
6592 projects directory in svn.
6593 - Enabled various circuit build timeout constants to be controlled
6594 by consensus parameters. Also set better defaults for these
6595 parameters based on experimentation on broadband and simulated
6599 - The 'EXTENDCIRCUIT' control port command can now be used with
6600 a circ id of 0 and no path. This feature will cause Tor to build
6601 a new 'fast' general purpose circuit using its own path selection
6603 - Added a BUILDTIMEOUT_SET controller event to describe changes
6604 to the circuit build timeout.
6605 - Future-proof the controller protocol a bit by ignoring keyword
6606 arguments we do not recognize.
6607 - Expand homedirs passed to tor-checkkey. This should silence a
6608 coverity complaint about passing a user-supplied string into
6609 open() without checking it.
6612 Changes in version 0.2.1.25 - 2010-03-16
6613 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
6614 prevent relays from guessing their IP address correctly. It also fixes
6615 several minor potential security bugs.
6618 - Fix a regression from our patch for bug 1244 that caused relays
6619 to guess their IP address incorrectly if they didn't set Address
6620 in their torrc and/or their address fails to resolve. Bugfix on
6621 0.2.1.23; fixes bug 1269.
6622 - When freeing a session key, zero it out completely. We only zeroed
6623 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6624 patched by ekir. Fixes bug 1254.
6627 - Fix a dereference-then-NULL-check sequence when publishing
6628 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6630 - Fix another dereference-then-NULL-check sequence. Bugfix on
6631 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6632 - Make sure we treat potentially not NUL-terminated strings correctly.
6633 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6637 Changes in version 0.2.1.24 - 2010-02-21
6638 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
6642 - Work correctly out-of-the-box with even more vendor-patched versions
6643 of OpenSSL. In particular, make it so Debian and OS X don't need
6644 customized patches to run/build.
6647 Changes in version 0.2.1.23 - 2010-02-13
6648 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
6649 again on the latest OS X, and updates the location of a directory
6652 o Major bugfixes (performance):
6653 - We were selecting our guards uniformly at random, and then weighting
6654 which of our guards we'd use uniformly at random. This imbalance
6655 meant that Tor clients were severely limited on throughput (and
6656 probably latency too) by the first hop in their circuit. Now we
6657 select guards weighted by currently advertised bandwidth. We also
6658 automatically discard guards picked using the old algorithm. Fixes
6659 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6662 - Make Tor work again on the latest OS X: when deciding whether to
6663 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6664 version at run-time, not compile time. We need to do this because
6665 Apple doesn't update its dev-tools headers when it updates its
6666 libraries in a security patch.
6667 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6668 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6669 a memory leak when requesting a hidden service descriptor we've
6670 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6673 o Directory authority changes:
6674 - Change IP address for dannenberg (v3 directory authority), and
6675 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6676 service directory authority) from the list.
6679 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6680 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6683 - Avoid a mad rush at the beginning of each month when each client
6684 rotates half of its guards. Instead we spread the rotation out
6685 throughout the month, but we still avoid leaving a precise timestamp
6686 in the state file about when we first picked the guard. Improves
6687 over the behavior introduced in 0.1.2.17.
6690 Changes in version 0.2.2.8-alpha - 2010-01-26
6691 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
6692 causing bridge relays to disappear. If you're running a bridge,
6696 - Fix a memory corruption bug on bridges that occured during the
6697 inclusion of stats data in extra-info descriptors. Also fix the
6698 interface for geoip_get_bridge_stats* to prevent similar bugs in
6699 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
6700 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
6703 - Ignore OutboundBindAddress when connecting to localhost.
6704 Connections to localhost need to come _from_ localhost, or else
6705 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
6709 Changes in version 0.2.2.7-alpha - 2010-01-19
6710 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
6711 as laying the groundwork for further relay-side performance fixes. It
6712 also starts cleaning up client behavior with respect to the EntryNodes,
6713 ExitNodes, and StrictNodes config options.
6715 This release also rotates two directory authority keys, due to a
6716 security breach of some of the Torproject servers.
6718 o Directory authority changes:
6719 - Rotate keys (both v3 identity and relay identity) for moria1
6722 o Major features (performance):
6723 - We were selecting our guards uniformly at random, and then weighting
6724 which of our guards we'd use uniformly at random. This imbalance
6725 meant that Tor clients were severely limited on throughput (and
6726 probably latency too) by the first hop in their circuit. Now we
6727 select guards weighted by currently advertised bandwidth. We also
6728 automatically discard guards picked using the old algorithm. Fixes
6729 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6730 - When choosing which cells to relay first, relays can now favor
6731 circuits that have been quiet recently, to provide lower latency
6732 for low-volume circuits. By default, relays enable or disable this
6733 feature based on a setting in the consensus. You can override
6734 this default by using the new "CircuitPriorityHalflife" config
6735 option. Design and code by Ian Goldberg, Can Tang, and Chris
6737 - Add separate per-conn write limiting to go with the per-conn read
6738 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
6739 but never per-conn write limits.
6740 - New consensus params "bwconnrate" and "bwconnburst" to let us
6741 rate-limit client connections as they enter the network. It's
6742 controlled in the consensus so we can turn it on and off for
6743 experiments. It's starting out off. Based on proposal 163.
6745 o Major features (relay selection options):
6746 - Switch to a StrictNodes config option, rather than the previous
6747 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
6748 "StrictExcludeNodes" option.
6749 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
6750 change during a config reload, mark and discard all our origin
6751 circuits. This fix should address edge cases where we change the
6752 config options and but then choose a circuit that we created before
6754 - If EntryNodes or ExitNodes are set, be more willing to use an
6755 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
6757 - Make EntryNodes config option much more aggressive even when
6758 StrictNodes is not set. Before it would prepend your requested
6759 entrynodes to your list of guard nodes, but feel free to use others
6760 after that. Now it chooses only from your EntryNodes if any of
6761 those are available, and only falls back to others if a) they're
6762 all down and b) StrictNodes is not set.
6763 - Now we refresh your entry guards from EntryNodes at each consensus
6764 fetch -- rather than just at startup and then they slowly rot as
6765 the network changes.
6768 - Stop bridge directory authorities from answering dbg-stability.txt
6769 directory queries, which would let people fetch a list of all
6770 bridge identities they track. Bugfix on 0.2.1.6-alpha.
6773 - Log a notice when we get a new control connection. Now it's easier
6774 for security-conscious users to recognize when a local application
6775 is knocking on their controller door. Suggested by bug 1196.
6776 - New config option "CircuitStreamTimeout" to override our internal
6777 timeout schedule for how many seconds until we detach a stream from
6778 a circuit and try a new circuit. If your network is particularly
6779 slow, you might want to set this to a number like 60.
6780 - New controller command "getinfo config-text". It returns the
6781 contents that Tor would write if you send it a SAVECONF command,
6782 so the controller can write the file to disk itself.
6783 - New options for SafeLogging to allow scrubbing only log messages
6784 generated while acting as a relay.
6785 - Ship the bridges spec file in the tarball too.
6786 - Avoid a mad rush at the beginning of each month when each client
6787 rotates half of its guards. Instead we spread the rotation out
6788 throughout the month, but we still avoid leaving a precise timestamp
6789 in the state file about when we first picked the guard. Improves
6790 over the behavior introduced in 0.1.2.17.
6792 o Minor bugfixes (compiling):
6793 - Fix compilation on OS X 10.3, which has a stub mlockall() but
6794 hides it. Bugfix on 0.2.2.6-alpha.
6795 - Fix compilation on Solaris by removing support for the
6796 DisableAllSwap config option. Solaris doesn't have an rlimit for
6797 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
6800 o Minor bugfixes (crashes):
6801 - Do not segfault when writing buffer stats when we haven't observed
6802 a single circuit to report about. Found by Fabian Lanze. Bugfix on
6804 - If we're in the pathological case where there's no exit bandwidth
6805 but there is non-exit bandwidth, or no guard bandwidth but there
6806 is non-guard bandwidth, don't crash during path selection. Bugfix
6808 - Fix an impossible-to-actually-trigger buffer overflow in relay
6809 descriptor generation. Bugfix on 0.1.0.15.
6811 o Minor bugfixes (privacy):
6812 - Fix an instance where a Tor directory mirror might accidentally
6813 log the IP address of a misbehaving Tor client. Bugfix on
6815 - Don't list Windows capabilities in relay descriptors. We never made
6816 use of them, and maybe it's a bad idea to publish them. Bugfix
6819 o Minor bugfixes (other):
6820 - Resolve an edge case in path weighting that could make us misweight
6821 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
6822 - Fix statistics on client numbers by country as seen by bridges that
6823 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
6824 intervals instead of variable 12-to-48-hour intervals.
6825 - After we free an internal connection structure, overwrite it
6826 with a different memory value than we use for overwriting a freed
6827 internal circuit structure. Should help with debugging. Suggested
6829 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
6833 - Remove the HSAuthorityRecordStats option that version 0 hidden
6834 service authorities could have used to track statistics of overall
6835 hidden service usage.
6838 Changes in version 0.2.1.22 - 2010-01-19
6839 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
6840 authorities -- it would tell you its whole history of bridge descriptors
6841 if you make the right directory request. This stable update also
6842 rotates two of the seven v3 directory authority keys and locations.
6844 o Directory authority changes:
6845 - Rotate keys (both v3 identity and relay identity) for moria1
6849 - Stop bridge directory authorities from answering dbg-stability.txt
6850 directory queries, which would let people fetch a list of all
6851 bridge identities they track. Bugfix on 0.2.1.6-alpha.
6854 Changes in version 0.2.1.21 - 2009-12-21
6855 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
6856 library. If you use Tor on Linux / Unix and you're getting SSL
6857 renegotiation errors, upgrading should help. We also recommend an
6858 upgrade if you're an exit relay.
6861 - Work around a security feature in OpenSSL 0.9.8l that prevents our
6862 handshake from working unless we explicitly tell OpenSSL that we
6863 are using SSL renegotiation safely. We are, of course, but OpenSSL
6864 0.9.8l won't work unless we say we are.
6865 - Avoid crashing if the client is trying to upload many bytes and the
6866 circuit gets torn down at the same time, or if the flip side
6867 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
6870 - Do not refuse to learn about authority certs and v2 networkstatus
6871 documents that are older than the latest consensus. This bug might
6872 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
6873 Spotted and fixed by xmux.
6874 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
6875 trigger platform-specific option misparsing case found by Coverity
6877 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
6878 trigger assert. Fixes bug 1173.
6881 Changes in version 0.2.2.6-alpha - 2009-11-19
6882 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
6883 support for the new lower-footprint "microdescriptor" directory design,
6884 future-proofing our consensus format against new hash functions or
6885 other changes, and an Android port. It also makes Tor compatible with
6886 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
6889 - Directory authorities can now create, vote on, and serve multiple
6890 parallel formats of directory data as part of their voting process.
6891 Partially implements Proposal 162: "Publish the consensus in
6893 - Directory authorities can now agree on and publish small summaries
6894 of router information that clients can use in place of regular
6895 server descriptors. This transition will eventually allow clients
6896 to use far less bandwidth for downloading information about the
6897 network. Begins the implementation of Proposal 158: "Clients
6898 download consensus + microdescriptors".
6899 - The directory voting system is now extensible to use multiple hash
6900 algorithms for signatures and resource selection. Newer formats
6901 are signed with SHA256, with a possibility for moving to a better
6902 hash algorithm in the future.
6903 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
6904 current and future memory pages via mlockall(). On supported
6905 platforms (modern Linux and probably BSD but not Windows or OS X),
6906 this should effectively disable any and all attempts to page out
6907 memory. This option requires that you start your Tor as root --
6908 if you use DisableAllSwap, please consider using the User option
6909 to properly reduce the privileges of your Tor.
6910 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
6911 to help Tor build correctly for Android phones.
6914 - Work around a security feature in OpenSSL 0.9.8l that prevents our
6915 handshake from working unless we explicitly tell OpenSSL that we
6916 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
6917 won't work unless we say we are.
6920 - Fix a crash bug when trying to initialize the evdns module in
6921 Libevent 2. Bugfix on 0.2.1.16-rc.
6922 - Stop logging at severity 'warn' when some other Tor client tries
6923 to establish a circuit with us using weak DH keys. It's a protocol
6924 violation, but that doesn't mean ordinary users need to hear about
6925 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
6926 - Do not refuse to learn about authority certs and v2 networkstatus
6927 documents that are older than the latest consensus. This bug might
6928 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
6929 Spotted and fixed by xmux.
6930 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
6931 - If all authorities restart at once right before a consensus vote,
6932 nobody will vote about "Running", and clients will get a consensus
6933 with no usable relays. Instead, authorities refuse to build a
6934 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
6935 - If your relay can't keep up with the number of incoming create
6936 cells, it would log one warning per failure into your logs. Limit
6937 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
6938 - Bridges now use "reject *:*" as their default exit policy. Bugfix
6939 on 0.2.0.3-alpha; fixes bug 1113.
6940 - Fix a memory leak on directory authorities during voting that was
6941 introduced in 0.2.2.1-alpha. Found via valgrind.
6944 Changes in version 0.2.1.20 - 2009-10-15
6945 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
6946 services at once, prepares for more performance improvements, and
6947 fixes a bunch of smaller bugs.
6949 The Windows and OS X bundles also include a more recent Vidalia,
6950 and switch from Privoxy to Polipo.
6952 The OS X installers are now drag and drop. It's best to un-install
6953 Tor/Vidalia and then install this new bundle, rather than upgrade. If
6954 you want to upgrade, you'll need to update the paths for Tor and Polipo
6955 in the Vidalia Settings window.
6958 - Send circuit or stream sendme cells when our window has decreased
6959 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
6960 by Karsten when testing the "reduce circuit window" performance
6961 patch. Bugfix on the 54th commit on Tor -- from July 2002,
6962 before the release of Tor 0.0.0. This is the new winner of the
6964 - Fix a remotely triggerable memory leak when a consensus document
6965 contains more than one signature from the same voter. Bugfix on
6967 - Avoid segfault in rare cases when finishing an introduction circuit
6968 as a client and finding out that we don't have an introduction key
6969 for it. Fixes bug 1073. Reported by Aaron Swartz.
6972 - Tor now reads the "circwindow" parameter out of the consensus,
6973 and uses that value for its circuit package window rather than the
6974 default of 1000 cells. Begins the implementation of proposal 168.
6976 o New directory authorities:
6977 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
6979 - Move moria1 and tonga to alternate IP addresses.
6982 - Fix a signed/unsigned compile warning in 0.2.1.19.
6983 - Fix possible segmentation fault on directory authorities. Bugfix on
6985 - Fix an extremely rare infinite recursion bug that could occur if
6986 we tried to log a message after shutting down the log subsystem.
6987 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
6988 - Fix an obscure bug where hidden services on 64-bit big-endian
6989 systems might mis-read the timestamp in v3 introduce cells, and
6990 refuse to connect back to the client. Discovered by "rotor".
6991 Bugfix on 0.2.1.6-alpha.
6992 - We were triggering a CLOCK_SKEW controller status event whenever
6993 we connect via the v2 connection protocol to any relay that has
6994 a wrong clock. Instead, we should only inform the controller when
6995 it's a trusted authority that claims our clock is wrong. Bugfix
6996 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
6997 - We were telling the controller about CHECKING_REACHABILITY and
6998 REACHABILITY_FAILED status events whenever we launch a testing
6999 circuit or notice that one has failed. Instead, only tell the
7000 controller when we want to inform the user of overall success or
7001 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7003 - Don't warn when we're using a circuit that ends with a node
7004 excluded in ExcludeExitNodes, but the circuit is not used to access
7005 the outside world. This should help fix bug 1090. Bugfix on
7007 - Work around a small memory leak in some versions of OpenSSL that
7008 stopped the memory used by the hostname TLS extension from being
7012 - Add a "getinfo status/accepted-server-descriptor" controller
7013 command, which is the recommended way for controllers to learn
7014 whether our server descriptor has been successfully received by at
7015 least on directory authority. Un-recommend good-server-descriptor
7016 getinfo and status events until we have a better design for them.
7019 Changes in version 0.2.2.5-alpha - 2009-10-11
7020 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
7023 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
7025 o Directory authorities:
7026 - Temporarily (just for this release) move dizum to an alternate
7030 Changes in version 0.2.2.4-alpha - 2009-10-10
7031 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
7032 introduces a new unit test framework, shifts directry authority
7033 addresses around to reduce the impact from recent blocking events,
7034 and fixes a few smaller bugs.
7037 - Fix several more asserts in the circuit_build_times code, for
7038 example one that causes Tor to fail to start once we have
7039 accumulated 5000 build times in the state file. Bugfixes on
7040 0.2.2.2-alpha; fixes bug 1108.
7042 o New directory authorities:
7043 - Move moria1 and Tonga to alternate IP addresses.
7046 - Log SSL state transitions at debug level during handshake, and
7047 include SSL states in error messages. This may help debug future
7048 SSL handshake issues.
7049 - Add a new "Handshake" log domain for activities that happen
7050 during the TLS handshake.
7051 - Revert to the "June 3 2009" ip-to-country file. The September one
7052 seems to have removed most US IP addresses.
7053 - Directory authorities now reject Tor relays with versions less than
7054 0.1.2.14. This step cuts out four relays from the current network,
7055 none of which are very big.
7058 - Fix a couple of smaller issues with gathering statistics. Bugfixes
7060 - Fix two memory leaks in the error case of
7061 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
7062 - Don't count one-hop circuits when we're estimating how long it
7063 takes circuits to build on average. Otherwise we'll set our circuit
7064 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
7065 - Directory authorities no longer change their opinion of, or vote on,
7066 whether a router is Running, unless they have themselves been
7067 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
7070 o Code simplifications and refactoring:
7071 - Revise our unit tests to use the "tinytest" framework, so we
7072 can run tests in their own processes, have smarter setup/teardown
7073 code, and so on. The unit test code has moved to its own
7074 subdirectory, and has been split into multiple modules.
7077 Changes in version 0.2.2.3-alpha - 2009-09-23
7078 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
7081 - Fix an overzealous assert in our new circuit build timeout code.
7082 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
7085 - If the networkstatus consensus tells us that we should use a
7086 negative circuit package window, ignore it. Otherwise we'll
7087 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
7090 Changes in version 0.2.2.2-alpha - 2009-09-21
7091 Tor 0.2.2.2-alpha introduces our latest performance improvement for
7092 clients: Tor tracks the average time it takes to build a circuit, and
7093 avoids using circuits that take too long to build. For fast connections,
7094 this feature can cut your expected latency in half. For slow or flaky
7095 connections, it could ruin your Tor experience. Let us know if it does!
7098 - Tor now tracks how long it takes to build client-side circuits
7099 over time, and adapts its timeout to local network performance.
7100 Since a circuit that takes a long time to build will also provide
7101 bad performance, we get significant latency improvements by
7102 discarding the slowest 20% of circuits. Specifically, Tor creates
7103 circuits more aggressively than usual until it has enough data
7104 points for a good timeout estimate. Implements proposal 151.
7105 We are especially looking for reports (good and bad) from users with
7106 both EDGE and broadband connections that can move from broadband
7107 to EDGE and find out if the build-time data in the .tor/state gets
7108 reset without loss of Tor usability. You should also see a notice
7109 log message telling you that Tor has reset its timeout.
7110 - Directory authorities can now vote on arbitary integer values as
7111 part of the consensus process. This is designed to help set
7112 network-wide parameters. Implements proposal 167.
7113 - Tor now reads the "circwindow" parameter out of the consensus,
7114 and uses that value for its circuit package window rather than the
7115 default of 1000 cells. Begins the implementation of proposal 168.
7118 - Fix a remotely triggerable memory leak when a consensus document
7119 contains more than one signature from the same voter. Bugfix on
7123 - Fix an extremely rare infinite recursion bug that could occur if
7124 we tried to log a message after shutting down the log subsystem.
7125 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
7126 - Fix parsing for memory or time units given without a space between
7127 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
7128 - A networkstatus vote must contain exactly one signature. Spec
7129 conformance issue. Bugfix on 0.2.0.3-alpha.
7130 - Fix an obscure bug where hidden services on 64-bit big-endian
7131 systems might mis-read the timestamp in v3 introduce cells, and
7132 refuse to connect back to the client. Discovered by "rotor".
7133 Bugfix on 0.2.1.6-alpha.
7134 - We were triggering a CLOCK_SKEW controller status event whenever
7135 we connect via the v2 connection protocol to any relay that has
7136 a wrong clock. Instead, we should only inform the controller when
7137 it's a trusted authority that claims our clock is wrong. Bugfix
7138 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
7139 - We were telling the controller about CHECKING_REACHABILITY and
7140 REACHABILITY_FAILED status events whenever we launch a testing
7141 circuit or notice that one has failed. Instead, only tell the
7142 controller when we want to inform the user of overall success or
7143 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7145 - Don't warn when we're using a circuit that ends with a node
7146 excluded in ExcludeExitNodes, but the circuit is not used to access
7147 the outside world. This should help fix bug 1090, but more problems
7148 remain. Bugfix on 0.2.1.6-alpha.
7149 - Work around a small memory leak in some versions of OpenSSL that
7150 stopped the memory used by the hostname TLS extension from being
7152 - Make our 'torify' script more portable; if we have only one of
7153 'torsocks' or 'tsocks' installed, don't complain to the user;
7154 and explain our warning about tsocks better.
7157 - Add a "getinfo status/accepted-server-descriptor" controller
7158 command, which is the recommended way for controllers to learn
7159 whether our server descriptor has been successfully received by at
7160 least on directory authority. Un-recommend good-server-descriptor
7161 getinfo and status events until we have a better design for them.
7162 - Update to the "September 4 2009" ip-to-country file.
7165 Changes in version 0.2.2.1-alpha - 2009-08-26
7166 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
7167 Tor clients to bootstrap on networks where only port 80 is reachable,
7168 makes it more straightforward to support hardware crypto accelerators,
7169 and starts the groundwork for gathering stats safely at relays.
7172 - Start the process of disabling ".exit" address notation, since it
7173 can be used for a variety of esoteric application-level attacks
7174 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
7177 o New directory authorities:
7178 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
7182 - New AccelName and AccelDir options add support for dynamic OpenSSL
7183 hardware crypto acceleration engines.
7184 - Tor now supports tunneling all of its outgoing connections over
7185 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
7186 configuration options. Code by Christopher Davis.
7189 - Send circuit or stream sendme cells when our window has decreased
7190 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
7191 by Karsten when testing the "reduce circuit window" performance
7192 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7193 before the release of Tor 0.0.0. This is the new winner of the
7196 o New options for gathering stats safely:
7197 - Directory mirrors that set "DirReqStatistics 1" write statistics
7198 about directory requests to disk every 24 hours. As compared to the
7199 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
7200 1) stats are written to disk exactly every 24 hours; 2) estimated
7201 shares of v2 and v3 requests are determined as mean values, not at
7202 the end of a measurement period; 3) unresolved requests are listed
7203 with country code '??'; 4) directories also measure download times.
7204 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
7205 number of exit streams and transferred bytes per port to disk every
7207 - Relays that set "CellStatistics 1" write statistics on how long
7208 cells spend in their circuit queues to disk every 24 hours.
7209 - Entry nodes that set "EntryStatistics 1" write statistics on the
7210 rough number and origins of connecting clients to disk every 24
7212 - Relays that write any of the above statistics to disk and set
7213 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
7214 their extra-info documents.
7217 - New --digests command-line switch to output the digests of the
7218 source files Tor was built with.
7219 - The "torify" script now uses torsocks where available.
7220 - The memarea code now uses a sentinel value at the end of each area
7221 to make sure nothing writes beyond the end of an area. This might
7222 help debug some conceivable causes of bug 930.
7223 - Time and memory units in the configuration file can now be set to
7224 fractional units. For example, "2.5 GB" is now a valid value for
7226 - Certain Tor clients (such as those behind check.torproject.org) may
7227 want to fetch the consensus in an extra early manner. To enable this
7228 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
7229 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
7230 as only certain clients who must have this information sooner should
7232 - Instead of adding the svn revision to the Tor version string, report
7233 the git commit (when we're building from a git checkout).
7236 - If any of the v3 certs we download are unparseable, we should
7237 actually notice the failure so we don't retry indefinitely. Bugfix
7238 on 0.2.0.x; reported by "rotator".
7239 - If the cached cert file is unparseable, warn but don't exit.
7240 - Fix possible segmentation fault on directory authorities. Bugfix on
7242 - When Tor fails to parse a descriptor of any kind, dump it to disk.
7243 Might help diagnosing bug 1051.
7245 o Deprecated and removed features:
7246 - The controller no longer accepts the old obsolete "addr-mappings/"
7247 or "unregistered-servers-" GETINFO values.
7248 - Hidden services no longer publish version 0 descriptors, and clients
7249 do not request or use version 0 descriptors. However, the old hidden
7250 service authorities still accept and serve version 0 descriptors
7251 when contacted by older hidden services/clients.
7252 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
7253 always on; using them is necessary for correct forward-compatible
7255 - Remove support for .noconnect style addresses. Nobody was using
7256 them, and they provided another avenue for detecting Tor users
7257 via application-level web tricks.
7259 o Packaging changes:
7260 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
7261 installer bundles. See
7262 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
7263 for details of what's new in Vidalia 0.2.3.
7264 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
7265 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
7266 configuration file, rather than the old Privoxy.
7267 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
7268 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
7269 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
7270 better compatibility with OS X 10.6, aka Snow Leopard.
7271 - OS X Vidalia Bundle: The multi-package installer is now replaced
7272 by a simple drag and drop to the /Applications folder. This change
7273 occurred with the upgrade to Vidalia 0.2.3.
7276 Changes in version 0.2.1.19 - 2009-07-28
7277 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
7278 services on Tor 0.2.1.3-alpha through 0.2.1.18.
7281 - Make accessing hidden services on 0.2.1.x work right again.
7282 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
7283 part of patch provided by "optimist".
7286 - When a relay/bridge is writing out its identity key fingerprint to
7287 the "fingerprint" file and to its logs, write it without spaces. Now
7288 it will look like the fingerprints in our bridges documentation,
7289 and confuse fewer users.
7292 - Relays no longer publish a new server descriptor if they change
7293 their MaxAdvertisedBandwidth config option but it doesn't end up
7294 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
7295 fixes bug 1026. Patch from Sebastian.
7296 - Avoid leaking memory every time we get a create cell but we have
7297 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
7298 fixes bug 1034. Reported by BarkerJr.
7301 Changes in version 0.2.1.18 - 2009-07-24
7302 Tor 0.2.1.18 lays the foundations for performance improvements,
7303 adds status events to help users diagnose bootstrap problems, adds
7304 optional authentication/authorization for hidden services, fixes a
7305 variety of potential anonymity problems, and includes a huge pile of
7306 other features and bug fixes.
7309 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
7312 Changes in version 0.2.1.17-rc - 2009-07-07
7313 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
7314 candidate for the 0.2.1.x series. It lays the groundwork for further
7315 client performance improvements, and also fixes a big bug with directory
7316 authorities that were causing them to assign Guard and Stable flags
7319 The Windows bundles also finally include the geoip database that we
7320 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
7321 should actually install Torbutton rather than giving you a cryptic
7322 failure message (oops).
7325 - Clients now use the bandwidth values in the consensus, rather than
7326 the bandwidth values in each relay descriptor. This approach opens
7327 the door to more accurate bandwidth estimates once the directory
7328 authorities start doing active measurements. Implements more of
7332 - When Tor clients restart after 1-5 days, they discard all their
7333 cached descriptors as too old, but they still use the cached
7334 consensus document. This approach is good for robustness, but
7335 bad for performance: since they don't know any bandwidths, they
7336 end up choosing at random rather than weighting their choice by
7337 speed. Fixed by the above feature of putting bandwidths in the
7338 consensus. Bugfix on 0.2.0.x.
7339 - Directory authorities were neglecting to mark relays down in their
7340 internal histories if the relays fall off the routerlist without
7341 ever being found unreachable. So there were relays in the histories
7342 that haven't been seen for eight months, and are listed as being
7343 up for eight months. This wreaked havoc on the "median wfu"
7344 and "median mtbf" calculations, in turn making Guard and Stable
7345 flags very wrong, hurting network performance. Fixes bugs 696 and
7346 969. Bugfix on 0.2.0.6-alpha.
7349 - Serve the DirPortFrontPage page even when we have been approaching
7350 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
7351 - The control port would close the connection before flushing long
7352 replies, such as the network consensus, if a QUIT command was issued
7353 before the reply had completed. Now, the control port flushes all
7354 pending replies before closing the connection. Also fixed a spurious
7355 warning when a QUIT command is issued after a malformed or rejected
7356 AUTHENTICATE command, but before the connection was closed. Patch
7357 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
7358 - When we can't find an intro key for a v2 hidden service descriptor,
7359 fall back to the v0 hidden service descriptor and log a bug message.
7360 Workaround for bug 1024.
7361 - Fix a log message that did not respect the SafeLogging option.
7365 - If we're a relay and we change our IP address, be more verbose
7366 about the reason that made us change. Should help track down
7367 further bugs for relays on dynamic IP addresses.
7370 Changes in version 0.2.0.35 - 2009-06-24
7372 - Avoid crashing in the presence of certain malformed descriptors.
7373 Found by lark, and by automated fuzzing.
7374 - Fix an edge case where a malicious exit relay could convince a
7375 controller that the client's DNS question resolves to an internal IP
7376 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7379 - Finally fix the bug where dynamic-IP relays disappear when their
7380 IP address changes: directory mirrors were mistakenly telling
7381 them their old address if they asked via begin_dir, so they
7382 never got an accurate answer about their new address, so they
7383 just vanished after a day. For belt-and-suspenders, relays that
7384 don't set Address in their config now avoid using begin_dir for
7385 all direct connections. Should fix bugs 827, 883, and 900.
7386 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7387 that would occur on some exit nodes when DNS failures and timeouts
7388 occurred in certain patterns. Fix for bug 957.
7391 - When starting with a cache over a few days old, do not leak
7392 memory for the obsolete router descriptors in it. Bugfix on
7393 0.2.0.33; fixes bug 672.
7394 - Hidden service clients didn't use a cached service descriptor that
7395 was older than 15 minutes, but wouldn't fetch a new one either,
7396 because there was already one in the cache. Now, fetch a v2
7397 descriptor unless the same descriptor was added to the cache within
7398 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7401 Changes in version 0.2.1.16-rc - 2009-06-20
7402 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
7403 a bunch of minor bugs.
7406 - Fix an edge case where a malicious exit relay could convince a
7407 controller that the client's DNS question resolves to an internal IP
7408 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7410 o Major performance improvements (on 0.2.0.x):
7411 - Disable and refactor some debugging checks that forced a linear scan
7412 over the whole server-side DNS cache. These accounted for over 50%
7413 of CPU time on a relatively busy exit node's gprof profile. Found
7415 - Disable some debugging checks that appeared in exit node profile
7419 - Update to the "June 3 2009" ip-to-country file.
7420 - Do not have tor-resolve automatically refuse all .onion addresses;
7421 if AutomapHostsOnResolve is set in your torrc, this will work fine.
7423 o Minor bugfixes (on 0.2.0.x):
7424 - Log correct error messages for DNS-related network errors on
7426 - Fix a race condition that could cause crashes or memory corruption
7427 when running as a server with a controller listening for log
7429 - Avoid crashing when we have a policy specified in a DirPolicy or
7430 SocksPolicy or ReachableAddresses option with ports set on it,
7431 and we re-load the policy. May fix bug 996.
7432 - Hidden service clients didn't use a cached service descriptor that
7433 was older than 15 minutes, but wouldn't fetch a new one either,
7434 because there was already one in the cache. Now, fetch a v2
7435 descriptor unless the same descriptor was added to the cache within
7436 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7438 o Minor bugfixes (on 0.2.1.x):
7439 - Don't warn users about low port and hibernation mix when they
7440 provide a *ListenAddress directive to fix that. Bugfix on
7442 - When switching back and forth between bridge mode, do not start
7443 gathering GeoIP data until two hours have passed.
7444 - Do not complain that the user has requested an excluded node as
7445 an exit when the node is not really an exit. This could happen
7446 because the circuit was for testing, or an introduction point.
7450 Changes in version 0.2.1.15-rc - 2009-05-25
7451 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
7452 series. It fixes a major bug on fast exit relays, as well as a variety
7455 o Major bugfixes (on 0.2.0.x):
7456 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7457 that would occur on some exit nodes when DNS failures and timeouts
7458 occurred in certain patterns. Fix for bug 957.
7460 o Minor bugfixes (on 0.2.0.x):
7461 - Actually return -1 in the error case for read_bandwidth_usage().
7462 Harmless bug, since we currently don't care about the return value
7463 anywhere. Bugfix on 0.2.0.9-alpha.
7464 - Provide a more useful log message if bug 977 (related to buffer
7465 freelists) ever reappears, and do not crash right away.
7466 - Fix an assertion failure on 64-bit platforms when we allocated
7467 memory right up to the end of a memarea, then realigned the memory
7468 one step beyond the end. Fixes a possible cause of bug 930.
7469 - Protect the count of open sockets with a mutex, so we can't
7470 corrupt it when two threads are closing or opening sockets at once.
7471 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
7472 - Don't allow a bridge to publish its router descriptor to a
7473 non-bridge directory authority. Fixes part of bug 932.
7474 - When we change to or from being a bridge, reset our counts of
7475 client usage by country. Fixes bug 932.
7476 - Fix a bug that made stream bandwidth get misreported to the
7478 - Stop using malloc_usable_size() to use more area than we had
7479 actually allocated: it was safe, but made valgrind really unhappy.
7480 - Fix a memory leak when v3 directory authorities load their keys
7481 and cert from disk. Bugfix on 0.2.0.1-alpha.
7483 o Minor bugfixes (on 0.2.1.x):
7484 - Fix use of freed memory when deciding to mark a non-addable
7485 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
7488 Changes in version 0.2.1.14-rc - 2009-04-12
7489 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
7490 series. It begins fixing some major performance problems, and also
7491 finally addresses the bug that was causing relays on dynamic IP
7492 addresses to fall out of the directory.
7495 - Clients replace entry guards that were chosen more than a few months
7496 ago. This change should significantly improve client performance,
7497 especially once more people upgrade, since relays that have been
7498 a guard for a long time are currently overloaded.
7500 o Major bugfixes (on 0.2.0):
7501 - Finally fix the bug where dynamic-IP relays disappear when their
7502 IP address changes: directory mirrors were mistakenly telling
7503 them their old address if they asked via begin_dir, so they
7504 never got an accurate answer about their new address, so they
7505 just vanished after a day. For belt-and-suspenders, relays that
7506 don't set Address in their config now avoid using begin_dir for
7507 all direct connections. Should fix bugs 827, 883, and 900.
7508 - Relays were falling out of the networkstatus consensus for
7509 part of a day if they changed their local config but the
7510 authorities discarded their new descriptor as "not sufficiently
7511 different". Now directory authorities accept a descriptor as changed
7512 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
7514 - Avoid crashing in the presence of certain malformed descriptors.
7515 Found by lark, and by automated fuzzing.
7518 - When generating circuit events with verbose nicknames for
7519 controllers, try harder to look up nicknames for routers on a
7520 circuit. (Previously, we would look in the router descriptors we had
7521 for nicknames, but not in the consensus.) Partial fix for bug 941.
7522 - If the bridge config line doesn't specify a port, assume 443.
7523 This makes bridge lines a bit smaller and easier for users to
7525 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
7526 bytes (aka 20KB/s), to match our documentation. Also update
7527 directory authorities so they always assign the Fast flag to relays
7528 with 20KB/s of capacity. Now people running relays won't suddenly
7529 find themselves not seeing any use, if the network gets faster
7531 - Update to the "April 3 2009" ip-to-country file.
7534 - Avoid trying to print raw memory to the logs when we decide to
7535 give up on downloading a given relay descriptor. Bugfix on
7537 - In tor-resolve, when the Tor client to use is specified by
7538 <hostname>:<port>, actually use the specified port rather than
7539 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
7540 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
7541 - When starting with a cache over a few days old, do not leak
7542 memory for the obsolete router descriptors in it. Bugfix on
7544 - Avoid double-free on list of successfully uploaded hidden
7545 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
7546 - Change memarea_strndup() implementation to work even when
7547 duplicating a string at the end of a page. This bug was
7548 harmless for now, but could have meant crashes later. Fix by
7549 lark. Bugfix on 0.2.1.1-alpha.
7550 - Limit uploaded directory documents to be 16M rather than 500K.
7551 The directory authorities were refusing v3 consensus votes from
7552 other authorities, since the votes are now 504K. Fixes bug 959;
7553 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
7554 - Directory authorities should never send a 503 "busy" response to
7555 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
7559 Changes in version 0.2.1.13-alpha - 2009-03-09
7560 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
7561 cleanups. We're finally getting close to a release candidate.
7564 - Correctly update the list of which countries we exclude as
7565 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
7566 lark. Bugfix on 0.2.1.6-alpha.
7568 o Minor bugfixes (on 0.2.0.x and earlier):
7569 - Automatically detect MacOSX versions earlier than 10.4.0, and
7570 disable kqueue from inside Tor when running with these versions.
7571 We previously did this from the startup script, but that was no
7572 help to people who didn't use the startup script. Resolves bug 863.
7573 - When we had picked an exit node for a connection, but marked it as
7574 "optional", and it turned out we had no onion key for the exit,
7575 stop wanting that exit and try again. This situation may not
7576 be possible now, but will probably become feasible with proposal
7577 158. Spotted by rovv. Fixes another case of bug 752.
7578 - Clients no longer cache certificates for authorities they do not
7579 recognize. Bugfix on 0.2.0.9-alpha.
7580 - When we can't transmit a DNS request due to a network error, retry
7581 it after a while, and eventually transmit a failing response to
7582 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
7583 - If the controller claimed responsibility for a stream, but that
7584 stream never finished making its connection, it would live
7585 forever in circuit_wait state. Now we close it after SocksTimeout
7586 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
7587 - Drop begin cells to a hidden service if they come from the middle
7588 of a circuit. Patch from lark.
7589 - When we erroneously receive two EXTEND cells for the same circuit
7590 ID on the same connection, drop the second. Patch from lark.
7591 - Fix a crash that occurs on exit nodes when a nameserver request
7592 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
7593 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
7595 - Do not assume that a stack-allocated character array will be
7596 64-bit aligned on platforms that demand that uint64_t access is
7597 aligned. Possible fix for bug 604.
7598 - Parse dates and IPv4 addresses in a locale- and libc-independent
7599 manner, to avoid platform-dependent behavior on malformed input.
7600 - Build correctly when configured to build outside the main source
7601 path. Patch from Michael Gold.
7602 - We were already rejecting relay begin cells with destination port
7603 of 0. Now also reject extend cells with destination port or address
7604 of 0. Suggested by lark.
7606 o Minor bugfixes (on 0.2.1.x):
7607 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
7608 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
7609 - If we're an exit node, scrub the IP address to which we are exiting
7610 in the logs. Bugfix on 0.2.1.8-alpha.
7613 - On Linux, use the prctl call to re-enable core dumps when the user
7615 - New controller event NEWCONSENSUS that lists the networkstatus
7616 lines for every recommended relay. Now controllers like Torflow
7617 can keep up-to-date on which relays they should be using.
7618 - Update to the "February 26 2009" ip-to-country file.
7621 Changes in version 0.2.0.34 - 2009-02-08
7622 Tor 0.2.0.34 features several more security-related fixes. You should
7623 upgrade, especially if you run an exit relay (remote crash) or a
7624 directory authority (remote infinite loop), or you're on an older
7625 (pre-XP) or not-recently-patched Windows (remote exploit).
7627 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
7628 have many known flaws, and nobody should be using them. You should
7629 upgrade. If you're using a Linux or BSD and its packages are obsolete,
7630 stop using those packages and upgrade anyway.
7633 - Fix an infinite-loop bug on handling corrupt votes under certain
7634 circumstances. Bugfix on 0.2.0.8-alpha.
7635 - Fix a temporary DoS vulnerability that could be performed by
7636 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7637 - Avoid a potential crash on exit nodes when processing malformed
7638 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
7639 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
7640 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
7643 - Fix compilation on systems where time_t is a 64-bit integer.
7644 Patch from Matthias Drochner.
7645 - Don't consider expiring already-closed client connections. Fixes
7646 bug 893. Bugfix on 0.0.2pre20.
7649 Changes in version 0.2.1.12-alpha - 2009-02-08
7650 Tor 0.2.1.12-alpha features several more security-related fixes. You
7651 should upgrade, especially if you run an exit relay (remote crash) or
7652 a directory authority (remote infinite loop), or you're on an older
7653 (pre-XP) or not-recently-patched Windows (remote exploit). It also
7654 includes a big pile of minor bugfixes and cleanups.
7657 - Fix an infinite-loop bug on handling corrupt votes under certain
7658 circumstances. Bugfix on 0.2.0.8-alpha.
7659 - Fix a temporary DoS vulnerability that could be performed by
7660 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7661 - Avoid a potential crash on exit nodes when processing malformed
7662 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
7665 - Let controllers actually ask for the "clients_seen" event for
7666 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
7667 reported by Matt Edman.
7668 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
7670 - Fix a bug in address parsing that was preventing bridges or hidden
7671 service targets from being at IPv6 addresses.
7672 - Solve a bug that kept hardware crypto acceleration from getting
7673 enabled when accounting was turned on. Fixes bug 907. Bugfix on
7675 - Remove a bash-ism from configure.in to build properly on non-Linux
7676 platforms. Bugfix on 0.2.1.1-alpha.
7677 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
7678 headers. Bugfix on 0.2.0.10-alpha.
7679 - Don't consider expiring already-closed client connections. Fixes
7680 bug 893. Bugfix on 0.0.2pre20.
7681 - Fix another interesting corner-case of bug 891 spotted by rovv:
7682 Previously, if two hosts had different amounts of clock drift, and
7683 one of them created a new connection with just the wrong timing,
7684 the other might decide to deprecate the new connection erroneously.
7685 Bugfix on 0.1.1.13-alpha.
7686 - Resolve a very rare crash bug that could occur when the user forced
7687 a nameserver reconfiguration during the middle of a nameserver
7688 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
7689 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
7690 Bugfix on 0.2.1.7-alpha.
7691 - If we're using bridges and our network goes away, be more willing
7692 to forgive our bridges and try again when we get an application
7693 request. Bugfix on 0.2.0.x.
7696 - Support platforms where time_t is 64 bits long. (Congratulations,
7697 NetBSD!) Patch from Matthias Drochner.
7698 - Add a 'getinfo status/clients-seen' controller command, in case
7699 controllers want to hear clients_seen events but connect late.
7702 - Disable GCC's strict alias optimization by default, to avoid the
7703 likelihood of its introducing subtle bugs whenever our code violates
7704 the letter of C99's alias rules.
7707 Changes in version 0.2.0.33 - 2009-01-21
7708 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
7709 useful to users. It also finally fixes a bug where a relay or client
7710 that's been off for many days would take a long time to bootstrap.
7712 This update also fixes an important security-related bug reported by
7713 Ilja van Sprundel. You should upgrade. (We'll send out more details
7714 about the bug once people have had some time to upgrade.)
7717 - Fix a heap-corruption bug that may be remotely triggerable on
7718 some platforms. Reported by Ilja van Sprundel.
7721 - When a stream at an exit relay is in state "resolving" or
7722 "connecting" and it receives an "end" relay cell, the exit relay
7723 would silently ignore the end cell and not close the stream. If
7724 the client never closes the circuit, then the exit relay never
7725 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
7727 - When sending CREATED cells back for a given circuit, use a 64-bit
7728 connection ID to find the right connection, rather than an addr:port
7729 combination. Now that we can have multiple OR connections between
7730 the same ORs, it is no longer possible to use addr:port to uniquely
7731 identify a connection.
7732 - Bridge relays that had DirPort set to 0 would stop fetching
7733 descriptors shortly after startup, and then briefly resume
7734 after a new bandwidth test and/or after publishing a new bridge
7735 descriptor. Bridge users that try to bootstrap from them would
7736 get a recent networkstatus but would get descriptors from up to
7737 18 hours earlier, meaning most of the descriptors were obsolete
7738 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
7739 - Prevent bridge relays from serving their 'extrainfo' document
7740 to anybody who asks, now that extrainfo docs include potentially
7741 sensitive aggregated client geoip summaries. Bugfix on
7743 - If the cached networkstatus consensus is more than five days old,
7744 discard it rather than trying to use it. In theory it could be
7745 useful because it lists alternate directory mirrors, but in practice
7746 it just means we spend many minutes trying directory mirrors that
7747 are long gone from the network. Also discard router descriptors as
7748 we load them if they are more than five days old, since the onion
7749 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
7752 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
7753 could make gcc generate non-functional binary search code. Bugfix
7755 - Build correctly on platforms without socklen_t.
7756 - Compile without warnings on solaris.
7757 - Avoid potential crash on internal error during signature collection.
7758 Fixes bug 864. Patch from rovv.
7759 - Correct handling of possible malformed authority signing key
7760 certificates with internal signature types. Fixes bug 880.
7761 Bugfix on 0.2.0.3-alpha.
7762 - Fix a hard-to-trigger resource leak when logging credential status.
7764 - When we can't initialize DNS because the network is down, do not
7765 automatically stop Tor from starting. Instead, we retry failed
7766 dns_init() every 10 minutes, and change the exit policy to reject
7767 *:* until one succeeds. Fixes bug 691.
7768 - Use 64 bits instead of 32 bits for connection identifiers used with
7769 the controller protocol, to greatly reduce risk of identifier reuse.
7770 - When we're choosing an exit node for a circuit, and we have
7771 no pending streams, choose a good general exit rather than one that
7772 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
7773 - Fix another case of assuming, when a specific exit is requested,
7774 that we know more than the user about what hosts it allows.
7775 Fixes one case of bug 752. Patch from rovv.
7776 - Clip the MaxCircuitDirtiness config option to a minimum of 10
7777 seconds. Warn the user if lower values are given in the
7778 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
7779 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
7780 user if lower values are given in the configuration. Bugfix on
7781 0.1.1.17-rc. Patch by Sebastian.
7782 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
7783 the cache because we already had a v0 descriptor with the same ID.
7784 Bugfix on 0.2.0.18-alpha.
7785 - Fix a race condition when freeing keys shared between main thread
7786 and CPU workers that could result in a memory leak. Bugfix on
7787 0.1.0.1-rc. Fixes bug 889.
7788 - Send a valid END cell back when a client tries to connect to a
7789 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
7790 840. Patch from rovv.
7791 - Check which hops rendezvous stream cells are associated with to
7792 prevent possible guess-the-streamid injection attacks from
7793 intermediate hops. Fixes another case of bug 446. Based on patch
7795 - If a broken client asks a non-exit router to connect somewhere,
7796 do not even do the DNS lookup before rejecting the connection.
7797 Fixes another case of bug 619. Patch from rovv.
7798 - When a relay gets a create cell it can't decrypt (e.g. because it's
7799 using the wrong onion key), we were dropping it and letting the
7800 client time out. Now actually answer with a destroy cell. Fixes
7801 bug 904. Bugfix on 0.0.2pre8.
7803 o Minor bugfixes (hidden services):
7804 - Do not throw away existing introduction points on SIGHUP. Bugfix on
7805 0.0.6pre1. Patch by Karsten. Fixes bug 874.
7808 - Report the case where all signatures in a detached set are rejected
7809 differently than the case where there is an error handling the
7811 - When we realize that another process has modified our cached
7812 descriptors, print out a more useful error message rather than
7813 triggering an assertion. Fixes bug 885. Patch from Karsten.
7814 - Implement the 0x20 hack to better resist DNS poisoning: set the
7815 case on outgoing DNS requests randomly, and reject responses that do
7816 not match the case correctly. This logic can be disabled with the
7817 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
7818 of servers that do not reliably preserve case in replies. See
7819 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
7821 - Check DNS replies for more matching fields to better resist DNS
7823 - Never use OpenSSL compression: it wastes RAM and CPU trying to
7824 compress cells, which are basically all encrypted, compressed, or
7828 Changes in version 0.2.1.11-alpha - 2009-01-20
7829 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
7830 week it will take a long time to bootstrap again" bug. It also fixes
7831 an important security-related bug reported by Ilja van Sprundel. You
7832 should upgrade. (We'll send out more details about the bug once people
7833 have had some time to upgrade.)
7836 - Fix a heap-corruption bug that may be remotely triggerable on
7837 some platforms. Reported by Ilja van Sprundel.
7840 - Discard router descriptors as we load them if they are more than
7841 five days old. Otherwise if Tor is off for a long time and then
7842 starts with cached descriptors, it will try to use the onion
7843 keys in those obsolete descriptors when building circuits. Bugfix
7844 on 0.2.0.x. Fixes bug 887.
7847 - Try to make sure that the version of Libevent we're running with
7848 is binary-compatible with the one we built with. May address bug
7850 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
7851 for bug 905. Bugfix on 0.2.1.7-alpha.
7852 - Add a new --enable-local-appdata configuration switch to change
7853 the default location of the datadir on win32 from APPDATA to
7854 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
7855 entirely. Patch from coderman.
7858 - Make outbound DNS packets respect the OutboundBindAddress setting.
7859 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
7860 - When our circuit fails at the first hop (e.g. we get a destroy
7861 cell back), avoid using that OR connection anymore, and also
7862 tell all the one-hop directory requests waiting for it that they
7863 should fail. Bugfix on 0.2.1.3-alpha.
7864 - In the torify(1) manpage, mention that tsocks will leak your
7868 Changes in version 0.2.1.10-alpha - 2009-01-06
7869 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
7870 would make the bridge relay not so useful if it had DirPort set to 0,
7871 and one that could let an attacker learn a little bit of information
7872 about the bridge's users), and a bug that would cause your Tor relay
7873 to ignore a circuit create request it can't decrypt (rather than reply
7874 with an error). It also fixes a wide variety of other bugs.
7877 - If the cached networkstatus consensus is more than five days old,
7878 discard it rather than trying to use it. In theory it could
7879 be useful because it lists alternate directory mirrors, but in
7880 practice it just means we spend many minutes trying directory
7881 mirrors that are long gone from the network. Helps bug 887 a bit;
7883 - Bridge relays that had DirPort set to 0 would stop fetching
7884 descriptors shortly after startup, and then briefly resume
7885 after a new bandwidth test and/or after publishing a new bridge
7886 descriptor. Bridge users that try to bootstrap from them would
7887 get a recent networkstatus but would get descriptors from up to
7888 18 hours earlier, meaning most of the descriptors were obsolete
7889 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
7890 - Prevent bridge relays from serving their 'extrainfo' document
7891 to anybody who asks, now that extrainfo docs include potentially
7892 sensitive aggregated client geoip summaries. Bugfix on
7896 - New controller event "clients_seen" to report a geoip-based summary
7897 of which countries we've seen clients from recently. Now controllers
7898 like Vidalia can show bridge operators that they're actually making
7900 - Build correctly against versions of OpenSSL 0.9.8 or later built
7901 without support for deprecated functions.
7902 - Update to the "December 19 2008" ip-to-country file.
7904 o Minor bugfixes (on 0.2.0.x):
7905 - Authorities now vote for the Stable flag for any router whose
7906 weighted MTBF is at least 5 days, regardless of the mean MTBF.
7907 - Do not remove routers as too old if we do not have any consensus
7908 document. Bugfix on 0.2.0.7-alpha.
7909 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
7910 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
7911 - When an exit relay resolves a stream address to a local IP address,
7912 do not just keep retrying that same exit relay over and
7913 over. Instead, just close the stream. Addresses bug 872. Bugfix
7914 on 0.2.0.32. Patch from rovv.
7915 - If a hidden service sends us an END cell, do not consider
7916 retrying the connection; just close it. Patch from rovv.
7917 - When we made bridge authorities stop serving bridge descriptors over
7918 unencrypted links, we also broke DirPort reachability testing for
7919 bridges. So bridges with a non-zero DirPort were printing spurious
7920 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
7921 - When a relay gets a create cell it can't decrypt (e.g. because it's
7922 using the wrong onion key), we were dropping it and letting the
7923 client time out. Now actually answer with a destroy cell. Fixes
7924 bug 904. Bugfix on 0.0.2pre8.
7925 - Squeeze 2-5% out of client performance (according to oprofile) by
7926 improving the implementation of some policy-manipulation functions.
7928 o Minor bugfixes (on 0.2.1.x):
7929 - Make get_interface_address() function work properly again; stop
7930 guessing the wrong parts of our address as our address.
7931 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
7932 send on that circuit. Otherwise we might violate the proposal-110
7933 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
7935 - When we're sending non-EXTEND cells to the first hop in a circuit,
7936 for example to use an encrypted directory connection, we don't need
7937 to use RELAY_EARLY cells: the first hop knows what kind of cell
7938 it is, and nobody else can even see the cell type. Conserving
7939 RELAY_EARLY cells makes it easier to cannibalize circuits like
7941 - Stop logging nameserver addresses in reverse order.
7942 - If we are retrying a directory download slowly over and over, do
7943 not automatically give up after the 254th failure. Bugfix on
7945 - Resume reporting accurate "stream end" reasons to the local control
7946 port. They were lost in the changes for Proposal 148. Bugfix on
7949 o Deprecated and removed features:
7950 - The old "tor --version --version" command, which would print out
7951 the subversion "Id" of most of the source files, is now removed. It
7952 turned out to be less useful than we'd expected, and harder to
7955 o Code simplifications and refactoring:
7956 - Change our header file guard macros to be less likely to conflict
7957 with system headers. Adam Langley noticed that we were conflicting
7958 with log.h on Android.
7959 - Tool-assisted documentation cleanup. Nearly every function or
7960 static variable in Tor should have its own documentation now.
7963 Changes in version 0.2.1.9-alpha - 2008-12-25
7964 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
7966 o New directory authorities:
7967 - gabelmoo (the authority run by Karsten Loesing) now has a new
7971 - Never use a connection with a mismatched address to extend a
7972 circuit, unless that connection is canonical. A canonical
7973 connection is one whose address is authenticated by the router's
7974 identity key, either in a NETINFO cell or in a router descriptor.
7975 - Avoid a possible memory corruption bug when receiving hidden service
7976 descriptors. Bugfix on 0.2.1.6-alpha.
7979 - Fix a logic error that would automatically reject all but the first
7980 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
7981 part of bug 813/868. Bug spotted by coderman.
7982 - When a stream at an exit relay is in state "resolving" or
7983 "connecting" and it receives an "end" relay cell, the exit relay
7984 would silently ignore the end cell and not close the stream. If
7985 the client never closes the circuit, then the exit relay never
7986 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
7988 - When we can't initialize DNS because the network is down, do not
7989 automatically stop Tor from starting. Instead, retry failed
7990 dns_init() every 10 minutes, and change the exit policy to reject
7991 *:* until one succeeds. Fixes bug 691.
7994 - Give a better error message when an overzealous init script says
7995 "sudo -u username tor --user username". Makes Bug 882 easier for
7997 - When a directory authority gives us a new guess for our IP address,
7998 log which authority we used. Hopefully this will help us debug
7999 the recent complaints about bad IP address guesses.
8000 - Detect svn revision properly when we're using git-svn.
8001 - Try not to open more than one descriptor-downloading connection
8002 to an authority at once. This should reduce load on directory
8003 authorities. Fixes bug 366.
8004 - Add cross-certification to newly generated certificates, so that
8005 a signing key is enough information to look up a certificate.
8006 Partial implementation of proposal 157.
8007 - Start serving certificates by <identity digest, signing key digest>
8008 pairs. Partial implementation of proposal 157.
8009 - Clients now never report any stream end reason except 'MISC'.
8010 Implements proposal 148.
8011 - On platforms with a maximum syslog string length, truncate syslog
8012 messages to that length ourselves, rather than relying on the
8013 system to do it for us.
8014 - Optimize out calls to time(NULL) that occur for every IO operation,
8015 or for every cell. On systems where time() is a slow syscall,
8016 this fix will be slightly helpful.
8017 - Exit servers can now answer resolve requests for ip6.arpa addresses.
8018 - When we download a descriptor that we then immediately (as
8019 a directory authority) reject, do not retry downloading it right
8020 away. Should save some bandwidth on authorities. Fix for bug
8021 888. Patch by Sebastian Hahn.
8022 - When a download gets us zero good descriptors, do not notify
8023 Tor that new directory information has arrived.
8024 - Avoid some nasty corner cases in the logic for marking connections
8025 as too old or obsolete or noncanonical for circuits. Partial
8028 o Minor features (controller):
8029 - New CONSENSUS_ARRIVED event to note when a new consensus has
8030 been fetched and validated.
8031 - When we realize that another process has modified our cached
8032 descriptors file, print out a more useful error message rather
8033 than triggering an assertion. Fixes bug 885. Patch from Karsten.
8034 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
8035 controllers to prevent SIGHUP from reloading the
8036 configuration. Fixes bug 856.
8039 - Resume using the correct "REASON=" stream when telling the
8040 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
8041 - When a canonical connection appears later in our internal list
8042 than a noncanonical one for a given OR ID, always use the
8043 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
8045 - Clip the MaxCircuitDirtiness config option to a minimum of 10
8046 seconds. Warn the user if lower values are given in the
8047 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
8048 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
8049 user if lower values are given in the configuration. Bugfix on
8050 0.1.1.17-rc. Patch by Sebastian.
8051 - Fix a race condition when freeing keys shared between main thread
8052 and CPU workers that could result in a memory leak. Bugfix on
8053 0.1.0.1-rc. Fixes bug 889.
8055 o Minor bugfixes (hidden services):
8056 - Do not throw away existing introduction points on SIGHUP (bugfix on
8057 0.0.6pre1); also, do not stall hidden services because we're
8058 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
8059 by John Brooks. Patch by Karsten. Fixes bug 874.
8060 - Fix a memory leak when we decline to add a v2 rendezvous
8061 descriptor to the cache because we already had a v0 descriptor
8062 with the same ID. Bugfix on 0.2.0.18-alpha.
8064 o Deprecated and removed features:
8065 - RedirectExits has been removed. It was deprecated since
8067 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
8068 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
8069 - Cell pools are now always enabled; --disable-cell-pools is ignored.
8071 o Code simplifications and refactoring:
8072 - Rename the confusing or_is_obsolete field to the more appropriate
8073 is_bad_for_new_circs, and move it to or_connection_t where it
8075 - Move edge-only flags from connection_t to edge_connection_t: not
8076 only is this better coding, but on machines of plausible alignment,
8077 it should save 4-8 bytes per connection_t. "Every little bit helps."
8078 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
8079 for consistency; keep old option working for backward compatibility.
8080 - Simplify the code for finding connections to use for a circuit.
8083 Changes in version 0.2.1.8-alpha - 2008-12-08
8084 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
8085 builds better on unusual platforms like Solaris and old OS X, and
8086 fixes a variety of other issues.
8089 - New DirPortFrontPage option that takes an html file and publishes
8090 it as "/" on the DirPort. Now relay operators can provide a
8091 disclaimer without needing to set up a separate webserver. There's
8092 a sample disclaimer in contrib/tor-exit-notice.html.
8095 - When the client is choosing entry guards, now it selects at most
8096 one guard from a given relay family. Otherwise we could end up with
8097 all of our entry points into the network run by the same operator.
8098 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
8101 - Fix a DOS opportunity during the voting signature collection process
8102 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8103 - Fix a possible segfault when establishing an exit connection. Bugfix
8107 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
8109 - Made Tor a little less aggressive about deleting expired
8110 certificates. Partial fix for bug 854.
8111 - Stop doing unaligned memory access that generated bus errors on
8112 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
8113 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
8114 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
8115 - Make USR2 log-level switch take effect immediately. Bugfix on
8117 - If one win32 nameserver fails to get added, continue adding the
8118 rest, and don't automatically fail.
8119 - Use fcntl() for locking when flock() is not available. Should fix
8120 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
8121 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
8122 could make gcc generate non-functional binary search code. Bugfix
8124 - Build correctly on platforms without socklen_t.
8125 - Avoid potential crash on internal error during signature collection.
8126 Fixes bug 864. Patch from rovv.
8127 - Do not use C's stdio library for writing to log files. This will
8128 improve logging performance by a minute amount, and will stop
8129 leaking fds when our disk is full. Fixes bug 861.
8130 - Stop erroneous use of O_APPEND in cases where we did not in fact
8131 want to re-seek to the end of a file before every last write().
8132 - Correct handling of possible malformed authority signing key
8133 certificates with internal signature types. Fixes bug 880. Bugfix
8135 - Fix a hard-to-trigger resource leak when logging credential status.
8139 - Directory mirrors no longer fetch the v1 directory or
8140 running-routers files. They are obsolete, and nobody asks for them
8141 anymore. This is the first step to making v1 authorities obsolete.
8143 o Minor features (controller):
8144 - Return circuit purposes in response to GETINFO circuit-status. Fixes
8148 Changes in version 0.2.0.32 - 2008-11-20
8149 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
8150 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8151 a smaller security flaw that might allow an attacker to access local
8152 services, further improves hidden service performance, and fixes a
8153 variety of other issues.
8156 - The "User" and "Group" config options did not clear the
8157 supplementary group entries for the Tor process. The "User" option
8158 is now more robust, and we now set the groups to the specified
8159 user's primary group. The "Group" option is now ignored. For more
8160 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8161 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8162 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
8163 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8164 consistently obeyed: if an exit relay refuses a stream because its
8165 exit policy doesn't allow it, we would remember what IP address
8166 the relay said the destination address resolves to, even if it's
8167 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8170 - Fix a DOS opportunity during the voting signature collection process
8171 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8173 o Major bugfixes (hidden services):
8174 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8175 we were failing the whole hidden service request when the v0
8176 descriptor fetch fails, even if the v2 fetch is still pending and
8177 might succeed. Similarly, if the last v2 fetch fails, we were
8178 failing the whole hidden service request even if a v0 fetch is
8179 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8180 - When extending a circuit to a hidden service directory to upload a
8181 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8182 requests failed, because the router descriptor has not been
8183 downloaded yet. In these cases, do not attempt to upload the
8184 rendezvous descriptor, but wait until the router descriptor is
8185 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
8186 descriptor from a hidden service directory for which the router
8187 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
8191 - Fix several infrequent memory leaks spotted by Coverity.
8192 - When testing for libevent functions, set the LDFLAGS variable
8193 correctly. Found by Riastradh.
8194 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8195 bootstrapping with tunneled directory connections. Bugfix on
8196 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8197 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8198 and we know that server B rejects most-but-not all connections to
8199 port 80, we would previously reject the connection. Now, we assume
8200 the user knows what they were asking for. Fixes bug 752. Bugfix
8201 on 0.0.9rc5. Diagnosed by BarkerJr.
8202 - If we overrun our per-second write limits a little, count this as
8203 having used up our write allocation for the second, and choke
8204 outgoing directory writes. Previously, we had only counted this when
8205 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
8206 Bugfix on 0.2.0.x (??).
8207 - Remove the old v2 directory authority 'lefkada' from the default
8208 list. It has been gone for many months.
8209 - Stop doing unaligned memory access that generated bus errors on
8210 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
8211 - Make USR2 log-level switch take effect immediately. Bugfix on
8214 o Minor bugfixes (controller):
8215 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
8216 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
8219 Changes in version 0.2.1.7-alpha - 2008-11-08
8220 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
8221 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8222 a smaller security flaw that might allow an attacker to access local
8223 services, adds better defense against DNS poisoning attacks on exit
8224 relays, further improves hidden service performance, and fixes a
8225 variety of other issues.
8228 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8229 consistently obeyed: if an exit relay refuses a stream because its
8230 exit policy doesn't allow it, we would remember what IP address
8231 the relay said the destination address resolves to, even if it's
8232 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8233 - The "User" and "Group" config options did not clear the
8234 supplementary group entries for the Tor process. The "User" option
8235 is now more robust, and we now set the groups to the specified
8236 user's primary group. The "Group" option is now ignored. For more
8237 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8238 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8239 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
8240 - Do not use or believe expired v3 authority certificates. Patch
8241 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
8244 - Now NodeFamily and MyFamily config options allow spaces in
8245 identity fingerprints, so it's easier to paste them in.
8246 Suggested by Lucky Green.
8247 - Implement the 0x20 hack to better resist DNS poisoning: set the
8248 case on outgoing DNS requests randomly, and reject responses that do
8249 not match the case correctly. This logic can be disabled with the
8250 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
8251 of servers that do not reliably preserve case in replies. See
8252 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
8254 - Preserve case in replies to DNSPort requests in order to support
8255 the 0x20 hack for resisting DNS poisoning attacks.
8257 o Hidden service performance improvements:
8258 - When the client launches an introduction circuit, retry with a
8259 new circuit after 30 seconds rather than 60 seconds.
8260 - Launch a second client-side introduction circuit in parallel
8261 after a delay of 15 seconds (based on work by Christian Wilms).
8262 - Hidden services start out building five intro circuits rather
8263 than three, and when the first three finish they publish a service
8264 descriptor using those. Now we publish our service descriptor much
8265 faster after restart.
8268 - Minor fix in the warning messages when you're having problems
8269 bootstrapping; also, be more forgiving of bootstrap problems when
8270 we're still making incremental progress on a given bootstrap phase.
8271 - When we're choosing an exit node for a circuit, and we have
8272 no pending streams, choose a good general exit rather than one that
8273 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
8274 - Send a valid END cell back when a client tries to connect to a
8275 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
8276 840. Patch from rovv.
8277 - If a broken client asks a non-exit router to connect somewhere,
8278 do not even do the DNS lookup before rejecting the connection.
8279 Fixes another case of bug 619. Patch from rovv.
8280 - Fix another case of assuming, when a specific exit is requested,
8281 that we know more than the user about what hosts it allows.
8282 Fixes another case of bug 752. Patch from rovv.
8283 - Check which hops rendezvous stream cells are associated with to
8284 prevent possible guess-the-streamid injection attacks from
8285 intermediate hops. Fixes another case of bug 446. Based on patch
8287 - Avoid using a negative right-shift when comparing 32-bit
8288 addresses. Possible fix for bug 845 and bug 811.
8289 - Make the assert_circuit_ok() function work correctly on circuits that
8290 have already been marked for close.
8291 - Fix read-off-the-end-of-string error in unit tests when decoding
8292 introduction points.
8293 - Fix uninitialized size field for memory area allocation: may improve
8294 memory performance during directory parsing.
8295 - Treat duplicate certificate fetches as failures, so that we do
8296 not try to re-fetch an expired certificate over and over and over.
8297 - Do not say we're fetching a certificate when we'll in fact skip it
8298 because of a pending download.
8301 Changes in version 0.2.1.6-alpha - 2008-09-30
8302 Tor 0.2.1.6-alpha further improves performance and robustness of
8303 hidden services, starts work on supporting per-country relay selection,
8304 and fixes a variety of smaller issues.
8307 - Implement proposal 121: make it possible to build hidden services
8308 that only certain clients are allowed to connect to. This is
8309 enforced at several points, so that unauthorized clients are unable
8310 to send INTRODUCE cells to the service, or even (depending on the
8311 type of authentication) to learn introduction points. This feature
8312 raises the bar for certain kinds of active attacks against hidden
8313 services. Code by Karsten Loesing.
8314 - Relays now store and serve v2 hidden service descriptors by default,
8315 i.e., the new default value for HidServDirectoryV2 is 1. This is
8316 the last step in proposal 114, which aims to make hidden service
8317 lookups more reliable.
8318 - Start work to allow node restrictions to include country codes. The
8319 syntax to exclude nodes in a country with country code XX is
8320 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
8321 refinement to decide what config options should take priority if
8322 you ask to both use a particular node and exclude it.
8323 - Allow ExitNodes list to include IP ranges and country codes, just
8324 like the Exclude*Nodes lists. Patch from Robert Hogan.
8327 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
8328 Tor to fail to start if you had it configured to use a bridge
8329 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
8330 - When extending a circuit to a hidden service directory to upload a
8331 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8332 requests failed, because the router descriptor had not been
8333 downloaded yet. In these cases, we now wait until the router
8334 descriptor is downloaded, and then retry. Likewise, clients
8335 now skip over a hidden service directory if they don't yet have
8336 its router descriptor, rather than futilely requesting it and
8337 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
8339 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8340 we were failing the whole hidden service request when the v0
8341 descriptor fetch fails, even if the v2 fetch is still pending and
8342 might succeed. Similarly, if the last v2 fetch fails, we were
8343 failing the whole hidden service request even if a v0 fetch is
8344 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8345 - DNS replies need to have names matching their requests, but
8346 these names should be in the questions section, not necessarily
8347 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
8350 - Update to the "September 1 2008" ip-to-country file.
8351 - Allow ports 465 and 587 in the default exit policy again. We had
8352 rejected them in 0.1.0.15, because back in 2005 they were commonly
8353 misconfigured and ended up as spam targets. We hear they are better
8354 locked down these days.
8355 - Use a lockfile to make sure that two Tor processes are not
8356 simultaneously running with the same datadir.
8357 - Serve the latest v3 networkstatus consensus via the control
8358 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
8359 - Better logging about stability/reliability calculations on directory
8361 - Drop the requirement to have an open dir port for storing and
8362 serving v2 hidden service descriptors.
8363 - Directory authorities now serve a /tor/dbg-stability.txt URL to
8364 help debug WFU and MTBF calculations.
8365 - Implement most of Proposal 152: allow specialized servers to permit
8366 single-hop circuits, and clients to use those servers to build
8367 single-hop circuits when using a specialized controller. Patch
8368 from Josh Albrecht. Resolves feature request 768.
8369 - Add a -p option to tor-resolve for specifying the SOCKS port: some
8370 people find host:port too confusing.
8371 - Make TrackHostExit mappings expire a while after their last use, not
8372 after their creation. Patch from Robert Hogan.
8373 - Provide circuit purposes along with circuit events to the controller.
8376 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
8378 - Fixed some memory leaks -- some quite frequent, some almost
8379 impossible to trigger -- based on results from Coverity.
8380 - When testing for libevent functions, set the LDFLAGS variable
8381 correctly. Found by Riastradh.
8382 - Fix an assertion bug in parsing policy-related options; possible fix
8384 - Catch and report a few more bootstrapping failure cases when Tor
8385 fails to establish a TCP connection. Cleanup on 0.2.1.x.
8386 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8387 bootstrapping with tunneled directory connections. Bugfix on
8388 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8389 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8390 and we know that server B rejects most-but-not all connections to
8391 port 80, we would previously reject the connection. Now, we assume
8392 the user knows what they were asking for. Fixes bug 752. Bugfix
8393 on 0.0.9rc5. Diagnosed by BarkerJr.
8394 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
8395 service directories if they have no advertised dir port. Bugfix
8397 - If we overrun our per-second write limits a little, count this as
8398 having used up our write allocation for the second, and choke
8399 outgoing directory writes. Previously, we had only counted this when
8400 we had met our limits precisely. Fixes bug 824. Patch by rovv.
8401 Bugfix on 0.2.0.x (??).
8402 - Avoid a "0 divided by 0" calculation when calculating router uptime
8403 at directory authorities. Bugfix on 0.2.0.8-alpha.
8404 - Make DNS resolved controller events into "CLOSED", not
8405 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
8407 - Fix a bug where an unreachable relay would establish enough
8408 reachability testing circuits to do a bandwidth test -- if
8409 we already have a connection to the middle hop of the testing
8410 circuit, then it could establish the last hop by using the existing
8411 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
8412 circuits no longer use entry guards in 0.2.1.3-alpha.
8413 - If we have correct permissions on $datadir, we complain to stdout
8414 and fail to start. But dangerous permissions on
8415 $datadir/cached-status/ would cause us to open a log and complain
8416 there. Now complain to stdout and fail to start in both cases. Fixes
8417 bug 820, reported by seeess.
8418 - Remove the old v2 directory authority 'lefkada' from the default
8419 list. It has been gone for many months.
8421 o Code simplifications and refactoring:
8422 - Revise the connection_new functions so that a more typesafe variant
8423 exists. This will work better with Coverity, and let us find any
8424 actual mistakes we're making here.
8425 - Refactor unit testing logic so that dmalloc can be used sensibly
8426 with unit tests to check for memory leaks.
8427 - Move all hidden-service related fields from connection and circuit
8428 structure to substructures: this way they won't eat so much memory.
8431 Changes in version 0.2.0.31 - 2008-09-03
8432 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
8433 a big bug we're seeing where in rare cases traffic from one Tor stream
8434 gets mixed into another stream, and fixes a variety of smaller issues.
8437 - Make sure that two circuits can never exist on the same connection
8438 with the same circuit ID, even if one is marked for close. This
8439 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
8440 - Relays now reject risky extend cells: if the extend cell includes
8441 a digest of all zeroes, or asks to extend back to the relay that
8442 sent the extend cell, tear down the circuit. Ideas suggested
8444 - If not enough of our entry guards are available so we add a new
8445 one, we might use the new one even if it overlapped with the
8446 current circuit's exit relay (or its family). Anonymity bugfix
8447 pointed out by rovv.
8450 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8451 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8452 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8453 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8454 - Pick size of default geoip filename string correctly on windows.
8455 Fixes bug 806. Bugfix on 0.2.0.30.
8456 - Make the autoconf script accept the obsolete --with-ssl-dir
8457 option as an alias for the actually-working --with-openssl-dir
8458 option. Fix the help documentation to recommend --with-openssl-dir.
8459 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8460 - When using the TransPort option on OpenBSD, and using the User
8461 option to change UID and drop privileges, make sure to open
8462 /dev/pf before dropping privileges. Fixes bug 782. Patch from
8463 Christopher Davis. Bugfix on 0.1.2.1-alpha.
8464 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8465 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8466 on the client side when connecting to a hidden service. Bugfix
8467 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8468 - When closing an application-side connection because its circuit is
8469 getting torn down, generate the stream event correctly. Bugfix on
8470 0.1.2.x. Anonymous patch.
8473 Changes in version 0.2.1.5-alpha - 2008-08-31
8474 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
8475 in a lot of the infrastructure for adding authorization to hidden
8476 services, lays the groundwork for having clients read their load
8477 balancing information out of the networkstatus consensus rather than
8478 the individual router descriptors, addresses two potential anonymity
8479 issues, and fixes a variety of smaller issues.
8482 - Convert many internal address representations to optionally hold
8484 - Generate and accept IPv6 addresses in many protocol elements.
8485 - Make resolver code handle nameservers located at ipv6 addresses.
8486 - Begin implementation of proposal 121 ("Client authorization for
8487 hidden services"): configure hidden services with client
8488 authorization, publish descriptors for them, and configure
8489 authorization data for hidden services at clients. The next
8490 step is to actually access hidden services that perform client
8492 - More progress toward proposal 141: Network status consensus
8493 documents and votes now contain bandwidth information for each
8494 router and a summary of that router's exit policy. Eventually this
8495 will be used by clients so that they do not have to download every
8496 known descriptor before building circuits.
8498 o Major bugfixes (on 0.2.0.x and before):
8499 - When sending CREATED cells back for a given circuit, use a 64-bit
8500 connection ID to find the right connection, rather than an addr:port
8501 combination. Now that we can have multiple OR connections between
8502 the same ORs, it is no longer possible to use addr:port to uniquely
8503 identify a connection.
8504 - Relays now reject risky extend cells: if the extend cell includes
8505 a digest of all zeroes, or asks to extend back to the relay that
8506 sent the extend cell, tear down the circuit. Ideas suggested
8508 - If not enough of our entry guards are available so we add a new
8509 one, we might use the new one even if it overlapped with the
8510 current circuit's exit relay (or its family). Anonymity bugfix
8511 pointed out by rovv.
8514 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8515 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8516 - When using the TransPort option on OpenBSD, and using the User
8517 option to change UID and drop privileges, make sure to open /dev/pf
8518 before dropping privileges. Fixes bug 782. Patch from Christopher
8519 Davis. Bugfix on 0.1.2.1-alpha.
8520 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8521 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8522 - Add a missing safe_str() call for a debug log message.
8523 - Use 64 bits instead of 32 bits for connection identifiers used with
8524 the controller protocol, to greatly reduce risk of identifier reuse.
8525 - Make the autoconf script accept the obsolete --with-ssl-dir
8526 option as an alias for the actually-working --with-openssl-dir
8527 option. Fix the help documentation to recommend --with-openssl-dir.
8528 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8531 - Rate-limit too-many-sockets messages: when they happen, they happen
8532 a lot. Resolves bug 748.
8533 - Resist DNS poisoning a little better by making sure that names in
8534 answer sections match.
8535 - Print the SOCKS5 error message string as well as the error code
8536 when a tor-resolve request fails. Patch from Jacob.
8539 Changes in version 0.2.1.4-alpha - 2008-08-04
8540 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
8543 - The address part of exit policies was not correctly written
8544 to router descriptors. This generated router descriptors that failed
8545 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
8547 - Tor triggered a false assert when extending a circuit to a relay
8548 but we already have a connection open to that relay. Noticed by
8549 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
8552 - Fix a hidden service logging bug: in some edge cases, the router
8553 descriptor of a previously picked introduction point becomes
8554 obsolete and we need to give up on it rather than continually
8555 complaining that it has become obsolete. Observed by xiando. Bugfix
8559 - Take out the TestVia config option, since it was a workaround for
8560 a bug that was fixed in Tor 0.1.1.21.
8563 Changes in version 0.2.1.3-alpha - 2008-08-03
8564 Tor 0.2.1.3-alpha implements most of the pieces to prevent
8565 infinite-length circuit attacks (see proposal 110); fixes a bug that
8566 might cause exit relays to corrupt streams they send back; allows
8567 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
8568 ExcludeExitNodes config options; and fixes a big pile of bugs.
8570 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
8571 - Send a bootstrap problem "warn" event on the first problem if the
8572 reason is NO_ROUTE (that is, our network is down).
8575 - Implement most of proposal 110: The first K cells to be sent
8576 along a circuit are marked as special "early" cells; only K "early"
8577 cells will be allowed. Once this code is universal, we can block
8578 certain kinds of DOS attack by requiring that EXTEND commands must
8579 be sent using an "early" cell.
8582 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8583 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8584 on the client side when connecting to a hidden service. Bugfix
8585 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8586 - Ensure that two circuits can never exist on the same connection
8587 with the same circuit ID, even if one is marked for close. This
8588 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
8591 - When relays do their initial bandwidth measurement, don't limit
8592 to just our entry guards for the test circuits. Otherwise we tend
8593 to have multiple test circuits going through a single entry guard,
8594 which makes our bandwidth test less accurate. Fixes part of bug 654;
8595 patch contributed by Josh Albrecht.
8596 - Add an ExcludeExitNodes option so users can list a set of nodes
8597 that should be be excluded from the exit node position, but
8598 allowed elsewhere. Implements proposal 151.
8599 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
8600 ExcludeNodes and ExcludeExitNodes lists.
8601 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
8602 be more efficient. Formerly it was quadratic in the number of
8603 servers; now it should be linear. Fixes bug 509.
8604 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
8605 and n_conn_id_digest fields into a separate structure that's
8606 only needed when the circuit has not yet attached to an n_conn.
8609 - Change the contrib/tor.logrotate script so it makes the new
8610 logs as "_tor:_tor" rather than the default, which is generally
8611 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
8612 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8613 warnings (occasionally), but it can also cause the compiler to
8614 eliminate error-checking code. Suggested by Peter Gutmann.
8615 - When a hidden service is giving up on an introduction point candidate
8616 that was not included in the last published rendezvous descriptor,
8617 don't reschedule publication of the next descriptor. Fixes bug 763.
8619 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
8620 HiddenServiceExcludeNodes as obsolete: they never worked properly,
8621 and nobody claims to be using them. Fixes bug 754. Bugfix on
8622 0.1.0.1-rc. Patch from Christian Wilms.
8623 - Fix a small alignment and memory-wasting bug on buffer chunks.
8626 o Minor bugfixes (controller):
8627 - When closing an application-side connection because its circuit
8628 is getting torn down, generate the stream event correctly.
8629 Bugfix on 0.1.2.x. Anonymous patch.
8632 - Remove all backward-compatibility code to support relays running
8633 versions of Tor so old that they no longer work at all on the
8637 Changes in version 0.2.0.30 - 2008-07-15
8639 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8640 warnings (occasionally), but it can also cause the compiler to
8641 eliminate error-checking code. Suggested by Peter Gutmann.
8644 Changes in version 0.2.0.29-rc - 2008-07-08
8645 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
8646 hidden-service performance bugs, and fixes a bunch of smaller bugs.
8649 - If you have more than one bridge but don't know their keys,
8650 you would only launch a request for the descriptor of the first one
8651 on your list. (Tor considered launching requests for the others, but
8652 found that it already had a connection on the way for $0000...0000
8653 so it didn't open another.) Bugfix on 0.2.0.x.
8654 - If you have more than one bridge but don't know their keys, and the
8655 connection to one of the bridges failed, you would cancel all
8656 pending bridge connections. (After all, they all have the same
8657 digest.) Bugfix on 0.2.0.x.
8658 - When a hidden service was trying to establish an introduction point,
8659 and Tor had built circuits preemptively for such purposes, we
8660 were ignoring all the preemptive circuits and launching a new one
8661 instead. Bugfix on 0.2.0.14-alpha.
8662 - When a hidden service was trying to establish an introduction point,
8663 and Tor *did* manage to reuse one of the preemptively built
8664 circuits, it didn't correctly remember which one it used,
8665 so it asked for another one soon after, until there were no
8666 more preemptive circuits, at which point it launched one from
8667 scratch. Bugfix on 0.0.9.x.
8668 - Make directory servers include the X-Your-Address-Is: http header in
8669 their responses even for begin_dir conns. Now clients who only
8670 ever use begin_dir connections still have a way to learn their IP
8671 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
8674 - Fix a macro/CPP interaction that was confusing some compilers:
8675 some GCCs don't like #if/#endif pairs inside macro arguments.
8677 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
8678 Fixes bug 704; fix from Steven Murdoch.
8679 - When opening /dev/null in finish_daemonize(), do not pass the
8680 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
8681 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
8682 - Correctly detect transparent proxy support on Linux hosts that
8683 require in.h to be included before netfilter_ipv4.h. Patch
8685 - Disallow session resumption attempts during the renegotiation
8686 stage of the v2 handshake protocol. Clients should never be trying
8687 session resumption at this point, but apparently some did, in
8688 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
8689 found by Geoff Goodell.
8692 Changes in version 0.2.1.2-alpha - 2008-06-20
8693 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
8694 make it easier to set up your own private Tor network; fixes several
8695 big bugs with using more than one bridge relay; fixes a big bug with
8696 offering hidden services quickly after Tor starts; and uses a better
8697 API for reporting potential bootstrapping problems to the controller.
8700 - New TestingTorNetwork config option to allow adjustment of
8701 previously constant values that, while reasonable, could slow
8702 bootstrapping. Implements proposal 135. Patch from Karsten.
8705 - If you have more than one bridge but don't know their digests,
8706 you would only learn a request for the descriptor of the first one
8707 on your list. (Tor considered launching requests for the others, but
8708 found that it already had a connection on the way for $0000...0000
8709 so it didn't open another.) Bugfix on 0.2.0.x.
8710 - If you have more than one bridge but don't know their digests,
8711 and the connection to one of the bridges failed, you would cancel
8712 all pending bridge connections. (After all, they all have the
8713 same digest.) Bugfix on 0.2.0.x.
8714 - When establishing a hidden service, introduction points that
8715 originate from cannibalized circuits are completely ignored and not
8716 included in rendezvous service descriptors. This might be another
8717 reason for delay in making a hidden service available. Bugfix
8718 from long ago (0.0.9.x?)
8721 - Allow OpenSSL to use dynamic locks if it wants.
8722 - When building a consensus, do not include routers that are down.
8723 This will cut down 30% to 40% on consensus size. Implements
8725 - In directory authorities' approved-routers files, allow
8726 fingerprints with or without space.
8727 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
8728 controller can query our current bootstrap state in case it attaches
8729 partway through and wants to catch up.
8730 - Send an initial "Starting" bootstrap status event, so we have a
8731 state to start out in.
8734 - Asking for a conditional consensus at .../consensus/<fingerprints>
8735 would crash a dirserver if it did not already have a
8736 consensus. Bugfix on 0.2.1.1-alpha.
8737 - Clean up some macro/CPP interactions: some GCC versions don't like
8738 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
8741 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
8742 - Directory authorities shouldn't complain about bootstrapping
8743 problems just because they do a lot of reachability testing and
8744 some of the connection attempts fail.
8745 - Start sending "count" and "recommendation" key/value pairs in
8746 bootstrap problem status events, so the controller can hear about
8747 problems even before Tor decides they're worth reporting for sure.
8748 - If you're using bridges, generate "bootstrap problem" warnings
8749 as soon as you run out of working bridges, rather than waiting
8750 for ten failures -- which will never happen if you have less than
8752 - If we close our OR connection because there's been a circuit
8753 pending on it for too long, we were telling our bootstrap status
8754 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
8757 Changes in version 0.2.1.1-alpha - 2008-06-13
8758 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
8759 were making the Tor process bloat especially on Linux; makes our TLS
8760 handshake blend in better; sends "bootstrap phase" status events to
8761 the controller, so it can keep the user informed of progress (and
8762 problems) fetching directory information and establishing circuits;
8763 and adds a variety of smaller features.
8766 - More work on making our TLS handshake blend in: modify the list
8767 of ciphers advertised by OpenSSL in client mode to even more
8768 closely resemble a common web browser. We cheat a little so that
8769 we can advertise ciphers that the locally installed OpenSSL doesn't
8771 - Start sending "bootstrap phase" status events to the controller,
8772 so it can keep the user informed of progress fetching directory
8773 information and establishing circuits. Also inform the controller
8774 if we think we're stuck at a particular bootstrap phase. Implements
8776 - Resume using OpenSSL's RAND_poll() for better (and more portable)
8777 cross-platform entropy collection again. We used to use it, then
8778 stopped using it because of a bug that could crash systems that
8779 called RAND_poll when they had a lot of fds open. It looks like the
8780 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
8781 at startup, and to call RAND_poll() when we reseed later only if
8782 we have a non-buggy OpenSSL version.
8785 - When we choose to abandon a new entry guard because we think our
8786 older ones might be better, close any circuits pending on that
8787 new entry guard connection. This fix should make us recover much
8788 faster when our network is down and then comes back. Bugfix on
8789 0.1.2.8-beta; found by lodger.
8791 o Memory fixes and improvements:
8792 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
8793 to avoid unused RAM in buffer chunks and memory pools.
8794 - Speed up parsing and cut down on memory fragmentation by using
8795 stack-style allocations for parsing directory objects. Previously,
8796 this accounted for over 40% of allocations from within Tor's code
8797 on a typical directory cache.
8798 - Use a Bloom filter rather than a digest-based set to track which
8799 descriptors we need to keep around when we're cleaning out old
8800 router descriptors. This speeds up the computation significantly,
8801 and may reduce fragmentation.
8802 - Reduce the default smartlist size from 32 to 16; it turns out that
8803 most smartlists hold around 8-12 elements tops.
8804 - Make dumpstats() log the fullness and size of openssl-internal
8806 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
8807 patch to their OpenSSL, turn it on to save memory on servers. This
8808 patch will (with any luck) get included in a mainline distribution
8810 - Never use OpenSSL compression: it wastes RAM and CPU trying to
8811 compress cells, which are basically all encrypted, compressed,
8815 - Stop reloading the router list from disk for no reason when we
8816 run out of reachable directory mirrors. Once upon a time reloading
8817 it would set the 'is_running' flag back to 1 for them. It hasn't
8818 done that for a long time.
8819 - In very rare situations new hidden service descriptors were
8820 published earlier than 30 seconds after the last change to the
8821 service. (We currently think that a hidden service descriptor
8822 that's been stable for 30 seconds is worth publishing.)
8825 - Allow separate log levels to be configured for different logging
8826 domains. For example, this allows one to log all notices, warnings,
8827 or errors, plus all memory management messages of level debug or
8828 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
8829 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
8830 and stop using a warning that had become unfixably verbose under
8832 - New --hush command-line option similar to --quiet. While --quiet
8833 disables all logging to the console on startup, --hush limits the
8834 output to messages of warning and error severity.
8835 - Servers support a new URL scheme for consensus downloads that
8836 allows the client to specify which authorities are trusted.
8837 The server then only sends the consensus if the client will trust
8838 it. Otherwise a 404 error is sent back. Clients use this
8839 new scheme when the server supports it (meaning it's running
8840 0.2.1.1-alpha or later). Implements proposal 134.
8841 - New configure/torrc options (--enable-geoip-stats,
8842 DirRecordUsageByCountry) to record how many IPs we've served
8843 directory info to in each country code, how many status documents
8844 total we've sent to each country code, and what share of the total
8845 directory requests we should expect to see.
8846 - Use the TLS1 hostname extension to more closely resemble browser
8848 - Lots of new unit tests.
8849 - Add a macro to implement the common pattern of iterating through
8850 two parallel lists in lockstep.
8853 Changes in version 0.2.0.28-rc - 2008-06-13
8854 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
8855 performance bug, and fixes a bunch of smaller bugs.
8858 - Fix a bug where, when we were choosing the 'end stream reason' to
8859 put in our relay end cell that we send to the exit relay, Tor
8860 clients on Windows were sometimes sending the wrong 'reason'. The
8861 anonymity problem is that exit relays may be able to guess whether
8862 the client is running Windows, thus helping partition the anonymity
8863 set. Down the road we should stop sending reasons to exit relays,
8864 or otherwise prevent future versions of this bug.
8867 - While setting up a hidden service, some valid introduction circuits
8868 were overlooked and abandoned. This might be the reason for
8869 the long delay in making a hidden service available. Bugfix on
8873 - Update to the "June 9 2008" ip-to-country file.
8874 - Run 'make test' as part of 'make dist', so we stop releasing so
8875 many development snapshots that fail their unit tests.
8878 - When we're checking if we have enough dir info for each relay
8879 to begin establishing circuits, make sure that we actually have
8880 the descriptor listed in the consensus, not just any descriptor.
8882 - Bridge relays no longer print "xx=0" in their extrainfo document
8883 for every single country code in the geoip db. Bugfix on
8885 - Only warn when we fail to load the geoip file if we were planning to
8886 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
8887 - If we change our MaxAdvertisedBandwidth and then reload torrc,
8888 Tor won't realize it should publish a new relay descriptor. Fixes
8889 bug 688, reported by mfr. Bugfix on 0.1.2.x.
8890 - When we haven't had any application requests lately, don't bother
8891 logging that we have expired a bunch of descriptors. Bugfix
8893 - Make relay cells written on a connection count as non-padding when
8894 tracking how long a connection has been in use. Bugfix on
8895 0.2.0.1-alpha. Spotted by lodger.
8896 - Fix unit tests in 0.2.0.27-rc.
8897 - Fix compile on Windows.
8900 Changes in version 0.2.0.27-rc - 2008-06-03
8901 Tor 0.2.0.27-rc adds a few features we left out of the earlier
8902 release candidates. In particular, we now include an IP-to-country
8903 GeoIP database, so controllers can easily look up what country a
8904 given relay is in, and so bridge relays can give us some sanitized
8905 summaries about which countries are making use of bridges. (See proposal
8906 126-geoip-fetching.txt for details.)
8909 - Include an IP-to-country GeoIP file in the tarball, so bridge
8910 relays can report sanitized summaries of the usage they're seeing.
8913 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
8914 Robert Hogan. Fixes the first part of bug 681.
8915 - Make bridge authorities never serve extrainfo docs.
8916 - Add support to detect Libevent versions in the 1.4.x series
8918 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
8919 - Include a new contrib/tor-exit-notice.html file that exit relay
8920 operators can put on their website to help reduce abuse queries.
8923 - When tunneling an encrypted directory connection, and its first
8924 circuit fails, do not leave it unattached and ask the controller
8925 to deal. Fixes the second part of bug 681.
8926 - Make bridge authorities correctly expire old extrainfo documents
8930 Changes in version 0.2.0.26-rc - 2008-05-13
8931 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
8932 in Debian's OpenSSL packages. All users running any 0.2.0.x version
8933 should upgrade, whether they're running Debian or not.
8935 o Major security fixes:
8936 - Use new V3 directory authority keys on the tor26, gabelmoo, and
8937 moria1 V3 directory authorities. The old keys were generated with
8938 a vulnerable version of Debian's OpenSSL package, and must be
8939 considered compromised. Other authorities' keys were not generated
8940 with an affected version of OpenSSL.
8943 - List authority signatures as "unrecognized" based on DirServer
8944 lines, not on cert cache. Bugfix on 0.2.0.x.
8947 - Add a new V3AuthUseLegacyKey option to make it easier for
8948 authorities to change their identity keys if they have to.
8951 Changes in version 0.2.0.25-rc - 2008-04-23
8952 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
8955 - Remember to initialize threading before initializing logging.
8956 Otherwise, many BSD-family implementations will crash hard on
8957 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
8960 - Authorities correctly free policies on bad servers on
8961 exit. Fixes bug 672. Bugfix on 0.2.0.x.
8964 Changes in version 0.2.0.24-rc - 2008-04-22
8965 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
8966 v3 directory authority, makes relays with dynamic IP addresses and no
8967 DirPort notice more quickly when their IP address changes, fixes a few
8968 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
8970 o New directory authorities:
8971 - Take lefkada out of the list of v3 directory authorities, since
8972 it has been down for months.
8973 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
8977 - Detect address changes more quickly on non-directory mirror
8978 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
8980 o Minor features (security):
8981 - Reject requests for reverse-dns lookup of names that are in
8982 a private address space. Patch from lodger.
8983 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
8986 o Minor bugfixes (crashes):
8987 - Avoid a rare assert that can trigger when Tor doesn't have much
8988 directory information yet and it tries to fetch a v2 hidden
8989 service descriptor. Fixes bug 651, reported by nwf.
8990 - Initialize log mutex before initializing dmalloc. Otherwise,
8991 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
8992 - Use recursive pthread mutexes in order to avoid deadlock when
8993 logging debug-level messages to a controller. Bug spotted by nwf,
8994 bugfix on 0.2.0.16-alpha.
8996 o Minor bugfixes (resource management):
8997 - Keep address policies from leaking memory: start their refcount
8998 at 1, not 2. Bugfix on 0.2.0.16-alpha.
8999 - Free authority certificates on exit, so they don't look like memory
9000 leaks. Bugfix on 0.2.0.19-alpha.
9001 - Free static hashtables for policy maps and for TLS connections on
9002 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
9003 - Avoid allocating extra space when computing consensuses on 64-bit
9004 platforms. Bug spotted by aakova.
9006 o Minor bugfixes (misc):
9007 - Do not read the configuration file when we've only been told to
9008 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
9009 based on patch from Sebastian Hahn.
9010 - Exit relays that are used as a client can now reach themselves
9011 using the .exit notation, rather than just launching an infinite
9012 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
9013 - When attempting to open a logfile fails, tell us why.
9014 - Fix a dumb bug that was preventing us from knowing that we should
9015 preemptively build circuits to handle expected directory requests.
9016 Fixes bug 660. Bugfix on 0.1.2.x.
9017 - Warn less verbosely about clock skew from netinfo cells from
9018 untrusted sources. Fixes bug 663.
9019 - Make controller stream events for DNS requests more consistent,
9020 by adding "new stream" events for DNS requests, and removing
9021 spurious "stream closed" events" for cached reverse resolves.
9022 Patch from mwenge. Fixes bug 646.
9023 - Correctly notify one-hop connections when a circuit build has
9024 failed. Possible fix for bug 669. Found by lodger.
9027 Changes in version 0.2.0.23-rc - 2008-03-24
9028 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
9029 makes bootstrapping faster if the first directory mirror you contact
9030 is down. The bundles also include the new Vidalia 0.1.2 release.
9033 - When a tunneled directory request is made to a directory server
9034 that's down, notice after 30 seconds rather than 120 seconds. Also,
9035 fail any begindir streams that are pending on it, so they can
9036 retry elsewhere. This was causing multi-minute delays on bootstrap.
9039 Changes in version 0.2.0.22-rc - 2008-03-18
9040 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
9041 enables encrypted directory connections by default for non-relays, fixes
9042 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
9043 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
9046 - Enable encrypted directory connections by default for non-relays,
9047 so censor tools that block Tor directory connections based on their
9048 plaintext patterns will no longer work. This means Tor works in
9049 certain censored countries by default again.
9052 - Make sure servers always request certificates from clients during
9053 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
9054 - Do not enter a CPU-eating loop when a connection is closed in
9055 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
9056 diagnosed by lodger; bugfix on 0.2.0.20-rc.
9057 - Fix assertion failure that could occur when a blocked circuit
9058 became unblocked, and it had pending client DNS requests. Bugfix
9059 on 0.2.0.1-alpha. Fixes bug 632.
9061 o Minor bugfixes (on 0.1.2.x):
9062 - Generate "STATUS_SERVER" events rather than misspelled
9063 "STATUS_SEVER" events. Caught by mwenge.
9064 - When counting the number of bytes written on a TLS connection,
9065 look at the BIO actually used for writing to the network, not
9066 at the BIO used (sometimes) to buffer data for the network.
9067 Looking at different BIOs could result in write counts on the
9068 order of ULONG_MAX. Fixes bug 614.
9069 - On Windows, correctly detect errors when listing the contents of
9070 a directory. Fix from lodger.
9072 o Minor bugfixes (on 0.2.0.x):
9073 - Downgrade "sslv3 alert handshake failure" message to INFO.
9074 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
9075 left BandwidthRate and BandwidthBurst at the default, we would be
9076 silently limited by those defaults. Now raise them to match the
9077 RelayBandwidth* values.
9078 - Fix the SVK version detection logic to work correctly on a branch.
9079 - Make --enable-openbsd-malloc work correctly on Linux with alpha
9080 CPUs. Fixes bug 625.
9081 - Logging functions now check that the passed severity is sane.
9082 - Use proper log levels in the testsuite call of
9083 get_interface_address6().
9084 - When using a nonstandard malloc, do not use the platform values for
9085 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
9086 - Make the openbsd malloc code use 8k pages on alpha CPUs and
9088 - Detect mismatched page sizes when using --enable-openbsd-malloc.
9089 - Avoid double-marked-for-close warning when certain kinds of invalid
9090 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
9091 for bug 617. Bugfix on 0.2.0.1-alpha.
9092 - Make sure that the "NULL-means-reject *:*" convention is followed by
9093 all the policy manipulation functions, avoiding some possible crash
9094 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
9095 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
9096 actually works, and doesn't warn about every single reverse lookup.
9097 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
9100 - Only log guard node status when guard node status has changed.
9101 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
9102 make "INFO" 75% less verbose.
9105 Changes in version 0.2.0.21-rc - 2008-03-02
9106 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
9107 makes Tor work well with Vidalia again, fixes a rare assert bug,
9108 and fixes a pair of more minor bugs. The bundles also include Vidalia
9109 0.1.0 and Torbutton 1.1.16.
9112 - The control port should declare that it requires password auth
9113 when HashedControlSessionPassword is set too. Patch from Matt Edman;
9114 bugfix on 0.2.0.20-rc. Fixes bug 615.
9115 - Downgrade assert in connection_buckets_decrement() to a log message.
9116 This may help us solve bug 614, and in any case will make its
9117 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
9118 - We were sometimes miscounting the number of bytes read from the
9119 network, causing our rate limiting to not be followed exactly.
9120 Bugfix on 0.2.0.16-alpha. Reported by lodger.
9123 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
9124 OpenSSL versions should have been working fine. Diagnosis and patch
9125 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
9126 Bugfix on 0.2.0.20-rc.
9129 Changes in version 0.2.0.20-rc - 2008-02-24
9130 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
9131 makes more progress towards normalizing Tor's TLS handshake, makes
9132 hidden services work better again, helps relays bootstrap if they don't
9133 know their IP address, adds optional support for linking in openbsd's
9134 allocator or tcmalloc, allows really fast relays to scale past 15000
9135 sockets, and fixes a bunch of minor bugs reported by Veracode.
9138 - Enable the revised TLS handshake based on the one designed by
9139 Steven Murdoch in proposal 124, as revised in proposal 130. It
9140 includes version negotiation for OR connections as described in
9141 proposal 105. The new handshake is meant to be harder for censors
9142 to fingerprint, and it adds the ability to detect certain kinds of
9143 man-in-the-middle traffic analysis attacks. The version negotiation
9144 feature will allow us to improve Tor's link protocol more safely
9146 - Choose which bridge to use proportional to its advertised bandwidth,
9147 rather than uniformly at random. This should speed up Tor for
9148 bridge users. Also do this for people who set StrictEntryNodes.
9149 - When a TrackHostExits-chosen exit fails too many times in a row,
9150 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
9153 - Resolved problems with (re-)fetching hidden service descriptors.
9154 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
9156 - If we only ever used Tor for hidden service lookups or posts, we
9157 would stop building circuits and start refusing connections after
9158 24 hours, since we falsely believed that Tor was dormant. Reported
9159 by nwf; bugfix on 0.1.2.x.
9160 - Servers that don't know their own IP address should go to the
9161 authorities for their first directory fetch, even if their DirPort
9162 is off or if they don't know they're reachable yet. This will help
9163 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
9164 - When counting the number of open sockets, count not only the number
9165 of sockets we have received from the socket() call, but also
9166 the number we've gotten from accept() and socketpair(). This bug
9167 made us fail to count all sockets that we were using for incoming
9168 connections. Bugfix on 0.2.0.x.
9169 - Fix code used to find strings within buffers, when those strings
9170 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
9171 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
9172 - Add a new __HashedControlSessionPassword option for controllers
9173 to use for one-off session password hashes that shouldn't get
9174 saved to disk by SAVECONF --- Vidalia users were accumulating a
9175 pile of HashedControlPassword lines in their torrc files, one for
9176 each time they had restarted Tor and then clicked Save. Make Tor
9177 automatically convert "HashedControlPassword" to this new option but
9178 only when it's given on the command line. Partial fix for bug 586.
9180 o Minor features (performance):
9181 - Tune parameters for cell pool allocation to minimize amount of
9183 - Add OpenBSD malloc code from phk as an optional malloc
9184 replacement on Linux: some glibc libraries do very poorly
9185 with Tor's memory allocation patterns. Pass
9186 --enable-openbsd-malloc to get the replacement malloc code.
9187 - Add a --with-tcmalloc option to the configure script to link
9188 against tcmalloc (if present). Does not yet search for
9189 non-system include paths.
9190 - Stop imposing an arbitrary maximum on the number of file descriptors
9191 used for busy servers. Bug reported by Olaf Selke; patch from
9194 o Minor features (other):
9195 - When SafeLogging is disabled, log addresses along with all TLS
9197 - When building with --enable-gcc-warnings, check for whether Apple's
9198 warning "-Wshorten-64-to-32" is available.
9199 - Add a --passphrase-fd argument to the tor-gencert command for
9202 o Minor bugfixes (memory leaks and code problems):
9203 - We were leaking a file descriptor if Tor started with a zero-length
9204 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
9205 - Detect size overflow in zlib code. Reported by Justin Ferguson and
9207 - We were comparing the raw BridgePassword entry with a base64'ed
9208 version of it, when handling a "/tor/networkstatus-bridges"
9209 directory request. Now compare correctly. Noticed by Veracode.
9210 - Recover from bad tracked-since value in MTBF-history file.
9212 - Alter the code that tries to recover from unhandled write
9213 errors, to not try to flush onto a socket that's given us
9214 unhandled errors. Bugfix on 0.1.2.x.
9215 - Make Unix controlsockets work correctly on OpenBSD. Patch from
9216 tup. Bugfix on 0.2.0.3-alpha.
9218 o Minor bugfixes (other):
9219 - If we have an extra-info document for our server, always make
9220 it available on the control port, even if we haven't gotten
9221 a copy of it from an authority yet. Patch from mwenge.
9222 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
9223 - Directory mirrors no longer include a guess at the client's IP
9224 address if the connection appears to be coming from the same /24
9225 network; it was producing too many wrong guesses.
9226 - Make the new hidden service code respect the SafeLogging setting.
9227 Bugfix on 0.2.0.x. Patch from Karsten.
9228 - When starting as an authority, do not overwrite all certificates
9229 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
9230 - If we're trying to flush the last bytes on a connection (for
9231 example, when answering a directory request), reset the
9232 time-to-give-up timeout every time we manage to write something
9233 on the socket. Bugfix on 0.1.2.x.
9234 - Change the behavior of "getinfo status/good-server-descriptor"
9235 so it doesn't return failure when any authority disappears.
9236 - Even though the man page said that "TrackHostExits ." should
9237 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
9238 - Report TLS "zero return" case as a "clean close" and "IO error"
9239 as a "close". Stop calling closes "unexpected closes": existing
9240 Tors don't use SSL_close(), so having a connection close without
9241 the TLS shutdown handshake is hardly unexpected.
9242 - Send NAMESERVER_STATUS messages for a single failed nameserver
9245 o Code simplifications and refactoring:
9246 - Remove the tor_strpartition function: its logic was confused,
9247 and it was only used for one thing that could be implemented far
9251 Changes in version 0.2.0.19-alpha - 2008-02-09
9252 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
9253 handshake, makes path selection for relays more secure and IP address
9254 guessing more robust, and generally fixes a lot of bugs in preparation
9255 for calling the 0.2.0 branch stable.
9258 - Do not include recognizeable strings in the commonname part of
9259 Tor's x509 certificates.
9262 - If we're a relay, avoid picking ourselves as an introduction point,
9263 a rendezvous point, or as the final hop for internal circuits. Bug
9264 reported by taranis and lodger. Bugfix on 0.1.2.x.
9265 - Patch from "Andrew S. Lists" to catch when we contact a directory
9266 mirror at IP address X and he says we look like we're coming from
9267 IP address X. Bugfix on 0.1.2.x.
9269 o Minor features (security):
9270 - Be more paranoid about overwriting sensitive memory on free(),
9271 as a defensive programming tactic to ensure forward secrecy.
9273 o Minor features (directory authority):
9274 - Actually validate the options passed to AuthDirReject,
9275 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
9276 - Reject router descriptors with out-of-range bandwidthcapacity or
9277 bandwidthburst values.
9279 o Minor features (controller):
9280 - Reject controller commands over 1MB in length. This keeps rogue
9281 processes from running us out of memory.
9283 o Minor features (misc):
9284 - Give more descriptive well-formedness errors for out-of-range
9285 hidden service descriptor/protocol versions.
9286 - Make memory debugging information describe more about history
9287 of cell allocation, so we can help reduce our memory use.
9289 o Deprecated features (controller):
9290 - The status/version/num-versioning and status/version/num-concurring
9291 GETINFO options are no longer useful in the v3 directory protocol:
9292 treat them as deprecated, and warn when they're used.
9295 - When our consensus networkstatus has been expired for a while, stop
9296 being willing to build circuits using it. Fixes bug 401. Bugfix
9298 - Directory caches now fetch certificates from all authorities
9299 listed in a networkstatus consensus, even when they do not
9300 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
9301 - When connecting to a bridge without specifying its key, insert
9302 the connection into the identity-to-connection map as soon as
9303 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
9304 - Detect versions of OS X where malloc_good_size() is present in the
9305 library but never actually declared. Resolves bug 587. Bugfix
9307 - Stop incorrectly truncating zlib responses to directory authority
9308 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
9309 - Stop recommending that every server operator send mail to tor-ops.
9310 Resolves bug 597. Bugfix on 0.1.2.x.
9311 - Don't trigger an assert if we start a directory authority with a
9312 private IP address (like 127.0.0.1).
9313 - Avoid possible failures when generating a directory with routers
9314 with over-long versions strings, or too many flags set. Bugfix
9316 - If an attempt to launch a DNS resolve request over the control
9317 port fails because we have overrun the limit on the number of
9318 connections, tell the controller that the request has failed.
9319 - Avoid using too little bandwidth when our clock skips a few
9320 seconds. Bugfix on 0.1.2.x.
9321 - Fix shell error when warning about missing packages in configure
9322 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
9323 - Do not become confused when receiving a spurious VERSIONS-like
9324 cell from a confused v1 client. Bugfix on 0.2.0.x.
9325 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
9326 introduction points for a hidden service have failed. Patch from
9327 Karsten Loesing. Bugfix on 0.2.0.x.
9329 o Code simplifications and refactoring:
9330 - Remove some needless generality from cpuworker code, for improved
9332 - Stop overloading the circuit_t.onionskin field for both "onionskin
9333 from a CREATE cell that we are waiting for a cpuworker to be
9334 assigned" and "onionskin from an EXTEND cell that we are going to
9335 send to an OR as soon as we are connected". Might help with bug 600.
9336 - Add an in-place version of aes_crypt() so that we can avoid doing a
9337 needless memcpy() call on each cell payload.
9340 Changes in version 0.2.0.18-alpha - 2008-01-25
9341 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
9342 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
9343 that can warn or reject connections to ports generally associated with
9344 vulnerable-plaintext protocols.
9346 o New directory authorities:
9347 - Set up dannenberg (run by CCC) as the sixth v3 directory
9351 - Fix a major memory leak when attempting to use the v2 TLS
9352 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
9353 - We accidentally enabled the under-development v2 TLS handshake
9354 code, which was causing log entries like "TLS error while
9355 renegotiating handshake". Disable it again. Resolves bug 590.
9356 - We were computing the wrong Content-Length: header for directory
9357 responses that need to be compressed on the fly, causing clients
9358 asking for those items to always fail. Bugfix on 0.2.0.x; partially
9362 - Avoid going directly to the directory authorities even if you're a
9363 relay, if you haven't found yourself reachable yet or if you've
9364 decided not to advertise your dirport yet. Addresses bug 556.
9365 - If we've gone 12 hours since our last bandwidth check, and we
9366 estimate we have less than 50KB bandwidth capacity but we could
9367 handle more, do another bandwidth test.
9368 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
9369 Tor can warn and/or refuse connections to ports commonly used with
9370 vulnerable-plaintext protocols. Currently we warn on ports 23,
9371 109, 110, and 143, but we don't reject any.
9374 - When we setconf ClientOnly to 1, close any current OR and Dir
9375 listeners. Reported by mwenge.
9376 - When we get a consensus that's been signed by more people than
9377 we expect, don't log about it; it's not a big deal. Reported
9381 - Don't answer "/tor/networkstatus-bridges" directory requests if
9382 the request isn't encrypted.
9383 - Make "ClientOnly 1" config option disable directory ports too.
9384 - Patches from Karsten Loesing to make v2 hidden services more
9385 robust: work even when there aren't enough HSDir relays available;
9386 retry when a v2 rend desc fetch fails; but don't retry if we
9387 already have a usable v0 rend desc.
9390 Changes in version 0.2.0.17-alpha - 2008-01-17
9391 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
9394 - Make the tor-gencert man page get included correctly in the tarball.
9397 Changes in version 0.2.0.16-alpha - 2008-01-17
9398 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
9399 Loesing, and generally cleans up a lot of features and minor bugs.
9401 o New directory authorities:
9402 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
9405 o Major performance improvements:
9406 - Switch our old ring buffer implementation for one more like that
9407 used by free Unix kernels. The wasted space in a buffer with 1mb
9408 of data will now be more like 8k than 1mb. The new implementation
9409 also avoids realloc();realloc(); patterns that can contribute to
9410 memory fragmentation.
9413 - Configuration files now accept C-style strings as values. This
9414 helps encode characters not allowed in the current configuration
9415 file format, such as newline or #. Addresses bug 557.
9416 - Although we fixed bug 539 (where servers would send HTTP status 503
9417 responses _and_ send a body too), there are still servers out
9418 there that haven't upgraded. Therefore, make clients parse such
9419 bodies when they receive them.
9420 - When we're not serving v2 directory information, there is no reason
9421 to actually keep any around. Remove the obsolete files and directory
9422 on startup if they are very old and we aren't going to serve them.
9424 o Minor performance improvements:
9425 - Reference-count and share copies of address policy entries; only 5%
9426 of them were actually distinct.
9427 - Never walk through the list of logs if we know that no log is
9428 interested in a given message.
9431 - When an authority has not signed a consensus, do not try to
9432 download a nonexistent "certificate with key 00000000". Bugfix
9433 on 0.2.0.x. Fixes bug 569.
9434 - Fix a rare assert error when we're closing one of our threads:
9435 use a mutex to protect the list of logs, so we never write to the
9436 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
9437 bug 575, which is kind of the revenge of bug 222.
9438 - Patch from Karsten Loesing to complain less at both the client
9439 and the relay when a relay used to have the HSDir flag but doesn't
9440 anymore, and we try to upload a hidden service descriptor.
9441 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
9443 - Do not try to download missing certificates until we have tried
9444 to check our fallback consensus. Fixes bug 583.
9445 - Make bridges round reported GeoIP stats info up to the nearest
9446 estimate, not down. Now we can distinguish between "0 people from
9447 this country" and "1 person from this country".
9448 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
9449 - Avoid possible segfault if key generation fails in
9450 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
9451 - Avoid segfault in the case where a badly behaved v2 versioning
9452 directory sends a signed networkstatus with missing client-versions.
9454 - Avoid segfaults on certain complex invocations of
9455 router_get_by_hexdigest(). Bugfix on 0.1.2.
9456 - Correct bad index on array access in parse_http_time(). Bugfix
9458 - Fix possible bug in vote generation when server versions are present
9459 but client versions are not.
9460 - Fix rare bug on REDIRECTSTREAM control command when called with no
9461 port set: it could erroneously report an error when none had
9463 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
9464 compressing large objects and find ourselves with more than 4k
9465 left over. Bugfix on 0.2.0.
9466 - Fix a small memory leak when setting up a hidden service.
9467 - Fix a few memory leaks that could in theory happen under bizarre
9469 - Fix an assert if we post a general-purpose descriptor via the
9470 control port but that descriptor isn't mentioned in our current
9471 network consensus. Bug reported by Jon McLachlan; bugfix on
9474 o Minor features (controller):
9475 - Get NS events working again. Patch from tup.
9476 - The GETCONF command now escapes and quotes configuration values
9477 that don't otherwise fit into the torrc file.
9478 - The SETCONF command now handles quoted values correctly.
9480 o Minor features (directory authorities):
9481 - New configuration options to override default maximum number of
9482 servers allowed on a single IP address. This is important for
9483 running a test network on a single host.
9484 - Actually implement the -s option to tor-gencert.
9485 - Add a manual page for tor-gencert.
9487 o Minor features (bridges):
9488 - Bridge authorities no longer serve bridge descriptors over
9489 unencrypted connections.
9491 o Minor features (other):
9492 - Add hidden services and DNSPorts to the list of things that make
9493 Tor accept that it has running ports. Change starting Tor with no
9494 ports from a fatal error to a warning; we might change it back if
9495 this turns out to confuse anybody. Fixes bug 579.
9498 Changes in version 0.1.2.19 - 2008-01-17
9499 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
9500 exit policy a little bit more conservative so it's safer to run an
9501 exit relay on a home system, and fixes a variety of smaller issues.
9504 - Exit policies now reject connections that are addressed to a
9505 relay's public (external) IP address too, unless
9506 ExitPolicyRejectPrivate is turned off. We do this because too
9507 many relays are running nearby to services that trust them based
9511 - When the clock jumps forward a lot, do not allow the bandwidth
9512 buckets to become negative. Fixes bug 544.
9513 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9514 on every successful resolve. Reported by Mike Perry.
9515 - Purge old entries from the "rephist" database and the hidden
9516 service descriptor database even when DirPort is zero.
9517 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9518 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9519 crashing or mis-answering these requests.
9520 - When we decide to send a 503 response to a request for servers, do
9521 not then also send the server descriptors: this defeats the whole
9522 purpose. Fixes bug 539.
9525 - Changing the ExitPolicyRejectPrivate setting should cause us to
9526 rebuild our server descriptor.
9527 - Fix handling of hex nicknames when answering controller requests for
9528 networkstatus by name, or when deciding whether to warn about
9529 unknown routers in a config option. (Patch from mwenge.)
9530 - Fix a couple of hard-to-trigger autoconf problems that could result
9531 in really weird results on platforms whose sys/types.h files define
9532 nonstandard integer types.
9533 - Don't try to create the datadir when running --verify-config or
9534 --hash-password. Resolves bug 540.
9535 - If we were having problems getting a particular descriptor from the
9536 directory caches, and then we learned about a new descriptor for
9537 that router, we weren't resetting our failure count. Reported
9539 - Although we fixed bug 539 (where servers would send HTTP status 503
9540 responses _and_ send a body too), there are still servers out there
9541 that haven't upgraded. Therefore, make clients parse such bodies
9542 when they receive them.
9543 - Run correctly on systems where rlim_t is larger than unsigned long.
9544 This includes some 64-bit systems.
9545 - Run correctly on platforms (like some versions of OS X 10.5) where
9546 the real limit for number of open files is OPEN_FILES, not rlim_max
9547 from getrlimit(RLIMIT_NOFILES).
9548 - Avoid a spurious free on base64 failure.
9549 - Avoid segfaults on certain complex invocations of
9550 router_get_by_hexdigest().
9551 - Fix rare bug on REDIRECTSTREAM control command when called with no
9552 port set: it could erroneously report an error when none had
9556 Changes in version 0.2.0.15-alpha - 2007-12-25
9557 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
9558 features added in 0.2.0.13-alpha.
9561 - Fix several remotely triggerable asserts based on DirPort requests
9562 for a v2 or v3 networkstatus object before we were prepared. This
9563 was particularly bad for 0.2.0.13 and later bridge relays, who
9564 would never have a v2 networkstatus and would thus always crash
9565 when used. Bugfixes on 0.2.0.x.
9566 - Estimate the v3 networkstatus size more accurately, rather than
9567 estimating it at zero bytes and giving it artificially high priority
9568 compared to other directory requests. Bugfix on 0.2.0.x.
9571 - Fix configure.in logic for cross-compilation.
9572 - When we load a bridge descriptor from the cache, and it was
9573 previously unreachable, mark it as retriable so we won't just
9574 ignore it. Also, try fetching a new copy immediately. Bugfixes
9576 - The bridge GeoIP stats were counting other relays, for example
9577 self-reachability and authority-reachability tests.
9580 - Support compilation to target iPhone; patch from cjacker huang.
9581 To build for iPhone, pass the --enable-iphone option to configure.
9584 Changes in version 0.2.0.14-alpha - 2007-12-23
9586 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
9587 without a datadirectory from a previous Tor install. Reported
9589 - Fix a crash when we fetch a descriptor that turns out to be
9590 unexpected (it used to be in our networkstatus when we started
9591 fetching it, but it isn't in our current networkstatus), and we
9592 aren't using bridges. Bugfix on 0.2.0.x.
9593 - Fix a crash when accessing hidden services: it would work the first
9594 time you use a given introduction point for your service, but
9595 on subsequent requests we'd be using garbage memory. Fixed by
9596 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
9597 - Fix a crash when we load a bridge descriptor from disk but we don't
9598 currently have a Bridge line for it in our torrc. Bugfix on
9602 - If bridge authorities set BridgePassword, they will serve a
9603 snapshot of known bridge routerstatuses from their DirPort to
9604 anybody who knows that password. Unset by default.
9607 - Make the unit tests build again.
9608 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
9609 - Make PublishServerDescriptor default to 1, so the default doesn't
9610 have to change as we invent new directory protocol versions.
9611 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
9612 be included unless sys/time.h is already included. Fixes
9613 bug 553. Bugfix on 0.2.0.x.
9614 - If we receive a general-purpose descriptor and then receive an
9615 identical bridge-purpose descriptor soon after, don't discard
9616 the next one as a duplicate.
9619 - If BridgeRelay is set to 1, then the default for
9620 PublishServerDescriptor is now "bridge" rather than "v2,v3".
9621 - If the user sets RelayBandwidthRate but doesn't set
9622 RelayBandwidthBurst, then make them equal rather than erroring out.
9625 Changes in version 0.2.0.13-alpha - 2007-12-21
9626 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
9627 Goodell, fixes many more bugs, and adds a lot of infrastructure for
9630 o New directory authorities:
9631 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
9635 - Only update guard status (usable / not usable) once we have
9636 enough directory information. This was causing us to always pick
9637 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
9638 causing us to discard all our guards on startup if we hadn't been
9639 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
9640 - Purge old entries from the "rephist" database and the hidden
9641 service descriptor databases even when DirPort is zero. Bugfix
9643 - We were ignoring our RelayBandwidthRate for the first 30 seconds
9644 after opening a circuit -- even a relayed circuit. Bugfix on
9646 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9647 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9648 crashing or mis-answering these types of requests.
9649 - Relays were publishing their server descriptor to v1 and v2
9650 directory authorities, but they didn't try publishing to v3-only
9651 authorities. Fix this; and also stop publishing to v1 authorities.
9653 - When we were reading router descriptors from cache, we were ignoring
9654 the annotations -- so for example we were reading in bridge-purpose
9655 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
9656 - When we decided to send a 503 response to a request for servers, we
9657 were then also sending the server descriptors: this defeats the
9658 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
9661 - Bridge relays now behave like clients with respect to time
9662 intervals for downloading new consensus documents -- otherwise they
9663 stand out. Bridge users now wait until the end of the interval,
9664 so their bridge relay will be sure to have a new consensus document.
9665 - Three new config options (AlternateDirAuthority,
9666 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
9667 user selectively replace the default directory authorities by type,
9668 rather than the all-or-nothing replacement that DirServer offers.
9669 - Tor can now be configured to read a GeoIP file from disk in one
9670 of two formats. This can be used by controllers to map IP addresses
9671 to countries. Eventually, it may support exit-by-country.
9672 - When possible, bridge relays remember which countries users
9673 are coming from, and report aggregate information in their
9674 extra-info documents, so that the bridge authorities can learn
9675 where Tor is blocked.
9676 - Bridge directory authorities now do reachability testing on the
9677 bridges they know. They provide router status summaries to the
9678 controller via "getinfo ns/purpose/bridge", and also dump summaries
9679 to a file periodically.
9680 - Stop fetching directory info so aggressively if your DirPort is
9681 on but your ORPort is off; stop fetching v2 dir info entirely.
9682 You can override these choices with the new FetchDirInfoEarly
9686 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
9687 consensus documents when there are too many relays at a single
9688 IP address. Now clear it in v2 network status documents too, and
9689 also clear it in routerinfo_t when the relay is no longer listed
9690 in the relevant networkstatus document.
9691 - Don't crash if we get an unexpected value for the
9692 PublishServerDescriptor config option. Reported by Matt Edman;
9693 bugfix on 0.2.0.9-alpha.
9694 - Our new v2 hidden service descriptor format allows descriptors
9695 that have no introduction points. But Tor crashed when we tried
9696 to build a descriptor with no intro points (and it would have
9697 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
9699 - Fix building with dmalloc 5.5.2 with glibc.
9700 - Reject uploaded descriptors and extrainfo documents if they're
9701 huge. Otherwise we'll cache them all over the network and it'll
9702 clog everything up. Reported by Aljosha Judmayer.
9703 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
9704 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
9705 - When the DANGEROUS_VERSION controller status event told us we're
9706 running an obsolete version, it used the string "OLD" to describe
9707 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
9708 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
9709 - If we can't expand our list of entry guards (e.g. because we're
9710 using bridges or we have StrictEntryNodes set), don't mark relays
9711 down when they fail a directory request. Otherwise we're too quick
9712 to mark all our entry points down. Bugfix on 0.1.2.x.
9713 - Fix handling of hex nicknames when answering controller requests for
9714 networkstatus by name, or when deciding whether to warn about unknown
9715 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
9716 - Fix a couple of hard-to-trigger autoconf problems that could result
9717 in really weird results on platforms whose sys/types.h files define
9718 nonstandard integer types. Bugfix on 0.1.2.x.
9719 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
9720 - Don't crash on name lookup when we have no current consensus. Fixes
9721 bug 538; bugfix on 0.2.0.x.
9722 - Only Tors that want to mirror the v2 directory info should
9723 create the "cached-status" directory in their datadir. (All Tors
9724 used to create it.) Bugfix on 0.2.0.9-alpha.
9725 - Directory authorities should only automatically download Extra Info
9726 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
9729 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
9730 consumers. (We already do this on HUP.)
9731 - Authorities and caches fetch the v2 networkstatus documents
9732 less often, now that v3 is encouraged.
9733 - Add a new config option BridgeRelay that specifies you want to
9734 be a bridge relay. Right now the only difference is that it makes
9735 you answer begin_dir requests, and it makes you cache dir info,
9736 even if your DirPort isn't on.
9737 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
9738 ask about source, timestamp of arrival, purpose, etc. We need
9739 something like this to help Vidalia not do GeoIP lookups on bridge
9741 - Allow multiple HashedControlPassword config lines, to support
9742 multiple controller passwords.
9743 - Authorities now decide whether they're authoritative for a given
9744 router based on the router's purpose.
9745 - New config options AuthDirBadDir and AuthDirListBadDirs for
9746 authorities to mark certain relays as "bad directories" in the
9747 networkstatus documents. Also supports the "!baddir" directive in
9748 the approved-routers file.
9751 Changes in version 0.2.0.12-alpha - 2007-11-16
9752 This twelfth development snapshot fixes some more build problems as
9753 well as a few minor bugs.
9756 - Make it build on OpenBSD again. Patch from tup.
9757 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
9758 package-building for Red Hat, OS X, etc.
9760 o Minor bugfixes (on 0.1.2.x):
9761 - Changing the ExitPolicyRejectPrivate setting should cause us to
9762 rebuild our server descriptor.
9764 o Minor bugfixes (on 0.2.0.x):
9765 - When we're lacking a consensus, don't try to perform rendezvous
9766 operations. Reported by Karsten Loesing.
9767 - Fix a small memory leak whenever we decide against using a
9768 newly picked entry guard. Reported by Mike Perry.
9769 - When authorities detected more than two relays running on the same
9770 IP address, they were clearing all the status flags but forgetting
9771 to clear the "hsdir" flag. So clients were being told that a
9772 given relay was the right choice for a v2 hsdir lookup, yet they
9773 never had its descriptor because it was marked as 'not running'
9775 - If we're trying to fetch a bridge descriptor and there's no way
9776 the bridge authority could help us (for example, we don't know
9777 a digest, or there is no bridge authority), don't be so eager to
9778 fall back to asking the bridge authority.
9779 - If we're using bridges or have strictentrynodes set, and our
9780 chosen exit is in the same family as all our bridges/entry guards,
9781 then be flexible about families.
9784 - When we negotiate a v2 link-layer connection (not yet implemented),
9785 accept RELAY_EARLY cells and turn them into RELAY cells if we've
9786 negotiated a v1 connection for their next step. Initial code for
9790 Changes in version 0.2.0.11-alpha - 2007-11-12
9791 This eleventh development snapshot fixes some build problems with
9792 the previous snapshot. It also includes a more secure-by-default exit
9793 policy for relays, fixes an enormous memory leak for exit relays, and
9794 fixes another bug where servers were falling out of the directory list.
9797 - Exit policies now reject connections that are addressed to a
9798 relay's public (external) IP address too, unless
9799 ExitPolicyRejectPrivate is turned off. We do this because too
9800 many relays are running nearby to services that trust them based
9801 on network address. Bugfix on 0.1.2.x.
9804 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9805 on every successful resolve. Reported by Mike Perry; bugfix
9807 - On authorities, never downgrade to old router descriptors simply
9808 because they're listed in the consensus. This created a catch-22
9809 where we wouldn't list a new descriptor because there was an
9810 old one in the consensus, and we couldn't get the new one in the
9811 consensus because we wouldn't list it. Possible fix for bug 548.
9812 Also, this might cause bug 543 to appear on authorities; if so,
9813 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
9815 o Packaging fixes on 0.2.0.10-alpha:
9816 - We were including instructions about what to do with the
9817 src/config/fallback-consensus file, but we weren't actually
9818 including it in the tarball. Disable all of that for now.
9821 - Allow people to say PreferTunnelledDirConns rather than
9822 PreferTunneledDirConns, for those alternate-spellers out there.
9825 - Don't reevaluate all the information from our consensus document
9826 just because we've downloaded a v2 networkstatus that we intend
9827 to cache. Fixes bug 545; bugfix on 0.2.0.x.
9830 Changes in version 0.2.0.10-alpha - 2007-11-10
9831 This tenth development snapshot adds a third v3 directory authority
9832 run by Mike Perry, adds most of Karsten Loesing's new hidden service
9833 descriptor format, fixes a bad crash bug and new bridge bugs introduced
9834 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
9835 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
9836 addresses many more minor issues.
9838 o New directory authorities:
9839 - Set up ides (run by Mike Perry) as the third v3 directory authority.
9842 - Allow tunnelled directory connections to ask for an encrypted
9843 "begin_dir" connection or an anonymized "uses a full Tor circuit"
9844 connection independently. Now we can make anonymized begin_dir
9845 connections for (e.g.) more secure hidden service posting and
9847 - More progress on proposal 114: code from Karsten Loesing to
9848 implement new hidden service descriptor format.
9849 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
9850 accommodate the growing number of servers that use the default
9851 and are reaching it.
9852 - Directory authorities use a new formula for selecting which nodes
9853 to advertise as Guards: they must be in the top 7/8 in terms of
9854 how long we have known about them, and above the median of those
9855 nodes in terms of weighted fractional uptime.
9856 - Make "not enough dir info yet" warnings describe *why* Tor feels
9857 it doesn't have enough directory info yet.
9860 - Stop servers from crashing if they set a Family option (or
9861 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
9863 - Make bridge users work again -- the move to v3 directories in
9864 0.2.0.9-alpha had introduced a number of bugs that made bridges
9865 no longer work for clients.
9866 - When the clock jumps forward a lot, do not allow the bandwidth
9867 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
9869 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
9870 - When the consensus lists a router descriptor that we previously were
9871 mirroring, but that we considered non-canonical, reload the
9872 descriptor as canonical. This fixes bug 543 where Tor servers
9873 would start complaining after a few days that they don't have
9874 enough directory information to build a circuit.
9875 - Consider replacing the current consensus when certificates arrive
9876 that make the pending consensus valid. Previously, we were only
9877 considering replacement when the new certs _didn't_ help.
9878 - Fix an assert error on startup if we didn't already have the
9879 consensus and certs cached in our datadirectory: we were caching
9880 the consensus in consensus_waiting_for_certs but then free'ing it
9882 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
9883 Request) if we need more v3 certs but we've already got pending
9884 requests for all of them.
9885 - Correctly back off from failing certificate downloads. Fixes
9887 - Authorities don't vote on the Running flag if they have been running
9888 for less than 30 minutes themselves. Fixes bug 547, where a newly
9889 started authority would vote that everyone was down.
9892 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
9893 it, it had no AES, and it hasn't seen any security patches since
9897 - Clients now hold circuitless TLS connections open for 1.5 times
9898 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
9899 rebuild a new circuit over them within that timeframe. Previously,
9900 they held them open only for KeepalivePeriod (5 minutes).
9901 - Use "If-Modified-Since" to avoid retrieving consensus
9902 networkstatuses that we already have.
9903 - When we have no consensus, check FallbackNetworkstatusFile (defaults
9904 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
9905 we start knowing some directory caches.
9906 - When we receive a consensus from the future, warn about skew.
9907 - Improve skew reporting: try to give the user a better log message
9908 about how skewed they are, and how much this matters.
9909 - When we have a certificate for an authority, believe that
9910 certificate's claims about the authority's IP address.
9911 - New --quiet command-line option to suppress the default console log.
9912 Good in combination with --hash-password.
9913 - Authorities send back an X-Descriptor-Not-New header in response to
9914 an accepted-but-discarded descriptor upload. Partially implements
9916 - Make the log message for "tls error. breaking." more useful.
9917 - Better log messages about certificate downloads, to attempt to
9918 track down the second incarnation of bug 546.
9920 o Minor features (bridges):
9921 - If bridge users set UpdateBridgesFromAuthority, but the digest
9922 they ask for is a 404 from the bridge authority, they now fall
9923 back to trying the bridge directly.
9924 - Bridges now use begin_dir to publish their server descriptor to
9925 the bridge authority, even when they haven't set TunnelDirConns.
9927 o Minor features (controller):
9928 - When reporting clock skew, and we know that the clock is _at least
9929 as skewed_ as some value, but we don't know the actual value,
9930 report the value as a "minimum skew."
9933 - Update linux-tor-prio.sh script to allow QoS based on the uid of
9934 the Tor process. Patch from Marco Bonetti with tweaks from Mike
9938 - Refuse to start if both ORPort and UseBridges are set. Bugfix
9939 on 0.2.0.x, suggested by Matt Edman.
9940 - Don't stop fetching descriptors when FetchUselessDescriptors is
9941 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
9942 reported by tup and ioerror.
9943 - Better log message on vote from unknown authority.
9944 - Don't log "Launching 0 request for 0 router" message.
9946 o Minor bugfixes (memory leaks):
9947 - Stop leaking memory every time we parse a v3 certificate. Bugfix
9949 - Stop leaking memory every time we load a v3 certificate. Bugfix
9950 on 0.2.0.1-alpha. Fixes bug 536.
9951 - Stop leaking a cached networkstatus on exit. Bugfix on
9953 - Stop leaking voter information every time we free a consensus.
9954 Bugfix on 0.2.0.3-alpha.
9955 - Stop leaking signed data every time we check a voter signature.
9956 Bugfix on 0.2.0.3-alpha.
9957 - Stop leaking a signature every time we fail to parse a consensus or
9958 a vote. Bugfix on 0.2.0.3-alpha.
9959 - Stop leaking v2_download_status_map on shutdown. Bugfix on
9961 - Stop leaking conn->nickname every time we make a connection to a
9962 Tor relay without knowing its expected identity digest (e.g. when
9963 using bridges). Bugfix on 0.2.0.3-alpha.
9965 - Minor bugfixes (portability):
9966 - Run correctly on platforms where rlim_t is larger than unsigned
9967 long, and/or where the real limit for number of open files is
9968 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
9969 particular, these may be needed for OS X 10.5.
9972 Changes in version 0.1.2.18 - 2007-10-28
9973 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
9974 hidden service introduction that were causing huge delays, and a big
9975 bug that was causing some servers to disappear from the network status
9976 lists for a few hours each day.
9978 o Major bugfixes (crashes):
9979 - If a connection is shut down abruptly because of something that
9980 happened inside connection_flushed_some(), do not call
9981 connection_finished_flushing(). Should fix bug 451:
9982 "connection_stop_writing: Assertion conn->write_event failed"
9983 Bugfix on 0.1.2.7-alpha.
9984 - Fix possible segfaults in functions called from
9985 rend_process_relay_cell().
9987 o Major bugfixes (hidden services):
9988 - Hidden services were choosing introduction points uniquely by
9989 hexdigest, but when constructing the hidden service descriptor
9990 they merely wrote the (potentially ambiguous) nickname.
9991 - Clients now use the v2 intro format for hidden service
9992 connections: they specify their chosen rendezvous point by identity
9993 digest rather than by (potentially ambiguous) nickname. These
9994 changes could speed up hidden service connections dramatically.
9996 o Major bugfixes (other):
9997 - Stop publishing a new server descriptor just because we get a
9998 HUP signal. This led (in a roundabout way) to some servers getting
9999 dropped from the networkstatus lists for a few hours each day.
10000 - When looking for a circuit to cannibalize, consider family as well
10001 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10002 circuit cannibalization).
10003 - When a router wasn't listed in a new networkstatus, we were leaving
10004 the flags for that router alone -- meaning it remained Named,
10005 Running, etc -- even though absence from the networkstatus means
10006 that it shouldn't be considered to exist at all anymore. Now we
10007 clear all the flags for routers that fall out of the networkstatus
10008 consensus. Fixes bug 529.
10011 - Don't try to access (or alter) the state file when running
10012 --list-fingerprint or --verify-config or --hash-password. Resolves
10014 - When generating information telling us how to extend to a given
10015 router, do not try to include the nickname if it is
10016 absent. Resolves bug 467.
10017 - Fix a user-triggerable segfault in expand_filename(). (There isn't
10018 a way to trigger this remotely.)
10019 - When sending a status event to the controller telling it that an
10020 OR address is reachable, set the port correctly. (Previously we
10021 were reporting the dir port.)
10022 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10023 command. Bugfix on 0.1.2.17.
10024 - When loading bandwidth history, do not believe any information in
10025 the future. Fixes bug 434.
10026 - When loading entry guard information, do not believe any information
10028 - When we have our clock set far in the future and generate an
10029 onion key, then re-set our clock to be correct, we should not stop
10030 the onion key from getting rotated.
10031 - On some platforms, accept() can return a broken address. Detect
10032 this more quietly, and deal accordingly. Fixes bug 483.
10033 - It's not actually an error to find a non-pending entry in the DNS
10034 cache when canceling a pending resolve. Don't log unless stuff
10035 is fishy. Resolves bug 463.
10036 - Don't reset trusted dir server list when we set a configuration
10037 option. Patch from Robert Hogan.
10038 - Don't try to create the datadir when running --verify-config or
10039 --hash-password. Resolves bug 540.
10042 Changes in version 0.2.0.9-alpha - 2007-10-24
10043 This ninth development snapshot switches clients to the new v3 directory
10044 system; allows servers to be listed in the network status even when they
10045 have the same nickname as a registered server; and fixes many other
10046 bugs including a big one that was causing some servers to disappear
10047 from the network status lists for a few hours each day.
10049 o Major features (directory system):
10050 - Clients now download v3 consensus networkstatus documents instead
10051 of v2 networkstatus documents. Clients and caches now base their
10052 opinions about routers on these consensus documents. Clients only
10053 download router descriptors listed in the consensus.
10054 - Authorities now list servers who have the same nickname as
10055 a different named server, but list them with a new flag,
10056 "Unnamed". Now we can list servers that happen to pick the same
10057 nickname as a server that registered two years ago and then
10058 disappeared. Partially implements proposal 122.
10059 - If the consensus lists a router as "Unnamed", the name is assigned
10060 to a different router: do not identify the router by that name.
10061 Partially implements proposal 122.
10062 - Authorities can now come to a consensus on which method to use to
10063 compute the consensus. This gives us forward compatibility.
10066 - Stop publishing a new server descriptor just because we HUP or
10067 when we find our DirPort to be reachable but won't actually publish
10068 it. New descriptors without any real changes are dropped by the
10069 authorities, and can screw up our "publish every 18 hours" schedule.
10071 - When a router wasn't listed in a new networkstatus, we were leaving
10072 the flags for that router alone -- meaning it remained Named,
10073 Running, etc -- even though absence from the networkstatus means
10074 that it shouldn't be considered to exist at all anymore. Now we
10075 clear all the flags for routers that fall out of the networkstatus
10076 consensus. Fixes bug 529; bugfix on 0.1.2.x.
10077 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
10078 extrainfo documents and then discard them immediately for not
10079 matching the latest router. Bugfix on 0.2.0.1-alpha.
10081 o Minor features (v3 directory protocol):
10082 - Allow tor-gencert to generate a new certificate without replacing
10084 - Allow certificates to include an address.
10085 - When we change our directory-cache settings, reschedule all voting
10086 and download operations.
10087 - Reattempt certificate downloads immediately on failure, as long as
10088 we haven't failed a threshold number of times yet.
10089 - Delay retrying consensus downloads while we're downloading
10090 certificates to verify the one we just got. Also, count getting a
10091 consensus that we already have (or one that isn't valid) as a failure,
10092 and count failing to get the certificates after 20 minutes as a
10094 - Build circuits and download descriptors even if our consensus is a
10095 little expired. (This feature will go away once authorities are
10098 o Minor features (router descriptor cache):
10099 - If we find a cached-routers file that's been sitting around for more
10100 than 28 days unmodified, then most likely it's a leftover from
10101 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
10103 - When we (as a cache) download a descriptor because it was listed
10104 in a consensus, remember when the consensus was supposed to expire,
10105 and don't expire the descriptor until then.
10107 o Minor features (performance):
10108 - Call routerlist_remove_old_routers() much less often. This should
10109 speed startup, especially on directory caches.
10110 - Don't try to launch new descriptor downloads quite so often when we
10111 already have enough directory information to build circuits.
10112 - Base64 decoding was actually showing up on our profile when parsing
10113 the initial descriptor file; switch to an in-process all-at-once
10114 implementation that's about 3.5x times faster than calling out to
10117 o Minor features (compilation):
10118 - Detect non-ASCII platforms (if any still exist) and refuse to
10119 build there: some of our code assumes that 'A' is 65 and so on.
10121 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
10122 - Make the "next period" votes into "current period" votes immediately
10123 after publishing the consensus; avoid a heisenbug that made them
10124 stick around indefinitely.
10125 - When we discard a vote as a duplicate, do not report this as
10127 - Treat missing v3 keys or certificates as an error when running as a
10128 v3 directory authority.
10129 - When we're configured to be a v3 authority, but we're only listed
10130 as a non-v3 authority in our DirServer line for ourself, correct
10132 - If an authority doesn't have a qualified hostname, just put
10133 its address in the vote. This fixes the problem where we referred to
10134 "moria on moria:9031."
10135 - Distinguish between detached signatures for the wrong period, and
10136 detached signatures for a divergent vote.
10137 - Fix a small memory leak when computing a consensus.
10138 - When there's no concensus, we were forming a vote every 30
10139 minutes, but writing the "valid-after" line in our vote based
10140 on our configured V3AuthVotingInterval: so unless the intervals
10141 matched up, we immediately rejected our own vote because it didn't
10142 start at the voting interval that caused us to construct a vote.
10144 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
10145 - Delete unverified-consensus when the real consensus is set.
10146 - Consider retrying a consensus networkstatus fetch immediately
10147 after one fails: don't wait 60 seconds to notice.
10148 - When fetching a consensus as a cache, wait until a newer consensus
10149 should exist before trying to replace the current one.
10150 - Use a more forgiving schedule for retrying failed consensus
10151 downloads than for other types.
10153 o Minor bugfixes (other directory issues):
10154 - Correct the implementation of "download votes by digest." Bugfix on
10156 - Authorities no longer send back "400 you're unreachable please fix
10157 it" errors to Tor servers that aren't online all the time. We're
10158 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
10160 o Minor bugfixes (controller):
10161 - Don't reset trusted dir server list when we set a configuration
10162 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
10163 - Respond to INT and TERM SIGNAL commands before we execute the
10164 signal, in case the signal shuts us down. We had a patch in
10165 0.1.2.1-alpha that tried to do this by queueing the response on
10166 the connection's buffer before shutting down, but that really
10167 isn't the same thing at all. Bug located by Matt Edman.
10169 o Minor bugfixes (misc):
10170 - Correctly check for bad options to the "PublishServerDescriptor"
10171 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
10172 - Stop leaking memory on failing case of base32_decode, and make
10173 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
10174 - Don't try to download extrainfo documents when we're trying to
10175 fetch enough directory info to build a circuit: having enough
10176 info should get priority. Bugfix on 0.2.0.x.
10177 - Don't complain that "your server has not managed to confirm that its
10178 ports are reachable" if we haven't been able to build any circuits
10179 yet. Bug found by spending four hours without a v3 consensus. Bugfix
10181 - Detect the reason for failing to mmap a descriptor file we just
10182 wrote, and give a more useful log message. Fixes bug 533. Bugfix
10185 o Code simplifications and refactoring:
10186 - Remove support for the old bw_accounting file: we've been storing
10187 bandwidth accounting information in the state file since
10188 0.1.2.5-alpha. This may result in bandwidth accounting errors
10189 if you try to upgrade from 0.1.1.x or earlier, or if you try to
10190 downgrade to 0.1.1.x or earlier.
10191 - New convenience code to locate a file within the DataDirectory.
10192 - Move non-authority functionality out of dirvote.c.
10193 - Refactor the arguments for router_pick_{directory_|trusteddir}server
10194 so that they all take the same named flags.
10197 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
10198 Unix users an easy way to script their Tor process (e.g. by
10199 adjusting bandwidth based on the time of the day).
10202 Changes in version 0.2.0.8-alpha - 2007-10-12
10203 This eighth development snapshot fixes a crash bug that's been bothering
10204 us since February 2007, lets bridge authorities store a list of bridge
10205 descriptors they've seen, gets v3 directory voting closer to working,
10206 starts caching v3 directory consensus documents on directory mirrors,
10207 and fixes a variety of smaller issues including some minor memory leaks.
10209 o Major features (router descriptor cache):
10210 - Store routers in a file called cached-descriptors instead of in
10211 cached-routers. Initialize cached-descriptors from cached-routers
10212 if the old format is around. The new format allows us to store
10213 annotations along with descriptors.
10214 - Use annotations to record the time we received each descriptor, its
10215 source, and its purpose.
10216 - Disable the SETROUTERPURPOSE controller command: it is now
10218 - Controllers should now specify cache=no or cache=yes when using
10219 the +POSTDESCRIPTOR command.
10220 - Bridge authorities now write bridge descriptors to disk, meaning
10221 we can export them to other programs and begin distributing them
10224 o Major features (directory authorities):
10225 - When a v3 authority is missing votes or signatures, it now tries
10227 - Directory authorities track weighted fractional uptime as well as
10228 weighted mean-time-between failures. WFU is suitable for deciding
10229 whether a node is "usually up", while MTBF is suitable for deciding
10230 whether a node is "likely to stay up." We need both, because
10231 "usually up" is a good requirement for guards, while "likely to
10232 stay up" is a good requirement for long-lived connections.
10234 o Major features (v3 directory system):
10235 - Caches now download v3 network status documents as needed,
10236 and download the descriptors listed in them.
10237 - All hosts now attempt to download and keep fresh v3 authority
10238 certificates, and re-attempt after failures.
10239 - More internal-consistency checks for vote parsing.
10241 o Major bugfixes (crashes):
10242 - If a connection is shut down abruptly because of something that
10243 happened inside connection_flushed_some(), do not call
10244 connection_finished_flushing(). Should fix bug 451. Bugfix on
10247 o Major bugfixes (performance):
10248 - Fix really bad O(n^2) performance when parsing a long list of
10249 routers: Instead of searching the entire list for an "extra-info "
10250 string which usually wasn't there, once for every routerinfo
10251 we read, just scan lines forward until we find one we like.
10253 - When we add data to a write buffer in response to the data on that
10254 write buffer getting low because of a flush, do not consider the
10255 newly added data as a candidate for immediate flushing, but rather
10256 make it wait until the next round of writing. Otherwise, we flush
10257 and refill recursively, and a single greedy TLS connection can
10258 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
10260 o Minor features (v3 authority system):
10261 - Add more ways for tools to download the votes that lead to the
10263 - Send a 503 when low on bandwidth and a vote, consensus, or
10264 certificate is requested.
10265 - If-modified-since is now implemented properly for all kinds of
10266 certificate requests.
10268 o Minor bugfixes (network statuses):
10269 - Tweak the implementation of proposal 109 slightly: allow at most
10270 two Tor servers on the same IP address, except if it's the location
10271 of a directory authority, in which case allow five. Bugfix on
10274 o Minor bugfixes (controller):
10275 - When sending a status event to the controller telling it that an
10276 OR address is reachable, set the port correctly. (Previously we
10277 were reporting the dir port.) Bugfix on 0.1.2.x.
10279 o Minor bugfixes (v3 directory system):
10280 - Fix logic to look up a cert by its signing key digest. Bugfix on
10282 - Only change the reply to a vote to "OK" if it's not already
10283 set. This gets rid of annoying "400 OK" log messages, which may
10284 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
10285 - When we get a valid consensus, recompute the voting schedule.
10286 - Base the valid-after time of a vote on the consensus voting
10287 schedule, not on our preferred schedule.
10288 - Make the return values and messages from signature uploads and
10289 downloads more sensible.
10290 - Fix a memory leak when serving votes and consensus documents, and
10291 another when serving certificates.
10293 o Minor bugfixes (performance):
10294 - Use a slightly simpler string hashing algorithm (copying Python's
10295 instead of Java's) and optimize our digest hashing algorithm to take
10296 advantage of 64-bit platforms and to remove some possibly-costly
10298 - Fix a minor memory leak whenever we parse guards from our state
10299 file. Bugfix on 0.2.0.7-alpha.
10300 - Fix a minor memory leak whenever we write out a file. Bugfix on
10302 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10303 command. Bugfix on 0.2.0.5-alpha.
10305 o Minor bugfixes (portability):
10306 - On some platforms, accept() can return a broken address. Detect
10307 this more quietly, and deal accordingly. Fixes bug 483.
10308 - Stop calling tor_strlower() on uninitialized memory in some cases.
10309 Bugfix in 0.2.0.7-alpha.
10311 o Minor bugfixes (usability):
10312 - Treat some 403 responses from directory servers as INFO rather than
10313 WARN-severity events.
10314 - It's not actually an error to find a non-pending entry in the DNS
10315 cache when canceling a pending resolve. Don't log unless stuff is
10316 fishy. Resolves bug 463.
10318 o Minor bugfixes (anonymity):
10319 - Never report that we've used more bandwidth than we're willing to
10320 relay: it leaks how much non-relay traffic we're using. Resolves
10322 - When looking for a circuit to cannibalize, consider family as well
10323 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10324 circuit cannibalization).
10326 o Code simplifications and refactoring:
10327 - Make a bunch of functions static. Remove some dead code.
10328 - Pull out about a third of the really big routerlist.c; put it in a
10329 new module, networkstatus.c.
10330 - Merge the extra fields in local_routerstatus_t back into
10331 routerstatus_t: we used to need one routerstatus_t for each
10332 authority's opinion, plus a local_routerstatus_t for the locally
10333 computed consensus opinion. To save space, we put the locally
10334 modified fields into local_routerstatus_t, and only the common
10335 stuff into routerstatus_t. But once v3 directories are in use,
10336 clients and caches will no longer need to hold authority opinions;
10337 thus, the rationale for keeping the types separate is now gone.
10338 - Make the code used to reschedule and reattempt downloads more
10340 - Turn all 'Are we a directory server/mirror?' logic into a call to
10342 - Remove the code to generate the oldest (v1) directory format.
10343 The code has been disabled since 0.2.0.5-alpha.
10346 Changes in version 0.2.0.7-alpha - 2007-09-21
10347 This seventh development snapshot makes bridges work again, makes bridge
10348 authorities work for the first time, fixes two huge performance flaws
10349 in hidden services, and fixes a variety of minor issues.
10351 o New directory authorities:
10352 - Set up moria1 and tor26 as the first v3 directory authorities. See
10353 doc/spec/dir-spec.txt for details on the new directory design.
10355 o Major bugfixes (crashes):
10356 - Fix possible segfaults in functions called from
10357 rend_process_relay_cell(). Bugfix on 0.1.2.x.
10359 o Major bugfixes (bridges):
10360 - Fix a bug that made servers send a "404 Not found" in response to
10361 attempts to fetch their server descriptor. This caused Tor servers
10362 to take many minutes to establish reachability for their DirPort,
10363 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
10364 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
10365 users configure that and specify a bridge with an identity
10366 fingerprint, now they will lookup the bridge descriptor at the
10367 default bridge authority via a one-hop tunnel, but once circuits
10368 are established they will switch to a three-hop tunnel for later
10369 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
10371 o Major bugfixes (hidden services):
10372 - Hidden services were choosing introduction points uniquely by
10373 hexdigest, but when constructing the hidden service descriptor
10374 they merely wrote the (potentially ambiguous) nickname.
10375 - Clients now use the v2 intro format for hidden service
10376 connections: they specify their chosen rendezvous point by identity
10377 digest rather than by (potentially ambiguous) nickname. Both
10378 are bugfixes on 0.1.2.x, and they could speed up hidden service
10379 connections dramatically. Thanks to Karsten Loesing.
10381 o Minor features (security):
10382 - As a client, do not believe any server that tells us that an
10383 address maps to an internal address space.
10384 - Make it possible to enable HashedControlPassword and
10385 CookieAuthentication at the same time.
10387 o Minor features (guard nodes):
10388 - Tag every guard node in our state file with the version that
10389 we believe added it, or with our own version if we add it. This way,
10390 if a user temporarily runs an old version of Tor and then switches
10391 back to a new one, she doesn't automatically lose her guards.
10393 o Minor features (speed):
10394 - When implementing AES counter mode, update only the portions of the
10395 counter buffer that need to change, and don't keep separate
10396 network-order and host-order counters when they are the same (i.e.,
10397 on big-endian hosts.)
10399 o Minor features (controller):
10400 - Accept LF instead of CRLF on controller, since some software has a
10401 hard time generating real Internet newlines.
10402 - Add GETINFO values for the server status events
10403 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
10406 o Removed features:
10407 - Routers no longer include bandwidth-history lines in their
10408 descriptors; this information is already available in extra-info
10409 documents, and including it in router descriptors took up 60%
10410 (!) of compressed router descriptor downloads. Completes
10411 implementation of proposal 104.
10412 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
10413 and TorControl.py, as they use the old v0 controller protocol,
10414 and are obsoleted by TorFlow anyway.
10415 - Drop support for v1 rendezvous descriptors, since we never used
10416 them anyway, and the code has probably rotted by now. Based on
10417 patch from Karsten Loesing.
10418 - On OSX, stop warning the user that kqueue support in libevent is
10419 "experimental", since it seems to have worked fine for ages.
10422 - When generating information telling us how to extend to a given
10423 router, do not try to include the nickname if it is absent. Fixes
10424 bug 467. Bugfix on 0.2.0.3-alpha.
10425 - Fix a user-triggerable (but not remotely-triggerable) segfault
10426 in expand_filename(). Bugfix on 0.1.2.x.
10427 - Fix a memory leak when freeing incomplete requests from DNSPort.
10428 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
10429 - Don't try to access (or alter) the state file when running
10430 --list-fingerprint or --verify-config or --hash-password. (Resolves
10431 bug 499.) Bugfix on 0.1.2.x.
10432 - Servers used to decline to publish their DirPort if their
10433 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
10434 were below a threshold. Now they only look at BandwidthRate and
10435 RelayBandwidthRate. Bugfix on 0.1.2.x.
10436 - Remove an optimization in the AES counter-mode code that assumed
10437 that the counter never exceeded 2^68. When the counter can be set
10438 arbitrarily as an IV (as it is by Karsten's new hidden services
10439 code), this assumption no longer holds. Bugfix on 0.1.2.x.
10440 - Resume listing "AUTHORITY" flag for authorities in network status.
10441 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
10443 o Code simplifications and refactoring:
10444 - Revamp file-writing logic so we don't need to have the entire
10445 contents of a file in memory at once before we write to disk. Tor,
10447 - Turn "descriptor store" into a full-fledged type.
10448 - Move all NT services code into a separate source file.
10449 - Unify all code that computes medians, percentile elements, etc.
10450 - Get rid of a needless malloc when parsing address policies.
10453 Changes in version 0.1.2.17 - 2007-08-30
10454 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
10455 X bundles. Vidalia 0.0.14 makes authentication required for the
10456 ControlPort in the default configuration, which addresses important
10457 security risks. Everybody who uses Vidalia (or another controller)
10460 In addition, this Tor update fixes major load balancing problems with
10461 path selection, which should speed things up a lot once many people
10464 o Major bugfixes (security):
10465 - We removed support for the old (v0) control protocol. It has been
10466 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
10467 become more of a headache than it's worth.
10469 o Major bugfixes (load balancing):
10470 - When choosing nodes for non-guard positions, weight guards
10471 proportionally less, since they already have enough load. Patch
10473 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10474 will allow fast Tor servers to get more attention.
10475 - When we're upgrading from an old Tor version, forget our current
10476 guards and pick new ones according to the new weightings. These
10477 three load balancing patches could raise effective network capacity
10478 by a factor of four. Thanks to Mike Perry for measurements.
10480 o Major bugfixes (stream expiration):
10481 - Expire not-yet-successful application streams in all cases if
10482 they've been around longer than SocksTimeout. Right now there are
10483 some cases where the stream will live forever, demanding a new
10484 circuit every 15 seconds. Fixes bug 454; reported by lodger.
10486 o Minor features (controller):
10487 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10488 is valid before any authentication has been received. It tells
10489 a controller what kind of authentication is expected, and what
10490 protocol is spoken. Implements proposal 119.
10492 o Minor bugfixes (performance):
10493 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
10494 greatly speeding up loading cached-routers from disk on startup.
10495 - Disable sentinel-based debugging for buffer code: we squashed all
10496 the bugs that this was supposed to detect a long time ago, and now
10497 its only effect is to change our buffer sizes from nice powers of
10498 two (which platform mallocs tend to like) to values slightly over
10499 powers of two (which make some platform mallocs sad).
10501 o Minor bugfixes (misc):
10502 - If exit bandwidth ever exceeds one third of total bandwidth, then
10503 use the correct formula to weight exit nodes when choosing paths.
10504 Based on patch from Mike Perry.
10505 - Choose perfectly fairly among routers when choosing by bandwidth and
10506 weighting by fraction of bandwidth provided by exits. Previously, we
10507 would choose with only approximate fairness, and correct ourselves
10508 if we ran off the end of the list.
10509 - If we require CookieAuthentication but we fail to write the
10510 cookie file, we would warn but not exit, and end up in a state
10511 where no controller could authenticate. Now we exit.
10512 - If we require CookieAuthentication, stop generating a new cookie
10513 every time we change any piece of our config.
10514 - Refuse to start with certain directory authority keys, and
10515 encourage people using them to stop.
10516 - Terminate multi-line control events properly. Original patch
10518 - Fix a minor memory leak when we fail to find enough suitable
10519 servers to choose a circuit.
10520 - Stop leaking part of the descriptor when we run into a particularly
10521 unparseable piece of it.
10524 Changes in version 0.2.0.6-alpha - 2007-08-26
10525 This sixth development snapshot features a new Vidalia version in the
10526 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
10527 the ControlPort in the default configuration, which addresses important
10530 In addition, this snapshot fixes major load balancing problems
10531 with path selection, which should speed things up a lot once many
10532 people have upgraded. The directory authorities also use a new
10533 mean-time-between-failure approach to tracking which servers are stable,
10534 rather than just looking at the most recent uptime.
10536 o New directory authorities:
10537 - Set up Tonga as the default bridge directory authority.
10540 - Directory authorities now track servers by weighted
10541 mean-times-between-failures. When we have 4 or more days of data,
10542 use measured MTBF rather than declared uptime to decide whether
10543 to call a router Stable. Implements proposal 108.
10545 o Major bugfixes (load balancing):
10546 - When choosing nodes for non-guard positions, weight guards
10547 proportionally less, since they already have enough load. Patch
10549 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10550 will allow fast Tor servers to get more attention.
10551 - When we're upgrading from an old Tor version, forget our current
10552 guards and pick new ones according to the new weightings. These
10553 three load balancing patches could raise effective network capacity
10554 by a factor of four. Thanks to Mike Perry for measurements.
10556 o Major bugfixes (descriptor parsing):
10557 - Handle unexpected whitespace better in malformed descriptors. Bug
10558 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
10561 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
10562 GETINFO for Torstat to use until it can switch to using extrainfos.
10563 - Optionally (if built with -DEXPORTMALLINFO) export the output
10564 of mallinfo via http, as tor/mallinfo.txt. Only accessible
10568 - Do not intermix bridge routers with controller-added
10569 routers. (Bugfix on 0.2.0.x)
10570 - Do not fail with an assert when accept() returns an unexpected
10571 address family. Addresses but does not wholly fix bug 483. (Bugfix
10573 - Let directory authorities startup even when they can't generate
10574 a descriptor immediately, e.g. because they don't know their
10576 - Stop putting the authentication cookie in a file called "0"
10577 in your working directory if you don't specify anything for the
10578 new CookieAuthFile option. Reported by Matt Edman.
10579 - Make it possible to read the PROTOCOLINFO response in a way that
10580 conforms to our control-spec. Reported by Matt Edman.
10581 - Fix a minor memory leak when we fail to find enough suitable
10582 servers to choose a circuit. Bugfix on 0.1.2.x.
10583 - Stop leaking part of the descriptor when we run into a particularly
10584 unparseable piece of it. Bugfix on 0.1.2.x.
10585 - Unmap the extrainfo cache file on exit.
10588 Changes in version 0.2.0.5-alpha - 2007-08-19
10589 This fifth development snapshot fixes compilation on Windows again;
10590 fixes an obnoxious client-side bug that slowed things down and put
10591 extra load on the network; gets us closer to using the v3 directory
10592 voting scheme; makes it easier for Tor controllers to use cookie-based
10593 authentication; and fixes a variety of other bugs.
10595 o Removed features:
10596 - Version 1 directories are no longer generated in full. Instead,
10597 authorities generate and serve "stub" v1 directories that list
10598 no servers. This will stop Tor versions 0.1.0.x and earlier from
10599 working, but (for security reasons) nobody should be running those
10602 o Major bugfixes (compilation, 0.2.0.x):
10603 - Try to fix Win32 compilation again: improve checking for IPv6 types.
10604 - Try to fix MSVC compilation: build correctly on platforms that do
10605 not define s6_addr16 or s6_addr32.
10606 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
10609 o Major bugfixes (stream expiration):
10610 - Expire not-yet-successful application streams in all cases if
10611 they've been around longer than SocksTimeout. Right now there are
10612 some cases where the stream will live forever, demanding a new
10613 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
10614 reported by lodger.
10616 o Minor features (directory servers):
10617 - When somebody requests a list of statuses or servers, and we have
10618 none of those, return a 404 rather than an empty 200.
10620 o Minor features (directory voting):
10621 - Store v3 consensus status consensuses on disk, and reload them
10624 o Minor features (security):
10625 - Warn about unsafe ControlPort configurations.
10626 - Refuse to start with certain directory authority keys, and
10627 encourage people using them to stop.
10629 o Minor features (controller):
10630 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10631 is valid before any authentication has been received. It tells
10632 a controller what kind of authentication is expected, and what
10633 protocol is spoken. Implements proposal 119.
10634 - New config option CookieAuthFile to choose a new location for the
10635 cookie authentication file, and config option
10636 CookieAuthFileGroupReadable to make it group-readable.
10638 o Minor features (unit testing):
10639 - Add command-line arguments to unit-test executable so that we can
10640 invoke any chosen test from the command line rather than having
10641 to run the whole test suite at once; and so that we can turn on
10642 logging for the unit tests.
10644 o Minor bugfixes (on 0.1.2.x):
10645 - If we require CookieAuthentication but we fail to write the
10646 cookie file, we would warn but not exit, and end up in a state
10647 where no controller could authenticate. Now we exit.
10648 - If we require CookieAuthentication, stop generating a new cookie
10649 every time we change any piece of our config.
10650 - When loading bandwidth history, do not believe any information in
10651 the future. Fixes bug 434.
10652 - When loading entry guard information, do not believe any information
10654 - When we have our clock set far in the future and generate an
10655 onion key, then re-set our clock to be correct, we should not stop
10656 the onion key from getting rotated.
10657 - Clean up torrc sample config file.
10658 - Do not automatically run configure from autogen.sh. This
10659 non-standard behavior tended to annoy people who have built other
10662 o Minor bugfixes (on 0.2.0.x):
10663 - Fix a bug with AutomapHostsOnResolve that would always cause
10664 the second request to fail. Bug reported by Kate. Bugfix on
10666 - Fix a bug in ADDRMAP controller replies that would sometimes
10667 try to print a NULL. Patch from tup.
10668 - Read v3 directory authority keys from the right location.
10669 - Numerous bugfixes to directory voting code.
10672 Changes in version 0.1.2.16 - 2007-08-01
10673 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
10674 remote attacker in certain situations to rewrite the user's torrc
10675 configuration file. This can completely compromise anonymity of users
10676 in most configurations, including those running the Vidalia bundles,
10677 TorK, etc. Or worse.
10679 o Major security fixes:
10680 - Close immediately after missing authentication on control port;
10681 do not allow multiple authentication attempts.
10684 Changes in version 0.2.0.4-alpha - 2007-08-01
10685 This fourth development snapshot fixes a critical security vulnerability
10686 for most users, specifically those running Vidalia, TorK, etc. Everybody
10687 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
10689 o Major security fixes:
10690 - Close immediately after missing authentication on control port;
10691 do not allow multiple authentication attempts.
10693 o Major bugfixes (compilation):
10694 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
10697 o Minor features (performance):
10698 - Be even more aggressive about releasing RAM from small
10699 empty buffers. Thanks to our free-list code, this shouldn't be too
10700 performance-intensive.
10701 - Disable sentinel-based debugging for buffer code: we squashed all
10702 the bugs that this was supposed to detect a long time ago, and
10703 now its only effect is to change our buffer sizes from nice
10704 powers of two (which platform mallocs tend to like) to values
10705 slightly over powers of two (which make some platform mallocs sad).
10706 - Log malloc statistics from mallinfo() on platforms where it
10710 Changes in version 0.2.0.3-alpha - 2007-07-29
10711 This third development snapshot introduces new experimental
10712 blocking-resistance features and a preliminary version of the v3
10713 directory voting design, and includes many other smaller features
10717 - The first pieces of our "bridge" design for blocking-resistance
10718 are implemented. People can run bridge directory authorities;
10719 people can run bridges; and people can configure their Tor clients
10720 with a set of bridges to use as the first hop into the Tor network.
10721 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
10723 - Create listener connections before we setuid to the configured
10724 User and Group. Now non-Windows users can choose port values
10725 under 1024, start Tor as root, and have Tor bind those ports
10726 before it changes to another UID. (Windows users could already
10728 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
10729 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
10730 on "vserver" accounts. (Patch from coderman.)
10731 - Be even more aggressive about separating local traffic from relayed
10732 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
10734 o Major features (experimental):
10735 - First cut of code for "v3 dir voting": directory authorities will
10736 vote on a common network status document rather than each publishing
10737 their own opinion. This code needs more testing and more corner-case
10738 handling before it's ready for use.
10741 - Directory authorities now call routers Fast if their bandwidth is
10742 at least 100KB/s, and consider their bandwidth adequate to be a
10743 Guard if it is at least 250KB/s, no matter the medians. This fix
10744 complements proposal 107. [Bugfix on 0.1.2.x]
10745 - Directory authorities now never mark more than 3 servers per IP as
10746 Valid and Running. (Implements proposal 109, by Kevin Bauer and
10748 - Minor change to organizationName and commonName generation
10749 procedures in TLS certificates during Tor handshakes, to invalidate
10750 some earlier censorware approaches. This is not a long-term
10751 solution, but applying it will give us a bit of time to look into
10752 the epidemiology of countermeasures as they spread.
10754 o Major bugfixes (directory):
10755 - Rewrite directory tokenization code to never run off the end of
10756 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
10758 o Minor features (controller):
10759 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
10760 match requests to applications. (Patch from Robert Hogan.)
10761 - Report address and port correctly on connections to DNSPort. (Patch
10762 from Robert Hogan.)
10763 - Add a RESOLVE command to launch hostname lookups. (Original patch
10764 from Robert Hogan.)
10765 - Add GETINFO status/enough-dir-info to let controllers tell whether
10766 Tor has downloaded sufficient directory information. (Patch
10768 - You can now use the ControlSocket option to tell Tor to listen for
10769 controller connections on Unix domain sockets on systems that
10770 support them. (Patch from Peter Palfrader.)
10771 - STREAM NEW events are generated for DNSPort requests and for
10772 tunneled directory connections. (Patch from Robert Hogan.)
10773 - New "GETINFO address-mappings/*" command to get address mappings
10774 with expiry information. "addr-mappings/*" is now deprecated.
10777 o Minor features (misc):
10778 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
10780 - The tor-gencert tool for v3 directory authorities now creates all
10781 files as readable to the file creator only, and write-protects
10782 the authority identity key.
10783 - When dumping memory usage, list bytes used in buffer memory
10785 - When running with dmalloc, dump more stats on hup and on exit.
10786 - Directory authorities now fail quickly and (relatively) harmlessly
10787 if they generate a network status document that is somehow
10790 o Traffic load balancing improvements:
10791 - If exit bandwidth ever exceeds one third of total bandwidth, then
10792 use the correct formula to weight exit nodes when choosing paths.
10793 (Based on patch from Mike Perry.)
10794 - Choose perfectly fairly among routers when choosing by bandwidth and
10795 weighting by fraction of bandwidth provided by exits. Previously, we
10796 would choose with only approximate fairness, and correct ourselves
10797 if we ran off the end of the list. [Bugfix on 0.1.2.x]
10799 o Performance improvements:
10800 - Be more aggressive with freeing buffer RAM or putting it on the
10802 - Use Critical Sections rather than Mutexes for synchronizing threads
10803 on win32; Mutexes are heavier-weight, and designed for synchronizing
10806 o Deprecated and removed features:
10807 - RedirectExits is now deprecated.
10808 - Stop allowing address masks that do not correspond to bit prefixes.
10809 We have warned about these for a really long time; now it's time
10810 to reject them. (Patch from croup.)
10812 o Minor bugfixes (directory):
10813 - Fix another crash bug related to extra-info caching. (Bug found by
10814 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
10815 - Directories no longer return a "304 not modified" when they don't
10816 have the networkstatus the client asked for. Also fix a memory
10817 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
10818 - We had accidentally labelled 0.1.2.x directory servers as not
10819 suitable for begin_dir requests, and had labelled no directory
10820 servers as suitable for uploading extra-info documents. [Bugfix
10823 o Minor bugfixes (dns):
10824 - Fix a crash when DNSPort is set more than once. (Patch from Robert
10825 Hogan.) [Bugfix on 0.2.0.2-alpha]
10826 - Add DNSPort connections to the global connection list, so that we
10827 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
10829 - Fix a dangling reference that could lead to a crash when DNSPort is
10830 changed or closed (Patch from Robert Hogan.) [Bugfix on
10833 o Minor bugfixes (controller):
10834 - Provide DNS expiry times in GMT, not in local time. For backward
10835 compatibility, ADDRMAP events only provide GMT expiry in an extended
10836 field. "GETINFO address-mappings" always does the right thing.
10837 - Use CRLF line endings properly in NS events.
10838 - Terminate multi-line control events properly. (Original patch
10839 from tup.) [Bugfix on 0.1.2.x-alpha]
10840 - Do not include spaces in SOURCE_ADDR fields in STREAM
10841 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
10844 Changes in version 0.1.2.15 - 2007-07-17
10845 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
10846 problems, fixes compilation on BSD, and fixes a variety of other
10847 bugs. Everybody should upgrade.
10849 o Major bugfixes (compilation):
10850 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
10852 o Major bugfixes (crashes):
10853 - Try even harder not to dereference the first character after
10854 an mmap(). Reported by lodger.
10855 - Fix a crash bug in directory authorities when we re-number the
10856 routerlist while inserting a new router.
10857 - When the cached-routers file is an even multiple of the page size,
10858 don't run off the end and crash. (Fixes bug 455; based on idea
10860 - Fix eventdns.c behavior on Solaris: It is critical to include
10861 orconfig.h _before_ sys/types.h, so that we can get the expected
10862 definition of _FILE_OFFSET_BITS.
10864 o Major bugfixes (security):
10865 - Fix a possible buffer overrun when using BSD natd support. Bug
10867 - When sending destroy cells from a circuit's origin, don't include
10868 the reason for tearing down the circuit. The spec says we didn't,
10869 and now we actually don't. Reported by lodger.
10870 - Keep streamids from different exits on a circuit separate. This
10871 bug may have allowed other routers on a given circuit to inject
10872 cells into streams. Reported by lodger; fixes bug 446.
10873 - If there's a never-before-connected-to guard node in our list,
10874 never choose any guards past it. This way we don't expand our
10875 guard list unless we need to.
10877 o Minor bugfixes (guard nodes):
10878 - Weight guard selection by bandwidth, so that low-bandwidth nodes
10879 don't get overused as guards.
10881 o Minor bugfixes (directory):
10882 - Correctly count the number of authorities that recommend each
10883 version. Previously, we were under-counting by 1.
10884 - Fix a potential crash bug when we load many server descriptors at
10885 once and some of them make others of them obsolete. Fixes bug 458.
10887 o Minor bugfixes (hidden services):
10888 - Stop tearing down the whole circuit when the user asks for a
10889 connection to a port that the hidden service didn't configure.
10892 o Minor bugfixes (misc):
10893 - On Windows, we were preventing other processes from reading
10894 cached-routers while Tor was running. Reported by janbar.
10895 - Fix a possible (but very unlikely) bug in picking routers by
10896 bandwidth. Add a log message to confirm that it is in fact
10897 unlikely. Patch from lodger.
10898 - Backport a couple of memory leak fixes.
10899 - Backport miscellaneous cosmetic bugfixes.
10902 Changes in version 0.2.0.2-alpha - 2007-06-02
10903 o Major bugfixes on 0.2.0.1-alpha:
10904 - Fix an assertion failure related to servers without extra-info digests.
10905 Resolves bugs 441 and 442.
10907 o Minor features (directory):
10908 - Support "If-Modified-Since" when answering HTTP requests for
10909 directories, running-routers documents, and network-status documents.
10910 (There's no need to support it for router descriptors, since those
10911 are downloaded by descriptor digest.)
10913 o Minor build issues:
10914 - Clear up some MIPSPro compiler warnings.
10915 - When building from a tarball on a machine that happens to have SVK
10916 installed, report the micro-revision as whatever version existed
10917 in the tarball, not as "x".
10920 Changes in version 0.2.0.1-alpha - 2007-06-01
10921 This early development snapshot provides new features for people running
10922 Tor as both a client and a server (check out the new RelayBandwidth
10923 config options); lets Tor run as a DNS proxy; and generally moves us
10924 forward on a lot of fronts.
10926 o Major features, server usability:
10927 - New config options RelayBandwidthRate and RelayBandwidthBurst:
10928 a separate set of token buckets for relayed traffic. Right now
10929 relayed traffic is defined as answers to directory requests, and
10930 OR connections that don't have any local circuits on them.
10932 o Major features, client usability:
10933 - A client-side DNS proxy feature to replace the need for
10934 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
10935 for DNS requests on port 9999, use the Tor network to resolve them
10936 anonymously, and send the reply back like a regular DNS server.
10937 The code still only implements a subset of DNS.
10938 - Make PreferTunneledDirConns and TunnelDirConns work even when
10939 we have no cached directory info. This means Tor clients can now
10940 do all of their connections protected by TLS.
10942 o Major features, performance and efficiency:
10943 - Directory authorities accept and serve "extra info" documents for
10944 routers. These documents contain fields from router descriptors
10945 that aren't usually needed, and that use a lot of excess
10946 bandwidth. Once these fields are removed from router descriptors,
10947 the bandwidth savings should be about 60%. [Partially implements
10949 - Servers upload extra-info documents to any authority that accepts
10950 them. Authorities (and caches that have been configured to download
10951 extra-info documents) download them as needed. [Partially implements
10953 - Change the way that Tor buffers data that it is waiting to write.
10954 Instead of queueing data cells in an enormous ring buffer for each
10955 client->OR or OR->OR connection, we now queue cells on a separate
10956 queue for each circuit. This lets us use less slack memory, and
10957 will eventually let us be smarter about prioritizing different kinds
10959 - Use memory pools to allocate cells with better speed and memory
10960 efficiency, especially on platforms where malloc() is inefficient.
10961 - Stop reading on edge connections when their corresponding circuit
10962 buffers are full; start again as the circuits empty out.
10964 o Major features, other:
10965 - Add an HSAuthorityRecordStats option that hidden service authorities
10966 can use to track statistics of overall hidden service usage without
10967 logging information that would be very useful to an attacker.
10968 - Start work implementing multi-level keys for directory authorities:
10969 Add a standalone tool to generate key certificates. (Proposal 103.)
10972 - Directory authorities now call routers Stable if they have an
10973 uptime of at least 30 days, even if that's not the median uptime
10974 in the network. Implements proposal 107, suggested by Kevin Bauer
10977 o Minor fixes (resource management):
10978 - Count the number of open sockets separately from the number
10979 of active connection_t objects. This will let us avoid underusing
10980 our allocated connection limit.
10981 - We no longer use socket pairs to link an edge connection to an
10982 anonymous directory connection or a DirPort test connection.
10983 Instead, we track the link internally and transfer the data
10984 in-process. This saves two sockets per "linked" connection (at the
10985 client and at the server), and avoids the nasty Windows socketpair()
10987 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
10988 for every single inactive connection_t. Free items from the
10989 4k/16k-buffer free lists when they haven't been used for a while.
10991 o Minor features (build):
10992 - Make autoconf search for libevent, openssl, and zlib consistently.
10993 - Update deprecated macros in configure.in.
10994 - When warning about missing headers, tell the user to let us
10995 know if the compile succeeds anyway, so we can downgrade the
10997 - Include the current subversion revision as part of the version
10998 string: either fetch it directly if we're in an SVN checkout, do
10999 some magic to guess it if we're in an SVK checkout, or use
11000 the last-detected version if we're building from a .tar.gz.
11001 Use this version consistently in log messages.
11003 o Minor features (logging):
11004 - Always prepend "Bug: " to any log message about a bug.
11005 - Put a platform string (e.g. "Linux i686") in the startup log
11006 message, so when people paste just their logs, we know if it's
11007 OpenBSD or Windows or what.
11008 - When logging memory usage, break down memory used in buffers by
11011 o Minor features (directory system):
11012 - New config option V2AuthoritativeDirectory that all directory
11013 authorities should set. This will let future authorities choose
11014 not to serve V2 directory information.
11015 - Directory authorities allow multiple router descriptors and/or extra
11016 info documents to be uploaded in a single go. This will make
11017 implementing proposal 104 simpler.
11019 o Minor features (controller):
11020 - Add a new config option __DisablePredictedCircuits designed for
11021 use by the controller, when we don't want Tor to build any circuits
11023 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
11024 so we can exit from the middle of the circuit.
11025 - Implement "getinfo status/circuit-established".
11026 - Implement "getinfo status/version/..." so a controller can tell
11027 whether the current version is recommended, and whether any versions
11028 are good, and how many authorities agree. (Patch from shibz.)
11030 o Minor features (hidden services):
11031 - Allow multiple HiddenServicePort directives with the same virtual
11032 port; when they occur, the user is sent round-robin to one
11033 of the target ports chosen at random. Partially fixes bug 393 by
11034 adding limited ad-hoc round-robining.
11036 o Minor features (other):
11038 - Add a new AutomapHostsOnResolve option: when it is enabled, any
11039 resolve request for hosts matching a given pattern causes Tor to
11040 generate an internal virtual address mapping for that host. This
11041 allows DNSPort to work sensibly with hidden service users. By
11042 default, .exit and .onion addresses are remapped; the list of
11043 patterns can be reconfigured with AutomapHostsSuffixes.
11044 - Add an "-F" option to tor-resolve to force a resolve for a .onion
11045 address. Thanks to the AutomapHostsOnResolve option, this is no
11046 longer a completely silly thing to do.
11047 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
11048 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
11049 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
11050 minus 1 byte: the actual maximum declared bandwidth.
11052 o Removed features:
11053 - Removed support for the old binary "version 0" controller protocol.
11054 This has been deprecated since 0.1.1, and warnings have been issued
11055 since 0.1.2. When we encounter a v0 control message, we now send
11056 back an error and close the connection.
11057 - Remove the old "dns worker" server DNS code: it hasn't been default
11058 since 0.1.2.2-alpha, and all the servers seem to be using the new
11061 o Minor bugfixes (portability):
11062 - Even though Windows is equally happy with / and \ as path separators,
11063 try to use \ consistently on Windows and / consistently on Unix: it
11064 makes the log messages nicer.
11065 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
11066 - Read resolv.conf files correctly on platforms where read() returns
11067 partial results on small file reads.
11069 o Minor bugfixes (directory):
11070 - Correctly enforce that elements of directory objects do not appear
11071 more often than they are allowed to appear.
11072 - When we are reporting the DirServer line we just parsed, we were
11073 logging the second stanza of the key fingerprint, not the first.
11075 o Minor bugfixes (logging):
11076 - When we hit an EOF on a log (probably because we're shutting down),
11077 don't try to remove the log from the list: just mark it as
11078 unusable. (Bulletproofs against bug 222.)
11080 o Minor bugfixes (other):
11081 - In the exitlist script, only consider the most recently published
11082 server descriptor for each server. Also, when the user requests
11083 a list of servers that _reject_ connections to a given address,
11084 explicitly exclude the IPs that also have servers that accept
11085 connections to that address. (Resolves bug 405.)
11086 - Stop allowing hibernating servers to be "stable" or "fast".
11087 - On Windows, we were preventing other processes from reading
11088 cached-routers while Tor was running. (Reported by janbar)
11089 - Make the NodeFamilies config option work. (Reported by
11090 lodger -- it has never actually worked, even though we added it
11092 - Check return values from pthread_mutex functions.
11093 - Don't save non-general-purpose router descriptors to the disk cache,
11094 because we have no way of remembering what their purpose was when
11096 - Add even more asserts to hunt down bug 417.
11097 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
11098 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
11099 Add a log message to confirm that it is in fact unlikely.
11101 o Minor bugfixes (controller):
11102 - Make 'getinfo fingerprint' return a 551 error if we're not a
11103 server, so we match what the control spec claims we do. Reported
11105 - Fix a typo in an error message when extendcircuit fails that
11106 caused us to not follow the \r\n-based delimiter protocol. Reported
11109 o Code simplifications and refactoring:
11110 - Stop passing around circuit_t and crypt_path_t pointers that are
11111 implicit in other procedure arguments.
11112 - Drop the old code to choke directory connections when the
11113 corresponding OR connections got full: thanks to the cell queue
11114 feature, OR conns don't get full any more.
11115 - Make dns_resolve() handle attaching connections to circuits
11116 properly, so the caller doesn't have to.
11117 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
11118 - Keep the connection array as a dynamic smartlist_t, rather than as
11119 a fixed-sized array. This is important, as the number of connections
11120 is becoming increasingly decoupled from the number of sockets.
11123 Changes in version 0.1.2.14 - 2007-05-25
11124 Tor 0.1.2.14 changes the addresses of two directory authorities (this
11125 change especially affects those who serve or use hidden services),
11126 and fixes several other crash- and security-related bugs.
11128 o Directory authority changes:
11129 - Two directory authorities (moria1 and moria2) just moved to new
11130 IP addresses. This change will particularly affect those who serve
11131 or use hidden services.
11133 o Major bugfixes (crashes):
11134 - If a directory server runs out of space in the connection table
11135 as it's processing a begin_dir request, it will free the exit stream
11136 but leave it attached to the circuit, leading to unpredictable
11137 behavior. (Reported by seeess, fixes bug 425.)
11138 - Fix a bug in dirserv_remove_invalid() that would cause authorities
11139 to corrupt memory under some really unlikely scenarios.
11140 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
11141 - Avoid segfaults when reading from mmaped descriptor file. (Reported
11144 o Major bugfixes (security):
11145 - When choosing an entry guard for a circuit, avoid using guards
11146 that are in the same family as the chosen exit -- not just guards
11147 that are exactly the chosen exit. (Reported by lodger.)
11149 o Major bugfixes (resource management):
11150 - If a directory authority is down, skip it when deciding where to get
11151 networkstatus objects or descriptors. Otherwise we keep asking
11152 every 10 seconds forever. Fixes bug 384.
11153 - Count it as a failure if we fetch a valid network-status but we
11154 don't want to keep it. Otherwise we'll keep fetching it and keep
11155 not wanting to keep it. Fixes part of bug 422.
11156 - If all of our dirservers have given us bad or no networkstatuses
11157 lately, then stop hammering them once per minute even when we
11158 think they're failed. Fixes another part of bug 422.
11161 - Actually set the purpose correctly for descriptors inserted with
11162 purpose=controller.
11163 - When we have k non-v2 authorities in our DirServer config,
11164 we ignored the last k authorities in the list when updating our
11166 - Correctly back-off from requesting router descriptors that we are
11167 having a hard time downloading.
11168 - Read resolv.conf files correctly on platforms where read() returns
11169 partial results on small file reads.
11170 - Don't rebuild the entire router store every time we get 32K of
11171 routers: rebuild it when the journal gets very large, or when
11172 the gaps in the store get very large.
11175 - When routers publish SVN revisions in their router descriptors,
11176 authorities now include those versions correctly in networkstatus
11178 - Warn when using a version of libevent before 1.3b to run a server on
11179 OSX or BSD: these versions interact badly with userspace threads.
11182 Changes in version 0.1.2.13 - 2007-04-24
11183 This release features some major anonymity fixes, such as safer path
11184 selection; better client performance; faster bootstrapping, better
11185 address detection, and better DNS support for servers; write limiting as
11186 well as read limiting to make servers easier to run; and a huge pile of
11187 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
11189 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
11190 of the Freenode IRC network, remembering his patience and vision for
11191 free speech on the Internet.
11194 - Fix a memory leak when we ask for "all" networkstatuses and we
11195 get one we don't recognize.
11196 - Add more asserts to hunt down bug 417.
11197 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
11200 Changes in version 0.1.2.12-rc - 2007-03-16
11202 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
11203 directory information requested inside Tor connections (i.e. via
11204 begin_dir cells). It only triggered when the same connection was
11205 serving other data at the same time. Reported by seeess.
11208 - When creating a circuit via the controller, send a 'launched'
11209 event when we're done, so we follow the spec better.
11212 Changes in version 0.1.2.11-rc - 2007-03-15
11213 o Minor bugfixes (controller), reported by daejees:
11214 - Correct the control spec to match how the code actually responds
11215 to 'getinfo addr-mappings/*'.
11216 - The control spec described a GUARDS event, but the code
11217 implemented a GUARD event. Standardize on GUARD, but let people
11218 ask for GUARDS too.
11221 Changes in version 0.1.2.10-rc - 2007-03-07
11222 o Major bugfixes (Windows):
11223 - Do not load the NT services library functions (which may not exist)
11224 just to detect if we're a service trying to shut down. Now we run
11225 on Win98 and friends again.
11227 o Minor bugfixes (other):
11228 - Clarify a couple of log messages.
11229 - Fix a misleading socks5 error number.
11232 Changes in version 0.1.2.9-rc - 2007-03-02
11233 o Major bugfixes (Windows):
11234 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
11235 of the usual GCC "%llu". This prevents a bug when saving 64-bit
11236 int configuration values: the high-order 32 bits would get
11237 truncated. In particular, we were being bitten by the default
11238 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
11239 and maybe also bug 397.)
11241 o Minor bugfixes (performance):
11242 - Use OpenSSL's AES implementation on platforms where it's faster.
11243 This could save us as much as 10% CPU usage.
11245 o Minor bugfixes (server):
11246 - Do not rotate onion key immediately after setting it for the first
11249 o Minor bugfixes (directory authorities):
11250 - Stop calling servers that have been hibernating for a long time
11251 "stable". Also, stop letting hibernating or obsolete servers affect
11252 uptime and bandwidth cutoffs.
11253 - Stop listing hibernating servers in the v1 directory.
11255 o Minor bugfixes (hidden services):
11256 - Upload hidden service descriptors slightly less often, to reduce
11257 load on authorities.
11259 o Minor bugfixes (other):
11260 - Fix an assert that could trigger if a controller quickly set then
11261 cleared EntryNodes. Bug found by Udo van den Heuvel.
11262 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
11264 - Fix a potential race condition in the rpm installer. Found by
11266 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
11267 of 2 as indicating that the server is completely bad; it sometimes
11268 means that the server is just bad for the request in question. (may fix
11269 the last of bug 326.)
11270 - Disable encrypted directory connections when we don't have a server
11271 descriptor for the destination. We'll get this working again in
11275 Changes in version 0.1.2.8-beta - 2007-02-26
11276 o Major bugfixes (crashes):
11277 - Stop crashing when the controller asks us to resetconf more than
11278 one config option at once. (Vidalia 0.0.11 does this.)
11279 - Fix a crash that happened on Win98 when we're given command-line
11280 arguments: don't try to load NT service functions from advapi32.dll
11281 except when we need them. (Bug introduced in 0.1.2.7-alpha;
11283 - Fix a longstanding obscure crash bug that could occur when
11284 we run out of DNS worker processes. (Resolves bug 390.)
11286 o Major bugfixes (hidden services):
11287 - Correctly detect whether hidden service descriptor downloads are
11288 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
11290 o Major bugfixes (accounting):
11291 - When we start during an accounting interval before it's time to wake
11292 up, remember to wake up at the correct time. (May fix bug 342.)
11294 o Minor bugfixes (controller):
11295 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
11296 clear the corresponding on_circuit variable, and remember later
11297 that we don't need to send a redundant CLOSED event. Resolves part
11299 - Report events where a resolve succeeded or where we got a socks
11300 protocol error correctly, rather than calling both of them
11302 - Change reported stream target addresses to IP consistently when
11303 we finally get the IP from an exit node.
11304 - Send log messages to the controller even if they happen to be very
11307 o Minor bugfixes (other):
11308 - Display correct results when reporting which versions are
11309 recommended, and how recommended they are. (Resolves bug 383.)
11310 - Improve our estimates for directory bandwidth to be less random:
11311 guess that an unrecognized directory will have the average bandwidth
11312 from all known directories, not that it will have the average
11313 bandwidth from those directories earlier than it on the list.
11314 - If we start a server with ClientOnly 1, then set ClientOnly to 0
11315 and hup, stop triggering an assert based on an empty onion_key.
11316 - On platforms with no working mmap() equivalent, don't warn the
11317 user when cached-routers doesn't exist.
11318 - Warn the user when mmap() [or its equivalent] fails for some reason
11319 other than file-not-found.
11320 - Don't warn the user when cached-routers.new doesn't exist: that's
11321 perfectly fine when starting up for the first time.
11322 - When EntryNodes are configured, rebuild the guard list to contain,
11323 in order: the EntryNodes that were guards before; the rest of the
11324 EntryNodes; the nodes that were guards before.
11325 - Mask out all signals in sub-threads; only the libevent signal
11326 handler should be processing them. This should prevent some crashes
11327 on some machines using pthreads. (Patch from coderman.)
11328 - Fix switched arguments on memset in the implementation of
11329 tor_munmap() for systems with no mmap() call.
11330 - When Tor receives a router descriptor that it asked for, but
11331 no longer wants (because it has received fresh networkstatuses
11332 in the meantime), do not warn the user. Cache the descriptor if
11333 we're a cache; drop it if we aren't.
11334 - Make earlier entry guards _really_ get retried when the network
11336 - On a malformed DNS reply, always give an error to the corresponding
11338 - Build with recent libevents on platforms that do not define the
11339 nonstandard types "u_int8_t" and friends.
11341 o Minor features (controller):
11342 - Warn the user when an application uses the obsolete binary v0
11343 control protocol. We're planning to remove support for it during
11344 the next development series, so it's good to give people some
11346 - Add STREAM_BW events to report per-entry-stream bandwidth
11347 use. (Patch from Robert Hogan.)
11348 - Rate-limit SIGNEWNYM signals in response to controllers that
11349 impolitely generate them for every single stream. (Patch from
11350 mwenge; closes bug 394.)
11351 - Make REMAP stream events have a SOURCE (cache or exit), and
11352 make them generated in every case where we get a successful
11353 connected or resolved cell.
11355 o Minor bugfixes (performance):
11356 - Call router_have_min_dir_info half as often. (This is showing up in
11357 some profiles, but not others.)
11358 - When using GCC, make log_debug never get called at all, and its
11359 arguments never get evaluated, when no debug logs are configured.
11360 (This is showing up in some profiles, but not others.)
11363 - Remove some never-implemented options. Mark PathlenCoinWeight as
11365 - Implement proposal 106: Stop requiring clients to have well-formed
11366 certificates; stop checking nicknames in certificates. (Clients
11367 have certificates so that they can look like Tor servers, but in
11368 the future we might want to allow them to look like regular TLS
11369 clients instead. Nicknames in certificates serve no purpose other
11370 than making our protocol easier to recognize on the wire.)
11371 - Revise messages on handshake failure again to be even more clear about
11372 which are incoming connections and which are outgoing.
11373 - Discard any v1 directory info that's over 1 month old (for
11374 directories) or over 1 week old (for running-routers lists).
11375 - Do not warn when individual nodes in the configuration's EntryNodes,
11376 ExitNodes, etc are down: warn only when all possible nodes
11377 are down. (Fixes bug 348.)
11378 - Always remove expired routers and networkstatus docs before checking
11379 whether we have enough information to build circuits. (Fixes
11381 - Put a lower-bound on MaxAdvertisedBandwidth.
11384 Changes in version 0.1.2.7-alpha - 2007-02-06
11385 o Major bugfixes (rate limiting):
11386 - Servers decline directory requests much more aggressively when
11387 they're low on bandwidth. Otherwise they end up queueing more and
11388 more directory responses, which can't be good for latency.
11389 - But never refuse directory requests from local addresses.
11390 - Fix a memory leak when sending a 503 response for a networkstatus
11392 - Be willing to read or write on local connections (e.g. controller
11393 connections) even when the global rate limiting buckets are empty.
11394 - If our system clock jumps back in time, don't publish a negative
11395 uptime in the descriptor. Also, don't let the global rate limiting
11396 buckets go absurdly negative.
11397 - Flush local controller connection buffers periodically as we're
11398 writing to them, so we avoid queueing 4+ megabytes of data before
11401 o Major bugfixes (NT services):
11402 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
11403 command-line flag so that admins can override the default by saying
11404 "tor --service install --user "SomeUser"". This will not affect
11405 existing installed services. Also, warn the user that the service
11406 will look for its configuration file in the service user's
11407 %appdata% directory. (We can't do the 'hardwire the user's appdata
11408 directory' trick any more, since we may not have read access to that
11411 o Major bugfixes (other):
11412 - Previously, we would cache up to 16 old networkstatus documents
11413 indefinitely, if they came from nontrusted authorities. Now we
11414 discard them if they are more than 10 days old.
11415 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
11417 - Detect and reject malformed DNS responses containing circular
11419 - If exits are rare enough that we're not marking exits as guards,
11420 ignore exit bandwidth when we're deciding the required bandwidth
11422 - When we're handling a directory connection tunneled over Tor,
11423 don't fill up internal memory buffers with all the data we want
11424 to tunnel; instead, only add it if the OR connection that will
11425 eventually receive it has some room for it. (This can lead to
11426 slowdowns in tunneled dir connections; a better solution will have
11427 to wait for 0.2.0.)
11429 o Minor bugfixes (dns):
11430 - Add some defensive programming to eventdns.c in an attempt to catch
11431 possible memory-stomping bugs.
11432 - Detect and reject DNS replies containing IPv4 or IPv6 records with
11433 an incorrect number of bytes. (Previously, we would ignore the
11435 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
11436 in the correct order, and doesn't crash.
11437 - Free memory held in recently-completed DNS lookup attempts on exit.
11438 This was not a memory leak, but may have been hiding memory leaks.
11439 - Handle TTL values correctly on reverse DNS lookups.
11440 - Treat failure to parse resolv.conf as an error.
11442 o Minor bugfixes (other):
11443 - Fix crash with "tor --list-fingerprint" (reported by seeess).
11444 - When computing clock skew from directory HTTP headers, consider what
11445 time it was when we finished asking for the directory, not what
11447 - Expire socks connections if they spend too long waiting for the
11448 handshake to finish. Previously we would let them sit around for
11449 days, if the connecting application didn't close them either.
11450 - And if the socks handshake hasn't started, don't send a
11451 "DNS resolve socks failed" handshake reply; just close it.
11452 - Stop using C functions that OpenBSD's linker doesn't like.
11453 - Don't launch requests for descriptors unless we have networkstatuses
11454 from at least half of the authorities. This delays the first
11455 download slightly under pathological circumstances, but can prevent
11456 us from downloading a bunch of descriptors we don't need.
11457 - Do not log IPs with TLS failures for incoming TLS
11458 connections. (Fixes bug 382.)
11459 - If the user asks to use invalid exit nodes, be willing to use
11461 - Stop using the reserved ac_cv namespace in our configure script.
11462 - Call stat() slightly less often; use fstat() when possible.
11463 - Refactor the way we handle pending circuits when an OR connection
11464 completes or fails, in an attempt to fix a rare crash bug.
11465 - Only rewrite a conn's address based on X-Forwarded-For: headers
11466 if it's a parseable public IP address; and stop adding extra quotes
11467 to the resulting address.
11470 - Weight directory requests by advertised bandwidth. Now we can
11471 let servers enable write limiting but still allow most clients to
11472 succeed at their directory requests. (We still ignore weights when
11473 choosing a directory authority; I hope this is a feature.)
11476 - Create a new file ReleaseNotes which was the old ChangeLog. The
11477 new ChangeLog file now includes the summaries for all development
11479 - Check for addresses with invalid characters at the exit as well
11480 as at the client, and warn less verbosely when they fail. You can
11481 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
11482 - Adapt a patch from goodell to let the contrib/exitlist script
11483 take arguments rather than require direct editing.
11484 - Inform the server operator when we decide not to advertise a
11485 DirPort due to AccountingMax enabled or a low BandwidthRate. It
11486 was confusing Zax, so now we're hopefully more helpful.
11487 - Bring us one step closer to being able to establish an encrypted
11488 directory tunnel without knowing a descriptor first. Still not
11489 ready yet. As part of the change, now assume we can use a
11490 create_fast cell if we don't know anything about a router.
11491 - Allow exit nodes to use nameservers running on ports other than 53.
11492 - Servers now cache reverse DNS replies.
11493 - Add an --ignore-missing-torrc command-line option so that we can
11494 get the "use sensible defaults if the configuration file doesn't
11495 exist" behavior even when specifying a torrc location on the command
11498 o Minor features (controller):
11499 - Track reasons for OR connection failure; make these reasons
11500 available via the controller interface. (Patch from Mike Perry.)
11501 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
11502 can learn when clients are sending malformed hostnames to Tor.
11503 - Clean up documentation for controller status events.
11504 - Add a REMAP status to stream events to note that a stream's
11505 address has changed because of a cached address or a MapAddress
11509 Changes in version 0.1.2.6-alpha - 2007-01-09
11511 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
11512 connection handles more than 4 gigs in either direction, we crash.
11513 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
11514 advertised exit node, somebody might try to exit from us when
11515 we're bootstrapping and before we've built our descriptor yet.
11516 Refuse the connection rather than crashing.
11519 - Warn if we (as a server) find that we've resolved an address that we
11520 weren't planning to resolve.
11521 - Warn that using select() on any libevent version before 1.1 will be
11522 unnecessarily slow (even for select()).
11523 - Flush ERR-level controller status events just like we currently
11524 flush ERR-level log events, so that a Tor shutdown doesn't prevent
11525 the controller from learning about current events.
11527 o Minor features (more controller status events):
11528 - Implement EXTERNAL_ADDRESS server status event so controllers can
11529 learn when our address changes.
11530 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
11531 can learn when directories reject our descriptor.
11532 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
11533 can learn when a client application is speaking a non-socks protocol
11535 - Implement DANGEROUS_SOCKS client status event so controllers
11536 can learn when a client application is leaking DNS addresses.
11537 - Implement BUG general status event so controllers can learn when
11538 Tor is unhappy about its internal invariants.
11539 - Implement CLOCK_SKEW general status event so controllers can learn
11540 when Tor thinks the system clock is set incorrectly.
11541 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
11542 server status events so controllers can learn when their descriptors
11543 are accepted by a directory.
11544 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
11545 server status events so controllers can learn about Tor's progress in
11546 deciding whether it's reachable from the outside.
11547 - Implement BAD_LIBEVENT general status event so controllers can learn
11548 when we have a version/method combination in libevent that needs to
11550 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
11551 and DNS_USELESS server status events so controllers can learn
11552 about changes to DNS server status.
11554 o Minor features (directory):
11555 - Authorities no longer recommend exits as guards if this would shift
11556 too much load to the exit nodes.
11559 Changes in version 0.1.2.5-alpha - 2007-01-06
11561 - Enable write limiting as well as read limiting. Now we sacrifice
11562 capacity if we're pushing out lots of directory traffic, rather
11563 than overrunning the user's intended bandwidth limits.
11564 - Include TLS overhead when counting bandwidth usage; previously, we
11565 would count only the bytes sent over TLS, but not the bytes used
11567 - Support running the Tor service with a torrc not in the same
11568 directory as tor.exe and default to using the torrc located in
11569 the %appdata%\Tor\ of the user who installed the service. Patch
11571 - Servers now check for the case when common DNS requests are going to
11572 wildcarded addresses (i.e. all getting the same answer), and change
11573 their exit policy to reject *:* if it's happening.
11574 - Implement BEGIN_DIR cells, so we can connect to the directory
11575 server via TLS to do encrypted directory requests rather than
11576 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
11577 config options if you like.
11579 o Minor features (config and docs):
11580 - Start using the state file to store bandwidth accounting data:
11581 the bw_accounting file is now obsolete. We'll keep generating it
11582 for a while for people who are still using 0.1.2.4-alpha.
11583 - Try to batch changes to the state file so that we do as few
11584 disk writes as possible while still storing important things in
11586 - The state file and the bw_accounting file get saved less often when
11587 the AvoidDiskWrites config option is set.
11588 - Make PIDFile work on Windows (untested).
11589 - Add internal descriptions for a bunch of configuration options:
11590 accessible via controller interface and in comments in saved
11592 - Reject *:563 (NNTPS) in the default exit policy. We already reject
11593 NNTP by default, so this seems like a sensible addition.
11594 - Clients now reject hostnames with invalid characters. This should
11595 avoid some inadvertent info leaks. Add an option
11596 AllowNonRFC953Hostnames to disable this behavior, in case somebody
11597 is running a private network with hosts called @, !, and #.
11598 - Add a maintainer script to tell us which options are missing
11599 documentation: "make check-docs".
11600 - Add a new address-spec.txt document to describe our special-case
11601 addresses: .exit, .onion, and .noconnnect.
11603 o Minor features (DNS):
11604 - Ongoing work on eventdns infrastructure: now it has dns server
11605 and ipv6 support. One day Tor will make use of it.
11606 - Add client-side caching for reverse DNS lookups.
11607 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
11608 - When we change nameservers or IP addresses, reset and re-launch
11609 our tests for DNS hijacking.
11611 o Minor features (directory):
11612 - Authorities now specify server versions in networkstatus. This adds
11613 about 2% to the size of compressed networkstatus docs, and allows
11614 clients to tell which servers support BEGIN_DIR and which don't.
11615 The implementation is forward-compatible with a proposed future
11616 protocol version scheme not tied to Tor versions.
11617 - DirServer configuration lines now have an orport= option so
11618 clients can open encrypted tunnels to the authorities without
11619 having downloaded their descriptors yet. Enabled for moria1,
11620 moria2, tor26, and lefkada now in the default configuration.
11621 - Directory servers are more willing to send a 503 "busy" if they
11622 are near their write limit, especially for v1 directory requests.
11623 Now they can use their limited bandwidth for actual Tor traffic.
11624 - Clients track responses with status 503 from dirservers. After a
11625 dirserver has given us a 503, we try not to use it until an hour has
11626 gone by, or until we have no dirservers that haven't given us a 503.
11627 - When we get a 503 from a directory, and we're not a server, we don't
11628 count the failure against the total number of failures allowed
11629 for the thing we're trying to download.
11630 - Report X-Your-Address-Is correctly from tunneled directory
11631 connections; don't report X-Your-Address-Is when it's an internal
11632 address; and never believe reported remote addresses when they're
11634 - Protect against an unlikely DoS attack on directory servers.
11635 - Add a BadDirectory flag to network status docs so that authorities
11636 can (eventually) tell clients about caches they believe to be
11639 o Minor features (controller):
11640 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
11641 - Reimplement GETINFO so that info/names stays in sync with the
11643 - Implement "GETINFO fingerprint".
11644 - Implement "SETEVENTS GUARD" so controllers can get updates on
11645 entry guard status as it changes.
11647 o Minor features (clean up obsolete pieces):
11648 - Remove some options that have been deprecated since at least
11649 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
11650 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
11651 to set log options.
11652 - We no longer look for identity and onion keys in "identity.key" and
11653 "onion.key" -- these were replaced by secret_id_key and
11654 secret_onion_key in 0.0.8pre1.
11655 - We no longer require unrecognized directory entries to be
11658 o Major bugfixes (security):
11659 - Stop sending the HttpProxyAuthenticator string to directory
11660 servers when directory connections are tunnelled through Tor.
11661 - Clients no longer store bandwidth history in the state file.
11662 - Do not log introduction points for hidden services if SafeLogging
11664 - When generating bandwidth history, round down to the nearest
11665 1k. When storing accounting data, round up to the nearest 1k.
11666 - When we're running as a server, remember when we last rotated onion
11667 keys, so that we will rotate keys once they're a week old even if
11668 we never stay up for a week ourselves.
11670 o Major bugfixes (other):
11671 - Fix a longstanding bug in eventdns that prevented the count of
11672 timed-out resolves from ever being reset. This bug caused us to
11673 give up on a nameserver the third time it timed out, and try it
11674 10 seconds later... and to give up on it every time it timed out
11676 - Take out the '5 second' timeout from the connection retry
11677 schedule. Now the first connect attempt will wait a full 10
11678 seconds before switching to a new circuit. Perhaps this will help
11679 a lot. Based on observations from Mike Perry.
11680 - Fix a bug on the Windows implementation of tor_mmap_file() that
11681 would prevent the cached-routers file from ever loading. Reported
11685 - Fix an assert failure when a directory authority sets
11686 AuthDirRejectUnlisted and then receives a descriptor from an
11687 unlisted router. Reported by seeess.
11688 - Avoid a double-free when parsing malformed DirServer lines.
11689 - Fix a bug when a BSD-style PF socket is first used. Patch from
11691 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
11692 to resolve an address at a given exit node even when they ask for
11694 - Servers no longer ever list themselves in their "family" line,
11695 even if configured to do so. This makes it easier to configure
11696 family lists conveniently.
11697 - When running as a server, don't fall back to 127.0.0.1 when no
11698 nameservers are configured in /etc/resolv.conf; instead, make the
11699 user fix resolv.conf or specify nameservers explicitly. (Resolves
11701 - Stop accepting certain malformed ports in configured exit policies.
11702 - Don't re-write the fingerprint file every restart, unless it has
11704 - Stop warning when a single nameserver fails: only warn when _all_ of
11705 our nameservers have failed. Also, when we only have one nameserver,
11706 raise the threshold for deciding that the nameserver is dead.
11707 - Directory authorities now only decide that routers are reachable
11708 if their identity keys are as expected.
11709 - When the user uses bad syntax in the Log config line, stop
11710 suggesting other bad syntax as a replacement.
11711 - Correctly detect ipv6 DNS capability on OpenBSD.
11713 o Minor bugfixes (controller):
11714 - Report the circuit number correctly in STREAM CLOSED events. Bug
11715 reported by Mike Perry.
11716 - Do not report bizarre values for results of accounting GETINFOs
11717 when the last second's write or read exceeds the allotted bandwidth.
11718 - Report "unrecognized key" rather than an empty string when the
11719 controller tries to fetch a networkstatus that doesn't exist.
11722 Changes in version 0.1.1.26 - 2006-12-14
11723 o Security bugfixes:
11724 - Stop sending the HttpProxyAuthenticator string to directory
11725 servers when directory connections are tunnelled through Tor.
11726 - Clients no longer store bandwidth history in the state file.
11727 - Do not log introduction points for hidden services if SafeLogging
11731 - Fix an assert failure when a directory authority sets
11732 AuthDirRejectUnlisted and then receives a descriptor from an
11733 unlisted router (reported by seeess).
11736 Changes in version 0.1.2.4-alpha - 2006-12-03
11738 - Add support for using natd; this allows FreeBSDs earlier than
11739 5.1.2 to have ipfw send connections through Tor without using
11740 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
11743 - Make all connections to addresses of the form ".noconnect"
11744 immediately get closed. This lets application/controller combos
11745 successfully test whether they're talking to the same Tor by
11746 watching for STREAM events.
11747 - Make cross.sh cross-compilation script work even when autogen.sh
11748 hasn't been run. (Patch from Michael Mohr.)
11749 - Statistics dumped by -USR2 now include a breakdown of public key
11750 operations, for profiling.
11753 - Fix a major leak when directory authorities parse their
11754 approved-routers list, a minor memory leak when we fail to pick
11755 an exit node, and a few rare leaks on errors.
11756 - Handle TransPort connections even when the server sends data before
11757 the client sends data. Previously, the connection would just hang
11758 until the client sent data. (Patch from tup based on patch from
11760 - Avoid assert failure when our cached-routers file is empty on
11764 - Don't log spurious warnings when we see a circuit close reason we
11765 don't recognize; it's probably just from a newer version of Tor.
11766 - Have directory authorities allow larger amounts of drift in uptime
11767 without replacing the server descriptor: previously, a server that
11768 restarted every 30 minutes could have 48 "interesting" descriptors
11770 - Start linking to the Tor specification and Tor reference manual
11771 correctly in the Windows installer.
11772 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11773 Tor/Privoxy we also uninstall Vidalia.
11774 - Resume building on Irix64, and fix a lot of warnings from its
11775 MIPSpro C compiler.
11776 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
11777 when we're running as a client.
11780 Changes in version 0.1.1.25 - 2006-11-04
11782 - When a client asks us to resolve (rather than connect to)
11783 an address, and we have a cached answer, give them the cached
11784 answer. Previously, we would give them no answer at all.
11785 - We were building exactly the wrong circuits when we predict
11786 hidden service requirements, meaning Tor would have to build all
11787 its circuits on demand.
11788 - If none of our live entry guards have a high uptime, but we
11789 require a guard with a high uptime, try adding a new guard before
11790 we give up on the requirement. This patch should make long-lived
11791 connections more stable on average.
11792 - When testing reachability of our DirPort, don't launch new
11793 tests when there's already one in progress -- unreachable
11794 servers were stacking up dozens of testing streams.
11796 o Security bugfixes:
11797 - When the user sends a NEWNYM signal, clear the client-side DNS
11798 cache too. Otherwise we continue to act on previous information.
11801 - Avoid a memory corruption bug when creating a hash table for
11803 - Avoid possibility of controller-triggered crash when misusing
11804 certain commands from a v0 controller on platforms that do not
11805 handle printf("%s",NULL) gracefully.
11806 - Avoid infinite loop on unexpected controller input.
11807 - Don't log spurious warnings when we see a circuit close reason we
11808 don't recognize; it's probably just from a newer version of Tor.
11809 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11810 Tor/Privoxy we also uninstall Vidalia.
11813 Changes in version 0.1.2.3-alpha - 2006-10-29
11815 - Prepare for servers to publish descriptors less often: never
11816 discard a descriptor simply for being too old until either it is
11817 recommended by no authorities, or until we get a better one for
11818 the same router. Make caches consider retaining old recommended
11819 routers for even longer.
11820 - If most authorities set a BadExit flag for a server, clients
11821 don't think of it as a general-purpose exit. Clients only consider
11822 authorities that advertise themselves as listing bad exits.
11823 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
11824 headers for content, so that we can work better in the presence of
11825 caching HTTP proxies.
11826 - Allow authorities to list nodes as bad exits by fingerprint or by
11829 o Minor features, controller:
11830 - Add a REASON field to CIRC events; for backward compatibility, this
11831 field is sent only to controllers that have enabled the extended
11832 event format. Also, add additional reason codes to explain why
11833 a given circuit has been destroyed or truncated. (Patches from
11835 - Add a REMOTE_REASON field to extended CIRC events to tell the
11836 controller about why a remote OR told us to close a circuit.
11837 - Stream events also now have REASON and REMOTE_REASON fields,
11838 working much like those for circuit events.
11839 - There's now a GETINFO ns/... field so that controllers can ask Tor
11840 about the current status of a router.
11841 - A new event type "NS" to inform a controller when our opinion of
11842 a router's status has changed.
11843 - Add a GETINFO events/names and GETINFO features/names so controllers
11844 can tell which events and features are supported.
11845 - A new CLEARDNSCACHE signal to allow controllers to clear the
11846 client-side DNS cache without expiring circuits.
11848 o Security bugfixes:
11849 - When the user sends a NEWNYM signal, clear the client-side DNS
11850 cache too. Otherwise we continue to act on previous information.
11853 - Avoid sending junk to controllers or segfaulting when a controller
11854 uses EVENT_NEW_DESC with verbose nicknames.
11855 - Stop triggering asserts if the controller tries to extend hidden
11856 service circuits (reported by mwenge).
11857 - Avoid infinite loop on unexpected controller input.
11858 - When the controller does a "GETINFO network-status", tell it
11859 about even those routers whose descriptors are very old, and use
11860 long nicknames where appropriate.
11861 - Change NT service functions to be loaded on demand. This lets us
11862 build with MinGW without breaking Tor for Windows 98 users.
11863 - Do DirPort reachability tests less often, since a single test
11864 chews through many circuits before giving up.
11865 - In the hidden service example in torrc.sample, stop recommending
11866 esoteric and discouraged hidden service options.
11867 - When stopping an NT service, wait up to 10 sec for it to actually
11868 stop. Patch from Matt Edman; resolves bug 295.
11869 - Fix handling of verbose nicknames with ORCONN controller events:
11870 make them show up exactly when requested, rather than exactly when
11872 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
11873 printing a duplicate "$" in the keys we send (reported by mwenge).
11874 - Correctly set maximum connection limit on Cygwin. (This time
11876 - Try to detect Windows correctly when cross-compiling.
11877 - Detect the size of the routers file correctly even if it is
11878 corrupted (on systems without mmap) or not page-aligned (on systems
11879 with mmap). This bug was harmless.
11880 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
11881 to open a stream fails; now we do in more cases. This should
11882 make clients able to find a good exit faster in some cases, since
11883 unhandleable requests will now get an error rather than timing out.
11884 - Resolve two memory leaks when rebuilding the on-disk router cache
11885 (reported by fookoowa).
11886 - Clean up minor code warnings suggested by the MIPSpro C compiler,
11887 and reported by some Centos users.
11888 - Controller signals now work on non-Unix platforms that don't define
11889 SIGUSR1 and SIGUSR2 the way we expect.
11890 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
11891 values before failing, and always enables eventdns.
11892 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
11893 Try to fix this in configure.in by checking for most functions
11894 before we check for libevent.
11897 Changes in version 0.1.2.2-alpha - 2006-10-07
11899 - Make our async eventdns library on-by-default for Tor servers,
11900 and plan to deprecate the separate dnsworker threads.
11901 - Add server-side support for "reverse" DNS lookups (using PTR
11902 records so clients can determine the canonical hostname for a given
11903 IPv4 address). Only supported by servers using eventdns; servers
11904 now announce in their descriptors whether they support eventdns.
11905 - Specify and implement client-side SOCKS5 interface for reverse DNS
11906 lookups (see doc/socks-extensions.txt).
11907 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
11908 connect to directory servers through Tor. Previously, clients needed
11909 to find Tor exits to make private connections to directory servers.
11910 - Avoid choosing Exit nodes for entry or middle hops when the
11911 total bandwidth available from non-Exit nodes is much higher than
11912 the total bandwidth available from Exit nodes.
11913 - Workaround for name servers (like Earthlink's) that hijack failing
11914 DNS requests and replace the no-such-server answer with a "helpful"
11915 redirect to an advertising-driven search portal. Also work around
11916 DNS hijackers who "helpfully" decline to hijack known-invalid
11917 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
11918 lets you turn it off.
11919 - Send out a burst of long-range padding cells once we've established
11920 that we're reachable. Spread them over 4 circuits, so hopefully
11921 a few will be fast. This exercises our bandwidth and bootstraps
11922 us into the directory more quickly.
11924 o New/improved config options:
11925 - Add new config option "ResolvConf" to let the server operator
11926 choose an alternate resolve.conf file when using eventdns.
11927 - Add an "EnforceDistinctSubnets" option to control our "exclude
11928 servers on the same /16" behavior. It's still on by default; this
11929 is mostly for people who want to operate private test networks with
11930 all the machines on the same subnet.
11931 - If one of our entry guards is on the ExcludeNodes list, or the
11932 directory authorities don't think it's a good guard, treat it as
11933 if it were unlisted: stop using it as a guard, and throw it off
11934 the guards list if it stays that way for a long time.
11935 - Allow directory authorities to be marked separately as authorities
11936 for the v1 directory protocol, the v2 directory protocol, and
11937 as hidden service directories, to make it easier to retire old
11938 authorities. V1 authorities should set "HSAuthoritativeDir 1"
11939 to continue being hidden service authorities too.
11940 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
11942 o Minor features, controller:
11943 - Fix CIRC controller events so that controllers can learn the
11944 identity digests of non-Named servers used in circuit paths.
11945 - Let controllers ask for more useful identifiers for servers. Instead
11946 of learning identity digests for un-Named servers and nicknames
11947 for Named servers, the new identifiers include digest, nickname,
11948 and indication of Named status. Off by default; see control-spec.txt
11949 for more information.
11950 - Add a "getinfo address" controller command so it can display Tor's
11951 best guess to the user.
11952 - New controller event to alert the controller when our server
11953 descriptor has changed.
11954 - Give more meaningful errors on controller authentication failure.
11956 o Minor features, other:
11957 - When asked to resolve a hostname, don't use non-exit servers unless
11958 requested to do so. This allows servers with broken DNS to be
11959 useful to the network.
11960 - Divide eventdns log messages into warn and info messages.
11961 - Reserve the nickname "Unnamed" for routers that can't pick
11962 a hostname: any router can call itself Unnamed; directory
11963 authorities will never allocate Unnamed to any particular router;
11964 clients won't believe that any router is the canonical Unnamed.
11965 - Only include function names in log messages for info/debug messages.
11966 For notice/warn/err, the content of the message should be clear on
11967 its own, and printing the function name only confuses users.
11968 - Avoid some false positives during reachability testing: don't try
11969 to test via a server that's on the same /24 as us.
11970 - If we fail to build a circuit to an intended enclave, and it's
11971 not mandatory that we use that enclave, stop wanting it.
11972 - When eventdns is enabled, allow multithreaded builds on NetBSD and
11973 OpenBSD. (We had previously disabled threads on these platforms
11974 because they didn't have working thread-safe resolver functions.)
11976 o Major bugfixes, anonymity/security:
11977 - If a client asked for a server by name, and there's a named server
11978 in our network-status but we don't have its descriptor yet, we
11979 could return an unnamed server instead.
11980 - Fix NetBSD bug that could allow someone to force uninitialized RAM
11981 to be sent to a server's DNS resolver. This only affects NetBSD
11982 and other platforms that do not bounds-check tolower().
11983 - Reject (most) attempts to use Tor circuits with length one. (If
11984 many people start using Tor as a one-hop proxy, exit nodes become
11985 a more attractive target for compromise.)
11986 - Just because your DirPort is open doesn't mean people should be
11987 able to remotely teach you about hidden service descriptors. Now
11988 only accept rendezvous posts if you've got HSAuthoritativeDir set.
11990 o Major bugfixes, other:
11991 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
11992 - When a client asks the server to resolve (not connect to)
11993 an address, and it has a cached answer, give them the cached answer.
11994 Previously, the server would give them no answer at all.
11995 - Allow really slow clients to not hang up five minutes into their
11996 directory downloads (suggested by Adam J. Richter).
11997 - We were building exactly the wrong circuits when we anticipated
11998 hidden service requirements, meaning Tor would have to build all
11999 its circuits on demand.
12000 - Avoid crashing when we mmap a router cache file of size 0.
12001 - When testing reachability of our DirPort, don't launch new
12002 tests when there's already one in progress -- unreachable
12003 servers were stacking up dozens of testing streams.
12005 o Minor bugfixes, correctness:
12006 - If we're a directory mirror and we ask for "all" network status
12007 documents, we would discard status documents from authorities
12008 we don't recognize.
12009 - Avoid a memory corruption bug when creating a hash table for
12011 - Avoid controller-triggered crash when misusing certain commands
12012 from a v0 controller on platforms that do not handle
12013 printf("%s",NULL) gracefully.
12014 - Don't crash when a controller sends a third argument to an
12015 "extendcircuit" request.
12016 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12017 response; fix error code when "getinfo dir/status/" fails.
12018 - Avoid crash when telling controller stream-status and a stream
12020 - Patch from Adam Langley to fix assert() in eventdns.c.
12021 - Fix a debug log message in eventdns to say "X resolved to Y"
12022 instead of "X resolved to X".
12023 - Make eventdns give strings for DNS errors, not just error numbers.
12024 - Track unreachable entry guards correctly: don't conflate
12025 'unreachable by us right now' with 'listed as down by the directory
12026 authorities'. With the old code, if a guard was unreachable by
12027 us but listed as running, it would clog our guard list forever.
12028 - Behave correctly in case we ever have a network with more than
12029 2GB/s total advertised capacity.
12030 - Make TrackExitHosts case-insensitive, and fix the behavior of
12031 ".suffix" TrackExitHosts items to avoid matching in the middle of
12033 - Finally fix the openssl warnings from newer gccs that believe that
12034 ignoring a return value is okay, but casting a return value and
12035 then ignoring it is a sign of madness.
12036 - Prevent the contrib/exitlist script from printing the same
12037 result more than once.
12038 - Patch from Steve Hildrey: Generate network status correctly on
12039 non-versioning dirservers.
12040 - Don't listen to the X-Your-Address-Is hint if you did the lookup
12041 via Tor; otherwise you'll think you're the exit node's IP address.
12043 o Minor bugfixes, performance:
12044 - Two small performance improvements on parsing descriptors.
12045 - Major performance improvement on inserting descriptors: change
12046 algorithm from O(n^2) to O(n).
12047 - Make the common memory allocation path faster on machines where
12048 malloc(0) returns a pointer.
12049 - Start remembering X-Your-Address-Is directory hints even if you're
12050 a client, so you can become a server more smoothly.
12051 - Avoid duplicate entries on MyFamily line in server descriptor.
12053 o Packaging, features:
12054 - Remove architecture from OS X builds. The official builds are
12055 now universal binaries.
12056 - The Debian package now uses --verify-config when (re)starting,
12057 to distinguish configuration errors from other errors.
12058 - Update RPMs to require libevent 1.1b.
12060 o Packaging, bugfixes:
12061 - Patches so Tor builds with MinGW on Windows.
12062 - Patches so Tor might run on Cygwin again.
12063 - Resume building on non-gcc compilers and ancient gcc. Resume
12064 building with the -O0 compile flag. Resume building cleanly on
12066 - Run correctly on OS X platforms with case-sensitive filesystems.
12067 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
12068 - Add autoconf checks so Tor can build on Solaris x86 again.
12071 - Documented (and renamed) ServerDNSSearchDomains and
12072 ServerDNSResolvConfFile options.
12073 - Be clearer that the *ListenAddress directives can be repeated
12077 Changes in version 0.1.1.24 - 2006-09-29
12079 - Allow really slow clients to not hang up five minutes into their
12080 directory downloads (suggested by Adam J. Richter).
12081 - Fix major performance regression from 0.1.0.x: instead of checking
12082 whether we have enough directory information every time we want to
12083 do something, only check when the directory information has changed.
12084 This should improve client CPU usage by 25-50%.
12085 - Don't crash if, after a server has been running for a while,
12086 it can't resolve its hostname.
12089 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12090 - Don't crash when the controller receives a third argument to an
12091 "extendcircuit" request.
12092 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12093 response; fix error code when "getinfo dir/status/" fails.
12094 - Fix configure.in to not produce broken configure files with
12095 more recent versions of autoconf. Thanks to Clint for his auto*
12097 - Fix security bug on NetBSD that could allow someone to force
12098 uninitialized RAM to be sent to a server's DNS resolver. This
12099 only affects NetBSD and other platforms that do not bounds-check
12101 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
12102 methods: these are known to be buggy.
12103 - If we're a directory mirror and we ask for "all" network status
12104 documents, we would discard status documents from authorities
12105 we don't recognize.
12108 Changes in version 0.1.2.1-alpha - 2006-08-27
12110 - Add "eventdns" async dns library from Adam Langley, tweaked to
12111 build on OSX and Windows. Only enabled if you pass the
12112 --enable-eventdns argument to configure.
12113 - Allow servers with no hostname or IP address to learn their
12114 IP address by asking the directory authorities. This code only
12115 kicks in when you would normally have exited with a "no address"
12116 error. Nothing's authenticated, so use with care.
12117 - Rather than waiting a fixed amount of time between retrying
12118 application connections, we wait only 5 seconds for the first,
12119 10 seconds for the second, and 15 seconds for each retry after
12120 that. Hopefully this will improve the expected user experience.
12121 - Patch from Tup to add support for transparent AP connections:
12122 this basically bundles the functionality of trans-proxy-tor
12123 into the Tor mainline. Now hosts with compliant pf/netfilter
12124 implementations can redirect TCP connections straight to Tor
12125 without diverting through SOCKS. Needs docs.
12126 - Busy directory servers save lots of memory by spooling server
12127 descriptors, v1 directories, and v2 networkstatus docs to buffers
12128 as needed rather than en masse. Also mmap the cached-routers
12129 files, so we don't need to keep the whole thing in memory too.
12130 - Automatically avoid picking more than one node from the same
12131 /16 network when constructing a circuit.
12132 - Revise and clean up the torrc.sample that we ship with; add
12133 a section for BandwidthRate and BandwidthBurst.
12136 - Split circuit_t into origin_circuit_t and or_circuit_t, and
12137 split connection_t into edge, or, dir, control, and base structs.
12138 These will save quite a bit of memory on busy servers, and they'll
12139 also help us track down bugs in the code and bugs in the spec.
12140 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
12141 or later. Log when we are doing this, so we can diagnose it when
12142 it fails. (Also, recommend libevent 1.1b for kqueue and
12143 win32 methods; deprecate libevent 1.0b harder; make libevent
12144 recommendation system saner.)
12145 - Start being able to build universal binaries on OS X (thanks
12147 - Export the default exit policy via the control port, so controllers
12148 don't need to guess what it is / will be later.
12149 - Add a man page entry for ProtocolWarnings.
12150 - Add TestVia config option to the man page.
12151 - Remove even more protocol-related warnings from Tor server logs,
12152 such as bad TLS handshakes and malformed begin cells.
12153 - Stop fetching descriptors if you're not a dir mirror and you
12154 haven't tried to establish any circuits lately. [This currently
12155 causes some dangerous behavior, because when you start up again
12156 you'll use your ancient server descriptors.]
12157 - New DirPort behavior: if you have your dirport set, you download
12158 descriptors aggressively like a directory mirror, whether or not
12159 your ORPort is set.
12160 - Get rid of the router_retry_connections notion. Now routers
12161 no longer try to rebuild long-term connections to directory
12162 authorities, and directory authorities no longer try to rebuild
12163 long-term connections to all servers. We still don't hang up
12164 connections in these two cases though -- we need to look at it
12165 more carefully to avoid flapping, and we likely need to wait til
12166 0.1.1.x is obsolete.
12167 - Drop compatibility with obsolete Tors that permit create cells
12168 to have the wrong circ_id_type.
12169 - Re-enable per-connection rate limiting. Get rid of the "OP
12170 bandwidth" concept. Lay groundwork for "bandwidth classes" --
12171 separate global buckets that apply depending on what sort of conn
12173 - Start publishing one minute or so after we find our ORPort
12174 to be reachable. This will help reduce the number of descriptors
12175 we have for ourselves floating around, since it's quite likely
12176 other things (e.g. DirPort) will change during that minute too.
12177 - Fork the v1 directory protocol into its own spec document,
12178 and mark dir-spec.txt as the currently correct (v2) spec.
12181 - When we find our DirPort to be reachable, publish a new descriptor
12182 so we'll tell the world (reported by pnx).
12183 - Publish a new descriptor after we hup/reload. This is important
12184 if our config has changed such that we'll want to start advertising
12185 our DirPort now, etc.
12186 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12187 - When we have a state file we cannot parse, tell the user and
12188 move it aside. Now we avoid situations where the user starts
12189 Tor in 1904, Tor writes a state file with that timestamp in it,
12190 the user fixes her clock, and Tor refuses to start.
12191 - Fix configure.in to not produce broken configure files with
12192 more recent versions of autoconf. Thanks to Clint for his auto*
12194 - "tor --verify-config" now exits with -1(255) or 0 depending on
12195 whether the config options are bad or good.
12196 - Resolve bug 321 when using dnsworkers: append a period to every
12197 address we resolve at the exit node, so that we do not accidentally
12198 pick up local addresses, and so that failing searches are retried
12199 in the resolver search domains. (This is already solved for
12200 eventdns.) (This breaks Blossom servers for now.)
12201 - If we are using an exit enclave and we can't connect, e.g. because
12202 its webserver is misconfigured to not listen on localhost, then
12203 back off and try connecting from somewhere else before we fail.
12206 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
12207 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
12208 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
12209 when the IP address is mapped through MapAddress to a hostname.
12210 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
12211 useless IPv6 DNS resolves.
12212 - Patch suggested by Karsten Loesing: respond to SIGNAL command
12213 before we execute the signal, in case the signal shuts us down.
12214 - Clean up AllowInvalidNodes man page entry.
12215 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
12216 - Add more asserts to track down an assert error on a windows Tor
12217 server with connection_add being called with socket == -1.
12218 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
12219 - Fix misleading log messages: an entry guard that is "unlisted",
12220 as well as not known to be "down" (because we've never heard
12221 of it), is not therefore "up".
12222 - Remove code to special-case "-cvs" ending, since it has not
12223 actually mattered since 0.0.9.
12224 - Make our socks5 handling more robust to broken socks clients:
12225 throw out everything waiting on the buffer in between socks
12226 handshake phases, since they can't possibly (so the theory
12227 goes) have predicted what we plan to respond to them.
12230 Changes in version 0.1.1.23 - 2006-07-30
12232 - Fast Tor servers, especially exit nodes, were triggering asserts
12233 due to a bug in handling the list of pending DNS resolves. Some
12234 bugs still remain here; we're hunting them.
12235 - Entry guards could crash clients by sending unexpected input.
12236 - More fixes on reachability testing: if you find yourself reachable,
12237 then don't ever make any client requests (so you stop predicting
12238 circuits), then hup or have your clock jump, then later your IP
12239 changes, you won't think circuits are working, so you won't try to
12240 test reachability, so you won't publish.
12243 - Avoid a crash if the controller does a resetconf firewallports
12244 and then a setconf fascistfirewall=1.
12245 - Avoid an integer underflow when the dir authority decides whether
12246 a router is stable: we might wrongly label it stable, and compute
12247 a slightly wrong median stability, when a descriptor is published
12249 - Fix a place where we might trigger an assert if we can't build our
12250 own server descriptor yet.
12253 Changes in version 0.1.1.22 - 2006-07-05
12255 - Fix a big bug that was causing servers to not find themselves
12256 reachable if they changed IP addresses. Since only 0.1.1.22+
12257 servers can do reachability testing correctly, now we automatically
12258 make sure to test via one of these.
12259 - Fix to allow clients and mirrors to learn directory info from
12260 descriptor downloads that get cut off partway through.
12261 - Directory authorities had a bug in deciding if a newly published
12262 descriptor was novel enough to make everybody want a copy -- a few
12263 servers seem to be publishing new descriptors many times a minute.
12265 - Fix a rare bug that was causing some servers to complain about
12266 "closing wedged cpuworkers" and skip some circuit create requests.
12267 - Make the Exit flag in directory status documents actually work.
12270 Changes in version 0.1.1.21 - 2006-06-10
12271 o Crash and assert fixes from 0.1.1.20:
12272 - Fix a rare crash on Tor servers that have enabled hibernation.
12273 - Fix a seg fault on startup for Tor networks that use only one
12274 directory authority.
12275 - Fix an assert from a race condition that occurs on Tor servers
12276 while exiting, where various threads are trying to log that they're
12277 exiting, and delete the logs, at the same time.
12278 - Make our unit tests pass again on certain obscure platforms.
12281 - Add support for building SUSE RPM packages.
12282 - Speed up initial bootstrapping for clients: if we are making our
12283 first ever connection to any entry guard, then don't mark it down
12285 - When only one Tor server in the network is labelled as a guard,
12286 and we've already picked him, we would cycle endlessly picking him
12287 again, being unhappy about it, etc. Now we specifically exclude
12288 current guards when picking a new guard.
12289 - Servers send create cells more reliably after the TLS connection
12290 is established: we were sometimes forgetting to send half of them
12291 when we had more than one pending.
12292 - If we get a create cell that asks us to extend somewhere, but the
12293 Tor server there doesn't match the expected digest, we now send
12294 a destroy cell back, rather than silently doing nothing.
12295 - Make options->RedirectExit work again.
12296 - Make cookie authentication for the controller work again.
12297 - Stop being picky about unusual characters in the arguments to
12298 mapaddress. It's none of our business.
12299 - Add a new config option "TestVia" that lets you specify preferred
12300 middle hops to use for test circuits. Perhaps this will let me
12301 debug the reachability problems better.
12303 o Log / documentation fixes:
12304 - If we're a server and some peer has a broken TLS certificate, don't
12305 log about it unless ProtocolWarnings is set, i.e., we want to hear
12306 about protocol violations by others.
12307 - Fix spelling of VirtualAddrNetwork in man page.
12308 - Add a better explanation at the top of the autogenerated torrc file
12309 about what happened to our old torrc.
12312 Changes in version 0.1.1.20 - 2006-05-23
12314 - Downgrade a log severity where servers complain that they're
12316 - Avoid a compile warning on FreeBSD.
12317 - Remove string size limit on NEWDESC messages; solve bug 291.
12318 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
12319 more thoroughly when we're running on windows.
12322 Changes in version 0.1.1.19-rc - 2006-05-03
12324 - Regenerate our local descriptor if it's dirty and we try to use
12325 it locally (e.g. if it changes during reachability detection).
12326 - If we setconf our ORPort to 0, we continued to listen on the
12327 old ORPort and receive connections.
12328 - Avoid a second warning about machine/limits.h on Debian
12330 - Be willing to add our own routerinfo into the routerlist.
12331 Now authorities will include themselves in their directories
12332 and network-statuses.
12333 - Stop trying to upload rendezvous descriptors to every
12334 directory authority: only try the v1 authorities.
12335 - Servers no longer complain when they think they're not
12336 registered with the directory authorities. There were too many
12338 - Backport dist-rpm changes so rpms can be built without errors.
12341 - Implement an option, VirtualAddrMask, to set which addresses
12342 get handed out in response to mapaddress requests. This works
12343 around a bug in tsocks where 127.0.0.0/8 is never socksified.
12346 Changes in version 0.1.1.18-rc - 2006-04-10
12348 - Work harder to download live network-statuses from all the
12349 directory authorities we know about. Improve the threshold
12350 decision logic so we're more robust to edge cases.
12351 - When fetching rendezvous descriptors, we were willing to ask
12352 v2 authorities too, which would always return 404.
12355 - Stop listing down or invalid nodes in the v1 directory. This will
12356 reduce its bulk by about 1/3, and reduce load on directory
12358 - When deciding whether a router is Fast or Guard-worthy, consider
12359 his advertised BandwidthRate and not just the BandwidthCapacity.
12360 - No longer ship INSTALL and README files -- they are useless now.
12361 - Force rpmbuild to behave and honor target_cpu.
12362 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
12363 - Start to include translated versions of the tor-doc-*.html
12364 files, along with the screenshots. Still needs more work.
12365 - Start sending back 512 and 451 errors if mapaddress fails,
12366 rather than not sending anything back at all.
12367 - When we fail to bind or listen on an incoming or outgoing
12368 socket, we should close it before failing. otherwise we just
12369 leak it. (thanks to weasel for finding.)
12370 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
12371 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
12372 - Make NoPublish (even though deprecated) work again.
12373 - Fix a minor security flaw where a versioning auth dirserver
12374 could list a recommended version many times in a row to make
12375 clients more convinced that it's recommended.
12376 - Fix crash bug if there are two unregistered servers running
12377 with the same nickname, one of them is down, and you ask for
12378 them by nickname in your EntryNodes or ExitNodes. Also, try
12379 to pick the one that's running rather than an arbitrary one.
12380 - Fix an infinite loop we could hit if we go offline for too long.
12381 - Complain when we hit WSAENOBUFS on recv() or write() too.
12382 Perhaps this will help us hunt the bug.
12383 - If you're not a versioning dirserver, don't put the string
12384 "client-versions \nserver-versions \n" in your network-status.
12385 - Lower the minimum required number of file descriptors to 1000,
12386 so we can have some overhead for Valgrind on Linux, where the
12387 default ulimit -n is 1024.
12390 - Add tor.dizum.com as the fifth authoritative directory server.
12391 - Add a new config option FetchUselessDescriptors, off by default,
12392 for when you plan to run "exitlist" on your client and you want
12393 to know about even the non-running descriptors.
12396 Changes in version 0.1.1.17-rc - 2006-03-28
12398 - Clients and servers since 0.1.1.10-alpha have been expiring
12399 connections whenever they are idle for 5 minutes and they *do*
12400 have circuits on them. Oops. With this new version, clients will
12401 discard their previous entry guard choices and avoid choosing
12402 entry guards running these flawed versions.
12403 - Fix memory leak when uncompressing concatenated zlib streams. This
12404 was causing substantial leaks over time on Tor servers.
12405 - The v1 directory was including servers as much as 48 hours old,
12406 because that's how the new routerlist->routers works. Now only
12407 include them if they're 20 hours old or less.
12410 - Resume building on irix64, netbsd 2.0, etc.
12411 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
12413 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
12414 and it is confusing some users.
12415 - Mirrors stop caching the v1 directory so often.
12416 - Make the max number of old descriptors that a cache will hold
12417 rise with the number of directory authorities, so we can scale.
12418 - Change our win32 uname() hack to be more forgiving about what
12419 win32 versions it thinks it's found.
12422 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
12424 - When the controller's *setconf commands fail, collect an error
12425 message in a string and hand it back to the controller.
12426 - Make the v2 dir's "Fast" flag based on relative capacity, just
12427 like "Stable" is based on median uptime. Name everything in the
12428 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
12429 - Log server fingerprint on startup, so new server operators don't
12430 have to go hunting around their filesystem for it.
12431 - Return a robots.txt on our dirport to discourage google indexing.
12432 - Let the controller ask for GETINFO dir/status/foo so it can ask
12433 directly rather than connecting to the dir port. Only works when
12434 dirport is set for now.
12436 o New config options rather than constants in the code:
12437 - SocksTimeout: How long do we let a socks connection wait
12438 unattached before we fail it?
12439 - CircuitBuildTimeout: Cull non-open circuits that were born
12440 at least this many seconds ago.
12441 - CircuitIdleTimeout: Cull open clean circuits that were born
12442 at least this many seconds ago.
12445 Changes in version 0.1.1.16-rc - 2006-03-18
12446 o Bugfixes on 0.1.1.15-rc:
12447 - Fix assert when the controller asks to attachstream a connect-wait
12448 or resolve-wait stream.
12449 - Now do address rewriting when the controller asks us to attach
12450 to a particular circuit too. This will let Blossom specify
12451 "moria2.exit" without having to learn what moria2's IP address is.
12452 - Make the "tor --verify-config" command-line work again, so people
12453 can automatically check if their torrc will parse.
12454 - Authoritative dirservers no longer require an open connection from
12455 a server to consider him "reachable". We need this change because
12456 when we add new auth dirservers, old servers won't know not to
12458 - Let Tor build on Sun CC again.
12459 - Fix an off-by-one buffer size in dirserv.c that magically never
12460 hit our three authorities but broke sjmurdoch's own tor network.
12461 - If we as a directory mirror don't know of any v1 directory
12462 authorities, then don't try to cache any v1 directories.
12463 - Stop warning about unknown servers in our family when they are
12464 given as hex digests.
12465 - Stop complaining as quickly to the server operator that he
12466 hasn't registered his nickname/key binding.
12467 - Various cleanups so we can add new V2 Auth Dirservers.
12468 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
12469 reflect the updated flags in our v2 dir protocol.
12470 - Resume allowing non-printable characters for exit streams (both
12471 for connecting and for resolving). Now we tolerate applications
12472 that don't follow the RFCs. But continue to block malformed names
12475 o Bugfixes on 0.1.0.x:
12476 - Fix assert bug in close_logs(): when we close and delete logs,
12477 remove them all from the global "logfiles" list.
12478 - Fix minor integer overflow in calculating when we expect to use up
12479 our bandwidth allocation before hibernating.
12480 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
12481 there are multiple SSLs installed with different versions.
12482 - When we try to be a server and Address is not explicitly set and
12483 our hostname resolves to a private IP address, try to use an
12484 interface address if it has a public address. Now Windows machines
12485 that think of themselves as localhost can work by default.
12488 - Let the controller ask for GETINFO dir/server/foo so it can ask
12489 directly rather than connecting to the dir port.
12490 - Let the controller tell us about certain router descriptors
12491 that it doesn't want Tor to use in circuits. Implement
12492 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
12493 - New config option SafeSocks to reject all application connections
12494 using unsafe socks protocols. Defaults to off.
12497 Changes in version 0.1.1.15-rc - 2006-03-11
12498 o Bugfixes and cleanups:
12499 - When we're printing strings from the network, don't try to print
12500 non-printable characters. This protects us against shell escape
12501 sequence exploits, and also against attacks to fool humans into
12502 misreading their logs.
12503 - Fix a bug where Tor would fail to establish any connections if you
12504 left it off for 24 hours and then started it: we were happy with
12505 the obsolete network statuses, but they all referred to router
12506 descriptors that were too old to fetch, so we ended up with no
12507 valid router descriptors.
12508 - Fix a seg fault in the controller's "getinfo orconn-status"
12509 command while listing status on incoming handshaking connections.
12510 Introduce a status name "NEW" for these connections.
12511 - If we get a linelist or linelist_s config option from the torrc
12512 (e.g. ExitPolicy) and it has no value, warn and skip rather than
12513 silently resetting it to its default.
12514 - Don't abandon entry guards until they've been down or gone for
12516 - Cleaner and quieter log messages.
12519 - New controller signal NEWNYM that makes new application requests
12520 use clean circuits.
12521 - Add a new circuit purpose 'controller' to let the controller ask
12522 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
12523 controller command to let you specify the purpose if you're
12524 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
12525 command to let you change a circuit's purpose after it's been
12527 - Accept "private:*" in routerdesc exit policies; not generated yet
12528 because older Tors do not understand it.
12529 - Add BSD-style contributed startup script "rc.subr" from Peter
12533 Changes in version 0.1.1.14-alpha - 2006-02-20
12534 o Bugfixes on 0.1.1.x:
12535 - Don't die if we ask for a stdout or stderr log (even implicitly)
12536 and we're set to RunAsDaemon -- just warn.
12537 - We still had a few bugs in the OR connection rotation code that
12538 caused directory servers to slowly aggregate connections to other
12539 fast Tor servers. This time for sure!
12540 - Make log entries on Win32 include the name of the function again.
12541 - We were treating a pair of exit policies if they were equal even
12542 if one said accept and the other said reject -- causing us to
12543 not always publish a new descriptor since we thought nothing
12545 - Retry pending server downloads as well as pending networkstatus
12546 downloads when we unexpectedly get a socks request.
12547 - We were ignoring the IS_FAST flag in the directory status,
12548 meaning we were willing to pick trivial-bandwidth nodes for "fast"
12550 - If the controller's SAVECONF command fails (e.g. due to file
12551 permissions), let the controller know that it failed.
12554 - If we're trying to be a Tor server and running Windows 95/98/ME
12555 as a server, explain that we'll likely crash.
12556 - When we're a server, a client asks for an old-style directory,
12557 and our write bucket is empty, don't give it to him. This way
12558 small servers can continue to serve the directory *sometimes*,
12559 without getting overloaded.
12560 - Compress exit policies even more -- look for duplicate lines
12562 - Clients now honor the "guard" flag in the router status when
12563 picking entry guards, rather than looking at is_fast or is_stable.
12564 - Retain unrecognized lines in $DATADIR/state file, so that we can
12565 be forward-compatible.
12566 - Generate 18.0.0.0/8 address policy format in descs when we can;
12567 warn when the mask is not reducible to a bit-prefix.
12568 - Let the user set ControlListenAddress in the torrc. This can be
12569 dangerous, but there are some cases (like a secured LAN) where it
12571 - Split ReachableAddresses into ReachableDirAddresses and
12572 ReachableORAddresses, so we can restrict Dir conns to port 80
12573 and OR conns to port 443.
12574 - Now we can target arch and OS in rpm builds (contributed by
12575 Phobos). Also make the resulting dist-rpm filename match the
12577 - New config options to help controllers: FetchServerDescriptors
12578 and FetchHidServDescriptors for whether to fetch server
12579 info and hidserv info or let the controller do it, and
12580 PublishServerDescriptor and PublishHidServDescriptors.
12581 - Also let the controller set the __AllDirActionsPrivate config
12582 option if you want all directory fetches/publishes to happen via
12583 Tor (it assumes your controller bootstraps your circuits).
12586 Changes in version 0.1.0.17 - 2006-02-17
12587 o Crash bugfixes on 0.1.0.x:
12588 - When servers with a non-zero DirPort came out of hibernation,
12589 sometimes they would trigger an assert.
12591 o Other important bugfixes:
12592 - On platforms that don't have getrlimit (like Windows), we were
12593 artificially constraining ourselves to a max of 1024
12594 connections. Now just assume that we can handle as many as 15000
12595 connections. Hopefully this won't cause other problems.
12597 o Backported features:
12598 - When we're a server, a client asks for an old-style directory,
12599 and our write bucket is empty, don't give it to him. This way
12600 small servers can continue to serve the directory *sometimes*,
12601 without getting overloaded.
12602 - Whenever you get a 503 in response to a directory fetch, try
12603 once more. This will become important once servers start sending
12604 503's whenever they feel busy.
12605 - Fetch a new directory every 120 minutes, not every 40 minutes.
12606 Now that we have hundreds of thousands of users running the old
12607 directory algorithm, it's starting to hurt a lot.
12608 - Bump up the period for forcing a hidden service descriptor upload
12609 from 20 minutes to 1 hour.
12612 Changes in version 0.1.1.13-alpha - 2006-02-09
12613 o Crashes in 0.1.1.x:
12614 - When you tried to setconf ORPort via the controller, Tor would
12615 crash. So people using TorCP to become a server were sad.
12616 - Solve (I hope) the stack-smashing bug that we were seeing on fast
12617 servers. The problem appears to be something do with OpenSSL's
12618 random number generation, or how we call it, or something. Let me
12619 know if the crashes continue.
12620 - Turn crypto hardware acceleration off by default, until we find
12621 somebody smart who can test it for us. (It appears to produce
12622 seg faults in at least some cases.)
12623 - Fix a rare assert error when we've tried all intro points for
12624 a hidden service and we try fetching the service descriptor again:
12625 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
12628 - Fix a major load balance bug: we were round-robining in 16 KB
12629 chunks, and servers with bandwidthrate of 20 KB, while downloading
12630 a 600 KB directory, would starve their other connections. Now we
12631 try to be a bit more fair.
12632 - Dir authorities and mirrors were never expiring the newest
12633 descriptor for each server, causing memory and directory bloat.
12634 - Fix memory-bloating and connection-bloating bug on servers: We
12635 were never closing any connection that had ever had a circuit on
12636 it, because we were checking conn->n_circuits == 0, yet we had a
12637 bug that let it go negative.
12638 - Make Tor work using squid as your http proxy again -- squid
12639 returns an error if you ask for a URL that's too long, and it uses
12640 a really generic error message. Plus, many people are behind a
12641 transparent squid so they don't even realize it.
12642 - On platforms that don't have getrlimit (like Windows), we were
12643 artificially constraining ourselves to a max of 1024
12644 connections. Now just assume that we can handle as many as 15000
12645 connections. Hopefully this won't cause other problems.
12646 - Add a new config option ExitPolicyRejectPrivate which defaults to
12647 1. This means all exit policies will begin with rejecting private
12648 addresses, unless the server operator explicitly turns it off.
12651 - Clients no longer download descriptors for non-running
12653 - Before we add new directory authorities, we should make it
12654 clear that only v1 authorities should receive/publish hidden
12655 service descriptors.
12658 - As soon as we've fetched some more directory info, immediately
12659 try to download more server descriptors. This way we don't have
12660 a 10 second pause during initial bootstrapping.
12661 - Remove even more loud log messages that the server operator can't
12663 - When we're running an obsolete or un-recommended version, make
12664 the log message more clear about what the problem is and what
12665 versions *are* still recommended.
12666 - Provide a more useful warn message when our onion queue gets full:
12667 the CPU is too slow or the exit policy is too liberal.
12668 - Don't warn when we receive a 503 from a dirserver/cache -- this
12669 will pave the way for them being able to refuse if they're busy.
12670 - When we fail to bind a listener, try to provide a more useful
12671 log message: e.g., "Is Tor already running?"
12672 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
12673 Goldberg can prove things about our handshake protocol more
12675 - MaxConn has been obsolete for a while now. Document the ConnLimit
12676 config option, which is a *minimum* number of file descriptors
12677 that must be available else Tor refuses to start.
12678 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
12679 if you log to syslog and want something other than LOG_DAEMON.
12680 - Make dirservers generate a separate "guard" flag to mean,
12681 "would make a good entry guard". Make clients parse it and vote
12682 on it. Not used by clients yet.
12683 - Implement --with-libevent-dir option to ./configure. Also, improve
12684 search techniques to find libevent, and use those for openssl too.
12685 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
12686 - Only start testing reachability once we've established a
12687 circuit. This will make startup on dirservers less noisy.
12688 - Don't try to upload hidden service descriptors until we have
12689 established a circuit.
12690 - Fix the controller's "attachstream 0" command to treat conn like
12691 it just connected, doing address remapping, handling .exit and
12692 .onion idioms, and so on. Now we're more uniform in making sure
12693 that the controller hears about new and closing connections.
12696 Changes in version 0.1.1.12-alpha - 2006-01-11
12697 o Bugfixes on 0.1.1.x:
12698 - The fix to close duplicate server connections was closing all
12699 Tor client connections if they didn't establish a circuit
12700 quickly enough. Oops.
12701 - Fix minor memory issue (double-free) that happened on exit.
12703 o Bugfixes on 0.1.0.x:
12704 - Tor didn't warn when it failed to open a log file.
12707 Changes in version 0.1.1.11-alpha - 2006-01-10
12708 o Crashes in 0.1.1.x:
12709 - Include all the assert/crash fixes from 0.1.0.16.
12710 - If you start Tor and then quit very quickly, there were some
12711 races that tried to free things that weren't allocated yet.
12712 - Fix a rare memory stomp if you're running hidden services.
12713 - Fix segfault when specifying DirServer in config without nickname.
12714 - Fix a seg fault when you finish connecting to a server but at
12715 that moment you dump his server descriptor.
12716 - Extendcircuit and Attachstream controller commands would
12717 assert/crash if you don't give them enough arguments.
12718 - Fix an assert error when we're out of space in the connection_list
12719 and we try to post a hidden service descriptor (reported by weasel).
12720 - If you specify a relative torrc path and you set RunAsDaemon in
12721 your torrc, then it chdir()'s to the new directory. If you HUP,
12722 it tries to load the new torrc location, fails, and exits.
12723 The fix: no longer allow a relative path to torrc using -f.
12726 - Implement "entry guards": automatically choose a handful of entry
12727 nodes and stick with them for all circuits. Only pick new guards
12728 when the ones you have are unsuitable, and if the old guards
12729 become suitable again, switch back. This will increase security
12730 dramatically against certain end-point attacks. The EntryNodes
12731 config option now provides some hints about which entry guards you
12732 want to use most; and StrictEntryNodes means to only use those.
12733 - New directory logic: download by descriptor digest, not by
12734 fingerprint. Caches try to download all listed digests from
12735 authorities; clients try to download "best" digests from caches.
12736 This avoids partitioning and isolating attacks better.
12737 - Make the "stable" router flag in network-status be the median of
12738 the uptimes of running valid servers, and make clients pay
12739 attention to the network-status flags. Thus the cutoff adapts
12740 to the stability of the network as a whole, making IRC, IM, etc
12741 connections more reliable.
12744 - Tor servers with dynamic IP addresses were needing to wait 18
12745 hours before they could start doing reachability testing using
12746 the new IP address and ports. This is because they were using
12747 the internal descriptor to learn what to test, yet they were only
12748 rebuilding the descriptor once they decided they were reachable.
12749 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
12750 to download certain server descriptors, throw them away, and then
12751 fetch them again after 30 minutes. Now mirrors throw away these
12752 server descriptors so clients can't get them.
12753 - We were leaving duplicate connections to other ORs open for a week,
12754 rather than closing them once we detect a duplicate. This only
12755 really affected authdirservers, but it affected them a lot.
12756 - Spread the authdirservers' reachability testing over the entire
12757 testing interval, so we don't try to do 500 TLS's at once every
12761 - If the network is down, and we try to connect to a conn because
12762 we have a circuit in mind, and we timeout (30 seconds) because the
12763 network never answers, we were expiring the circuit, but we weren't
12764 obsoleting the connection or telling the entry_guards functions.
12765 - Some Tor servers process billions of cells per day. These statistics
12766 need to be uint64_t's.
12767 - Check for integer overflows in more places, when adding elements
12768 to smartlists. This could possibly prevent a buffer overflow
12769 on malicious huge inputs. I don't see any, but I haven't looked
12771 - ReachableAddresses kept growing new "reject *:*" lines on every
12773 - When you "setconf log" via the controller, it should remove all
12774 logs. We were automatically adding back in a "log notice stdout".
12775 - Newly bootstrapped Tor networks couldn't establish hidden service
12776 circuits until they had nodes with high uptime. Be more tolerant.
12777 - We were marking servers down when they could not answer every piece
12778 of the directory request we sent them. This was far too harsh.
12779 - Fix the torify (tsocks) config file to not use Tor for localhost
12781 - Directory authorities now go to the proper authority when asking for
12782 a networkstatus, even when they want a compressed one.
12783 - Fix a harmless bug that was causing Tor servers to log
12784 "Got an end because of misc error, but we're not an AP. Closing."
12785 - Authorities were treating their own descriptor changes as cosmetic,
12786 meaning the descriptor available in the network-status and the
12787 descriptor that clients downloaded were different.
12788 - The OS X installer was adding a symlink for tor_resolve but
12789 the binary was called tor-resolve (reported by Thomas Hardly).
12790 - Workaround a problem with some http proxies where they refuse GET
12791 requests that specify "Content-Length: 0" (reported by Adrian).
12792 - Fix wrong log message when you add a "HiddenServiceNodes" config
12793 line without any HiddenServiceDir line (reported by Chris Thomas).
12796 - Write the TorVersion into the state file so we have a prayer of
12797 keeping forward and backward compatibility.
12798 - Revive the FascistFirewall config option rather than eliminating it:
12799 now it's a synonym for ReachableAddresses *:80,*:443.
12800 - Clients choose directory servers from the network status lists,
12801 not from their internal list of router descriptors. Now they can
12802 go to caches directly rather than needing to go to authorities
12804 - Directory authorities ignore router descriptors that have only
12805 cosmetic differences: do this for 0.1.0.x servers now too.
12806 - Add a new flag to network-status indicating whether the server
12807 can answer v2 directory requests too.
12808 - Authdirs now stop whining so loudly about bad descriptors that
12809 they fetch from other dirservers. So when there's a log complaint,
12810 it's for sure from a freshly uploaded descriptor.
12811 - Reduce memory requirements in our structs by changing the order
12813 - There used to be two ways to specify your listening ports in a
12814 server descriptor: on the "router" line and with a separate "ports"
12815 line. Remove support for the "ports" line.
12816 - New config option "AuthDirRejectUnlisted" for auth dirservers as
12817 a panic button: if we get flooded with unusable servers we can
12818 revert to only listing servers in the approved-routers file.
12819 - Auth dir servers can now mark a fingerprint as "!reject" or
12820 "!invalid" in the approved-routers file (as its nickname), to
12821 refuse descriptors outright or include them but marked as invalid.
12822 - Servers store bandwidth history across restarts/crashes.
12823 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
12824 get a better idea of why their circuits failed. Not used yet.
12825 - Directory mirrors now cache up to 16 unrecognized network-status
12826 docs. Now we can add new authdirservers and they'll be cached too.
12827 - When picking a random directory, prefer non-authorities if any
12829 - New controller option "getinfo desc/all-recent" to fetch the
12830 latest server descriptor for every router that Tor knows about.
12833 Changes in version 0.1.0.16 - 2006-01-02
12834 o Crash bugfixes on 0.1.0.x:
12835 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
12836 corrupting the heap, losing FDs, or crashing when we need to resize
12837 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
12838 - It turns out sparc64 platforms crash on unaligned memory access
12839 too -- so detect and avoid this.
12840 - Handle truncated compressed data correctly (by detecting it and
12842 - Fix possible-but-unlikely free(NULL) in control.c.
12843 - When we were closing connections, there was a rare case that
12844 stomped on memory, triggering seg faults and asserts.
12845 - Avoid potential infinite recursion when building a descriptor. (We
12846 don't know that it ever happened, but better to fix it anyway.)
12847 - We were neglecting to unlink marked circuits from soon-to-close OR
12848 connections, which caused some rare scribbling on freed memory.
12849 - Fix a memory stomping race bug when closing the joining point of two
12850 rendezvous circuits.
12851 - Fix an assert in time parsing found by Steven Murdoch.
12853 o Other bugfixes on 0.1.0.x:
12854 - When we're doing reachability testing, provide more useful log
12855 messages so the operator knows what to expect.
12856 - Do not check whether DirPort is reachable when we are suppressing
12857 advertising it because of hibernation.
12858 - When building with -static or on Solaris, we sometimes needed -ldl.
12859 - When we're deciding whether a stream has enough circuits around
12860 that can handle it, count the freshly dirty ones and not the ones
12861 that are so dirty they won't be able to handle it.
12862 - When we're expiring old circuits, we had a logic error that caused
12863 us to close new rendezvous circuits rather than old ones.
12864 - Give a more helpful log message when you try to change ORPort via
12865 the controller: you should upgrade Tor if you want that to work.
12866 - We were failing to parse Tor versions that start with "Tor ".
12867 - Tolerate faulty streams better: when a stream fails for reason
12868 exitpolicy, stop assuming that the router is lying about his exit
12869 policy. When a stream fails for reason misc, allow it to retry just
12870 as if it was resolvefailed. When a stream has failed three times,
12871 reset its failure count so we can try again and get all three tries.
12874 Changes in version 0.1.1.10-alpha - 2005-12-11
12875 o Correctness bugfixes on 0.1.0.x:
12876 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
12877 corrupting the heap, losing FDs, or crashing when we need to resize
12878 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
12879 - Stop doing the complex voodoo overkill checking for insecure
12880 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
12881 - When we were closing connections, there was a rare case that
12882 stomped on memory, triggering seg faults and asserts.
12883 - We were neglecting to unlink marked circuits from soon-to-close OR
12884 connections, which caused some rare scribbling on freed memory.
12885 - When we're deciding whether a stream has enough circuits around
12886 that can handle it, count the freshly dirty ones and not the ones
12887 that are so dirty they won't be able to handle it.
12888 - Recover better from TCP connections to Tor servers that are
12889 broken but don't tell you (it happens!); and rotate TLS
12890 connections once a week.
12891 - When we're expiring old circuits, we had a logic error that caused
12892 us to close new rendezvous circuits rather than old ones.
12893 - Fix a scary-looking but apparently harmless bug where circuits
12894 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
12895 servers, and never switch to state CIRCUIT_STATE_OPEN.
12896 - When building with -static or on Solaris, we sometimes needed to
12898 - Give a useful message when people run Tor as the wrong user,
12899 rather than telling them to start chowning random directories.
12900 - We were failing to inform the controller about new .onion streams.
12902 o Security bugfixes on 0.1.0.x:
12903 - Refuse server descriptors if the fingerprint line doesn't match
12904 the included identity key. Tor doesn't care, but other apps (and
12905 humans) might actually be trusting the fingerprint line.
12906 - We used to kill the circuit when we receive a relay command we
12907 don't recognize. Now we just drop it.
12908 - Start obeying our firewall options more rigorously:
12909 . If we can't get to a dirserver directly, try going via Tor.
12910 . Don't ever try to connect (as a client) to a place our
12911 firewall options forbid.
12912 . If we specify a proxy and also firewall options, obey the
12913 firewall options even when we're using the proxy: some proxies
12914 can only proxy to certain destinations.
12915 - Fix a bug found by Lasse Overlier: when we were making internal
12916 circuits (intended to be cannibalized later for rendezvous and
12917 introduction circuits), we were picking them so that they had
12918 useful exit nodes. There was no need for this, and it actually
12919 aids some statistical attacks.
12920 - Start treating internal circuits and exit circuits separately.
12921 It's important to keep them separate because internal circuits
12922 have their last hops picked like middle hops, rather than like
12923 exit hops. So exiting on them will break the user's expectations.
12925 o Bugfixes on 0.1.1.x:
12926 - Take out the mis-feature where we tried to detect IP address
12927 flapping for people with DynDNS, and chose not to upload a new
12928 server descriptor sometimes.
12929 - Try to be compatible with OpenSSL 0.9.6 again.
12930 - Log fix: when the controller is logging about .onion addresses,
12931 sometimes it didn't include the ".onion" part of the address.
12932 - Don't try to modify options->DirServers internally -- if the
12933 user didn't specify any, just add the default ones directly to
12934 the trusted dirserver list. This fixes a bug where people running
12935 controllers would use SETCONF on some totally unrelated config
12936 option, and Tor would start yelling at them about changing their
12938 - Let the controller's redirectstream command specify a port, in
12939 case the controller wants to change that too.
12940 - When we requested a pile of server descriptors, we sometimes
12941 accidentally launched a duplicate request for the first one.
12942 - Bugfix for trackhostexits: write down the fingerprint of the
12943 chosen exit, not its nickname, because the chosen exit might not
12945 - When parsing foo.exit, if foo is unknown, and we are leaving
12946 circuits unattached, set the chosen_exit field and leave the
12947 address empty. This matters because controllers got confused
12949 - Directory authorities no longer try to download server
12950 descriptors that they know they will reject.
12952 o Features and updates:
12953 - Replace balanced trees with hash tables: this should make stuff
12954 significantly faster.
12955 - Resume using the AES counter-mode implementation that we ship,
12956 rather than OpenSSL's. Ours is significantly faster.
12957 - Many other CPU and memory improvements.
12958 - Add a new config option FastFirstHopPK (on by default) so clients
12959 do a trivial crypto handshake for their first hop, since TLS has
12960 already taken care of confidentiality and authentication.
12961 - Add a new config option TestSocks so people can see if their
12962 applications are using socks4, socks4a, socks5-with-ip, or
12963 socks5-with-hostname. This way they don't have to keep mucking
12964 with tcpdump and wondering if something got cached somewhere.
12965 - Warn when listening on a public address for socks. I suspect a
12966 lot of people are setting themselves up as open socks proxies,
12967 and they have no idea that jerks on the Internet are using them,
12968 since they simply proxy the traffic into the Tor network.
12969 - Add "private:*" as an alias in configuration for policies. Now
12970 you can simplify your exit policy rather than needing to list
12971 every single internal or nonroutable network space.
12972 - Add a new controller event type that allows controllers to get
12973 all server descriptors that were uploaded to a router in its role
12974 as authoritative dirserver.
12975 - Start shipping socks-extensions.txt, tor-doc-unix.html,
12976 tor-doc-server.html, and stylesheet.css in the tarball.
12977 - Stop shipping tor-doc.html in the tarball.
12980 Changes in version 0.1.1.9-alpha - 2005-11-15
12981 o Usability improvements:
12982 - Start calling it FooListenAddress rather than FooBindAddress,
12983 since few of our users know what it means to bind an address
12985 - Reduce clutter in server logs. We're going to try to make
12986 them actually usable now. New config option ProtocolWarnings that
12987 lets you hear about how _other Tors_ are breaking the protocol. Off
12989 - Divide log messages into logging domains. Once we put some sort
12990 of interface on this, it will let people looking at more verbose
12991 log levels specify the topics they want to hear more about.
12992 - Make directory servers return better http 404 error messages
12993 instead of a generic "Servers unavailable".
12994 - Check for even more Windows version flags when writing the platform
12995 string in server descriptors, and note any we don't recognize.
12996 - Clean up more of the OpenSSL memory when exiting, so we can detect
12997 memory leaks better.
12998 - Make directory authorities be non-versioning, non-naming by
12999 default. Now we can add new directory servers without requiring
13000 their operators to pay close attention.
13001 - When logging via syslog, include the pid whenever we provide
13002 a log entry. Suggested by Todd Fries.
13004 o Performance improvements:
13005 - Directory servers now silently throw away new descriptors that
13006 haven't changed much if the timestamps are similar. We do this to
13007 tolerate older Tor servers that upload a new descriptor every 15
13008 minutes. (It seemed like a good idea at the time.)
13009 - Inline bottleneck smartlist functions; use fast versions by default.
13010 - Add a "Map from digest to void*" abstraction digestmap_t so we
13011 can do less hex encoding/decoding. Use it in router_get_by_digest()
13012 to resolve a performance bottleneck.
13013 - Allow tor_gzip_uncompress to extract as much as possible from
13014 truncated compressed data. Try to extract as many
13015 descriptors as possible from truncated http responses (when
13016 DIR_PURPOSE_FETCH_ROUTERDESC).
13017 - Make circ->onionskin a pointer, not a static array. moria2 was using
13018 125000 circuit_t's after it had been up for a few weeks, which
13019 translates to 20+ megs of wasted space.
13020 - The private half of our EDH handshake keys are now chosen out
13021 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
13023 o Security improvements:
13024 - Start making directory caches retain old routerinfos, so soon
13025 clients can start asking by digest of descriptor rather than by
13026 fingerprint of server.
13027 - Add half our entropy from RAND_poll in OpenSSL. This knows how
13028 to use egd (if present), openbsd weirdness (if present), vms/os2
13029 weirdness (if we ever port there), and more in the future.
13031 o Bugfixes on 0.1.0.x:
13032 - Do round-robin writes of at most 16 kB per write. This might be
13033 more fair on loaded Tor servers, and it might resolve our Windows
13034 crash bug. It might also slow things down.
13035 - Our TLS handshakes were generating a single public/private
13036 keypair for the TLS context, rather than making a new one for
13037 each new connections. Oops. (But we were still rotating them
13038 periodically, so it's not so bad.)
13039 - When we were cannibalizing a circuit with a particular exit
13040 node in mind, we weren't checking to see if that exit node was
13041 already present earlier in the circuit. Oops.
13042 - When a Tor server's IP changes (e.g. from a dyndns address),
13043 upload a new descriptor so clients will learn too.
13044 - Really busy servers were keeping enough circuits open on stable
13045 connections that they were wrapping around the circuit_id
13046 space. (It's only two bytes.) This exposed a bug where we would
13047 feel free to reuse a circuit_id even if it still exists but has
13048 been marked for close. Try to fix this bug. Some bug remains.
13049 - If we would close a stream early (e.g. it asks for a .exit that
13050 we know would refuse it) but the LeaveStreamsUnattached config
13051 option is set by the controller, then don't close it.
13053 o Bugfixes on 0.1.1.8-alpha:
13054 - Fix a big pile of memory leaks, some of them serious.
13055 - Do not try to download a routerdesc if we would immediately reject
13057 - Resume inserting a newline between all router descriptors when
13058 generating (old style) signed directories, since our spec says
13060 - When providing content-type application/octet-stream for
13061 server descriptors using .z, we were leaving out the
13062 content-encoding header. Oops. (Everything tolerated this just
13063 fine, but that doesn't mean we need to be part of the problem.)
13064 - Fix a potential seg fault in getconf and getinfo using version 1
13065 of the controller protocol.
13066 - Avoid crash: do not check whether DirPort is reachable when we
13067 are suppressing it because of hibernation.
13068 - Make --hash-password not crash on exit.
13071 Changes in version 0.1.1.8-alpha - 2005-10-07
13072 o New features (major):
13073 - Clients don't download or use the directory anymore. Now they
13074 download and use network-statuses from the trusted dirservers,
13075 and fetch individual server descriptors as needed from mirrors.
13076 See dir-spec.txt for all the gory details.
13077 - Be more conservative about whether to advertise our DirPort.
13078 The main change is to not advertise if we're running at capacity
13079 and either a) we could hibernate or b) our capacity is low and
13080 we're using a default DirPort.
13081 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
13083 o New features (minor):
13084 - Try to be smart about when to retry network-status and
13085 server-descriptor fetches. Still needs some tuning.
13086 - Stop parsing, storing, or using running-routers output (but
13087 mirrors still cache and serve it).
13088 - Consider a threshold of versioning dirservers (dirservers who have
13089 an opinion about which Tor versions are still recommended) before
13090 deciding whether to warn the user that he's obsolete.
13091 - Dirservers can now reject/invalidate by key and IP, with the
13092 config options "AuthDirInvalid" and "AuthDirReject". This is
13093 useful since currently we automatically list servers as running
13094 and usable even if we know they're jerks.
13095 - Provide dire warnings to any users who set DirServer; move it out
13096 of torrc.sample and into torrc.complete.
13097 - Add MyFamily to torrc.sample in the server section.
13098 - Add nicknames to the DirServer line, so we can refer to them
13099 without requiring all our users to memorize their IP addresses.
13100 - When we get an EOF or a timeout on a directory connection, note
13101 how many bytes of serverdesc we are dropping. This will help
13102 us determine whether it is smart to parse incomplete serverdesc
13104 - Add a new function to "change pseudonyms" -- that is, to stop
13105 using any currently-dirty circuits for new streams, so we don't
13106 link new actions to old actions. Currently it's only called on
13107 HUP (or SIGNAL RELOAD).
13108 - On sighup, if UseHelperNodes changed to 1, use new circuits.
13109 - Start using RAND_bytes rather than RAND_pseudo_bytes from
13110 OpenSSL. Also, reseed our entropy every hour, not just at
13111 startup. And entropy in 512-bit chunks, not 160-bit chunks.
13113 o Fixes on 0.1.1.7-alpha:
13114 - Nobody ever implemented EVENT_ADDRMAP for control protocol
13115 version 0, so don't let version 0 controllers ask for it.
13116 - If you requested something with too many newlines via the
13117 v1 controller protocol, you could crash tor.
13118 - Fix a number of memory leaks, including some pretty serious ones.
13119 - Re-enable DirPort testing again, so Tor servers will be willing
13120 to advertise their DirPort if it's reachable.
13121 - On TLS handshake, only check the other router's nickname against
13122 its expected nickname if is_named is set.
13124 o Fixes forward-ported from 0.1.0.15:
13125 - Don't crash when we don't have any spare file descriptors and we
13126 try to spawn a dns or cpu worker.
13127 - Make the numbers in read-history and write-history into uint64s,
13128 so they don't overflow and publish negatives in the descriptor.
13130 o Fixes on 0.1.0.x:
13131 - For the OS X package's modified privoxy config file, comment
13132 out the "logfile" line so we don't log everything passed
13134 - We were whining about using socks4 or socks5-with-local-lookup
13135 even when it's an IP in the "virtual" range we designed exactly
13137 - We were leaking some memory every time the client changes IPs.
13138 - Never call free() on tor_malloc()d memory. This will help us
13139 use dmalloc to detect memory leaks.
13140 - Check for named servers when looking them up by nickname;
13141 warn when we'recalling a non-named server by its nickname;
13142 don't warn twice about the same name.
13143 - Try to list MyFamily elements by key, not by nickname, and warn
13144 if we've not heard of the server.
13145 - Make windows platform detection (uname equivalent) smarter.
13146 - It turns out sparc64 doesn't like unaligned access either.
13149 Changes in version 0.1.0.15 - 2005-09-23
13150 o Bugfixes on 0.1.0.x:
13151 - Reject ports 465 and 587 (spam targets) in default exit policy.
13152 - Don't crash when we don't have any spare file descriptors and we
13153 try to spawn a dns or cpu worker.
13154 - Get rid of IgnoreVersion undocumented config option, and make us
13155 only warn, never exit, when we're running an obsolete version.
13156 - Don't try to print a null string when your server finds itself to
13157 be unreachable and the Address config option is empty.
13158 - Make the numbers in read-history and write-history into uint64s,
13159 so they don't overflow and publish negatives in the descriptor.
13160 - Fix a minor memory leak in smartlist_string_remove().
13161 - We were only allowing ourselves to upload a server descriptor at
13162 most every 20 minutes, even if it changed earlier than that.
13163 - Clean up log entries that pointed to old URLs.
13166 Changes in version 0.1.1.7-alpha - 2005-09-14
13167 o Fixes on 0.1.1.6-alpha:
13168 - Exit servers were crashing when people asked them to make a
13169 connection to an address not in their exit policy.
13170 - Looking up a non-existent stream for a v1 control connection would
13172 - Fix a seg fault if we ask a dirserver for a descriptor by
13173 fingerprint but he doesn't know about him.
13174 - SETCONF was appending items to linelists, not clearing them.
13175 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
13176 out and refuse the setconf if it would fail.
13177 - Downgrade the dirserver log messages when whining about
13181 - Add Peter Palfrader's check-tor script to tor/contrib/
13182 It lets you easily check whether a given server (referenced by
13183 nickname) is reachable by you.
13184 - Numerous changes to move towards client-side v2 directories. Not
13187 o Fixes on 0.1.0.x:
13188 - If the user gave tor an odd number of command-line arguments,
13189 we were silently ignoring the last one. Now we complain and fail.
13190 [This wins the oldest-bug prize -- this bug has been present since
13191 November 2002, as released in Tor 0.0.0.]
13192 - Do not use unaligned memory access on alpha, mips, or mipsel.
13193 It *works*, but is very slow, so we treat them as if it doesn't.
13194 - Retry directory requests if we fail to get an answer we like
13195 from a given dirserver (we were retrying before, but only if
13196 we fail to connect).
13197 - When writing the RecommendedVersions line, sort them first.
13198 - When the client asked for a rendezvous port that the hidden
13199 service didn't want to provide, we were sending an IP address
13200 back along with the end cell. Fortunately, it was zero. But stop
13202 - Correct "your server is reachable" log entries to indicate that
13203 it was self-testing that told us so.
13206 Changes in version 0.1.1.6-alpha - 2005-09-09
13207 o Fixes on 0.1.1.5-alpha:
13208 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
13209 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
13210 - Fix bug with tor_memmem finding a match at the end of the string.
13211 - Make unit tests run without segfaulting.
13212 - Resolve some solaris x86 compile warnings.
13213 - Handle duplicate lines in approved-routers files without warning.
13214 - Fix bug where as soon as a server refused any requests due to his
13215 exit policy (e.g. when we ask for localhost and he tells us that's
13216 127.0.0.1 and he won't do it), we decided he wasn't obeying his
13217 exit policy using him for any exits.
13218 - Only do openssl hardware accelerator stuff if openssl version is
13221 o New controller features/fixes:
13222 - Add a "RESETCONF" command so you can set config options like
13223 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
13224 a config option in the torrc with no value, then it clears it
13225 entirely (rather than setting it to its default).
13226 - Add a "GETINFO config-file" to tell us where torrc is.
13227 - Avoid sending blank lines when GETINFO replies should be empty.
13228 - Add a QUIT command for the controller (for using it manually).
13229 - Fix a bug in SAVECONF that was adding default dirservers and
13230 other redundant entries to the torrc file.
13232 o Start on the new directory design:
13233 - Generate, publish, cache, serve new network-status format.
13234 - Publish individual descriptors (by fingerprint, by "all", and by
13236 - Publish client and server recommended versions separately.
13237 - Allow tor_gzip_uncompress() to handle multiple concatenated
13238 compressed strings. Serve compressed groups of router
13239 descriptors. The compression logic here could be more
13241 - Distinguish v1 authorities (all currently trusted directories)
13242 from v2 authorities (all trusted directories).
13243 - Change DirServers config line to note which dirs are v1 authorities.
13244 - Add configuration option "V1AuthoritativeDirectory 1" which
13245 moria1, moria2, and tor26 should set.
13246 - Remove option when getting directory cache to see whether they
13247 support running-routers; they all do now. Replace it with one
13248 to see whether caches support v2 stuff.
13251 - Dirservers now do their own external reachability testing of each
13252 Tor server, and only list them as running if they've been found to
13253 be reachable. We also send back warnings to the server's logs if
13254 it uploads a descriptor that we already believe is unreachable.
13255 - Implement exit enclaves: if we know an IP address for the
13256 destination, and there's a running Tor server at that address
13257 which allows exit to the destination, then extend the circuit to
13258 that exit first. This provides end-to-end encryption and end-to-end
13259 authentication. Also, if the user wants a .exit address or enclave,
13260 use 4 hops rather than 3, and cannibalize a general circ for it
13262 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
13263 controller. Also, rotate dns and cpu workers if the controller
13264 changes options that will affect them; and initialize the dns
13265 worker cache tree whether or not we start out as a server.
13266 - Only upload a new server descriptor when options change, 18
13267 hours have passed, uptime is reset, or bandwidth changes a lot.
13268 - Check [X-]Forwarded-For headers in HTTP requests when generating
13269 log messages. This lets people run dirservers (and caches) behind
13270 Apache but still know which IP addresses are causing warnings.
13272 o Config option changes:
13273 - Replace (Fascist)Firewall* config options with a new
13274 ReachableAddresses option that understands address policies.
13275 For example, "ReachableAddresses *:80,*:443"
13276 - Get rid of IgnoreVersion undocumented config option, and make us
13277 only warn, never exit, when we're running an obsolete version.
13278 - Make MonthlyAccountingStart config option truly obsolete now.
13280 o Fixes on 0.1.0.x:
13281 - Reject ports 465 and 587 in the default exit policy, since
13282 people have started using them for spam too.
13283 - It turns out we couldn't bootstrap a network since we added
13284 reachability detection in 0.1.0.1-rc. Good thing the Tor network
13285 has never gone down. Add an AssumeReachable config option to let
13286 servers and dirservers bootstrap. When we're trying to build a
13287 high-uptime or high-bandwidth circuit but there aren't enough
13288 suitable servers, try being less picky rather than simply failing.
13289 - Our logic to decide if the OR we connected to was the right guy
13290 was brittle and maybe open to a mitm for unverified routers.
13291 - We weren't cannibalizing circuits correctly for
13292 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
13293 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
13294 build those from scratch. This should make hidden services faster.
13295 - Predict required circuits better, with an eye toward making hidden
13296 services faster on the service end.
13297 - Retry streams if the exit node sends back a 'misc' failure. This
13298 should result in fewer random failures. Also, after failing
13299 from resolve failed or misc, reset the num failures, so we give
13300 it a fair shake next time we try.
13301 - Clean up the rendezvous warn log msgs, and downgrade some to info.
13302 - Reduce severity on logs about dns worker spawning and culling.
13303 - When we're shutting down and we do something like try to post a
13304 server descriptor or rendezvous descriptor, don't complain that
13305 we seem to be unreachable. Of course we are, we're shutting down.
13306 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
13307 We don't use them yet, but maybe one day our DNS resolver will be
13308 able to discover them.
13309 - Make ContactInfo mandatory for authoritative directory servers.
13310 - Require server descriptors to list IPv4 addresses -- hostnames
13311 are no longer allowed. This also fixes some potential security
13312 problems with people providing hostnames as their address and then
13313 preferentially resolving them to partition users.
13314 - Change log line for unreachability to explicitly suggest /etc/hosts
13315 as the culprit. Also make it clearer what IP address and ports we're
13316 testing for reachability.
13317 - Put quotes around user-supplied strings when logging so users are
13318 more likely to realize if they add bad characters (like quotes)
13320 - Let auth dir servers start without specifying an Address config
13322 - Make unit tests (and other invocations that aren't the real Tor)
13323 run without launching listeners, creating subdirectories, and so on.
13326 Changes in version 0.1.1.5-alpha - 2005-08-08
13327 o Bugfixes included in 0.1.0.14.
13329 o Bugfixes on 0.1.0.x:
13330 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
13331 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
13332 it would silently using ignore the 6668.
13335 Changes in version 0.1.0.14 - 2005-08-08
13336 o Bugfixes on 0.1.0.x:
13337 - Fix the other half of the bug with crypto handshakes
13339 - Fix an assert trigger if you send a 'signal term' via the
13340 controller when it's listening for 'event info' messages.
13343 Changes in version 0.1.1.4-alpha - 2005-08-04
13344 o Bugfixes included in 0.1.0.13.
13347 - Improve tor_gettimeofday() granularity on windows.
13348 - Make clients regenerate their keys when their IP address changes.
13349 - Implement some more GETINFO goodness: expose helper nodes, config
13350 options, getinfo keys.
13353 Changes in version 0.1.0.13 - 2005-08-04
13354 o Bugfixes on 0.1.0.x:
13355 - Fix a critical bug in the security of our crypto handshakes.
13356 - Fix a size_t underflow in smartlist_join_strings2() that made
13357 it do bad things when you hand it an empty smartlist.
13358 - Fix Windows installer to ship Tor license (thanks to Aphex for
13359 pointing out this oversight) and put a link to the doc directory
13361 - Explicitly set no-unaligned-access for sparc: it turns out the
13362 new gcc's let you compile broken code, but that doesn't make it
13366 Changes in version 0.1.1.3-alpha - 2005-07-23
13367 o Bugfixes on 0.1.1.2-alpha:
13368 - Fix a bug in handling the controller's "post descriptor"
13370 - Fix several bugs in handling the controller's "extend circuit"
13372 - Fix a bug in handling the controller's "stream status" event.
13373 - Fix an assert failure if we have a controller listening for
13374 circuit events and we go offline.
13375 - Re-allow hidden service descriptors to publish 0 intro points.
13376 - Fix a crash when generating your hidden service descriptor if
13377 you don't have enough intro points already.
13379 o New features on 0.1.1.2-alpha:
13380 - New controller function "getinfo accounting", to ask how
13381 many bytes we've used in this time period.
13382 - Experimental support for helper nodes: a lot of the risk from
13383 a small static adversary comes because users pick new random
13384 nodes every time they rebuild a circuit. Now users will try to
13385 stick to the same small set of entry nodes if they can. Not
13386 enabled by default yet.
13388 o Bugfixes on 0.1.0.12:
13389 - If you're an auth dir server, always publish your dirport,
13390 even if you haven't yet found yourself to be reachable.
13391 - Fix a size_t underflow in smartlist_join_strings2() that made
13392 it do bad things when you hand it an empty smartlist.
13395 Changes in version 0.1.0.12 - 2005-07-18
13396 o New directory servers:
13397 - tor26 has changed IP address.
13399 o Bugfixes on 0.1.0.x:
13400 - Fix a possible double-free in tor_gzip_uncompress().
13401 - When --disable-threads is set, do not search for or link against
13402 pthreads libraries.
13403 - Don't trigger an assert if an authoritative directory server
13404 claims its dirport is 0.
13405 - Fix bug with removing Tor as an NT service: some people were
13406 getting "The service did not return an error." Thanks to Matt
13410 Changes in version 0.1.1.2-alpha - 2005-07-15
13411 o New directory servers:
13412 - tor26 has changed IP address.
13414 o Bugfixes on 0.1.0.x, crashes/leaks:
13415 - Port the servers-not-obeying-their-exit-policies fix from
13417 - Fix an fd leak in start_daemon().
13418 - On Windows, you can't always reopen a port right after you've
13419 closed it. So change retry_listeners() to only close and re-open
13420 ports that have changed.
13421 - Fix a possible double-free in tor_gzip_uncompress().
13423 o Bugfixes on 0.1.0.x, usability:
13424 - When tor_socketpair() fails in Windows, give a reasonable
13425 Windows-style errno back.
13426 - Let people type "tor --install" as well as "tor -install" when
13428 want to make it an NT service.
13429 - NT service patch from Matt Edman to improve error messages.
13430 - When the controller asks for a config option with an abbreviated
13431 name, give the full name in our response.
13432 - Correct the man page entry on TrackHostExitsExpire.
13433 - Looks like we were never delivering deflated (i.e. compressed)
13434 running-routers lists, even when asked. Oops.
13435 - When --disable-threads is set, do not search for or link against
13436 pthreads libraries.
13438 o Bugfixes on 0.1.1.x:
13439 - Fix a seg fault with autodetecting which controller version is
13443 - New hidden service descriptor format: put a version in it, and
13444 let people specify introduction/rendezvous points that aren't
13445 in "the directory" (which is subjective anyway).
13446 - Allow the DEBUG controller event to work again. Mark certain log
13447 entries as "don't tell this to controllers", so we avoid cycles.
13450 Changes in version 0.1.0.11 - 2005-06-30
13451 o Bugfixes on 0.1.0.x:
13452 - Fix major security bug: servers were disregarding their
13453 exit policies if clients behaved unexpectedly.
13454 - Make OS X init script check for missing argument, so we don't
13455 confuse users who invoke it incorrectly.
13456 - Fix a seg fault in "tor --hash-password foo".
13457 - The MAPADDRESS control command was broken.
13460 Changes in version 0.1.1.1-alpha - 2005-06-29
13462 - Make OS X init script check for missing argument, so we don't
13463 confuse users who invoke it incorrectly.
13464 - Fix a seg fault in "tor --hash-password foo".
13465 - Fix a possible way to DoS dirservers.
13466 - When we complain that your exit policy implicitly allows local or
13467 private address spaces, name them explicitly so operators can
13469 - Make the log message less scary when all the dirservers are
13470 temporarily unreachable.
13471 - We were printing the number of idle dns workers incorrectly when
13475 - Revised controller protocol (version 1) that uses ascii rather
13476 than binary. Add supporting libraries in python and java so you
13477 can use the controller from your applications without caring how
13478 our protocol works.
13479 - Spiffy new support for crypto hardware accelerators. Can somebody
13483 Changes in version 0.0.9.10 - 2005-06-16
13484 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
13485 - Refuse relay cells that claim to have a length larger than the
13486 maximum allowed. This prevents a potential attack that could read
13487 arbitrary memory (e.g. keys) from an exit server's process
13491 Changes in version 0.1.0.10 - 2005-06-14
13492 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
13493 libevent before 1.1a.
13496 Changes in version 0.1.0.9-rc - 2005-06-09
13498 - Reset buf->highwater every time buf_shrink() is called, not just on
13499 a successful shrink. This was causing significant memory bloat.
13500 - Fix buffer overflow when checking hashed passwords.
13501 - Security fix: if seeding the RNG on Win32 fails, quit.
13502 - Allow seeding the RNG on Win32 even when you're not running as
13504 - Disable threading on Solaris too. Something is wonky with it,
13505 cpuworkers, and reentrant libs.
13506 - Reenable the part of the code that tries to flush as soon as an
13507 OR outbuf has a full TLS record available. Perhaps this will make
13508 OR outbufs not grow as huge except in rare cases, thus saving lots
13509 of CPU time plus memory.
13510 - Reject malformed .onion addresses rather then passing them on as
13511 normal web requests.
13512 - Adapt patch from Adam Langley: fix possible memory leak in
13513 tor_lookup_hostname().
13514 - Initialize libevent later in the startup process, so the logs are
13515 already established by the time we start logging libevent warns.
13516 - Use correct errno on win32 if libevent fails.
13517 - Check and warn about known-bad/slow libevent versions.
13518 - Pay more attention to the ClientOnly config option.
13519 - Have torctl.in/tor.sh.in check for location of su binary (needed
13521 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
13522 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
13523 HttpProxyAuthenticator
13524 - Stop warning about sigpipes in the logs. We're going to
13525 pretend that getting these occassionally is normal and fine.
13526 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
13528 installer screens; and don't put stuff into StartupItems unless
13529 the user asks you to.
13530 - Require servers that use the default dirservers to have public IP
13531 addresses. We have too many servers that are configured with private
13532 IPs and their admins never notice the log entries complaining that
13533 their descriptors are being rejected.
13534 - Add OSX uninstall instructions. An actual uninstall script will
13538 Changes in version 0.1.0.8-rc - 2005-05-23
13540 - It turns out that kqueue on OS X 10.3.9 was causing kernel
13541 panics. Disable kqueue on all OS X Tors.
13542 - Fix RPM: remove duplicate line accidentally added to the rpm
13544 - Disable threads on openbsd too, since its gethostaddr is not
13546 - Tolerate libevent 0.8 since it still works, even though it's
13548 - Enable building on Red Hat 9.0 again.
13549 - Allow the middle hop of the testing circuit to be running any
13550 version, now that most of them have the bugfix to let them connect
13551 to unknown servers. This will allow reachability testing to work
13552 even when 0.0.9.7-0.0.9.9 become obsolete.
13553 - Handle relay cells with rh.length too large. This prevents
13554 a potential attack that could read arbitrary memory (maybe even
13555 keys) from the exit server's process.
13556 - We screwed up the dirport reachability testing when we don't yet
13557 have a cached version of the directory. Hopefully now fixed.
13558 - Clean up router_load_single_router() (used by the controller),
13559 so it doesn't seg fault on error.
13560 - Fix a minor memory leak when somebody establishes an introduction
13561 point at your Tor server.
13562 - If a socks connection ends because read fails, don't warn that
13563 you're not sending a socks reply back.
13566 - Add HttpProxyAuthenticator config option too, that works like
13567 the HttpsProxyAuthenticator config option.
13568 - Encode hashed controller passwords in hex instead of base64,
13569 to make it easier to write controllers.
13572 Changes in version 0.1.0.7-rc - 2005-05-17
13574 - Fix a bug in the OS X package installer that prevented it from
13575 installing on Tiger.
13576 - Fix a script bug in the OS X package installer that made it
13577 complain during installation.
13578 - Find libevent even if it's hiding in /usr/local/ and your
13579 CFLAGS and LDFLAGS don't tell you to look there.
13580 - Be able to link with libevent as a shared library (the default
13581 after 1.0d), even if it's hiding in /usr/local/lib and even
13582 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
13583 assuming you're running gcc. Otherwise fail and give a useful
13585 - Fix a bug in the RPM packager: set home directory for _tor to
13586 something more reasonable when first installing.
13587 - Free a minor amount of memory that is still reachable on exit.
13590 Changes in version 0.1.0.6-rc - 2005-05-14
13592 - Implement --disable-threads configure option. Disable threads on
13593 netbsd by default, because it appears to have no reentrant resolver
13595 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
13596 release (1.1) detects and disables kqueue if it's broken.
13597 - Append default exit policy before checking for implicit internal
13598 addresses. Now we don't log a bunch of complaints on startup
13599 when using the default exit policy.
13600 - Some people were putting "Address " in their torrc, and they had
13601 a buggy resolver that resolved " " to 0.0.0.0. Oops.
13602 - If DataDir is ~/.tor, and that expands to /.tor, then default to
13603 LOCALSTATEDIR/tor instead.
13604 - Fix fragmented-message bug in TorControl.py.
13605 - Resolve a minor bug which would prevent unreachable dirports
13606 from getting suppressed in the published descriptor.
13607 - When the controller gave us a new descriptor, we weren't resolving
13608 it immediately, so Tor would think its address was 0.0.0.0 until
13609 we fetched a new directory.
13610 - Fix an uppercase/lowercase case error in suppressing a bogus
13611 libevent warning on some Linuxes.
13614 - Begin scrubbing sensitive strings from logs by default. Turn off
13615 the config option SafeLogging if you need to do debugging.
13616 - Switch to a new buffer management algorithm, which tries to avoid
13617 reallocing and copying quite as much. In first tests it looks like
13618 it uses *more* memory on average, but less cpu.
13619 - First cut at support for "create-fast" cells. Clients can use
13620 these when extending to their first hop, since the TLS already
13621 provides forward secrecy and authentication. Not enabled on
13623 - When dirservers refuse a router descriptor, we now log its
13624 contactinfo, platform, and the poster's IP address.
13625 - Call tor_free_all instead of connections_free_all after forking, to
13626 save memory on systems that need to fork.
13627 - Whine at you if you're a server and you don't set your contactinfo.
13628 - Implement --verify-config command-line option to check if your torrc
13629 is valid without actually launching Tor.
13630 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
13631 rather than just rejecting it.
13634 Changes in version 0.1.0.5-rc - 2005-04-27
13636 - Stop trying to print a null pointer if an OR conn fails because
13637 we didn't like its cert.
13639 - Switch our internal buffers implementation to use a ring buffer,
13640 to hopefully improve performance for fast servers a lot.
13641 - Add HttpsProxyAuthenticator support (basic auth only), based
13642 on patch from Adam Langley.
13643 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
13644 the fast servers that have been joining lately.
13645 - Give hidden service accesses extra time on the first attempt,
13646 since 60 seconds is often only barely enough. This might improve
13648 - Improve performance for dirservers: stop re-parsing the whole
13649 directory every time you regenerate it.
13650 - Add more debugging info to help us find the weird dns freebsd
13651 pthreads bug; cleaner debug messages to help track future issues.
13654 Changes in version 0.0.9.9 - 2005-04-23
13655 o Bugfixes on 0.0.9.x:
13656 - If unofficial Tor clients connect and send weird TLS certs, our
13657 Tor server triggers an assert. This release contains a minimal
13658 backport from the broader fix that we put into 0.1.0.4-rc.
13661 Changes in version 0.1.0.4-rc - 2005-04-23
13663 - If unofficial Tor clients connect and send weird TLS certs, our
13664 Tor server triggers an assert. Stop asserting, and start handling
13665 TLS errors better in other situations too.
13666 - When the controller asks us to tell it about all the debug-level
13667 logs, it turns out we were generating debug-level logs while
13668 telling it about them, which turns into a bad loop. Now keep
13669 track of whether you're sending a debug log to the controller,
13670 and don't log when you are.
13671 - Fix the "postdescriptor" feature of the controller interface: on
13672 non-complete success, only say "done" once.
13674 - Clients are now willing to load balance over up to 2mB, not 1mB,
13675 of advertised bandwidth capacity.
13676 - Add a NoPublish config option, so you can be a server (e.g. for
13677 testing running Tor servers in other Tor networks) without
13678 publishing your descriptor to the primary dirservers.
13681 Changes in version 0.1.0.3-rc - 2005-04-08
13682 o Improvements on 0.1.0.2-rc:
13683 - Client now retries when streams end early for 'hibernating' or
13684 'resource limit' reasons, rather than failing them.
13685 - More automated handling for dirserver operators:
13686 - Automatically approve nodes running 0.1.0.2-rc or later,
13687 now that the the reachability detection stuff is working.
13688 - Now we allow two unverified servers with the same nickname
13689 but different keys. But if a nickname is verified, only that
13690 nickname+key are allowed.
13691 - If you're an authdirserver connecting to an address:port,
13692 and it's not the OR you were expecting, forget about that
13693 descriptor. If he *was* the one you were expecting, then forget
13694 about all other descriptors for that address:port.
13695 - Allow servers to publish descriptors from 12 hours in the future.
13696 Corollary: only whine about clock skew from the dirserver if
13697 he's a trusted dirserver (since now even verified servers could
13698 have quite wrong clocks).
13699 - Adjust maximum skew and age for rendezvous descriptors: let skew
13700 be 48 hours rather than 90 minutes.
13701 - Efficiency improvements:
13702 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
13703 it much faster to look up a circuit for each relay cell.
13704 - Remove most calls to assert_all_pending_dns_resolves_ok(),
13705 since they're eating our cpu on exit nodes.
13706 - Stop wasting time doing a case insensitive comparison for every
13707 dns name every time we do any lookup. Canonicalize the names to
13708 lowercase and be done with it.
13709 - Start sending 'truncated' cells back rather than destroy cells,
13710 if the circuit closes in front of you. This means we won't have
13711 to abandon partially built circuits.
13712 - Only warn once per nickname from add_nickname_list_to_smartlist
13713 per failure, so an entrynode or exitnode choice that's down won't
13715 - Put a note in the torrc about abuse potential with the default
13717 - Revise control spec and implementation to allow all log messages to
13718 be sent to controller with their severities intact (suggested by
13719 Matt Edman). Update TorControl to handle new log event types.
13720 - Provide better explanation messages when controller's POSTDESCRIPTOR
13722 - Stop putting nodename in the Platform string in server descriptors.
13723 It doesn't actually help, and it is confusing/upsetting some people.
13725 o Bugfixes on 0.1.0.2-rc:
13726 - We were printing the host mask wrong in exit policies in server
13727 descriptors. This isn't a critical bug though, since we were still
13728 obeying the exit policy internally.
13729 - Fix Tor when compiled with libevent but without pthreads: move
13730 connection_unregister() from _connection_free() to
13732 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
13733 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
13734 when we look through the connection array, we'll find any of the
13735 cpu/dnsworkers. This is no good.
13737 o Bugfixes on 0.0.9.8:
13738 - Fix possible bug on threading platforms (e.g. win32) which was
13739 leaking a file descriptor whenever a cpuworker or dnsworker died.
13740 - When using preferred entry or exit nodes, ignore whether the
13741 circuit wants uptime or capacity. They asked for the nodes, they
13743 - chdir() to your datadirectory at the *end* of the daemonize process,
13744 not the beginning. This was a problem because the first time you
13745 run tor, if your datadir isn't there, and you have runasdaemon set
13746 to 1, it will try to chdir to it before it tries to create it. Oops.
13747 - Handle changed router status correctly when dirserver reloads
13748 fingerprint file. We used to be dropping all unverified descriptors
13749 right then. The bug was hidden because we would immediately
13750 fetch a directory from another dirserver, which would include the
13751 descriptors we just dropped.
13752 - When we're connecting to an OR and he's got a different nickname/key
13753 than we were expecting, only complain loudly if we're an OP or a
13754 dirserver. Complaining loudly to the OR admins just confuses them.
13755 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
13756 artificially capped at 500kB.
13759 Changes in version 0.0.9.8 - 2005-04-07
13760 o Bugfixes on 0.0.9.x:
13761 - We have a bug that I haven't found yet. Sometimes, very rarely,
13762 cpuworkers get stuck in the 'busy' state, even though the cpuworker
13763 thinks of itself as idle. This meant that no new circuits ever got
13764 established. Here's a workaround to kill any cpuworker that's been
13765 busy for more than 100 seconds.
13768 Changes in version 0.1.0.2-rc - 2005-04-01
13769 o Bugfixes on 0.1.0.1-rc:
13770 - Fixes on reachability detection:
13771 - Don't check for reachability while hibernating.
13772 - If ORPort is reachable but DirPort isn't, still publish the
13773 descriptor, but zero out DirPort until it's found reachable.
13774 - When building testing circs for ORPort testing, use only
13775 high-bandwidth nodes, so fewer circuits fail.
13776 - Complain about unreachable ORPort separately from unreachable
13777 DirPort, so the user knows what's going on.
13778 - Make sure we only conclude ORPort reachability if we didn't
13779 initiate the conn. Otherwise we could falsely conclude that
13780 we're reachable just because we connected to the guy earlier
13781 and he used that same pipe to extend to us.
13782 - Authdirservers shouldn't do ORPort reachability detection,
13783 since they're in clique mode, so it will be rare to find a
13784 server not already connected to them.
13785 - When building testing circuits, always pick middle hops running
13786 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
13787 bug. (This is a kludge; it will go away when 0.0.9.x becomes
13789 - When we decide we're reachable, actually publish our descriptor
13791 - Fix bug in redirectstream in the controller.
13792 - Fix the state descriptor strings so logs don't claim edge streams
13793 are in a different state than they actually are.
13794 - Use recent libevent features when possible (this only really affects
13795 win32 and osx right now, because the new libevent with these
13796 features hasn't been released yet). Add code to suppress spurious
13798 - Prevent possible segfault in connection_close_unattached_ap().
13799 - Fix newlines on torrc in win32.
13800 - Improve error msgs when tor-resolve fails.
13802 o Improvements on 0.0.9.x:
13803 - New experimental script tor/contrib/ExerciseServer.py (needs more
13804 work) that uses the controller interface to build circuits and
13805 fetch pages over them. This will help us bootstrap servers that
13806 have lots of capacity but haven't noticed it yet.
13807 - New experimental script tor/contrib/PathDemo.py (needs more work)
13808 that uses the controller interface to let you choose whole paths
13810 "<hostname>.<path,separated by dots>.<length of path>.path"
13811 - When we've connected to an OR and handshaked but didn't like
13812 the result, we were closing the conn without sending destroy
13813 cells back for pending circuits. Now send those destroys.
13816 Changes in version 0.0.9.7 - 2005-04-01
13817 o Bugfixes on 0.0.9.x:
13818 - Fix another race crash bug (thanks to Glenn Fink for reporting).
13819 - Compare identity to identity, not to nickname, when extending to
13820 a router not already in the directory. This was preventing us from
13821 extending to unknown routers. Oops.
13822 - Make sure to create OS X Tor user in <500 range, so we aren't
13823 creating actual system users.
13824 - Note where connection-that-hasn't-sent-end was marked, and fix
13825 a few really loud instances of this harmless bug (it's fixed more
13829 Changes in version 0.1.0.1-rc - 2005-03-28
13831 - Add reachability testing. Your Tor server will automatically try
13832 to see if its ORPort and DirPort are reachable from the outside,
13833 and it won't upload its descriptor until it decides they are.
13834 - Handle unavailable hidden services better. Handle slow or busy
13835 hidden services better.
13836 - Add support for CONNECTing through https proxies, with "HttpsProxy"
13838 - New exit policy: accept most low-numbered ports, rather than
13839 rejecting most low-numbered ports.
13840 - More Tor controller support (still experimental). See
13841 http://tor.eff.org/doc/control-spec.txt for all the new features,
13842 including signals to emulate unix signals from any platform;
13843 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
13844 closestream; closecircuit; etc.
13845 - Make nt services work and start on startup on win32 (based on
13846 patch by Matt Edman).
13847 - Add a new AddressMap config directive to rewrite incoming socks
13848 addresses. This lets you, for example, declare an implicit
13849 required exit node for certain sites.
13850 - Add a new TrackHostExits config directive to trigger addressmaps
13851 for certain incoming socks addresses -- for sites that break when
13852 your exit keeps changing (based on patch by Mike Perry).
13853 - Redo the client-side dns cache so it's just an addressmap too.
13854 - Notice when our IP changes, and reset stats/uptime/reachability.
13855 - When an application is using socks5, give him the whole variety of
13856 potential socks5 responses (connect refused, host unreachable, etc),
13857 rather than just "success" or "failure".
13858 - A more sane version numbering system. See
13859 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
13860 - New contributed script "exitlist": a simple python script to
13861 parse directories and find Tor nodes that exit to listed
13863 - New contributed script "privoxy-tor-toggle" to toggle whether
13864 Privoxy uses Tor. Seems to be configured for Debian by default.
13865 - Report HTTP reasons to client when getting a response from directory
13866 servers -- so you can actually know what went wrong.
13867 - New config option MaxAdvertisedBandwidth which lets you advertise
13868 a low bandwidthrate (to not attract as many circuits) while still
13869 allowing a higher bandwidthrate in reality.
13871 o Robustness/stability fixes:
13872 - Make Tor use Niels Provos's libevent instead of its current
13873 poll-but-sometimes-select mess. This will let us use faster async
13874 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
13876 - pthread support now too. This was forced because when we forked,
13877 we ended up wasting a lot of duplicate ram over time. Also switch
13878 to foo_r versions of some library calls to allow reentry and
13880 - Better handling for heterogeneous / unreliable nodes:
13881 - Annotate circuits w/ whether they aim to contain high uptime nodes
13882 and/or high capacity nodes. When building circuits, choose
13884 - This means that every single node in an intro rend circuit,
13885 not just the last one, will have a minimum uptime.
13886 - New config option LongLivedPorts to indicate application streams
13887 that will want high uptime circuits.
13888 - Servers reset uptime when a dir fetch entirely fails. This
13889 hopefully reflects stability of the server's network connectivity.
13890 - If somebody starts his tor server in Jan 2004 and then fixes his
13891 clock, don't make his published uptime be a year.
13892 - Reset published uptime when you wake up from hibernation.
13893 - Introduce a notion of 'internal' circs, which are chosen without
13894 regard to the exit policy of the last hop. Intro and rendezvous
13895 circs must be internal circs, to avoid leaking information. Resolve
13896 and connect streams can use internal circs if they want.
13897 - New circuit pooling algorithm: make sure to have enough circs around
13898 to satisfy any predicted ports, and also make sure to have 2 internal
13899 circs around if we've required internal circs lately (and with high
13900 uptime if we've seen that lately too).
13901 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
13902 which describes how often we retry making new circuits if current
13903 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
13904 how long we're willing to make use of an already-dirty circuit.
13905 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
13906 circ as necessary, if there are any completed ones lying around
13907 when we try to launch one.
13908 - Make hidden services try to establish a rendezvous for 30 seconds,
13909 rather than for n (where n=3) attempts to build a circuit.
13910 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
13911 "ShutdownWaitLength".
13912 - Try to be more zealous about calling connection_edge_end when
13913 things go bad with edge conns in connection.c.
13914 - Revise tor-spec to add more/better stream end reasons.
13915 - Revise all calls to connection_edge_end to avoid sending "misc",
13916 and to take errno into account where possible.
13919 - Fix a race condition that can trigger an assert, when we have a
13920 pending create cell and an OR connection fails right then.
13921 - Fix several double-mark-for-close bugs, e.g. where we were finding
13922 a conn for a cell even if that conn is already marked for close.
13923 - Make sequence of log messages when starting on win32 with no config
13924 file more reasonable.
13925 - When choosing an exit node for a new non-internal circ, don't take
13926 into account whether it'll be useful for any pending x.onion
13927 addresses -- it won't.
13928 - Turn addr_policy_compare from a tristate to a quadstate; this should
13929 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
13930 for google.com" problem.
13931 - Make "platform" string in descriptor more accurate for Win32 servers,
13932 so it's not just "unknown platform".
13933 - Fix an edge case in parsing config options (thanks weasel).
13934 If they say "--" on the commandline, it's not an option.
13935 - Reject odd-looking addresses at the client (e.g. addresses that
13936 contain a colon), rather than having the server drop them because
13938 - tor-resolve requests were ignoring .exit if there was a working circuit
13939 they could use instead.
13940 - REUSEADDR on normal platforms means you can rebind to the port
13941 right after somebody else has let it go. But REUSEADDR on win32
13942 means to let you bind to the port _even when somebody else
13943 already has it bound_! So, don't do that on Win32.
13944 - Change version parsing logic: a version is "obsolete" if it is not
13945 recommended and (1) there is a newer recommended version in the
13946 same series, or (2) there are no recommended versions in the same
13947 series, but there are some recommended versions in a newer series.
13948 A version is "new" if it is newer than any recommended version in
13950 - Stop most cases of hanging up on a socks connection without sending
13954 - Require BandwidthRate to be at least 20kB/s for servers.
13955 - When a dirserver causes you to give a warn, mention which dirserver
13957 - New config option DirAllowPrivateAddresses for authdirservers.
13958 Now by default they refuse router descriptors that have non-IP or
13959 private-IP addresses.
13960 - Stop publishing socksport in the directory, since it's not
13961 actually meant to be public. For compatibility, publish a 0 there
13963 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
13964 smart" value, that is low for servers and high for clients.
13965 - If our clock jumps forward by 100 seconds or more, assume something
13966 has gone wrong with our network and abandon all not-yet-used circs.
13967 - Warn when exit policy implicitly allows local addresses.
13968 - If we get an incredibly skewed timestamp from a dirserver mirror
13969 that isn't a verified OR, don't warn -- it's probably him that's
13971 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
13972 cookies to disk and doesn't log each web request to disk. (Thanks
13973 to Brett Carrington for pointing this out.)
13974 - When a client asks us for a dir mirror and we don't have one,
13975 launch an attempt to get a fresh one.
13976 - If we're hibernating and we get a SIGINT, exit immediately.
13977 - Add --with-dmalloc ./configure option, to track memory leaks.
13978 - And try to free all memory on closing, so we can detect what
13980 - Cache local dns resolves correctly even when they're .exit
13982 - Give a better warning when some other server advertises an
13983 ORPort that is actually an apache running ssl.
13984 - Add "opt hibernating 1" to server descriptor to make it clearer
13985 whether the server is hibernating.
13988 Changes in version 0.0.9.6 - 2005-03-24
13989 o Bugfixes on 0.0.9.x (crashes and asserts):
13990 - Add new end stream reasons to maintainance branch. Fix bug where
13991 reason (8) could trigger an assert. Prevent bug from recurring.
13992 - Apparently win32 stat wants paths to not end with a slash.
13993 - Fix assert triggers in assert_cpath_layer_ok(), where we were
13994 blowing away the circuit that conn->cpath_layer points to, then
13995 checking to see if the circ is well-formed. Backport check to make
13996 sure we dont use the cpath on a closed connection.
13997 - Prevent circuit_resume_edge_reading_helper() from trying to package
13998 inbufs for marked-for-close streams.
13999 - Don't crash on hup if your options->address has become unresolvable.
14000 - Some systems (like OS X) sometimes accept() a connection and tell
14001 you the remote host is 0.0.0.0:0. If this happens, due to some
14002 other mis-features, we get confused; so refuse the conn for now.
14004 o Bugfixes on 0.0.9.x (other):
14005 - Fix harmless but scary "Unrecognized content encoding" warn message.
14006 - Add new stream error reason: TORPROTOCOL reason means "you are not
14007 speaking a version of Tor I understand; say bye-bye to your stream."
14008 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
14009 into the future, now that we are more tolerant of skew. This
14010 resolves a bug where a Tor server would refuse to cache a directory
14011 because all the directories it gets are too far in the future;
14012 yet the Tor server never logs any complaints about clock skew.
14013 - Mac packaging magic: make man pages useable, and do not overwrite
14014 existing torrc files.
14015 - Make OS X log happily to /var/log/tor/tor.log
14018 Changes in version 0.0.9.5 - 2005-02-22
14019 o Bugfixes on 0.0.9.x:
14020 - Fix an assert race at exit nodes when resolve requests fail.
14021 - Stop picking unverified dir mirrors--it only leads to misery.
14022 - Patch from Matt Edman to make NT services work better. Service
14023 support is still not compiled into the executable by default.
14024 - Patch from Dmitri Bely so the Tor service runs better under
14025 the win32 SYSTEM account.
14026 - Make tor-resolve actually work (?) on Win32.
14027 - Fix a sign bug when getrlimit claims to have 4+ billion
14028 file descriptors available.
14029 - Stop refusing to start when bandwidthburst == bandwidthrate.
14030 - When create cells have been on the onion queue more than five
14031 seconds, just send back a destroy and take them off the list.
14034 Changes in version 0.0.9.4 - 2005-02-03
14035 o Bugfixes on 0.0.9:
14036 - Fix an assert bug that took down most of our servers: when
14037 a server claims to have 1 GB of bandwidthburst, don't
14039 - Don't crash as badly if we have spawned the max allowed number
14040 of dnsworkers, or we're out of file descriptors.
14041 - Block more file-sharing ports in the default exit policy.
14042 - MaxConn is now automatically set to the hard limit of max
14043 file descriptors we're allowed (ulimit -n), minus a few for
14045 - Give a clearer message when servers need to raise their
14046 ulimit -n when they start running out of file descriptors.
14047 - SGI Compatibility patches from Jan Schaumann.
14048 - Tolerate a corrupt cached directory better.
14049 - When a dirserver hasn't approved your server, list which one.
14050 - Go into soft hibernation after 95% of the bandwidth is used,
14051 not 99%. This is especially important for daily hibernators who
14052 have a small accounting max. Hopefully it will result in fewer
14053 cut connections when the hard hibernation starts.
14054 - Load-balance better when using servers that claim more than
14055 800kB/s of capacity.
14056 - Make NT services work (experimental, only used if compiled in).
14059 Changes in version 0.0.9.3 - 2005-01-21
14060 o Bugfixes on 0.0.9:
14061 - Backport the cpu use fixes from main branch, so busy servers won't
14062 need as much processor time.
14063 - Work better when we go offline and then come back, or when we
14064 run Tor at boot before the network is up. We do this by
14065 optimistically trying to fetch a new directory whenever an
14066 application request comes in and we think we're offline -- the
14067 human is hopefully a good measure of when the network is back.
14068 - Backport some minimal hidserv bugfixes: keep rend circuits open as
14069 long as you keep using them; actually publish hidserv descriptors
14070 shortly after they change, rather than waiting 20-40 minutes.
14071 - Enable Mac startup script by default.
14072 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
14073 - When you update AllowUnverifiedNodes or FirewallPorts via the
14074 controller's setconf feature, we were always appending, never
14076 - When you update HiddenServiceDir via setconf, it was screwing up
14077 the order of reading the lines, making it fail.
14078 - Do not rewrite a cached directory back to the cache; otherwise we
14079 will think it is recent and not fetch a newer one on startup.
14080 - Workaround for webservers that lie about Content-Encoding: Tor
14081 now tries to autodetect compressed directories and compression
14082 itself. This lets us Proxypass dir fetches through apache.
14085 Changes in version 0.0.9.2 - 2005-01-04
14086 o Bugfixes on 0.0.9 (crashes and asserts):
14087 - Fix an assert on startup when the disk is full and you're logging
14089 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
14090 style address, then we'd crash.
14091 - Fix an assert trigger when the running-routers string we get from
14092 a dirserver is broken.
14093 - Make worker threads start and run on win32. Now win32 servers
14095 - Bandaid (not actually fix, but now it doesn't crash) an assert
14096 where the dns worker dies mysteriously and the main Tor process
14097 doesn't remember anything about the address it was resolving.
14099 o Bugfixes on 0.0.9 (Win32):
14100 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
14101 name out of the warning/assert messages.
14102 - Fix a superficial "unhandled error on read" bug on win32.
14103 - The win32 installer no longer requires a click-through for our
14104 license, since our Free Software license grants rights but does not
14106 - Win32: When connecting to a dirserver fails, try another one
14107 immediately. (This was already working for non-win32 Tors.)
14108 - Stop trying to parse $HOME on win32 when hunting for default
14110 - Make tor-resolve.c work on win32 by calling network_init().
14112 o Bugfixes on 0.0.9 (other):
14113 - Make 0.0.9.x build on Solaris again.
14114 - Due to a fencepost error, we were blowing away the \n when reporting
14115 confvalue items in the controller. So asking for multiple config
14116 values at once couldn't work.
14117 - When listing circuits that are pending on an opening OR connection,
14118 if we're an OR we were listing circuits that *end* at us as
14119 being pending on every listener, dns/cpu worker, etc. Stop that.
14120 - Dirservers were failing to create 'running-routers' or 'directory'
14121 strings if we had more than some threshold of routers. Fix them so
14122 they can handle any number of routers.
14123 - Fix a superficial "Duplicate mark for close" bug.
14124 - Stop checking for clock skew for OR connections, even for servers.
14125 - Fix a fencepost error that was chopping off the last letter of any
14126 nickname that is the maximum allowed nickname length.
14127 - Update URLs in log messages so they point to the new website.
14128 - Fix a potential problem in mangling server private keys while
14129 writing to disk (not triggered yet, as far as we know).
14130 - Include the licenses for other free software we include in Tor,
14131 now that we're shipping binary distributions more regularly.
14134 Changes in version 0.0.9.1 - 2004-12-15
14135 o Bugfixes on 0.0.9:
14136 - Make hibernation actually work.
14137 - Make HashedControlPassword config option work.
14138 - When we're reporting event circuit status to a controller,
14139 don't use the stream status code.
14142 Changes in version 0.0.9 - 2004-12-12
14144 - Clean up manpage and torrc.sample file.
14145 - Clean up severities and text of log warnings.
14147 - Make servers trigger an assert when they enter hibernation.
14150 Changes in version 0.0.9rc7 - 2004-12-08
14151 o Bugfixes on 0.0.9rc:
14152 - Fix a stack-trashing crash when an exit node begins hibernating.
14153 - Avoid looking at unallocated memory while considering which
14154 ports we need to build circuits to cover.
14155 - Stop a sigpipe: when an 'end' cell races with eof from the app,
14156 we shouldn't hold-open-until-flush if the eof arrived first.
14157 - Fix a bug with init_cookie_authentication() in the controller.
14158 - When recommending new-format log lines, if the upper bound is
14159 LOG_ERR, leave it implicit.
14161 o Bugfixes on 0.0.8.1:
14162 - Fix a whole slew of memory leaks.
14163 - Fix isspace() and friends so they still make Solaris happy
14164 but also so they don't trigger asserts on win32.
14165 - Fix parse_iso_time on platforms without strptime (eg win32).
14166 - win32: tolerate extra "readable" events better.
14167 - win32: when being multithreaded, leave parent fdarray open.
14168 - Make unit tests work on win32.
14171 Changes in version 0.0.9rc6 - 2004-12-06
14172 o Bugfixes on 0.0.9pre:
14173 - Clean up some more integer underflow opportunities (not exploitable
14175 - While hibernating, hup should not regrow our listeners.
14176 - Send an end to the streams we close when we hibernate, rather
14177 than just chopping them off.
14178 - React to eof immediately on non-open edge connections.
14180 o Bugfixes on 0.0.8.1:
14181 - Calculate timeout for waiting for a connected cell from the time
14182 we sent the begin cell, not from the time the stream started. If
14183 it took a long time to establish the circuit, we would time out
14184 right after sending the begin cell.
14185 - Fix router_compare_addr_to_addr_policy: it was not treating a port
14186 of * as always matching, so we were picking reject *:* nodes as
14187 exit nodes too. Oops.
14190 - New circuit building strategy: keep a list of ports that we've
14191 used in the past 6 hours, and always try to have 2 circuits open
14192 or on the way that will handle each such port. Seed us with port
14193 80 so web users won't complain that Tor is "slow to start up".
14194 - Make kill -USR1 dump more useful stats about circuits.
14195 - When warning about retrying or giving up, print the address, so
14196 the user knows which one it's talking about.
14197 - If you haven't used a clean circuit in an hour, throw it away,
14198 just to be on the safe side. (This means after 6 hours a totally
14199 unused Tor client will have no circuits open.)
14202 Changes in version 0.0.9rc5 - 2004-12-01
14203 o Bugfixes on 0.0.8.1:
14204 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
14205 - Let resolve conns retry/expire also, rather than sticking around
14207 - If we are using select, make sure we stay within FD_SETSIZE.
14209 o Bugfixes on 0.0.9pre:
14210 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
14211 but doesn't seem to be currently; thanks to Ilja van Sprundel for
14213 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
14214 instead. Impose minima and maxima for all *Period options; impose
14215 even tighter maxima for fetching if we are a caching dirserver.
14216 Clip rather than rejecting.
14217 - Fetch cached running-routers from servers that serve it (that is,
14218 authdirservers and servers running 0.0.9rc5-cvs or later.)
14221 - Accept *:706 (silc) in default exit policy.
14222 - Implement new versioning format for post 0.1.
14223 - Support "foo.nickname.exit" addresses, to let Alice request the
14224 address "foo" as viewed by exit node "nickname". Based on a patch
14226 - Make tor --version --version dump the cvs Id of every file.
14229 Changes in version 0.0.9rc4 - 2004-11-28
14230 o Bugfixes on 0.0.8.1:
14231 - Make windows sockets actually non-blocking (oops), and handle
14232 win32 socket errors better.
14234 o Bugfixes on 0.0.9rc1:
14235 - Actually catch the -USR2 signal.
14238 Changes in version 0.0.9rc3 - 2004-11-25
14239 o Bugfixes on 0.0.8.1:
14240 - Flush the log file descriptor after we print "Tor opening log file",
14241 so we don't see those messages days later.
14243 o Bugfixes on 0.0.9rc1:
14244 - Make tor-resolve work again.
14245 - Avoid infinite loop in tor-resolve if tor hangs up on it.
14246 - Fix an assert trigger for clients/servers handling resolves.
14249 Changes in version 0.0.9rc2 - 2004-11-24
14250 o Bugfixes on 0.0.9rc1:
14251 - I broke socks5 support while fixing the eof bug.
14252 - Allow unitless bandwidths and intervals; they default to bytes
14254 - New servers don't start out hibernating; they are active until
14255 they run out of bytes, so they have a better estimate of how
14256 long it takes, and so their operators can know they're working.
14259 Changes in version 0.0.9rc1 - 2004-11-23
14260 o Bugfixes on 0.0.8.1:
14261 - Finally fix a bug that's been plaguing us for a year:
14262 With high load, circuit package window was reaching 0. Whenever
14263 we got a circuit-level sendme, we were reading a lot on each
14264 socket, but only writing out a bit. So we would eventually reach
14265 eof. This would be noticed and acted on even when there were still
14266 bytes sitting in the inbuf.
14267 - When poll() is interrupted, we shouldn't believe the revents values.
14269 o Bugfixes on 0.0.9pre6:
14270 - Fix hibernate bug that caused pre6 to be broken.
14271 - Don't keep rephist info for routers that haven't had activity for
14272 24 hours. (This matters now that clients have keys, since we track
14274 - Never call close_temp_logs while validating log options.
14275 - Fix backslash-escaping on tor.sh.in and torctl.in.
14278 - Implement weekly/monthly/daily accounting: now you specify your
14279 hibernation properties by
14280 AccountingMax N bytes|KB|MB|GB|TB
14281 AccountingStart day|week|month [day] HH:MM
14282 Defaults to "month 1 0:00".
14283 - Let bandwidth and interval config options be specified as 5 bytes,
14284 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
14285 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
14286 get back to normal.)
14287 - If your requested entry or exit node has advertised bandwidth 0,
14289 - Be more greedy about filling up relay cells -- we try reading again
14290 once we've processed the stuff we read, in case enough has arrived
14291 to fill the last cell completely.
14292 - Apply NT service patch from Osamu Fujino. Still needs more work.
14295 Changes in version 0.0.9pre6 - 2004-11-15
14296 o Bugfixes on 0.0.8.1:
14297 - Fix assert failure on malformed socks4a requests.
14298 - Use identity comparison, not nickname comparison, to choose which
14299 half of circuit-ID-space each side gets to use. This is needed
14300 because sometimes we think of a router as a nickname, and sometimes
14301 as a hex ID, and we can't predict what the other side will do.
14302 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
14303 write() call will fail and we handle it there.
14304 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
14305 and smartlist_len, which are two major profiling offenders.
14307 o Bugfixes on 0.0.9pre5:
14308 - Fix a bug in read_all that was corrupting config files on windows.
14309 - When we're raising the max number of open file descriptors to
14310 'unlimited', don't log that we just raised it to '-1'.
14311 - Include event code with events, as required by control-spec.txt.
14312 - Don't give a fingerprint when clients do --list-fingerprint:
14313 it's misleading, because it will never be the same again.
14314 - Stop using strlcpy in tor_strndup, since it was slowing us
14316 - Remove warn on startup about missing cached-directory file.
14317 - Make kill -USR1 work again.
14318 - Hibernate if we start tor during the "wait for wakeup-time" phase
14319 of an accounting interval. Log our hibernation plans better.
14320 - Authoritative dirservers now also cache their directory, so they
14321 have it on start-up.
14324 - Fetch running-routers; cache running-routers; compress
14325 running-routers; serve compressed running-routers.z
14326 - Add NSI installer script contributed by J Doe.
14327 - Commit VC6 and VC7 workspace/project files.
14328 - Commit a tor.spec for making RPM files, with help from jbash.
14329 - Add contrib/torctl.in contributed by Glenn Fink.
14330 - Implement the control-spec's SAVECONF command, to write your
14331 configuration to torrc.
14332 - Get cookie authentication for the controller closer to working.
14333 - Include control-spec.txt in the tarball.
14334 - When set_conf changes our server descriptor, upload a new copy.
14335 But don't upload it too often if there are frequent changes.
14336 - Document authentication config in man page, and document signals
14338 - Clean up confusing parts of man page and torrc.sample.
14339 - Make expand_filename handle ~ and ~username.
14340 - Use autoconf to enable largefile support where necessary. Use
14341 ftello where available, since ftell can fail at 2GB.
14342 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
14343 log more informatively.
14344 - Give a slightly more useful output for "tor -h".
14345 - Refuse application socks connections to port 0.
14346 - Check clock skew for verified servers, but allow unverified
14347 servers and clients to have any clock skew.
14348 - Break DirFetchPostPeriod into:
14349 - DirFetchPeriod for fetching full directory,
14350 - StatusFetchPeriod for fetching running-routers,
14351 - DirPostPeriod for posting server descriptor,
14352 - RendPostPeriod for posting hidden service descriptors.
14353 - Make sure the hidden service descriptors are at a random offset
14354 from each other, to hinder linkability.
14357 Changes in version 0.0.9pre5 - 2004-11-09
14358 o Bugfixes on 0.0.9pre4:
14359 - Fix a seg fault in unit tests (doesn't affect main program).
14360 - Fix an assert bug where a hidden service provider would fail if
14361 the first hop of his rendezvous circuit was down.
14362 - Hidden service operators now correctly handle version 1 style
14363 INTRODUCE1 cells (nobody generates them still, so not a critical
14365 - If do_hup fails, actually notice.
14366 - Handle more errnos from accept() without closing the listener.
14367 Some OpenBSD machines were closing their listeners because
14368 they ran out of file descriptors.
14369 - Send resolve cells to exit routers that are running a new
14370 enough version of the resolve code to work right.
14371 - Better handling of winsock includes on non-MSV win32 compilers.
14372 - Some people had wrapped their tor client/server in a script
14373 that would restart it whenever it died. This did not play well
14374 with our "shut down if your version is obsolete" code. Now people
14375 don't fetch a new directory if their local cached version is
14377 - Make our autogen.sh work on ksh as well as bash.
14380 - Hibernation: New config option "AccountingMaxKB" lets you
14381 set how many KBytes per month you want to allow your server to
14382 consume. Rather than spreading those bytes out evenly over the
14383 month, we instead hibernate for some of the month and pop up
14384 at a deterministic time, work until the bytes are consumed, then
14385 hibernate again. Config option "MonthlyAccountingStart" lets you
14386 specify which day of the month your billing cycle starts on.
14387 - Control interface: a separate program can now talk to your
14388 client/server over a socket, and get/set config options, receive
14389 notifications of circuits and streams starting/finishing/dying,
14390 bandwidth used, etc. The next step is to get some GUIs working.
14391 Let us know if you want to help out. See doc/control-spec.txt .
14392 - Ship a contrib/tor-control.py as an example script to interact
14393 with the control port.
14394 - "tor --hash-password zzyxz" will output a salted password for
14395 use in authenticating to the control interface.
14396 - New log format in config:
14397 "Log minsev[-maxsev] stdout|stderr|syslog" or
14398 "Log minsev[-maxsev] file /var/foo"
14401 - DirPolicy config option, to let people reject incoming addresses
14402 from their dirserver.
14403 - "tor --list-fingerprint" will list your identity key fingerprint
14405 - Add "pass" target for RedirectExit, to make it easier to break
14406 out of a sequence of RedirectExit rules.
14407 - Clients now generate a TLS cert too, in preparation for having
14408 them act more like real nodes.
14409 - Ship src/win32/ in the tarball, so people can use it to build.
14410 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
14412 - New "router-status" line in directory, to better bind each verified
14413 nickname to its identity key.
14414 - Deprecate unofficial config option abbreviations, and abbreviations
14415 not on the command line.
14416 - Add a pure-C tor-resolve implementation.
14417 - Use getrlimit and friends to ensure we can reach MaxConn (currently
14418 1024) file descriptors.
14420 o Code security improvements, inspired by Ilja:
14421 - Replace sprintf with snprintf. (I think they were all safe, but
14423 - Replace strcpy/strncpy with strlcpy in more places.
14424 - Avoid strcat; use snprintf or strlcat instead.
14425 - snprintf wrapper with consistent (though not C99) overflow behavior.
14428 Changes in version 0.0.9pre4 - 2004-10-17
14429 o Bugfixes on 0.0.9pre3:
14430 - If the server doesn't specify an exit policy, use the real default
14431 exit policy, not reject *:*.
14432 - Ignore fascistfirewall when uploading/downloading hidden service
14433 descriptors, since we go through Tor for those; and when using
14434 an HttpProxy, since we assume it can reach them all.
14435 - When looking for an authoritative dirserver, use only the ones
14436 configured at boot. Don't bother looking in the directory.
14437 - The rest of the fix for get_default_conf_file() on older win32.
14438 - Make 'Routerfile' config option obsolete.
14441 - New 'MyFamily nick1,...' config option for a server to
14442 specify other servers that shouldn't be used in the same circuit
14443 with it. Only believed if nick1 also specifies us.
14444 - New 'NodeFamily nick1,nick2,...' config option for a client to
14445 specify nodes that it doesn't want to use in the same circuit.
14446 - New 'Redirectexit pattern address:port' config option for a
14447 server to redirect exit connections, e.g. to a local squid.
14450 Changes in version 0.0.9pre3 - 2004-10-13
14451 o Bugfixes on 0.0.8.1:
14452 - Better torrc example lines for dirbindaddress and orbindaddress.
14453 - Improved bounds checking on parsed ints (e.g. config options and
14454 the ones we find in directories.)
14455 - Better handling of size_t vs int, so we're more robust on 64
14457 - Fix the rest of the bug where a newly started OR would appear
14458 as unverified even after we've added his fingerprint and hupped
14460 - Fix a bug from 0.0.7: when read() failed on a stream, we would
14461 close it without sending back an end. So 'connection refused'
14462 would simply be ignored and the user would get no response.
14464 o Bugfixes on 0.0.9pre2:
14465 - Serving the cached-on-disk directory to people is bad. We now
14466 provide no directory until we've fetched a fresh one.
14467 - Workaround for bug on windows where cached-directories get crlf
14469 - Make get_default_conf_file() work on older windows too.
14470 - If we write a *:* exit policy line in the descriptor, don't write
14471 any more exit policy lines.
14474 - Use only 0.0.9pre1 and later servers for resolve cells.
14475 - Make the dirservers file obsolete.
14476 - Include a dir-signing-key token in directories to tell the
14477 parsing entity which key is being used to sign.
14478 - Remove the built-in bulky default dirservers string.
14479 - New config option "Dirserver %s:%d [fingerprint]", which can be
14480 repeated as many times as needed. If no dirservers specified,
14481 default to moria1,moria2,tor26.
14482 - Make moria2 advertise a dirport of 80, so people behind firewalls
14483 will be able to get a directory.
14484 - Http proxy support
14485 - Dirservers translate requests for http://%s:%d/x to /x
14486 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
14487 be routed through this host.
14488 - Clients ask for /tor/x rather than /x for new enough dirservers.
14489 This way we can one day coexist peacefully with apache.
14490 - Clients specify a "Host: %s%d" http header, to be compatible
14491 with more proxies, and so running squid on an exit node can work.
14494 Changes in version 0.0.8.1 - 2004-10-13
14496 - Fix a seg fault that can be triggered remotely for Tor
14497 clients/servers with an open dirport.
14498 - Fix a rare assert trigger, where routerinfos for entries in
14499 our cpath would expire while we're building the path.
14500 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14501 - Fix a rare seg fault for people running hidden services on
14502 intermittent connections.
14503 - Fix a bug in parsing opt keywords with objects.
14504 - Fix a stale pointer assert bug when a stream detaches and
14506 - Fix a string format vulnerability (probably not exploitable)
14507 in reporting stats locally.
14508 - Fix an assert trigger: sometimes launching circuits can fail
14509 immediately, e.g. because too many circuits have failed recently.
14510 - Fix a compile warning on 64 bit platforms.
14513 Changes in version 0.0.9pre2 - 2004-10-03
14515 - Make fetching a cached directory work for 64-bit platforms too.
14516 - Make zlib.h a required header, not an optional header.
14519 Changes in version 0.0.9pre1 - 2004-10-01
14521 - Stop using separate defaults for no-config-file and
14522 empty-config-file. Now you have to explicitly turn off SocksPort,
14523 if you don't want it open.
14524 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14525 - Improve man page to mention more of the 0.0.8 features.
14526 - Fix a rare seg fault for people running hidden services on
14527 intermittent connections.
14528 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
14530 - Fix more dns related bugs: send back resolve_failed and end cells
14531 more reliably when the resolve fails, rather than closing the
14532 circuit and then trying to send the cell. Also attach dummy resolve
14533 connections to a circuit *before* calling dns_resolve(), to fix
14534 a bug where cached answers would never be sent in RESOLVED cells.
14535 - When we run out of disk space, or other log writing error, don't
14536 crash. Just stop logging to that log and continue.
14537 - We were starting to daemonize before we opened our logs, so if
14538 there were any problems opening logs, we would complain to stderr,
14539 which wouldn't work, and then mysteriously exit.
14540 - Fix a rare bug where sometimes a verified OR would connect to us
14541 before he'd uploaded his descriptor, which would cause us to
14542 assign conn->nickname as though he's unverified. Now we look through
14543 the fingerprint list to see if he's there.
14544 - Fix a rare assert trigger, where routerinfos for entries in
14545 our cpath would expire while we're building the path.
14548 - Clients can ask dirservers for /dir.z to get a compressed version
14549 of the directory. Only works for servers running 0.0.9, of course.
14550 - Make clients cache directories and use them to seed their router
14551 lists at startup. This means clients have a datadir again.
14552 - Configuration infrastructure support for warning on obsolete
14554 - Respond to content-encoding headers by trying to uncompress as
14556 - Reply with a deflated directory when a client asks for "dir.z".
14557 We could use allow-encodings instead, but allow-encodings isn't
14558 specified in HTTP 1.0.
14559 - Raise the max dns workers from 50 to 100.
14560 - Discourage people from setting their dirfetchpostperiod more often
14561 than once per minute.
14562 - Protect dirservers from overzealous descriptor uploading -- wait
14563 10 seconds after directory gets dirty, before regenerating.
14566 Changes in version 0.0.8 - 2004-08-25
14567 o Port it to SunOS 5.9 / Athena
14570 Changes in version 0.0.8rc2 - 2004-08-20
14571 o Make it compile on cygwin again.
14572 o When picking unverified routers, skip those with low uptime and/or
14573 low bandwidth, depending on what properties you care about.
14576 Changes in version 0.0.8rc1 - 2004-08-18
14577 o Changes from 0.0.7.3:
14579 - Fix assert triggers: if the other side returns an address 0.0.0.0,
14580 don't put it into the client dns cache.
14581 - If a begin failed due to exit policy, but we believe the IP address
14582 should have been allowed, switch that router to exitpolicy reject *:*
14583 until we get our next directory.
14585 - Clients choose nodes proportional to advertised bandwidth.
14586 - Avoid using nodes with low uptime as introduction points.
14587 - Handle servers with dynamic IP addresses: don't replace
14588 options->Address with the resolved one at startup, and
14589 detect our address right before we make a routerinfo each time.
14590 - 'FascistFirewall' option to pick dirservers and ORs on specific
14591 ports; plus 'FirewallPorts' config option to tell FascistFirewall
14592 which ports are open. (Defaults to 80,443)
14593 - Be more aggressive about trying to make circuits when the network
14594 has changed (e.g. when you unsuspend your laptop).
14595 - Check for time skew on http headers; report date in response to
14597 - If the entrynode config line has only one node, don't pick it as
14599 - Add strict{entry|exit}nodes config options. If set to 1, then
14600 we refuse to build circuits that don't include the specified entry
14602 - OutboundBindAddress config option, to bind to a specific
14603 IP address for outgoing connect()s.
14604 - End truncated log entries (e.g. directories) with "[truncated]".
14606 o Patches to 0.0.8preX:
14608 - Patches to compile and run on win32 again (maybe)?
14609 - Fix crash when looking for ~/.torrc with no $HOME set.
14610 - Fix a race bug in the unit tests.
14611 - Handle verified/unverified name collisions better when new
14612 routerinfo's arrive in a directory.
14613 - Sometimes routers were getting entered into the stats before
14614 we'd assigned their identity_digest. Oops.
14615 - Only pick and establish intro points after we've gotten a
14618 - AllowUnverifiedNodes config option to let circuits choose no-name
14619 routers in entry,middle,exit,introduction,rendezvous positions.
14620 Allow middle and rendezvous positions by default.
14621 - Add a man page for tor-resolve.
14624 Changes in version 0.0.7.3 - 2004-08-12
14625 o Stop dnsworkers from triggering an assert failure when you
14626 ask them to resolve the host "".
14629 Changes in version 0.0.8pre3 - 2004-08-09
14630 o Changes from 0.0.7.2:
14631 - Allow multiple ORs with same nickname in routerlist -- now when
14632 people give us one identity key for a nickname, then later
14633 another, we don't constantly complain until the first expires.
14634 - Remember used bandwidth (both in and out), and publish 15-minute
14635 snapshots for the past day into our descriptor.
14636 - You can now fetch $DIRURL/running-routers to get just the
14637 running-routers line, not the whole descriptor list. (But
14638 clients don't use this yet.)
14639 - When people mistakenly use Tor as an http proxy, point them
14640 at the tor-doc.html rather than the INSTALL.
14641 - Remove our mostly unused -- and broken -- hex_encode()
14642 function. Use base16_encode() instead. (Thanks to Timo Lindfors
14643 for pointing out this bug.)
14644 - Rotate onion keys every 12 hours, not every 2 hours, so we have
14645 fewer problems with people using the wrong key.
14646 - Change the default exit policy to reject the default edonkey,
14647 kazaa, gnutella ports.
14648 - Add replace_file() to util.[ch] to handle win32's rename().
14650 o Changes from 0.0.8preX:
14651 - Fix two bugs in saving onion keys to disk when rotating, so
14652 hopefully we'll get fewer people using old onion keys.
14653 - Fix an assert error that was making SocksPolicy not work.
14654 - Be willing to expire routers that have an open dirport -- it's
14655 just the authoritative dirservers we want to not forget.
14656 - Reject tor-resolve requests for .onion addresses early, so we
14657 don't build a whole rendezvous circuit and then fail.
14658 - When you're warning a server that he's unverified, don't cry
14659 wolf unpredictably.
14660 - Fix a race condition: don't try to extend onto a connection
14661 that's still handshaking.
14662 - For servers in clique mode, require the conn to be open before
14663 you'll choose it for your path.
14664 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
14665 end relay cell, etc.
14666 - Measure bandwidth capacity over the last 24 hours, not just 12
14667 - Bugfix: authoritative dirservers were making and signing a new
14668 directory for each client, rather than reusing the cached one.
14671 Changes in version 0.0.8pre2 - 2004-08-04
14672 o Changes from 0.0.7.2:
14674 - Check directory signature _before_ you decide whether you're
14675 you're running an obsolete version and should exit.
14676 - Check directory signature _before_ you parse the running-routers
14677 list to decide who's running or verified.
14678 - Bugfixes and features:
14679 - Check return value of fclose while writing to disk, so we don't
14680 end up with broken files when servers run out of disk space.
14681 - Log a warning if the user uses an unsafe socks variant, so people
14682 are more likely to learn about privoxy or socat.
14683 - Dirservers now include RFC1123-style dates in the HTTP headers,
14684 which one day we will use to better detect clock skew.
14686 o Changes from 0.0.8pre1:
14687 - Make it compile without warnings again on win32.
14688 - Log a warning if you're running an unverified server, to let you
14689 know you might want to get it verified.
14690 - Only pick a default nickname if you plan to be a server.
14693 Changes in version 0.0.8pre1 - 2004-07-23
14695 - Made our unit tests compile again on OpenBSD 3.5, and tor
14696 itself compile again on OpenBSD on a sparc64.
14697 - We were neglecting milliseconds when logging on win32, so
14698 everything appeared to happen at the beginning of each second.
14700 o Protocol changes:
14701 - 'Extend' relay cell payloads now include the digest of the
14702 intended next hop's identity key. Now we can verify that we're
14703 extending to the right router, and also extend to routers we
14704 hadn't heard of before.
14707 - Tor nodes can now act as relays (with an advertised ORPort)
14708 without being manually verified by the dirserver operators.
14709 - Uploaded descriptors of unverified routers are now accepted
14710 by the dirservers, and included in the directory.
14711 - Verified routers are listed by nickname in the running-routers
14712 list; unverified routers are listed as "$<fingerprint>".
14713 - We now use hash-of-identity-key in most places rather than
14714 nickname or addr:port, for improved security/flexibility.
14715 - To avoid Sybil attacks, paths still use only verified servers.
14716 But now we have a chance to play around with hybrid approaches.
14717 - Nodes track bandwidth usage to estimate capacity (not used yet).
14718 - ClientOnly option for nodes that never want to become servers.
14719 - Directory caching.
14720 - "AuthoritativeDir 1" option for the official dirservers.
14721 - Now other nodes (clients and servers) will cache the latest
14722 directory they've pulled down.
14723 - They can enable their DirPort to serve it to others.
14724 - Clients will pull down a directory from any node with an open
14725 DirPort, and check the signature/timestamp correctly.
14726 - Authoritative dirservers now fetch directories from other
14727 authdirservers, to stay better synced.
14728 - Running-routers list tells who's down also, along with noting
14729 if they're verified (listed by nickname) or unverified (listed
14731 - Allow dirservers to serve running-router list separately.
14732 This isn't used yet.
14733 - ORs connect-on-demand to other ORs
14734 - If you get an extend cell to an OR you're not connected to,
14735 connect, handshake, and forward the create cell.
14736 - The authoritative dirservers stay connected to everybody,
14737 and everybody stays connected to 0.0.7 servers, but otherwise
14738 clients/servers expire unused connections after 5 minutes.
14739 - When servers get a sigint, they delay 30 seconds (refusing new
14740 connections) then exit. A second sigint causes immediate exit.
14741 - File and name management:
14742 - Look for .torrc if no CONFDIR "torrc" is found.
14743 - If no datadir is defined, then choose, make, and secure ~/.tor
14745 - If torrc not found, exitpolicy reject *:*.
14746 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
14747 - If no nickname is defined, derive default from hostname.
14748 - Rename secret key files, e.g. identity.key -> secret_id_key,
14749 to discourage people from mailing their identity key to tor-ops.
14750 - Refuse to build a circuit before the directory has arrived --
14751 it won't work anyway, since you won't know the right onion keys
14753 - Try other dirservers immediately if the one you try is down. This
14754 should tolerate down dirservers better now.
14755 - Parse tor version numbers so we can do an is-newer-than check
14756 rather than an is-in-the-list check.
14757 - New socks command 'resolve', to let us shim gethostbyname()
14759 - A 'tor_resolve' script to access the socks resolve functionality.
14760 - A new socks-extensions.txt doc file to describe our
14761 interpretation and extensions to the socks protocols.
14762 - Add a ContactInfo option, which gets published in descriptor.
14763 - Publish OR uptime in descriptor (and thus in directory) too.
14764 - Write tor version at the top of each log file
14765 - New docs in the tarball:
14767 - Document that you should proxy your SSL traffic too.
14770 Changes in version 0.0.7.2 - 2004-07-07
14771 o A better fix for the 0.0.0.0 problem, that will hopefully
14772 eliminate the remaining related assertion failures.
14775 Changes in version 0.0.7.1 - 2004-07-04
14776 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
14777 since internally we use 0.0.0.0 to signify "not yet resolved".
14780 Changes in version 0.0.7 - 2004-06-07
14781 o Updated the man page to reflect the new features.
14784 Changes in version 0.0.7rc2 - 2004-06-06
14785 o Changes from 0.0.7rc1:
14786 - Make it build on Win32 again.
14787 o Changes from 0.0.6.2:
14788 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
14792 Changes in version 0.0.7rc1 - 2004-06-02
14794 - On sighup, we were adding another log without removing the first
14795 one. So log messages would get duplicated n times for n sighups.
14796 - Several cases of using a connection after we'd freed it. The
14797 problem was that connections that are pending resolve are in both
14798 the pending_resolve tree, and also the circuit's resolving_streams
14799 list. When you want to remove one, you must remove it from both.
14800 - Fix a double-mark-for-close where an end cell arrived for a
14801 resolving stream, and then the resolve failed.
14802 - Check directory signatures based on name of signer, not on whom
14803 we got the directory from. This will let us cache directories more
14806 - Crank up some of our constants to handle more users.
14809 Changes in version 0.0.7pre1 - 2004-06-02
14810 o Fixes for crashes and other obnoxious bugs:
14811 - Fix an epipe bug: sometimes when directory connections failed
14812 to connect, we would give them a chance to flush before closing
14814 - When we detached from a circuit because of resolvefailed, we
14815 would immediately try the same circuit twice more, and then
14816 give up on the resolve thinking we'd tried three different
14818 - Limit the number of intro circuits we'll attempt to build for a
14819 hidden service per 15-minute period.
14820 - Check recommended-software string *early*, before actually parsing
14821 the directory. Thus we can detect an obsolete version and exit,
14822 even if the new directory format doesn't parse.
14823 o Fixes for security bugs:
14824 - Remember which nodes are dirservers when you startup, and if a
14825 random OR enables his dirport, don't automatically assume he's
14826 a trusted dirserver.
14828 - Directory connections were asking the wrong poll socket to
14829 start writing, and not asking themselves to start writing.
14830 - When we detached from a circuit because we sent a begin but
14831 didn't get a connected, we would use it again the first time;
14832 but after that we would correctly switch to a different one.
14833 - Stop warning when the first onion decrypt attempt fails; they
14834 will sometimes legitimately fail now that we rotate keys.
14835 - Override unaligned-access-ok check when $host_cpu is ia64 or
14836 arm. Apparently they allow it but the kernel whines.
14837 - Dirservers try to reconnect periodically too, in case connections
14839 - Fix some memory leaks in directory servers.
14840 - Allow backslash in Win32 filenames.
14841 - Made Tor build complain-free on FreeBSD, hopefully without
14842 breaking other BSD builds. We'll see.
14844 - Doxygen markup on all functions and global variables.
14845 - Make directory functions update routerlist, not replace it. So
14846 now directory disagreements are not so critical a problem.
14847 - Remove the upper limit on number of descriptors in a dirserver's
14848 directory (not that we were anywhere close).
14849 - Allow multiple logfiles at different severity ranges.
14850 - Allow *BindAddress to specify ":port" rather than setting *Port
14851 separately. Allow multiple instances of each BindAddress config
14852 option, so you can bind to multiple interfaces if you want.
14853 - Allow multiple exit policy lines, which are processed in order.
14854 Now we don't need that huge line with all the commas in it.
14855 - Enable accept/reject policies on SOCKS connections, so you can bind
14856 to 0.0.0.0 but still control who can use your OP.
14859 Changes in version 0.0.6.2 - 2004-05-16
14860 o Our integrity-checking digest was checking only the most recent cell,
14861 not the previous cells like we'd thought.
14862 Thanks to Stefan Mark for finding the flaw!
14865 Changes in version 0.0.6.1 - 2004-05-06
14866 o Fix two bugs in our AES counter-mode implementation (this affected
14867 onion-level stream encryption, but not TLS-level). It turns
14868 out we were doing something much more akin to a 16-character
14869 polyalphabetic cipher. Oops.
14870 Thanks to Stefan Mark for finding the flaw!
14871 o Retire moria3 as a directory server, and add tor26 as a directory
14875 Changes in version 0.0.6 - 2004-05-02
14876 [version bump only]
14879 Changes in version 0.0.6rc4 - 2004-05-01
14880 o Update the built-in dirservers list to use the new directory format
14881 o Fix a rare seg fault: if a node offering a hidden service attempts
14882 to build a circuit to Alice's rendezvous point and fails before it
14883 reaches the last hop, it retries with a different circuit, but
14885 o Handle windows socket errors correctly.
14888 Changes in version 0.0.6rc3 - 2004-04-28
14889 o Don't expire non-general excess circuits (if we had enough
14890 circuits open, we were expiring rendezvous circuits -- even
14891 when they had a stream attached. oops.)
14892 o Fetch randomness from /dev/urandom better (not via fopen/fread)
14893 o Better debugging for tls errors
14894 o Some versions of openssl have an SSL_pending function that erroneously
14895 returns bytes when there is a non-application record pending.
14896 o Set Content-Type on the directory and hidserv descriptor.
14897 o Remove IVs from cipher code, since AES-ctr has none.
14898 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
14899 o We were using an array of length zero in a few places.
14900 o win32's gethostbyname can't resolve an IP to an IP.
14901 o win32's close can't close a socket.
14904 Changes in version 0.0.6rc2 - 2004-04-26
14905 o Fix a bug where we were closing tls connections intermittently.
14906 It turns out openssl keeps its errors around -- so if an error
14907 happens, and you don't ask about it, and then another openssl
14908 operation happens and succeeds, and you ask if there was an error,
14909 it tells you about the first error. Fun fun.
14910 o Fix a bug that's been lurking since 27 may 03 (!)
14911 When passing back a destroy cell, we would use the wrong circ id.
14912 'Mostly harmless', but still worth fixing.
14913 o Since we don't support truncateds much, don't bother sending them;
14914 just close the circ.
14915 o check for <machine/limits.h> so we build on NetBSD again (I hope).
14916 o don't crash if a conn that sent a begin has suddenly lost its circuit
14917 (this was quite rare).
14920 Changes in version 0.0.6rc1 - 2004-04-25
14921 o We now rotate link (tls context) keys and onion keys.
14922 o CREATE cells now include oaep padding, so you can tell
14923 if you decrypted them correctly.
14924 o Add bandwidthburst to server descriptor.
14925 o Directories now say which dirserver signed them.
14926 o Use a tor_assert macro that logs failed assertions too.
14929 Changes in version 0.0.6pre5 - 2004-04-18
14930 o changes from 0.0.6pre4:
14931 - make tor build on broken freebsd 5.2 installs
14932 - fix a failed assert when you try an intro point, get a nack, and try
14933 a second one and it works.
14934 - when alice uses a port that the hidden service doesn't accept,
14935 it now sends back an end cell (denied by exit policy). otherwise
14936 alice would just have to wait to time out.
14937 - fix another rare bug: when we had tried all the intro
14938 points for a hidden service, we fetched the descriptor
14939 again, but we left our introcirc thinking it had already
14940 sent an intro, so it kept waiting for a response...
14941 - bugfix: when you sleep your hidden-service laptop, as soon
14942 as it wakes up it tries to upload a service descriptor, but
14943 socketpair fails for some reason (localhost not up yet?).
14944 now we simply give up on that upload, and we'll try again later.
14945 i'd still like to find the bug though.
14946 - if an intro circ waiting for an ack dies before getting one, then
14948 - we were reusing stale service descriptors and refetching usable
14952 Changes in version 0.0.6pre4 - 2004-04-14
14953 o changes from 0.0.6pre3:
14954 - when bob fails to connect to the rendezvous point, and his
14955 circ didn't fail because of the rendezvous point itself, then
14956 he retries a couple of times
14957 - we expire introduction and rendezvous circs more thoroughly
14958 (sometimes they were hanging around forever)
14959 - we expire unattached rendezvous streams that have been around
14960 too long (they were sticking around forever).
14961 - fix a measly fencepost error that was crashing everybody with
14965 Changes in version 0.0.6pre3 - 2004-04-14
14966 o changes from 0.0.6pre2:
14967 - make hup work again
14968 - fix some memory leaks for dirservers
14969 - allow more skew in rendezvous descriptor timestamps, to help
14970 handle people like blanu who don't know what time it is
14971 - normal circs are 3 hops, but some rend/intro circs are 4, if
14972 the initiator doesn't get to choose the last hop
14973 - send acks for introductions, so alice can know whether to try
14975 - bob publishes intro points more correctly
14976 o changes from 0.0.5:
14977 - fix an assert trigger that's been plaguing us since the days
14978 of 0.0.2prexx (thanks weasel!)
14979 - retry stream correctly when we fail to connect because of
14980 exit-policy-reject (should try another) or can't-resolve-address
14981 (also should try another, because dns on random internet servers
14983 - when we hup a dirserver and we've *removed* a server from the
14984 approved-routers list, now we remove that server from the
14985 in-memory directories too
14988 Changes in version 0.0.6pre2 - 2004-04-08
14989 o We fixed our base32 implementation. Now it works on all architectures.
14992 Changes in version 0.0.6pre1 - 2004-04-08
14994 - Hidden services and rendezvous points are implemented. Go to
14995 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
14996 hidden services. (This only works via a socks4a proxy such as
14997 Privoxy, and currently it's quite slow.)
15000 Changes in version 0.0.5 - 2004-03-30
15001 [version bump only]
15004 Changes in version 0.0.5rc3 - 2004-03-29
15005 o Install torrc as torrc.sample -- we no longer clobber your
15007 o Re-enable recommendedversion checking (we broke it in rc2, oops)
15008 o Add in a 'notice' log level for things the operator should hear
15009 but that aren't warnings
15012 Changes in version 0.0.5rc2 - 2004-03-29
15013 o Hold socks connection open until reply is flushed (if possible)
15014 o Make exit nodes resolve IPs to IPs immediately, rather than asking
15015 the dns farm to do it.
15016 o Fix c99 aliasing warnings in rephist.c
15017 o Don't include server descriptors that are older than 24 hours in the
15019 o Give socks 'reject' replies their whole 15s to attempt to flush,
15020 rather than seeing the 60s timeout and assuming the flush had failed.
15021 o Clean automake droppings from the cvs repository
15024 Changes in version 0.0.5rc1 - 2004-03-28
15025 o Fix mangled-state bug in directory fetching (was causing sigpipes).
15026 o Only build circuits after we've fetched the directory: clients were
15027 using only the directory servers before they'd fetched a directory.
15028 This also means longer startup time; so it goes.
15029 o Fix an assert trigger where an OP would fail to handshake, and we'd
15030 expect it to have a nickname.
15031 o Work around a tsocks bug: do a socks reject when AP connection dies
15032 early, else tsocks goes into an infinite loop.
15035 Changes in version 0.0.4 - 2004-03-26
15036 o When connecting to a dirserver or OR and the network is down,
15040 Changes in version 0.0.3 - 2004-03-26
15041 o Warn and fail if server chose a nickname with illegal characters
15042 o Port to Solaris and Sparc:
15043 - include missing header fcntl.h
15044 - have autoconf find -lsocket -lnsl automatically
15045 - deal with hardware word alignment
15046 - make uname() work (solaris has a different return convention)
15047 - switch from using signal() to sigaction()
15048 o Preliminary work on reputation system:
15049 - Keep statistics on success/fail of connect attempts; they're published
15050 by kill -USR1 currently.
15051 - Add a RunTesting option to try to learn link state by creating test
15052 circuits, even when SocksPort is off.
15053 - Remove unused open circuits when there are too many.
15056 Changes in version 0.0.2 - 2004-03-19
15057 - Include strlcpy and strlcat for safer string ops
15058 - define INADDR_NONE so we compile (but still not run) on solaris
15061 Changes in version 0.0.2pre27 - 2004-03-14
15063 - Allow internal tor networks (we were rejecting internal IPs,
15064 now we allow them if they're set explicitly).
15065 - And fix a few endian issues.
15068 Changes in version 0.0.2pre26 - 2004-03-14
15070 - If a stream times out after 15s without a connected cell, don't
15071 try that circuit again: try a new one.
15072 - Retry streams at most 4 times. Then give up.
15073 - When a dirserver gets a descriptor from an unknown router, it
15074 logs its fingerprint (so the dirserver operator can choose to
15075 accept it even without mail from the server operator).
15076 - Inform unapproved servers when we reject their descriptors.
15077 - Make tor build on Windows again. It works as a client, who knows
15079 - Clearer instructions in the torrc for how to set up a server.
15080 - Be more efficient about reading fd's when our global token bucket
15081 (used for rate limiting) becomes empty.
15083 - Stop asserting that computers always go forward in time. It's
15085 - When we sent a cell (e.g. destroy) and then marked an OR connection
15086 expired, we might close it before finishing a flush if the other
15087 side isn't reading right then.
15088 - Don't allow dirservers to start if they haven't defined
15089 RecommendedVersions
15090 - We were caching transient dns failures. Oops.
15091 - Prevent servers from publishing an internal IP as their address.
15092 - Address a strcat vulnerability in circuit.c
15095 Changes in version 0.0.2pre25 - 2004-03-04
15097 - Put the OR's IP in its router descriptor, not its fqdn. That way
15098 we'll stop being stalled by gethostbyname for nodes with flaky dns,
15101 - If the user typed in an address that didn't resolve, the server
15105 Changes in version 0.0.2pre24 - 2004-03-03
15107 - Fix an assertion failure in dns.c, where we were trying to dequeue
15108 a pending dns resolve even if it wasn't pending
15109 - Fix a spurious socks5 warning about still trying to write after the
15110 connection is finished.
15111 - Hold certain marked_for_close connections open until they're finished
15112 flushing, rather than losing bytes by closing them too early.
15113 - Correctly report the reason for ending a stream
15114 - Remove some duplicate calls to connection_mark_for_close
15115 - Put switch_id and start_daemon earlier in the boot sequence, so it
15116 will actually try to chdir() to options.DataDirectory
15117 - Make 'make test' exit(1) if a test fails; fix some unit tests
15118 - Make tor fail when you use a config option it doesn't know about,
15119 rather than warn and continue.
15120 - Make --version work
15121 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
15124 Changes in version 0.0.2pre23 - 2004-02-29
15126 - Print a statement when the first circ is finished, so the user
15127 knows it's working.
15128 - If a relay cell is unrecognized at the end of the circuit,
15129 send back a destroy. (So attacks to mutate cells are more
15131 - New config option 'excludenodes' to avoid certain nodes for circuits.
15132 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
15133 so you can collect coredumps there.
15135 - Fix a bug in tls flushing where sometimes data got wedged and
15136 didn't flush until more data got sent. Hopefully this bug was
15137 a big factor in the random delays we were seeing.
15138 - Make 'connected' cells include the resolved IP, so the client
15139 dns cache actually gets populated.
15140 - Disallow changing from ORPort=0 to ORPort>0 on hup.
15141 - When we time-out on a stream and detach from the circuit, send an
15142 end cell down it first.
15143 - Only warn about an unknown router (in exitnodes, entrynodes,
15144 excludenodes) after we've fetched a directory.
15147 Changes in version 0.0.2pre22 - 2004-02-26
15149 - Servers publish less revealing uname information in descriptors.
15150 - More memory tracking and assertions, to crash more usefully when
15152 - If the default torrc isn't there, just use some default defaults.
15153 Plus provide an internal dirservers file if they don't have one.
15154 - When the user tries to use Tor as an http proxy, give them an http
15155 501 failure explaining that we're a socks proxy.
15156 - Dump a new router.desc on hup, to help confused people who change
15157 their exit policies and then wonder why router.desc doesn't reflect
15159 - Clean up the generic tor.sh init script that we ship with.
15161 - If the exit stream is pending on the resolve, and a destroy arrives,
15162 then the stream wasn't getting removed from the pending list. I
15163 think this was the one causing recent server crashes.
15164 - Use a more robust poll on OSX 10.3, since their poll is flaky.
15165 - When it couldn't resolve any dirservers, it was useless from then on.
15166 Now it reloads the RouterFile (or default dirservers) if it has no
15168 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
15169 many users don't even *have* a /usr/local/sbin/.
15172 Changes in version 0.0.2pre21 - 2004-02-18
15174 - There's a ChangeLog file that actually reflects the changelog.
15175 - There's a 'torify' wrapper script, with an accompanying
15176 tor-tsocks.conf, that simplifies the process of using tsocks for
15177 tor. It even has a man page.
15178 - The tor binary gets installed to sbin rather than bin now.
15179 - Retry streams where the connected cell hasn't arrived in 15 seconds
15180 - Clean up exit policy handling -- get the default out of the torrc,
15181 so we can update it without forcing each server operator to fix
15183 - Allow imaps and pop3s in default exit policy
15185 - Prevent picking middleman nodes as the last node in the circuit
15188 Changes in version 0.0.2pre20 - 2004-01-30
15190 - We now have a deb package, and it's in debian unstable. Go to
15191 it, apt-getters. :)
15192 - I've split the TotalBandwidth option into BandwidthRate (how many
15193 bytes per second you want to allow, long-term) and
15194 BandwidthBurst (how many bytes you will allow at once before the cap
15195 kicks in). This better token bucket approach lets you, say, set
15196 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
15197 performance while not exceeding your monthly bandwidth quota.
15198 - Push out a tls record's worth of data once you've got it, rather
15199 than waiting until you've read everything waiting to be read. This
15200 may improve performance by pipelining better. We'll see.
15201 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
15202 from failed circuits (if they haven't been connected yet) and attach
15204 - Expire old streams that haven't managed to connect. Some day we'll
15205 have them reattach to new circuits instead.
15208 - Fix several memory leaks that were causing servers to become bloated
15210 - Fix a few very rare assert triggers. A few more remain.
15211 - Setuid to User _before_ complaining about running as root.
15214 Changes in version 0.0.2pre19 - 2004-01-07
15216 - Fix deadlock condition in dns farm. We were telling a child to die by
15217 closing the parent's file descriptor to him. But newer children were
15218 inheriting the open file descriptor from the parent, and since they
15219 weren't closing it, the socket never closed, so the child never read
15220 eof, so he never knew to exit. Similarly, dns workers were holding
15221 open other sockets, leading to all sorts of chaos.
15222 - New cleaner daemon() code for forking and backgrounding.
15223 - If you log to a file, it now prints an entry at the top of the
15224 logfile so you know it's working.
15225 - The onionskin challenge length was 30 bytes longer than necessary.
15226 - Started to patch up the spec so it's not quite so out of date.
15229 Changes in version 0.0.2pre18 - 2004-01-02
15231 - Fix endian issues with the 'integrity' field in the relay header.
15232 - Fix a potential bug where connections in state
15233 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
15236 Changes in version 0.0.2pre17 - 2003-12-30
15238 - Made --debuglogfile (or any second log file, actually) work.
15239 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
15240 adversary could force us into an infinite loop.
15243 - Each onionskin handshake now includes a hash of the computed key,
15244 to prove the server's identity and help perfect forward secrecy.
15245 - Changed cell size from 256 to 512 bytes (working toward compatibility
15247 - Changed cell length to 2 bytes, and moved it to the relay header.
15248 - Implemented end-to-end integrity checking for the payloads of
15250 - Separated streamid from 'recognized' (otherwise circuits will get
15251 messed up when we try to have streams exit from the middle). We
15252 use the integrity-checking to confirm that a cell is addressed to
15254 - Randomize the initial circid and streamid values, so an adversary who
15255 breaks into a node can't learn how many circuits or streams have
15259 Changes in version 0.0.2pre16 - 2003-12-14
15261 - Fixed a bug that made HUP trigger an assert
15262 - Fixed a bug where a circuit that immediately failed wasn't being
15263 counted as a failed circuit in counting retries.
15266 - Now we close the circuit when we get a truncated cell: otherwise we're
15267 open to an anonymity attack where a bad node in the path truncates
15268 the circuit and then we open streams at him.
15269 - Add port ranges to exit policies
15270 - Add a conservative default exit policy
15271 - Warn if you're running tor as root
15272 - on HUP, retry OR connections and close/rebind listeners
15273 - options.EntryNodes: try these nodes first when picking the first node
15274 - options.ExitNodes: if your best choices happen to include any of
15275 your preferred exit nodes, you choose among just those preferred
15277 - options.ExcludedNodes: nodes that are never picked in path building
15280 Changes in version 0.0.2pre15 - 2003-12-03
15281 o Robustness and bugfixes:
15282 - Sometimes clients would cache incorrect DNS resolves, which would
15283 really screw things up.
15284 - An OP that goes offline would slowly leak all its sockets and stop
15286 - A wide variety of bugfixes in exit node selection, exit policy
15287 handling, and processing pending streams when a new circuit is
15289 - Pick nodes for a path only from those the directory says are up
15290 - Choose randomly from all running dirservers, not always the first one
15291 - Increase allowed http header size for directory fetch.
15292 - Stop writing to stderr (if we're daemonized it will be closed).
15293 - Enable -g always, so cores will be more useful to me.
15294 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
15297 - Wrote a man page. It lists commonly used options.
15300 - Change default loglevel to warn.
15301 - Make PidFile default to null rather than littering in your CWD.
15302 - OnionRouter config option is now obsolete. Instead it just checks
15304 - Moved to a single unified torrc file for both clients and servers.
15307 Changes in version 0.0.2pre14 - 2003-11-29
15308 o Robustness and bugfixes:
15309 - Force the admin to make the DataDirectory himself
15310 - to get ownership/permissions right
15311 - so clients no longer make a DataDirectory and then never use it
15312 - fix bug where a client who was offline for 45 minutes would never
15313 pull down a directory again
15314 - fix (or at least hide really well) the dns assert bug that was
15315 causing server crashes
15316 - warnings and improved robustness wrt clockskew for certs
15317 - use the native daemon(3) to daemonize, when available
15318 - exit if bind() fails
15319 - exit if neither socksport nor orport is defined
15320 - include our own tor_timegm (Win32 doesn't have its own)
15321 - bugfix for win32 with lots of connections
15322 - fix minor bias in PRNG
15323 - make dirserver more robust to corrupt cached directory
15326 - Wrote the design document (woo)
15328 o Circuit building and exit policies:
15329 - Circuits no longer try to use nodes that the directory has told them
15331 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
15332 bitcounts (18.0.0.0/8).
15333 - Make AP connections standby for a circuit if no suitable circuit
15334 exists, rather than failing
15335 - Circuits choose exit node based on addr/port, exit policies, and
15336 which AP connections are standing by
15337 - Bump min pathlen from 2 to 3
15338 - Relay end cells have a payload to describe why the stream ended.
15339 - If the stream failed because of exit policy, try again with a new
15341 - Clients have a dns cache to remember resolved addresses.
15342 - Notice more quickly when we have no working circuits
15345 - APPort is now called SocksPort
15346 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
15348 - RecommendedVersions is now a config variable rather than
15349 hardcoded (for dirservers)
15350 - Reloads config on HUP
15351 - Usage info on -h or --help
15352 - If you set User and Group config vars, it'll setu/gid to them.
15355 Changes in version 0.0.2pre13 - 2003-10-19
15356 o General stability:
15357 - SSL_write no longer fails when it returns WANTWRITE and the number
15358 of bytes in the buf has changed by the next SSL_write call.
15359 - Fix segfault fetching directory when network is down
15360 - Fix a variety of minor memory leaks
15361 - Dirservers reload the fingerprints file on HUP, so I don't have
15362 to take down the network when I approve a new router
15363 - Default server config file has explicit Address line to specify fqdn
15366 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
15367 - Make listener connections not ever alloc bufs
15369 o Autoconf improvements:
15370 - don't clobber an external CFLAGS in ./configure
15371 - Make install now works
15372 - create var/lib/tor on make install
15373 - autocreate a tor.sh initscript to help distribs
15374 - autocreate the torrc and sample-server-torrc with correct paths
15376 o Log files and Daemonizing now work:
15377 - If --DebugLogFile is specified, log to it at -l debug
15378 - If --LogFile is specified, use it instead of commandline
15379 - If --RunAsDaemon is set, tor forks and backgrounds on startup