1 Changes in version 0.2.4.20 - 2013-12-22
2 Tor 0.2.4.20 fixes potentially poor random number generation for users
3 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
4 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
5 and 4) have no state file in their DataDirectory (as would happen on
6 first start). Users who generated relay or hidden service identity
7 keys in such a situation should discard them and generate new ones.
9 This release also fixes a logic error that caused Tor clients to build
10 many more preemptive circuits than they actually need.
13 - Do not allow OpenSSL engines to replace the PRNG, even when
14 HardwareAccel is set. The only default builtin PRNG engine uses
15 the Intel RDRAND instruction to replace the entire PRNG, and
16 ignores all attempts to seed it with more entropy. That's
17 cryptographically stupid: the right response to a new alleged
18 entropy source is never to discard all previously used entropy
19 sources. Fixes bug 10402; works around behavior introduced in
20 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
22 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
23 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
24 - Avoid launching spurious extra circuits when a stream is pending.
25 This fixes a bug where any circuit that _wasn't_ unusable for new
26 streams would be treated as if it were, causing extra circuits to
27 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
30 - Avoid a crash bug when starting with a corrupted microdescriptor
31 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
32 - If we fail to dump a previously cached microdescriptor to disk, avoid
33 freeing duplicate data later on. Fixes bug 10423; bugfix on
34 0.2.4.13-alpha. Spotted by "bobnomnom".
37 Changes in version 0.2.4.19 - 2013-12-11
38 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
39 (1986-2013). Aaron worked on diverse projects including helping to guide
40 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
41 transparency to the U.S government's PACER documents, and contributing
42 design and development for Tor and Tor2Web. Aaron was one of the latest
43 martyrs in our collective fight for civil liberties and human rights,
44 and his death is all the more painful because he was one of us.
46 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
47 a new circuit handshake and link encryption that use ECC to provide
48 better security and efficiency; makes relays better manage circuit
49 creation requests; uses "directory guards" to reduce client enumeration
50 risks; makes bridges collect and report statistics about the pluggable
51 transports they support; cleans up and improves our geoip database;
52 gets much closer to IPv6 support for clients, bridges, and relays; makes
53 directory authorities use measured bandwidths rather than advertised
54 ones when computing flags and thresholds; disables client-side DNS
55 caching to reduce tracking risks; and fixes a big bug in bridge
56 reachability testing. This release introduces two new design
57 abstractions in the code: a new "channel" abstraction between circuits
58 and or_connections to allow for implementing alternate relay-to-relay
59 transports, and a new "circuitmux" abstraction storing the queue of
60 circuits for a channel. The release also includes many stability,
61 security, and privacy fixes.
64 Changes in version 0.2.4.18-rc - 2013-11-16
65 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
66 series. It takes a variety of fixes from the 0.2.5.x branch to improve
67 stability, performance, and better handling of edge cases.
70 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
71 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
72 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
73 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
74 them to solve bug 6033.)
77 - No longer stop reading or writing on cpuworker connections when
78 our rate limiting buckets go empty. Now we should handle circuit
79 handshake requests more promptly. Resolves bug 9731.
80 - If we are unable to save a microdescriptor to the journal, do not
81 drop it from memory and then reattempt downloading it. Fixes bug
82 9645; bugfix on 0.2.2.6-alpha.
83 - Stop trying to bootstrap all our directory information from
84 only our first guard. Discovered while fixing bug 9946; bugfix
86 - The new channel code sometimes lost track of in-progress circuits,
87 causing long-running clients to stop building new circuits. The
88 fix is to always call circuit_n_chan_done(chan, 0) from
89 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
91 o Minor bugfixes (on 0.2.4.x):
92 - Correctly log long IPv6 exit policies, instead of truncating them
93 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
94 - Our default TLS ecdhe groups were backwards: we meant to be using
95 P224 for relays (for performance win) and P256 for bridges (since
96 it is more common in the wild). Instead we had it backwards. After
97 reconsideration, we decided that the default should be P256 on all
98 hosts, since its security is probably better, and since P224 is
99 reportedly used quite little in the wild. Found by "skruffy" on
100 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
101 - Free directory authority certificate download statuses on exit
102 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
104 o Minor bugfixes (on 0.2.3.x and earlier):
105 - If the guard we choose first doesn't answer, we would try the
106 second guard, but once we connected to the second guard we would
107 abandon it and retry the first one, slowing down bootstrapping.
108 The fix is to treat all our initially chosen guards as acceptable
109 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
110 - Fix an assertion failure that would occur when disabling the
111 ORPort setting on a running Tor process while accounting was
112 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
113 - When examining the list of network interfaces to find our address,
114 do not consider non-running or disabled network interfaces. Fixes
115 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
116 - Avoid an off-by-one error when checking buffer boundaries when
117 formatting the exit status of a pluggable transport helper.
118 This is probably not an exploitable bug, but better safe than
119 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
122 o Minor features (protecting client timestamps):
123 - Clients no longer send timestamps in their NETINFO cells. These were
124 not used for anything, and they provided one small way for clients
125 to be distinguished from each other as they moved from network to
126 network or behind NAT. Implements part of proposal 222.
127 - Clients now round timestamps in INTRODUCE cells down to the nearest
128 10 minutes. If a new Support022HiddenServices option is set to 0, or
129 if it's set to "auto" and the feature is disabled in the consensus,
130 the timestamp is sent as 0 instead. Implements part of proposal 222.
131 - Stop sending timestamps in AUTHENTICATE cells. This is not such
132 a big deal from a security point of view, but it achieves no actual
133 good purpose, and isn't needed. Implements part of proposal 222.
134 - Reduce down accuracy of timestamps in hidden service descriptors.
135 Implements part of proposal 222.
137 o Minor features (other):
138 - Improve the circuit queue out-of-memory handler. Previously, when
139 we ran low on memory, we'd close whichever circuits had the most
140 queued cells. Now, we close those that have the *oldest* queued
141 cells, on the theory that those are most responsible for us
142 running low on memory. Based on analysis from a forthcoming paper
143 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
144 - Generate bootstrapping status update events correctly when fetching
145 microdescriptors. Fixes bug 9927.
146 - Update to the October 2 2013 Maxmind GeoLite Country database.
148 o Documentation fixes:
149 - Clarify the usage and risks of setting the ContactInfo torrc line
150 for your relay or bridge. Resolves ticket 9854.
151 - Add anchors to the manpage so we can link to the html version of
152 the documentation for specific options. Resolves ticket 9866.
153 - Replace remaining references to DirServer in man page and
154 log entries. Resolves ticket 10124.
157 Changes in version 0.2.5.1-alpha - 2013-10-02
158 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
159 on Linux, allows bridges that offer pluggable transports to report usage
160 statistics, fixes many issues to make testing easier, and provides
161 a pile of minor features and bugfixes that have been waiting for a
162 release of the new branch.
164 This is the first alpha release in a new series, so expect there to
165 be bugs. Users who would rather test out a more stable branch should
166 stay with 0.2.4.x for now.
168 o Major features (security):
169 - Use the seccomp2 syscall filtering facility on Linux to limit
170 which system calls Tor can invoke. This is an experimental,
171 Linux-only feature to provide defense-in-depth against unknown
172 attacks. To try turning it on, set "Sandbox 1" in your torrc
173 file. Please be ready to report bugs. We hope to add support
174 for better sandboxing in the future, including more fine-grained
175 filters, better division of responsibility, and support for more
176 platforms. This work has been done by Cristian-Matei Toader for
177 Google Summer of Code.
178 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
179 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
180 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
181 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
182 them to solve bug 6033.)
184 o Major features (other):
185 - Add support for passing arguments to managed pluggable transport
186 proxies. Implements ticket 3594.
187 - Bridges now track GeoIP information and the number of their users
188 even when pluggable transports are in use, and report usage
189 statistics in their extra-info descriptors. Resolves tickets 4773
191 - Make testing Tor networks bootstrap better: lower directory fetch
192 retry schedules and maximum interval without directory requests,
193 and raise maximum download tries. Implements ticket 6752.
194 - Add make target 'test-network' to run tests on a Chutney network.
195 Implements ticket 8530.
196 - The ntor handshake is now on-by-default, no matter what the
197 directory authorities recommend. Implements ticket 8561.
200 - Instead of writing destroy cells directly to outgoing connection
201 buffers, queue them and intersperse them with other outgoing cells.
202 This can prevent a set of resource starvation conditions where too
203 many pending destroy cells prevent data cells from actually getting
204 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
205 bugfix on 0.2.0.1-alpha.
206 - If we are unable to save a microdescriptor to the journal, do not
207 drop it from memory and then reattempt downloading it. Fixes bug
208 9645; bugfix on 0.2.2.6-alpha.
209 - The new channel code sometimes lost track of in-progress circuits,
210 causing long-running clients to stop building new circuits. The
211 fix is to always call circuit_n_chan_done(chan, 0) from
212 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
215 - Tor now builds each source file in two modes: a mode that avoids
216 exposing identifiers needlessly, and another mode that exposes
217 more identifiers for testing. This lets the compiler do better at
218 optimizing the production code, while enabling us to take more
219 radical measures to let the unit tests test things.
220 - The production builds no longer include functions used only in
221 the unit tests; all functions exposed from a module only for
222 unit-testing are now static in production builds.
223 - Add an --enable-coverage configuration option to make the unit
224 tests (and a new src/or/tor-cov target) to build with gcov test
228 - We now have rudimentary function mocking support that our unit
229 tests can use to test functions in isolation. Function mocking
230 lets the tests temporarily replace a function's dependencies with
231 stub functions, so that the tests can check the function without
232 invoking the other functions it calls.
233 - Add more unit tests for the <circid,channel>->circuit map, and
234 the destroy-cell-tracking code to fix bug 7912.
235 - Unit tests for failing cases of the TAP onion handshake.
236 - More unit tests for address-manipulation functions.
238 o Minor features (protecting client timestamps):
239 - Clients no longer send timestamps in their NETINFO cells. These were
240 not used for anything, and they provided one small way for clients
241 to be distinguished from each other as they moved from network to
242 network or behind NAT. Implements part of proposal 222.
243 - Clients now round timestamps in INTRODUCE cells down to the nearest
244 10 minutes. If a new Support022HiddenServices option is set to 0, or
245 if it's set to "auto" and the feature is disabled in the consensus,
246 the timestamp is sent as 0 instead. Implements part of proposal 222.
247 - Stop sending timestamps in AUTHENTICATE cells. This is not such
248 a big deal from a security point of view, but it achieves no actual
249 good purpose, and isn't needed. Implements part of proposal 222.
250 - Reduce down accuracy of timestamps in hidden service descriptors.
251 Implements part of proposal 222.
253 o Minor features (config options):
254 - Config (torrc) lines now handle fingerprints which are missing
255 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
256 - Support a --dump-config option to print some or all of the
257 configured options. Mainly useful for debugging the command-line
258 option parsing code. Helps resolve ticket 4647.
259 - Raise awareness of safer logging: notify user of potentially
260 unsafe config options, like logging more verbosely than severity
261 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
262 - Add a new configuration option TestingV3AuthVotingStartOffset
263 that bootstraps a network faster by changing the timing for
264 consensus votes. Addresses ticket 8532.
265 - Add a new torrc option "ServerTransportOptions" that allows
266 bridge operators to pass configuration parameters to their
267 pluggable transports. Resolves ticket 8929.
268 - The config (torrc) file now accepts bandwidth and space limits in
269 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
270 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
273 o Minor features (build):
274 - Add support for `--library-versions` flag. Implements ticket 6384.
275 - Return the "unexpected sendme" warnings to a warn severity, but make
276 them rate limited, to help diagnose ticket 8093.
277 - Detect a missing asciidoc, and warn the user about it, during
278 configure rather than at build time. Fixes issue 6506. Patch from
281 o Minor features (other):
282 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
283 sockets in a single system call. Implements ticket 5129.
284 - Log current accounting state (bytes sent and received + remaining
285 time for the current accounting period) in the relay's heartbeat
286 message. Implements ticket 5526; patch from Peter Retzlaff.
287 - Implement the TRANSPORT_LAUNCHED control port event that
288 notifies controllers about new launched pluggable
289 transports. Resolves ticket 5609.
290 - If we're using the pure-C 32-bit curve25519_donna implementation
291 of curve25519, build it with the -fomit-frame-pointer option to
292 make it go faster on register-starved hosts. This improves our
293 handshake performance by about 6% on i386 hosts without nacl.
295 - Update to the September 4 2013 Maxmind GeoLite Country database.
298 - Set the listen() backlog limit to the largest actually supported
299 on the system, not to the value in a header file. Fixes bug 9716;
300 bugfix on every released Tor.
301 - No longer accept malformed http headers when parsing urls from
302 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
304 - In munge_extrainfo_into_routerinfo(), check the return value of
305 memchr(). This would have been a serious issue if we ever passed
306 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
308 - On the chance that somebody manages to build Tor on a
309 platform where time_t is unsigned, correct the way that
310 microdesc_add_to_cache() handles negative time arguments.
311 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
312 - Reject relative control socket paths and emit a warning. Previously,
313 single-component control socket paths would be rejected, but Tor
314 would not log why it could not validate the config. Fixes bug 9258;
315 bugfix on 0.2.3.16-alpha.
317 o Minor bugfixes (command line):
318 - Use a single command-line parser for parsing torrc options on the
319 command line and for finding special command-line options to avoid
320 inconsistent behavior for torrc option arguments that have the same
321 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
323 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
324 9573; bugfix on 0.0.9pre5.
326 o Minor fixes (build, auxiliary programs):
327 - Stop preprocessing the "torify" script with autoconf, since
328 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
330 - The tor-fw-helper program now follows the standard convention and
331 exits with status code "0" on success. Fixes bug 9030; bugfix on
332 0.2.3.1-alpha. Patch by Arlo Breault.
333 - Corrected ./configure advice for what openssl dev package you should
334 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
336 o Minor code improvements:
337 - Remove constants and tests for PKCS1 padding; it's insecure and
338 shouldn't be used for anything new. Fixes bug 8792; patch
340 - Remove instances of strcpy() from the unit tests. They weren't
341 hurting anything, since they were only in the unit tests, but it's
342 embarassing to have strcpy() in the code at all, and some analysis
343 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
344 0.2.3.8-alpha. Patch from Arlo Breault.
347 - Remove migration code from when we renamed the "cached-routers"
348 file to "cached-descriptors" back in 0.2.0.8-alpha. This
349 incidentally resolves ticket 6502 by cleaning up the related code
350 a bit. Patch from Akshay Hebbar.
352 o Code simplification and refactoring:
353 - Extract the common duplicated code for creating a subdirectory
354 of the data directory and writing to a file in it. Fixes ticket
355 4282; patch from Peter Retzlaff.
356 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
357 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
358 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
359 - Add a set of accessor functions for the circuit timeout data
360 structure. Fixes ticket 6153; patch from "piet".
361 - Clean up exit paths from connection_listener_new(). Closes ticket
362 8789. Patch from Arlo Breault.
363 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
364 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
365 - Use a doubly-linked list to implement the global circuit list.
366 Resolves ticket 9108. Patch from Marek Majkowski.
367 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
370 Changes in version 0.2.4.17-rc - 2013-09-05
371 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
372 series. It adds an emergency step to help us tolerate the massive
373 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
374 circuit-level handshakes now effectively jump the queue compared to
375 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
376 big bug hindering bridge reachability tests.
379 - Relays now process the new "NTor" circuit-level handshake requests
380 with higher priority than the old "TAP" circuit-level handshake
381 requests. We still process some TAP requests to not totally starve
382 0.2.3 clients when NTor becomes popular. A new consensus parameter
383 "NumNTorsPerTAP" lets us tune the balance later if we need to.
384 Implements ticket 9574.
387 - If the circuit build timeout logic is disabled (via the consensus,
388 or because we are an authority), then don't build testing circuits.
389 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
390 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
391 previously they did not, which prevented them from receiving
392 successful connections from relays for self-test or bandwidth
393 testing. Also, when a relay is extending a circuit to a bridge,
394 it needs to send a NETINFO cell, even when the bridge hasn't sent
395 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
396 - If the time to download the next old-style networkstatus is in
397 the future, do not decline to consider whether to download the
398 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
402 - Avoid double-closing the listener socket in our socketpair()
403 replacement (used on Windows) in the case where the addresses on
404 our opened sockets don't match what we expected. Fixes bug 9400;
405 bugfix on 0.0.2pre7. Found by Coverity.
407 o Minor fixes (config options):
408 - Avoid overflows when the user sets MaxCircuitDirtiness to a
409 ridiculously high value, by imposing a (ridiculously high) 30-day
410 maximum on MaxCircuitDirtiness.
411 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
412 message is logged at notice, not at info.
413 - Warn and fail if a server is configured not to advertise any
414 ORPorts at all. (We need *something* to put in our descriptor,
415 or we just won't work.)
418 - Track how many "TAP" and "NTor" circuit handshake requests we get,
419 and how many we complete, and log it every hour to help relay
420 operators follow trends in network load. Addresses ticket 9658.
421 - Update to the August 7 2013 Maxmind GeoLite Country database.
424 Changes in version 0.2.4.16-rc - 2013-08-10
425 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
426 series. It fixes several crash bugs in the 0.2.4 branch.
429 - Fix a bug in the voting algorithm that could yield incorrect results
430 when a non-naming authority declared too many flags. Fixes bug 9200;
431 bugfix on 0.2.0.3-alpha.
432 - Fix an uninitialized read that could in some cases lead to a remote
433 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
434 Anybody running a hidden service on the experimental 0.2.4.x
435 branch should upgrade. (This is, so far as we know, unrelated to
437 - Avoid an assertion failure when processing DNS replies without the
438 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
439 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
440 0.2.4.15-rc. Found by stem integration tests.
443 - Fix an invalid memory read that occured when a pluggable
444 transport proxy failed its configuration protocol.
445 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
446 - When evaluating whether to use a connection that we haven't
447 decided is canonical using a recent link protocol version,
448 decide that it's canonical only if it used address _does_
449 match the desired address. Fixes bug 9309; bugfix on
450 0.2.4.4-alpha. Reported by skruffy.
451 - Make the default behavior of NumDirectoryGuards be to track
452 NumEntryGuards. Now a user who changes only NumEntryGuards will get
453 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
454 - Fix a spurious compilation warning with some older versions of
455 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
458 - Update to the July 3 2013 Maxmind GeoLite Country database.
461 Changes in version 0.2.4.15-rc - 2013-07-01
462 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
463 series. It fixes a few smaller bugs, but generally appears stable.
464 Please test it and let us know whether it is!
467 - When receiving a new configuration file via the control port's
468 LOADCONF command, do not treat the defaults file as absent.
469 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
472 - Issue a warning when running with the bufferevents backend enabled.
473 It's still not stable, and people should know that they're likely
474 to hit unexpected problems. Closes ticket 9147.
477 Changes in version 0.2.4.14-alpha - 2013-06-18
478 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
479 present in 0.2.4.13-alpha.
482 - When we have too much memory queued in circuits (according to a new
483 MaxMemInCellQueues option), close the circuits consuming the most
484 memory. This prevents us from running out of memory as a relay if
485 circuits fill up faster than they can be drained. Fixes bug 9063;
486 bugfix on the 54th commit of Tor. This bug is a further fix beyond
487 bug 6252, whose fix was merged into 0.2.3.21-rc.
489 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
490 where we tried to solve this issue simply by imposing an upper limit
491 on the number of queued cells for a single circuit. That approach
492 proved to be problematic, since there are ways to provoke clients to
493 send a number of cells in excess of any such reasonable limit. Fixes
494 bug 9072; bugfix on 0.2.4.13-alpha.
496 - Limit hidden service descriptors to at most ten introduction
497 points, to slow one kind of guard enumeration. Fixes bug 9002;
498 bugfix on 0.1.1.11-alpha.
501 Changes in version 0.2.4.13-alpha - 2013-06-14
502 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
503 vulnerabilities, makes socks5 username/password circuit isolation
504 actually actually work (this time for sure!), and cleans up a bunch
505 of other issues in preparation for a release candidate.
507 o Major bugfixes (robustness):
508 - Close any circuit that has too many cells queued on it. Fixes
509 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
510 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
511 - Prevent the get_freelists() function from running off the end of
512 the list of freelists if it somehow gets an unrecognized
513 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
515 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
516 when an exit connection with optimistic data succeeds immediately
517 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
519 - Fix a directory authority crash bug when building a consensus
520 using an older consensus as its basis. Fixes bug 8833. Bugfix
524 - Avoid a memory leak where we would leak a consensus body when we
525 find that a consensus which we couldn't previously verify due to
526 missing certificates is now verifiable. Fixes bug 8719; bugfix
528 - We used to always request authority certificates by identity digest,
529 meaning we'd get the newest one even when we wanted one with a
530 different signing key. Then we would complain about being given
531 a certificate we already had, and never get the one we really
532 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
533 resource to request the one we want. Fixes bug 5595; bugfix on
535 - Follow the socks5 protocol when offering username/password
536 authentication. The fix for bug 8117 exposed this bug, and it
537 turns out real-world applications like Pidgin do care. Bugfix on
538 0.2.3.2-alpha; fixes bug 8879.
539 - Prevent failures on Windows Vista and later when rebuilding the
540 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
541 bugfix on 0.2.4.12-alpha.
544 - Fix an impossible buffer overrun in the AES unit tests. Fixes
545 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
546 - If for some reason we fail to write a microdescriptor while
547 rebuilding the cache, do not let the annotations from that
548 microdescriptor linger in the cache file, and do not let the
549 microdescriptor stay recorded as present in its old location.
550 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
551 - Fix a memory leak that would occur whenever a configuration
552 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
553 - Paste the description for PathBias parameters from the man
554 page into or.h, so the code documents them too. Fixes bug 7982;
555 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
556 - Relays now treat a changed IPv6 ORPort as sufficient reason to
557 publish an updated descriptor. Fixes bug 6026; bugfix on
559 - When launching a resolve request on behalf of an AF_UNIX control
560 socket, omit the address field of the new entry connection, used in
561 subsequent controller events, rather than letting tor_dup_addr()
562 set it to "<unknown address type>". Fixes bug 8639; bugfix on
565 o Minor bugfixes (log messages):
566 - Fix a scaling issue in the path bias accounting code that
567 resulted in "Bug:" log messages from either
568 pathbias_scale_close_rates() or pathbias_count_build_success().
569 This represents a bugfix on a previous bugfix: the original fix
570 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
572 - Give a less useless error message when the user asks for an IPv4
573 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
577 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
578 to tolerate bug 8093 for now.
579 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
580 in directory authority votes to describe whether they have enough
581 measured bandwidths to ignore advertised (relay descriptor)
582 bandwidth claims. Resolves ticket 8711.
583 - Update to the June 5 2013 Maxmind GeoLite Country database.
585 o Removed documentation:
586 - Remove some of the older contents of doc/ as obsolete; move others
587 to torspec.git. Fixes bug 8965.
589 o Code simplification and refactoring:
590 - Avoid using character buffers when constructing most directory
591 objects: this approach was unwieldy and error-prone. Instead,
592 build smartlists of strings, and concatenate them when done.
595 Changes in version 0.2.4.12-alpha - 2013-04-18
596 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
597 process for lengthening the guard rotation period, makes directory
598 authority opinions in the consensus a bit less gameable, makes socks5
599 username/password circuit isolation actually work, and fixes a wide
600 variety of other issues.
603 - Raise the default time that a client keeps an entry guard from
604 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
605 2012 paper. (We would make it even longer, but we need better client
606 load balancing first.) Also, make the guard lifetime controllable
607 via a new GuardLifetime torrc option and a GuardLifetime consensus
608 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
609 - Directory authorities now prefer using measured bandwidths to
610 advertised ones when computing flags and thresholds. Resolves
612 - Directory authorities that have more than a threshold number
613 of relays with measured bandwidths now treat relays with unmeasured
614 bandwidths as having bandwidth 0. Resolves ticket 8435.
616 o Major bugfixes (assert / resource use):
617 - Avoid a bug where our response to TLS renegotiation under certain
618 network conditions could lead to a busy-loop, with 100% CPU
619 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
620 - Avoid an assertion when we discover that we'd like to write a cell
621 onto a closing connection: just discard the cell. Fixes another
622 case of bug 7350; bugfix on 0.2.4.4-alpha.
624 o Major bugfixes (client-side privacy):
625 - When we mark a circuit as unusable for new circuits, have it
626 continue to be unusable for new circuits even if MaxCircuitDirtiness
627 is increased too much at the wrong time, or the system clock jumps
628 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
629 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
630 which have resolved to internal addresses") is set, apply that
631 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
632 - When an exit relay rejects a stream with reason "exit policy", but
633 we only know an exit policy summary (e.g. from the microdesc
634 consensus) for it, do not mark the relay as useless for all exiting.
635 Instead, mark just the circuit as unsuitable for that particular
636 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
637 - Allow applications to get proper stream isolation with
638 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
639 username/password authentication also offer "no authentication". Tor
640 had previously preferred "no authentication", so the applications
641 never actually sent Tor their auth details. Now Tor selects
642 username/password authentication if it's offered. You can disable
643 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
644 bug 8117; bugfix on 0.2.3.3-alpha.
646 o Major bugfixes (other):
647 - When unable to find any working directory nodes to use as a
648 directory guard, give up rather than adding the same non-working
649 nodes to the directory guard list over and over. Fixes bug 8231;
650 bugfix on 0.2.4.8-alpha.
653 - Reject as invalid most directory objects containing a NUL.
654 Belt-and-suspender fix for bug 8037.
655 - In our testsuite, create temporary directories with a bit more
656 entropy in their name to make name collisions less likely. Fixes
658 - Add CACHED keyword to ADDRMAP events in the control protocol
659 to indicate whether a DNS result will be cached or not. Resolves
661 - Update to the April 3 2013 Maxmind GeoLite Country database.
663 o Minor features (build):
664 - Detect and reject attempts to build Tor with threading support
665 when OpenSSL has been compiled without threading support.
667 - Clarify that when autoconf is checking for nacl, it is checking
668 specifically for nacl with a fast curve25519 implementation.
670 - Warn if building on a platform with an unsigned time_t: there
671 are too many places where Tor currently assumes that time_t can
672 hold negative values. We'd like to fix them all, but probably
675 o Minor bugfixes (build):
676 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
677 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
678 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
679 - Add the old src/or/micro-revision.i filename to CLEANFILES.
680 On the off chance that somebody has one, it will go away as soon
681 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
682 - Build Tor correctly on 32-bit platforms where the compiler can build
683 but not run code using the "uint128_t" construction. Fixes bug 8587;
684 bugfix on 0.2.4.8-alpha.
685 - Fix compilation warning with some versions of clang that would
686 prefer the -Wswitch-enum compiler flag to warn about switch
687 statements with missing enum values, even if those switch
688 statements have a "default:" statement. Fixes bug 8598; bugfix
691 o Minor bugfixes (protocol):
692 - Fix the handling of a TRUNCATE cell when it arrives while the
693 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
694 - Fix a misframing issue when reading the version numbers in a
695 VERSIONS cell. Previously we would recognize [00 01 00 02] as
696 'version 1, version 2, and version 0x100', when it should have
697 only included versions 1 and 2. Fixes bug 8059; bugfix on
698 0.2.0.10-alpha. Reported pseudonymously.
699 - Make the format and order of STREAM events for DNS lookups
700 consistent among the various ways to launch DNS lookups. Fixes
701 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
702 - Correct our check for which versions of Tor support the EXTEND2
703 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
704 later, when support was really added in version 0.2.4.8-alpha.
705 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
707 o Minor bugfixes (other):
708 - Correctly store microdescriptors and extrainfo descriptors with
709 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
710 Bug reported by "cypherpunks".
711 - Increase the width of the field used to remember a connection's
712 link protocol version to two bytes. Harmless for now, since the
713 only currently recognized versions are one byte long. Reported
714 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
715 - If the state file's path bias counts are invalid (presumably from a
716 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
717 additional checks and log messages to the scaling of Path Bias
718 counts, in case there still are remaining issues with scaling.
719 Should help resolve bug 8235.
720 - Eliminate several instances where we use "Nickname=ID" to refer to
721 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
722 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
723 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
725 o Minor bugfixes (syscalls):
726 - Always check the return values of functions fcntl() and
727 setsockopt(). We don't believe these are ever actually failing in
728 practice, but better safe than sorry. Also, checking these return
729 values should please analysis tools like Coverity. Patch from
730 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
731 - Use direct writes rather than stdio when building microdescriptor
732 caches, in an attempt to mitigate bug 8031, or at least make it
735 o Minor bugfixes (config):
736 - When rejecting a configuration because we were unable to parse a
737 quoted string, log an actual error message. Fixes bug 7950; bugfix
739 - Behave correctly when the user disables LearnCircuitBuildTimeout
740 but doesn't tell us what they would like the timeout to be. Fixes
741 bug 6304; bugfix on 0.2.2.14-alpha.
742 - When autodetecting the number of CPUs, use the number of available
743 CPUs in preference to the number of configured CPUs. Inform the
744 user if this reduces the number of available CPUs. Fixes bug 8002;
745 bugfix on 0.2.3.1-alpha.
746 - Make it an error when you set EntryNodes but disable UseGuardNodes,
747 since it will (surprisingly to some users) ignore EntryNodes. Fixes
748 bug 8180; bugfix on 0.2.3.11-alpha.
749 - Allow TestingTorNetworks to override the 4096-byte minimum for
750 the Fast threshold. Otherwise they can't bootstrap until they've
751 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
752 - Fix some logic errors when the user manually overrides the
753 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
756 o Minor bugfixes (log messages to help diagnose bugs):
757 - If we fail to free a microdescriptor because of bug 7164, log
758 the filename and line number from which we tried to free it.
759 - Add another diagnostic to the heartbeat message: track and log
760 overhead that TLS is adding to the data we write. If this is
761 high, we are sending too little data to SSL_write at a time.
762 Diagnostic for bug 7707.
763 - Add more detail to a log message about relaxed timeouts, to help
765 - Warn more aggressively when flushing microdescriptors to a
766 microdescriptor cache fails, in an attempt to mitigate bug 8031,
767 or at least make it more diagnosable.
768 - Improve debugging output to help track down bug 8185 ("Bug:
769 outgoing relay cell has n_chan==NULL. Dropping.")
770 - Log the purpose of a path-bias testing circuit correctly.
771 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
773 o Minor bugfixes (0.2.4.x log messages that were too noisy):
774 - Don't attempt to relax the timeout of already opened 1-hop circuits.
775 They might never timeout. This should eliminate some/all cases of
776 the relaxed timeout log message.
777 - Use circuit creation time for network liveness evaluation. This
778 should eliminate warning log messages about liveness caused
779 by changes in timeout evaluation. Fixes bug 6572; bugfix on
781 - Reduce a path bias length check from notice to info. The message
782 is triggered when creating controller circuits. Fixes bug 8196;
783 bugfix on 0.2.4.8-alpha.
784 - Fix a path state issue that triggered a notice during relay startup.
785 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
786 - Reduce occurrences of warns about circuit purpose in
787 connection_ap_expire_building(). Fixes bug 8477; bugfix on
790 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
791 - If we encounter a write failure on a SOCKS connection before we
792 finish our SOCKS handshake, don't warn that we closed the
793 connection before we could send a SOCKS reply. Fixes bug 8427;
794 bugfix on 0.1.0.1-rc.
795 - Correctly recognize that [::1] is a loopback address. Fixes
796 bug 8377; bugfix on 0.2.1.3-alpha.
797 - Fix a directory authority warn caused when we have a large amount
798 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
799 - Don't log inappropriate heartbeat messages when hibernating: a
800 hibernating node is _expected_ to drop out of the consensus,
801 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
802 bugfix on 0.2.3.1-alpha.
803 - Don't complain about bootstrapping problems while hibernating.
804 These complaints reflect a general code problem, but not one
805 with any problematic effects (no connections are actually
806 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
808 o Documentation fixes:
809 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
810 names match. Fixes bug 7768.
811 - Make the torify manpage no longer refer to tsocks; torify hasn't
812 supported tsocks since 0.2.3.14-alpha.
813 - Make the tor manpage no longer reference tsocks.
814 - Fix the GeoIPExcludeUnknown documentation to refer to
815 ExcludeExitNodes rather than the currently nonexistent
816 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
819 - The tor-tsocks.conf is no longer distributed or installed. We
820 recommend that tsocks users use torsocks instead. Resolves
824 Changes in version 0.2.4.11-alpha - 2013-03-11
825 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
826 more robust, makes hidden service authentication work again, and
827 resolves a DPI fingerprint for Tor's SSL transport.
829 o Major features (directory authorities):
830 - Directory authorities now support a new consensus method (17)
831 where they cap the published bandwidth of servers for which
832 insufficient bandwidth measurements exist. Fixes part of bug 2286.
833 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
834 serve any v2 directory information. Now we can test disabling the
835 old deprecated v2 directory format, and see whether doing so has
836 any effect on network load. Begins to fix bug 6783.
837 - Directory authorities now include inside each vote a statement of
838 the performance thresholds they used when assigning flags.
839 Implements ticket 8151.
841 o Major bugfixes (directory authorities):
842 - Stop marking every relay as having been down for one hour every
843 time we restart a directory authority. These artificial downtimes
844 were messing with our Stable and Guard flag calculations. Fixes
845 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
847 o Major bugfixes (hidden services):
848 - Allow hidden service authentication to succeed again. When we
849 refactored the hidden service introduction code back
850 in 0.2.4.1-alpha, we didn't update the code that checks
851 whether authentication information is present, causing all
852 authentication checks to return "false". Fix for bug 8207; bugfix
853 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
855 o Minor features (relays, bridges):
856 - Make bridge relays check once a minute for whether their IP
857 address has changed, rather than only every 15 minutes. Resolves
859 - Refactor resolve_my_address() so it returns the method by which we
860 decided our public IP address (explicitly configured, resolved from
861 explicit hostname, guessed from interfaces, learned by gethostname).
862 Now we can provide more helpful log messages when a relay guesses
863 its IP address incorrectly (e.g. due to unexpected lines in
864 /etc/hosts). Resolves ticket 2267.
865 - Teach bridge-using clients to avoid 0.2.2 bridges when making
866 microdescriptor-related dir requests, and only fall back to normal
867 descriptors if none of their bridges can handle microdescriptors
868 (as opposed to the fix in ticket 4013, which caused them to fall
869 back to normal descriptors if *any* of their bridges preferred
870 them). Resolves ticket 4994.
871 - Randomize the lifetime of our SSL link certificate, so censors can't
872 use the static value for filtering Tor flows. Resolves ticket 8443;
873 related to ticket 4014 which was included in 0.2.2.33.
875 o Minor features (portability):
876 - Tweak the curve25519-donna*.c implementations to tolerate systems
877 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
878 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
879 the signs of types during autoconf. This is better than our old
880 approach, which didn't work when cross-compiling.
881 - Detect the sign of enum values, rather than assuming that MSC is the
882 only compiler where enum types are all signed. Fixes bug 7727;
883 bugfix on 0.2.4.10-alpha.
885 o Minor features (other):
886 - Say "KBytes" rather than "KB" in the man page (for various values
887 of K), to further reduce confusion about whether Tor counts in
888 units of memory or fractions of units of memory. Resolves ticket 7054.
889 - Clear the high bit on curve25519 public keys before passing them to
890 our backend, in case we ever wind up using a backend that doesn't do
891 so itself. If we used such a backend, and *didn't* clear the high bit,
892 we could wind up in a situation where users with such backends would
893 be distinguishable from users without. Fixes bug 8121; bugfix on
895 - Update to the March 6 2013 Maxmind GeoLite Country database.
897 o Minor bugfixes (clients):
898 - When we receive a RELAY_END cell with the reason DONE, or with no
899 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
900 status as "connection refused". Previously we reported these cases
901 as success but then immediately closed the connection. Fixes bug
902 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
903 - Downgrade an assertion in connection_ap_expire_beginning to an
904 LD_BUG message. The fix for bug 8024 should prevent this message
905 from displaying, but just in case, a warn that we can diagnose
906 is better than more assert crashes. Fixes bug 8065; bugfix on
908 - Lower path use bias thresholds to .80 for notice and .60 for warn.
909 Also make the rate limiting flags for the path use bias log messages
910 independent from the original path bias flags. Fixes bug 8161;
911 bugfix on 0.2.4.10-alpha.
913 o Minor bugfixes (relays):
914 - Stop trying to resolve our hostname so often (e.g. every time we
915 think about doing a directory fetch). Now we reuse the cached
916 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
917 and 2410 (bugfix on 0.1.2.2-alpha).
918 - Stop sending a stray "(null)" in some cases for the server status
919 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
921 - When choosing which stream on a formerly stalled circuit to wake
922 first, make better use of the platform's weak RNG. Previously,
923 we had been using the % ("modulo") operator to try to generate a
924 1/N chance of picking each stream, but this behaves badly with
925 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
927 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
928 Irix's random() only return 15 bits; Solaris's random() returns more
929 bits but its RAND_MAX says it only returns 15, and so on. Motivated
930 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
932 o Minor bugfixes (directory authorities):
933 - Directory authorities now use less space when formatting identical
934 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
937 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
938 - Avoid leaking memory if we fail to compute a consensus signature
939 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
940 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
942 - Fix a memory leak during safe-cookie controller authentication.
943 Bugfix on 0.2.3.13-alpha.
944 - Avoid memory leak of IPv6 policy content if we fail to format it into
945 a router descriptor. Bugfix on 0.2.4.7-alpha.
947 o Minor bugfixes (other code correctness issues):
948 - Avoid a crash if we fail to generate an extrainfo descriptor.
949 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
951 - When detecting the largest possible file descriptor (in order to
952 close all file descriptors when launching a new program), actually
953 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
954 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
956 - Fix a copy-and-paste error when adding a missing A1 to a routerset
957 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
958 Bugfix on 0.2.4.10-alpha.
959 - Fix an impossible-to-trigger integer overflow when estimating how
960 long our onionskin queue would take. (This overflow would require us
961 to accept 4 million onionskins before processing 100 of them.) Fixes
962 bug 8210; bugfix on 0.2.4.10-alpha.
964 o Code simplification and refactoring:
965 - Add a wrapper function for the common "log a message with a
969 Changes in version 0.2.4.10-alpha - 2013-02-04
970 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
971 certain attacks that flood the network with relays; changes the queue
972 for circuit create requests from a sized-based limit to a time-based
973 limit; resumes building with MSVC on Windows; and fixes a wide variety
976 o Major bugfixes (directory authority):
977 - When computing directory thresholds, ignore any rejected-as-sybil
978 nodes during the computation so that they can't influence Fast,
979 Guard, etc. (We should have done this for proposal 109.) Fixes
981 - When marking a node as a likely sybil, reset its uptime metrics
982 to zero, so that it cannot time towards getting marked as Guard,
983 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
987 - When a TLS write is partially successful but incomplete, remember
988 that the flushed part has been flushed, and notice that bytes were
989 actually written. Reported and fixed pseudonymously. Fixes bug
990 7708; bugfix on Tor 0.1.0.5-rc.
991 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
992 ID: these could be used to create unexpected streams and circuits
993 which would count as "present" to some parts of Tor but "absent"
994 to others, leading to zombie circuits and streams or to a bandwidth
995 denial-of-service. Fixes bug 7889; bugfix on every released version
996 of Tor. Reported by "oftc_must_be_destroyed".
997 - Rename all macros in our local copy of queue.h to begin with "TOR_".
998 This change seems the only good way to permanently prevent conflicts
999 with queue.h on various operating systems. Fixes bug 8107; bugfix
1002 o Major features (relay):
1003 - Instead of limiting the number of queued onionskins (aka circuit
1004 create requests) to a fixed, hard-to-configure number, we limit
1005 the size of the queue based on how many we expect to be able to
1006 process in a given amount of time. We estimate the time it will
1007 take to process an onionskin based on average processing time
1008 of previous onionskins. Closes ticket 7291. You'll never have to
1009 configure MaxOnionsPending again.
1011 o Major features (portability):
1012 - Resume building correctly with MSVC and Makefile.nmake. This patch
1013 resolves numerous bugs and fixes reported by ultramage, including
1014 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
1015 - Make the ntor and curve25519 code build correctly with MSVC.
1016 Fix on 0.2.4.8-alpha.
1019 - When directory authorities are computing thresholds for flags,
1020 never let the threshold for the Fast flag fall below 4096
1021 bytes. Also, do not consider nodes with extremely low bandwidths
1022 when deciding thresholds for various directory flags. This change
1023 should raise our threshold for Fast relays, possibly in turn
1024 improving overall network performance; see ticket 1854. Resolves
1026 - The Tor client now ignores sub-domain components of a .onion
1027 address. This change makes HTTP "virtual" hosting
1028 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
1029 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
1030 hosted on the same hidden service. Implements proposal 204.
1031 - We compute the overhead from passing onionskins back and forth to
1032 cpuworkers, and report it when dumping statistics in response to
1033 SIGUSR1. Supports ticket 7291.
1035 o Minor features (path selection):
1036 - When deciding whether we have enough descriptors to build circuits,
1037 instead of looking at raw relay counts, look at which fraction
1038 of (bandwidth-weighted) paths we're able to build. This approach
1039 keeps clients from building circuits if their paths are likely to
1040 stand out statistically. The default fraction of paths needed is
1041 taken from the consensus directory; you can override it with the
1042 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
1043 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
1044 and we have GeoIP information, also exclude all nodes with unknown
1045 countries "??" and "A1". This behavior is controlled by the
1046 new GeoIPExcludeUnknown option: you can make such nodes always
1047 excluded with "GeoIPExcludeUnknown 1", and disable the feature
1048 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
1049 gets you the default behavior. Implements feature 7706.
1050 - Path Use Bias: Perform separate accounting for successful circuit
1051 use. Keep separate statistics on stream attempt rates versus stream
1052 success rates for each guard. Provide configurable thresholds to
1053 determine when to emit log messages or disable use of guards that
1054 fail too many stream attempts. Resolves ticket 7802.
1056 o Minor features (log messages):
1057 - When learning a fingerprint for a bridge, log its corresponding
1058 transport type. Implements ticket 7896.
1059 - Improve the log message when "Bug/attack: unexpected sendme cell
1060 from client" occurs, to help us track bug 8093.
1063 - Remove a couple of extraneous semicolons that were upsetting the
1064 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
1065 bugfix on 0.2.2.1-alpha.
1066 - Remove a source of rounding error during path bias count scaling;
1067 don't count cannibalized circuits as used for path bias until we
1068 actually try to use them; and fix a circuit_package_relay_cell()
1069 warning message about n_chan==NULL. Fixes bug 7802.
1070 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
1071 actually link against nacl when we're configured to use it. Fixes
1072 bug 7972; bugfix on 0.2.4.8-alpha.
1073 - Compile correctly with the --disable-curve25519 option. Fixes
1074 bug 8153; bugfix on 0.2.4.8-alpha.
1076 o Build improvements:
1077 - Do not report status verbosely from autogen.sh unless the -v flag
1078 is specified. Fixes issue 4664. Patch from Onizuka.
1079 - Replace all calls to snprintf() outside of src/ext with
1080 tor_snprintf(). Also remove the #define to replace snprintf with
1081 _snprintf on Windows; they have different semantics, and all of
1082 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
1083 - Try to detect if we are ever building on a platform where
1084 memset(...,0,...) does not set the value of a double to 0.0. Such
1085 platforms are permitted by the C standard, though in practice
1086 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
1087 currently support them, but it's better to detect them and fail
1088 than to perform erroneously.
1091 - Stop exporting estimates of v2 and v3 directory traffic shares
1092 in extrainfo documents. They were unneeded and sometimes inaccurate.
1093 Also stop exporting any v2 directory request statistics. Resolves
1095 - Drop support for detecting and warning about versions of Libevent
1096 before 1.3e. Nothing reasonable ships with them any longer;
1097 warning the user about them shouldn't be needed. Resolves ticket
1100 o Code simplifications and refactoring:
1101 - Rename "isin" functions to "contains", for grammar. Resolves
1103 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
1104 with the natural logarithm function from the system libm. Resolves
1108 Changes in version 0.2.4.9-alpha - 2013-01-15
1109 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
1113 - Fix backward compatibility logic when receiving an embedded ntor
1114 handshake tunneled in a CREATE cell. This clears up the "Bug:
1115 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
1119 Changes in version 0.2.4.8-alpha - 2013-01-14
1120 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
1121 risks, adds a new stronger and faster circuit handshake, and offers
1122 stronger and faster link encryption when both sides support it.
1125 - Preliminary support for directory guards (proposal 207): when
1126 possible, clients now use their entry guards for non-anonymous
1127 directory requests. This can help prevent client enumeration. Note
1128 that this behavior only works when we have a usable consensus
1129 directory, and when options about what to download are more or less
1130 standard. In the future we should re-bootstrap from our guards,
1131 rather than re-bootstrapping from the preconfigured list of
1132 directory sources that ships with Tor. Resolves ticket 6526.
1133 - Tor relays and clients now support a better CREATE/EXTEND cell
1134 format, allowing the sender to specify multiple address, identity,
1135 and handshake types. Implements Robert Ransom's proposal 200;
1138 o Major features (new circuit handshake):
1139 - Tor now supports a new circuit extension handshake designed by Ian
1140 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
1141 circuit extension handshake, later called "TAP", was a bit slow
1142 (especially on the relay side), had a fragile security proof, and
1143 used weaker keys than we'd now prefer. The new circuit handshake
1144 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
1145 function, making it significantly more secure than the older
1146 handshake, and significantly faster. Tor can use one of two built-in
1147 pure-C curve25519-donna implementations by Adam Langley, or it
1148 can link against the "nacl" library for a tuned version if present.
1150 The built-in version is very fast for 64-bit systems when building
1151 with GCC. The built-in 32-bit version is still faster than the
1152 old TAP protocol, but using libnacl is better on most such hosts.
1154 Clients don't currently use this protocol by default, since
1155 comparatively few clients support it so far. To try it, set
1156 UseNTorHandshake to 1.
1158 Implements proposal 216; closes ticket 7202.
1160 o Major features (better link encryption):
1161 - Relays can now enable the ECDHE TLS ciphersuites when available
1162 and appropriate. These ciphersuites let us negotiate forward-secure
1163 TLS secret keys more safely and more efficiently than with our
1164 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
1165 public relays prefer the (faster) P224 group, and bridges prefer
1166 the (more common) P256 group; you can override this with the
1169 Enabling these ciphers was a little tricky, since for a long time,
1170 clients had been claiming to support them without actually doing
1171 so, in order to foil fingerprinting. But with the client-side
1172 implementation of proposal 198 in 0.2.3.17-beta, clients can now
1173 match the ciphers from recent Firefox versions *and* list the
1174 ciphers they actually mean, so relays can believe such clients
1175 when they advertise ECDHE support in their TLS ClientHello messages.
1177 This feature requires clients running 0.2.3.17-beta or later,
1178 and requires both sides to be running OpenSSL 1.0.0 or later
1179 with ECC support. OpenSSL 1.0.1, with the compile-time option
1180 "enable-ec_nistp_64_gcc_128", is highly recommended.
1182 Implements the relay side of proposal 198; closes ticket 7200.
1185 - Avoid crashing when, as a relay without IPv6-exit support, a
1186 client insists on getting an IPv6 address or nothing. Fixes bug
1187 7814; bugfix on 0.2.4.7-alpha.
1190 - Improve circuit build timeout handling for hidden services.
1191 In particular: adjust build timeouts more accurately depending
1192 upon the number of hop-RTTs that a particular circuit type
1193 undergoes. Additionally, launch intro circuits in parallel
1194 if they timeout, and take the first one to reply as valid.
1195 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
1196 separate error codes; or at least, don't break for that reason.
1197 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
1198 - Update to the January 2 2013 Maxmind GeoLite Country database.
1200 o Minor features (testing):
1201 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
1202 (P-256) Diffie-Hellman handshakes to src/or/bench.
1203 - Add benchmark functions to test onion handshake performance.
1205 o Minor features (path bias detection):
1206 - Alter the Path Bias log messages to be more descriptive in terms
1207 of reporting timeouts and other statistics.
1208 - Create three levels of Path Bias log messages, as opposed to just
1209 two. These are configurable via consensus as well as via the torrc
1210 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
1211 The default values are 0.70, 0.50, and 0.30 respectively.
1212 - Separate the log message levels from the decision to drop guards,
1213 which also is available via torrc option PathBiasDropGuards.
1214 PathBiasDropGuards still defaults to 0 (off).
1215 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
1216 in combination with PathBiasExtremeRate.
1217 - Increase the default values for PathBiasScaleThreshold and
1218 PathBiasCircThreshold from (200, 20) to (300, 150).
1219 - Add in circuit usage accounting to path bias. If we try to use a
1220 built circuit but fail for any reason, it counts as path bias.
1221 Certain classes of circuits where the adversary gets to pick your
1222 destination node are exempt from this accounting. Usage accounting
1223 can be specifically disabled via consensus parameter or torrc.
1224 - Convert all internal path bias state to double-precision floating
1225 point, to avoid roundoff error and other issues.
1226 - Only record path bias information for circuits that have completed
1227 *two* hops. Assuming end-to-end tagging is the attack vector, this
1228 makes us more resilient to ambient circuit failure without any
1229 detection capability loss.
1231 o Minor bugfixes (log messages):
1232 - Rate-limit the "No circuits are opened. Relaxed timeout for a
1233 circuit with channel state open..." message to once per hour to
1234 keep it from filling the notice logs. Mitigates bug 7799 but does
1235 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
1236 - Avoid spurious warnings when configuring multiple client ports of
1237 which only some are nonlocal. Previously, we had claimed that some
1238 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
1241 o Code simplifications and refactoring:
1242 - Get rid of a couple of harmless clang warnings, where we compared
1243 enums to ints. These warnings are newly introduced in clang 3.2.
1244 - Split the onion.c file into separate modules for the onion queue
1245 and the different handshakes it supports.
1246 - Remove the marshalling/unmarshalling code for sending requests to
1247 cpuworkers over a socket, and instead just send structs. The
1248 recipient will always be the same Tor binary as the sender, so
1249 any encoding is overkill.
1252 Changes in version 0.2.4.7-alpha - 2012-12-24
1253 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
1254 directory mirrors for more robust bootstrapping; fixes more issues where
1255 clients with changing network conditions refuse to make any circuits;
1256 adds initial support for exiting to IPv6 addresses; resumes being able
1257 to update our GeoIP database, and includes the geoip6 file this time;
1258 turns off the client-side DNS cache by default due to privacy risks;
1259 and fixes a variety of other issues.
1261 o Major features (client resilience):
1262 - Add a new "FallbackDir" torrc option to use when we can't use
1263 a directory mirror from the consensus (either because we lack a
1264 consensus, or because they're all down). Currently, all authorities
1265 are fallbacks by default, and there are no other default fallbacks,
1266 but that will change. This option will allow us to give clients a
1267 longer list of servers to try to get a consensus from when first
1268 connecting to the Tor network, and thereby reduce load on the
1269 directory authorities. Implements proposal 206, "Preconfigured
1270 directory sources for bootstrapping". We also removed the old
1271 "FallbackNetworkstatus" option, since we never got it working well
1272 enough to use it. Closes bug 572.
1273 - If we have no circuits open, use a relaxed timeout (the
1274 95-percentile cutoff) until a circuit succeeds. This heuristic
1275 should allow Tor to succeed at building circuits even when the
1276 network connection drastically changes. Should help with bug 3443.
1278 o Major features (IPv6):
1279 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
1280 connectivity, then set the IPv6Exit flag to 1. Also make sure your
1281 exit policy reads as you would like: the address * applies to all
1282 address families, whereas *4 is IPv4 address only, and *6 is IPv6
1283 addresses only. On the client side, you'll need to wait until the
1284 authorities have upgraded, wait for enough exits to support IPv6,
1285 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
1286 ticket 5547, implements proposal 117 as revised in proposal 208.
1288 We DO NOT recommend that clients with actual anonymity needs start
1289 using IPv6 over Tor yet, since not enough exits support it yet.
1291 o Major features (geoip database):
1292 - Maxmind began labelling Tor relays as being in country "A1",
1293 which breaks by-country node selection inside Tor. Now we use a
1294 script to replace "A1" ("Anonymous Proxy") entries in our geoip
1295 file with real country codes. This script fixes about 90% of "A1"
1296 entries automatically and uses manual country code assignments to
1297 fix the remaining 10%. See src/config/README.geoip for details.
1298 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
1299 Country database, as modified above.
1301 o Major bugfixes (client-side DNS):
1302 - Turn off the client-side DNS cache by default. Updating and using
1303 the DNS cache is now configurable on a per-client-port
1304 level. SOCKSPort, DNSPort, etc lines may now contain
1305 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
1306 cache these types of DNS answers when we receive them from an
1307 exit node in response to an application request on this port, and
1308 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
1309 cached DNS answers of these types, we shouldn't use them. It's
1310 potentially risky to use cached DNS answers at the client, since
1311 doing so can indicate to one exit what answers we've gotten
1312 for DNS lookups in the past. With IPv6, this becomes especially
1313 problematic. Using cached DNS answers for requests on the same
1314 circuit would present less linkability risk, since all traffic
1315 on a circuit is already linkable, but it would also provide
1316 little performance benefit: the exit node caches DNS replies
1317 too. Implements a simplified version of Proposal 205. Implements
1320 o Major bugfixes (other):
1321 - Alter circuit build timeout measurement to start at the point
1322 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
1323 initialization). This should make our timeout measurements more
1324 uniform. Previously, we were sometimes including ORconn setup time
1325 in our circuit build time measurements. Should resolve bug 3443.
1326 - Fix an assertion that could trigger in hibernate_go_dormant() when
1327 closing an or_connection_t: call channel_mark_for_close() rather
1328 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
1330 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
1331 7655; bugfix on 0.2.4.6-alpha.
1334 - Add a new torrc option "ServerTransportListenAddr" to let bridge
1335 operators select the address where their pluggable transports will
1336 listen for connections. Resolves ticket 7013.
1337 - Allow an optional $ before the node identity digest in the
1338 controller command GETINFO ns/id/<identity>, for consistency with
1339 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
1340 - Log packaged cell fullness as part of the heartbeat message.
1341 Diagnosis to try to determine the extent of bug 7743.
1343 o Minor features (IPv6):
1344 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
1345 prefer to hand out virtual IPv6 addresses, since there are more of
1346 them and we can't run out. To override this behavior and make IPv4
1347 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
1348 or DNSPort you're using for resolving. Implements ticket 7571.
1349 - AutomapHostsOnResolve responses are now randomized, to avoid
1350 annoying situations where Tor is restarted and applications
1351 connect to the wrong addresses.
1352 - Never try more than 1000 times to pick a new virtual address when
1353 AutomapHostsOnResolve is set. That's good enough so long as we
1354 aren't close to handing out our entire virtual address space;
1355 if you're getting there, it's best to switch to IPv6 virtual
1359 - The ADDRMAP command can no longer generate an ill-formed error
1360 code on a failed MAPADDRESS. It now says "internal" rather than
1361 an English sentence fragment with spaces in the middle. Bugfix on
1363 - Fix log messages and comments to avoid saying "GMT" when we mean
1364 "UTC". Fixes bug 6113.
1365 - Compile on win64 using mingw64. Fixes bug 7260; patches from
1367 - Fix a crash when debugging unit tests on Windows: deallocate a
1368 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
1369 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
1372 - The DirServer option is now DirAuthority, for consistency with
1373 current naming patterns. You can still use the old DirServer form.
1375 o Code simplification and refactoring:
1376 - Move the client-side address-map/virtual-address/DNS-cache code
1377 out of connection_edge.c into a new addressmap.c module.
1378 - Remove unused code for parsing v1 directories and "running routers"
1379 documents. Fixes bug 6887.
1382 Changes in version 0.2.3.25 - 2012-11-19
1383 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
1384 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
1385 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
1386 programmer, and friend. Unstinting in his dedication to the cause of
1387 freedom, he inspired and helped many of us as we began our work on
1388 anonymity, and inspires us still. Please honor his memory by writing
1389 software to protect people's freedoms, and by helping others to do so.
1391 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
1392 significantly reduced directory overhead (via microdescriptors),
1393 enormous crypto performance improvements for fast relays on new
1394 enough hardware, a new v3 TLS handshake protocol that can better
1395 resist fingerprinting, support for protocol obfuscation plugins (aka
1396 pluggable transports), better scalability for hidden services, IPv6
1397 support for bridges, performance improvements like allowing clients
1398 to skip the first round-trip on the circuit ("optimistic data") and
1399 refilling token buckets more often, a new "stream isolation" design
1400 to isolate different applications on different circuits, and many
1401 stability, security, and privacy fixes.
1404 - Tor tries to wipe potentially sensitive data after using it, so
1405 that if some subsequent security failure exposes Tor's memory,
1406 the damage will be limited. But we had a bug where the compiler
1407 was eliminating these wipe operations when it decided that the
1408 memory was no longer visible to a (correctly running) program,
1409 hence defeating our attempt at defense in depth. We fix that
1410 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1411 is unlikely to optimize away. Future versions of Tor may use
1412 a less ridiculously heavy approach for this. Fixes bug 7352.
1413 Reported in an article by Andrey Karpov.
1416 - Fix a harmless bug when opting against publishing a relay descriptor
1417 because DisableNetwork is set. Fixes bug 7464; bugfix on
1421 Changes in version 0.2.4.6-alpha - 2012-11-13
1422 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
1423 makes our defense-in-depth memory wiping more reliable, and begins to
1424 count IPv6 addresses in bridge statistics,
1427 - Fix an assertion failure that could occur when closing a connection
1428 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
1430 - Tor tries to wipe potentially sensitive data after using it, so
1431 that if some subsequent security failure exposes Tor's memory,
1432 the damage will be limited. But we had a bug where the compiler
1433 was eliminating these wipe operations when it decided that the
1434 memory was no longer visible to a (correctly running) program,
1435 hence defeating our attempt at defense in depth. We fix that
1436 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1437 is unlikely to optimize away. Future versions of Tor may use
1438 a less ridiculously heavy approach for this. Fixes bug 7352.
1439 Reported in an article by Andrey Karpov.
1442 - Add GeoIP database for IPv6 addresses. The new config option
1444 - Bridge statistics now count bridge clients connecting over IPv6:
1445 bridge statistics files now list "bridge-ip-versions" and
1446 extra-info documents list "geoip6-db-digest". The control protocol
1447 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
1448 implementation by "shkoo", addressing ticket 5055.
1451 - Warn when we are binding low ports when hibernation is enabled;
1452 previously we had warned when we were _advertising_ low ports with
1453 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
1454 - Fix a harmless bug when opting against publishing a relay descriptor
1455 because DisableNetwork is set. Fixes bug 7464; bugfix on
1457 - Add warning message when a managed proxy dies during configuration.
1458 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
1459 - Fix a linking error when building tor-fw-helper without miniupnp.
1460 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
1461 - Check for closing an or_connection_t without going through correct
1462 channel functions; emit a warning and then call
1463 connection_or_close_for_error() so we don't assert as in bugs 7212
1465 - Compile correctly on compilers without C99 designated initializer
1466 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
1467 - Avoid a possible assert that can occur when channel_send_destroy() is
1468 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
1469 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
1470 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
1471 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
1472 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
1474 o Code simplification and refactoring:
1475 - Start using OpenBSD's implementation of queue.h, so that we don't
1476 need to hand-roll our own pointer and list structures whenever we
1477 need them. (We can't rely on a sys/queue.h, since some operating
1478 systems don't have them, and the ones that do have them don't all
1479 present the same extensions.)
1482 Changes in version 0.2.4.5-alpha - 2012-10-25
1483 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
1484 two important security vulnerabilities that could lead to remotely
1485 triggerable relay crashes, fix a major bug that was preventing clients
1486 from choosing suitable exit nodes, and refactor some of our code.
1488 o Major bugfixes (security, also in 0.2.3.24-rc):
1489 - Fix a group of remotely triggerable assertion failures related to
1490 incorrect link protocol negotiation. Found, diagnosed, and fixed
1491 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1493 - Fix a denial of service attack by which any directory authority
1494 could crash all the others, or by which a single v2 directory
1495 authority could crash everybody downloading v2 directory
1496 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1498 o Major bugfixes (also in 0.2.3.24-rc):
1499 - When parsing exit policy summaries from microdescriptors, we had
1500 previously been ignoring the last character in each one, so that
1501 "accept 80,443,8080" would be treated by clients as indicating
1502 a node that allows access to ports 80, 443, and 808. That would
1503 lead to clients attempting connections that could never work,
1504 and ignoring exit nodes that would support their connections. Now
1505 clients parse these exit policy summaries correctly. Fixes bug 7192;
1506 bugfix on 0.2.3.1-alpha.
1508 o Minor bugfixes (also in 0.2.3.24-rc):
1509 - Clients now consider the ClientRejectInternalAddresses config option
1510 when using a microdescriptor consensus stanza to decide whether
1511 an exit relay would allow exiting to an internal address. Fixes
1512 bug 7190; bugfix on 0.2.3.1-alpha.
1515 - Only disable TLS session ticket support when running as a TLS
1516 server. Now clients will blend better with regular Firefox
1517 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
1519 o Code simplification and refactoring:
1520 - Start using OpenBSD's implementation of queue.h (originally by
1522 - Move the entry node code from circuitbuild.c to its own file.
1523 - Move the circuit build timeout tracking code from circuitbuild.c
1527 Changes in version 0.2.3.24-rc - 2012-10-25
1528 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
1529 could lead to remotely triggerable relay crashes, and fixes
1530 a major bug that was preventing clients from choosing suitable exit
1533 o Major bugfixes (security):
1534 - Fix a group of remotely triggerable assertion failures related to
1535 incorrect link protocol negotiation. Found, diagnosed, and fixed
1536 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1538 - Fix a denial of service attack by which any directory authority
1539 could crash all the others, or by which a single v2 directory
1540 authority could crash everybody downloading v2 directory
1541 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1544 - When parsing exit policy summaries from microdescriptors, we had
1545 previously been ignoring the last character in each one, so that
1546 "accept 80,443,8080" would be treated by clients as indicating
1547 a node that allows access to ports 80, 443, and 808. That would
1548 lead to clients attempting connections that could never work,
1549 and ignoring exit nodes that would support their connections. Now
1550 clients parse these exit policy summaries correctly. Fixes bug 7192;
1551 bugfix on 0.2.3.1-alpha.
1554 - Clients now consider the ClientRejectInternalAddresses config option
1555 when using a microdescriptor consensus stanza to decide whether
1556 an exit relay would allow exiting to an internal address. Fixes
1557 bug 7190; bugfix on 0.2.3.1-alpha.
1560 Changes in version 0.2.4.4-alpha - 2012-10-20
1561 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
1562 vulnerability introduced by a change in OpenSSL, fixes a remotely
1563 triggerable assert, and adds new channel_t and circuitmux_t abstractions
1564 that will make it easier to test new connection transport and cell
1565 scheduling algorithms.
1567 o New directory authorities (also in 0.2.3.23-rc):
1568 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1569 authority. Closes ticket 5749.
1571 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
1572 - Disable TLS session tickets. OpenSSL's implementation was giving
1573 our TLS session keys the lifetime of our TLS context objects, when
1574 perfect forward secrecy would want us to discard anything that
1575 could decrypt a link connection as soon as the link connection
1576 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1577 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1578 - Discard extraneous renegotiation attempts once the V3 link
1579 protocol has been initiated. Failure to do so left us open to
1580 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1581 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1583 o Internal abstraction features:
1584 - Introduce new channel_t abstraction between circuits and
1585 or_connection_t to allow for implementing alternate OR-to-OR
1586 transports. A channel_t is an abstract object which can either be a
1587 cell-bearing channel, which is responsible for authenticating and
1588 handshaking with the remote OR and transmitting cells to and from
1589 it, or a listening channel, which spawns new cell-bearing channels
1590 at the request of remote ORs. Implements part of ticket 6465.
1591 - Also new is the channel_tls_t subclass of channel_t, adapting it
1592 to the existing or_connection_t code. The V2/V3 protocol handshaking
1593 code which formerly resided in command.c has been moved below the
1594 channel_t abstraction layer and may be found in channeltls.c now.
1595 Implements the rest of ticket 6465.
1596 - Introduce new circuitmux_t storing the queue of circuits for
1597 a channel; this encapsulates and abstracts the queue logic and
1598 circuit selection policy, and allows the latter to be overridden
1599 easily by switching out a policy object. The existing EWMA behavior
1600 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
1602 o Required libraries:
1603 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
1604 strongly recommended.
1607 - Warn users who run hidden services on a Tor client with
1608 UseEntryGuards disabled that their hidden services will be
1609 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
1610 attack which motivated Tor to support entry guards in the first
1611 place). Resolves ticket 6889.
1612 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
1613 dhill. Resolves ticket 6982.
1614 - Option OutboundBindAddress can be specified multiple times and
1615 accepts IPv6 addresses. Resolves ticket 6876.
1617 o Minor bugfixes (also in 0.2.3.23-rc):
1618 - Don't serve or accept v2 hidden service descriptors over a
1619 relay's DirPort. It's never correct to do so, and disabling it
1620 might make it more annoying to exploit any bugs that turn up in the
1621 descriptor-parsing code. Fixes bug 7149.
1622 - Fix two cases in src/or/transports.c where we were calling
1623 fmt_addr() twice in a parameter list. Bug found by David
1624 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1625 - Fix memory leaks whenever we logged any message about the "path
1626 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1627 - When relays refuse a "create" cell because their queue of pending
1628 create cells is too big (typically because their cpu can't keep up
1629 with the arrival rate), send back reason "resource limit" rather
1630 than reason "internal", so network measurement scripts can get a
1631 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
1634 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
1635 - Free some more still-in-use memory at exit, to make hunting for
1636 memory leaks easier. Resolves bug 7029.
1637 - When a Tor client gets a "truncated" relay cell, the first byte of
1638 its payload specifies why the circuit was truncated. We were
1639 ignoring this 'reason' byte when tearing down the circuit, resulting
1640 in the controller not being told why the circuit closed. Now we
1641 pass the reason from the truncated cell to the controller. Bugfix
1642 on 0.1.2.3-alpha; fixes bug 7039.
1643 - Downgrade "Failed to hand off onionskin" messages to "debug"
1644 severity, since they're typically redundant with the "Your computer
1645 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
1646 - Make clients running with IPv6 bridges connect over IPv6 again,
1647 even without setting new config options ClientUseIPv6 and
1648 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
1649 - Use square brackets around IPv6 addresses in numerous places
1650 that needed them, including log messages, HTTPS CONNECT proxy
1651 requests, TransportProxy statefile entries, and pluggable transport
1652 extra-info lines. Fixes bug 7011; patch by David Fifield.
1654 o Code refactoring and cleanup:
1655 - Source files taken from other packages now reside in src/ext;
1656 previously they were scattered around the rest of Tor.
1657 - Avoid use of reserved identifiers in our C code. The C standard
1658 doesn't like us declaring anything that starts with an
1659 underscore, so let's knock it off before we get in trouble. Fix
1660 for bug 1031; bugfix on the first Tor commit.
1663 Changes in version 0.2.3.23-rc - 2012-10-20
1664 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
1665 vulnerability introduced by a change in OpenSSL, and fixes a variety
1666 of smaller bugs in preparation for the release.
1668 o New directory authorities:
1669 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1670 authority. Closes ticket 5749.
1672 o Major bugfixes (security/privacy):
1673 - Disable TLS session tickets. OpenSSL's implementation was giving
1674 our TLS session keys the lifetime of our TLS context objects, when
1675 perfect forward secrecy would want us to discard anything that
1676 could decrypt a link connection as soon as the link connection
1677 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1678 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1679 - Discard extraneous renegotiation attempts once the V3 link
1680 protocol has been initiated. Failure to do so left us open to
1681 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1682 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1685 - Fix a possible crash bug when checking for deactivated circuits
1686 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1687 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1689 o Minor bugfixes (on 0.2.3.x):
1690 - Fix two cases in src/or/transports.c where we were calling
1691 fmt_addr() twice in a parameter list. Bug found by David
1692 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1693 - Convert an assert in the pathbias code to a log message. The assert
1694 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1695 bugfix on 0.2.3.17-beta.
1696 - Fix memory leaks whenever we logged any message about the "path
1697 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1699 o Minor bugfixes (on 0.2.2.x and earlier):
1700 - Don't serve or accept v2 hidden service descriptors over a relay's
1701 DirPort. It's never correct to do so, and disabling it might
1702 make it more annoying to exploit any bugs that turn up in the
1703 descriptor-parsing code. Fixes bug 7149.
1704 - When relays refuse a "create" cell because their queue of pending
1705 create cells is too big (typically because their cpu can't keep up
1706 with the arrival rate), send back reason "resource limit" rather
1707 than reason "internal", so network measurement scripts can get a
1708 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
1709 - Correct file sizes when reading binary files on Cygwin, to avoid
1710 a bug where Tor would fail to read its state file. Fixes bug 6844;
1711 bugfix on 0.1.2.7-alpha.
1712 - Avoid undefined behaviour when parsing the list of supported
1713 rendezvous/introduction protocols in a hidden service descriptor.
1714 Previously, Tor would have confused (as-yet-unused) protocol version
1715 numbers greater than 32 with lower ones on many platforms. Fixes
1716 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1718 o Documentation fixes:
1719 - Clarify that hidden services are TCP only. Fixes bug 6024.
1722 Changes in version 0.2.4.3-alpha - 2012-09-22
1723 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
1724 assertion, resumes letting relays test reachability of their DirPort,
1725 and cleans up a bunch of smaller bugs.
1728 - Fix an assertion failure in tor_timegm() that could be triggered
1729 by a badly formatted directory object. Bug found by fuzzing with
1730 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1733 - Fix a possible crash bug when checking for deactivated circuits
1734 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1735 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1736 - Allow routers to detect that their own DirPorts are running. When
1737 we removed support for versions_supports_begindir, we also
1738 accidentally removed the mechanism we used to self-test our
1739 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
1740 bugfix on 0.2.4.2-alpha.
1742 o Security features:
1743 - Switch to a completely time-invariant approach for picking nodes
1744 weighted by bandwidth. Our old approach would run through the
1745 part of the loop after it had made its choice slightly slower
1746 than it ran through the part of the loop before it had made its
1747 choice. Addresses ticket 6538.
1748 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
1749 by tor2web clients allows hidden services to identify tor2web
1750 clients through their repeated selection of the same rendezvous
1751 and introduction point circuit endpoints (their guards). Resolves
1755 - Enable Tor to read configuration, state, and key information from
1756 a FIFO. Previously Tor would only read from files with a positive
1757 stat.st_size. Code from meejah; fixes bug 6044.
1760 - Correct file sizes when reading binary files on Cygwin, to avoid
1761 a bug where Tor would fail to read its state file. Fixes bug 6844;
1762 bugfix on 0.1.2.7-alpha.
1763 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
1764 bugfix on 0.2.0.3-alpha.
1765 - When complaining about a client port on a public address, log
1766 which address we're complaining about. Fixes bug 4020; bugfix on
1767 0.2.3.3-alpha. Patch by Tom Fitzhenry.
1768 - Convert an assert in the pathbias code to a log message. The assert
1769 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1770 bugfix on 0.2.3.17-beta.
1771 - Our new buildsystem was overzealous about rebuilding manpages: it
1772 would rebuild them all whenever any one of them changed. Now our
1773 dependency checking should be correct. Fixes bug 6843; bugfix on
1775 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
1776 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
1777 - Correct log printout about which address family is preferred
1778 when connecting to a bridge with both an IPv4 and IPv6 OR port.
1779 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
1781 o Minor bugfixes (code cleanliness):
1782 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
1783 with large values. This situation was untriggered, but nevertheless
1784 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
1785 - Reject consensus votes with more than 64 known-flags. We aren't even
1786 close to that limit yet, and our code doesn't handle it correctly.
1787 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
1788 - Avoid undefined behaviour when parsing the list of supported
1789 rendezvous/introduction protocols in a hidden service descriptor.
1790 Previously, Tor would have confused (as-yet-unused) protocol version
1791 numbers greater than 32 with lower ones on many platforms. Fixes
1792 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1793 - Fix handling of rendezvous client authorization types over 8.
1794 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
1795 - Fix building with older versions of GCC (2.95, for one) that don't
1796 like preprocessor directives inside macro arguments. Found by
1797 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
1798 - Switch weighted node selection rule from using a list of doubles
1799 to using a list of int64_t. This change should make the process
1800 slightly easier to debug and maintain. Needed to finish ticket 6538.
1802 o Code simplification and refactoring:
1803 - Move the generic "config" code into a new file, and have "config.c"
1804 hold only torrc- and state-related code. Resolves ticket 6823.
1805 - Move the core of our "choose a weighted element at random" logic
1806 into its own function, and give it unit tests. Now the logic is
1807 testable, and a little less fragile too.
1808 - Removed the testing_since field of node_t, which hasn't been used
1809 for anything since 0.2.0.9-alpha.
1811 o Documentation fixes:
1812 - Clarify that hidden services are TCP only. Fixes bug 6024.
1813 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
1817 Changes in version 0.2.3.22-rc - 2012-09-11
1818 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
1822 - Fix an assertion failure in tor_timegm() that could be triggered
1823 by a badly formatted directory object. Bug found by fuzzing with
1824 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1827 - Avoid segfault when starting up having run with an extremely old
1828 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1832 Changes in version 0.2.2.39 - 2012-09-11
1833 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
1837 - Fix an assertion failure in tor_timegm() that could be triggered
1838 by a badly formatted directory object. Bug found by fuzzing with
1839 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1840 - Do not crash when comparing an address with port value 0 to an
1841 address policy. This bug could have been used to cause a remote
1842 assertion failure by or against directory authorities, or to
1843 allow some applications to crash clients. Fixes bug 6690; bugfix
1847 Changes in version 0.2.4.2-alpha - 2012-09-10
1848 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
1849 raises the default rate limiting even more, and makes the bootstrapping
1850 log messages less noisy.
1853 - Automatically forward the TCP ports of pluggable transport
1854 proxies using tor-fw-helper if PortForwarding is enabled. Implements
1858 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
1859 to 1GB/1GB. The previous defaults were intended to be "basically
1860 infinite", but it turns out they're now limiting our 100mbit+
1861 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
1862 last time we raised it).
1865 - Detect when we're running with a version of OpenSSL other than the
1866 one we compiled with. This has occasionally given people hard-to-
1868 - Log fewer lines at level "notice" about our OpenSSL and Libevent
1869 versions and capabilities when everything is going right. Resolves
1870 part of ticket 6736.
1871 - Directory authorities no long accept descriptors for any version of
1872 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
1873 These versions are insecure, unsupported, or both. Implements
1877 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
1878 to start with a triple-underscore so the controller won't touch it.
1879 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
1880 - Avoid segfault when starting up having run with an extremely old
1881 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1883 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
1884 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
1885 - Don't follow the NULL pointer if microdescriptor generation fails.
1886 (This does not appear to be triggerable, but it's best to be safe.)
1887 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
1888 - Fix mis-declared dependencies on src/common/crypto.c and
1889 src/or/tor_main.c that could break out-of-tree builds under some
1890 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
1891 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
1892 6778; bugfix on 0.2.4.1-alpha.
1893 - Fix a harmless (in this case) build warning for implicitly
1894 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
1897 - Now that all versions before 0.2.2.x are disallowed, we no longer
1898 need to work around their missing features. Thus we can remove a
1899 bunch of compatibility code.
1902 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
1903 TCP ports to forward. In the past it only accepted two ports:
1904 the ORPort and the DirPort.
1907 Changes in version 0.2.4.1-alpha - 2012-09-05
1908 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
1909 bridgedb; lets relays use IPv6 addresses and directory authorities
1910 advertise them; and switches to a cleaner build interface.
1912 This is the first alpha release in a new series, so expect there to
1913 be bugs. Users who would rather test out a more stable branch should
1914 stay with 0.2.3.x for now.
1916 o Major features (bridges):
1917 - Bridges now report the pluggable transports they support to the
1918 bridge authority, so it can pass the supported transports on to
1919 bridgedb and/or eventually do reachability testing. Implements
1922 o Major features (IPv6):
1923 - Bridge authorities now accept IPv6 bridge addresses and include
1924 them in network status documents. Implements ticket 5534.
1925 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
1926 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
1927 to happen. Implements ticket 5535.
1928 - All kind of relays, not just bridges, can now advertise an IPv6
1929 OR port. Implements ticket 6362.
1930 - Directory authorities vote on IPv6 OR ports using the new consensus
1931 method 14. Implements ticket 6363.
1933 o Major features (build):
1934 - Switch to a nonrecursive Makefile structure. Now instead of each
1935 Makefile.am invoking other Makefile.am's, there is a master
1936 Makefile.am that includes the others. This change makes our build
1937 process slightly more maintainable, and improves parallelism for
1938 building with make -j. Original patch by Stewart Smith; various
1939 fixes by Jim Meyering.
1940 - Where available, we now use automake's "silent" make rules by
1941 default, so that warnings are easier to spot. You can get the old
1942 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
1944 o Minor features (code security and spec conformance):
1945 - Clear keys and key-derived material left on the stack in
1946 rendservice.c and rendclient.c. Check return value of
1947 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
1948 These fixes should make us more forward-secure against cold-boot
1949 attacks and the like. Fixes bug 2385.
1950 - Reject EXTEND cells sent to nonexistent streams. According to the
1951 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
1952 we were only checking for stream IDs that were currently in use.
1953 Found while hunting for more instances of bug 6271. Bugfix on
1954 0.0.2pre8, which introduced incremental circuit construction.
1956 o Minor features (streamlining);
1957 - No longer include the "opt" prefix when generating routerinfos
1958 or v2 directories: it has been needless since Tor 0.1.2. Closes
1960 - Remove some now-needless code that tried to aggressively flush
1961 OR connections as data was added to them. Since 0.2.0.1-alpha, our
1962 cell queue logic has saved us from the failure mode that this code
1963 was supposed to prevent. Removing this code will limit the number
1964 of baroque control flow paths through Tor's network logic. Reported
1965 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
1967 o Minor features (controller):
1968 - Add a "GETINFO signal/names" control port command. Implements
1970 - Provide default values for all options via "GETINFO config/defaults".
1971 Implements ticket 4971.
1973 o Minor features (IPv6):
1974 - New config option "AuthDirHasIPv6Connectivity 1" that directory
1975 authorities should set if they have IPv6 connectivity and want to
1976 do reachability tests for IPv6 relays. Implements feature 5974.
1977 - A relay with an IPv6 OR port now sends that address in NETINFO
1978 cells (in addition to its other address). Implements ticket 6364.
1980 o Minor features (log messages):
1981 - Omit the first heartbeat log message, because it never has anything
1982 useful to say, and it clutters up the bootstrapping messages.
1983 Resolves ticket 6758.
1984 - Don't log about reloading the microdescriptor cache at startup. Our
1985 bootstrap warnings are supposed to tell the user when there's a
1986 problem, and our bootstrap notices say when there isn't. Resolves
1987 ticket 6759; bugfix on 0.2.2.6-alpha.
1988 - Don't log "I learned some more directory information" when we're
1989 reading cached directory information. Reserve it for when new
1990 directory information arrives in response to a fetch. Resolves
1992 - Prevent rounding error in path bias counts when scaling
1993 them down, and use the correct scale factor default. Also demote
1994 some path bias related log messages down a level and make others
1995 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
1996 - We no longer warn so much when generating manpages from their
1999 o Code simplifications and refactoring:
2000 - Enhance our internal sscanf replacement so that we can eliminate
2001 the last remaining uses of the system sscanf. (Though those uses
2002 of sscanf were safe, sscanf itself is generally error prone, so
2003 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
2005 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
2006 - Move last_reachable and testing_since from routerinfo_t to node_t.
2007 Implements ticket 5529.
2008 - Add replaycache_t structure, functions and unit tests, then refactor
2009 rend_service_introduce() to be more clear to read, improve, debug,
2010 and test. Resolves bug 6177.
2011 - Finally remove support for malloc_good_size and malloc_usable_size.
2012 We had hoped that these functions would let us eke a little more
2013 memory out of our malloc implementation. Unfortunately, the only
2014 implementations that provided these functions are also ones that
2015 are already efficient about not overallocation: they never got us
2016 more than 7 or so bytes per allocation. Removing them saves us a
2017 little code complexity and a nontrivial amount of build complexity.
2020 - Tor maintainers now require Automake version 1.9 or later to build
2021 Tor from the Git repository. (Automake is not required when building
2022 from a source distribution.)
2025 Changes in version 0.2.3.21-rc - 2012-09-05
2026 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
2027 series. It fixes a trio of potential security bugs, fixes a bug where
2028 we were leaving some of the fast relays out of the microdescriptor
2029 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
2030 and cleans up other smaller issues.
2032 o Major bugfixes (security):
2033 - Tear down the circuit if we get an unexpected SENDME cell. Clients
2034 could use this trick to make their circuits receive cells faster
2035 than our flow control would have allowed, or to gum up the network,
2036 or possibly to do targeted memory denial-of-service attacks on
2037 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
2038 from July 2002, before the release of Tor 0.0.0. We had committed
2039 this patch previously, but we had to revert it because of bug 6271.
2040 Now that 6271 is fixed, this patch appears to work.
2041 - Reject any attempt to extend to an internal address. Without
2042 this fix, a router could be used to probe addresses on an internal
2043 network to see whether they were accepting connections. Fixes bug
2044 6710; bugfix on 0.0.8pre1.
2045 - Do not crash when comparing an address with port value 0 to an
2046 address policy. This bug could have been used to cause a remote
2047 assertion failure by or against directory authorities, or to
2048 allow some applications to crash clients. Fixes bug 6690; bugfix
2052 - Remove the upper bound on microdescriptor length. We were hitting
2053 the limit for routers with complex exit policies or family
2054 declarations, causing clients to not use them. Fixes the first
2055 piece of bug 6404; fix on 0.2.2.6-alpha.
2056 - Detect "ORPort 0" as meaning, uniformly, that we're not running
2057 as a relay. Previously, some of our code would treat the presence
2058 of any ORPort line as meaning that we should act like a relay,
2059 even though our new listener code would correctly not open any
2060 ORPorts for ORPort 0. Similar bugs in other Port options are also
2061 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
2064 - Avoid a pair of double-free and use-after-mark bugs that can
2065 occur with certain timings in canceled and re-received DNS
2066 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
2067 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
2068 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
2069 - Allow one-hop directory fetching circuits the full "circuit build
2070 timeout" period, rather than just half of it, before failing them
2071 and marking the relay down. This fix should help reduce cases where
2072 clients declare relays (or worse, bridges) unreachable because
2073 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
2074 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
2076 - Authorities no longer include any router in their microdescriptor
2077 consensuses for which they couldn't generate or agree on a
2078 microdescriptor. Fixes the second piece of bug 6404; fix on
2080 - Detect and reject attempts to specify both "FooPort" and
2081 "FooPort 0" in the same configuration domain. (It's still okay
2082 to have a FooPort in your configuration file, and use "FooPort 0"
2083 on the command line to disable it.) Fixes the second half of bug
2084 6507; bugfix on 0.2.3.3-alpha.
2085 - Make wildcarded addresses (that is, ones beginning with "*.") work
2086 when provided via the controller's MapAddress command. Previously,
2087 they were accepted, but we never actually noticed that they were
2088 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
2089 - Avoid crashing on a malformed state file where EntryGuardPathBias
2090 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
2091 - Add a (probably redundant) memory clear between iterations of
2092 the router status voting loop, to prevent future coding errors
2093 where data might leak between iterations of the loop. Resolves
2096 o Minor bugfixes (log messages):
2097 - Downgrade "set buildtimeout to low value" messages to "info"
2098 severity; they were never an actual problem, there was never
2099 anything reasonable to do about them, and they tended to spam logs
2100 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
2101 - Downgrade path-bias warning messages to "info". We'll try to get
2102 them working better in 0.2.4. Add internal circuit construction
2103 state to protect against the noisy warn message "Unexpectedly high
2104 circuit_successes". Also add some additional rate-limited notice
2105 messages to help determine the root cause of the warn. Fixes bug
2106 6475. Bugfix against 0.2.3.17-beta.
2107 - Move log message when unable to find a microdesc in a routerstatus
2108 entry to parse time. Previously we'd spam this warning every time
2109 we tried to figure out which microdescriptors to download. Fixes
2110 the third piece of bug 6404; fix on 0.2.3.18-rc.
2113 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
2114 change when the authority is deciding whether to accept a newly
2115 uploaded descriptor. Implements ticket 6423.
2116 - Add missing documentation for consensus and microdesc files.
2117 Resolves ticket 6732.
2120 Changes in version 0.2.2.38 - 2012-08-12
2121 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
2122 attack that could in theory leak path information.
2125 - Avoid an uninitialized memory read when reading a vote or consensus
2126 document that has an unrecognized flavor name. This read could
2127 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
2128 - Try to leak less information about what relays a client is
2129 choosing to a side-channel attacker. Previously, a Tor client would
2130 stop iterating through the list of available relays as soon as it
2131 had chosen one, thus finishing a little earlier when it picked
2132 a router earlier in the list. If an attacker can recover this
2133 timing information (nontrivial but not proven to be impossible),
2134 they could learn some coarse-grained information about which relays
2135 a client was picking (middle nodes in particular are likelier to
2136 be affected than exits). The timing attack might be mitigated by
2137 other factors (see bug 6537 for some discussion), but it's best
2138 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
2141 Changes in version 0.2.3.20-rc - 2012-08-05
2142 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
2143 series. It fixes a pair of code security bugs and a potential anonymity
2144 issue, updates our RPM spec files, and cleans up other smaller issues.
2147 - Avoid read-from-freed-memory and double-free bugs that could occur
2148 when a DNS request fails while launching it. Fixes bug 6480;
2149 bugfix on 0.2.0.1-alpha.
2150 - Avoid an uninitialized memory read when reading a vote or consensus
2151 document that has an unrecognized flavor name. This read could
2152 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
2153 - Try to leak less information about what relays a client is
2154 choosing to a side-channel attacker. Previously, a Tor client would
2155 stop iterating through the list of available relays as soon as it
2156 had chosen one, thus finishing a little earlier when it picked
2157 a router earlier in the list. If an attacker can recover this
2158 timing information (nontrivial but not proven to be impossible),
2159 they could learn some coarse-grained information about which relays
2160 a client was picking (middle nodes in particular are likelier to
2161 be affected than exits). The timing attack might be mitigated by
2162 other factors (see bug 6537 for some discussion), but it's best
2163 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
2166 - Try to make the warning when giving an obsolete SOCKSListenAddress
2167 a little more useful.
2168 - Terminate active server managed proxies if Tor stops being a
2169 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
2170 - Provide a better error message about possible OSX Asciidoc failure
2171 reasons. Fixes bug 6436.
2172 - Warn when Tor is configured to use accounting in a way that can
2173 link a hidden service to some other hidden service or public
2174 address. Resolves ticket 6490.
2177 - Check return value of fputs() when writing authority certificate
2178 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
2179 - Ignore ServerTransportPlugin lines when Tor is not configured as
2180 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
2181 - When disabling guards for having too high a proportion of failed
2182 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
2186 - Update our default RPM spec files to work with mock and rpmbuild
2187 on RHEL/Fedora. They have an updated set of dependencies and
2188 conflicts, a fix for an ancient typo when creating the "_tor"
2189 user, and better instructions. Thanks to Ondrej Mikle for the
2190 patch series. Fixes bug 6043.
2193 - Make it possible to set the TestingTorNetwork configuration
2194 option using AlternateDirAuthority and AlternateBridgeAuthority
2195 as an alternative to setting DirServer. Addresses ticket 6377.
2198 - Clarify the documentation for the Alternate*Authority options.
2200 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
2202 o Code simplification and refactoring:
2203 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
2204 10 lines. Also, don't nest them. Doing so in the past has
2205 led to hard-to-debug code. The new style is to use the
2206 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
2209 Changes in version 0.2.3.19-rc - 2012-07-06
2210 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
2211 series. It fixes the compile on Windows, reverts to a GeoIP database
2212 that isn't as broken, and fixes a flow control bug that has been around
2213 since the beginning of Tor.
2216 - Fix a bug handling SENDME cells on nonexistent streams that could
2217 result in bizarre window values. Report and patch contributed
2218 pseudonymously. Fixes part of bug 6271. This bug was introduced
2219 before the first Tor release, in svn commit r152.
2220 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
2221 June 2012 database, Maxmind marked many Tor relays as country "A1",
2222 which will cause risky behavior for clients that set EntryNodes
2223 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
2224 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
2225 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
2228 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
2229 bugfix on 0.2.1.10-alpha.
2232 Changes in version 0.2.3.18-rc - 2012-06-28
2233 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
2234 series. It fixes a few smaller bugs, but generally appears stable.
2235 Please test it and let us know whether it is!
2238 - Allow wildcarded mapaddress targets to be specified on the
2239 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
2240 - Make our linker option detection code more robust against linkers
2241 such as on FreeBSD 8, where a bad combination of options completes
2242 successfully but makes an unrunnable binary. Fixes bug 6173;
2243 bugfix on 0.2.3.17-beta.
2245 o Minor bugfixes (on 0.2.2.x and earlier):
2246 - Avoid a false positive in the util/threads unit test by increasing
2247 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
2248 - Replace "Sending publish request" log messages with "Launching
2249 upload", so that they no longer confusingly imply that we're
2250 sending something to a directory we might not even be connected
2251 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
2252 - Make sure to set *socket_error in all error cases in
2253 connection_connect(), so it can't produce a warning about
2254 errno being zero from errno_to_orconn_end_reason(). Bugfix on
2255 0.2.1.1-alpha; resolves ticket 6028.
2256 - Downgrade "Got a certificate, but we already have it" log messages
2257 from warning to info, except when we're a dirauth. Fixes bug 5238;
2258 bugfix on 0.2.1.7-alpha.
2259 - When checking for requested signatures on the latest consensus
2260 before serving it to a client, make sure to check the right
2261 consensus flavor. Bugfix on 0.2.2.6-alpha.
2262 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
2263 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
2265 o Minor bugfixes (on 0.2.3.x):
2266 - Make format_helper_exit_status() avoid unnecessary space padding
2267 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
2269 - Downgrade a message about cleaning the microdescriptor cache to
2270 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
2271 - Log a BUG message at severity INFO if we have a networkstatus with
2272 a missing entry for some microdescriptor. Continues on a patch
2274 - Improve the log message when a managed proxy fails to launch. Fixes
2275 bug 5099; bugfix on 0.2.3.6-alpha.
2276 - Don't do DNS lookups when parsing corrupted managed proxy protocol
2277 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
2278 - When formatting wildcarded address mappings for the controller,
2279 be sure to include "*." as appropriate. Partially fixes bug 6244;
2280 bugfix on 0.2.3.9-alpha.
2281 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
2282 Bugfix on 0.2.3.13-alpha.
2283 - Stop logging messages about running with circuit timeout learning
2284 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
2285 - Disable a spurious warning about reading on a marked and flushing
2286 connection. We shouldn't be doing that, but apparently we
2287 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
2288 - Fix a bug that stopped AllowDotExit from working on addresses
2289 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
2292 o Code simplification, refactoring, unit tests:
2293 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
2294 Libevent's notion of cached time when possible.
2295 - Remove duplicate code for invoking getrlimit() from control.c.
2296 - Add a unit test for the environment_variable_names_equal function.
2299 - Document the --defaults-torrc option, and the new (in 0.2.3)
2300 semantics for overriding, extending, and clearing lists of
2301 options. Closes bug 4748.
2304 Changes in version 0.2.3.17-beta - 2012-06-15
2305 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
2306 gets our TLS handshake back on track for being able to blend in with
2307 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
2308 with Vidalia, and otherwise continues to get us closer to a release
2312 - Enable gcc and ld hardening by default. Resolves ticket 5210.
2313 - Update TLS cipher list to match Firefox 8 and later. Resolves
2315 - Implement the client side of proposal 198: remove support for
2316 clients falsely claiming to support standard ciphersuites that
2317 they can actually provide. As of modern OpenSSL versions, it's not
2318 necessary to fake any standard ciphersuite, and doing so prevents
2319 us from using better ciphersuites in the future, since servers
2320 can't know whether an advertised ciphersuite is really supported or
2321 not. Some hosts -- notably, ones with very old versions of OpenSSL
2322 or where OpenSSL has been built with ECC disabled -- will stand
2323 out because of this change; TBB users should not be affected.
2326 - Change the default value for DynamicDHGroups (introduced in
2327 0.2.3.9-alpha) to 0. This feature can make Tor relays less
2328 identifiable by their use of the mod_ssl DH group, but at
2329 the cost of some usability (#4721) and bridge tracing (#6087)
2330 regressions. Resolves ticket 5598.
2331 - Send a CRLF at the end of each STATUS_* control protocol event. This
2332 bug tickled a bug in Vidalia which would make it freeze. Fixes
2333 bug 6094; bugfix on 0.2.3.16-alpha.
2336 - Disable writing on marked-for-close connections when they are
2337 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
2338 bug 5263; bugfix on 0.0.2pre13, where we first added a special
2339 case for flushing marked connections.
2340 - Detect SSL handshake even when the initial attempt to write the
2341 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
2342 - Change the AllowDotExit rules so they should actually work.
2343 We now enforce AllowDotExit only immediately after receiving an
2344 address via SOCKS or DNSPort: other sources are free to provide
2345 .exit addresses after the resolution occurs. Fixes bug 3940;
2346 bugfix on 0.2.2.1-alpha.
2347 - Fix a (harmless) integer overflow in cell statistics reported by
2348 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
2349 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
2350 right places and never depends on the consensus parameters or
2351 computes adaptive timeouts when it is disabled. Fixes bug 5049;
2352 bugfix on 0.2.2.14-alpha.
2353 - When building Tor on Windows with -DUNICODE (not default), ensure
2354 that error messages, filenames, and DNS server names are always
2355 NUL-terminated when we convert them to a single-byte encoding.
2356 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
2357 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
2358 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
2359 - Fix an edge case where TestingTorNetwork is set but the authorities
2360 and relays all have an uptime of zero, where the private Tor network
2361 could briefly lack support for hidden services. Fixes bug 3886;
2362 bugfix on 0.2.2.18-alpha.
2363 - Correct the manpage's descriptions for the default values of
2364 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
2366 - Fix the documentation for the --hush and --quiet command line
2367 options, which changed their behavior back in 0.2.3.3-alpha.
2368 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
2372 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
2373 more information to it, so that we can track it down in case it
2374 returns again. Mitigates bug 5235.
2375 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
2376 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
2377 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
2378 - Warn the user when HTTPProxy, but no other proxy type, is
2379 configured. This can cause surprising behavior: it doesn't send
2380 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
2381 directory traffic only. Resolves ticket 4663.
2382 - Issue a notice if a guard completes less than 40% of your circuits.
2383 Threshold is configurable by torrc option PathBiasNoticeRate and
2384 consensus parameter pb_noticepct. There is additional, off-by-
2385 default code to disable guards which fail too many circuits.
2386 Addresses ticket 5458.
2387 - Update to the June 6 2012 Maxmind GeoLite Country database.
2389 o Code simplifications and refactoring:
2390 - Remove validate_pluggable_transports_config(): its warning
2391 message is now handled by connection_or_connect().
2394 Changes in version 0.2.2.37 - 2012-06-06
2395 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
2396 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2400 - Work around a bug in OpenSSL that broke renegotiation with TLS
2401 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2402 the v2 Tor connection protocol when both sides were using OpenSSL
2403 1.0.1 would fail. Resolves ticket 6033.
2404 - When waiting for a client to renegotiate, don't allow it to add
2405 any bytes to the input buffer. This fixes a potential DoS issue.
2406 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2407 - Fix an edge case where if we fetch or publish a hidden service
2408 descriptor, we might build a 4-hop circuit and then use that circuit
2409 for exiting afterwards -- even if the new last hop doesn't obey our
2410 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2413 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2414 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2417 - Tell GCC and Clang to check for any errors in format strings passed
2418 to the tor_v*(print|scan)f functions.
2421 Changes in version 0.2.3.16-alpha - 2012-06-05
2422 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
2423 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2424 currently). It also fixes a variety of smaller bugs and other cleanups
2425 that get us closer to a release candidate.
2427 o Major bugfixes (general):
2428 - Work around a bug in OpenSSL that broke renegotiation with TLS
2429 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2430 the v2 Tor connection protocol when both sides were using OpenSSL
2431 1.0.1 would fail. Resolves ticket 6033.
2432 - When waiting for a client to renegotiate, don't allow it to add
2433 any bytes to the input buffer. This fixes a potential DoS issue.
2434 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2435 - Pass correct OR address to managed proxies (like obfsproxy),
2436 even when ORListenAddress is used. Fixes bug 4865; bugfix on
2438 - The advertised platform of a router now includes only its operating
2439 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
2440 service pack level (for Windows) or its CPU architecture (for Unix).
2441 We also no longer include the "git-XYZ" tag in the version. Resolves
2444 o Major bugfixes (clients):
2445 - If we are unable to find any exit that supports our predicted ports,
2446 stop calling them predicted, so that we don't loop and build
2447 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
2448 which introduced predicted ports.
2449 - Fix an edge case where if we fetch or publish a hidden service
2450 descriptor, we might build a 4-hop circuit and then use that circuit
2451 for exiting afterwards -- even if the new last hop doesn't obey our
2452 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2453 - Check at each new consensus whether our entry guards were picked
2454 long enough ago that we should rotate them. Previously, we only
2455 did this check at startup, which could lead to us holding a guard
2456 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
2457 - When fetching a bridge descriptor from a bridge authority,
2458 always do so anonymously, whether we have been able to open
2459 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
2460 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
2461 but we'll need to wait for bug 6010 before it's actually usable.
2463 o Major bugfixes (directory authorities):
2464 - When computing weight parameters, behave more robustly in the
2465 presence of a bad bwweightscale value. Previously, the authorities
2466 would crash if they agreed on a sufficiently broken weight_scale
2467 value: now, they use a reasonable default and carry on. Partial
2468 fix for 5786; bugfix on 0.2.2.17-alpha.
2469 - Check more thoroughly to prevent a rogue authority from
2470 double-voting on any consensus directory parameter. Previously,
2471 authorities would crash in this case if the total number of
2472 votes for any parameter exceeded the number of active voters,
2473 but would let it pass otherwise. Partial fix for bug 5786; bugfix
2477 - Rate-limit log messages when asked to connect anonymously to
2478 a private address. When these hit, they tended to hit fast and
2479 often. Also, don't bother trying to connect to addresses that we
2480 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
2481 reply makes us think we have been lied to, even when the address the
2482 client tried to connect to was "localhost." Resolves ticket 2822.
2483 - Allow packagers to insert an extra string in server descriptor
2484 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
2485 Resolves the rest of ticket 2988.
2486 - Raise the threshold of server descriptors needed (75%) and exit
2487 server descriptors needed (50%) before we will declare ourselves
2488 bootstrapped. This will make clients start building circuits a
2489 little later, but makes the initially constructed circuits less
2490 skewed and less in conflict with further directory fetches. Fixes
2492 - Close any connection that sends unrecognized junk before the
2493 handshake. Solves an issue noted in bug 4369.
2494 - Improve log messages about managed transports. Resolves ticket 5070.
2495 - Tag a bridge's descriptor as "never to be sent unencrypted".
2496 This shouldn't matter, since bridges don't open non-anonymous
2497 connections to the bridge authority and don't allow unencrypted
2498 directory connections from clients, but we might as well make
2499 sure. Closes bug 5139.
2500 - Expose our view of whether we have gone dormant to the controller,
2501 via a new "GETINFO dormant" value. Torbutton and other controllers
2502 can use this to avoid doing periodic requests through Tor while
2503 it's dormant (bug 4718). Fixes bug 5954.
2504 - Tell GCC and Clang to check for any errors in format strings passed
2505 to the tor_v*(print|scan)f functions.
2506 - Update to the May 1 2012 Maxmind GeoLite Country database.
2508 o Minor bugfixes (already included in 0.2.2.36):
2509 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2510 Fixes bug 5346; bugfix on 0.0.8pre3.
2511 - Correct parsing of certain date types in parse_http_time().
2512 Without this patch, If-Modified-Since would behave
2513 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2514 Esteban Manchado Velázques.
2515 - Make our number-parsing functions always treat too-large values
2516 as an error, even when those values exceed the width of the
2517 underlying type. Previously, if the caller provided these
2518 functions with minima or maxima set to the extreme values of the
2519 underlying integer type, these functions would return those
2520 values on overflow rather than treating overflow as an error.
2521 Fixes part of bug 5786; bugfix on 0.0.9.
2522 - If we hit the error case where routerlist_insert() replaces an
2523 existing (old) server descriptor, make sure to remove that
2524 server descriptor from the old_routers list. Fix related to bug
2525 1776. Bugfix on 0.2.2.18-alpha.
2526 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2527 circuits. Fixes issue 5259.
2529 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
2530 - Prevent a null-pointer dereference when receiving a data cell
2531 for a nonexistent stream when the circuit in question has an
2532 empty deliver window. We don't believe this is triggerable,
2533 since we don't currently allow deliver windows to become empty,
2534 but the logic is tricky enough that it's better to make the code
2535 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
2536 - Fix a memory leak when trying to launch a DNS request when the
2537 network is disabled or the nameservers are unconfigurable. Fixes
2538 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
2539 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
2540 - Don't hold a Windows file handle open for every file mapping;
2541 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
2543 - Avoid O(n^2) performance characteristics when parsing a large
2544 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
2545 - Format more doubles with %f, not %lf. Patch from grarpamp to make
2546 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
2548 - Make our replacement implementation of strtok_r() compatible with
2549 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
2550 bugfix on 0.2.2.1-alpha.
2551 - Fix a NULL-pointer dereference on a badly formed
2552 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
2553 bugfix on 0.2.2.9-alpha.
2554 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2555 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2556 - Defensively refactor rend_mid_rendezvous() so that protocol
2557 violations and length checks happen in the beginning. Fixes
2559 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
2560 that IPv6 stuff will compile on MSVC, and compilation issues
2561 will be easier to track down. Fixes bug 5861.
2563 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
2564 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
2565 resource exhaustion, so that clients can adjust their load to
2566 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
2567 started using END_STREAM_REASON_RESOURCELIMIT.
2568 - Don't check for whether the address we're using for outbound
2569 connections has changed until after the outbound connection has
2570 completed. On Windows, getsockname() doesn't succeed until the
2571 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
2572 - If the configuration tries to set MyFamily on a bridge, refuse to
2573 do so, and warn about the security implications. Fixes bug 4657;
2574 bugfix on 0.2.0.3-alpha.
2575 - If the client fails to set a reasonable set of ciphersuites
2576 during its v2 handshake renegotiation, allow the renegotiation to
2577 continue nevertheless (i.e. send all the required certificates).
2578 Fixes bug 4591; bugfix on 0.2.0.20-rc.
2579 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
2580 option is set to 0 (which Vidalia version 0.2.16 now does when
2581 a SAVECONF attempt fails), perform other actions that SIGHUP
2582 usually causes (like reopening the logs). Fixes bug 5095; bugfix
2584 - If we fail to write a microdescriptor to the disk cache, do not
2585 continue replacing the old microdescriptor file. Fixes bug 2954;
2586 bugfix on 0.2.2.6-alpha.
2587 - Exit nodes don't need to fetch certificates for authorities that
2588 they don't recognize; only directory authorities, bridges,
2589 and caches need to do that. Fixes part of bug 2297; bugfix on
2591 - Correctly handle checking the permissions on the parent
2592 directory of a control socket in the root directory. Bug found
2593 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
2595 - When told to add a bridge with the same digest as a preexisting
2596 bridge but a different addr:port, change the addr:port as
2597 requested. Previously we would not notice the change. Fixes half
2598 of bug 5603; fix on 0.2.2.26-beta.
2599 - End AUTHCHALLENGE error messages (in the control protocol) with
2600 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
2602 o Minor bugfixes (on 0.2.3.x):
2603 - Turn an assertion (that the number of handshakes received as a
2604 server is not < 1) into a warning. Fixes bug 4873; bugfix on
2606 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
2607 we had reversed them when the answer was cached.) Fixes bug
2608 5723; bugfix on 0.2.3.1-alpha.
2609 - Work correctly on Linux systems with accept4 support advertised in
2610 their headers, but without accept4 support in the kernel. Fix
2611 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
2612 - When told to add a bridge with the same addr:port as a preexisting
2613 bridge but a different transport, change the transport as
2614 requested. Previously we would not notice the change. Fixes half
2615 of bug 5603; fix on 0.2.3.2-alpha.
2616 - Avoid a "double-reply" warning when replying to a SOCKS request
2617 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
2618 bugfix on 0.2.3.4-alpha.
2619 - Fix a bug where a bridge authority crashes if it has seen no
2620 directory requests when it's time to write statistics to disk.
2621 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
2623 - Don't try to open non-control listeners when DisableNetwork is set.
2624 Previously, we'd open all listeners, then immediately close them.
2625 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
2626 - Don't abort the managed proxy protocol if the managed proxy
2627 sends us an unrecognized line; ignore it instead. Fixes bug
2628 5910; bugfix on 0.2.3.9-alpha.
2629 - Fix a compile warning in crypto.c when compiling with clang 3.1.
2630 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
2631 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
2632 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
2633 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
2634 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
2635 - Resolve numerous small warnings and build issues with MSVC. Resolves
2638 o Documentation fixes:
2639 - Improve the manual's documentation for the NT Service command-line
2640 options. Addresses ticket 3964.
2641 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
2642 - Document the changes to the ORPort and DirPort options, and the
2643 fact that {OR/Dir}ListenAddress is now unnecessary (and
2644 therefore deprecated). Resolves ticket 5597.
2647 - Remove the torrc.bridge file: we don't use it for anything, and
2648 it had become badly desynchronized from torrc.sample. Resolves
2652 Changes in version 0.2.2.36 - 2012-05-24
2653 Tor 0.2.2.36 updates the addresses for two of the eight directory
2654 authorities, fixes some potential anonymity and security issues,
2655 and fixes several crash bugs.
2657 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
2658 known flaws, and nobody should be using them. You should upgrade. If
2659 you're using a Linux or BSD and its packages are obsolete, stop using
2660 those packages and upgrade anyway.
2662 o Directory authority changes:
2663 - Change IP address for maatuska (v3 directory authority).
2664 - Change IP address for ides (v3 directory authority), and rename
2668 - When building or running with any version of OpenSSL earlier
2669 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2670 versions have a bug (CVE-2011-4576) in which their block cipher
2671 padding includes uninitialized data, potentially leaking sensitive
2672 information to any peer with whom they make a SSLv3 connection. Tor
2673 does not use SSL v3 by default, but a hostile client or server
2674 could force an SSLv3 connection in order to gain information that
2675 they shouldn't have been able to get. The best solution here is to
2676 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2677 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2678 to make sure that the bug can't happen.
2679 - Never use a bridge or a controller-supplied node as an exit, even
2680 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2681 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2682 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2683 - Only build circuits if we have a sufficient threshold of the total
2684 descriptors that are marked in the consensus with the "Exit"
2685 flag. This mitigates an attack proposed by wanoskarnet, in which
2686 all of a client's bridges collude to restrict the exit nodes that
2687 the client knows about. Fixes bug 5343.
2688 - Provide controllers with a safer way to implement the cookie
2689 authentication mechanism. With the old method, if another locally
2690 running program could convince a controller that it was the Tor
2691 process, then that program could trick the controller into telling
2692 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2693 authentication method uses a challenge-response approach to prevent
2694 this attack. Fixes bug 5185; implements proposal 193.
2697 - Avoid logging uninitialized data when unable to decode a hidden
2698 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2699 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2700 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2702 - Fix builds when the path to sed, openssl, or sha1sum contains
2703 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2705 - Correct our replacements for the timeradd() and timersub() functions
2706 on platforms that lack them (for example, Windows). The timersub()
2707 function is used when expiring circuits, while timeradd() is
2708 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2709 bugfix on 0.2.2.24-alpha.
2710 - Fix the SOCKET_OK test that we use to tell when socket
2711 creation fails so that it works on Win64. Fixes part of bug 4533;
2712 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2715 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2716 Fixes bug 5346; bugfix on 0.0.8pre3.
2717 - Make our number-parsing functions always treat too-large values
2718 as an error, even when those values exceed the width of the
2719 underlying type. Previously, if the caller provided these
2720 functions with minima or maxima set to the extreme values of the
2721 underlying integer type, these functions would return those
2722 values on overflow rather than treating overflow as an error.
2723 Fixes part of bug 5786; bugfix on 0.0.9.
2724 - Older Linux kernels erroneously respond to strange nmap behavior
2725 by having accept() return successfully with a zero-length
2726 socket. When this happens, just close the connection. Previously,
2727 we would try harder to learn the remote address: but there was
2728 no such remote address to learn, and our method for trying to
2729 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2730 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2731 - Correct parsing of certain date types in parse_http_time().
2732 Without this patch, If-Modified-Since would behave
2733 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2734 Esteban Manchado Velázques.
2735 - Change the BridgePassword feature (part of the "bridge community"
2736 design, which is not yet implemented) to use a time-independent
2737 comparison. The old behavior might have allowed an adversary
2738 to use timing to guess the BridgePassword value. Fixes bug 5543;
2739 bugfix on 0.2.0.14-alpha.
2740 - Detect and reject certain misformed escape sequences in
2741 configuration values. Previously, these values would cause us
2742 to crash if received in a torrc file or over an authenticated
2743 control port. Bug found by Esteban Manchado Velázquez, and
2744 independently by Robert Connolly from Matta Consulting who further
2745 noted that it allows a post-authentication heap overflow. Patch
2746 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2747 bugfix on 0.2.0.16-alpha.
2748 - Fix a compile warning when using the --enable-openbsd-malloc
2749 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2750 - During configure, detect when we're building with clang version
2751 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2752 CFLAGS. clang doesn't support them yet.
2753 - When sending an HTTP/1.1 proxy request, include a Host header.
2754 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2755 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
2756 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
2757 - If we hit the error case where routerlist_insert() replaces an
2758 existing (old) server descriptor, make sure to remove that
2759 server descriptor from the old_routers list. Fix related to bug
2760 1776. Bugfix on 0.2.2.18-alpha.
2762 o Minor bugfixes (documentation and log messages):
2763 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2764 Fixes bug 4856; bugfix on Tor 0.0.6.
2765 - Update "ClientOnly" man page entry to explain that there isn't
2766 really any point to messing with it. Resolves ticket 5005.
2767 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2768 directory authority option (introduced in Tor 0.2.2.34).
2769 - Downgrade the "We're missing a certificate" message from notice
2770 to info: people kept mistaking it for a real problem, whereas it
2771 is seldom the problem even when we are failing to bootstrap. Fixes
2772 bug 5067; bugfix on 0.2.0.10-alpha.
2773 - Correctly spell "connect" in a log message on failure to create a
2774 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
2775 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2776 circuits. Fixes issue 5259.
2779 - Directory authorities now reject versions of Tor older than
2780 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2781 inclusive. These versions accounted for only a small fraction of
2782 the Tor network, and have numerous known security issues. Resolves
2784 - Update to the May 1 2012 Maxmind GeoLite Country database.
2787 - When sending or relaying a RELAY_EARLY cell, we used to convert
2788 it to a RELAY cell if the connection was using the v1 link
2789 protocol. This was a workaround for older versions of Tor, which
2790 didn't handle RELAY_EARLY cells properly. Now that all supported
2791 versions can handle RELAY_EARLY cells, and now that we're enforcing
2792 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2793 remove this workaround. Addresses bug 4786.
2796 Changes in version 0.2.3.15-alpha - 2012-04-30
2797 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
2798 the development branch build on Windows again.
2800 o Minor bugfixes (on 0.2.2.x and earlier):
2801 - Make sure that there are no unhandled pending TLS errors before
2802 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
2803 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
2804 Bugfix on 0.1.0.5-rc; fixes bug 4528.
2805 - Fix an assert that directory authorities could trigger on sighup
2806 during some configuration state transitions. We now don't treat
2807 it as a fatal error when the new descriptor we just generated in
2808 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
2809 - After we pick a directory mirror, we would refuse to use it if
2810 it's in our ExcludeExitNodes list, resulting in mysterious failures
2811 to bootstrap for people who just wanted to avoid exiting from
2812 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
2813 - When building with --enable-static-tor on OpenBSD, do not
2814 erroneously attempt to link -lrt. Fixes bug 5103.
2816 o Minor bugfixes (on 0.2.3.x):
2817 - When Tor is built with kernel headers from a recent (last few
2818 years) Linux kernel, do not fail to run on older (pre-2.6.28
2819 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
2820 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
2822 - Fix compilation with miniupnpc version 1.6; patch from
2823 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
2824 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
2825 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
2826 - Fix compilation on platforms without unistd.h, or where environ
2827 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
2830 - Directory authorities are now a little more lenient at accepting
2831 older router descriptors, or newer router descriptors that don't
2832 make big changes. This should help ameliorate past and future
2833 issues where routers think they have uploaded valid descriptors,
2834 but the authorities don't think so. Fix for ticket 2479.
2835 - Make the code that clients use to detect an address change be
2836 IPv6-aware, so that it won't fill clients' logs with error
2837 messages when trying to get the IPv4 address of an IPv6
2838 connection. Implements ticket 5537.
2841 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
2842 authorities needed to use it for a while to keep the network working
2843 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
2844 that was six months ago. As of now, it should no longer be needed
2848 Changes in version 0.2.3.14-alpha - 2012-04-23
2849 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
2850 candidate. It also dramatically speeds up AES: fast relays should
2851 consider switching to the newer OpenSSL library.
2853 o Directory authority changes:
2854 - Change IP address for ides (v3 directory authority), and rename
2858 - Avoid logging uninitialized data when unable to decode a hidden
2859 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2860 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2861 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2863 - If authorities are unable to get a v2 consensus document from other
2864 directory authorities, they no longer fall back to fetching
2865 them from regular directory caches. Fixes bug 5635; bugfix on
2866 0.2.2.26-beta, where routers stopped downloading v2 consensus
2868 - When we start a Tor client with a normal consensus already cached,
2869 be willing to download a microdescriptor consensus. Fixes bug 4011;
2870 fix on 0.2.3.1-alpha.
2872 o Major features (performance):
2873 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
2874 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
2875 vectorized AES implementations as appropriate. These can be much,
2876 much faster than other AES implementations.
2878 o Minor bugfixes (0.2.2.x and earlier):
2879 - Don't launch more than 10 service-side introduction-point circuits
2880 for a hidden service in five minutes. Previously, we would consider
2881 launching more introduction-point circuits if at least one second
2882 had passed without any introduction-point circuits failing. Fixes
2883 bug 4607; bugfix on 0.0.7pre1.
2884 - Change the BridgePassword feature (part of the "bridge community"
2885 design, which is not yet implemented) to use a time-independent
2886 comparison. The old behavior might have allowed an adversary
2887 to use timing to guess the BridgePassword value. Fixes bug 5543;
2888 bugfix on 0.2.0.14-alpha.
2889 - Enforce correct return behavior of tor_vsscanf() when the '%%'
2890 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
2891 - When sending an HTTP/1.1 proxy request, include a Host header.
2892 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2893 - Don't log that we have "decided to publish new relay descriptor"
2894 unless we are actually publishing a descriptor. Fixes bug 3942;
2895 bugfix on 0.2.2.28-beta.
2897 o Minor bugfixes (0.2.3.x):
2898 - Fix a bug where a bridge authority crashes (on a failed assert)
2899 if it has seen no directory requests when it's time to write
2900 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
2901 - Fix bug stomping on ORPort option NoListen and ignoring option
2902 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
2903 - In the testsuite, provide a large enough buffer in the tor_sscanf
2904 unit test. Otherwise we'd overrun that buffer and crash during
2905 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
2907 - Make sure we create the keys directory if it doesn't exist and we're
2908 about to store the dynamic Diffie-Hellman parameters. Fixes bug
2909 5572; bugfix on 0.2.3.13-alpha.
2910 - Fix a small memory leak when trying to decode incorrect base16
2911 authenticator during SAFECOOKIE authentication. Found by
2912 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
2915 - Add more information to a log statement that might help track down
2916 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
2917 non-IP address" messages (or any Bug messages, for that matter!),
2918 please let us know about it.
2919 - Relays now understand an IPv6 address when they get one from a
2920 directory server. Resolves ticket 4875.
2921 - Resolve IPv6 addresses in bridge and entry statistics to country
2922 code "??" which means we at least count them. Resolves ticket 5053;
2923 improves on 0.2.3.9-alpha.
2924 - Update to the April 3 2012 Maxmind GeoLite Country database.
2925 - Begin a doc/state-contents.txt file to explain the contents of
2926 the Tor state file. Fixes bug 2987.
2928 o Default torrc changes:
2929 - Stop listing "socksport 9050" in torrc.sample. We open a socks
2930 port on 9050 by default anyway, so this should not change anything
2932 - Stop mentioning the deprecated *ListenAddress options in
2933 torrc.sample. Fixes bug 5438.
2934 - Document unit of bandwidth related options in sample torrc.
2938 - The "torify" script no longer supports the "tsocks" socksifier
2939 tool, since tsocks doesn't support DNS and UDP right for Tor.
2940 Everyone should be using torsocks instead. Fixes bugs 3530 and
2941 5180. Based on a patch by "ugh".
2944 - Change the symmetric cipher interface so that creating and
2945 initializing a stream cipher are no longer separate functions.
2946 - Remove all internal support for unpadded RSA. We never used it, and
2947 it would be a bad idea to start.
2950 Changes in version 0.2.3.13-alpha - 2012-03-26
2951 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
2952 in managed pluggable transports, as well as providing other cleanups
2953 that get us closer to a release candidate.
2955 o Directory authority changes:
2956 - Change IP address for maatuska (v3 directory authority).
2959 - Provide controllers with a safer way to implement the cookie
2960 authentication mechanism. With the old method, if another locally
2961 running program could convince a controller that it was the Tor
2962 process, then that program could trick the controller into telling
2963 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2964 authentication method uses a challenge-response approach to prevent
2965 this attack. Fixes bug 5185, implements proposal 193.
2966 - Never use a bridge or a controller-supplied node as an exit, even
2967 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2968 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2969 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2970 - Only build circuits if we have a sufficient threshold of the total
2971 descriptors that are marked in the consensus with the "Exit"
2972 flag. This mitigates an attack proposed by wanoskarnet, in which
2973 all of a client's bridges collude to restrict the exit nodes that
2974 the client knows about. Fixes bug 5343.
2976 o Major bugfixes (on Tor 0.2.3.x):
2977 - Avoid an assert when managed proxies like obfsproxy are configured,
2978 and we receive HUP signals or setconf attempts too rapidly. This
2979 situation happens most commonly when Vidalia tries to attach to
2980 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
2981 bugfix on 0.2.3.6-alpha.
2982 - Fix a relay-side pluggable transports bug where managed proxies were
2983 unreachable from the Internet, because Tor asked them to bind on
2984 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
2985 - Stop discarding command-line arguments when TestingTorNetwork
2986 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
2987 0.2.3.9-alpha, where task 4552 added support for two layers of
2989 - Resume allowing the unit tests to run in gdb. This was accidentally
2990 made impossible when the DisableDebuggerAttachment option was
2991 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
2992 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
2993 0.2.3.11-alpha. Reported by Anthony G. Basile.
2995 o Minor bugfixes (on 0.2.2.x and earlier):
2996 - Ensure we don't cannibalize circuits that are longer than three hops
2997 already, so we don't end up making circuits with 5 or more
2998 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
2999 0.1.0.1-rc which introduced cannibalization.
3000 - Detect and reject certain misformed escape sequences in
3001 configuration values. Previously, these values would cause us
3002 to crash if received in a torrc file or over an authenticated
3003 control port. Bug found by Esteban Manchado Velázquez, and
3004 independently by Robert Connolly from Matta Consulting who further
3005 noted that it allows a post-authentication heap overflow. Patch
3006 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
3007 bugfix on 0.2.0.16-alpha.
3008 - Fix a compile warning when using the --enable-openbsd-malloc
3009 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
3010 - Directory caches no longer refuse to clean out descriptors because
3011 of missing v2 networkstatus documents, unless they're configured
3012 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
3013 0.2.2.26-beta. Patch by Daniel Bryg.
3014 - Update to the latest version of the tinytest unit testing framework.
3015 This includes a couple of bugfixes that can be relevant for
3016 running forked unit tests on Windows, and removes all reserved
3019 o Minor bugfixes (on 0.2.3.x):
3020 - On a failed pipe() call, don't leak file descriptors. Fixes bug
3021 4296; bugfix on 0.2.3.1-alpha.
3022 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
3023 until after we have received a CERTS cell. Fixes bug 4361; bugfix
3024 on 0.2.3.6-alpha. Patch by "frosty".
3025 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
3026 option, so that the IP stack doesn't decide to use it for IPv4
3027 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
3028 - Ensure that variables set in Tor's environment cannot override
3029 environment variables that Tor passes to a managed
3030 pluggable-transport proxy. Previously, Tor would pass every
3031 variable in its environment to managed proxies along with the new
3032 ones, in such a way that on many operating systems, the inherited
3033 environment variables would override those which Tor tried to
3034 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
3035 bugfix on 0.2.3.9-alpha for Windows.
3038 - A wide variety of new unit tests by Esteban Manchado Velázquez.
3039 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
3040 - Update to the March 6 2012 Maxmind GeoLite Country database.
3043 Changes in version 0.2.3.12-alpha - 2012-02-13
3044 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
3045 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
3046 when Tor is configured to use a pluggable transport like obfsproxy.
3049 - Fix builds when the path to sed, openssl, or sha1sum contains
3050 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
3052 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
3053 connections. This change should allow busy exit relays to stop
3054 running out of available sockets as quickly. Fixes bug 4950;
3055 bugfix on 0.2.2.26-beta.
3056 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
3057 would ask the bridge for microdescriptors, which are only supported
3058 in 0.2.3.x, and then fail to bootstrap when it didn't get the
3059 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
3060 - Properly set up obfsproxy's environment when in managed mode. The
3061 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
3062 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
3063 5076 and 5082; bugfix on 0.2.3.6-alpha.
3066 - Use the dead_strip option when building Tor on OS X. This reduces
3067 binary size by almost 19% when linking openssl and libevent
3068 statically, which we do for Tor Browser Bundle.
3069 - Fix broken URLs in the sample torrc file, and tell readers about
3070 the OutboundBindAddress, ExitPolicyRejectPrivate, and
3071 PublishServerDescriptor options. Addresses bug 4652.
3072 - Update to the February 7 2012 Maxmind GeoLite Country database.
3075 - Downgrade the "We're missing a certificate" message from notice
3076 to info: people kept mistaking it for a real problem, whereas it
3077 is seldom the problem even when we are failing to bootstrap. Fixes
3078 bug 5067; bugfix on 0.2.0.10-alpha.
3079 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
3080 managed pluggable transport server proxy's environment.
3081 Previously, we would put it there, even though Tor doesn't
3082 implement an 'extended server port' yet, and even though Tor
3083 almost certainly isn't listening at that address. For now, we set
3084 it to an empty string to avoid crashing older obfsproxies. Bugfix
3086 - Log the heartbeat message every HeartbeatPeriod seconds, not every
3087 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
3088 0.2.3.1-alpha. Bug reported by Scott Bennett.
3089 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
3090 bugfix on 0.2.3.11-alpha.
3091 - Update "ClientOnly" man page entry to explain that there isn't
3092 really any point to messing with it. Resolves ticket 5005.
3093 - Use the correct CVE number for CVE-2011-4576 in our comments and
3094 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
3097 o Code simplifications and refactoring:
3098 - Use the _WIN32 macro throughout our code to detect Windows.
3099 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
3103 Changes in version 0.2.3.11-alpha - 2012-01-22
3104 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
3105 the last step of the plan to limit maximum circuit length, includes
3106 a wide variety of hidden service performance and correctness fixes,
3107 works around an OpenSSL security flaw if your distro is too stubborn
3108 to upgrade, and fixes a bunch of smaller issues.
3111 - Now that Tor 0.2.0.x is completely deprecated, enable the final
3112 part of "Proposal 110: Avoiding infinite length circuits" by
3113 refusing all circuit-extend requests that do not use a relay_early
3114 cell. This change helps Tor resist a class of denial-of-service
3115 attacks by limiting the maximum circuit length.
3116 - Adjust the number of introduction points that a hidden service
3117 will try to maintain based on how long its introduction points
3118 remain in use and how many introductions they handle. Fixes
3120 - Try to use system facilities for enumerating local interface
3121 addresses, before falling back to our old approach (which was
3122 binding a UDP socket, and calling getsockname() on it). That
3123 approach was scaring OS X users whose draconian firewall
3124 software warned about binding to UDP sockets, regardless of
3125 whether packets were sent. Now we try to use getifaddrs(),
3126 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
3127 system supports. Resolves ticket 1827.
3129 o Major security workaround:
3130 - When building or running with any version of OpenSSL earlier
3131 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
3132 versions have a bug (CVE-2011-4576) in which their block cipher
3133 padding includes uninitialized data, potentially leaking sensitive
3134 information to any peer with whom they make a SSLv3 connection. Tor
3135 does not use SSL v3 by default, but a hostile client or server
3136 could force an SSLv3 connection in order to gain information that
3137 they shouldn't have been able to get. The best solution here is to
3138 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
3139 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
3140 to make sure that the bug can't happen.
3143 - Fix the SOCKET_OK test that we use to tell when socket
3144 creation fails so that it works on Win64. Fixes part of bug 4533;
3145 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
3146 - Correct our replacements for the timeradd() and timersub() functions
3147 on platforms that lack them (for example, Windows). The timersub()
3148 function is used when expiring circuits, while timeradd() is
3149 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
3150 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
3151 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
3152 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
3153 bug at runtime, not compile time, because some distributions hack
3154 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
3155 on 0.2.3.9-alpha. Found by Pascal.
3157 o Minor features (controller):
3158 - Use absolute path names when reporting the torrc filename in the
3159 control protocol, so a controller can more easily find the torrc
3160 file. Resolves bug 1101.
3161 - Extend the control protocol to report flags that control a circuit's
3162 path selection in CIRC events and in replies to 'GETINFO
3163 circuit-status'. Implements part of ticket 2411.
3164 - Extend the control protocol to report the hidden service address
3165 and current state of a hidden-service-related circuit in CIRC
3166 events and in replies to 'GETINFO circuit-status'. Implements part
3168 - When reporting the path to the cookie file to the controller,
3169 give an absolute path. Resolves ticket 4881.
3170 - Allow controllers to request an event notification whenever a
3171 circuit is cannibalized or its purpose is changed. Implements
3172 part of ticket 3457.
3173 - Include the creation time of a circuit in CIRC and CIRC2
3174 control-port events and the list produced by the 'GETINFO
3175 circuit-status' control-port command.
3177 o Minor features (directory authorities):
3178 - Directory authorities now reject versions of Tor older than
3179 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
3180 inclusive. These versions accounted for only a small fraction of
3181 the Tor network, and have numerous known security issues. Resolves
3183 - Authority operators can now vote for all relays in a given
3184 set of countries to be BadDir/BadExit/Invalid/Rejected.
3185 - Provide two consensus parameters (FastFlagMinThreshold and
3186 FastFlagMaxThreshold) to control the range of allowable bandwidths
3187 for the Fast directory flag. These allow authorities to run
3188 experiments on appropriate requirements for being a "Fast" node.
3189 The AuthDirFastGuarantee config value still applies. Implements
3191 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
3192 directory authority option (introduced in Tor 0.2.2.34).
3194 o Minor features (other):
3195 - Don't disable the DirPort when we cannot exceed our AccountingMax
3196 limit during this interval because the effective bandwidthrate is
3197 low enough. This is useful in a situation where AccountMax is only
3198 used as an additional safeguard or to provide statistics.
3199 - Prepend an informative header to generated dynamic_dh_params files.
3200 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
3201 EntryNodes will have no effect. Resolves issue 2571.
3202 - Log more useful messages when we fail to disable debugger
3204 - Log which authority we're missing votes from when we go to fetch
3205 them from the other auths.
3206 - Log (at debug level) whenever a circuit's purpose is changed.
3207 - Add missing documentation for the MaxClientCircuitsPending,
3208 UseMicrodescriptors, UserspaceIOCPBuffers, and
3209 _UseFilteringSSLBufferevents options, all introduced during
3211 - Update to the January 3 2012 Maxmind GeoLite Country database.
3213 o Minor bugfixes (hidden services):
3214 - Don't close hidden service client circuits which have almost
3215 finished connecting to their destination when they reach
3216 the normal circuit-build timeout. Previously, we would close
3217 introduction circuits which are waiting for an acknowledgement
3218 from the introduction point, and rendezvous circuits which have
3219 been specified in an INTRODUCE1 cell sent to a hidden service,
3220 after the normal CBT. Now, we mark them as 'timed out', and launch
3221 another rendezvous attempt in parallel. This behavior change can
3222 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
3223 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
3224 - Don't close hidden-service-side rendezvous circuits when they
3225 reach the normal circuit-build timeout. This behaviour change can
3226 be disabled using the new
3227 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
3228 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
3229 - Make sure we never mark the wrong rendezvous circuit as having
3230 had its introduction cell acknowleged by the introduction-point
3231 relay. Previously, when we received an INTRODUCE_ACK cell on a
3232 client-side hidden-service introduction circuit, we might have
3233 marked a rendezvous circuit other than the one we specified in
3234 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
3235 a warning message and interfered with the hidden service
3236 connection-establishment process. Fixes bug 4759; bugfix on
3237 0.2.3.3-alpha, when we added the stream-isolation feature which
3238 might cause Tor to open multiple rendezvous circuits for the same
3240 - Don't trigger an assertion failure when we mark a new client-side
3241 hidden-service introduction circuit for close during the process
3242 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
3245 o Minor bugfixes (log messages):
3246 - Correctly spell "connect" in a log message on failure to create a
3247 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
3249 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
3250 Fixes bug 4856; bugfix on Tor 0.0.6.
3251 - Fix the log message describing how we work around discovering
3252 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
3253 4837; bugfix on 0.2.2.9-alpha.
3254 - When logging about a disallowed .exit name, do not also call it
3255 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
3257 o Minor bugfixes (build fixes):
3258 - During configure, detect when we're building with clang version
3259 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
3260 CFLAGS. clang doesn't support them yet.
3261 - During configure, search for library containing cos function as
3262 libm lives in libcore on some platforms (BeOS/Haiku). Linking
3263 against libm was hard-coded before. Fixes the first part of bug
3264 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
3266 - Detect attempts to build Tor on (as yet hypothetical) versions
3267 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
3268 fix for bug 4533. Bugfix on 0.2.2.28-beta.
3269 - Preprocessor directives should not be put inside the arguments
3270 of a macro. This would break compilation with GCC releases prior
3271 to version 3.3. We would never recommend such an old GCC version,
3272 but it is apparently required for binary compatibility on some
3273 platforms (namely, certain builds of Haiku). Fixes the other part
3274 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
3277 o Minor bugfixes (other):
3278 - Older Linux kernels erroneously respond to strange nmap behavior
3279 by having accept() return successfully with a zero-length
3280 socket. When this happens, just close the connection. Previously,
3281 we would try harder to learn the remote address: but there was
3282 no such remote address to learn, and our method for trying to
3283 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
3284 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
3285 - Fix null-pointer access that could occur if TLS allocation failed.
3286 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
3287 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
3288 accidentally been reverted.
3289 - Fix our implementation of crypto_random_hostname() so it can't
3290 overflow on ridiculously large inputs. (No Tor version has ever
3291 provided this kind of bad inputs, but let's be correct in depth.)
3292 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
3293 - Find more places in the code that should have been testing for
3294 invalid sockets using the SOCKET_OK macro. Required for a fix
3295 for bug 4533. Bugfix on 0.2.2.28-beta.
3296 - Fix an assertion failure when, while running with bufferevents, a
3297 connection finishes connecting after it is marked for close, but
3298 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
3299 - test_util_spawn_background_ok() hardcoded the expected value
3300 for ENOENT to 2. This isn't portable as error numbers are
3301 platform specific, and particularly the hurd has ENOENT at
3302 0x40000002. Construct expected string at runtime, using the correct
3303 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
3304 - Reject attempts to disable DisableDebuggerAttachment while Tor is
3305 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
3306 - Use an appropriate-width type for sockets in tor-fw-helper on
3307 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
3310 - When sending or relaying a RELAY_EARLY cell, we used to convert
3311 it to a RELAY cell if the connection was using the v1 link
3312 protocol. This was a workaround for older versions of Tor, which
3313 didn't handle RELAY_EARLY cells properly. Now that all supported
3314 versions can handle RELAY_EARLY cells, and now that we're enforcing
3315 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
3316 remove this workaround. Addresses bug 4786.
3318 o Code simplifications and refactoring:
3319 - Use OpenSSL's built-in SSL_state_string_long() instead of our
3320 own homebrewed ssl_state_to_string() replacement. Patch from
3321 Emile Snyder. Fixes bug 4653.
3322 - Use macros to indicate OpenSSL versions, so we don't need to worry
3323 about accidental hexadecimal bit shifts.
3324 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
3326 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
3327 - Use the smartlist_add_asprintf() alias more consistently.
3328 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
3329 invalid value, rather than just -1.
3330 - Rename a handful of old identifiers, mostly related to crypto
3331 structures and crypto functions. By convention, our "create an
3332 object" functions are called "type_new()", our "free an object"
3333 functions are called "type_free()", and our types indicate that
3334 they are types only with a final "_t". But a handful of older
3335 types and functions broke these rules, with function names like
3336 "type_create" or "subsystem_op_type", or with type names like
3340 Changes in version 0.2.3.10-alpha - 2011-12-16
3341 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
3342 Tor's buffers code. Absolutely everybody should upgrade.
3344 The bug relied on an incorrect calculation when making data continuous
3345 in one of our IO buffers, if the first chunk of the buffer was
3346 misaligned by just the wrong amount. The miscalculation would allow an
3347 attacker to overflow a piece of heap-allocated memory. To mount this
3348 attack, the attacker would need to either open a SOCKS connection to
3349 Tor's SocksPort (usually restricted to localhost), or target a Tor
3350 instance configured to make its connections through a SOCKS proxy
3351 (which Tor does not do by default).
3353 Good security practice requires that all heap-overflow bugs should be
3354 presumed to be exploitable until proven otherwise, so we are treating
3355 this as a potential code execution attack. Please upgrade immediately!
3356 This bug does not affect bufferevents-based builds of Tor. Special
3357 thanks to "Vektor" for reporting this issue to us!
3359 This release also contains a few minor bugfixes for issues discovered
3363 - Fix a heap overflow bug that could occur when trying to pull
3364 data into the first chunk of a buffer, when that chunk had
3365 already had some data drained from it. Fixes CVE-2011-2778;
3366 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3369 - If we can't attach streams to a rendezvous circuit when we
3370 finish connecting to a hidden service, clear the rendezvous
3371 circuit's stream-isolation state and try to attach streams
3372 again. Previously, we cleared rendezvous circuits' isolation
3373 state either too early (if they were freshly built) or not at all
3374 (if they had been built earlier and were cannibalized). Bugfix on
3375 0.2.3.3-alpha; fixes bug 4655.
3376 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
3377 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
3378 - Fix an assertion failure when a relay with accounting enabled
3379 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
3382 - Update to the December 6 2011 Maxmind GeoLite Country database.
3385 Changes in version 0.2.2.35 - 2011-12-16
3386 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
3387 buffers code. Absolutely everybody should upgrade.
3389 The bug relied on an incorrect calculation when making data continuous
3390 in one of our IO buffers, if the first chunk of the buffer was
3391 misaligned by just the wrong amount. The miscalculation would allow an
3392 attacker to overflow a piece of heap-allocated memory. To mount this
3393 attack, the attacker would need to either open a SOCKS connection to
3394 Tor's SocksPort (usually restricted to localhost), or target a Tor
3395 instance configured to make its connections through a SOCKS proxy
3396 (which Tor does not do by default).
3398 Good security practice requires that all heap-overflow bugs should be
3399 presumed to be exploitable until proven otherwise, so we are treating
3400 this as a potential code execution attack. Please upgrade immediately!
3401 This bug does not affect bufferevents-based builds of Tor. Special
3402 thanks to "Vektor" for reporting this issue to us!
3404 Tor 0.2.2.35 also fixes several bugs in previous versions, including
3405 crash bugs for unusual configurations, and a long-term bug that
3406 would prevent Tor from starting on Windows machines with draconian
3409 With this release, we remind everyone that 0.2.0.x has reached its
3410 formal end-of-life. Those Tor versions have many known flaws, and
3411 nobody should be using them. You should upgrade -- ideally to the
3412 0.2.2.x series. If you're using a Linux or BSD and its packages are
3413 obsolete, stop using those packages and upgrade anyway.
3415 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
3416 longer receive support after some time in early 2012.
3419 - Fix a heap overflow bug that could occur when trying to pull
3420 data into the first chunk of a buffer, when that chunk had
3421 already had some data drained from it. Fixes CVE-2011-2778;
3422 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3423 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3424 that it doesn't attempt to allocate a socketpair. This could cause
3425 some problems on Windows systems with overzealous firewalls. Fix for
3426 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3428 - If we mark an OR connection for close based on a cell we process,
3429 don't process any further cells on it. We already avoid further
3430 reads on marked-for-close connections, but now we also discard the
3431 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3432 which was the first version where we might mark a connection for
3433 close based on processing a cell on it.
3434 - Correctly sanity-check that we don't underflow on a memory
3435 allocation (and then assert) for hidden service introduction
3436 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3437 bugfix on 0.2.1.5-alpha.
3438 - Fix a memory leak when we check whether a hidden service
3439 descriptor has any usable introduction points left. Fixes bug
3440 4424. Bugfix on 0.2.2.25-alpha.
3441 - Don't crash when we're running as a relay and don't have a GeoIP
3442 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
3443 we've had in the 0.2.3.x branch already.
3444 - When running as a client, do not print a misleading (and plain
3445 wrong) log message that we're collecting "directory request"
3446 statistics: clients don't collect statistics. Also don't create a
3447 useless (because empty) stats file in the stats/ directory. Fixes
3448 bug 4353; bugfix on 0.2.2.34.
3451 - Detect failure to initialize Libevent. This fix provides better
3452 detection for future instances of bug 4457.
3453 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3454 function. This was eating up hideously large amounts of time on some
3455 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3456 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3457 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3459 - Don't warn about unused log_mutex in log.c when building with
3460 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3461 0.1.0.6-rc which introduced --disable-threads.
3462 - When configuring, starting, or stopping an NT service, stop
3463 immediately after the service configuration attempt has succeeded
3464 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3465 - When sending a NETINFO cell, include the original address
3466 received for the other side, not its canonical address. Found
3467 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3468 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
3469 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3470 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3471 occurred when a client tried to fetch a descriptor for a bridge
3472 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3473 - Backport fixes for a pair of compilation warnings on Windows.
3474 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
3475 - If we had ever tried to call tor_addr_to_str on an address of
3476 unknown type, we would have done a strdup on an uninitialized
3477 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3478 Reported by "troll_un".
3479 - Correctly detect and handle transient lookup failures from
3480 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3481 Reported by "troll_un".
3482 - Fix null-pointer access that could occur if TLS allocation failed.
3483 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3484 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3485 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3488 - Add two new config options for directory authorities:
3489 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3490 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3491 that is always sufficient to satisfy the bandwidth requirement for
3492 the Guard flag. Now it will be easier for researchers to simulate
3493 Tor networks with different values. Resolves ticket 4484.
3494 - When Tor ignores a hidden service specified in its configuration,
3495 include the hidden service's directory in the warning message.
3496 Previously, we would only tell the user that some hidden service
3497 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3498 - Update to the December 6 2011 Maxmind GeoLite Country database.
3500 o Packaging changes:
3501 - Make it easier to automate expert package builds on Windows,
3502 by removing an absolute path from makensis.exe command.
3505 Changes in version 0.2.1.32 - 2011-12-16
3506 Tor 0.2.1.32 backports important security and privacy fixes for
3507 oldstable. This release is intended only for package maintainers and
3508 others who cannot use the 0.2.2 stable series. All others should be
3509 using Tor 0.2.2.x or newer.
3511 The Tor 0.2.1.x series will reach formal end-of-life some time in
3512 early 2012; we will stop releasing patches for it then.
3514 o Major bugfixes (also included in 0.2.2.x):
3515 - Correctly sanity-check that we don't underflow on a memory
3516 allocation (and then assert) for hidden service introduction
3517 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3518 bugfix on 0.2.1.5-alpha.
3519 - Fix a heap overflow bug that could occur when trying to pull
3520 data into the first chunk of a buffer, when that chunk had
3521 already had some data drained from it. Fixes CVE-2011-2778;
3522 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3525 - Update to the December 6 2011 Maxmind GeoLite Country database.
3528 Changes in version 0.2.3.9-alpha - 2011-12-08
3529 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
3530 a "DisableNetwork" security feature that bundles can use to avoid
3531 touching the network until bridges are configured, moves forward on
3532 the pluggable transport design, fixes a flaw in the hidden service
3533 design that unnecessarily prevented clients with wrong clocks from
3534 reaching hidden services, and fixes a wide variety of other issues.
3537 - Clients can now connect to private bridges over IPv6. Bridges
3538 still need at least one IPv4 address in order to connect to
3539 other relays. Note that we don't yet handle the case where the
3540 user has two bridge lines for the same bridge (one IPv4, one
3541 IPv6). Implements parts of proposal 186.
3542 - New "DisableNetwork" config option to prevent Tor from launching any
3543 connections or accepting any connections except on a control port.
3544 Bundles and controllers can set this option before letting Tor talk
3545 to the rest of the network, for example to prevent any connections
3546 to a non-bridge address. Packages like Orbot can also use this
3547 option to instruct Tor to save power when the network is off.
3548 - Clients and bridges can now be configured to use a separate
3549 "transport" proxy. This approach makes the censorship arms race
3550 easier by allowing bridges to use protocol obfuscation plugins. It
3551 implements the "managed proxy" part of proposal 180 (ticket 3472).
3552 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
3553 implementation. It makes AES_CTR about 7% faster than our old one
3554 (which was about 10% faster than the one OpenSSL used to provide).
3555 Resolves ticket 4526.
3556 - Add a "tor2web mode" for clients that want to connect to hidden
3557 services non-anonymously (and possibly more quickly). As a safety
3558 measure to try to keep users from turning this on without knowing
3559 what they are doing, tor2web mode must be explicitly enabled at
3560 compile time, and a copy of Tor compiled to run in tor2web mode
3561 cannot be used as a normal Tor client. Implements feature 2553.
3562 - Add experimental support for running on Windows with IOCP and no
3563 kernel-space socket buffers. This feature is controlled by a new
3564 "UserspaceIOCPBuffers" config option (off by default), which has
3565 no effect unless Tor has been built with support for bufferevents,
3566 is running on Windows, and has enabled IOCP. This may, in the long
3567 run, help solve or mitigate bug 98.
3568 - Use a more secure consensus parameter voting algorithm. Now at
3569 least three directory authorities or a majority of them must
3570 vote on a given parameter before it will be included in the
3571 consensus. Implements proposal 178.
3574 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
3575 They used to check that the timestamp was within 30 minutes
3576 of their system clock, so they could cap the size of their
3577 replay-detection cache, but that approach unnecessarily refused
3578 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
3579 the v3 intro-point protocol (the first one which sent a timestamp
3580 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
3581 - Only use the EVP interface when AES acceleration is enabled,
3582 to avoid a 5-7% performance regression. Resolves issue 4525;
3583 bugfix on 0.2.3.8-alpha.
3585 o Privacy/anonymity features (bridge detection):
3586 - Make bridge SSL certificates a bit more stealthy by using random
3587 serial numbers, in the same fashion as OpenSSL when generating
3588 self-signed certificates. Implements ticket 4584.
3589 - Introduce a new config option "DynamicDHGroups", enabled by
3590 default, which provides each bridge with a unique prime DH modulus
3591 to be used during SSL handshakes. This option attempts to help
3592 against censors who might use the Apache DH modulus as a static
3593 identifier for bridges. Addresses ticket 4548.
3595 o Minor features (new/different config options):
3596 - New configuration option "DisableDebuggerAttachment" (on by default)
3597 to prevent basic debugging attachment attempts by other processes.
3598 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
3599 - Allow MapAddress directives to specify matches against super-domains,
3600 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
3601 Implements issue 933.
3602 - Slightly change behavior of "list" options (that is, config
3603 options that can appear more than once) when they appear both in
3604 torrc and on the command line. Previously, the command-line options
3605 would be appended to the ones from torrc. Now, the command-line
3606 options override the torrc options entirely. This new behavior
3607 allows the user to override list options (like exit policies and
3608 ports to listen on) from the command line, rather than simply
3609 appending to the list.
3610 - You can get the old (appending) command-line behavior for "list"
3611 options by prefixing the option name with a "+".
3612 - You can remove all the values for a "list" option from the command
3613 line without adding any new ones by prefixing the option name
3615 - Add experimental support for a "defaults" torrc file to be parsed
3616 before the regular torrc. Torrc options override the defaults file's
3617 options in the same way that the command line overrides the torrc.
3618 The SAVECONF controller command saves only those options which
3619 differ between the current configuration and the defaults file. HUP
3620 reloads both files. (Note: This is an experimental feature; its
3621 behavior will probably be refined in future 0.2.3.x-alpha versions
3622 to better meet packagers' needs.) Implements task 4552.
3625 - Try to make the introductory warning message that Tor prints on
3626 startup more useful for actually finding help and information.
3627 Resolves ticket 2474.
3628 - Running "make version" now displays the version of Tor that
3629 we're about to build. Idea from katmagic; resolves issue 4400.
3630 - Expire old or over-used hidden service introduction points.
3631 Required by fix for bug 3460.
3632 - Move the replay-detection cache for the RSA-encrypted parts of
3633 INTRODUCE2 cells to the introduction point data structures.
3634 Previously, we would use one replay-detection cache per hidden
3635 service. Required by fix for bug 3460.
3636 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
3637 public key replay-detection cache from 60 minutes to 5 minutes. This
3638 replay-detection cache is now used only to detect multiple
3639 INTRODUCE2 cells specifying the same rendezvous point, so we can
3640 avoid launching multiple simultaneous attempts to connect to it.
3642 o Minor bugfixes (on Tor 0.2.2.x and earlier):
3643 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3644 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3646 - Fix a minor formatting issue in one of tor-gencert's error messages.
3648 - Prevent a false positive from the check-spaces script, by disabling
3649 the "whitespace between function name and (" check for functions
3651 - Fix a log message suggesting that people contact a non-existent
3652 email address. Fixes bug 3448.
3653 - Fix null-pointer access that could occur if TLS allocation failed.
3654 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3655 - Report a real bootstrap problem to the controller on router
3656 identity mismatch. Previously we just said "foo", which probably
3657 made a lot of sense at the time. Fixes bug 4169; bugfix on
3659 - If we had ever tried to call tor_addr_to_str() on an address of
3660 unknown type, we would have done a strdup() on an uninitialized
3661 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3662 Reported by "troll_un".
3663 - Correctly detect and handle transient lookup failures from
3664 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3665 Reported by "troll_un".
3666 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3667 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3668 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
3669 bug 4532; found by "troll_un".
3671 o Minor bugfixes (on Tor 0.2.3.x):
3672 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
3674 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
3675 circuit for use as a hidden service client's rendezvous point.
3676 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
3677 with help from wanoskarnet.
3678 - Restore behavior of overriding SocksPort, ORPort, and similar
3679 options from the command line. Bugfix on 0.2.3.3-alpha.
3682 - Properly handle the case where the build-tree is not the same
3683 as the source tree when generating src/common/common_sha1.i,
3684 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
3685 bugfix on 0.2.0.1-alpha.
3687 o Code simplifications, cleanups, and refactorings:
3688 - Remove the pure attribute from all functions that used it
3689 previously. In many cases we assigned it incorrectly, because the
3690 functions might assert or call impure functions, and we don't have
3691 evidence that keeping the pure attribute is worthwhile. Implements
3692 changes suggested in ticket 4421.
3693 - Remove some dead code spotted by coverity. Fixes cid 432.
3694 Bugfix on 0.2.3.1-alpha, closes bug 4637.
3697 Changes in version 0.2.3.8-alpha - 2011-11-22
3698 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
3699 socketpair-related bug that has been bothering Windows users. It adds
3700 support to serve microdescriptors to controllers, so Vidalia's network
3701 map can resume listing relays (once Vidalia implements its side),
3702 and adds better support for hardware AES acceleration. Finally, it
3703 starts the process of adjusting the bandwidth cutoff for getting the
3704 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
3705 that tiny relays harm performance more than they help network capacity.
3708 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3709 that it doesn't attempt to allocate a socketpair. This could cause
3710 some problems on Windows systems with overzealous firewalls. Fix for
3711 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3713 - Correctly sanity-check that we don't underflow on a memory
3714 allocation (and then assert) for hidden service introduction
3715 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3716 bugfix on 0.2.1.5-alpha.
3717 - Remove the artificially low cutoff of 20KB to guarantee the Fast
3718 flag. In the past few years the average relay speed has picked
3719 up, and while the "top 7/8 of the network get the Fast flag" and
3720 "all relays with 20KB or more of capacity get the Fast flag" rules
3721 used to have the same result, now the top 7/8 of the network has
3722 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
3723 - Fix a rare assertion failure when checking whether a v0 hidden
3724 service descriptor has any usable introduction points left, and
3725 we don't have enough information to build a circuit to the first
3726 intro point named in the descriptor. The HS client code in
3727 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
3728 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
3729 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
3730 - Make bridge authorities not crash when they are asked for their own
3731 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
3732 - When running as a client, do not print a misleading (and plain
3733 wrong) log message that we're collecting "directory request"
3734 statistics: clients don't collect statistics. Also don't create a
3735 useless (because empty) stats file in the stats/ directory. Fixes
3736 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
3739 - Allow Tor controllers like Vidalia to obtain the microdescriptor
3740 for a relay by identity digest or nickname. Previously,
3741 microdescriptors were only available by their own digests, so a
3742 controller would have to ask for and parse the whole microdescriptor
3743 consensus in order to look up a single relay's microdesc. Fixes
3744 bug 3832; bugfix on 0.2.3.1-alpha.
3745 - Use OpenSSL's EVP interface for AES encryption, so that all AES
3746 operations can use hardware acceleration (if present). Resolves
3749 o Minor bugfixes (on 0.2.2.x and earlier):
3750 - Detect failure to initialize Libevent. This fix provides better
3751 detection for future instances of bug 4457.
3752 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3753 function. This was eating up hideously large amounts of time on some
3754 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3755 - Don't warn about unused log_mutex in log.c when building with
3756 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3757 0.1.0.6-rc which introduced --disable-threads.
3758 - Allow manual 'authenticate' commands to the controller interface
3759 from netcat (nc) as well as telnet. We were rejecting them because
3760 they didn't come with the expected whitespace at the end of the
3761 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
3762 - Fix some (not actually triggerable) buffer size checks in usage of
3763 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
3765 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
3766 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
3767 - When configuring, starting, or stopping an NT service, stop
3768 immediately after the service configuration attempt has succeeded
3769 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3770 - When sending a NETINFO cell, include the original address
3771 received for the other side, not its canonical address. Found
3772 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3773 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
3774 can pick them up when the tests aren't disabled. Bugfix on
3775 0.2.2.4-alpha which introduced tinytest.
3776 - Fix a memory leak when we check whether a hidden service
3777 descriptor has any usable introduction points left. Fixes bug
3778 4424. Bugfix on 0.2.2.25-alpha.
3779 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3780 occurred when a client tried to fetch a descriptor for a bridge
3781 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3783 o Minor bugfixes (on 0.2.3.x):
3784 - Make util unit tests build correctly with MSVC. Bugfix on
3785 0.2.3.3-alpha. Patch by Gisle Vanem.
3786 - Successfully detect AUTH_CHALLENGE cells with no recognized
3787 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
3789 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
3790 it should still send a NETINFO cell to allow the connection to
3791 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
3793 - Log less loudly when we get an invalid authentication certificate
3794 from a source other than a directory authority: it's not unusual
3795 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
3797 - Tolerate servers with more clock skew in their authentication
3798 certificates than previously. Fixes bug 4371; bugfix on
3800 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
3801 on 0.2.3.4-alpha and 0.2.3.6-alpha.
3804 - Add two new config options for directory authorities:
3805 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3806 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3807 that is always sufficient to satisfy the bandwidth requirement for
3808 the Guard flag. Now it will be easier for researchers to simulate
3809 Tor networks with different values. Resolves ticket 4484.
3810 - When Tor ignores a hidden service specified in its configuration,
3811 include the hidden service's directory in the warning message.
3812 Previously, we would only tell the user that some hidden service
3813 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3814 - When we fail to initialize Libevent, retry with IOCP disabled so we
3815 don't need to turn on multi-threading support in Libevent, which in
3816 turn requires a working socketpair(). This is a workaround for bug
3817 4457, which affects Libevent versions from 2.0.1-alpha through
3819 - Detect when we try to build on a platform that doesn't define
3820 AF_UNSPEC to 0. We don't work there, so refuse to compile.
3821 - Update to the November 1 2011 Maxmind GeoLite Country database.
3823 o Packaging changes:
3824 - Make it easier to automate expert package builds on Windows,
3825 by removing an absolute path from makensis.exe command.
3827 o Code simplifications and refactoring:
3828 - Remove some redundant #include directives throughout the code.
3829 Patch from Andrea Gelmini.
3830 - Unconditionally use OpenSSL's AES implementation instead of our
3831 old built-in one. OpenSSL's AES has been better for a while, and
3832 relatively few servers should still be on any version of OpenSSL
3833 that doesn't have good optimized assembly AES.
3834 - Use the name "CERTS" consistently to refer to the new cell type;
3835 we were calling it CERT in some places and CERTS in others.
3838 - Numerous new unit tests for functions in util.c and address.c by
3840 - The long-disabled benchmark tests are now split into their own
3841 ./src/test/bench binary.
3842 - The benchmark tests can now use more accurate timers than
3843 gettimeofday() when such timers are available.
3846 Changes in version 0.2.3.7-alpha - 2011-10-30
3847 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
3848 the new v3 handshake. It also resolves yet another bridge address
3852 - If we mark an OR connection for close based on a cell we process,
3853 don't process any further cells on it. We already avoid further
3854 reads on marked-for-close connections, but now we also discard the
3855 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3856 which was the first version where we might mark a connection for
3857 close based on processing a cell on it.
3858 - Fix a double-free bug that would occur when we received an invalid
3859 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
3860 bugfix on 0.2.3.6-alpha.
3861 - Bridges no longer include their address in NETINFO cells on outgoing
3862 OR connections, to allow them to blend in better with clients.
3863 Removes another avenue for enumerating bridges. Reported by
3864 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
3865 cells were introduced.
3868 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
3869 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3872 Changes in version 0.2.3.6-alpha - 2011-10-26
3873 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
3874 anonymity vulnerability where an attacker can deanonymize Tor
3875 users. Everybody should upgrade.
3877 This release also features support for a new v3 connection handshake
3878 protocol, and fixes to make hidden service connections more robust.
3881 - Implement a new handshake protocol (v3) for authenticating Tors to
3882 each other over TLS. It should be more resistant to fingerprinting
3883 than previous protocols, and should require less TLS hacking for
3884 future Tor implementations. Implements proposal 176.
3885 - Allow variable-length padding cells to disguise the length of
3886 Tor's TLS records. Implements part of proposal 184.
3888 o Privacy/anonymity fixes (clients):
3889 - Clients and bridges no longer send TLS certificate chains on
3890 outgoing OR connections. Previously, each client or bridge would
3891 use the same cert chain for all outgoing OR connections until
3892 its IP address changes, which allowed any relay that the client
3893 or bridge contacted to determine which entry guards it is using.
3894 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3895 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3896 no longer considers that connection as suitable for satisfying a
3897 circuit EXTEND request. Now relays can protect clients from the
3898 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3899 - Directory authorities no longer assign the Guard flag to relays
3900 that haven't upgraded to the above "refuse EXTEND requests
3901 to client connections" fix. Now directory authorities can
3902 protect clients from the CVE-2011-2768 issue even if neither
3903 the clients nor the relays have upgraded yet. There's a new
3904 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3905 to let us transition smoothly, else tomorrow there would be no
3908 o Major bugfixes (hidden services):
3909 - Improve hidden service robustness: when an attempt to connect to
3910 a hidden service ends, be willing to refetch its hidden service
3911 descriptors from each of the HSDir relays responsible for them
3912 immediately. Previously, we would not consider refetching the
3913 service's descriptors from each HSDir for 15 minutes after the last
3914 fetch, which was inconvenient if the hidden service was not running
3915 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
3916 - When one of a hidden service's introduction points appears to be
3917 unreachable, stop trying it. Previously, we would keep trying
3918 to build circuits to the introduction point until we lost the
3919 descriptor, usually because the user gave up and restarted Tor.
3920 Partly fixes bug 3825.
3921 - Don't launch a useless circuit after failing to use one of a
3922 hidden service's introduction points. Previously, we would
3923 launch a new introduction circuit, but not set the hidden service
3924 which that circuit was intended to connect to, so it would never
3925 actually be used. A different piece of code would then create a
3926 new introduction circuit correctly. Bug reported by katmagic and
3927 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3929 o Major bugfixes (other):
3930 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3931 that they initiated. Relays could distinguish incoming bridge
3932 connections from client connections, creating another avenue for
3933 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3934 Found by "frosty_un".
3935 - Don't update the AccountingSoftLimitHitAt state file entry whenever
3936 tor gets started. This prevents a wrong average bandwidth
3937 estimate, which would cause relays to always start a new accounting
3938 interval at the earliest possible moment. Fixes bug 2003; bugfix
3939 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
3940 immensely in tracking this bug down.
3941 - Fix a crash bug when changing node restrictions while a DNS lookup
3942 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3945 o Minor bugfixes (on 0.2.2.x and earlier):
3946 - When a hidden service turns an extra service-side introduction
3947 circuit into a general-purpose circuit, free the rend_data and
3948 intro_key fields first, so we won't leak memory if the circuit
3949 is cannibalized for use as another service-side introduction
3950 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3951 - Rephrase the log message emitted if the TestSocks check is
3952 successful. Patch from Fabian Keil; fixes bug 4094.
3953 - Bridges now skip DNS self-tests, to act a little more stealthily.
3954 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3955 bridges. Patch by "warms0x".
3956 - Remove a confusing dollar sign from the example fingerprint in the
3957 man page, and also make the example fingerprint a valid one. Fixes
3958 bug 4309; bugfix on 0.2.1.3-alpha.
3959 - Fix internal bug-checking logic that was supposed to catch
3960 failures in digest generation so that it will fail more robustly
3961 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3962 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3963 - Report any failure in init_keys() calls launched because our
3964 IP address has changed. Spotted by Coverity Scan. Bugfix on
3965 0.1.1.4-alpha; fixes CID 484.
3967 o Minor bugfixes (on 0.2.3.x):
3968 - Fix a bug in configure.in that kept it from building a configure
3969 script with autoconf versions earlier than 2.61. Fixes bug 2430;
3970 bugfix on 0.2.3.1-alpha.
3971 - Don't warn users that they are exposing a client port to the
3972 Internet if they have specified an RFC1918 address. Previously,
3973 we would warn if the user had specified any non-loopback
3974 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
3975 - Fix memory leaks in the failing cases of the new SocksPort and
3976 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
3977 fixes coverity CIDs 485, 486, and 487.
3980 - When a hidden service's introduction point times out, consider
3981 trying it again during the next attempt to connect to the
3982 HS. Previously, we would not try it again unless a newly fetched
3983 descriptor contained it. Required by fixes for bugs 1297 and 3825.
3984 - The next version of Windows will be called Windows 8, and it has
3985 a major version of 6, minor version of 2. Correctly identify that
3986 version instead of calling it "Very recent version". Resolves
3987 ticket 4153; reported by funkstar.
3988 - The Bridge Authority now writes statistics on how many bridge
3989 descriptors it gave out in total, and how many unique descriptors
3990 it gave out. It also lists how often the most and least commonly
3991 fetched descriptors were given out, as well as the median and
3992 25th/75th percentile. Implements tickets 4200 and 4294.
3993 - Update to the October 4 2011 Maxmind GeoLite Country database.
3995 o Code simplifications and refactoring:
3996 - Remove some old code to remember statistics about which descriptors
3997 we've served as a directory mirror. The feature wasn't used and
3998 is outdated now that microdescriptors are around.
3999 - Rename Tor functions that turn strings into addresses, so that
4000 "parse" indicates that no hostname resolution occurs, and
4001 "lookup" indicates that hostname resolution may occur. This
4002 should help prevent mistakes in the future. Fixes bug 3512.
4005 Changes in version 0.2.2.34 - 2011-10-26
4006 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
4007 can deanonymize Tor users. Everybody should upgrade.
4009 The attack relies on four components: 1) Clients reuse their TLS cert
4010 when talking to different relays, so relays can recognize a user by
4011 the identity key in her cert. 2) An attacker who knows the client's
4012 identity key can probe each guard relay to see if that identity key
4013 is connected to that guard relay right now. 3) A variety of active
4014 attacks in the literature (starting from "Low-Cost Traffic Analysis
4015 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
4016 discover the guard relays that a Tor user visiting the website is using.
4017 4) Clients typically pick three guards at random, so the set of guards
4018 for a given user could well be a unique fingerprint for her. This
4019 release fixes components #1 and #2, which is enough to block the attack;
4020 the other two remain as open research problems. Special thanks to
4021 "frosty_un" for reporting the issue to us!
4023 Clients should upgrade so they are no longer recognizable by the TLS
4024 certs they present. Relays should upgrade so they no longer allow a
4025 remote attacker to probe them to test whether unpatched clients are
4026 currently connected to them.
4028 This release also fixes several vulnerabilities that allow an attacker
4029 to enumerate bridge relays. Some bridge enumeration attacks still
4030 remain; see for example proposal 188.
4032 o Privacy/anonymity fixes (clients):
4033 - Clients and bridges no longer send TLS certificate chains on
4034 outgoing OR connections. Previously, each client or bridge would
4035 use the same cert chain for all outgoing OR connections until
4036 its IP address changes, which allowed any relay that the client
4037 or bridge contacted to determine which entry guards it is using.
4038 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
4039 - If a relay receives a CREATE_FAST cell on a TLS connection, it
4040 no longer considers that connection as suitable for satisfying a
4041 circuit EXTEND request. Now relays can protect clients from the
4042 CVE-2011-2768 issue even if the clients haven't upgraded yet.
4043 - Directory authorities no longer assign the Guard flag to relays
4044 that haven't upgraded to the above "refuse EXTEND requests
4045 to client connections" fix. Now directory authorities can
4046 protect clients from the CVE-2011-2768 issue even if neither
4047 the clients nor the relays have upgraded yet. There's a new
4048 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
4049 to let us transition smoothly, else tomorrow there would be no
4052 o Privacy/anonymity fixes (bridge enumeration):
4053 - Bridge relays now do their directory fetches inside Tor TLS
4054 connections, like all the other clients do, rather than connecting
4055 directly to the DirPort like public relays do. Removes another
4056 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
4057 - Bridges relays now build circuits for themselves in a more similar
4058 way to how clients build them. Removes another avenue for
4059 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
4060 when bridges were introduced.
4061 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
4062 that they initiated. Relays could distinguish incoming bridge
4063 connections from client connections, creating another avenue for
4064 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
4065 Found by "frosty_un".
4068 - Fix a crash bug when changing node restrictions while a DNS lookup
4069 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
4071 - Don't launch a useless circuit after failing to use one of a
4072 hidden service's introduction points. Previously, we would
4073 launch a new introduction circuit, but not set the hidden service
4074 which that circuit was intended to connect to, so it would never
4075 actually be used. A different piece of code would then create a
4076 new introduction circuit correctly. Bug reported by katmagic and
4077 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
4080 - Change an integer overflow check in the OpenBSD_Malloc code so
4081 that GCC is less likely to eliminate it as impossible. Patch
4082 from Mansour Moufid. Fixes bug 4059.
4083 - When a hidden service turns an extra service-side introduction
4084 circuit into a general-purpose circuit, free the rend_data and
4085 intro_key fields first, so we won't leak memory if the circuit
4086 is cannibalized for use as another service-side introduction
4087 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
4088 - Bridges now skip DNS self-tests, to act a little more stealthily.
4089 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
4090 bridges. Patch by "warms0x".
4091 - Fix internal bug-checking logic that was supposed to catch
4092 failures in digest generation so that it will fail more robustly
4093 if we ask for a nonexistent algorithm. Found by Coverity Scan.
4094 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
4095 - Report any failure in init_keys() calls launched because our
4096 IP address has changed. Spotted by Coverity Scan. Bugfix on
4097 0.1.1.4-alpha; fixes CID 484.
4099 o Minor bugfixes (log messages and documentation):
4100 - Remove a confusing dollar sign from the example fingerprint in the
4101 man page, and also make the example fingerprint a valid one. Fixes
4102 bug 4309; bugfix on 0.2.1.3-alpha.
4103 - The next version of Windows will be called Windows 8, and it has
4104 a major version of 6, minor version of 2. Correctly identify that
4105 version instead of calling it "Very recent version". Resolves
4106 ticket 4153; reported by funkstar.
4107 - Downgrade log messages about circuit timeout calibration from
4108 "notice" to "info": they don't require or suggest any human
4109 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
4110 bugfix on 0.2.2.14-alpha.
4113 - Turn on directory request statistics by default and include them in
4114 extra-info descriptors. Don't break if we have no GeoIP database.
4115 Backported from 0.2.3.1-alpha; implements ticket 3951.
4116 - Update to the October 4 2011 Maxmind GeoLite Country database.
4119 Changes in version 0.2.1.31 - 2011-10-26
4120 Tor 0.2.1.31 backports important security and privacy fixes for
4121 oldstable. This release is intended only for package maintainers and
4122 others who cannot use the 0.2.2 stable series. All others should be
4123 using Tor 0.2.2.x or newer.
4125 o Security fixes (also included in 0.2.2.x):
4126 - Replace all potentially sensitive memory comparison operations
4127 with versions whose runtime does not depend on the data being
4128 compared. This will help resist a class of attacks where an
4129 adversary can use variations in timing information to learn
4130 sensitive data. Fix for one case of bug 3122. (Safe memcmp
4131 implementation by Robert Ransom based partially on code by DJB.)
4132 - Fix an assert in parsing router descriptors containing IPv6
4133 addresses. This one took down the directory authorities when
4134 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
4136 o Privacy/anonymity fixes (also included in 0.2.2.x):
4137 - Clients and bridges no longer send TLS certificate chains on
4138 outgoing OR connections. Previously, each client or bridge would
4139 use the same cert chain for all outgoing OR connections until
4140 its IP address changes, which allowed any relay that the client
4141 or bridge contacted to determine which entry guards it is using.
4142 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
4143 - If a relay receives a CREATE_FAST cell on a TLS connection, it
4144 no longer considers that connection as suitable for satisfying a
4145 circuit EXTEND request. Now relays can protect clients from the
4146 CVE-2011-2768 issue even if the clients haven't upgraded yet.
4147 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
4148 that they initiated. Relays could distinguish incoming bridge
4149 connections from client connections, creating another avenue for
4150 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
4151 Found by "frosty_un".
4152 - When receiving a hidden service descriptor, check that it is for
4153 the hidden service we wanted. Previously, Tor would store any
4154 hidden service descriptors that a directory gave it, whether it
4155 wanted them or not. This wouldn't have let an attacker impersonate
4156 a hidden service, but it did let directories pre-seed a client
4157 with descriptors that it didn't want. Bugfix on 0.0.6.
4158 - Avoid linkability based on cached hidden service descriptors: forget
4159 all hidden service descriptors cached as a client when processing a
4160 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
4161 - Make the bridge directory authority refuse to answer directory
4162 requests for "all" descriptors. It used to include bridge
4163 descriptors in its answer, which was a major information leak.
4164 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
4165 - Don't attach new streams to old rendezvous circuits after SIGNAL
4166 NEWNYM. Previously, we would keep using an existing rendezvous
4167 circuit if it remained open (i.e. if it were kept open by a
4168 long-lived stream, or if a new stream were attached to it before
4169 Tor could notice that it was old and no longer in use). Bugfix on
4170 0.1.1.15-rc; fixes bug 3375.
4172 o Minor bugfixes (also included in 0.2.2.x):
4173 - When we restart our relay, we might get a successful connection
4174 from the outside before we've started our reachability tests,
4175 triggering a warning: "ORPort found reachable, but I have no
4176 routerinfo yet. Failing to inform controller of success." This
4177 bug was harmless unless Tor is running under a controller
4178 like Vidalia, in which case the controller would never get a
4179 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
4181 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
4182 enabled. Fixes bug 1526.
4183 - Remove undocumented option "-F" from tor-resolve: it hasn't done
4184 anything since 0.2.1.16-rc.
4185 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
4186 None of the cases where we did this before were wrong, but by making
4187 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
4188 - Fix a rare crash bug that could occur when a client was configured
4189 with a large number of bridges. Fixes bug 2629; bugfix on
4190 0.2.1.2-alpha. Bugfix by trac user "shitlei".
4191 - Correct the warning displayed when a rendezvous descriptor exceeds
4192 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
4194 - Fix an uncommon assertion failure when running with DNSPort under
4195 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
4196 - When warning about missing zlib development packages during compile,
4197 give the correct package names. Bugfix on 0.2.0.1-alpha.
4198 - Require that introduction point keys and onion keys have public
4199 exponent 65537. Bugfix on 0.2.0.10-alpha.
4200 - Do not crash when our configuration file becomes unreadable, for
4201 example due to a permissions change, between when we start up
4202 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
4204 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4206 - Always NUL-terminate the sun_path field of a sockaddr_un before
4207 passing it to the kernel. (Not a security issue: kernels are
4208 smart enough to reject bad sockaddr_uns.) Found by Coverity;
4209 CID #428. Bugfix on Tor 0.2.0.3-alpha.
4210 - Don't stack-allocate the list of supplementary GIDs when we're
4211 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4212 could take up to 256K, which is way too much stack. Found by
4213 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4215 o Minor bugfixes (only in 0.2.1.x):
4216 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
4217 rely on them. Bugfix on 0.2.1.30.
4218 - Use git revisions instead of svn revisions when generating our
4219 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
4221 o Minor features (also included in 0.2.2.x):
4222 - Adjust the expiration time on our SSL session certificates to
4223 better match SSL certs seen in the wild. Resolves ticket 4014.
4224 - Allow nameservers with IPv6 address. Resolves bug 2574.
4225 - Update to the October 4 2011 Maxmind GeoLite Country database.
4228 Changes in version 0.2.3.5-alpha - 2011-09-28
4229 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
4230 bridge relays; fixes an assertion error that many users started hitting
4231 today; and adds the ability to refill token buckets more often than
4232 once per second, allowing significant performance improvements.
4235 - Bridge relays now do their directory fetches inside Tor TLS
4236 connections, like all the other clients do, rather than connecting
4237 directly to the DirPort like public relays do. Removes another
4238 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
4239 - Bridges relays now build circuits for themselves in a more similar
4240 way to how clients build them. Removes another avenue for
4241 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
4242 when bridges were introduced.
4245 - Fix an "Assertion md->held_by_node == 1 failed" error that could
4246 occur when the same microdescriptor was referenced by two node_t
4247 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
4249 o Major features (networking):
4250 - Add a new TokenBucketRefillInterval option to refill token buckets
4251 more frequently than once per second. This should improve network
4252 performance, alleviate queueing problems, and make traffic less
4253 bursty. Implements proposal 183; closes ticket 3630. Design by
4254 Florian Tschorsch and Björn Scheuermann; implementation by
4258 - Change an integer overflow check in the OpenBSD_Malloc code so
4259 that GCC is less likely to eliminate it as impossible. Patch
4260 from Mansour Moufid. Fixes bug 4059.
4262 o Minor bugfixes (usability):
4263 - Downgrade log messages about circuit timeout calibration from
4264 "notice" to "info": they don't require or suggest any human
4265 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
4266 bugfix on 0.2.2.14-alpha.
4268 o Minor features (diagnostics):
4269 - When the system call to create a listener socket fails, log the
4270 error message explaining why. This may help diagnose bug 4027.
4273 Changes in version 0.2.3.4-alpha - 2011-09-13
4274 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
4275 tweak to Tor's TLS handshake that makes relays and bridges that run
4276 this new version reachable from Iran again. It also fixes a few new
4277 bugs in 0.2.3.x, and teaches relays to recognize when they're not
4278 listed in the network consensus and republish.
4280 o Major bugfixes (also part of 0.2.2.33):
4281 - Avoid an assertion failure when reloading a configuration with
4282 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
4283 3923; bugfix on 0.2.2.25-alpha.
4285 o Minor features (security, also part of 0.2.2.33):
4286 - Check for replays of the public-key encrypted portion of an
4287 INTRODUCE1 cell, in addition to the current check for replays of
4288 the g^x value. This prevents a possible class of active attacks
4289 by an attacker who controls both an introduction point and a
4290 rendezvous point, and who uses the malleability of AES-CTR to
4291 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
4292 that these attacks are infeasible (requiring the attacker to send
4293 on the order of zettabytes of altered cells in a short interval),
4294 but we'd rather block them off in case there are any classes of
4295 this attack that we missed. Reported by Willem Pinckaers.
4297 o Minor features (also part of 0.2.2.33):
4298 - Adjust the expiration time on our SSL session certificates to
4299 better match SSL certs seen in the wild. Resolves ticket 4014.
4300 - Change the default required uptime for a relay to be accepted as
4301 a HSDir (hidden service directory) from 24 hours to 25 hours.
4302 Improves on 0.2.0.10-alpha; resolves ticket 2649.
4303 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
4304 authorities to abstain from voting on assignment of the HSDir
4305 consensus flag. Related to bug 2649.
4306 - Update to the September 6 2011 Maxmind GeoLite Country database.
4308 o Minor bugfixes (also part of 0.2.2.33):
4309 - Demote the 'replay detected' log message emitted when a hidden
4310 service receives the same Diffie-Hellman public key in two different
4311 INTRODUCE2 cells to info level. A normal Tor client can cause that
4312 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4313 fixes part of bug 2442.
4314 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4315 level. There is nothing that a hidden service's operator can do
4316 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4318 - Clarify a log message specifying the characters permitted in
4319 HiddenServiceAuthorizeClient client names. Previously, the log
4320 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4321 given the impression that every ASCII character between "+" and "_"
4322 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4324 o Build fixes (also part of 0.2.2.33):
4325 - Clean up some code issues that prevented Tor from building on older
4326 BSDs. Fixes bug 3894; reported by "grarpamp".
4327 - Search for a platform-specific version of "ar" when cross-compiling.
4328 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4331 - Fix a bug where the SocksPort option (for example) would get
4332 ignored and replaced by the default if a SocksListenAddress
4333 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
4337 - Relays now try regenerating and uploading their descriptor more
4338 frequently if they are not listed in the consensus, or if the
4339 version of their descriptor listed in the consensus is too
4340 old. This fix should prevent situations where a server declines
4341 to re-publish itself because it has done so too recently, even
4342 though the authorities decided not to list its recent-enough
4343 descriptor. Fix for bug 3327.
4346 - Relays now include a reason for regenerating their descriptors
4347 in an HTTP header when uploading to the authorities. This will
4348 make it easier to debug descriptor-upload issues in the future.
4349 - When starting as root and then changing our UID via the User
4350 control option, and we have a ControlSocket configured, make sure
4351 that the ControlSocket is owned by the same account that Tor will
4352 run under. Implements ticket 3421; fix by Jérémy Bobbio.
4355 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
4356 utility function used in the control-port code). This shouldn't
4357 ever happen unless Tor is completely out of memory, but if it did
4358 happen and Tor somehow recovered from it, Tor could have sent a log
4359 message to a control port in the middle of a reply to a controller
4360 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
4361 - Make 'FetchUselessDescriptors' cause all descriptor types and
4362 all consensus types (including microdescriptors) to get fetched.
4363 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
4366 - Make a new "entry connection" struct as an internal subtype of "edge
4367 connection", to simplify the code and make exit connections smaller.
4370 Changes in version 0.2.2.33 - 2011-09-13
4371 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
4372 TLS handshake that makes relays and bridges that run this new version
4373 reachable from Iran again.
4376 - Avoid an assertion failure when reloading a configuration with
4377 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
4378 3923; bugfix on 0.2.2.25-alpha.
4380 o Minor features (security):
4381 - Check for replays of the public-key encrypted portion of an
4382 INTRODUCE1 cell, in addition to the current check for replays of
4383 the g^x value. This prevents a possible class of active attacks
4384 by an attacker who controls both an introduction point and a
4385 rendezvous point, and who uses the malleability of AES-CTR to
4386 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
4387 that these attacks are infeasible (requiring the attacker to send
4388 on the order of zettabytes of altered cells in a short interval),
4389 but we'd rather block them off in case there are any classes of
4390 this attack that we missed. Reported by Willem Pinckaers.
4393 - Adjust the expiration time on our SSL session certificates to
4394 better match SSL certs seen in the wild. Resolves ticket 4014.
4395 - Change the default required uptime for a relay to be accepted as
4396 a HSDir (hidden service directory) from 24 hours to 25 hours.
4397 Improves on 0.2.0.10-alpha; resolves ticket 2649.
4398 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
4399 authorities to abstain from voting on assignment of the HSDir
4400 consensus flag. Related to bug 2649.
4401 - Update to the September 6 2011 Maxmind GeoLite Country database.
4403 o Minor bugfixes (documentation and log messages):
4404 - Correct the man page to explain that HashedControlPassword and
4405 CookieAuthentication can both be set, in which case either method
4406 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4407 when we decided to allow these config options to both be set. Issue
4409 - Demote the 'replay detected' log message emitted when a hidden
4410 service receives the same Diffie-Hellman public key in two different
4411 INTRODUCE2 cells to info level. A normal Tor client can cause that
4412 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4413 fixes part of bug 2442.
4414 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4415 level. There is nothing that a hidden service's operator can do
4416 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4418 - Clarify a log message specifying the characters permitted in
4419 HiddenServiceAuthorizeClient client names. Previously, the log
4420 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4421 given the impression that every ASCII character between "+" and "_"
4422 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4425 - Provide a substitute implementation of lround() for MSVC, which
4426 apparently lacks it. Patch from Gisle Vanem.
4427 - Clean up some code issues that prevented Tor from building on older
4428 BSDs. Fixes bug 3894; reported by "grarpamp".
4429 - Search for a platform-specific version of "ar" when cross-compiling.
4430 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4433 Changes in version 0.2.3.3-alpha - 2011-09-01
4434 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
4435 security, and provides client-side support for the microdescriptor
4436 and optimistic data features introduced earlier in the 0.2.3.x
4437 series. It also includes numerous critical bugfixes in the (optional)
4438 bufferevent-based networking backend.
4440 o Major features (stream isolation):
4441 - You can now configure Tor so that streams from different
4442 applications are isolated on different circuits, to prevent an
4443 attacker who sees your streams as they leave an exit node from
4444 linking your sessions to one another. To do this, choose some way
4445 to distinguish the applications: have them connect to different
4446 SocksPorts, or have one of them use SOCKS4 while the other uses
4447 SOCKS5, or have them pass different authentication strings to the
4448 SOCKS proxy. Then, use the new SocksPort syntax to configure the
4449 degree of isolation you need. This implements Proposal 171.
4450 - There's a new syntax for specifying multiple client ports (such as
4451 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
4452 multiple *Port entries with full addr:port syntax on each.
4453 The old *ListenAddress format is still supported, but you can't
4454 mix it with the new *Port syntax.
4456 o Major features (other):
4457 - Enable microdescriptor fetching by default for clients. This allows
4458 clients to download a much smaller amount of directory information.
4459 To disable it (and go back to the old-style consensus and
4460 descriptors), set "UseMicrodescriptors 0" in your torrc file.
4461 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
4462 "PortForwarding" config option), now supports Windows.
4463 - When using an exit relay running 0.2.3.x, clients can now
4464 "optimistically" send data before the exit relay reports that
4465 the stream has opened. This saves a round trip when starting
4466 connections where the client speaks first (such as web browsing).
4467 This behavior is controlled by a consensus parameter (currently
4468 disabled). To turn it on or off manually, use the "OptimisticData"
4469 torrc option. Implements proposal 181; code by Ian Goldberg.
4471 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
4472 - When using IOCP on Windows, we need to enable Libevent windows
4474 - The IOCP backend now works even when the user has not specified
4475 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
4476 Fixes part of bug 3752.
4477 - Correctly record the bytes we've read and written when using
4478 bufferevents, so that we can include them in our bandwidth history
4479 and advertised bandwidth. Fixes bug 3803.
4480 - Apply rate-limiting only at the bottom of a chain of filtering
4481 bufferevents. This prevents us from filling up internal read
4482 buffers and violating rate-limits when filtering bufferevents
4483 are enabled. Fixes part of bug 3804.
4484 - Add high-watermarks to the output buffers for filtered
4485 bufferevents. This prevents us from filling up internal write
4486 buffers and wasting CPU cycles when filtering bufferevents are
4487 enabled. Fixes part of bug 3804.
4488 - Correctly notice when data has been written from a bufferevent
4489 without flushing it completely. Fixes bug 3805.
4490 - Fix a bug where server-side tunneled bufferevent-based directory
4491 streams would get closed prematurely. Fixes bug 3814.
4492 - Fix a use-after-free error with per-connection rate-limiting
4493 buckets. Fixes bug 3888.
4495 o Major bugfixes (also part of 0.2.2.31-rc):
4496 - If we're configured to write our ControlPorts to disk, only write
4497 them after switching UID and creating the data directory. This way,
4498 we don't fail when starting up with a nonexistent DataDirectory
4499 and a ControlPortWriteToFile setting based on that directory. Fixes
4500 bug 3747; bugfix on Tor 0.2.2.26-beta.
4503 - Added a new CONF_CHANGED event so that controllers can be notified
4504 of any configuration changes made by other controllers, or by the
4505 user. Implements ticket 1692.
4506 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
4507 leak when using bufferevents, and lets Libevent worry about how to
4508 best copy data out of a buffer.
4509 - Replace files in stats/ rather than appending to them. Now that we
4510 include statistics in extra-info descriptors, it makes no sense to
4511 keep old statistics forever. Implements ticket 2930.
4513 o Minor features (build compatibility):
4514 - Limited, experimental support for building with nmake and MSVC.
4515 - Provide a substitute implementation of lround() for MSVC, which
4516 apparently lacks it. Patch from Gisle Vanem.
4518 o Minor features (also part of 0.2.2.31-rc):
4519 - Update to the August 2 2011 Maxmind GeoLite Country database.
4521 o Minor bugfixes (on 0.2.3.x-alpha):
4522 - Fix a spurious warning when parsing SOCKS requests with
4523 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
4524 - Get rid of a harmless warning that could happen on relays running
4525 with bufferevents. The warning was caused by someone doing an http
4526 request to a relay's orport. Also don't warn for a few related
4527 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
4529 o Minor bugfixes (on 2.2.x and earlier):
4530 - Correct the man page to explain that HashedControlPassword and
4531 CookieAuthentication can both be set, in which case either method
4532 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4533 when we decided to allow these config options to both be set. Issue
4535 - The "--quiet" and "--hush" options now apply not only to Tor's
4536 behavior before logs are configured, but also to Tor's behavior in
4537 the absense of configured logs. Fixes bug 3550; bugfix on
4540 o Minor bugfixes (also part of 0.2.2.31-rc):
4541 - Write several files in text mode, on OSes that distinguish text
4542 mode from binary mode (namely, Windows). These files are:
4543 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4544 that collect those statistics; 'client_keys' and 'hostname' for
4545 hidden services that use authentication; and (in the tor-gencert
4546 utility) newly generated identity and signing keys. Previously,
4547 we wouldn't specify text mode or binary mode, leading to an
4548 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4549 the DirRecordUsageByCountry option which would have triggered
4550 the assertion failure was added), although this assertion failure
4551 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4552 - Selectively disable deprecation warnings on OS X because Lion
4553 started deprecating the shipped copy of openssl. Fixes bug 3643.
4554 - Remove an extra pair of quotation marks around the error
4555 message in control-port STATUS_GENERAL BUG events. Bugfix on
4556 0.1.2.6-alpha; fixes bug 3732.
4557 - When unable to format an address as a string, report its value
4558 as "???" rather than reusing the last formatted address. Bugfix
4561 o Code simplifications and refactoring:
4562 - Rewrite the listener-selection logic so that parsing which ports
4563 we want to listen on is now separate from binding to the ports
4567 - Building Tor with bufferevent support now requires Libevent
4568 2.0.13-stable or later. Previous versions of Libevent had bugs in
4569 SSL-related bufferevents and related issues that would make Tor
4570 work badly with bufferevents. Requiring 2.0.13-stable also allows
4571 Tor with bufferevents to take advantage of Libevent APIs
4572 introduced after 2.0.8-rc.
4575 Changes in version 0.2.2.32 - 2011-08-27
4576 The Tor 0.2.2 release series is dedicated to the memory of Andreas
4577 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
4578 a founder of the PETS community, a leader in our field, a mentor,
4579 and a friend. He left us with these words: "I had the possibility
4580 to contribute to this world that is not as it should be. I hope I
4581 could help in some areas to make the world a better place, and that
4582 I could also encourage other people to be engaged in improving the
4583 world. Please, stay engaged. This world needs you, your love, your
4584 initiative -- now I cannot be part of that anymore."
4586 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
4587 ready. More than two years in the making, this release features improved
4588 client performance and hidden service reliability, better compatibility
4589 for Android, correct behavior for bridges that listen on more than
4590 one address, more extensible and flexible directory object handling,
4591 better reporting of network statistics, improved code security, and
4592 many many other features and bugfixes.
4595 Changes in version 0.2.2.31-rc - 2011-08-17
4596 Tor 0.2.2.31-rc is the second and hopefully final release candidate
4597 for the Tor 0.2.2.x series.
4600 - Remove an extra pair of quotation marks around the error
4601 message in control-port STATUS_GENERAL BUG events. Bugfix on
4602 0.1.2.6-alpha; fixes bug 3732.
4603 - If we're configured to write our ControlPorts to disk, only write
4604 them after switching UID and creating the data directory. This way,
4605 we don't fail when starting up with a nonexistent DataDirectory
4606 and a ControlPortWriteToFile setting based on that directory. Fixes
4607 bug 3747; bugfix on Tor 0.2.2.26-beta.
4610 - Update to the August 2 2011 Maxmind GeoLite Country database.
4613 - Allow GETINFO fingerprint to return a fingerprint even when
4614 we have not yet built a router descriptor. Fixes bug 3577;
4615 bugfix on 0.2.0.1-alpha.
4616 - Write several files in text mode, on OSes that distinguish text
4617 mode from binary mode (namely, Windows). These files are:
4618 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4619 that collect those statistics; 'client_keys' and 'hostname' for
4620 hidden services that use authentication; and (in the tor-gencert
4621 utility) newly generated identity and signing keys. Previously,
4622 we wouldn't specify text mode or binary mode, leading to an
4623 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4624 the DirRecordUsageByCountry option which would have triggered
4625 the assertion failure was added), although this assertion failure
4626 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4627 - Selectively disable deprecation warnings on OS X because Lion
4628 started deprecating the shipped copy of openssl. Fixes bug 3643.
4629 - When unable to format an address as a string, report its value
4630 as "???" rather than reusing the last formatted address. Bugfix
4634 Changes in version 0.2.3.2-alpha - 2011-07-18
4635 Tor 0.2.3.2-alpha introduces two new experimental features:
4636 microdescriptors and pluggable transports. It also continues cleaning
4637 up a variety of recently introduced features.
4640 - Clients can now use microdescriptors instead of regular descriptors
4641 to build circuits. Microdescriptors are authority-generated
4642 summaries of regular descriptors' contents, designed to change
4643 very rarely (see proposal 158 for details). This feature is
4644 designed to save bandwidth, especially for clients on slow internet
4645 connections. It's off by default for now, since nearly no caches
4646 support it, but it will be on-by-default for clients in a future
4647 version. You can use the UseMicrodescriptors option to turn it on.
4648 - Tor clients using bridges can now be configured to use a separate
4649 'transport' proxy for each bridge. This approach helps to resist
4650 censorship by allowing bridges to use protocol obfuscation
4651 plugins. It implements part of proposal 180. Implements ticket 2841.
4652 - While we're trying to bootstrap, record how many TLS connections
4653 fail in each state, and report which states saw the most failures
4654 in response to any bootstrap failures. This feature may speed up
4655 diagnosis of censorship events. Implements ticket 3116.
4657 o Major bugfixes (on 0.2.3.1-alpha):
4658 - When configuring a large set of nodes in EntryNodes (as with
4659 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
4660 random subset to be guards, and choose them in random
4661 order. Fixes bug 2798.
4662 - Tor could crash when remembering a consensus in a non-used consensus
4663 flavor without having a current consensus set. Fixes bug 3361.
4664 - Comparing an unknown address to a microdescriptor's shortened exit
4665 policy would always give a "rejected" result. Fixes bug 3599.
4666 - Using microdescriptors as a client no longer prevents Tor from
4667 uploading and downloading hidden service descriptors. Fixes
4671 - Allow nameservers with IPv6 address. Resolves bug 2574.
4672 - Accept attempts to include a password authenticator in the
4673 handshake, as supported by SOCKS5. This handles SOCKS clients that
4674 don't know how to omit a password when authenticating. Resolves
4676 - When configuring a large set of nodes in EntryNodes, and there are
4677 enough of them listed as Guard so that we don't need to consider
4678 the non-guard entries, prefer the ones listed with the Guard flag.
4679 - Check for and recover from inconsistency in the microdescriptor
4680 cache. This will make it harder for us to accidentally free a
4681 microdescriptor without removing it from the appropriate data
4682 structures. Fixes issue 3135; issue noted by "wanoskarnet".
4683 - Log SSL state transitions at log level DEBUG, log domain
4684 HANDSHAKE. This can be useful for debugging censorship events.
4685 Implements ticket 3264.
4686 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
4687 implements ticket 3439.
4689 o Minor bugfixes (on 0.2.3.1-alpha):
4690 - Do not free all general-purpose regular descriptors just
4691 because microdescriptor use is enabled. Fixes bug 3113.
4692 - Correctly link libevent_openssl when --enable-static-libevent
4693 is passed to configure. Fixes bug 3118.
4694 - Bridges should not complain during their heartbeat log messages that
4695 they are unlisted in the consensus: that's more or less the point
4696 of being a bridge. Fixes bug 3183.
4697 - Report a SIGNAL event to controllers when acting on a delayed
4698 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
4699 event to the controller if we acted on a SIGNAL NEWNYM command
4700 immediately, and otherwise not report a SIGNAL event for the
4701 command at all. Fixes bug 3349.
4702 - Fix a crash when handling the SIGNAL controller command or
4703 reporting ERR-level status events with bufferevents enabled. Found
4704 by Robert Ransom. Fixes bug 3367.
4705 - Always ship the tor-fw-helper manpage in our release tarballs.
4706 Fixes bug 3389. Reported by Stephen Walker.
4707 - Fix a class of double-mark-for-close bugs when bufferevents
4708 are enabled. Fixes bug 3403.
4709 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
4710 - Add SIGNAL to the list returned by the 'GETINFO events/names'
4711 control-port command. Fixes part of bug 3465.
4712 - Prevent using negative indices during unit test runs when read_all()
4713 fails. Spotted by coverity.
4714 - Fix a rare memory leak when checking the nodelist without it being
4715 present. Found by coverity.
4716 - Only try to download a microdescriptor-flavored consensus from
4717 a directory cache that provides them.
4719 o Minor bugfixes (on 0.2.2.x and earlier):
4720 - Assert that hidden-service-related operations are not performed
4721 using single-hop circuits. Previously, Tor would assert that
4722 client-side streams are not attached to single-hop circuits,
4723 but not that other sensitive operations on the client and service
4724 side are not performed using single-hop circuits. Fixes bug 3332;
4726 - Don't publish a new relay descriptor when we reload our onion key,
4727 unless the onion key has actually changed. Fixes bug 3263 and
4728 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
4729 - Allow GETINFO fingerprint to return a fingerprint even when
4730 we have not yet built a router descriptor. Fixes bug 3577;
4731 bugfix on 0.2.0.1-alpha.
4732 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
4733 on 0.2.2.4-alpha; fixes bug 3427.
4735 o Code simplification and refactoring:
4736 - Use tor_sscanf() in place of scanf() in more places through the
4737 code. This makes us a little more locale-independent, and
4738 should help shut up code-analysis tools that can't tell
4739 a safe sscanf string from a dangerous one.
4740 - Use tt_assert(), not tor_assert(), for checking for test failures.
4741 This makes the unit tests more able to go on in the event that
4743 - Split connection_about_to_close() into separate functions for each
4747 - On Windows, we now define the _WIN32_WINNT macros only if they
4748 are not already defined. This lets the person building Tor decide,
4749 if they want, to require a later version of Windows.
4752 Changes in version 0.2.2.30-rc - 2011-07-07
4753 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
4754 series. It fixes a few smaller bugs, but generally appears stable.
4755 Please test it and let us know whether it is!
4758 - Send a SUCCEEDED stream event to the controller when a reverse
4759 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
4760 discovered by katmagic.
4761 - Always NUL-terminate the sun_path field of a sockaddr_un before
4762 passing it to the kernel. (Not a security issue: kernels are
4763 smart enough to reject bad sockaddr_uns.) Found by Coverity;
4764 CID #428. Bugfix on Tor 0.2.0.3-alpha.
4765 - Don't stack-allocate the list of supplementary GIDs when we're
4766 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4767 could take up to 256K, which is way too much stack. Found by
4768 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4769 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
4770 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
4771 fixes part of bug 3465.
4772 - Fix a memory leak when receiving a descriptor for a hidden
4773 service we didn't ask for. Found by Coverity; CID #30. Bugfix
4777 - Update to the July 1 2011 Maxmind GeoLite Country database.
4780 Changes in version 0.2.2.29-beta - 2011-06-20
4781 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
4782 have bridge lines in their torrc but don't want to use them; gets
4783 us closer to having the control socket feature working on Debian;
4784 and fixes a variety of smaller bugs.
4787 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
4788 When we changed the default behavior to "use bridges if any
4789 are listed in the torrc", we surprised users who had bridges
4790 in their torrc files but who didn't actually want to use them.
4791 Partial resolution for bug 3354.
4794 - Don't attach new streams to old rendezvous circuits after SIGNAL
4795 NEWNYM. Previously, we would keep using an existing rendezvous
4796 circuit if it remained open (i.e. if it were kept open by a
4797 long-lived stream, or if a new stream were attached to it before
4798 Tor could notice that it was old and no longer in use). Bugfix on
4799 0.1.1.15-rc; fixes bug 3375.
4802 - Fix a bug when using ControlSocketsGroupWritable with User. The
4803 directory's group would be checked against the current group, not
4804 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
4805 bugfix on 0.2.2.26-beta.
4806 - Make connection_printf_to_buf()'s behaviour sane. Its callers
4807 expect it to emit a CRLF iff the format string ends with CRLF;
4808 it actually emitted a CRLF iff (a) the format string ended with
4809 CRLF or (b) the resulting string was over 1023 characters long or
4810 (c) the format string did not end with CRLF *and* the resulting
4811 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
4812 fixes part of bug 3407.
4813 - Make send_control_event_impl()'s behaviour sane. Its callers
4814 expect it to always emit a CRLF at the end of the string; it
4815 might have emitted extra control characters as well. Bugfix on
4816 0.1.1.9-alpha; fixes another part of bug 3407.
4817 - Make crypto_rand_int() check the value of its input correctly.
4818 Previously, it accepted values up to UINT_MAX, but could return a
4819 negative number if given a value above INT_MAX+1. Found by George
4820 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
4821 - Avoid a segfault when reading a malformed circuit build state
4822 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
4824 - When asked about a DNS record type we don't support via a
4825 client DNSPort, reply with NOTIMPL rather than an empty
4826 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
4827 - Fix a rare memory leak during stats writing. Found by coverity.
4830 - Update to the June 1 2011 Maxmind GeoLite Country database.
4832 o Code simplifications and refactoring:
4833 - Remove some dead code as indicated by coverity.
4834 - Remove a few dead assignments during router parsing. Found by
4836 - Add some forgotten return value checks during unit tests. Found
4838 - Don't use 1-bit wide signed bit fields. Found by coverity.
4841 Changes in version 0.2.2.28-beta - 2011-06-04
4842 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
4843 fixed a big bug in whether relays stay in the consensus consistently,
4844 we moved closer to handling bridges and hidden services correctly,
4845 and we started the process of better handling the dreaded "my Vidalia
4846 died, and now my Tor demands a password when I try to reconnect to it"
4850 - Don't decide to make a new descriptor when receiving a HUP signal.
4851 This bug has caused a lot of 0.2.2.x relays to disappear from the
4852 consensus periodically. Fixes the most common case of triggering
4853 bug 1810; bugfix on 0.2.2.7-alpha.
4854 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
4855 - Don't try to build descriptors if "ORPort auto" is set and we
4856 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
4858 - Resolve a crash that occurred when setting BridgeRelay to 1 with
4859 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
4860 - Apply circuit timeouts to opened hidden-service-related circuits
4861 based on the correct start time. Previously, we would apply the
4862 circuit build timeout based on time since the circuit's creation;
4863 it was supposed to be applied based on time since the circuit
4864 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
4865 - Use the same circuit timeout for client-side introduction
4866 circuits as for other four-hop circuits, rather than the timeout
4867 for single-hop directory-fetch circuits; the shorter timeout may
4868 have been appropriate with the static circuit build timeout in
4869 0.2.1.x and earlier, but caused many hidden service access attempts
4870 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
4871 on 0.2.2.2-alpha; fixes another part of bug 1297.
4872 - In ticket 2511 we fixed a case where you could use an unconfigured
4873 bridge if you had configured it as a bridge the last time you ran
4874 Tor. Now fix another edge case: if you had configured it as a bridge
4875 but then switched to a different bridge via the controller, you
4876 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
4880 - Add an __OwningControllerProcess configuration option and a
4881 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
4882 that when it exits, Tor will shut down. Implements feature 3049.
4883 - If "UseBridges 1" is set and no bridges are configured, Tor will
4884 now refuse to build any circuits until some bridges are set.
4885 If "UseBridges auto" is set, Tor will use bridges if they are
4886 configured and we are not running as a server, but otherwise will
4887 make circuits as usual. The new default is "auto". Patch by anonym,
4888 so the Tails LiveCD can stop automatically revealing you as a Tor
4892 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4893 - Remove a trailing asterisk from "exit-policy/default" in the
4894 output of the control port command "GETINFO info/names". Bugfix
4896 - Use a wide type to hold sockets when built for 64-bit Windows builds.
4898 - Warn when the user configures two HiddenServiceDir lines that point
4899 to the same directory. Bugfix on 0.0.6 (the version introducing
4900 HiddenServiceDir); fixes bug 3289.
4901 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
4902 part of bug 2748; bugfix on 0.2.0.10-alpha.
4903 - Log malformed requests for rendezvous descriptors as protocol
4904 warnings, not warnings. Also, use a more informative log message
4905 in case someone sees it at log level warning without prior
4906 info-level messages. Fixes the other part of bug 2748; bugfix
4908 - Clear the table recording the time of the last request for each
4909 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
4910 Previously, we would clear our HS descriptor cache on SIGNAL
4911 NEWNYM, but if we had previously retrieved a descriptor (or tried
4912 to) from every directory responsible for it, we would refuse to
4913 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
4915 - Fix a log message that said "bits" while displaying a value in
4916 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
4918 - When checking for 1024-bit keys, check for 1024 bits, not 128
4919 bytes. This allows Tor to correctly discard keys of length 1017
4920 through 1023. Bugfix on 0.0.9pre5.
4923 - Relays now log the reason for publishing a new relay descriptor,
4924 so we have a better chance of hunting down instances of bug 1810.
4925 Resolves ticket 3252.
4926 - Revise most log messages that refer to nodes by nickname to
4927 instead use the "$key=nickname at address" format. This should be
4928 more useful, especially since nicknames are less and less likely
4929 to be unique. Resolves ticket 3045.
4930 - Log (at info level) when purging pieces of hidden-service-client
4931 state because of SIGNAL NEWNYM.
4934 - Remove undocumented option "-F" from tor-resolve: it hasn't done
4935 anything since 0.2.1.16-rc.
4938 Changes in version 0.2.2.27-beta - 2011-05-18
4939 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
4940 release, and also adds a few more general bugfixes.
4943 - Fix a crash bug when changing bridges in a running Tor process.
4944 Fixes bug 3213; bugfix on 0.2.2.26-beta.
4945 - When the controller configures a new bridge, don't wait 10 to 60
4946 seconds before trying to fetch its descriptor. Bugfix on
4947 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
4950 - Require that onion keys have exponent 65537 in microdescriptors too.
4951 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
4952 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
4953 Changed the limit to 512 characters by removing base64 newlines.
4954 Fixes bug 2752. Fix by Michael Yakubovich.
4955 - When a client starts or stops using bridges, never use a circuit
4956 that was built before the configuration change. This behavior could
4957 put at risk a user who uses bridges to ensure that her traffic
4958 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
4962 Changes in version 0.2.2.26-beta - 2011-05-17
4963 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
4964 also introduces a new "socksport auto" approach that should make it
4965 easier to run multiple Tors on the same system, and does a lot of
4966 cleanup to get us closer to a release candidate.
4968 o Security/privacy fixes:
4969 - Replace all potentially sensitive memory comparison operations
4970 with versions whose runtime does not depend on the data being
4971 compared. This will help resist a class of attacks where an
4972 adversary can use variations in timing information to learn
4973 sensitive data. Fix for one case of bug 3122. (Safe memcmp
4974 implementation by Robert Ransom based partially on code by DJB.)
4975 - When receiving a hidden service descriptor, check that it is for
4976 the hidden service we wanted. Previously, Tor would store any
4977 hidden service descriptors that a directory gave it, whether it
4978 wanted them or not. This wouldn't have let an attacker impersonate
4979 a hidden service, but it did let directories pre-seed a client
4980 with descriptors that it didn't want. Bugfix on 0.0.6.
4981 - On SIGHUP, do not clear out all TrackHostExits mappings, client
4982 DNS cache entries, and virtual address mappings: that's what
4983 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
4986 - The options SocksPort, ControlPort, and so on now all accept a
4987 value "auto" that opens a socket on an OS-selected port. A
4988 new ControlPortWriteToFile option tells Tor to write its
4989 actual control port or ports to a chosen file. If the option
4990 ControlPortFileGroupReadable is set, the file is created as
4991 group-readable. Now users can run two Tor clients on the same
4992 system without needing to manually mess with parameters. Resolves
4993 part of ticket 3076.
4994 - Set SO_REUSEADDR on all sockets, not just listeners. This should
4995 help busy exit nodes avoid running out of useable ports just
4996 because all the ports have been used in the near past. Resolves
5000 - New "GETINFO net/listeners/(type)" controller command to return
5001 a list of addresses and ports that are bound for listeners for a
5002 given connection type. This is useful when the user has configured
5003 "SocksPort auto" and the controller needs to know which port got
5004 chosen. Resolves another part of ticket 3076.
5005 - Add a new ControlSocketsGroupWritable configuration option: when
5006 it is turned on, ControlSockets are group-writeable by the default
5007 group of the current user. Patch by Jérémy Bobbio; implements
5009 - Tor now refuses to create a ControlSocket in a directory that is
5010 world-readable (or group-readable if ControlSocketsGroupWritable
5011 is 0). This is necessary because some operating systems do not
5012 enforce permissions on an AF_UNIX sockets. Permissions on the
5013 directory holding the socket, however, seems to work everywhere.
5014 - Rate-limit a warning about failures to download v2 networkstatus
5015 documents. Resolves part of bug 1352.
5016 - Backport code from 0.2.3.x that allows directory authorities to
5017 clean their microdescriptor caches. Needed to resolve bug 2230.
5018 - When an HTTPS proxy reports "403 Forbidden", we now explain
5019 what it means rather than calling it an unexpected status code.
5020 Closes bug 2503. Patch from Michael Yakubovich.
5021 - Update to the May 1 2011 Maxmind GeoLite Country database.
5024 - Authorities now clean their microdesc cache periodically and when
5025 reading from disk initially, not only when adding new descriptors.
5026 This prevents a bug where we could lose microdescriptors. Bugfix
5027 on 0.2.2.6-alpha. Fixes bug 2230.
5028 - Do not crash when our configuration file becomes unreadable, for
5029 example due to a permissions change, between when we start up
5030 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
5032 - Avoid a bug that would keep us from replacing a microdescriptor
5033 cache on Windows. (We would try to replace the file while still
5034 holding it open. That's fine on Unix, but Windows doesn't let us
5035 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
5036 - Add missing explanations for the authority-related torrc options
5037 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
5038 man page. Resolves issue 2379.
5039 - As an authority, do not upload our own vote or signature set to
5040 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
5041 it would get flagged as a duplicate. Resolves bug 3026.
5042 - Accept hidden service descriptors if we think we might be a hidden
5043 service directory, regardless of what our consensus says. This
5044 helps robustness, since clients and hidden services can sometimes
5045 have a more up-to-date view of the network consensus than we do,
5046 and if they think that the directory authorities list us a HSDir,
5047 we might actually be one. Related to bug 2732; bugfix on
5049 - When a controller changes TrackHostExits, remove mappings for
5050 hosts that should no longer have their exits tracked. Bugfix on
5052 - When a controller changes VirtualAddrNetwork, remove any mappings
5053 for hosts that were automapped to the old network. Bugfix on
5055 - When a controller changes one of the AutomapHosts* options, remove
5056 any mappings for hosts that should no longer be automapped. Bugfix
5058 - Do not reset the bridge descriptor download status every time we
5059 re-parse our configuration or get a configuration change. Fixes
5060 bug 3019; bugfix on 0.2.0.3-alpha.
5062 o Minor bugfixes (code cleanup):
5063 - When loading the microdesc journal, remember its current size.
5064 In 0.2.2, this helps prevent the microdesc journal from growing
5065 without limit on authorities (who are the only ones to use it in
5066 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
5067 Fix posted by "cypherpunks."
5068 - The microdesc journal is supposed to get rebuilt only if it is
5069 at least _half_ the length of the store, not _twice_ the length
5070 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
5071 - Fix a potential null-pointer dereference while computing a
5072 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
5074 - Avoid a possible null-pointer dereference when rebuilding the mdesc
5075 cache without actually having any descriptors to cache. Bugfix on
5076 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
5077 - If we fail to compute the identity digest of a v3 legacy keypair,
5078 warn, and don't use a buffer-full of junk instead. Bugfix on
5079 0.2.1.1-alpha; fixes bug 3106.
5080 - Resolve an untriggerable issue in smartlist_string_num_isin(),
5081 where if the function had ever in the future been used to check
5082 for the presence of a too-large number, it would have given an
5083 incorrect result. (Fortunately, we only used it for 16-bit
5084 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
5085 - Require that introduction point keys and onion handshake keys
5086 have a public exponent of 65537. Starts to fix bug 3207; bugfix
5090 - Caches no longer download and serve v2 networkstatus documents
5091 unless FetchV2Networkstatus flag is set: these documents haven't
5092 haven't been used by clients or relays since 0.2.0.x. Resolves
5096 Changes in version 0.2.3.1-alpha - 2011-05-05
5097 Tor 0.2.3.1-alpha adds some new experimental features, including support
5098 for an improved network IO backend, IOCP networking on Windows,
5099 microdescriptor caching, "fast-start" support for streams, and automatic
5100 home router configuration. There are also numerous internal improvements
5101 to try to make the code easier for developers to work with.
5103 This is the first alpha release in a new series, so expect there to be
5104 bugs. Users who would rather test out a more stable branch should
5105 stay with 0.2.2.x for now.
5108 - Tor can now optionally build with the "bufferevents" buffered IO
5109 backend provided by Libevent 2. To use this feature, make sure you
5110 have the latest possible version of Libevent, and pass the
5111 --enable-bufferevents flag to configure when building Tor from
5112 source. This feature will make our networking code more flexible,
5113 let us stack layers on each other, and let us use more efficient
5114 zero-copy transports where available.
5115 - As an experimental feature, Tor can use IOCP for networking on Windows.
5116 Once this code is tuned and optimized, it promises much better
5117 performance than the select-based backend we've used in the past. To
5118 try this feature, you must build Tor with Libevent 2, configure Tor
5119 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
5120 your torrc. There are known bugs here: only try this if you can help
5121 debug it as it breaks.
5122 - The EntryNodes option can now include country codes like {de} or IP
5123 addresses or network masks. Previously we had disallowed these options
5124 because we didn't have an efficient way to keep the list up to
5125 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
5126 - Exit nodes now accept and queue data on not-yet-connected streams.
5127 Previously, the client wasn't allowed to send data until the stream was
5128 connected, which slowed down all connections. This change will enable
5129 clients to perform a "fast-start" on streams and send data without
5130 having to wait for a confirmation that the stream has opened. (Patch
5131 from Ian Goldberg; implements the server side of Proposal 174.)
5132 - Tor now has initial support for automatic port mapping on the many
5133 home routers that support NAT-PMP or UPnP. (Not yet supported on
5134 Windows). To build the support code, you'll need to have libnatpnp
5135 library and/or the libminiupnpc library, and you'll need to enable the
5136 feature specifically by passing "--enable-upnp" and/or
5137 "--enable-natpnp" to configure. To turn it on, use the new
5138 PortForwarding option.
5139 - Caches now download, cache, and serve multiple "flavors" of the
5140 consensus, including a flavor that describes microdescriptors.
5141 - Caches now download, cache, and serve microdescriptors -- small
5142 summaries of router descriptors that are authenticated by all of the
5143 directory authorities. Once enough caches are running this code,
5144 clients will be able to save significant amounts of directory bandwidth
5145 by downloading microdescriptors instead of router descriptors.
5148 - Make logging resolution configurable with a new LogTimeGranularity
5149 option, and change the default from 1 millisecond to 1 second.
5150 Implements enhancement 1668.
5151 - We log which torrc file we're using on startup. Implements ticket
5153 - Ordinarily, Tor does not count traffic from private addresses (like
5154 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
5155 There is now a new option, CountPrivateBandwidth, to disable this
5156 behavior. Patch from Daniel Cagara.
5157 - New --enable-static-tor configure option for building Tor as
5158 statically as possible. Idea, general hackery and thoughts from
5159 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
5161 - If you set the NumCPUs option to 0, Tor will now try to detect how
5162 many CPUs you have. This is the new default behavior.
5163 - Turn on directory request statistics by default and include them in
5164 extra-info descriptors. Don't break if we have no GeoIP database.
5165 - Relays that set "ConnDirectionStatistics 1" write statistics on the
5166 bidirectional use of connections to disk every 24 hours.
5167 - Add a GeoIP file digest to the extra-info descriptor. Implements
5169 - The NodeFamily option -- which let you declare that you want to
5170 consider nodes to be part of a family whether they list themselves
5171 that way or not -- now allows IP address ranges and country codes.
5172 - Add a new 'Heartbeat' log message type to periodically log a message
5173 describing Tor's status at level Notice. This feature is meant for
5174 operators who log at notice, and want to make sure that their Tor
5175 server is still working. Implementation by George Kadianakis.
5177 o Minor bugfixes (on 0.2.2.25-alpha):
5178 - When loading the microdesc journal, remember its current size.
5179 In 0.2.2, this helps prevent the microdesc journal from growing
5180 without limit on authorities (who are the only ones to use it in
5181 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
5182 Fix posted by "cypherpunks."
5183 - The microdesc journal is supposed to get rebuilt only if it is
5184 at least _half_ the length of the store, not _twice_ the length
5185 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
5186 - If as an authority we fail to compute the identity digest of a v3
5187 legacy keypair, warn, and don't use a buffer-full of junk instead.
5188 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
5189 - Authorities now clean their microdesc cache periodically and when
5190 reading from disk initially, not only when adding new descriptors.
5191 This prevents a bug where we could lose microdescriptors. Bugfix
5194 o Minor features (controller):
5195 - Add a new SIGNAL event to the controller interface so that
5196 controllers can be notified when Tor handles a signal. Resolves
5197 issue 1955. Patch by John Brooks.
5198 - Add a new GETINFO option to get total bytes read and written. Patch
5199 from pipe, revised by atagar. Resolves ticket 2345.
5200 - Implement some GETINFO controller fields to provide information about
5201 the Tor process's pid, euid, username, and resource limits.
5204 - Our build system requires automake 1.6 or later to create the
5205 Makefile.in files. Previously, you could have used 1.4.
5206 This only affects developers and people building Tor from git;
5207 people who build Tor from the source distribution without changing
5208 the Makefile.am files should be fine.
5209 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
5210 so on. This is more robust against some of the failure modes
5211 associated with running the autotools pieces on their own.
5213 o Minor packaging issues:
5214 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
5215 already created. Patch from Andreas Stieger. Fixes bug 2573.
5217 o Code simplifications and refactoring:
5218 - A major revision to our internal node-selecting and listing logic.
5219 Tor already had at least two major ways to look at the question of
5220 "which Tor servers do we know about": a list of router descriptors,
5221 and a list of entries in the current consensus. With
5222 microdescriptors, we're adding a third. Having so many systems
5223 without an abstraction layer over them was hurting the codebase.
5224 Now, we have a new "node_t" abstraction that presents a consistent
5225 interface to a client's view of a Tor node, and holds (nearly) all
5226 of the mutable state formerly in routerinfo_t and routerstatus_t.
5227 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
5228 no longer link against Libevent: they never used it, but
5229 our library structure used to force them to link it.
5232 - Remove some old code to work around even older versions of Tor that
5233 used forked processes to handle DNS requests. Such versions of Tor
5234 are no longer in use as servers.
5236 o Documentation fixes:
5237 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
5238 - Add missing documentation for the authority-related torrc options
5239 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
5243 Changes in version 0.2.2.25-alpha - 2011-04-29
5244 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
5245 robust, routers no longer overreport their bandwidth, Win7 should crash
5246 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
5247 now prevents hidden service-related activity from being linkable. It
5248 provides more information to Vidalia so you can see if your bridge is
5249 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
5250 StrictNodes configuration options to make them more reliable, more
5251 understandable, and more regularly applied. If you use those options,
5252 please see the revised documentation for them in the manual page.
5255 - Relays were publishing grossly inflated bandwidth values because
5256 they were writing their state files wrong--now they write the
5257 correct value. Also, resume reading bandwidth history from the
5258 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
5259 - Improve hidden service robustness: When we find that we have
5260 extended a hidden service's introduction circuit to a relay not
5261 listed as an introduction point in the HS descriptor we currently
5262 have, retry with an introduction point from the current
5263 descriptor. Previously we would just give up. Fixes bugs 1024 and
5264 1930; bugfix on 0.2.0.10-alpha.
5265 - Clients now stop trying to use an exit node associated with a given
5266 destination by TrackHostExits if they fail to reach that exit node.
5267 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
5268 - Fix crash bug on platforms where gmtime and localtime can return
5269 NULL. Windows 7 users were running into this one. Fixes part of bug
5270 2077. Bugfix on all versions of Tor. Found by boboper.
5272 o Security and stability fixes:
5273 - Don't double-free a parsable, but invalid, microdescriptor, even if
5274 it is followed in the blob we're parsing by an unparsable
5275 microdescriptor. Fixes an issue reported in a comment on bug 2954.
5276 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
5277 - If the Nickname configuration option isn't given, Tor would pick a
5278 nickname based on the local hostname as the nickname for a relay.
5279 Because nicknames are not very important in today's Tor and the
5280 "Unnamed" nickname has been implemented, this is now problematic
5281 behavior: It leaks information about the hostname without being
5282 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
5283 introduced the Unnamed nickname. Reported by tagnaq.
5284 - Fix an uncommon assertion failure when running with DNSPort under
5285 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
5286 - Avoid linkability based on cached hidden service descriptors: forget
5287 all hidden service descriptors cached as a client when processing a
5288 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
5291 - Export GeoIP information on bridge usage to controllers even if we
5292 have not yet been running for 24 hours. Now Vidalia bridge operators
5293 can get more accurate and immediate feedback about their
5294 contributions to the network.
5296 o Major features and bugfixes (node selection):
5297 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
5298 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
5299 options. Previously, we had been ambiguous in describing what
5300 counted as an "exit" node, and what operations exactly "StrictNodes
5301 0" would permit. This created confusion when people saw nodes built
5302 through unexpected circuits, and made it hard to tell real bugs from
5303 surprises. Now the intended behavior is:
5304 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
5305 a node that delivers user traffic outside the Tor network.
5306 . "Entry", in the context of EntryNodes, means a node used as the
5307 first hop of a multihop circuit. It doesn't include direct
5308 connections to directory servers.
5309 . "ExcludeNodes" applies to all nodes.
5310 . "StrictNodes" changes the behavior of ExcludeNodes only. When
5311 StrictNodes is set, Tor should avoid all nodes listed in
5312 ExcludeNodes, even when it will make user requests fail. When
5313 StrictNodes is *not* set, then Tor should follow ExcludeNodes
5314 whenever it can, except when it must use an excluded node to
5315 perform self-tests, connect to a hidden service, provide a
5316 hidden service, fulfill a .exit request, upload directory
5317 information, or fetch directory information.
5318 Collectively, the changes to implement the behavior fix bug 1090.
5319 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
5320 a node is listed in both, it's treated as excluded.
5321 - ExcludeNodes now applies to directory nodes -- as a preference if
5322 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
5323 Don't exclude all the directory authorities and set StrictNodes to 1
5324 unless you really want your Tor to break.
5325 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
5326 - ExcludeExitNodes now overrides .exit requests.
5327 - We don't use bridges listed in ExcludeNodes.
5328 - When StrictNodes is 1:
5329 . We now apply ExcludeNodes to hidden service introduction points
5330 and to rendezvous points selected by hidden service users. This
5331 can make your hidden service less reliable: use it with caution!
5332 . If we have used ExcludeNodes on ourself, do not try relay
5333 reachability self-tests.
5334 . If we have excluded all the directory authorities, we will not
5335 even try to upload our descriptor if we're a relay.
5336 . Do not honor .exit requests to an excluded node.
5337 - Remove a misfeature that caused us to ignore the Fast/Stable flags
5338 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
5339 - When the set of permitted nodes changes, we now remove any mappings
5340 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
5342 - We never cannibalize a circuit that had excluded nodes on it, even
5343 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
5344 - Revert a change where we would be laxer about attaching streams to
5345 circuits than when building the circuits. This was meant to prevent
5346 a set of bugs where streams were never attachable, but our improved
5347 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
5348 - Keep track of how many times we launch a new circuit to handle a
5349 given stream. Too many launches could indicate an inconsistency
5350 between our "launch a circuit to handle this stream" logic and our
5351 "attach this stream to one of the available circuits" logic.
5352 - Improve log messages related to excluded nodes.
5355 - Fix a spurious warning when moving from a short month to a long
5356 month on relays with month-based BandwidthAccounting. Bugfix on
5357 0.2.2.17-alpha; fixes bug 3020.
5358 - When a client finds that an origin circuit has run out of 16-bit
5359 stream IDs, we now mark it as unusable for new streams. Previously,
5360 we would try to close the entire circuit. Bugfix on 0.0.6.
5361 - Add a forgotten cast that caused a compile warning on OS X 10.6.
5362 Bugfix on 0.2.2.24-alpha.
5363 - Be more careful about reporting the correct error from a failed
5364 connect() system call. Under some circumstances, it was possible to
5365 look at an incorrect value for errno when sending the end reason.
5366 Bugfix on 0.1.0.1-rc.
5367 - Correctly handle an "impossible" overflow cases in connection byte
5368 counting, where we write or read more than 4GB on an edge connection
5369 in a single second. Bugfix on 0.1.2.8-beta.
5370 - Correct the warning displayed when a rendezvous descriptor exceeds
5371 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
5373 - Clients and hidden services now use HSDir-flagged relays for hidden
5374 service descriptor downloads and uploads even if the relays have no
5375 DirPort set and the client has disabled TunnelDirConns. This will
5376 eventually allow us to give the HSDir flag to relays with no
5377 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
5378 - Downgrade "no current certificates known for authority" message from
5379 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
5380 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
5381 2917. Bugfix on 0.1.1.1-alpha.
5382 - Only limit the lengths of single HS descriptors, even when multiple
5383 HS descriptors are published to an HSDir relay in a single POST
5384 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
5385 - Write the current time into the LastWritten line in our state file,
5386 rather than the time from the previous write attempt. Also, stop
5387 trying to use a time of -1 in our log statements. Fixes bug 3039;
5388 bugfix on 0.2.2.14-alpha.
5389 - Be more consistent in our treatment of file system paths. "~" should
5390 get expanded to the user's home directory in the Log config option.
5391 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
5392 feature for the -f and --DataDirectory options.
5395 - Make sure every relay writes a state file at least every 12 hours.
5396 Previously, a relay could go for weeks without writing its state
5397 file, and on a crash could lose its bandwidth history, capacity
5398 estimates, client country statistics, and so on. Addresses bug 3012.
5399 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
5400 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
5401 clients are already deprecated because of security bugs.
5402 - Don't allow v0 hidden service authorities to act as clients.
5403 Required by fix for bug 3000.
5404 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
5405 by fix for bug 3000.
5406 - Ensure that no empty [dirreq-](read|write)-history lines are added
5407 to an extrainfo document. Implements ticket 2497.
5409 o Code simplification and refactoring:
5410 - Remove workaround code to handle directory responses from servers
5411 that had bug 539 (they would send HTTP status 503 responses _and_
5412 send a body too). Since only server versions before
5413 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
5414 keep the workaround in place.
5415 - Remove the old 'fuzzy time' logic. It was supposed to be used for
5416 handling calculations where we have a known amount of clock skew and
5417 an allowed amount of unknown skew. But we only used it in three
5418 places, and we never adjusted the known/unknown skew values. This is
5419 still something we might want to do someday, but if we do, we'll
5420 want to do it differently.
5421 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
5422 None of the cases where we did this before were wrong, but by making
5423 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
5424 - Use GetTempDir to find the proper temporary directory location on
5425 Windows when generating temporary files for the unit tests. Patch by
5429 Changes in version 0.2.2.24-alpha - 2011-04-08
5430 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
5431 prevented Tor clients from effectively using "multihomed" bridges,
5432 that is, bridges that listen on multiple ports or IP addresses so users
5433 can continue to use some of their addresses even if others get blocked.
5436 - Fix a bug where bridge users who configure the non-canonical
5437 address of a bridge automatically switch to its canonical
5438 address. If a bridge listens at more than one address, it should be
5439 able to advertise those addresses independently and any non-blocked
5440 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
5442 - If you configured Tor to use bridge A, and then quit and
5443 configured Tor to use bridge B instead, it would happily continue
5444 to use bridge A if it's still reachable. While this behavior is
5445 a feature if your goal is connectivity, in some scenarios it's a
5446 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
5447 - Directory authorities now use data collected from their own
5448 uptime observations when choosing whether to assign the HSDir flag
5449 to relays, instead of trusting the uptime value the relay reports in
5450 its descriptor. This change helps prevent an attack where a small
5451 set of nodes with frequently-changing identity keys can blackhole
5452 a hidden service. (Only authorities need upgrade; others will be
5453 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
5456 - When we restart our relay, we might get a successful connection
5457 from the outside before we've started our reachability tests,
5458 triggering a warning: "ORPort found reachable, but I have no
5459 routerinfo yet. Failing to inform controller of success." This
5460 bug was harmless unless Tor is running under a controller
5461 like Vidalia, in which case the controller would never get a
5462 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
5464 - Make directory authorities more accurate at recording when
5465 relays that have failed several reachability tests became
5466 unreachable, so we can provide more accuracy at assigning Stable,
5467 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
5468 - Fix an issue that prevented static linking of libevent on
5469 some platforms (notably Linux). Fixes bug 2698; bugfix on
5470 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
5471 the --with-static-libevent configure option).
5472 - We now ask the other side of a stream (the client or the exit)
5473 for more data on that stream when the amount of queued data on
5474 that stream dips low enough. Previously, we wouldn't ask the
5475 other side for more data until either it sent us more data (which
5476 it wasn't supposed to do if it had exhausted its window!) or we
5477 had completely flushed all our queued data. This flow control fix
5478 should improve throughput. Fixes bug 2756; bugfix on the earliest
5479 released versions of Tor (svn commit r152).
5480 - Avoid a double-mark-for-free warning when failing to attach a
5481 transparent proxy connection. (We thought we had fixed this in
5482 0.2.2.23-alpha, but it turns out our fix was checking the wrong
5483 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
5484 bug) and 0.2.2.23-alpha (the incorrect fix).
5485 - When warning about missing zlib development packages during compile,
5486 give the correct package names. Bugfix on 0.2.0.1-alpha.
5489 - Directory authorities now log the source of a rejected POSTed v3
5491 - Make compilation with clang possible when using
5492 --enable-gcc-warnings by removing two warning options that clang
5493 hasn't implemented yet and by fixing a few warnings. Implements
5495 - When expiring circuits, use microsecond timers rather than
5496 one-second timers. This can avoid an unpleasant situation where a
5497 circuit is launched near the end of one second and expired right
5498 near the beginning of the next, and prevent fluctuations in circuit
5500 - Use computed circuit-build timeouts to decide when to launch
5501 parallel introduction circuits for hidden services. (Previously,
5502 we would retry after 15 seconds.)
5503 - Update to the April 1 2011 Maxmind GeoLite Country database.
5506 - Create the /var/run/tor directory on startup on OpenSUSE if it is
5507 not already created. Patch from Andreas Stieger. Fixes bug 2573.
5509 o Documentation changes:
5510 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
5511 - Resolve all doxygen warnings except those for missing documentation.
5513 - Add doxygen documentation for more functions, fields, and types.
5516 Changes in version 0.2.2.23-alpha - 2011-03-08
5517 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
5518 they restart they don't lose their bandwidth capacity estimate. This
5519 release also fixes a diverse set of user-facing bugs, ranging from
5520 relays overrunning their rate limiting to clients falsely warning about
5521 clock skew to bridge descriptor leaks by our bridge directory authority.
5524 - Stop sending a CLOCK_SKEW controller status event whenever
5525 we fetch directory information from a relay that has a wrong clock.
5526 Instead, only inform the controller when it's a trusted authority
5527 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5528 the rest of bug 1074.
5529 - Fix an assert in parsing router descriptors containing IPv6
5530 addresses. This one took down the directory authorities when
5531 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
5532 - Make the bridge directory authority refuse to answer directory
5533 requests for "all" descriptors. It used to include bridge
5534 descriptors in its answer, which was a major information leak.
5535 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
5536 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5537 Tor would ignore their RelayBandwidthBurst setting,
5538 potentially using more bandwidth than expected. Bugfix on
5539 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5540 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5541 hidserv" in her torrc. The 'hidserv' argument never controlled
5542 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5545 - Relays now save observed peak bandwidth throughput rates to their
5546 state file (along with total usage, which was already saved)
5547 so that they can determine their correct estimated bandwidth on
5548 restart. Resolves bug 1863, where Tor relays would reset their
5549 estimated bandwidth to 0 after restarting.
5550 - Directory authorities now take changes in router IP address and
5551 ORPort into account when determining router stability. Previously,
5552 if a router changed its IP or ORPort, the authorities would not
5553 treat it as having any downtime for the purposes of stability
5554 calculation, whereas clients would experience downtime since the
5555 change could take a while to propagate to them. Resolves issue 1035.
5556 - Enable Address Space Layout Randomization (ASLR) and Data Execution
5557 Prevention (DEP) by default on Windows to make it harder for
5558 attackers to exploit vulnerabilities. Patch from John Brooks.
5560 o Minor bugfixes (on 0.2.1.x and earlier):
5561 - Fix a rare crash bug that could occur when a client was configured
5562 with a large number of bridges. Fixes bug 2629; bugfix on
5563 0.2.1.2-alpha. Bugfix by trac user "shitlei".
5564 - Avoid a double mark-for-free warning when failing to attach a
5565 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
5567 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
5568 found by "cypherpunks". This bug was introduced before the first
5569 Tor release, in svn commit r110.
5570 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
5571 don't mention them in the manpage. Fixes bug 2450; issue
5572 spotted by keb and G-Lo.
5573 - Fix a bug in bandwidth history state parsing that could have been
5574 triggered if a future version of Tor ever changed the timing
5575 granularity at which bandwidth history is measured. Bugfix on
5577 - When a relay decides that its DNS is too broken for it to serve
5578 as an exit server, it advertised itself as a non-exit, but
5579 continued to act as an exit. This could create accidental
5580 partitioning opportunities for users. Instead, if a relay is
5581 going to advertise reject *:* as its exit policy, it should
5582 really act with exit policy "reject *:*". Fixes bug 2366.
5583 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
5584 - In the special case where you configure a public exit relay as your
5585 bridge, Tor would be willing to use that exit relay as the last
5586 hop in your circuit as well. Now we fail that circuit instead.
5587 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
5588 - Fix a bug with our locking implementation on Windows that couldn't
5589 correctly detect when a file was already locked. Fixes bug 2504,
5590 bugfix on 0.2.1.6-alpha.
5591 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
5592 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
5594 - Set target port in get_interface_address6() correctly. Bugfix
5595 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
5596 - Directory authorities are now more robust to hops back in time
5597 when calculating router stability. Previously, if a run of uptime
5598 or downtime appeared to be negative, the calculation could give
5599 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
5601 - Fix an assert that got triggered when using the TestingTorNetwork
5602 configuration option and then issuing a GETINFO config-text control
5603 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
5605 o Minor bugfixes (on 0.2.2.x):
5606 - Clients should not weight BadExit nodes as Exits in their node
5607 selection. Similarly, directory authorities should not count BadExit
5608 bandwidth as Exit bandwidth when computing bandwidth-weights.
5609 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
5610 - Correctly clear our dir_read/dir_write history when there is an
5611 error parsing any bw history value from the state file. Bugfix on
5613 - Resolve a bug in verifying signatures of directory objects
5614 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
5615 Fixes bug 2409. Found by "piebeer".
5616 - Bridge authorities no longer crash on SIGHUP when they try to
5617 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
5621 - Log less aggressively about circuit timeout changes, and improve
5622 some other circuit timeout messages. Resolves bug 2004.
5623 - Log a little more clearly about the times at which we're no longer
5624 accepting new connections. Resolves bug 2181.
5625 - Reject attempts at the client side to open connections to private
5626 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
5627 a randomly chosen exit node. Attempts to do so are always
5628 ill-defined, generally prevented by exit policies, and usually
5629 in error. This will also help to detect loops in transparent
5630 proxy configurations. You can disable this feature by setting
5631 "ClientRejectInternalAddresses 0" in your torrc.
5632 - Always treat failure to allocate an RSA key as an unrecoverable
5634 - Update to the March 1 2011 Maxmind GeoLite Country database.
5636 o Minor features (log subsystem):
5637 - Add documentation for configuring logging at different severities in
5638 different log domains. We've had this feature since 0.2.1.1-alpha,
5639 but for some reason it never made it into the manpage. Fixes
5641 - Make it simpler to specify "All log domains except for A and B".
5642 Previously you needed to say "[*,~A,~B]". Now you can just say
5644 - Add a "LogMessageDomains 1" option to include the domains of log
5645 messages along with the messages. Without this, there's no way
5646 to use log domains without reading the source or doing a lot
5649 o Packaging changes:
5650 - Stop shipping the Tor specs files and development proposal documents
5651 in the tarball. They are now in a separate git repository at
5652 git://git.torproject.org/torspec.git
5655 Changes in version 0.2.1.30 - 2011-02-23
5656 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
5657 change is a slight tweak to Tor's TLS handshake that makes relays
5658 and bridges that run this new version reachable from Iran again.
5659 We don't expect this tweak will win the arms race long-term, but it
5660 buys us time until we roll out a better solution.
5663 - Stop sending a CLOCK_SKEW controller status event whenever
5664 we fetch directory information from a relay that has a wrong clock.
5665 Instead, only inform the controller when it's a trusted authority
5666 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5667 the rest of bug 1074.
5668 - Fix a bounds-checking error that could allow an attacker to
5669 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5671 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5672 Tor would ignore their RelayBandwidthBurst setting,
5673 potentially using more bandwidth than expected. Bugfix on
5674 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5675 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5676 hidserv" in her torrc. The 'hidserv' argument never controlled
5677 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5680 - Adjust our TLS Diffie-Hellman parameters to match those used by
5682 - Update to the February 1 2011 Maxmind GeoLite Country database.
5685 - Check for and reject overly long directory certificates and
5686 directory tokens before they have a chance to hit any assertions.
5687 Bugfix on 0.2.1.28. Found by "doorss".
5688 - Bring the logic that gathers routerinfos and assesses the
5689 acceptability of circuits into line. This prevents a Tor OP from
5690 getting locked in a cycle of choosing its local OR as an exit for a
5691 path (due to a .exit request) and then rejecting the circuit because
5692 its OR is not listed yet. It also prevents Tor clients from using an
5693 OR running in the same instance as an exit (due to a .exit request)
5694 if the OR does not meet the same requirements expected of an OR
5695 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5697 o Packaging changes:
5698 - Stop shipping the Tor specs files and development proposal documents
5699 in the tarball. They are now in a separate git repository at
5700 git://git.torproject.org/torspec.git
5701 - Do not include Git version tags as though they are SVN tags when
5702 generating a tarball from inside a repository that has switched
5703 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
5706 Changes in version 0.2.2.22-alpha - 2011-01-25
5707 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
5708 main other change is a slight tweak to Tor's TLS handshake that makes
5709 relays and bridges that run this new version reachable from Iran again.
5710 We don't expect this tweak will win the arms race long-term, but it
5711 will buy us a bit more time until we roll out a better solution.
5714 - Fix a bounds-checking error that could allow an attacker to
5715 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5717 - Don't assert when changing from bridge to relay or vice versa
5718 via the controller. The assert happened because we didn't properly
5719 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
5720 bug 2433. Reported by bastik.
5723 - Adjust our TLS Diffie-Hellman parameters to match those used by
5725 - Provide a log message stating which geoip file we're parsing
5726 instead of just stating that we're parsing the geoip file.
5727 Implements ticket 2432.
5730 - Check for and reject overly long directory certificates and
5731 directory tokens before they have a chance to hit any assertions.
5732 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
5735 Changes in version 0.2.2.21-alpha - 2011-01-15
5736 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
5737 continues our recent code security audit work. The main fix resolves
5738 a remote heap overflow vulnerability that can allow remote code
5739 execution (CVE-2011-0427). Other fixes address a variety of assert
5740 and crash bugs, most of which we think are hard to exploit remotely.
5742 o Major bugfixes (security), also included in 0.2.1.29:
5743 - Fix a heap overflow bug where an adversary could cause heap
5744 corruption. This bug probably allows remote code execution
5745 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5747 - Prevent a denial-of-service attack by disallowing any
5748 zlib-compressed data whose compression factor is implausibly
5749 high. Fixes part of bug 2324; reported by "doorss".
5750 - Zero out a few more keys in memory before freeing them. Fixes
5751 bug 2384 and part of bug 2385. These key instances found by
5752 "cypherpunks", based on Andrew Case's report about being able
5753 to find sensitive data in Tor's memory space if you have enough
5754 permissions. Bugfix on 0.0.2pre9.
5756 o Major bugfixes (crashes), also included in 0.2.1.29:
5757 - Prevent calls to Libevent from inside Libevent log handlers.
5758 This had potential to cause a nasty set of crashes, especially
5759 if running Libevent with debug logging enabled, and running
5760 Tor with a controller watching for low-severity log messages.
5761 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5762 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5763 underflow errors there too. Fixes the other part of bug 2324.
5764 - Fix a bug where we would assert if we ever had a
5765 cached-descriptors.new file (or another file read directly into
5766 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5767 on 0.2.1.25. Found by doorss.
5768 - Fix some potential asserts and parsing issues with grossly
5769 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5772 o Minor bugfixes (other), also included in 0.2.1.29:
5773 - Fix a bug with handling misformed replies to reverse DNS lookup
5774 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5775 bug reported by doorss.
5776 - Fix compilation on mingw when a pthreads compatibility library
5777 has been installed. (We don't want to use it, so we shouldn't
5778 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5779 - Fix a bug where we would declare that we had run out of virtual
5780 addresses when the address space was only half-exhausted. Bugfix
5782 - Correctly handle the case where AutomapHostsOnResolve is set but
5783 no virtual addresses are available. Fixes bug 2328; bugfix on
5784 0.1.2.1-alpha. Bug found by doorss.
5785 - Correctly handle wrapping around when we run out of virtual
5786 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
5788 o Minor features, also included in 0.2.1.29:
5789 - Update to the January 1 2011 Maxmind GeoLite Country database.
5790 - Introduce output size checks on all of our decryption functions.
5792 o Build changes, also included in 0.2.1.29:
5793 - Tor does not build packages correctly with Automake 1.6 and earlier;
5794 added a check to Makefile.am to make sure that we're building with
5795 Automake 1.7 or later.
5796 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5797 because we built it with a too-old version of automake. Thus that
5798 release broke ./configure --enable-openbsd-malloc, which is popular
5799 among really fast exit relays on Linux.
5801 o Major bugfixes, new in 0.2.2.21-alpha:
5802 - Prevent crash/heap corruption when the cbtnummodes consensus
5803 parameter is set to 0 or large values. Fixes bug 2317; bugfix
5806 o Major features, new in 0.2.2.21-alpha:
5807 - Introduce minimum/maximum values that clients will believe
5808 from the consensus. Now we'll have a better chance to avoid crashes
5809 or worse when a consensus param has a weird value.
5811 o Minor features, new in 0.2.2.21-alpha:
5812 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
5813 used on bridges, and it makes bridge scanning somewhat easier.
5814 - If writing the state file to disk fails, wait up to an hour before
5815 retrying again, rather than trying again each second. Fixes bug
5816 2346; bugfix on Tor 0.1.1.3-alpha.
5817 - Make Libevent log messages get delivered to controllers later,
5818 and not from inside the Libevent log handler. This prevents unsafe
5819 reentrant Libevent calls while still letting the log messages
5821 - Detect platforms that brokenly use a signed size_t, and refuse to
5822 build there. Found and analyzed by doorss and rransom.
5823 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
5826 o Minor bugfixes, new in 0.2.2.21-alpha:
5827 - Handle SOCKS messages longer than 128 bytes long correctly, rather
5828 than waiting forever for them to finish. Fixes bug 2330; bugfix
5829 on 0.2.0.16-alpha. Found by doorss.
5830 - Add assertions to check for overflow in arguments to
5831 base32_encode() and base32_decode(); fix a signed-unsigned
5832 comparison there too. These bugs are not actually reachable in Tor,
5833 but it's good to prevent future errors too. Found by doorss.
5834 - Correctly detect failures to create DNS requests when using Libevent
5835 versions before v2. (Before Libevent 2, we used our own evdns
5836 implementation. Its return values for Libevent's evdns_resolve_*()
5837 functions are not consistent with those from Libevent.) Fixes bug
5838 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
5840 o Documentation, new in 0.2.2.21-alpha:
5841 - Document the default socks host and port (127.0.0.1:9050) for
5845 Changes in version 0.2.1.29 - 2011-01-15
5846 Tor 0.2.1.29 continues our recent code security audit work. The main
5847 fix resolves a remote heap overflow vulnerability that can allow remote
5848 code execution. Other fixes address a variety of assert and crash bugs,
5849 most of which we think are hard to exploit remotely.
5851 o Major bugfixes (security):
5852 - Fix a heap overflow bug where an adversary could cause heap
5853 corruption. This bug probably allows remote code execution
5854 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5856 - Prevent a denial-of-service attack by disallowing any
5857 zlib-compressed data whose compression factor is implausibly
5858 high. Fixes part of bug 2324; reported by "doorss".
5859 - Zero out a few more keys in memory before freeing them. Fixes
5860 bug 2384 and part of bug 2385. These key instances found by
5861 "cypherpunks", based on Andrew Case's report about being able
5862 to find sensitive data in Tor's memory space if you have enough
5863 permissions. Bugfix on 0.0.2pre9.
5865 o Major bugfixes (crashes):
5866 - Prevent calls to Libevent from inside Libevent log handlers.
5867 This had potential to cause a nasty set of crashes, especially
5868 if running Libevent with debug logging enabled, and running
5869 Tor with a controller watching for low-severity log messages.
5870 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5871 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5872 underflow errors there too. Fixes the other part of bug 2324.
5873 - Fix a bug where we would assert if we ever had a
5874 cached-descriptors.new file (or another file read directly into
5875 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5876 on 0.2.1.25. Found by doorss.
5877 - Fix some potential asserts and parsing issues with grossly
5878 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5881 o Minor bugfixes (other):
5882 - Fix a bug with handling misformed replies to reverse DNS lookup
5883 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5884 bug reported by doorss.
5885 - Fix compilation on mingw when a pthreads compatibility library
5886 has been installed. (We don't want to use it, so we shouldn't
5887 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5888 - Fix a bug where we would declare that we had run out of virtual
5889 addresses when the address space was only half-exhausted. Bugfix
5891 - Correctly handle the case where AutomapHostsOnResolve is set but
5892 no virtual addresses are available. Fixes bug 2328; bugfix on
5893 0.1.2.1-alpha. Bug found by doorss.
5894 - Correctly handle wrapping around to when we run out of virtual
5895 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
5896 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5897 because we built it with a too-old version of automake. Thus that
5898 release broke ./configure --enable-openbsd-malloc, which is popular
5899 among really fast exit relays on Linux.
5902 - Update to the January 1 2011 Maxmind GeoLite Country database.
5903 - Introduce output size checks on all of our decryption functions.
5906 - Tor does not build packages correctly with Automake 1.6 and earlier;
5907 added a check to Makefile.am to make sure that we're building with
5908 Automake 1.7 or later.
5911 Changes in version 0.2.2.20-alpha - 2010-12-17
5912 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
5913 exploitable bugs. We also fix a variety of other significant bugs,
5914 change the IP address for one of our directory authorities, and update
5915 the minimum version that Tor relays must run to join the network.
5918 - Fix a remotely exploitable bug that could be used to crash instances
5919 of Tor remotely by overflowing on the heap. Remote-code execution
5920 hasn't been confirmed, but can't be ruled out. Everyone should
5921 upgrade. Bugfix on the 0.1.1 series and later.
5922 - Fix a bug that could break accounting on 64-bit systems with large
5923 time_t values, making them hibernate for impossibly long intervals.
5924 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
5925 - Fix a logic error in directory_fetches_from_authorities() that
5926 would cause all _non_-exits refusing single-hop-like circuits
5927 to fetch from authorities, when we wanted to have _exits_ fetch
5928 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
5930 - Fix a stream fairness bug that would cause newer streams on a given
5931 circuit to get preference when reading bytes from the origin or
5932 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
5933 introduced before the first Tor release, in svn revision r152.
5935 o Directory authority changes:
5936 - Change IP address and ports for gabelmoo (v3 directory authority).
5939 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
5940 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
5941 - Fix an off-by-one error in calculating some controller command
5942 argument lengths. Fortunately, this mistake is harmless since
5943 the controller code does redundant NUL termination too. Found by
5944 boboper. Bugfix on 0.1.1.1-alpha.
5945 - Do not dereference NULL if a bridge fails to build its
5946 extra-info descriptor. Found by an anonymous commenter on
5947 Trac. Bugfix on 0.2.2.19-alpha.
5950 - Update to the December 1 2010 Maxmind GeoLite Country database.
5951 - Directory authorities now reject relays running any versions of
5952 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
5953 known bugs that keep RELAY_EARLY cells from working on rendezvous
5954 circuits. Followup to fix for bug 2081.
5955 - Directory authorities now reject relays running any version of Tor
5956 older than 0.2.0.26-rc. That version is the earliest that fetches
5957 current directory information correctly. Fixes bug 2156.
5958 - Report only the top 10 ports in exit-port stats in order not to
5959 exceed the maximum extra-info descriptor length of 50 KB. Implements
5963 Changes in version 0.2.1.28 - 2010-12-17
5964 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
5965 exploitable bugs. We also took this opportunity to change the IP address
5966 for one of our directory authorities, and to update the geoip database
5970 - Fix a remotely exploitable bug that could be used to crash instances
5971 of Tor remotely by overflowing on the heap. Remote-code execution
5972 hasn't been confirmed, but can't be ruled out. Everyone should
5973 upgrade. Bugfix on the 0.1.1 series and later.
5975 o Directory authority changes:
5976 - Change IP address and ports for gabelmoo (v3 directory authority).
5979 - Update to the December 1 2010 Maxmind GeoLite Country database.
5982 Changes in version 0.2.1.27 - 2010-11-23
5983 Yet another OpenSSL security patch broke its compatibility with Tor:
5984 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
5985 also took this opportunity to fix several crash bugs, integrate a new
5986 directory authority, and update the bundled GeoIP database.
5989 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5990 No longer set the tlsext_host_name extension on server SSL objects;
5991 but continue to set it on client SSL objects. Our goal in setting
5992 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5993 bugfix on 0.2.1.1-alpha.
5994 - Do not log messages to the controller while shrinking buffer
5995 freelists. Doing so would sometimes make the controller connection
5996 try to allocate a buffer chunk, which would mess up the internals
5997 of the freelist and cause an assertion failure. Fixes bug 1125;
5998 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5999 - Learn our external IP address when we're a relay or bridge, even if
6000 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
6001 where we introduced bridge relays that don't need to publish to
6002 be useful. Fixes bug 2050.
6003 - Do even more to reject (and not just ignore) annotations on
6004 router descriptors received anywhere but from the cache. Previously
6005 we would ignore such annotations at first, but cache them to disk
6006 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
6007 - When you're using bridges and your network goes away and your
6008 bridges get marked as down, recover when you attempt a new socks
6009 connection (if the network is back), rather than waiting up to an
6010 hour to try fetching new descriptors for your bridges. Bugfix on
6011 0.2.0.3-alpha; fixes bug 1981.
6014 - Move to the November 2010 Maxmind GeoLite country db (rather
6015 than the June 2009 ip-to-country GeoIP db) for our statistics that
6016 count how many users relays are seeing from each country. Now we'll
6017 have more accurate data, especially for many African countries.
6019 o New directory authorities:
6020 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
6024 - Fix an assertion failure that could occur in directory caches or
6025 bridge users when using a very short voting interval on a testing
6026 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
6028 - Enforce multiplicity rules when parsing annotations. Bugfix on
6029 0.2.0.8-alpha. Found by piebeer.
6030 - Allow handshaking OR connections to take a full KeepalivePeriod
6031 seconds to handshake. Previously, we would close them after
6032 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
6033 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
6035 - When building with --enable-gcc-warnings on OpenBSD, disable
6036 warnings in system headers. This makes --enable-gcc-warnings
6037 pass on OpenBSD 4.8.
6040 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
6041 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
6042 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
6043 Servers can start sending this code when enough clients recognize
6044 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
6045 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
6046 Patch from mingw-san.
6049 - Remove the old debian/ directory from the main Tor distribution.
6050 The official Tor-for-debian git repository lives at the URL
6051 https://git.torproject.org/debian/tor.git
6052 - Stop shipping the old doc/website/ directory in the tarball. We
6053 changed the website format in late 2010, and what we shipped in
6054 0.2.1.26 really wasn't that useful anyway.
6057 Changes in version 0.2.2.19-alpha - 2010-11-22
6058 Yet another OpenSSL security patch broke its compatibility with Tor:
6059 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
6062 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
6063 No longer set the tlsext_host_name extension on server SSL objects;
6064 but continue to set it on client SSL objects. Our goal in setting
6065 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
6066 bugfix on 0.2.1.1-alpha.
6069 - Try harder not to exceed the maximum length of 50 KB when writing
6070 statistics to extra-info descriptors. This bug was triggered by very
6071 fast relays reporting exit-port, entry, and dirreq statistics.
6072 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
6073 - Publish a router descriptor even if generating an extra-info
6074 descriptor fails. Previously we would not publish a router
6075 descriptor without an extra-info descriptor; this can cause fast
6076 exit relays collecting exit-port statistics to drop from the
6077 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
6080 Changes in version 0.2.2.18-alpha - 2010-11-16
6081 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
6082 us lately, makes unpublished bridge relays able to detect their IP
6083 address, and fixes a wide variety of other bugs to get us much closer
6084 to a stable release.
6087 - Do even more to reject (and not just ignore) annotations on
6088 router descriptors received anywhere but from the cache. Previously
6089 we would ignore such annotations at first, but cache them to disk
6090 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
6091 - Do not log messages to the controller while shrinking buffer
6092 freelists. Doing so would sometimes make the controller connection
6093 try to allocate a buffer chunk, which would mess up the internals
6094 of the freelist and cause an assertion failure. Fixes bug 1125;
6095 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
6096 - Learn our external IP address when we're a relay or bridge, even if
6097 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
6098 where we introduced bridge relays that don't need to publish to
6099 be useful. Fixes bug 2050.
6100 - Maintain separate TLS contexts and certificates for incoming and
6101 outgoing connections in bridge relays. Previously we would use the
6102 same TLS contexts and certs for incoming and outgoing connections.
6103 Bugfix on 0.2.0.3-alpha; addresses bug 988.
6104 - Maintain separate identity keys for incoming and outgoing TLS
6105 contexts in bridge relays. Previously we would use the same
6106 identity keys for incoming and outgoing TLS contexts. Bugfix on
6107 0.2.0.3-alpha; addresses the other half of bug 988.
6108 - Avoid an assertion failure when we as an authority receive a
6109 duplicate upload of a router descriptor that we already have,
6110 but which we previously considered an obsolete descriptor.
6111 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
6112 - Avoid a crash bug triggered by looking at a dangling pointer while
6113 setting the network status consensus. Found by Robert Ransom.
6114 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
6115 - Fix a logic error where servers that _didn't_ act as exits would
6116 try to keep their server lists more aggressively up to date than
6117 exits, when it was supposed to be the other way around. Bugfix
6120 o Minor bugfixes (on Tor 0.2.1.x and earlier):
6121 - When we're trying to guess whether we know our IP address as
6122 a relay, we would log various ways that we failed to guess
6123 our address, but never log that we ended up guessing it
6124 successfully. Now add a log line to help confused and anxious
6125 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
6126 - Bring the logic that gathers routerinfos and assesses the
6127 acceptability of circuits into line. This prevents a Tor OP from
6128 getting locked in a cycle of choosing its local OR as an exit for a
6129 path (due to a .exit request) and then rejecting the circuit because
6130 its OR is not listed yet. It also prevents Tor clients from using an
6131 OR running in the same instance as an exit (due to a .exit request)
6132 if the OR does not meet the same requirements expected of an OR
6133 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
6134 - Correctly describe errors that occur when generating a TLS object.
6135 Previously we would attribute them to a failure while generating a
6136 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
6138 - Enforce multiplicity rules when parsing annotations. Bugfix on
6139 0.2.0.8-alpha. Found by piebeer.
6140 - Fix warnings that newer versions of autoconf produced during
6141 ./autogen.sh. These warnings appear to be harmless in our case,
6142 but they were extremely verbose. Fixes bug 2020.
6144 o Minor bugfixes (on Tor 0.2.2.x):
6145 - Enable protection of small arrays whenever we build with gcc
6146 hardening features, not only when also building with warnings
6147 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
6150 - Make hidden services work better in private Tor networks by not
6151 requiring any uptime to join the hidden service descriptor
6152 DHT. Implements ticket 2088.
6153 - Rate-limit the "your application is giving Tor only an IP address"
6154 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
6155 - When AllowSingleHopExits is set, print a warning to explain to the
6156 relay operator why most clients are avoiding her relay.
6157 - Update to the November 1 2010 Maxmind GeoLite Country database.
6159 o Code simplifications and refactoring:
6160 - When we fixed bug 1038 we had to put in a restriction not to send
6161 RELAY_EARLY cells on rend circuits. This was necessary as long
6162 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
6163 active. Now remove this obsolete check. Resolves bug 2081.
6164 - Some options used different conventions for uppercasing of acronyms
6165 when comparing manpage and source. Fix those in favor of the
6166 manpage, as it makes sense to capitalize acronyms.
6167 - Remove the torrc.complete file. It hasn't been kept up to date
6168 and users will have better luck checking out the manpage.
6169 - Remove the obsolete "NoPublish" option; it has been flagged
6170 as obsolete and has produced a warning since 0.1.1.18-rc.
6171 - Remove everything related to building the expert bundle for OS X.
6172 It has confused many users, doesn't work right on OS X 10.6,
6173 and is hard to get rid of once installed. Resolves bug 1274.
6176 Changes in version 0.2.2.17-alpha - 2010-09-30
6177 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
6178 to use one-hop circuits (which can put the exit relays at higher risk,
6179 plus unbalance the network); fixes a big bug in bandwidth accounting
6180 for relays that want to limit their monthly bandwidth use; fixes a
6181 big pile of bugs in how clients tolerate temporary network failure;
6182 and makes our adaptive circuit build timeout feature (which improves
6183 client performance if your network is fast while not breaking things
6184 if your network is slow) better handle bad networks.
6187 - Exit relays now try harder to block exit attempts from unknown
6188 relays, to make it harder for people to use them as one-hop proxies
6189 a la tortunnel. Controlled by the refuseunknownexits consensus
6190 parameter (currently enabled), or you can override it on your
6191 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
6193 o Major bugfixes (0.2.1.x and earlier):
6194 - Fix a bug in bandwidth accounting that could make us use twice
6195 the intended bandwidth when our interval start changes due to
6196 daylight saving time. Now we tolerate skew in stored vs computed
6197 interval starts: if the start of the period changes by no more than
6198 50% of the period's duration, we remember bytes that we transferred
6199 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
6200 - Always search the Windows system directory for system DLLs, and
6201 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
6202 - When you're using bridges and your network goes away and your
6203 bridges get marked as down, recover when you attempt a new socks
6204 connection (if the network is back), rather than waiting up to an
6205 hour to try fetching new descriptors for your bridges. Bugfix on
6206 0.2.0.3-alpha; fixes bug 1981.
6208 o Major bugfixes (on 0.2.2.x):
6209 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
6211 - Fix a segfault that could happen when operating a bridge relay with
6212 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
6213 - The consensus bandwidth-weights (used by clients to choose fast
6214 relays) entered an unexpected edge case in September where
6215 Exits were much scarcer than Guards, resulting in bad weight
6216 recommendations. Now we compute them using new constraints that
6217 should succeed in all cases. Also alter directory authorities to
6218 not include the bandwidth-weights line if they fail to produce
6219 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
6220 - When weighting bridges during path selection, we used to trust
6221 the bandwidths they provided in their descriptor, only capping them
6222 at 10MB/s. This turned out to be problematic for two reasons:
6223 Bridges could claim to handle a lot more traffic then they
6224 actually would, thus making more clients pick them and have a
6225 pretty effective DoS attack. The other issue is that new bridges
6226 that might not have a good estimate for their bw capacity yet
6227 would not get used at all unless no other bridges are available
6228 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
6230 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
6231 - Ignore cannibalized circuits when recording circuit build times.
6232 This should provide for a minor performance improvement for hidden
6233 service users using 0.2.2.14-alpha, and should remove two spurious
6234 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
6235 - Simplify the logic that causes us to decide if the network is
6236 unavailable for purposes of recording circuit build times. If we
6237 receive no cells whatsoever for the entire duration of a circuit's
6238 full measured lifetime, the network is probably down. Also ignore
6239 one-hop directory fetching circuit timeouts when calculating our
6240 circuit build times. These changes should hopefully reduce the
6241 cases where we see ridiculous circuit build timeouts for people
6242 with spotty wireless connections. Fixes part of bug 1772; bugfix
6244 - Prevent the circuit build timeout from becoming larger than
6245 the maximum build time we have ever seen. Also, prevent the time
6246 period for measurement circuits from becoming larger than twice that
6247 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
6250 - When we run out of directory information such that we can't build
6251 circuits, but then get enough that we can build circuits, log when
6252 we actually construct a circuit, so the user has a better chance of
6253 knowing what's going on. Fixes bug 1362.
6254 - Be more generous with how much bandwidth we'd use up (with
6255 accounting enabled) before entering "soft hibernation". Previously,
6256 we'd refuse new connections and circuits once we'd used up 95% of
6257 our allotment. Now, we use up 95% of our allotment, AND make sure
6258 that we have no more than 500MB (or 3 hours of expected traffic,
6259 whichever is lower) remaining before we enter soft hibernation.
6260 - If we've configured EntryNodes and our network goes away and/or all
6261 our entrynodes get marked down, optimistically retry them all when
6262 a new socks application request appears. Fixes bug 1882.
6263 - Add some more defensive programming for architectures that can't
6264 handle unaligned integer accesses. We don't know of any actual bugs
6265 right now, but that's the best time to fix them. Fixes bug 1943.
6266 - Support line continuations in the torrc config file. If a line
6267 ends with a single backslash character, the newline is ignored, and
6268 the configuration value is treated as continuing on the next line.
6271 o Minor bugfixes (on 0.2.1.x and earlier):
6272 - For bandwidth accounting, calculate our expected bandwidth rate
6273 based on the time during which we were active and not in
6274 soft-hibernation during the last interval. Previously, we were
6275 also considering the time spent in soft-hibernation. If this
6276 was a long time, we would wind up underestimating our bandwidth
6277 by a lot, and skewing our wakeup time towards the start of the
6278 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
6280 o Minor bugfixes (on 0.2.2.x):
6281 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
6282 which were disabled by the circuit build timeout changes in
6283 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
6284 - Make sure we don't warn about missing bandwidth weights when
6285 choosing bridges or other relays not in the consensus. Bugfix on
6286 0.2.2.10-alpha; fixes bug 1805.
6287 - In our logs, do not double-report signatures from unrecognized
6288 authorities both as "from unknown authority" and "not
6289 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
6292 Changes in version 0.2.2.16-alpha - 2010-09-17
6293 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
6294 evident at exit relays), and also continues to resolve all the little
6295 bugs that have been filling up trac lately.
6297 o Major bugfixes (stream-level fairness):
6298 - When receiving a circuit-level SENDME for a blocked circuit, try
6299 to package cells fairly from all the streams that had previously
6300 been blocked on that circuit. Previously, we had started with the
6301 oldest stream, and allowed each stream to potentially exhaust
6302 the circuit's package window. This gave older streams on any
6303 given circuit priority over newer ones. Fixes bug 1937. Detected
6304 originally by Camilo Viecco. This bug was introduced before the
6305 first Tor release, in svn commit r152: it is the new winner of
6306 the longest-lived bug prize.
6307 - When the exit relay got a circuit-level sendme cell, it started
6308 reading on the exit streams, even if had 500 cells queued in the
6309 circuit queue already, so the circuit queue just grew and grew in
6310 some cases. We fix this by not re-enabling reading on receipt of a
6311 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
6312 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
6314 - Newly created streams were allowed to read cells onto circuits,
6315 even if the circuit's cell queue was blocked and waiting to drain.
6316 This created potential unfairness, as older streams would be
6317 blocked, but newer streams would gladly fill the queue completely.
6318 We add code to detect this situation and prevent any stream from
6319 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
6323 - Update to the September 1 2010 Maxmind GeoLite Country database.
6324 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
6325 not. This would lead to a cookie that is still not group readable.
6326 Closes bug 1843. Suggested by katmagic.
6327 - When logging a rate-limited warning, we now mention how many messages
6328 got suppressed since the last warning.
6329 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
6330 do individual connection-level rate limiting of clients. The torrc
6331 config options with the same names trump the consensus params, if
6332 both are present. Replaces the old "bwconnrate" and "bwconnburst"
6333 consensus params which were broken from 0.2.2.7-alpha through
6334 0.2.2.14-alpha. Closes bug 1947.
6335 - When a router changes IP address or port, authorities now launch
6336 a new reachability test for it. Implements ticket 1899.
6337 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
6338 2 no signature, 4 required" messages about consensus signatures
6339 easier to read, and make sure they get logged at the same severity
6340 as the messages explaining which keys are which. Fixes bug 1290.
6341 - Don't warn when we have a consensus that we can't verify because
6342 of missing certificates, unless those certificates are ones
6343 that we have been trying and failing to download. Fixes bug 1145.
6344 - If you configure your bridge with a known identity fingerprint,
6345 and the bridge authority is unreachable (as it is in at least
6346 one country now), fall back to directly requesting the descriptor
6347 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
6349 - When building with --enable-gcc-warnings on OpenBSD, disable
6350 warnings in system headers. This makes --enable-gcc-warnings
6351 pass on OpenBSD 4.8.
6353 o Minor bugfixes (on 0.2.1.x and earlier):
6354 - Authorities will now attempt to download consensuses if their
6355 own efforts to make a live consensus have failed. This change
6356 means authorities that restart will fetch a valid consensus, and
6357 it means authorities that didn't agree with the current consensus
6358 will still fetch and serve it if it has enough signatures. Bugfix
6359 on 0.2.0.9-alpha; fixes bug 1300.
6360 - Ensure DNS requests launched by "RESOLVE" commands from the
6361 controller respect the __LeaveStreamsUnattached setconf options. The
6362 same goes for requests launched via DNSPort or transparent
6363 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
6364 - Allow handshaking OR connections to take a full KeepalivePeriod
6365 seconds to handshake. Previously, we would close them after
6366 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
6367 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
6369 - Rate-limit "Failed to hand off onionskin" warnings.
6370 - Never relay a cell for a circuit we have already destroyed.
6371 Between marking a circuit as closeable and finally closing it,
6372 it may have been possible for a few queued cells to get relayed,
6373 even though they would have been immediately dropped by the next
6374 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
6375 - Never queue a cell for a circuit that's already been marked
6377 - Never vote for a server as "Running" if we have a descriptor for
6378 it claiming to be hibernating, and that descriptor was published
6379 more recently than our last contact with the server. Bugfix on
6380 0.2.0.3-alpha; fixes bug 911.
6381 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
6384 o Minor bugfixes (on 0.2.2.x):
6385 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
6386 down if a directory fetch fails and you've configured either
6387 bridges or EntryNodes. The intent was to mark the relay as down
6388 _unless_ you're using bridges or EntryNodes, since if you are
6389 then you could quickly run out of entry points.
6390 - Fix the Windows directory-listing code. A bug introduced in
6391 0.2.2.14-alpha could make Windows directory servers forget to load
6392 some of their cached v2 networkstatus files.
6393 - Really allow clients to use relays as bridges. Fixes bug 1776;
6394 bugfix on 0.2.2.15-alpha.
6395 - Demote a warn to info that happens when the CellStatistics option
6396 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
6397 Reported by Moritz Bartl.
6398 - On Windows, build correctly either with or without Unicode support.
6399 This is necessary so that Tor can support fringe platforms like
6400 Windows 98 (which has no Unicode), or Windows CE (which has no
6401 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
6404 - Add a unit test for cross-platform directory-listing code.
6407 Changes in version 0.2.2.15-alpha - 2010-08-18
6408 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
6409 fixes a variety of other bugs that were preventing performance
6410 experiments from moving forward, fixes several bothersome memory leaks,
6411 and generally closes a lot of smaller bugs that have been filling up
6415 - Stop assigning the HSDir flag to relays that disable their
6416 DirPort (and thus will refuse to answer directory requests). This
6417 fix should dramatically improve the reachability of hidden services:
6418 hidden services and hidden service clients pick six HSDir relays
6419 to store and retrieve the hidden service descriptor, and currently
6420 about half of the HSDir relays will refuse to work. Bugfix on
6421 0.2.0.10-alpha; fixes part of bug 1693.
6422 - The PerConnBWRate and Burst config options, along with the
6423 bwconnrate and bwconnburst consensus params, initialized each conn's
6424 token bucket values only when the connection is established. Now we
6425 update them if the config options change, and update them every time
6426 we get a new consensus. Otherwise we can encounter an ugly edge
6427 case where we initialize an OR conn to client-level bandwidth,
6428 but then later the relay joins the consensus and we leave it
6429 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
6430 - Fix a regression that caused Tor to rebind its ports if it receives
6431 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
6434 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
6435 should give us approximately 40-50% more Guard-flagged nodes,
6436 improving the anonymity the Tor network can provide and also
6437 decreasing the dropoff in throughput that relays experience when
6438 they first get the Guard flag.
6439 - Allow enabling or disabling the *Statistics config options while
6443 - Update to the August 1 2010 Maxmind GeoLite Country database.
6444 - Have the controller interface give a more useful message than
6445 "Internal Error" in response to failed GETINFO requests.
6446 - Warn when the same option is provided more than once in a torrc
6447 file, on the command line, or in a single SETCONF statement, and
6448 the option is one that only accepts a single line. Closes bug 1384.
6449 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
6450 Patch from mingw-san.
6451 - Add support for the country code "{??}" in torrc options like
6452 ExcludeNodes, to indicate all routers of unknown country. Closes
6454 - Relays report the number of bytes spent on answering directory
6455 requests in extra-info descriptors similar to {read,write}-history.
6456 Implements enhancement 1790.
6458 o Minor bugfixes (on 0.2.1.x and earlier):
6459 - Complain if PublishServerDescriptor is given multiple arguments that
6460 include 0 or 1. This configuration will be rejected in the future.
6461 Bugfix on 0.2.0.1-alpha; closes bug 1107.
6462 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
6463 Bugfix on 0.2.0.13-alpha; closes bug 928.
6464 - Change "Application request when we're believed to be offline."
6465 notice to "Application request when we haven't used client
6466 functionality lately.", to clarify that it's not an error. Bugfix
6467 on 0.0.9.3; fixes bug 1222.
6468 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
6469 would return "551 Internal error" rather than "552 Unrecognized key
6470 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
6471 - Users can't configure a regular relay to be their bridge. It didn't
6472 work because when Tor fetched the bridge descriptor, it found
6473 that it already had it, and didn't realize that the purpose of the
6474 descriptor had changed. Now we replace routers with a purpose other
6475 than bridge with bridge descriptors when fetching them. Bugfix on
6476 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
6477 refetch the descriptor with router purpose 'general', disabling
6479 - Fix a rare bug in rend_fn unit tests: we would fail a test when
6480 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
6481 on 0.2.0.10-alpha; fixes bug 1808.
6482 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
6483 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
6484 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
6485 Servers can start sending this code when enough clients recognize
6486 it. Also update the spec to reflect this new reason. Bugfix on
6487 0.1.0.1-rc; fixes part of bug 1793.
6488 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
6489 when we switch from being a public relay to a bridge. Otherwise
6490 there will still be clients that see the relay in their consensus,
6491 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
6493 - Instead of giving an assertion failure on an internal mismatch
6494 on estimated freelist size, just log a BUG warning and try later.
6495 Mitigates but does not fix bug 1125.
6496 - Fix an assertion failure that could occur in caches or bridge users
6497 when using a very short voting interval on a testing network.
6498 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
6500 o Minor bugfixes (on 0.2.2.x):
6501 - Alter directory authorities to always consider Exit-flagged nodes
6502 as potential Guard nodes in their votes. The actual decision to
6503 use Exits as Guards is done in the consensus bandwidth weights.
6504 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
6505 - When the controller is reporting the purpose of circuits that
6506 didn't finish building before the circuit build timeout, it was
6507 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
6508 - Our libevent version parsing code couldn't handle versions like
6509 1.4.14b-stable and incorrectly warned the user about using an
6510 old and broken version of libevent. Treat 1.4.14b-stable like
6511 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
6513 - Don't use substitution references like $(VAR:MOD) when
6514 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
6515 '$(:x)' to 'x' rather than the empty string. This bites us in
6516 doc/ when configured with --disable-asciidoc. Bugfix on
6517 0.2.2.9-alpha; fixes bug 1773.
6518 - Remove a spurious hidden service server-side log notice about
6519 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
6521 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
6523 - Correctly report written bytes on linked connections. Found while
6524 implementing 1790. Bugfix on 0.2.2.4-alpha.
6525 - Fix three memory leaks: one in circuit_build_times_parse_state(),
6526 one in dirvote_add_signatures_to_pending_consensus(), and one every
6527 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
6528 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
6530 o Code simplifications and refactoring:
6531 - Take a first step towards making or.h smaller by splitting out
6532 function definitions for all source files in src/or/. Leave
6533 structures and defines in or.h for now.
6534 - Remove a bunch of unused function declarations as well as a block of
6535 #if 0'd code from the unit tests. Closes bug 1824.
6536 - New unit tests for exit-port history statistics; refactored exit
6537 statistics code to be more easily tested.
6538 - Remove the old debian/ directory from the main Tor distribution.
6539 The official Tor-for-debian git repository lives at the URL
6540 https://git.torproject.org/debian/tor.git
6543 Changes in version 0.2.2.14-alpha - 2010-07-12
6544 Tor 0.2.2.14-alpha greatly improves client-side handling of
6545 circuit build timeouts, which are used to estimate speed and improve
6546 performance. We also move to a much better GeoIP database, port Tor to
6547 Windows CE, introduce new compile flags that improve code security,
6548 add an eighth v3 directory authority, and address a lot of more
6552 - Tor directory authorities no longer crash when started with a
6553 cached-microdesc-consensus file in their data directory. Bugfix
6554 on 0.2.2.6-alpha; fixes bug 1532.
6555 - Treat an unset $HOME like an empty $HOME rather than triggering an
6556 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
6557 - Ignore negative and large circuit build timeout values that can
6558 happen during a suspend or hibernate. These values caused various
6559 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
6560 - Alter calculation of Pareto distribution parameter 'Xm' for
6561 Circuit Build Timeout learning to use the weighted average of the
6562 top N=3 modes (because we have three entry guards). Considering
6563 multiple modes should improve the timeout calculation in some cases,
6564 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
6566 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
6567 right censored distribution model. This approach improves over the
6568 synthetic timeout generation approach that was producing insanely
6569 high timeout values. Now we calculate build timeouts using truncated
6570 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
6571 - Do not close circuits that are under construction when they reach
6572 the circuit build timeout. Instead, leave them building (but do not
6573 use them) for up until the time corresponding to the 95th percentile
6574 on the Pareto CDF or 60 seconds, whichever is greater. This is done
6575 to provide better data for the new Pareto model. This percentile
6576 can be controlled by the consensus.
6579 - Move to the June 2010 Maxmind GeoLite country db (rather than the
6580 June 2009 ip-to-country GeoIP db) for our statistics that count
6581 how many users relays are seeing from each country. Now we have
6582 more accurate data for many African countries.
6583 - Port Tor to build and run correctly on Windows CE systems, using
6584 the wcecompat library. Contributed by Valerio Lupi.
6585 - New "--enable-gcc-hardening" ./configure flag (off by default)
6586 to turn on gcc compile time hardening options. It ensures
6587 that signed ints have defined behavior (-fwrapv), enables
6588 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
6589 with canaries (-fstack-protector-all), turns on ASLR protection if
6590 supported by the kernel (-fPIE, -pie), and adds additional security
6591 related warnings. Verified to work on Mac OS X and Debian Lenny.
6592 - New "--enable-linker-hardening" ./configure flag (off by default)
6593 to turn on ELF specific hardening features (relro, now). This does
6594 not work with Mac OS X or any other non-ELF binary format.
6596 o New directory authorities:
6597 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
6601 - New config option "WarnUnsafeSocks 0" disables the warning that
6602 occurs whenever Tor receives a socks handshake using a version of
6603 the socks protocol that can only provide an IP address (rather
6604 than a hostname). Setups that do DNS locally over Tor are fine,
6605 and we shouldn't spam the logs in that case.
6606 - Convert the HACKING file to asciidoc, and add a few new sections
6607 to it, explaining how we use Git, how we make changelogs, and
6608 what should go in a patch.
6609 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
6610 event, to give information on the current rate of circuit timeouts
6611 over our stored history.
6612 - Add ability to disable circuit build time learning via consensus
6613 parameter and via a LearnCircuitBuildTimeout config option. Also
6614 automatically disable circuit build time calculation if we are
6615 either a AuthoritativeDirectory, or if we fail to write our state
6616 file. Fixes bug 1296.
6617 - More gracefully handle corrupt state files, removing asserts
6618 in favor of saving a backup and resetting state.
6619 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
6623 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
6625 - When a2x fails, mention that the user could disable manpages instead
6626 of trying to fix their asciidoc installation.
6627 - Where available, use Libevent 2.0's periodic timers so that our
6628 once-per-second cleanup code gets called even more closely to
6629 once per second than it would otherwise. Fixes bug 943.
6630 - If you run a bridge that listens on multiple IP addresses, and
6631 some user configures a bridge address that uses a different IP
6632 address than your bridge writes in its router descriptor, and the
6633 user doesn't specify an identity key, their Tor would discard the
6634 descriptor because "it isn't one of our configured bridges", and
6635 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
6636 Bugfix on 0.2.0.3-alpha.
6637 - If OpenSSL fails to make a duplicate of a private or public key, log
6638 an error message and try to exit cleanly. May help with debugging
6639 if bug 1209 ever remanifests.
6640 - Save a couple bytes in memory allocation every time we escape
6641 certain characters in a string. Patch from Florian Zumbiehl.
6642 - Make it explicit that we don't cannibalize one-hop circuits. This
6643 happens in the wild, but doesn't turn out to be a problem because
6644 we fortunately don't use those circuits. Many thanks to outofwords
6645 for the initial analysis and to swissknife who confirmed that
6646 two-hop circuits are actually created.
6647 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
6648 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
6649 - Eliminate a case where a circuit build time warning was displayed
6650 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
6653 Changes in version 0.2.1.26 - 2010-05-02
6654 Tor 0.2.1.26 addresses the recent connection and memory overload
6655 problems we've been seeing on relays, especially relays with their
6656 DirPort open. If your relay has been crashing, or you turned it off
6657 because it used too many resources, give this release a try.
6659 This release also fixes yet another instance of broken OpenSSL libraries
6660 that was causing some relays to drop out of the consensus.
6663 - Teach relays to defend themselves from connection overload. Relays
6664 now close idle circuits early if it looks like they were intended
6665 for directory fetches. Relays are also more aggressive about closing
6666 TLS connections that have no circuits on them. Such circuits are
6667 unlikely to be re-used, and tens of thousands of them were piling
6668 up at the fast relays, causing the relays to run out of sockets
6669 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6670 their directory fetches over TLS).
6671 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6672 that claim to be earlier than 0.9.8m, but which have in reality
6673 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6674 behavior. Possible fix for some cases of bug 1346.
6675 - Directory mirrors were fetching relay descriptors only from v2
6676 directory authorities, rather than v3 authorities like they should.
6677 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6678 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6681 - Finally get rid of the deprecated and now harmful notion of "clique
6682 mode", where directory authorities maintain TLS connections to
6686 - In the util/threads test, no longer free the test_mutex before all
6687 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6688 - The master thread could starve the worker threads quite badly on
6689 certain systems, causing them to run only partially in the allowed
6690 window. This resulted in test failures. Now the master thread sleeps
6691 occasionally for a few microseconds while the two worker-threads
6692 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6695 Changes in version 0.2.2.13-alpha - 2010-04-24
6696 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
6697 problems we've been seeing on relays, especially relays with their
6698 DirPort open. If your relay has been crashing, or you turned it off
6699 because it used too many resources, give this release a try.
6702 - Teach relays to defend themselves from connection overload. Relays
6703 now close idle circuits early if it looks like they were intended
6704 for directory fetches. Relays are also more aggressive about closing
6705 TLS connections that have no circuits on them. Such circuits are
6706 unlikely to be re-used, and tens of thousands of them were piling
6707 up at the fast relays, causing the relays to run out of sockets
6708 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6709 their directory fetches over TLS).
6712 - Finally get rid of the deprecated and now harmful notion of "clique
6713 mode", where directory authorities maintain TLS connections to
6715 - Directory authorities now do an immediate reachability check as soon
6716 as they hear about a new relay. This change should slightly reduce
6717 the time between setting up a relay and getting listed as running
6718 in the consensus. It should also improve the time between setting
6719 up a bridge and seeing use by bridge users.
6720 - Directory authorities no longer launch a TLS connection to every
6721 relay as they startup. Now that we have 2k+ descriptors cached,
6722 the resulting network hiccup is becoming a burden. Besides,
6723 authorities already avoid voting about Running for the first half
6724 hour of their uptime.
6727 Changes in version 0.2.2.12-alpha - 2010-04-20
6728 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
6729 handle and vote on descriptors. It was causing relays to drop out of
6733 - Many relays have been falling out of the consensus lately because
6734 not enough authorities know about their descriptor for them to get
6735 a majority of votes. When we deprecated the v2 directory protocol,
6736 we got rid of the only way that v3 authorities can hear from each
6737 other about other descriptors. Now authorities examine every v3
6738 vote for new descriptors, and fetch them from that authority. Bugfix
6740 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
6741 and a warning in or.h related to bandwidth_weight_rule_t that
6742 prevented clean compile on OS X. Fixes bug 1363; bugfix on
6744 - Fix a segfault on relays when DirReqStatistics is enabled
6745 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
6749 - Demote a confusing TLS warning that relay operators might get when
6750 someone tries to talk to their OrPort. It is neither the operator's
6751 fault nor can they do anything about it. Fixes bug 1364; bugfix
6755 Changes in version 0.2.2.11-alpha - 2010-04-15
6756 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
6757 libraries that was causing some relays to drop out of the consensus.
6760 - Directory mirrors were fetching relay descriptors only from v2
6761 directory authorities, rather than v3 authorities like they should.
6762 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6763 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6764 - Fix a parsing error that made every possible value of
6765 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
6766 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
6767 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
6768 about the option without breaking older ones.
6769 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6770 that claim to be earlier than 0.9.8m, but which have in reality
6771 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6772 behavior. Possible fix for some cases of bug 1346.
6775 - Experiment with a more aggressive approach to preventing clients
6776 from making one-hop exit streams. Exit relays who want to try it
6777 out can set "RefuseUnknownExits 1" in their torrc, and then look
6778 for "Attempt by %s to open a stream" log messages. Let us know
6780 - Add support for statically linking zlib by specifying
6781 --enable-static-zlib, to go with our support for statically linking
6782 openssl and libevent. Resolves bug 1358.
6785 - Fix a segfault that happens whenever a Tor client that is using
6786 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
6788 - When we cleaned up the contrib/tor-exit-notice.html file, we left
6789 out the first line. Fixes bug 1295.
6790 - When building the manpage from a tarball, we required asciidoc, but
6791 the asciidoc -> roff/html conversion was already done for the
6792 tarball. Make 'make' complain only when we need asciidoc (either
6793 because we're compiling directly from git, or because we altered
6794 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
6795 - When none of the directory authorities vote on any params, Tor
6796 segfaulted when trying to make the consensus from the votes. We
6797 didn't trigger the bug in practice, because authorities do include
6798 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
6801 - In the util/threads test, no longer free the test_mutex before all
6802 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6803 - The master thread could starve the worker threads quite badly on
6804 certain systems, causing them to run only partially in the allowed
6805 window. This resulted in test failures. Now the master thread sleeps
6806 occasionally for a few microseconds while the two worker-threads
6807 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6810 Changes in version 0.2.2.10-alpha - 2010-03-07
6811 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
6812 could prevent relays from guessing their IP address correctly. It also
6813 starts the groundwork for another client-side performance boost, since
6814 currently we're not making efficient use of relays that have both the
6815 Guard flag and the Exit flag.
6818 - Fix a regression from our patch for bug 1244 that caused relays
6819 to guess their IP address incorrectly if they didn't set Address
6820 in their torrc and/or their address fails to resolve. Bugfix on
6821 0.2.2.9-alpha; fixes bug 1269.
6823 o Major features (performance):
6824 - Directory authorities now compute consensus weightings that instruct
6825 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
6826 and no flag. Clients that use these weightings will distribute
6827 network load more evenly across these different relay types. The
6828 weightings are in the consensus so we can change them globally in
6829 the future. Extra thanks to "outofwords" for finding some nasty
6830 security bugs in the first implementation of this feature.
6832 o Minor features (performance):
6833 - Always perform router selections using weighted relay bandwidth,
6834 even if we don't need a high capacity circuit at the time. Non-fast
6835 circuits now only differ from fast ones in that they can use relays
6836 not marked with the Fast flag. This "feature" could turn out to
6837 be a horrible bug; we should investigate more before it goes into
6841 - Allow disabling building of the manpages. Skipping the manpage
6842 speeds up the build considerably.
6844 o Minor bugfixes (on 0.2.2.x):
6845 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
6846 Bugfix on 0.2.2.9-alpha.
6847 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
6848 config option. Bugfix on 0.2.2.7-alpha.
6849 - Ship the asciidoc-helper file in the tarball, so that people can
6850 build from source if they want to, and touching the .1.txt files
6851 doesn't break the build. Bugfix on 0.2.2.9-alpha.
6853 o Minor bugfixes (on 0.2.1.x or earlier):
6854 - Fix a dereference-then-NULL-check sequence when publishing
6855 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6857 - Fix another dereference-then-NULL-check sequence. Bugfix on
6858 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6859 - Make sure we treat potentially not NUL-terminated strings correctly.
6860 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6862 o Code simplifications and refactoring:
6863 - Fix some urls in the exit notice file and make it XHTML1.1 strict
6864 compliant. Based on a patch from Christian Kujau.
6865 - Don't use sed in asciidoc-helper anymore.
6866 - Make the build process fail if asciidoc cannot be found and
6867 building with asciidoc isn't disabled.
6870 Changes in version 0.2.2.9-alpha - 2010-02-22
6871 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
6872 location of a directory authority, and cleans up a bunch of small bugs.
6874 o Directory authority changes:
6875 - Change IP address for dannenberg (v3 directory authority), and
6876 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6877 service directory authority) from the list.
6880 - Make Tor work again on the latest OS X: when deciding whether to
6881 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6882 version at run-time, not compile time. We need to do this because
6883 Apple doesn't update its dev-tools headers when it updates its
6884 libraries in a security patch.
6885 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6886 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6887 a memory leak when requesting a hidden service descriptor we've
6888 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6890 - Authorities could be tricked into giving out the Exit flag to relays
6891 that didn't allow exiting to any ports. This bug could screw
6892 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
6893 1238. Bug discovered by Martin Kowalczyk.
6894 - When freeing a session key, zero it out completely. We only zeroed
6895 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6896 patched by ekir. Fixes bug 1254.
6899 - Fix static compilation by listing the openssl libraries in the right
6900 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
6901 - Resume handling .exit hostnames in a special way: originally we
6902 stripped the .exit part and used the requested exit relay. In
6903 0.2.2.1-alpha we stopped treating them in any special way, meaning
6904 if you use a .exit address then Tor will pass it on to the exit
6905 relay. Now we reject the .exit stream outright, since that behavior
6906 might be more expected by the user. Found and diagnosed by Scott
6907 Bennett and Downie on or-talk.
6908 - Don't spam the controller with events when we have no file
6909 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
6910 for log messages was already solved from bug 748.)
6911 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
6913 - Make the DNSPort option work with libevent 2.x. Don't alter the
6914 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
6915 - Emit a GUARD DROPPED controller event for a case we missed.
6916 - Make more fields in the controller protocol case-insensitive, since
6917 control-spec.txt said they were.
6918 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6919 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6920 - Fix a spec conformance issue: the network-status-version token
6921 must be the first token in a v3 consensus or vote. Discovered by
6922 parakeep. Bugfix on 0.2.0.3-alpha.
6924 o Code simplifications and refactoring:
6925 - Generate our manpage and HTML documentation using Asciidoc. This
6926 change should make it easier to maintain the documentation, and
6928 - Remove the --enable-iphone option. According to reports from Marco
6929 Bonetti, Tor builds fine without any special tweaking on recent
6930 iPhone SDK versions.
6931 - Removed some unnecessary files from the source distribution. The
6932 AUTHORS file has now been merged into the people page on the
6933 website. The roadmaps and design doc can now be found in the
6934 projects directory in svn.
6935 - Enabled various circuit build timeout constants to be controlled
6936 by consensus parameters. Also set better defaults for these
6937 parameters based on experimentation on broadband and simulated
6941 - The 'EXTENDCIRCUIT' control port command can now be used with
6942 a circ id of 0 and no path. This feature will cause Tor to build
6943 a new 'fast' general purpose circuit using its own path selection
6945 - Added a BUILDTIMEOUT_SET controller event to describe changes
6946 to the circuit build timeout.
6947 - Future-proof the controller protocol a bit by ignoring keyword
6948 arguments we do not recognize.
6949 - Expand homedirs passed to tor-checkkey. This should silence a
6950 coverity complaint about passing a user-supplied string into
6951 open() without checking it.
6954 Changes in version 0.2.1.25 - 2010-03-16
6955 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
6956 prevent relays from guessing their IP address correctly. It also fixes
6957 several minor potential security bugs.
6960 - Fix a regression from our patch for bug 1244 that caused relays
6961 to guess their IP address incorrectly if they didn't set Address
6962 in their torrc and/or their address fails to resolve. Bugfix on
6963 0.2.1.23; fixes bug 1269.
6964 - When freeing a session key, zero it out completely. We only zeroed
6965 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6966 patched by ekir. Fixes bug 1254.
6969 - Fix a dereference-then-NULL-check sequence when publishing
6970 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6972 - Fix another dereference-then-NULL-check sequence. Bugfix on
6973 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6974 - Make sure we treat potentially not NUL-terminated strings correctly.
6975 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6979 Changes in version 0.2.1.24 - 2010-02-21
6980 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
6984 - Work correctly out-of-the-box with even more vendor-patched versions
6985 of OpenSSL. In particular, make it so Debian and OS X don't need
6986 customized patches to run/build.
6989 Changes in version 0.2.1.23 - 2010-02-13
6990 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
6991 again on the latest OS X, and updates the location of a directory
6994 o Major bugfixes (performance):
6995 - We were selecting our guards uniformly at random, and then weighting
6996 which of our guards we'd use uniformly at random. This imbalance
6997 meant that Tor clients were severely limited on throughput (and
6998 probably latency too) by the first hop in their circuit. Now we
6999 select guards weighted by currently advertised bandwidth. We also
7000 automatically discard guards picked using the old algorithm. Fixes
7001 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
7004 - Make Tor work again on the latest OS X: when deciding whether to
7005 use strange flags to turn TLS renegotiation on, detect the OpenSSL
7006 version at run-time, not compile time. We need to do this because
7007 Apple doesn't update its dev-tools headers when it updates its
7008 libraries in a security patch.
7009 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
7010 that could happen on 32-bit platforms with 64-bit time_t. Also fix
7011 a memory leak when requesting a hidden service descriptor we've
7012 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
7015 o Directory authority changes:
7016 - Change IP address for dannenberg (v3 directory authority), and
7017 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
7018 service directory authority) from the list.
7021 - Refactor resolve_my_address() to not use gethostbyname() anymore.
7022 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
7025 - Avoid a mad rush at the beginning of each month when each client
7026 rotates half of its guards. Instead we spread the rotation out
7027 throughout the month, but we still avoid leaving a precise timestamp
7028 in the state file about when we first picked the guard. Improves
7029 over the behavior introduced in 0.1.2.17.
7032 Changes in version 0.2.2.8-alpha - 2010-01-26
7033 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
7034 causing bridge relays to disappear. If you're running a bridge,
7038 - Fix a memory corruption bug on bridges that occured during the
7039 inclusion of stats data in extra-info descriptors. Also fix the
7040 interface for geoip_get_bridge_stats* to prevent similar bugs in
7041 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
7042 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
7045 - Ignore OutboundBindAddress when connecting to localhost.
7046 Connections to localhost need to come _from_ localhost, or else
7047 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
7051 Changes in version 0.2.2.7-alpha - 2010-01-19
7052 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
7053 as laying the groundwork for further relay-side performance fixes. It
7054 also starts cleaning up client behavior with respect to the EntryNodes,
7055 ExitNodes, and StrictNodes config options.
7057 This release also rotates two directory authority keys, due to a
7058 security breach of some of the Torproject servers.
7060 o Directory authority changes:
7061 - Rotate keys (both v3 identity and relay identity) for moria1
7064 o Major features (performance):
7065 - We were selecting our guards uniformly at random, and then weighting
7066 which of our guards we'd use uniformly at random. This imbalance
7067 meant that Tor clients were severely limited on throughput (and
7068 probably latency too) by the first hop in their circuit. Now we
7069 select guards weighted by currently advertised bandwidth. We also
7070 automatically discard guards picked using the old algorithm. Fixes
7071 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
7072 - When choosing which cells to relay first, relays can now favor
7073 circuits that have been quiet recently, to provide lower latency
7074 for low-volume circuits. By default, relays enable or disable this
7075 feature based on a setting in the consensus. You can override
7076 this default by using the new "CircuitPriorityHalflife" config
7077 option. Design and code by Ian Goldberg, Can Tang, and Chris
7079 - Add separate per-conn write limiting to go with the per-conn read
7080 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
7081 but never per-conn write limits.
7082 - New consensus params "bwconnrate" and "bwconnburst" to let us
7083 rate-limit client connections as they enter the network. It's
7084 controlled in the consensus so we can turn it on and off for
7085 experiments. It's starting out off. Based on proposal 163.
7087 o Major features (relay selection options):
7088 - Switch to a StrictNodes config option, rather than the previous
7089 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
7090 "StrictExcludeNodes" option.
7091 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
7092 change during a config reload, mark and discard all our origin
7093 circuits. This fix should address edge cases where we change the
7094 config options and but then choose a circuit that we created before
7096 - If EntryNodes or ExitNodes are set, be more willing to use an
7097 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
7099 - Make EntryNodes config option much more aggressive even when
7100 StrictNodes is not set. Before it would prepend your requested
7101 entrynodes to your list of guard nodes, but feel free to use others
7102 after that. Now it chooses only from your EntryNodes if any of
7103 those are available, and only falls back to others if a) they're
7104 all down and b) StrictNodes is not set.
7105 - Now we refresh your entry guards from EntryNodes at each consensus
7106 fetch -- rather than just at startup and then they slowly rot as
7107 the network changes.
7110 - Stop bridge directory authorities from answering dbg-stability.txt
7111 directory queries, which would let people fetch a list of all
7112 bridge identities they track. Bugfix on 0.2.1.6-alpha.
7115 - Log a notice when we get a new control connection. Now it's easier
7116 for security-conscious users to recognize when a local application
7117 is knocking on their controller door. Suggested by bug 1196.
7118 - New config option "CircuitStreamTimeout" to override our internal
7119 timeout schedule for how many seconds until we detach a stream from
7120 a circuit and try a new circuit. If your network is particularly
7121 slow, you might want to set this to a number like 60.
7122 - New controller command "getinfo config-text". It returns the
7123 contents that Tor would write if you send it a SAVECONF command,
7124 so the controller can write the file to disk itself.
7125 - New options for SafeLogging to allow scrubbing only log messages
7126 generated while acting as a relay.
7127 - Ship the bridges spec file in the tarball too.
7128 - Avoid a mad rush at the beginning of each month when each client
7129 rotates half of its guards. Instead we spread the rotation out
7130 throughout the month, but we still avoid leaving a precise timestamp
7131 in the state file about when we first picked the guard. Improves
7132 over the behavior introduced in 0.1.2.17.
7134 o Minor bugfixes (compiling):
7135 - Fix compilation on OS X 10.3, which has a stub mlockall() but
7136 hides it. Bugfix on 0.2.2.6-alpha.
7137 - Fix compilation on Solaris by removing support for the
7138 DisableAllSwap config option. Solaris doesn't have an rlimit for
7139 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
7142 o Minor bugfixes (crashes):
7143 - Do not segfault when writing buffer stats when we haven't observed
7144 a single circuit to report about. Found by Fabian Lanze. Bugfix on
7146 - If we're in the pathological case where there's no exit bandwidth
7147 but there is non-exit bandwidth, or no guard bandwidth but there
7148 is non-guard bandwidth, don't crash during path selection. Bugfix
7150 - Fix an impossible-to-actually-trigger buffer overflow in relay
7151 descriptor generation. Bugfix on 0.1.0.15.
7153 o Minor bugfixes (privacy):
7154 - Fix an instance where a Tor directory mirror might accidentally
7155 log the IP address of a misbehaving Tor client. Bugfix on
7157 - Don't list Windows capabilities in relay descriptors. We never made
7158 use of them, and maybe it's a bad idea to publish them. Bugfix
7161 o Minor bugfixes (other):
7162 - Resolve an edge case in path weighting that could make us misweight
7163 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
7164 - Fix statistics on client numbers by country as seen by bridges that
7165 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
7166 intervals instead of variable 12-to-48-hour intervals.
7167 - After we free an internal connection structure, overwrite it
7168 with a different memory value than we use for overwriting a freed
7169 internal circuit structure. Should help with debugging. Suggested
7171 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
7175 - Remove the HSAuthorityRecordStats option that version 0 hidden
7176 service authorities could have used to track statistics of overall
7177 hidden service usage.
7180 Changes in version 0.2.1.22 - 2010-01-19
7181 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
7182 authorities -- it would tell you its whole history of bridge descriptors
7183 if you make the right directory request. This stable update also
7184 rotates two of the seven v3 directory authority keys and locations.
7186 o Directory authority changes:
7187 - Rotate keys (both v3 identity and relay identity) for moria1
7191 - Stop bridge directory authorities from answering dbg-stability.txt
7192 directory queries, which would let people fetch a list of all
7193 bridge identities they track. Bugfix on 0.2.1.6-alpha.
7196 Changes in version 0.2.1.21 - 2009-12-21
7197 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
7198 library. If you use Tor on Linux / Unix and you're getting SSL
7199 renegotiation errors, upgrading should help. We also recommend an
7200 upgrade if you're an exit relay.
7203 - Work around a security feature in OpenSSL 0.9.8l that prevents our
7204 handshake from working unless we explicitly tell OpenSSL that we
7205 are using SSL renegotiation safely. We are, of course, but OpenSSL
7206 0.9.8l won't work unless we say we are.
7207 - Avoid crashing if the client is trying to upload many bytes and the
7208 circuit gets torn down at the same time, or if the flip side
7209 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
7212 - Do not refuse to learn about authority certs and v2 networkstatus
7213 documents that are older than the latest consensus. This bug might
7214 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
7215 Spotted and fixed by xmux.
7216 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
7217 trigger platform-specific option misparsing case found by Coverity
7219 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
7220 trigger assert. Fixes bug 1173.
7223 Changes in version 0.2.2.6-alpha - 2009-11-19
7224 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
7225 support for the new lower-footprint "microdescriptor" directory design,
7226 future-proofing our consensus format against new hash functions or
7227 other changes, and an Android port. It also makes Tor compatible with
7228 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
7231 - Directory authorities can now create, vote on, and serve multiple
7232 parallel formats of directory data as part of their voting process.
7233 Partially implements Proposal 162: "Publish the consensus in
7235 - Directory authorities can now agree on and publish small summaries
7236 of router information that clients can use in place of regular
7237 server descriptors. This transition will eventually allow clients
7238 to use far less bandwidth for downloading information about the
7239 network. Begins the implementation of Proposal 158: "Clients
7240 download consensus + microdescriptors".
7241 - The directory voting system is now extensible to use multiple hash
7242 algorithms for signatures and resource selection. Newer formats
7243 are signed with SHA256, with a possibility for moving to a better
7244 hash algorithm in the future.
7245 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
7246 current and future memory pages via mlockall(). On supported
7247 platforms (modern Linux and probably BSD but not Windows or OS X),
7248 this should effectively disable any and all attempts to page out
7249 memory. This option requires that you start your Tor as root --
7250 if you use DisableAllSwap, please consider using the User option
7251 to properly reduce the privileges of your Tor.
7252 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
7253 to help Tor build correctly for Android phones.
7256 - Work around a security feature in OpenSSL 0.9.8l that prevents our
7257 handshake from working unless we explicitly tell OpenSSL that we
7258 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
7259 won't work unless we say we are.
7262 - Fix a crash bug when trying to initialize the evdns module in
7263 Libevent 2. Bugfix on 0.2.1.16-rc.
7264 - Stop logging at severity 'warn' when some other Tor client tries
7265 to establish a circuit with us using weak DH keys. It's a protocol
7266 violation, but that doesn't mean ordinary users need to hear about
7267 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
7268 - Do not refuse to learn about authority certs and v2 networkstatus
7269 documents that are older than the latest consensus. This bug might
7270 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
7271 Spotted and fixed by xmux.
7272 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
7273 - If all authorities restart at once right before a consensus vote,
7274 nobody will vote about "Running", and clients will get a consensus
7275 with no usable relays. Instead, authorities refuse to build a
7276 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
7277 - If your relay can't keep up with the number of incoming create
7278 cells, it would log one warning per failure into your logs. Limit
7279 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
7280 - Bridges now use "reject *:*" as their default exit policy. Bugfix
7281 on 0.2.0.3-alpha; fixes bug 1113.
7282 - Fix a memory leak on directory authorities during voting that was
7283 introduced in 0.2.2.1-alpha. Found via valgrind.
7286 Changes in version 0.2.1.20 - 2009-10-15
7287 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
7288 services at once, prepares for more performance improvements, and
7289 fixes a bunch of smaller bugs.
7291 The Windows and OS X bundles also include a more recent Vidalia,
7292 and switch from Privoxy to Polipo.
7294 The OS X installers are now drag and drop. It's best to un-install
7295 Tor/Vidalia and then install this new bundle, rather than upgrade. If
7296 you want to upgrade, you'll need to update the paths for Tor and Polipo
7297 in the Vidalia Settings window.
7300 - Send circuit or stream sendme cells when our window has decreased
7301 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
7302 by Karsten when testing the "reduce circuit window" performance
7303 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7304 before the release of Tor 0.0.0. This is the new winner of the
7306 - Fix a remotely triggerable memory leak when a consensus document
7307 contains more than one signature from the same voter. Bugfix on
7309 - Avoid segfault in rare cases when finishing an introduction circuit
7310 as a client and finding out that we don't have an introduction key
7311 for it. Fixes bug 1073. Reported by Aaron Swartz.
7314 - Tor now reads the "circwindow" parameter out of the consensus,
7315 and uses that value for its circuit package window rather than the
7316 default of 1000 cells. Begins the implementation of proposal 168.
7318 o New directory authorities:
7319 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
7321 - Move moria1 and tonga to alternate IP addresses.
7324 - Fix a signed/unsigned compile warning in 0.2.1.19.
7325 - Fix possible segmentation fault on directory authorities. Bugfix on
7327 - Fix an extremely rare infinite recursion bug that could occur if
7328 we tried to log a message after shutting down the log subsystem.
7329 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
7330 - Fix an obscure bug where hidden services on 64-bit big-endian
7331 systems might mis-read the timestamp in v3 introduce cells, and
7332 refuse to connect back to the client. Discovered by "rotor".
7333 Bugfix on 0.2.1.6-alpha.
7334 - We were triggering a CLOCK_SKEW controller status event whenever
7335 we connect via the v2 connection protocol to any relay that has
7336 a wrong clock. Instead, we should only inform the controller when
7337 it's a trusted authority that claims our clock is wrong. Bugfix
7338 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
7339 - We were telling the controller about CHECKING_REACHABILITY and
7340 REACHABILITY_FAILED status events whenever we launch a testing
7341 circuit or notice that one has failed. Instead, only tell the
7342 controller when we want to inform the user of overall success or
7343 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7345 - Don't warn when we're using a circuit that ends with a node
7346 excluded in ExcludeExitNodes, but the circuit is not used to access
7347 the outside world. This should help fix bug 1090. Bugfix on
7349 - Work around a small memory leak in some versions of OpenSSL that
7350 stopped the memory used by the hostname TLS extension from being
7354 - Add a "getinfo status/accepted-server-descriptor" controller
7355 command, which is the recommended way for controllers to learn
7356 whether our server descriptor has been successfully received by at
7357 least on directory authority. Un-recommend good-server-descriptor
7358 getinfo and status events until we have a better design for them.
7361 Changes in version 0.2.2.5-alpha - 2009-10-11
7362 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
7365 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
7367 o Directory authorities:
7368 - Temporarily (just for this release) move dizum to an alternate
7372 Changes in version 0.2.2.4-alpha - 2009-10-10
7373 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
7374 introduces a new unit test framework, shifts directry authority
7375 addresses around to reduce the impact from recent blocking events,
7376 and fixes a few smaller bugs.
7379 - Fix several more asserts in the circuit_build_times code, for
7380 example one that causes Tor to fail to start once we have
7381 accumulated 5000 build times in the state file. Bugfixes on
7382 0.2.2.2-alpha; fixes bug 1108.
7384 o New directory authorities:
7385 - Move moria1 and Tonga to alternate IP addresses.
7388 - Log SSL state transitions at debug level during handshake, and
7389 include SSL states in error messages. This may help debug future
7390 SSL handshake issues.
7391 - Add a new "Handshake" log domain for activities that happen
7392 during the TLS handshake.
7393 - Revert to the "June 3 2009" ip-to-country file. The September one
7394 seems to have removed most US IP addresses.
7395 - Directory authorities now reject Tor relays with versions less than
7396 0.1.2.14. This step cuts out four relays from the current network,
7397 none of which are very big.
7400 - Fix a couple of smaller issues with gathering statistics. Bugfixes
7402 - Fix two memory leaks in the error case of
7403 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
7404 - Don't count one-hop circuits when we're estimating how long it
7405 takes circuits to build on average. Otherwise we'll set our circuit
7406 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
7407 - Directory authorities no longer change their opinion of, or vote on,
7408 whether a router is Running, unless they have themselves been
7409 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
7412 o Code simplifications and refactoring:
7413 - Revise our unit tests to use the "tinytest" framework, so we
7414 can run tests in their own processes, have smarter setup/teardown
7415 code, and so on. The unit test code has moved to its own
7416 subdirectory, and has been split into multiple modules.
7419 Changes in version 0.2.2.3-alpha - 2009-09-23
7420 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
7423 - Fix an overzealous assert in our new circuit build timeout code.
7424 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
7427 - If the networkstatus consensus tells us that we should use a
7428 negative circuit package window, ignore it. Otherwise we'll
7429 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
7432 Changes in version 0.2.2.2-alpha - 2009-09-21
7433 Tor 0.2.2.2-alpha introduces our latest performance improvement for
7434 clients: Tor tracks the average time it takes to build a circuit, and
7435 avoids using circuits that take too long to build. For fast connections,
7436 this feature can cut your expected latency in half. For slow or flaky
7437 connections, it could ruin your Tor experience. Let us know if it does!
7440 - Tor now tracks how long it takes to build client-side circuits
7441 over time, and adapts its timeout to local network performance.
7442 Since a circuit that takes a long time to build will also provide
7443 bad performance, we get significant latency improvements by
7444 discarding the slowest 20% of circuits. Specifically, Tor creates
7445 circuits more aggressively than usual until it has enough data
7446 points for a good timeout estimate. Implements proposal 151.
7447 We are especially looking for reports (good and bad) from users with
7448 both EDGE and broadband connections that can move from broadband
7449 to EDGE and find out if the build-time data in the .tor/state gets
7450 reset without loss of Tor usability. You should also see a notice
7451 log message telling you that Tor has reset its timeout.
7452 - Directory authorities can now vote on arbitary integer values as
7453 part of the consensus process. This is designed to help set
7454 network-wide parameters. Implements proposal 167.
7455 - Tor now reads the "circwindow" parameter out of the consensus,
7456 and uses that value for its circuit package window rather than the
7457 default of 1000 cells. Begins the implementation of proposal 168.
7460 - Fix a remotely triggerable memory leak when a consensus document
7461 contains more than one signature from the same voter. Bugfix on
7465 - Fix an extremely rare infinite recursion bug that could occur if
7466 we tried to log a message after shutting down the log subsystem.
7467 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
7468 - Fix parsing for memory or time units given without a space between
7469 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
7470 - A networkstatus vote must contain exactly one signature. Spec
7471 conformance issue. Bugfix on 0.2.0.3-alpha.
7472 - Fix an obscure bug where hidden services on 64-bit big-endian
7473 systems might mis-read the timestamp in v3 introduce cells, and
7474 refuse to connect back to the client. Discovered by "rotor".
7475 Bugfix on 0.2.1.6-alpha.
7476 - We were triggering a CLOCK_SKEW controller status event whenever
7477 we connect via the v2 connection protocol to any relay that has
7478 a wrong clock. Instead, we should only inform the controller when
7479 it's a trusted authority that claims our clock is wrong. Bugfix
7480 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
7481 - We were telling the controller about CHECKING_REACHABILITY and
7482 REACHABILITY_FAILED status events whenever we launch a testing
7483 circuit or notice that one has failed. Instead, only tell the
7484 controller when we want to inform the user of overall success or
7485 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7487 - Don't warn when we're using a circuit that ends with a node
7488 excluded in ExcludeExitNodes, but the circuit is not used to access
7489 the outside world. This should help fix bug 1090, but more problems
7490 remain. Bugfix on 0.2.1.6-alpha.
7491 - Work around a small memory leak in some versions of OpenSSL that
7492 stopped the memory used by the hostname TLS extension from being
7494 - Make our 'torify' script more portable; if we have only one of
7495 'torsocks' or 'tsocks' installed, don't complain to the user;
7496 and explain our warning about tsocks better.
7499 - Add a "getinfo status/accepted-server-descriptor" controller
7500 command, which is the recommended way for controllers to learn
7501 whether our server descriptor has been successfully received by at
7502 least on directory authority. Un-recommend good-server-descriptor
7503 getinfo and status events until we have a better design for them.
7504 - Update to the "September 4 2009" ip-to-country file.
7507 Changes in version 0.2.2.1-alpha - 2009-08-26
7508 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
7509 Tor clients to bootstrap on networks where only port 80 is reachable,
7510 makes it more straightforward to support hardware crypto accelerators,
7511 and starts the groundwork for gathering stats safely at relays.
7514 - Start the process of disabling ".exit" address notation, since it
7515 can be used for a variety of esoteric application-level attacks
7516 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
7519 o New directory authorities:
7520 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
7524 - New AccelName and AccelDir options add support for dynamic OpenSSL
7525 hardware crypto acceleration engines.
7526 - Tor now supports tunneling all of its outgoing connections over
7527 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
7528 configuration options. Code by Christopher Davis.
7531 - Send circuit or stream sendme cells when our window has decreased
7532 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
7533 by Karsten when testing the "reduce circuit window" performance
7534 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7535 before the release of Tor 0.0.0. This is the new winner of the
7538 o New options for gathering stats safely:
7539 - Directory mirrors that set "DirReqStatistics 1" write statistics
7540 about directory requests to disk every 24 hours. As compared to the
7541 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
7542 1) stats are written to disk exactly every 24 hours; 2) estimated
7543 shares of v2 and v3 requests are determined as mean values, not at
7544 the end of a measurement period; 3) unresolved requests are listed
7545 with country code '??'; 4) directories also measure download times.
7546 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
7547 number of exit streams and transferred bytes per port to disk every
7549 - Relays that set "CellStatistics 1" write statistics on how long
7550 cells spend in their circuit queues to disk every 24 hours.
7551 - Entry nodes that set "EntryStatistics 1" write statistics on the
7552 rough number and origins of connecting clients to disk every 24
7554 - Relays that write any of the above statistics to disk and set
7555 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
7556 their extra-info documents.
7559 - New --digests command-line switch to output the digests of the
7560 source files Tor was built with.
7561 - The "torify" script now uses torsocks where available.
7562 - The memarea code now uses a sentinel value at the end of each area
7563 to make sure nothing writes beyond the end of an area. This might
7564 help debug some conceivable causes of bug 930.
7565 - Time and memory units in the configuration file can now be set to
7566 fractional units. For example, "2.5 GB" is now a valid value for
7568 - Certain Tor clients (such as those behind check.torproject.org) may
7569 want to fetch the consensus in an extra early manner. To enable this
7570 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
7571 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
7572 as only certain clients who must have this information sooner should
7574 - Instead of adding the svn revision to the Tor version string, report
7575 the git commit (when we're building from a git checkout).
7578 - If any of the v3 certs we download are unparseable, we should
7579 actually notice the failure so we don't retry indefinitely. Bugfix
7580 on 0.2.0.x; reported by "rotator".
7581 - If the cached cert file is unparseable, warn but don't exit.
7582 - Fix possible segmentation fault on directory authorities. Bugfix on
7584 - When Tor fails to parse a descriptor of any kind, dump it to disk.
7585 Might help diagnosing bug 1051.
7587 o Deprecated and removed features:
7588 - The controller no longer accepts the old obsolete "addr-mappings/"
7589 or "unregistered-servers-" GETINFO values.
7590 - Hidden services no longer publish version 0 descriptors, and clients
7591 do not request or use version 0 descriptors. However, the old hidden
7592 service authorities still accept and serve version 0 descriptors
7593 when contacted by older hidden services/clients.
7594 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
7595 always on; using them is necessary for correct forward-compatible
7597 - Remove support for .noconnect style addresses. Nobody was using
7598 them, and they provided another avenue for detecting Tor users
7599 via application-level web tricks.
7601 o Packaging changes:
7602 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
7603 installer bundles. See
7604 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
7605 for details of what's new in Vidalia 0.2.3.
7606 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
7607 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
7608 configuration file, rather than the old Privoxy.
7609 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
7610 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
7611 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
7612 better compatibility with OS X 10.6, aka Snow Leopard.
7613 - OS X Vidalia Bundle: The multi-package installer is now replaced
7614 by a simple drag and drop to the /Applications folder. This change
7615 occurred with the upgrade to Vidalia 0.2.3.
7618 Changes in version 0.2.1.19 - 2009-07-28
7619 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
7620 services on Tor 0.2.1.3-alpha through 0.2.1.18.
7623 - Make accessing hidden services on 0.2.1.x work right again.
7624 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
7625 part of patch provided by "optimist".
7628 - When a relay/bridge is writing out its identity key fingerprint to
7629 the "fingerprint" file and to its logs, write it without spaces. Now
7630 it will look like the fingerprints in our bridges documentation,
7631 and confuse fewer users.
7634 - Relays no longer publish a new server descriptor if they change
7635 their MaxAdvertisedBandwidth config option but it doesn't end up
7636 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
7637 fixes bug 1026. Patch from Sebastian.
7638 - Avoid leaking memory every time we get a create cell but we have
7639 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
7640 fixes bug 1034. Reported by BarkerJr.
7643 Changes in version 0.2.1.18 - 2009-07-24
7644 Tor 0.2.1.18 lays the foundations for performance improvements,
7645 adds status events to help users diagnose bootstrap problems, adds
7646 optional authentication/authorization for hidden services, fixes a
7647 variety of potential anonymity problems, and includes a huge pile of
7648 other features and bug fixes.
7651 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
7654 Changes in version 0.2.1.17-rc - 2009-07-07
7655 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
7656 candidate for the 0.2.1.x series. It lays the groundwork for further
7657 client performance improvements, and also fixes a big bug with directory
7658 authorities that were causing them to assign Guard and Stable flags
7661 The Windows bundles also finally include the geoip database that we
7662 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
7663 should actually install Torbutton rather than giving you a cryptic
7664 failure message (oops).
7667 - Clients now use the bandwidth values in the consensus, rather than
7668 the bandwidth values in each relay descriptor. This approach opens
7669 the door to more accurate bandwidth estimates once the directory
7670 authorities start doing active measurements. Implements more of
7674 - When Tor clients restart after 1-5 days, they discard all their
7675 cached descriptors as too old, but they still use the cached
7676 consensus document. This approach is good for robustness, but
7677 bad for performance: since they don't know any bandwidths, they
7678 end up choosing at random rather than weighting their choice by
7679 speed. Fixed by the above feature of putting bandwidths in the
7680 consensus. Bugfix on 0.2.0.x.
7681 - Directory authorities were neglecting to mark relays down in their
7682 internal histories if the relays fall off the routerlist without
7683 ever being found unreachable. So there were relays in the histories
7684 that haven't been seen for eight months, and are listed as being
7685 up for eight months. This wreaked havoc on the "median wfu"
7686 and "median mtbf" calculations, in turn making Guard and Stable
7687 flags very wrong, hurting network performance. Fixes bugs 696 and
7688 969. Bugfix on 0.2.0.6-alpha.
7691 - Serve the DirPortFrontPage page even when we have been approaching
7692 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
7693 - The control port would close the connection before flushing long
7694 replies, such as the network consensus, if a QUIT command was issued
7695 before the reply had completed. Now, the control port flushes all
7696 pending replies before closing the connection. Also fixed a spurious
7697 warning when a QUIT command is issued after a malformed or rejected
7698 AUTHENTICATE command, but before the connection was closed. Patch
7699 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
7700 - When we can't find an intro key for a v2 hidden service descriptor,
7701 fall back to the v0 hidden service descriptor and log a bug message.
7702 Workaround for bug 1024.
7703 - Fix a log message that did not respect the SafeLogging option.
7707 - If we're a relay and we change our IP address, be more verbose
7708 about the reason that made us change. Should help track down
7709 further bugs for relays on dynamic IP addresses.
7712 Changes in version 0.2.0.35 - 2009-06-24
7714 - Avoid crashing in the presence of certain malformed descriptors.
7715 Found by lark, and by automated fuzzing.
7716 - Fix an edge case where a malicious exit relay could convince a
7717 controller that the client's DNS question resolves to an internal IP
7718 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7721 - Finally fix the bug where dynamic-IP relays disappear when their
7722 IP address changes: directory mirrors were mistakenly telling
7723 them their old address if they asked via begin_dir, so they
7724 never got an accurate answer about their new address, so they
7725 just vanished after a day. For belt-and-suspenders, relays that
7726 don't set Address in their config now avoid using begin_dir for
7727 all direct connections. Should fix bugs 827, 883, and 900.
7728 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7729 that would occur on some exit nodes when DNS failures and timeouts
7730 occurred in certain patterns. Fix for bug 957.
7733 - When starting with a cache over a few days old, do not leak
7734 memory for the obsolete router descriptors in it. Bugfix on
7735 0.2.0.33; fixes bug 672.
7736 - Hidden service clients didn't use a cached service descriptor that
7737 was older than 15 minutes, but wouldn't fetch a new one either,
7738 because there was already one in the cache. Now, fetch a v2
7739 descriptor unless the same descriptor was added to the cache within
7740 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7743 Changes in version 0.2.1.16-rc - 2009-06-20
7744 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
7745 a bunch of minor bugs.
7748 - Fix an edge case where a malicious exit relay could convince a
7749 controller that the client's DNS question resolves to an internal IP
7750 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7752 o Major performance improvements (on 0.2.0.x):
7753 - Disable and refactor some debugging checks that forced a linear scan
7754 over the whole server-side DNS cache. These accounted for over 50%
7755 of CPU time on a relatively busy exit node's gprof profile. Found
7757 - Disable some debugging checks that appeared in exit node profile
7761 - Update to the "June 3 2009" ip-to-country file.
7762 - Do not have tor-resolve automatically refuse all .onion addresses;
7763 if AutomapHostsOnResolve is set in your torrc, this will work fine.
7765 o Minor bugfixes (on 0.2.0.x):
7766 - Log correct error messages for DNS-related network errors on
7768 - Fix a race condition that could cause crashes or memory corruption
7769 when running as a server with a controller listening for log
7771 - Avoid crashing when we have a policy specified in a DirPolicy or
7772 SocksPolicy or ReachableAddresses option with ports set on it,
7773 and we re-load the policy. May fix bug 996.
7774 - Hidden service clients didn't use a cached service descriptor that
7775 was older than 15 minutes, but wouldn't fetch a new one either,
7776 because there was already one in the cache. Now, fetch a v2
7777 descriptor unless the same descriptor was added to the cache within
7778 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7780 o Minor bugfixes (on 0.2.1.x):
7781 - Don't warn users about low port and hibernation mix when they
7782 provide a *ListenAddress directive to fix that. Bugfix on
7784 - When switching back and forth between bridge mode, do not start
7785 gathering GeoIP data until two hours have passed.
7786 - Do not complain that the user has requested an excluded node as
7787 an exit when the node is not really an exit. This could happen
7788 because the circuit was for testing, or an introduction point.
7792 Changes in version 0.2.1.15-rc - 2009-05-25
7793 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
7794 series. It fixes a major bug on fast exit relays, as well as a variety
7797 o Major bugfixes (on 0.2.0.x):
7798 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7799 that would occur on some exit nodes when DNS failures and timeouts
7800 occurred in certain patterns. Fix for bug 957.
7802 o Minor bugfixes (on 0.2.0.x):
7803 - Actually return -1 in the error case for read_bandwidth_usage().
7804 Harmless bug, since we currently don't care about the return value
7805 anywhere. Bugfix on 0.2.0.9-alpha.
7806 - Provide a more useful log message if bug 977 (related to buffer
7807 freelists) ever reappears, and do not crash right away.
7808 - Fix an assertion failure on 64-bit platforms when we allocated
7809 memory right up to the end of a memarea, then realigned the memory
7810 one step beyond the end. Fixes a possible cause of bug 930.
7811 - Protect the count of open sockets with a mutex, so we can't
7812 corrupt it when two threads are closing or opening sockets at once.
7813 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
7814 - Don't allow a bridge to publish its router descriptor to a
7815 non-bridge directory authority. Fixes part of bug 932.
7816 - When we change to or from being a bridge, reset our counts of
7817 client usage by country. Fixes bug 932.
7818 - Fix a bug that made stream bandwidth get misreported to the
7820 - Stop using malloc_usable_size() to use more area than we had
7821 actually allocated: it was safe, but made valgrind really unhappy.
7822 - Fix a memory leak when v3 directory authorities load their keys
7823 and cert from disk. Bugfix on 0.2.0.1-alpha.
7825 o Minor bugfixes (on 0.2.1.x):
7826 - Fix use of freed memory when deciding to mark a non-addable
7827 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
7830 Changes in version 0.2.1.14-rc - 2009-04-12
7831 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
7832 series. It begins fixing some major performance problems, and also
7833 finally addresses the bug that was causing relays on dynamic IP
7834 addresses to fall out of the directory.
7837 - Clients replace entry guards that were chosen more than a few months
7838 ago. This change should significantly improve client performance,
7839 especially once more people upgrade, since relays that have been
7840 a guard for a long time are currently overloaded.
7842 o Major bugfixes (on 0.2.0):
7843 - Finally fix the bug where dynamic-IP relays disappear when their
7844 IP address changes: directory mirrors were mistakenly telling
7845 them their old address if they asked via begin_dir, so they
7846 never got an accurate answer about their new address, so they
7847 just vanished after a day. For belt-and-suspenders, relays that
7848 don't set Address in their config now avoid using begin_dir for
7849 all direct connections. Should fix bugs 827, 883, and 900.
7850 - Relays were falling out of the networkstatus consensus for
7851 part of a day if they changed their local config but the
7852 authorities discarded their new descriptor as "not sufficiently
7853 different". Now directory authorities accept a descriptor as changed
7854 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
7856 - Avoid crashing in the presence of certain malformed descriptors.
7857 Found by lark, and by automated fuzzing.
7860 - When generating circuit events with verbose nicknames for
7861 controllers, try harder to look up nicknames for routers on a
7862 circuit. (Previously, we would look in the router descriptors we had
7863 for nicknames, but not in the consensus.) Partial fix for bug 941.
7864 - If the bridge config line doesn't specify a port, assume 443.
7865 This makes bridge lines a bit smaller and easier for users to
7867 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
7868 bytes (aka 20KB/s), to match our documentation. Also update
7869 directory authorities so they always assign the Fast flag to relays
7870 with 20KB/s of capacity. Now people running relays won't suddenly
7871 find themselves not seeing any use, if the network gets faster
7873 - Update to the "April 3 2009" ip-to-country file.
7876 - Avoid trying to print raw memory to the logs when we decide to
7877 give up on downloading a given relay descriptor. Bugfix on
7879 - In tor-resolve, when the Tor client to use is specified by
7880 <hostname>:<port>, actually use the specified port rather than
7881 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
7882 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
7883 - When starting with a cache over a few days old, do not leak
7884 memory for the obsolete router descriptors in it. Bugfix on
7886 - Avoid double-free on list of successfully uploaded hidden
7887 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
7888 - Change memarea_strndup() implementation to work even when
7889 duplicating a string at the end of a page. This bug was
7890 harmless for now, but could have meant crashes later. Fix by
7891 lark. Bugfix on 0.2.1.1-alpha.
7892 - Limit uploaded directory documents to be 16M rather than 500K.
7893 The directory authorities were refusing v3 consensus votes from
7894 other authorities, since the votes are now 504K. Fixes bug 959;
7895 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
7896 - Directory authorities should never send a 503 "busy" response to
7897 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
7901 Changes in version 0.2.1.13-alpha - 2009-03-09
7902 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
7903 cleanups. We're finally getting close to a release candidate.
7906 - Correctly update the list of which countries we exclude as
7907 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
7908 lark. Bugfix on 0.2.1.6-alpha.
7910 o Minor bugfixes (on 0.2.0.x and earlier):
7911 - Automatically detect MacOSX versions earlier than 10.4.0, and
7912 disable kqueue from inside Tor when running with these versions.
7913 We previously did this from the startup script, but that was no
7914 help to people who didn't use the startup script. Resolves bug 863.
7915 - When we had picked an exit node for a connection, but marked it as
7916 "optional", and it turned out we had no onion key for the exit,
7917 stop wanting that exit and try again. This situation may not
7918 be possible now, but will probably become feasible with proposal
7919 158. Spotted by rovv. Fixes another case of bug 752.
7920 - Clients no longer cache certificates for authorities they do not
7921 recognize. Bugfix on 0.2.0.9-alpha.
7922 - When we can't transmit a DNS request due to a network error, retry
7923 it after a while, and eventually transmit a failing response to
7924 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
7925 - If the controller claimed responsibility for a stream, but that
7926 stream never finished making its connection, it would live
7927 forever in circuit_wait state. Now we close it after SocksTimeout
7928 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
7929 - Drop begin cells to a hidden service if they come from the middle
7930 of a circuit. Patch from lark.
7931 - When we erroneously receive two EXTEND cells for the same circuit
7932 ID on the same connection, drop the second. Patch from lark.
7933 - Fix a crash that occurs on exit nodes when a nameserver request
7934 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
7935 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
7937 - Do not assume that a stack-allocated character array will be
7938 64-bit aligned on platforms that demand that uint64_t access is
7939 aligned. Possible fix for bug 604.
7940 - Parse dates and IPv4 addresses in a locale- and libc-independent
7941 manner, to avoid platform-dependent behavior on malformed input.
7942 - Build correctly when configured to build outside the main source
7943 path. Patch from Michael Gold.
7944 - We were already rejecting relay begin cells with destination port
7945 of 0. Now also reject extend cells with destination port or address
7946 of 0. Suggested by lark.
7948 o Minor bugfixes (on 0.2.1.x):
7949 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
7950 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
7951 - If we're an exit node, scrub the IP address to which we are exiting
7952 in the logs. Bugfix on 0.2.1.8-alpha.
7955 - On Linux, use the prctl call to re-enable core dumps when the user
7957 - New controller event NEWCONSENSUS that lists the networkstatus
7958 lines for every recommended relay. Now controllers like Torflow
7959 can keep up-to-date on which relays they should be using.
7960 - Update to the "February 26 2009" ip-to-country file.
7963 Changes in version 0.2.0.34 - 2009-02-08
7964 Tor 0.2.0.34 features several more security-related fixes. You should
7965 upgrade, especially if you run an exit relay (remote crash) or a
7966 directory authority (remote infinite loop), or you're on an older
7967 (pre-XP) or not-recently-patched Windows (remote exploit).
7969 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
7970 have many known flaws, and nobody should be using them. You should
7971 upgrade. If you're using a Linux or BSD and its packages are obsolete,
7972 stop using those packages and upgrade anyway.
7975 - Fix an infinite-loop bug on handling corrupt votes under certain
7976 circumstances. Bugfix on 0.2.0.8-alpha.
7977 - Fix a temporary DoS vulnerability that could be performed by
7978 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7979 - Avoid a potential crash on exit nodes when processing malformed
7980 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
7981 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
7982 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
7985 - Fix compilation on systems where time_t is a 64-bit integer.
7986 Patch from Matthias Drochner.
7987 - Don't consider expiring already-closed client connections. Fixes
7988 bug 893. Bugfix on 0.0.2pre20.
7991 Changes in version 0.2.1.12-alpha - 2009-02-08
7992 Tor 0.2.1.12-alpha features several more security-related fixes. You
7993 should upgrade, especially if you run an exit relay (remote crash) or
7994 a directory authority (remote infinite loop), or you're on an older
7995 (pre-XP) or not-recently-patched Windows (remote exploit). It also
7996 includes a big pile of minor bugfixes and cleanups.
7999 - Fix an infinite-loop bug on handling corrupt votes under certain
8000 circumstances. Bugfix on 0.2.0.8-alpha.
8001 - Fix a temporary DoS vulnerability that could be performed by
8002 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
8003 - Avoid a potential crash on exit nodes when processing malformed
8004 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
8007 - Let controllers actually ask for the "clients_seen" event for
8008 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
8009 reported by Matt Edman.
8010 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
8012 - Fix a bug in address parsing that was preventing bridges or hidden
8013 service targets from being at IPv6 addresses.
8014 - Solve a bug that kept hardware crypto acceleration from getting
8015 enabled when accounting was turned on. Fixes bug 907. Bugfix on
8017 - Remove a bash-ism from configure.in to build properly on non-Linux
8018 platforms. Bugfix on 0.2.1.1-alpha.
8019 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
8020 headers. Bugfix on 0.2.0.10-alpha.
8021 - Don't consider expiring already-closed client connections. Fixes
8022 bug 893. Bugfix on 0.0.2pre20.
8023 - Fix another interesting corner-case of bug 891 spotted by rovv:
8024 Previously, if two hosts had different amounts of clock drift, and
8025 one of them created a new connection with just the wrong timing,
8026 the other might decide to deprecate the new connection erroneously.
8027 Bugfix on 0.1.1.13-alpha.
8028 - Resolve a very rare crash bug that could occur when the user forced
8029 a nameserver reconfiguration during the middle of a nameserver
8030 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
8031 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
8032 Bugfix on 0.2.1.7-alpha.
8033 - If we're using bridges and our network goes away, be more willing
8034 to forgive our bridges and try again when we get an application
8035 request. Bugfix on 0.2.0.x.
8038 - Support platforms where time_t is 64 bits long. (Congratulations,
8039 NetBSD!) Patch from Matthias Drochner.
8040 - Add a 'getinfo status/clients-seen' controller command, in case
8041 controllers want to hear clients_seen events but connect late.
8044 - Disable GCC's strict alias optimization by default, to avoid the
8045 likelihood of its introducing subtle bugs whenever our code violates
8046 the letter of C99's alias rules.
8049 Changes in version 0.2.0.33 - 2009-01-21
8050 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
8051 useful to users. It also finally fixes a bug where a relay or client
8052 that's been off for many days would take a long time to bootstrap.
8054 This update also fixes an important security-related bug reported by
8055 Ilja van Sprundel. You should upgrade. (We'll send out more details
8056 about the bug once people have had some time to upgrade.)
8059 - Fix a heap-corruption bug that may be remotely triggerable on
8060 some platforms. Reported by Ilja van Sprundel.
8063 - When a stream at an exit relay is in state "resolving" or
8064 "connecting" and it receives an "end" relay cell, the exit relay
8065 would silently ignore the end cell and not close the stream. If
8066 the client never closes the circuit, then the exit relay never
8067 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
8069 - When sending CREATED cells back for a given circuit, use a 64-bit
8070 connection ID to find the right connection, rather than an addr:port
8071 combination. Now that we can have multiple OR connections between
8072 the same ORs, it is no longer possible to use addr:port to uniquely
8073 identify a connection.
8074 - Bridge relays that had DirPort set to 0 would stop fetching
8075 descriptors shortly after startup, and then briefly resume
8076 after a new bandwidth test and/or after publishing a new bridge
8077 descriptor. Bridge users that try to bootstrap from them would
8078 get a recent networkstatus but would get descriptors from up to
8079 18 hours earlier, meaning most of the descriptors were obsolete
8080 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
8081 - Prevent bridge relays from serving their 'extrainfo' document
8082 to anybody who asks, now that extrainfo docs include potentially
8083 sensitive aggregated client geoip summaries. Bugfix on
8085 - If the cached networkstatus consensus is more than five days old,
8086 discard it rather than trying to use it. In theory it could be
8087 useful because it lists alternate directory mirrors, but in practice
8088 it just means we spend many minutes trying directory mirrors that
8089 are long gone from the network. Also discard router descriptors as
8090 we load them if they are more than five days old, since the onion
8091 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
8094 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
8095 could make gcc generate non-functional binary search code. Bugfix
8097 - Build correctly on platforms without socklen_t.
8098 - Compile without warnings on solaris.
8099 - Avoid potential crash on internal error during signature collection.
8100 Fixes bug 864. Patch from rovv.
8101 - Correct handling of possible malformed authority signing key
8102 certificates with internal signature types. Fixes bug 880.
8103 Bugfix on 0.2.0.3-alpha.
8104 - Fix a hard-to-trigger resource leak when logging credential status.
8106 - When we can't initialize DNS because the network is down, do not
8107 automatically stop Tor from starting. Instead, we retry failed
8108 dns_init() every 10 minutes, and change the exit policy to reject
8109 *:* until one succeeds. Fixes bug 691.
8110 - Use 64 bits instead of 32 bits for connection identifiers used with
8111 the controller protocol, to greatly reduce risk of identifier reuse.
8112 - When we're choosing an exit node for a circuit, and we have
8113 no pending streams, choose a good general exit rather than one that
8114 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
8115 - Fix another case of assuming, when a specific exit is requested,
8116 that we know more than the user about what hosts it allows.
8117 Fixes one case of bug 752. Patch from rovv.
8118 - Clip the MaxCircuitDirtiness config option to a minimum of 10
8119 seconds. Warn the user if lower values are given in the
8120 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
8121 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
8122 user if lower values are given in the configuration. Bugfix on
8123 0.1.1.17-rc. Patch by Sebastian.
8124 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
8125 the cache because we already had a v0 descriptor with the same ID.
8126 Bugfix on 0.2.0.18-alpha.
8127 - Fix a race condition when freeing keys shared between main thread
8128 and CPU workers that could result in a memory leak. Bugfix on
8129 0.1.0.1-rc. Fixes bug 889.
8130 - Send a valid END cell back when a client tries to connect to a
8131 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
8132 840. Patch from rovv.
8133 - Check which hops rendezvous stream cells are associated with to
8134 prevent possible guess-the-streamid injection attacks from
8135 intermediate hops. Fixes another case of bug 446. Based on patch
8137 - If a broken client asks a non-exit router to connect somewhere,
8138 do not even do the DNS lookup before rejecting the connection.
8139 Fixes another case of bug 619. Patch from rovv.
8140 - When a relay gets a create cell it can't decrypt (e.g. because it's
8141 using the wrong onion key), we were dropping it and letting the
8142 client time out. Now actually answer with a destroy cell. Fixes
8143 bug 904. Bugfix on 0.0.2pre8.
8145 o Minor bugfixes (hidden services):
8146 - Do not throw away existing introduction points on SIGHUP. Bugfix on
8147 0.0.6pre1. Patch by Karsten. Fixes bug 874.
8150 - Report the case where all signatures in a detached set are rejected
8151 differently than the case where there is an error handling the
8153 - When we realize that another process has modified our cached
8154 descriptors, print out a more useful error message rather than
8155 triggering an assertion. Fixes bug 885. Patch from Karsten.
8156 - Implement the 0x20 hack to better resist DNS poisoning: set the
8157 case on outgoing DNS requests randomly, and reject responses that do
8158 not match the case correctly. This logic can be disabled with the
8159 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
8160 of servers that do not reliably preserve case in replies. See
8161 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
8163 - Check DNS replies for more matching fields to better resist DNS
8165 - Never use OpenSSL compression: it wastes RAM and CPU trying to
8166 compress cells, which are basically all encrypted, compressed, or
8170 Changes in version 0.2.1.11-alpha - 2009-01-20
8171 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
8172 week it will take a long time to bootstrap again" bug. It also fixes
8173 an important security-related bug reported by Ilja van Sprundel. You
8174 should upgrade. (We'll send out more details about the bug once people
8175 have had some time to upgrade.)
8178 - Fix a heap-corruption bug that may be remotely triggerable on
8179 some platforms. Reported by Ilja van Sprundel.
8182 - Discard router descriptors as we load them if they are more than
8183 five days old. Otherwise if Tor is off for a long time and then
8184 starts with cached descriptors, it will try to use the onion
8185 keys in those obsolete descriptors when building circuits. Bugfix
8186 on 0.2.0.x. Fixes bug 887.
8189 - Try to make sure that the version of Libevent we're running with
8190 is binary-compatible with the one we built with. May address bug
8192 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
8193 for bug 905. Bugfix on 0.2.1.7-alpha.
8194 - Add a new --enable-local-appdata configuration switch to change
8195 the default location of the datadir on win32 from APPDATA to
8196 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
8197 entirely. Patch from coderman.
8200 - Make outbound DNS packets respect the OutboundBindAddress setting.
8201 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
8202 - When our circuit fails at the first hop (e.g. we get a destroy
8203 cell back), avoid using that OR connection anymore, and also
8204 tell all the one-hop directory requests waiting for it that they
8205 should fail. Bugfix on 0.2.1.3-alpha.
8206 - In the torify(1) manpage, mention that tsocks will leak your
8210 Changes in version 0.2.1.10-alpha - 2009-01-06
8211 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
8212 would make the bridge relay not so useful if it had DirPort set to 0,
8213 and one that could let an attacker learn a little bit of information
8214 about the bridge's users), and a bug that would cause your Tor relay
8215 to ignore a circuit create request it can't decrypt (rather than reply
8216 with an error). It also fixes a wide variety of other bugs.
8219 - If the cached networkstatus consensus is more than five days old,
8220 discard it rather than trying to use it. In theory it could
8221 be useful because it lists alternate directory mirrors, but in
8222 practice it just means we spend many minutes trying directory
8223 mirrors that are long gone from the network. Helps bug 887 a bit;
8225 - Bridge relays that had DirPort set to 0 would stop fetching
8226 descriptors shortly after startup, and then briefly resume
8227 after a new bandwidth test and/or after publishing a new bridge
8228 descriptor. Bridge users that try to bootstrap from them would
8229 get a recent networkstatus but would get descriptors from up to
8230 18 hours earlier, meaning most of the descriptors were obsolete
8231 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
8232 - Prevent bridge relays from serving their 'extrainfo' document
8233 to anybody who asks, now that extrainfo docs include potentially
8234 sensitive aggregated client geoip summaries. Bugfix on
8238 - New controller event "clients_seen" to report a geoip-based summary
8239 of which countries we've seen clients from recently. Now controllers
8240 like Vidalia can show bridge operators that they're actually making
8242 - Build correctly against versions of OpenSSL 0.9.8 or later built
8243 without support for deprecated functions.
8244 - Update to the "December 19 2008" ip-to-country file.
8246 o Minor bugfixes (on 0.2.0.x):
8247 - Authorities now vote for the Stable flag for any router whose
8248 weighted MTBF is at least 5 days, regardless of the mean MTBF.
8249 - Do not remove routers as too old if we do not have any consensus
8250 document. Bugfix on 0.2.0.7-alpha.
8251 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
8252 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
8253 - When an exit relay resolves a stream address to a local IP address,
8254 do not just keep retrying that same exit relay over and
8255 over. Instead, just close the stream. Addresses bug 872. Bugfix
8256 on 0.2.0.32. Patch from rovv.
8257 - If a hidden service sends us an END cell, do not consider
8258 retrying the connection; just close it. Patch from rovv.
8259 - When we made bridge authorities stop serving bridge descriptors over
8260 unencrypted links, we also broke DirPort reachability testing for
8261 bridges. So bridges with a non-zero DirPort were printing spurious
8262 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
8263 - When a relay gets a create cell it can't decrypt (e.g. because it's
8264 using the wrong onion key), we were dropping it and letting the
8265 client time out. Now actually answer with a destroy cell. Fixes
8266 bug 904. Bugfix on 0.0.2pre8.
8267 - Squeeze 2-5% out of client performance (according to oprofile) by
8268 improving the implementation of some policy-manipulation functions.
8270 o Minor bugfixes (on 0.2.1.x):
8271 - Make get_interface_address() function work properly again; stop
8272 guessing the wrong parts of our address as our address.
8273 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
8274 send on that circuit. Otherwise we might violate the proposal-110
8275 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
8277 - When we're sending non-EXTEND cells to the first hop in a circuit,
8278 for example to use an encrypted directory connection, we don't need
8279 to use RELAY_EARLY cells: the first hop knows what kind of cell
8280 it is, and nobody else can even see the cell type. Conserving
8281 RELAY_EARLY cells makes it easier to cannibalize circuits like
8283 - Stop logging nameserver addresses in reverse order.
8284 - If we are retrying a directory download slowly over and over, do
8285 not automatically give up after the 254th failure. Bugfix on
8287 - Resume reporting accurate "stream end" reasons to the local control
8288 port. They were lost in the changes for Proposal 148. Bugfix on
8291 o Deprecated and removed features:
8292 - The old "tor --version --version" command, which would print out
8293 the subversion "Id" of most of the source files, is now removed. It
8294 turned out to be less useful than we'd expected, and harder to
8297 o Code simplifications and refactoring:
8298 - Change our header file guard macros to be less likely to conflict
8299 with system headers. Adam Langley noticed that we were conflicting
8300 with log.h on Android.
8301 - Tool-assisted documentation cleanup. Nearly every function or
8302 static variable in Tor should have its own documentation now.
8305 Changes in version 0.2.1.9-alpha - 2008-12-25
8306 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
8308 o New directory authorities:
8309 - gabelmoo (the authority run by Karsten Loesing) now has a new
8313 - Never use a connection with a mismatched address to extend a
8314 circuit, unless that connection is canonical. A canonical
8315 connection is one whose address is authenticated by the router's
8316 identity key, either in a NETINFO cell or in a router descriptor.
8317 - Avoid a possible memory corruption bug when receiving hidden service
8318 descriptors. Bugfix on 0.2.1.6-alpha.
8321 - Fix a logic error that would automatically reject all but the first
8322 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
8323 part of bug 813/868. Bug spotted by coderman.
8324 - When a stream at an exit relay is in state "resolving" or
8325 "connecting" and it receives an "end" relay cell, the exit relay
8326 would silently ignore the end cell and not close the stream. If
8327 the client never closes the circuit, then the exit relay never
8328 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
8330 - When we can't initialize DNS because the network is down, do not
8331 automatically stop Tor from starting. Instead, retry failed
8332 dns_init() every 10 minutes, and change the exit policy to reject
8333 *:* until one succeeds. Fixes bug 691.
8336 - Give a better error message when an overzealous init script says
8337 "sudo -u username tor --user username". Makes Bug 882 easier for
8339 - When a directory authority gives us a new guess for our IP address,
8340 log which authority we used. Hopefully this will help us debug
8341 the recent complaints about bad IP address guesses.
8342 - Detect svn revision properly when we're using git-svn.
8343 - Try not to open more than one descriptor-downloading connection
8344 to an authority at once. This should reduce load on directory
8345 authorities. Fixes bug 366.
8346 - Add cross-certification to newly generated certificates, so that
8347 a signing key is enough information to look up a certificate.
8348 Partial implementation of proposal 157.
8349 - Start serving certificates by <identity digest, signing key digest>
8350 pairs. Partial implementation of proposal 157.
8351 - Clients now never report any stream end reason except 'MISC'.
8352 Implements proposal 148.
8353 - On platforms with a maximum syslog string length, truncate syslog
8354 messages to that length ourselves, rather than relying on the
8355 system to do it for us.
8356 - Optimize out calls to time(NULL) that occur for every IO operation,
8357 or for every cell. On systems where time() is a slow syscall,
8358 this fix will be slightly helpful.
8359 - Exit servers can now answer resolve requests for ip6.arpa addresses.
8360 - When we download a descriptor that we then immediately (as
8361 a directory authority) reject, do not retry downloading it right
8362 away. Should save some bandwidth on authorities. Fix for bug
8363 888. Patch by Sebastian Hahn.
8364 - When a download gets us zero good descriptors, do not notify
8365 Tor that new directory information has arrived.
8366 - Avoid some nasty corner cases in the logic for marking connections
8367 as too old or obsolete or noncanonical for circuits. Partial
8370 o Minor features (controller):
8371 - New CONSENSUS_ARRIVED event to note when a new consensus has
8372 been fetched and validated.
8373 - When we realize that another process has modified our cached
8374 descriptors file, print out a more useful error message rather
8375 than triggering an assertion. Fixes bug 885. Patch from Karsten.
8376 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
8377 controllers to prevent SIGHUP from reloading the
8378 configuration. Fixes bug 856.
8381 - Resume using the correct "REASON=" stream when telling the
8382 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
8383 - When a canonical connection appears later in our internal list
8384 than a noncanonical one for a given OR ID, always use the
8385 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
8387 - Clip the MaxCircuitDirtiness config option to a minimum of 10
8388 seconds. Warn the user if lower values are given in the
8389 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
8390 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
8391 user if lower values are given in the configuration. Bugfix on
8392 0.1.1.17-rc. Patch by Sebastian.
8393 - Fix a race condition when freeing keys shared between main thread
8394 and CPU workers that could result in a memory leak. Bugfix on
8395 0.1.0.1-rc. Fixes bug 889.
8397 o Minor bugfixes (hidden services):
8398 - Do not throw away existing introduction points on SIGHUP (bugfix on
8399 0.0.6pre1); also, do not stall hidden services because we're
8400 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
8401 by John Brooks. Patch by Karsten. Fixes bug 874.
8402 - Fix a memory leak when we decline to add a v2 rendezvous
8403 descriptor to the cache because we already had a v0 descriptor
8404 with the same ID. Bugfix on 0.2.0.18-alpha.
8406 o Deprecated and removed features:
8407 - RedirectExits has been removed. It was deprecated since
8409 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
8410 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
8411 - Cell pools are now always enabled; --disable-cell-pools is ignored.
8413 o Code simplifications and refactoring:
8414 - Rename the confusing or_is_obsolete field to the more appropriate
8415 is_bad_for_new_circs, and move it to or_connection_t where it
8417 - Move edge-only flags from connection_t to edge_connection_t: not
8418 only is this better coding, but on machines of plausible alignment,
8419 it should save 4-8 bytes per connection_t. "Every little bit helps."
8420 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
8421 for consistency; keep old option working for backward compatibility.
8422 - Simplify the code for finding connections to use for a circuit.
8425 Changes in version 0.2.1.8-alpha - 2008-12-08
8426 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
8427 builds better on unusual platforms like Solaris and old OS X, and
8428 fixes a variety of other issues.
8431 - New DirPortFrontPage option that takes an html file and publishes
8432 it as "/" on the DirPort. Now relay operators can provide a
8433 disclaimer without needing to set up a separate webserver. There's
8434 a sample disclaimer in contrib/tor-exit-notice.html.
8437 - When the client is choosing entry guards, now it selects at most
8438 one guard from a given relay family. Otherwise we could end up with
8439 all of our entry points into the network run by the same operator.
8440 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
8443 - Fix a DOS opportunity during the voting signature collection process
8444 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8445 - Fix a possible segfault when establishing an exit connection. Bugfix
8449 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
8451 - Made Tor a little less aggressive about deleting expired
8452 certificates. Partial fix for bug 854.
8453 - Stop doing unaligned memory access that generated bus errors on
8454 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
8455 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
8456 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
8457 - Make USR2 log-level switch take effect immediately. Bugfix on
8459 - If one win32 nameserver fails to get added, continue adding the
8460 rest, and don't automatically fail.
8461 - Use fcntl() for locking when flock() is not available. Should fix
8462 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
8463 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
8464 could make gcc generate non-functional binary search code. Bugfix
8466 - Build correctly on platforms without socklen_t.
8467 - Avoid potential crash on internal error during signature collection.
8468 Fixes bug 864. Patch from rovv.
8469 - Do not use C's stdio library for writing to log files. This will
8470 improve logging performance by a minute amount, and will stop
8471 leaking fds when our disk is full. Fixes bug 861.
8472 - Stop erroneous use of O_APPEND in cases where we did not in fact
8473 want to re-seek to the end of a file before every last write().
8474 - Correct handling of possible malformed authority signing key
8475 certificates with internal signature types. Fixes bug 880. Bugfix
8477 - Fix a hard-to-trigger resource leak when logging credential status.
8481 - Directory mirrors no longer fetch the v1 directory or
8482 running-routers files. They are obsolete, and nobody asks for them
8483 anymore. This is the first step to making v1 authorities obsolete.
8485 o Minor features (controller):
8486 - Return circuit purposes in response to GETINFO circuit-status. Fixes
8490 Changes in version 0.2.0.32 - 2008-11-20
8491 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
8492 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8493 a smaller security flaw that might allow an attacker to access local
8494 services, further improves hidden service performance, and fixes a
8495 variety of other issues.
8498 - The "User" and "Group" config options did not clear the
8499 supplementary group entries for the Tor process. The "User" option
8500 is now more robust, and we now set the groups to the specified
8501 user's primary group. The "Group" option is now ignored. For more
8502 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8503 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8504 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
8505 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8506 consistently obeyed: if an exit relay refuses a stream because its
8507 exit policy doesn't allow it, we would remember what IP address
8508 the relay said the destination address resolves to, even if it's
8509 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8512 - Fix a DOS opportunity during the voting signature collection process
8513 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8515 o Major bugfixes (hidden services):
8516 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8517 we were failing the whole hidden service request when the v0
8518 descriptor fetch fails, even if the v2 fetch is still pending and
8519 might succeed. Similarly, if the last v2 fetch fails, we were
8520 failing the whole hidden service request even if a v0 fetch is
8521 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8522 - When extending a circuit to a hidden service directory to upload a
8523 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8524 requests failed, because the router descriptor has not been
8525 downloaded yet. In these cases, do not attempt to upload the
8526 rendezvous descriptor, but wait until the router descriptor is
8527 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
8528 descriptor from a hidden service directory for which the router
8529 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
8533 - Fix several infrequent memory leaks spotted by Coverity.
8534 - When testing for libevent functions, set the LDFLAGS variable
8535 correctly. Found by Riastradh.
8536 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8537 bootstrapping with tunneled directory connections. Bugfix on
8538 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8539 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8540 and we know that server B rejects most-but-not all connections to
8541 port 80, we would previously reject the connection. Now, we assume
8542 the user knows what they were asking for. Fixes bug 752. Bugfix
8543 on 0.0.9rc5. Diagnosed by BarkerJr.
8544 - If we overrun our per-second write limits a little, count this as
8545 having used up our write allocation for the second, and choke
8546 outgoing directory writes. Previously, we had only counted this when
8547 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
8548 Bugfix on 0.2.0.x (??).
8549 - Remove the old v2 directory authority 'lefkada' from the default
8550 list. It has been gone for many months.
8551 - Stop doing unaligned memory access that generated bus errors on
8552 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
8553 - Make USR2 log-level switch take effect immediately. Bugfix on
8556 o Minor bugfixes (controller):
8557 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
8558 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
8561 Changes in version 0.2.1.7-alpha - 2008-11-08
8562 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
8563 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8564 a smaller security flaw that might allow an attacker to access local
8565 services, adds better defense against DNS poisoning attacks on exit
8566 relays, further improves hidden service performance, and fixes a
8567 variety of other issues.
8570 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8571 consistently obeyed: if an exit relay refuses a stream because its
8572 exit policy doesn't allow it, we would remember what IP address
8573 the relay said the destination address resolves to, even if it's
8574 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8575 - The "User" and "Group" config options did not clear the
8576 supplementary group entries for the Tor process. The "User" option
8577 is now more robust, and we now set the groups to the specified
8578 user's primary group. The "Group" option is now ignored. For more
8579 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8580 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8581 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
8582 - Do not use or believe expired v3 authority certificates. Patch
8583 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
8586 - Now NodeFamily and MyFamily config options allow spaces in
8587 identity fingerprints, so it's easier to paste them in.
8588 Suggested by Lucky Green.
8589 - Implement the 0x20 hack to better resist DNS poisoning: set the
8590 case on outgoing DNS requests randomly, and reject responses that do
8591 not match the case correctly. This logic can be disabled with the
8592 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
8593 of servers that do not reliably preserve case in replies. See
8594 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
8596 - Preserve case in replies to DNSPort requests in order to support
8597 the 0x20 hack for resisting DNS poisoning attacks.
8599 o Hidden service performance improvements:
8600 - When the client launches an introduction circuit, retry with a
8601 new circuit after 30 seconds rather than 60 seconds.
8602 - Launch a second client-side introduction circuit in parallel
8603 after a delay of 15 seconds (based on work by Christian Wilms).
8604 - Hidden services start out building five intro circuits rather
8605 than three, and when the first three finish they publish a service
8606 descriptor using those. Now we publish our service descriptor much
8607 faster after restart.
8610 - Minor fix in the warning messages when you're having problems
8611 bootstrapping; also, be more forgiving of bootstrap problems when
8612 we're still making incremental progress on a given bootstrap phase.
8613 - When we're choosing an exit node for a circuit, and we have
8614 no pending streams, choose a good general exit rather than one that
8615 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
8616 - Send a valid END cell back when a client tries to connect to a
8617 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
8618 840. Patch from rovv.
8619 - If a broken client asks a non-exit router to connect somewhere,
8620 do not even do the DNS lookup before rejecting the connection.
8621 Fixes another case of bug 619. Patch from rovv.
8622 - Fix another case of assuming, when a specific exit is requested,
8623 that we know more than the user about what hosts it allows.
8624 Fixes another case of bug 752. Patch from rovv.
8625 - Check which hops rendezvous stream cells are associated with to
8626 prevent possible guess-the-streamid injection attacks from
8627 intermediate hops. Fixes another case of bug 446. Based on patch
8629 - Avoid using a negative right-shift when comparing 32-bit
8630 addresses. Possible fix for bug 845 and bug 811.
8631 - Make the assert_circuit_ok() function work correctly on circuits that
8632 have already been marked for close.
8633 - Fix read-off-the-end-of-string error in unit tests when decoding
8634 introduction points.
8635 - Fix uninitialized size field for memory area allocation: may improve
8636 memory performance during directory parsing.
8637 - Treat duplicate certificate fetches as failures, so that we do
8638 not try to re-fetch an expired certificate over and over and over.
8639 - Do not say we're fetching a certificate when we'll in fact skip it
8640 because of a pending download.
8643 Changes in version 0.2.1.6-alpha - 2008-09-30
8644 Tor 0.2.1.6-alpha further improves performance and robustness of
8645 hidden services, starts work on supporting per-country relay selection,
8646 and fixes a variety of smaller issues.
8649 - Implement proposal 121: make it possible to build hidden services
8650 that only certain clients are allowed to connect to. This is
8651 enforced at several points, so that unauthorized clients are unable
8652 to send INTRODUCE cells to the service, or even (depending on the
8653 type of authentication) to learn introduction points. This feature
8654 raises the bar for certain kinds of active attacks against hidden
8655 services. Code by Karsten Loesing.
8656 - Relays now store and serve v2 hidden service descriptors by default,
8657 i.e., the new default value for HidServDirectoryV2 is 1. This is
8658 the last step in proposal 114, which aims to make hidden service
8659 lookups more reliable.
8660 - Start work to allow node restrictions to include country codes. The
8661 syntax to exclude nodes in a country with country code XX is
8662 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
8663 refinement to decide what config options should take priority if
8664 you ask to both use a particular node and exclude it.
8665 - Allow ExitNodes list to include IP ranges and country codes, just
8666 like the Exclude*Nodes lists. Patch from Robert Hogan.
8669 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
8670 Tor to fail to start if you had it configured to use a bridge
8671 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
8672 - When extending a circuit to a hidden service directory to upload a
8673 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8674 requests failed, because the router descriptor had not been
8675 downloaded yet. In these cases, we now wait until the router
8676 descriptor is downloaded, and then retry. Likewise, clients
8677 now skip over a hidden service directory if they don't yet have
8678 its router descriptor, rather than futilely requesting it and
8679 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
8681 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8682 we were failing the whole hidden service request when the v0
8683 descriptor fetch fails, even if the v2 fetch is still pending and
8684 might succeed. Similarly, if the last v2 fetch fails, we were
8685 failing the whole hidden service request even if a v0 fetch is
8686 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8687 - DNS replies need to have names matching their requests, but
8688 these names should be in the questions section, not necessarily
8689 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
8692 - Update to the "September 1 2008" ip-to-country file.
8693 - Allow ports 465 and 587 in the default exit policy again. We had
8694 rejected them in 0.1.0.15, because back in 2005 they were commonly
8695 misconfigured and ended up as spam targets. We hear they are better
8696 locked down these days.
8697 - Use a lockfile to make sure that two Tor processes are not
8698 simultaneously running with the same datadir.
8699 - Serve the latest v3 networkstatus consensus via the control
8700 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
8701 - Better logging about stability/reliability calculations on directory
8703 - Drop the requirement to have an open dir port for storing and
8704 serving v2 hidden service descriptors.
8705 - Directory authorities now serve a /tor/dbg-stability.txt URL to
8706 help debug WFU and MTBF calculations.
8707 - Implement most of Proposal 152: allow specialized servers to permit
8708 single-hop circuits, and clients to use those servers to build
8709 single-hop circuits when using a specialized controller. Patch
8710 from Josh Albrecht. Resolves feature request 768.
8711 - Add a -p option to tor-resolve for specifying the SOCKS port: some
8712 people find host:port too confusing.
8713 - Make TrackHostExit mappings expire a while after their last use, not
8714 after their creation. Patch from Robert Hogan.
8715 - Provide circuit purposes along with circuit events to the controller.
8718 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
8720 - Fixed some memory leaks -- some quite frequent, some almost
8721 impossible to trigger -- based on results from Coverity.
8722 - When testing for libevent functions, set the LDFLAGS variable
8723 correctly. Found by Riastradh.
8724 - Fix an assertion bug in parsing policy-related options; possible fix
8726 - Catch and report a few more bootstrapping failure cases when Tor
8727 fails to establish a TCP connection. Cleanup on 0.2.1.x.
8728 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8729 bootstrapping with tunneled directory connections. Bugfix on
8730 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8731 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8732 and we know that server B rejects most-but-not all connections to
8733 port 80, we would previously reject the connection. Now, we assume
8734 the user knows what they were asking for. Fixes bug 752. Bugfix
8735 on 0.0.9rc5. Diagnosed by BarkerJr.
8736 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
8737 service directories if they have no advertised dir port. Bugfix
8739 - If we overrun our per-second write limits a little, count this as
8740 having used up our write allocation for the second, and choke
8741 outgoing directory writes. Previously, we had only counted this when
8742 we had met our limits precisely. Fixes bug 824. Patch by rovv.
8743 Bugfix on 0.2.0.x (??).
8744 - Avoid a "0 divided by 0" calculation when calculating router uptime
8745 at directory authorities. Bugfix on 0.2.0.8-alpha.
8746 - Make DNS resolved controller events into "CLOSED", not
8747 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
8749 - Fix a bug where an unreachable relay would establish enough
8750 reachability testing circuits to do a bandwidth test -- if
8751 we already have a connection to the middle hop of the testing
8752 circuit, then it could establish the last hop by using the existing
8753 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
8754 circuits no longer use entry guards in 0.2.1.3-alpha.
8755 - If we have correct permissions on $datadir, we complain to stdout
8756 and fail to start. But dangerous permissions on
8757 $datadir/cached-status/ would cause us to open a log and complain
8758 there. Now complain to stdout and fail to start in both cases. Fixes
8759 bug 820, reported by seeess.
8760 - Remove the old v2 directory authority 'lefkada' from the default
8761 list. It has been gone for many months.
8763 o Code simplifications and refactoring:
8764 - Revise the connection_new functions so that a more typesafe variant
8765 exists. This will work better with Coverity, and let us find any
8766 actual mistakes we're making here.
8767 - Refactor unit testing logic so that dmalloc can be used sensibly
8768 with unit tests to check for memory leaks.
8769 - Move all hidden-service related fields from connection and circuit
8770 structure to substructures: this way they won't eat so much memory.
8773 Changes in version 0.2.0.31 - 2008-09-03
8774 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
8775 a big bug we're seeing where in rare cases traffic from one Tor stream
8776 gets mixed into another stream, and fixes a variety of smaller issues.
8779 - Make sure that two circuits can never exist on the same connection
8780 with the same circuit ID, even if one is marked for close. This
8781 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
8782 - Relays now reject risky extend cells: if the extend cell includes
8783 a digest of all zeroes, or asks to extend back to the relay that
8784 sent the extend cell, tear down the circuit. Ideas suggested
8786 - If not enough of our entry guards are available so we add a new
8787 one, we might use the new one even if it overlapped with the
8788 current circuit's exit relay (or its family). Anonymity bugfix
8789 pointed out by rovv.
8792 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8793 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8794 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8795 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8796 - Pick size of default geoip filename string correctly on windows.
8797 Fixes bug 806. Bugfix on 0.2.0.30.
8798 - Make the autoconf script accept the obsolete --with-ssl-dir
8799 option as an alias for the actually-working --with-openssl-dir
8800 option. Fix the help documentation to recommend --with-openssl-dir.
8801 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8802 - When using the TransPort option on OpenBSD, and using the User
8803 option to change UID and drop privileges, make sure to open
8804 /dev/pf before dropping privileges. Fixes bug 782. Patch from
8805 Christopher Davis. Bugfix on 0.1.2.1-alpha.
8806 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8807 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8808 on the client side when connecting to a hidden service. Bugfix
8809 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8810 - When closing an application-side connection because its circuit is
8811 getting torn down, generate the stream event correctly. Bugfix on
8812 0.1.2.x. Anonymous patch.
8815 Changes in version 0.2.1.5-alpha - 2008-08-31
8816 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
8817 in a lot of the infrastructure for adding authorization to hidden
8818 services, lays the groundwork for having clients read their load
8819 balancing information out of the networkstatus consensus rather than
8820 the individual router descriptors, addresses two potential anonymity
8821 issues, and fixes a variety of smaller issues.
8824 - Convert many internal address representations to optionally hold
8826 - Generate and accept IPv6 addresses in many protocol elements.
8827 - Make resolver code handle nameservers located at ipv6 addresses.
8828 - Begin implementation of proposal 121 ("Client authorization for
8829 hidden services"): configure hidden services with client
8830 authorization, publish descriptors for them, and configure
8831 authorization data for hidden services at clients. The next
8832 step is to actually access hidden services that perform client
8834 - More progress toward proposal 141: Network status consensus
8835 documents and votes now contain bandwidth information for each
8836 router and a summary of that router's exit policy. Eventually this
8837 will be used by clients so that they do not have to download every
8838 known descriptor before building circuits.
8840 o Major bugfixes (on 0.2.0.x and before):
8841 - When sending CREATED cells back for a given circuit, use a 64-bit
8842 connection ID to find the right connection, rather than an addr:port
8843 combination. Now that we can have multiple OR connections between
8844 the same ORs, it is no longer possible to use addr:port to uniquely
8845 identify a connection.
8846 - Relays now reject risky extend cells: if the extend cell includes
8847 a digest of all zeroes, or asks to extend back to the relay that
8848 sent the extend cell, tear down the circuit. Ideas suggested
8850 - If not enough of our entry guards are available so we add a new
8851 one, we might use the new one even if it overlapped with the
8852 current circuit's exit relay (or its family). Anonymity bugfix
8853 pointed out by rovv.
8856 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8857 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8858 - When using the TransPort option on OpenBSD, and using the User
8859 option to change UID and drop privileges, make sure to open /dev/pf
8860 before dropping privileges. Fixes bug 782. Patch from Christopher
8861 Davis. Bugfix on 0.1.2.1-alpha.
8862 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8863 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8864 - Add a missing safe_str() call for a debug log message.
8865 - Use 64 bits instead of 32 bits for connection identifiers used with
8866 the controller protocol, to greatly reduce risk of identifier reuse.
8867 - Make the autoconf script accept the obsolete --with-ssl-dir
8868 option as an alias for the actually-working --with-openssl-dir
8869 option. Fix the help documentation to recommend --with-openssl-dir.
8870 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8873 - Rate-limit too-many-sockets messages: when they happen, they happen
8874 a lot. Resolves bug 748.
8875 - Resist DNS poisoning a little better by making sure that names in
8876 answer sections match.
8877 - Print the SOCKS5 error message string as well as the error code
8878 when a tor-resolve request fails. Patch from Jacob.
8881 Changes in version 0.2.1.4-alpha - 2008-08-04
8882 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
8885 - The address part of exit policies was not correctly written
8886 to router descriptors. This generated router descriptors that failed
8887 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
8889 - Tor triggered a false assert when extending a circuit to a relay
8890 but we already have a connection open to that relay. Noticed by
8891 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
8894 - Fix a hidden service logging bug: in some edge cases, the router
8895 descriptor of a previously picked introduction point becomes
8896 obsolete and we need to give up on it rather than continually
8897 complaining that it has become obsolete. Observed by xiando. Bugfix
8901 - Take out the TestVia config option, since it was a workaround for
8902 a bug that was fixed in Tor 0.1.1.21.
8905 Changes in version 0.2.1.3-alpha - 2008-08-03
8906 Tor 0.2.1.3-alpha implements most of the pieces to prevent
8907 infinite-length circuit attacks (see proposal 110); fixes a bug that
8908 might cause exit relays to corrupt streams they send back; allows
8909 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
8910 ExcludeExitNodes config options; and fixes a big pile of bugs.
8912 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
8913 - Send a bootstrap problem "warn" event on the first problem if the
8914 reason is NO_ROUTE (that is, our network is down).
8917 - Implement most of proposal 110: The first K cells to be sent
8918 along a circuit are marked as special "early" cells; only K "early"
8919 cells will be allowed. Once this code is universal, we can block
8920 certain kinds of DOS attack by requiring that EXTEND commands must
8921 be sent using an "early" cell.
8924 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8925 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8926 on the client side when connecting to a hidden service. Bugfix
8927 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8928 - Ensure that two circuits can never exist on the same connection
8929 with the same circuit ID, even if one is marked for close. This
8930 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
8933 - When relays do their initial bandwidth measurement, don't limit
8934 to just our entry guards for the test circuits. Otherwise we tend
8935 to have multiple test circuits going through a single entry guard,
8936 which makes our bandwidth test less accurate. Fixes part of bug 654;
8937 patch contributed by Josh Albrecht.
8938 - Add an ExcludeExitNodes option so users can list a set of nodes
8939 that should be be excluded from the exit node position, but
8940 allowed elsewhere. Implements proposal 151.
8941 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
8942 ExcludeNodes and ExcludeExitNodes lists.
8943 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
8944 be more efficient. Formerly it was quadratic in the number of
8945 servers; now it should be linear. Fixes bug 509.
8946 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
8947 and n_conn_id_digest fields into a separate structure that's
8948 only needed when the circuit has not yet attached to an n_conn.
8951 - Change the contrib/tor.logrotate script so it makes the new
8952 logs as "_tor:_tor" rather than the default, which is generally
8953 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
8954 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8955 warnings (occasionally), but it can also cause the compiler to
8956 eliminate error-checking code. Suggested by Peter Gutmann.
8957 - When a hidden service is giving up on an introduction point candidate
8958 that was not included in the last published rendezvous descriptor,
8959 don't reschedule publication of the next descriptor. Fixes bug 763.
8961 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
8962 HiddenServiceExcludeNodes as obsolete: they never worked properly,
8963 and nobody claims to be using them. Fixes bug 754. Bugfix on
8964 0.1.0.1-rc. Patch from Christian Wilms.
8965 - Fix a small alignment and memory-wasting bug on buffer chunks.
8968 o Minor bugfixes (controller):
8969 - When closing an application-side connection because its circuit
8970 is getting torn down, generate the stream event correctly.
8971 Bugfix on 0.1.2.x. Anonymous patch.
8974 - Remove all backward-compatibility code to support relays running
8975 versions of Tor so old that they no longer work at all on the
8979 Changes in version 0.2.0.30 - 2008-07-15
8981 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8982 warnings (occasionally), but it can also cause the compiler to
8983 eliminate error-checking code. Suggested by Peter Gutmann.
8986 Changes in version 0.2.0.29-rc - 2008-07-08
8987 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
8988 hidden-service performance bugs, and fixes a bunch of smaller bugs.
8991 - If you have more than one bridge but don't know their keys,
8992 you would only launch a request for the descriptor of the first one
8993 on your list. (Tor considered launching requests for the others, but
8994 found that it already had a connection on the way for $0000...0000
8995 so it didn't open another.) Bugfix on 0.2.0.x.
8996 - If you have more than one bridge but don't know their keys, and the
8997 connection to one of the bridges failed, you would cancel all
8998 pending bridge connections. (After all, they all have the same
8999 digest.) Bugfix on 0.2.0.x.
9000 - When a hidden service was trying to establish an introduction point,
9001 and Tor had built circuits preemptively for such purposes, we
9002 were ignoring all the preemptive circuits and launching a new one
9003 instead. Bugfix on 0.2.0.14-alpha.
9004 - When a hidden service was trying to establish an introduction point,
9005 and Tor *did* manage to reuse one of the preemptively built
9006 circuits, it didn't correctly remember which one it used,
9007 so it asked for another one soon after, until there were no
9008 more preemptive circuits, at which point it launched one from
9009 scratch. Bugfix on 0.0.9.x.
9010 - Make directory servers include the X-Your-Address-Is: http header in
9011 their responses even for begin_dir conns. Now clients who only
9012 ever use begin_dir connections still have a way to learn their IP
9013 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
9016 - Fix a macro/CPP interaction that was confusing some compilers:
9017 some GCCs don't like #if/#endif pairs inside macro arguments.
9019 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
9020 Fixes bug 704; fix from Steven Murdoch.
9021 - When opening /dev/null in finish_daemonize(), do not pass the
9022 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
9023 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
9024 - Correctly detect transparent proxy support on Linux hosts that
9025 require in.h to be included before netfilter_ipv4.h. Patch
9027 - Disallow session resumption attempts during the renegotiation
9028 stage of the v2 handshake protocol. Clients should never be trying
9029 session resumption at this point, but apparently some did, in
9030 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
9031 found by Geoff Goodell.
9034 Changes in version 0.2.1.2-alpha - 2008-06-20
9035 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
9036 make it easier to set up your own private Tor network; fixes several
9037 big bugs with using more than one bridge relay; fixes a big bug with
9038 offering hidden services quickly after Tor starts; and uses a better
9039 API for reporting potential bootstrapping problems to the controller.
9042 - New TestingTorNetwork config option to allow adjustment of
9043 previously constant values that, while reasonable, could slow
9044 bootstrapping. Implements proposal 135. Patch from Karsten.
9047 - If you have more than one bridge but don't know their digests,
9048 you would only learn a request for the descriptor of the first one
9049 on your list. (Tor considered launching requests for the others, but
9050 found that it already had a connection on the way for $0000...0000
9051 so it didn't open another.) Bugfix on 0.2.0.x.
9052 - If you have more than one bridge but don't know their digests,
9053 and the connection to one of the bridges failed, you would cancel
9054 all pending bridge connections. (After all, they all have the
9055 same digest.) Bugfix on 0.2.0.x.
9056 - When establishing a hidden service, introduction points that
9057 originate from cannibalized circuits are completely ignored and not
9058 included in rendezvous service descriptors. This might be another
9059 reason for delay in making a hidden service available. Bugfix
9060 from long ago (0.0.9.x?)
9063 - Allow OpenSSL to use dynamic locks if it wants.
9064 - When building a consensus, do not include routers that are down.
9065 This will cut down 30% to 40% on consensus size. Implements
9067 - In directory authorities' approved-routers files, allow
9068 fingerprints with or without space.
9069 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
9070 controller can query our current bootstrap state in case it attaches
9071 partway through and wants to catch up.
9072 - Send an initial "Starting" bootstrap status event, so we have a
9073 state to start out in.
9076 - Asking for a conditional consensus at .../consensus/<fingerprints>
9077 would crash a dirserver if it did not already have a
9078 consensus. Bugfix on 0.2.1.1-alpha.
9079 - Clean up some macro/CPP interactions: some GCC versions don't like
9080 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
9083 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
9084 - Directory authorities shouldn't complain about bootstrapping
9085 problems just because they do a lot of reachability testing and
9086 some of the connection attempts fail.
9087 - Start sending "count" and "recommendation" key/value pairs in
9088 bootstrap problem status events, so the controller can hear about
9089 problems even before Tor decides they're worth reporting for sure.
9090 - If you're using bridges, generate "bootstrap problem" warnings
9091 as soon as you run out of working bridges, rather than waiting
9092 for ten failures -- which will never happen if you have less than
9094 - If we close our OR connection because there's been a circuit
9095 pending on it for too long, we were telling our bootstrap status
9096 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
9099 Changes in version 0.2.1.1-alpha - 2008-06-13
9100 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
9101 were making the Tor process bloat especially on Linux; makes our TLS
9102 handshake blend in better; sends "bootstrap phase" status events to
9103 the controller, so it can keep the user informed of progress (and
9104 problems) fetching directory information and establishing circuits;
9105 and adds a variety of smaller features.
9108 - More work on making our TLS handshake blend in: modify the list
9109 of ciphers advertised by OpenSSL in client mode to even more
9110 closely resemble a common web browser. We cheat a little so that
9111 we can advertise ciphers that the locally installed OpenSSL doesn't
9113 - Start sending "bootstrap phase" status events to the controller,
9114 so it can keep the user informed of progress fetching directory
9115 information and establishing circuits. Also inform the controller
9116 if we think we're stuck at a particular bootstrap phase. Implements
9118 - Resume using OpenSSL's RAND_poll() for better (and more portable)
9119 cross-platform entropy collection again. We used to use it, then
9120 stopped using it because of a bug that could crash systems that
9121 called RAND_poll when they had a lot of fds open. It looks like the
9122 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
9123 at startup, and to call RAND_poll() when we reseed later only if
9124 we have a non-buggy OpenSSL version.
9127 - When we choose to abandon a new entry guard because we think our
9128 older ones might be better, close any circuits pending on that
9129 new entry guard connection. This fix should make us recover much
9130 faster when our network is down and then comes back. Bugfix on
9131 0.1.2.8-beta; found by lodger.
9133 o Memory fixes and improvements:
9134 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
9135 to avoid unused RAM in buffer chunks and memory pools.
9136 - Speed up parsing and cut down on memory fragmentation by using
9137 stack-style allocations for parsing directory objects. Previously,
9138 this accounted for over 40% of allocations from within Tor's code
9139 on a typical directory cache.
9140 - Use a Bloom filter rather than a digest-based set to track which
9141 descriptors we need to keep around when we're cleaning out old
9142 router descriptors. This speeds up the computation significantly,
9143 and may reduce fragmentation.
9144 - Reduce the default smartlist size from 32 to 16; it turns out that
9145 most smartlists hold around 8-12 elements tops.
9146 - Make dumpstats() log the fullness and size of openssl-internal
9148 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
9149 patch to their OpenSSL, turn it on to save memory on servers. This
9150 patch will (with any luck) get included in a mainline distribution
9152 - Never use OpenSSL compression: it wastes RAM and CPU trying to
9153 compress cells, which are basically all encrypted, compressed,
9157 - Stop reloading the router list from disk for no reason when we
9158 run out of reachable directory mirrors. Once upon a time reloading
9159 it would set the 'is_running' flag back to 1 for them. It hasn't
9160 done that for a long time.
9161 - In very rare situations new hidden service descriptors were
9162 published earlier than 30 seconds after the last change to the
9163 service. (We currently think that a hidden service descriptor
9164 that's been stable for 30 seconds is worth publishing.)
9167 - Allow separate log levels to be configured for different logging
9168 domains. For example, this allows one to log all notices, warnings,
9169 or errors, plus all memory management messages of level debug or
9170 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
9171 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
9172 and stop using a warning that had become unfixably verbose under
9174 - New --hush command-line option similar to --quiet. While --quiet
9175 disables all logging to the console on startup, --hush limits the
9176 output to messages of warning and error severity.
9177 - Servers support a new URL scheme for consensus downloads that
9178 allows the client to specify which authorities are trusted.
9179 The server then only sends the consensus if the client will trust
9180 it. Otherwise a 404 error is sent back. Clients use this
9181 new scheme when the server supports it (meaning it's running
9182 0.2.1.1-alpha or later). Implements proposal 134.
9183 - New configure/torrc options (--enable-geoip-stats,
9184 DirRecordUsageByCountry) to record how many IPs we've served
9185 directory info to in each country code, how many status documents
9186 total we've sent to each country code, and what share of the total
9187 directory requests we should expect to see.
9188 - Use the TLS1 hostname extension to more closely resemble browser
9190 - Lots of new unit tests.
9191 - Add a macro to implement the common pattern of iterating through
9192 two parallel lists in lockstep.
9195 Changes in version 0.2.0.28-rc - 2008-06-13
9196 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
9197 performance bug, and fixes a bunch of smaller bugs.
9200 - Fix a bug where, when we were choosing the 'end stream reason' to
9201 put in our relay end cell that we send to the exit relay, Tor
9202 clients on Windows were sometimes sending the wrong 'reason'. The
9203 anonymity problem is that exit relays may be able to guess whether
9204 the client is running Windows, thus helping partition the anonymity
9205 set. Down the road we should stop sending reasons to exit relays,
9206 or otherwise prevent future versions of this bug.
9209 - While setting up a hidden service, some valid introduction circuits
9210 were overlooked and abandoned. This might be the reason for
9211 the long delay in making a hidden service available. Bugfix on
9215 - Update to the "June 9 2008" ip-to-country file.
9216 - Run 'make test' as part of 'make dist', so we stop releasing so
9217 many development snapshots that fail their unit tests.
9220 - When we're checking if we have enough dir info for each relay
9221 to begin establishing circuits, make sure that we actually have
9222 the descriptor listed in the consensus, not just any descriptor.
9224 - Bridge relays no longer print "xx=0" in their extrainfo document
9225 for every single country code in the geoip db. Bugfix on
9227 - Only warn when we fail to load the geoip file if we were planning to
9228 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
9229 - If we change our MaxAdvertisedBandwidth and then reload torrc,
9230 Tor won't realize it should publish a new relay descriptor. Fixes
9231 bug 688, reported by mfr. Bugfix on 0.1.2.x.
9232 - When we haven't had any application requests lately, don't bother
9233 logging that we have expired a bunch of descriptors. Bugfix
9235 - Make relay cells written on a connection count as non-padding when
9236 tracking how long a connection has been in use. Bugfix on
9237 0.2.0.1-alpha. Spotted by lodger.
9238 - Fix unit tests in 0.2.0.27-rc.
9239 - Fix compile on Windows.
9242 Changes in version 0.2.0.27-rc - 2008-06-03
9243 Tor 0.2.0.27-rc adds a few features we left out of the earlier
9244 release candidates. In particular, we now include an IP-to-country
9245 GeoIP database, so controllers can easily look up what country a
9246 given relay is in, and so bridge relays can give us some sanitized
9247 summaries about which countries are making use of bridges. (See proposal
9248 126-geoip-fetching.txt for details.)
9251 - Include an IP-to-country GeoIP file in the tarball, so bridge
9252 relays can report sanitized summaries of the usage they're seeing.
9255 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
9256 Robert Hogan. Fixes the first part of bug 681.
9257 - Make bridge authorities never serve extrainfo docs.
9258 - Add support to detect Libevent versions in the 1.4.x series
9260 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
9261 - Include a new contrib/tor-exit-notice.html file that exit relay
9262 operators can put on their website to help reduce abuse queries.
9265 - When tunneling an encrypted directory connection, and its first
9266 circuit fails, do not leave it unattached and ask the controller
9267 to deal. Fixes the second part of bug 681.
9268 - Make bridge authorities correctly expire old extrainfo documents
9272 Changes in version 0.2.0.26-rc - 2008-05-13
9273 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
9274 in Debian's OpenSSL packages. All users running any 0.2.0.x version
9275 should upgrade, whether they're running Debian or not.
9277 o Major security fixes:
9278 - Use new V3 directory authority keys on the tor26, gabelmoo, and
9279 moria1 V3 directory authorities. The old keys were generated with
9280 a vulnerable version of Debian's OpenSSL package, and must be
9281 considered compromised. Other authorities' keys were not generated
9282 with an affected version of OpenSSL.
9285 - List authority signatures as "unrecognized" based on DirServer
9286 lines, not on cert cache. Bugfix on 0.2.0.x.
9289 - Add a new V3AuthUseLegacyKey option to make it easier for
9290 authorities to change their identity keys if they have to.
9293 Changes in version 0.2.0.25-rc - 2008-04-23
9294 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
9297 - Remember to initialize threading before initializing logging.
9298 Otherwise, many BSD-family implementations will crash hard on
9299 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
9302 - Authorities correctly free policies on bad servers on
9303 exit. Fixes bug 672. Bugfix on 0.2.0.x.
9306 Changes in version 0.2.0.24-rc - 2008-04-22
9307 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
9308 v3 directory authority, makes relays with dynamic IP addresses and no
9309 DirPort notice more quickly when their IP address changes, fixes a few
9310 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
9312 o New directory authorities:
9313 - Take lefkada out of the list of v3 directory authorities, since
9314 it has been down for months.
9315 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
9319 - Detect address changes more quickly on non-directory mirror
9320 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
9322 o Minor features (security):
9323 - Reject requests for reverse-dns lookup of names that are in
9324 a private address space. Patch from lodger.
9325 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
9328 o Minor bugfixes (crashes):
9329 - Avoid a rare assert that can trigger when Tor doesn't have much
9330 directory information yet and it tries to fetch a v2 hidden
9331 service descriptor. Fixes bug 651, reported by nwf.
9332 - Initialize log mutex before initializing dmalloc. Otherwise,
9333 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
9334 - Use recursive pthread mutexes in order to avoid deadlock when
9335 logging debug-level messages to a controller. Bug spotted by nwf,
9336 bugfix on 0.2.0.16-alpha.
9338 o Minor bugfixes (resource management):
9339 - Keep address policies from leaking memory: start their refcount
9340 at 1, not 2. Bugfix on 0.2.0.16-alpha.
9341 - Free authority certificates on exit, so they don't look like memory
9342 leaks. Bugfix on 0.2.0.19-alpha.
9343 - Free static hashtables for policy maps and for TLS connections on
9344 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
9345 - Avoid allocating extra space when computing consensuses on 64-bit
9346 platforms. Bug spotted by aakova.
9348 o Minor bugfixes (misc):
9349 - Do not read the configuration file when we've only been told to
9350 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
9351 based on patch from Sebastian Hahn.
9352 - Exit relays that are used as a client can now reach themselves
9353 using the .exit notation, rather than just launching an infinite
9354 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
9355 - When attempting to open a logfile fails, tell us why.
9356 - Fix a dumb bug that was preventing us from knowing that we should
9357 preemptively build circuits to handle expected directory requests.
9358 Fixes bug 660. Bugfix on 0.1.2.x.
9359 - Warn less verbosely about clock skew from netinfo cells from
9360 untrusted sources. Fixes bug 663.
9361 - Make controller stream events for DNS requests more consistent,
9362 by adding "new stream" events for DNS requests, and removing
9363 spurious "stream closed" events" for cached reverse resolves.
9364 Patch from mwenge. Fixes bug 646.
9365 - Correctly notify one-hop connections when a circuit build has
9366 failed. Possible fix for bug 669. Found by lodger.
9369 Changes in version 0.2.0.23-rc - 2008-03-24
9370 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
9371 makes bootstrapping faster if the first directory mirror you contact
9372 is down. The bundles also include the new Vidalia 0.1.2 release.
9375 - When a tunneled directory request is made to a directory server
9376 that's down, notice after 30 seconds rather than 120 seconds. Also,
9377 fail any begindir streams that are pending on it, so they can
9378 retry elsewhere. This was causing multi-minute delays on bootstrap.
9381 Changes in version 0.2.0.22-rc - 2008-03-18
9382 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
9383 enables encrypted directory connections by default for non-relays, fixes
9384 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
9385 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
9388 - Enable encrypted directory connections by default for non-relays,
9389 so censor tools that block Tor directory connections based on their
9390 plaintext patterns will no longer work. This means Tor works in
9391 certain censored countries by default again.
9394 - Make sure servers always request certificates from clients during
9395 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
9396 - Do not enter a CPU-eating loop when a connection is closed in
9397 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
9398 diagnosed by lodger; bugfix on 0.2.0.20-rc.
9399 - Fix assertion failure that could occur when a blocked circuit
9400 became unblocked, and it had pending client DNS requests. Bugfix
9401 on 0.2.0.1-alpha. Fixes bug 632.
9403 o Minor bugfixes (on 0.1.2.x):
9404 - Generate "STATUS_SERVER" events rather than misspelled
9405 "STATUS_SEVER" events. Caught by mwenge.
9406 - When counting the number of bytes written on a TLS connection,
9407 look at the BIO actually used for writing to the network, not
9408 at the BIO used (sometimes) to buffer data for the network.
9409 Looking at different BIOs could result in write counts on the
9410 order of ULONG_MAX. Fixes bug 614.
9411 - On Windows, correctly detect errors when listing the contents of
9412 a directory. Fix from lodger.
9414 o Minor bugfixes (on 0.2.0.x):
9415 - Downgrade "sslv3 alert handshake failure" message to INFO.
9416 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
9417 left BandwidthRate and BandwidthBurst at the default, we would be
9418 silently limited by those defaults. Now raise them to match the
9419 RelayBandwidth* values.
9420 - Fix the SVK version detection logic to work correctly on a branch.
9421 - Make --enable-openbsd-malloc work correctly on Linux with alpha
9422 CPUs. Fixes bug 625.
9423 - Logging functions now check that the passed severity is sane.
9424 - Use proper log levels in the testsuite call of
9425 get_interface_address6().
9426 - When using a nonstandard malloc, do not use the platform values for
9427 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
9428 - Make the openbsd malloc code use 8k pages on alpha CPUs and
9430 - Detect mismatched page sizes when using --enable-openbsd-malloc.
9431 - Avoid double-marked-for-close warning when certain kinds of invalid
9432 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
9433 for bug 617. Bugfix on 0.2.0.1-alpha.
9434 - Make sure that the "NULL-means-reject *:*" convention is followed by
9435 all the policy manipulation functions, avoiding some possible crash
9436 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
9437 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
9438 actually works, and doesn't warn about every single reverse lookup.
9439 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
9442 - Only log guard node status when guard node status has changed.
9443 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
9444 make "INFO" 75% less verbose.
9447 Changes in version 0.2.0.21-rc - 2008-03-02
9448 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
9449 makes Tor work well with Vidalia again, fixes a rare assert bug,
9450 and fixes a pair of more minor bugs. The bundles also include Vidalia
9451 0.1.0 and Torbutton 1.1.16.
9454 - The control port should declare that it requires password auth
9455 when HashedControlSessionPassword is set too. Patch from Matt Edman;
9456 bugfix on 0.2.0.20-rc. Fixes bug 615.
9457 - Downgrade assert in connection_buckets_decrement() to a log message.
9458 This may help us solve bug 614, and in any case will make its
9459 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
9460 - We were sometimes miscounting the number of bytes read from the
9461 network, causing our rate limiting to not be followed exactly.
9462 Bugfix on 0.2.0.16-alpha. Reported by lodger.
9465 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
9466 OpenSSL versions should have been working fine. Diagnosis and patch
9467 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
9468 Bugfix on 0.2.0.20-rc.
9471 Changes in version 0.2.0.20-rc - 2008-02-24
9472 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
9473 makes more progress towards normalizing Tor's TLS handshake, makes
9474 hidden services work better again, helps relays bootstrap if they don't
9475 know their IP address, adds optional support for linking in openbsd's
9476 allocator or tcmalloc, allows really fast relays to scale past 15000
9477 sockets, and fixes a bunch of minor bugs reported by Veracode.
9480 - Enable the revised TLS handshake based on the one designed by
9481 Steven Murdoch in proposal 124, as revised in proposal 130. It
9482 includes version negotiation for OR connections as described in
9483 proposal 105. The new handshake is meant to be harder for censors
9484 to fingerprint, and it adds the ability to detect certain kinds of
9485 man-in-the-middle traffic analysis attacks. The version negotiation
9486 feature will allow us to improve Tor's link protocol more safely
9488 - Choose which bridge to use proportional to its advertised bandwidth,
9489 rather than uniformly at random. This should speed up Tor for
9490 bridge users. Also do this for people who set StrictEntryNodes.
9491 - When a TrackHostExits-chosen exit fails too many times in a row,
9492 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
9495 - Resolved problems with (re-)fetching hidden service descriptors.
9496 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
9498 - If we only ever used Tor for hidden service lookups or posts, we
9499 would stop building circuits and start refusing connections after
9500 24 hours, since we falsely believed that Tor was dormant. Reported
9501 by nwf; bugfix on 0.1.2.x.
9502 - Servers that don't know their own IP address should go to the
9503 authorities for their first directory fetch, even if their DirPort
9504 is off or if they don't know they're reachable yet. This will help
9505 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
9506 - When counting the number of open sockets, count not only the number
9507 of sockets we have received from the socket() call, but also
9508 the number we've gotten from accept() and socketpair(). This bug
9509 made us fail to count all sockets that we were using for incoming
9510 connections. Bugfix on 0.2.0.x.
9511 - Fix code used to find strings within buffers, when those strings
9512 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
9513 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
9514 - Add a new __HashedControlSessionPassword option for controllers
9515 to use for one-off session password hashes that shouldn't get
9516 saved to disk by SAVECONF --- Vidalia users were accumulating a
9517 pile of HashedControlPassword lines in their torrc files, one for
9518 each time they had restarted Tor and then clicked Save. Make Tor
9519 automatically convert "HashedControlPassword" to this new option but
9520 only when it's given on the command line. Partial fix for bug 586.
9522 o Minor features (performance):
9523 - Tune parameters for cell pool allocation to minimize amount of
9525 - Add OpenBSD malloc code from phk as an optional malloc
9526 replacement on Linux: some glibc libraries do very poorly
9527 with Tor's memory allocation patterns. Pass
9528 --enable-openbsd-malloc to get the replacement malloc code.
9529 - Add a --with-tcmalloc option to the configure script to link
9530 against tcmalloc (if present). Does not yet search for
9531 non-system include paths.
9532 - Stop imposing an arbitrary maximum on the number of file descriptors
9533 used for busy servers. Bug reported by Olaf Selke; patch from
9536 o Minor features (other):
9537 - When SafeLogging is disabled, log addresses along with all TLS
9539 - When building with --enable-gcc-warnings, check for whether Apple's
9540 warning "-Wshorten-64-to-32" is available.
9541 - Add a --passphrase-fd argument to the tor-gencert command for
9544 o Minor bugfixes (memory leaks and code problems):
9545 - We were leaking a file descriptor if Tor started with a zero-length
9546 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
9547 - Detect size overflow in zlib code. Reported by Justin Ferguson and
9549 - We were comparing the raw BridgePassword entry with a base64'ed
9550 version of it, when handling a "/tor/networkstatus-bridges"
9551 directory request. Now compare correctly. Noticed by Veracode.
9552 - Recover from bad tracked-since value in MTBF-history file.
9554 - Alter the code that tries to recover from unhandled write
9555 errors, to not try to flush onto a socket that's given us
9556 unhandled errors. Bugfix on 0.1.2.x.
9557 - Make Unix controlsockets work correctly on OpenBSD. Patch from
9558 tup. Bugfix on 0.2.0.3-alpha.
9560 o Minor bugfixes (other):
9561 - If we have an extra-info document for our server, always make
9562 it available on the control port, even if we haven't gotten
9563 a copy of it from an authority yet. Patch from mwenge.
9564 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
9565 - Directory mirrors no longer include a guess at the client's IP
9566 address if the connection appears to be coming from the same /24
9567 network; it was producing too many wrong guesses.
9568 - Make the new hidden service code respect the SafeLogging setting.
9569 Bugfix on 0.2.0.x. Patch from Karsten.
9570 - When starting as an authority, do not overwrite all certificates
9571 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
9572 - If we're trying to flush the last bytes on a connection (for
9573 example, when answering a directory request), reset the
9574 time-to-give-up timeout every time we manage to write something
9575 on the socket. Bugfix on 0.1.2.x.
9576 - Change the behavior of "getinfo status/good-server-descriptor"
9577 so it doesn't return failure when any authority disappears.
9578 - Even though the man page said that "TrackHostExits ." should
9579 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
9580 - Report TLS "zero return" case as a "clean close" and "IO error"
9581 as a "close". Stop calling closes "unexpected closes": existing
9582 Tors don't use SSL_close(), so having a connection close without
9583 the TLS shutdown handshake is hardly unexpected.
9584 - Send NAMESERVER_STATUS messages for a single failed nameserver
9587 o Code simplifications and refactoring:
9588 - Remove the tor_strpartition function: its logic was confused,
9589 and it was only used for one thing that could be implemented far
9593 Changes in version 0.2.0.19-alpha - 2008-02-09
9594 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
9595 handshake, makes path selection for relays more secure and IP address
9596 guessing more robust, and generally fixes a lot of bugs in preparation
9597 for calling the 0.2.0 branch stable.
9600 - Do not include recognizeable strings in the commonname part of
9601 Tor's x509 certificates.
9604 - If we're a relay, avoid picking ourselves as an introduction point,
9605 a rendezvous point, or as the final hop for internal circuits. Bug
9606 reported by taranis and lodger. Bugfix on 0.1.2.x.
9607 - Patch from "Andrew S. Lists" to catch when we contact a directory
9608 mirror at IP address X and he says we look like we're coming from
9609 IP address X. Bugfix on 0.1.2.x.
9611 o Minor features (security):
9612 - Be more paranoid about overwriting sensitive memory on free(),
9613 as a defensive programming tactic to ensure forward secrecy.
9615 o Minor features (directory authority):
9616 - Actually validate the options passed to AuthDirReject,
9617 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
9618 - Reject router descriptors with out-of-range bandwidthcapacity or
9619 bandwidthburst values.
9621 o Minor features (controller):
9622 - Reject controller commands over 1MB in length. This keeps rogue
9623 processes from running us out of memory.
9625 o Minor features (misc):
9626 - Give more descriptive well-formedness errors for out-of-range
9627 hidden service descriptor/protocol versions.
9628 - Make memory debugging information describe more about history
9629 of cell allocation, so we can help reduce our memory use.
9631 o Deprecated features (controller):
9632 - The status/version/num-versioning and status/version/num-concurring
9633 GETINFO options are no longer useful in the v3 directory protocol:
9634 treat them as deprecated, and warn when they're used.
9637 - When our consensus networkstatus has been expired for a while, stop
9638 being willing to build circuits using it. Fixes bug 401. Bugfix
9640 - Directory caches now fetch certificates from all authorities
9641 listed in a networkstatus consensus, even when they do not
9642 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
9643 - When connecting to a bridge without specifying its key, insert
9644 the connection into the identity-to-connection map as soon as
9645 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
9646 - Detect versions of OS X where malloc_good_size() is present in the
9647 library but never actually declared. Resolves bug 587. Bugfix
9649 - Stop incorrectly truncating zlib responses to directory authority
9650 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
9651 - Stop recommending that every server operator send mail to tor-ops.
9652 Resolves bug 597. Bugfix on 0.1.2.x.
9653 - Don't trigger an assert if we start a directory authority with a
9654 private IP address (like 127.0.0.1).
9655 - Avoid possible failures when generating a directory with routers
9656 with over-long versions strings, or too many flags set. Bugfix
9658 - If an attempt to launch a DNS resolve request over the control
9659 port fails because we have overrun the limit on the number of
9660 connections, tell the controller that the request has failed.
9661 - Avoid using too little bandwidth when our clock skips a few
9662 seconds. Bugfix on 0.1.2.x.
9663 - Fix shell error when warning about missing packages in configure
9664 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
9665 - Do not become confused when receiving a spurious VERSIONS-like
9666 cell from a confused v1 client. Bugfix on 0.2.0.x.
9667 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
9668 introduction points for a hidden service have failed. Patch from
9669 Karsten Loesing. Bugfix on 0.2.0.x.
9671 o Code simplifications and refactoring:
9672 - Remove some needless generality from cpuworker code, for improved
9674 - Stop overloading the circuit_t.onionskin field for both "onionskin
9675 from a CREATE cell that we are waiting for a cpuworker to be
9676 assigned" and "onionskin from an EXTEND cell that we are going to
9677 send to an OR as soon as we are connected". Might help with bug 600.
9678 - Add an in-place version of aes_crypt() so that we can avoid doing a
9679 needless memcpy() call on each cell payload.
9682 Changes in version 0.2.0.18-alpha - 2008-01-25
9683 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
9684 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
9685 that can warn or reject connections to ports generally associated with
9686 vulnerable-plaintext protocols.
9688 o New directory authorities:
9689 - Set up dannenberg (run by CCC) as the sixth v3 directory
9693 - Fix a major memory leak when attempting to use the v2 TLS
9694 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
9695 - We accidentally enabled the under-development v2 TLS handshake
9696 code, which was causing log entries like "TLS error while
9697 renegotiating handshake". Disable it again. Resolves bug 590.
9698 - We were computing the wrong Content-Length: header for directory
9699 responses that need to be compressed on the fly, causing clients
9700 asking for those items to always fail. Bugfix on 0.2.0.x; partially
9704 - Avoid going directly to the directory authorities even if you're a
9705 relay, if you haven't found yourself reachable yet or if you've
9706 decided not to advertise your dirport yet. Addresses bug 556.
9707 - If we've gone 12 hours since our last bandwidth check, and we
9708 estimate we have less than 50KB bandwidth capacity but we could
9709 handle more, do another bandwidth test.
9710 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
9711 Tor can warn and/or refuse connections to ports commonly used with
9712 vulnerable-plaintext protocols. Currently we warn on ports 23,
9713 109, 110, and 143, but we don't reject any.
9716 - When we setconf ClientOnly to 1, close any current OR and Dir
9717 listeners. Reported by mwenge.
9718 - When we get a consensus that's been signed by more people than
9719 we expect, don't log about it; it's not a big deal. Reported
9723 - Don't answer "/tor/networkstatus-bridges" directory requests if
9724 the request isn't encrypted.
9725 - Make "ClientOnly 1" config option disable directory ports too.
9726 - Patches from Karsten Loesing to make v2 hidden services more
9727 robust: work even when there aren't enough HSDir relays available;
9728 retry when a v2 rend desc fetch fails; but don't retry if we
9729 already have a usable v0 rend desc.
9732 Changes in version 0.2.0.17-alpha - 2008-01-17
9733 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
9736 - Make the tor-gencert man page get included correctly in the tarball.
9739 Changes in version 0.2.0.16-alpha - 2008-01-17
9740 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
9741 Loesing, and generally cleans up a lot of features and minor bugs.
9743 o New directory authorities:
9744 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
9747 o Major performance improvements:
9748 - Switch our old ring buffer implementation for one more like that
9749 used by free Unix kernels. The wasted space in a buffer with 1mb
9750 of data will now be more like 8k than 1mb. The new implementation
9751 also avoids realloc();realloc(); patterns that can contribute to
9752 memory fragmentation.
9755 - Configuration files now accept C-style strings as values. This
9756 helps encode characters not allowed in the current configuration
9757 file format, such as newline or #. Addresses bug 557.
9758 - Although we fixed bug 539 (where servers would send HTTP status 503
9759 responses _and_ send a body too), there are still servers out
9760 there that haven't upgraded. Therefore, make clients parse such
9761 bodies when they receive them.
9762 - When we're not serving v2 directory information, there is no reason
9763 to actually keep any around. Remove the obsolete files and directory
9764 on startup if they are very old and we aren't going to serve them.
9766 o Minor performance improvements:
9767 - Reference-count and share copies of address policy entries; only 5%
9768 of them were actually distinct.
9769 - Never walk through the list of logs if we know that no log is
9770 interested in a given message.
9773 - When an authority has not signed a consensus, do not try to
9774 download a nonexistent "certificate with key 00000000". Bugfix
9775 on 0.2.0.x. Fixes bug 569.
9776 - Fix a rare assert error when we're closing one of our threads:
9777 use a mutex to protect the list of logs, so we never write to the
9778 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
9779 bug 575, which is kind of the revenge of bug 222.
9780 - Patch from Karsten Loesing to complain less at both the client
9781 and the relay when a relay used to have the HSDir flag but doesn't
9782 anymore, and we try to upload a hidden service descriptor.
9783 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
9785 - Do not try to download missing certificates until we have tried
9786 to check our fallback consensus. Fixes bug 583.
9787 - Make bridges round reported GeoIP stats info up to the nearest
9788 estimate, not down. Now we can distinguish between "0 people from
9789 this country" and "1 person from this country".
9790 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
9791 - Avoid possible segfault if key generation fails in
9792 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
9793 - Avoid segfault in the case where a badly behaved v2 versioning
9794 directory sends a signed networkstatus with missing client-versions.
9796 - Avoid segfaults on certain complex invocations of
9797 router_get_by_hexdigest(). Bugfix on 0.1.2.
9798 - Correct bad index on array access in parse_http_time(). Bugfix
9800 - Fix possible bug in vote generation when server versions are present
9801 but client versions are not.
9802 - Fix rare bug on REDIRECTSTREAM control command when called with no
9803 port set: it could erroneously report an error when none had
9805 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
9806 compressing large objects and find ourselves with more than 4k
9807 left over. Bugfix on 0.2.0.
9808 - Fix a small memory leak when setting up a hidden service.
9809 - Fix a few memory leaks that could in theory happen under bizarre
9811 - Fix an assert if we post a general-purpose descriptor via the
9812 control port but that descriptor isn't mentioned in our current
9813 network consensus. Bug reported by Jon McLachlan; bugfix on
9816 o Minor features (controller):
9817 - Get NS events working again. Patch from tup.
9818 - The GETCONF command now escapes and quotes configuration values
9819 that don't otherwise fit into the torrc file.
9820 - The SETCONF command now handles quoted values correctly.
9822 o Minor features (directory authorities):
9823 - New configuration options to override default maximum number of
9824 servers allowed on a single IP address. This is important for
9825 running a test network on a single host.
9826 - Actually implement the -s option to tor-gencert.
9827 - Add a manual page for tor-gencert.
9829 o Minor features (bridges):
9830 - Bridge authorities no longer serve bridge descriptors over
9831 unencrypted connections.
9833 o Minor features (other):
9834 - Add hidden services and DNSPorts to the list of things that make
9835 Tor accept that it has running ports. Change starting Tor with no
9836 ports from a fatal error to a warning; we might change it back if
9837 this turns out to confuse anybody. Fixes bug 579.
9840 Changes in version 0.1.2.19 - 2008-01-17
9841 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
9842 exit policy a little bit more conservative so it's safer to run an
9843 exit relay on a home system, and fixes a variety of smaller issues.
9846 - Exit policies now reject connections that are addressed to a
9847 relay's public (external) IP address too, unless
9848 ExitPolicyRejectPrivate is turned off. We do this because too
9849 many relays are running nearby to services that trust them based
9853 - When the clock jumps forward a lot, do not allow the bandwidth
9854 buckets to become negative. Fixes bug 544.
9855 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9856 on every successful resolve. Reported by Mike Perry.
9857 - Purge old entries from the "rephist" database and the hidden
9858 service descriptor database even when DirPort is zero.
9859 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9860 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9861 crashing or mis-answering these requests.
9862 - When we decide to send a 503 response to a request for servers, do
9863 not then also send the server descriptors: this defeats the whole
9864 purpose. Fixes bug 539.
9867 - Changing the ExitPolicyRejectPrivate setting should cause us to
9868 rebuild our server descriptor.
9869 - Fix handling of hex nicknames when answering controller requests for
9870 networkstatus by name, or when deciding whether to warn about
9871 unknown routers in a config option. (Patch from mwenge.)
9872 - Fix a couple of hard-to-trigger autoconf problems that could result
9873 in really weird results on platforms whose sys/types.h files define
9874 nonstandard integer types.
9875 - Don't try to create the datadir when running --verify-config or
9876 --hash-password. Resolves bug 540.
9877 - If we were having problems getting a particular descriptor from the
9878 directory caches, and then we learned about a new descriptor for
9879 that router, we weren't resetting our failure count. Reported
9881 - Although we fixed bug 539 (where servers would send HTTP status 503
9882 responses _and_ send a body too), there are still servers out there
9883 that haven't upgraded. Therefore, make clients parse such bodies
9884 when they receive them.
9885 - Run correctly on systems where rlim_t is larger than unsigned long.
9886 This includes some 64-bit systems.
9887 - Run correctly on platforms (like some versions of OS X 10.5) where
9888 the real limit for number of open files is OPEN_FILES, not rlim_max
9889 from getrlimit(RLIMIT_NOFILES).
9890 - Avoid a spurious free on base64 failure.
9891 - Avoid segfaults on certain complex invocations of
9892 router_get_by_hexdigest().
9893 - Fix rare bug on REDIRECTSTREAM control command when called with no
9894 port set: it could erroneously report an error when none had
9898 Changes in version 0.2.0.15-alpha - 2007-12-25
9899 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
9900 features added in 0.2.0.13-alpha.
9903 - Fix several remotely triggerable asserts based on DirPort requests
9904 for a v2 or v3 networkstatus object before we were prepared. This
9905 was particularly bad for 0.2.0.13 and later bridge relays, who
9906 would never have a v2 networkstatus and would thus always crash
9907 when used. Bugfixes on 0.2.0.x.
9908 - Estimate the v3 networkstatus size more accurately, rather than
9909 estimating it at zero bytes and giving it artificially high priority
9910 compared to other directory requests. Bugfix on 0.2.0.x.
9913 - Fix configure.in logic for cross-compilation.
9914 - When we load a bridge descriptor from the cache, and it was
9915 previously unreachable, mark it as retriable so we won't just
9916 ignore it. Also, try fetching a new copy immediately. Bugfixes
9918 - The bridge GeoIP stats were counting other relays, for example
9919 self-reachability and authority-reachability tests.
9922 - Support compilation to target iPhone; patch from cjacker huang.
9923 To build for iPhone, pass the --enable-iphone option to configure.
9926 Changes in version 0.2.0.14-alpha - 2007-12-23
9928 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
9929 without a datadirectory from a previous Tor install. Reported
9931 - Fix a crash when we fetch a descriptor that turns out to be
9932 unexpected (it used to be in our networkstatus when we started
9933 fetching it, but it isn't in our current networkstatus), and we
9934 aren't using bridges. Bugfix on 0.2.0.x.
9935 - Fix a crash when accessing hidden services: it would work the first
9936 time you use a given introduction point for your service, but
9937 on subsequent requests we'd be using garbage memory. Fixed by
9938 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
9939 - Fix a crash when we load a bridge descriptor from disk but we don't
9940 currently have a Bridge line for it in our torrc. Bugfix on
9944 - If bridge authorities set BridgePassword, they will serve a
9945 snapshot of known bridge routerstatuses from their DirPort to
9946 anybody who knows that password. Unset by default.
9949 - Make the unit tests build again.
9950 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
9951 - Make PublishServerDescriptor default to 1, so the default doesn't
9952 have to change as we invent new directory protocol versions.
9953 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
9954 be included unless sys/time.h is already included. Fixes
9955 bug 553. Bugfix on 0.2.0.x.
9956 - If we receive a general-purpose descriptor and then receive an
9957 identical bridge-purpose descriptor soon after, don't discard
9958 the next one as a duplicate.
9961 - If BridgeRelay is set to 1, then the default for
9962 PublishServerDescriptor is now "bridge" rather than "v2,v3".
9963 - If the user sets RelayBandwidthRate but doesn't set
9964 RelayBandwidthBurst, then make them equal rather than erroring out.
9967 Changes in version 0.2.0.13-alpha - 2007-12-21
9968 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
9969 Goodell, fixes many more bugs, and adds a lot of infrastructure for
9972 o New directory authorities:
9973 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
9977 - Only update guard status (usable / not usable) once we have
9978 enough directory information. This was causing us to always pick
9979 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
9980 causing us to discard all our guards on startup if we hadn't been
9981 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
9982 - Purge old entries from the "rephist" database and the hidden
9983 service descriptor databases even when DirPort is zero. Bugfix
9985 - We were ignoring our RelayBandwidthRate for the first 30 seconds
9986 after opening a circuit -- even a relayed circuit. Bugfix on
9988 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9989 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9990 crashing or mis-answering these types of requests.
9991 - Relays were publishing their server descriptor to v1 and v2
9992 directory authorities, but they didn't try publishing to v3-only
9993 authorities. Fix this; and also stop publishing to v1 authorities.
9995 - When we were reading router descriptors from cache, we were ignoring
9996 the annotations -- so for example we were reading in bridge-purpose
9997 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
9998 - When we decided to send a 503 response to a request for servers, we
9999 were then also sending the server descriptors: this defeats the
10000 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
10003 - Bridge relays now behave like clients with respect to time
10004 intervals for downloading new consensus documents -- otherwise they
10005 stand out. Bridge users now wait until the end of the interval,
10006 so their bridge relay will be sure to have a new consensus document.
10007 - Three new config options (AlternateDirAuthority,
10008 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
10009 user selectively replace the default directory authorities by type,
10010 rather than the all-or-nothing replacement that DirServer offers.
10011 - Tor can now be configured to read a GeoIP file from disk in one
10012 of two formats. This can be used by controllers to map IP addresses
10013 to countries. Eventually, it may support exit-by-country.
10014 - When possible, bridge relays remember which countries users
10015 are coming from, and report aggregate information in their
10016 extra-info documents, so that the bridge authorities can learn
10017 where Tor is blocked.
10018 - Bridge directory authorities now do reachability testing on the
10019 bridges they know. They provide router status summaries to the
10020 controller via "getinfo ns/purpose/bridge", and also dump summaries
10021 to a file periodically.
10022 - Stop fetching directory info so aggressively if your DirPort is
10023 on but your ORPort is off; stop fetching v2 dir info entirely.
10024 You can override these choices with the new FetchDirInfoEarly
10028 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
10029 consensus documents when there are too many relays at a single
10030 IP address. Now clear it in v2 network status documents too, and
10031 also clear it in routerinfo_t when the relay is no longer listed
10032 in the relevant networkstatus document.
10033 - Don't crash if we get an unexpected value for the
10034 PublishServerDescriptor config option. Reported by Matt Edman;
10035 bugfix on 0.2.0.9-alpha.
10036 - Our new v2 hidden service descriptor format allows descriptors
10037 that have no introduction points. But Tor crashed when we tried
10038 to build a descriptor with no intro points (and it would have
10039 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
10040 by Karsten Loesing.
10041 - Fix building with dmalloc 5.5.2 with glibc.
10042 - Reject uploaded descriptors and extrainfo documents if they're
10043 huge. Otherwise we'll cache them all over the network and it'll
10044 clog everything up. Reported by Aljosha Judmayer.
10045 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
10046 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
10047 - When the DANGEROUS_VERSION controller status event told us we're
10048 running an obsolete version, it used the string "OLD" to describe
10049 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
10050 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
10051 - If we can't expand our list of entry guards (e.g. because we're
10052 using bridges or we have StrictEntryNodes set), don't mark relays
10053 down when they fail a directory request. Otherwise we're too quick
10054 to mark all our entry points down. Bugfix on 0.1.2.x.
10055 - Fix handling of hex nicknames when answering controller requests for
10056 networkstatus by name, or when deciding whether to warn about unknown
10057 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
10058 - Fix a couple of hard-to-trigger autoconf problems that could result
10059 in really weird results on platforms whose sys/types.h files define
10060 nonstandard integer types. Bugfix on 0.1.2.x.
10061 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
10062 - Don't crash on name lookup when we have no current consensus. Fixes
10063 bug 538; bugfix on 0.2.0.x.
10064 - Only Tors that want to mirror the v2 directory info should
10065 create the "cached-status" directory in their datadir. (All Tors
10066 used to create it.) Bugfix on 0.2.0.9-alpha.
10067 - Directory authorities should only automatically download Extra Info
10068 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
10071 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
10072 consumers. (We already do this on HUP.)
10073 - Authorities and caches fetch the v2 networkstatus documents
10074 less often, now that v3 is encouraged.
10075 - Add a new config option BridgeRelay that specifies you want to
10076 be a bridge relay. Right now the only difference is that it makes
10077 you answer begin_dir requests, and it makes you cache dir info,
10078 even if your DirPort isn't on.
10079 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
10080 ask about source, timestamp of arrival, purpose, etc. We need
10081 something like this to help Vidalia not do GeoIP lookups on bridge
10083 - Allow multiple HashedControlPassword config lines, to support
10084 multiple controller passwords.
10085 - Authorities now decide whether they're authoritative for a given
10086 router based on the router's purpose.
10087 - New config options AuthDirBadDir and AuthDirListBadDirs for
10088 authorities to mark certain relays as "bad directories" in the
10089 networkstatus documents. Also supports the "!baddir" directive in
10090 the approved-routers file.
10093 Changes in version 0.2.0.12-alpha - 2007-11-16
10094 This twelfth development snapshot fixes some more build problems as
10095 well as a few minor bugs.
10098 - Make it build on OpenBSD again. Patch from tup.
10099 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
10100 package-building for Red Hat, OS X, etc.
10102 o Minor bugfixes (on 0.1.2.x):
10103 - Changing the ExitPolicyRejectPrivate setting should cause us to
10104 rebuild our server descriptor.
10106 o Minor bugfixes (on 0.2.0.x):
10107 - When we're lacking a consensus, don't try to perform rendezvous
10108 operations. Reported by Karsten Loesing.
10109 - Fix a small memory leak whenever we decide against using a
10110 newly picked entry guard. Reported by Mike Perry.
10111 - When authorities detected more than two relays running on the same
10112 IP address, they were clearing all the status flags but forgetting
10113 to clear the "hsdir" flag. So clients were being told that a
10114 given relay was the right choice for a v2 hsdir lookup, yet they
10115 never had its descriptor because it was marked as 'not running'
10117 - If we're trying to fetch a bridge descriptor and there's no way
10118 the bridge authority could help us (for example, we don't know
10119 a digest, or there is no bridge authority), don't be so eager to
10120 fall back to asking the bridge authority.
10121 - If we're using bridges or have strictentrynodes set, and our
10122 chosen exit is in the same family as all our bridges/entry guards,
10123 then be flexible about families.
10126 - When we negotiate a v2 link-layer connection (not yet implemented),
10127 accept RELAY_EARLY cells and turn them into RELAY cells if we've
10128 negotiated a v1 connection for their next step. Initial code for
10132 Changes in version 0.2.0.11-alpha - 2007-11-12
10133 This eleventh development snapshot fixes some build problems with
10134 the previous snapshot. It also includes a more secure-by-default exit
10135 policy for relays, fixes an enormous memory leak for exit relays, and
10136 fixes another bug where servers were falling out of the directory list.
10139 - Exit policies now reject connections that are addressed to a
10140 relay's public (external) IP address too, unless
10141 ExitPolicyRejectPrivate is turned off. We do this because too
10142 many relays are running nearby to services that trust them based
10143 on network address. Bugfix on 0.1.2.x.
10146 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
10147 on every successful resolve. Reported by Mike Perry; bugfix
10149 - On authorities, never downgrade to old router descriptors simply
10150 because they're listed in the consensus. This created a catch-22
10151 where we wouldn't list a new descriptor because there was an
10152 old one in the consensus, and we couldn't get the new one in the
10153 consensus because we wouldn't list it. Possible fix for bug 548.
10154 Also, this might cause bug 543 to appear on authorities; if so,
10155 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
10157 o Packaging fixes on 0.2.0.10-alpha:
10158 - We were including instructions about what to do with the
10159 src/config/fallback-consensus file, but we weren't actually
10160 including it in the tarball. Disable all of that for now.
10163 - Allow people to say PreferTunnelledDirConns rather than
10164 PreferTunneledDirConns, for those alternate-spellers out there.
10167 - Don't reevaluate all the information from our consensus document
10168 just because we've downloaded a v2 networkstatus that we intend
10169 to cache. Fixes bug 545; bugfix on 0.2.0.x.
10172 Changes in version 0.2.0.10-alpha - 2007-11-10
10173 This tenth development snapshot adds a third v3 directory authority
10174 run by Mike Perry, adds most of Karsten Loesing's new hidden service
10175 descriptor format, fixes a bad crash bug and new bridge bugs introduced
10176 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
10177 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
10178 addresses many more minor issues.
10180 o New directory authorities:
10181 - Set up ides (run by Mike Perry) as the third v3 directory authority.
10184 - Allow tunnelled directory connections to ask for an encrypted
10185 "begin_dir" connection or an anonymized "uses a full Tor circuit"
10186 connection independently. Now we can make anonymized begin_dir
10187 connections for (e.g.) more secure hidden service posting and
10189 - More progress on proposal 114: code from Karsten Loesing to
10190 implement new hidden service descriptor format.
10191 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
10192 accommodate the growing number of servers that use the default
10193 and are reaching it.
10194 - Directory authorities use a new formula for selecting which nodes
10195 to advertise as Guards: they must be in the top 7/8 in terms of
10196 how long we have known about them, and above the median of those
10197 nodes in terms of weighted fractional uptime.
10198 - Make "not enough dir info yet" warnings describe *why* Tor feels
10199 it doesn't have enough directory info yet.
10202 - Stop servers from crashing if they set a Family option (or
10203 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
10205 - Make bridge users work again -- the move to v3 directories in
10206 0.2.0.9-alpha had introduced a number of bugs that made bridges
10207 no longer work for clients.
10208 - When the clock jumps forward a lot, do not allow the bandwidth
10209 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
10211 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
10212 - When the consensus lists a router descriptor that we previously were
10213 mirroring, but that we considered non-canonical, reload the
10214 descriptor as canonical. This fixes bug 543 where Tor servers
10215 would start complaining after a few days that they don't have
10216 enough directory information to build a circuit.
10217 - Consider replacing the current consensus when certificates arrive
10218 that make the pending consensus valid. Previously, we were only
10219 considering replacement when the new certs _didn't_ help.
10220 - Fix an assert error on startup if we didn't already have the
10221 consensus and certs cached in our datadirectory: we were caching
10222 the consensus in consensus_waiting_for_certs but then free'ing it
10224 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
10225 Request) if we need more v3 certs but we've already got pending
10226 requests for all of them.
10227 - Correctly back off from failing certificate downloads. Fixes
10229 - Authorities don't vote on the Running flag if they have been running
10230 for less than 30 minutes themselves. Fixes bug 547, where a newly
10231 started authority would vote that everyone was down.
10233 o New requirements:
10234 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
10235 it, it had no AES, and it hasn't seen any security patches since
10239 - Clients now hold circuitless TLS connections open for 1.5 times
10240 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
10241 rebuild a new circuit over them within that timeframe. Previously,
10242 they held them open only for KeepalivePeriod (5 minutes).
10243 - Use "If-Modified-Since" to avoid retrieving consensus
10244 networkstatuses that we already have.
10245 - When we have no consensus, check FallbackNetworkstatusFile (defaults
10246 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
10247 we start knowing some directory caches.
10248 - When we receive a consensus from the future, warn about skew.
10249 - Improve skew reporting: try to give the user a better log message
10250 about how skewed they are, and how much this matters.
10251 - When we have a certificate for an authority, believe that
10252 certificate's claims about the authority's IP address.
10253 - New --quiet command-line option to suppress the default console log.
10254 Good in combination with --hash-password.
10255 - Authorities send back an X-Descriptor-Not-New header in response to
10256 an accepted-but-discarded descriptor upload. Partially implements
10258 - Make the log message for "tls error. breaking." more useful.
10259 - Better log messages about certificate downloads, to attempt to
10260 track down the second incarnation of bug 546.
10262 o Minor features (bridges):
10263 - If bridge users set UpdateBridgesFromAuthority, but the digest
10264 they ask for is a 404 from the bridge authority, they now fall
10265 back to trying the bridge directly.
10266 - Bridges now use begin_dir to publish their server descriptor to
10267 the bridge authority, even when they haven't set TunnelDirConns.
10269 o Minor features (controller):
10270 - When reporting clock skew, and we know that the clock is _at least
10271 as skewed_ as some value, but we don't know the actual value,
10272 report the value as a "minimum skew."
10275 - Update linux-tor-prio.sh script to allow QoS based on the uid of
10276 the Tor process. Patch from Marco Bonetti with tweaks from Mike
10280 - Refuse to start if both ORPort and UseBridges are set. Bugfix
10281 on 0.2.0.x, suggested by Matt Edman.
10282 - Don't stop fetching descriptors when FetchUselessDescriptors is
10283 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
10284 reported by tup and ioerror.
10285 - Better log message on vote from unknown authority.
10286 - Don't log "Launching 0 request for 0 router" message.
10288 o Minor bugfixes (memory leaks):
10289 - Stop leaking memory every time we parse a v3 certificate. Bugfix
10291 - Stop leaking memory every time we load a v3 certificate. Bugfix
10292 on 0.2.0.1-alpha. Fixes bug 536.
10293 - Stop leaking a cached networkstatus on exit. Bugfix on
10295 - Stop leaking voter information every time we free a consensus.
10296 Bugfix on 0.2.0.3-alpha.
10297 - Stop leaking signed data every time we check a voter signature.
10298 Bugfix on 0.2.0.3-alpha.
10299 - Stop leaking a signature every time we fail to parse a consensus or
10300 a vote. Bugfix on 0.2.0.3-alpha.
10301 - Stop leaking v2_download_status_map on shutdown. Bugfix on
10303 - Stop leaking conn->nickname every time we make a connection to a
10304 Tor relay without knowing its expected identity digest (e.g. when
10305 using bridges). Bugfix on 0.2.0.3-alpha.
10307 - Minor bugfixes (portability):
10308 - Run correctly on platforms where rlim_t is larger than unsigned
10309 long, and/or where the real limit for number of open files is
10310 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
10311 particular, these may be needed for OS X 10.5.
10314 Changes in version 0.1.2.18 - 2007-10-28
10315 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
10316 hidden service introduction that were causing huge delays, and a big
10317 bug that was causing some servers to disappear from the network status
10318 lists for a few hours each day.
10320 o Major bugfixes (crashes):
10321 - If a connection is shut down abruptly because of something that
10322 happened inside connection_flushed_some(), do not call
10323 connection_finished_flushing(). Should fix bug 451:
10324 "connection_stop_writing: Assertion conn->write_event failed"
10325 Bugfix on 0.1.2.7-alpha.
10326 - Fix possible segfaults in functions called from
10327 rend_process_relay_cell().
10329 o Major bugfixes (hidden services):
10330 - Hidden services were choosing introduction points uniquely by
10331 hexdigest, but when constructing the hidden service descriptor
10332 they merely wrote the (potentially ambiguous) nickname.
10333 - Clients now use the v2 intro format for hidden service
10334 connections: they specify their chosen rendezvous point by identity
10335 digest rather than by (potentially ambiguous) nickname. These
10336 changes could speed up hidden service connections dramatically.
10338 o Major bugfixes (other):
10339 - Stop publishing a new server descriptor just because we get a
10340 HUP signal. This led (in a roundabout way) to some servers getting
10341 dropped from the networkstatus lists for a few hours each day.
10342 - When looking for a circuit to cannibalize, consider family as well
10343 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10344 circuit cannibalization).
10345 - When a router wasn't listed in a new networkstatus, we were leaving
10346 the flags for that router alone -- meaning it remained Named,
10347 Running, etc -- even though absence from the networkstatus means
10348 that it shouldn't be considered to exist at all anymore. Now we
10349 clear all the flags for routers that fall out of the networkstatus
10350 consensus. Fixes bug 529.
10353 - Don't try to access (or alter) the state file when running
10354 --list-fingerprint or --verify-config or --hash-password. Resolves
10356 - When generating information telling us how to extend to a given
10357 router, do not try to include the nickname if it is
10358 absent. Resolves bug 467.
10359 - Fix a user-triggerable segfault in expand_filename(). (There isn't
10360 a way to trigger this remotely.)
10361 - When sending a status event to the controller telling it that an
10362 OR address is reachable, set the port correctly. (Previously we
10363 were reporting the dir port.)
10364 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10365 command. Bugfix on 0.1.2.17.
10366 - When loading bandwidth history, do not believe any information in
10367 the future. Fixes bug 434.
10368 - When loading entry guard information, do not believe any information
10370 - When we have our clock set far in the future and generate an
10371 onion key, then re-set our clock to be correct, we should not stop
10372 the onion key from getting rotated.
10373 - On some platforms, accept() can return a broken address. Detect
10374 this more quietly, and deal accordingly. Fixes bug 483.
10375 - It's not actually an error to find a non-pending entry in the DNS
10376 cache when canceling a pending resolve. Don't log unless stuff
10377 is fishy. Resolves bug 463.
10378 - Don't reset trusted dir server list when we set a configuration
10379 option. Patch from Robert Hogan.
10380 - Don't try to create the datadir when running --verify-config or
10381 --hash-password. Resolves bug 540.
10384 Changes in version 0.2.0.9-alpha - 2007-10-24
10385 This ninth development snapshot switches clients to the new v3 directory
10386 system; allows servers to be listed in the network status even when they
10387 have the same nickname as a registered server; and fixes many other
10388 bugs including a big one that was causing some servers to disappear
10389 from the network status lists for a few hours each day.
10391 o Major features (directory system):
10392 - Clients now download v3 consensus networkstatus documents instead
10393 of v2 networkstatus documents. Clients and caches now base their
10394 opinions about routers on these consensus documents. Clients only
10395 download router descriptors listed in the consensus.
10396 - Authorities now list servers who have the same nickname as
10397 a different named server, but list them with a new flag,
10398 "Unnamed". Now we can list servers that happen to pick the same
10399 nickname as a server that registered two years ago and then
10400 disappeared. Partially implements proposal 122.
10401 - If the consensus lists a router as "Unnamed", the name is assigned
10402 to a different router: do not identify the router by that name.
10403 Partially implements proposal 122.
10404 - Authorities can now come to a consensus on which method to use to
10405 compute the consensus. This gives us forward compatibility.
10408 - Stop publishing a new server descriptor just because we HUP or
10409 when we find our DirPort to be reachable but won't actually publish
10410 it. New descriptors without any real changes are dropped by the
10411 authorities, and can screw up our "publish every 18 hours" schedule.
10413 - When a router wasn't listed in a new networkstatus, we were leaving
10414 the flags for that router alone -- meaning it remained Named,
10415 Running, etc -- even though absence from the networkstatus means
10416 that it shouldn't be considered to exist at all anymore. Now we
10417 clear all the flags for routers that fall out of the networkstatus
10418 consensus. Fixes bug 529; bugfix on 0.1.2.x.
10419 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
10420 extrainfo documents and then discard them immediately for not
10421 matching the latest router. Bugfix on 0.2.0.1-alpha.
10423 o Minor features (v3 directory protocol):
10424 - Allow tor-gencert to generate a new certificate without replacing
10426 - Allow certificates to include an address.
10427 - When we change our directory-cache settings, reschedule all voting
10428 and download operations.
10429 - Reattempt certificate downloads immediately on failure, as long as
10430 we haven't failed a threshold number of times yet.
10431 - Delay retrying consensus downloads while we're downloading
10432 certificates to verify the one we just got. Also, count getting a
10433 consensus that we already have (or one that isn't valid) as a failure,
10434 and count failing to get the certificates after 20 minutes as a
10436 - Build circuits and download descriptors even if our consensus is a
10437 little expired. (This feature will go away once authorities are
10440 o Minor features (router descriptor cache):
10441 - If we find a cached-routers file that's been sitting around for more
10442 than 28 days unmodified, then most likely it's a leftover from
10443 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
10445 - When we (as a cache) download a descriptor because it was listed
10446 in a consensus, remember when the consensus was supposed to expire,
10447 and don't expire the descriptor until then.
10449 o Minor features (performance):
10450 - Call routerlist_remove_old_routers() much less often. This should
10451 speed startup, especially on directory caches.
10452 - Don't try to launch new descriptor downloads quite so often when we
10453 already have enough directory information to build circuits.
10454 - Base64 decoding was actually showing up on our profile when parsing
10455 the initial descriptor file; switch to an in-process all-at-once
10456 implementation that's about 3.5x times faster than calling out to
10459 o Minor features (compilation):
10460 - Detect non-ASCII platforms (if any still exist) and refuse to
10461 build there: some of our code assumes that 'A' is 65 and so on.
10463 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
10464 - Make the "next period" votes into "current period" votes immediately
10465 after publishing the consensus; avoid a heisenbug that made them
10466 stick around indefinitely.
10467 - When we discard a vote as a duplicate, do not report this as
10469 - Treat missing v3 keys or certificates as an error when running as a
10470 v3 directory authority.
10471 - When we're configured to be a v3 authority, but we're only listed
10472 as a non-v3 authority in our DirServer line for ourself, correct
10474 - If an authority doesn't have a qualified hostname, just put
10475 its address in the vote. This fixes the problem where we referred to
10476 "moria on moria:9031."
10477 - Distinguish between detached signatures for the wrong period, and
10478 detached signatures for a divergent vote.
10479 - Fix a small memory leak when computing a consensus.
10480 - When there's no concensus, we were forming a vote every 30
10481 minutes, but writing the "valid-after" line in our vote based
10482 on our configured V3AuthVotingInterval: so unless the intervals
10483 matched up, we immediately rejected our own vote because it didn't
10484 start at the voting interval that caused us to construct a vote.
10486 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
10487 - Delete unverified-consensus when the real consensus is set.
10488 - Consider retrying a consensus networkstatus fetch immediately
10489 after one fails: don't wait 60 seconds to notice.
10490 - When fetching a consensus as a cache, wait until a newer consensus
10491 should exist before trying to replace the current one.
10492 - Use a more forgiving schedule for retrying failed consensus
10493 downloads than for other types.
10495 o Minor bugfixes (other directory issues):
10496 - Correct the implementation of "download votes by digest." Bugfix on
10498 - Authorities no longer send back "400 you're unreachable please fix
10499 it" errors to Tor servers that aren't online all the time. We're
10500 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
10502 o Minor bugfixes (controller):
10503 - Don't reset trusted dir server list when we set a configuration
10504 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
10505 - Respond to INT and TERM SIGNAL commands before we execute the
10506 signal, in case the signal shuts us down. We had a patch in
10507 0.1.2.1-alpha that tried to do this by queueing the response on
10508 the connection's buffer before shutting down, but that really
10509 isn't the same thing at all. Bug located by Matt Edman.
10511 o Minor bugfixes (misc):
10512 - Correctly check for bad options to the "PublishServerDescriptor"
10513 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
10514 - Stop leaking memory on failing case of base32_decode, and make
10515 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
10516 - Don't try to download extrainfo documents when we're trying to
10517 fetch enough directory info to build a circuit: having enough
10518 info should get priority. Bugfix on 0.2.0.x.
10519 - Don't complain that "your server has not managed to confirm that its
10520 ports are reachable" if we haven't been able to build any circuits
10521 yet. Bug found by spending four hours without a v3 consensus. Bugfix
10523 - Detect the reason for failing to mmap a descriptor file we just
10524 wrote, and give a more useful log message. Fixes bug 533. Bugfix
10527 o Code simplifications and refactoring:
10528 - Remove support for the old bw_accounting file: we've been storing
10529 bandwidth accounting information in the state file since
10530 0.1.2.5-alpha. This may result in bandwidth accounting errors
10531 if you try to upgrade from 0.1.1.x or earlier, or if you try to
10532 downgrade to 0.1.1.x or earlier.
10533 - New convenience code to locate a file within the DataDirectory.
10534 - Move non-authority functionality out of dirvote.c.
10535 - Refactor the arguments for router_pick_{directory_|trusteddir}server
10536 so that they all take the same named flags.
10539 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
10540 Unix users an easy way to script their Tor process (e.g. by
10541 adjusting bandwidth based on the time of the day).
10544 Changes in version 0.2.0.8-alpha - 2007-10-12
10545 This eighth development snapshot fixes a crash bug that's been bothering
10546 us since February 2007, lets bridge authorities store a list of bridge
10547 descriptors they've seen, gets v3 directory voting closer to working,
10548 starts caching v3 directory consensus documents on directory mirrors,
10549 and fixes a variety of smaller issues including some minor memory leaks.
10551 o Major features (router descriptor cache):
10552 - Store routers in a file called cached-descriptors instead of in
10553 cached-routers. Initialize cached-descriptors from cached-routers
10554 if the old format is around. The new format allows us to store
10555 annotations along with descriptors.
10556 - Use annotations to record the time we received each descriptor, its
10557 source, and its purpose.
10558 - Disable the SETROUTERPURPOSE controller command: it is now
10560 - Controllers should now specify cache=no or cache=yes when using
10561 the +POSTDESCRIPTOR command.
10562 - Bridge authorities now write bridge descriptors to disk, meaning
10563 we can export them to other programs and begin distributing them
10566 o Major features (directory authorities):
10567 - When a v3 authority is missing votes or signatures, it now tries
10569 - Directory authorities track weighted fractional uptime as well as
10570 weighted mean-time-between failures. WFU is suitable for deciding
10571 whether a node is "usually up", while MTBF is suitable for deciding
10572 whether a node is "likely to stay up." We need both, because
10573 "usually up" is a good requirement for guards, while "likely to
10574 stay up" is a good requirement for long-lived connections.
10576 o Major features (v3 directory system):
10577 - Caches now download v3 network status documents as needed,
10578 and download the descriptors listed in them.
10579 - All hosts now attempt to download and keep fresh v3 authority
10580 certificates, and re-attempt after failures.
10581 - More internal-consistency checks for vote parsing.
10583 o Major bugfixes (crashes):
10584 - If a connection is shut down abruptly because of something that
10585 happened inside connection_flushed_some(), do not call
10586 connection_finished_flushing(). Should fix bug 451. Bugfix on
10589 o Major bugfixes (performance):
10590 - Fix really bad O(n^2) performance when parsing a long list of
10591 routers: Instead of searching the entire list for an "extra-info "
10592 string which usually wasn't there, once for every routerinfo
10593 we read, just scan lines forward until we find one we like.
10595 - When we add data to a write buffer in response to the data on that
10596 write buffer getting low because of a flush, do not consider the
10597 newly added data as a candidate for immediate flushing, but rather
10598 make it wait until the next round of writing. Otherwise, we flush
10599 and refill recursively, and a single greedy TLS connection can
10600 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
10602 o Minor features (v3 authority system):
10603 - Add more ways for tools to download the votes that lead to the
10605 - Send a 503 when low on bandwidth and a vote, consensus, or
10606 certificate is requested.
10607 - If-modified-since is now implemented properly for all kinds of
10608 certificate requests.
10610 o Minor bugfixes (network statuses):
10611 - Tweak the implementation of proposal 109 slightly: allow at most
10612 two Tor servers on the same IP address, except if it's the location
10613 of a directory authority, in which case allow five. Bugfix on
10616 o Minor bugfixes (controller):
10617 - When sending a status event to the controller telling it that an
10618 OR address is reachable, set the port correctly. (Previously we
10619 were reporting the dir port.) Bugfix on 0.1.2.x.
10621 o Minor bugfixes (v3 directory system):
10622 - Fix logic to look up a cert by its signing key digest. Bugfix on
10624 - Only change the reply to a vote to "OK" if it's not already
10625 set. This gets rid of annoying "400 OK" log messages, which may
10626 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
10627 - When we get a valid consensus, recompute the voting schedule.
10628 - Base the valid-after time of a vote on the consensus voting
10629 schedule, not on our preferred schedule.
10630 - Make the return values and messages from signature uploads and
10631 downloads more sensible.
10632 - Fix a memory leak when serving votes and consensus documents, and
10633 another when serving certificates.
10635 o Minor bugfixes (performance):
10636 - Use a slightly simpler string hashing algorithm (copying Python's
10637 instead of Java's) and optimize our digest hashing algorithm to take
10638 advantage of 64-bit platforms and to remove some possibly-costly
10640 - Fix a minor memory leak whenever we parse guards from our state
10641 file. Bugfix on 0.2.0.7-alpha.
10642 - Fix a minor memory leak whenever we write out a file. Bugfix on
10644 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10645 command. Bugfix on 0.2.0.5-alpha.
10647 o Minor bugfixes (portability):
10648 - On some platforms, accept() can return a broken address. Detect
10649 this more quietly, and deal accordingly. Fixes bug 483.
10650 - Stop calling tor_strlower() on uninitialized memory in some cases.
10651 Bugfix in 0.2.0.7-alpha.
10653 o Minor bugfixes (usability):
10654 - Treat some 403 responses from directory servers as INFO rather than
10655 WARN-severity events.
10656 - It's not actually an error to find a non-pending entry in the DNS
10657 cache when canceling a pending resolve. Don't log unless stuff is
10658 fishy. Resolves bug 463.
10660 o Minor bugfixes (anonymity):
10661 - Never report that we've used more bandwidth than we're willing to
10662 relay: it leaks how much non-relay traffic we're using. Resolves
10664 - When looking for a circuit to cannibalize, consider family as well
10665 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10666 circuit cannibalization).
10668 o Code simplifications and refactoring:
10669 - Make a bunch of functions static. Remove some dead code.
10670 - Pull out about a third of the really big routerlist.c; put it in a
10671 new module, networkstatus.c.
10672 - Merge the extra fields in local_routerstatus_t back into
10673 routerstatus_t: we used to need one routerstatus_t for each
10674 authority's opinion, plus a local_routerstatus_t for the locally
10675 computed consensus opinion. To save space, we put the locally
10676 modified fields into local_routerstatus_t, and only the common
10677 stuff into routerstatus_t. But once v3 directories are in use,
10678 clients and caches will no longer need to hold authority opinions;
10679 thus, the rationale for keeping the types separate is now gone.
10680 - Make the code used to reschedule and reattempt downloads more
10682 - Turn all 'Are we a directory server/mirror?' logic into a call to
10684 - Remove the code to generate the oldest (v1) directory format.
10685 The code has been disabled since 0.2.0.5-alpha.
10688 Changes in version 0.2.0.7-alpha - 2007-09-21
10689 This seventh development snapshot makes bridges work again, makes bridge
10690 authorities work for the first time, fixes two huge performance flaws
10691 in hidden services, and fixes a variety of minor issues.
10693 o New directory authorities:
10694 - Set up moria1 and tor26 as the first v3 directory authorities. See
10695 doc/spec/dir-spec.txt for details on the new directory design.
10697 o Major bugfixes (crashes):
10698 - Fix possible segfaults in functions called from
10699 rend_process_relay_cell(). Bugfix on 0.1.2.x.
10701 o Major bugfixes (bridges):
10702 - Fix a bug that made servers send a "404 Not found" in response to
10703 attempts to fetch their server descriptor. This caused Tor servers
10704 to take many minutes to establish reachability for their DirPort,
10705 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
10706 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
10707 users configure that and specify a bridge with an identity
10708 fingerprint, now they will lookup the bridge descriptor at the
10709 default bridge authority via a one-hop tunnel, but once circuits
10710 are established they will switch to a three-hop tunnel for later
10711 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
10713 o Major bugfixes (hidden services):
10714 - Hidden services were choosing introduction points uniquely by
10715 hexdigest, but when constructing the hidden service descriptor
10716 they merely wrote the (potentially ambiguous) nickname.
10717 - Clients now use the v2 intro format for hidden service
10718 connections: they specify their chosen rendezvous point by identity
10719 digest rather than by (potentially ambiguous) nickname. Both
10720 are bugfixes on 0.1.2.x, and they could speed up hidden service
10721 connections dramatically. Thanks to Karsten Loesing.
10723 o Minor features (security):
10724 - As a client, do not believe any server that tells us that an
10725 address maps to an internal address space.
10726 - Make it possible to enable HashedControlPassword and
10727 CookieAuthentication at the same time.
10729 o Minor features (guard nodes):
10730 - Tag every guard node in our state file with the version that
10731 we believe added it, or with our own version if we add it. This way,
10732 if a user temporarily runs an old version of Tor and then switches
10733 back to a new one, she doesn't automatically lose her guards.
10735 o Minor features (speed):
10736 - When implementing AES counter mode, update only the portions of the
10737 counter buffer that need to change, and don't keep separate
10738 network-order and host-order counters when they are the same (i.e.,
10739 on big-endian hosts.)
10741 o Minor features (controller):
10742 - Accept LF instead of CRLF on controller, since some software has a
10743 hard time generating real Internet newlines.
10744 - Add GETINFO values for the server status events
10745 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
10748 o Removed features:
10749 - Routers no longer include bandwidth-history lines in their
10750 descriptors; this information is already available in extra-info
10751 documents, and including it in router descriptors took up 60%
10752 (!) of compressed router descriptor downloads. Completes
10753 implementation of proposal 104.
10754 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
10755 and TorControl.py, as they use the old v0 controller protocol,
10756 and are obsoleted by TorFlow anyway.
10757 - Drop support for v1 rendezvous descriptors, since we never used
10758 them anyway, and the code has probably rotted by now. Based on
10759 patch from Karsten Loesing.
10760 - On OSX, stop warning the user that kqueue support in libevent is
10761 "experimental", since it seems to have worked fine for ages.
10764 - When generating information telling us how to extend to a given
10765 router, do not try to include the nickname if it is absent. Fixes
10766 bug 467. Bugfix on 0.2.0.3-alpha.
10767 - Fix a user-triggerable (but not remotely-triggerable) segfault
10768 in expand_filename(). Bugfix on 0.1.2.x.
10769 - Fix a memory leak when freeing incomplete requests from DNSPort.
10770 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
10771 - Don't try to access (or alter) the state file when running
10772 --list-fingerprint or --verify-config or --hash-password. (Resolves
10773 bug 499.) Bugfix on 0.1.2.x.
10774 - Servers used to decline to publish their DirPort if their
10775 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
10776 were below a threshold. Now they only look at BandwidthRate and
10777 RelayBandwidthRate. Bugfix on 0.1.2.x.
10778 - Remove an optimization in the AES counter-mode code that assumed
10779 that the counter never exceeded 2^68. When the counter can be set
10780 arbitrarily as an IV (as it is by Karsten's new hidden services
10781 code), this assumption no longer holds. Bugfix on 0.1.2.x.
10782 - Resume listing "AUTHORITY" flag for authorities in network status.
10783 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
10785 o Code simplifications and refactoring:
10786 - Revamp file-writing logic so we don't need to have the entire
10787 contents of a file in memory at once before we write to disk. Tor,
10789 - Turn "descriptor store" into a full-fledged type.
10790 - Move all NT services code into a separate source file.
10791 - Unify all code that computes medians, percentile elements, etc.
10792 - Get rid of a needless malloc when parsing address policies.
10795 Changes in version 0.1.2.17 - 2007-08-30
10796 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
10797 X bundles. Vidalia 0.0.14 makes authentication required for the
10798 ControlPort in the default configuration, which addresses important
10799 security risks. Everybody who uses Vidalia (or another controller)
10802 In addition, this Tor update fixes major load balancing problems with
10803 path selection, which should speed things up a lot once many people
10806 o Major bugfixes (security):
10807 - We removed support for the old (v0) control protocol. It has been
10808 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
10809 become more of a headache than it's worth.
10811 o Major bugfixes (load balancing):
10812 - When choosing nodes for non-guard positions, weight guards
10813 proportionally less, since they already have enough load. Patch
10815 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10816 will allow fast Tor servers to get more attention.
10817 - When we're upgrading from an old Tor version, forget our current
10818 guards and pick new ones according to the new weightings. These
10819 three load balancing patches could raise effective network capacity
10820 by a factor of four. Thanks to Mike Perry for measurements.
10822 o Major bugfixes (stream expiration):
10823 - Expire not-yet-successful application streams in all cases if
10824 they've been around longer than SocksTimeout. Right now there are
10825 some cases where the stream will live forever, demanding a new
10826 circuit every 15 seconds. Fixes bug 454; reported by lodger.
10828 o Minor features (controller):
10829 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10830 is valid before any authentication has been received. It tells
10831 a controller what kind of authentication is expected, and what
10832 protocol is spoken. Implements proposal 119.
10834 o Minor bugfixes (performance):
10835 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
10836 greatly speeding up loading cached-routers from disk on startup.
10837 - Disable sentinel-based debugging for buffer code: we squashed all
10838 the bugs that this was supposed to detect a long time ago, and now
10839 its only effect is to change our buffer sizes from nice powers of
10840 two (which platform mallocs tend to like) to values slightly over
10841 powers of two (which make some platform mallocs sad).
10843 o Minor bugfixes (misc):
10844 - If exit bandwidth ever exceeds one third of total bandwidth, then
10845 use the correct formula to weight exit nodes when choosing paths.
10846 Based on patch from Mike Perry.
10847 - Choose perfectly fairly among routers when choosing by bandwidth and
10848 weighting by fraction of bandwidth provided by exits. Previously, we
10849 would choose with only approximate fairness, and correct ourselves
10850 if we ran off the end of the list.
10851 - If we require CookieAuthentication but we fail to write the
10852 cookie file, we would warn but not exit, and end up in a state
10853 where no controller could authenticate. Now we exit.
10854 - If we require CookieAuthentication, stop generating a new cookie
10855 every time we change any piece of our config.
10856 - Refuse to start with certain directory authority keys, and
10857 encourage people using them to stop.
10858 - Terminate multi-line control events properly. Original patch
10860 - Fix a minor memory leak when we fail to find enough suitable
10861 servers to choose a circuit.
10862 - Stop leaking part of the descriptor when we run into a particularly
10863 unparseable piece of it.
10866 Changes in version 0.2.0.6-alpha - 2007-08-26
10867 This sixth development snapshot features a new Vidalia version in the
10868 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
10869 the ControlPort in the default configuration, which addresses important
10872 In addition, this snapshot fixes major load balancing problems
10873 with path selection, which should speed things up a lot once many
10874 people have upgraded. The directory authorities also use a new
10875 mean-time-between-failure approach to tracking which servers are stable,
10876 rather than just looking at the most recent uptime.
10878 o New directory authorities:
10879 - Set up Tonga as the default bridge directory authority.
10882 - Directory authorities now track servers by weighted
10883 mean-times-between-failures. When we have 4 or more days of data,
10884 use measured MTBF rather than declared uptime to decide whether
10885 to call a router Stable. Implements proposal 108.
10887 o Major bugfixes (load balancing):
10888 - When choosing nodes for non-guard positions, weight guards
10889 proportionally less, since they already have enough load. Patch
10891 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10892 will allow fast Tor servers to get more attention.
10893 - When we're upgrading from an old Tor version, forget our current
10894 guards and pick new ones according to the new weightings. These
10895 three load balancing patches could raise effective network capacity
10896 by a factor of four. Thanks to Mike Perry for measurements.
10898 o Major bugfixes (descriptor parsing):
10899 - Handle unexpected whitespace better in malformed descriptors. Bug
10900 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
10903 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
10904 GETINFO for Torstat to use until it can switch to using extrainfos.
10905 - Optionally (if built with -DEXPORTMALLINFO) export the output
10906 of mallinfo via http, as tor/mallinfo.txt. Only accessible
10910 - Do not intermix bridge routers with controller-added
10911 routers. (Bugfix on 0.2.0.x)
10912 - Do not fail with an assert when accept() returns an unexpected
10913 address family. Addresses but does not wholly fix bug 483. (Bugfix
10915 - Let directory authorities startup even when they can't generate
10916 a descriptor immediately, e.g. because they don't know their
10918 - Stop putting the authentication cookie in a file called "0"
10919 in your working directory if you don't specify anything for the
10920 new CookieAuthFile option. Reported by Matt Edman.
10921 - Make it possible to read the PROTOCOLINFO response in a way that
10922 conforms to our control-spec. Reported by Matt Edman.
10923 - Fix a minor memory leak when we fail to find enough suitable
10924 servers to choose a circuit. Bugfix on 0.1.2.x.
10925 - Stop leaking part of the descriptor when we run into a particularly
10926 unparseable piece of it. Bugfix on 0.1.2.x.
10927 - Unmap the extrainfo cache file on exit.
10930 Changes in version 0.2.0.5-alpha - 2007-08-19
10931 This fifth development snapshot fixes compilation on Windows again;
10932 fixes an obnoxious client-side bug that slowed things down and put
10933 extra load on the network; gets us closer to using the v3 directory
10934 voting scheme; makes it easier for Tor controllers to use cookie-based
10935 authentication; and fixes a variety of other bugs.
10937 o Removed features:
10938 - Version 1 directories are no longer generated in full. Instead,
10939 authorities generate and serve "stub" v1 directories that list
10940 no servers. This will stop Tor versions 0.1.0.x and earlier from
10941 working, but (for security reasons) nobody should be running those
10944 o Major bugfixes (compilation, 0.2.0.x):
10945 - Try to fix Win32 compilation again: improve checking for IPv6 types.
10946 - Try to fix MSVC compilation: build correctly on platforms that do
10947 not define s6_addr16 or s6_addr32.
10948 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
10951 o Major bugfixes (stream expiration):
10952 - Expire not-yet-successful application streams in all cases if
10953 they've been around longer than SocksTimeout. Right now there are
10954 some cases where the stream will live forever, demanding a new
10955 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
10956 reported by lodger.
10958 o Minor features (directory servers):
10959 - When somebody requests a list of statuses or servers, and we have
10960 none of those, return a 404 rather than an empty 200.
10962 o Minor features (directory voting):
10963 - Store v3 consensus status consensuses on disk, and reload them
10966 o Minor features (security):
10967 - Warn about unsafe ControlPort configurations.
10968 - Refuse to start with certain directory authority keys, and
10969 encourage people using them to stop.
10971 o Minor features (controller):
10972 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10973 is valid before any authentication has been received. It tells
10974 a controller what kind of authentication is expected, and what
10975 protocol is spoken. Implements proposal 119.
10976 - New config option CookieAuthFile to choose a new location for the
10977 cookie authentication file, and config option
10978 CookieAuthFileGroupReadable to make it group-readable.
10980 o Minor features (unit testing):
10981 - Add command-line arguments to unit-test executable so that we can
10982 invoke any chosen test from the command line rather than having
10983 to run the whole test suite at once; and so that we can turn on
10984 logging for the unit tests.
10986 o Minor bugfixes (on 0.1.2.x):
10987 - If we require CookieAuthentication but we fail to write the
10988 cookie file, we would warn but not exit, and end up in a state
10989 where no controller could authenticate. Now we exit.
10990 - If we require CookieAuthentication, stop generating a new cookie
10991 every time we change any piece of our config.
10992 - When loading bandwidth history, do not believe any information in
10993 the future. Fixes bug 434.
10994 - When loading entry guard information, do not believe any information
10996 - When we have our clock set far in the future and generate an
10997 onion key, then re-set our clock to be correct, we should not stop
10998 the onion key from getting rotated.
10999 - Clean up torrc sample config file.
11000 - Do not automatically run configure from autogen.sh. This
11001 non-standard behavior tended to annoy people who have built other
11004 o Minor bugfixes (on 0.2.0.x):
11005 - Fix a bug with AutomapHostsOnResolve that would always cause
11006 the second request to fail. Bug reported by Kate. Bugfix on
11008 - Fix a bug in ADDRMAP controller replies that would sometimes
11009 try to print a NULL. Patch from tup.
11010 - Read v3 directory authority keys from the right location.
11011 - Numerous bugfixes to directory voting code.
11014 Changes in version 0.1.2.16 - 2007-08-01
11015 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
11016 remote attacker in certain situations to rewrite the user's torrc
11017 configuration file. This can completely compromise anonymity of users
11018 in most configurations, including those running the Vidalia bundles,
11019 TorK, etc. Or worse.
11021 o Major security fixes:
11022 - Close immediately after missing authentication on control port;
11023 do not allow multiple authentication attempts.
11026 Changes in version 0.2.0.4-alpha - 2007-08-01
11027 This fourth development snapshot fixes a critical security vulnerability
11028 for most users, specifically those running Vidalia, TorK, etc. Everybody
11029 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
11031 o Major security fixes:
11032 - Close immediately after missing authentication on control port;
11033 do not allow multiple authentication attempts.
11035 o Major bugfixes (compilation):
11036 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
11039 o Minor features (performance):
11040 - Be even more aggressive about releasing RAM from small
11041 empty buffers. Thanks to our free-list code, this shouldn't be too
11042 performance-intensive.
11043 - Disable sentinel-based debugging for buffer code: we squashed all
11044 the bugs that this was supposed to detect a long time ago, and
11045 now its only effect is to change our buffer sizes from nice
11046 powers of two (which platform mallocs tend to like) to values
11047 slightly over powers of two (which make some platform mallocs sad).
11048 - Log malloc statistics from mallinfo() on platforms where it
11052 Changes in version 0.2.0.3-alpha - 2007-07-29
11053 This third development snapshot introduces new experimental
11054 blocking-resistance features and a preliminary version of the v3
11055 directory voting design, and includes many other smaller features
11059 - The first pieces of our "bridge" design for blocking-resistance
11060 are implemented. People can run bridge directory authorities;
11061 people can run bridges; and people can configure their Tor clients
11062 with a set of bridges to use as the first hop into the Tor network.
11063 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
11065 - Create listener connections before we setuid to the configured
11066 User and Group. Now non-Windows users can choose port values
11067 under 1024, start Tor as root, and have Tor bind those ports
11068 before it changes to another UID. (Windows users could already
11070 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
11071 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
11072 on "vserver" accounts. (Patch from coderman.)
11073 - Be even more aggressive about separating local traffic from relayed
11074 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
11076 o Major features (experimental):
11077 - First cut of code for "v3 dir voting": directory authorities will
11078 vote on a common network status document rather than each publishing
11079 their own opinion. This code needs more testing and more corner-case
11080 handling before it's ready for use.
11083 - Directory authorities now call routers Fast if their bandwidth is
11084 at least 100KB/s, and consider their bandwidth adequate to be a
11085 Guard if it is at least 250KB/s, no matter the medians. This fix
11086 complements proposal 107. [Bugfix on 0.1.2.x]
11087 - Directory authorities now never mark more than 3 servers per IP as
11088 Valid and Running. (Implements proposal 109, by Kevin Bauer and
11090 - Minor change to organizationName and commonName generation
11091 procedures in TLS certificates during Tor handshakes, to invalidate
11092 some earlier censorware approaches. This is not a long-term
11093 solution, but applying it will give us a bit of time to look into
11094 the epidemiology of countermeasures as they spread.
11096 o Major bugfixes (directory):
11097 - Rewrite directory tokenization code to never run off the end of
11098 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
11100 o Minor features (controller):
11101 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
11102 match requests to applications. (Patch from Robert Hogan.)
11103 - Report address and port correctly on connections to DNSPort. (Patch
11104 from Robert Hogan.)
11105 - Add a RESOLVE command to launch hostname lookups. (Original patch
11106 from Robert Hogan.)
11107 - Add GETINFO status/enough-dir-info to let controllers tell whether
11108 Tor has downloaded sufficient directory information. (Patch
11110 - You can now use the ControlSocket option to tell Tor to listen for
11111 controller connections on Unix domain sockets on systems that
11112 support them. (Patch from Peter Palfrader.)
11113 - STREAM NEW events are generated for DNSPort requests and for
11114 tunneled directory connections. (Patch from Robert Hogan.)
11115 - New "GETINFO address-mappings/*" command to get address mappings
11116 with expiry information. "addr-mappings/*" is now deprecated.
11119 o Minor features (misc):
11120 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
11122 - The tor-gencert tool for v3 directory authorities now creates all
11123 files as readable to the file creator only, and write-protects
11124 the authority identity key.
11125 - When dumping memory usage, list bytes used in buffer memory
11127 - When running with dmalloc, dump more stats on hup and on exit.
11128 - Directory authorities now fail quickly and (relatively) harmlessly
11129 if they generate a network status document that is somehow
11132 o Traffic load balancing improvements:
11133 - If exit bandwidth ever exceeds one third of total bandwidth, then
11134 use the correct formula to weight exit nodes when choosing paths.
11135 (Based on patch from Mike Perry.)
11136 - Choose perfectly fairly among routers when choosing by bandwidth and
11137 weighting by fraction of bandwidth provided by exits. Previously, we
11138 would choose with only approximate fairness, and correct ourselves
11139 if we ran off the end of the list. [Bugfix on 0.1.2.x]
11141 o Performance improvements:
11142 - Be more aggressive with freeing buffer RAM or putting it on the
11144 - Use Critical Sections rather than Mutexes for synchronizing threads
11145 on win32; Mutexes are heavier-weight, and designed for synchronizing
11148 o Deprecated and removed features:
11149 - RedirectExits is now deprecated.
11150 - Stop allowing address masks that do not correspond to bit prefixes.
11151 We have warned about these for a really long time; now it's time
11152 to reject them. (Patch from croup.)
11154 o Minor bugfixes (directory):
11155 - Fix another crash bug related to extra-info caching. (Bug found by
11156 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
11157 - Directories no longer return a "304 not modified" when they don't
11158 have the networkstatus the client asked for. Also fix a memory
11159 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
11160 - We had accidentally labelled 0.1.2.x directory servers as not
11161 suitable for begin_dir requests, and had labelled no directory
11162 servers as suitable for uploading extra-info documents. [Bugfix
11165 o Minor bugfixes (dns):
11166 - Fix a crash when DNSPort is set more than once. (Patch from Robert
11167 Hogan.) [Bugfix on 0.2.0.2-alpha]
11168 - Add DNSPort connections to the global connection list, so that we
11169 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
11171 - Fix a dangling reference that could lead to a crash when DNSPort is
11172 changed or closed (Patch from Robert Hogan.) [Bugfix on
11175 o Minor bugfixes (controller):
11176 - Provide DNS expiry times in GMT, not in local time. For backward
11177 compatibility, ADDRMAP events only provide GMT expiry in an extended
11178 field. "GETINFO address-mappings" always does the right thing.
11179 - Use CRLF line endings properly in NS events.
11180 - Terminate multi-line control events properly. (Original patch
11181 from tup.) [Bugfix on 0.1.2.x-alpha]
11182 - Do not include spaces in SOURCE_ADDR fields in STREAM
11183 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
11186 Changes in version 0.1.2.15 - 2007-07-17
11187 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
11188 problems, fixes compilation on BSD, and fixes a variety of other
11189 bugs. Everybody should upgrade.
11191 o Major bugfixes (compilation):
11192 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
11194 o Major bugfixes (crashes):
11195 - Try even harder not to dereference the first character after
11196 an mmap(). Reported by lodger.
11197 - Fix a crash bug in directory authorities when we re-number the
11198 routerlist while inserting a new router.
11199 - When the cached-routers file is an even multiple of the page size,
11200 don't run off the end and crash. (Fixes bug 455; based on idea
11202 - Fix eventdns.c behavior on Solaris: It is critical to include
11203 orconfig.h _before_ sys/types.h, so that we can get the expected
11204 definition of _FILE_OFFSET_BITS.
11206 o Major bugfixes (security):
11207 - Fix a possible buffer overrun when using BSD natd support. Bug
11209 - When sending destroy cells from a circuit's origin, don't include
11210 the reason for tearing down the circuit. The spec says we didn't,
11211 and now we actually don't. Reported by lodger.
11212 - Keep streamids from different exits on a circuit separate. This
11213 bug may have allowed other routers on a given circuit to inject
11214 cells into streams. Reported by lodger; fixes bug 446.
11215 - If there's a never-before-connected-to guard node in our list,
11216 never choose any guards past it. This way we don't expand our
11217 guard list unless we need to.
11219 o Minor bugfixes (guard nodes):
11220 - Weight guard selection by bandwidth, so that low-bandwidth nodes
11221 don't get overused as guards.
11223 o Minor bugfixes (directory):
11224 - Correctly count the number of authorities that recommend each
11225 version. Previously, we were under-counting by 1.
11226 - Fix a potential crash bug when we load many server descriptors at
11227 once and some of them make others of them obsolete. Fixes bug 458.
11229 o Minor bugfixes (hidden services):
11230 - Stop tearing down the whole circuit when the user asks for a
11231 connection to a port that the hidden service didn't configure.
11234 o Minor bugfixes (misc):
11235 - On Windows, we were preventing other processes from reading
11236 cached-routers while Tor was running. Reported by janbar.
11237 - Fix a possible (but very unlikely) bug in picking routers by
11238 bandwidth. Add a log message to confirm that it is in fact
11239 unlikely. Patch from lodger.
11240 - Backport a couple of memory leak fixes.
11241 - Backport miscellaneous cosmetic bugfixes.
11244 Changes in version 0.2.0.2-alpha - 2007-06-02
11245 o Major bugfixes on 0.2.0.1-alpha:
11246 - Fix an assertion failure related to servers without extra-info digests.
11247 Resolves bugs 441 and 442.
11249 o Minor features (directory):
11250 - Support "If-Modified-Since" when answering HTTP requests for
11251 directories, running-routers documents, and network-status documents.
11252 (There's no need to support it for router descriptors, since those
11253 are downloaded by descriptor digest.)
11255 o Minor build issues:
11256 - Clear up some MIPSPro compiler warnings.
11257 - When building from a tarball on a machine that happens to have SVK
11258 installed, report the micro-revision as whatever version existed
11259 in the tarball, not as "x".
11262 Changes in version 0.2.0.1-alpha - 2007-06-01
11263 This early development snapshot provides new features for people running
11264 Tor as both a client and a server (check out the new RelayBandwidth
11265 config options); lets Tor run as a DNS proxy; and generally moves us
11266 forward on a lot of fronts.
11268 o Major features, server usability:
11269 - New config options RelayBandwidthRate and RelayBandwidthBurst:
11270 a separate set of token buckets for relayed traffic. Right now
11271 relayed traffic is defined as answers to directory requests, and
11272 OR connections that don't have any local circuits on them.
11274 o Major features, client usability:
11275 - A client-side DNS proxy feature to replace the need for
11276 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
11277 for DNS requests on port 9999, use the Tor network to resolve them
11278 anonymously, and send the reply back like a regular DNS server.
11279 The code still only implements a subset of DNS.
11280 - Make PreferTunneledDirConns and TunnelDirConns work even when
11281 we have no cached directory info. This means Tor clients can now
11282 do all of their connections protected by TLS.
11284 o Major features, performance and efficiency:
11285 - Directory authorities accept and serve "extra info" documents for
11286 routers. These documents contain fields from router descriptors
11287 that aren't usually needed, and that use a lot of excess
11288 bandwidth. Once these fields are removed from router descriptors,
11289 the bandwidth savings should be about 60%. [Partially implements
11291 - Servers upload extra-info documents to any authority that accepts
11292 them. Authorities (and caches that have been configured to download
11293 extra-info documents) download them as needed. [Partially implements
11295 - Change the way that Tor buffers data that it is waiting to write.
11296 Instead of queueing data cells in an enormous ring buffer for each
11297 client->OR or OR->OR connection, we now queue cells on a separate
11298 queue for each circuit. This lets us use less slack memory, and
11299 will eventually let us be smarter about prioritizing different kinds
11301 - Use memory pools to allocate cells with better speed and memory
11302 efficiency, especially on platforms where malloc() is inefficient.
11303 - Stop reading on edge connections when their corresponding circuit
11304 buffers are full; start again as the circuits empty out.
11306 o Major features, other:
11307 - Add an HSAuthorityRecordStats option that hidden service authorities
11308 can use to track statistics of overall hidden service usage without
11309 logging information that would be very useful to an attacker.
11310 - Start work implementing multi-level keys for directory authorities:
11311 Add a standalone tool to generate key certificates. (Proposal 103.)
11314 - Directory authorities now call routers Stable if they have an
11315 uptime of at least 30 days, even if that's not the median uptime
11316 in the network. Implements proposal 107, suggested by Kevin Bauer
11319 o Minor fixes (resource management):
11320 - Count the number of open sockets separately from the number
11321 of active connection_t objects. This will let us avoid underusing
11322 our allocated connection limit.
11323 - We no longer use socket pairs to link an edge connection to an
11324 anonymous directory connection or a DirPort test connection.
11325 Instead, we track the link internally and transfer the data
11326 in-process. This saves two sockets per "linked" connection (at the
11327 client and at the server), and avoids the nasty Windows socketpair()
11329 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
11330 for every single inactive connection_t. Free items from the
11331 4k/16k-buffer free lists when they haven't been used for a while.
11333 o Minor features (build):
11334 - Make autoconf search for libevent, openssl, and zlib consistently.
11335 - Update deprecated macros in configure.in.
11336 - When warning about missing headers, tell the user to let us
11337 know if the compile succeeds anyway, so we can downgrade the
11339 - Include the current subversion revision as part of the version
11340 string: either fetch it directly if we're in an SVN checkout, do
11341 some magic to guess it if we're in an SVK checkout, or use
11342 the last-detected version if we're building from a .tar.gz.
11343 Use this version consistently in log messages.
11345 o Minor features (logging):
11346 - Always prepend "Bug: " to any log message about a bug.
11347 - Put a platform string (e.g. "Linux i686") in the startup log
11348 message, so when people paste just their logs, we know if it's
11349 OpenBSD or Windows or what.
11350 - When logging memory usage, break down memory used in buffers by
11353 o Minor features (directory system):
11354 - New config option V2AuthoritativeDirectory that all directory
11355 authorities should set. This will let future authorities choose
11356 not to serve V2 directory information.
11357 - Directory authorities allow multiple router descriptors and/or extra
11358 info documents to be uploaded in a single go. This will make
11359 implementing proposal 104 simpler.
11361 o Minor features (controller):
11362 - Add a new config option __DisablePredictedCircuits designed for
11363 use by the controller, when we don't want Tor to build any circuits
11365 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
11366 so we can exit from the middle of the circuit.
11367 - Implement "getinfo status/circuit-established".
11368 - Implement "getinfo status/version/..." so a controller can tell
11369 whether the current version is recommended, and whether any versions
11370 are good, and how many authorities agree. (Patch from shibz.)
11372 o Minor features (hidden services):
11373 - Allow multiple HiddenServicePort directives with the same virtual
11374 port; when they occur, the user is sent round-robin to one
11375 of the target ports chosen at random. Partially fixes bug 393 by
11376 adding limited ad-hoc round-robining.
11378 o Minor features (other):
11380 - Add a new AutomapHostsOnResolve option: when it is enabled, any
11381 resolve request for hosts matching a given pattern causes Tor to
11382 generate an internal virtual address mapping for that host. This
11383 allows DNSPort to work sensibly with hidden service users. By
11384 default, .exit and .onion addresses are remapped; the list of
11385 patterns can be reconfigured with AutomapHostsSuffixes.
11386 - Add an "-F" option to tor-resolve to force a resolve for a .onion
11387 address. Thanks to the AutomapHostsOnResolve option, this is no
11388 longer a completely silly thing to do.
11389 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
11390 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
11391 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
11392 minus 1 byte: the actual maximum declared bandwidth.
11394 o Removed features:
11395 - Removed support for the old binary "version 0" controller protocol.
11396 This has been deprecated since 0.1.1, and warnings have been issued
11397 since 0.1.2. When we encounter a v0 control message, we now send
11398 back an error and close the connection.
11399 - Remove the old "dns worker" server DNS code: it hasn't been default
11400 since 0.1.2.2-alpha, and all the servers seem to be using the new
11403 o Minor bugfixes (portability):
11404 - Even though Windows is equally happy with / and \ as path separators,
11405 try to use \ consistently on Windows and / consistently on Unix: it
11406 makes the log messages nicer.
11407 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
11408 - Read resolv.conf files correctly on platforms where read() returns
11409 partial results on small file reads.
11411 o Minor bugfixes (directory):
11412 - Correctly enforce that elements of directory objects do not appear
11413 more often than they are allowed to appear.
11414 - When we are reporting the DirServer line we just parsed, we were
11415 logging the second stanza of the key fingerprint, not the first.
11417 o Minor bugfixes (logging):
11418 - When we hit an EOF on a log (probably because we're shutting down),
11419 don't try to remove the log from the list: just mark it as
11420 unusable. (Bulletproofs against bug 222.)
11422 o Minor bugfixes (other):
11423 - In the exitlist script, only consider the most recently published
11424 server descriptor for each server. Also, when the user requests
11425 a list of servers that _reject_ connections to a given address,
11426 explicitly exclude the IPs that also have servers that accept
11427 connections to that address. (Resolves bug 405.)
11428 - Stop allowing hibernating servers to be "stable" or "fast".
11429 - On Windows, we were preventing other processes from reading
11430 cached-routers while Tor was running. (Reported by janbar)
11431 - Make the NodeFamilies config option work. (Reported by
11432 lodger -- it has never actually worked, even though we added it
11434 - Check return values from pthread_mutex functions.
11435 - Don't save non-general-purpose router descriptors to the disk cache,
11436 because we have no way of remembering what their purpose was when
11438 - Add even more asserts to hunt down bug 417.
11439 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
11440 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
11441 Add a log message to confirm that it is in fact unlikely.
11443 o Minor bugfixes (controller):
11444 - Make 'getinfo fingerprint' return a 551 error if we're not a
11445 server, so we match what the control spec claims we do. Reported
11447 - Fix a typo in an error message when extendcircuit fails that
11448 caused us to not follow the \r\n-based delimiter protocol. Reported
11451 o Code simplifications and refactoring:
11452 - Stop passing around circuit_t and crypt_path_t pointers that are
11453 implicit in other procedure arguments.
11454 - Drop the old code to choke directory connections when the
11455 corresponding OR connections got full: thanks to the cell queue
11456 feature, OR conns don't get full any more.
11457 - Make dns_resolve() handle attaching connections to circuits
11458 properly, so the caller doesn't have to.
11459 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
11460 - Keep the connection array as a dynamic smartlist_t, rather than as
11461 a fixed-sized array. This is important, as the number of connections
11462 is becoming increasingly decoupled from the number of sockets.
11465 Changes in version 0.1.2.14 - 2007-05-25
11466 Tor 0.1.2.14 changes the addresses of two directory authorities (this
11467 change especially affects those who serve or use hidden services),
11468 and fixes several other crash- and security-related bugs.
11470 o Directory authority changes:
11471 - Two directory authorities (moria1 and moria2) just moved to new
11472 IP addresses. This change will particularly affect those who serve
11473 or use hidden services.
11475 o Major bugfixes (crashes):
11476 - If a directory server runs out of space in the connection table
11477 as it's processing a begin_dir request, it will free the exit stream
11478 but leave it attached to the circuit, leading to unpredictable
11479 behavior. (Reported by seeess, fixes bug 425.)
11480 - Fix a bug in dirserv_remove_invalid() that would cause authorities
11481 to corrupt memory under some really unlikely scenarios.
11482 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
11483 - Avoid segfaults when reading from mmaped descriptor file. (Reported
11486 o Major bugfixes (security):
11487 - When choosing an entry guard for a circuit, avoid using guards
11488 that are in the same family as the chosen exit -- not just guards
11489 that are exactly the chosen exit. (Reported by lodger.)
11491 o Major bugfixes (resource management):
11492 - If a directory authority is down, skip it when deciding where to get
11493 networkstatus objects or descriptors. Otherwise we keep asking
11494 every 10 seconds forever. Fixes bug 384.
11495 - Count it as a failure if we fetch a valid network-status but we
11496 don't want to keep it. Otherwise we'll keep fetching it and keep
11497 not wanting to keep it. Fixes part of bug 422.
11498 - If all of our dirservers have given us bad or no networkstatuses
11499 lately, then stop hammering them once per minute even when we
11500 think they're failed. Fixes another part of bug 422.
11503 - Actually set the purpose correctly for descriptors inserted with
11504 purpose=controller.
11505 - When we have k non-v2 authorities in our DirServer config,
11506 we ignored the last k authorities in the list when updating our
11508 - Correctly back-off from requesting router descriptors that we are
11509 having a hard time downloading.
11510 - Read resolv.conf files correctly on platforms where read() returns
11511 partial results on small file reads.
11512 - Don't rebuild the entire router store every time we get 32K of
11513 routers: rebuild it when the journal gets very large, or when
11514 the gaps in the store get very large.
11517 - When routers publish SVN revisions in their router descriptors,
11518 authorities now include those versions correctly in networkstatus
11520 - Warn when using a version of libevent before 1.3b to run a server on
11521 OSX or BSD: these versions interact badly with userspace threads.
11524 Changes in version 0.1.2.13 - 2007-04-24
11525 This release features some major anonymity fixes, such as safer path
11526 selection; better client performance; faster bootstrapping, better
11527 address detection, and better DNS support for servers; write limiting as
11528 well as read limiting to make servers easier to run; and a huge pile of
11529 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
11531 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
11532 of the Freenode IRC network, remembering his patience and vision for
11533 free speech on the Internet.
11536 - Fix a memory leak when we ask for "all" networkstatuses and we
11537 get one we don't recognize.
11538 - Add more asserts to hunt down bug 417.
11539 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
11542 Changes in version 0.1.2.12-rc - 2007-03-16
11544 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
11545 directory information requested inside Tor connections (i.e. via
11546 begin_dir cells). It only triggered when the same connection was
11547 serving other data at the same time. Reported by seeess.
11550 - When creating a circuit via the controller, send a 'launched'
11551 event when we're done, so we follow the spec better.
11554 Changes in version 0.1.2.11-rc - 2007-03-15
11555 o Minor bugfixes (controller), reported by daejees:
11556 - Correct the control spec to match how the code actually responds
11557 to 'getinfo addr-mappings/*'.
11558 - The control spec described a GUARDS event, but the code
11559 implemented a GUARD event. Standardize on GUARD, but let people
11560 ask for GUARDS too.
11563 Changes in version 0.1.2.10-rc - 2007-03-07
11564 o Major bugfixes (Windows):
11565 - Do not load the NT services library functions (which may not exist)
11566 just to detect if we're a service trying to shut down. Now we run
11567 on Win98 and friends again.
11569 o Minor bugfixes (other):
11570 - Clarify a couple of log messages.
11571 - Fix a misleading socks5 error number.
11574 Changes in version 0.1.2.9-rc - 2007-03-02
11575 o Major bugfixes (Windows):
11576 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
11577 of the usual GCC "%llu". This prevents a bug when saving 64-bit
11578 int configuration values: the high-order 32 bits would get
11579 truncated. In particular, we were being bitten by the default
11580 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
11581 and maybe also bug 397.)
11583 o Minor bugfixes (performance):
11584 - Use OpenSSL's AES implementation on platforms where it's faster.
11585 This could save us as much as 10% CPU usage.
11587 o Minor bugfixes (server):
11588 - Do not rotate onion key immediately after setting it for the first
11591 o Minor bugfixes (directory authorities):
11592 - Stop calling servers that have been hibernating for a long time
11593 "stable". Also, stop letting hibernating or obsolete servers affect
11594 uptime and bandwidth cutoffs.
11595 - Stop listing hibernating servers in the v1 directory.
11597 o Minor bugfixes (hidden services):
11598 - Upload hidden service descriptors slightly less often, to reduce
11599 load on authorities.
11601 o Minor bugfixes (other):
11602 - Fix an assert that could trigger if a controller quickly set then
11603 cleared EntryNodes. Bug found by Udo van den Heuvel.
11604 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
11606 - Fix a potential race condition in the rpm installer. Found by
11608 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
11609 of 2 as indicating that the server is completely bad; it sometimes
11610 means that the server is just bad for the request in question. (may fix
11611 the last of bug 326.)
11612 - Disable encrypted directory connections when we don't have a server
11613 descriptor for the destination. We'll get this working again in
11617 Changes in version 0.1.2.8-beta - 2007-02-26
11618 o Major bugfixes (crashes):
11619 - Stop crashing when the controller asks us to resetconf more than
11620 one config option at once. (Vidalia 0.0.11 does this.)
11621 - Fix a crash that happened on Win98 when we're given command-line
11622 arguments: don't try to load NT service functions from advapi32.dll
11623 except when we need them. (Bug introduced in 0.1.2.7-alpha;
11625 - Fix a longstanding obscure crash bug that could occur when
11626 we run out of DNS worker processes. (Resolves bug 390.)
11628 o Major bugfixes (hidden services):
11629 - Correctly detect whether hidden service descriptor downloads are
11630 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
11632 o Major bugfixes (accounting):
11633 - When we start during an accounting interval before it's time to wake
11634 up, remember to wake up at the correct time. (May fix bug 342.)
11636 o Minor bugfixes (controller):
11637 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
11638 clear the corresponding on_circuit variable, and remember later
11639 that we don't need to send a redundant CLOSED event. Resolves part
11641 - Report events where a resolve succeeded or where we got a socks
11642 protocol error correctly, rather than calling both of them
11644 - Change reported stream target addresses to IP consistently when
11645 we finally get the IP from an exit node.
11646 - Send log messages to the controller even if they happen to be very
11649 o Minor bugfixes (other):
11650 - Display correct results when reporting which versions are
11651 recommended, and how recommended they are. (Resolves bug 383.)
11652 - Improve our estimates for directory bandwidth to be less random:
11653 guess that an unrecognized directory will have the average bandwidth
11654 from all known directories, not that it will have the average
11655 bandwidth from those directories earlier than it on the list.
11656 - If we start a server with ClientOnly 1, then set ClientOnly to 0
11657 and hup, stop triggering an assert based on an empty onion_key.
11658 - On platforms with no working mmap() equivalent, don't warn the
11659 user when cached-routers doesn't exist.
11660 - Warn the user when mmap() [or its equivalent] fails for some reason
11661 other than file-not-found.
11662 - Don't warn the user when cached-routers.new doesn't exist: that's
11663 perfectly fine when starting up for the first time.
11664 - When EntryNodes are configured, rebuild the guard list to contain,
11665 in order: the EntryNodes that were guards before; the rest of the
11666 EntryNodes; the nodes that were guards before.
11667 - Mask out all signals in sub-threads; only the libevent signal
11668 handler should be processing them. This should prevent some crashes
11669 on some machines using pthreads. (Patch from coderman.)
11670 - Fix switched arguments on memset in the implementation of
11671 tor_munmap() for systems with no mmap() call.
11672 - When Tor receives a router descriptor that it asked for, but
11673 no longer wants (because it has received fresh networkstatuses
11674 in the meantime), do not warn the user. Cache the descriptor if
11675 we're a cache; drop it if we aren't.
11676 - Make earlier entry guards _really_ get retried when the network
11678 - On a malformed DNS reply, always give an error to the corresponding
11680 - Build with recent libevents on platforms that do not define the
11681 nonstandard types "u_int8_t" and friends.
11683 o Minor features (controller):
11684 - Warn the user when an application uses the obsolete binary v0
11685 control protocol. We're planning to remove support for it during
11686 the next development series, so it's good to give people some
11688 - Add STREAM_BW events to report per-entry-stream bandwidth
11689 use. (Patch from Robert Hogan.)
11690 - Rate-limit SIGNEWNYM signals in response to controllers that
11691 impolitely generate them for every single stream. (Patch from
11692 mwenge; closes bug 394.)
11693 - Make REMAP stream events have a SOURCE (cache or exit), and
11694 make them generated in every case where we get a successful
11695 connected or resolved cell.
11697 o Minor bugfixes (performance):
11698 - Call router_have_min_dir_info half as often. (This is showing up in
11699 some profiles, but not others.)
11700 - When using GCC, make log_debug never get called at all, and its
11701 arguments never get evaluated, when no debug logs are configured.
11702 (This is showing up in some profiles, but not others.)
11705 - Remove some never-implemented options. Mark PathlenCoinWeight as
11707 - Implement proposal 106: Stop requiring clients to have well-formed
11708 certificates; stop checking nicknames in certificates. (Clients
11709 have certificates so that they can look like Tor servers, but in
11710 the future we might want to allow them to look like regular TLS
11711 clients instead. Nicknames in certificates serve no purpose other
11712 than making our protocol easier to recognize on the wire.)
11713 - Revise messages on handshake failure again to be even more clear about
11714 which are incoming connections and which are outgoing.
11715 - Discard any v1 directory info that's over 1 month old (for
11716 directories) or over 1 week old (for running-routers lists).
11717 - Do not warn when individual nodes in the configuration's EntryNodes,
11718 ExitNodes, etc are down: warn only when all possible nodes
11719 are down. (Fixes bug 348.)
11720 - Always remove expired routers and networkstatus docs before checking
11721 whether we have enough information to build circuits. (Fixes
11723 - Put a lower-bound on MaxAdvertisedBandwidth.
11726 Changes in version 0.1.2.7-alpha - 2007-02-06
11727 o Major bugfixes (rate limiting):
11728 - Servers decline directory requests much more aggressively when
11729 they're low on bandwidth. Otherwise they end up queueing more and
11730 more directory responses, which can't be good for latency.
11731 - But never refuse directory requests from local addresses.
11732 - Fix a memory leak when sending a 503 response for a networkstatus
11734 - Be willing to read or write on local connections (e.g. controller
11735 connections) even when the global rate limiting buckets are empty.
11736 - If our system clock jumps back in time, don't publish a negative
11737 uptime in the descriptor. Also, don't let the global rate limiting
11738 buckets go absurdly negative.
11739 - Flush local controller connection buffers periodically as we're
11740 writing to them, so we avoid queueing 4+ megabytes of data before
11743 o Major bugfixes (NT services):
11744 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
11745 command-line flag so that admins can override the default by saying
11746 "tor --service install --user "SomeUser"". This will not affect
11747 existing installed services. Also, warn the user that the service
11748 will look for its configuration file in the service user's
11749 %appdata% directory. (We can't do the 'hardwire the user's appdata
11750 directory' trick any more, since we may not have read access to that
11753 o Major bugfixes (other):
11754 - Previously, we would cache up to 16 old networkstatus documents
11755 indefinitely, if they came from nontrusted authorities. Now we
11756 discard them if they are more than 10 days old.
11757 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
11759 - Detect and reject malformed DNS responses containing circular
11761 - If exits are rare enough that we're not marking exits as guards,
11762 ignore exit bandwidth when we're deciding the required bandwidth
11764 - When we're handling a directory connection tunneled over Tor,
11765 don't fill up internal memory buffers with all the data we want
11766 to tunnel; instead, only add it if the OR connection that will
11767 eventually receive it has some room for it. (This can lead to
11768 slowdowns in tunneled dir connections; a better solution will have
11769 to wait for 0.2.0.)
11771 o Minor bugfixes (dns):
11772 - Add some defensive programming to eventdns.c in an attempt to catch
11773 possible memory-stomping bugs.
11774 - Detect and reject DNS replies containing IPv4 or IPv6 records with
11775 an incorrect number of bytes. (Previously, we would ignore the
11777 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
11778 in the correct order, and doesn't crash.
11779 - Free memory held in recently-completed DNS lookup attempts on exit.
11780 This was not a memory leak, but may have been hiding memory leaks.
11781 - Handle TTL values correctly on reverse DNS lookups.
11782 - Treat failure to parse resolv.conf as an error.
11784 o Minor bugfixes (other):
11785 - Fix crash with "tor --list-fingerprint" (reported by seeess).
11786 - When computing clock skew from directory HTTP headers, consider what
11787 time it was when we finished asking for the directory, not what
11789 - Expire socks connections if they spend too long waiting for the
11790 handshake to finish. Previously we would let them sit around for
11791 days, if the connecting application didn't close them either.
11792 - And if the socks handshake hasn't started, don't send a
11793 "DNS resolve socks failed" handshake reply; just close it.
11794 - Stop using C functions that OpenBSD's linker doesn't like.
11795 - Don't launch requests for descriptors unless we have networkstatuses
11796 from at least half of the authorities. This delays the first
11797 download slightly under pathological circumstances, but can prevent
11798 us from downloading a bunch of descriptors we don't need.
11799 - Do not log IPs with TLS failures for incoming TLS
11800 connections. (Fixes bug 382.)
11801 - If the user asks to use invalid exit nodes, be willing to use
11803 - Stop using the reserved ac_cv namespace in our configure script.
11804 - Call stat() slightly less often; use fstat() when possible.
11805 - Refactor the way we handle pending circuits when an OR connection
11806 completes or fails, in an attempt to fix a rare crash bug.
11807 - Only rewrite a conn's address based on X-Forwarded-For: headers
11808 if it's a parseable public IP address; and stop adding extra quotes
11809 to the resulting address.
11812 - Weight directory requests by advertised bandwidth. Now we can
11813 let servers enable write limiting but still allow most clients to
11814 succeed at their directory requests. (We still ignore weights when
11815 choosing a directory authority; I hope this is a feature.)
11818 - Create a new file ReleaseNotes which was the old ChangeLog. The
11819 new ChangeLog file now includes the summaries for all development
11821 - Check for addresses with invalid characters at the exit as well
11822 as at the client, and warn less verbosely when they fail. You can
11823 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
11824 - Adapt a patch from goodell to let the contrib/exitlist script
11825 take arguments rather than require direct editing.
11826 - Inform the server operator when we decide not to advertise a
11827 DirPort due to AccountingMax enabled or a low BandwidthRate. It
11828 was confusing Zax, so now we're hopefully more helpful.
11829 - Bring us one step closer to being able to establish an encrypted
11830 directory tunnel without knowing a descriptor first. Still not
11831 ready yet. As part of the change, now assume we can use a
11832 create_fast cell if we don't know anything about a router.
11833 - Allow exit nodes to use nameservers running on ports other than 53.
11834 - Servers now cache reverse DNS replies.
11835 - Add an --ignore-missing-torrc command-line option so that we can
11836 get the "use sensible defaults if the configuration file doesn't
11837 exist" behavior even when specifying a torrc location on the command
11840 o Minor features (controller):
11841 - Track reasons for OR connection failure; make these reasons
11842 available via the controller interface. (Patch from Mike Perry.)
11843 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
11844 can learn when clients are sending malformed hostnames to Tor.
11845 - Clean up documentation for controller status events.
11846 - Add a REMAP status to stream events to note that a stream's
11847 address has changed because of a cached address or a MapAddress
11851 Changes in version 0.1.2.6-alpha - 2007-01-09
11853 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
11854 connection handles more than 4 gigs in either direction, we crash.
11855 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
11856 advertised exit node, somebody might try to exit from us when
11857 we're bootstrapping and before we've built our descriptor yet.
11858 Refuse the connection rather than crashing.
11861 - Warn if we (as a server) find that we've resolved an address that we
11862 weren't planning to resolve.
11863 - Warn that using select() on any libevent version before 1.1 will be
11864 unnecessarily slow (even for select()).
11865 - Flush ERR-level controller status events just like we currently
11866 flush ERR-level log events, so that a Tor shutdown doesn't prevent
11867 the controller from learning about current events.
11869 o Minor features (more controller status events):
11870 - Implement EXTERNAL_ADDRESS server status event so controllers can
11871 learn when our address changes.
11872 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
11873 can learn when directories reject our descriptor.
11874 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
11875 can learn when a client application is speaking a non-socks protocol
11877 - Implement DANGEROUS_SOCKS client status event so controllers
11878 can learn when a client application is leaking DNS addresses.
11879 - Implement BUG general status event so controllers can learn when
11880 Tor is unhappy about its internal invariants.
11881 - Implement CLOCK_SKEW general status event so controllers can learn
11882 when Tor thinks the system clock is set incorrectly.
11883 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
11884 server status events so controllers can learn when their descriptors
11885 are accepted by a directory.
11886 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
11887 server status events so controllers can learn about Tor's progress in
11888 deciding whether it's reachable from the outside.
11889 - Implement BAD_LIBEVENT general status event so controllers can learn
11890 when we have a version/method combination in libevent that needs to
11892 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
11893 and DNS_USELESS server status events so controllers can learn
11894 about changes to DNS server status.
11896 o Minor features (directory):
11897 - Authorities no longer recommend exits as guards if this would shift
11898 too much load to the exit nodes.
11901 Changes in version 0.1.2.5-alpha - 2007-01-06
11903 - Enable write limiting as well as read limiting. Now we sacrifice
11904 capacity if we're pushing out lots of directory traffic, rather
11905 than overrunning the user's intended bandwidth limits.
11906 - Include TLS overhead when counting bandwidth usage; previously, we
11907 would count only the bytes sent over TLS, but not the bytes used
11909 - Support running the Tor service with a torrc not in the same
11910 directory as tor.exe and default to using the torrc located in
11911 the %appdata%\Tor\ of the user who installed the service. Patch
11913 - Servers now check for the case when common DNS requests are going to
11914 wildcarded addresses (i.e. all getting the same answer), and change
11915 their exit policy to reject *:* if it's happening.
11916 - Implement BEGIN_DIR cells, so we can connect to the directory
11917 server via TLS to do encrypted directory requests rather than
11918 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
11919 config options if you like.
11921 o Minor features (config and docs):
11922 - Start using the state file to store bandwidth accounting data:
11923 the bw_accounting file is now obsolete. We'll keep generating it
11924 for a while for people who are still using 0.1.2.4-alpha.
11925 - Try to batch changes to the state file so that we do as few
11926 disk writes as possible while still storing important things in
11928 - The state file and the bw_accounting file get saved less often when
11929 the AvoidDiskWrites config option is set.
11930 - Make PIDFile work on Windows (untested).
11931 - Add internal descriptions for a bunch of configuration options:
11932 accessible via controller interface and in comments in saved
11934 - Reject *:563 (NNTPS) in the default exit policy. We already reject
11935 NNTP by default, so this seems like a sensible addition.
11936 - Clients now reject hostnames with invalid characters. This should
11937 avoid some inadvertent info leaks. Add an option
11938 AllowNonRFC953Hostnames to disable this behavior, in case somebody
11939 is running a private network with hosts called @, !, and #.
11940 - Add a maintainer script to tell us which options are missing
11941 documentation: "make check-docs".
11942 - Add a new address-spec.txt document to describe our special-case
11943 addresses: .exit, .onion, and .noconnnect.
11945 o Minor features (DNS):
11946 - Ongoing work on eventdns infrastructure: now it has dns server
11947 and ipv6 support. One day Tor will make use of it.
11948 - Add client-side caching for reverse DNS lookups.
11949 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
11950 - When we change nameservers or IP addresses, reset and re-launch
11951 our tests for DNS hijacking.
11953 o Minor features (directory):
11954 - Authorities now specify server versions in networkstatus. This adds
11955 about 2% to the size of compressed networkstatus docs, and allows
11956 clients to tell which servers support BEGIN_DIR and which don't.
11957 The implementation is forward-compatible with a proposed future
11958 protocol version scheme not tied to Tor versions.
11959 - DirServer configuration lines now have an orport= option so
11960 clients can open encrypted tunnels to the authorities without
11961 having downloaded their descriptors yet. Enabled for moria1,
11962 moria2, tor26, and lefkada now in the default configuration.
11963 - Directory servers are more willing to send a 503 "busy" if they
11964 are near their write limit, especially for v1 directory requests.
11965 Now they can use their limited bandwidth for actual Tor traffic.
11966 - Clients track responses with status 503 from dirservers. After a
11967 dirserver has given us a 503, we try not to use it until an hour has
11968 gone by, or until we have no dirservers that haven't given us a 503.
11969 - When we get a 503 from a directory, and we're not a server, we don't
11970 count the failure against the total number of failures allowed
11971 for the thing we're trying to download.
11972 - Report X-Your-Address-Is correctly from tunneled directory
11973 connections; don't report X-Your-Address-Is when it's an internal
11974 address; and never believe reported remote addresses when they're
11976 - Protect against an unlikely DoS attack on directory servers.
11977 - Add a BadDirectory flag to network status docs so that authorities
11978 can (eventually) tell clients about caches they believe to be
11981 o Minor features (controller):
11982 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
11983 - Reimplement GETINFO so that info/names stays in sync with the
11985 - Implement "GETINFO fingerprint".
11986 - Implement "SETEVENTS GUARD" so controllers can get updates on
11987 entry guard status as it changes.
11989 o Minor features (clean up obsolete pieces):
11990 - Remove some options that have been deprecated since at least
11991 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
11992 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
11993 to set log options.
11994 - We no longer look for identity and onion keys in "identity.key" and
11995 "onion.key" -- these were replaced by secret_id_key and
11996 secret_onion_key in 0.0.8pre1.
11997 - We no longer require unrecognized directory entries to be
12000 o Major bugfixes (security):
12001 - Stop sending the HttpProxyAuthenticator string to directory
12002 servers when directory connections are tunnelled through Tor.
12003 - Clients no longer store bandwidth history in the state file.
12004 - Do not log introduction points for hidden services if SafeLogging
12006 - When generating bandwidth history, round down to the nearest
12007 1k. When storing accounting data, round up to the nearest 1k.
12008 - When we're running as a server, remember when we last rotated onion
12009 keys, so that we will rotate keys once they're a week old even if
12010 we never stay up for a week ourselves.
12012 o Major bugfixes (other):
12013 - Fix a longstanding bug in eventdns that prevented the count of
12014 timed-out resolves from ever being reset. This bug caused us to
12015 give up on a nameserver the third time it timed out, and try it
12016 10 seconds later... and to give up on it every time it timed out
12018 - Take out the '5 second' timeout from the connection retry
12019 schedule. Now the first connect attempt will wait a full 10
12020 seconds before switching to a new circuit. Perhaps this will help
12021 a lot. Based on observations from Mike Perry.
12022 - Fix a bug on the Windows implementation of tor_mmap_file() that
12023 would prevent the cached-routers file from ever loading. Reported
12027 - Fix an assert failure when a directory authority sets
12028 AuthDirRejectUnlisted and then receives a descriptor from an
12029 unlisted router. Reported by seeess.
12030 - Avoid a double-free when parsing malformed DirServer lines.
12031 - Fix a bug when a BSD-style PF socket is first used. Patch from
12033 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
12034 to resolve an address at a given exit node even when they ask for
12036 - Servers no longer ever list themselves in their "family" line,
12037 even if configured to do so. This makes it easier to configure
12038 family lists conveniently.
12039 - When running as a server, don't fall back to 127.0.0.1 when no
12040 nameservers are configured in /etc/resolv.conf; instead, make the
12041 user fix resolv.conf or specify nameservers explicitly. (Resolves
12043 - Stop accepting certain malformed ports in configured exit policies.
12044 - Don't re-write the fingerprint file every restart, unless it has
12046 - Stop warning when a single nameserver fails: only warn when _all_ of
12047 our nameservers have failed. Also, when we only have one nameserver,
12048 raise the threshold for deciding that the nameserver is dead.
12049 - Directory authorities now only decide that routers are reachable
12050 if their identity keys are as expected.
12051 - When the user uses bad syntax in the Log config line, stop
12052 suggesting other bad syntax as a replacement.
12053 - Correctly detect ipv6 DNS capability on OpenBSD.
12055 o Minor bugfixes (controller):
12056 - Report the circuit number correctly in STREAM CLOSED events. Bug
12057 reported by Mike Perry.
12058 - Do not report bizarre values for results of accounting GETINFOs
12059 when the last second's write or read exceeds the allotted bandwidth.
12060 - Report "unrecognized key" rather than an empty string when the
12061 controller tries to fetch a networkstatus that doesn't exist.
12064 Changes in version 0.1.1.26 - 2006-12-14
12065 o Security bugfixes:
12066 - Stop sending the HttpProxyAuthenticator string to directory
12067 servers when directory connections are tunnelled through Tor.
12068 - Clients no longer store bandwidth history in the state file.
12069 - Do not log introduction points for hidden services if SafeLogging
12073 - Fix an assert failure when a directory authority sets
12074 AuthDirRejectUnlisted and then receives a descriptor from an
12075 unlisted router (reported by seeess).
12078 Changes in version 0.1.2.4-alpha - 2006-12-03
12080 - Add support for using natd; this allows FreeBSDs earlier than
12081 5.1.2 to have ipfw send connections through Tor without using
12082 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
12085 - Make all connections to addresses of the form ".noconnect"
12086 immediately get closed. This lets application/controller combos
12087 successfully test whether they're talking to the same Tor by
12088 watching for STREAM events.
12089 - Make cross.sh cross-compilation script work even when autogen.sh
12090 hasn't been run. (Patch from Michael Mohr.)
12091 - Statistics dumped by -USR2 now include a breakdown of public key
12092 operations, for profiling.
12095 - Fix a major leak when directory authorities parse their
12096 approved-routers list, a minor memory leak when we fail to pick
12097 an exit node, and a few rare leaks on errors.
12098 - Handle TransPort connections even when the server sends data before
12099 the client sends data. Previously, the connection would just hang
12100 until the client sent data. (Patch from tup based on patch from
12102 - Avoid assert failure when our cached-routers file is empty on
12106 - Don't log spurious warnings when we see a circuit close reason we
12107 don't recognize; it's probably just from a newer version of Tor.
12108 - Have directory authorities allow larger amounts of drift in uptime
12109 without replacing the server descriptor: previously, a server that
12110 restarted every 30 minutes could have 48 "interesting" descriptors
12112 - Start linking to the Tor specification and Tor reference manual
12113 correctly in the Windows installer.
12114 - Add Vidalia to the OS X uninstaller script, so when we uninstall
12115 Tor/Privoxy we also uninstall Vidalia.
12116 - Resume building on Irix64, and fix a lot of warnings from its
12117 MIPSpro C compiler.
12118 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
12119 when we're running as a client.
12122 Changes in version 0.1.1.25 - 2006-11-04
12124 - When a client asks us to resolve (rather than connect to)
12125 an address, and we have a cached answer, give them the cached
12126 answer. Previously, we would give them no answer at all.
12127 - We were building exactly the wrong circuits when we predict
12128 hidden service requirements, meaning Tor would have to build all
12129 its circuits on demand.
12130 - If none of our live entry guards have a high uptime, but we
12131 require a guard with a high uptime, try adding a new guard before
12132 we give up on the requirement. This patch should make long-lived
12133 connections more stable on average.
12134 - When testing reachability of our DirPort, don't launch new
12135 tests when there's already one in progress -- unreachable
12136 servers were stacking up dozens of testing streams.
12138 o Security bugfixes:
12139 - When the user sends a NEWNYM signal, clear the client-side DNS
12140 cache too. Otherwise we continue to act on previous information.
12143 - Avoid a memory corruption bug when creating a hash table for
12145 - Avoid possibility of controller-triggered crash when misusing
12146 certain commands from a v0 controller on platforms that do not
12147 handle printf("%s",NULL) gracefully.
12148 - Avoid infinite loop on unexpected controller input.
12149 - Don't log spurious warnings when we see a circuit close reason we
12150 don't recognize; it's probably just from a newer version of Tor.
12151 - Add Vidalia to the OS X uninstaller script, so when we uninstall
12152 Tor/Privoxy we also uninstall Vidalia.
12155 Changes in version 0.1.2.3-alpha - 2006-10-29
12157 - Prepare for servers to publish descriptors less often: never
12158 discard a descriptor simply for being too old until either it is
12159 recommended by no authorities, or until we get a better one for
12160 the same router. Make caches consider retaining old recommended
12161 routers for even longer.
12162 - If most authorities set a BadExit flag for a server, clients
12163 don't think of it as a general-purpose exit. Clients only consider
12164 authorities that advertise themselves as listing bad exits.
12165 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
12166 headers for content, so that we can work better in the presence of
12167 caching HTTP proxies.
12168 - Allow authorities to list nodes as bad exits by fingerprint or by
12171 o Minor features, controller:
12172 - Add a REASON field to CIRC events; for backward compatibility, this
12173 field is sent only to controllers that have enabled the extended
12174 event format. Also, add additional reason codes to explain why
12175 a given circuit has been destroyed or truncated. (Patches from
12177 - Add a REMOTE_REASON field to extended CIRC events to tell the
12178 controller about why a remote OR told us to close a circuit.
12179 - Stream events also now have REASON and REMOTE_REASON fields,
12180 working much like those for circuit events.
12181 - There's now a GETINFO ns/... field so that controllers can ask Tor
12182 about the current status of a router.
12183 - A new event type "NS" to inform a controller when our opinion of
12184 a router's status has changed.
12185 - Add a GETINFO events/names and GETINFO features/names so controllers
12186 can tell which events and features are supported.
12187 - A new CLEARDNSCACHE signal to allow controllers to clear the
12188 client-side DNS cache without expiring circuits.
12190 o Security bugfixes:
12191 - When the user sends a NEWNYM signal, clear the client-side DNS
12192 cache too. Otherwise we continue to act on previous information.
12195 - Avoid sending junk to controllers or segfaulting when a controller
12196 uses EVENT_NEW_DESC with verbose nicknames.
12197 - Stop triggering asserts if the controller tries to extend hidden
12198 service circuits (reported by mwenge).
12199 - Avoid infinite loop on unexpected controller input.
12200 - When the controller does a "GETINFO network-status", tell it
12201 about even those routers whose descriptors are very old, and use
12202 long nicknames where appropriate.
12203 - Change NT service functions to be loaded on demand. This lets us
12204 build with MinGW without breaking Tor for Windows 98 users.
12205 - Do DirPort reachability tests less often, since a single test
12206 chews through many circuits before giving up.
12207 - In the hidden service example in torrc.sample, stop recommending
12208 esoteric and discouraged hidden service options.
12209 - When stopping an NT service, wait up to 10 sec for it to actually
12210 stop. Patch from Matt Edman; resolves bug 295.
12211 - Fix handling of verbose nicknames with ORCONN controller events:
12212 make them show up exactly when requested, rather than exactly when
12214 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
12215 printing a duplicate "$" in the keys we send (reported by mwenge).
12216 - Correctly set maximum connection limit on Cygwin. (This time
12218 - Try to detect Windows correctly when cross-compiling.
12219 - Detect the size of the routers file correctly even if it is
12220 corrupted (on systems without mmap) or not page-aligned (on systems
12221 with mmap). This bug was harmless.
12222 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
12223 to open a stream fails; now we do in more cases. This should
12224 make clients able to find a good exit faster in some cases, since
12225 unhandleable requests will now get an error rather than timing out.
12226 - Resolve two memory leaks when rebuilding the on-disk router cache
12227 (reported by fookoowa).
12228 - Clean up minor code warnings suggested by the MIPSpro C compiler,
12229 and reported by some Centos users.
12230 - Controller signals now work on non-Unix platforms that don't define
12231 SIGUSR1 and SIGUSR2 the way we expect.
12232 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
12233 values before failing, and always enables eventdns.
12234 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
12235 Try to fix this in configure.in by checking for most functions
12236 before we check for libevent.
12239 Changes in version 0.1.2.2-alpha - 2006-10-07
12241 - Make our async eventdns library on-by-default for Tor servers,
12242 and plan to deprecate the separate dnsworker threads.
12243 - Add server-side support for "reverse" DNS lookups (using PTR
12244 records so clients can determine the canonical hostname for a given
12245 IPv4 address). Only supported by servers using eventdns; servers
12246 now announce in their descriptors whether they support eventdns.
12247 - Specify and implement client-side SOCKS5 interface for reverse DNS
12248 lookups (see doc/socks-extensions.txt).
12249 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
12250 connect to directory servers through Tor. Previously, clients needed
12251 to find Tor exits to make private connections to directory servers.
12252 - Avoid choosing Exit nodes for entry or middle hops when the
12253 total bandwidth available from non-Exit nodes is much higher than
12254 the total bandwidth available from Exit nodes.
12255 - Workaround for name servers (like Earthlink's) that hijack failing
12256 DNS requests and replace the no-such-server answer with a "helpful"
12257 redirect to an advertising-driven search portal. Also work around
12258 DNS hijackers who "helpfully" decline to hijack known-invalid
12259 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
12260 lets you turn it off.
12261 - Send out a burst of long-range padding cells once we've established
12262 that we're reachable. Spread them over 4 circuits, so hopefully
12263 a few will be fast. This exercises our bandwidth and bootstraps
12264 us into the directory more quickly.
12266 o New/improved config options:
12267 - Add new config option "ResolvConf" to let the server operator
12268 choose an alternate resolve.conf file when using eventdns.
12269 - Add an "EnforceDistinctSubnets" option to control our "exclude
12270 servers on the same /16" behavior. It's still on by default; this
12271 is mostly for people who want to operate private test networks with
12272 all the machines on the same subnet.
12273 - If one of our entry guards is on the ExcludeNodes list, or the
12274 directory authorities don't think it's a good guard, treat it as
12275 if it were unlisted: stop using it as a guard, and throw it off
12276 the guards list if it stays that way for a long time.
12277 - Allow directory authorities to be marked separately as authorities
12278 for the v1 directory protocol, the v2 directory protocol, and
12279 as hidden service directories, to make it easier to retire old
12280 authorities. V1 authorities should set "HSAuthoritativeDir 1"
12281 to continue being hidden service authorities too.
12282 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
12284 o Minor features, controller:
12285 - Fix CIRC controller events so that controllers can learn the
12286 identity digests of non-Named servers used in circuit paths.
12287 - Let controllers ask for more useful identifiers for servers. Instead
12288 of learning identity digests for un-Named servers and nicknames
12289 for Named servers, the new identifiers include digest, nickname,
12290 and indication of Named status. Off by default; see control-spec.txt
12291 for more information.
12292 - Add a "getinfo address" controller command so it can display Tor's
12293 best guess to the user.
12294 - New controller event to alert the controller when our server
12295 descriptor has changed.
12296 - Give more meaningful errors on controller authentication failure.
12298 o Minor features, other:
12299 - When asked to resolve a hostname, don't use non-exit servers unless
12300 requested to do so. This allows servers with broken DNS to be
12301 useful to the network.
12302 - Divide eventdns log messages into warn and info messages.
12303 - Reserve the nickname "Unnamed" for routers that can't pick
12304 a hostname: any router can call itself Unnamed; directory
12305 authorities will never allocate Unnamed to any particular router;
12306 clients won't believe that any router is the canonical Unnamed.
12307 - Only include function names in log messages for info/debug messages.
12308 For notice/warn/err, the content of the message should be clear on
12309 its own, and printing the function name only confuses users.
12310 - Avoid some false positives during reachability testing: don't try
12311 to test via a server that's on the same /24 as us.
12312 - If we fail to build a circuit to an intended enclave, and it's
12313 not mandatory that we use that enclave, stop wanting it.
12314 - When eventdns is enabled, allow multithreaded builds on NetBSD and
12315 OpenBSD. (We had previously disabled threads on these platforms
12316 because they didn't have working thread-safe resolver functions.)
12318 o Major bugfixes, anonymity/security:
12319 - If a client asked for a server by name, and there's a named server
12320 in our network-status but we don't have its descriptor yet, we
12321 could return an unnamed server instead.
12322 - Fix NetBSD bug that could allow someone to force uninitialized RAM
12323 to be sent to a server's DNS resolver. This only affects NetBSD
12324 and other platforms that do not bounds-check tolower().
12325 - Reject (most) attempts to use Tor circuits with length one. (If
12326 many people start using Tor as a one-hop proxy, exit nodes become
12327 a more attractive target for compromise.)
12328 - Just because your DirPort is open doesn't mean people should be
12329 able to remotely teach you about hidden service descriptors. Now
12330 only accept rendezvous posts if you've got HSAuthoritativeDir set.
12332 o Major bugfixes, other:
12333 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
12334 - When a client asks the server to resolve (not connect to)
12335 an address, and it has a cached answer, give them the cached answer.
12336 Previously, the server would give them no answer at all.
12337 - Allow really slow clients to not hang up five minutes into their
12338 directory downloads (suggested by Adam J. Richter).
12339 - We were building exactly the wrong circuits when we anticipated
12340 hidden service requirements, meaning Tor would have to build all
12341 its circuits on demand.
12342 - Avoid crashing when we mmap a router cache file of size 0.
12343 - When testing reachability of our DirPort, don't launch new
12344 tests when there's already one in progress -- unreachable
12345 servers were stacking up dozens of testing streams.
12347 o Minor bugfixes, correctness:
12348 - If we're a directory mirror and we ask for "all" network status
12349 documents, we would discard status documents from authorities
12350 we don't recognize.
12351 - Avoid a memory corruption bug when creating a hash table for
12353 - Avoid controller-triggered crash when misusing certain commands
12354 from a v0 controller on platforms that do not handle
12355 printf("%s",NULL) gracefully.
12356 - Don't crash when a controller sends a third argument to an
12357 "extendcircuit" request.
12358 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12359 response; fix error code when "getinfo dir/status/" fails.
12360 - Avoid crash when telling controller stream-status and a stream
12362 - Patch from Adam Langley to fix assert() in eventdns.c.
12363 - Fix a debug log message in eventdns to say "X resolved to Y"
12364 instead of "X resolved to X".
12365 - Make eventdns give strings for DNS errors, not just error numbers.
12366 - Track unreachable entry guards correctly: don't conflate
12367 'unreachable by us right now' with 'listed as down by the directory
12368 authorities'. With the old code, if a guard was unreachable by
12369 us but listed as running, it would clog our guard list forever.
12370 - Behave correctly in case we ever have a network with more than
12371 2GB/s total advertised capacity.
12372 - Make TrackExitHosts case-insensitive, and fix the behavior of
12373 ".suffix" TrackExitHosts items to avoid matching in the middle of
12375 - Finally fix the openssl warnings from newer gccs that believe that
12376 ignoring a return value is okay, but casting a return value and
12377 then ignoring it is a sign of madness.
12378 - Prevent the contrib/exitlist script from printing the same
12379 result more than once.
12380 - Patch from Steve Hildrey: Generate network status correctly on
12381 non-versioning dirservers.
12382 - Don't listen to the X-Your-Address-Is hint if you did the lookup
12383 via Tor; otherwise you'll think you're the exit node's IP address.
12385 o Minor bugfixes, performance:
12386 - Two small performance improvements on parsing descriptors.
12387 - Major performance improvement on inserting descriptors: change
12388 algorithm from O(n^2) to O(n).
12389 - Make the common memory allocation path faster on machines where
12390 malloc(0) returns a pointer.
12391 - Start remembering X-Your-Address-Is directory hints even if you're
12392 a client, so you can become a server more smoothly.
12393 - Avoid duplicate entries on MyFamily line in server descriptor.
12395 o Packaging, features:
12396 - Remove architecture from OS X builds. The official builds are
12397 now universal binaries.
12398 - The Debian package now uses --verify-config when (re)starting,
12399 to distinguish configuration errors from other errors.
12400 - Update RPMs to require libevent 1.1b.
12402 o Packaging, bugfixes:
12403 - Patches so Tor builds with MinGW on Windows.
12404 - Patches so Tor might run on Cygwin again.
12405 - Resume building on non-gcc compilers and ancient gcc. Resume
12406 building with the -O0 compile flag. Resume building cleanly on
12408 - Run correctly on OS X platforms with case-sensitive filesystems.
12409 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
12410 - Add autoconf checks so Tor can build on Solaris x86 again.
12413 - Documented (and renamed) ServerDNSSearchDomains and
12414 ServerDNSResolvConfFile options.
12415 - Be clearer that the *ListenAddress directives can be repeated
12419 Changes in version 0.1.1.24 - 2006-09-29
12421 - Allow really slow clients to not hang up five minutes into their
12422 directory downloads (suggested by Adam J. Richter).
12423 - Fix major performance regression from 0.1.0.x: instead of checking
12424 whether we have enough directory information every time we want to
12425 do something, only check when the directory information has changed.
12426 This should improve client CPU usage by 25-50%.
12427 - Don't crash if, after a server has been running for a while,
12428 it can't resolve its hostname.
12431 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12432 - Don't crash when the controller receives a third argument to an
12433 "extendcircuit" request.
12434 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12435 response; fix error code when "getinfo dir/status/" fails.
12436 - Fix configure.in to not produce broken configure files with
12437 more recent versions of autoconf. Thanks to Clint for his auto*
12439 - Fix security bug on NetBSD that could allow someone to force
12440 uninitialized RAM to be sent to a server's DNS resolver. This
12441 only affects NetBSD and other platforms that do not bounds-check
12443 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
12444 methods: these are known to be buggy.
12445 - If we're a directory mirror and we ask for "all" network status
12446 documents, we would discard status documents from authorities
12447 we don't recognize.
12450 Changes in version 0.1.2.1-alpha - 2006-08-27
12452 - Add "eventdns" async dns library from Adam Langley, tweaked to
12453 build on OSX and Windows. Only enabled if you pass the
12454 --enable-eventdns argument to configure.
12455 - Allow servers with no hostname or IP address to learn their
12456 IP address by asking the directory authorities. This code only
12457 kicks in when you would normally have exited with a "no address"
12458 error. Nothing's authenticated, so use with care.
12459 - Rather than waiting a fixed amount of time between retrying
12460 application connections, we wait only 5 seconds for the first,
12461 10 seconds for the second, and 15 seconds for each retry after
12462 that. Hopefully this will improve the expected user experience.
12463 - Patch from Tup to add support for transparent AP connections:
12464 this basically bundles the functionality of trans-proxy-tor
12465 into the Tor mainline. Now hosts with compliant pf/netfilter
12466 implementations can redirect TCP connections straight to Tor
12467 without diverting through SOCKS. Needs docs.
12468 - Busy directory servers save lots of memory by spooling server
12469 descriptors, v1 directories, and v2 networkstatus docs to buffers
12470 as needed rather than en masse. Also mmap the cached-routers
12471 files, so we don't need to keep the whole thing in memory too.
12472 - Automatically avoid picking more than one node from the same
12473 /16 network when constructing a circuit.
12474 - Revise and clean up the torrc.sample that we ship with; add
12475 a section for BandwidthRate and BandwidthBurst.
12478 - Split circuit_t into origin_circuit_t and or_circuit_t, and
12479 split connection_t into edge, or, dir, control, and base structs.
12480 These will save quite a bit of memory on busy servers, and they'll
12481 also help us track down bugs in the code and bugs in the spec.
12482 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
12483 or later. Log when we are doing this, so we can diagnose it when
12484 it fails. (Also, recommend libevent 1.1b for kqueue and
12485 win32 methods; deprecate libevent 1.0b harder; make libevent
12486 recommendation system saner.)
12487 - Start being able to build universal binaries on OS X (thanks
12489 - Export the default exit policy via the control port, so controllers
12490 don't need to guess what it is / will be later.
12491 - Add a man page entry for ProtocolWarnings.
12492 - Add TestVia config option to the man page.
12493 - Remove even more protocol-related warnings from Tor server logs,
12494 such as bad TLS handshakes and malformed begin cells.
12495 - Stop fetching descriptors if you're not a dir mirror and you
12496 haven't tried to establish any circuits lately. [This currently
12497 causes some dangerous behavior, because when you start up again
12498 you'll use your ancient server descriptors.]
12499 - New DirPort behavior: if you have your dirport set, you download
12500 descriptors aggressively like a directory mirror, whether or not
12501 your ORPort is set.
12502 - Get rid of the router_retry_connections notion. Now routers
12503 no longer try to rebuild long-term connections to directory
12504 authorities, and directory authorities no longer try to rebuild
12505 long-term connections to all servers. We still don't hang up
12506 connections in these two cases though -- we need to look at it
12507 more carefully to avoid flapping, and we likely need to wait til
12508 0.1.1.x is obsolete.
12509 - Drop compatibility with obsolete Tors that permit create cells
12510 to have the wrong circ_id_type.
12511 - Re-enable per-connection rate limiting. Get rid of the "OP
12512 bandwidth" concept. Lay groundwork for "bandwidth classes" --
12513 separate global buckets that apply depending on what sort of conn
12515 - Start publishing one minute or so after we find our ORPort
12516 to be reachable. This will help reduce the number of descriptors
12517 we have for ourselves floating around, since it's quite likely
12518 other things (e.g. DirPort) will change during that minute too.
12519 - Fork the v1 directory protocol into its own spec document,
12520 and mark dir-spec.txt as the currently correct (v2) spec.
12523 - When we find our DirPort to be reachable, publish a new descriptor
12524 so we'll tell the world (reported by pnx).
12525 - Publish a new descriptor after we hup/reload. This is important
12526 if our config has changed such that we'll want to start advertising
12527 our DirPort now, etc.
12528 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12529 - When we have a state file we cannot parse, tell the user and
12530 move it aside. Now we avoid situations where the user starts
12531 Tor in 1904, Tor writes a state file with that timestamp in it,
12532 the user fixes her clock, and Tor refuses to start.
12533 - Fix configure.in to not produce broken configure files with
12534 more recent versions of autoconf. Thanks to Clint for his auto*
12536 - "tor --verify-config" now exits with -1(255) or 0 depending on
12537 whether the config options are bad or good.
12538 - Resolve bug 321 when using dnsworkers: append a period to every
12539 address we resolve at the exit node, so that we do not accidentally
12540 pick up local addresses, and so that failing searches are retried
12541 in the resolver search domains. (This is already solved for
12542 eventdns.) (This breaks Blossom servers for now.)
12543 - If we are using an exit enclave and we can't connect, e.g. because
12544 its webserver is misconfigured to not listen on localhost, then
12545 back off and try connecting from somewhere else before we fail.
12548 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
12549 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
12550 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
12551 when the IP address is mapped through MapAddress to a hostname.
12552 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
12553 useless IPv6 DNS resolves.
12554 - Patch suggested by Karsten Loesing: respond to SIGNAL command
12555 before we execute the signal, in case the signal shuts us down.
12556 - Clean up AllowInvalidNodes man page entry.
12557 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
12558 - Add more asserts to track down an assert error on a windows Tor
12559 server with connection_add being called with socket == -1.
12560 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
12561 - Fix misleading log messages: an entry guard that is "unlisted",
12562 as well as not known to be "down" (because we've never heard
12563 of it), is not therefore "up".
12564 - Remove code to special-case "-cvs" ending, since it has not
12565 actually mattered since 0.0.9.
12566 - Make our socks5 handling more robust to broken socks clients:
12567 throw out everything waiting on the buffer in between socks
12568 handshake phases, since they can't possibly (so the theory
12569 goes) have predicted what we plan to respond to them.
12572 Changes in version 0.1.1.23 - 2006-07-30
12574 - Fast Tor servers, especially exit nodes, were triggering asserts
12575 due to a bug in handling the list of pending DNS resolves. Some
12576 bugs still remain here; we're hunting them.
12577 - Entry guards could crash clients by sending unexpected input.
12578 - More fixes on reachability testing: if you find yourself reachable,
12579 then don't ever make any client requests (so you stop predicting
12580 circuits), then hup or have your clock jump, then later your IP
12581 changes, you won't think circuits are working, so you won't try to
12582 test reachability, so you won't publish.
12585 - Avoid a crash if the controller does a resetconf firewallports
12586 and then a setconf fascistfirewall=1.
12587 - Avoid an integer underflow when the dir authority decides whether
12588 a router is stable: we might wrongly label it stable, and compute
12589 a slightly wrong median stability, when a descriptor is published
12591 - Fix a place where we might trigger an assert if we can't build our
12592 own server descriptor yet.
12595 Changes in version 0.1.1.22 - 2006-07-05
12597 - Fix a big bug that was causing servers to not find themselves
12598 reachable if they changed IP addresses. Since only 0.1.1.22+
12599 servers can do reachability testing correctly, now we automatically
12600 make sure to test via one of these.
12601 - Fix to allow clients and mirrors to learn directory info from
12602 descriptor downloads that get cut off partway through.
12603 - Directory authorities had a bug in deciding if a newly published
12604 descriptor was novel enough to make everybody want a copy -- a few
12605 servers seem to be publishing new descriptors many times a minute.
12607 - Fix a rare bug that was causing some servers to complain about
12608 "closing wedged cpuworkers" and skip some circuit create requests.
12609 - Make the Exit flag in directory status documents actually work.
12612 Changes in version 0.1.1.21 - 2006-06-10
12613 o Crash and assert fixes from 0.1.1.20:
12614 - Fix a rare crash on Tor servers that have enabled hibernation.
12615 - Fix a seg fault on startup for Tor networks that use only one
12616 directory authority.
12617 - Fix an assert from a race condition that occurs on Tor servers
12618 while exiting, where various threads are trying to log that they're
12619 exiting, and delete the logs, at the same time.
12620 - Make our unit tests pass again on certain obscure platforms.
12623 - Add support for building SUSE RPM packages.
12624 - Speed up initial bootstrapping for clients: if we are making our
12625 first ever connection to any entry guard, then don't mark it down
12627 - When only one Tor server in the network is labelled as a guard,
12628 and we've already picked him, we would cycle endlessly picking him
12629 again, being unhappy about it, etc. Now we specifically exclude
12630 current guards when picking a new guard.
12631 - Servers send create cells more reliably after the TLS connection
12632 is established: we were sometimes forgetting to send half of them
12633 when we had more than one pending.
12634 - If we get a create cell that asks us to extend somewhere, but the
12635 Tor server there doesn't match the expected digest, we now send
12636 a destroy cell back, rather than silently doing nothing.
12637 - Make options->RedirectExit work again.
12638 - Make cookie authentication for the controller work again.
12639 - Stop being picky about unusual characters in the arguments to
12640 mapaddress. It's none of our business.
12641 - Add a new config option "TestVia" that lets you specify preferred
12642 middle hops to use for test circuits. Perhaps this will let me
12643 debug the reachability problems better.
12645 o Log / documentation fixes:
12646 - If we're a server and some peer has a broken TLS certificate, don't
12647 log about it unless ProtocolWarnings is set, i.e., we want to hear
12648 about protocol violations by others.
12649 - Fix spelling of VirtualAddrNetwork in man page.
12650 - Add a better explanation at the top of the autogenerated torrc file
12651 about what happened to our old torrc.
12654 Changes in version 0.1.1.20 - 2006-05-23
12656 - Downgrade a log severity where servers complain that they're
12658 - Avoid a compile warning on FreeBSD.
12659 - Remove string size limit on NEWDESC messages; solve bug 291.
12660 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
12661 more thoroughly when we're running on windows.
12664 Changes in version 0.1.1.19-rc - 2006-05-03
12666 - Regenerate our local descriptor if it's dirty and we try to use
12667 it locally (e.g. if it changes during reachability detection).
12668 - If we setconf our ORPort to 0, we continued to listen on the
12669 old ORPort and receive connections.
12670 - Avoid a second warning about machine/limits.h on Debian
12672 - Be willing to add our own routerinfo into the routerlist.
12673 Now authorities will include themselves in their directories
12674 and network-statuses.
12675 - Stop trying to upload rendezvous descriptors to every
12676 directory authority: only try the v1 authorities.
12677 - Servers no longer complain when they think they're not
12678 registered with the directory authorities. There were too many
12680 - Backport dist-rpm changes so rpms can be built without errors.
12683 - Implement an option, VirtualAddrMask, to set which addresses
12684 get handed out in response to mapaddress requests. This works
12685 around a bug in tsocks where 127.0.0.0/8 is never socksified.
12688 Changes in version 0.1.1.18-rc - 2006-04-10
12690 - Work harder to download live network-statuses from all the
12691 directory authorities we know about. Improve the threshold
12692 decision logic so we're more robust to edge cases.
12693 - When fetching rendezvous descriptors, we were willing to ask
12694 v2 authorities too, which would always return 404.
12697 - Stop listing down or invalid nodes in the v1 directory. This will
12698 reduce its bulk by about 1/3, and reduce load on directory
12700 - When deciding whether a router is Fast or Guard-worthy, consider
12701 his advertised BandwidthRate and not just the BandwidthCapacity.
12702 - No longer ship INSTALL and README files -- they are useless now.
12703 - Force rpmbuild to behave and honor target_cpu.
12704 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
12705 - Start to include translated versions of the tor-doc-*.html
12706 files, along with the screenshots. Still needs more work.
12707 - Start sending back 512 and 451 errors if mapaddress fails,
12708 rather than not sending anything back at all.
12709 - When we fail to bind or listen on an incoming or outgoing
12710 socket, we should close it before failing. otherwise we just
12711 leak it. (thanks to weasel for finding.)
12712 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
12713 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
12714 - Make NoPublish (even though deprecated) work again.
12715 - Fix a minor security flaw where a versioning auth dirserver
12716 could list a recommended version many times in a row to make
12717 clients more convinced that it's recommended.
12718 - Fix crash bug if there are two unregistered servers running
12719 with the same nickname, one of them is down, and you ask for
12720 them by nickname in your EntryNodes or ExitNodes. Also, try
12721 to pick the one that's running rather than an arbitrary one.
12722 - Fix an infinite loop we could hit if we go offline for too long.
12723 - Complain when we hit WSAENOBUFS on recv() or write() too.
12724 Perhaps this will help us hunt the bug.
12725 - If you're not a versioning dirserver, don't put the string
12726 "client-versions \nserver-versions \n" in your network-status.
12727 - Lower the minimum required number of file descriptors to 1000,
12728 so we can have some overhead for Valgrind on Linux, where the
12729 default ulimit -n is 1024.
12732 - Add tor.dizum.com as the fifth authoritative directory server.
12733 - Add a new config option FetchUselessDescriptors, off by default,
12734 for when you plan to run "exitlist" on your client and you want
12735 to know about even the non-running descriptors.
12738 Changes in version 0.1.1.17-rc - 2006-03-28
12740 - Clients and servers since 0.1.1.10-alpha have been expiring
12741 connections whenever they are idle for 5 minutes and they *do*
12742 have circuits on them. Oops. With this new version, clients will
12743 discard their previous entry guard choices and avoid choosing
12744 entry guards running these flawed versions.
12745 - Fix memory leak when uncompressing concatenated zlib streams. This
12746 was causing substantial leaks over time on Tor servers.
12747 - The v1 directory was including servers as much as 48 hours old,
12748 because that's how the new routerlist->routers works. Now only
12749 include them if they're 20 hours old or less.
12752 - Resume building on irix64, netbsd 2.0, etc.
12753 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
12755 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
12756 and it is confusing some users.
12757 - Mirrors stop caching the v1 directory so often.
12758 - Make the max number of old descriptors that a cache will hold
12759 rise with the number of directory authorities, so we can scale.
12760 - Change our win32 uname() hack to be more forgiving about what
12761 win32 versions it thinks it's found.
12764 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
12766 - When the controller's *setconf commands fail, collect an error
12767 message in a string and hand it back to the controller.
12768 - Make the v2 dir's "Fast" flag based on relative capacity, just
12769 like "Stable" is based on median uptime. Name everything in the
12770 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
12771 - Log server fingerprint on startup, so new server operators don't
12772 have to go hunting around their filesystem for it.
12773 - Return a robots.txt on our dirport to discourage google indexing.
12774 - Let the controller ask for GETINFO dir/status/foo so it can ask
12775 directly rather than connecting to the dir port. Only works when
12776 dirport is set for now.
12778 o New config options rather than constants in the code:
12779 - SocksTimeout: How long do we let a socks connection wait
12780 unattached before we fail it?
12781 - CircuitBuildTimeout: Cull non-open circuits that were born
12782 at least this many seconds ago.
12783 - CircuitIdleTimeout: Cull open clean circuits that were born
12784 at least this many seconds ago.
12787 Changes in version 0.1.1.16-rc - 2006-03-18
12788 o Bugfixes on 0.1.1.15-rc:
12789 - Fix assert when the controller asks to attachstream a connect-wait
12790 or resolve-wait stream.
12791 - Now do address rewriting when the controller asks us to attach
12792 to a particular circuit too. This will let Blossom specify
12793 "moria2.exit" without having to learn what moria2's IP address is.
12794 - Make the "tor --verify-config" command-line work again, so people
12795 can automatically check if their torrc will parse.
12796 - Authoritative dirservers no longer require an open connection from
12797 a server to consider him "reachable". We need this change because
12798 when we add new auth dirservers, old servers won't know not to
12800 - Let Tor build on Sun CC again.
12801 - Fix an off-by-one buffer size in dirserv.c that magically never
12802 hit our three authorities but broke sjmurdoch's own tor network.
12803 - If we as a directory mirror don't know of any v1 directory
12804 authorities, then don't try to cache any v1 directories.
12805 - Stop warning about unknown servers in our family when they are
12806 given as hex digests.
12807 - Stop complaining as quickly to the server operator that he
12808 hasn't registered his nickname/key binding.
12809 - Various cleanups so we can add new V2 Auth Dirservers.
12810 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
12811 reflect the updated flags in our v2 dir protocol.
12812 - Resume allowing non-printable characters for exit streams (both
12813 for connecting and for resolving). Now we tolerate applications
12814 that don't follow the RFCs. But continue to block malformed names
12817 o Bugfixes on 0.1.0.x:
12818 - Fix assert bug in close_logs(): when we close and delete logs,
12819 remove them all from the global "logfiles" list.
12820 - Fix minor integer overflow in calculating when we expect to use up
12821 our bandwidth allocation before hibernating.
12822 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
12823 there are multiple SSLs installed with different versions.
12824 - When we try to be a server and Address is not explicitly set and
12825 our hostname resolves to a private IP address, try to use an
12826 interface address if it has a public address. Now Windows machines
12827 that think of themselves as localhost can work by default.
12830 - Let the controller ask for GETINFO dir/server/foo so it can ask
12831 directly rather than connecting to the dir port.
12832 - Let the controller tell us about certain router descriptors
12833 that it doesn't want Tor to use in circuits. Implement
12834 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
12835 - New config option SafeSocks to reject all application connections
12836 using unsafe socks protocols. Defaults to off.
12839 Changes in version 0.1.1.15-rc - 2006-03-11
12840 o Bugfixes and cleanups:
12841 - When we're printing strings from the network, don't try to print
12842 non-printable characters. This protects us against shell escape
12843 sequence exploits, and also against attacks to fool humans into
12844 misreading their logs.
12845 - Fix a bug where Tor would fail to establish any connections if you
12846 left it off for 24 hours and then started it: we were happy with
12847 the obsolete network statuses, but they all referred to router
12848 descriptors that were too old to fetch, so we ended up with no
12849 valid router descriptors.
12850 - Fix a seg fault in the controller's "getinfo orconn-status"
12851 command while listing status on incoming handshaking connections.
12852 Introduce a status name "NEW" for these connections.
12853 - If we get a linelist or linelist_s config option from the torrc
12854 (e.g. ExitPolicy) and it has no value, warn and skip rather than
12855 silently resetting it to its default.
12856 - Don't abandon entry guards until they've been down or gone for
12858 - Cleaner and quieter log messages.
12861 - New controller signal NEWNYM that makes new application requests
12862 use clean circuits.
12863 - Add a new circuit purpose 'controller' to let the controller ask
12864 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
12865 controller command to let you specify the purpose if you're
12866 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
12867 command to let you change a circuit's purpose after it's been
12869 - Accept "private:*" in routerdesc exit policies; not generated yet
12870 because older Tors do not understand it.
12871 - Add BSD-style contributed startup script "rc.subr" from Peter
12875 Changes in version 0.1.1.14-alpha - 2006-02-20
12876 o Bugfixes on 0.1.1.x:
12877 - Don't die if we ask for a stdout or stderr log (even implicitly)
12878 and we're set to RunAsDaemon -- just warn.
12879 - We still had a few bugs in the OR connection rotation code that
12880 caused directory servers to slowly aggregate connections to other
12881 fast Tor servers. This time for sure!
12882 - Make log entries on Win32 include the name of the function again.
12883 - We were treating a pair of exit policies if they were equal even
12884 if one said accept and the other said reject -- causing us to
12885 not always publish a new descriptor since we thought nothing
12887 - Retry pending server downloads as well as pending networkstatus
12888 downloads when we unexpectedly get a socks request.
12889 - We were ignoring the IS_FAST flag in the directory status,
12890 meaning we were willing to pick trivial-bandwidth nodes for "fast"
12892 - If the controller's SAVECONF command fails (e.g. due to file
12893 permissions), let the controller know that it failed.
12896 - If we're trying to be a Tor server and running Windows 95/98/ME
12897 as a server, explain that we'll likely crash.
12898 - When we're a server, a client asks for an old-style directory,
12899 and our write bucket is empty, don't give it to him. This way
12900 small servers can continue to serve the directory *sometimes*,
12901 without getting overloaded.
12902 - Compress exit policies even more -- look for duplicate lines
12904 - Clients now honor the "guard" flag in the router status when
12905 picking entry guards, rather than looking at is_fast or is_stable.
12906 - Retain unrecognized lines in $DATADIR/state file, so that we can
12907 be forward-compatible.
12908 - Generate 18.0.0.0/8 address policy format in descs when we can;
12909 warn when the mask is not reducible to a bit-prefix.
12910 - Let the user set ControlListenAddress in the torrc. This can be
12911 dangerous, but there are some cases (like a secured LAN) where it
12913 - Split ReachableAddresses into ReachableDirAddresses and
12914 ReachableORAddresses, so we can restrict Dir conns to port 80
12915 and OR conns to port 443.
12916 - Now we can target arch and OS in rpm builds (contributed by
12917 Phobos). Also make the resulting dist-rpm filename match the
12919 - New config options to help controllers: FetchServerDescriptors
12920 and FetchHidServDescriptors for whether to fetch server
12921 info and hidserv info or let the controller do it, and
12922 PublishServerDescriptor and PublishHidServDescriptors.
12923 - Also let the controller set the __AllDirActionsPrivate config
12924 option if you want all directory fetches/publishes to happen via
12925 Tor (it assumes your controller bootstraps your circuits).
12928 Changes in version 0.1.0.17 - 2006-02-17
12929 o Crash bugfixes on 0.1.0.x:
12930 - When servers with a non-zero DirPort came out of hibernation,
12931 sometimes they would trigger an assert.
12933 o Other important bugfixes:
12934 - On platforms that don't have getrlimit (like Windows), we were
12935 artificially constraining ourselves to a max of 1024
12936 connections. Now just assume that we can handle as many as 15000
12937 connections. Hopefully this won't cause other problems.
12939 o Backported features:
12940 - When we're a server, a client asks for an old-style directory,
12941 and our write bucket is empty, don't give it to him. This way
12942 small servers can continue to serve the directory *sometimes*,
12943 without getting overloaded.
12944 - Whenever you get a 503 in response to a directory fetch, try
12945 once more. This will become important once servers start sending
12946 503's whenever they feel busy.
12947 - Fetch a new directory every 120 minutes, not every 40 minutes.
12948 Now that we have hundreds of thousands of users running the old
12949 directory algorithm, it's starting to hurt a lot.
12950 - Bump up the period for forcing a hidden service descriptor upload
12951 from 20 minutes to 1 hour.
12954 Changes in version 0.1.1.13-alpha - 2006-02-09
12955 o Crashes in 0.1.1.x:
12956 - When you tried to setconf ORPort via the controller, Tor would
12957 crash. So people using TorCP to become a server were sad.
12958 - Solve (I hope) the stack-smashing bug that we were seeing on fast
12959 servers. The problem appears to be something do with OpenSSL's
12960 random number generation, or how we call it, or something. Let me
12961 know if the crashes continue.
12962 - Turn crypto hardware acceleration off by default, until we find
12963 somebody smart who can test it for us. (It appears to produce
12964 seg faults in at least some cases.)
12965 - Fix a rare assert error when we've tried all intro points for
12966 a hidden service and we try fetching the service descriptor again:
12967 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
12970 - Fix a major load balance bug: we were round-robining in 16 KB
12971 chunks, and servers with bandwidthrate of 20 KB, while downloading
12972 a 600 KB directory, would starve their other connections. Now we
12973 try to be a bit more fair.
12974 - Dir authorities and mirrors were never expiring the newest
12975 descriptor for each server, causing memory and directory bloat.
12976 - Fix memory-bloating and connection-bloating bug on servers: We
12977 were never closing any connection that had ever had a circuit on
12978 it, because we were checking conn->n_circuits == 0, yet we had a
12979 bug that let it go negative.
12980 - Make Tor work using squid as your http proxy again -- squid
12981 returns an error if you ask for a URL that's too long, and it uses
12982 a really generic error message. Plus, many people are behind a
12983 transparent squid so they don't even realize it.
12984 - On platforms that don't have getrlimit (like Windows), we were
12985 artificially constraining ourselves to a max of 1024
12986 connections. Now just assume that we can handle as many as 15000
12987 connections. Hopefully this won't cause other problems.
12988 - Add a new config option ExitPolicyRejectPrivate which defaults to
12989 1. This means all exit policies will begin with rejecting private
12990 addresses, unless the server operator explicitly turns it off.
12993 - Clients no longer download descriptors for non-running
12995 - Before we add new directory authorities, we should make it
12996 clear that only v1 authorities should receive/publish hidden
12997 service descriptors.
13000 - As soon as we've fetched some more directory info, immediately
13001 try to download more server descriptors. This way we don't have
13002 a 10 second pause during initial bootstrapping.
13003 - Remove even more loud log messages that the server operator can't
13005 - When we're running an obsolete or un-recommended version, make
13006 the log message more clear about what the problem is and what
13007 versions *are* still recommended.
13008 - Provide a more useful warn message when our onion queue gets full:
13009 the CPU is too slow or the exit policy is too liberal.
13010 - Don't warn when we receive a 503 from a dirserver/cache -- this
13011 will pave the way for them being able to refuse if they're busy.
13012 - When we fail to bind a listener, try to provide a more useful
13013 log message: e.g., "Is Tor already running?"
13014 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
13015 Goldberg can prove things about our handshake protocol more
13017 - MaxConn has been obsolete for a while now. Document the ConnLimit
13018 config option, which is a *minimum* number of file descriptors
13019 that must be available else Tor refuses to start.
13020 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
13021 if you log to syslog and want something other than LOG_DAEMON.
13022 - Make dirservers generate a separate "guard" flag to mean,
13023 "would make a good entry guard". Make clients parse it and vote
13024 on it. Not used by clients yet.
13025 - Implement --with-libevent-dir option to ./configure. Also, improve
13026 search techniques to find libevent, and use those for openssl too.
13027 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
13028 - Only start testing reachability once we've established a
13029 circuit. This will make startup on dirservers less noisy.
13030 - Don't try to upload hidden service descriptors until we have
13031 established a circuit.
13032 - Fix the controller's "attachstream 0" command to treat conn like
13033 it just connected, doing address remapping, handling .exit and
13034 .onion idioms, and so on. Now we're more uniform in making sure
13035 that the controller hears about new and closing connections.
13038 Changes in version 0.1.1.12-alpha - 2006-01-11
13039 o Bugfixes on 0.1.1.x:
13040 - The fix to close duplicate server connections was closing all
13041 Tor client connections if they didn't establish a circuit
13042 quickly enough. Oops.
13043 - Fix minor memory issue (double-free) that happened on exit.
13045 o Bugfixes on 0.1.0.x:
13046 - Tor didn't warn when it failed to open a log file.
13049 Changes in version 0.1.1.11-alpha - 2006-01-10
13050 o Crashes in 0.1.1.x:
13051 - Include all the assert/crash fixes from 0.1.0.16.
13052 - If you start Tor and then quit very quickly, there were some
13053 races that tried to free things that weren't allocated yet.
13054 - Fix a rare memory stomp if you're running hidden services.
13055 - Fix segfault when specifying DirServer in config without nickname.
13056 - Fix a seg fault when you finish connecting to a server but at
13057 that moment you dump his server descriptor.
13058 - Extendcircuit and Attachstream controller commands would
13059 assert/crash if you don't give them enough arguments.
13060 - Fix an assert error when we're out of space in the connection_list
13061 and we try to post a hidden service descriptor (reported by weasel).
13062 - If you specify a relative torrc path and you set RunAsDaemon in
13063 your torrc, then it chdir()'s to the new directory. If you HUP,
13064 it tries to load the new torrc location, fails, and exits.
13065 The fix: no longer allow a relative path to torrc using -f.
13068 - Implement "entry guards": automatically choose a handful of entry
13069 nodes and stick with them for all circuits. Only pick new guards
13070 when the ones you have are unsuitable, and if the old guards
13071 become suitable again, switch back. This will increase security
13072 dramatically against certain end-point attacks. The EntryNodes
13073 config option now provides some hints about which entry guards you
13074 want to use most; and StrictEntryNodes means to only use those.
13075 - New directory logic: download by descriptor digest, not by
13076 fingerprint. Caches try to download all listed digests from
13077 authorities; clients try to download "best" digests from caches.
13078 This avoids partitioning and isolating attacks better.
13079 - Make the "stable" router flag in network-status be the median of
13080 the uptimes of running valid servers, and make clients pay
13081 attention to the network-status flags. Thus the cutoff adapts
13082 to the stability of the network as a whole, making IRC, IM, etc
13083 connections more reliable.
13086 - Tor servers with dynamic IP addresses were needing to wait 18
13087 hours before they could start doing reachability testing using
13088 the new IP address and ports. This is because they were using
13089 the internal descriptor to learn what to test, yet they were only
13090 rebuilding the descriptor once they decided they were reachable.
13091 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
13092 to download certain server descriptors, throw them away, and then
13093 fetch them again after 30 minutes. Now mirrors throw away these
13094 server descriptors so clients can't get them.
13095 - We were leaving duplicate connections to other ORs open for a week,
13096 rather than closing them once we detect a duplicate. This only
13097 really affected authdirservers, but it affected them a lot.
13098 - Spread the authdirservers' reachability testing over the entire
13099 testing interval, so we don't try to do 500 TLS's at once every
13103 - If the network is down, and we try to connect to a conn because
13104 we have a circuit in mind, and we timeout (30 seconds) because the
13105 network never answers, we were expiring the circuit, but we weren't
13106 obsoleting the connection or telling the entry_guards functions.
13107 - Some Tor servers process billions of cells per day. These statistics
13108 need to be uint64_t's.
13109 - Check for integer overflows in more places, when adding elements
13110 to smartlists. This could possibly prevent a buffer overflow
13111 on malicious huge inputs. I don't see any, but I haven't looked
13113 - ReachableAddresses kept growing new "reject *:*" lines on every
13115 - When you "setconf log" via the controller, it should remove all
13116 logs. We were automatically adding back in a "log notice stdout".
13117 - Newly bootstrapped Tor networks couldn't establish hidden service
13118 circuits until they had nodes with high uptime. Be more tolerant.
13119 - We were marking servers down when they could not answer every piece
13120 of the directory request we sent them. This was far too harsh.
13121 - Fix the torify (tsocks) config file to not use Tor for localhost
13123 - Directory authorities now go to the proper authority when asking for
13124 a networkstatus, even when they want a compressed one.
13125 - Fix a harmless bug that was causing Tor servers to log
13126 "Got an end because of misc error, but we're not an AP. Closing."
13127 - Authorities were treating their own descriptor changes as cosmetic,
13128 meaning the descriptor available in the network-status and the
13129 descriptor that clients downloaded were different.
13130 - The OS X installer was adding a symlink for tor_resolve but
13131 the binary was called tor-resolve (reported by Thomas Hardly).
13132 - Workaround a problem with some http proxies where they refuse GET
13133 requests that specify "Content-Length: 0" (reported by Adrian).
13134 - Fix wrong log message when you add a "HiddenServiceNodes" config
13135 line without any HiddenServiceDir line (reported by Chris Thomas).
13138 - Write the TorVersion into the state file so we have a prayer of
13139 keeping forward and backward compatibility.
13140 - Revive the FascistFirewall config option rather than eliminating it:
13141 now it's a synonym for ReachableAddresses *:80,*:443.
13142 - Clients choose directory servers from the network status lists,
13143 not from their internal list of router descriptors. Now they can
13144 go to caches directly rather than needing to go to authorities
13146 - Directory authorities ignore router descriptors that have only
13147 cosmetic differences: do this for 0.1.0.x servers now too.
13148 - Add a new flag to network-status indicating whether the server
13149 can answer v2 directory requests too.
13150 - Authdirs now stop whining so loudly about bad descriptors that
13151 they fetch from other dirservers. So when there's a log complaint,
13152 it's for sure from a freshly uploaded descriptor.
13153 - Reduce memory requirements in our structs by changing the order
13155 - There used to be two ways to specify your listening ports in a
13156 server descriptor: on the "router" line and with a separate "ports"
13157 line. Remove support for the "ports" line.
13158 - New config option "AuthDirRejectUnlisted" for auth dirservers as
13159 a panic button: if we get flooded with unusable servers we can
13160 revert to only listing servers in the approved-routers file.
13161 - Auth dir servers can now mark a fingerprint as "!reject" or
13162 "!invalid" in the approved-routers file (as its nickname), to
13163 refuse descriptors outright or include them but marked as invalid.
13164 - Servers store bandwidth history across restarts/crashes.
13165 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
13166 get a better idea of why their circuits failed. Not used yet.
13167 - Directory mirrors now cache up to 16 unrecognized network-status
13168 docs. Now we can add new authdirservers and they'll be cached too.
13169 - When picking a random directory, prefer non-authorities if any
13171 - New controller option "getinfo desc/all-recent" to fetch the
13172 latest server descriptor for every router that Tor knows about.
13175 Changes in version 0.1.0.16 - 2006-01-02
13176 o Crash bugfixes on 0.1.0.x:
13177 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
13178 corrupting the heap, losing FDs, or crashing when we need to resize
13179 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
13180 - It turns out sparc64 platforms crash on unaligned memory access
13181 too -- so detect and avoid this.
13182 - Handle truncated compressed data correctly (by detecting it and
13184 - Fix possible-but-unlikely free(NULL) in control.c.
13185 - When we were closing connections, there was a rare case that
13186 stomped on memory, triggering seg faults and asserts.
13187 - Avoid potential infinite recursion when building a descriptor. (We
13188 don't know that it ever happened, but better to fix it anyway.)
13189 - We were neglecting to unlink marked circuits from soon-to-close OR
13190 connections, which caused some rare scribbling on freed memory.
13191 - Fix a memory stomping race bug when closing the joining point of two
13192 rendezvous circuits.
13193 - Fix an assert in time parsing found by Steven Murdoch.
13195 o Other bugfixes on 0.1.0.x:
13196 - When we're doing reachability testing, provide more useful log
13197 messages so the operator knows what to expect.
13198 - Do not check whether DirPort is reachable when we are suppressing
13199 advertising it because of hibernation.
13200 - When building with -static or on Solaris, we sometimes needed -ldl.
13201 - When we're deciding whether a stream has enough circuits around
13202 that can handle it, count the freshly dirty ones and not the ones
13203 that are so dirty they won't be able to handle it.
13204 - When we're expiring old circuits, we had a logic error that caused
13205 us to close new rendezvous circuits rather than old ones.
13206 - Give a more helpful log message when you try to change ORPort via
13207 the controller: you should upgrade Tor if you want that to work.
13208 - We were failing to parse Tor versions that start with "Tor ".
13209 - Tolerate faulty streams better: when a stream fails for reason
13210 exitpolicy, stop assuming that the router is lying about his exit
13211 policy. When a stream fails for reason misc, allow it to retry just
13212 as if it was resolvefailed. When a stream has failed three times,
13213 reset its failure count so we can try again and get all three tries.
13216 Changes in version 0.1.1.10-alpha - 2005-12-11
13217 o Correctness bugfixes on 0.1.0.x:
13218 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
13219 corrupting the heap, losing FDs, or crashing when we need to resize
13220 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
13221 - Stop doing the complex voodoo overkill checking for insecure
13222 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
13223 - When we were closing connections, there was a rare case that
13224 stomped on memory, triggering seg faults and asserts.
13225 - We were neglecting to unlink marked circuits from soon-to-close OR
13226 connections, which caused some rare scribbling on freed memory.
13227 - When we're deciding whether a stream has enough circuits around
13228 that can handle it, count the freshly dirty ones and not the ones
13229 that are so dirty they won't be able to handle it.
13230 - Recover better from TCP connections to Tor servers that are
13231 broken but don't tell you (it happens!); and rotate TLS
13232 connections once a week.
13233 - When we're expiring old circuits, we had a logic error that caused
13234 us to close new rendezvous circuits rather than old ones.
13235 - Fix a scary-looking but apparently harmless bug where circuits
13236 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
13237 servers, and never switch to state CIRCUIT_STATE_OPEN.
13238 - When building with -static or on Solaris, we sometimes needed to
13240 - Give a useful message when people run Tor as the wrong user,
13241 rather than telling them to start chowning random directories.
13242 - We were failing to inform the controller about new .onion streams.
13244 o Security bugfixes on 0.1.0.x:
13245 - Refuse server descriptors if the fingerprint line doesn't match
13246 the included identity key. Tor doesn't care, but other apps (and
13247 humans) might actually be trusting the fingerprint line.
13248 - We used to kill the circuit when we receive a relay command we
13249 don't recognize. Now we just drop it.
13250 - Start obeying our firewall options more rigorously:
13251 . If we can't get to a dirserver directly, try going via Tor.
13252 . Don't ever try to connect (as a client) to a place our
13253 firewall options forbid.
13254 . If we specify a proxy and also firewall options, obey the
13255 firewall options even when we're using the proxy: some proxies
13256 can only proxy to certain destinations.
13257 - Fix a bug found by Lasse Overlier: when we were making internal
13258 circuits (intended to be cannibalized later for rendezvous and
13259 introduction circuits), we were picking them so that they had
13260 useful exit nodes. There was no need for this, and it actually
13261 aids some statistical attacks.
13262 - Start treating internal circuits and exit circuits separately.
13263 It's important to keep them separate because internal circuits
13264 have their last hops picked like middle hops, rather than like
13265 exit hops. So exiting on them will break the user's expectations.
13267 o Bugfixes on 0.1.1.x:
13268 - Take out the mis-feature where we tried to detect IP address
13269 flapping for people with DynDNS, and chose not to upload a new
13270 server descriptor sometimes.
13271 - Try to be compatible with OpenSSL 0.9.6 again.
13272 - Log fix: when the controller is logging about .onion addresses,
13273 sometimes it didn't include the ".onion" part of the address.
13274 - Don't try to modify options->DirServers internally -- if the
13275 user didn't specify any, just add the default ones directly to
13276 the trusted dirserver list. This fixes a bug where people running
13277 controllers would use SETCONF on some totally unrelated config
13278 option, and Tor would start yelling at them about changing their
13280 - Let the controller's redirectstream command specify a port, in
13281 case the controller wants to change that too.
13282 - When we requested a pile of server descriptors, we sometimes
13283 accidentally launched a duplicate request for the first one.
13284 - Bugfix for trackhostexits: write down the fingerprint of the
13285 chosen exit, not its nickname, because the chosen exit might not
13287 - When parsing foo.exit, if foo is unknown, and we are leaving
13288 circuits unattached, set the chosen_exit field and leave the
13289 address empty. This matters because controllers got confused
13291 - Directory authorities no longer try to download server
13292 descriptors that they know they will reject.
13294 o Features and updates:
13295 - Replace balanced trees with hash tables: this should make stuff
13296 significantly faster.
13297 - Resume using the AES counter-mode implementation that we ship,
13298 rather than OpenSSL's. Ours is significantly faster.
13299 - Many other CPU and memory improvements.
13300 - Add a new config option FastFirstHopPK (on by default) so clients
13301 do a trivial crypto handshake for their first hop, since TLS has
13302 already taken care of confidentiality and authentication.
13303 - Add a new config option TestSocks so people can see if their
13304 applications are using socks4, socks4a, socks5-with-ip, or
13305 socks5-with-hostname. This way they don't have to keep mucking
13306 with tcpdump and wondering if something got cached somewhere.
13307 - Warn when listening on a public address for socks. I suspect a
13308 lot of people are setting themselves up as open socks proxies,
13309 and they have no idea that jerks on the Internet are using them,
13310 since they simply proxy the traffic into the Tor network.
13311 - Add "private:*" as an alias in configuration for policies. Now
13312 you can simplify your exit policy rather than needing to list
13313 every single internal or nonroutable network space.
13314 - Add a new controller event type that allows controllers to get
13315 all server descriptors that were uploaded to a router in its role
13316 as authoritative dirserver.
13317 - Start shipping socks-extensions.txt, tor-doc-unix.html,
13318 tor-doc-server.html, and stylesheet.css in the tarball.
13319 - Stop shipping tor-doc.html in the tarball.
13322 Changes in version 0.1.1.9-alpha - 2005-11-15
13323 o Usability improvements:
13324 - Start calling it FooListenAddress rather than FooBindAddress,
13325 since few of our users know what it means to bind an address
13327 - Reduce clutter in server logs. We're going to try to make
13328 them actually usable now. New config option ProtocolWarnings that
13329 lets you hear about how _other Tors_ are breaking the protocol. Off
13331 - Divide log messages into logging domains. Once we put some sort
13332 of interface on this, it will let people looking at more verbose
13333 log levels specify the topics they want to hear more about.
13334 - Make directory servers return better http 404 error messages
13335 instead of a generic "Servers unavailable".
13336 - Check for even more Windows version flags when writing the platform
13337 string in server descriptors, and note any we don't recognize.
13338 - Clean up more of the OpenSSL memory when exiting, so we can detect
13339 memory leaks better.
13340 - Make directory authorities be non-versioning, non-naming by
13341 default. Now we can add new directory servers without requiring
13342 their operators to pay close attention.
13343 - When logging via syslog, include the pid whenever we provide
13344 a log entry. Suggested by Todd Fries.
13346 o Performance improvements:
13347 - Directory servers now silently throw away new descriptors that
13348 haven't changed much if the timestamps are similar. We do this to
13349 tolerate older Tor servers that upload a new descriptor every 15
13350 minutes. (It seemed like a good idea at the time.)
13351 - Inline bottleneck smartlist functions; use fast versions by default.
13352 - Add a "Map from digest to void*" abstraction digestmap_t so we
13353 can do less hex encoding/decoding. Use it in router_get_by_digest()
13354 to resolve a performance bottleneck.
13355 - Allow tor_gzip_uncompress to extract as much as possible from
13356 truncated compressed data. Try to extract as many
13357 descriptors as possible from truncated http responses (when
13358 DIR_PURPOSE_FETCH_ROUTERDESC).
13359 - Make circ->onionskin a pointer, not a static array. moria2 was using
13360 125000 circuit_t's after it had been up for a few weeks, which
13361 translates to 20+ megs of wasted space.
13362 - The private half of our EDH handshake keys are now chosen out
13363 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
13365 o Security improvements:
13366 - Start making directory caches retain old routerinfos, so soon
13367 clients can start asking by digest of descriptor rather than by
13368 fingerprint of server.
13369 - Add half our entropy from RAND_poll in OpenSSL. This knows how
13370 to use egd (if present), openbsd weirdness (if present), vms/os2
13371 weirdness (if we ever port there), and more in the future.
13373 o Bugfixes on 0.1.0.x:
13374 - Do round-robin writes of at most 16 kB per write. This might be
13375 more fair on loaded Tor servers, and it might resolve our Windows
13376 crash bug. It might also slow things down.
13377 - Our TLS handshakes were generating a single public/private
13378 keypair for the TLS context, rather than making a new one for
13379 each new connections. Oops. (But we were still rotating them
13380 periodically, so it's not so bad.)
13381 - When we were cannibalizing a circuit with a particular exit
13382 node in mind, we weren't checking to see if that exit node was
13383 already present earlier in the circuit. Oops.
13384 - When a Tor server's IP changes (e.g. from a dyndns address),
13385 upload a new descriptor so clients will learn too.
13386 - Really busy servers were keeping enough circuits open on stable
13387 connections that they were wrapping around the circuit_id
13388 space. (It's only two bytes.) This exposed a bug where we would
13389 feel free to reuse a circuit_id even if it still exists but has
13390 been marked for close. Try to fix this bug. Some bug remains.
13391 - If we would close a stream early (e.g. it asks for a .exit that
13392 we know would refuse it) but the LeaveStreamsUnattached config
13393 option is set by the controller, then don't close it.
13395 o Bugfixes on 0.1.1.8-alpha:
13396 - Fix a big pile of memory leaks, some of them serious.
13397 - Do not try to download a routerdesc if we would immediately reject
13399 - Resume inserting a newline between all router descriptors when
13400 generating (old style) signed directories, since our spec says
13402 - When providing content-type application/octet-stream for
13403 server descriptors using .z, we were leaving out the
13404 content-encoding header. Oops. (Everything tolerated this just
13405 fine, but that doesn't mean we need to be part of the problem.)
13406 - Fix a potential seg fault in getconf and getinfo using version 1
13407 of the controller protocol.
13408 - Avoid crash: do not check whether DirPort is reachable when we
13409 are suppressing it because of hibernation.
13410 - Make --hash-password not crash on exit.
13413 Changes in version 0.1.1.8-alpha - 2005-10-07
13414 o New features (major):
13415 - Clients don't download or use the directory anymore. Now they
13416 download and use network-statuses from the trusted dirservers,
13417 and fetch individual server descriptors as needed from mirrors.
13418 See dir-spec.txt for all the gory details.
13419 - Be more conservative about whether to advertise our DirPort.
13420 The main change is to not advertise if we're running at capacity
13421 and either a) we could hibernate or b) our capacity is low and
13422 we're using a default DirPort.
13423 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
13425 o New features (minor):
13426 - Try to be smart about when to retry network-status and
13427 server-descriptor fetches. Still needs some tuning.
13428 - Stop parsing, storing, or using running-routers output (but
13429 mirrors still cache and serve it).
13430 - Consider a threshold of versioning dirservers (dirservers who have
13431 an opinion about which Tor versions are still recommended) before
13432 deciding whether to warn the user that he's obsolete.
13433 - Dirservers can now reject/invalidate by key and IP, with the
13434 config options "AuthDirInvalid" and "AuthDirReject". This is
13435 useful since currently we automatically list servers as running
13436 and usable even if we know they're jerks.
13437 - Provide dire warnings to any users who set DirServer; move it out
13438 of torrc.sample and into torrc.complete.
13439 - Add MyFamily to torrc.sample in the server section.
13440 - Add nicknames to the DirServer line, so we can refer to them
13441 without requiring all our users to memorize their IP addresses.
13442 - When we get an EOF or a timeout on a directory connection, note
13443 how many bytes of serverdesc we are dropping. This will help
13444 us determine whether it is smart to parse incomplete serverdesc
13446 - Add a new function to "change pseudonyms" -- that is, to stop
13447 using any currently-dirty circuits for new streams, so we don't
13448 link new actions to old actions. Currently it's only called on
13449 HUP (or SIGNAL RELOAD).
13450 - On sighup, if UseHelperNodes changed to 1, use new circuits.
13451 - Start using RAND_bytes rather than RAND_pseudo_bytes from
13452 OpenSSL. Also, reseed our entropy every hour, not just at
13453 startup. And entropy in 512-bit chunks, not 160-bit chunks.
13455 o Fixes on 0.1.1.7-alpha:
13456 - Nobody ever implemented EVENT_ADDRMAP for control protocol
13457 version 0, so don't let version 0 controllers ask for it.
13458 - If you requested something with too many newlines via the
13459 v1 controller protocol, you could crash tor.
13460 - Fix a number of memory leaks, including some pretty serious ones.
13461 - Re-enable DirPort testing again, so Tor servers will be willing
13462 to advertise their DirPort if it's reachable.
13463 - On TLS handshake, only check the other router's nickname against
13464 its expected nickname if is_named is set.
13466 o Fixes forward-ported from 0.1.0.15:
13467 - Don't crash when we don't have any spare file descriptors and we
13468 try to spawn a dns or cpu worker.
13469 - Make the numbers in read-history and write-history into uint64s,
13470 so they don't overflow and publish negatives in the descriptor.
13472 o Fixes on 0.1.0.x:
13473 - For the OS X package's modified privoxy config file, comment
13474 out the "logfile" line so we don't log everything passed
13476 - We were whining about using socks4 or socks5-with-local-lookup
13477 even when it's an IP in the "virtual" range we designed exactly
13479 - We were leaking some memory every time the client changes IPs.
13480 - Never call free() on tor_malloc()d memory. This will help us
13481 use dmalloc to detect memory leaks.
13482 - Check for named servers when looking them up by nickname;
13483 warn when we'recalling a non-named server by its nickname;
13484 don't warn twice about the same name.
13485 - Try to list MyFamily elements by key, not by nickname, and warn
13486 if we've not heard of the server.
13487 - Make windows platform detection (uname equivalent) smarter.
13488 - It turns out sparc64 doesn't like unaligned access either.
13491 Changes in version 0.1.0.15 - 2005-09-23
13492 o Bugfixes on 0.1.0.x:
13493 - Reject ports 465 and 587 (spam targets) in default exit policy.
13494 - Don't crash when we don't have any spare file descriptors and we
13495 try to spawn a dns or cpu worker.
13496 - Get rid of IgnoreVersion undocumented config option, and make us
13497 only warn, never exit, when we're running an obsolete version.
13498 - Don't try to print a null string when your server finds itself to
13499 be unreachable and the Address config option is empty.
13500 - Make the numbers in read-history and write-history into uint64s,
13501 so they don't overflow and publish negatives in the descriptor.
13502 - Fix a minor memory leak in smartlist_string_remove().
13503 - We were only allowing ourselves to upload a server descriptor at
13504 most every 20 minutes, even if it changed earlier than that.
13505 - Clean up log entries that pointed to old URLs.
13508 Changes in version 0.1.1.7-alpha - 2005-09-14
13509 o Fixes on 0.1.1.6-alpha:
13510 - Exit servers were crashing when people asked them to make a
13511 connection to an address not in their exit policy.
13512 - Looking up a non-existent stream for a v1 control connection would
13514 - Fix a seg fault if we ask a dirserver for a descriptor by
13515 fingerprint but he doesn't know about him.
13516 - SETCONF was appending items to linelists, not clearing them.
13517 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
13518 out and refuse the setconf if it would fail.
13519 - Downgrade the dirserver log messages when whining about
13523 - Add Peter Palfrader's check-tor script to tor/contrib/
13524 It lets you easily check whether a given server (referenced by
13525 nickname) is reachable by you.
13526 - Numerous changes to move towards client-side v2 directories. Not
13529 o Fixes on 0.1.0.x:
13530 - If the user gave tor an odd number of command-line arguments,
13531 we were silently ignoring the last one. Now we complain and fail.
13532 [This wins the oldest-bug prize -- this bug has been present since
13533 November 2002, as released in Tor 0.0.0.]
13534 - Do not use unaligned memory access on alpha, mips, or mipsel.
13535 It *works*, but is very slow, so we treat them as if it doesn't.
13536 - Retry directory requests if we fail to get an answer we like
13537 from a given dirserver (we were retrying before, but only if
13538 we fail to connect).
13539 - When writing the RecommendedVersions line, sort them first.
13540 - When the client asked for a rendezvous port that the hidden
13541 service didn't want to provide, we were sending an IP address
13542 back along with the end cell. Fortunately, it was zero. But stop
13544 - Correct "your server is reachable" log entries to indicate that
13545 it was self-testing that told us so.
13548 Changes in version 0.1.1.6-alpha - 2005-09-09
13549 o Fixes on 0.1.1.5-alpha:
13550 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
13551 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
13552 - Fix bug with tor_memmem finding a match at the end of the string.
13553 - Make unit tests run without segfaulting.
13554 - Resolve some solaris x86 compile warnings.
13555 - Handle duplicate lines in approved-routers files without warning.
13556 - Fix bug where as soon as a server refused any requests due to his
13557 exit policy (e.g. when we ask for localhost and he tells us that's
13558 127.0.0.1 and he won't do it), we decided he wasn't obeying his
13559 exit policy using him for any exits.
13560 - Only do openssl hardware accelerator stuff if openssl version is
13563 o New controller features/fixes:
13564 - Add a "RESETCONF" command so you can set config options like
13565 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
13566 a config option in the torrc with no value, then it clears it
13567 entirely (rather than setting it to its default).
13568 - Add a "GETINFO config-file" to tell us where torrc is.
13569 - Avoid sending blank lines when GETINFO replies should be empty.
13570 - Add a QUIT command for the controller (for using it manually).
13571 - Fix a bug in SAVECONF that was adding default dirservers and
13572 other redundant entries to the torrc file.
13574 o Start on the new directory design:
13575 - Generate, publish, cache, serve new network-status format.
13576 - Publish individual descriptors (by fingerprint, by "all", and by
13578 - Publish client and server recommended versions separately.
13579 - Allow tor_gzip_uncompress() to handle multiple concatenated
13580 compressed strings. Serve compressed groups of router
13581 descriptors. The compression logic here could be more
13583 - Distinguish v1 authorities (all currently trusted directories)
13584 from v2 authorities (all trusted directories).
13585 - Change DirServers config line to note which dirs are v1 authorities.
13586 - Add configuration option "V1AuthoritativeDirectory 1" which
13587 moria1, moria2, and tor26 should set.
13588 - Remove option when getting directory cache to see whether they
13589 support running-routers; they all do now. Replace it with one
13590 to see whether caches support v2 stuff.
13593 - Dirservers now do their own external reachability testing of each
13594 Tor server, and only list them as running if they've been found to
13595 be reachable. We also send back warnings to the server's logs if
13596 it uploads a descriptor that we already believe is unreachable.
13597 - Implement exit enclaves: if we know an IP address for the
13598 destination, and there's a running Tor server at that address
13599 which allows exit to the destination, then extend the circuit to
13600 that exit first. This provides end-to-end encryption and end-to-end
13601 authentication. Also, if the user wants a .exit address or enclave,
13602 use 4 hops rather than 3, and cannibalize a general circ for it
13604 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
13605 controller. Also, rotate dns and cpu workers if the controller
13606 changes options that will affect them; and initialize the dns
13607 worker cache tree whether or not we start out as a server.
13608 - Only upload a new server descriptor when options change, 18
13609 hours have passed, uptime is reset, or bandwidth changes a lot.
13610 - Check [X-]Forwarded-For headers in HTTP requests when generating
13611 log messages. This lets people run dirservers (and caches) behind
13612 Apache but still know which IP addresses are causing warnings.
13614 o Config option changes:
13615 - Replace (Fascist)Firewall* config options with a new
13616 ReachableAddresses option that understands address policies.
13617 For example, "ReachableAddresses *:80,*:443"
13618 - Get rid of IgnoreVersion undocumented config option, and make us
13619 only warn, never exit, when we're running an obsolete version.
13620 - Make MonthlyAccountingStart config option truly obsolete now.
13622 o Fixes on 0.1.0.x:
13623 - Reject ports 465 and 587 in the default exit policy, since
13624 people have started using them for spam too.
13625 - It turns out we couldn't bootstrap a network since we added
13626 reachability detection in 0.1.0.1-rc. Good thing the Tor network
13627 has never gone down. Add an AssumeReachable config option to let
13628 servers and dirservers bootstrap. When we're trying to build a
13629 high-uptime or high-bandwidth circuit but there aren't enough
13630 suitable servers, try being less picky rather than simply failing.
13631 - Our logic to decide if the OR we connected to was the right guy
13632 was brittle and maybe open to a mitm for unverified routers.
13633 - We weren't cannibalizing circuits correctly for
13634 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
13635 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
13636 build those from scratch. This should make hidden services faster.
13637 - Predict required circuits better, with an eye toward making hidden
13638 services faster on the service end.
13639 - Retry streams if the exit node sends back a 'misc' failure. This
13640 should result in fewer random failures. Also, after failing
13641 from resolve failed or misc, reset the num failures, so we give
13642 it a fair shake next time we try.
13643 - Clean up the rendezvous warn log msgs, and downgrade some to info.
13644 - Reduce severity on logs about dns worker spawning and culling.
13645 - When we're shutting down and we do something like try to post a
13646 server descriptor or rendezvous descriptor, don't complain that
13647 we seem to be unreachable. Of course we are, we're shutting down.
13648 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
13649 We don't use them yet, but maybe one day our DNS resolver will be
13650 able to discover them.
13651 - Make ContactInfo mandatory for authoritative directory servers.
13652 - Require server descriptors to list IPv4 addresses -- hostnames
13653 are no longer allowed. This also fixes some potential security
13654 problems with people providing hostnames as their address and then
13655 preferentially resolving them to partition users.
13656 - Change log line for unreachability to explicitly suggest /etc/hosts
13657 as the culprit. Also make it clearer what IP address and ports we're
13658 testing for reachability.
13659 - Put quotes around user-supplied strings when logging so users are
13660 more likely to realize if they add bad characters (like quotes)
13662 - Let auth dir servers start without specifying an Address config
13664 - Make unit tests (and other invocations that aren't the real Tor)
13665 run without launching listeners, creating subdirectories, and so on.
13668 Changes in version 0.1.1.5-alpha - 2005-08-08
13669 o Bugfixes included in 0.1.0.14.
13671 o Bugfixes on 0.1.0.x:
13672 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
13673 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
13674 it would silently using ignore the 6668.
13677 Changes in version 0.1.0.14 - 2005-08-08
13678 o Bugfixes on 0.1.0.x:
13679 - Fix the other half of the bug with crypto handshakes
13681 - Fix an assert trigger if you send a 'signal term' via the
13682 controller when it's listening for 'event info' messages.
13685 Changes in version 0.1.1.4-alpha - 2005-08-04
13686 o Bugfixes included in 0.1.0.13.
13689 - Improve tor_gettimeofday() granularity on windows.
13690 - Make clients regenerate their keys when their IP address changes.
13691 - Implement some more GETINFO goodness: expose helper nodes, config
13692 options, getinfo keys.
13695 Changes in version 0.1.0.13 - 2005-08-04
13696 o Bugfixes on 0.1.0.x:
13697 - Fix a critical bug in the security of our crypto handshakes.
13698 - Fix a size_t underflow in smartlist_join_strings2() that made
13699 it do bad things when you hand it an empty smartlist.
13700 - Fix Windows installer to ship Tor license (thanks to Aphex for
13701 pointing out this oversight) and put a link to the doc directory
13703 - Explicitly set no-unaligned-access for sparc: it turns out the
13704 new gcc's let you compile broken code, but that doesn't make it
13708 Changes in version 0.1.1.3-alpha - 2005-07-23
13709 o Bugfixes on 0.1.1.2-alpha:
13710 - Fix a bug in handling the controller's "post descriptor"
13712 - Fix several bugs in handling the controller's "extend circuit"
13714 - Fix a bug in handling the controller's "stream status" event.
13715 - Fix an assert failure if we have a controller listening for
13716 circuit events and we go offline.
13717 - Re-allow hidden service descriptors to publish 0 intro points.
13718 - Fix a crash when generating your hidden service descriptor if
13719 you don't have enough intro points already.
13721 o New features on 0.1.1.2-alpha:
13722 - New controller function "getinfo accounting", to ask how
13723 many bytes we've used in this time period.
13724 - Experimental support for helper nodes: a lot of the risk from
13725 a small static adversary comes because users pick new random
13726 nodes every time they rebuild a circuit. Now users will try to
13727 stick to the same small set of entry nodes if they can. Not
13728 enabled by default yet.
13730 o Bugfixes on 0.1.0.12:
13731 - If you're an auth dir server, always publish your dirport,
13732 even if you haven't yet found yourself to be reachable.
13733 - Fix a size_t underflow in smartlist_join_strings2() that made
13734 it do bad things when you hand it an empty smartlist.
13737 Changes in version 0.1.0.12 - 2005-07-18
13738 o New directory servers:
13739 - tor26 has changed IP address.
13741 o Bugfixes on 0.1.0.x:
13742 - Fix a possible double-free in tor_gzip_uncompress().
13743 - When --disable-threads is set, do not search for or link against
13744 pthreads libraries.
13745 - Don't trigger an assert if an authoritative directory server
13746 claims its dirport is 0.
13747 - Fix bug with removing Tor as an NT service: some people were
13748 getting "The service did not return an error." Thanks to Matt
13752 Changes in version 0.1.1.2-alpha - 2005-07-15
13753 o New directory servers:
13754 - tor26 has changed IP address.
13756 o Bugfixes on 0.1.0.x, crashes/leaks:
13757 - Port the servers-not-obeying-their-exit-policies fix from
13759 - Fix an fd leak in start_daemon().
13760 - On Windows, you can't always reopen a port right after you've
13761 closed it. So change retry_listeners() to only close and re-open
13762 ports that have changed.
13763 - Fix a possible double-free in tor_gzip_uncompress().
13765 o Bugfixes on 0.1.0.x, usability:
13766 - When tor_socketpair() fails in Windows, give a reasonable
13767 Windows-style errno back.
13768 - Let people type "tor --install" as well as "tor -install" when
13770 want to make it an NT service.
13771 - NT service patch from Matt Edman to improve error messages.
13772 - When the controller asks for a config option with an abbreviated
13773 name, give the full name in our response.
13774 - Correct the man page entry on TrackHostExitsExpire.
13775 - Looks like we were never delivering deflated (i.e. compressed)
13776 running-routers lists, even when asked. Oops.
13777 - When --disable-threads is set, do not search for or link against
13778 pthreads libraries.
13780 o Bugfixes on 0.1.1.x:
13781 - Fix a seg fault with autodetecting which controller version is
13785 - New hidden service descriptor format: put a version in it, and
13786 let people specify introduction/rendezvous points that aren't
13787 in "the directory" (which is subjective anyway).
13788 - Allow the DEBUG controller event to work again. Mark certain log
13789 entries as "don't tell this to controllers", so we avoid cycles.
13792 Changes in version 0.1.0.11 - 2005-06-30
13793 o Bugfixes on 0.1.0.x:
13794 - Fix major security bug: servers were disregarding their
13795 exit policies if clients behaved unexpectedly.
13796 - Make OS X init script check for missing argument, so we don't
13797 confuse users who invoke it incorrectly.
13798 - Fix a seg fault in "tor --hash-password foo".
13799 - The MAPADDRESS control command was broken.
13802 Changes in version 0.1.1.1-alpha - 2005-06-29
13804 - Make OS X init script check for missing argument, so we don't
13805 confuse users who invoke it incorrectly.
13806 - Fix a seg fault in "tor --hash-password foo".
13807 - Fix a possible way to DoS dirservers.
13808 - When we complain that your exit policy implicitly allows local or
13809 private address spaces, name them explicitly so operators can
13811 - Make the log message less scary when all the dirservers are
13812 temporarily unreachable.
13813 - We were printing the number of idle dns workers incorrectly when
13817 - Revised controller protocol (version 1) that uses ascii rather
13818 than binary. Add supporting libraries in python and java so you
13819 can use the controller from your applications without caring how
13820 our protocol works.
13821 - Spiffy new support for crypto hardware accelerators. Can somebody
13825 Changes in version 0.0.9.10 - 2005-06-16
13826 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
13827 - Refuse relay cells that claim to have a length larger than the
13828 maximum allowed. This prevents a potential attack that could read
13829 arbitrary memory (e.g. keys) from an exit server's process
13833 Changes in version 0.1.0.10 - 2005-06-14
13834 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
13835 libevent before 1.1a.
13838 Changes in version 0.1.0.9-rc - 2005-06-09
13840 - Reset buf->highwater every time buf_shrink() is called, not just on
13841 a successful shrink. This was causing significant memory bloat.
13842 - Fix buffer overflow when checking hashed passwords.
13843 - Security fix: if seeding the RNG on Win32 fails, quit.
13844 - Allow seeding the RNG on Win32 even when you're not running as
13846 - Disable threading on Solaris too. Something is wonky with it,
13847 cpuworkers, and reentrant libs.
13848 - Reenable the part of the code that tries to flush as soon as an
13849 OR outbuf has a full TLS record available. Perhaps this will make
13850 OR outbufs not grow as huge except in rare cases, thus saving lots
13851 of CPU time plus memory.
13852 - Reject malformed .onion addresses rather then passing them on as
13853 normal web requests.
13854 - Adapt patch from Adam Langley: fix possible memory leak in
13855 tor_lookup_hostname().
13856 - Initialize libevent later in the startup process, so the logs are
13857 already established by the time we start logging libevent warns.
13858 - Use correct errno on win32 if libevent fails.
13859 - Check and warn about known-bad/slow libevent versions.
13860 - Pay more attention to the ClientOnly config option.
13861 - Have torctl.in/tor.sh.in check for location of su binary (needed
13863 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
13864 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
13865 HttpProxyAuthenticator
13866 - Stop warning about sigpipes in the logs. We're going to
13867 pretend that getting these occassionally is normal and fine.
13868 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
13870 installer screens; and don't put stuff into StartupItems unless
13871 the user asks you to.
13872 - Require servers that use the default dirservers to have public IP
13873 addresses. We have too many servers that are configured with private
13874 IPs and their admins never notice the log entries complaining that
13875 their descriptors are being rejected.
13876 - Add OSX uninstall instructions. An actual uninstall script will
13880 Changes in version 0.1.0.8-rc - 2005-05-23
13882 - It turns out that kqueue on OS X 10.3.9 was causing kernel
13883 panics. Disable kqueue on all OS X Tors.
13884 - Fix RPM: remove duplicate line accidentally added to the rpm
13886 - Disable threads on openbsd too, since its gethostaddr is not
13888 - Tolerate libevent 0.8 since it still works, even though it's
13890 - Enable building on Red Hat 9.0 again.
13891 - Allow the middle hop of the testing circuit to be running any
13892 version, now that most of them have the bugfix to let them connect
13893 to unknown servers. This will allow reachability testing to work
13894 even when 0.0.9.7-0.0.9.9 become obsolete.
13895 - Handle relay cells with rh.length too large. This prevents
13896 a potential attack that could read arbitrary memory (maybe even
13897 keys) from the exit server's process.
13898 - We screwed up the dirport reachability testing when we don't yet
13899 have a cached version of the directory. Hopefully now fixed.
13900 - Clean up router_load_single_router() (used by the controller),
13901 so it doesn't seg fault on error.
13902 - Fix a minor memory leak when somebody establishes an introduction
13903 point at your Tor server.
13904 - If a socks connection ends because read fails, don't warn that
13905 you're not sending a socks reply back.
13908 - Add HttpProxyAuthenticator config option too, that works like
13909 the HttpsProxyAuthenticator config option.
13910 - Encode hashed controller passwords in hex instead of base64,
13911 to make it easier to write controllers.
13914 Changes in version 0.1.0.7-rc - 2005-05-17
13916 - Fix a bug in the OS X package installer that prevented it from
13917 installing on Tiger.
13918 - Fix a script bug in the OS X package installer that made it
13919 complain during installation.
13920 - Find libevent even if it's hiding in /usr/local/ and your
13921 CFLAGS and LDFLAGS don't tell you to look there.
13922 - Be able to link with libevent as a shared library (the default
13923 after 1.0d), even if it's hiding in /usr/local/lib and even
13924 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
13925 assuming you're running gcc. Otherwise fail and give a useful
13927 - Fix a bug in the RPM packager: set home directory for _tor to
13928 something more reasonable when first installing.
13929 - Free a minor amount of memory that is still reachable on exit.
13932 Changes in version 0.1.0.6-rc - 2005-05-14
13934 - Implement --disable-threads configure option. Disable threads on
13935 netbsd by default, because it appears to have no reentrant resolver
13937 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
13938 release (1.1) detects and disables kqueue if it's broken.
13939 - Append default exit policy before checking for implicit internal
13940 addresses. Now we don't log a bunch of complaints on startup
13941 when using the default exit policy.
13942 - Some people were putting "Address " in their torrc, and they had
13943 a buggy resolver that resolved " " to 0.0.0.0. Oops.
13944 - If DataDir is ~/.tor, and that expands to /.tor, then default to
13945 LOCALSTATEDIR/tor instead.
13946 - Fix fragmented-message bug in TorControl.py.
13947 - Resolve a minor bug which would prevent unreachable dirports
13948 from getting suppressed in the published descriptor.
13949 - When the controller gave us a new descriptor, we weren't resolving
13950 it immediately, so Tor would think its address was 0.0.0.0 until
13951 we fetched a new directory.
13952 - Fix an uppercase/lowercase case error in suppressing a bogus
13953 libevent warning on some Linuxes.
13956 - Begin scrubbing sensitive strings from logs by default. Turn off
13957 the config option SafeLogging if you need to do debugging.
13958 - Switch to a new buffer management algorithm, which tries to avoid
13959 reallocing and copying quite as much. In first tests it looks like
13960 it uses *more* memory on average, but less cpu.
13961 - First cut at support for "create-fast" cells. Clients can use
13962 these when extending to their first hop, since the TLS already
13963 provides forward secrecy and authentication. Not enabled on
13965 - When dirservers refuse a router descriptor, we now log its
13966 contactinfo, platform, and the poster's IP address.
13967 - Call tor_free_all instead of connections_free_all after forking, to
13968 save memory on systems that need to fork.
13969 - Whine at you if you're a server and you don't set your contactinfo.
13970 - Implement --verify-config command-line option to check if your torrc
13971 is valid without actually launching Tor.
13972 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
13973 rather than just rejecting it.
13976 Changes in version 0.1.0.5-rc - 2005-04-27
13978 - Stop trying to print a null pointer if an OR conn fails because
13979 we didn't like its cert.
13981 - Switch our internal buffers implementation to use a ring buffer,
13982 to hopefully improve performance for fast servers a lot.
13983 - Add HttpsProxyAuthenticator support (basic auth only), based
13984 on patch from Adam Langley.
13985 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
13986 the fast servers that have been joining lately.
13987 - Give hidden service accesses extra time on the first attempt,
13988 since 60 seconds is often only barely enough. This might improve
13990 - Improve performance for dirservers: stop re-parsing the whole
13991 directory every time you regenerate it.
13992 - Add more debugging info to help us find the weird dns freebsd
13993 pthreads bug; cleaner debug messages to help track future issues.
13996 Changes in version 0.0.9.9 - 2005-04-23
13997 o Bugfixes on 0.0.9.x:
13998 - If unofficial Tor clients connect and send weird TLS certs, our
13999 Tor server triggers an assert. This release contains a minimal
14000 backport from the broader fix that we put into 0.1.0.4-rc.
14003 Changes in version 0.1.0.4-rc - 2005-04-23
14005 - If unofficial Tor clients connect and send weird TLS certs, our
14006 Tor server triggers an assert. Stop asserting, and start handling
14007 TLS errors better in other situations too.
14008 - When the controller asks us to tell it about all the debug-level
14009 logs, it turns out we were generating debug-level logs while
14010 telling it about them, which turns into a bad loop. Now keep
14011 track of whether you're sending a debug log to the controller,
14012 and don't log when you are.
14013 - Fix the "postdescriptor" feature of the controller interface: on
14014 non-complete success, only say "done" once.
14016 - Clients are now willing to load balance over up to 2mB, not 1mB,
14017 of advertised bandwidth capacity.
14018 - Add a NoPublish config option, so you can be a server (e.g. for
14019 testing running Tor servers in other Tor networks) without
14020 publishing your descriptor to the primary dirservers.
14023 Changes in version 0.1.0.3-rc - 2005-04-08
14024 o Improvements on 0.1.0.2-rc:
14025 - Client now retries when streams end early for 'hibernating' or
14026 'resource limit' reasons, rather than failing them.
14027 - More automated handling for dirserver operators:
14028 - Automatically approve nodes running 0.1.0.2-rc or later,
14029 now that the the reachability detection stuff is working.
14030 - Now we allow two unverified servers with the same nickname
14031 but different keys. But if a nickname is verified, only that
14032 nickname+key are allowed.
14033 - If you're an authdirserver connecting to an address:port,
14034 and it's not the OR you were expecting, forget about that
14035 descriptor. If he *was* the one you were expecting, then forget
14036 about all other descriptors for that address:port.
14037 - Allow servers to publish descriptors from 12 hours in the future.
14038 Corollary: only whine about clock skew from the dirserver if
14039 he's a trusted dirserver (since now even verified servers could
14040 have quite wrong clocks).
14041 - Adjust maximum skew and age for rendezvous descriptors: let skew
14042 be 48 hours rather than 90 minutes.
14043 - Efficiency improvements:
14044 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
14045 it much faster to look up a circuit for each relay cell.
14046 - Remove most calls to assert_all_pending_dns_resolves_ok(),
14047 since they're eating our cpu on exit nodes.
14048 - Stop wasting time doing a case insensitive comparison for every
14049 dns name every time we do any lookup. Canonicalize the names to
14050 lowercase and be done with it.
14051 - Start sending 'truncated' cells back rather than destroy cells,
14052 if the circuit closes in front of you. This means we won't have
14053 to abandon partially built circuits.
14054 - Only warn once per nickname from add_nickname_list_to_smartlist
14055 per failure, so an entrynode or exitnode choice that's down won't
14057 - Put a note in the torrc about abuse potential with the default
14059 - Revise control spec and implementation to allow all log messages to
14060 be sent to controller with their severities intact (suggested by
14061 Matt Edman). Update TorControl to handle new log event types.
14062 - Provide better explanation messages when controller's POSTDESCRIPTOR
14064 - Stop putting nodename in the Platform string in server descriptors.
14065 It doesn't actually help, and it is confusing/upsetting some people.
14067 o Bugfixes on 0.1.0.2-rc:
14068 - We were printing the host mask wrong in exit policies in server
14069 descriptors. This isn't a critical bug though, since we were still
14070 obeying the exit policy internally.
14071 - Fix Tor when compiled with libevent but without pthreads: move
14072 connection_unregister() from _connection_free() to
14074 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
14075 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
14076 when we look through the connection array, we'll find any of the
14077 cpu/dnsworkers. This is no good.
14079 o Bugfixes on 0.0.9.8:
14080 - Fix possible bug on threading platforms (e.g. win32) which was
14081 leaking a file descriptor whenever a cpuworker or dnsworker died.
14082 - When using preferred entry or exit nodes, ignore whether the
14083 circuit wants uptime or capacity. They asked for the nodes, they
14085 - chdir() to your datadirectory at the *end* of the daemonize process,
14086 not the beginning. This was a problem because the first time you
14087 run tor, if your datadir isn't there, and you have runasdaemon set
14088 to 1, it will try to chdir to it before it tries to create it. Oops.
14089 - Handle changed router status correctly when dirserver reloads
14090 fingerprint file. We used to be dropping all unverified descriptors
14091 right then. The bug was hidden because we would immediately
14092 fetch a directory from another dirserver, which would include the
14093 descriptors we just dropped.
14094 - When we're connecting to an OR and he's got a different nickname/key
14095 than we were expecting, only complain loudly if we're an OP or a
14096 dirserver. Complaining loudly to the OR admins just confuses them.
14097 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
14098 artificially capped at 500kB.
14101 Changes in version 0.0.9.8 - 2005-04-07
14102 o Bugfixes on 0.0.9.x:
14103 - We have a bug that I haven't found yet. Sometimes, very rarely,
14104 cpuworkers get stuck in the 'busy' state, even though the cpuworker
14105 thinks of itself as idle. This meant that no new circuits ever got
14106 established. Here's a workaround to kill any cpuworker that's been
14107 busy for more than 100 seconds.
14110 Changes in version 0.1.0.2-rc - 2005-04-01
14111 o Bugfixes on 0.1.0.1-rc:
14112 - Fixes on reachability detection:
14113 - Don't check for reachability while hibernating.
14114 - If ORPort is reachable but DirPort isn't, still publish the
14115 descriptor, but zero out DirPort until it's found reachable.
14116 - When building testing circs for ORPort testing, use only
14117 high-bandwidth nodes, so fewer circuits fail.
14118 - Complain about unreachable ORPort separately from unreachable
14119 DirPort, so the user knows what's going on.
14120 - Make sure we only conclude ORPort reachability if we didn't
14121 initiate the conn. Otherwise we could falsely conclude that
14122 we're reachable just because we connected to the guy earlier
14123 and he used that same pipe to extend to us.
14124 - Authdirservers shouldn't do ORPort reachability detection,
14125 since they're in clique mode, so it will be rare to find a
14126 server not already connected to them.
14127 - When building testing circuits, always pick middle hops running
14128 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
14129 bug. (This is a kludge; it will go away when 0.0.9.x becomes
14131 - When we decide we're reachable, actually publish our descriptor
14133 - Fix bug in redirectstream in the controller.
14134 - Fix the state descriptor strings so logs don't claim edge streams
14135 are in a different state than they actually are.
14136 - Use recent libevent features when possible (this only really affects
14137 win32 and osx right now, because the new libevent with these
14138 features hasn't been released yet). Add code to suppress spurious
14140 - Prevent possible segfault in connection_close_unattached_ap().
14141 - Fix newlines on torrc in win32.
14142 - Improve error msgs when tor-resolve fails.
14144 o Improvements on 0.0.9.x:
14145 - New experimental script tor/contrib/ExerciseServer.py (needs more
14146 work) that uses the controller interface to build circuits and
14147 fetch pages over them. This will help us bootstrap servers that
14148 have lots of capacity but haven't noticed it yet.
14149 - New experimental script tor/contrib/PathDemo.py (needs more work)
14150 that uses the controller interface to let you choose whole paths
14152 "<hostname>.<path,separated by dots>.<length of path>.path"
14153 - When we've connected to an OR and handshaked but didn't like
14154 the result, we were closing the conn without sending destroy
14155 cells back for pending circuits. Now send those destroys.
14158 Changes in version 0.0.9.7 - 2005-04-01
14159 o Bugfixes on 0.0.9.x:
14160 - Fix another race crash bug (thanks to Glenn Fink for reporting).
14161 - Compare identity to identity, not to nickname, when extending to
14162 a router not already in the directory. This was preventing us from
14163 extending to unknown routers. Oops.
14164 - Make sure to create OS X Tor user in <500 range, so we aren't
14165 creating actual system users.
14166 - Note where connection-that-hasn't-sent-end was marked, and fix
14167 a few really loud instances of this harmless bug (it's fixed more
14171 Changes in version 0.1.0.1-rc - 2005-03-28
14173 - Add reachability testing. Your Tor server will automatically try
14174 to see if its ORPort and DirPort are reachable from the outside,
14175 and it won't upload its descriptor until it decides they are.
14176 - Handle unavailable hidden services better. Handle slow or busy
14177 hidden services better.
14178 - Add support for CONNECTing through https proxies, with "HttpsProxy"
14180 - New exit policy: accept most low-numbered ports, rather than
14181 rejecting most low-numbered ports.
14182 - More Tor controller support (still experimental). See
14183 http://tor.eff.org/doc/control-spec.txt for all the new features,
14184 including signals to emulate unix signals from any platform;
14185 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
14186 closestream; closecircuit; etc.
14187 - Make nt services work and start on startup on win32 (based on
14188 patch by Matt Edman).
14189 - Add a new AddressMap config directive to rewrite incoming socks
14190 addresses. This lets you, for example, declare an implicit
14191 required exit node for certain sites.
14192 - Add a new TrackHostExits config directive to trigger addressmaps
14193 for certain incoming socks addresses -- for sites that break when
14194 your exit keeps changing (based on patch by Mike Perry).
14195 - Redo the client-side dns cache so it's just an addressmap too.
14196 - Notice when our IP changes, and reset stats/uptime/reachability.
14197 - When an application is using socks5, give him the whole variety of
14198 potential socks5 responses (connect refused, host unreachable, etc),
14199 rather than just "success" or "failure".
14200 - A more sane version numbering system. See
14201 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
14202 - New contributed script "exitlist": a simple python script to
14203 parse directories and find Tor nodes that exit to listed
14205 - New contributed script "privoxy-tor-toggle" to toggle whether
14206 Privoxy uses Tor. Seems to be configured for Debian by default.
14207 - Report HTTP reasons to client when getting a response from directory
14208 servers -- so you can actually know what went wrong.
14209 - New config option MaxAdvertisedBandwidth which lets you advertise
14210 a low bandwidthrate (to not attract as many circuits) while still
14211 allowing a higher bandwidthrate in reality.
14213 o Robustness/stability fixes:
14214 - Make Tor use Niels Provos's libevent instead of its current
14215 poll-but-sometimes-select mess. This will let us use faster async
14216 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
14218 - pthread support now too. This was forced because when we forked,
14219 we ended up wasting a lot of duplicate ram over time. Also switch
14220 to foo_r versions of some library calls to allow reentry and
14222 - Better handling for heterogeneous / unreliable nodes:
14223 - Annotate circuits w/ whether they aim to contain high uptime nodes
14224 and/or high capacity nodes. When building circuits, choose
14226 - This means that every single node in an intro rend circuit,
14227 not just the last one, will have a minimum uptime.
14228 - New config option LongLivedPorts to indicate application streams
14229 that will want high uptime circuits.
14230 - Servers reset uptime when a dir fetch entirely fails. This
14231 hopefully reflects stability of the server's network connectivity.
14232 - If somebody starts his tor server in Jan 2004 and then fixes his
14233 clock, don't make his published uptime be a year.
14234 - Reset published uptime when you wake up from hibernation.
14235 - Introduce a notion of 'internal' circs, which are chosen without
14236 regard to the exit policy of the last hop. Intro and rendezvous
14237 circs must be internal circs, to avoid leaking information. Resolve
14238 and connect streams can use internal circs if they want.
14239 - New circuit pooling algorithm: make sure to have enough circs around
14240 to satisfy any predicted ports, and also make sure to have 2 internal
14241 circs around if we've required internal circs lately (and with high
14242 uptime if we've seen that lately too).
14243 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
14244 which describes how often we retry making new circuits if current
14245 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
14246 how long we're willing to make use of an already-dirty circuit.
14247 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
14248 circ as necessary, if there are any completed ones lying around
14249 when we try to launch one.
14250 - Make hidden services try to establish a rendezvous for 30 seconds,
14251 rather than for n (where n=3) attempts to build a circuit.
14252 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
14253 "ShutdownWaitLength".
14254 - Try to be more zealous about calling connection_edge_end when
14255 things go bad with edge conns in connection.c.
14256 - Revise tor-spec to add more/better stream end reasons.
14257 - Revise all calls to connection_edge_end to avoid sending "misc",
14258 and to take errno into account where possible.
14261 - Fix a race condition that can trigger an assert, when we have a
14262 pending create cell and an OR connection fails right then.
14263 - Fix several double-mark-for-close bugs, e.g. where we were finding
14264 a conn for a cell even if that conn is already marked for close.
14265 - Make sequence of log messages when starting on win32 with no config
14266 file more reasonable.
14267 - When choosing an exit node for a new non-internal circ, don't take
14268 into account whether it'll be useful for any pending x.onion
14269 addresses -- it won't.
14270 - Turn addr_policy_compare from a tristate to a quadstate; this should
14271 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
14272 for google.com" problem.
14273 - Make "platform" string in descriptor more accurate for Win32 servers,
14274 so it's not just "unknown platform".
14275 - Fix an edge case in parsing config options (thanks weasel).
14276 If they say "--" on the commandline, it's not an option.
14277 - Reject odd-looking addresses at the client (e.g. addresses that
14278 contain a colon), rather than having the server drop them because
14280 - tor-resolve requests were ignoring .exit if there was a working circuit
14281 they could use instead.
14282 - REUSEADDR on normal platforms means you can rebind to the port
14283 right after somebody else has let it go. But REUSEADDR on win32
14284 means to let you bind to the port _even when somebody else
14285 already has it bound_! So, don't do that on Win32.
14286 - Change version parsing logic: a version is "obsolete" if it is not
14287 recommended and (1) there is a newer recommended version in the
14288 same series, or (2) there are no recommended versions in the same
14289 series, but there are some recommended versions in a newer series.
14290 A version is "new" if it is newer than any recommended version in
14292 - Stop most cases of hanging up on a socks connection without sending
14296 - Require BandwidthRate to be at least 20kB/s for servers.
14297 - When a dirserver causes you to give a warn, mention which dirserver
14299 - New config option DirAllowPrivateAddresses for authdirservers.
14300 Now by default they refuse router descriptors that have non-IP or
14301 private-IP addresses.
14302 - Stop publishing socksport in the directory, since it's not
14303 actually meant to be public. For compatibility, publish a 0 there
14305 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
14306 smart" value, that is low for servers and high for clients.
14307 - If our clock jumps forward by 100 seconds or more, assume something
14308 has gone wrong with our network and abandon all not-yet-used circs.
14309 - Warn when exit policy implicitly allows local addresses.
14310 - If we get an incredibly skewed timestamp from a dirserver mirror
14311 that isn't a verified OR, don't warn -- it's probably him that's
14313 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
14314 cookies to disk and doesn't log each web request to disk. (Thanks
14315 to Brett Carrington for pointing this out.)
14316 - When a client asks us for a dir mirror and we don't have one,
14317 launch an attempt to get a fresh one.
14318 - If we're hibernating and we get a SIGINT, exit immediately.
14319 - Add --with-dmalloc ./configure option, to track memory leaks.
14320 - And try to free all memory on closing, so we can detect what
14322 - Cache local dns resolves correctly even when they're .exit
14324 - Give a better warning when some other server advertises an
14325 ORPort that is actually an apache running ssl.
14326 - Add "opt hibernating 1" to server descriptor to make it clearer
14327 whether the server is hibernating.
14330 Changes in version 0.0.9.6 - 2005-03-24
14331 o Bugfixes on 0.0.9.x (crashes and asserts):
14332 - Add new end stream reasons to maintainance branch. Fix bug where
14333 reason (8) could trigger an assert. Prevent bug from recurring.
14334 - Apparently win32 stat wants paths to not end with a slash.
14335 - Fix assert triggers in assert_cpath_layer_ok(), where we were
14336 blowing away the circuit that conn->cpath_layer points to, then
14337 checking to see if the circ is well-formed. Backport check to make
14338 sure we dont use the cpath on a closed connection.
14339 - Prevent circuit_resume_edge_reading_helper() from trying to package
14340 inbufs for marked-for-close streams.
14341 - Don't crash on hup if your options->address has become unresolvable.
14342 - Some systems (like OS X) sometimes accept() a connection and tell
14343 you the remote host is 0.0.0.0:0. If this happens, due to some
14344 other mis-features, we get confused; so refuse the conn for now.
14346 o Bugfixes on 0.0.9.x (other):
14347 - Fix harmless but scary "Unrecognized content encoding" warn message.
14348 - Add new stream error reason: TORPROTOCOL reason means "you are not
14349 speaking a version of Tor I understand; say bye-bye to your stream."
14350 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
14351 into the future, now that we are more tolerant of skew. This
14352 resolves a bug where a Tor server would refuse to cache a directory
14353 because all the directories it gets are too far in the future;
14354 yet the Tor server never logs any complaints about clock skew.
14355 - Mac packaging magic: make man pages useable, and do not overwrite
14356 existing torrc files.
14357 - Make OS X log happily to /var/log/tor/tor.log
14360 Changes in version 0.0.9.5 - 2005-02-22
14361 o Bugfixes on 0.0.9.x:
14362 - Fix an assert race at exit nodes when resolve requests fail.
14363 - Stop picking unverified dir mirrors--it only leads to misery.
14364 - Patch from Matt Edman to make NT services work better. Service
14365 support is still not compiled into the executable by default.
14366 - Patch from Dmitri Bely so the Tor service runs better under
14367 the win32 SYSTEM account.
14368 - Make tor-resolve actually work (?) on Win32.
14369 - Fix a sign bug when getrlimit claims to have 4+ billion
14370 file descriptors available.
14371 - Stop refusing to start when bandwidthburst == bandwidthrate.
14372 - When create cells have been on the onion queue more than five
14373 seconds, just send back a destroy and take them off the list.
14376 Changes in version 0.0.9.4 - 2005-02-03
14377 o Bugfixes on 0.0.9:
14378 - Fix an assert bug that took down most of our servers: when
14379 a server claims to have 1 GB of bandwidthburst, don't
14381 - Don't crash as badly if we have spawned the max allowed number
14382 of dnsworkers, or we're out of file descriptors.
14383 - Block more file-sharing ports in the default exit policy.
14384 - MaxConn is now automatically set to the hard limit of max
14385 file descriptors we're allowed (ulimit -n), minus a few for
14387 - Give a clearer message when servers need to raise their
14388 ulimit -n when they start running out of file descriptors.
14389 - SGI Compatibility patches from Jan Schaumann.
14390 - Tolerate a corrupt cached directory better.
14391 - When a dirserver hasn't approved your server, list which one.
14392 - Go into soft hibernation after 95% of the bandwidth is used,
14393 not 99%. This is especially important for daily hibernators who
14394 have a small accounting max. Hopefully it will result in fewer
14395 cut connections when the hard hibernation starts.
14396 - Load-balance better when using servers that claim more than
14397 800kB/s of capacity.
14398 - Make NT services work (experimental, only used if compiled in).
14401 Changes in version 0.0.9.3 - 2005-01-21
14402 o Bugfixes on 0.0.9:
14403 - Backport the cpu use fixes from main branch, so busy servers won't
14404 need as much processor time.
14405 - Work better when we go offline and then come back, or when we
14406 run Tor at boot before the network is up. We do this by
14407 optimistically trying to fetch a new directory whenever an
14408 application request comes in and we think we're offline -- the
14409 human is hopefully a good measure of when the network is back.
14410 - Backport some minimal hidserv bugfixes: keep rend circuits open as
14411 long as you keep using them; actually publish hidserv descriptors
14412 shortly after they change, rather than waiting 20-40 minutes.
14413 - Enable Mac startup script by default.
14414 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
14415 - When you update AllowUnverifiedNodes or FirewallPorts via the
14416 controller's setconf feature, we were always appending, never
14418 - When you update HiddenServiceDir via setconf, it was screwing up
14419 the order of reading the lines, making it fail.
14420 - Do not rewrite a cached directory back to the cache; otherwise we
14421 will think it is recent and not fetch a newer one on startup.
14422 - Workaround for webservers that lie about Content-Encoding: Tor
14423 now tries to autodetect compressed directories and compression
14424 itself. This lets us Proxypass dir fetches through apache.
14427 Changes in version 0.0.9.2 - 2005-01-04
14428 o Bugfixes on 0.0.9 (crashes and asserts):
14429 - Fix an assert on startup when the disk is full and you're logging
14431 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
14432 style address, then we'd crash.
14433 - Fix an assert trigger when the running-routers string we get from
14434 a dirserver is broken.
14435 - Make worker threads start and run on win32. Now win32 servers
14437 - Bandaid (not actually fix, but now it doesn't crash) an assert
14438 where the dns worker dies mysteriously and the main Tor process
14439 doesn't remember anything about the address it was resolving.
14441 o Bugfixes on 0.0.9 (Win32):
14442 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
14443 name out of the warning/assert messages.
14444 - Fix a superficial "unhandled error on read" bug on win32.
14445 - The win32 installer no longer requires a click-through for our
14446 license, since our Free Software license grants rights but does not
14448 - Win32: When connecting to a dirserver fails, try another one
14449 immediately. (This was already working for non-win32 Tors.)
14450 - Stop trying to parse $HOME on win32 when hunting for default
14452 - Make tor-resolve.c work on win32 by calling network_init().
14454 o Bugfixes on 0.0.9 (other):
14455 - Make 0.0.9.x build on Solaris again.
14456 - Due to a fencepost error, we were blowing away the \n when reporting
14457 confvalue items in the controller. So asking for multiple config
14458 values at once couldn't work.
14459 - When listing circuits that are pending on an opening OR connection,
14460 if we're an OR we were listing circuits that *end* at us as
14461 being pending on every listener, dns/cpu worker, etc. Stop that.
14462 - Dirservers were failing to create 'running-routers' or 'directory'
14463 strings if we had more than some threshold of routers. Fix them so
14464 they can handle any number of routers.
14465 - Fix a superficial "Duplicate mark for close" bug.
14466 - Stop checking for clock skew for OR connections, even for servers.
14467 - Fix a fencepost error that was chopping off the last letter of any
14468 nickname that is the maximum allowed nickname length.
14469 - Update URLs in log messages so they point to the new website.
14470 - Fix a potential problem in mangling server private keys while
14471 writing to disk (not triggered yet, as far as we know).
14472 - Include the licenses for other free software we include in Tor,
14473 now that we're shipping binary distributions more regularly.
14476 Changes in version 0.0.9.1 - 2004-12-15
14477 o Bugfixes on 0.0.9:
14478 - Make hibernation actually work.
14479 - Make HashedControlPassword config option work.
14480 - When we're reporting event circuit status to a controller,
14481 don't use the stream status code.
14484 Changes in version 0.0.9 - 2004-12-12
14486 - Clean up manpage and torrc.sample file.
14487 - Clean up severities and text of log warnings.
14489 - Make servers trigger an assert when they enter hibernation.
14492 Changes in version 0.0.9rc7 - 2004-12-08
14493 o Bugfixes on 0.0.9rc:
14494 - Fix a stack-trashing crash when an exit node begins hibernating.
14495 - Avoid looking at unallocated memory while considering which
14496 ports we need to build circuits to cover.
14497 - Stop a sigpipe: when an 'end' cell races with eof from the app,
14498 we shouldn't hold-open-until-flush if the eof arrived first.
14499 - Fix a bug with init_cookie_authentication() in the controller.
14500 - When recommending new-format log lines, if the upper bound is
14501 LOG_ERR, leave it implicit.
14503 o Bugfixes on 0.0.8.1:
14504 - Fix a whole slew of memory leaks.
14505 - Fix isspace() and friends so they still make Solaris happy
14506 but also so they don't trigger asserts on win32.
14507 - Fix parse_iso_time on platforms without strptime (eg win32).
14508 - win32: tolerate extra "readable" events better.
14509 - win32: when being multithreaded, leave parent fdarray open.
14510 - Make unit tests work on win32.
14513 Changes in version 0.0.9rc6 - 2004-12-06
14514 o Bugfixes on 0.0.9pre:
14515 - Clean up some more integer underflow opportunities (not exploitable
14517 - While hibernating, hup should not regrow our listeners.
14518 - Send an end to the streams we close when we hibernate, rather
14519 than just chopping them off.
14520 - React to eof immediately on non-open edge connections.
14522 o Bugfixes on 0.0.8.1:
14523 - Calculate timeout for waiting for a connected cell from the time
14524 we sent the begin cell, not from the time the stream started. If
14525 it took a long time to establish the circuit, we would time out
14526 right after sending the begin cell.
14527 - Fix router_compare_addr_to_addr_policy: it was not treating a port
14528 of * as always matching, so we were picking reject *:* nodes as
14529 exit nodes too. Oops.
14532 - New circuit building strategy: keep a list of ports that we've
14533 used in the past 6 hours, and always try to have 2 circuits open
14534 or on the way that will handle each such port. Seed us with port
14535 80 so web users won't complain that Tor is "slow to start up".
14536 - Make kill -USR1 dump more useful stats about circuits.
14537 - When warning about retrying or giving up, print the address, so
14538 the user knows which one it's talking about.
14539 - If you haven't used a clean circuit in an hour, throw it away,
14540 just to be on the safe side. (This means after 6 hours a totally
14541 unused Tor client will have no circuits open.)
14544 Changes in version 0.0.9rc5 - 2004-12-01
14545 o Bugfixes on 0.0.8.1:
14546 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
14547 - Let resolve conns retry/expire also, rather than sticking around
14549 - If we are using select, make sure we stay within FD_SETSIZE.
14551 o Bugfixes on 0.0.9pre:
14552 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
14553 but doesn't seem to be currently; thanks to Ilja van Sprundel for
14555 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
14556 instead. Impose minima and maxima for all *Period options; impose
14557 even tighter maxima for fetching if we are a caching dirserver.
14558 Clip rather than rejecting.
14559 - Fetch cached running-routers from servers that serve it (that is,
14560 authdirservers and servers running 0.0.9rc5-cvs or later.)
14563 - Accept *:706 (silc) in default exit policy.
14564 - Implement new versioning format for post 0.1.
14565 - Support "foo.nickname.exit" addresses, to let Alice request the
14566 address "foo" as viewed by exit node "nickname". Based on a patch
14568 - Make tor --version --version dump the cvs Id of every file.
14571 Changes in version 0.0.9rc4 - 2004-11-28
14572 o Bugfixes on 0.0.8.1:
14573 - Make windows sockets actually non-blocking (oops), and handle
14574 win32 socket errors better.
14576 o Bugfixes on 0.0.9rc1:
14577 - Actually catch the -USR2 signal.
14580 Changes in version 0.0.9rc3 - 2004-11-25
14581 o Bugfixes on 0.0.8.1:
14582 - Flush the log file descriptor after we print "Tor opening log file",
14583 so we don't see those messages days later.
14585 o Bugfixes on 0.0.9rc1:
14586 - Make tor-resolve work again.
14587 - Avoid infinite loop in tor-resolve if tor hangs up on it.
14588 - Fix an assert trigger for clients/servers handling resolves.
14591 Changes in version 0.0.9rc2 - 2004-11-24
14592 o Bugfixes on 0.0.9rc1:
14593 - I broke socks5 support while fixing the eof bug.
14594 - Allow unitless bandwidths and intervals; they default to bytes
14596 - New servers don't start out hibernating; they are active until
14597 they run out of bytes, so they have a better estimate of how
14598 long it takes, and so their operators can know they're working.
14601 Changes in version 0.0.9rc1 - 2004-11-23
14602 o Bugfixes on 0.0.8.1:
14603 - Finally fix a bug that's been plaguing us for a year:
14604 With high load, circuit package window was reaching 0. Whenever
14605 we got a circuit-level sendme, we were reading a lot on each
14606 socket, but only writing out a bit. So we would eventually reach
14607 eof. This would be noticed and acted on even when there were still
14608 bytes sitting in the inbuf.
14609 - When poll() is interrupted, we shouldn't believe the revents values.
14611 o Bugfixes on 0.0.9pre6:
14612 - Fix hibernate bug that caused pre6 to be broken.
14613 - Don't keep rephist info for routers that haven't had activity for
14614 24 hours. (This matters now that clients have keys, since we track
14616 - Never call close_temp_logs while validating log options.
14617 - Fix backslash-escaping on tor.sh.in and torctl.in.
14620 - Implement weekly/monthly/daily accounting: now you specify your
14621 hibernation properties by
14622 AccountingMax N bytes|KB|MB|GB|TB
14623 AccountingStart day|week|month [day] HH:MM
14624 Defaults to "month 1 0:00".
14625 - Let bandwidth and interval config options be specified as 5 bytes,
14626 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
14627 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
14628 get back to normal.)
14629 - If your requested entry or exit node has advertised bandwidth 0,
14631 - Be more greedy about filling up relay cells -- we try reading again
14632 once we've processed the stuff we read, in case enough has arrived
14633 to fill the last cell completely.
14634 - Apply NT service patch from Osamu Fujino. Still needs more work.
14637 Changes in version 0.0.9pre6 - 2004-11-15
14638 o Bugfixes on 0.0.8.1:
14639 - Fix assert failure on malformed socks4a requests.
14640 - Use identity comparison, not nickname comparison, to choose which
14641 half of circuit-ID-space each side gets to use. This is needed
14642 because sometimes we think of a router as a nickname, and sometimes
14643 as a hex ID, and we can't predict what the other side will do.
14644 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
14645 write() call will fail and we handle it there.
14646 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
14647 and smartlist_len, which are two major profiling offenders.
14649 o Bugfixes on 0.0.9pre5:
14650 - Fix a bug in read_all that was corrupting config files on windows.
14651 - When we're raising the max number of open file descriptors to
14652 'unlimited', don't log that we just raised it to '-1'.
14653 - Include event code with events, as required by control-spec.txt.
14654 - Don't give a fingerprint when clients do --list-fingerprint:
14655 it's misleading, because it will never be the same again.
14656 - Stop using strlcpy in tor_strndup, since it was slowing us
14658 - Remove warn on startup about missing cached-directory file.
14659 - Make kill -USR1 work again.
14660 - Hibernate if we start tor during the "wait for wakeup-time" phase
14661 of an accounting interval. Log our hibernation plans better.
14662 - Authoritative dirservers now also cache their directory, so they
14663 have it on start-up.
14666 - Fetch running-routers; cache running-routers; compress
14667 running-routers; serve compressed running-routers.z
14668 - Add NSI installer script contributed by J Doe.
14669 - Commit VC6 and VC7 workspace/project files.
14670 - Commit a tor.spec for making RPM files, with help from jbash.
14671 - Add contrib/torctl.in contributed by Glenn Fink.
14672 - Implement the control-spec's SAVECONF command, to write your
14673 configuration to torrc.
14674 - Get cookie authentication for the controller closer to working.
14675 - Include control-spec.txt in the tarball.
14676 - When set_conf changes our server descriptor, upload a new copy.
14677 But don't upload it too often if there are frequent changes.
14678 - Document authentication config in man page, and document signals
14680 - Clean up confusing parts of man page and torrc.sample.
14681 - Make expand_filename handle ~ and ~username.
14682 - Use autoconf to enable largefile support where necessary. Use
14683 ftello where available, since ftell can fail at 2GB.
14684 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
14685 log more informatively.
14686 - Give a slightly more useful output for "tor -h".
14687 - Refuse application socks connections to port 0.
14688 - Check clock skew for verified servers, but allow unverified
14689 servers and clients to have any clock skew.
14690 - Break DirFetchPostPeriod into:
14691 - DirFetchPeriod for fetching full directory,
14692 - StatusFetchPeriod for fetching running-routers,
14693 - DirPostPeriod for posting server descriptor,
14694 - RendPostPeriod for posting hidden service descriptors.
14695 - Make sure the hidden service descriptors are at a random offset
14696 from each other, to hinder linkability.
14699 Changes in version 0.0.9pre5 - 2004-11-09
14700 o Bugfixes on 0.0.9pre4:
14701 - Fix a seg fault in unit tests (doesn't affect main program).
14702 - Fix an assert bug where a hidden service provider would fail if
14703 the first hop of his rendezvous circuit was down.
14704 - Hidden service operators now correctly handle version 1 style
14705 INTRODUCE1 cells (nobody generates them still, so not a critical
14707 - If do_hup fails, actually notice.
14708 - Handle more errnos from accept() without closing the listener.
14709 Some OpenBSD machines were closing their listeners because
14710 they ran out of file descriptors.
14711 - Send resolve cells to exit routers that are running a new
14712 enough version of the resolve code to work right.
14713 - Better handling of winsock includes on non-MSV win32 compilers.
14714 - Some people had wrapped their tor client/server in a script
14715 that would restart it whenever it died. This did not play well
14716 with our "shut down if your version is obsolete" code. Now people
14717 don't fetch a new directory if their local cached version is
14719 - Make our autogen.sh work on ksh as well as bash.
14722 - Hibernation: New config option "AccountingMaxKB" lets you
14723 set how many KBytes per month you want to allow your server to
14724 consume. Rather than spreading those bytes out evenly over the
14725 month, we instead hibernate for some of the month and pop up
14726 at a deterministic time, work until the bytes are consumed, then
14727 hibernate again. Config option "MonthlyAccountingStart" lets you
14728 specify which day of the month your billing cycle starts on.
14729 - Control interface: a separate program can now talk to your
14730 client/server over a socket, and get/set config options, receive
14731 notifications of circuits and streams starting/finishing/dying,
14732 bandwidth used, etc. The next step is to get some GUIs working.
14733 Let us know if you want to help out. See doc/control-spec.txt .
14734 - Ship a contrib/tor-control.py as an example script to interact
14735 with the control port.
14736 - "tor --hash-password zzyxz" will output a salted password for
14737 use in authenticating to the control interface.
14738 - New log format in config:
14739 "Log minsev[-maxsev] stdout|stderr|syslog" or
14740 "Log minsev[-maxsev] file /var/foo"
14743 - DirPolicy config option, to let people reject incoming addresses
14744 from their dirserver.
14745 - "tor --list-fingerprint" will list your identity key fingerprint
14747 - Add "pass" target for RedirectExit, to make it easier to break
14748 out of a sequence of RedirectExit rules.
14749 - Clients now generate a TLS cert too, in preparation for having
14750 them act more like real nodes.
14751 - Ship src/win32/ in the tarball, so people can use it to build.
14752 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
14754 - New "router-status" line in directory, to better bind each verified
14755 nickname to its identity key.
14756 - Deprecate unofficial config option abbreviations, and abbreviations
14757 not on the command line.
14758 - Add a pure-C tor-resolve implementation.
14759 - Use getrlimit and friends to ensure we can reach MaxConn (currently
14760 1024) file descriptors.
14762 o Code security improvements, inspired by Ilja:
14763 - Replace sprintf with snprintf. (I think they were all safe, but
14765 - Replace strcpy/strncpy with strlcpy in more places.
14766 - Avoid strcat; use snprintf or strlcat instead.
14767 - snprintf wrapper with consistent (though not C99) overflow behavior.
14770 Changes in version 0.0.9pre4 - 2004-10-17
14771 o Bugfixes on 0.0.9pre3:
14772 - If the server doesn't specify an exit policy, use the real default
14773 exit policy, not reject *:*.
14774 - Ignore fascistfirewall when uploading/downloading hidden service
14775 descriptors, since we go through Tor for those; and when using
14776 an HttpProxy, since we assume it can reach them all.
14777 - When looking for an authoritative dirserver, use only the ones
14778 configured at boot. Don't bother looking in the directory.
14779 - The rest of the fix for get_default_conf_file() on older win32.
14780 - Make 'Routerfile' config option obsolete.
14783 - New 'MyFamily nick1,...' config option for a server to
14784 specify other servers that shouldn't be used in the same circuit
14785 with it. Only believed if nick1 also specifies us.
14786 - New 'NodeFamily nick1,nick2,...' config option for a client to
14787 specify nodes that it doesn't want to use in the same circuit.
14788 - New 'Redirectexit pattern address:port' config option for a
14789 server to redirect exit connections, e.g. to a local squid.
14792 Changes in version 0.0.9pre3 - 2004-10-13
14793 o Bugfixes on 0.0.8.1:
14794 - Better torrc example lines for dirbindaddress and orbindaddress.
14795 - Improved bounds checking on parsed ints (e.g. config options and
14796 the ones we find in directories.)
14797 - Better handling of size_t vs int, so we're more robust on 64
14799 - Fix the rest of the bug where a newly started OR would appear
14800 as unverified even after we've added his fingerprint and hupped
14802 - Fix a bug from 0.0.7: when read() failed on a stream, we would
14803 close it without sending back an end. So 'connection refused'
14804 would simply be ignored and the user would get no response.
14806 o Bugfixes on 0.0.9pre2:
14807 - Serving the cached-on-disk directory to people is bad. We now
14808 provide no directory until we've fetched a fresh one.
14809 - Workaround for bug on windows where cached-directories get crlf
14811 - Make get_default_conf_file() work on older windows too.
14812 - If we write a *:* exit policy line in the descriptor, don't write
14813 any more exit policy lines.
14816 - Use only 0.0.9pre1 and later servers for resolve cells.
14817 - Make the dirservers file obsolete.
14818 - Include a dir-signing-key token in directories to tell the
14819 parsing entity which key is being used to sign.
14820 - Remove the built-in bulky default dirservers string.
14821 - New config option "Dirserver %s:%d [fingerprint]", which can be
14822 repeated as many times as needed. If no dirservers specified,
14823 default to moria1,moria2,tor26.
14824 - Make moria2 advertise a dirport of 80, so people behind firewalls
14825 will be able to get a directory.
14826 - Http proxy support
14827 - Dirservers translate requests for http://%s:%d/x to /x
14828 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
14829 be routed through this host.
14830 - Clients ask for /tor/x rather than /x for new enough dirservers.
14831 This way we can one day coexist peacefully with apache.
14832 - Clients specify a "Host: %s%d" http header, to be compatible
14833 with more proxies, and so running squid on an exit node can work.
14836 Changes in version 0.0.8.1 - 2004-10-13
14838 - Fix a seg fault that can be triggered remotely for Tor
14839 clients/servers with an open dirport.
14840 - Fix a rare assert trigger, where routerinfos for entries in
14841 our cpath would expire while we're building the path.
14842 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14843 - Fix a rare seg fault for people running hidden services on
14844 intermittent connections.
14845 - Fix a bug in parsing opt keywords with objects.
14846 - Fix a stale pointer assert bug when a stream detaches and
14848 - Fix a string format vulnerability (probably not exploitable)
14849 in reporting stats locally.
14850 - Fix an assert trigger: sometimes launching circuits can fail
14851 immediately, e.g. because too many circuits have failed recently.
14852 - Fix a compile warning on 64 bit platforms.
14855 Changes in version 0.0.9pre2 - 2004-10-03
14857 - Make fetching a cached directory work for 64-bit platforms too.
14858 - Make zlib.h a required header, not an optional header.
14861 Changes in version 0.0.9pre1 - 2004-10-01
14863 - Stop using separate defaults for no-config-file and
14864 empty-config-file. Now you have to explicitly turn off SocksPort,
14865 if you don't want it open.
14866 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14867 - Improve man page to mention more of the 0.0.8 features.
14868 - Fix a rare seg fault for people running hidden services on
14869 intermittent connections.
14870 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
14872 - Fix more dns related bugs: send back resolve_failed and end cells
14873 more reliably when the resolve fails, rather than closing the
14874 circuit and then trying to send the cell. Also attach dummy resolve
14875 connections to a circuit *before* calling dns_resolve(), to fix
14876 a bug where cached answers would never be sent in RESOLVED cells.
14877 - When we run out of disk space, or other log writing error, don't
14878 crash. Just stop logging to that log and continue.
14879 - We were starting to daemonize before we opened our logs, so if
14880 there were any problems opening logs, we would complain to stderr,
14881 which wouldn't work, and then mysteriously exit.
14882 - Fix a rare bug where sometimes a verified OR would connect to us
14883 before he'd uploaded his descriptor, which would cause us to
14884 assign conn->nickname as though he's unverified. Now we look through
14885 the fingerprint list to see if he's there.
14886 - Fix a rare assert trigger, where routerinfos for entries in
14887 our cpath would expire while we're building the path.
14890 - Clients can ask dirservers for /dir.z to get a compressed version
14891 of the directory. Only works for servers running 0.0.9, of course.
14892 - Make clients cache directories and use them to seed their router
14893 lists at startup. This means clients have a datadir again.
14894 - Configuration infrastructure support for warning on obsolete
14896 - Respond to content-encoding headers by trying to uncompress as
14898 - Reply with a deflated directory when a client asks for "dir.z".
14899 We could use allow-encodings instead, but allow-encodings isn't
14900 specified in HTTP 1.0.
14901 - Raise the max dns workers from 50 to 100.
14902 - Discourage people from setting their dirfetchpostperiod more often
14903 than once per minute.
14904 - Protect dirservers from overzealous descriptor uploading -- wait
14905 10 seconds after directory gets dirty, before regenerating.
14908 Changes in version 0.0.8 - 2004-08-25
14909 o Port it to SunOS 5.9 / Athena
14912 Changes in version 0.0.8rc2 - 2004-08-20
14913 o Make it compile on cygwin again.
14914 o When picking unverified routers, skip those with low uptime and/or
14915 low bandwidth, depending on what properties you care about.
14918 Changes in version 0.0.8rc1 - 2004-08-18
14919 o Changes from 0.0.7.3:
14921 - Fix assert triggers: if the other side returns an address 0.0.0.0,
14922 don't put it into the client dns cache.
14923 - If a begin failed due to exit policy, but we believe the IP address
14924 should have been allowed, switch that router to exitpolicy reject *:*
14925 until we get our next directory.
14927 - Clients choose nodes proportional to advertised bandwidth.
14928 - Avoid using nodes with low uptime as introduction points.
14929 - Handle servers with dynamic IP addresses: don't replace
14930 options->Address with the resolved one at startup, and
14931 detect our address right before we make a routerinfo each time.
14932 - 'FascistFirewall' option to pick dirservers and ORs on specific
14933 ports; plus 'FirewallPorts' config option to tell FascistFirewall
14934 which ports are open. (Defaults to 80,443)
14935 - Be more aggressive about trying to make circuits when the network
14936 has changed (e.g. when you unsuspend your laptop).
14937 - Check for time skew on http headers; report date in response to
14939 - If the entrynode config line has only one node, don't pick it as
14941 - Add strict{entry|exit}nodes config options. If set to 1, then
14942 we refuse to build circuits that don't include the specified entry
14944 - OutboundBindAddress config option, to bind to a specific
14945 IP address for outgoing connect()s.
14946 - End truncated log entries (e.g. directories) with "[truncated]".
14948 o Patches to 0.0.8preX:
14950 - Patches to compile and run on win32 again (maybe)?
14951 - Fix crash when looking for ~/.torrc with no $HOME set.
14952 - Fix a race bug in the unit tests.
14953 - Handle verified/unverified name collisions better when new
14954 routerinfo's arrive in a directory.
14955 - Sometimes routers were getting entered into the stats before
14956 we'd assigned their identity_digest. Oops.
14957 - Only pick and establish intro points after we've gotten a
14960 - AllowUnverifiedNodes config option to let circuits choose no-name
14961 routers in entry,middle,exit,introduction,rendezvous positions.
14962 Allow middle and rendezvous positions by default.
14963 - Add a man page for tor-resolve.
14966 Changes in version 0.0.7.3 - 2004-08-12
14967 o Stop dnsworkers from triggering an assert failure when you
14968 ask them to resolve the host "".
14971 Changes in version 0.0.8pre3 - 2004-08-09
14972 o Changes from 0.0.7.2:
14973 - Allow multiple ORs with same nickname in routerlist -- now when
14974 people give us one identity key for a nickname, then later
14975 another, we don't constantly complain until the first expires.
14976 - Remember used bandwidth (both in and out), and publish 15-minute
14977 snapshots for the past day into our descriptor.
14978 - You can now fetch $DIRURL/running-routers to get just the
14979 running-routers line, not the whole descriptor list. (But
14980 clients don't use this yet.)
14981 - When people mistakenly use Tor as an http proxy, point them
14982 at the tor-doc.html rather than the INSTALL.
14983 - Remove our mostly unused -- and broken -- hex_encode()
14984 function. Use base16_encode() instead. (Thanks to Timo Lindfors
14985 for pointing out this bug.)
14986 - Rotate onion keys every 12 hours, not every 2 hours, so we have
14987 fewer problems with people using the wrong key.
14988 - Change the default exit policy to reject the default edonkey,
14989 kazaa, gnutella ports.
14990 - Add replace_file() to util.[ch] to handle win32's rename().
14992 o Changes from 0.0.8preX:
14993 - Fix two bugs in saving onion keys to disk when rotating, so
14994 hopefully we'll get fewer people using old onion keys.
14995 - Fix an assert error that was making SocksPolicy not work.
14996 - Be willing to expire routers that have an open dirport -- it's
14997 just the authoritative dirservers we want to not forget.
14998 - Reject tor-resolve requests for .onion addresses early, so we
14999 don't build a whole rendezvous circuit and then fail.
15000 - When you're warning a server that he's unverified, don't cry
15001 wolf unpredictably.
15002 - Fix a race condition: don't try to extend onto a connection
15003 that's still handshaking.
15004 - For servers in clique mode, require the conn to be open before
15005 you'll choose it for your path.
15006 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
15007 end relay cell, etc.
15008 - Measure bandwidth capacity over the last 24 hours, not just 12
15009 - Bugfix: authoritative dirservers were making and signing a new
15010 directory for each client, rather than reusing the cached one.
15013 Changes in version 0.0.8pre2 - 2004-08-04
15014 o Changes from 0.0.7.2:
15016 - Check directory signature _before_ you decide whether you're
15017 you're running an obsolete version and should exit.
15018 - Check directory signature _before_ you parse the running-routers
15019 list to decide who's running or verified.
15020 - Bugfixes and features:
15021 - Check return value of fclose while writing to disk, so we don't
15022 end up with broken files when servers run out of disk space.
15023 - Log a warning if the user uses an unsafe socks variant, so people
15024 are more likely to learn about privoxy or socat.
15025 - Dirservers now include RFC1123-style dates in the HTTP headers,
15026 which one day we will use to better detect clock skew.
15028 o Changes from 0.0.8pre1:
15029 - Make it compile without warnings again on win32.
15030 - Log a warning if you're running an unverified server, to let you
15031 know you might want to get it verified.
15032 - Only pick a default nickname if you plan to be a server.
15035 Changes in version 0.0.8pre1 - 2004-07-23
15037 - Made our unit tests compile again on OpenBSD 3.5, and tor
15038 itself compile again on OpenBSD on a sparc64.
15039 - We were neglecting milliseconds when logging on win32, so
15040 everything appeared to happen at the beginning of each second.
15042 o Protocol changes:
15043 - 'Extend' relay cell payloads now include the digest of the
15044 intended next hop's identity key. Now we can verify that we're
15045 extending to the right router, and also extend to routers we
15046 hadn't heard of before.
15049 - Tor nodes can now act as relays (with an advertised ORPort)
15050 without being manually verified by the dirserver operators.
15051 - Uploaded descriptors of unverified routers are now accepted
15052 by the dirservers, and included in the directory.
15053 - Verified routers are listed by nickname in the running-routers
15054 list; unverified routers are listed as "$<fingerprint>".
15055 - We now use hash-of-identity-key in most places rather than
15056 nickname or addr:port, for improved security/flexibility.
15057 - To avoid Sybil attacks, paths still use only verified servers.
15058 But now we have a chance to play around with hybrid approaches.
15059 - Nodes track bandwidth usage to estimate capacity (not used yet).
15060 - ClientOnly option for nodes that never want to become servers.
15061 - Directory caching.
15062 - "AuthoritativeDir 1" option for the official dirservers.
15063 - Now other nodes (clients and servers) will cache the latest
15064 directory they've pulled down.
15065 - They can enable their DirPort to serve it to others.
15066 - Clients will pull down a directory from any node with an open
15067 DirPort, and check the signature/timestamp correctly.
15068 - Authoritative dirservers now fetch directories from other
15069 authdirservers, to stay better synced.
15070 - Running-routers list tells who's down also, along with noting
15071 if they're verified (listed by nickname) or unverified (listed
15073 - Allow dirservers to serve running-router list separately.
15074 This isn't used yet.
15075 - ORs connect-on-demand to other ORs
15076 - If you get an extend cell to an OR you're not connected to,
15077 connect, handshake, and forward the create cell.
15078 - The authoritative dirservers stay connected to everybody,
15079 and everybody stays connected to 0.0.7 servers, but otherwise
15080 clients/servers expire unused connections after 5 minutes.
15081 - When servers get a sigint, they delay 30 seconds (refusing new
15082 connections) then exit. A second sigint causes immediate exit.
15083 - File and name management:
15084 - Look for .torrc if no CONFDIR "torrc" is found.
15085 - If no datadir is defined, then choose, make, and secure ~/.tor
15087 - If torrc not found, exitpolicy reject *:*.
15088 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
15089 - If no nickname is defined, derive default from hostname.
15090 - Rename secret key files, e.g. identity.key -> secret_id_key,
15091 to discourage people from mailing their identity key to tor-ops.
15092 - Refuse to build a circuit before the directory has arrived --
15093 it won't work anyway, since you won't know the right onion keys
15095 - Try other dirservers immediately if the one you try is down. This
15096 should tolerate down dirservers better now.
15097 - Parse tor version numbers so we can do an is-newer-than check
15098 rather than an is-in-the-list check.
15099 - New socks command 'resolve', to let us shim gethostbyname()
15101 - A 'tor_resolve' script to access the socks resolve functionality.
15102 - A new socks-extensions.txt doc file to describe our
15103 interpretation and extensions to the socks protocols.
15104 - Add a ContactInfo option, which gets published in descriptor.
15105 - Publish OR uptime in descriptor (and thus in directory) too.
15106 - Write tor version at the top of each log file
15107 - New docs in the tarball:
15109 - Document that you should proxy your SSL traffic too.
15112 Changes in version 0.0.7.2 - 2004-07-07
15113 o A better fix for the 0.0.0.0 problem, that will hopefully
15114 eliminate the remaining related assertion failures.
15117 Changes in version 0.0.7.1 - 2004-07-04
15118 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
15119 since internally we use 0.0.0.0 to signify "not yet resolved".
15122 Changes in version 0.0.7 - 2004-06-07
15123 o Updated the man page to reflect the new features.
15126 Changes in version 0.0.7rc2 - 2004-06-06
15127 o Changes from 0.0.7rc1:
15128 - Make it build on Win32 again.
15129 o Changes from 0.0.6.2:
15130 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
15134 Changes in version 0.0.7rc1 - 2004-06-02
15136 - On sighup, we were adding another log without removing the first
15137 one. So log messages would get duplicated n times for n sighups.
15138 - Several cases of using a connection after we'd freed it. The
15139 problem was that connections that are pending resolve are in both
15140 the pending_resolve tree, and also the circuit's resolving_streams
15141 list. When you want to remove one, you must remove it from both.
15142 - Fix a double-mark-for-close where an end cell arrived for a
15143 resolving stream, and then the resolve failed.
15144 - Check directory signatures based on name of signer, not on whom
15145 we got the directory from. This will let us cache directories more
15148 - Crank up some of our constants to handle more users.
15151 Changes in version 0.0.7pre1 - 2004-06-02
15152 o Fixes for crashes and other obnoxious bugs:
15153 - Fix an epipe bug: sometimes when directory connections failed
15154 to connect, we would give them a chance to flush before closing
15156 - When we detached from a circuit because of resolvefailed, we
15157 would immediately try the same circuit twice more, and then
15158 give up on the resolve thinking we'd tried three different
15160 - Limit the number of intro circuits we'll attempt to build for a
15161 hidden service per 15-minute period.
15162 - Check recommended-software string *early*, before actually parsing
15163 the directory. Thus we can detect an obsolete version and exit,
15164 even if the new directory format doesn't parse.
15165 o Fixes for security bugs:
15166 - Remember which nodes are dirservers when you startup, and if a
15167 random OR enables his dirport, don't automatically assume he's
15168 a trusted dirserver.
15170 - Directory connections were asking the wrong poll socket to
15171 start writing, and not asking themselves to start writing.
15172 - When we detached from a circuit because we sent a begin but
15173 didn't get a connected, we would use it again the first time;
15174 but after that we would correctly switch to a different one.
15175 - Stop warning when the first onion decrypt attempt fails; they
15176 will sometimes legitimately fail now that we rotate keys.
15177 - Override unaligned-access-ok check when $host_cpu is ia64 or
15178 arm. Apparently they allow it but the kernel whines.
15179 - Dirservers try to reconnect periodically too, in case connections
15181 - Fix some memory leaks in directory servers.
15182 - Allow backslash in Win32 filenames.
15183 - Made Tor build complain-free on FreeBSD, hopefully without
15184 breaking other BSD builds. We'll see.
15186 - Doxygen markup on all functions and global variables.
15187 - Make directory functions update routerlist, not replace it. So
15188 now directory disagreements are not so critical a problem.
15189 - Remove the upper limit on number of descriptors in a dirserver's
15190 directory (not that we were anywhere close).
15191 - Allow multiple logfiles at different severity ranges.
15192 - Allow *BindAddress to specify ":port" rather than setting *Port
15193 separately. Allow multiple instances of each BindAddress config
15194 option, so you can bind to multiple interfaces if you want.
15195 - Allow multiple exit policy lines, which are processed in order.
15196 Now we don't need that huge line with all the commas in it.
15197 - Enable accept/reject policies on SOCKS connections, so you can bind
15198 to 0.0.0.0 but still control who can use your OP.
15201 Changes in version 0.0.6.2 - 2004-05-16
15202 o Our integrity-checking digest was checking only the most recent cell,
15203 not the previous cells like we'd thought.
15204 Thanks to Stefan Mark for finding the flaw!
15207 Changes in version 0.0.6.1 - 2004-05-06
15208 o Fix two bugs in our AES counter-mode implementation (this affected
15209 onion-level stream encryption, but not TLS-level). It turns
15210 out we were doing something much more akin to a 16-character
15211 polyalphabetic cipher. Oops.
15212 Thanks to Stefan Mark for finding the flaw!
15213 o Retire moria3 as a directory server, and add tor26 as a directory
15217 Changes in version 0.0.6 - 2004-05-02
15218 [version bump only]
15221 Changes in version 0.0.6rc4 - 2004-05-01
15222 o Update the built-in dirservers list to use the new directory format
15223 o Fix a rare seg fault: if a node offering a hidden service attempts
15224 to build a circuit to Alice's rendezvous point and fails before it
15225 reaches the last hop, it retries with a different circuit, but
15227 o Handle windows socket errors correctly.
15230 Changes in version 0.0.6rc3 - 2004-04-28
15231 o Don't expire non-general excess circuits (if we had enough
15232 circuits open, we were expiring rendezvous circuits -- even
15233 when they had a stream attached. oops.)
15234 o Fetch randomness from /dev/urandom better (not via fopen/fread)
15235 o Better debugging for tls errors
15236 o Some versions of openssl have an SSL_pending function that erroneously
15237 returns bytes when there is a non-application record pending.
15238 o Set Content-Type on the directory and hidserv descriptor.
15239 o Remove IVs from cipher code, since AES-ctr has none.
15240 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
15241 o We were using an array of length zero in a few places.
15242 o win32's gethostbyname can't resolve an IP to an IP.
15243 o win32's close can't close a socket.
15246 Changes in version 0.0.6rc2 - 2004-04-26
15247 o Fix a bug where we were closing tls connections intermittently.
15248 It turns out openssl keeps its errors around -- so if an error
15249 happens, and you don't ask about it, and then another openssl
15250 operation happens and succeeds, and you ask if there was an error,
15251 it tells you about the first error. Fun fun.
15252 o Fix a bug that's been lurking since 27 may 03 (!)
15253 When passing back a destroy cell, we would use the wrong circ id.
15254 'Mostly harmless', but still worth fixing.
15255 o Since we don't support truncateds much, don't bother sending them;
15256 just close the circ.
15257 o check for <machine/limits.h> so we build on NetBSD again (I hope).
15258 o don't crash if a conn that sent a begin has suddenly lost its circuit
15259 (this was quite rare).
15262 Changes in version 0.0.6rc1 - 2004-04-25
15263 o We now rotate link (tls context) keys and onion keys.
15264 o CREATE cells now include oaep padding, so you can tell
15265 if you decrypted them correctly.
15266 o Add bandwidthburst to server descriptor.
15267 o Directories now say which dirserver signed them.
15268 o Use a tor_assert macro that logs failed assertions too.
15271 Changes in version 0.0.6pre5 - 2004-04-18
15272 o changes from 0.0.6pre4:
15273 - make tor build on broken freebsd 5.2 installs
15274 - fix a failed assert when you try an intro point, get a nack, and try
15275 a second one and it works.
15276 - when alice uses a port that the hidden service doesn't accept,
15277 it now sends back an end cell (denied by exit policy). otherwise
15278 alice would just have to wait to time out.
15279 - fix another rare bug: when we had tried all the intro
15280 points for a hidden service, we fetched the descriptor
15281 again, but we left our introcirc thinking it had already
15282 sent an intro, so it kept waiting for a response...
15283 - bugfix: when you sleep your hidden-service laptop, as soon
15284 as it wakes up it tries to upload a service descriptor, but
15285 socketpair fails for some reason (localhost not up yet?).
15286 now we simply give up on that upload, and we'll try again later.
15287 i'd still like to find the bug though.
15288 - if an intro circ waiting for an ack dies before getting one, then
15290 - we were reusing stale service descriptors and refetching usable
15294 Changes in version 0.0.6pre4 - 2004-04-14
15295 o changes from 0.0.6pre3:
15296 - when bob fails to connect to the rendezvous point, and his
15297 circ didn't fail because of the rendezvous point itself, then
15298 he retries a couple of times
15299 - we expire introduction and rendezvous circs more thoroughly
15300 (sometimes they were hanging around forever)
15301 - we expire unattached rendezvous streams that have been around
15302 too long (they were sticking around forever).
15303 - fix a measly fencepost error that was crashing everybody with
15307 Changes in version 0.0.6pre3 - 2004-04-14
15308 o changes from 0.0.6pre2:
15309 - make hup work again
15310 - fix some memory leaks for dirservers
15311 - allow more skew in rendezvous descriptor timestamps, to help
15312 handle people like blanu who don't know what time it is
15313 - normal circs are 3 hops, but some rend/intro circs are 4, if
15314 the initiator doesn't get to choose the last hop
15315 - send acks for introductions, so alice can know whether to try
15317 - bob publishes intro points more correctly
15318 o changes from 0.0.5:
15319 - fix an assert trigger that's been plaguing us since the days
15320 of 0.0.2prexx (thanks weasel!)
15321 - retry stream correctly when we fail to connect because of
15322 exit-policy-reject (should try another) or can't-resolve-address
15323 (also should try another, because dns on random internet servers
15325 - when we hup a dirserver and we've *removed* a server from the
15326 approved-routers list, now we remove that server from the
15327 in-memory directories too
15330 Changes in version 0.0.6pre2 - 2004-04-08
15331 o We fixed our base32 implementation. Now it works on all architectures.
15334 Changes in version 0.0.6pre1 - 2004-04-08
15336 - Hidden services and rendezvous points are implemented. Go to
15337 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
15338 hidden services. (This only works via a socks4a proxy such as
15339 Privoxy, and currently it's quite slow.)
15342 Changes in version 0.0.5 - 2004-03-30
15343 [version bump only]
15346 Changes in version 0.0.5rc3 - 2004-03-29
15347 o Install torrc as torrc.sample -- we no longer clobber your
15349 o Re-enable recommendedversion checking (we broke it in rc2, oops)
15350 o Add in a 'notice' log level for things the operator should hear
15351 but that aren't warnings
15354 Changes in version 0.0.5rc2 - 2004-03-29
15355 o Hold socks connection open until reply is flushed (if possible)
15356 o Make exit nodes resolve IPs to IPs immediately, rather than asking
15357 the dns farm to do it.
15358 o Fix c99 aliasing warnings in rephist.c
15359 o Don't include server descriptors that are older than 24 hours in the
15361 o Give socks 'reject' replies their whole 15s to attempt to flush,
15362 rather than seeing the 60s timeout and assuming the flush had failed.
15363 o Clean automake droppings from the cvs repository
15366 Changes in version 0.0.5rc1 - 2004-03-28
15367 o Fix mangled-state bug in directory fetching (was causing sigpipes).
15368 o Only build circuits after we've fetched the directory: clients were
15369 using only the directory servers before they'd fetched a directory.
15370 This also means longer startup time; so it goes.
15371 o Fix an assert trigger where an OP would fail to handshake, and we'd
15372 expect it to have a nickname.
15373 o Work around a tsocks bug: do a socks reject when AP connection dies
15374 early, else tsocks goes into an infinite loop.
15377 Changes in version 0.0.4 - 2004-03-26
15378 o When connecting to a dirserver or OR and the network is down,
15382 Changes in version 0.0.3 - 2004-03-26
15383 o Warn and fail if server chose a nickname with illegal characters
15384 o Port to Solaris and Sparc:
15385 - include missing header fcntl.h
15386 - have autoconf find -lsocket -lnsl automatically
15387 - deal with hardware word alignment
15388 - make uname() work (solaris has a different return convention)
15389 - switch from using signal() to sigaction()
15390 o Preliminary work on reputation system:
15391 - Keep statistics on success/fail of connect attempts; they're published
15392 by kill -USR1 currently.
15393 - Add a RunTesting option to try to learn link state by creating test
15394 circuits, even when SocksPort is off.
15395 - Remove unused open circuits when there are too many.
15398 Changes in version 0.0.2 - 2004-03-19
15399 - Include strlcpy and strlcat for safer string ops
15400 - define INADDR_NONE so we compile (but still not run) on solaris
15403 Changes in version 0.0.2pre27 - 2004-03-14
15405 - Allow internal tor networks (we were rejecting internal IPs,
15406 now we allow them if they're set explicitly).
15407 - And fix a few endian issues.
15410 Changes in version 0.0.2pre26 - 2004-03-14
15412 - If a stream times out after 15s without a connected cell, don't
15413 try that circuit again: try a new one.
15414 - Retry streams at most 4 times. Then give up.
15415 - When a dirserver gets a descriptor from an unknown router, it
15416 logs its fingerprint (so the dirserver operator can choose to
15417 accept it even without mail from the server operator).
15418 - Inform unapproved servers when we reject their descriptors.
15419 - Make tor build on Windows again. It works as a client, who knows
15421 - Clearer instructions in the torrc for how to set up a server.
15422 - Be more efficient about reading fd's when our global token bucket
15423 (used for rate limiting) becomes empty.
15425 - Stop asserting that computers always go forward in time. It's
15427 - When we sent a cell (e.g. destroy) and then marked an OR connection
15428 expired, we might close it before finishing a flush if the other
15429 side isn't reading right then.
15430 - Don't allow dirservers to start if they haven't defined
15431 RecommendedVersions
15432 - We were caching transient dns failures. Oops.
15433 - Prevent servers from publishing an internal IP as their address.
15434 - Address a strcat vulnerability in circuit.c
15437 Changes in version 0.0.2pre25 - 2004-03-04
15439 - Put the OR's IP in its router descriptor, not its fqdn. That way
15440 we'll stop being stalled by gethostbyname for nodes with flaky dns,
15443 - If the user typed in an address that didn't resolve, the server
15447 Changes in version 0.0.2pre24 - 2004-03-03
15449 - Fix an assertion failure in dns.c, where we were trying to dequeue
15450 a pending dns resolve even if it wasn't pending
15451 - Fix a spurious socks5 warning about still trying to write after the
15452 connection is finished.
15453 - Hold certain marked_for_close connections open until they're finished
15454 flushing, rather than losing bytes by closing them too early.
15455 - Correctly report the reason for ending a stream
15456 - Remove some duplicate calls to connection_mark_for_close
15457 - Put switch_id and start_daemon earlier in the boot sequence, so it
15458 will actually try to chdir() to options.DataDirectory
15459 - Make 'make test' exit(1) if a test fails; fix some unit tests
15460 - Make tor fail when you use a config option it doesn't know about,
15461 rather than warn and continue.
15462 - Make --version work
15463 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
15466 Changes in version 0.0.2pre23 - 2004-02-29
15468 - Print a statement when the first circ is finished, so the user
15469 knows it's working.
15470 - If a relay cell is unrecognized at the end of the circuit,
15471 send back a destroy. (So attacks to mutate cells are more
15473 - New config option 'excludenodes' to avoid certain nodes for circuits.
15474 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
15475 so you can collect coredumps there.
15477 - Fix a bug in tls flushing where sometimes data got wedged and
15478 didn't flush until more data got sent. Hopefully this bug was
15479 a big factor in the random delays we were seeing.
15480 - Make 'connected' cells include the resolved IP, so the client
15481 dns cache actually gets populated.
15482 - Disallow changing from ORPort=0 to ORPort>0 on hup.
15483 - When we time-out on a stream and detach from the circuit, send an
15484 end cell down it first.
15485 - Only warn about an unknown router (in exitnodes, entrynodes,
15486 excludenodes) after we've fetched a directory.
15489 Changes in version 0.0.2pre22 - 2004-02-26
15491 - Servers publish less revealing uname information in descriptors.
15492 - More memory tracking and assertions, to crash more usefully when
15494 - If the default torrc isn't there, just use some default defaults.
15495 Plus provide an internal dirservers file if they don't have one.
15496 - When the user tries to use Tor as an http proxy, give them an http
15497 501 failure explaining that we're a socks proxy.
15498 - Dump a new router.desc on hup, to help confused people who change
15499 their exit policies and then wonder why router.desc doesn't reflect
15501 - Clean up the generic tor.sh init script that we ship with.
15503 - If the exit stream is pending on the resolve, and a destroy arrives,
15504 then the stream wasn't getting removed from the pending list. I
15505 think this was the one causing recent server crashes.
15506 - Use a more robust poll on OSX 10.3, since their poll is flaky.
15507 - When it couldn't resolve any dirservers, it was useless from then on.
15508 Now it reloads the RouterFile (or default dirservers) if it has no
15510 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
15511 many users don't even *have* a /usr/local/sbin/.
15514 Changes in version 0.0.2pre21 - 2004-02-18
15516 - There's a ChangeLog file that actually reflects the changelog.
15517 - There's a 'torify' wrapper script, with an accompanying
15518 tor-tsocks.conf, that simplifies the process of using tsocks for
15519 tor. It even has a man page.
15520 - The tor binary gets installed to sbin rather than bin now.
15521 - Retry streams where the connected cell hasn't arrived in 15 seconds
15522 - Clean up exit policy handling -- get the default out of the torrc,
15523 so we can update it without forcing each server operator to fix
15525 - Allow imaps and pop3s in default exit policy
15527 - Prevent picking middleman nodes as the last node in the circuit
15530 Changes in version 0.0.2pre20 - 2004-01-30
15532 - We now have a deb package, and it's in debian unstable. Go to
15533 it, apt-getters. :)
15534 - I've split the TotalBandwidth option into BandwidthRate (how many
15535 bytes per second you want to allow, long-term) and
15536 BandwidthBurst (how many bytes you will allow at once before the cap
15537 kicks in). This better token bucket approach lets you, say, set
15538 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
15539 performance while not exceeding your monthly bandwidth quota.
15540 - Push out a tls record's worth of data once you've got it, rather
15541 than waiting until you've read everything waiting to be read. This
15542 may improve performance by pipelining better. We'll see.
15543 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
15544 from failed circuits (if they haven't been connected yet) and attach
15546 - Expire old streams that haven't managed to connect. Some day we'll
15547 have them reattach to new circuits instead.
15550 - Fix several memory leaks that were causing servers to become bloated
15552 - Fix a few very rare assert triggers. A few more remain.
15553 - Setuid to User _before_ complaining about running as root.
15556 Changes in version 0.0.2pre19 - 2004-01-07
15558 - Fix deadlock condition in dns farm. We were telling a child to die by
15559 closing the parent's file descriptor to him. But newer children were
15560 inheriting the open file descriptor from the parent, and since they
15561 weren't closing it, the socket never closed, so the child never read
15562 eof, so he never knew to exit. Similarly, dns workers were holding
15563 open other sockets, leading to all sorts of chaos.
15564 - New cleaner daemon() code for forking and backgrounding.
15565 - If you log to a file, it now prints an entry at the top of the
15566 logfile so you know it's working.
15567 - The onionskin challenge length was 30 bytes longer than necessary.
15568 - Started to patch up the spec so it's not quite so out of date.
15571 Changes in version 0.0.2pre18 - 2004-01-02
15573 - Fix endian issues with the 'integrity' field in the relay header.
15574 - Fix a potential bug where connections in state
15575 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
15578 Changes in version 0.0.2pre17 - 2003-12-30
15580 - Made --debuglogfile (or any second log file, actually) work.
15581 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
15582 adversary could force us into an infinite loop.
15585 - Each onionskin handshake now includes a hash of the computed key,
15586 to prove the server's identity and help perfect forward secrecy.
15587 - Changed cell size from 256 to 512 bytes (working toward compatibility
15589 - Changed cell length to 2 bytes, and moved it to the relay header.
15590 - Implemented end-to-end integrity checking for the payloads of
15592 - Separated streamid from 'recognized' (otherwise circuits will get
15593 messed up when we try to have streams exit from the middle). We
15594 use the integrity-checking to confirm that a cell is addressed to
15596 - Randomize the initial circid and streamid values, so an adversary who
15597 breaks into a node can't learn how many circuits or streams have
15601 Changes in version 0.0.2pre16 - 2003-12-14
15603 - Fixed a bug that made HUP trigger an assert
15604 - Fixed a bug where a circuit that immediately failed wasn't being
15605 counted as a failed circuit in counting retries.
15608 - Now we close the circuit when we get a truncated cell: otherwise we're
15609 open to an anonymity attack where a bad node in the path truncates
15610 the circuit and then we open streams at him.
15611 - Add port ranges to exit policies
15612 - Add a conservative default exit policy
15613 - Warn if you're running tor as root
15614 - on HUP, retry OR connections and close/rebind listeners
15615 - options.EntryNodes: try these nodes first when picking the first node
15616 - options.ExitNodes: if your best choices happen to include any of
15617 your preferred exit nodes, you choose among just those preferred
15619 - options.ExcludedNodes: nodes that are never picked in path building
15622 Changes in version 0.0.2pre15 - 2003-12-03
15623 o Robustness and bugfixes:
15624 - Sometimes clients would cache incorrect DNS resolves, which would
15625 really screw things up.
15626 - An OP that goes offline would slowly leak all its sockets and stop
15628 - A wide variety of bugfixes in exit node selection, exit policy
15629 handling, and processing pending streams when a new circuit is
15631 - Pick nodes for a path only from those the directory says are up
15632 - Choose randomly from all running dirservers, not always the first one
15633 - Increase allowed http header size for directory fetch.
15634 - Stop writing to stderr (if we're daemonized it will be closed).
15635 - Enable -g always, so cores will be more useful to me.
15636 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
15639 - Wrote a man page. It lists commonly used options.
15642 - Change default loglevel to warn.
15643 - Make PidFile default to null rather than littering in your CWD.
15644 - OnionRouter config option is now obsolete. Instead it just checks
15646 - Moved to a single unified torrc file for both clients and servers.
15649 Changes in version 0.0.2pre14 - 2003-11-29
15650 o Robustness and bugfixes:
15651 - Force the admin to make the DataDirectory himself
15652 - to get ownership/permissions right
15653 - so clients no longer make a DataDirectory and then never use it
15654 - fix bug where a client who was offline for 45 minutes would never
15655 pull down a directory again
15656 - fix (or at least hide really well) the dns assert bug that was
15657 causing server crashes
15658 - warnings and improved robustness wrt clockskew for certs
15659 - use the native daemon(3) to daemonize, when available
15660 - exit if bind() fails
15661 - exit if neither socksport nor orport is defined
15662 - include our own tor_timegm (Win32 doesn't have its own)
15663 - bugfix for win32 with lots of connections
15664 - fix minor bias in PRNG
15665 - make dirserver more robust to corrupt cached directory
15668 - Wrote the design document (woo)
15670 o Circuit building and exit policies:
15671 - Circuits no longer try to use nodes that the directory has told them
15673 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
15674 bitcounts (18.0.0.0/8).
15675 - Make AP connections standby for a circuit if no suitable circuit
15676 exists, rather than failing
15677 - Circuits choose exit node based on addr/port, exit policies, and
15678 which AP connections are standing by
15679 - Bump min pathlen from 2 to 3
15680 - Relay end cells have a payload to describe why the stream ended.
15681 - If the stream failed because of exit policy, try again with a new
15683 - Clients have a dns cache to remember resolved addresses.
15684 - Notice more quickly when we have no working circuits
15687 - APPort is now called SocksPort
15688 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
15690 - RecommendedVersions is now a config variable rather than
15691 hardcoded (for dirservers)
15692 - Reloads config on HUP
15693 - Usage info on -h or --help
15694 - If you set User and Group config vars, it'll setu/gid to them.
15697 Changes in version 0.0.2pre13 - 2003-10-19
15698 o General stability:
15699 - SSL_write no longer fails when it returns WANTWRITE and the number
15700 of bytes in the buf has changed by the next SSL_write call.
15701 - Fix segfault fetching directory when network is down
15702 - Fix a variety of minor memory leaks
15703 - Dirservers reload the fingerprints file on HUP, so I don't have
15704 to take down the network when I approve a new router
15705 - Default server config file has explicit Address line to specify fqdn
15708 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
15709 - Make listener connections not ever alloc bufs
15711 o Autoconf improvements:
15712 - don't clobber an external CFLAGS in ./configure
15713 - Make install now works
15714 - create var/lib/tor on make install
15715 - autocreate a tor.sh initscript to help distribs
15716 - autocreate the torrc and sample-server-torrc with correct paths
15718 o Log files and Daemonizing now work:
15719 - If --DebugLogFile is specified, log to it at -l debug
15720 - If --LogFile is specified, use it instead of commandline
15721 - If --RunAsDaemon is set, tor forks and backgrounds on startup