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.4.17-rc - 2013-09-05
158 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
159 series. It adds an emergency step to help us tolerate the massive
160 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
161 circuit-level handshakes now effectively jump the queue compared to
162 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
163 big bug hindering bridge reachability tests.
166 - Relays now process the new "NTor" circuit-level handshake requests
167 with higher priority than the old "TAP" circuit-level handshake
168 requests. We still process some TAP requests to not totally starve
169 0.2.3 clients when NTor becomes popular. A new consensus parameter
170 "NumNTorsPerTAP" lets us tune the balance later if we need to.
171 Implements ticket 9574.
174 - If the circuit build timeout logic is disabled (via the consensus,
175 or because we are an authority), then don't build testing circuits.
176 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
177 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
178 previously they did not, which prevented them from receiving
179 successful connections from relays for self-test or bandwidth
180 testing. Also, when a relay is extending a circuit to a bridge,
181 it needs to send a NETINFO cell, even when the bridge hasn't sent
182 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
183 - If the time to download the next old-style networkstatus is in
184 the future, do not decline to consider whether to download the
185 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
189 - Avoid double-closing the listener socket in our socketpair()
190 replacement (used on Windows) in the case where the addresses on
191 our opened sockets don't match what we expected. Fixes bug 9400;
192 bugfix on 0.0.2pre7. Found by Coverity.
194 o Minor fixes (config options):
195 - Avoid overflows when the user sets MaxCircuitDirtiness to a
196 ridiculously high value, by imposing a (ridiculously high) 30-day
197 maximum on MaxCircuitDirtiness.
198 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
199 message is logged at notice, not at info.
200 - Warn and fail if a server is configured not to advertise any
201 ORPorts at all. (We need *something* to put in our descriptor,
202 or we just won't work.)
205 - Track how many "TAP" and "NTor" circuit handshake requests we get,
206 and how many we complete, and log it every hour to help relay
207 operators follow trends in network load. Addresses ticket 9658.
208 - Update to the August 7 2013 Maxmind GeoLite Country database.
211 Changes in version 0.2.4.16-rc - 2013-08-10
212 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
213 series. It fixes several crash bugs in the 0.2.4 branch.
216 - Fix a bug in the voting algorithm that could yield incorrect results
217 when a non-naming authority declared too many flags. Fixes bug 9200;
218 bugfix on 0.2.0.3-alpha.
219 - Fix an uninitialized read that could in some cases lead to a remote
220 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
221 Anybody running a hidden service on the experimental 0.2.4.x
222 branch should upgrade. (This is, so far as we know, unrelated to
224 - Avoid an assertion failure when processing DNS replies without the
225 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
226 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
227 0.2.4.15-rc. Found by stem integration tests.
230 - Fix an invalid memory read that occured when a pluggable
231 transport proxy failed its configuration protocol.
232 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
233 - When evaluating whether to use a connection that we haven't
234 decided is canonical using a recent link protocol version,
235 decide that it's canonical only if it used address _does_
236 match the desired address. Fixes bug 9309; bugfix on
237 0.2.4.4-alpha. Reported by skruffy.
238 - Make the default behavior of NumDirectoryGuards be to track
239 NumEntryGuards. Now a user who changes only NumEntryGuards will get
240 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
241 - Fix a spurious compilation warning with some older versions of
242 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
245 - Update to the July 3 2013 Maxmind GeoLite Country database.
248 Changes in version 0.2.4.15-rc - 2013-07-01
249 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
250 series. It fixes a few smaller bugs, but generally appears stable.
251 Please test it and let us know whether it is!
254 - When receiving a new configuration file via the control port's
255 LOADCONF command, do not treat the defaults file as absent.
256 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
259 - Issue a warning when running with the bufferevents backend enabled.
260 It's still not stable, and people should know that they're likely
261 to hit unexpected problems. Closes ticket 9147.
264 Changes in version 0.2.4.14-alpha - 2013-06-18
265 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
266 present in 0.2.4.13-alpha.
269 - When we have too much memory queued in circuits (according to a new
270 MaxMemInCellQueues option), close the circuits consuming the most
271 memory. This prevents us from running out of memory as a relay if
272 circuits fill up faster than they can be drained. Fixes bug 9063;
273 bugfix on the 54th commit of Tor. This bug is a further fix beyond
274 bug 6252, whose fix was merged into 0.2.3.21-rc.
276 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
277 where we tried to solve this issue simply by imposing an upper limit
278 on the number of queued cells for a single circuit. That approach
279 proved to be problematic, since there are ways to provoke clients to
280 send a number of cells in excess of any such reasonable limit. Fixes
281 bug 9072; bugfix on 0.2.4.13-alpha.
283 - Limit hidden service descriptors to at most ten introduction
284 points, to slow one kind of guard enumeration. Fixes bug 9002;
285 bugfix on 0.1.1.11-alpha.
288 Changes in version 0.2.4.13-alpha - 2013-06-14
289 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
290 vulnerabilities, makes socks5 username/password circuit isolation
291 actually actually work (this time for sure!), and cleans up a bunch
292 of other issues in preparation for a release candidate.
294 o Major bugfixes (robustness):
295 - Close any circuit that has too many cells queued on it. Fixes
296 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
297 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
298 - Prevent the get_freelists() function from running off the end of
299 the list of freelists if it somehow gets an unrecognized
300 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
302 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
303 when an exit connection with optimistic data succeeds immediately
304 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
306 - Fix a directory authority crash bug when building a consensus
307 using an older consensus as its basis. Fixes bug 8833. Bugfix
311 - Avoid a memory leak where we would leak a consensus body when we
312 find that a consensus which we couldn't previously verify due to
313 missing certificates is now verifiable. Fixes bug 8719; bugfix
315 - We used to always request authority certificates by identity digest,
316 meaning we'd get the newest one even when we wanted one with a
317 different signing key. Then we would complain about being given
318 a certificate we already had, and never get the one we really
319 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
320 resource to request the one we want. Fixes bug 5595; bugfix on
322 - Follow the socks5 protocol when offering username/password
323 authentication. The fix for bug 8117 exposed this bug, and it
324 turns out real-world applications like Pidgin do care. Bugfix on
325 0.2.3.2-alpha; fixes bug 8879.
326 - Prevent failures on Windows Vista and later when rebuilding the
327 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
328 bugfix on 0.2.4.12-alpha.
331 - Fix an impossible buffer overrun in the AES unit tests. Fixes
332 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
333 - If for some reason we fail to write a microdescriptor while
334 rebuilding the cache, do not let the annotations from that
335 microdescriptor linger in the cache file, and do not let the
336 microdescriptor stay recorded as present in its old location.
337 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
338 - Fix a memory leak that would occur whenever a configuration
339 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
340 - Paste the description for PathBias parameters from the man
341 page into or.h, so the code documents them too. Fixes bug 7982;
342 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
343 - Relays now treat a changed IPv6 ORPort as sufficient reason to
344 publish an updated descriptor. Fixes bug 6026; bugfix on
346 - When launching a resolve request on behalf of an AF_UNIX control
347 socket, omit the address field of the new entry connection, used in
348 subsequent controller events, rather than letting tor_dup_addr()
349 set it to "<unknown address type>". Fixes bug 8639; bugfix on
352 o Minor bugfixes (log messages):
353 - Fix a scaling issue in the path bias accounting code that
354 resulted in "Bug:" log messages from either
355 pathbias_scale_close_rates() or pathbias_count_build_success().
356 This represents a bugfix on a previous bugfix: the original fix
357 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
359 - Give a less useless error message when the user asks for an IPv4
360 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
364 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
365 to tolerate bug 8093 for now.
366 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
367 in directory authority votes to describe whether they have enough
368 measured bandwidths to ignore advertised (relay descriptor)
369 bandwidth claims. Resolves ticket 8711.
370 - Update to the June 5 2013 Maxmind GeoLite Country database.
372 o Removed documentation:
373 - Remove some of the older contents of doc/ as obsolete; move others
374 to torspec.git. Fixes bug 8965.
376 o Code simplification and refactoring:
377 - Avoid using character buffers when constructing most directory
378 objects: this approach was unwieldy and error-prone. Instead,
379 build smartlists of strings, and concatenate them when done.
382 Changes in version 0.2.4.12-alpha - 2013-04-18
383 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
384 process for lengthening the guard rotation period, makes directory
385 authority opinions in the consensus a bit less gameable, makes socks5
386 username/password circuit isolation actually work, and fixes a wide
387 variety of other issues.
390 - Raise the default time that a client keeps an entry guard from
391 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
392 2012 paper. (We would make it even longer, but we need better client
393 load balancing first.) Also, make the guard lifetime controllable
394 via a new GuardLifetime torrc option and a GuardLifetime consensus
395 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
396 - Directory authorities now prefer using measured bandwidths to
397 advertised ones when computing flags and thresholds. Resolves
399 - Directory authorities that have more than a threshold number
400 of relays with measured bandwidths now treat relays with unmeasured
401 bandwidths as having bandwidth 0. Resolves ticket 8435.
403 o Major bugfixes (assert / resource use):
404 - Avoid a bug where our response to TLS renegotiation under certain
405 network conditions could lead to a busy-loop, with 100% CPU
406 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
407 - Avoid an assertion when we discover that we'd like to write a cell
408 onto a closing connection: just discard the cell. Fixes another
409 case of bug 7350; bugfix on 0.2.4.4-alpha.
411 o Major bugfixes (client-side privacy):
412 - When we mark a circuit as unusable for new circuits, have it
413 continue to be unusable for new circuits even if MaxCircuitDirtiness
414 is increased too much at the wrong time, or the system clock jumps
415 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
416 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
417 which have resolved to internal addresses") is set, apply that
418 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
419 - When an exit relay rejects a stream with reason "exit policy", but
420 we only know an exit policy summary (e.g. from the microdesc
421 consensus) for it, do not mark the relay as useless for all exiting.
422 Instead, mark just the circuit as unsuitable for that particular
423 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
424 - Allow applications to get proper stream isolation with
425 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
426 username/password authentication also offer "no authentication". Tor
427 had previously preferred "no authentication", so the applications
428 never actually sent Tor their auth details. Now Tor selects
429 username/password authentication if it's offered. You can disable
430 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
431 bug 8117; bugfix on 0.2.3.3-alpha.
433 o Major bugfixes (other):
434 - When unable to find any working directory nodes to use as a
435 directory guard, give up rather than adding the same non-working
436 nodes to the directory guard list over and over. Fixes bug 8231;
437 bugfix on 0.2.4.8-alpha.
440 - Reject as invalid most directory objects containing a NUL.
441 Belt-and-suspender fix for bug 8037.
442 - In our testsuite, create temporary directories with a bit more
443 entropy in their name to make name collisions less likely. Fixes
445 - Add CACHED keyword to ADDRMAP events in the control protocol
446 to indicate whether a DNS result will be cached or not. Resolves
448 - Update to the April 3 2013 Maxmind GeoLite Country database.
450 o Minor features (build):
451 - Detect and reject attempts to build Tor with threading support
452 when OpenSSL has been compiled without threading support.
454 - Clarify that when autoconf is checking for nacl, it is checking
455 specifically for nacl with a fast curve25519 implementation.
457 - Warn if building on a platform with an unsigned time_t: there
458 are too many places where Tor currently assumes that time_t can
459 hold negative values. We'd like to fix them all, but probably
462 o Minor bugfixes (build):
463 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
464 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
465 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
466 - Add the old src/or/micro-revision.i filename to CLEANFILES.
467 On the off chance that somebody has one, it will go away as soon
468 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
469 - Build Tor correctly on 32-bit platforms where the compiler can build
470 but not run code using the "uint128_t" construction. Fixes bug 8587;
471 bugfix on 0.2.4.8-alpha.
472 - Fix compilation warning with some versions of clang that would
473 prefer the -Wswitch-enum compiler flag to warn about switch
474 statements with missing enum values, even if those switch
475 statements have a "default:" statement. Fixes bug 8598; bugfix
478 o Minor bugfixes (protocol):
479 - Fix the handling of a TRUNCATE cell when it arrives while the
480 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
481 - Fix a misframing issue when reading the version numbers in a
482 VERSIONS cell. Previously we would recognize [00 01 00 02] as
483 'version 1, version 2, and version 0x100', when it should have
484 only included versions 1 and 2. Fixes bug 8059; bugfix on
485 0.2.0.10-alpha. Reported pseudonymously.
486 - Make the format and order of STREAM events for DNS lookups
487 consistent among the various ways to launch DNS lookups. Fixes
488 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
489 - Correct our check for which versions of Tor support the EXTEND2
490 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
491 later, when support was really added in version 0.2.4.8-alpha.
492 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
494 o Minor bugfixes (other):
495 - Correctly store microdescriptors and extrainfo descriptors with
496 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
497 Bug reported by "cypherpunks".
498 - Increase the width of the field used to remember a connection's
499 link protocol version to two bytes. Harmless for now, since the
500 only currently recognized versions are one byte long. Reported
501 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
502 - If the state file's path bias counts are invalid (presumably from a
503 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
504 additional checks and log messages to the scaling of Path Bias
505 counts, in case there still are remaining issues with scaling.
506 Should help resolve bug 8235.
507 - Eliminate several instances where we use "Nickname=ID" to refer to
508 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
509 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
510 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
512 o Minor bugfixes (syscalls):
513 - Always check the return values of functions fcntl() and
514 setsockopt(). We don't believe these are ever actually failing in
515 practice, but better safe than sorry. Also, checking these return
516 values should please analysis tools like Coverity. Patch from
517 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
518 - Use direct writes rather than stdio when building microdescriptor
519 caches, in an attempt to mitigate bug 8031, or at least make it
522 o Minor bugfixes (config):
523 - When rejecting a configuration because we were unable to parse a
524 quoted string, log an actual error message. Fixes bug 7950; bugfix
526 - Behave correctly when the user disables LearnCircuitBuildTimeout
527 but doesn't tell us what they would like the timeout to be. Fixes
528 bug 6304; bugfix on 0.2.2.14-alpha.
529 - When autodetecting the number of CPUs, use the number of available
530 CPUs in preference to the number of configured CPUs. Inform the
531 user if this reduces the number of available CPUs. Fixes bug 8002;
532 bugfix on 0.2.3.1-alpha.
533 - Make it an error when you set EntryNodes but disable UseGuardNodes,
534 since it will (surprisingly to some users) ignore EntryNodes. Fixes
535 bug 8180; bugfix on 0.2.3.11-alpha.
536 - Allow TestingTorNetworks to override the 4096-byte minimum for
537 the Fast threshold. Otherwise they can't bootstrap until they've
538 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
539 - Fix some logic errors when the user manually overrides the
540 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
543 o Minor bugfixes (log messages to help diagnose bugs):
544 - If we fail to free a microdescriptor because of bug 7164, log
545 the filename and line number from which we tried to free it.
546 - Add another diagnostic to the heartbeat message: track and log
547 overhead that TLS is adding to the data we write. If this is
548 high, we are sending too little data to SSL_write at a time.
549 Diagnostic for bug 7707.
550 - Add more detail to a log message about relaxed timeouts, to help
552 - Warn more aggressively when flushing microdescriptors to a
553 microdescriptor cache fails, in an attempt to mitigate bug 8031,
554 or at least make it more diagnosable.
555 - Improve debugging output to help track down bug 8185 ("Bug:
556 outgoing relay cell has n_chan==NULL. Dropping.")
557 - Log the purpose of a path-bias testing circuit correctly.
558 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
560 o Minor bugfixes (0.2.4.x log messages that were too noisy):
561 - Don't attempt to relax the timeout of already opened 1-hop circuits.
562 They might never timeout. This should eliminate some/all cases of
563 the relaxed timeout log message.
564 - Use circuit creation time for network liveness evaluation. This
565 should eliminate warning log messages about liveness caused
566 by changes in timeout evaluation. Fixes bug 6572; bugfix on
568 - Reduce a path bias length check from notice to info. The message
569 is triggered when creating controller circuits. Fixes bug 8196;
570 bugfix on 0.2.4.8-alpha.
571 - Fix a path state issue that triggered a notice during relay startup.
572 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
573 - Reduce occurrences of warns about circuit purpose in
574 connection_ap_expire_building(). Fixes bug 8477; bugfix on
577 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
578 - If we encounter a write failure on a SOCKS connection before we
579 finish our SOCKS handshake, don't warn that we closed the
580 connection before we could send a SOCKS reply. Fixes bug 8427;
581 bugfix on 0.1.0.1-rc.
582 - Correctly recognize that [::1] is a loopback address. Fixes
583 bug 8377; bugfix on 0.2.1.3-alpha.
584 - Fix a directory authority warn caused when we have a large amount
585 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
586 - Don't log inappropriate heartbeat messages when hibernating: a
587 hibernating node is _expected_ to drop out of the consensus,
588 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
589 bugfix on 0.2.3.1-alpha.
590 - Don't complain about bootstrapping problems while hibernating.
591 These complaints reflect a general code problem, but not one
592 with any problematic effects (no connections are actually
593 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
595 o Documentation fixes:
596 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
597 names match. Fixes bug 7768.
598 - Make the torify manpage no longer refer to tsocks; torify hasn't
599 supported tsocks since 0.2.3.14-alpha.
600 - Make the tor manpage no longer reference tsocks.
601 - Fix the GeoIPExcludeUnknown documentation to refer to
602 ExcludeExitNodes rather than the currently nonexistent
603 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
606 - The tor-tsocks.conf is no longer distributed or installed. We
607 recommend that tsocks users use torsocks instead. Resolves
611 Changes in version 0.2.4.11-alpha - 2013-03-11
612 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
613 more robust, makes hidden service authentication work again, and
614 resolves a DPI fingerprint for Tor's SSL transport.
616 o Major features (directory authorities):
617 - Directory authorities now support a new consensus method (17)
618 where they cap the published bandwidth of servers for which
619 insufficient bandwidth measurements exist. Fixes part of bug 2286.
620 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
621 serve any v2 directory information. Now we can test disabling the
622 old deprecated v2 directory format, and see whether doing so has
623 any effect on network load. Begins to fix bug 6783.
624 - Directory authorities now include inside each vote a statement of
625 the performance thresholds they used when assigning flags.
626 Implements ticket 8151.
628 o Major bugfixes (directory authorities):
629 - Stop marking every relay as having been down for one hour every
630 time we restart a directory authority. These artificial downtimes
631 were messing with our Stable and Guard flag calculations. Fixes
632 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
634 o Major bugfixes (hidden services):
635 - Allow hidden service authentication to succeed again. When we
636 refactored the hidden service introduction code back
637 in 0.2.4.1-alpha, we didn't update the code that checks
638 whether authentication information is present, causing all
639 authentication checks to return "false". Fix for bug 8207; bugfix
640 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
642 o Minor features (relays, bridges):
643 - Make bridge relays check once a minute for whether their IP
644 address has changed, rather than only every 15 minutes. Resolves
646 - Refactor resolve_my_address() so it returns the method by which we
647 decided our public IP address (explicitly configured, resolved from
648 explicit hostname, guessed from interfaces, learned by gethostname).
649 Now we can provide more helpful log messages when a relay guesses
650 its IP address incorrectly (e.g. due to unexpected lines in
651 /etc/hosts). Resolves ticket 2267.
652 - Teach bridge-using clients to avoid 0.2.2 bridges when making
653 microdescriptor-related dir requests, and only fall back to normal
654 descriptors if none of their bridges can handle microdescriptors
655 (as opposed to the fix in ticket 4013, which caused them to fall
656 back to normal descriptors if *any* of their bridges preferred
657 them). Resolves ticket 4994.
658 - Randomize the lifetime of our SSL link certificate, so censors can't
659 use the static value for filtering Tor flows. Resolves ticket 8443;
660 related to ticket 4014 which was included in 0.2.2.33.
662 o Minor features (portability):
663 - Tweak the curve25519-donna*.c implementations to tolerate systems
664 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
665 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
666 the signs of types during autoconf. This is better than our old
667 approach, which didn't work when cross-compiling.
668 - Detect the sign of enum values, rather than assuming that MSC is the
669 only compiler where enum types are all signed. Fixes bug 7727;
670 bugfix on 0.2.4.10-alpha.
672 o Minor features (other):
673 - Say "KBytes" rather than "KB" in the man page (for various values
674 of K), to further reduce confusion about whether Tor counts in
675 units of memory or fractions of units of memory. Resolves ticket 7054.
676 - Clear the high bit on curve25519 public keys before passing them to
677 our backend, in case we ever wind up using a backend that doesn't do
678 so itself. If we used such a backend, and *didn't* clear the high bit,
679 we could wind up in a situation where users with such backends would
680 be distinguishable from users without. Fixes bug 8121; bugfix on
682 - Update to the March 6 2013 Maxmind GeoLite Country database.
684 o Minor bugfixes (clients):
685 - When we receive a RELAY_END cell with the reason DONE, or with no
686 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
687 status as "connection refused". Previously we reported these cases
688 as success but then immediately closed the connection. Fixes bug
689 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
690 - Downgrade an assertion in connection_ap_expire_beginning to an
691 LD_BUG message. The fix for bug 8024 should prevent this message
692 from displaying, but just in case, a warn that we can diagnose
693 is better than more assert crashes. Fixes bug 8065; bugfix on
695 - Lower path use bias thresholds to .80 for notice and .60 for warn.
696 Also make the rate limiting flags for the path use bias log messages
697 independent from the original path bias flags. Fixes bug 8161;
698 bugfix on 0.2.4.10-alpha.
700 o Minor bugfixes (relays):
701 - Stop trying to resolve our hostname so often (e.g. every time we
702 think about doing a directory fetch). Now we reuse the cached
703 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
704 and 2410 (bugfix on 0.1.2.2-alpha).
705 - Stop sending a stray "(null)" in some cases for the server status
706 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
708 - When choosing which stream on a formerly stalled circuit to wake
709 first, make better use of the platform's weak RNG. Previously,
710 we had been using the % ("modulo") operator to try to generate a
711 1/N chance of picking each stream, but this behaves badly with
712 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
714 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
715 Irix's random() only return 15 bits; Solaris's random() returns more
716 bits but its RAND_MAX says it only returns 15, and so on. Motivated
717 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
719 o Minor bugfixes (directory authorities):
720 - Directory authorities now use less space when formatting identical
721 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
724 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
725 - Avoid leaking memory if we fail to compute a consensus signature
726 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
727 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
729 - Fix a memory leak during safe-cookie controller authentication.
730 Bugfix on 0.2.3.13-alpha.
731 - Avoid memory leak of IPv6 policy content if we fail to format it into
732 a router descriptor. Bugfix on 0.2.4.7-alpha.
734 o Minor bugfixes (other code correctness issues):
735 - Avoid a crash if we fail to generate an extrainfo descriptor.
736 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
738 - When detecting the largest possible file descriptor (in order to
739 close all file descriptors when launching a new program), actually
740 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
741 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
743 - Fix a copy-and-paste error when adding a missing A1 to a routerset
744 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
745 Bugfix on 0.2.4.10-alpha.
746 - Fix an impossible-to-trigger integer overflow when estimating how
747 long our onionskin queue would take. (This overflow would require us
748 to accept 4 million onionskins before processing 100 of them.) Fixes
749 bug 8210; bugfix on 0.2.4.10-alpha.
751 o Code simplification and refactoring:
752 - Add a wrapper function for the common "log a message with a
756 Changes in version 0.2.4.10-alpha - 2013-02-04
757 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
758 certain attacks that flood the network with relays; changes the queue
759 for circuit create requests from a sized-based limit to a time-based
760 limit; resumes building with MSVC on Windows; and fixes a wide variety
763 o Major bugfixes (directory authority):
764 - When computing directory thresholds, ignore any rejected-as-sybil
765 nodes during the computation so that they can't influence Fast,
766 Guard, etc. (We should have done this for proposal 109.) Fixes
768 - When marking a node as a likely sybil, reset its uptime metrics
769 to zero, so that it cannot time towards getting marked as Guard,
770 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
774 - When a TLS write is partially successful but incomplete, remember
775 that the flushed part has been flushed, and notice that bytes were
776 actually written. Reported and fixed pseudonymously. Fixes bug
777 7708; bugfix on Tor 0.1.0.5-rc.
778 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
779 ID: these could be used to create unexpected streams and circuits
780 which would count as "present" to some parts of Tor but "absent"
781 to others, leading to zombie circuits and streams or to a bandwidth
782 denial-of-service. Fixes bug 7889; bugfix on every released version
783 of Tor. Reported by "oftc_must_be_destroyed".
784 - Rename all macros in our local copy of queue.h to begin with "TOR_".
785 This change seems the only good way to permanently prevent conflicts
786 with queue.h on various operating systems. Fixes bug 8107; bugfix
789 o Major features (relay):
790 - Instead of limiting the number of queued onionskins (aka circuit
791 create requests) to a fixed, hard-to-configure number, we limit
792 the size of the queue based on how many we expect to be able to
793 process in a given amount of time. We estimate the time it will
794 take to process an onionskin based on average processing time
795 of previous onionskins. Closes ticket 7291. You'll never have to
796 configure MaxOnionsPending again.
798 o Major features (portability):
799 - Resume building correctly with MSVC and Makefile.nmake. This patch
800 resolves numerous bugs and fixes reported by ultramage, including
801 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
802 - Make the ntor and curve25519 code build correctly with MSVC.
803 Fix on 0.2.4.8-alpha.
806 - When directory authorities are computing thresholds for flags,
807 never let the threshold for the Fast flag fall below 4096
808 bytes. Also, do not consider nodes with extremely low bandwidths
809 when deciding thresholds for various directory flags. This change
810 should raise our threshold for Fast relays, possibly in turn
811 improving overall network performance; see ticket 1854. Resolves
813 - The Tor client now ignores sub-domain components of a .onion
814 address. This change makes HTTP "virtual" hosting
815 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
816 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
817 hosted on the same hidden service. Implements proposal 204.
818 - We compute the overhead from passing onionskins back and forth to
819 cpuworkers, and report it when dumping statistics in response to
820 SIGUSR1. Supports ticket 7291.
822 o Minor features (path selection):
823 - When deciding whether we have enough descriptors to build circuits,
824 instead of looking at raw relay counts, look at which fraction
825 of (bandwidth-weighted) paths we're able to build. This approach
826 keeps clients from building circuits if their paths are likely to
827 stand out statistically. The default fraction of paths needed is
828 taken from the consensus directory; you can override it with the
829 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
830 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
831 and we have GeoIP information, also exclude all nodes with unknown
832 countries "??" and "A1". This behavior is controlled by the
833 new GeoIPExcludeUnknown option: you can make such nodes always
834 excluded with "GeoIPExcludeUnknown 1", and disable the feature
835 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
836 gets you the default behavior. Implements feature 7706.
837 - Path Use Bias: Perform separate accounting for successful circuit
838 use. Keep separate statistics on stream attempt rates versus stream
839 success rates for each guard. Provide configurable thresholds to
840 determine when to emit log messages or disable use of guards that
841 fail too many stream attempts. Resolves ticket 7802.
843 o Minor features (log messages):
844 - When learning a fingerprint for a bridge, log its corresponding
845 transport type. Implements ticket 7896.
846 - Improve the log message when "Bug/attack: unexpected sendme cell
847 from client" occurs, to help us track bug 8093.
850 - Remove a couple of extraneous semicolons that were upsetting the
851 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
852 bugfix on 0.2.2.1-alpha.
853 - Remove a source of rounding error during path bias count scaling;
854 don't count cannibalized circuits as used for path bias until we
855 actually try to use them; and fix a circuit_package_relay_cell()
856 warning message about n_chan==NULL. Fixes bug 7802.
857 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
858 actually link against nacl when we're configured to use it. Fixes
859 bug 7972; bugfix on 0.2.4.8-alpha.
860 - Compile correctly with the --disable-curve25519 option. Fixes
861 bug 8153; bugfix on 0.2.4.8-alpha.
863 o Build improvements:
864 - Do not report status verbosely from autogen.sh unless the -v flag
865 is specified. Fixes issue 4664. Patch from Onizuka.
866 - Replace all calls to snprintf() outside of src/ext with
867 tor_snprintf(). Also remove the #define to replace snprintf with
868 _snprintf on Windows; they have different semantics, and all of
869 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
870 - Try to detect if we are ever building on a platform where
871 memset(...,0,...) does not set the value of a double to 0.0. Such
872 platforms are permitted by the C standard, though in practice
873 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
874 currently support them, but it's better to detect them and fail
875 than to perform erroneously.
878 - Stop exporting estimates of v2 and v3 directory traffic shares
879 in extrainfo documents. They were unneeded and sometimes inaccurate.
880 Also stop exporting any v2 directory request statistics. Resolves
882 - Drop support for detecting and warning about versions of Libevent
883 before 1.3e. Nothing reasonable ships with them any longer;
884 warning the user about them shouldn't be needed. Resolves ticket
887 o Code simplifications and refactoring:
888 - Rename "isin" functions to "contains", for grammar. Resolves
890 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
891 with the natural logarithm function from the system libm. Resolves
895 Changes in version 0.2.4.9-alpha - 2013-01-15
896 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
900 - Fix backward compatibility logic when receiving an embedded ntor
901 handshake tunneled in a CREATE cell. This clears up the "Bug:
902 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
906 Changes in version 0.2.4.8-alpha - 2013-01-14
907 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
908 risks, adds a new stronger and faster circuit handshake, and offers
909 stronger and faster link encryption when both sides support it.
912 - Preliminary support for directory guards (proposal 207): when
913 possible, clients now use their entry guards for non-anonymous
914 directory requests. This can help prevent client enumeration. Note
915 that this behavior only works when we have a usable consensus
916 directory, and when options about what to download are more or less
917 standard. In the future we should re-bootstrap from our guards,
918 rather than re-bootstrapping from the preconfigured list of
919 directory sources that ships with Tor. Resolves ticket 6526.
920 - Tor relays and clients now support a better CREATE/EXTEND cell
921 format, allowing the sender to specify multiple address, identity,
922 and handshake types. Implements Robert Ransom's proposal 200;
925 o Major features (new circuit handshake):
926 - Tor now supports a new circuit extension handshake designed by Ian
927 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
928 circuit extension handshake, later called "TAP", was a bit slow
929 (especially on the relay side), had a fragile security proof, and
930 used weaker keys than we'd now prefer. The new circuit handshake
931 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
932 function, making it significantly more secure than the older
933 handshake, and significantly faster. Tor can use one of two built-in
934 pure-C curve25519-donna implementations by Adam Langley, or it
935 can link against the "nacl" library for a tuned version if present.
937 The built-in version is very fast for 64-bit systems when building
938 with GCC. The built-in 32-bit version is still faster than the
939 old TAP protocol, but using libnacl is better on most such hosts.
941 Clients don't currently use this protocol by default, since
942 comparatively few clients support it so far. To try it, set
943 UseNTorHandshake to 1.
945 Implements proposal 216; closes ticket 7202.
947 o Major features (better link encryption):
948 - Relays can now enable the ECDHE TLS ciphersuites when available
949 and appropriate. These ciphersuites let us negotiate forward-secure
950 TLS secret keys more safely and more efficiently than with our
951 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
952 public relays prefer the (faster) P224 group, and bridges prefer
953 the (more common) P256 group; you can override this with the
956 Enabling these ciphers was a little tricky, since for a long time,
957 clients had been claiming to support them without actually doing
958 so, in order to foil fingerprinting. But with the client-side
959 implementation of proposal 198 in 0.2.3.17-beta, clients can now
960 match the ciphers from recent Firefox versions *and* list the
961 ciphers they actually mean, so relays can believe such clients
962 when they advertise ECDHE support in their TLS ClientHello messages.
964 This feature requires clients running 0.2.3.17-beta or later,
965 and requires both sides to be running OpenSSL 1.0.0 or later
966 with ECC support. OpenSSL 1.0.1, with the compile-time option
967 "enable-ec_nistp_64_gcc_128", is highly recommended.
969 Implements the relay side of proposal 198; closes ticket 7200.
972 - Avoid crashing when, as a relay without IPv6-exit support, a
973 client insists on getting an IPv6 address or nothing. Fixes bug
974 7814; bugfix on 0.2.4.7-alpha.
977 - Improve circuit build timeout handling for hidden services.
978 In particular: adjust build timeouts more accurately depending
979 upon the number of hop-RTTs that a particular circuit type
980 undergoes. Additionally, launch intro circuits in parallel
981 if they timeout, and take the first one to reply as valid.
982 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
983 separate error codes; or at least, don't break for that reason.
984 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
985 - Update to the January 2 2013 Maxmind GeoLite Country database.
987 o Minor features (testing):
988 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
989 (P-256) Diffie-Hellman handshakes to src/or/bench.
990 - Add benchmark functions to test onion handshake performance.
992 o Minor features (path bias detection):
993 - Alter the Path Bias log messages to be more descriptive in terms
994 of reporting timeouts and other statistics.
995 - Create three levels of Path Bias log messages, as opposed to just
996 two. These are configurable via consensus as well as via the torrc
997 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
998 The default values are 0.70, 0.50, and 0.30 respectively.
999 - Separate the log message levels from the decision to drop guards,
1000 which also is available via torrc option PathBiasDropGuards.
1001 PathBiasDropGuards still defaults to 0 (off).
1002 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
1003 in combination with PathBiasExtremeRate.
1004 - Increase the default values for PathBiasScaleThreshold and
1005 PathBiasCircThreshold from (200, 20) to (300, 150).
1006 - Add in circuit usage accounting to path bias. If we try to use a
1007 built circuit but fail for any reason, it counts as path bias.
1008 Certain classes of circuits where the adversary gets to pick your
1009 destination node are exempt from this accounting. Usage accounting
1010 can be specifically disabled via consensus parameter or torrc.
1011 - Convert all internal path bias state to double-precision floating
1012 point, to avoid roundoff error and other issues.
1013 - Only record path bias information for circuits that have completed
1014 *two* hops. Assuming end-to-end tagging is the attack vector, this
1015 makes us more resilient to ambient circuit failure without any
1016 detection capability loss.
1018 o Minor bugfixes (log messages):
1019 - Rate-limit the "No circuits are opened. Relaxed timeout for a
1020 circuit with channel state open..." message to once per hour to
1021 keep it from filling the notice logs. Mitigates bug 7799 but does
1022 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
1023 - Avoid spurious warnings when configuring multiple client ports of
1024 which only some are nonlocal. Previously, we had claimed that some
1025 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
1028 o Code simplifications and refactoring:
1029 - Get rid of a couple of harmless clang warnings, where we compared
1030 enums to ints. These warnings are newly introduced in clang 3.2.
1031 - Split the onion.c file into separate modules for the onion queue
1032 and the different handshakes it supports.
1033 - Remove the marshalling/unmarshalling code for sending requests to
1034 cpuworkers over a socket, and instead just send structs. The
1035 recipient will always be the same Tor binary as the sender, so
1036 any encoding is overkill.
1039 Changes in version 0.2.4.7-alpha - 2012-12-24
1040 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
1041 directory mirrors for more robust bootstrapping; fixes more issues where
1042 clients with changing network conditions refuse to make any circuits;
1043 adds initial support for exiting to IPv6 addresses; resumes being able
1044 to update our GeoIP database, and includes the geoip6 file this time;
1045 turns off the client-side DNS cache by default due to privacy risks;
1046 and fixes a variety of other issues.
1048 o Major features (client resilience):
1049 - Add a new "FallbackDir" torrc option to use when we can't use
1050 a directory mirror from the consensus (either because we lack a
1051 consensus, or because they're all down). Currently, all authorities
1052 are fallbacks by default, and there are no other default fallbacks,
1053 but that will change. This option will allow us to give clients a
1054 longer list of servers to try to get a consensus from when first
1055 connecting to the Tor network, and thereby reduce load on the
1056 directory authorities. Implements proposal 206, "Preconfigured
1057 directory sources for bootstrapping". We also removed the old
1058 "FallbackNetworkstatus" option, since we never got it working well
1059 enough to use it. Closes bug 572.
1060 - If we have no circuits open, use a relaxed timeout (the
1061 95th-percentile cutoff) until a circuit succeeds. This heuristic
1062 should allow Tor to succeed at building circuits even when the
1063 network connection drastically changes. Should help with bug 3443.
1065 o Major features (IPv6):
1066 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
1067 connectivity, then set the IPv6Exit flag to 1. Also make sure your
1068 exit policy reads as you would like: the address * applies to all
1069 address families, whereas *4 is IPv4 address only, and *6 is IPv6
1070 addresses only. On the client side, you'll need to wait until the
1071 authorities have upgraded, wait for enough exits to support IPv6,
1072 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
1073 ticket 5547, implements proposal 117 as revised in proposal 208.
1075 We DO NOT recommend that clients with actual anonymity needs start
1076 using IPv6 over Tor yet, since not enough exits support it yet.
1078 o Major features (geoip database):
1079 - Maxmind began labelling Tor relays as being in country "A1",
1080 which breaks by-country node selection inside Tor. Now we use a
1081 script to replace "A1" ("Anonymous Proxy") entries in our geoip
1082 file with real country codes. This script fixes about 90% of "A1"
1083 entries automatically and uses manual country code assignments to
1084 fix the remaining 10%. See src/config/README.geoip for details.
1085 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
1086 Country database, as modified above.
1088 o Major bugfixes (client-side DNS):
1089 - Turn off the client-side DNS cache by default. Updating and using
1090 the DNS cache is now configurable on a per-client-port
1091 level. SOCKSPort, DNSPort, etc lines may now contain
1092 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
1093 cache these types of DNS answers when we receive them from an
1094 exit node in response to an application request on this port, and
1095 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
1096 cached DNS answers of these types, we shouldn't use them. It's
1097 potentially risky to use cached DNS answers at the client, since
1098 doing so can indicate to one exit what answers we've gotten
1099 for DNS lookups in the past. With IPv6, this becomes especially
1100 problematic. Using cached DNS answers for requests on the same
1101 circuit would present less linkability risk, since all traffic
1102 on a circuit is already linkable, but it would also provide
1103 little performance benefit: the exit node caches DNS replies
1104 too. Implements a simplified version of Proposal 205. Implements
1107 o Major bugfixes (other):
1108 - Alter circuit build timeout measurement to start at the point
1109 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
1110 initialization). This should make our timeout measurements more
1111 uniform. Previously, we were sometimes including ORconn setup time
1112 in our circuit build time measurements. Should resolve bug 3443.
1113 - Fix an assertion that could trigger in hibernate_go_dormant() when
1114 closing an or_connection_t: call channel_mark_for_close() rather
1115 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
1117 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
1118 7655; bugfix on 0.2.4.6-alpha.
1121 - Add a new torrc option "ServerTransportListenAddr" to let bridge
1122 operators select the address where their pluggable transports will
1123 listen for connections. Resolves ticket 7013.
1124 - Allow an optional $ before the node identity digest in the
1125 controller command GETINFO ns/id/<identity>, for consistency with
1126 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
1127 - Log packaged cell fullness as part of the heartbeat message.
1128 Diagnosis to try to determine the extent of bug 7743.
1130 o Minor features (IPv6):
1131 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
1132 prefer to hand out virtual IPv6 addresses, since there are more of
1133 them and we can't run out. To override this behavior and make IPv4
1134 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
1135 or DNSPort you're using for resolving. Implements ticket 7571.
1136 - AutomapHostsOnResolve responses are now randomized, to avoid
1137 annoying situations where Tor is restarted and applications
1138 connect to the wrong addresses.
1139 - Never try more than 1000 times to pick a new virtual address when
1140 AutomapHostsOnResolve is set. That's good enough so long as we
1141 aren't close to handing out our entire virtual address space;
1142 if you're getting there, it's best to switch to IPv6 virtual
1146 - The ADDRMAP command can no longer generate an ill-formed error
1147 code on a failed MAPADDRESS. It now says "internal" rather than
1148 an English sentence fragment with spaces in the middle. Bugfix on
1150 - Fix log messages and comments to avoid saying "GMT" when we mean
1151 "UTC". Fixes bug 6113.
1152 - Compile on win64 using mingw64. Fixes bug 7260; patches from
1154 - Fix a crash when debugging unit tests on Windows: deallocate a
1155 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
1156 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
1159 - The DirServer option is now DirAuthority, for consistency with
1160 current naming patterns. You can still use the old DirServer form.
1162 o Code simplification and refactoring:
1163 - Move the client-side address-map/virtual-address/DNS-cache code
1164 out of connection_edge.c into a new addressmap.c module.
1165 - Remove unused code for parsing v1 directories and "running routers"
1166 documents. Fixes bug 6887.
1169 Changes in version 0.2.3.25 - 2012-11-19
1170 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
1171 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
1172 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
1173 programmer, and friend. Unstinting in his dedication to the cause of
1174 freedom, he inspired and helped many of us as we began our work on
1175 anonymity, and inspires us still. Please honor his memory by writing
1176 software to protect people's freedoms, and by helping others to do so.
1178 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
1179 significantly reduced directory overhead (via microdescriptors),
1180 enormous crypto performance improvements for fast relays on new
1181 enough hardware, a new v3 TLS handshake protocol that can better
1182 resist fingerprinting, support for protocol obfuscation plugins (aka
1183 pluggable transports), better scalability for hidden services, IPv6
1184 support for bridges, performance improvements like allowing clients
1185 to skip the first round-trip on the circuit ("optimistic data") and
1186 refilling token buckets more often, a new "stream isolation" design
1187 to isolate different applications on different circuits, and many
1188 stability, security, and privacy fixes.
1191 - Tor tries to wipe potentially sensitive data after using it, so
1192 that if some subsequent security failure exposes Tor's memory,
1193 the damage will be limited. But we had a bug where the compiler
1194 was eliminating these wipe operations when it decided that the
1195 memory was no longer visible to a (correctly running) program,
1196 hence defeating our attempt at defense in depth. We fix that
1197 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1198 is unlikely to optimize away. Future versions of Tor may use
1199 a less ridiculously heavy approach for this. Fixes bug 7352.
1200 Reported in an article by Andrey Karpov.
1203 - Fix a harmless bug when opting against publishing a relay descriptor
1204 because DisableNetwork is set. Fixes bug 7464; bugfix on
1208 Changes in version 0.2.4.6-alpha - 2012-11-13
1209 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
1210 makes our defense-in-depth memory wiping more reliable, and begins to
1211 count IPv6 addresses in bridge statistics,
1214 - Fix an assertion failure that could occur when closing a connection
1215 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
1217 - Tor tries to wipe potentially sensitive data after using it, so
1218 that if some subsequent security failure exposes Tor's memory,
1219 the damage will be limited. But we had a bug where the compiler
1220 was eliminating these wipe operations when it decided that the
1221 memory was no longer visible to a (correctly running) program,
1222 hence defeating our attempt at defense in depth. We fix that
1223 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1224 is unlikely to optimize away. Future versions of Tor may use
1225 a less ridiculously heavy approach for this. Fixes bug 7352.
1226 Reported in an article by Andrey Karpov.
1229 - Add GeoIP database for IPv6 addresses. The new config option
1231 - Bridge statistics now count bridge clients connecting over IPv6:
1232 bridge statistics files now list "bridge-ip-versions" and
1233 extra-info documents list "geoip6-db-digest". The control protocol
1234 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
1235 implementation by "shkoo", addressing ticket 5055.
1238 - Warn when we are binding low ports when hibernation is enabled;
1239 previously we had warned when we were _advertising_ low ports with
1240 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
1241 - Fix a harmless bug when opting against publishing a relay descriptor
1242 because DisableNetwork is set. Fixes bug 7464; bugfix on
1244 - Add warning message when a managed proxy dies during configuration.
1245 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
1246 - Fix a linking error when building tor-fw-helper without miniupnp.
1247 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
1248 - Check for closing an or_connection_t without going through correct
1249 channel functions; emit a warning and then call
1250 connection_or_close_for_error() so we don't assert as in bugs 7212
1252 - Compile correctly on compilers without C99 designated initializer
1253 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
1254 - Avoid a possible assert that can occur when channel_send_destroy() is
1255 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
1256 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
1257 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
1258 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
1259 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
1261 o Code simplification and refactoring:
1262 - Start using OpenBSD's implementation of queue.h, so that we don't
1263 need to hand-roll our own pointer and list structures whenever we
1264 need them. (We can't rely on a sys/queue.h, since some operating
1265 systems don't have them, and the ones that do have them don't all
1266 present the same extensions.)
1269 Changes in version 0.2.4.5-alpha - 2012-10-25
1270 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
1271 two important security vulnerabilities that could lead to remotely
1272 triggerable relay crashes, fix a major bug that was preventing clients
1273 from choosing suitable exit nodes, and refactor some of our code.
1275 o Major bugfixes (security, also in 0.2.3.24-rc):
1276 - Fix a group of remotely triggerable assertion failures related to
1277 incorrect link protocol negotiation. Found, diagnosed, and fixed
1278 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1280 - Fix a denial of service attack by which any directory authority
1281 could crash all the others, or by which a single v2 directory
1282 authority could crash everybody downloading v2 directory
1283 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1285 o Major bugfixes (also in 0.2.3.24-rc):
1286 - When parsing exit policy summaries from microdescriptors, we had
1287 previously been ignoring the last character in each one, so that
1288 "accept 80,443,8080" would be treated by clients as indicating
1289 a node that allows access to ports 80, 443, and 808. That would
1290 lead to clients attempting connections that could never work,
1291 and ignoring exit nodes that would support their connections. Now
1292 clients parse these exit policy summaries correctly. Fixes bug 7192;
1293 bugfix on 0.2.3.1-alpha.
1295 o Minor bugfixes (also in 0.2.3.24-rc):
1296 - Clients now consider the ClientRejectInternalAddresses config option
1297 when using a microdescriptor consensus stanza to decide whether
1298 an exit relay would allow exiting to an internal address. Fixes
1299 bug 7190; bugfix on 0.2.3.1-alpha.
1302 - Only disable TLS session ticket support when running as a TLS
1303 server. Now clients will blend better with regular Firefox
1304 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
1306 o Code simplification and refactoring:
1307 - Start using OpenBSD's implementation of queue.h (originally by
1309 - Move the entry node code from circuitbuild.c to its own file.
1310 - Move the circuit build timeout tracking code from circuitbuild.c
1314 Changes in version 0.2.3.24-rc - 2012-10-25
1315 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
1316 could lead to remotely triggerable relay crashes, and fixes
1317 a major bug that was preventing clients from choosing suitable exit
1320 o Major bugfixes (security):
1321 - Fix a group of remotely triggerable assertion failures related to
1322 incorrect link protocol negotiation. Found, diagnosed, and fixed
1323 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1325 - Fix a denial of service attack by which any directory authority
1326 could crash all the others, or by which a single v2 directory
1327 authority could crash everybody downloading v2 directory
1328 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1331 - When parsing exit policy summaries from microdescriptors, we had
1332 previously been ignoring the last character in each one, so that
1333 "accept 80,443,8080" would be treated by clients as indicating
1334 a node that allows access to ports 80, 443, and 808. That would
1335 lead to clients attempting connections that could never work,
1336 and ignoring exit nodes that would support their connections. Now
1337 clients parse these exit policy summaries correctly. Fixes bug 7192;
1338 bugfix on 0.2.3.1-alpha.
1341 - Clients now consider the ClientRejectInternalAddresses config option
1342 when using a microdescriptor consensus stanza to decide whether
1343 an exit relay would allow exiting to an internal address. Fixes
1344 bug 7190; bugfix on 0.2.3.1-alpha.
1347 Changes in version 0.2.4.4-alpha - 2012-10-20
1348 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
1349 vulnerability introduced by a change in OpenSSL, fixes a remotely
1350 triggerable assert, and adds new channel_t and circuitmux_t abstractions
1351 that will make it easier to test new connection transport and cell
1352 scheduling algorithms.
1354 o New directory authorities (also in 0.2.3.23-rc):
1355 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1356 authority. Closes ticket 5749.
1358 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
1359 - Disable TLS session tickets. OpenSSL's implementation was giving
1360 our TLS session keys the lifetime of our TLS context objects, when
1361 perfect forward secrecy would want us to discard anything that
1362 could decrypt a link connection as soon as the link connection
1363 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1364 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1365 - Discard extraneous renegotiation attempts once the V3 link
1366 protocol has been initiated. Failure to do so left us open to
1367 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1368 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1370 o Internal abstraction features:
1371 - Introduce new channel_t abstraction between circuits and
1372 or_connection_t to allow for implementing alternate OR-to-OR
1373 transports. A channel_t is an abstract object which can either be a
1374 cell-bearing channel, which is responsible for authenticating and
1375 handshaking with the remote OR and transmitting cells to and from
1376 it, or a listening channel, which spawns new cell-bearing channels
1377 at the request of remote ORs. Implements part of ticket 6465.
1378 - Also new is the channel_tls_t subclass of channel_t, adapting it
1379 to the existing or_connection_t code. The V2/V3 protocol handshaking
1380 code which formerly resided in command.c has been moved below the
1381 channel_t abstraction layer and may be found in channeltls.c now.
1382 Implements the rest of ticket 6465.
1383 - Introduce new circuitmux_t storing the queue of circuits for
1384 a channel; this encapsulates and abstracts the queue logic and
1385 circuit selection policy, and allows the latter to be overridden
1386 easily by switching out a policy object. The existing EWMA behavior
1387 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
1389 o Required libraries:
1390 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
1391 strongly recommended.
1394 - Warn users who run hidden services on a Tor client with
1395 UseEntryGuards disabled that their hidden services will be
1396 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
1397 attack which motivated Tor to support entry guards in the first
1398 place). Resolves ticket 6889.
1399 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
1400 dhill. Resolves ticket 6982.
1401 - Option OutboundBindAddress can be specified multiple times and
1402 accepts IPv6 addresses. Resolves ticket 6876.
1404 o Minor bugfixes (also in 0.2.3.23-rc):
1405 - Don't serve or accept v2 hidden service descriptors over a
1406 relay's DirPort. It's never correct to do so, and disabling it
1407 might make it more annoying to exploit any bugs that turn up in the
1408 descriptor-parsing code. Fixes bug 7149.
1409 - Fix two cases in src/or/transports.c where we were calling
1410 fmt_addr() twice in a parameter list. Bug found by David
1411 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1412 - Fix memory leaks whenever we logged any message about the "path
1413 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1414 - When relays refuse a "create" cell because their queue of pending
1415 create cells is too big (typically because their cpu can't keep up
1416 with the arrival rate), send back reason "resource limit" rather
1417 than reason "internal", so network measurement scripts can get a
1418 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
1421 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
1422 - Free some more still-in-use memory at exit, to make hunting for
1423 memory leaks easier. Resolves bug 7029.
1424 - When a Tor client gets a "truncated" relay cell, the first byte of
1425 its payload specifies why the circuit was truncated. We were
1426 ignoring this 'reason' byte when tearing down the circuit, resulting
1427 in the controller not being told why the circuit closed. Now we
1428 pass the reason from the truncated cell to the controller. Bugfix
1429 on 0.1.2.3-alpha; fixes bug 7039.
1430 - Downgrade "Failed to hand off onionskin" messages to "debug"
1431 severity, since they're typically redundant with the "Your computer
1432 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
1433 - Make clients running with IPv6 bridges connect over IPv6 again,
1434 even without setting new config options ClientUseIPv6 and
1435 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
1436 - Use square brackets around IPv6 addresses in numerous places
1437 that needed them, including log messages, HTTPS CONNECT proxy
1438 requests, TransportProxy statefile entries, and pluggable transport
1439 extra-info lines. Fixes bug 7011; patch by David Fifield.
1441 o Code refactoring and cleanup:
1442 - Source files taken from other packages now reside in src/ext;
1443 previously they were scattered around the rest of Tor.
1444 - Avoid use of reserved identifiers in our C code. The C standard
1445 doesn't like us declaring anything that starts with an
1446 underscore, so let's knock it off before we get in trouble. Fix
1447 for bug 1031; bugfix on the first Tor commit.
1450 Changes in version 0.2.3.23-rc - 2012-10-20
1451 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
1452 vulnerability introduced by a change in OpenSSL, and fixes a variety
1453 of smaller bugs in preparation for the release.
1455 o New directory authorities:
1456 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1457 authority. Closes ticket 5749.
1459 o Major bugfixes (security/privacy):
1460 - Disable TLS session tickets. OpenSSL's implementation was giving
1461 our TLS session keys the lifetime of our TLS context objects, when
1462 perfect forward secrecy would want us to discard anything that
1463 could decrypt a link connection as soon as the link connection
1464 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1465 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1466 - Discard extraneous renegotiation attempts once the V3 link
1467 protocol has been initiated. Failure to do so left us open to
1468 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1469 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1472 - Fix a possible crash bug when checking for deactivated circuits
1473 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1474 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1476 o Minor bugfixes (on 0.2.3.x):
1477 - Fix two cases in src/or/transports.c where we were calling
1478 fmt_addr() twice in a parameter list. Bug found by David
1479 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1480 - Convert an assert in the pathbias code to a log message. The assert
1481 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1482 bugfix on 0.2.3.17-beta.
1483 - Fix memory leaks whenever we logged any message about the "path
1484 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1486 o Minor bugfixes (on 0.2.2.x and earlier):
1487 - Don't serve or accept v2 hidden service descriptors over a relay's
1488 DirPort. It's never correct to do so, and disabling it might
1489 make it more annoying to exploit any bugs that turn up in the
1490 descriptor-parsing code. Fixes bug 7149.
1491 - When relays refuse a "create" cell because their queue of pending
1492 create cells is too big (typically because their cpu can't keep up
1493 with the arrival rate), send back reason "resource limit" rather
1494 than reason "internal", so network measurement scripts can get a
1495 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
1496 - Correct file sizes when reading binary files on Cygwin, to avoid
1497 a bug where Tor would fail to read its state file. Fixes bug 6844;
1498 bugfix on 0.1.2.7-alpha.
1499 - Avoid undefined behaviour when parsing the list of supported
1500 rendezvous/introduction protocols in a hidden service descriptor.
1501 Previously, Tor would have confused (as-yet-unused) protocol version
1502 numbers greater than 32 with lower ones on many platforms. Fixes
1503 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1505 o Documentation fixes:
1506 - Clarify that hidden services are TCP only. Fixes bug 6024.
1509 Changes in version 0.2.4.3-alpha - 2012-09-22
1510 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
1511 assertion, resumes letting relays test reachability of their DirPort,
1512 and cleans up a bunch of smaller bugs.
1515 - Fix an assertion failure in tor_timegm() that could be triggered
1516 by a badly formatted directory object. Bug found by fuzzing with
1517 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1520 - Fix a possible crash bug when checking for deactivated circuits
1521 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1522 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1523 - Allow routers to detect that their own DirPorts are running. When
1524 we removed support for versions_supports_begindir, we also
1525 accidentally removed the mechanism we used to self-test our
1526 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
1527 bugfix on 0.2.4.2-alpha.
1529 o Security features:
1530 - Switch to a completely time-invariant approach for picking nodes
1531 weighted by bandwidth. Our old approach would run through the
1532 part of the loop after it had made its choice slightly slower
1533 than it ran through the part of the loop before it had made its
1534 choice. Addresses ticket 6538.
1535 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
1536 by tor2web clients allows hidden services to identify tor2web
1537 clients through their repeated selection of the same rendezvous
1538 and introduction point circuit endpoints (their guards). Resolves
1542 - Enable Tor to read configuration, state, and key information from
1543 a FIFO. Previously Tor would only read from files with a positive
1544 stat.st_size. Code from meejah; fixes bug 6044.
1547 - Correct file sizes when reading binary files on Cygwin, to avoid
1548 a bug where Tor would fail to read its state file. Fixes bug 6844;
1549 bugfix on 0.1.2.7-alpha.
1550 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
1551 bugfix on 0.2.0.3-alpha.
1552 - When complaining about a client port on a public address, log
1553 which address we're complaining about. Fixes bug 4020; bugfix on
1554 0.2.3.3-alpha. Patch by Tom Fitzhenry.
1555 - Convert an assert in the pathbias code to a log message. The assert
1556 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1557 bugfix on 0.2.3.17-beta.
1558 - Our new buildsystem was overzealous about rebuilding manpages: it
1559 would rebuild them all whenever any one of them changed. Now our
1560 dependency checking should be correct. Fixes bug 6843; bugfix on
1562 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
1563 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
1564 - Correct log printout about which address family is preferred
1565 when connecting to a bridge with both an IPv4 and IPv6 OR port.
1566 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
1568 o Minor bugfixes (code cleanliness):
1569 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
1570 with large values. This situation was untriggered, but nevertheless
1571 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
1572 - Reject consensus votes with more than 64 known-flags. We aren't even
1573 close to that limit yet, and our code doesn't handle it correctly.
1574 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
1575 - Avoid undefined behaviour when parsing the list of supported
1576 rendezvous/introduction protocols in a hidden service descriptor.
1577 Previously, Tor would have confused (as-yet-unused) protocol version
1578 numbers greater than 32 with lower ones on many platforms. Fixes
1579 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1580 - Fix handling of rendezvous client authorization types over 8.
1581 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
1582 - Fix building with older versions of GCC (2.95, for one) that don't
1583 like preprocessor directives inside macro arguments. Found by
1584 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
1585 - Switch weighted node selection rule from using a list of doubles
1586 to using a list of int64_t. This change should make the process
1587 slightly easier to debug and maintain. Needed to finish ticket 6538.
1589 o Code simplification and refactoring:
1590 - Move the generic "config" code into a new file, and have "config.c"
1591 hold only torrc- and state-related code. Resolves ticket 6823.
1592 - Move the core of our "choose a weighted element at random" logic
1593 into its own function, and give it unit tests. Now the logic is
1594 testable, and a little less fragile too.
1595 - Removed the testing_since field of node_t, which hasn't been used
1596 for anything since 0.2.0.9-alpha.
1598 o Documentation fixes:
1599 - Clarify that hidden services are TCP only. Fixes bug 6024.
1600 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
1604 Changes in version 0.2.3.22-rc - 2012-09-11
1605 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
1609 - Fix an assertion failure in tor_timegm() that could be triggered
1610 by a badly formatted directory object. Bug found by fuzzing with
1611 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1614 - Avoid segfault when starting up having run with an extremely old
1615 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1619 Changes in version 0.2.2.39 - 2012-09-11
1620 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
1624 - Fix an assertion failure in tor_timegm() that could be triggered
1625 by a badly formatted directory object. Bug found by fuzzing with
1626 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1627 - Do not crash when comparing an address with port value 0 to an
1628 address policy. This bug could have been used to cause a remote
1629 assertion failure by or against directory authorities, or to
1630 allow some applications to crash clients. Fixes bug 6690; bugfix
1634 Changes in version 0.2.4.2-alpha - 2012-09-10
1635 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
1636 raises the default rate limiting even more, and makes the bootstrapping
1637 log messages less noisy.
1640 - Automatically forward the TCP ports of pluggable transport
1641 proxies using tor-fw-helper if PortForwarding is enabled. Implements
1645 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
1646 to 1GB/1GB. The previous defaults were intended to be "basically
1647 infinite", but it turns out they're now limiting our 100mbit+
1648 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
1649 last time we raised it).
1652 - Detect when we're running with a version of OpenSSL other than the
1653 one we compiled with. This has occasionally given people hard-to-
1655 - Log fewer lines at level "notice" about our OpenSSL and Libevent
1656 versions and capabilities when everything is going right. Resolves
1657 part of ticket 6736.
1658 - Directory authorities no long accept descriptors for any version of
1659 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
1660 These versions are insecure, unsupported, or both. Implements
1664 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
1665 to start with a triple-underscore so the controller won't touch it.
1666 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
1667 - Avoid segfault when starting up having run with an extremely old
1668 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1670 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
1671 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
1672 - Don't follow the NULL pointer if microdescriptor generation fails.
1673 (This does not appear to be triggerable, but it's best to be safe.)
1674 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
1675 - Fix mis-declared dependencies on src/common/crypto.c and
1676 src/or/tor_main.c that could break out-of-tree builds under some
1677 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
1678 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
1679 6778; bugfix on 0.2.4.1-alpha.
1680 - Fix a harmless (in this case) build warning for implicitly
1681 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
1684 - Now that all versions before 0.2.2.x are disallowed, we no longer
1685 need to work around their missing features. Thus we can remove a
1686 bunch of compatibility code.
1689 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
1690 TCP ports to forward. In the past it only accepted two ports:
1691 the ORPort and the DirPort.
1694 Changes in version 0.2.4.1-alpha - 2012-09-05
1695 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
1696 bridgedb; lets relays use IPv6 addresses and directory authorities
1697 advertise them; and switches to a cleaner build interface.
1699 This is the first alpha release in a new series, so expect there to
1700 be bugs. Users who would rather test out a more stable branch should
1701 stay with 0.2.3.x for now.
1703 o Major features (bridges):
1704 - Bridges now report the pluggable transports they support to the
1705 bridge authority, so it can pass the supported transports on to
1706 bridgedb and/or eventually do reachability testing. Implements
1709 o Major features (IPv6):
1710 - Bridge authorities now accept IPv6 bridge addresses and include
1711 them in network status documents. Implements ticket 5534.
1712 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
1713 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
1714 to happen. Implements ticket 5535.
1715 - All kind of relays, not just bridges, can now advertise an IPv6
1716 OR port. Implements ticket 6362.
1717 - Directory authorities vote on IPv6 OR ports using the new consensus
1718 method 14. Implements ticket 6363.
1720 o Major features (build):
1721 - Switch to a nonrecursive Makefile structure. Now instead of each
1722 Makefile.am invoking other Makefile.am's, there is a master
1723 Makefile.am that includes the others. This change makes our build
1724 process slightly more maintainable, and improves parallelism for
1725 building with make -j. Original patch by Stewart Smith; various
1726 fixes by Jim Meyering.
1727 - Where available, we now use automake's "silent" make rules by
1728 default, so that warnings are easier to spot. You can get the old
1729 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
1731 o Minor features (code security and spec conformance):
1732 - Clear keys and key-derived material left on the stack in
1733 rendservice.c and rendclient.c. Check return value of
1734 crypto_pk_write_private_key_to_string() in end_service_load_keys().
1735 These fixes should make us more forward-secure against cold-boot
1736 attacks and the like. Fixes bug 2385.
1737 - Reject EXTEND cells sent to nonexistent streams. According to the
1738 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
1739 we were only checking for stream IDs that were currently in use.
1740 Found while hunting for more instances of bug 6271. Bugfix on
1741 0.0.2pre8, which introduced incremental circuit construction.
1743 o Minor features (streamlining);
1744 - No longer include the "opt" prefix when generating routerinfos
1745 or v2 directories: it has been needless since Tor 0.1.2. Closes
1747 - Remove some now-needless code that tried to aggressively flush
1748 OR connections as data was added to them. Since 0.2.0.1-alpha, our
1749 cell queue logic has saved us from the failure mode that this code
1750 was supposed to prevent. Removing this code will limit the number
1751 of baroque control flow paths through Tor's network logic. Reported
1752 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
1754 o Minor features (controller):
1755 - Add a "GETINFO signal/names" control port command. Implements
1757 - Provide default values for all options via "GETINFO config/defaults".
1758 Implements ticket 4971.
1760 o Minor features (IPv6):
1761 - New config option "AuthDirHasIPv6Connectivity 1" that directory
1762 authorities should set if they have IPv6 connectivity and want to
1763 do reachability tests for IPv6 relays. Implements feature 5974.
1764 - A relay with an IPv6 OR port now sends that address in NETINFO
1765 cells (in addition to its other address). Implements ticket 6364.
1767 o Minor features (log messages):
1768 - Omit the first heartbeat log message, because it never has anything
1769 useful to say, and it clutters up the bootstrapping messages.
1770 Resolves ticket 6758.
1771 - Don't log about reloading the microdescriptor cache at startup. Our
1772 bootstrap warnings are supposed to tell the user when there's a
1773 problem, and our bootstrap notices say when there isn't. Resolves
1774 ticket 6759; bugfix on 0.2.2.6-alpha.
1775 - Don't log "I learned some more directory information" when we're
1776 reading cached directory information. Reserve it for when new
1777 directory information arrives in response to a fetch. Resolves
1779 - Prevent rounding error in path bias counts when scaling
1780 them down, and use the correct scale factor default. Also demote
1781 some path bias related log messages down a level and make others
1782 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
1783 - We no longer warn so much when generating manpages from their
1786 o Code simplifications and refactoring:
1787 - Enhance our internal sscanf replacement so that we can eliminate
1788 the last remaining uses of the system sscanf. (Though those uses
1789 of sscanf were safe, sscanf itself is generally error prone, so
1790 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
1792 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
1793 - Move last_reachable and testing_since from routerinfo_t to node_t.
1794 Implements ticket 5529.
1795 - Add replaycache_t structure, functions and unit tests, then refactor
1796 rend_service_introduce() to be more clear to read, improve, debug,
1797 and test. Resolves bug 6177.
1798 - Finally remove support for malloc_good_size and malloc_usable_size.
1799 We had hoped that these functions would let us eke a little more
1800 memory out of our malloc implementation. Unfortunately, the only
1801 implementations that provided these functions are also ones that
1802 are already efficient about not overallocation: they never got us
1803 more than 7 or so bytes per allocation. Removing them saves us a
1804 little code complexity and a nontrivial amount of build complexity.
1807 - Tor maintainers now require Automake version 1.9 or later to build
1808 Tor from the Git repository. (Automake is not required when building
1809 from a source distribution.)
1812 Changes in version 0.2.3.21-rc - 2012-09-05
1813 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
1814 series. It fixes a trio of potential security bugs, fixes a bug where
1815 we were leaving some of the fast relays out of the microdescriptor
1816 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
1817 and cleans up other smaller issues.
1819 o Major bugfixes (security):
1820 - Tear down the circuit if we get an unexpected SENDME cell. Clients
1821 could use this trick to make their circuits receive cells faster
1822 than our flow control would have allowed, or to gum up the network,
1823 or possibly to do targeted memory denial-of-service attacks on
1824 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
1825 from July 2002, before the release of Tor 0.0.0. We had committed
1826 this patch previously, but we had to revert it because of bug 6271.
1827 Now that 6271 is fixed, this patch appears to work.
1828 - Reject any attempt to extend to an internal address. Without
1829 this fix, a router could be used to probe addresses on an internal
1830 network to see whether they were accepting connections. Fixes bug
1831 6710; bugfix on 0.0.8pre1.
1832 - Do not crash when comparing an address with port value 0 to an
1833 address policy. This bug could have been used to cause a remote
1834 assertion failure by or against directory authorities, or to
1835 allow some applications to crash clients. Fixes bug 6690; bugfix
1839 - Remove the upper bound on microdescriptor length. We were hitting
1840 the limit for routers with complex exit policies or family
1841 declarations, causing clients to not use them. Fixes the first
1842 piece of bug 6404; fix on 0.2.2.6-alpha.
1843 - Detect "ORPort 0" as meaning, uniformly, that we're not running
1844 as a relay. Previously, some of our code would treat the presence
1845 of any ORPort line as meaning that we should act like a relay,
1846 even though our new listener code would correctly not open any
1847 ORPorts for ORPort 0. Similar bugs in other Port options are also
1848 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
1851 - Avoid a pair of double-free and use-after-mark bugs that can
1852 occur with certain timings in canceled and re-received DNS
1853 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
1854 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
1855 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
1856 - Allow one-hop directory fetching circuits the full "circuit build
1857 timeout" period, rather than just half of it, before failing them
1858 and marking the relay down. This fix should help reduce cases where
1859 clients declare relays (or worse, bridges) unreachable because
1860 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
1861 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
1863 - Authorities no longer include any router in their microdescriptor
1864 consensuses for which they couldn't generate or agree on a
1865 microdescriptor. Fixes the second piece of bug 6404; fix on
1867 - Detect and reject attempts to specify both "FooPort" and
1868 "FooPort 0" in the same configuration domain. (It's still okay
1869 to have a FooPort in your configuration file, and use "FooPort 0"
1870 on the command line to disable it.) Fixes the second half of bug
1871 6507; bugfix on 0.2.3.3-alpha.
1872 - Make wildcarded addresses (that is, ones beginning with "*.") work
1873 when provided via the controller's MapAddress command. Previously,
1874 they were accepted, but we never actually noticed that they were
1875 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
1876 - Avoid crashing on a malformed state file where EntryGuardPathBias
1877 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
1878 - Add a (probably redundant) memory clear between iterations of
1879 the router status voting loop, to prevent future coding errors
1880 where data might leak between iterations of the loop. Resolves
1883 o Minor bugfixes (log messages):
1884 - Downgrade "set buildtimeout to low value" messages to "info"
1885 severity; they were never an actual problem, there was never
1886 anything reasonable to do about them, and they tended to spam logs
1887 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
1888 - Downgrade path-bias warning messages to "info". We'll try to get
1889 them working better in 0.2.4. Add internal circuit construction
1890 state to protect against the noisy warn message "Unexpectedly high
1891 circuit_successes". Also add some additional rate-limited notice
1892 messages to help determine the root cause of the warn. Fixes bug
1893 6475. Bugfix against 0.2.3.17-beta.
1894 - Move log message when unable to find a microdesc in a routerstatus
1895 entry to parse time. Previously we'd spam this warning every time
1896 we tried to figure out which microdescriptors to download. Fixes
1897 the third piece of bug 6404; fix on 0.2.3.18-rc.
1900 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
1901 change when the authority is deciding whether to accept a newly
1902 uploaded descriptor. Implements ticket 6423.
1903 - Add missing documentation for consensus and microdesc files.
1904 Resolves ticket 6732.
1907 Changes in version 0.2.2.38 - 2012-08-12
1908 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
1909 attack that could in theory leak path information.
1912 - Avoid an uninitialized memory read when reading a vote or consensus
1913 document that has an unrecognized flavor name. This read could
1914 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1915 - Try to leak less information about what relays a client is
1916 choosing to a side-channel attacker. Previously, a Tor client would
1917 stop iterating through the list of available relays as soon as it
1918 had chosen one, thus finishing a little earlier when it picked
1919 a router earlier in the list. If an attacker can recover this
1920 timing information (nontrivial but not proven to be impossible),
1921 they could learn some coarse-grained information about which relays
1922 a client was picking (middle nodes in particular are likelier to
1923 be affected than exits). The timing attack might be mitigated by
1924 other factors (see bug 6537 for some discussion), but it's best
1925 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
1928 Changes in version 0.2.3.20-rc - 2012-08-05
1929 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
1930 series. It fixes a pair of code security bugs and a potential anonymity
1931 issue, updates our RPM spec files, and cleans up other smaller issues.
1934 - Avoid read-from-freed-memory and double-free bugs that could occur
1935 when a DNS request fails while launching it. Fixes bug 6480;
1936 bugfix on 0.2.0.1-alpha.
1937 - Avoid an uninitialized memory read when reading a vote or consensus
1938 document that has an unrecognized flavor name. This read could
1939 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1940 - Try to leak less information about what relays a client is
1941 choosing to a side-channel attacker. Previously, a Tor client would
1942 stop iterating through the list of available relays as soon as it
1943 had chosen one, thus finishing a little earlier when it picked
1944 a router earlier in the list. If an attacker can recover this
1945 timing information (nontrivial but not proven to be impossible),
1946 they could learn some coarse-grained information about which relays
1947 a client was picking (middle nodes in particular are likelier to
1948 be affected than exits). The timing attack might be mitigated by
1949 other factors (see bug 6537 for some discussion), but it's best
1950 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
1953 - Try to make the warning when giving an obsolete SOCKSListenAddress
1954 a little more useful.
1955 - Terminate active server managed proxies if Tor stops being a
1956 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
1957 - Provide a better error message about possible OSX Asciidoc failure
1958 reasons. Fixes bug 6436.
1959 - Warn when Tor is configured to use accounting in a way that can
1960 link a hidden service to some other hidden service or public
1961 address. Resolves ticket 6490.
1964 - Check return value of fputs() when writing authority certificate
1965 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
1966 - Ignore ServerTransportPlugin lines when Tor is not configured as
1967 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
1968 - When disabling guards for having too high a proportion of failed
1969 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
1973 - Update our default RPM spec files to work with mock and rpmbuild
1974 on RHEL/Fedora. They have an updated set of dependencies and
1975 conflicts, a fix for an ancient typo when creating the "_tor"
1976 user, and better instructions. Thanks to Ondrej Mikle for the
1977 patch series. Fixes bug 6043.
1980 - Make it possible to set the TestingTorNetwork configuration
1981 option using AlternateDirAuthority and AlternateBridgeAuthority
1982 as an alternative to setting DirServer. Addresses ticket 6377.
1985 - Clarify the documentation for the Alternate*Authority options.
1987 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
1989 o Code simplification and refactoring:
1990 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
1991 10 lines. Also, don't nest them. Doing so in the past has
1992 led to hard-to-debug code. The new style is to use the
1993 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
1996 Changes in version 0.2.3.19-rc - 2012-07-06
1997 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
1998 series. It fixes the compile on Windows, reverts to a GeoIP database
1999 that isn't as broken, and fixes a flow control bug that has been around
2000 since the beginning of Tor.
2003 - Fix a bug handling SENDME cells on nonexistent streams that could
2004 result in bizarre window values. Report and patch contributed
2005 pseudonymously. Fixes part of bug 6271. This bug was introduced
2006 before the first Tor release, in svn commit r152.
2007 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
2008 June 2012 database, Maxmind marked many Tor relays as country "A1",
2009 which will cause risky behavior for clients that set EntryNodes
2010 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
2011 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
2012 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
2015 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
2016 bugfix on 0.2.1.10-alpha.
2019 Changes in version 0.2.3.18-rc - 2012-06-28
2020 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
2021 series. It fixes a few smaller bugs, but generally appears stable.
2022 Please test it and let us know whether it is!
2025 - Allow wildcarded mapaddress targets to be specified on the
2026 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
2027 - Make our linker option detection code more robust against linkers
2028 such as on FreeBSD 8, where a bad combination of options completes
2029 successfully but makes an unrunnable binary. Fixes bug 6173;
2030 bugfix on 0.2.3.17-beta.
2032 o Minor bugfixes (on 0.2.2.x and earlier):
2033 - Avoid a false positive in the util/threads unit test by increasing
2034 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
2035 - Replace "Sending publish request" log messages with "Launching
2036 upload", so that they no longer confusingly imply that we're
2037 sending something to a directory we might not even be connected
2038 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
2039 - Make sure to set *socket_error in all error cases in
2040 connection_connect(), so it can't produce a warning about
2041 errno being zero from errno_to_orconn_end_reason(). Bugfix on
2042 0.2.1.1-alpha; resolves ticket 6028.
2043 - Downgrade "Got a certificate, but we already have it" log messages
2044 from warning to info, except when we're a dirauth. Fixes bug 5238;
2045 bugfix on 0.2.1.7-alpha.
2046 - When checking for requested signatures on the latest consensus
2047 before serving it to a client, make sure to check the right
2048 consensus flavor. Bugfix on 0.2.2.6-alpha.
2049 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
2050 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
2052 o Minor bugfixes (on 0.2.3.x):
2053 - Make format_helper_exit_status() avoid unnecessary space padding
2054 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
2056 - Downgrade a message about cleaning the microdescriptor cache to
2057 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
2058 - Log a BUG message at severity INFO if we have a networkstatus with
2059 a missing entry for some microdescriptor. Continues on a patch
2061 - Improve the log message when a managed proxy fails to launch. Fixes
2062 bug 5099; bugfix on 0.2.3.6-alpha.
2063 - Don't do DNS lookups when parsing corrupted managed proxy protocol
2064 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
2065 - When formatting wildcarded address mappings for the controller,
2066 be sure to include "*." as appropriate. Partially fixes bug 6244;
2067 bugfix on 0.2.3.9-alpha.
2068 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
2069 Bugfix on 0.2.3.13-alpha.
2070 - Stop logging messages about running with circuit timeout learning
2071 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
2072 - Disable a spurious warning about reading on a marked and flushing
2073 connection. We shouldn't be doing that, but apparently we
2074 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
2075 - Fix a bug that stopped AllowDotExit from working on addresses
2076 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
2079 o Code simplification, refactoring, unit tests:
2080 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
2081 Libevent's notion of cached time when possible.
2082 - Remove duplicate code for invoking getrlimit() from control.c.
2083 - Add a unit test for the environment_variable_names_equal function.
2086 - Document the --defaults-torrc option, and the new (in 0.2.3)
2087 semantics for overriding, extending, and clearing lists of
2088 options. Closes bug 4748.
2091 Changes in version 0.2.3.17-beta - 2012-06-15
2092 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
2093 gets our TLS handshake back on track for being able to blend in with
2094 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
2095 with Vidalia, and otherwise continues to get us closer to a release
2099 - Enable gcc and ld hardening by default. Resolves ticket 5210.
2100 - Update TLS cipher list to match Firefox 8 and later. Resolves
2102 - Implement the client side of proposal 198: remove support for
2103 clients falsely claiming to support standard ciphersuites that
2104 they can actually provide. As of modern OpenSSL versions, it's not
2105 necessary to fake any standard ciphersuite, and doing so prevents
2106 us from using better ciphersuites in the future, since servers
2107 can't know whether an advertised ciphersuite is really supported or
2108 not. Some hosts -- notably, ones with very old versions of OpenSSL
2109 or where OpenSSL has been built with ECC disabled -- will stand
2110 out because of this change; TBB users should not be affected.
2113 - Change the default value for DynamicDHGroups (introduced in
2114 0.2.3.9-alpha) to 0. This feature can make Tor relays less
2115 identifiable by their use of the mod_ssl DH group, but at
2116 the cost of some usability (#4721) and bridge tracing (#6087)
2117 regressions. Resolves ticket 5598.
2118 - Send a CRLF at the end of each STATUS_* control protocol event. This
2119 bug tickled a bug in Vidalia which would make it freeze. Fixes
2120 bug 6094; bugfix on 0.2.3.16-alpha.
2123 - Disable writing on marked-for-close connections when they are
2124 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
2125 bug 5263; bugfix on 0.0.2pre13, where we first added a special
2126 case for flushing marked connections.
2127 - Detect SSL handshake even when the initial attempt to write the
2128 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
2129 - Change the AllowDotExit rules so they should actually work.
2130 We now enforce AllowDotExit only immediately after receiving an
2131 address via SOCKS or DNSPort: other sources are free to provide
2132 .exit addresses after the resolution occurs. Fixes bug 3940;
2133 bugfix on 0.2.2.1-alpha.
2134 - Fix a (harmless) integer overflow in cell statistics reported by
2135 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
2136 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
2137 right places and never depends on the consensus parameters or
2138 computes adaptive timeouts when it is disabled. Fixes bug 5049;
2139 bugfix on 0.2.2.14-alpha.
2140 - When building Tor on Windows with -DUNICODE (not default), ensure
2141 that error messages, filenames, and DNS server names are always
2142 NUL-terminated when we convert them to a single-byte encoding.
2143 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
2144 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
2145 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
2146 - Fix an edge case where TestingTorNetwork is set but the authorities
2147 and relays all have an uptime of zero, where the private Tor network
2148 could briefly lack support for hidden services. Fixes bug 3886;
2149 bugfix on 0.2.2.18-alpha.
2150 - Correct the manpage's descriptions for the default values of
2151 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
2153 - Fix the documentation for the --hush and --quiet command line
2154 options, which changed their behavior back in 0.2.3.3-alpha.
2155 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
2159 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
2160 more information to it, so that we can track it down in case it
2161 returns again. Mitigates bug 5235.
2162 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
2163 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
2164 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
2165 - Warn the user when HTTPProxy, but no other proxy type, is
2166 configured. This can cause surprising behavior: it doesn't send
2167 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
2168 directory traffic only. Resolves ticket 4663.
2169 - Issue a notice if a guard completes less than 40% of your circuits.
2170 Threshold is configurable by torrc option PathBiasNoticeRate and
2171 consensus parameter pb_noticepct. There is additional, off-by-
2172 default code to disable guards which fail too many circuits.
2173 Addresses ticket 5458.
2174 - Update to the June 6 2012 Maxmind GeoLite Country database.
2176 o Code simplifications and refactoring:
2177 - Remove validate_pluggable_transports_config(): its warning
2178 message is now handled by connection_or_connect().
2181 Changes in version 0.2.2.37 - 2012-06-06
2182 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
2183 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2187 - Work around a bug in OpenSSL that broke renegotiation with TLS
2188 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2189 the v2 Tor connection protocol when both sides were using OpenSSL
2190 1.0.1 would fail. Resolves ticket 6033.
2191 - When waiting for a client to renegotiate, don't allow it to add
2192 any bytes to the input buffer. This fixes a potential DoS issue.
2193 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2194 - Fix an edge case where if we fetch or publish a hidden service
2195 descriptor, we might build a 4-hop circuit and then use that circuit
2196 for exiting afterwards -- even if the new last hop doesn't obey our
2197 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2200 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2201 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2204 - Tell GCC and Clang to check for any errors in format strings passed
2205 to the tor_v*(print|scan)f functions.
2208 Changes in version 0.2.3.16-alpha - 2012-06-05
2209 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
2210 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2211 currently). It also fixes a variety of smaller bugs and other cleanups
2212 that get us closer to a release candidate.
2214 o Major bugfixes (general):
2215 - Work around a bug in OpenSSL that broke renegotiation with TLS
2216 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2217 the v2 Tor connection protocol when both sides were using OpenSSL
2218 1.0.1 would fail. Resolves ticket 6033.
2219 - When waiting for a client to renegotiate, don't allow it to add
2220 any bytes to the input buffer. This fixes a potential DoS issue.
2221 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2222 - Pass correct OR address to managed proxies (like obfsproxy),
2223 even when ORListenAddress is used. Fixes bug 4865; bugfix on
2225 - The advertised platform of a router now includes only its operating
2226 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
2227 service pack level (for Windows) or its CPU architecture (for Unix).
2228 We also no longer include the "git-XYZ" tag in the version. Resolves
2231 o Major bugfixes (clients):
2232 - If we are unable to find any exit that supports our predicted ports,
2233 stop calling them predicted, so that we don't loop and build
2234 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
2235 which introduced predicted ports.
2236 - Fix an edge case where if we fetch or publish a hidden service
2237 descriptor, we might build a 4-hop circuit and then use that circuit
2238 for exiting afterwards -- even if the new last hop doesn't obey our
2239 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2240 - Check at each new consensus whether our entry guards were picked
2241 long enough ago that we should rotate them. Previously, we only
2242 did this check at startup, which could lead to us holding a guard
2243 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
2244 - When fetching a bridge descriptor from a bridge authority,
2245 always do so anonymously, whether we have been able to open
2246 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
2247 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
2248 but we'll need to wait for bug 6010 before it's actually usable.
2250 o Major bugfixes (directory authorities):
2251 - When computing weight parameters, behave more robustly in the
2252 presence of a bad bwweightscale value. Previously, the authorities
2253 would crash if they agreed on a sufficiently broken weight_scale
2254 value: now, they use a reasonable default and carry on. Partial
2255 fix for 5786; bugfix on 0.2.2.17-alpha.
2256 - Check more thoroughly to prevent a rogue authority from
2257 double-voting on any consensus directory parameter. Previously,
2258 authorities would crash in this case if the total number of
2259 votes for any parameter exceeded the number of active voters,
2260 but would let it pass otherwise. Partial fix for bug 5786; bugfix
2264 - Rate-limit log messages when asked to connect anonymously to
2265 a private address. When these hit, they tended to hit fast and
2266 often. Also, don't bother trying to connect to addresses that we
2267 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
2268 reply makes us think we have been lied to, even when the address the
2269 client tried to connect to was "localhost." Resolves ticket 2822.
2270 - Allow packagers to insert an extra string in server descriptor
2271 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
2272 Resolves the rest of ticket 2988.
2273 - Raise the threshold of server descriptors needed (75%) and exit
2274 server descriptors needed (50%) before we will declare ourselves
2275 bootstrapped. This will make clients start building circuits a
2276 little later, but makes the initially constructed circuits less
2277 skewed and less in conflict with further directory fetches. Fixes
2279 - Close any connection that sends unrecognized junk before the
2280 handshake. Solves an issue noted in bug 4369.
2281 - Improve log messages about managed transports. Resolves ticket 5070.
2282 - Tag a bridge's descriptor as "never to be sent unencrypted".
2283 This shouldn't matter, since bridges don't open non-anonymous
2284 connections to the bridge authority and don't allow unencrypted
2285 directory connections from clients, but we might as well make
2286 sure. Closes bug 5139.
2287 - Expose our view of whether we have gone dormant to the controller,
2288 via a new "GETINFO dormant" value. Torbutton and other controllers
2289 can use this to avoid doing periodic requests through Tor while
2290 it's dormant (bug 4718). Fixes bug 5954.
2291 - Tell GCC and Clang to check for any errors in format strings passed
2292 to the tor_v*(print|scan)f functions.
2293 - Update to the May 1 2012 Maxmind GeoLite Country database.
2295 o Minor bugfixes (already included in 0.2.2.36):
2296 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2297 Fixes bug 5346; bugfix on 0.0.8pre3.
2298 - Correct parsing of certain date types in parse_http_time().
2299 Without this patch, If-Modified-Since would behave
2300 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2301 Esteban Manchado Velázques.
2302 - Make our number-parsing functions always treat too-large values
2303 as an error, even when those values exceed the width of the
2304 underlying type. Previously, if the caller provided these
2305 functions with minima or maxima set to the extreme values of the
2306 underlying integer type, these functions would return those
2307 values on overflow rather than treating overflow as an error.
2308 Fixes part of bug 5786; bugfix on 0.0.9.
2309 - If we hit the error case where routerlist_insert() replaces an
2310 existing (old) server descriptor, make sure to remove that
2311 server descriptor from the old_routers list. Fix related to bug
2312 1776. Bugfix on 0.2.2.18-alpha.
2313 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2314 circuits. Fixes issue 5259.
2316 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
2317 - Prevent a null-pointer dereference when receiving a data cell
2318 for a nonexistent stream when the circuit in question has an
2319 empty deliver window. We don't believe this is triggerable,
2320 since we don't currently allow deliver windows to become empty,
2321 but the logic is tricky enough that it's better to make the code
2322 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
2323 - Fix a memory leak when trying to launch a DNS request when the
2324 network is disabled or the nameservers are unconfigurable. Fixes
2325 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
2326 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
2327 - Don't hold a Windows file handle open for every file mapping;
2328 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
2330 - Avoid O(n^2) performance characteristics when parsing a large
2331 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
2332 - Format more doubles with %f, not %lf. Patch from grarpamp to make
2333 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
2335 - Make our replacement implementation of strtok_r() compatible with
2336 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
2337 bugfix on 0.2.2.1-alpha.
2338 - Fix a NULL-pointer dereference on a badly formed
2339 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
2340 bugfix on 0.2.2.9-alpha.
2341 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2342 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2343 - Defensively refactor rend_mid_rendezvous() so that protocol
2344 violations and length checks happen in the beginning. Fixes
2346 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
2347 that IPv6 stuff will compile on MSVC, and compilation issues
2348 will be easier to track down. Fixes bug 5861.
2350 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
2351 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
2352 resource exhaustion, so that clients can adjust their load to
2353 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
2354 started using END_STREAM_REASON_RESOURCELIMIT.
2355 - Don't check for whether the address we're using for outbound
2356 connections has changed until after the outbound connection has
2357 completed. On Windows, getsockname() doesn't succeed until the
2358 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
2359 - If the configuration tries to set MyFamily on a bridge, refuse to
2360 do so, and warn about the security implications. Fixes bug 4657;
2361 bugfix on 0.2.0.3-alpha.
2362 - If the client fails to set a reasonable set of ciphersuites
2363 during its v2 handshake renegotiation, allow the renegotiation to
2364 continue nevertheless (i.e. send all the required certificates).
2365 Fixes bug 4591; bugfix on 0.2.0.20-rc.
2366 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
2367 option is set to 0 (which Vidalia version 0.2.16 now does when
2368 a SAVECONF attempt fails), perform other actions that SIGHUP
2369 usually causes (like reopening the logs). Fixes bug 5095; bugfix
2371 - If we fail to write a microdescriptor to the disk cache, do not
2372 continue replacing the old microdescriptor file. Fixes bug 2954;
2373 bugfix on 0.2.2.6-alpha.
2374 - Exit nodes don't need to fetch certificates for authorities that
2375 they don't recognize; only directory authorities, bridges,
2376 and caches need to do that. Fixes part of bug 2297; bugfix on
2378 - Correctly handle checking the permissions on the parent
2379 directory of a control socket in the root directory. Bug found
2380 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
2382 - When told to add a bridge with the same digest as a preexisting
2383 bridge but a different addr:port, change the addr:port as
2384 requested. Previously we would not notice the change. Fixes half
2385 of bug 5603; fix on 0.2.2.26-beta.
2386 - End AUTHCHALLENGE error messages (in the control protocol) with
2387 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
2389 o Minor bugfixes (on 0.2.3.x):
2390 - Turn an assertion (that the number of handshakes received as a
2391 server is not < 1) into a warning. Fixes bug 4873; bugfix on
2393 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
2394 we had reversed them when the answer was cached.) Fixes bug
2395 5723; bugfix on 0.2.3.1-alpha.
2396 - Work correctly on Linux systems with accept4 support advertised in
2397 their headers, but without accept4 support in the kernel. Fix
2398 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
2399 - When told to add a bridge with the same addr:port as a preexisting
2400 bridge but a different transport, change the transport as
2401 requested. Previously we would not notice the change. Fixes half
2402 of bug 5603; fix on 0.2.3.2-alpha.
2403 - Avoid a "double-reply" warning when replying to a SOCKS request
2404 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
2405 bugfix on 0.2.3.4-alpha.
2406 - Fix a bug where a bridge authority crashes if it has seen no
2407 directory requests when it's time to write statistics to disk.
2408 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
2410 - Don't try to open non-control listeners when DisableNetwork is set.
2411 Previously, we'd open all listeners, then immediately close them.
2412 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
2413 - Don't abort the managed proxy protocol if the managed proxy
2414 sends us an unrecognized line; ignore it instead. Fixes bug
2415 5910; bugfix on 0.2.3.9-alpha.
2416 - Fix a compile warning in crypto.c when compiling with clang 3.1.
2417 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
2418 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
2419 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
2420 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
2421 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
2422 - Resolve numerous small warnings and build issues with MSVC. Resolves
2425 o Documentation fixes:
2426 - Improve the manual's documentation for the NT Service command-line
2427 options. Addresses ticket 3964.
2428 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
2429 - Document the changes to the ORPort and DirPort options, and the
2430 fact that {OR/Dir}ListenAddress is now unnecessary (and
2431 therefore deprecated). Resolves ticket 5597.
2434 - Remove the torrc.bridge file: we don't use it for anything, and
2435 it had become badly desynchronized from torrc.sample. Resolves
2439 Changes in version 0.2.2.36 - 2012-05-24
2440 Tor 0.2.2.36 updates the addresses for two of the eight directory
2441 authorities, fixes some potential anonymity and security issues,
2442 and fixes several crash bugs.
2444 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
2445 known flaws, and nobody should be using them. You should upgrade. If
2446 you're using a Linux or BSD and its packages are obsolete, stop using
2447 those packages and upgrade anyway.
2449 o Directory authority changes:
2450 - Change IP address for maatuska (v3 directory authority).
2451 - Change IP address for ides (v3 directory authority), and rename
2455 - When building or running with any version of OpenSSL earlier
2456 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2457 versions have a bug (CVE-2011-4576) in which their block cipher
2458 padding includes uninitialized data, potentially leaking sensitive
2459 information to any peer with whom they make a SSLv3 connection. Tor
2460 does not use SSL v3 by default, but a hostile client or server
2461 could force an SSLv3 connection in order to gain information that
2462 they shouldn't have been able to get. The best solution here is to
2463 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2464 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2465 to make sure that the bug can't happen.
2466 - Never use a bridge or a controller-supplied node as an exit, even
2467 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2468 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2469 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2470 - Only build circuits if we have a sufficient threshold of the total
2471 descriptors that are marked in the consensus with the "Exit"
2472 flag. This mitigates an attack proposed by wanoskarnet, in which
2473 all of a client's bridges collude to restrict the exit nodes that
2474 the client knows about. Fixes bug 5343.
2475 - Provide controllers with a safer way to implement the cookie
2476 authentication mechanism. With the old method, if another locally
2477 running program could convince a controller that it was the Tor
2478 process, then that program could trick the controller into telling
2479 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2480 authentication method uses a challenge-response approach to prevent
2481 this attack. Fixes bug 5185; implements proposal 193.
2484 - Avoid logging uninitialized data when unable to decode a hidden
2485 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2486 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2487 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2489 - Fix builds when the path to sed, openssl, or sha1sum contains
2490 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2492 - Correct our replacements for the timeradd() and timersub() functions
2493 on platforms that lack them (for example, Windows). The timersub()
2494 function is used when expiring circuits, while timeradd() is
2495 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2496 bugfix on 0.2.2.24-alpha.
2497 - Fix the SOCKET_OK test that we use to tell when socket
2498 creation fails so that it works on Win64. Fixes part of bug 4533;
2499 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2502 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2503 Fixes bug 5346; bugfix on 0.0.8pre3.
2504 - Make our number-parsing functions always treat too-large values
2505 as an error, even when those values exceed the width of the
2506 underlying type. Previously, if the caller provided these
2507 functions with minima or maxima set to the extreme values of the
2508 underlying integer type, these functions would return those
2509 values on overflow rather than treating overflow as an error.
2510 Fixes part of bug 5786; bugfix on 0.0.9.
2511 - Older Linux kernels erroneously respond to strange nmap behavior
2512 by having accept() return successfully with a zero-length
2513 socket. When this happens, just close the connection. Previously,
2514 we would try harder to learn the remote address: but there was
2515 no such remote address to learn, and our method for trying to
2516 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2517 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2518 - Correct parsing of certain date types in parse_http_time().
2519 Without this patch, If-Modified-Since would behave
2520 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2521 Esteban Manchado Velázques.
2522 - Change the BridgePassword feature (part of the "bridge community"
2523 design, which is not yet implemented) to use a time-independent
2524 comparison. The old behavior might have allowed an adversary
2525 to use timing to guess the BridgePassword value. Fixes bug 5543;
2526 bugfix on 0.2.0.14-alpha.
2527 - Detect and reject certain misformed escape sequences in
2528 configuration values. Previously, these values would cause us
2529 to crash if received in a torrc file or over an authenticated
2530 control port. Bug found by Esteban Manchado Velázquez, and
2531 independently by Robert Connolly from Matta Consulting who further
2532 noted that it allows a post-authentication heap overflow. Patch
2533 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2534 bugfix on 0.2.0.16-alpha.
2535 - Fix a compile warning when using the --enable-openbsd-malloc
2536 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2537 - During configure, detect when we're building with clang version
2538 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2539 CFLAGS. clang doesn't support them yet.
2540 - When sending an HTTP/1.1 proxy request, include a Host header.
2541 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2542 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
2543 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
2544 - If we hit the error case where routerlist_insert() replaces an
2545 existing (old) server descriptor, make sure to remove that
2546 server descriptor from the old_routers list. Fix related to bug
2547 1776. Bugfix on 0.2.2.18-alpha.
2549 o Minor bugfixes (documentation and log messages):
2550 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2551 Fixes bug 4856; bugfix on Tor 0.0.6.
2552 - Update "ClientOnly" man page entry to explain that there isn't
2553 really any point to messing with it. Resolves ticket 5005.
2554 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2555 directory authority option (introduced in Tor 0.2.2.34).
2556 - Downgrade the "We're missing a certificate" message from notice
2557 to info: people kept mistaking it for a real problem, whereas it
2558 is seldom the problem even when we are failing to bootstrap. Fixes
2559 bug 5067; bugfix on 0.2.0.10-alpha.
2560 - Correctly spell "connect" in a log message on failure to create a
2561 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
2562 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2563 circuits. Fixes issue 5259.
2566 - Directory authorities now reject versions of Tor older than
2567 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2568 inclusive. These versions accounted for only a small fraction of
2569 the Tor network, and have numerous known security issues. Resolves
2571 - Update to the May 1 2012 Maxmind GeoLite Country database.
2574 - When sending or relaying a RELAY_EARLY cell, we used to convert
2575 it to a RELAY cell if the connection was using the v1 link
2576 protocol. This was a workaround for older versions of Tor, which
2577 didn't handle RELAY_EARLY cells properly. Now that all supported
2578 versions can handle RELAY_EARLY cells, and now that we're enforcing
2579 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2580 remove this workaround. Addresses bug 4786.
2583 Changes in version 0.2.3.15-alpha - 2012-04-30
2584 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
2585 the development branch build on Windows again.
2587 o Minor bugfixes (on 0.2.2.x and earlier):
2588 - Make sure that there are no unhandled pending TLS errors before
2589 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
2590 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
2591 Bugfix on 0.1.0.5-rc; fixes bug 4528.
2592 - Fix an assert that directory authorities could trigger on sighup
2593 during some configuration state transitions. We now don't treat
2594 it as a fatal error when the new descriptor we just generated in
2595 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
2596 - After we pick a directory mirror, we would refuse to use it if
2597 it's in our ExcludeExitNodes list, resulting in mysterious failures
2598 to bootstrap for people who just wanted to avoid exiting from
2599 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
2600 - When building with --enable-static-tor on OpenBSD, do not
2601 erroneously attempt to link -lrt. Fixes bug 5103.
2603 o Minor bugfixes (on 0.2.3.x):
2604 - When Tor is built with kernel headers from a recent (last few
2605 years) Linux kernel, do not fail to run on older (pre-2.6.28
2606 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
2607 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
2609 - Fix compilation with miniupnpc version 1.6; patch from
2610 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
2611 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
2612 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
2613 - Fix compilation on platforms without unistd.h, or where environ
2614 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
2617 - Directory authorities are now a little more lenient at accepting
2618 older router descriptors, or newer router descriptors that don't
2619 make big changes. This should help ameliorate past and future
2620 issues where routers think they have uploaded valid descriptors,
2621 but the authorities don't think so. Fix for ticket 2479.
2622 - Make the code that clients use to detect an address change be
2623 IPv6-aware, so that it won't fill clients' logs with error
2624 messages when trying to get the IPv4 address of an IPv6
2625 connection. Implements ticket 5537.
2628 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
2629 authorities needed to use it for a while to keep the network working
2630 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
2631 that was six months ago. As of now, it should no longer be needed
2635 Changes in version 0.2.3.14-alpha - 2012-04-23
2636 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
2637 candidate. It also dramatically speeds up AES: fast relays should
2638 consider switching to the newer OpenSSL library.
2640 o Directory authority changes:
2641 - Change IP address for ides (v3 directory authority), and rename
2645 - Avoid logging uninitialized data when unable to decode a hidden
2646 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2647 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2648 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2650 - If authorities are unable to get a v2 consensus document from other
2651 directory authorities, they no longer fall back to fetching
2652 them from regular directory caches. Fixes bug 5635; bugfix on
2653 0.2.2.26-beta, where routers stopped downloading v2 consensus
2655 - When we start a Tor client with a normal consensus already cached,
2656 be willing to download a microdescriptor consensus. Fixes bug 4011;
2657 fix on 0.2.3.1-alpha.
2659 o Major features (performance):
2660 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
2661 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
2662 vectorized AES implementations as appropriate. These can be much,
2663 much faster than other AES implementations.
2665 o Minor bugfixes (0.2.2.x and earlier):
2666 - Don't launch more than 10 service-side introduction-point circuits
2667 for a hidden service in five minutes. Previously, we would consider
2668 launching more introduction-point circuits if at least one second
2669 had passed without any introduction-point circuits failing. Fixes
2670 bug 4607; bugfix on 0.0.7pre1.
2671 - Change the BridgePassword feature (part of the "bridge community"
2672 design, which is not yet implemented) to use a time-independent
2673 comparison. The old behavior might have allowed an adversary
2674 to use timing to guess the BridgePassword value. Fixes bug 5543;
2675 bugfix on 0.2.0.14-alpha.
2676 - Enforce correct return behavior of tor_vsscanf() when the '%%'
2677 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
2678 - When sending an HTTP/1.1 proxy request, include a Host header.
2679 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2680 - Don't log that we have "decided to publish new relay descriptor"
2681 unless we are actually publishing a descriptor. Fixes bug 3942;
2682 bugfix on 0.2.2.28-beta.
2684 o Minor bugfixes (0.2.3.x):
2685 - Fix a bug where a bridge authority crashes (on a failed assert)
2686 if it has seen no directory requests when it's time to write
2687 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
2688 - Fix bug stomping on ORPort option NoListen and ignoring option
2689 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
2690 - In the testsuite, provide a large enough buffer in the tor_sscanf
2691 unit test. Otherwise we'd overrun that buffer and crash during
2692 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
2694 - Make sure we create the keys directory if it doesn't exist and we're
2695 about to store the dynamic Diffie-Hellman parameters. Fixes bug
2696 5572; bugfix on 0.2.3.13-alpha.
2697 - Fix a small memory leak when trying to decode incorrect base16
2698 authenticator during SAFECOOKIE authentication. Found by
2699 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
2702 - Add more information to a log statement that might help track down
2703 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
2704 non-IP address" messages (or any Bug messages, for that matter!),
2705 please let us know about it.
2706 - Relays now understand an IPv6 address when they get one from a
2707 directory server. Resolves ticket 4875.
2708 - Resolve IPv6 addresses in bridge and entry statistics to country
2709 code "??" which means we at least count them. Resolves ticket 5053;
2710 improves on 0.2.3.9-alpha.
2711 - Update to the April 3 2012 Maxmind GeoLite Country database.
2712 - Begin a doc/state-contents.txt file to explain the contents of
2713 the Tor state file. Fixes bug 2987.
2715 o Default torrc changes:
2716 - Stop listing "socksport 9050" in torrc.sample. We open a socks
2717 port on 9050 by default anyway, so this should not change anything
2719 - Stop mentioning the deprecated *ListenAddress options in
2720 torrc.sample. Fixes bug 5438.
2721 - Document unit of bandwidth related options in sample torrc.
2725 - The "torify" script no longer supports the "tsocks" socksifier
2726 tool, since tsocks doesn't support DNS and UDP right for Tor.
2727 Everyone should be using torsocks instead. Fixes bugs 3530 and
2728 5180. Based on a patch by "ugh".
2731 - Change the symmetric cipher interface so that creating and
2732 initializing a stream cipher are no longer separate functions.
2733 - Remove all internal support for unpadded RSA. We never used it, and
2734 it would be a bad idea to start.
2737 Changes in version 0.2.3.13-alpha - 2012-03-26
2738 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
2739 in managed pluggable transports, as well as providing other cleanups
2740 that get us closer to a release candidate.
2742 o Directory authority changes:
2743 - Change IP address for maatuska (v3 directory authority).
2746 - Provide controllers with a safer way to implement the cookie
2747 authentication mechanism. With the old method, if another locally
2748 running program could convince a controller that it was the Tor
2749 process, then that program could trick the controller into telling
2750 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2751 authentication method uses a challenge-response approach to prevent
2752 this attack. Fixes bug 5185, implements proposal 193.
2753 - Never use a bridge or a controller-supplied node as an exit, even
2754 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2755 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2756 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2757 - Only build circuits if we have a sufficient threshold of the total
2758 descriptors that are marked in the consensus with the "Exit"
2759 flag. This mitigates an attack proposed by wanoskarnet, in which
2760 all of a client's bridges collude to restrict the exit nodes that
2761 the client knows about. Fixes bug 5343.
2763 o Major bugfixes (on Tor 0.2.3.x):
2764 - Avoid an assert when managed proxies like obfsproxy are configured,
2765 and we receive HUP signals or setconf attempts too rapidly. This
2766 situation happens most commonly when Vidalia tries to attach to
2767 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
2768 bugfix on 0.2.3.6-alpha.
2769 - Fix a relay-side pluggable transports bug where managed proxies were
2770 unreachable from the Internet, because Tor asked them to bind on
2771 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
2772 - Stop discarding command-line arguments when TestingTorNetwork
2773 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
2774 0.2.3.9-alpha, where task 4552 added support for two layers of
2776 - Resume allowing the unit tests to run in gdb. This was accidentally
2777 made impossible when the DisableDebuggerAttachment option was
2778 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
2779 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
2780 0.2.3.11-alpha. Reported by Anthony G. Basile.
2782 o Minor bugfixes (on 0.2.2.x and earlier):
2783 - Ensure we don't cannibalize circuits that are longer than three hops
2784 already, so we don't end up making circuits with 5 or more
2785 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
2786 0.1.0.1-rc which introduced cannibalization.
2787 - Detect and reject certain misformed escape sequences in
2788 configuration values. Previously, these values would cause us
2789 to crash if received in a torrc file or over an authenticated
2790 control port. Bug found by Esteban Manchado Velázquez, and
2791 independently by Robert Connolly from Matta Consulting who further
2792 noted that it allows a post-authentication heap overflow. Patch
2793 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2794 bugfix on 0.2.0.16-alpha.
2795 - Fix a compile warning when using the --enable-openbsd-malloc
2796 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2797 - Directory caches no longer refuse to clean out descriptors because
2798 of missing v2 networkstatus documents, unless they're configured
2799 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
2800 0.2.2.26-beta. Patch by Daniel Bryg.
2801 - Update to the latest version of the tinytest unit testing framework.
2802 This includes a couple of bugfixes that can be relevant for
2803 running forked unit tests on Windows, and removes all reserved
2806 o Minor bugfixes (on 0.2.3.x):
2807 - On a failed pipe() call, don't leak file descriptors. Fixes bug
2808 4296; bugfix on 0.2.3.1-alpha.
2809 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
2810 until after we have received a CERTS cell. Fixes bug 4361; bugfix
2811 on 0.2.3.6-alpha. Patch by "frosty".
2812 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
2813 option, so that the IP stack doesn't decide to use it for IPv4
2814 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
2815 - Ensure that variables set in Tor's environment cannot override
2816 environment variables that Tor passes to a managed
2817 pluggable-transport proxy. Previously, Tor would pass every
2818 variable in its environment to managed proxies along with the new
2819 ones, in such a way that on many operating systems, the inherited
2820 environment variables would override those which Tor tried to
2821 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
2822 bugfix on 0.2.3.9-alpha for Windows.
2825 - A wide variety of new unit tests by Esteban Manchado Velázquez.
2826 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
2827 - Update to the March 6 2012 Maxmind GeoLite Country database.
2830 Changes in version 0.2.3.12-alpha - 2012-02-13
2831 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
2832 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
2833 when Tor is configured to use a pluggable transport like obfsproxy.
2836 - Fix builds when the path to sed, openssl, or sha1sum contains
2837 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2839 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
2840 connections. This change should allow busy exit relays to stop
2841 running out of available sockets as quickly. Fixes bug 4950;
2842 bugfix on 0.2.2.26-beta.
2843 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
2844 would ask the bridge for microdescriptors, which are only supported
2845 in 0.2.3.x, and then fail to bootstrap when it didn't get the
2846 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
2847 - Properly set up obfsproxy's environment when in managed mode. The
2848 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
2849 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
2850 5076 and 5082; bugfix on 0.2.3.6-alpha.
2853 - Use the dead_strip option when building Tor on OS X. This reduces
2854 binary size by almost 19% when linking openssl and libevent
2855 statically, which we do for Tor Browser Bundle.
2856 - Fix broken URLs in the sample torrc file, and tell readers about
2857 the OutboundBindAddress, ExitPolicyRejectPrivate, and
2858 PublishServerDescriptor options. Addresses bug 4652.
2859 - Update to the February 7 2012 Maxmind GeoLite Country database.
2862 - Downgrade the "We're missing a certificate" message from notice
2863 to info: people kept mistaking it for a real problem, whereas it
2864 is seldom the problem even when we are failing to bootstrap. Fixes
2865 bug 5067; bugfix on 0.2.0.10-alpha.
2866 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
2867 managed pluggable transport server proxy's environment.
2868 Previously, we would put it there, even though Tor doesn't
2869 implement an 'extended server port' yet, and even though Tor
2870 almost certainly isn't listening at that address. For now, we set
2871 it to an empty string to avoid crashing older obfsproxies. Bugfix
2873 - Log the heartbeat message every HeartbeatPeriod seconds, not every
2874 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
2875 0.2.3.1-alpha. Bug reported by Scott Bennett.
2876 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
2877 bugfix on 0.2.3.11-alpha.
2878 - Update "ClientOnly" man page entry to explain that there isn't
2879 really any point to messing with it. Resolves ticket 5005.
2880 - Use the correct CVE number for CVE-2011-4576 in our comments and
2881 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
2884 o Code simplifications and refactoring:
2885 - Use the _WIN32 macro throughout our code to detect Windows.
2886 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
2890 Changes in version 0.2.3.11-alpha - 2012-01-22
2891 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
2892 the last step of the plan to limit maximum circuit length, includes
2893 a wide variety of hidden service performance and correctness fixes,
2894 works around an OpenSSL security flaw if your distro is too stubborn
2895 to upgrade, and fixes a bunch of smaller issues.
2898 - Now that Tor 0.2.0.x is completely deprecated, enable the final
2899 part of "Proposal 110: Avoiding infinite length circuits" by
2900 refusing all circuit-extend requests that do not use a relay_early
2901 cell. This change helps Tor resist a class of denial-of-service
2902 attacks by limiting the maximum circuit length.
2903 - Adjust the number of introduction points that a hidden service
2904 will try to maintain based on how long its introduction points
2905 remain in use and how many introductions they handle. Fixes
2907 - Try to use system facilities for enumerating local interface
2908 addresses, before falling back to our old approach (which was
2909 binding a UDP socket, and calling getsockname() on it). That
2910 approach was scaring OS X users whose draconian firewall
2911 software warned about binding to UDP sockets, regardless of
2912 whether packets were sent. Now we try to use getifaddrs(),
2913 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
2914 system supports. Resolves ticket 1827.
2916 o Major security workaround:
2917 - When building or running with any version of OpenSSL earlier
2918 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2919 versions have a bug (CVE-2011-4576) in which their block cipher
2920 padding includes uninitialized data, potentially leaking sensitive
2921 information to any peer with whom they make a SSLv3 connection. Tor
2922 does not use SSL v3 by default, but a hostile client or server
2923 could force an SSLv3 connection in order to gain information that
2924 they shouldn't have been able to get. The best solution here is to
2925 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2926 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2927 to make sure that the bug can't happen.
2930 - Fix the SOCKET_OK test that we use to tell when socket
2931 creation fails so that it works on Win64. Fixes part of bug 4533;
2932 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2933 - Correct our replacements for the timeradd() and timersub() functions
2934 on platforms that lack them (for example, Windows). The timersub()
2935 function is used when expiring circuits, while timeradd() is
2936 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2937 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
2938 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
2939 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
2940 bug at runtime, not compile time, because some distributions hack
2941 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
2942 on 0.2.3.9-alpha. Found by Pascal.
2944 o Minor features (controller):
2945 - Use absolute path names when reporting the torrc filename in the
2946 control protocol, so a controller can more easily find the torrc
2947 file. Resolves bug 1101.
2948 - Extend the control protocol to report flags that control a circuit's
2949 path selection in CIRC events and in replies to 'GETINFO
2950 circuit-status'. Implements part of ticket 2411.
2951 - Extend the control protocol to report the hidden service address
2952 and current state of a hidden-service-related circuit in CIRC
2953 events and in replies to 'GETINFO circuit-status'. Implements part
2955 - When reporting the path to the cookie file to the controller,
2956 give an absolute path. Resolves ticket 4881.
2957 - Allow controllers to request an event notification whenever a
2958 circuit is cannibalized or its purpose is changed. Implements
2959 part of ticket 3457.
2960 - Include the creation time of a circuit in CIRC and CIRC2
2961 control-port events and the list produced by the 'GETINFO
2962 circuit-status' control-port command.
2964 o Minor features (directory authorities):
2965 - Directory authorities now reject versions of Tor older than
2966 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2967 inclusive. These versions accounted for only a small fraction of
2968 the Tor network, and have numerous known security issues. Resolves
2970 - Authority operators can now vote for all relays in a given
2971 set of countries to be BadDir/BadExit/Invalid/Rejected.
2972 - Provide two consensus parameters (FastFlagMinThreshold and
2973 FastFlagMaxThreshold) to control the range of allowable bandwidths
2974 for the Fast directory flag. These allow authorities to run
2975 experiments on appropriate requirements for being a "Fast" node.
2976 The AuthDirFastGuarantee config value still applies. Implements
2978 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2979 directory authority option (introduced in Tor 0.2.2.34).
2981 o Minor features (other):
2982 - Don't disable the DirPort when we cannot exceed our AccountingMax
2983 limit during this interval because the effective bandwidthrate is
2984 low enough. This is useful in a situation where AccountMax is only
2985 used as an additional safeguard or to provide statistics.
2986 - Prepend an informative header to generated dynamic_dh_params files.
2987 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
2988 EntryNodes will have no effect. Resolves issue 2571.
2989 - Log more useful messages when we fail to disable debugger
2991 - Log which authority we're missing votes from when we go to fetch
2992 them from the other auths.
2993 - Log (at debug level) whenever a circuit's purpose is changed.
2994 - Add missing documentation for the MaxClientCircuitsPending,
2995 UseMicrodescriptors, UserspaceIOCPBuffers, and
2996 _UseFilteringSSLBufferevents options, all introduced during
2998 - Update to the January 3 2012 Maxmind GeoLite Country database.
3000 o Minor bugfixes (hidden services):
3001 - Don't close hidden service client circuits which have almost
3002 finished connecting to their destination when they reach
3003 the normal circuit-build timeout. Previously, we would close
3004 introduction circuits which are waiting for an acknowledgement
3005 from the introduction point, and rendezvous circuits which have
3006 been specified in an INTRODUCE1 cell sent to a hidden service,
3007 after the normal CBT. Now, we mark them as 'timed out', and launch
3008 another rendezvous attempt in parallel. This behavior change can
3009 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
3010 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
3011 - Don't close hidden-service-side rendezvous circuits when they
3012 reach the normal circuit-build timeout. This behaviour change can
3013 be disabled using the new
3014 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
3015 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
3016 - Make sure we never mark the wrong rendezvous circuit as having
3017 had its introduction cell acknowleged by the introduction-point
3018 relay. Previously, when we received an INTRODUCE_ACK cell on a
3019 client-side hidden-service introduction circuit, we might have
3020 marked a rendezvous circuit other than the one we specified in
3021 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
3022 a warning message and interfered with the hidden service
3023 connection-establishment process. Fixes bug 4759; bugfix on
3024 0.2.3.3-alpha, when we added the stream-isolation feature which
3025 might cause Tor to open multiple rendezvous circuits for the same
3027 - Don't trigger an assertion failure when we mark a new client-side
3028 hidden-service introduction circuit for close during the process
3029 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
3032 o Minor bugfixes (log messages):
3033 - Correctly spell "connect" in a log message on failure to create a
3034 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
3036 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
3037 Fixes bug 4856; bugfix on Tor 0.0.6.
3038 - Fix the log message describing how we work around discovering
3039 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
3040 4837; bugfix on 0.2.2.9-alpha.
3041 - When logging about a disallowed .exit name, do not also call it
3042 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
3044 o Minor bugfixes (build fixes):
3045 - During configure, detect when we're building with clang version
3046 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
3047 CFLAGS. clang doesn't support them yet.
3048 - During configure, search for library containing cos function as
3049 libm lives in libcore on some platforms (BeOS/Haiku). Linking
3050 against libm was hard-coded before. Fixes the first part of bug
3051 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
3053 - Detect attempts to build Tor on (as yet hypothetical) versions
3054 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
3055 fix for bug 4533. Bugfix on 0.2.2.28-beta.
3056 - Preprocessor directives should not be put inside the arguments
3057 of a macro. This would break compilation with GCC releases prior
3058 to version 3.3. We would never recommend such an old GCC version,
3059 but it is apparently required for binary compatibility on some
3060 platforms (namely, certain builds of Haiku). Fixes the other part
3061 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
3064 o Minor bugfixes (other):
3065 - Older Linux kernels erroneously respond to strange nmap behavior
3066 by having accept() return successfully with a zero-length
3067 socket. When this happens, just close the connection. Previously,
3068 we would try harder to learn the remote address: but there was
3069 no such remote address to learn, and our method for trying to
3070 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
3071 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
3072 - Fix null-pointer access that could occur if TLS allocation failed.
3073 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
3074 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
3075 accidentally been reverted.
3076 - Fix our implementation of crypto_random_hostname() so it can't
3077 overflow on ridiculously large inputs. (No Tor version has ever
3078 provided this kind of bad inputs, but let's be correct in depth.)
3079 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
3080 - Find more places in the code that should have been testing for
3081 invalid sockets using the SOCKET_OK macro. Required for a fix
3082 for bug 4533. Bugfix on 0.2.2.28-beta.
3083 - Fix an assertion failure when, while running with bufferevents, a
3084 connection finishes connecting after it is marked for close, but
3085 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
3086 - test_util_spawn_background_ok() hardcoded the expected value
3087 for ENOENT to 2. This isn't portable as error numbers are
3088 platform specific, and particularly the hurd has ENOENT at
3089 0x40000002. Construct expected string at runtime, using the correct
3090 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
3091 - Reject attempts to disable DisableDebuggerAttachment while Tor is
3092 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
3093 - Use an appropriate-width type for sockets in tor-fw-helper on
3094 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
3097 - When sending or relaying a RELAY_EARLY cell, we used to convert
3098 it to a RELAY cell if the connection was using the v1 link
3099 protocol. This was a workaround for older versions of Tor, which
3100 didn't handle RELAY_EARLY cells properly. Now that all supported
3101 versions can handle RELAY_EARLY cells, and now that we're enforcing
3102 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
3103 remove this workaround. Addresses bug 4786.
3105 o Code simplifications and refactoring:
3106 - Use OpenSSL's built-in SSL_state_string_long() instead of our
3107 own homebrewed ssl_state_to_string() replacement. Patch from
3108 Emile Snyder. Fixes bug 4653.
3109 - Use macros to indicate OpenSSL versions, so we don't need to worry
3110 about accidental hexadecimal bit shifts.
3111 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
3113 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
3114 - Use the smartlist_add_asprintf() alias more consistently.
3115 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
3116 invalid value, rather than just -1.
3117 - Rename a handful of old identifiers, mostly related to crypto
3118 structures and crypto functions. By convention, our "create an
3119 object" functions are called "type_new()", our "free an object"
3120 functions are called "type_free()", and our types indicate that
3121 they are types only with a final "_t". But a handful of older
3122 types and functions broke these rules, with function names like
3123 "type_create" or "subsystem_op_type", or with type names like
3127 Changes in version 0.2.3.10-alpha - 2011-12-16
3128 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
3129 Tor's buffers code. Absolutely everybody should upgrade.
3131 The bug relied on an incorrect calculation when making data continuous
3132 in one of our IO buffers, if the first chunk of the buffer was
3133 misaligned by just the wrong amount. The miscalculation would allow an
3134 attacker to overflow a piece of heap-allocated memory. To mount this
3135 attack, the attacker would need to either open a SOCKS connection to
3136 Tor's SocksPort (usually restricted to localhost), or target a Tor
3137 instance configured to make its connections through a SOCKS proxy
3138 (which Tor does not do by default).
3140 Good security practice requires that all heap-overflow bugs should be
3141 presumed to be exploitable until proven otherwise, so we are treating
3142 this as a potential code execution attack. Please upgrade immediately!
3143 This bug does not affect bufferevents-based builds of Tor. Special
3144 thanks to "Vektor" for reporting this issue to us!
3146 This release also contains a few minor bugfixes for issues discovered
3150 - Fix a heap overflow bug that could occur when trying to pull
3151 data into the first chunk of a buffer, when that chunk had
3152 already had some data drained from it. Fixes CVE-2011-2778;
3153 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3156 - If we can't attach streams to a rendezvous circuit when we
3157 finish connecting to a hidden service, clear the rendezvous
3158 circuit's stream-isolation state and try to attach streams
3159 again. Previously, we cleared rendezvous circuits' isolation
3160 state either too early (if they were freshly built) or not at all
3161 (if they had been built earlier and were cannibalized). Bugfix on
3162 0.2.3.3-alpha; fixes bug 4655.
3163 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
3164 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
3165 - Fix an assertion failure when a relay with accounting enabled
3166 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
3169 - Update to the December 6 2011 Maxmind GeoLite Country database.
3172 Changes in version 0.2.2.35 - 2011-12-16
3173 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
3174 buffers code. Absolutely everybody should upgrade.
3176 The bug relied on an incorrect calculation when making data continuous
3177 in one of our IO buffers, if the first chunk of the buffer was
3178 misaligned by just the wrong amount. The miscalculation would allow an
3179 attacker to overflow a piece of heap-allocated memory. To mount this
3180 attack, the attacker would need to either open a SOCKS connection to
3181 Tor's SocksPort (usually restricted to localhost), or target a Tor
3182 instance configured to make its connections through a SOCKS proxy
3183 (which Tor does not do by default).
3185 Good security practice requires that all heap-overflow bugs should be
3186 presumed to be exploitable until proven otherwise, so we are treating
3187 this as a potential code execution attack. Please upgrade immediately!
3188 This bug does not affect bufferevents-based builds of Tor. Special
3189 thanks to "Vektor" for reporting this issue to us!
3191 Tor 0.2.2.35 also fixes several bugs in previous versions, including
3192 crash bugs for unusual configurations, and a long-term bug that
3193 would prevent Tor from starting on Windows machines with draconian
3196 With this release, we remind everyone that 0.2.0.x has reached its
3197 formal end-of-life. Those Tor versions have many known flaws, and
3198 nobody should be using them. You should upgrade -- ideally to the
3199 0.2.2.x series. If you're using a Linux or BSD and its packages are
3200 obsolete, stop using those packages and upgrade anyway.
3202 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
3203 longer receive support after some time in early 2012.
3206 - Fix a heap overflow bug that could occur when trying to pull
3207 data into the first chunk of a buffer, when that chunk had
3208 already had some data drained from it. Fixes CVE-2011-2778;
3209 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3210 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3211 that it doesn't attempt to allocate a socketpair. This could cause
3212 some problems on Windows systems with overzealous firewalls. Fix for
3213 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3215 - If we mark an OR connection for close based on a cell we process,
3216 don't process any further cells on it. We already avoid further
3217 reads on marked-for-close connections, but now we also discard the
3218 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3219 which was the first version where we might mark a connection for
3220 close based on processing a cell on it.
3221 - Correctly sanity-check that we don't underflow on a memory
3222 allocation (and then assert) for hidden service introduction
3223 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3224 bugfix on 0.2.1.5-alpha.
3225 - Fix a memory leak when we check whether a hidden service
3226 descriptor has any usable introduction points left. Fixes bug
3227 4424. Bugfix on 0.2.2.25-alpha.
3228 - Don't crash when we're running as a relay and don't have a GeoIP
3229 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
3230 we've had in the 0.2.3.x branch already.
3231 - When running as a client, do not print a misleading (and plain
3232 wrong) log message that we're collecting "directory request"
3233 statistics: clients don't collect statistics. Also don't create a
3234 useless (because empty) stats file in the stats/ directory. Fixes
3235 bug 4353; bugfix on 0.2.2.34.
3238 - Detect failure to initialize Libevent. This fix provides better
3239 detection for future instances of bug 4457.
3240 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3241 function. This was eating up hideously large amounts of time on some
3242 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3243 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3244 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3246 - Don't warn about unused log_mutex in log.c when building with
3247 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3248 0.1.0.6-rc which introduced --disable-threads.
3249 - When configuring, starting, or stopping an NT service, stop
3250 immediately after the service configuration attempt has succeeded
3251 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3252 - When sending a NETINFO cell, include the original address
3253 received for the other side, not its canonical address. Found
3254 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3255 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
3256 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3257 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3258 occurred when a client tried to fetch a descriptor for a bridge
3259 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3260 - Backport fixes for a pair of compilation warnings on Windows.
3261 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
3262 - If we had ever tried to call tor_addr_to_str on an address of
3263 unknown type, we would have done a strdup on an uninitialized
3264 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3265 Reported by "troll_un".
3266 - Correctly detect and handle transient lookup failures from
3267 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3268 Reported by "troll_un".
3269 - Fix null-pointer access that could occur if TLS allocation failed.
3270 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3271 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3272 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3275 - Add two new config options for directory authorities:
3276 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3277 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3278 that is always sufficient to satisfy the bandwidth requirement for
3279 the Guard flag. Now it will be easier for researchers to simulate
3280 Tor networks with different values. Resolves ticket 4484.
3281 - When Tor ignores a hidden service specified in its configuration,
3282 include the hidden service's directory in the warning message.
3283 Previously, we would only tell the user that some hidden service
3284 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3285 - Update to the December 6 2011 Maxmind GeoLite Country database.
3287 o Packaging changes:
3288 - Make it easier to automate expert package builds on Windows,
3289 by removing an absolute path from makensis.exe command.
3292 Changes in version 0.2.1.32 - 2011-12-16
3293 Tor 0.2.1.32 backports important security and privacy fixes for
3294 oldstable. This release is intended only for package maintainers and
3295 others who cannot use the 0.2.2 stable series. All others should be
3296 using Tor 0.2.2.x or newer.
3298 The Tor 0.2.1.x series will reach formal end-of-life some time in
3299 early 2012; we will stop releasing patches for it then.
3301 o Major bugfixes (also included in 0.2.2.x):
3302 - Correctly sanity-check that we don't underflow on a memory
3303 allocation (and then assert) for hidden service introduction
3304 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3305 bugfix on 0.2.1.5-alpha.
3306 - Fix a heap overflow bug that could occur when trying to pull
3307 data into the first chunk of a buffer, when that chunk had
3308 already had some data drained from it. Fixes CVE-2011-2778;
3309 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3312 - Update to the December 6 2011 Maxmind GeoLite Country database.
3315 Changes in version 0.2.3.9-alpha - 2011-12-08
3316 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
3317 a "DisableNetwork" security feature that bundles can use to avoid
3318 touching the network until bridges are configured, moves forward on
3319 the pluggable transport design, fixes a flaw in the hidden service
3320 design that unnecessarily prevented clients with wrong clocks from
3321 reaching hidden services, and fixes a wide variety of other issues.
3324 - Clients can now connect to private bridges over IPv6. Bridges
3325 still need at least one IPv4 address in order to connect to
3326 other relays. Note that we don't yet handle the case where the
3327 user has two bridge lines for the same bridge (one IPv4, one
3328 IPv6). Implements parts of proposal 186.
3329 - New "DisableNetwork" config option to prevent Tor from launching any
3330 connections or accepting any connections except on a control port.
3331 Bundles and controllers can set this option before letting Tor talk
3332 to the rest of the network, for example to prevent any connections
3333 to a non-bridge address. Packages like Orbot can also use this
3334 option to instruct Tor to save power when the network is off.
3335 - Clients and bridges can now be configured to use a separate
3336 "transport" proxy. This approach makes the censorship arms race
3337 easier by allowing bridges to use protocol obfuscation plugins. It
3338 implements the "managed proxy" part of proposal 180 (ticket 3472).
3339 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
3340 implementation. It makes AES_CTR about 7% faster than our old one
3341 (which was about 10% faster than the one OpenSSL used to provide).
3342 Resolves ticket 4526.
3343 - Add a "tor2web mode" for clients that want to connect to hidden
3344 services non-anonymously (and possibly more quickly). As a safety
3345 measure to try to keep users from turning this on without knowing
3346 what they are doing, tor2web mode must be explicitly enabled at
3347 compile time, and a copy of Tor compiled to run in tor2web mode
3348 cannot be used as a normal Tor client. Implements feature 2553.
3349 - Add experimental support for running on Windows with IOCP and no
3350 kernel-space socket buffers. This feature is controlled by a new
3351 "UserspaceIOCPBuffers" config option (off by default), which has
3352 no effect unless Tor has been built with support for bufferevents,
3353 is running on Windows, and has enabled IOCP. This may, in the long
3354 run, help solve or mitigate bug 98.
3355 - Use a more secure consensus parameter voting algorithm. Now at
3356 least three directory authorities or a majority of them must
3357 vote on a given parameter before it will be included in the
3358 consensus. Implements proposal 178.
3361 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
3362 They used to check that the timestamp was within 30 minutes
3363 of their system clock, so they could cap the size of their
3364 replay-detection cache, but that approach unnecessarily refused
3365 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
3366 the v3 intro-point protocol (the first one which sent a timestamp
3367 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
3368 - Only use the EVP interface when AES acceleration is enabled,
3369 to avoid a 5-7% performance regression. Resolves issue 4525;
3370 bugfix on 0.2.3.8-alpha.
3372 o Privacy/anonymity features (bridge detection):
3373 - Make bridge SSL certificates a bit more stealthy by using random
3374 serial numbers, in the same fashion as OpenSSL when generating
3375 self-signed certificates. Implements ticket 4584.
3376 - Introduce a new config option "DynamicDHGroups", enabled by
3377 default, which provides each bridge with a unique prime DH modulus
3378 to be used during SSL handshakes. This option attempts to help
3379 against censors who might use the Apache DH modulus as a static
3380 identifier for bridges. Addresses ticket 4548.
3382 o Minor features (new/different config options):
3383 - New configuration option "DisableDebuggerAttachment" (on by default)
3384 to prevent basic debugging attachment attempts by other processes.
3385 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
3386 - Allow MapAddress directives to specify matches against super-domains,
3387 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
3388 Implements issue 933.
3389 - Slightly change behavior of "list" options (that is, config
3390 options that can appear more than once) when they appear both in
3391 torrc and on the command line. Previously, the command-line options
3392 would be appended to the ones from torrc. Now, the command-line
3393 options override the torrc options entirely. This new behavior
3394 allows the user to override list options (like exit policies and
3395 ports to listen on) from the command line, rather than simply
3396 appending to the list.
3397 - You can get the old (appending) command-line behavior for "list"
3398 options by prefixing the option name with a "+".
3399 - You can remove all the values for a "list" option from the command
3400 line without adding any new ones by prefixing the option name
3402 - Add experimental support for a "defaults" torrc file to be parsed
3403 before the regular torrc. Torrc options override the defaults file's
3404 options in the same way that the command line overrides the torrc.
3405 The SAVECONF controller command saves only those options which
3406 differ between the current configuration and the defaults file. HUP
3407 reloads both files. (Note: This is an experimental feature; its
3408 behavior will probably be refined in future 0.2.3.x-alpha versions
3409 to better meet packagers' needs.) Implements task 4552.
3412 - Try to make the introductory warning message that Tor prints on
3413 startup more useful for actually finding help and information.
3414 Resolves ticket 2474.
3415 - Running "make version" now displays the version of Tor that
3416 we're about to build. Idea from katmagic; resolves issue 4400.
3417 - Expire old or over-used hidden service introduction points.
3418 Required by fix for bug 3460.
3419 - Move the replay-detection cache for the RSA-encrypted parts of
3420 INTRODUCE2 cells to the introduction point data structures.
3421 Previously, we would use one replay-detection cache per hidden
3422 service. Required by fix for bug 3460.
3423 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
3424 public key replay-detection cache from 60 minutes to 5 minutes. This
3425 replay-detection cache is now used only to detect multiple
3426 INTRODUCE2 cells specifying the same rendezvous point, so we can
3427 avoid launching multiple simultaneous attempts to connect to it.
3429 o Minor bugfixes (on Tor 0.2.2.x and earlier):
3430 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3431 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3433 - Fix a minor formatting issue in one of tor-gencert's error messages.
3435 - Prevent a false positive from the check-spaces script, by disabling
3436 the "whitespace between function name and (" check for functions
3438 - Fix a log message suggesting that people contact a non-existent
3439 email address. Fixes bug 3448.
3440 - Fix null-pointer access that could occur if TLS allocation failed.
3441 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3442 - Report a real bootstrap problem to the controller on router
3443 identity mismatch. Previously we just said "foo", which probably
3444 made a lot of sense at the time. Fixes bug 4169; bugfix on
3446 - If we had ever tried to call tor_addr_to_str() on an address of
3447 unknown type, we would have done a strdup() on an uninitialized
3448 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3449 Reported by "troll_un".
3450 - Correctly detect and handle transient lookup failures from
3451 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3452 Reported by "troll_un".
3453 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3454 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3455 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
3456 bug 4532; found by "troll_un".
3458 o Minor bugfixes (on Tor 0.2.3.x):
3459 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
3461 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
3462 circuit for use as a hidden service client's rendezvous point.
3463 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
3464 with help from wanoskarnet.
3465 - Restore behavior of overriding SocksPort, ORPort, and similar
3466 options from the command line. Bugfix on 0.2.3.3-alpha.
3469 - Properly handle the case where the build-tree is not the same
3470 as the source tree when generating src/common/common_sha1.i,
3471 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
3472 bugfix on 0.2.0.1-alpha.
3474 o Code simplifications, cleanups, and refactorings:
3475 - Remove the pure attribute from all functions that used it
3476 previously. In many cases we assigned it incorrectly, because the
3477 functions might assert or call impure functions, and we don't have
3478 evidence that keeping the pure attribute is worthwhile. Implements
3479 changes suggested in ticket 4421.
3480 - Remove some dead code spotted by coverity. Fixes cid 432.
3481 Bugfix on 0.2.3.1-alpha, closes bug 4637.
3484 Changes in version 0.2.3.8-alpha - 2011-11-22
3485 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
3486 socketpair-related bug that has been bothering Windows users. It adds
3487 support to serve microdescriptors to controllers, so Vidalia's network
3488 map can resume listing relays (once Vidalia implements its side),
3489 and adds better support for hardware AES acceleration. Finally, it
3490 starts the process of adjusting the bandwidth cutoff for getting the
3491 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
3492 that tiny relays harm performance more than they help network capacity.
3495 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3496 that it doesn't attempt to allocate a socketpair. This could cause
3497 some problems on Windows systems with overzealous firewalls. Fix for
3498 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3500 - Correctly sanity-check that we don't underflow on a memory
3501 allocation (and then assert) for hidden service introduction
3502 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3503 bugfix on 0.2.1.5-alpha.
3504 - Remove the artificially low cutoff of 20KB to guarantee the Fast
3505 flag. In the past few years the average relay speed has picked
3506 up, and while the "top 7/8 of the network get the Fast flag" and
3507 "all relays with 20KB or more of capacity get the Fast flag" rules
3508 used to have the same result, now the top 7/8 of the network has
3509 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
3510 - Fix a rare assertion failure when checking whether a v0 hidden
3511 service descriptor has any usable introduction points left, and
3512 we don't have enough information to build a circuit to the first
3513 intro point named in the descriptor. The HS client code in
3514 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
3515 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
3516 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
3517 - Make bridge authorities not crash when they are asked for their own
3518 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
3519 - When running as a client, do not print a misleading (and plain
3520 wrong) log message that we're collecting "directory request"
3521 statistics: clients don't collect statistics. Also don't create a
3522 useless (because empty) stats file in the stats/ directory. Fixes
3523 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
3526 - Allow Tor controllers like Vidalia to obtain the microdescriptor
3527 for a relay by identity digest or nickname. Previously,
3528 microdescriptors were only available by their own digests, so a
3529 controller would have to ask for and parse the whole microdescriptor
3530 consensus in order to look up a single relay's microdesc. Fixes
3531 bug 3832; bugfix on 0.2.3.1-alpha.
3532 - Use OpenSSL's EVP interface for AES encryption, so that all AES
3533 operations can use hardware acceleration (if present). Resolves
3536 o Minor bugfixes (on 0.2.2.x and earlier):
3537 - Detect failure to initialize Libevent. This fix provides better
3538 detection for future instances of bug 4457.
3539 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3540 function. This was eating up hideously large amounts of time on some
3541 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3542 - Don't warn about unused log_mutex in log.c when building with
3543 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3544 0.1.0.6-rc which introduced --disable-threads.
3545 - Allow manual 'authenticate' commands to the controller interface
3546 from netcat (nc) as well as telnet. We were rejecting them because
3547 they didn't come with the expected whitespace at the end of the
3548 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
3549 - Fix some (not actually triggerable) buffer size checks in usage of
3550 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
3552 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
3553 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
3554 - When configuring, starting, or stopping an NT service, stop
3555 immediately after the service configuration attempt has succeeded
3556 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3557 - When sending a NETINFO cell, include the original address
3558 received for the other side, not its canonical address. Found
3559 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3560 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
3561 can pick them up when the tests aren't disabled. Bugfix on
3562 0.2.2.4-alpha which introduced tinytest.
3563 - Fix a memory leak when we check whether a hidden service
3564 descriptor has any usable introduction points left. Fixes bug
3565 4424. Bugfix on 0.2.2.25-alpha.
3566 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3567 occurred when a client tried to fetch a descriptor for a bridge
3568 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3570 o Minor bugfixes (on 0.2.3.x):
3571 - Make util unit tests build correctly with MSVC. Bugfix on
3572 0.2.3.3-alpha. Patch by Gisle Vanem.
3573 - Successfully detect AUTH_CHALLENGE cells with no recognized
3574 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
3576 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
3577 it should still send a NETINFO cell to allow the connection to
3578 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
3580 - Log less loudly when we get an invalid authentication certificate
3581 from a source other than a directory authority: it's not unusual
3582 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
3584 - Tolerate servers with more clock skew in their authentication
3585 certificates than previously. Fixes bug 4371; bugfix on
3587 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
3588 on 0.2.3.4-alpha and 0.2.3.6-alpha.
3591 - Add two new config options for directory authorities:
3592 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3593 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3594 that is always sufficient to satisfy the bandwidth requirement for
3595 the Guard flag. Now it will be easier for researchers to simulate
3596 Tor networks with different values. Resolves ticket 4484.
3597 - When Tor ignores a hidden service specified in its configuration,
3598 include the hidden service's directory in the warning message.
3599 Previously, we would only tell the user that some hidden service
3600 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3601 - When we fail to initialize Libevent, retry with IOCP disabled so we
3602 don't need to turn on multi-threading support in Libevent, which in
3603 turn requires a working socketpair(). This is a workaround for bug
3604 4457, which affects Libevent versions from 2.0.1-alpha through
3606 - Detect when we try to build on a platform that doesn't define
3607 AF_UNSPEC to 0. We don't work there, so refuse to compile.
3608 - Update to the November 1 2011 Maxmind GeoLite Country database.
3610 o Packaging changes:
3611 - Make it easier to automate expert package builds on Windows,
3612 by removing an absolute path from makensis.exe command.
3614 o Code simplifications and refactoring:
3615 - Remove some redundant #include directives throughout the code.
3616 Patch from Andrea Gelmini.
3617 - Unconditionally use OpenSSL's AES implementation instead of our
3618 old built-in one. OpenSSL's AES has been better for a while, and
3619 relatively few servers should still be on any version of OpenSSL
3620 that doesn't have good optimized assembly AES.
3621 - Use the name "CERTS" consistently to refer to the new cell type;
3622 we were calling it CERT in some places and CERTS in others.
3625 - Numerous new unit tests for functions in util.c and address.c by
3627 - The long-disabled benchmark tests are now split into their own
3628 ./src/test/bench binary.
3629 - The benchmark tests can now use more accurate timers than
3630 gettimeofday() when such timers are available.
3633 Changes in version 0.2.3.7-alpha - 2011-10-30
3634 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
3635 the new v3 handshake. It also resolves yet another bridge address
3639 - If we mark an OR connection for close based on a cell we process,
3640 don't process any further cells on it. We already avoid further
3641 reads on marked-for-close connections, but now we also discard the
3642 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3643 which was the first version where we might mark a connection for
3644 close based on processing a cell on it.
3645 - Fix a double-free bug that would occur when we received an invalid
3646 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
3647 bugfix on 0.2.3.6-alpha.
3648 - Bridges no longer include their address in NETINFO cells on outgoing
3649 OR connections, to allow them to blend in better with clients.
3650 Removes another avenue for enumerating bridges. Reported by
3651 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
3652 cells were introduced.
3655 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
3656 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3659 Changes in version 0.2.3.6-alpha - 2011-10-26
3660 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
3661 anonymity vulnerability where an attacker can deanonymize Tor
3662 users. Everybody should upgrade.
3664 This release also features support for a new v3 connection handshake
3665 protocol, and fixes to make hidden service connections more robust.
3668 - Implement a new handshake protocol (v3) for authenticating Tors to
3669 each other over TLS. It should be more resistant to fingerprinting
3670 than previous protocols, and should require less TLS hacking for
3671 future Tor implementations. Implements proposal 176.
3672 - Allow variable-length padding cells to disguise the length of
3673 Tor's TLS records. Implements part of proposal 184.
3675 o Privacy/anonymity fixes (clients):
3676 - Clients and bridges no longer send TLS certificate chains on
3677 outgoing OR connections. Previously, each client or bridge would
3678 use the same cert chain for all outgoing OR connections until
3679 its IP address changes, which allowed any relay that the client
3680 or bridge contacted to determine which entry guards it is using.
3681 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3682 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3683 no longer considers that connection as suitable for satisfying a
3684 circuit EXTEND request. Now relays can protect clients from the
3685 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3686 - Directory authorities no longer assign the Guard flag to relays
3687 that haven't upgraded to the above "refuse EXTEND requests
3688 to client connections" fix. Now directory authorities can
3689 protect clients from the CVE-2011-2768 issue even if neither
3690 the clients nor the relays have upgraded yet. There's a new
3691 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3692 to let us transition smoothly, else tomorrow there would be no
3695 o Major bugfixes (hidden services):
3696 - Improve hidden service robustness: when an attempt to connect to
3697 a hidden service ends, be willing to refetch its hidden service
3698 descriptors from each of the HSDir relays responsible for them
3699 immediately. Previously, we would not consider refetching the
3700 service's descriptors from each HSDir for 15 minutes after the last
3701 fetch, which was inconvenient if the hidden service was not running
3702 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
3703 - When one of a hidden service's introduction points appears to be
3704 unreachable, stop trying it. Previously, we would keep trying
3705 to build circuits to the introduction point until we lost the
3706 descriptor, usually because the user gave up and restarted Tor.
3707 Partly fixes bug 3825.
3708 - Don't launch a useless circuit after failing to use one of a
3709 hidden service's introduction points. Previously, we would
3710 launch a new introduction circuit, but not set the hidden service
3711 which that circuit was intended to connect to, so it would never
3712 actually be used. A different piece of code would then create a
3713 new introduction circuit correctly. Bug reported by katmagic and
3714 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3716 o Major bugfixes (other):
3717 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3718 that they initiated. Relays could distinguish incoming bridge
3719 connections from client connections, creating another avenue for
3720 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3721 Found by "frosty_un".
3722 - Don't update the AccountingSoftLimitHitAt state file entry whenever
3723 tor gets started. This prevents a wrong average bandwidth
3724 estimate, which would cause relays to always start a new accounting
3725 interval at the earliest possible moment. Fixes bug 2003; bugfix
3726 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
3727 immensely in tracking this bug down.
3728 - Fix a crash bug when changing node restrictions while a DNS lookup
3729 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3732 o Minor bugfixes (on 0.2.2.x and earlier):
3733 - When a hidden service turns an extra service-side introduction
3734 circuit into a general-purpose circuit, free the rend_data and
3735 intro_key fields first, so we won't leak memory if the circuit
3736 is cannibalized for use as another service-side introduction
3737 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3738 - Rephrase the log message emitted if the TestSocks check is
3739 successful. Patch from Fabian Keil; fixes bug 4094.
3740 - Bridges now skip DNS self-tests, to act a little more stealthily.
3741 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3742 bridges. Patch by "warms0x".
3743 - Remove a confusing dollar sign from the example fingerprint in the
3744 man page, and also make the example fingerprint a valid one. Fixes
3745 bug 4309; bugfix on 0.2.1.3-alpha.
3746 - Fix internal bug-checking logic that was supposed to catch
3747 failures in digest generation so that it will fail more robustly
3748 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3749 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3750 - Report any failure in init_keys() calls launched because our
3751 IP address has changed. Spotted by Coverity Scan. Bugfix on
3752 0.1.1.4-alpha; fixes CID 484.
3754 o Minor bugfixes (on 0.2.3.x):
3755 - Fix a bug in configure.in that kept it from building a configure
3756 script with autoconf versions earlier than 2.61. Fixes bug 2430;
3757 bugfix on 0.2.3.1-alpha.
3758 - Don't warn users that they are exposing a client port to the
3759 Internet if they have specified an RFC1918 address. Previously,
3760 we would warn if the user had specified any non-loopback
3761 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
3762 - Fix memory leaks in the failing cases of the new SocksPort and
3763 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
3764 fixes coverity CIDs 485, 486, and 487.
3767 - When a hidden service's introduction point times out, consider
3768 trying it again during the next attempt to connect to the
3769 HS. Previously, we would not try it again unless a newly fetched
3770 descriptor contained it. Required by fixes for bugs 1297 and 3825.
3771 - The next version of Windows will be called Windows 8, and it has
3772 a major version of 6, minor version of 2. Correctly identify that
3773 version instead of calling it "Very recent version". Resolves
3774 ticket 4153; reported by funkstar.
3775 - The Bridge Authority now writes statistics on how many bridge
3776 descriptors it gave out in total, and how many unique descriptors
3777 it gave out. It also lists how often the most and least commonly
3778 fetched descriptors were given out, as well as the median and
3779 25th/75th percentile. Implements tickets 4200 and 4294.
3780 - Update to the October 4 2011 Maxmind GeoLite Country database.
3782 o Code simplifications and refactoring:
3783 - Remove some old code to remember statistics about which descriptors
3784 we've served as a directory mirror. The feature wasn't used and
3785 is outdated now that microdescriptors are around.
3786 - Rename Tor functions that turn strings into addresses, so that
3787 "parse" indicates that no hostname resolution occurs, and
3788 "lookup" indicates that hostname resolution may occur. This
3789 should help prevent mistakes in the future. Fixes bug 3512.
3792 Changes in version 0.2.2.34 - 2011-10-26
3793 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
3794 can deanonymize Tor users. Everybody should upgrade.
3796 The attack relies on four components: 1) Clients reuse their TLS cert
3797 when talking to different relays, so relays can recognize a user by
3798 the identity key in her cert. 2) An attacker who knows the client's
3799 identity key can probe each guard relay to see if that identity key
3800 is connected to that guard relay right now. 3) A variety of active
3801 attacks in the literature (starting from "Low-Cost Traffic Analysis
3802 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
3803 discover the guard relays that a Tor user visiting the website is using.
3804 4) Clients typically pick three guards at random, so the set of guards
3805 for a given user could well be a unique fingerprint for her. This
3806 release fixes components #1 and #2, which is enough to block the attack;
3807 the other two remain as open research problems. Special thanks to
3808 "frosty_un" for reporting the issue to us!
3810 Clients should upgrade so they are no longer recognizable by the TLS
3811 certs they present. Relays should upgrade so they no longer allow a
3812 remote attacker to probe them to test whether unpatched clients are
3813 currently connected to them.
3815 This release also fixes several vulnerabilities that allow an attacker
3816 to enumerate bridge relays. Some bridge enumeration attacks still
3817 remain; see for example proposal 188.
3819 o Privacy/anonymity fixes (clients):
3820 - Clients and bridges no longer send TLS certificate chains on
3821 outgoing OR connections. Previously, each client or bridge would
3822 use the same cert chain for all outgoing OR connections until
3823 its IP address changes, which allowed any relay that the client
3824 or bridge contacted to determine which entry guards it is using.
3825 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3826 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3827 no longer considers that connection as suitable for satisfying a
3828 circuit EXTEND request. Now relays can protect clients from the
3829 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3830 - Directory authorities no longer assign the Guard flag to relays
3831 that haven't upgraded to the above "refuse EXTEND requests
3832 to client connections" fix. Now directory authorities can
3833 protect clients from the CVE-2011-2768 issue even if neither
3834 the clients nor the relays have upgraded yet. There's a new
3835 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3836 to let us transition smoothly, else tomorrow there would be no
3839 o Privacy/anonymity fixes (bridge enumeration):
3840 - Bridge relays now do their directory fetches inside Tor TLS
3841 connections, like all the other clients do, rather than connecting
3842 directly to the DirPort like public relays do. Removes another
3843 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
3844 - Bridges relays now build circuits for themselves in a more similar
3845 way to how clients build them. Removes another avenue for
3846 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
3847 when bridges were introduced.
3848 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3849 that they initiated. Relays could distinguish incoming bridge
3850 connections from client connections, creating another avenue for
3851 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3852 Found by "frosty_un".
3855 - Fix a crash bug when changing node restrictions while a DNS lookup
3856 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3858 - Don't launch a useless circuit after failing to use one of a
3859 hidden service's introduction points. Previously, we would
3860 launch a new introduction circuit, but not set the hidden service
3861 which that circuit was intended to connect to, so it would never
3862 actually be used. A different piece of code would then create a
3863 new introduction circuit correctly. Bug reported by katmagic and
3864 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3867 - Change an integer overflow check in the OpenBSD_Malloc code so
3868 that GCC is less likely to eliminate it as impossible. Patch
3869 from Mansour Moufid. Fixes bug 4059.
3870 - When a hidden service turns an extra service-side introduction
3871 circuit into a general-purpose circuit, free the rend_data and
3872 intro_key fields first, so we won't leak memory if the circuit
3873 is cannibalized for use as another service-side introduction
3874 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3875 - Bridges now skip DNS self-tests, to act a little more stealthily.
3876 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3877 bridges. Patch by "warms0x".
3878 - Fix internal bug-checking logic that was supposed to catch
3879 failures in digest generation so that it will fail more robustly
3880 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3881 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3882 - Report any failure in init_keys() calls launched because our
3883 IP address has changed. Spotted by Coverity Scan. Bugfix on
3884 0.1.1.4-alpha; fixes CID 484.
3886 o Minor bugfixes (log messages and documentation):
3887 - Remove a confusing dollar sign from the example fingerprint in the
3888 man page, and also make the example fingerprint a valid one. Fixes
3889 bug 4309; bugfix on 0.2.1.3-alpha.
3890 - The next version of Windows will be called Windows 8, and it has
3891 a major version of 6, minor version of 2. Correctly identify that
3892 version instead of calling it "Very recent version". Resolves
3893 ticket 4153; reported by funkstar.
3894 - Downgrade log messages about circuit timeout calibration from
3895 "notice" to "info": they don't require or suggest any human
3896 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3897 bugfix on 0.2.2.14-alpha.
3900 - Turn on directory request statistics by default and include them in
3901 extra-info descriptors. Don't break if we have no GeoIP database.
3902 Backported from 0.2.3.1-alpha; implements ticket 3951.
3903 - Update to the October 4 2011 Maxmind GeoLite Country database.
3906 Changes in version 0.2.1.31 - 2011-10-26
3907 Tor 0.2.1.31 backports important security and privacy fixes for
3908 oldstable. This release is intended only for package maintainers and
3909 others who cannot use the 0.2.2 stable series. All others should be
3910 using Tor 0.2.2.x or newer.
3912 o Security fixes (also included in 0.2.2.x):
3913 - Replace all potentially sensitive memory comparison operations
3914 with versions whose runtime does not depend on the data being
3915 compared. This will help resist a class of attacks where an
3916 adversary can use variations in timing information to learn
3917 sensitive data. Fix for one case of bug 3122. (Safe memcmp
3918 implementation by Robert Ransom based partially on code by DJB.)
3919 - Fix an assert in parsing router descriptors containing IPv6
3920 addresses. This one took down the directory authorities when
3921 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3923 o Privacy/anonymity fixes (also included in 0.2.2.x):
3924 - Clients and bridges no longer send TLS certificate chains on
3925 outgoing OR connections. Previously, each client or bridge would
3926 use the same cert chain for all outgoing OR connections until
3927 its IP address changes, which allowed any relay that the client
3928 or bridge contacted to determine which entry guards it is using.
3929 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3930 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3931 no longer considers that connection as suitable for satisfying a
3932 circuit EXTEND request. Now relays can protect clients from the
3933 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3934 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3935 that they initiated. Relays could distinguish incoming bridge
3936 connections from client connections, creating another avenue for
3937 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3938 Found by "frosty_un".
3939 - When receiving a hidden service descriptor, check that it is for
3940 the hidden service we wanted. Previously, Tor would store any
3941 hidden service descriptors that a directory gave it, whether it
3942 wanted them or not. This wouldn't have let an attacker impersonate
3943 a hidden service, but it did let directories pre-seed a client
3944 with descriptors that it didn't want. Bugfix on 0.0.6.
3945 - Avoid linkability based on cached hidden service descriptors: forget
3946 all hidden service descriptors cached as a client when processing a
3947 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3948 - Make the bridge directory authority refuse to answer directory
3949 requests for "all" descriptors. It used to include bridge
3950 descriptors in its answer, which was a major information leak.
3951 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3952 - Don't attach new streams to old rendezvous circuits after SIGNAL
3953 NEWNYM. Previously, we would keep using an existing rendezvous
3954 circuit if it remained open (i.e. if it were kept open by a
3955 long-lived stream, or if a new stream were attached to it before
3956 Tor could notice that it was old and no longer in use). Bugfix on
3957 0.1.1.15-rc; fixes bug 3375.
3959 o Minor bugfixes (also included in 0.2.2.x):
3960 - When we restart our relay, we might get a successful connection
3961 from the outside before we've started our reachability tests,
3962 triggering a warning: "ORPort found reachable, but I have no
3963 routerinfo yet. Failing to inform controller of success." This
3964 bug was harmless unless Tor is running under a controller
3965 like Vidalia, in which case the controller would never get a
3966 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3968 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
3969 enabled. Fixes bug 1526.
3970 - Remove undocumented option "-F" from tor-resolve: it hasn't done
3971 anything since 0.2.1.16-rc.
3972 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3973 None of the cases where we did this before were wrong, but by making
3974 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3975 - Fix a rare crash bug that could occur when a client was configured
3976 with a large number of bridges. Fixes bug 2629; bugfix on
3977 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3978 - Correct the warning displayed when a rendezvous descriptor exceeds
3979 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3981 - Fix an uncommon assertion failure when running with DNSPort under
3982 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3983 - When warning about missing zlib development packages during compile,
3984 give the correct package names. Bugfix on 0.2.0.1-alpha.
3985 - Require that introduction point keys and onion keys have public
3986 exponent 65537. Bugfix on 0.2.0.10-alpha.
3987 - Do not crash when our configuration file becomes unreadable, for
3988 example due to a permissions change, between when we start up
3989 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
3991 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
3993 - Always NUL-terminate the sun_path field of a sockaddr_un before
3994 passing it to the kernel. (Not a security issue: kernels are
3995 smart enough to reject bad sockaddr_uns.) Found by Coverity;
3996 CID #428. Bugfix on Tor 0.2.0.3-alpha.
3997 - Don't stack-allocate the list of supplementary GIDs when we're
3998 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
3999 could take up to 256K, which is way too much stack. Found by
4000 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4002 o Minor bugfixes (only in 0.2.1.x):
4003 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
4004 rely on them. Bugfix on 0.2.1.30.
4005 - Use git revisions instead of svn revisions when generating our
4006 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
4008 o Minor features (also included in 0.2.2.x):
4009 - Adjust the expiration time on our SSL session certificates to
4010 better match SSL certs seen in the wild. Resolves ticket 4014.
4011 - Allow nameservers with IPv6 address. Resolves bug 2574.
4012 - Update to the October 4 2011 Maxmind GeoLite Country database.
4015 Changes in version 0.2.3.5-alpha - 2011-09-28
4016 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
4017 bridge relays; fixes an assertion error that many users started hitting
4018 today; and adds the ability to refill token buckets more often than
4019 once per second, allowing significant performance improvements.
4022 - Bridge relays now do their directory fetches inside Tor TLS
4023 connections, like all the other clients do, rather than connecting
4024 directly to the DirPort like public relays do. Removes another
4025 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
4026 - Bridges relays now build circuits for themselves in a more similar
4027 way to how clients build them. Removes another avenue for
4028 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
4029 when bridges were introduced.
4032 - Fix an "Assertion md->held_by_node == 1 failed" error that could
4033 occur when the same microdescriptor was referenced by two node_t
4034 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
4036 o Major features (networking):
4037 - Add a new TokenBucketRefillInterval option to refill token buckets
4038 more frequently than once per second. This should improve network
4039 performance, alleviate queueing problems, and make traffic less
4040 bursty. Implements proposal 183; closes ticket 3630. Design by
4041 Florian Tschorsch and Björn Scheuermann; implementation by
4045 - Change an integer overflow check in the OpenBSD_Malloc code so
4046 that GCC is less likely to eliminate it as impossible. Patch
4047 from Mansour Moufid. Fixes bug 4059.
4049 o Minor bugfixes (usability):
4050 - Downgrade log messages about circuit timeout calibration from
4051 "notice" to "info": they don't require or suggest any human
4052 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
4053 bugfix on 0.2.2.14-alpha.
4055 o Minor features (diagnostics):
4056 - When the system call to create a listener socket fails, log the
4057 error message explaining why. This may help diagnose bug 4027.
4060 Changes in version 0.2.3.4-alpha - 2011-09-13
4061 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
4062 tweak to Tor's TLS handshake that makes relays and bridges that run
4063 this new version reachable from Iran again. It also fixes a few new
4064 bugs in 0.2.3.x, and teaches relays to recognize when they're not
4065 listed in the network consensus and republish.
4067 o Major bugfixes (also part of 0.2.2.33):
4068 - Avoid an assertion failure when reloading a configuration with
4069 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
4070 3923; bugfix on 0.2.2.25-alpha.
4072 o Minor features (security, also part of 0.2.2.33):
4073 - Check for replays of the public-key encrypted portion of an
4074 INTRODUCE1 cell, in addition to the current check for replays of
4075 the g^x value. This prevents a possible class of active attacks
4076 by an attacker who controls both an introduction point and a
4077 rendezvous point, and who uses the malleability of AES-CTR to
4078 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
4079 that these attacks is infeasible (requiring the attacker to send
4080 on the order of zettabytes of altered cells in a short interval),
4081 but we'd rather block them off in case there are any classes of
4082 this attack that we missed. Reported by Willem Pinckaers.
4084 o Minor features (also part of 0.2.2.33):
4085 - Adjust the expiration time on our SSL session certificates to
4086 better match SSL certs seen in the wild. Resolves ticket 4014.
4087 - Change the default required uptime for a relay to be accepted as
4088 a HSDir (hidden service directory) from 24 hours to 25 hours.
4089 Improves on 0.2.0.10-alpha; resolves ticket 2649.
4090 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
4091 authorities to abstain from voting on assignment of the HSDir
4092 consensus flag. Related to bug 2649.
4093 - Update to the September 6 2011 Maxmind GeoLite Country database.
4095 o Minor bugfixes (also part of 0.2.2.33):
4096 - Demote the 'replay detected' log message emitted when a hidden
4097 service receives the same Diffie-Hellman public key in two different
4098 INTRODUCE2 cells to info level. A normal Tor client can cause that
4099 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4100 fixes part of bug 2442.
4101 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4102 level. There is nothing that a hidden service's operator can do
4103 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4105 - Clarify a log message specifying the characters permitted in
4106 HiddenServiceAuthorizeClient client names. Previously, the log
4107 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4108 given the impression that every ASCII character between "+" and "_"
4109 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4111 o Build fixes (also part of 0.2.2.33):
4112 - Clean up some code issues that prevented Tor from building on older
4113 BSDs. Fixes bug 3894; reported by "grarpamp".
4114 - Search for a platform-specific version of "ar" when cross-compiling.
4115 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4118 - Fix a bug where the SocksPort option (for example) would get
4119 ignored and replaced by the default if a SocksListenAddress
4120 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
4124 - Relays now try regenerating and uploading their descriptor more
4125 frequently if they are not listed in the consensus, or if the
4126 version of their descriptor listed in the consensus is too
4127 old. This fix should prevent situations where a server declines
4128 to re-publish itself because it has done so too recently, even
4129 though the authorities decided not to list its recent-enough
4130 descriptor. Fix for bug 3327.
4133 - Relays now include a reason for regenerating their descriptors
4134 in an HTTP header when uploading to the authorities. This will
4135 make it easier to debug descriptor-upload issues in the future.
4136 - When starting as root and then changing our UID via the User
4137 control option, and we have a ControlSocket configured, make sure
4138 that the ControlSocket is owned by the same account that Tor will
4139 run under. Implements ticket 3421; fix by Jérémy Bobbio.
4142 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
4143 utility function used in the control-port code). This shouldn't
4144 ever happen unless Tor is completely out of memory, but if it did
4145 happen and Tor somehow recovered from it, Tor could have sent a log
4146 message to a control port in the middle of a reply to a controller
4147 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
4148 - Make 'FetchUselessDescriptors' cause all descriptor types and
4149 all consensus types (including microdescriptors) to get fetched.
4150 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
4153 - Make a new "entry connection" struct as an internal subtype of "edge
4154 connection", to simplify the code and make exit connections smaller.
4157 Changes in version 0.2.2.33 - 2011-09-13
4158 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
4159 TLS handshake that makes relays and bridges that run this new version
4160 reachable from Iran again.
4163 - Avoid an assertion failure when reloading a configuration with
4164 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
4165 3923; bugfix on 0.2.2.25-alpha.
4167 o Minor features (security):
4168 - Check for replays of the public-key encrypted portion of an
4169 INTRODUCE1 cell, in addition to the current check for replays of
4170 the g^x value. This prevents a possible class of active attacks
4171 by an attacker who controls both an introduction point and a
4172 rendezvous point, and who uses the malleability of AES-CTR to
4173 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
4174 that these attacks are infeasible (requiring the attacker to send
4175 on the order of zettabytes of altered cells in a short interval),
4176 but we'd rather block them off in case there are any classes of
4177 this attack that we missed. Reported by Willem Pinckaers.
4180 - Adjust the expiration time on our SSL session certificates to
4181 better match SSL certs seen in the wild. Resolves ticket 4014.
4182 - Change the default required uptime for a relay to be accepted as
4183 a HSDir (hidden service directory) from 24 hours to 25 hours.
4184 Improves on 0.2.0.10-alpha; resolves ticket 2649.
4185 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
4186 authorities to abstain from voting on assignment of the HSDir
4187 consensus flag. Related to bug 2649.
4188 - Update to the September 6 2011 Maxmind GeoLite Country database.
4190 o Minor bugfixes (documentation and log messages):
4191 - Correct the man page to explain that HashedControlPassword and
4192 CookieAuthentication can both be set, in which case either method
4193 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4194 when we decided to allow these config options to both be set. Issue
4196 - Demote the 'replay detected' log message emitted when a hidden
4197 service receives the same Diffie-Hellman public key in two different
4198 INTRODUCE2 cells to info level. A normal Tor client can cause that
4199 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4200 fixes part of bug 2442.
4201 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4202 level. There is nothing that a hidden service's operator can do
4203 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4205 - Clarify a log message specifying the characters permitted in
4206 HiddenServiceAuthorizeClient client names. Previously, the log
4207 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4208 given the impression that every ASCII character between "+" and "_"
4209 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4212 - Provide a substitute implementation of lround() for MSVC, which
4213 apparently lacks it. Patch from Gisle Vanem.
4214 - Clean up some code issues that prevented Tor from building on older
4215 BSDs. Fixes bug 3894; reported by "grarpamp".
4216 - Search for a platform-specific version of "ar" when cross-compiling.
4217 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4220 Changes in version 0.2.3.3-alpha - 2011-09-01
4221 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
4222 security, and provides client-side support for the microdescriptor
4223 and optimistic data features introduced earlier in the 0.2.3.x
4224 series. It also includes numerous critical bugfixes in the (optional)
4225 bufferevent-based networking backend.
4227 o Major features (stream isolation):
4228 - You can now configure Tor so that streams from different
4229 applications are isolated on different circuits, to prevent an
4230 attacker who sees your streams as they leave an exit node from
4231 linking your sessions to one another. To do this, choose some way
4232 to distinguish the applications: have them connect to different
4233 SocksPorts, or have one of them use SOCKS4 while the other uses
4234 SOCKS5, or have them pass different authentication strings to the
4235 SOCKS proxy. Then, use the new SocksPort syntax to configure the
4236 degree of isolation you need. This implements Proposal 171.
4237 - There's a new syntax for specifying multiple client ports (such as
4238 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
4239 multiple *Port entries with full addr:port syntax on each.
4240 The old *ListenAddress format is still supported, but you can't
4241 mix it with the new *Port syntax.
4243 o Major features (other):
4244 - Enable microdescriptor fetching by default for clients. This allows
4245 clients to download a much smaller amount of directory information.
4246 To disable it (and go back to the old-style consensus and
4247 descriptors), set "UseMicrodescriptors 0" in your torrc file.
4248 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
4249 "PortForwarding" config option), now supports Windows.
4250 - When using an exit relay running 0.2.3.x, clients can now
4251 "optimistically" send data before the exit relay reports that
4252 the stream has opened. This saves a round trip when starting
4253 connections where the client speaks first (such as web browsing).
4254 This behavior is controlled by a consensus parameter (currently
4255 disabled). To turn it on or off manually, use the "OptimisticData"
4256 torrc option. Implements proposal 181; code by Ian Goldberg.
4258 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
4259 - When using IOCP on Windows, we need to enable Libevent windows
4261 - The IOCP backend now works even when the user has not specified
4262 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
4263 Fixes part of bug 3752.
4264 - Correctly record the bytes we've read and written when using
4265 bufferevents, so that we can include them in our bandwidth history
4266 and advertised bandwidth. Fixes bug 3803.
4267 - Apply rate-limiting only at the bottom of a chain of filtering
4268 bufferevents. This prevents us from filling up internal read
4269 buffers and violating rate-limits when filtering bufferevents
4270 are enabled. Fixes part of bug 3804.
4271 - Add high-watermarks to the output buffers for filtered
4272 bufferevents. This prevents us from filling up internal write
4273 buffers and wasting CPU cycles when filtering bufferevents are
4274 enabled. Fixes part of bug 3804.
4275 - Correctly notice when data has been written from a bufferevent
4276 without flushing it completely. Fixes bug 3805.
4277 - Fix a bug where server-side tunneled bufferevent-based directory
4278 streams would get closed prematurely. Fixes bug 3814.
4279 - Fix a use-after-free error with per-connection rate-limiting
4280 buckets. Fixes bug 3888.
4282 o Major bugfixes (also part of 0.2.2.31-rc):
4283 - If we're configured to write our ControlPorts to disk, only write
4284 them after switching UID and creating the data directory. This way,
4285 we don't fail when starting up with a nonexistent DataDirectory
4286 and a ControlPortWriteToFile setting based on that directory. Fixes
4287 bug 3747; bugfix on Tor 0.2.2.26-beta.
4290 - Added a new CONF_CHANGED event so that controllers can be notified
4291 of any configuration changes made by other controllers, or by the
4292 user. Implements ticket 1692.
4293 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
4294 leak when using bufferevents, and lets Libevent worry about how to
4295 best copy data out of a buffer.
4296 - Replace files in stats/ rather than appending to them. Now that we
4297 include statistics in extra-info descriptors, it makes no sense to
4298 keep old statistics forever. Implements ticket 2930.
4300 o Minor features (build compatibility):
4301 - Limited, experimental support for building with nmake and MSVC.
4302 - Provide a substitute implementation of lround() for MSVC, which
4303 apparently lacks it. Patch from Gisle Vanem.
4305 o Minor features (also part of 0.2.2.31-rc):
4306 - Update to the August 2 2011 Maxmind GeoLite Country database.
4308 o Minor bugfixes (on 0.2.3.x-alpha):
4309 - Fix a spurious warning when parsing SOCKS requests with
4310 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
4311 - Get rid of a harmless warning that could happen on relays running
4312 with bufferevents. The warning was caused by someone doing an http
4313 request to a relay's orport. Also don't warn for a few related
4314 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
4316 o Minor bugfixes (on 2.2.x and earlier):
4317 - Correct the man page to explain that HashedControlPassword and
4318 CookieAuthentication can both be set, in which case either method
4319 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4320 when we decided to allow these config options to both be set. Issue
4322 - The "--quiet" and "--hush" options now apply not only to Tor's
4323 behavior before logs are configured, but also to Tor's behavior in
4324 the absense of configured logs. Fixes bug 3550; bugfix on
4327 o Minor bugfixes (also part of 0.2.2.31-rc):
4328 - Write several files in text mode, on OSes that distinguish text
4329 mode from binary mode (namely, Windows). These files are:
4330 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4331 that collect those statistics; 'client_keys' and 'hostname' for
4332 hidden services that use authentication; and (in the tor-gencert
4333 utility) newly generated identity and signing keys. Previously,
4334 we wouldn't specify text mode or binary mode, leading to an
4335 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4336 the DirRecordUsageByCountry option which would have triggered
4337 the assertion failure was added), although this assertion failure
4338 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4339 - Selectively disable deprecation warnings on OS X because Lion
4340 started deprecating the shipped copy of openssl. Fixes bug 3643.
4341 - Remove an extra pair of quotation marks around the error
4342 message in control-port STATUS_GENERAL BUG events. Bugfix on
4343 0.1.2.6-alpha; fixes bug 3732.
4344 - When unable to format an address as a string, report its value
4345 as "???" rather than reusing the last formatted address. Bugfix
4348 o Code simplifications and refactoring:
4349 - Rewrite the listener-selection logic so that parsing which ports
4350 we want to listen on is now separate from binding to the ports
4354 - Building Tor with bufferevent support now requires Libevent
4355 2.0.13-stable or later. Previous versions of Libevent had bugs in
4356 SSL-related bufferevents and related issues that would make Tor
4357 work badly with bufferevents. Requiring 2.0.13-stable also allows
4358 Tor with bufferevents to take advantage of Libevent APIs
4359 introduced after 2.0.8-rc.
4362 Changes in version 0.2.2.32 - 2011-08-27
4363 The Tor 0.2.2 release series is dedicated to the memory of Andreas
4364 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
4365 a founder of the PETS community, a leader in our field, a mentor,
4366 and a friend. He left us with these words: "I had the possibility
4367 to contribute to this world that is not as it should be. I hope I
4368 could help in some areas to make the world a better place, and that
4369 I could also encourage other people to be engaged in improving the
4370 world. Please, stay engaged. This world needs you, your love, your
4371 initiative -- now I cannot be part of that anymore."
4373 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
4374 ready. More than two years in the making, this release features improved
4375 client performance and hidden service reliability, better compatibility
4376 for Android, correct behavior for bridges that listen on more than
4377 one address, more extensible and flexible directory object handling,
4378 better reporting of network statistics, improved code security, and
4379 many many other features and bugfixes.
4382 Changes in version 0.2.2.31-rc - 2011-08-17
4383 Tor 0.2.2.31-rc is the second and hopefully final release candidate
4384 for the Tor 0.2.2.x series.
4387 - Remove an extra pair of quotation marks around the error
4388 message in control-port STATUS_GENERAL BUG events. Bugfix on
4389 0.1.2.6-alpha; fixes bug 3732.
4390 - If we're configured to write our ControlPorts to disk, only write
4391 them after switching UID and creating the data directory. This way,
4392 we don't fail when starting up with a nonexistent DataDirectory
4393 and a ControlPortWriteToFile setting based on that directory. Fixes
4394 bug 3747; bugfix on Tor 0.2.2.26-beta.
4397 - Update to the August 2 2011 Maxmind GeoLite Country database.
4400 - Allow GETINFO fingerprint to return a fingerprint even when
4401 we have not yet built a router descriptor. Fixes bug 3577;
4402 bugfix on 0.2.0.1-alpha.
4403 - Write several files in text mode, on OSes that distinguish text
4404 mode from binary mode (namely, Windows). These files are:
4405 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4406 that collect those statistics; 'client_keys' and 'hostname' for
4407 hidden services that use authentication; and (in the tor-gencert
4408 utility) newly generated identity and signing keys. Previously,
4409 we wouldn't specify text mode or binary mode, leading to an
4410 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4411 the DirRecordUsageByCountry option which would have triggered
4412 the assertion failure was added), although this assertion failure
4413 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4414 - Selectively disable deprecation warnings on OS X because Lion
4415 started deprecating the shipped copy of openssl. Fixes bug 3643.
4416 - When unable to format an address as a string, report its value
4417 as "???" rather than reusing the last formatted address. Bugfix
4421 Changes in version 0.2.3.2-alpha - 2011-07-18
4422 Tor 0.2.3.2-alpha introduces two new experimental features:
4423 microdescriptors and pluggable transports. It also continues cleaning
4424 up a variety of recently introduced features.
4427 - Clients can now use microdescriptors instead of regular descriptors
4428 to build circuits. Microdescriptors are authority-generated
4429 summaries of regular descriptors' contents, designed to change
4430 very rarely (see proposal 158 for details). This feature is
4431 designed to save bandwidth, especially for clients on slow internet
4432 connections. It's off by default for now, since nearly no caches
4433 support it, but it will be on-by-default for clients in a future
4434 version. You can use the UseMicrodescriptors option to turn it on.
4435 - Tor clients using bridges can now be configured to use a separate
4436 'transport' proxy for each bridge. This approach helps to resist
4437 censorship by allowing bridges to use protocol obfuscation
4438 plugins. It implements part of proposal 180. Implements ticket 2841.
4439 - While we're trying to bootstrap, record how many TLS connections
4440 fail in each state, and report which states saw the most failures
4441 in response to any bootstrap failures. This feature may speed up
4442 diagnosis of censorship events. Implements ticket 3116.
4444 o Major bugfixes (on 0.2.3.1-alpha):
4445 - When configuring a large set of nodes in EntryNodes (as with
4446 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
4447 random subset to be guards, and choose them in random
4448 order. Fixes bug 2798.
4449 - Tor could crash when remembering a consensus in a non-used consensus
4450 flavor without having a current consensus set. Fixes bug 3361.
4451 - Comparing an unknown address to a microdescriptor's shortened exit
4452 policy would always give a "rejected" result. Fixes bug 3599.
4453 - Using microdescriptors as a client no longer prevents Tor from
4454 uploading and downloading hidden service descriptors. Fixes
4458 - Allow nameservers with IPv6 address. Resolves bug 2574.
4459 - Accept attempts to include a password authenticator in the
4460 handshake, as supported by SOCKS5. This handles SOCKS clients that
4461 don't know how to omit a password when authenticating. Resolves
4463 - When configuring a large set of nodes in EntryNodes, and there are
4464 enough of them listed as Guard so that we don't need to consider
4465 the non-guard entries, prefer the ones listed with the Guard flag.
4466 - Check for and recover from inconsistency in the microdescriptor
4467 cache. This will make it harder for us to accidentally free a
4468 microdescriptor without removing it from the appropriate data
4469 structures. Fixes issue 3135; issue noted by "wanoskarnet".
4470 - Log SSL state transitions at log level DEBUG, log domain
4471 HANDSHAKE. This can be useful for debugging censorship events.
4472 Implements ticket 3264.
4473 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
4474 implements ticket 3439.
4476 o Minor bugfixes (on 0.2.3.1-alpha):
4477 - Do not free all general-purpose regular descriptors just
4478 because microdescriptor use is enabled. Fixes bug 3113.
4479 - Correctly link libevent_openssl when --enable-static-libevent
4480 is passed to configure. Fixes bug 3118.
4481 - Bridges should not complain during their heartbeat log messages that
4482 they are unlisted in the consensus: that's more or less the point
4483 of being a bridge. Fixes bug 3183.
4484 - Report a SIGNAL event to controllers when acting on a delayed
4485 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
4486 event to the controller if we acted on a SIGNAL NEWNYM command
4487 immediately, and otherwise not report a SIGNAL event for the
4488 command at all. Fixes bug 3349.
4489 - Fix a crash when handling the SIGNAL controller command or
4490 reporting ERR-level status events with bufferevents enabled. Found
4491 by Robert Ransom. Fixes bug 3367.
4492 - Always ship the tor-fw-helper manpage in our release tarballs.
4493 Fixes bug 3389. Reported by Stephen Walker.
4494 - Fix a class of double-mark-for-close bugs when bufferevents
4495 are enabled. Fixes bug 3403.
4496 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
4497 - Add SIGNAL to the list returned by the 'GETINFO events/names'
4498 control-port command. Fixes part of bug 3465.
4499 - Prevent using negative indices during unit test runs when read_all()
4500 fails. Spotted by coverity.
4501 - Fix a rare memory leak when checking the nodelist without it being
4502 present. Found by coverity.
4503 - Only try to download a microdescriptor-flavored consensus from
4504 a directory cache that provides them.
4506 o Minor bugfixes (on 0.2.2.x and earlier):
4507 - Assert that hidden-service-related operations are not performed
4508 using single-hop circuits. Previously, Tor would assert that
4509 client-side streams are not attached to single-hop circuits,
4510 but not that other sensitive operations on the client and service
4511 side are not performed using single-hop circuits. Fixes bug 3332;
4513 - Don't publish a new relay descriptor when we reload our onion key,
4514 unless the onion key has actually changed. Fixes bug 3263 and
4515 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
4516 - Allow GETINFO fingerprint to return a fingerprint even when
4517 we have not yet built a router descriptor. Fixes bug 3577;
4518 bugfix on 0.2.0.1-alpha.
4519 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
4520 on 0.2.2.4-alpha; fixes bug 3427.
4522 o Code simplification and refactoring:
4523 - Use tor_sscanf() in place of scanf() in more places through the
4524 code. This makes us a little more locale-independent, and
4525 should help shut up code-analysis tools that can't tell
4526 a safe sscanf string from a dangerous one.
4527 - Use tt_assert(), not tor_assert(), for checking for test failures.
4528 This makes the unit tests more able to go on in the event that
4530 - Split connection_about_to_close() into separate functions for each
4534 - On Windows, we now define the _WIN32_WINNT macros only if they
4535 are not already defined. This lets the person building Tor decide,
4536 if they want, to require a later version of Windows.
4539 Changes in version 0.2.2.30-rc - 2011-07-07
4540 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
4541 series. It fixes a few smaller bugs, but generally appears stable.
4542 Please test it and let us know whether it is!
4545 - Send a SUCCEEDED stream event to the controller when a reverse
4546 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
4547 discovered by katmagic.
4548 - Always NUL-terminate the sun_path field of a sockaddr_un before
4549 passing it to the kernel. (Not a security issue: kernels are
4550 smart enough to reject bad sockaddr_uns.) Found by Coverity;
4551 CID #428. Bugfix on Tor 0.2.0.3-alpha.
4552 - Don't stack-allocate the list of supplementary GIDs when we're
4553 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4554 could take up to 256K, which is way too much stack. Found by
4555 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4556 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
4557 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
4558 fixes part of bug 3465.
4559 - Fix a memory leak when receiving a descriptor for a hidden
4560 service we didn't ask for. Found by Coverity; CID #30. Bugfix
4564 - Update to the July 1 2011 Maxmind GeoLite Country database.
4567 Changes in version 0.2.2.29-beta - 2011-06-20
4568 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
4569 have bridge lines in their torrc but don't want to use them; gets
4570 us closer to having the control socket feature working on Debian;
4571 and fixes a variety of smaller bugs.
4574 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
4575 When we changed the default behavior to "use bridges if any
4576 are listed in the torrc", we surprised users who had bridges
4577 in their torrc files but who didn't actually want to use them.
4578 Partial resolution for bug 3354.
4581 - Don't attach new streams to old rendezvous circuits after SIGNAL
4582 NEWNYM. Previously, we would keep using an existing rendezvous
4583 circuit if it remained open (i.e. if it were kept open by a
4584 long-lived stream, or if a new stream were attached to it before
4585 Tor could notice that it was old and no longer in use). Bugfix on
4586 0.1.1.15-rc; fixes bug 3375.
4589 - Fix a bug when using ControlSocketsGroupWritable with User. The
4590 directory's group would be checked against the current group, not
4591 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
4592 bugfix on 0.2.2.26-beta.
4593 - Make connection_printf_to_buf()'s behaviour sane. Its callers
4594 expect it to emit a CRLF iff the format string ends with CRLF;
4595 it actually emitted a CRLF iff (a) the format string ended with
4596 CRLF or (b) the resulting string was over 1023 characters long or
4597 (c) the format string did not end with CRLF *and* the resulting
4598 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
4599 fixes part of bug 3407.
4600 - Make send_control_event_impl()'s behaviour sane. Its callers
4601 expect it to always emit a CRLF at the end of the string; it
4602 might have emitted extra control characters as well. Bugfix on
4603 0.1.1.9-alpha; fixes another part of bug 3407.
4604 - Make crypto_rand_int() check the value of its input correctly.
4605 Previously, it accepted values up to UINT_MAX, but could return a
4606 negative number if given a value above INT_MAX+1. Found by George
4607 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
4608 - Avoid a segfault when reading a malformed circuit build state
4609 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
4611 - When asked about a DNS record type we don't support via a
4612 client DNSPort, reply with NOTIMPL rather than an empty
4613 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
4614 - Fix a rare memory leak during stats writing. Found by coverity.
4617 - Update to the June 1 2011 Maxmind GeoLite Country database.
4619 o Code simplifications and refactoring:
4620 - Remove some dead code as indicated by coverity.
4621 - Remove a few dead assignments during router parsing. Found by
4623 - Add some forgotten return value checks during unit tests. Found
4625 - Don't use 1-bit wide signed bit fields. Found by coverity.
4628 Changes in version 0.2.2.28-beta - 2011-06-04
4629 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
4630 fixed a big bug in whether relays stay in the consensus consistently,
4631 we moved closer to handling bridges and hidden services correctly,
4632 and we started the process of better handling the dreaded "my Vidalia
4633 died, and now my Tor demands a password when I try to reconnect to it"
4637 - Don't decide to make a new descriptor when receiving a HUP signal.
4638 This bug has caused a lot of 0.2.2.x relays to disappear from the
4639 consensus periodically. Fixes the most common case of triggering
4640 bug 1810; bugfix on 0.2.2.7-alpha.
4641 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
4642 - Don't try to build descriptors if "ORPort auto" is set and we
4643 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
4645 - Resolve a crash that occurred when setting BridgeRelay to 1 with
4646 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
4647 - Apply circuit timeouts to opened hidden-service-related circuits
4648 based on the correct start time. Previously, we would apply the
4649 circuit build timeout based on time since the circuit's creation;
4650 it was supposed to be applied based on time since the circuit
4651 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
4652 - Use the same circuit timeout for client-side introduction
4653 circuits as for other four-hop circuits, rather than the timeout
4654 for single-hop directory-fetch circuits; the shorter timeout may
4655 have been appropriate with the static circuit build timeout in
4656 0.2.1.x and earlier, but caused many hidden service access attempts
4657 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
4658 on 0.2.2.2-alpha; fixes another part of bug 1297.
4659 - In ticket 2511 we fixed a case where you could use an unconfigured
4660 bridge if you had configured it as a bridge the last time you ran
4661 Tor. Now fix another edge case: if you had configured it as a bridge
4662 but then switched to a different bridge via the controller, you
4663 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
4667 - Add an __OwningControllerProcess configuration option and a
4668 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
4669 that when it exits, Tor will shut down. Implements feature 3049.
4670 - If "UseBridges 1" is set and no bridges are configured, Tor will
4671 now refuse to build any circuits until some bridges are set.
4672 If "UseBridges auto" is set, Tor will use bridges if they are
4673 configured and we are not running as a server, but otherwise will
4674 make circuits as usual. The new default is "auto". Patch by anonym,
4675 so the Tails LiveCD can stop automatically revealing you as a Tor
4679 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4680 - Remove a trailing asterisk from "exit-policy/default" in the
4681 output of the control port command "GETINFO info/names". Bugfix
4683 - Use a wide type to hold sockets when built for 64-bit Windows builds.
4685 - Warn when the user configures two HiddenServiceDir lines that point
4686 to the same directory. Bugfix on 0.0.6 (the version introducing
4687 HiddenServiceDir); fixes bug 3289.
4688 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
4689 part of bug 2748; bugfix on 0.2.0.10-alpha.
4690 - Log malformed requests for rendezvous descriptors as protocol
4691 warnings, not warnings. Also, use a more informative log message
4692 in case someone sees it at log level warning without prior
4693 info-level messages. Fixes the other part of bug 2748; bugfix
4695 - Clear the table recording the time of the last request for each
4696 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
4697 Previously, we would clear our HS descriptor cache on SIGNAL
4698 NEWNYM, but if we had previously retrieved a descriptor (or tried
4699 to) from every directory responsible for it, we would refuse to
4700 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
4702 - Fix a log message that said "bits" while displaying a value in
4703 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
4705 - When checking for 1024-bit keys, check for 1024 bits, not 128
4706 bytes. This allows Tor to correctly discard keys of length 1017
4707 through 1023. Bugfix on 0.0.9pre5.
4710 - Relays now log the reason for publishing a new relay descriptor,
4711 so we have a better chance of hunting down instances of bug 1810.
4712 Resolves ticket 3252.
4713 - Revise most log messages that refer to nodes by nickname to
4714 instead use the "$key=nickname at address" format. This should be
4715 more useful, especially since nicknames are less and less likely
4716 to be unique. Resolves ticket 3045.
4717 - Log (at info level) when purging pieces of hidden-service-client
4718 state because of SIGNAL NEWNYM.
4721 - Remove undocumented option "-F" from tor-resolve: it hasn't done
4722 anything since 0.2.1.16-rc.
4725 Changes in version 0.2.2.27-beta - 2011-05-18
4726 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
4727 release, and also adds a few more general bugfixes.
4730 - Fix a crash bug when changing bridges in a running Tor process.
4731 Fixes bug 3213; bugfix on 0.2.2.26-beta.
4732 - When the controller configures a new bridge, don't wait 10 to 60
4733 seconds before trying to fetch its descriptor. Bugfix on
4734 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
4737 - Require that onion keys have exponent 65537 in microdescriptors too.
4738 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
4739 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
4740 Changed the limit to 512 characters by removing base64 newlines.
4741 Fixes bug 2752. Fix by Michael Yakubovich.
4742 - When a client starts or stops using bridges, never use a circuit
4743 that was built before the configuration change. This behavior could
4744 put at risk a user who uses bridges to ensure that her traffic
4745 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
4749 Changes in version 0.2.2.26-beta - 2011-05-17
4750 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
4751 also introduces a new "socksport auto" approach that should make it
4752 easier to run multiple Tors on the same system, and does a lot of
4753 cleanup to get us closer to a release candidate.
4755 o Security/privacy fixes:
4756 - Replace all potentially sensitive memory comparison operations
4757 with versions whose runtime does not depend on the data being
4758 compared. This will help resist a class of attacks where an
4759 adversary can use variations in timing information to learn
4760 sensitive data. Fix for one case of bug 3122. (Safe memcmp
4761 implementation by Robert Ransom based partially on code by DJB.)
4762 - When receiving a hidden service descriptor, check that it is for
4763 the hidden service we wanted. Previously, Tor would store any
4764 hidden service descriptors that a directory gave it, whether it
4765 wanted them or not. This wouldn't have let an attacker impersonate
4766 a hidden service, but it did let directories pre-seed a client
4767 with descriptors that it didn't want. Bugfix on 0.0.6.
4768 - On SIGHUP, do not clear out all TrackHostExits mappings, client
4769 DNS cache entries, and virtual address mappings: that's what
4770 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
4773 - The options SocksPort, ControlPort, and so on now all accept a
4774 value "auto" that opens a socket on an OS-selected port. A
4775 new ControlPortWriteToFile option tells Tor to write its
4776 actual control port or ports to a chosen file. If the option
4777 ControlPortFileGroupReadable is set, the file is created as
4778 group-readable. Now users can run two Tor clients on the same
4779 system without needing to manually mess with parameters. Resolves
4780 part of ticket 3076.
4781 - Set SO_REUSEADDR on all sockets, not just listeners. This should
4782 help busy exit nodes avoid running out of useable ports just
4783 because all the ports have been used in the near past. Resolves
4787 - New "GETINFO net/listeners/(type)" controller command to return
4788 a list of addresses and ports that are bound for listeners for a
4789 given connection type. This is useful when the user has configured
4790 "SocksPort auto" and the controller needs to know which port got
4791 chosen. Resolves another part of ticket 3076.
4792 - Add a new ControlSocketsGroupWritable configuration option: when
4793 it is turned on, ControlSockets are group-writeable by the default
4794 group of the current user. Patch by Jérémy Bobbio; implements
4796 - Tor now refuses to create a ControlSocket in a directory that is
4797 world-readable (or group-readable if ControlSocketsGroupWritable
4798 is 0). This is necessary because some operating systems do not
4799 enforce permissions on an AF_UNIX sockets. Permissions on the
4800 directory holding the socket, however, seems to work everywhere.
4801 - Rate-limit a warning about failures to download v2 networkstatus
4802 documents. Resolves part of bug 1352.
4803 - Backport code from 0.2.3.x that allows directory authorities to
4804 clean their microdescriptor caches. Needed to resolve bug 2230.
4805 - When an HTTPS proxy reports "403 Forbidden", we now explain
4806 what it means rather than calling it an unexpected status code.
4807 Closes bug 2503. Patch from Michael Yakubovich.
4808 - Update to the May 1 2011 Maxmind GeoLite Country database.
4811 - Authorities now clean their microdesc cache periodically and when
4812 reading from disk initially, not only when adding new descriptors.
4813 This prevents a bug where we could lose microdescriptors. Bugfix
4814 on 0.2.2.6-alpha. Fixes bug 2230.
4815 - Do not crash when our configuration file becomes unreadable, for
4816 example due to a permissions change, between when we start up
4817 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
4819 - Avoid a bug that would keep us from replacing a microdescriptor
4820 cache on Windows. (We would try to replace the file while still
4821 holding it open. That's fine on Unix, but Windows doesn't let us
4822 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
4823 - Add missing explanations for the authority-related torrc options
4824 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
4825 man page. Resolves issue 2379.
4826 - As an authority, do not upload our own vote or signature set to
4827 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
4828 it would get flagged as a duplicate. Resolves bug 3026.
4829 - Accept hidden service descriptors if we think we might be a hidden
4830 service directory, regardless of what our consensus says. This
4831 helps robustness, since clients and hidden services can sometimes
4832 have a more up-to-date view of the network consensus than we do,
4833 and if they think that the directory authorities list us a HSDir,
4834 we might actually be one. Related to bug 2732; bugfix on
4836 - When a controller changes TrackHostExits, remove mappings for
4837 hosts that should no longer have their exits tracked. Bugfix on
4839 - When a controller changes VirtualAddrNetwork, remove any mappings
4840 for hosts that were automapped to the old network. Bugfix on
4842 - When a controller changes one of the AutomapHosts* options, remove
4843 any mappings for hosts that should no longer be automapped. Bugfix
4845 - Do not reset the bridge descriptor download status every time we
4846 re-parse our configuration or get a configuration change. Fixes
4847 bug 3019; bugfix on 0.2.0.3-alpha.
4849 o Minor bugfixes (code cleanup):
4850 - When loading the microdesc journal, remember its current size.
4851 In 0.2.2, this helps prevent the microdesc journal from growing
4852 without limit on authorities (who are the only ones to use it in
4853 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
4854 Fix posted by "cypherpunks."
4855 - The microdesc journal is supposed to get rebuilt only if it is
4856 at least _half_ the length of the store, not _twice_ the length
4857 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
4858 - Fix a potential null-pointer dereference while computing a
4859 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
4861 - Avoid a possible null-pointer dereference when rebuilding the mdesc
4862 cache without actually having any descriptors to cache. Bugfix on
4863 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
4864 - If we fail to compute the identity digest of a v3 legacy keypair,
4865 warn, and don't use a buffer-full of junk instead. Bugfix on
4866 0.2.1.1-alpha; fixes bug 3106.
4867 - Resolve an untriggerable issue in smartlist_string_num_isin(),
4868 where if the function had ever in the future been used to check
4869 for the presence of a too-large number, it would have given an
4870 incorrect result. (Fortunately, we only used it for 16-bit
4871 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
4872 - Require that introduction point keys and onion handshake keys
4873 have a public exponent of 65537. Starts to fix bug 3207; bugfix
4877 - Caches no longer download and serve v2 networkstatus documents
4878 unless FetchV2Networkstatus flag is set: these documents haven't
4879 haven't been used by clients or relays since 0.2.0.x. Resolves
4883 Changes in version 0.2.3.1-alpha - 2011-05-05
4884 Tor 0.2.3.1-alpha adds some new experimental features, including support
4885 for an improved network IO backend, IOCP networking on Windows,
4886 microdescriptor caching, "fast-start" support for streams, and automatic
4887 home router configuration. There are also numerous internal improvements
4888 to try to make the code easier for developers to work with.
4890 This is the first alpha release in a new series, so expect there to be
4891 bugs. Users who would rather test out a more stable branch should
4892 stay with 0.2.2.x for now.
4895 - Tor can now optionally build with the "bufferevents" buffered IO
4896 backend provided by Libevent 2. To use this feature, make sure you
4897 have the latest possible version of Libevent, and pass the
4898 --enable-bufferevents flag to configure when building Tor from
4899 source. This feature will make our networking code more flexible,
4900 let us stack layers on each other, and let us use more efficient
4901 zero-copy transports where available.
4902 - As an experimental feature, Tor can use IOCP for networking on Windows.
4903 Once this code is tuned and optimized, it promises much better
4904 performance than the select-based backend we've used in the past. To
4905 try this feature, you must build Tor with Libevent 2, configure Tor
4906 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
4907 your torrc. There are known bugs here: only try this if you can help
4908 debug it as it breaks.
4909 - The EntryNodes option can now include country codes like {de} or IP
4910 addresses or network masks. Previously we had disallowed these options
4911 because we didn't have an efficient way to keep the list up to
4912 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
4913 - Exit nodes now accept and queue data on not-yet-connected streams.
4914 Previously, the client wasn't allowed to send data until the stream was
4915 connected, which slowed down all connections. This change will enable
4916 clients to perform a "fast-start" on streams and send data without
4917 having to wait for a confirmation that the stream has opened. (Patch
4918 from Ian Goldberg; implements the server side of Proposal 174.)
4919 - Tor now has initial support for automatic port mapping on the many
4920 home routers that support NAT-PMP or UPnP. (Not yet supported on
4921 Windows). To build the support code, you'll need to have libnatpnp
4922 library and/or the libminiupnpc library, and you'll need to enable the
4923 feature specifically by passing "--enable-upnp" and/or
4924 "--enable-natpnp" to configure. To turn it on, use the new
4925 PortForwarding option.
4926 - Caches now download, cache, and serve multiple "flavors" of the
4927 consensus, including a flavor that describes microdescriptors.
4928 - Caches now download, cache, and serve microdescriptors -- small
4929 summaries of router descriptors that are authenticated by all of the
4930 directory authorities. Once enough caches are running this code,
4931 clients will be able to save significant amounts of directory bandwidth
4932 by downloading microdescriptors instead of router descriptors.
4935 - Make logging resolution configurable with a new LogTimeGranularity
4936 option, and change the default from 1 millisecond to 1 second.
4937 Implements enhancement 1668.
4938 - We log which torrc file we're using on startup. Implements ticket
4940 - Ordinarily, Tor does not count traffic from private addresses (like
4941 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
4942 There is now a new option, CountPrivateBandwidth, to disable this
4943 behavior. Patch from Daniel Cagara.
4944 - New --enable-static-tor configure option for building Tor as
4945 statically as possible. Idea, general hackery and thoughts from
4946 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
4948 - If you set the NumCPUs option to 0, Tor will now try to detect how
4949 many CPUs you have. This is the new default behavior.
4950 - Turn on directory request statistics by default and include them in
4951 extra-info descriptors. Don't break if we have no GeoIP database.
4952 - Relays that set "ConnDirectionStatistics 1" write statistics on the
4953 bidirectional use of connections to disk every 24 hours.
4954 - Add a GeoIP file digest to the extra-info descriptor. Implements
4956 - The NodeFamily option -- which let you declare that you want to
4957 consider nodes to be part of a family whether they list themselves
4958 that way or not -- now allows IP address ranges and country codes.
4959 - Add a new 'Heartbeat' log message type to periodically log a message
4960 describing Tor's status at level Notice. This feature is meant for
4961 operators who log at notice, and want to make sure that their Tor
4962 server is still working. Implementation by George Kadianakis.
4964 o Minor bugfixes (on 0.2.2.25-alpha):
4965 - When loading the microdesc journal, remember its current size.
4966 In 0.2.2, this helps prevent the microdesc journal from growing
4967 without limit on authorities (who are the only ones to use it in
4968 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
4969 Fix posted by "cypherpunks."
4970 - The microdesc journal is supposed to get rebuilt only if it is
4971 at least _half_ the length of the store, not _twice_ the length
4972 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
4973 - If as an authority we fail to compute the identity digest of a v3
4974 legacy keypair, warn, and don't use a buffer-full of junk instead.
4975 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
4976 - Authorities now clean their microdesc cache periodically and when
4977 reading from disk initially, not only when adding new descriptors.
4978 This prevents a bug where we could lose microdescriptors. Bugfix
4981 o Minor features (controller):
4982 - Add a new SIGNAL event to the controller interface so that
4983 controllers can be notified when Tor handles a signal. Resolves
4984 issue 1955. Patch by John Brooks.
4985 - Add a new GETINFO option to get total bytes read and written. Patch
4986 from pipe, revised by atagar. Resolves ticket 2345.
4987 - Implement some GETINFO controller fields to provide information about
4988 the Tor process's pid, euid, username, and resource limits.
4991 - Our build system requires automake 1.6 or later to create the
4992 Makefile.in files. Previously, you could have used 1.4.
4993 This only affects developers and people building Tor from git;
4994 people who build Tor from the source distribution without changing
4995 the Makefile.am files should be fine.
4996 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
4997 so on. This is more robust against some of the failure modes
4998 associated with running the autotools pieces on their own.
5000 o Minor packaging issues:
5001 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
5002 already created. Patch from Andreas Stieger. Fixes bug 2573.
5004 o Code simplifications and refactoring:
5005 - A major revision to our internal node-selecting and listing logic.
5006 Tor already had at least two major ways to look at the question of
5007 "which Tor servers do we know about": a list of router descriptors,
5008 and a list of entries in the current consensus. With
5009 microdescriptors, we're adding a third. Having so many systems
5010 without an abstraction layer over them was hurting the codebase.
5011 Now, we have a new "node_t" abstraction that presents a consistent
5012 interface to a client's view of a Tor node, and holds (nearly) all
5013 of the mutable state formerly in routerinfo_t and routerstatus_t.
5014 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
5015 no longer link against Libevent: they never used it, but
5016 our library structure used to force them to link it.
5019 - Remove some old code to work around even older versions of Tor that
5020 used forked processes to handle DNS requests. Such versions of Tor
5021 are no longer in use as servers.
5023 o Documentation fixes:
5024 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
5025 - Add missing documentation for the authority-related torrc options
5026 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
5030 Changes in version 0.2.2.25-alpha - 2011-04-29
5031 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
5032 robust, routers no longer overreport their bandwidth, Win7 should crash
5033 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
5034 now prevents hidden service-related activity from being linkable. It
5035 provides more information to Vidalia so you can see if your bridge is
5036 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
5037 StrictNodes configuration options to make them more reliable, more
5038 understandable, and more regularly applied. If you use those options,
5039 please see the revised documentation for them in the manual page.
5042 - Relays were publishing grossly inflated bandwidth values because
5043 they were writing their state files wrong--now they write the
5044 correct value. Also, resume reading bandwidth history from the
5045 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
5046 - Improve hidden service robustness: When we find that we have
5047 extended a hidden service's introduction circuit to a relay not
5048 listed as an introduction point in the HS descriptor we currently
5049 have, retry with an introduction point from the current
5050 descriptor. Previously we would just give up. Fixes bugs 1024 and
5051 1930; bugfix on 0.2.0.10-alpha.
5052 - Clients now stop trying to use an exit node associated with a given
5053 destination by TrackHostExits if they fail to reach that exit node.
5054 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
5055 - Fix crash bug on platforms where gmtime and localtime can return
5056 NULL. Windows 7 users were running into this one. Fixes part of bug
5057 2077. Bugfix on all versions of Tor. Found by boboper.
5059 o Security and stability fixes:
5060 - Don't double-free a parsable, but invalid, microdescriptor, even if
5061 it is followed in the blob we're parsing by an unparsable
5062 microdescriptor. Fixes an issue reported in a comment on bug 2954.
5063 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
5064 - If the Nickname configuration option isn't given, Tor would pick a
5065 nickname based on the local hostname as the nickname for a relay.
5066 Because nicknames are not very important in today's Tor and the
5067 "Unnamed" nickname has been implemented, this is now problematic
5068 behavior: It leaks information about the hostname without being
5069 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
5070 introduced the Unnamed nickname. Reported by tagnaq.
5071 - Fix an uncommon assertion failure when running with DNSPort under
5072 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
5073 - Avoid linkability based on cached hidden service descriptors: forget
5074 all hidden service descriptors cached as a client when processing a
5075 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
5078 - Export GeoIP information on bridge usage to controllers even if we
5079 have not yet been running for 24 hours. Now Vidalia bridge operators
5080 can get more accurate and immediate feedback about their
5081 contributions to the network.
5083 o Major features and bugfixes (node selection):
5084 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
5085 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
5086 options. Previously, we had been ambiguous in describing what
5087 counted as an "exit" node, and what operations exactly "StrictNodes
5088 0" would permit. This created confusion when people saw nodes built
5089 through unexpected circuits, and made it hard to tell real bugs from
5090 surprises. Now the intended behavior is:
5091 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
5092 a node that delivers user traffic outside the Tor network.
5093 . "Entry", in the context of EntryNodes, means a node used as the
5094 first hop of a multihop circuit. It doesn't include direct
5095 connections to directory servers.
5096 . "ExcludeNodes" applies to all nodes.
5097 . "StrictNodes" changes the behavior of ExcludeNodes only. When
5098 StrictNodes is set, Tor should avoid all nodes listed in
5099 ExcludeNodes, even when it will make user requests fail. When
5100 StrictNodes is *not* set, then Tor should follow ExcludeNodes
5101 whenever it can, except when it must use an excluded node to
5102 perform self-tests, connect to a hidden service, provide a
5103 hidden service, fulfill a .exit request, upload directory
5104 information, or fetch directory information.
5105 Collectively, the changes to implement the behavior fix bug 1090.
5106 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
5107 a node is listed in both, it's treated as excluded.
5108 - ExcludeNodes now applies to directory nodes -- as a preference if
5109 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
5110 Don't exclude all the directory authorities and set StrictNodes to 1
5111 unless you really want your Tor to break.
5112 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
5113 - ExcludeExitNodes now overrides .exit requests.
5114 - We don't use bridges listed in ExcludeNodes.
5115 - When StrictNodes is 1:
5116 . We now apply ExcludeNodes to hidden service introduction points
5117 and to rendezvous points selected by hidden service users. This
5118 can make your hidden service less reliable: use it with caution!
5119 . If we have used ExcludeNodes on ourself, do not try relay
5120 reachability self-tests.
5121 . If we have excluded all the directory authorities, we will not
5122 even try to upload our descriptor if we're a relay.
5123 . Do not honor .exit requests to an excluded node.
5124 - Remove a misfeature that caused us to ignore the Fast/Stable flags
5125 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
5126 - When the set of permitted nodes changes, we now remove any mappings
5127 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
5129 - We never cannibalize a circuit that had excluded nodes on it, even
5130 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
5131 - Revert a change where we would be laxer about attaching streams to
5132 circuits than when building the circuits. This was meant to prevent
5133 a set of bugs where streams were never attachable, but our improved
5134 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
5135 - Keep track of how many times we launch a new circuit to handle a
5136 given stream. Too many launches could indicate an inconsistency
5137 between our "launch a circuit to handle this stream" logic and our
5138 "attach this stream to one of the available circuits" logic.
5139 - Improve log messages related to excluded nodes.
5142 - Fix a spurious warning when moving from a short month to a long
5143 month on relays with month-based BandwidthAccounting. Bugfix on
5144 0.2.2.17-alpha; fixes bug 3020.
5145 - When a client finds that an origin circuit has run out of 16-bit
5146 stream IDs, we now mark it as unusable for new streams. Previously,
5147 we would try to close the entire circuit. Bugfix on 0.0.6.
5148 - Add a forgotten cast that caused a compile warning on OS X 10.6.
5149 Bugfix on 0.2.2.24-alpha.
5150 - Be more careful about reporting the correct error from a failed
5151 connect() system call. Under some circumstances, it was possible to
5152 look at an incorrect value for errno when sending the end reason.
5153 Bugfix on 0.1.0.1-rc.
5154 - Correctly handle an "impossible" overflow cases in connection byte
5155 counting, where we write or read more than 4GB on an edge connection
5156 in a single second. Bugfix on 0.1.2.8-beta.
5157 - Correct the warning displayed when a rendezvous descriptor exceeds
5158 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
5160 - Clients and hidden services now use HSDir-flagged relays for hidden
5161 service descriptor downloads and uploads even if the relays have no
5162 DirPort set and the client has disabled TunnelDirConns. This will
5163 eventually allow us to give the HSDir flag to relays with no
5164 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
5165 - Downgrade "no current certificates known for authority" message from
5166 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
5167 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
5168 2917. Bugfix on 0.1.1.1-alpha.
5169 - Only limit the lengths of single HS descriptors, even when multiple
5170 HS descriptors are published to an HSDir relay in a single POST
5171 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
5172 - Write the current time into the LastWritten line in our state file,
5173 rather than the time from the previous write attempt. Also, stop
5174 trying to use a time of -1 in our log statements. Fixes bug 3039;
5175 bugfix on 0.2.2.14-alpha.
5176 - Be more consistent in our treatment of file system paths. "~" should
5177 get expanded to the user's home directory in the Log config option.
5178 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
5179 feature for the -f and --DataDirectory options.
5182 - Make sure every relay writes a state file at least every 12 hours.
5183 Previously, a relay could go for weeks without writing its state
5184 file, and on a crash could lose its bandwidth history, capacity
5185 estimates, client country statistics, and so on. Addresses bug 3012.
5186 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
5187 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
5188 clients are already deprecated because of security bugs.
5189 - Don't allow v0 hidden service authorities to act as clients.
5190 Required by fix for bug 3000.
5191 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
5192 by fix for bug 3000.
5193 - Ensure that no empty [dirreq-](read|write)-history lines are added
5194 to an extrainfo document. Implements ticket 2497.
5196 o Code simplification and refactoring:
5197 - Remove workaround code to handle directory responses from servers
5198 that had bug 539 (they would send HTTP status 503 responses _and_
5199 send a body too). Since only server versions before
5200 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
5201 keep the workaround in place.
5202 - Remove the old 'fuzzy time' logic. It was supposed to be used for
5203 handling calculations where we have a known amount of clock skew and
5204 an allowed amount of unknown skew. But we only used it in three
5205 places, and we never adjusted the known/unknown skew values. This is
5206 still something we might want to do someday, but if we do, we'll
5207 want to do it differently.
5208 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
5209 None of the cases where we did this before were wrong, but by making
5210 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
5211 - Use GetTempDir to find the proper temporary directory location on
5212 Windows when generating temporary files for the unit tests. Patch by
5216 Changes in version 0.2.2.24-alpha - 2011-04-08
5217 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
5218 prevented Tor clients from effectively using "multihomed" bridges,
5219 that is, bridges that listen on multiple ports or IP addresses so users
5220 can continue to use some of their addresses even if others get blocked.
5223 - Fix a bug where bridge users who configure the non-canonical
5224 address of a bridge automatically switch to its canonical
5225 address. If a bridge listens at more than one address, it should be
5226 able to advertise those addresses independently and any non-blocked
5227 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
5229 - If you configured Tor to use bridge A, and then quit and
5230 configured Tor to use bridge B instead, it would happily continue
5231 to use bridge A if it's still reachable. While this behavior is
5232 a feature if your goal is connectivity, in some scenarios it's a
5233 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
5234 - Directory authorities now use data collected from their own
5235 uptime observations when choosing whether to assign the HSDir flag
5236 to relays, instead of trusting the uptime value the relay reports in
5237 its descriptor. This change helps prevent an attack where a small
5238 set of nodes with frequently-changing identity keys can blackhole
5239 a hidden service. (Only authorities need upgrade; others will be
5240 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
5243 - When we restart our relay, we might get a successful connection
5244 from the outside before we've started our reachability tests,
5245 triggering a warning: "ORPort found reachable, but I have no
5246 routerinfo yet. Failing to inform controller of success." This
5247 bug was harmless unless Tor is running under a controller
5248 like Vidalia, in which case the controller would never get a
5249 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
5251 - Make directory authorities more accurate at recording when
5252 relays that have failed several reachability tests became
5253 unreachable, so we can provide more accuracy at assigning Stable,
5254 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
5255 - Fix an issue that prevented static linking of libevent on
5256 some platforms (notably Linux). Fixes bug 2698; bugfix on
5257 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
5258 the --with-static-libevent configure option).
5259 - We now ask the other side of a stream (the client or the exit)
5260 for more data on that stream when the amount of queued data on
5261 that stream dips low enough. Previously, we wouldn't ask the
5262 other side for more data until either it sent us more data (which
5263 it wasn't supposed to do if it had exhausted its window!) or we
5264 had completely flushed all our queued data. This flow control fix
5265 should improve throughput. Fixes bug 2756; bugfix on the earliest
5266 released versions of Tor (svn commit r152).
5267 - Avoid a double-mark-for-free warning when failing to attach a
5268 transparent proxy connection. (We thought we had fixed this in
5269 0.2.2.23-alpha, but it turns out our fix was checking the wrong
5270 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
5271 bug) and 0.2.2.23-alpha (the incorrect fix).
5272 - When warning about missing zlib development packages during compile,
5273 give the correct package names. Bugfix on 0.2.0.1-alpha.
5276 - Directory authorities now log the source of a rejected POSTed v3
5278 - Make compilation with clang possible when using
5279 --enable-gcc-warnings by removing two warning options that clang
5280 hasn't implemented yet and by fixing a few warnings. Implements
5282 - When expiring circuits, use microsecond timers rather than
5283 one-second timers. This can avoid an unpleasant situation where a
5284 circuit is launched near the end of one second and expired right
5285 near the beginning of the next, and prevent fluctuations in circuit
5287 - Use computed circuit-build timeouts to decide when to launch
5288 parallel introduction circuits for hidden services. (Previously,
5289 we would retry after 15 seconds.)
5290 - Update to the April 1 2011 Maxmind GeoLite Country database.
5293 - Create the /var/run/tor directory on startup on OpenSUSE if it is
5294 not already created. Patch from Andreas Stieger. Fixes bug 2573.
5296 o Documentation changes:
5297 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
5298 - Resolve all doxygen warnings except those for missing documentation.
5300 - Add doxygen documentation for more functions, fields, and types.
5303 Changes in version 0.2.2.23-alpha - 2011-03-08
5304 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
5305 they restart they don't lose their bandwidth capacity estimate. This
5306 release also fixes a diverse set of user-facing bugs, ranging from
5307 relays overrunning their rate limiting to clients falsely warning about
5308 clock skew to bridge descriptor leaks by our bridge directory authority.
5311 - Stop sending a CLOCK_SKEW controller status event whenever
5312 we fetch directory information from a relay that has a wrong clock.
5313 Instead, only inform the controller when it's a trusted authority
5314 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5315 the rest of bug 1074.
5316 - Fix an assert in parsing router descriptors containing IPv6
5317 addresses. This one took down the directory authorities when
5318 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
5319 - Make the bridge directory authority refuse to answer directory
5320 requests for "all" descriptors. It used to include bridge
5321 descriptors in its answer, which was a major information leak.
5322 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
5323 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5324 Tor would ignore their RelayBandwidthBurst setting,
5325 potentially using more bandwidth than expected. Bugfix on
5326 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5327 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5328 hidserv" in her torrc. The 'hidserv' argument never controlled
5329 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5332 - Relays now save observed peak bandwidth throughput rates to their
5333 state file (along with total usage, which was already saved)
5334 so that they can determine their correct estimated bandwidth on
5335 restart. Resolves bug 1863, where Tor relays would reset their
5336 estimated bandwidth to 0 after restarting.
5337 - Directory authorities now take changes in router IP address and
5338 ORPort into account when determining router stability. Previously,
5339 if a router changed its IP or ORPort, the authorities would not
5340 treat it as having any downtime for the purposes of stability
5341 calculation, whereas clients would experience downtime since the
5342 change could take a while to propagate to them. Resolves issue 1035.
5343 - Enable Address Space Layout Randomization (ASLR) and Data Execution
5344 Prevention (DEP) by default on Windows to make it harder for
5345 attackers to exploit vulnerabilities. Patch from John Brooks.
5347 o Minor bugfixes (on 0.2.1.x and earlier):
5348 - Fix a rare crash bug that could occur when a client was configured
5349 with a large number of bridges. Fixes bug 2629; bugfix on
5350 0.2.1.2-alpha. Bugfix by trac user "shitlei".
5351 - Avoid a double mark-for-free warning when failing to attach a
5352 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
5354 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
5355 found by "cypherpunks". This bug was introduced before the first
5356 Tor release, in svn commit r110.
5357 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
5358 don't mention them in the manpage. Fixes bug 2450; issue
5359 spotted by keb and G-Lo.
5360 - Fix a bug in bandwidth history state parsing that could have been
5361 triggered if a future version of Tor ever changed the timing
5362 granularity at which bandwidth history is measured. Bugfix on
5364 - When a relay decides that its DNS is too broken for it to serve
5365 as an exit server, it advertised itself as a non-exit, but
5366 continued to act as an exit. This could create accidental
5367 partitioning opportunities for users. Instead, if a relay is
5368 going to advertise reject *:* as its exit policy, it should
5369 really act with exit policy "reject *:*". Fixes bug 2366.
5370 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
5371 - In the special case where you configure a public exit relay as your
5372 bridge, Tor would be willing to use that exit relay as the last
5373 hop in your circuit as well. Now we fail that circuit instead.
5374 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
5375 - Fix a bug with our locking implementation on Windows that couldn't
5376 correctly detect when a file was already locked. Fixes bug 2504,
5377 bugfix on 0.2.1.6-alpha.
5378 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
5379 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
5381 - Set target port in get_interface_address6() correctly. Bugfix
5382 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
5383 - Directory authorities are now more robust to hops back in time
5384 when calculating router stability. Previously, if a run of uptime
5385 or downtime appeared to be negative, the calculation could give
5386 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
5388 - Fix an assert that got triggered when using the TestingTorNetwork
5389 configuration option and then issuing a GETINFO config-text control
5390 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
5392 o Minor bugfixes (on 0.2.2.x):
5393 - Clients should not weight BadExit nodes as Exits in their node
5394 selection. Similarly, directory authorities should not count BadExit
5395 bandwidth as Exit bandwidth when computing bandwidth-weights.
5396 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
5397 - Correctly clear our dir_read/dir_write history when there is an
5398 error parsing any bw history value from the state file. Bugfix on
5400 - Resolve a bug in verifying signatures of directory objects
5401 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
5402 Fixes bug 2409. Found by "piebeer".
5403 - Bridge authorities no longer crash on SIGHUP when they try to
5404 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
5408 - Log less aggressively about circuit timeout changes, and improve
5409 some other circuit timeout messages. Resolves bug 2004.
5410 - Log a little more clearly about the times at which we're no longer
5411 accepting new connections. Resolves bug 2181.
5412 - Reject attempts at the client side to open connections to private
5413 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
5414 a randomly chosen exit node. Attempts to do so are always
5415 ill-defined, generally prevented by exit policies, and usually
5416 in error. This will also help to detect loops in transparent
5417 proxy configurations. You can disable this feature by setting
5418 "ClientRejectInternalAddresses 0" in your torrc.
5419 - Always treat failure to allocate an RSA key as an unrecoverable
5421 - Update to the March 1 2011 Maxmind GeoLite Country database.
5423 o Minor features (log subsystem):
5424 - Add documentation for configuring logging at different severities in
5425 different log domains. We've had this feature since 0.2.1.1-alpha,
5426 but for some reason it never made it into the manpage. Fixes
5428 - Make it simpler to specify "All log domains except for A and B".
5429 Previously you needed to say "[*,~A,~B]". Now you can just say
5431 - Add a "LogMessageDomains 1" option to include the domains of log
5432 messages along with the messages. Without this, there's no way
5433 to use log domains without reading the source or doing a lot
5436 o Packaging changes:
5437 - Stop shipping the Tor specs files and development proposal documents
5438 in the tarball. They are now in a separate git repository at
5439 git://git.torproject.org/torspec.git
5442 Changes in version 0.2.1.30 - 2011-02-23
5443 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
5444 change is a slight tweak to Tor's TLS handshake that makes relays
5445 and bridges that run this new version reachable from Iran again.
5446 We don't expect this tweak will win the arms race long-term, but it
5447 buys us time until we roll out a better solution.
5450 - Stop sending a CLOCK_SKEW controller status event whenever
5451 we fetch directory information from a relay that has a wrong clock.
5452 Instead, only inform the controller when it's a trusted authority
5453 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5454 the rest of bug 1074.
5455 - Fix a bounds-checking error that could allow an attacker to
5456 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5458 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5459 Tor would ignore their RelayBandwidthBurst setting,
5460 potentially using more bandwidth than expected. Bugfix on
5461 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5462 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5463 hidserv" in her torrc. The 'hidserv' argument never controlled
5464 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5467 - Adjust our TLS Diffie-Hellman parameters to match those used by
5469 - Update to the February 1 2011 Maxmind GeoLite Country database.
5472 - Check for and reject overly long directory certificates and
5473 directory tokens before they have a chance to hit any assertions.
5474 Bugfix on 0.2.1.28. Found by "doorss".
5475 - Bring the logic that gathers routerinfos and assesses the
5476 acceptability of circuits into line. This prevents a Tor OP from
5477 getting locked in a cycle of choosing its local OR as an exit for a
5478 path (due to a .exit request) and then rejecting the circuit because
5479 its OR is not listed yet. It also prevents Tor clients from using an
5480 OR running in the same instance as an exit (due to a .exit request)
5481 if the OR does not meet the same requirements expected of an OR
5482 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5484 o Packaging changes:
5485 - Stop shipping the Tor specs files and development proposal documents
5486 in the tarball. They are now in a separate git repository at
5487 git://git.torproject.org/torspec.git
5488 - Do not include Git version tags as though they are SVN tags when
5489 generating a tarball from inside a repository that has switched
5490 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
5493 Changes in version 0.2.2.22-alpha - 2011-01-25
5494 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
5495 main other change is a slight tweak to Tor's TLS handshake that makes
5496 relays and bridges that run this new version reachable from Iran again.
5497 We don't expect this tweak will win the arms race long-term, but it
5498 will buy us a bit more time until we roll out a better solution.
5501 - Fix a bounds-checking error that could allow an attacker to
5502 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5504 - Don't assert when changing from bridge to relay or vice versa
5505 via the controller. The assert happened because we didn't properly
5506 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
5507 bug 2433. Reported by bastik.
5510 - Adjust our TLS Diffie-Hellman parameters to match those used by
5512 - Provide a log message stating which geoip file we're parsing
5513 instead of just stating that we're parsing the geoip file.
5514 Implements ticket 2432.
5517 - Check for and reject overly long directory certificates and
5518 directory tokens before they have a chance to hit any assertions.
5519 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
5522 Changes in version 0.2.2.21-alpha - 2011-01-15
5523 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
5524 continues our recent code security audit work. The main fix resolves
5525 a remote heap overflow vulnerability that can allow remote code
5526 execution (CVE-2011-0427). Other fixes address a variety of assert
5527 and crash bugs, most of which we think are hard to exploit remotely.
5529 o Major bugfixes (security), also included in 0.2.1.29:
5530 - Fix a heap overflow bug where an adversary could cause heap
5531 corruption. This bug probably allows remote code execution
5532 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5534 - Prevent a denial-of-service attack by disallowing any
5535 zlib-compressed data whose compression factor is implausibly
5536 high. Fixes part of bug 2324; reported by "doorss".
5537 - Zero out a few more keys in memory before freeing them. Fixes
5538 bug 2384 and part of bug 2385. These key instances found by
5539 "cypherpunks", based on Andrew Case's report about being able
5540 to find sensitive data in Tor's memory space if you have enough
5541 permissions. Bugfix on 0.0.2pre9.
5543 o Major bugfixes (crashes), also included in 0.2.1.29:
5544 - Prevent calls to Libevent from inside Libevent log handlers.
5545 This had potential to cause a nasty set of crashes, especially
5546 if running Libevent with debug logging enabled, and running
5547 Tor with a controller watching for low-severity log messages.
5548 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5549 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5550 underflow errors there too. Fixes the other part of bug 2324.
5551 - Fix a bug where we would assert if we ever had a
5552 cached-descriptors.new file (or another file read directly into
5553 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5554 on 0.2.1.25. Found by doorss.
5555 - Fix some potential asserts and parsing issues with grossly
5556 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5559 o Minor bugfixes (other), also included in 0.2.1.29:
5560 - Fix a bug with handling misformed replies to reverse DNS lookup
5561 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5562 bug reported by doorss.
5563 - Fix compilation on mingw when a pthreads compatibility library
5564 has been installed. (We don't want to use it, so we shouldn't
5565 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5566 - Fix a bug where we would declare that we had run out of virtual
5567 addresses when the address space was only half-exhausted. Bugfix
5569 - Correctly handle the case where AutomapHostsOnResolve is set but
5570 no virtual addresses are available. Fixes bug 2328; bugfix on
5571 0.1.2.1-alpha. Bug found by doorss.
5572 - Correctly handle wrapping around when we run out of virtual
5573 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
5575 o Minor features, also included in 0.2.1.29:
5576 - Update to the January 1 2011 Maxmind GeoLite Country database.
5577 - Introduce output size checks on all of our decryption functions.
5579 o Build changes, also included in 0.2.1.29:
5580 - Tor does not build packages correctly with Automake 1.6 and earlier;
5581 added a check to Makefile.am to make sure that we're building with
5582 Automake 1.7 or later.
5583 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5584 because we built it with a too-old version of automake. Thus that
5585 release broke ./configure --enable-openbsd-malloc, which is popular
5586 among really fast exit relays on Linux.
5588 o Major bugfixes, new in 0.2.2.21-alpha:
5589 - Prevent crash/heap corruption when the cbtnummodes consensus
5590 parameter is set to 0 or large values. Fixes bug 2317; bugfix
5593 o Major features, new in 0.2.2.21-alpha:
5594 - Introduce minimum/maximum values that clients will believe
5595 from the consensus. Now we'll have a better chance to avoid crashes
5596 or worse when a consensus param has a weird value.
5598 o Minor features, new in 0.2.2.21-alpha:
5599 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
5600 used on bridges, and it makes bridge scanning somewhat easier.
5601 - If writing the state file to disk fails, wait up to an hour before
5602 retrying again, rather than trying again each second. Fixes bug
5603 2346; bugfix on Tor 0.1.1.3-alpha.
5604 - Make Libevent log messages get delivered to controllers later,
5605 and not from inside the Libevent log handler. This prevents unsafe
5606 reentrant Libevent calls while still letting the log messages
5608 - Detect platforms that brokenly use a signed size_t, and refuse to
5609 build there. Found and analyzed by doorss and rransom.
5610 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
5613 o Minor bugfixes, new in 0.2.2.21-alpha:
5614 - Handle SOCKS messages longer than 128 bytes long correctly, rather
5615 than waiting forever for them to finish. Fixes bug 2330; bugfix
5616 on 0.2.0.16-alpha. Found by doorss.
5617 - Add assertions to check for overflow in arguments to
5618 base32_encode() and base32_decode(); fix a signed-unsigned
5619 comparison there too. These bugs are not actually reachable in Tor,
5620 but it's good to prevent future errors too. Found by doorss.
5621 - Correctly detect failures to create DNS requests when using Libevent
5622 versions before v2. (Before Libevent 2, we used our own evdns
5623 implementation. Its return values for Libevent's evdns_resolve_*()
5624 functions are not consistent with those from Libevent.) Fixes bug
5625 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
5627 o Documentation, new in 0.2.2.21-alpha:
5628 - Document the default socks host and port (127.0.0.1:9050) for
5632 Changes in version 0.2.1.29 - 2011-01-15
5633 Tor 0.2.1.29 continues our recent code security audit work. The main
5634 fix resolves a remote heap overflow vulnerability that can allow remote
5635 code execution. Other fixes address a variety of assert and crash bugs,
5636 most of which we think are hard to exploit remotely.
5638 o Major bugfixes (security):
5639 - Fix a heap overflow bug where an adversary could cause heap
5640 corruption. This bug probably allows remote code execution
5641 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5643 - Prevent a denial-of-service attack by disallowing any
5644 zlib-compressed data whose compression factor is implausibly
5645 high. Fixes part of bug 2324; reported by "doorss".
5646 - Zero out a few more keys in memory before freeing them. Fixes
5647 bug 2384 and part of bug 2385. These key instances found by
5648 "cypherpunks", based on Andrew Case's report about being able
5649 to find sensitive data in Tor's memory space if you have enough
5650 permissions. Bugfix on 0.0.2pre9.
5652 o Major bugfixes (crashes):
5653 - Prevent calls to Libevent from inside Libevent log handlers.
5654 This had potential to cause a nasty set of crashes, especially
5655 if running Libevent with debug logging enabled, and running
5656 Tor with a controller watching for low-severity log messages.
5657 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5658 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5659 underflow errors there too. Fixes the other part of bug 2324.
5660 - Fix a bug where we would assert if we ever had a
5661 cached-descriptors.new file (or another file read directly into
5662 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5663 on 0.2.1.25. Found by doorss.
5664 - Fix some potential asserts and parsing issues with grossly
5665 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5668 o Minor bugfixes (other):
5669 - Fix a bug with handling misformed replies to reverse DNS lookup
5670 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5671 bug reported by doorss.
5672 - Fix compilation on mingw when a pthreads compatibility library
5673 has been installed. (We don't want to use it, so we shouldn't
5674 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5675 - Fix a bug where we would declare that we had run out of virtual
5676 addresses when the address space was only half-exhausted. Bugfix
5678 - Correctly handle the case where AutomapHostsOnResolve is set but
5679 no virtual addresses are available. Fixes bug 2328; bugfix on
5680 0.1.2.1-alpha. Bug found by doorss.
5681 - Correctly handle wrapping around to when we run out of virtual
5682 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
5683 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5684 because we built it with a too-old version of automake. Thus that
5685 release broke ./configure --enable-openbsd-malloc, which is popular
5686 among really fast exit relays on Linux.
5689 - Update to the January 1 2011 Maxmind GeoLite Country database.
5690 - Introduce output size checks on all of our decryption functions.
5693 - Tor does not build packages correctly with Automake 1.6 and earlier;
5694 added a check to Makefile.am to make sure that we're building with
5695 Automake 1.7 or later.
5698 Changes in version 0.2.2.20-alpha - 2010-12-17
5699 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
5700 exploitable bugs. We also fix a variety of other significant bugs,
5701 change the IP address for one of our directory authorities, and update
5702 the minimum version that Tor relays must run to join the network.
5705 - Fix a remotely exploitable bug that could be used to crash instances
5706 of Tor remotely by overflowing on the heap. Remote-code execution
5707 hasn't been confirmed, but can't be ruled out. Everyone should
5708 upgrade. Bugfix on the 0.1.1 series and later.
5709 - Fix a bug that could break accounting on 64-bit systems with large
5710 time_t values, making them hibernate for impossibly long intervals.
5711 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
5712 - Fix a logic error in directory_fetches_from_authorities() that
5713 would cause all _non_-exits refusing single-hop-like circuits
5714 to fetch from authorities, when we wanted to have _exits_ fetch
5715 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
5717 - Fix a stream fairness bug that would cause newer streams on a given
5718 circuit to get preference when reading bytes from the origin or
5719 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
5720 introduced before the first Tor release, in svn revision r152.
5722 o Directory authority changes:
5723 - Change IP address and ports for gabelmoo (v3 directory authority).
5726 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
5727 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
5728 - Fix an off-by-one error in calculating some controller command
5729 argument lengths. Fortunately, this mistake is harmless since
5730 the controller code does redundant NUL termination too. Found by
5731 boboper. Bugfix on 0.1.1.1-alpha.
5732 - Do not dereference NULL if a bridge fails to build its
5733 extra-info descriptor. Found by an anonymous commenter on
5734 Trac. Bugfix on 0.2.2.19-alpha.
5737 - Update to the December 1 2010 Maxmind GeoLite Country database.
5738 - Directory authorities now reject relays running any versions of
5739 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
5740 known bugs that keep RELAY_EARLY cells from working on rendezvous
5741 circuits. Followup to fix for bug 2081.
5742 - Directory authorities now reject relays running any version of Tor
5743 older than 0.2.0.26-rc. That version is the earliest that fetches
5744 current directory information correctly. Fixes bug 2156.
5745 - Report only the top 10 ports in exit-port stats in order not to
5746 exceed the maximum extra-info descriptor length of 50 KB. Implements
5750 Changes in version 0.2.1.28 - 2010-12-17
5751 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
5752 exploitable bugs. We also took this opportunity to change the IP address
5753 for one of our directory authorities, and to update the geoip database
5757 - Fix a remotely exploitable bug that could be used to crash instances
5758 of Tor remotely by overflowing on the heap. Remote-code execution
5759 hasn't been confirmed, but can't be ruled out. Everyone should
5760 upgrade. Bugfix on the 0.1.1 series and later.
5762 o Directory authority changes:
5763 - Change IP address and ports for gabelmoo (v3 directory authority).
5766 - Update to the December 1 2010 Maxmind GeoLite Country database.
5769 Changes in version 0.2.1.27 - 2010-11-23
5770 Yet another OpenSSL security patch broke its compatibility with Tor:
5771 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
5772 also took this opportunity to fix several crash bugs, integrate a new
5773 directory authority, and update the bundled GeoIP database.
5776 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5777 No longer set the tlsext_host_name extension on server SSL objects;
5778 but continue to set it on client SSL objects. Our goal in setting
5779 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5780 bugfix on 0.2.1.1-alpha.
5781 - Do not log messages to the controller while shrinking buffer
5782 freelists. Doing so would sometimes make the controller connection
5783 try to allocate a buffer chunk, which would mess up the internals
5784 of the freelist and cause an assertion failure. Fixes bug 1125;
5785 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5786 - Learn our external IP address when we're a relay or bridge, even if
5787 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5788 where we introduced bridge relays that don't need to publish to
5789 be useful. Fixes bug 2050.
5790 - Do even more to reject (and not just ignore) annotations on
5791 router descriptors received anywhere but from the cache. Previously
5792 we would ignore such annotations at first, but cache them to disk
5793 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5794 - When you're using bridges and your network goes away and your
5795 bridges get marked as down, recover when you attempt a new socks
5796 connection (if the network is back), rather than waiting up to an
5797 hour to try fetching new descriptors for your bridges. Bugfix on
5798 0.2.0.3-alpha; fixes bug 1981.
5801 - Move to the November 2010 Maxmind GeoLite country db (rather
5802 than the June 2009 ip-to-country GeoIP db) for our statistics that
5803 count how many users relays are seeing from each country. Now we'll
5804 have more accurate data, especially for many African countries.
5806 o New directory authorities:
5807 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
5811 - Fix an assertion failure that could occur in directory caches or
5812 bridge users when using a very short voting interval on a testing
5813 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
5815 - Enforce multiplicity rules when parsing annotations. Bugfix on
5816 0.2.0.8-alpha. Found by piebeer.
5817 - Allow handshaking OR connections to take a full KeepalivePeriod
5818 seconds to handshake. Previously, we would close them after
5819 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
5820 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
5822 - When building with --enable-gcc-warnings on OpenBSD, disable
5823 warnings in system headers. This makes --enable-gcc-warnings
5824 pass on OpenBSD 4.8.
5827 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
5828 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
5829 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
5830 Servers can start sending this code when enough clients recognize
5831 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
5832 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
5833 Patch from mingw-san.
5836 - Remove the old debian/ directory from the main Tor distribution.
5837 The official Tor-for-debian git repository lives at the URL
5838 https://git.torproject.org/debian/tor.git
5839 - Stop shipping the old doc/website/ directory in the tarball. We
5840 changed the website format in late 2010, and what we shipped in
5841 0.2.1.26 really wasn't that useful anyway.
5844 Changes in version 0.2.2.19-alpha - 2010-11-22
5845 Yet another OpenSSL security patch broke its compatibility with Tor:
5846 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
5849 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5850 No longer set the tlsext_host_name extension on server SSL objects;
5851 but continue to set it on client SSL objects. Our goal in setting
5852 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5853 bugfix on 0.2.1.1-alpha.
5856 - Try harder not to exceed the maximum length of 50 KB when writing
5857 statistics to extra-info descriptors. This bug was triggered by very
5858 fast relays reporting exit-port, entry, and dirreq statistics.
5859 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
5860 - Publish a router descriptor even if generating an extra-info
5861 descriptor fails. Previously we would not publish a router
5862 descriptor without an extra-info descriptor; this can cause fast
5863 exit relays collecting exit-port statistics to drop from the
5864 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
5867 Changes in version 0.2.2.18-alpha - 2010-11-16
5868 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
5869 us lately, makes unpublished bridge relays able to detect their IP
5870 address, and fixes a wide variety of other bugs to get us much closer
5871 to a stable release.
5874 - Do even more to reject (and not just ignore) annotations on
5875 router descriptors received anywhere but from the cache. Previously
5876 we would ignore such annotations at first, but cache them to disk
5877 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5878 - Do not log messages to the controller while shrinking buffer
5879 freelists. Doing so would sometimes make the controller connection
5880 try to allocate a buffer chunk, which would mess up the internals
5881 of the freelist and cause an assertion failure. Fixes bug 1125;
5882 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5883 - Learn our external IP address when we're a relay or bridge, even if
5884 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5885 where we introduced bridge relays that don't need to publish to
5886 be useful. Fixes bug 2050.
5887 - Maintain separate TLS contexts and certificates for incoming and
5888 outgoing connections in bridge relays. Previously we would use the
5889 same TLS contexts and certs for incoming and outgoing connections.
5890 Bugfix on 0.2.0.3-alpha; addresses bug 988.
5891 - Maintain separate identity keys for incoming and outgoing TLS
5892 contexts in bridge relays. Previously we would use the same
5893 identity keys for incoming and outgoing TLS contexts. Bugfix on
5894 0.2.0.3-alpha; addresses the other half of bug 988.
5895 - Avoid an assertion failure when we as an authority receive a
5896 duplicate upload of a router descriptor that we already have,
5897 but which we previously considered an obsolete descriptor.
5898 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
5899 - Avoid a crash bug triggered by looking at a dangling pointer while
5900 setting the network status consensus. Found by Robert Ransom.
5901 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
5902 - Fix a logic error where servers that _didn't_ act as exits would
5903 try to keep their server lists more aggressively up to date than
5904 exits, when it was supposed to be the other way around. Bugfix
5907 o Minor bugfixes (on Tor 0.2.1.x and earlier):
5908 - When we're trying to guess whether we know our IP address as
5909 a relay, we would log various ways that we failed to guess
5910 our address, but never log that we ended up guessing it
5911 successfully. Now add a log line to help confused and anxious
5912 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
5913 - Bring the logic that gathers routerinfos and assesses the
5914 acceptability of circuits into line. This prevents a Tor OP from
5915 getting locked in a cycle of choosing its local OR as an exit for a
5916 path (due to a .exit request) and then rejecting the circuit because
5917 its OR is not listed yet. It also prevents Tor clients from using an
5918 OR running in the same instance as an exit (due to a .exit request)
5919 if the OR does not meet the same requirements expected of an OR
5920 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5921 - Correctly describe errors that occur when generating a TLS object.
5922 Previously we would attribute them to a failure while generating a
5923 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
5925 - Enforce multiplicity rules when parsing annotations. Bugfix on
5926 0.2.0.8-alpha. Found by piebeer.
5927 - Fix warnings that newer versions of autoconf produced during
5928 ./autogen.sh. These warnings appear to be harmless in our case,
5929 but they were extremely verbose. Fixes bug 2020.
5931 o Minor bugfixes (on Tor 0.2.2.x):
5932 - Enable protection of small arrays whenever we build with gcc
5933 hardening features, not only when also building with warnings
5934 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
5937 - Make hidden services work better in private Tor networks by not
5938 requiring any uptime to join the hidden service descriptor
5939 DHT. Implements ticket 2088.
5940 - Rate-limit the "your application is giving Tor only an IP address"
5941 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
5942 - When AllowSingleHopExits is set, print a warning to explain to the
5943 relay operator why most clients are avoiding her relay.
5944 - Update to the November 1 2010 Maxmind GeoLite Country database.
5946 o Code simplifications and refactoring:
5947 - When we fixed bug 1038 we had to put in a restriction not to send
5948 RELAY_EARLY cells on rend circuits. This was necessary as long
5949 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
5950 active. Now remove this obsolete check. Resolves bug 2081.
5951 - Some options used different conventions for uppercasing of acronyms
5952 when comparing manpage and source. Fix those in favor of the
5953 manpage, as it makes sense to capitalize acronyms.
5954 - Remove the torrc.complete file. It hasn't been kept up to date
5955 and users will have better luck checking out the manpage.
5956 - Remove the obsolete "NoPublish" option; it has been flagged
5957 as obsolete and has produced a warning since 0.1.1.18-rc.
5958 - Remove everything related to building the expert bundle for OS X.
5959 It has confused many users, doesn't work right on OS X 10.6,
5960 and is hard to get rid of once installed. Resolves bug 1274.
5963 Changes in version 0.2.2.17-alpha - 2010-09-30
5964 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
5965 to use one-hop circuits (which can put the exit relays at higher risk,
5966 plus unbalance the network); fixes a big bug in bandwidth accounting
5967 for relays that want to limit their monthly bandwidth use; fixes a
5968 big pile of bugs in how clients tolerate temporary network failure;
5969 and makes our adaptive circuit build timeout feature (which improves
5970 client performance if your network is fast while not breaking things
5971 if your network is slow) better handle bad networks.
5974 - Exit relays now try harder to block exit attempts from unknown
5975 relays, to make it harder for people to use them as one-hop proxies
5976 a la tortunnel. Controlled by the refuseunknownexits consensus
5977 parameter (currently enabled), or you can override it on your
5978 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
5980 o Major bugfixes (0.2.1.x and earlier):
5981 - Fix a bug in bandwidth accounting that could make us use twice
5982 the intended bandwidth when our interval start changes due to
5983 daylight saving time. Now we tolerate skew in stored vs computed
5984 interval starts: if the start of the period changes by no more than
5985 50% of the period's duration, we remember bytes that we transferred
5986 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
5987 - Always search the Windows system directory for system DLLs, and
5988 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
5989 - When you're using bridges and your network goes away and your
5990 bridges get marked as down, recover when you attempt a new socks
5991 connection (if the network is back), rather than waiting up to an
5992 hour to try fetching new descriptors for your bridges. Bugfix on
5993 0.2.0.3-alpha; fixes bug 1981.
5995 o Major bugfixes (on 0.2.2.x):
5996 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
5998 - Fix a segfault that could happen when operating a bridge relay with
5999 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
6000 - The consensus bandwidth-weights (used by clients to choose fast
6001 relays) entered an unexpected edge case in September where
6002 Exits were much scarcer than Guards, resulting in bad weight
6003 recommendations. Now we compute them using new constraints that
6004 should succeed in all cases. Also alter directory authorities to
6005 not include the bandwidth-weights line if they fail to produce
6006 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
6007 - When weighting bridges during path selection, we used to trust
6008 the bandwidths they provided in their descriptor, only capping them
6009 at 10MB/s. This turned out to be problematic for two reasons:
6010 Bridges could claim to handle a lot more traffic then they
6011 actually would, thus making more clients pick them and have a
6012 pretty effective DoS attack. The other issue is that new bridges
6013 that might not have a good estimate for their bw capacity yet
6014 would not get used at all unless no other bridges are available
6015 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
6017 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
6018 - Ignore cannibalized circuits when recording circuit build times.
6019 This should provide for a minor performance improvement for hidden
6020 service users using 0.2.2.14-alpha, and should remove two spurious
6021 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
6022 - Simplify the logic that causes us to decide if the network is
6023 unavailable for purposes of recording circuit build times. If we
6024 receive no cells whatsoever for the entire duration of a circuit's
6025 full measured lifetime, the network is probably down. Also ignore
6026 one-hop directory fetching circuit timeouts when calculating our
6027 circuit build times. These changes should hopefully reduce the
6028 cases where we see ridiculous circuit build timeouts for people
6029 with spotty wireless connections. Fixes part of bug 1772; bugfix
6031 - Prevent the circuit build timeout from becoming larger than
6032 the maximum build time we have ever seen. Also, prevent the time
6033 period for measurement circuits from becoming larger than twice that
6034 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
6037 - When we run out of directory information such that we can't build
6038 circuits, but then get enough that we can build circuits, log when
6039 we actually construct a circuit, so the user has a better chance of
6040 knowing what's going on. Fixes bug 1362.
6041 - Be more generous with how much bandwidth we'd use up (with
6042 accounting enabled) before entering "soft hibernation". Previously,
6043 we'd refuse new connections and circuits once we'd used up 95% of
6044 our allotment. Now, we use up 95% of our allotment, AND make sure
6045 that we have no more than 500MB (or 3 hours of expected traffic,
6046 whichever is lower) remaining before we enter soft hibernation.
6047 - If we've configured EntryNodes and our network goes away and/or all
6048 our entrynodes get marked down, optimistically retry them all when
6049 a new socks application request appears. Fixes bug 1882.
6050 - Add some more defensive programming for architectures that can't
6051 handle unaligned integer accesses. We don't know of any actual bugs
6052 right now, but that's the best time to fix them. Fixes bug 1943.
6053 - Support line continuations in the torrc config file. If a line
6054 ends with a single backslash character, the newline is ignored, and
6055 the configuration value is treated as continuing on the next line.
6058 o Minor bugfixes (on 0.2.1.x and earlier):
6059 - For bandwidth accounting, calculate our expected bandwidth rate
6060 based on the time during which we were active and not in
6061 soft-hibernation during the last interval. Previously, we were
6062 also considering the time spent in soft-hibernation. If this
6063 was a long time, we would wind up underestimating our bandwidth
6064 by a lot, and skewing our wakeup time towards the start of the
6065 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
6067 o Minor bugfixes (on 0.2.2.x):
6068 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
6069 which were disabled by the circuit build timeout changes in
6070 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
6071 - Make sure we don't warn about missing bandwidth weights when
6072 choosing bridges or other relays not in the consensus. Bugfix on
6073 0.2.2.10-alpha; fixes bug 1805.
6074 - In our logs, do not double-report signatures from unrecognized
6075 authorities both as "from unknown authority" and "not
6076 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
6079 Changes in version 0.2.2.16-alpha - 2010-09-17
6080 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
6081 evident at exit relays), and also continues to resolve all the little
6082 bugs that have been filling up trac lately.
6084 o Major bugfixes (stream-level fairness):
6085 - When receiving a circuit-level SENDME for a blocked circuit, try
6086 to package cells fairly from all the streams that had previously
6087 been blocked on that circuit. Previously, we had started with the
6088 oldest stream, and allowed each stream to potentially exhaust
6089 the circuit's package window. This gave older streams on any
6090 given circuit priority over newer ones. Fixes bug 1937. Detected
6091 originally by Camilo Viecco. This bug was introduced before the
6092 first Tor release, in svn commit r152: it is the new winner of
6093 the longest-lived bug prize.
6094 - When the exit relay got a circuit-level sendme cell, it started
6095 reading on the exit streams, even if had 500 cells queued in the
6096 circuit queue already, so the circuit queue just grew and grew in
6097 some cases. We fix this by not re-enabling reading on receipt of a
6098 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
6099 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
6101 - Newly created streams were allowed to read cells onto circuits,
6102 even if the circuit's cell queue was blocked and waiting to drain.
6103 This created potential unfairness, as older streams would be
6104 blocked, but newer streams would gladly fill the queue completely.
6105 We add code to detect this situation and prevent any stream from
6106 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
6110 - Update to the September 1 2010 Maxmind GeoLite Country database.
6111 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
6112 not. This would lead to a cookie that is still not group readable.
6113 Closes bug 1843. Suggested by katmagic.
6114 - When logging a rate-limited warning, we now mention how many messages
6115 got suppressed since the last warning.
6116 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
6117 do individual connection-level rate limiting of clients. The torrc
6118 config options with the same names trump the consensus params, if
6119 both are present. Replaces the old "bwconnrate" and "bwconnburst"
6120 consensus params which were broken from 0.2.2.7-alpha through
6121 0.2.2.14-alpha. Closes bug 1947.
6122 - When a router changes IP address or port, authorities now launch
6123 a new reachability test for it. Implements ticket 1899.
6124 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
6125 2 no signature, 4 required" messages about consensus signatures
6126 easier to read, and make sure they get logged at the same severity
6127 as the messages explaining which keys are which. Fixes bug 1290.
6128 - Don't warn when we have a consensus that we can't verify because
6129 of missing certificates, unless those certificates are ones
6130 that we have been trying and failing to download. Fixes bug 1145.
6131 - If you configure your bridge with a known identity fingerprint,
6132 and the bridge authority is unreachable (as it is in at least
6133 one country now), fall back to directly requesting the descriptor
6134 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
6136 - When building with --enable-gcc-warnings on OpenBSD, disable
6137 warnings in system headers. This makes --enable-gcc-warnings
6138 pass on OpenBSD 4.8.
6140 o Minor bugfixes (on 0.2.1.x and earlier):
6141 - Authorities will now attempt to download consensuses if their
6142 own efforts to make a live consensus have failed. This change
6143 means authorities that restart will fetch a valid consensus, and
6144 it means authorities that didn't agree with the current consensus
6145 will still fetch and serve it if it has enough signatures. Bugfix
6146 on 0.2.0.9-alpha; fixes bug 1300.
6147 - Ensure DNS requests launched by "RESOLVE" commands from the
6148 controller respect the __LeaveStreamsUnattached setconf options. The
6149 same goes for requests launched via DNSPort or transparent
6150 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
6151 - Allow handshaking OR connections to take a full KeepalivePeriod
6152 seconds to handshake. Previously, we would close them after
6153 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
6154 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
6156 - Rate-limit "Failed to hand off onionskin" warnings.
6157 - Never relay a cell for a circuit we have already destroyed.
6158 Between marking a circuit as closeable and finally closing it,
6159 it may have been possible for a few queued cells to get relayed,
6160 even though they would have been immediately dropped by the next
6161 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
6162 - Never queue a cell for a circuit that's already been marked
6164 - Never vote for a server as "Running" if we have a descriptor for
6165 it claiming to be hibernating, and that descriptor was published
6166 more recently than our last contact with the server. Bugfix on
6167 0.2.0.3-alpha; fixes bug 911.
6168 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
6171 o Minor bugfixes (on 0.2.2.x):
6172 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
6173 down if a directory fetch fails and you've configured either
6174 bridges or EntryNodes. The intent was to mark the relay as down
6175 _unless_ you're using bridges or EntryNodes, since if you are
6176 then you could quickly run out of entry points.
6177 - Fix the Windows directory-listing code. A bug introduced in
6178 0.2.2.14-alpha could make Windows directory servers forget to load
6179 some of their cached v2 networkstatus files.
6180 - Really allow clients to use relays as bridges. Fixes bug 1776;
6181 bugfix on 0.2.2.15-alpha.
6182 - Demote a warn to info that happens when the CellStatistics option
6183 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
6184 Reported by Moritz Bartl.
6185 - On Windows, build correctly either with or without Unicode support.
6186 This is necessary so that Tor can support fringe platforms like
6187 Windows 98 (which has no Unicode), or Windows CE (which has no
6188 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
6191 - Add a unit test for cross-platform directory-listing code.
6194 Changes in version 0.2.2.15-alpha - 2010-08-18
6195 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
6196 fixes a variety of other bugs that were preventing performance
6197 experiments from moving forward, fixes several bothersome memory leaks,
6198 and generally closes a lot of smaller bugs that have been filling up
6202 - Stop assigning the HSDir flag to relays that disable their
6203 DirPort (and thus will refuse to answer directory requests). This
6204 fix should dramatically improve the reachability of hidden services:
6205 hidden services and hidden service clients pick six HSDir relays
6206 to store and retrieve the hidden service descriptor, and currently
6207 about half of the HSDir relays will refuse to work. Bugfix on
6208 0.2.0.10-alpha; fixes part of bug 1693.
6209 - The PerConnBWRate and Burst config options, along with the
6210 bwconnrate and bwconnburst consensus params, initialized each conn's
6211 token bucket values only when the connection is established. Now we
6212 update them if the config options change, and update them every time
6213 we get a new consensus. Otherwise we can encounter an ugly edge
6214 case where we initialize an OR conn to client-level bandwidth,
6215 but then later the relay joins the consensus and we leave it
6216 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
6217 - Fix a regression that caused Tor to rebind its ports if it receives
6218 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
6221 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
6222 should give us approximately 40-50% more Guard-flagged nodes,
6223 improving the anonymity the Tor network can provide and also
6224 decreasing the dropoff in throughput that relays experience when
6225 they first get the Guard flag.
6226 - Allow enabling or disabling the *Statistics config options while
6230 - Update to the August 1 2010 Maxmind GeoLite Country database.
6231 - Have the controller interface give a more useful message than
6232 "Internal Error" in response to failed GETINFO requests.
6233 - Warn when the same option is provided more than once in a torrc
6234 file, on the command line, or in a single SETCONF statement, and
6235 the option is one that only accepts a single line. Closes bug 1384.
6236 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
6237 Patch from mingw-san.
6238 - Add support for the country code "{??}" in torrc options like
6239 ExcludeNodes, to indicate all routers of unknown country. Closes
6241 - Relays report the number of bytes spent on answering directory
6242 requests in extra-info descriptors similar to {read,write}-history.
6243 Implements enhancement 1790.
6245 o Minor bugfixes (on 0.2.1.x and earlier):
6246 - Complain if PublishServerDescriptor is given multiple arguments that
6247 include 0 or 1. This configuration will be rejected in the future.
6248 Bugfix on 0.2.0.1-alpha; closes bug 1107.
6249 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
6250 Bugfix on 0.2.0.13-alpha; closes bug 928.
6251 - Change "Application request when we're believed to be offline."
6252 notice to "Application request when we haven't used client
6253 functionality lately.", to clarify that it's not an error. Bugfix
6254 on 0.0.9.3; fixes bug 1222.
6255 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
6256 would return "551 Internal error" rather than "552 Unrecognized key
6257 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
6258 - Users can't configure a regular relay to be their bridge. It didn't
6259 work because when Tor fetched the bridge descriptor, it found
6260 that it already had it, and didn't realize that the purpose of the
6261 descriptor had changed. Now we replace routers with a purpose other
6262 than bridge with bridge descriptors when fetching them. Bugfix on
6263 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
6264 refetch the descriptor with router purpose 'general', disabling
6266 - Fix a rare bug in rend_fn unit tests: we would fail a test when
6267 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
6268 on 0.2.0.10-alpha; fixes bug 1808.
6269 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
6270 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
6271 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
6272 Servers can start sending this code when enough clients recognize
6273 it. Also update the spec to reflect this new reason. Bugfix on
6274 0.1.0.1-rc; fixes part of bug 1793.
6275 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
6276 when we switch from being a public relay to a bridge. Otherwise
6277 there will still be clients that see the relay in their consensus,
6278 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
6280 - Instead of giving an assertion failure on an internal mismatch
6281 on estimated freelist size, just log a BUG warning and try later.
6282 Mitigates but does not fix bug 1125.
6283 - Fix an assertion failure that could occur in caches or bridge users
6284 when using a very short voting interval on a testing network.
6285 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
6287 o Minor bugfixes (on 0.2.2.x):
6288 - Alter directory authorities to always consider Exit-flagged nodes
6289 as potential Guard nodes in their votes. The actual decision to
6290 use Exits as Guards is done in the consensus bandwidth weights.
6291 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
6292 - When the controller is reporting the purpose of circuits that
6293 didn't finish building before the circuit build timeout, it was
6294 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
6295 - Our libevent version parsing code couldn't handle versions like
6296 1.4.14b-stable and incorrectly warned the user about using an
6297 old and broken version of libevent. Treat 1.4.14b-stable like
6298 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
6300 - Don't use substitution references like $(VAR:MOD) when
6301 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
6302 '$(:x)' to 'x' rather than the empty string. This bites us in
6303 doc/ when configured with --disable-asciidoc. Bugfix on
6304 0.2.2.9-alpha; fixes bug 1773.
6305 - Remove a spurious hidden service server-side log notice about
6306 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
6308 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
6310 - Correctly report written bytes on linked connections. Found while
6311 implementing 1790. Bugfix on 0.2.2.4-alpha.
6312 - Fix three memory leaks: one in circuit_build_times_parse_state(),
6313 one in dirvote_add_signatures_to_pending_consensus(), and one every
6314 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
6315 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
6317 o Code simplifications and refactoring:
6318 - Take a first step towards making or.h smaller by splitting out
6319 function definitions for all source files in src/or/. Leave
6320 structures and defines in or.h for now.
6321 - Remove a bunch of unused function declarations as well as a block of
6322 #if 0'd code from the unit tests. Closes bug 1824.
6323 - New unit tests for exit-port history statistics; refactored exit
6324 statistics code to be more easily tested.
6325 - Remove the old debian/ directory from the main Tor distribution.
6326 The official Tor-for-debian git repository lives at the URL
6327 https://git.torproject.org/debian/tor.git
6330 Changes in version 0.2.2.14-alpha - 2010-07-12
6331 Tor 0.2.2.14-alpha greatly improves client-side handling of
6332 circuit build timeouts, which are used to estimate speed and improve
6333 performance. We also move to a much better GeoIP database, port Tor to
6334 Windows CE, introduce new compile flags that improve code security,
6335 add an eighth v3 directory authority, and address a lot of more
6339 - Tor directory authorities no longer crash when started with a
6340 cached-microdesc-consensus file in their data directory. Bugfix
6341 on 0.2.2.6-alpha; fixes bug 1532.
6342 - Treat an unset $HOME like an empty $HOME rather than triggering an
6343 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
6344 - Ignore negative and large circuit build timeout values that can
6345 happen during a suspend or hibernate. These values caused various
6346 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
6347 - Alter calculation of Pareto distribution parameter 'Xm' for
6348 Circuit Build Timeout learning to use the weighted average of the
6349 top N=3 modes (because we have three entry guards). Considering
6350 multiple modes should improve the timeout calculation in some cases,
6351 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
6353 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
6354 right censored distribution model. This approach improves over the
6355 synthetic timeout generation approach that was producing insanely
6356 high timeout values. Now we calculate build timeouts using truncated
6357 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
6358 - Do not close circuits that are under construction when they reach
6359 the circuit build timeout. Instead, leave them building (but do not
6360 use them) for up until the time corresponding to the 95th percentile
6361 on the Pareto CDF or 60 seconds, whichever is greater. This is done
6362 to provide better data for the new Pareto model. This percentile
6363 can be controlled by the consensus.
6366 - Move to the June 2010 Maxmind GeoLite country db (rather than the
6367 June 2009 ip-to-country GeoIP db) for our statistics that count
6368 how many users relays are seeing from each country. Now we have
6369 more accurate data for many African countries.
6370 - Port Tor to build and run correctly on Windows CE systems, using
6371 the wcecompat library. Contributed by Valerio Lupi.
6372 - New "--enable-gcc-hardening" ./configure flag (off by default)
6373 to turn on gcc compile time hardening options. It ensures
6374 that signed ints have defined behavior (-fwrapv), enables
6375 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
6376 with canaries (-fstack-protector-all), turns on ASLR protection if
6377 supported by the kernel (-fPIE, -pie), and adds additional security
6378 related warnings. Verified to work on Mac OS X and Debian Lenny.
6379 - New "--enable-linker-hardening" ./configure flag (off by default)
6380 to turn on ELF specific hardening features (relro, now). This does
6381 not work with Mac OS X or any other non-ELF binary format.
6383 o New directory authorities:
6384 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
6388 - New config option "WarnUnsafeSocks 0" disables the warning that
6389 occurs whenever Tor receives a socks handshake using a version of
6390 the socks protocol that can only provide an IP address (rather
6391 than a hostname). Setups that do DNS locally over Tor are fine,
6392 and we shouldn't spam the logs in that case.
6393 - Convert the HACKING file to asciidoc, and add a few new sections
6394 to it, explaining how we use Git, how we make changelogs, and
6395 what should go in a patch.
6396 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
6397 event, to give information on the current rate of circuit timeouts
6398 over our stored history.
6399 - Add ability to disable circuit build time learning via consensus
6400 parameter and via a LearnCircuitBuildTimeout config option. Also
6401 automatically disable circuit build time calculation if we are
6402 either a AuthoritativeDirectory, or if we fail to write our state
6403 file. Fixes bug 1296.
6404 - More gracefully handle corrupt state files, removing asserts
6405 in favor of saving a backup and resetting state.
6406 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
6410 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
6412 - When a2x fails, mention that the user could disable manpages instead
6413 of trying to fix their asciidoc installation.
6414 - Where available, use Libevent 2.0's periodic timers so that our
6415 once-per-second cleanup code gets called even more closely to
6416 once per second than it would otherwise. Fixes bug 943.
6417 - If you run a bridge that listens on multiple IP addresses, and
6418 some user configures a bridge address that uses a different IP
6419 address than your bridge writes in its router descriptor, and the
6420 user doesn't specify an identity key, their Tor would discard the
6421 descriptor because "it isn't one of our configured bridges", and
6422 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
6423 Bugfix on 0.2.0.3-alpha.
6424 - If OpenSSL fails to make a duplicate of a private or public key, log
6425 an error message and try to exit cleanly. May help with debugging
6426 if bug 1209 ever remanifests.
6427 - Save a couple bytes in memory allocation every time we escape
6428 certain characters in a string. Patch from Florian Zumbiehl.
6429 - Make it explicit that we don't cannibalize one-hop circuits. This
6430 happens in the wild, but doesn't turn out to be a problem because
6431 we fortunately don't use those circuits. Many thanks to outofwords
6432 for the initial analysis and to swissknife who confirmed that
6433 two-hop circuits are actually created.
6434 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
6435 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
6436 - Eliminate a case where a circuit build time warning was displayed
6437 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
6440 Changes in version 0.2.1.26 - 2010-05-02
6441 Tor 0.2.1.26 addresses the recent connection and memory overload
6442 problems we've been seeing on relays, especially relays with their
6443 DirPort open. If your relay has been crashing, or you turned it off
6444 because it used too many resources, give this release a try.
6446 This release also fixes yet another instance of broken OpenSSL libraries
6447 that was causing some relays to drop out of the consensus.
6450 - Teach relays to defend themselves from connection overload. Relays
6451 now close idle circuits early if it looks like they were intended
6452 for directory fetches. Relays are also more aggressive about closing
6453 TLS connections that have no circuits on them. Such circuits are
6454 unlikely to be re-used, and tens of thousands of them were piling
6455 up at the fast relays, causing the relays to run out of sockets
6456 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6457 their directory fetches over TLS).
6458 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6459 that claim to be earlier than 0.9.8m, but which have in reality
6460 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6461 behavior. Possible fix for some cases of bug 1346.
6462 - Directory mirrors were fetching relay descriptors only from v2
6463 directory authorities, rather than v3 authorities like they should.
6464 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6465 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6468 - Finally get rid of the deprecated and now harmful notion of "clique
6469 mode", where directory authorities maintain TLS connections to
6473 - In the util/threads test, no longer free the test_mutex before all
6474 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6475 - The master thread could starve the worker threads quite badly on
6476 certain systems, causing them to run only partially in the allowed
6477 window. This resulted in test failures. Now the master thread sleeps
6478 occasionally for a few microseconds while the two worker-threads
6479 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6482 Changes in version 0.2.2.13-alpha - 2010-04-24
6483 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
6484 problems we've been seeing on relays, especially relays with their
6485 DirPort open. If your relay has been crashing, or you turned it off
6486 because it used too many resources, give this release a try.
6489 - Teach relays to defend themselves from connection overload. Relays
6490 now close idle circuits early if it looks like they were intended
6491 for directory fetches. Relays are also more aggressive about closing
6492 TLS connections that have no circuits on them. Such circuits are
6493 unlikely to be re-used, and tens of thousands of them were piling
6494 up at the fast relays, causing the relays to run out of sockets
6495 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6496 their directory fetches over TLS).
6499 - Finally get rid of the deprecated and now harmful notion of "clique
6500 mode", where directory authorities maintain TLS connections to
6502 - Directory authorities now do an immediate reachability check as soon
6503 as they hear about a new relay. This change should slightly reduce
6504 the time between setting up a relay and getting listed as running
6505 in the consensus. It should also improve the time between setting
6506 up a bridge and seeing use by bridge users.
6507 - Directory authorities no longer launch a TLS connection to every
6508 relay as they startup. Now that we have 2k+ descriptors cached,
6509 the resulting network hiccup is becoming a burden. Besides,
6510 authorities already avoid voting about Running for the first half
6511 hour of their uptime.
6514 Changes in version 0.2.2.12-alpha - 2010-04-20
6515 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
6516 handle and vote on descriptors. It was causing relays to drop out of
6520 - Many relays have been falling out of the consensus lately because
6521 not enough authorities know about their descriptor for them to get
6522 a majority of votes. When we deprecated the v2 directory protocol,
6523 we got rid of the only way that v3 authorities can hear from each
6524 other about other descriptors. Now authorities examine every v3
6525 vote for new descriptors, and fetch them from that authority. Bugfix
6527 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
6528 and a warning in or.h related to bandwidth_weight_rule_t that
6529 prevented clean compile on OS X. Fixes bug 1363; bugfix on
6531 - Fix a segfault on relays when DirReqStatistics is enabled
6532 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
6536 - Demote a confusing TLS warning that relay operators might get when
6537 someone tries to talk to their OrPort. It is neither the operator's
6538 fault nor can they do anything about it. Fixes bug 1364; bugfix
6542 Changes in version 0.2.2.11-alpha - 2010-04-15
6543 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
6544 libraries that was causing some relays to drop out of the consensus.
6547 - Directory mirrors were fetching relay descriptors only from v2
6548 directory authorities, rather than v3 authorities like they should.
6549 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6550 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6551 - Fix a parsing error that made every possible value of
6552 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
6553 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
6554 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
6555 about the option without breaking older ones.
6556 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6557 that claim to be earlier than 0.9.8m, but which have in reality
6558 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6559 behavior. Possible fix for some cases of bug 1346.
6562 - Experiment with a more aggressive approach to preventing clients
6563 from making one-hop exit streams. Exit relays who want to try it
6564 out can set "RefuseUnknownExits 1" in their torrc, and then look
6565 for "Attempt by %s to open a stream" log messages. Let us know
6567 - Add support for statically linking zlib by specifying
6568 --enable-static-zlib, to go with our support for statically linking
6569 openssl and libevent. Resolves bug 1358.
6572 - Fix a segfault that happens whenever a Tor client that is using
6573 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
6575 - When we cleaned up the contrib/tor-exit-notice.html file, we left
6576 out the first line. Fixes bug 1295.
6577 - When building the manpage from a tarball, we required asciidoc, but
6578 the asciidoc -> roff/html conversion was already done for the
6579 tarball. Make 'make' complain only when we need asciidoc (either
6580 because we're compiling directly from git, or because we altered
6581 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
6582 - When none of the directory authorities vote on any params, Tor
6583 segfaulted when trying to make the consensus from the votes. We
6584 didn't trigger the bug in practice, because authorities do include
6585 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
6588 - In the util/threads test, no longer free the test_mutex before all
6589 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6590 - The master thread could starve the worker threads quite badly on
6591 certain systems, causing them to run only partially in the allowed
6592 window. This resulted in test failures. Now the master thread sleeps
6593 occasionally for a few microseconds while the two worker-threads
6594 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6597 Changes in version 0.2.2.10-alpha - 2010-03-07
6598 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
6599 could prevent relays from guessing their IP address correctly. It also
6600 starts the groundwork for another client-side performance boost, since
6601 currently we're not making efficient use of relays that have both the
6602 Guard flag and the Exit flag.
6605 - Fix a regression from our patch for bug 1244 that caused relays
6606 to guess their IP address incorrectly if they didn't set Address
6607 in their torrc and/or their address fails to resolve. Bugfix on
6608 0.2.2.9-alpha; fixes bug 1269.
6610 o Major features (performance):
6611 - Directory authorities now compute consensus weightings that instruct
6612 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
6613 and no flag. Clients that use these weightings will distribute
6614 network load more evenly across these different relay types. The
6615 weightings are in the consensus so we can change them globally in
6616 the future. Extra thanks to "outofwords" for finding some nasty
6617 security bugs in the first implementation of this feature.
6619 o Minor features (performance):
6620 - Always perform router selections using weighted relay bandwidth,
6621 even if we don't need a high capacity circuit at the time. Non-fast
6622 circuits now only differ from fast ones in that they can use relays
6623 not marked with the Fast flag. This "feature" could turn out to
6624 be a horrible bug; we should investigate more before it goes into
6628 - Allow disabling building of the manpages. Skipping the manpage
6629 speeds up the build considerably.
6631 o Minor bugfixes (on 0.2.2.x):
6632 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
6633 Bugfix on 0.2.2.9-alpha.
6634 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
6635 config option. Bugfix on 0.2.2.7-alpha.
6636 - Ship the asciidoc-helper file in the tarball, so that people can
6637 build from source if they want to, and touching the .1.txt files
6638 doesn't break the build. Bugfix on 0.2.2.9-alpha.
6640 o Minor bugfixes (on 0.2.1.x or earlier):
6641 - Fix a dereference-then-NULL-check sequence when publishing
6642 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6644 - Fix another dereference-then-NULL-check sequence. Bugfix on
6645 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6646 - Make sure we treat potentially not NUL-terminated strings correctly.
6647 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6649 o Code simplifications and refactoring:
6650 - Fix some urls in the exit notice file and make it XHTML1.1 strict
6651 compliant. Based on a patch from Christian Kujau.
6652 - Don't use sed in asciidoc-helper anymore.
6653 - Make the build process fail if asciidoc cannot be found and
6654 building with asciidoc isn't disabled.
6657 Changes in version 0.2.2.9-alpha - 2010-02-22
6658 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
6659 location of a directory authority, and cleans up a bunch of small bugs.
6661 o Directory authority changes:
6662 - Change IP address for dannenberg (v3 directory authority), and
6663 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6664 service directory authority) from the list.
6667 - Make Tor work again on the latest OS X: when deciding whether to
6668 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6669 version at run-time, not compile time. We need to do this because
6670 Apple doesn't update its dev-tools headers when it updates its
6671 libraries in a security patch.
6672 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6673 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6674 a memory leak when requesting a hidden service descriptor we've
6675 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6677 - Authorities could be tricked into giving out the Exit flag to relays
6678 that didn't allow exiting to any ports. This bug could screw
6679 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
6680 1238. Bug discovered by Martin Kowalczyk.
6681 - When freeing a session key, zero it out completely. We only zeroed
6682 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6683 patched by ekir. Fixes bug 1254.
6686 - Fix static compilation by listing the openssl libraries in the right
6687 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
6688 - Resume handling .exit hostnames in a special way: originally we
6689 stripped the .exit part and used the requested exit relay. In
6690 0.2.2.1-alpha we stopped treating them in any special way, meaning
6691 if you use a .exit address then Tor will pass it on to the exit
6692 relay. Now we reject the .exit stream outright, since that behavior
6693 might be more expected by the user. Found and diagnosed by Scott
6694 Bennett and Downie on or-talk.
6695 - Don't spam the controller with events when we have no file
6696 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
6697 for log messages was already solved from bug 748.)
6698 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
6700 - Make the DNSPort option work with libevent 2.x. Don't alter the
6701 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
6702 - Emit a GUARD DROPPED controller event for a case we missed.
6703 - Make more fields in the controller protocol case-insensitive, since
6704 control-spec.txt said they were.
6705 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6706 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6707 - Fix a spec conformance issue: the network-status-version token
6708 must be the first token in a v3 consensus or vote. Discovered by
6709 parakeep. Bugfix on 0.2.0.3-alpha.
6711 o Code simplifications and refactoring:
6712 - Generate our manpage and HTML documentation using Asciidoc. This
6713 change should make it easier to maintain the documentation, and
6715 - Remove the --enable-iphone option. According to reports from Marco
6716 Bonetti, Tor builds fine without any special tweaking on recent
6717 iPhone SDK versions.
6718 - Removed some unnecessary files from the source distribution. The
6719 AUTHORS file has now been merged into the people page on the
6720 website. The roadmaps and design doc can now be found in the
6721 projects directory in svn.
6722 - Enabled various circuit build timeout constants to be controlled
6723 by consensus parameters. Also set better defaults for these
6724 parameters based on experimentation on broadband and simulated
6728 - The 'EXTENDCIRCUIT' control port command can now be used with
6729 a circ id of 0 and no path. This feature will cause Tor to build
6730 a new 'fast' general purpose circuit using its own path selection
6732 - Added a BUILDTIMEOUT_SET controller event to describe changes
6733 to the circuit build timeout.
6734 - Future-proof the controller protocol a bit by ignoring keyword
6735 arguments we do not recognize.
6736 - Expand homedirs passed to tor-checkkey. This should silence a
6737 coverity complaint about passing a user-supplied string into
6738 open() without checking it.
6741 Changes in version 0.2.1.25 - 2010-03-16
6742 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
6743 prevent relays from guessing their IP address correctly. It also fixes
6744 several minor potential security bugs.
6747 - Fix a regression from our patch for bug 1244 that caused relays
6748 to guess their IP address incorrectly if they didn't set Address
6749 in their torrc and/or their address fails to resolve. Bugfix on
6750 0.2.1.23; fixes bug 1269.
6751 - When freeing a session key, zero it out completely. We only zeroed
6752 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6753 patched by ekir. Fixes bug 1254.
6756 - Fix a dereference-then-NULL-check sequence when publishing
6757 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6759 - Fix another dereference-then-NULL-check sequence. Bugfix on
6760 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6761 - Make sure we treat potentially not NUL-terminated strings correctly.
6762 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6766 Changes in version 0.2.1.24 - 2010-02-21
6767 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
6771 - Work correctly out-of-the-box with even more vendor-patched versions
6772 of OpenSSL. In particular, make it so Debian and OS X don't need
6773 customized patches to run/build.
6776 Changes in version 0.2.1.23 - 2010-02-13
6777 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
6778 again on the latest OS X, and updates the location of a directory
6781 o Major bugfixes (performance):
6782 - We were selecting our guards uniformly at random, and then weighting
6783 which of our guards we'd use uniformly at random. This imbalance
6784 meant that Tor clients were severely limited on throughput (and
6785 probably latency too) by the first hop in their circuit. Now we
6786 select guards weighted by currently advertised bandwidth. We also
6787 automatically discard guards picked using the old algorithm. Fixes
6788 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6791 - Make Tor work again on the latest OS X: when deciding whether to
6792 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6793 version at run-time, not compile time. We need to do this because
6794 Apple doesn't update its dev-tools headers when it updates its
6795 libraries in a security patch.
6796 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6797 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6798 a memory leak when requesting a hidden service descriptor we've
6799 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6802 o Directory authority changes:
6803 - Change IP address for dannenberg (v3 directory authority), and
6804 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6805 service directory authority) from the list.
6808 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6809 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6812 - Avoid a mad rush at the beginning of each month when each client
6813 rotates half of its guards. Instead we spread the rotation out
6814 throughout the month, but we still avoid leaving a precise timestamp
6815 in the state file about when we first picked the guard. Improves
6816 over the behavior introduced in 0.1.2.17.
6819 Changes in version 0.2.2.8-alpha - 2010-01-26
6820 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
6821 causing bridge relays to disappear. If you're running a bridge,
6825 - Fix a memory corruption bug on bridges that occured during the
6826 inclusion of stats data in extra-info descriptors. Also fix the
6827 interface for geoip_get_bridge_stats* to prevent similar bugs in
6828 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
6829 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
6832 - Ignore OutboundBindAddress when connecting to localhost.
6833 Connections to localhost need to come _from_ localhost, or else
6834 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
6838 Changes in version 0.2.2.7-alpha - 2010-01-19
6839 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
6840 as laying the groundwork for further relay-side performance fixes. It
6841 also starts cleaning up client behavior with respect to the EntryNodes,
6842 ExitNodes, and StrictNodes config options.
6844 This release also rotates two directory authority keys, due to a
6845 security breach of some of the Torproject servers.
6847 o Directory authority changes:
6848 - Rotate keys (both v3 identity and relay identity) for moria1
6851 o Major features (performance):
6852 - We were selecting our guards uniformly at random, and then weighting
6853 which of our guards we'd use uniformly at random. This imbalance
6854 meant that Tor clients were severely limited on throughput (and
6855 probably latency too) by the first hop in their circuit. Now we
6856 select guards weighted by currently advertised bandwidth. We also
6857 automatically discard guards picked using the old algorithm. Fixes
6858 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6859 - When choosing which cells to relay first, relays can now favor
6860 circuits that have been quiet recently, to provide lower latency
6861 for low-volume circuits. By default, relays enable or disable this
6862 feature based on a setting in the consensus. You can override
6863 this default by using the new "CircuitPriorityHalflife" config
6864 option. Design and code by Ian Goldberg, Can Tang, and Chris
6866 - Add separate per-conn write limiting to go with the per-conn read
6867 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
6868 but never per-conn write limits.
6869 - New consensus params "bwconnrate" and "bwconnburst" to let us
6870 rate-limit client connections as they enter the network. It's
6871 controlled in the consensus so we can turn it on and off for
6872 experiments. It's starting out off. Based on proposal 163.
6874 o Major features (relay selection options):
6875 - Switch to a StrictNodes config option, rather than the previous
6876 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
6877 "StrictExcludeNodes" option.
6878 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
6879 change during a config reload, mark and discard all our origin
6880 circuits. This fix should address edge cases where we change the
6881 config options and but then choose a circuit that we created before
6883 - If EntryNodes or ExitNodes are set, be more willing to use an
6884 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
6886 - Make EntryNodes config option much more aggressive even when
6887 StrictNodes is not set. Before it would prepend your requested
6888 entrynodes to your list of guard nodes, but feel free to use others
6889 after that. Now it chooses only from your EntryNodes if any of
6890 those are available, and only falls back to others if a) they're
6891 all down and b) StrictNodes is not set.
6892 - Now we refresh your entry guards from EntryNodes at each consensus
6893 fetch -- rather than just at startup and then they slowly rot as
6894 the network changes.
6897 - Stop bridge directory authorities from answering dbg-stability.txt
6898 directory queries, which would let people fetch a list of all
6899 bridge identities they track. Bugfix on 0.2.1.6-alpha.
6902 - Log a notice when we get a new control connection. Now it's easier
6903 for security-conscious users to recognize when a local application
6904 is knocking on their controller door. Suggested by bug 1196.
6905 - New config option "CircuitStreamTimeout" to override our internal
6906 timeout schedule for how many seconds until we detach a stream from
6907 a circuit and try a new circuit. If your network is particularly
6908 slow, you might want to set this to a number like 60.
6909 - New controller command "getinfo config-text". It returns the
6910 contents that Tor would write if you send it a SAVECONF command,
6911 so the controller can write the file to disk itself.
6912 - New options for SafeLogging to allow scrubbing only log messages
6913 generated while acting as a relay.
6914 - Ship the bridges spec file in the tarball too.
6915 - Avoid a mad rush at the beginning of each month when each client
6916 rotates half of its guards. Instead we spread the rotation out
6917 throughout the month, but we still avoid leaving a precise timestamp
6918 in the state file about when we first picked the guard. Improves
6919 over the behavior introduced in 0.1.2.17.
6921 o Minor bugfixes (compiling):
6922 - Fix compilation on OS X 10.3, which has a stub mlockall() but
6923 hides it. Bugfix on 0.2.2.6-alpha.
6924 - Fix compilation on Solaris by removing support for the
6925 DisableAllSwap config option. Solaris doesn't have an rlimit for
6926 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
6929 o Minor bugfixes (crashes):
6930 - Do not segfault when writing buffer stats when we haven't observed
6931 a single circuit to report about. Found by Fabian Lanze. Bugfix on
6933 - If we're in the pathological case where there's no exit bandwidth
6934 but there is non-exit bandwidth, or no guard bandwidth but there
6935 is non-guard bandwidth, don't crash during path selection. Bugfix
6937 - Fix an impossible-to-actually-trigger buffer overflow in relay
6938 descriptor generation. Bugfix on 0.1.0.15.
6940 o Minor bugfixes (privacy):
6941 - Fix an instance where a Tor directory mirror might accidentally
6942 log the IP address of a misbehaving Tor client. Bugfix on
6944 - Don't list Windows capabilities in relay descriptors. We never made
6945 use of them, and maybe it's a bad idea to publish them. Bugfix
6948 o Minor bugfixes (other):
6949 - Resolve an edge case in path weighting that could make us misweight
6950 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
6951 - Fix statistics on client numbers by country as seen by bridges that
6952 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
6953 intervals instead of variable 12-to-48-hour intervals.
6954 - After we free an internal connection structure, overwrite it
6955 with a different memory value than we use for overwriting a freed
6956 internal circuit structure. Should help with debugging. Suggested
6958 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
6962 - Remove the HSAuthorityRecordStats option that version 0 hidden
6963 service authorities could have used to track statistics of overall
6964 hidden service usage.
6967 Changes in version 0.2.1.22 - 2010-01-19
6968 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
6969 authorities -- it would tell you its whole history of bridge descriptors
6970 if you make the right directory request. This stable update also
6971 rotates two of the seven v3 directory authority keys and locations.
6973 o Directory authority changes:
6974 - Rotate keys (both v3 identity and relay identity) for moria1
6978 - Stop bridge directory authorities from answering dbg-stability.txt
6979 directory queries, which would let people fetch a list of all
6980 bridge identities they track. Bugfix on 0.2.1.6-alpha.
6983 Changes in version 0.2.1.21 - 2009-12-21
6984 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
6985 library. If you use Tor on Linux / Unix and you're getting SSL
6986 renegotiation errors, upgrading should help. We also recommend an
6987 upgrade if you're an exit relay.
6990 - Work around a security feature in OpenSSL 0.9.8l that prevents our
6991 handshake from working unless we explicitly tell OpenSSL that we
6992 are using SSL renegotiation safely. We are, of course, but OpenSSL
6993 0.9.8l won't work unless we say we are.
6994 - Avoid crashing if the client is trying to upload many bytes and the
6995 circuit gets torn down at the same time, or if the flip side
6996 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
6999 - Do not refuse to learn about authority certs and v2 networkstatus
7000 documents that are older than the latest consensus. This bug might
7001 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
7002 Spotted and fixed by xmux.
7003 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
7004 trigger platform-specific option misparsing case found by Coverity
7006 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
7007 trigger assert. Fixes bug 1173.
7010 Changes in version 0.2.2.6-alpha - 2009-11-19
7011 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
7012 support for the new lower-footprint "microdescriptor" directory design,
7013 future-proofing our consensus format against new hash functions or
7014 other changes, and an Android port. It also makes Tor compatible with
7015 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
7018 - Directory authorities can now create, vote on, and serve multiple
7019 parallel formats of directory data as part of their voting process.
7020 Partially implements Proposal 162: "Publish the consensus in
7022 - Directory authorities can now agree on and publish small summaries
7023 of router information that clients can use in place of regular
7024 server descriptors. This transition will eventually allow clients
7025 to use far less bandwidth for downloading information about the
7026 network. Begins the implementation of Proposal 158: "Clients
7027 download consensus + microdescriptors".
7028 - The directory voting system is now extensible to use multiple hash
7029 algorithms for signatures and resource selection. Newer formats
7030 are signed with SHA256, with a possibility for moving to a better
7031 hash algorithm in the future.
7032 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
7033 current and future memory pages via mlockall(). On supported
7034 platforms (modern Linux and probably BSD but not Windows or OS X),
7035 this should effectively disable any and all attempts to page out
7036 memory. This option requires that you start your Tor as root --
7037 if you use DisableAllSwap, please consider using the User option
7038 to properly reduce the privileges of your Tor.
7039 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
7040 to help Tor build correctly for Android phones.
7043 - Work around a security feature in OpenSSL 0.9.8l that prevents our
7044 handshake from working unless we explicitly tell OpenSSL that we
7045 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
7046 won't work unless we say we are.
7049 - Fix a crash bug when trying to initialize the evdns module in
7050 Libevent 2. Bugfix on 0.2.1.16-rc.
7051 - Stop logging at severity 'warn' when some other Tor client tries
7052 to establish a circuit with us using weak DH keys. It's a protocol
7053 violation, but that doesn't mean ordinary users need to hear about
7054 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
7055 - Do not refuse to learn about authority certs and v2 networkstatus
7056 documents that are older than the latest consensus. This bug might
7057 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
7058 Spotted and fixed by xmux.
7059 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
7060 - If all authorities restart at once right before a consensus vote,
7061 nobody will vote about "Running", and clients will get a consensus
7062 with no usable relays. Instead, authorities refuse to build a
7063 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
7064 - If your relay can't keep up with the number of incoming create
7065 cells, it would log one warning per failure into your logs. Limit
7066 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
7067 - Bridges now use "reject *:*" as their default exit policy. Bugfix
7068 on 0.2.0.3-alpha; fixes bug 1113.
7069 - Fix a memory leak on directory authorities during voting that was
7070 introduced in 0.2.2.1-alpha. Found via valgrind.
7073 Changes in version 0.2.1.20 - 2009-10-15
7074 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
7075 services at once, prepares for more performance improvements, and
7076 fixes a bunch of smaller bugs.
7078 The Windows and OS X bundles also include a more recent Vidalia,
7079 and switch from Privoxy to Polipo.
7081 The OS X installers are now drag and drop. It's best to un-install
7082 Tor/Vidalia and then install this new bundle, rather than upgrade. If
7083 you want to upgrade, you'll need to update the paths for Tor and Polipo
7084 in the Vidalia Settings window.
7087 - Send circuit or stream sendme cells when our window has decreased
7088 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
7089 by Karsten when testing the "reduce circuit window" performance
7090 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7091 before the release of Tor 0.0.0. This is the new winner of the
7093 - Fix a remotely triggerable memory leak when a consensus document
7094 contains more than one signature from the same voter. Bugfix on
7096 - Avoid segfault in rare cases when finishing an introduction circuit
7097 as a client and finding out that we don't have an introduction key
7098 for it. Fixes bug 1073. Reported by Aaron Swartz.
7101 - Tor now reads the "circwindow" parameter out of the consensus,
7102 and uses that value for its circuit package window rather than the
7103 default of 1000 cells. Begins the implementation of proposal 168.
7105 o New directory authorities:
7106 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
7108 - Move moria1 and tonga to alternate IP addresses.
7111 - Fix a signed/unsigned compile warning in 0.2.1.19.
7112 - Fix possible segmentation fault on directory authorities. Bugfix on
7114 - Fix an extremely rare infinite recursion bug that could occur if
7115 we tried to log a message after shutting down the log subsystem.
7116 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
7117 - Fix an obscure bug where hidden services on 64-bit big-endian
7118 systems might mis-read the timestamp in v3 introduce cells, and
7119 refuse to connect back to the client. Discovered by "rotor".
7120 Bugfix on 0.2.1.6-alpha.
7121 - We were triggering a CLOCK_SKEW controller status event whenever
7122 we connect via the v2 connection protocol to any relay that has
7123 a wrong clock. Instead, we should only inform the controller when
7124 it's a trusted authority that claims our clock is wrong. Bugfix
7125 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
7126 - We were telling the controller about CHECKING_REACHABILITY and
7127 REACHABILITY_FAILED status events whenever we launch a testing
7128 circuit or notice that one has failed. Instead, only tell the
7129 controller when we want to inform the user of overall success or
7130 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7132 - Don't warn when we're using a circuit that ends with a node
7133 excluded in ExcludeExitNodes, but the circuit is not used to access
7134 the outside world. This should help fix bug 1090. Bugfix on
7136 - Work around a small memory leak in some versions of OpenSSL that
7137 stopped the memory used by the hostname TLS extension from being
7141 - Add a "getinfo status/accepted-server-descriptor" controller
7142 command, which is the recommended way for controllers to learn
7143 whether our server descriptor has been successfully received by at
7144 least on directory authority. Un-recommend good-server-descriptor
7145 getinfo and status events until we have a better design for them.
7148 Changes in version 0.2.2.5-alpha - 2009-10-11
7149 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
7152 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
7154 o Directory authorities:
7155 - Temporarily (just for this release) move dizum to an alternate
7159 Changes in version 0.2.2.4-alpha - 2009-10-10
7160 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
7161 introduces a new unit test framework, shifts directry authority
7162 addresses around to reduce the impact from recent blocking events,
7163 and fixes a few smaller bugs.
7166 - Fix several more asserts in the circuit_build_times code, for
7167 example one that causes Tor to fail to start once we have
7168 accumulated 5000 build times in the state file. Bugfixes on
7169 0.2.2.2-alpha; fixes bug 1108.
7171 o New directory authorities:
7172 - Move moria1 and Tonga to alternate IP addresses.
7175 - Log SSL state transitions at debug level during handshake, and
7176 include SSL states in error messages. This may help debug future
7177 SSL handshake issues.
7178 - Add a new "Handshake" log domain for activities that happen
7179 during the TLS handshake.
7180 - Revert to the "June 3 2009" ip-to-country file. The September one
7181 seems to have removed most US IP addresses.
7182 - Directory authorities now reject Tor relays with versions less than
7183 0.1.2.14. This step cuts out four relays from the current network,
7184 none of which are very big.
7187 - Fix a couple of smaller issues with gathering statistics. Bugfixes
7189 - Fix two memory leaks in the error case of
7190 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
7191 - Don't count one-hop circuits when we're estimating how long it
7192 takes circuits to build on average. Otherwise we'll set our circuit
7193 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
7194 - Directory authorities no longer change their opinion of, or vote on,
7195 whether a router is Running, unless they have themselves been
7196 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
7199 o Code simplifications and refactoring:
7200 - Revise our unit tests to use the "tinytest" framework, so we
7201 can run tests in their own processes, have smarter setup/teardown
7202 code, and so on. The unit test code has moved to its own
7203 subdirectory, and has been split into multiple modules.
7206 Changes in version 0.2.2.3-alpha - 2009-09-23
7207 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
7210 - Fix an overzealous assert in our new circuit build timeout code.
7211 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
7214 - If the networkstatus consensus tells us that we should use a
7215 negative circuit package window, ignore it. Otherwise we'll
7216 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
7219 Changes in version 0.2.2.2-alpha - 2009-09-21
7220 Tor 0.2.2.2-alpha introduces our latest performance improvement for
7221 clients: Tor tracks the average time it takes to build a circuit, and
7222 avoids using circuits that take too long to build. For fast connections,
7223 this feature can cut your expected latency in half. For slow or flaky
7224 connections, it could ruin your Tor experience. Let us know if it does!
7227 - Tor now tracks how long it takes to build client-side circuits
7228 over time, and adapts its timeout to local network performance.
7229 Since a circuit that takes a long time to build will also provide
7230 bad performance, we get significant latency improvements by
7231 discarding the slowest 20% of circuits. Specifically, Tor creates
7232 circuits more aggressively than usual until it has enough data
7233 points for a good timeout estimate. Implements proposal 151.
7234 We are especially looking for reports (good and bad) from users with
7235 both EDGE and broadband connections that can move from broadband
7236 to EDGE and find out if the build-time data in the .tor/state gets
7237 reset without loss of Tor usability. You should also see a notice
7238 log message telling you that Tor has reset its timeout.
7239 - Directory authorities can now vote on arbitary integer values as
7240 part of the consensus process. This is designed to help set
7241 network-wide parameters. Implements proposal 167.
7242 - Tor now reads the "circwindow" parameter out of the consensus,
7243 and uses that value for its circuit package window rather than the
7244 default of 1000 cells. Begins the implementation of proposal 168.
7247 - Fix a remotely triggerable memory leak when a consensus document
7248 contains more than one signature from the same voter. Bugfix on
7252 - Fix an extremely rare infinite recursion bug that could occur if
7253 we tried to log a message after shutting down the log subsystem.
7254 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
7255 - Fix parsing for memory or time units given without a space between
7256 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
7257 - A networkstatus vote must contain exactly one signature. Spec
7258 conformance issue. Bugfix on 0.2.0.3-alpha.
7259 - Fix an obscure bug where hidden services on 64-bit big-endian
7260 systems might mis-read the timestamp in v3 introduce cells, and
7261 refuse to connect back to the client. Discovered by "rotor".
7262 Bugfix on 0.2.1.6-alpha.
7263 - We were triggering a CLOCK_SKEW controller status event whenever
7264 we connect via the v2 connection protocol to any relay that has
7265 a wrong clock. Instead, we should only inform the controller when
7266 it's a trusted authority that claims our clock is wrong. Bugfix
7267 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
7268 - We were telling the controller about CHECKING_REACHABILITY and
7269 REACHABILITY_FAILED status events whenever we launch a testing
7270 circuit or notice that one has failed. Instead, only tell the
7271 controller when we want to inform the user of overall success or
7272 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7274 - Don't warn when we're using a circuit that ends with a node
7275 excluded in ExcludeExitNodes, but the circuit is not used to access
7276 the outside world. This should help fix bug 1090, but more problems
7277 remain. Bugfix on 0.2.1.6-alpha.
7278 - Work around a small memory leak in some versions of OpenSSL that
7279 stopped the memory used by the hostname TLS extension from being
7281 - Make our 'torify' script more portable; if we have only one of
7282 'torsocks' or 'tsocks' installed, don't complain to the user;
7283 and explain our warning about tsocks better.
7286 - Add a "getinfo status/accepted-server-descriptor" controller
7287 command, which is the recommended way for controllers to learn
7288 whether our server descriptor has been successfully received by at
7289 least on directory authority. Un-recommend good-server-descriptor
7290 getinfo and status events until we have a better design for them.
7291 - Update to the "September 4 2009" ip-to-country file.
7294 Changes in version 0.2.2.1-alpha - 2009-08-26
7295 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
7296 Tor clients to bootstrap on networks where only port 80 is reachable,
7297 makes it more straightforward to support hardware crypto accelerators,
7298 and starts the groundwork for gathering stats safely at relays.
7301 - Start the process of disabling ".exit" address notation, since it
7302 can be used for a variety of esoteric application-level attacks
7303 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
7306 o New directory authorities:
7307 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
7311 - New AccelName and AccelDir options add support for dynamic OpenSSL
7312 hardware crypto acceleration engines.
7313 - Tor now supports tunneling all of its outgoing connections over
7314 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
7315 configuration options. Code by Christopher Davis.
7318 - Send circuit or stream sendme cells when our window has decreased
7319 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
7320 by Karsten when testing the "reduce circuit window" performance
7321 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7322 before the release of Tor 0.0.0. This is the new winner of the
7325 o New options for gathering stats safely:
7326 - Directory mirrors that set "DirReqStatistics 1" write statistics
7327 about directory requests to disk every 24 hours. As compared to the
7328 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
7329 1) stats are written to disk exactly every 24 hours; 2) estimated
7330 shares of v2 and v3 requests are determined as mean values, not at
7331 the end of a measurement period; 3) unresolved requests are listed
7332 with country code '??'; 4) directories also measure download times.
7333 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
7334 number of exit streams and transferred bytes per port to disk every
7336 - Relays that set "CellStatistics 1" write statistics on how long
7337 cells spend in their circuit queues to disk every 24 hours.
7338 - Entry nodes that set "EntryStatistics 1" write statistics on the
7339 rough number and origins of connecting clients to disk every 24
7341 - Relays that write any of the above statistics to disk and set
7342 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
7343 their extra-info documents.
7346 - New --digests command-line switch to output the digests of the
7347 source files Tor was built with.
7348 - The "torify" script now uses torsocks where available.
7349 - The memarea code now uses a sentinel value at the end of each area
7350 to make sure nothing writes beyond the end of an area. This might
7351 help debug some conceivable causes of bug 930.
7352 - Time and memory units in the configuration file can now be set to
7353 fractional units. For example, "2.5 GB" is now a valid value for
7355 - Certain Tor clients (such as those behind check.torproject.org) may
7356 want to fetch the consensus in an extra early manner. To enable this
7357 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
7358 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
7359 as only certain clients who must have this information sooner should
7361 - Instead of adding the svn revision to the Tor version string, report
7362 the git commit (when we're building from a git checkout).
7365 - If any of the v3 certs we download are unparseable, we should
7366 actually notice the failure so we don't retry indefinitely. Bugfix
7367 on 0.2.0.x; reported by "rotator".
7368 - If the cached cert file is unparseable, warn but don't exit.
7369 - Fix possible segmentation fault on directory authorities. Bugfix on
7371 - When Tor fails to parse a descriptor of any kind, dump it to disk.
7372 Might help diagnosing bug 1051.
7374 o Deprecated and removed features:
7375 - The controller no longer accepts the old obsolete "addr-mappings/"
7376 or "unregistered-servers-" GETINFO values.
7377 - Hidden services no longer publish version 0 descriptors, and clients
7378 do not request or use version 0 descriptors. However, the old hidden
7379 service authorities still accept and serve version 0 descriptors
7380 when contacted by older hidden services/clients.
7381 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
7382 always on; using them is necessary for correct forward-compatible
7384 - Remove support for .noconnect style addresses. Nobody was using
7385 them, and they provided another avenue for detecting Tor users
7386 via application-level web tricks.
7388 o Packaging changes:
7389 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
7390 installer bundles. See
7391 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
7392 for details of what's new in Vidalia 0.2.3.
7393 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
7394 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
7395 configuration file, rather than the old Privoxy.
7396 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
7397 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
7398 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
7399 better compatibility with OS X 10.6, aka Snow Leopard.
7400 - OS X Vidalia Bundle: The multi-package installer is now replaced
7401 by a simple drag and drop to the /Applications folder. This change
7402 occurred with the upgrade to Vidalia 0.2.3.
7405 Changes in version 0.2.1.19 - 2009-07-28
7406 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
7407 services on Tor 0.2.1.3-alpha through 0.2.1.18.
7410 - Make accessing hidden services on 0.2.1.x work right again.
7411 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
7412 part of patch provided by "optimist".
7415 - When a relay/bridge is writing out its identity key fingerprint to
7416 the "fingerprint" file and to its logs, write it without spaces. Now
7417 it will look like the fingerprints in our bridges documentation,
7418 and confuse fewer users.
7421 - Relays no longer publish a new server descriptor if they change
7422 their MaxAdvertisedBandwidth config option but it doesn't end up
7423 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
7424 fixes bug 1026. Patch from Sebastian.
7425 - Avoid leaking memory every time we get a create cell but we have
7426 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
7427 fixes bug 1034. Reported by BarkerJr.
7430 Changes in version 0.2.1.18 - 2009-07-24
7431 Tor 0.2.1.18 lays the foundations for performance improvements,
7432 adds status events to help users diagnose bootstrap problems, adds
7433 optional authentication/authorization for hidden services, fixes a
7434 variety of potential anonymity problems, and includes a huge pile of
7435 other features and bug fixes.
7438 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
7441 Changes in version 0.2.1.17-rc - 2009-07-07
7442 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
7443 candidate for the 0.2.1.x series. It lays the groundwork for further
7444 client performance improvements, and also fixes a big bug with directory
7445 authorities that were causing them to assign Guard and Stable flags
7448 The Windows bundles also finally include the geoip database that we
7449 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
7450 should actually install Torbutton rather than giving you a cryptic
7451 failure message (oops).
7454 - Clients now use the bandwidth values in the consensus, rather than
7455 the bandwidth values in each relay descriptor. This approach opens
7456 the door to more accurate bandwidth estimates once the directory
7457 authorities start doing active measurements. Implements more of
7461 - When Tor clients restart after 1-5 days, they discard all their
7462 cached descriptors as too old, but they still use the cached
7463 consensus document. This approach is good for robustness, but
7464 bad for performance: since they don't know any bandwidths, they
7465 end up choosing at random rather than weighting their choice by
7466 speed. Fixed by the above feature of putting bandwidths in the
7467 consensus. Bugfix on 0.2.0.x.
7468 - Directory authorities were neglecting to mark relays down in their
7469 internal histories if the relays fall off the routerlist without
7470 ever being found unreachable. So there were relays in the histories
7471 that haven't been seen for eight months, and are listed as being
7472 up for eight months. This wreaked havoc on the "median wfu"
7473 and "median mtbf" calculations, in turn making Guard and Stable
7474 flags very wrong, hurting network performance. Fixes bugs 696 and
7475 969. Bugfix on 0.2.0.6-alpha.
7478 - Serve the DirPortFrontPage page even when we have been approaching
7479 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
7480 - The control port would close the connection before flushing long
7481 replies, such as the network consensus, if a QUIT command was issued
7482 before the reply had completed. Now, the control port flushes all
7483 pending replies before closing the connection. Also fixed a spurious
7484 warning when a QUIT command is issued after a malformed or rejected
7485 AUTHENTICATE command, but before the connection was closed. Patch
7486 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
7487 - When we can't find an intro key for a v2 hidden service descriptor,
7488 fall back to the v0 hidden service descriptor and log a bug message.
7489 Workaround for bug 1024.
7490 - Fix a log message that did not respect the SafeLogging option.
7494 - If we're a relay and we change our IP address, be more verbose
7495 about the reason that made us change. Should help track down
7496 further bugs for relays on dynamic IP addresses.
7499 Changes in version 0.2.0.35 - 2009-06-24
7501 - Avoid crashing in the presence of certain malformed descriptors.
7502 Found by lark, and by automated fuzzing.
7503 - Fix an edge case where a malicious exit relay could convince a
7504 controller that the client's DNS question resolves to an internal IP
7505 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7508 - Finally fix the bug where dynamic-IP relays disappear when their
7509 IP address changes: directory mirrors were mistakenly telling
7510 them their old address if they asked via begin_dir, so they
7511 never got an accurate answer about their new address, so they
7512 just vanished after a day. For belt-and-suspenders, relays that
7513 don't set Address in their config now avoid using begin_dir for
7514 all direct connections. Should fix bugs 827, 883, and 900.
7515 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7516 that would occur on some exit nodes when DNS failures and timeouts
7517 occurred in certain patterns. Fix for bug 957.
7520 - When starting with a cache over a few days old, do not leak
7521 memory for the obsolete router descriptors in it. Bugfix on
7522 0.2.0.33; fixes bug 672.
7523 - Hidden service clients didn't use a cached service descriptor that
7524 was older than 15 minutes, but wouldn't fetch a new one either,
7525 because there was already one in the cache. Now, fetch a v2
7526 descriptor unless the same descriptor was added to the cache within
7527 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7530 Changes in version 0.2.1.16-rc - 2009-06-20
7531 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
7532 a bunch of minor bugs.
7535 - Fix an edge case where a malicious exit relay could convince a
7536 controller that the client's DNS question resolves to an internal IP
7537 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7539 o Major performance improvements (on 0.2.0.x):
7540 - Disable and refactor some debugging checks that forced a linear scan
7541 over the whole server-side DNS cache. These accounted for over 50%
7542 of CPU time on a relatively busy exit node's gprof profile. Found
7544 - Disable some debugging checks that appeared in exit node profile
7548 - Update to the "June 3 2009" ip-to-country file.
7549 - Do not have tor-resolve automatically refuse all .onion addresses;
7550 if AutomapHostsOnResolve is set in your torrc, this will work fine.
7552 o Minor bugfixes (on 0.2.0.x):
7553 - Log correct error messages for DNS-related network errors on
7555 - Fix a race condition that could cause crashes or memory corruption
7556 when running as a server with a controller listening for log
7558 - Avoid crashing when we have a policy specified in a DirPolicy or
7559 SocksPolicy or ReachableAddresses option with ports set on it,
7560 and we re-load the policy. May fix bug 996.
7561 - Hidden service clients didn't use a cached service descriptor that
7562 was older than 15 minutes, but wouldn't fetch a new one either,
7563 because there was already one in the cache. Now, fetch a v2
7564 descriptor unless the same descriptor was added to the cache within
7565 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7567 o Minor bugfixes (on 0.2.1.x):
7568 - Don't warn users about low port and hibernation mix when they
7569 provide a *ListenAddress directive to fix that. Bugfix on
7571 - When switching back and forth between bridge mode, do not start
7572 gathering GeoIP data until two hours have passed.
7573 - Do not complain that the user has requested an excluded node as
7574 an exit when the node is not really an exit. This could happen
7575 because the circuit was for testing, or an introduction point.
7579 Changes in version 0.2.1.15-rc - 2009-05-25
7580 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
7581 series. It fixes a major bug on fast exit relays, as well as a variety
7584 o Major bugfixes (on 0.2.0.x):
7585 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7586 that would occur on some exit nodes when DNS failures and timeouts
7587 occurred in certain patterns. Fix for bug 957.
7589 o Minor bugfixes (on 0.2.0.x):
7590 - Actually return -1 in the error case for read_bandwidth_usage().
7591 Harmless bug, since we currently don't care about the return value
7592 anywhere. Bugfix on 0.2.0.9-alpha.
7593 - Provide a more useful log message if bug 977 (related to buffer
7594 freelists) ever reappears, and do not crash right away.
7595 - Fix an assertion failure on 64-bit platforms when we allocated
7596 memory right up to the end of a memarea, then realigned the memory
7597 one step beyond the end. Fixes a possible cause of bug 930.
7598 - Protect the count of open sockets with a mutex, so we can't
7599 corrupt it when two threads are closing or opening sockets at once.
7600 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
7601 - Don't allow a bridge to publish its router descriptor to a
7602 non-bridge directory authority. Fixes part of bug 932.
7603 - When we change to or from being a bridge, reset our counts of
7604 client usage by country. Fixes bug 932.
7605 - Fix a bug that made stream bandwidth get misreported to the
7607 - Stop using malloc_usable_size() to use more area than we had
7608 actually allocated: it was safe, but made valgrind really unhappy.
7609 - Fix a memory leak when v3 directory authorities load their keys
7610 and cert from disk. Bugfix on 0.2.0.1-alpha.
7612 o Minor bugfixes (on 0.2.1.x):
7613 - Fix use of freed memory when deciding to mark a non-addable
7614 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
7617 Changes in version 0.2.1.14-rc - 2009-04-12
7618 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
7619 series. It begins fixing some major performance problems, and also
7620 finally addresses the bug that was causing relays on dynamic IP
7621 addresses to fall out of the directory.
7624 - Clients replace entry guards that were chosen more than a few months
7625 ago. This change should significantly improve client performance,
7626 especially once more people upgrade, since relays that have been
7627 a guard for a long time are currently overloaded.
7629 o Major bugfixes (on 0.2.0):
7630 - Finally fix the bug where dynamic-IP relays disappear when their
7631 IP address changes: directory mirrors were mistakenly telling
7632 them their old address if they asked via begin_dir, so they
7633 never got an accurate answer about their new address, so they
7634 just vanished after a day. For belt-and-suspenders, relays that
7635 don't set Address in their config now avoid using begin_dir for
7636 all direct connections. Should fix bugs 827, 883, and 900.
7637 - Relays were falling out of the networkstatus consensus for
7638 part of a day if they changed their local config but the
7639 authorities discarded their new descriptor as "not sufficiently
7640 different". Now directory authorities accept a descriptor as changed
7641 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
7643 - Avoid crashing in the presence of certain malformed descriptors.
7644 Found by lark, and by automated fuzzing.
7647 - When generating circuit events with verbose nicknames for
7648 controllers, try harder to look up nicknames for routers on a
7649 circuit. (Previously, we would look in the router descriptors we had
7650 for nicknames, but not in the consensus.) Partial fix for bug 941.
7651 - If the bridge config line doesn't specify a port, assume 443.
7652 This makes bridge lines a bit smaller and easier for users to
7654 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
7655 bytes (aka 20KB/s), to match our documentation. Also update
7656 directory authorities so they always assign the Fast flag to relays
7657 with 20KB/s of capacity. Now people running relays won't suddenly
7658 find themselves not seeing any use, if the network gets faster
7660 - Update to the "April 3 2009" ip-to-country file.
7663 - Avoid trying to print raw memory to the logs when we decide to
7664 give up on downloading a given relay descriptor. Bugfix on
7666 - In tor-resolve, when the Tor client to use is specified by
7667 <hostname>:<port>, actually use the specified port rather than
7668 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
7669 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
7670 - When starting with a cache over a few days old, do not leak
7671 memory for the obsolete router descriptors in it. Bugfix on
7673 - Avoid double-free on list of successfully uploaded hidden
7674 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
7675 - Change memarea_strndup() implementation to work even when
7676 duplicating a string at the end of a page. This bug was
7677 harmless for now, but could have meant crashes later. Fix by
7678 lark. Bugfix on 0.2.1.1-alpha.
7679 - Limit uploaded directory documents to be 16M rather than 500K.
7680 The directory authorities were refusing v3 consensus votes from
7681 other authorities, since the votes are now 504K. Fixes bug 959;
7682 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
7683 - Directory authorities should never send a 503 "busy" response to
7684 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
7688 Changes in version 0.2.1.13-alpha - 2009-03-09
7689 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
7690 cleanups. We're finally getting close to a release candidate.
7693 - Correctly update the list of which countries we exclude as
7694 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
7695 lark. Bugfix on 0.2.1.6-alpha.
7697 o Minor bugfixes (on 0.2.0.x and earlier):
7698 - Automatically detect MacOSX versions earlier than 10.4.0, and
7699 disable kqueue from inside Tor when running with these versions.
7700 We previously did this from the startup script, but that was no
7701 help to people who didn't use the startup script. Resolves bug 863.
7702 - When we had picked an exit node for a connection, but marked it as
7703 "optional", and it turned out we had no onion key for the exit,
7704 stop wanting that exit and try again. This situation may not
7705 be possible now, but will probably become feasible with proposal
7706 158. Spotted by rovv. Fixes another case of bug 752.
7707 - Clients no longer cache certificates for authorities they do not
7708 recognize. Bugfix on 0.2.0.9-alpha.
7709 - When we can't transmit a DNS request due to a network error, retry
7710 it after a while, and eventually transmit a failing response to
7711 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
7712 - If the controller claimed responsibility for a stream, but that
7713 stream never finished making its connection, it would live
7714 forever in circuit_wait state. Now we close it after SocksTimeout
7715 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
7716 - Drop begin cells to a hidden service if they come from the middle
7717 of a circuit. Patch from lark.
7718 - When we erroneously receive two EXTEND cells for the same circuit
7719 ID on the same connection, drop the second. Patch from lark.
7720 - Fix a crash that occurs on exit nodes when a nameserver request
7721 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
7722 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
7724 - Do not assume that a stack-allocated character array will be
7725 64-bit aligned on platforms that demand that uint64_t access is
7726 aligned. Possible fix for bug 604.
7727 - Parse dates and IPv4 addresses in a locale- and libc-independent
7728 manner, to avoid platform-dependent behavior on malformed input.
7729 - Build correctly when configured to build outside the main source
7730 path. Patch from Michael Gold.
7731 - We were already rejecting relay begin cells with destination port
7732 of 0. Now also reject extend cells with destination port or address
7733 of 0. Suggested by lark.
7735 o Minor bugfixes (on 0.2.1.x):
7736 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
7737 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
7738 - If we're an exit node, scrub the IP address to which we are exiting
7739 in the logs. Bugfix on 0.2.1.8-alpha.
7742 - On Linux, use the prctl call to re-enable core dumps when the user
7744 - New controller event NEWCONSENSUS that lists the networkstatus
7745 lines for every recommended relay. Now controllers like Torflow
7746 can keep up-to-date on which relays they should be using.
7747 - Update to the "February 26 2009" ip-to-country file.
7750 Changes in version 0.2.0.34 - 2009-02-08
7751 Tor 0.2.0.34 features several more security-related fixes. You should
7752 upgrade, especially if you run an exit relay (remote crash) or a
7753 directory authority (remote infinite loop), or you're on an older
7754 (pre-XP) or not-recently-patched Windows (remote exploit).
7756 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
7757 have many known flaws, and nobody should be using them. You should
7758 upgrade. If you're using a Linux or BSD and its packages are obsolete,
7759 stop using those packages and upgrade anyway.
7762 - Fix an infinite-loop bug on handling corrupt votes under certain
7763 circumstances. Bugfix on 0.2.0.8-alpha.
7764 - Fix a temporary DoS vulnerability that could be performed by
7765 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7766 - Avoid a potential crash on exit nodes when processing malformed
7767 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
7768 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
7769 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
7772 - Fix compilation on systems where time_t is a 64-bit integer.
7773 Patch from Matthias Drochner.
7774 - Don't consider expiring already-closed client connections. Fixes
7775 bug 893. Bugfix on 0.0.2pre20.
7778 Changes in version 0.2.1.12-alpha - 2009-02-08
7779 Tor 0.2.1.12-alpha features several more security-related fixes. You
7780 should upgrade, especially if you run an exit relay (remote crash) or
7781 a directory authority (remote infinite loop), or you're on an older
7782 (pre-XP) or not-recently-patched Windows (remote exploit). It also
7783 includes a big pile of minor bugfixes and cleanups.
7786 - Fix an infinite-loop bug on handling corrupt votes under certain
7787 circumstances. Bugfix on 0.2.0.8-alpha.
7788 - Fix a temporary DoS vulnerability that could be performed by
7789 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7790 - Avoid a potential crash on exit nodes when processing malformed
7791 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
7794 - Let controllers actually ask for the "clients_seen" event for
7795 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
7796 reported by Matt Edman.
7797 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
7799 - Fix a bug in address parsing that was preventing bridges or hidden
7800 service targets from being at IPv6 addresses.
7801 - Solve a bug that kept hardware crypto acceleration from getting
7802 enabled when accounting was turned on. Fixes bug 907. Bugfix on
7804 - Remove a bash-ism from configure.in to build properly on non-Linux
7805 platforms. Bugfix on 0.2.1.1-alpha.
7806 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
7807 headers. Bugfix on 0.2.0.10-alpha.
7808 - Don't consider expiring already-closed client connections. Fixes
7809 bug 893. Bugfix on 0.0.2pre20.
7810 - Fix another interesting corner-case of bug 891 spotted by rovv:
7811 Previously, if two hosts had different amounts of clock drift, and
7812 one of them created a new connection with just the wrong timing,
7813 the other might decide to deprecate the new connection erroneously.
7814 Bugfix on 0.1.1.13-alpha.
7815 - Resolve a very rare crash bug that could occur when the user forced
7816 a nameserver reconfiguration during the middle of a nameserver
7817 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
7818 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
7819 Bugfix on 0.2.1.7-alpha.
7820 - If we're using bridges and our network goes away, be more willing
7821 to forgive our bridges and try again when we get an application
7822 request. Bugfix on 0.2.0.x.
7825 - Support platforms where time_t is 64 bits long. (Congratulations,
7826 NetBSD!) Patch from Matthias Drochner.
7827 - Add a 'getinfo status/clients-seen' controller command, in case
7828 controllers want to hear clients_seen events but connect late.
7831 - Disable GCC's strict alias optimization by default, to avoid the
7832 likelihood of its introducing subtle bugs whenever our code violates
7833 the letter of C99's alias rules.
7836 Changes in version 0.2.0.33 - 2009-01-21
7837 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
7838 useful to users. It also finally fixes a bug where a relay or client
7839 that's been off for many days would take a long time to bootstrap.
7841 This update also fixes an important security-related bug reported by
7842 Ilja van Sprundel. You should upgrade. (We'll send out more details
7843 about the bug once people have had some time to upgrade.)
7846 - Fix a heap-corruption bug that may be remotely triggerable on
7847 some platforms. Reported by Ilja van Sprundel.
7850 - When a stream at an exit relay is in state "resolving" or
7851 "connecting" and it receives an "end" relay cell, the exit relay
7852 would silently ignore the end cell and not close the stream. If
7853 the client never closes the circuit, then the exit relay never
7854 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
7856 - When sending CREATED cells back for a given circuit, use a 64-bit
7857 connection ID to find the right connection, rather than an addr:port
7858 combination. Now that we can have multiple OR connections between
7859 the same ORs, it is no longer possible to use addr:port to uniquely
7860 identify a connection.
7861 - Bridge relays that had DirPort set to 0 would stop fetching
7862 descriptors shortly after startup, and then briefly resume
7863 after a new bandwidth test and/or after publishing a new bridge
7864 descriptor. Bridge users that try to bootstrap from them would
7865 get a recent networkstatus but would get descriptors from up to
7866 18 hours earlier, meaning most of the descriptors were obsolete
7867 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
7868 - Prevent bridge relays from serving their 'extrainfo' document
7869 to anybody who asks, now that extrainfo docs include potentially
7870 sensitive aggregated client geoip summaries. Bugfix on
7872 - If the cached networkstatus consensus is more than five days old,
7873 discard it rather than trying to use it. In theory it could be
7874 useful because it lists alternate directory mirrors, but in practice
7875 it just means we spend many minutes trying directory mirrors that
7876 are long gone from the network. Also discard router descriptors as
7877 we load them if they are more than five days old, since the onion
7878 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
7881 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
7882 could make gcc generate non-functional binary search code. Bugfix
7884 - Build correctly on platforms without socklen_t.
7885 - Compile without warnings on solaris.
7886 - Avoid potential crash on internal error during signature collection.
7887 Fixes bug 864. Patch from rovv.
7888 - Correct handling of possible malformed authority signing key
7889 certificates with internal signature types. Fixes bug 880.
7890 Bugfix on 0.2.0.3-alpha.
7891 - Fix a hard-to-trigger resource leak when logging credential status.
7893 - When we can't initialize DNS because the network is down, do not
7894 automatically stop Tor from starting. Instead, we retry failed
7895 dns_init() every 10 minutes, and change the exit policy to reject
7896 *:* until one succeeds. Fixes bug 691.
7897 - Use 64 bits instead of 32 bits for connection identifiers used with
7898 the controller protocol, to greatly reduce risk of identifier reuse.
7899 - When we're choosing an exit node for a circuit, and we have
7900 no pending streams, choose a good general exit rather than one that
7901 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
7902 - Fix another case of assuming, when a specific exit is requested,
7903 that we know more than the user about what hosts it allows.
7904 Fixes one case of bug 752. Patch from rovv.
7905 - Clip the MaxCircuitDirtiness config option to a minimum of 10
7906 seconds. Warn the user if lower values are given in the
7907 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
7908 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
7909 user if lower values are given in the configuration. Bugfix on
7910 0.1.1.17-rc. Patch by Sebastian.
7911 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
7912 the cache because we already had a v0 descriptor with the same ID.
7913 Bugfix on 0.2.0.18-alpha.
7914 - Fix a race condition when freeing keys shared between main thread
7915 and CPU workers that could result in a memory leak. Bugfix on
7916 0.1.0.1-rc. Fixes bug 889.
7917 - Send a valid END cell back when a client tries to connect to a
7918 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
7919 840. Patch from rovv.
7920 - Check which hops rendezvous stream cells are associated with to
7921 prevent possible guess-the-streamid injection attacks from
7922 intermediate hops. Fixes another case of bug 446. Based on patch
7924 - If a broken client asks a non-exit router to connect somewhere,
7925 do not even do the DNS lookup before rejecting the connection.
7926 Fixes another case of bug 619. Patch from rovv.
7927 - When a relay gets a create cell it can't decrypt (e.g. because it's
7928 using the wrong onion key), we were dropping it and letting the
7929 client time out. Now actually answer with a destroy cell. Fixes
7930 bug 904. Bugfix on 0.0.2pre8.
7932 o Minor bugfixes (hidden services):
7933 - Do not throw away existing introduction points on SIGHUP. Bugfix on
7934 0.0.6pre1. Patch by Karsten. Fixes bug 874.
7937 - Report the case where all signatures in a detached set are rejected
7938 differently than the case where there is an error handling the
7940 - When we realize that another process has modified our cached
7941 descriptors, print out a more useful error message rather than
7942 triggering an assertion. Fixes bug 885. Patch from Karsten.
7943 - Implement the 0x20 hack to better resist DNS poisoning: set the
7944 case on outgoing DNS requests randomly, and reject responses that do
7945 not match the case correctly. This logic can be disabled with the
7946 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
7947 of servers that do not reliably preserve case in replies. See
7948 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
7950 - Check DNS replies for more matching fields to better resist DNS
7952 - Never use OpenSSL compression: it wastes RAM and CPU trying to
7953 compress cells, which are basically all encrypted, compressed, or
7957 Changes in version 0.2.1.11-alpha - 2009-01-20
7958 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
7959 week it will take a long time to bootstrap again" bug. It also fixes
7960 an important security-related bug reported by Ilja van Sprundel. You
7961 should upgrade. (We'll send out more details about the bug once people
7962 have had some time to upgrade.)
7965 - Fix a heap-corruption bug that may be remotely triggerable on
7966 some platforms. Reported by Ilja van Sprundel.
7969 - Discard router descriptors as we load them if they are more than
7970 five days old. Otherwise if Tor is off for a long time and then
7971 starts with cached descriptors, it will try to use the onion
7972 keys in those obsolete descriptors when building circuits. Bugfix
7973 on 0.2.0.x. Fixes bug 887.
7976 - Try to make sure that the version of Libevent we're running with
7977 is binary-compatible with the one we built with. May address bug
7979 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
7980 for bug 905. Bugfix on 0.2.1.7-alpha.
7981 - Add a new --enable-local-appdata configuration switch to change
7982 the default location of the datadir on win32 from APPDATA to
7983 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
7984 entirely. Patch from coderman.
7987 - Make outbound DNS packets respect the OutboundBindAddress setting.
7988 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
7989 - When our circuit fails at the first hop (e.g. we get a destroy
7990 cell back), avoid using that OR connection anymore, and also
7991 tell all the one-hop directory requests waiting for it that they
7992 should fail. Bugfix on 0.2.1.3-alpha.
7993 - In the torify(1) manpage, mention that tsocks will leak your
7997 Changes in version 0.2.1.10-alpha - 2009-01-06
7998 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
7999 would make the bridge relay not so useful if it had DirPort set to 0,
8000 and one that could let an attacker learn a little bit of information
8001 about the bridge's users), and a bug that would cause your Tor relay
8002 to ignore a circuit create request it can't decrypt (rather than reply
8003 with an error). It also fixes a wide variety of other bugs.
8006 - If the cached networkstatus consensus is more than five days old,
8007 discard it rather than trying to use it. In theory it could
8008 be useful because it lists alternate directory mirrors, but in
8009 practice it just means we spend many minutes trying directory
8010 mirrors that are long gone from the network. Helps bug 887 a bit;
8012 - Bridge relays that had DirPort set to 0 would stop fetching
8013 descriptors shortly after startup, and then briefly resume
8014 after a new bandwidth test and/or after publishing a new bridge
8015 descriptor. Bridge users that try to bootstrap from them would
8016 get a recent networkstatus but would get descriptors from up to
8017 18 hours earlier, meaning most of the descriptors were obsolete
8018 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
8019 - Prevent bridge relays from serving their 'extrainfo' document
8020 to anybody who asks, now that extrainfo docs include potentially
8021 sensitive aggregated client geoip summaries. Bugfix on
8025 - New controller event "clients_seen" to report a geoip-based summary
8026 of which countries we've seen clients from recently. Now controllers
8027 like Vidalia can show bridge operators that they're actually making
8029 - Build correctly against versions of OpenSSL 0.9.8 or later built
8030 without support for deprecated functions.
8031 - Update to the "December 19 2008" ip-to-country file.
8033 o Minor bugfixes (on 0.2.0.x):
8034 - Authorities now vote for the Stable flag for any router whose
8035 weighted MTBF is at least 5 days, regardless of the mean MTBF.
8036 - Do not remove routers as too old if we do not have any consensus
8037 document. Bugfix on 0.2.0.7-alpha.
8038 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
8039 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
8040 - When an exit relay resolves a stream address to a local IP address,
8041 do not just keep retrying that same exit relay over and
8042 over. Instead, just close the stream. Addresses bug 872. Bugfix
8043 on 0.2.0.32. Patch from rovv.
8044 - If a hidden service sends us an END cell, do not consider
8045 retrying the connection; just close it. Patch from rovv.
8046 - When we made bridge authorities stop serving bridge descriptors over
8047 unencrypted links, we also broke DirPort reachability testing for
8048 bridges. So bridges with a non-zero DirPort were printing spurious
8049 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
8050 - When a relay gets a create cell it can't decrypt (e.g. because it's
8051 using the wrong onion key), we were dropping it and letting the
8052 client time out. Now actually answer with a destroy cell. Fixes
8053 bug 904. Bugfix on 0.0.2pre8.
8054 - Squeeze 2-5% out of client performance (according to oprofile) by
8055 improving the implementation of some policy-manipulation functions.
8057 o Minor bugfixes (on 0.2.1.x):
8058 - Make get_interface_address() function work properly again; stop
8059 guessing the wrong parts of our address as our address.
8060 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
8061 send on that circuit. Otherwise we might violate the proposal-110
8062 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
8064 - When we're sending non-EXTEND cells to the first hop in a circuit,
8065 for example to use an encrypted directory connection, we don't need
8066 to use RELAY_EARLY cells: the first hop knows what kind of cell
8067 it is, and nobody else can even see the cell type. Conserving
8068 RELAY_EARLY cells makes it easier to cannibalize circuits like
8070 - Stop logging nameserver addresses in reverse order.
8071 - If we are retrying a directory download slowly over and over, do
8072 not automatically give up after the 254th failure. Bugfix on
8074 - Resume reporting accurate "stream end" reasons to the local control
8075 port. They were lost in the changes for Proposal 148. Bugfix on
8078 o Deprecated and removed features:
8079 - The old "tor --version --version" command, which would print out
8080 the subversion "Id" of most of the source files, is now removed. It
8081 turned out to be less useful than we'd expected, and harder to
8084 o Code simplifications and refactoring:
8085 - Change our header file guard macros to be less likely to conflict
8086 with system headers. Adam Langley noticed that we were conflicting
8087 with log.h on Android.
8088 - Tool-assisted documentation cleanup. Nearly every function or
8089 static variable in Tor should have its own documentation now.
8092 Changes in version 0.2.1.9-alpha - 2008-12-25
8093 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
8095 o New directory authorities:
8096 - gabelmoo (the authority run by Karsten Loesing) now has a new
8100 - Never use a connection with a mismatched address to extend a
8101 circuit, unless that connection is canonical. A canonical
8102 connection is one whose address is authenticated by the router's
8103 identity key, either in a NETINFO cell or in a router descriptor.
8104 - Avoid a possible memory corruption bug when receiving hidden service
8105 descriptors. Bugfix on 0.2.1.6-alpha.
8108 - Fix a logic error that would automatically reject all but the first
8109 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
8110 part of bug 813/868. Bug spotted by coderman.
8111 - When a stream at an exit relay is in state "resolving" or
8112 "connecting" and it receives an "end" relay cell, the exit relay
8113 would silently ignore the end cell and not close the stream. If
8114 the client never closes the circuit, then the exit relay never
8115 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
8117 - When we can't initialize DNS because the network is down, do not
8118 automatically stop Tor from starting. Instead, retry failed
8119 dns_init() every 10 minutes, and change the exit policy to reject
8120 *:* until one succeeds. Fixes bug 691.
8123 - Give a better error message when an overzealous init script says
8124 "sudo -u username tor --user username". Makes Bug 882 easier for
8126 - When a directory authority gives us a new guess for our IP address,
8127 log which authority we used. Hopefully this will help us debug
8128 the recent complaints about bad IP address guesses.
8129 - Detect svn revision properly when we're using git-svn.
8130 - Try not to open more than one descriptor-downloading connection
8131 to an authority at once. This should reduce load on directory
8132 authorities. Fixes bug 366.
8133 - Add cross-certification to newly generated certificates, so that
8134 a signing key is enough information to look up a certificate.
8135 Partial implementation of proposal 157.
8136 - Start serving certificates by <identity digest, signing key digest>
8137 pairs. Partial implementation of proposal 157.
8138 - Clients now never report any stream end reason except 'MISC'.
8139 Implements proposal 148.
8140 - On platforms with a maximum syslog string length, truncate syslog
8141 messages to that length ourselves, rather than relying on the
8142 system to do it for us.
8143 - Optimize out calls to time(NULL) that occur for every IO operation,
8144 or for every cell. On systems where time() is a slow syscall,
8145 this fix will be slightly helpful.
8146 - Exit servers can now answer resolve requests for ip6.arpa addresses.
8147 - When we download a descriptor that we then immediately (as
8148 a directory authority) reject, do not retry downloading it right
8149 away. Should save some bandwidth on authorities. Fix for bug
8150 888. Patch by Sebastian Hahn.
8151 - When a download gets us zero good descriptors, do not notify
8152 Tor that new directory information has arrived.
8153 - Avoid some nasty corner cases in the logic for marking connections
8154 as too old or obsolete or noncanonical for circuits. Partial
8157 o Minor features (controller):
8158 - New CONSENSUS_ARRIVED event to note when a new consensus has
8159 been fetched and validated.
8160 - When we realize that another process has modified our cached
8161 descriptors file, print out a more useful error message rather
8162 than triggering an assertion. Fixes bug 885. Patch from Karsten.
8163 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
8164 controllers to prevent SIGHUP from reloading the
8165 configuration. Fixes bug 856.
8168 - Resume using the correct "REASON=" stream when telling the
8169 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
8170 - When a canonical connection appears later in our internal list
8171 than a noncanonical one for a given OR ID, always use the
8172 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
8174 - Clip the MaxCircuitDirtiness config option to a minimum of 10
8175 seconds. Warn the user if lower values are given in the
8176 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
8177 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
8178 user if lower values are given in the configuration. Bugfix on
8179 0.1.1.17-rc. Patch by Sebastian.
8180 - Fix a race condition when freeing keys shared between main thread
8181 and CPU workers that could result in a memory leak. Bugfix on
8182 0.1.0.1-rc. Fixes bug 889.
8184 o Minor bugfixes (hidden services):
8185 - Do not throw away existing introduction points on SIGHUP (bugfix on
8186 0.0.6pre1); also, do not stall hidden services because we're
8187 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
8188 by John Brooks. Patch by Karsten. Fixes bug 874.
8189 - Fix a memory leak when we decline to add a v2 rendezvous
8190 descriptor to the cache because we already had a v0 descriptor
8191 with the same ID. Bugfix on 0.2.0.18-alpha.
8193 o Deprecated and removed features:
8194 - RedirectExits has been removed. It was deprecated since
8196 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
8197 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
8198 - Cell pools are now always enabled; --disable-cell-pools is ignored.
8200 o Code simplifications and refactoring:
8201 - Rename the confusing or_is_obsolete field to the more appropriate
8202 is_bad_for_new_circs, and move it to or_connection_t where it
8204 - Move edge-only flags from connection_t to edge_connection_t: not
8205 only is this better coding, but on machines of plausible alignment,
8206 it should save 4-8 bytes per connection_t. "Every little bit helps."
8207 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
8208 for consistency; keep old option working for backward compatibility.
8209 - Simplify the code for finding connections to use for a circuit.
8212 Changes in version 0.2.1.8-alpha - 2008-12-08
8213 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
8214 builds better on unusual platforms like Solaris and old OS X, and
8215 fixes a variety of other issues.
8218 - New DirPortFrontPage option that takes an html file and publishes
8219 it as "/" on the DirPort. Now relay operators can provide a
8220 disclaimer without needing to set up a separate webserver. There's
8221 a sample disclaimer in contrib/tor-exit-notice.html.
8224 - When the client is choosing entry guards, now it selects at most
8225 one guard from a given relay family. Otherwise we could end up with
8226 all of our entry points into the network run by the same operator.
8227 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
8230 - Fix a DOS opportunity during the voting signature collection process
8231 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8232 - Fix a possible segfault when establishing an exit connection. Bugfix
8236 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
8238 - Made Tor a little less aggressive about deleting expired
8239 certificates. Partial fix for bug 854.
8240 - Stop doing unaligned memory access that generated bus errors on
8241 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
8242 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
8243 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
8244 - Make USR2 log-level switch take effect immediately. Bugfix on
8246 - If one win32 nameserver fails to get added, continue adding the
8247 rest, and don't automatically fail.
8248 - Use fcntl() for locking when flock() is not available. Should fix
8249 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
8250 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
8251 could make gcc generate non-functional binary search code. Bugfix
8253 - Build correctly on platforms without socklen_t.
8254 - Avoid potential crash on internal error during signature collection.
8255 Fixes bug 864. Patch from rovv.
8256 - Do not use C's stdio library for writing to log files. This will
8257 improve logging performance by a minute amount, and will stop
8258 leaking fds when our disk is full. Fixes bug 861.
8259 - Stop erroneous use of O_APPEND in cases where we did not in fact
8260 want to re-seek to the end of a file before every last write().
8261 - Correct handling of possible malformed authority signing key
8262 certificates with internal signature types. Fixes bug 880. Bugfix
8264 - Fix a hard-to-trigger resource leak when logging credential status.
8268 - Directory mirrors no longer fetch the v1 directory or
8269 running-routers files. They are obsolete, and nobody asks for them
8270 anymore. This is the first step to making v1 authorities obsolete.
8272 o Minor features (controller):
8273 - Return circuit purposes in response to GETINFO circuit-status. Fixes
8277 Changes in version 0.2.0.32 - 2008-11-20
8278 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
8279 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8280 a smaller security flaw that might allow an attacker to access local
8281 services, further improves hidden service performance, and fixes a
8282 variety of other issues.
8285 - The "User" and "Group" config options did not clear the
8286 supplementary group entries for the Tor process. The "User" option
8287 is now more robust, and we now set the groups to the specified
8288 user's primary group. The "Group" option is now ignored. For more
8289 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8290 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8291 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
8292 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8293 consistently obeyed: if an exit relay refuses a stream because its
8294 exit policy doesn't allow it, we would remember what IP address
8295 the relay said the destination address resolves to, even if it's
8296 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8299 - Fix a DOS opportunity during the voting signature collection process
8300 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8302 o Major bugfixes (hidden services):
8303 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8304 we were failing the whole hidden service request when the v0
8305 descriptor fetch fails, even if the v2 fetch is still pending and
8306 might succeed. Similarly, if the last v2 fetch fails, we were
8307 failing the whole hidden service request even if a v0 fetch is
8308 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8309 - When extending a circuit to a hidden service directory to upload a
8310 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8311 requests failed, because the router descriptor has not been
8312 downloaded yet. In these cases, do not attempt to upload the
8313 rendezvous descriptor, but wait until the router descriptor is
8314 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
8315 descriptor from a hidden service directory for which the router
8316 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
8320 - Fix several infrequent memory leaks spotted by Coverity.
8321 - When testing for libevent functions, set the LDFLAGS variable
8322 correctly. Found by Riastradh.
8323 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8324 bootstrapping with tunneled directory connections. Bugfix on
8325 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8326 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8327 and we know that server B rejects most-but-not all connections to
8328 port 80, we would previously reject the connection. Now, we assume
8329 the user knows what they were asking for. Fixes bug 752. Bugfix
8330 on 0.0.9rc5. Diagnosed by BarkerJr.
8331 - If we overrun our per-second write limits a little, count this as
8332 having used up our write allocation for the second, and choke
8333 outgoing directory writes. Previously, we had only counted this when
8334 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
8335 Bugfix on 0.2.0.x (??).
8336 - Remove the old v2 directory authority 'lefkada' from the default
8337 list. It has been gone for many months.
8338 - Stop doing unaligned memory access that generated bus errors on
8339 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
8340 - Make USR2 log-level switch take effect immediately. Bugfix on
8343 o Minor bugfixes (controller):
8344 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
8345 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
8348 Changes in version 0.2.1.7-alpha - 2008-11-08
8349 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
8350 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8351 a smaller security flaw that might allow an attacker to access local
8352 services, adds better defense against DNS poisoning attacks on exit
8353 relays, further improves hidden service performance, and fixes a
8354 variety of other issues.
8357 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8358 consistently obeyed: if an exit relay refuses a stream because its
8359 exit policy doesn't allow it, we would remember what IP address
8360 the relay said the destination address resolves to, even if it's
8361 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8362 - The "User" and "Group" config options did not clear the
8363 supplementary group entries for the Tor process. The "User" option
8364 is now more robust, and we now set the groups to the specified
8365 user's primary group. The "Group" option is now ignored. For more
8366 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8367 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8368 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
8369 - Do not use or believe expired v3 authority certificates. Patch
8370 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
8373 - Now NodeFamily and MyFamily config options allow spaces in
8374 identity fingerprints, so it's easier to paste them in.
8375 Suggested by Lucky Green.
8376 - Implement the 0x20 hack to better resist DNS poisoning: set the
8377 case on outgoing DNS requests randomly, and reject responses that do
8378 not match the case correctly. This logic can be disabled with the
8379 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
8380 of servers that do not reliably preserve case in replies. See
8381 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
8383 - Preserve case in replies to DNSPort requests in order to support
8384 the 0x20 hack for resisting DNS poisoning attacks.
8386 o Hidden service performance improvements:
8387 - When the client launches an introduction circuit, retry with a
8388 new circuit after 30 seconds rather than 60 seconds.
8389 - Launch a second client-side introduction circuit in parallel
8390 after a delay of 15 seconds (based on work by Christian Wilms).
8391 - Hidden services start out building five intro circuits rather
8392 than three, and when the first three finish they publish a service
8393 descriptor using those. Now we publish our service descriptor much
8394 faster after restart.
8397 - Minor fix in the warning messages when you're having problems
8398 bootstrapping; also, be more forgiving of bootstrap problems when
8399 we're still making incremental progress on a given bootstrap phase.
8400 - When we're choosing an exit node for a circuit, and we have
8401 no pending streams, choose a good general exit rather than one that
8402 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
8403 - Send a valid END cell back when a client tries to connect to a
8404 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
8405 840. Patch from rovv.
8406 - If a broken client asks a non-exit router to connect somewhere,
8407 do not even do the DNS lookup before rejecting the connection.
8408 Fixes another case of bug 619. Patch from rovv.
8409 - Fix another case of assuming, when a specific exit is requested,
8410 that we know more than the user about what hosts it allows.
8411 Fixes another case of bug 752. Patch from rovv.
8412 - Check which hops rendezvous stream cells are associated with to
8413 prevent possible guess-the-streamid injection attacks from
8414 intermediate hops. Fixes another case of bug 446. Based on patch
8416 - Avoid using a negative right-shift when comparing 32-bit
8417 addresses. Possible fix for bug 845 and bug 811.
8418 - Make the assert_circuit_ok() function work correctly on circuits that
8419 have already been marked for close.
8420 - Fix read-off-the-end-of-string error in unit tests when decoding
8421 introduction points.
8422 - Fix uninitialized size field for memory area allocation: may improve
8423 memory performance during directory parsing.
8424 - Treat duplicate certificate fetches as failures, so that we do
8425 not try to re-fetch an expired certificate over and over and over.
8426 - Do not say we're fetching a certificate when we'll in fact skip it
8427 because of a pending download.
8430 Changes in version 0.2.1.6-alpha - 2008-09-30
8431 Tor 0.2.1.6-alpha further improves performance and robustness of
8432 hidden services, starts work on supporting per-country relay selection,
8433 and fixes a variety of smaller issues.
8436 - Implement proposal 121: make it possible to build hidden services
8437 that only certain clients are allowed to connect to. This is
8438 enforced at several points, so that unauthorized clients are unable
8439 to send INTRODUCE cells to the service, or even (depending on the
8440 type of authentication) to learn introduction points. This feature
8441 raises the bar for certain kinds of active attacks against hidden
8442 services. Code by Karsten Loesing.
8443 - Relays now store and serve v2 hidden service descriptors by default,
8444 i.e., the new default value for HidServDirectoryV2 is 1. This is
8445 the last step in proposal 114, which aims to make hidden service
8446 lookups more reliable.
8447 - Start work to allow node restrictions to include country codes. The
8448 syntax to exclude nodes in a country with country code XX is
8449 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
8450 refinement to decide what config options should take priority if
8451 you ask to both use a particular node and exclude it.
8452 - Allow ExitNodes list to include IP ranges and country codes, just
8453 like the Exclude*Nodes lists. Patch from Robert Hogan.
8456 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
8457 Tor to fail to start if you had it configured to use a bridge
8458 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
8459 - When extending a circuit to a hidden service directory to upload a
8460 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8461 requests failed, because the router descriptor had not been
8462 downloaded yet. In these cases, we now wait until the router
8463 descriptor is downloaded, and then retry. Likewise, clients
8464 now skip over a hidden service directory if they don't yet have
8465 its router descriptor, rather than futilely requesting it and
8466 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
8468 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8469 we were failing the whole hidden service request when the v0
8470 descriptor fetch fails, even if the v2 fetch is still pending and
8471 might succeed. Similarly, if the last v2 fetch fails, we were
8472 failing the whole hidden service request even if a v0 fetch is
8473 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8474 - DNS replies need to have names matching their requests, but
8475 these names should be in the questions section, not necessarily
8476 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
8479 - Update to the "September 1 2008" ip-to-country file.
8480 - Allow ports 465 and 587 in the default exit policy again. We had
8481 rejected them in 0.1.0.15, because back in 2005 they were commonly
8482 misconfigured and ended up as spam targets. We hear they are better
8483 locked down these days.
8484 - Use a lockfile to make sure that two Tor processes are not
8485 simultaneously running with the same datadir.
8486 - Serve the latest v3 networkstatus consensus via the control
8487 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
8488 - Better logging about stability/reliability calculations on directory
8490 - Drop the requirement to have an open dir port for storing and
8491 serving v2 hidden service descriptors.
8492 - Directory authorities now serve a /tor/dbg-stability.txt URL to
8493 help debug WFU and MTBF calculations.
8494 - Implement most of Proposal 152: allow specialized servers to permit
8495 single-hop circuits, and clients to use those servers to build
8496 single-hop circuits when using a specialized controller. Patch
8497 from Josh Albrecht. Resolves feature request 768.
8498 - Add a -p option to tor-resolve for specifying the SOCKS port: some
8499 people find host:port too confusing.
8500 - Make TrackHostExit mappings expire a while after their last use, not
8501 after their creation. Patch from Robert Hogan.
8502 - Provide circuit purposes along with circuit events to the controller.
8505 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
8507 - Fixed some memory leaks -- some quite frequent, some almost
8508 impossible to trigger -- based on results from Coverity.
8509 - When testing for libevent functions, set the LDFLAGS variable
8510 correctly. Found by Riastradh.
8511 - Fix an assertion bug in parsing policy-related options; possible fix
8513 - Catch and report a few more bootstrapping failure cases when Tor
8514 fails to establish a TCP connection. Cleanup on 0.2.1.x.
8515 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8516 bootstrapping with tunneled directory connections. Bugfix on
8517 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8518 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8519 and we know that server B rejects most-but-not all connections to
8520 port 80, we would previously reject the connection. Now, we assume
8521 the user knows what they were asking for. Fixes bug 752. Bugfix
8522 on 0.0.9rc5. Diagnosed by BarkerJr.
8523 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
8524 service directories if they have no advertised dir port. Bugfix
8526 - If we overrun our per-second write limits a little, count this as
8527 having used up our write allocation for the second, and choke
8528 outgoing directory writes. Previously, we had only counted this when
8529 we had met our limits precisely. Fixes bug 824. Patch by rovv.
8530 Bugfix on 0.2.0.x (??).
8531 - Avoid a "0 divided by 0" calculation when calculating router uptime
8532 at directory authorities. Bugfix on 0.2.0.8-alpha.
8533 - Make DNS resolved controller events into "CLOSED", not
8534 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
8536 - Fix a bug where an unreachable relay would establish enough
8537 reachability testing circuits to do a bandwidth test -- if
8538 we already have a connection to the middle hop of the testing
8539 circuit, then it could establish the last hop by using the existing
8540 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
8541 circuits no longer use entry guards in 0.2.1.3-alpha.
8542 - If we have correct permissions on $datadir, we complain to stdout
8543 and fail to start. But dangerous permissions on
8544 $datadir/cached-status/ would cause us to open a log and complain
8545 there. Now complain to stdout and fail to start in both cases. Fixes
8546 bug 820, reported by seeess.
8547 - Remove the old v2 directory authority 'lefkada' from the default
8548 list. It has been gone for many months.
8550 o Code simplifications and refactoring:
8551 - Revise the connection_new functions so that a more typesafe variant
8552 exists. This will work better with Coverity, and let us find any
8553 actual mistakes we're making here.
8554 - Refactor unit testing logic so that dmalloc can be used sensibly
8555 with unit tests to check for memory leaks.
8556 - Move all hidden-service related fields from connection and circuit
8557 structure to substructures: this way they won't eat so much memory.
8560 Changes in version 0.2.0.31 - 2008-09-03
8561 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
8562 a big bug we're seeing where in rare cases traffic from one Tor stream
8563 gets mixed into another stream, and fixes a variety of smaller issues.
8566 - Make sure that two circuits can never exist on the same connection
8567 with the same circuit ID, even if one is marked for close. This
8568 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
8569 - Relays now reject risky extend cells: if the extend cell includes
8570 a digest of all zeroes, or asks to extend back to the relay that
8571 sent the extend cell, tear down the circuit. Ideas suggested
8573 - If not enough of our entry guards are available so we add a new
8574 one, we might use the new one even if it overlapped with the
8575 current circuit's exit relay (or its family). Anonymity bugfix
8576 pointed out by rovv.
8579 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8580 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8581 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8582 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8583 - Pick size of default geoip filename string correctly on windows.
8584 Fixes bug 806. Bugfix on 0.2.0.30.
8585 - Make the autoconf script accept the obsolete --with-ssl-dir
8586 option as an alias for the actually-working --with-openssl-dir
8587 option. Fix the help documentation to recommend --with-openssl-dir.
8588 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8589 - When using the TransPort option on OpenBSD, and using the User
8590 option to change UID and drop privileges, make sure to open
8591 /dev/pf before dropping privileges. Fixes bug 782. Patch from
8592 Christopher Davis. Bugfix on 0.1.2.1-alpha.
8593 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8594 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8595 on the client side when connecting to a hidden service. Bugfix
8596 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8597 - When closing an application-side connection because its circuit is
8598 getting torn down, generate the stream event correctly. Bugfix on
8599 0.1.2.x. Anonymous patch.
8602 Changes in version 0.2.1.5-alpha - 2008-08-31
8603 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
8604 in a lot of the infrastructure for adding authorization to hidden
8605 services, lays the groundwork for having clients read their load
8606 balancing information out of the networkstatus consensus rather than
8607 the individual router descriptors, addresses two potential anonymity
8608 issues, and fixes a variety of smaller issues.
8611 - Convert many internal address representations to optionally hold
8613 - Generate and accept IPv6 addresses in many protocol elements.
8614 - Make resolver code handle nameservers located at ipv6 addresses.
8615 - Begin implementation of proposal 121 ("Client authorization for
8616 hidden services"): configure hidden services with client
8617 authorization, publish descriptors for them, and configure
8618 authorization data for hidden services at clients. The next
8619 step is to actually access hidden services that perform client
8621 - More progress toward proposal 141: Network status consensus
8622 documents and votes now contain bandwidth information for each
8623 router and a summary of that router's exit policy. Eventually this
8624 will be used by clients so that they do not have to download every
8625 known descriptor before building circuits.
8627 o Major bugfixes (on 0.2.0.x and before):
8628 - When sending CREATED cells back for a given circuit, use a 64-bit
8629 connection ID to find the right connection, rather than an addr:port
8630 combination. Now that we can have multiple OR connections between
8631 the same ORs, it is no longer possible to use addr:port to uniquely
8632 identify a connection.
8633 - Relays now reject risky extend cells: if the extend cell includes
8634 a digest of all zeroes, or asks to extend back to the relay that
8635 sent the extend cell, tear down the circuit. Ideas suggested
8637 - If not enough of our entry guards are available so we add a new
8638 one, we might use the new one even if it overlapped with the
8639 current circuit's exit relay (or its family). Anonymity bugfix
8640 pointed out by rovv.
8643 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8644 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8645 - When using the TransPort option on OpenBSD, and using the User
8646 option to change UID and drop privileges, make sure to open /dev/pf
8647 before dropping privileges. Fixes bug 782. Patch from Christopher
8648 Davis. Bugfix on 0.1.2.1-alpha.
8649 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8650 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8651 - Add a missing safe_str() call for a debug log message.
8652 - Use 64 bits instead of 32 bits for connection identifiers used with
8653 the controller protocol, to greatly reduce risk of identifier reuse.
8654 - Make the autoconf script accept the obsolete --with-ssl-dir
8655 option as an alias for the actually-working --with-openssl-dir
8656 option. Fix the help documentation to recommend --with-openssl-dir.
8657 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8660 - Rate-limit too-many-sockets messages: when they happen, they happen
8661 a lot. Resolves bug 748.
8662 - Resist DNS poisoning a little better by making sure that names in
8663 answer sections match.
8664 - Print the SOCKS5 error message string as well as the error code
8665 when a tor-resolve request fails. Patch from Jacob.
8668 Changes in version 0.2.1.4-alpha - 2008-08-04
8669 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
8672 - The address part of exit policies was not correctly written
8673 to router descriptors. This generated router descriptors that failed
8674 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
8676 - Tor triggered a false assert when extending a circuit to a relay
8677 but we already have a connection open to that relay. Noticed by
8678 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
8681 - Fix a hidden service logging bug: in some edge cases, the router
8682 descriptor of a previously picked introduction point becomes
8683 obsolete and we need to give up on it rather than continually
8684 complaining that it has become obsolete. Observed by xiando. Bugfix
8688 - Take out the TestVia config option, since it was a workaround for
8689 a bug that was fixed in Tor 0.1.1.21.
8692 Changes in version 0.2.1.3-alpha - 2008-08-03
8693 Tor 0.2.1.3-alpha implements most of the pieces to prevent
8694 infinite-length circuit attacks (see proposal 110); fixes a bug that
8695 might cause exit relays to corrupt streams they send back; allows
8696 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
8697 ExcludeExitNodes config options; and fixes a big pile of bugs.
8699 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
8700 - Send a bootstrap problem "warn" event on the first problem if the
8701 reason is NO_ROUTE (that is, our network is down).
8704 - Implement most of proposal 110: The first K cells to be sent
8705 along a circuit are marked as special "early" cells; only K "early"
8706 cells will be allowed. Once this code is universal, we can block
8707 certain kinds of DOS attack by requiring that EXTEND commands must
8708 be sent using an "early" cell.
8711 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8712 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8713 on the client side when connecting to a hidden service. Bugfix
8714 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8715 - Ensure that two circuits can never exist on the same connection
8716 with the same circuit ID, even if one is marked for close. This
8717 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
8720 - When relays do their initial bandwidth measurement, don't limit
8721 to just our entry guards for the test circuits. Otherwise we tend
8722 to have multiple test circuits going through a single entry guard,
8723 which makes our bandwidth test less accurate. Fixes part of bug 654;
8724 patch contributed by Josh Albrecht.
8725 - Add an ExcludeExitNodes option so users can list a set of nodes
8726 that should be be excluded from the exit node position, but
8727 allowed elsewhere. Implements proposal 151.
8728 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
8729 ExcludeNodes and ExcludeExitNodes lists.
8730 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
8731 be more efficient. Formerly it was quadratic in the number of
8732 servers; now it should be linear. Fixes bug 509.
8733 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
8734 and n_conn_id_digest fields into a separate structure that's
8735 only needed when the circuit has not yet attached to an n_conn.
8738 - Change the contrib/tor.logrotate script so it makes the new
8739 logs as "_tor:_tor" rather than the default, which is generally
8740 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
8741 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8742 warnings (occasionally), but it can also cause the compiler to
8743 eliminate error-checking code. Suggested by Peter Gutmann.
8744 - When a hidden service is giving up on an introduction point candidate
8745 that was not included in the last published rendezvous descriptor,
8746 don't reschedule publication of the next descriptor. Fixes bug 763.
8748 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
8749 HiddenServiceExcludeNodes as obsolete: they never worked properly,
8750 and nobody claims to be using them. Fixes bug 754. Bugfix on
8751 0.1.0.1-rc. Patch from Christian Wilms.
8752 - Fix a small alignment and memory-wasting bug on buffer chunks.
8755 o Minor bugfixes (controller):
8756 - When closing an application-side connection because its circuit
8757 is getting torn down, generate the stream event correctly.
8758 Bugfix on 0.1.2.x. Anonymous patch.
8761 - Remove all backward-compatibility code to support relays running
8762 versions of Tor so old that they no longer work at all on the
8766 Changes in version 0.2.0.30 - 2008-07-15
8768 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8769 warnings (occasionally), but it can also cause the compiler to
8770 eliminate error-checking code. Suggested by Peter Gutmann.
8773 Changes in version 0.2.0.29-rc - 2008-07-08
8774 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
8775 hidden-service performance bugs, and fixes a bunch of smaller bugs.
8778 - If you have more than one bridge but don't know their keys,
8779 you would only launch a request for the descriptor of the first one
8780 on your list. (Tor considered launching requests for the others, but
8781 found that it already had a connection on the way for $0000...0000
8782 so it didn't open another.) Bugfix on 0.2.0.x.
8783 - If you have more than one bridge but don't know their keys, and the
8784 connection to one of the bridges failed, you would cancel all
8785 pending bridge connections. (After all, they all have the same
8786 digest.) Bugfix on 0.2.0.x.
8787 - When a hidden service was trying to establish an introduction point,
8788 and Tor had built circuits preemptively for such purposes, we
8789 were ignoring all the preemptive circuits and launching a new one
8790 instead. Bugfix on 0.2.0.14-alpha.
8791 - When a hidden service was trying to establish an introduction point,
8792 and Tor *did* manage to reuse one of the preemptively built
8793 circuits, it didn't correctly remember which one it used,
8794 so it asked for another one soon after, until there were no
8795 more preemptive circuits, at which point it launched one from
8796 scratch. Bugfix on 0.0.9.x.
8797 - Make directory servers include the X-Your-Address-Is: http header in
8798 their responses even for begin_dir conns. Now clients who only
8799 ever use begin_dir connections still have a way to learn their IP
8800 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
8803 - Fix a macro/CPP interaction that was confusing some compilers:
8804 some GCCs don't like #if/#endif pairs inside macro arguments.
8806 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
8807 Fixes bug 704; fix from Steven Murdoch.
8808 - When opening /dev/null in finish_daemonize(), do not pass the
8809 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
8810 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
8811 - Correctly detect transparent proxy support on Linux hosts that
8812 require in.h to be included before netfilter_ipv4.h. Patch
8814 - Disallow session resumption attempts during the renegotiation
8815 stage of the v2 handshake protocol. Clients should never be trying
8816 session resumption at this point, but apparently some did, in
8817 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
8818 found by Geoff Goodell.
8821 Changes in version 0.2.1.2-alpha - 2008-06-20
8822 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
8823 make it easier to set up your own private Tor network; fixes several
8824 big bugs with using more than one bridge relay; fixes a big bug with
8825 offering hidden services quickly after Tor starts; and uses a better
8826 API for reporting potential bootstrapping problems to the controller.
8829 - New TestingTorNetwork config option to allow adjustment of
8830 previously constant values that, while reasonable, could slow
8831 bootstrapping. Implements proposal 135. Patch from Karsten.
8834 - If you have more than one bridge but don't know their digests,
8835 you would only learn a request for the descriptor of the first one
8836 on your list. (Tor considered launching requests for the others, but
8837 found that it already had a connection on the way for $0000...0000
8838 so it didn't open another.) Bugfix on 0.2.0.x.
8839 - If you have more than one bridge but don't know their digests,
8840 and the connection to one of the bridges failed, you would cancel
8841 all pending bridge connections. (After all, they all have the
8842 same digest.) Bugfix on 0.2.0.x.
8843 - When establishing a hidden service, introduction points that
8844 originate from cannibalized circuits are completely ignored and not
8845 included in rendezvous service descriptors. This might be another
8846 reason for delay in making a hidden service available. Bugfix
8847 from long ago (0.0.9.x?)
8850 - Allow OpenSSL to use dynamic locks if it wants.
8851 - When building a consensus, do not include routers that are down.
8852 This will cut down 30% to 40% on consensus size. Implements
8854 - In directory authorities' approved-routers files, allow
8855 fingerprints with or without space.
8856 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
8857 controller can query our current bootstrap state in case it attaches
8858 partway through and wants to catch up.
8859 - Send an initial "Starting" bootstrap status event, so we have a
8860 state to start out in.
8863 - Asking for a conditional consensus at .../consensus/<fingerprints>
8864 would crash a dirserver if it did not already have a
8865 consensus. Bugfix on 0.2.1.1-alpha.
8866 - Clean up some macro/CPP interactions: some GCC versions don't like
8867 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
8870 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
8871 - Directory authorities shouldn't complain about bootstrapping
8872 problems just because they do a lot of reachability testing and
8873 some of the connection attempts fail.
8874 - Start sending "count" and "recommendation" key/value pairs in
8875 bootstrap problem status events, so the controller can hear about
8876 problems even before Tor decides they're worth reporting for sure.
8877 - If you're using bridges, generate "bootstrap problem" warnings
8878 as soon as you run out of working bridges, rather than waiting
8879 for ten failures -- which will never happen if you have less than
8881 - If we close our OR connection because there's been a circuit
8882 pending on it for too long, we were telling our bootstrap status
8883 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
8886 Changes in version 0.2.1.1-alpha - 2008-06-13
8887 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
8888 were making the Tor process bloat especially on Linux; makes our TLS
8889 handshake blend in better; sends "bootstrap phase" status events to
8890 the controller, so it can keep the user informed of progress (and
8891 problems) fetching directory information and establishing circuits;
8892 and adds a variety of smaller features.
8895 - More work on making our TLS handshake blend in: modify the list
8896 of ciphers advertised by OpenSSL in client mode to even more
8897 closely resemble a common web browser. We cheat a little so that
8898 we can advertise ciphers that the locally installed OpenSSL doesn't
8900 - Start sending "bootstrap phase" status events to the controller,
8901 so it can keep the user informed of progress fetching directory
8902 information and establishing circuits. Also inform the controller
8903 if we think we're stuck at a particular bootstrap phase. Implements
8905 - Resume using OpenSSL's RAND_poll() for better (and more portable)
8906 cross-platform entropy collection again. We used to use it, then
8907 stopped using it because of a bug that could crash systems that
8908 called RAND_poll when they had a lot of fds open. It looks like the
8909 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
8910 at startup, and to call RAND_poll() when we reseed later only if
8911 we have a non-buggy OpenSSL version.
8914 - When we choose to abandon a new entry guard because we think our
8915 older ones might be better, close any circuits pending on that
8916 new entry guard connection. This fix should make us recover much
8917 faster when our network is down and then comes back. Bugfix on
8918 0.1.2.8-beta; found by lodger.
8920 o Memory fixes and improvements:
8921 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
8922 to avoid unused RAM in buffer chunks and memory pools.
8923 - Speed up parsing and cut down on memory fragmentation by using
8924 stack-style allocations for parsing directory objects. Previously,
8925 this accounted for over 40% of allocations from within Tor's code
8926 on a typical directory cache.
8927 - Use a Bloom filter rather than a digest-based set to track which
8928 descriptors we need to keep around when we're cleaning out old
8929 router descriptors. This speeds up the computation significantly,
8930 and may reduce fragmentation.
8931 - Reduce the default smartlist size from 32 to 16; it turns out that
8932 most smartlists hold around 8-12 elements tops.
8933 - Make dumpstats() log the fullness and size of openssl-internal
8935 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
8936 patch to their OpenSSL, turn it on to save memory on servers. This
8937 patch will (with any luck) get included in a mainline distribution
8939 - Never use OpenSSL compression: it wastes RAM and CPU trying to
8940 compress cells, which are basically all encrypted, compressed,
8944 - Stop reloading the router list from disk for no reason when we
8945 run out of reachable directory mirrors. Once upon a time reloading
8946 it would set the 'is_running' flag back to 1 for them. It hasn't
8947 done that for a long time.
8948 - In very rare situations new hidden service descriptors were
8949 published earlier than 30 seconds after the last change to the
8950 service. (We currently think that a hidden service descriptor
8951 that's been stable for 30 seconds is worth publishing.)
8954 - Allow separate log levels to be configured for different logging
8955 domains. For example, this allows one to log all notices, warnings,
8956 or errors, plus all memory management messages of level debug or
8957 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
8958 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
8959 and stop using a warning that had become unfixably verbose under
8961 - New --hush command-line option similar to --quiet. While --quiet
8962 disables all logging to the console on startup, --hush limits the
8963 output to messages of warning and error severity.
8964 - Servers support a new URL scheme for consensus downloads that
8965 allows the client to specify which authorities are trusted.
8966 The server then only sends the consensus if the client will trust
8967 it. Otherwise a 404 error is sent back. Clients use this
8968 new scheme when the server supports it (meaning it's running
8969 0.2.1.1-alpha or later). Implements proposal 134.
8970 - New configure/torrc options (--enable-geoip-stats,
8971 DirRecordUsageByCountry) to record how many IPs we've served
8972 directory info to in each country code, how many status documents
8973 total we've sent to each country code, and what share of the total
8974 directory requests we should expect to see.
8975 - Use the TLS1 hostname extension to more closely resemble browser
8977 - Lots of new unit tests.
8978 - Add a macro to implement the common pattern of iterating through
8979 two parallel lists in lockstep.
8982 Changes in version 0.2.0.28-rc - 2008-06-13
8983 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
8984 performance bug, and fixes a bunch of smaller bugs.
8987 - Fix a bug where, when we were choosing the 'end stream reason' to
8988 put in our relay end cell that we send to the exit relay, Tor
8989 clients on Windows were sometimes sending the wrong 'reason'. The
8990 anonymity problem is that exit relays may be able to guess whether
8991 the client is running Windows, thus helping partition the anonymity
8992 set. Down the road we should stop sending reasons to exit relays,
8993 or otherwise prevent future versions of this bug.
8996 - While setting up a hidden service, some valid introduction circuits
8997 were overlooked and abandoned. This might be the reason for
8998 the long delay in making a hidden service available. Bugfix on
9002 - Update to the "June 9 2008" ip-to-country file.
9003 - Run 'make test' as part of 'make dist', so we stop releasing so
9004 many development snapshots that fail their unit tests.
9007 - When we're checking if we have enough dir info for each relay
9008 to begin establishing circuits, make sure that we actually have
9009 the descriptor listed in the consensus, not just any descriptor.
9011 - Bridge relays no longer print "xx=0" in their extrainfo document
9012 for every single country code in the geoip db. Bugfix on
9014 - Only warn when we fail to load the geoip file if we were planning to
9015 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
9016 - If we change our MaxAdvertisedBandwidth and then reload torrc,
9017 Tor won't realize it should publish a new relay descriptor. Fixes
9018 bug 688, reported by mfr. Bugfix on 0.1.2.x.
9019 - When we haven't had any application requests lately, don't bother
9020 logging that we have expired a bunch of descriptors. Bugfix
9022 - Make relay cells written on a connection count as non-padding when
9023 tracking how long a connection has been in use. Bugfix on
9024 0.2.0.1-alpha. Spotted by lodger.
9025 - Fix unit tests in 0.2.0.27-rc.
9026 - Fix compile on Windows.
9029 Changes in version 0.2.0.27-rc - 2008-06-03
9030 Tor 0.2.0.27-rc adds a few features we left out of the earlier
9031 release candidates. In particular, we now include an IP-to-country
9032 GeoIP database, so controllers can easily look up what country a
9033 given relay is in, and so bridge relays can give us some sanitized
9034 summaries about which countries are making use of bridges. (See proposal
9035 126-geoip-fetching.txt for details.)
9038 - Include an IP-to-country GeoIP file in the tarball, so bridge
9039 relays can report sanitized summaries of the usage they're seeing.
9042 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
9043 Robert Hogan. Fixes the first part of bug 681.
9044 - Make bridge authorities never serve extrainfo docs.
9045 - Add support to detect Libevent versions in the 1.4.x series
9047 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
9048 - Include a new contrib/tor-exit-notice.html file that exit relay
9049 operators can put on their website to help reduce abuse queries.
9052 - When tunneling an encrypted directory connection, and its first
9053 circuit fails, do not leave it unattached and ask the controller
9054 to deal. Fixes the second part of bug 681.
9055 - Make bridge authorities correctly expire old extrainfo documents
9059 Changes in version 0.2.0.26-rc - 2008-05-13
9060 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
9061 in Debian's OpenSSL packages. All users running any 0.2.0.x version
9062 should upgrade, whether they're running Debian or not.
9064 o Major security fixes:
9065 - Use new V3 directory authority keys on the tor26, gabelmoo, and
9066 moria1 V3 directory authorities. The old keys were generated with
9067 a vulnerable version of Debian's OpenSSL package, and must be
9068 considered compromised. Other authorities' keys were not generated
9069 with an affected version of OpenSSL.
9072 - List authority signatures as "unrecognized" based on DirServer
9073 lines, not on cert cache. Bugfix on 0.2.0.x.
9076 - Add a new V3AuthUseLegacyKey option to make it easier for
9077 authorities to change their identity keys if they have to.
9080 Changes in version 0.2.0.25-rc - 2008-04-23
9081 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
9084 - Remember to initialize threading before initializing logging.
9085 Otherwise, many BSD-family implementations will crash hard on
9086 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
9089 - Authorities correctly free policies on bad servers on
9090 exit. Fixes bug 672. Bugfix on 0.2.0.x.
9093 Changes in version 0.2.0.24-rc - 2008-04-22
9094 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
9095 v3 directory authority, makes relays with dynamic IP addresses and no
9096 DirPort notice more quickly when their IP address changes, fixes a few
9097 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
9099 o New directory authorities:
9100 - Take lefkada out of the list of v3 directory authorities, since
9101 it has been down for months.
9102 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
9106 - Detect address changes more quickly on non-directory mirror
9107 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
9109 o Minor features (security):
9110 - Reject requests for reverse-dns lookup of names that are in
9111 a private address space. Patch from lodger.
9112 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
9115 o Minor bugfixes (crashes):
9116 - Avoid a rare assert that can trigger when Tor doesn't have much
9117 directory information yet and it tries to fetch a v2 hidden
9118 service descriptor. Fixes bug 651, reported by nwf.
9119 - Initialize log mutex before initializing dmalloc. Otherwise,
9120 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
9121 - Use recursive pthread mutexes in order to avoid deadlock when
9122 logging debug-level messages to a controller. Bug spotted by nwf,
9123 bugfix on 0.2.0.16-alpha.
9125 o Minor bugfixes (resource management):
9126 - Keep address policies from leaking memory: start their refcount
9127 at 1, not 2. Bugfix on 0.2.0.16-alpha.
9128 - Free authority certificates on exit, so they don't look like memory
9129 leaks. Bugfix on 0.2.0.19-alpha.
9130 - Free static hashtables for policy maps and for TLS connections on
9131 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
9132 - Avoid allocating extra space when computing consensuses on 64-bit
9133 platforms. Bug spotted by aakova.
9135 o Minor bugfixes (misc):
9136 - Do not read the configuration file when we've only been told to
9137 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
9138 based on patch from Sebastian Hahn.
9139 - Exit relays that are used as a client can now reach themselves
9140 using the .exit notation, rather than just launching an infinite
9141 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
9142 - When attempting to open a logfile fails, tell us why.
9143 - Fix a dumb bug that was preventing us from knowing that we should
9144 preemptively build circuits to handle expected directory requests.
9145 Fixes bug 660. Bugfix on 0.1.2.x.
9146 - Warn less verbosely about clock skew from netinfo cells from
9147 untrusted sources. Fixes bug 663.
9148 - Make controller stream events for DNS requests more consistent,
9149 by adding "new stream" events for DNS requests, and removing
9150 spurious "stream closed" events" for cached reverse resolves.
9151 Patch from mwenge. Fixes bug 646.
9152 - Correctly notify one-hop connections when a circuit build has
9153 failed. Possible fix for bug 669. Found by lodger.
9156 Changes in version 0.2.0.23-rc - 2008-03-24
9157 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
9158 makes bootstrapping faster if the first directory mirror you contact
9159 is down. The bundles also include the new Vidalia 0.1.2 release.
9162 - When a tunneled directory request is made to a directory server
9163 that's down, notice after 30 seconds rather than 120 seconds. Also,
9164 fail any begindir streams that are pending on it, so they can
9165 retry elsewhere. This was causing multi-minute delays on bootstrap.
9168 Changes in version 0.2.0.22-rc - 2008-03-18
9169 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
9170 enables encrypted directory connections by default for non-relays, fixes
9171 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
9172 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
9175 - Enable encrypted directory connections by default for non-relays,
9176 so censor tools that block Tor directory connections based on their
9177 plaintext patterns will no longer work. This means Tor works in
9178 certain censored countries by default again.
9181 - Make sure servers always request certificates from clients during
9182 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
9183 - Do not enter a CPU-eating loop when a connection is closed in
9184 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
9185 diagnosed by lodger; bugfix on 0.2.0.20-rc.
9186 - Fix assertion failure that could occur when a blocked circuit
9187 became unblocked, and it had pending client DNS requests. Bugfix
9188 on 0.2.0.1-alpha. Fixes bug 632.
9190 o Minor bugfixes (on 0.1.2.x):
9191 - Generate "STATUS_SERVER" events rather than misspelled
9192 "STATUS_SEVER" events. Caught by mwenge.
9193 - When counting the number of bytes written on a TLS connection,
9194 look at the BIO actually used for writing to the network, not
9195 at the BIO used (sometimes) to buffer data for the network.
9196 Looking at different BIOs could result in write counts on the
9197 order of ULONG_MAX. Fixes bug 614.
9198 - On Windows, correctly detect errors when listing the contents of
9199 a directory. Fix from lodger.
9201 o Minor bugfixes (on 0.2.0.x):
9202 - Downgrade "sslv3 alert handshake failure" message to INFO.
9203 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
9204 left BandwidthRate and BandwidthBurst at the default, we would be
9205 silently limited by those defaults. Now raise them to match the
9206 RelayBandwidth* values.
9207 - Fix the SVK version detection logic to work correctly on a branch.
9208 - Make --enable-openbsd-malloc work correctly on Linux with alpha
9209 CPUs. Fixes bug 625.
9210 - Logging functions now check that the passed severity is sane.
9211 - Use proper log levels in the testsuite call of
9212 get_interface_address6().
9213 - When using a nonstandard malloc, do not use the platform values for
9214 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
9215 - Make the openbsd malloc code use 8k pages on alpha CPUs and
9217 - Detect mismatched page sizes when using --enable-openbsd-malloc.
9218 - Avoid double-marked-for-close warning when certain kinds of invalid
9219 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
9220 for bug 617. Bugfix on 0.2.0.1-alpha.
9221 - Make sure that the "NULL-means-reject *:*" convention is followed by
9222 all the policy manipulation functions, avoiding some possible crash
9223 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
9224 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
9225 actually works, and doesn't warn about every single reverse lookup.
9226 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
9229 - Only log guard node status when guard node status has changed.
9230 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
9231 make "INFO" 75% less verbose.
9234 Changes in version 0.2.0.21-rc - 2008-03-02
9235 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
9236 makes Tor work well with Vidalia again, fixes a rare assert bug,
9237 and fixes a pair of more minor bugs. The bundles also include Vidalia
9238 0.1.0 and Torbutton 1.1.16.
9241 - The control port should declare that it requires password auth
9242 when HashedControlSessionPassword is set too. Patch from Matt Edman;
9243 bugfix on 0.2.0.20-rc. Fixes bug 615.
9244 - Downgrade assert in connection_buckets_decrement() to a log message.
9245 This may help us solve bug 614, and in any case will make its
9246 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
9247 - We were sometimes miscounting the number of bytes read from the
9248 network, causing our rate limiting to not be followed exactly.
9249 Bugfix on 0.2.0.16-alpha. Reported by lodger.
9252 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
9253 OpenSSL versions should have been working fine. Diagnosis and patch
9254 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
9255 Bugfix on 0.2.0.20-rc.
9258 Changes in version 0.2.0.20-rc - 2008-02-24
9259 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
9260 makes more progress towards normalizing Tor's TLS handshake, makes
9261 hidden services work better again, helps relays bootstrap if they don't
9262 know their IP address, adds optional support for linking in openbsd's
9263 allocator or tcmalloc, allows really fast relays to scale past 15000
9264 sockets, and fixes a bunch of minor bugs reported by Veracode.
9267 - Enable the revised TLS handshake based on the one designed by
9268 Steven Murdoch in proposal 124, as revised in proposal 130. It
9269 includes version negotiation for OR connections as described in
9270 proposal 105. The new handshake is meant to be harder for censors
9271 to fingerprint, and it adds the ability to detect certain kinds of
9272 man-in-the-middle traffic analysis attacks. The version negotiation
9273 feature will allow us to improve Tor's link protocol more safely
9275 - Choose which bridge to use proportional to its advertised bandwidth,
9276 rather than uniformly at random. This should speed up Tor for
9277 bridge users. Also do this for people who set StrictEntryNodes.
9278 - When a TrackHostExits-chosen exit fails too many times in a row,
9279 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
9282 - Resolved problems with (re-)fetching hidden service descriptors.
9283 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
9285 - If we only ever used Tor for hidden service lookups or posts, we
9286 would stop building circuits and start refusing connections after
9287 24 hours, since we falsely believed that Tor was dormant. Reported
9288 by nwf; bugfix on 0.1.2.x.
9289 - Servers that don't know their own IP address should go to the
9290 authorities for their first directory fetch, even if their DirPort
9291 is off or if they don't know they're reachable yet. This will help
9292 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
9293 - When counting the number of open sockets, count not only the number
9294 of sockets we have received from the socket() call, but also
9295 the number we've gotten from accept() and socketpair(). This bug
9296 made us fail to count all sockets that we were using for incoming
9297 connections. Bugfix on 0.2.0.x.
9298 - Fix code used to find strings within buffers, when those strings
9299 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
9300 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
9301 - Add a new __HashedControlSessionPassword option for controllers
9302 to use for one-off session password hashes that shouldn't get
9303 saved to disk by SAVECONF --- Vidalia users were accumulating a
9304 pile of HashedControlPassword lines in their torrc files, one for
9305 each time they had restarted Tor and then clicked Save. Make Tor
9306 automatically convert "HashedControlPassword" to this new option but
9307 only when it's given on the command line. Partial fix for bug 586.
9309 o Minor features (performance):
9310 - Tune parameters for cell pool allocation to minimize amount of
9312 - Add OpenBSD malloc code from phk as an optional malloc
9313 replacement on Linux: some glibc libraries do very poorly
9314 with Tor's memory allocation patterns. Pass
9315 --enable-openbsd-malloc to get the replacement malloc code.
9316 - Add a --with-tcmalloc option to the configure script to link
9317 against tcmalloc (if present). Does not yet search for
9318 non-system include paths.
9319 - Stop imposing an arbitrary maximum on the number of file descriptors
9320 used for busy servers. Bug reported by Olaf Selke; patch from
9323 o Minor features (other):
9324 - When SafeLogging is disabled, log addresses along with all TLS
9326 - When building with --enable-gcc-warnings, check for whether Apple's
9327 warning "-Wshorten-64-to-32" is available.
9328 - Add a --passphrase-fd argument to the tor-gencert command for
9331 o Minor bugfixes (memory leaks and code problems):
9332 - We were leaking a file descriptor if Tor started with a zero-length
9333 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
9334 - Detect size overflow in zlib code. Reported by Justin Ferguson and
9336 - We were comparing the raw BridgePassword entry with a base64'ed
9337 version of it, when handling a "/tor/networkstatus-bridges"
9338 directory request. Now compare correctly. Noticed by Veracode.
9339 - Recover from bad tracked-since value in MTBF-history file.
9341 - Alter the code that tries to recover from unhandled write
9342 errors, to not try to flush onto a socket that's given us
9343 unhandled errors. Bugfix on 0.1.2.x.
9344 - Make Unix controlsockets work correctly on OpenBSD. Patch from
9345 tup. Bugfix on 0.2.0.3-alpha.
9347 o Minor bugfixes (other):
9348 - If we have an extra-info document for our server, always make
9349 it available on the control port, even if we haven't gotten
9350 a copy of it from an authority yet. Patch from mwenge.
9351 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
9352 - Directory mirrors no longer include a guess at the client's IP
9353 address if the connection appears to be coming from the same /24
9354 network; it was producing too many wrong guesses.
9355 - Make the new hidden service code respect the SafeLogging setting.
9356 Bugfix on 0.2.0.x. Patch from Karsten.
9357 - When starting as an authority, do not overwrite all certificates
9358 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
9359 - If we're trying to flush the last bytes on a connection (for
9360 example, when answering a directory request), reset the
9361 time-to-give-up timeout every time we manage to write something
9362 on the socket. Bugfix on 0.1.2.x.
9363 - Change the behavior of "getinfo status/good-server-descriptor"
9364 so it doesn't return failure when any authority disappears.
9365 - Even though the man page said that "TrackHostExits ." should
9366 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
9367 - Report TLS "zero return" case as a "clean close" and "IO error"
9368 as a "close". Stop calling closes "unexpected closes": existing
9369 Tors don't use SSL_close(), so having a connection close without
9370 the TLS shutdown handshake is hardly unexpected.
9371 - Send NAMESERVER_STATUS messages for a single failed nameserver
9374 o Code simplifications and refactoring:
9375 - Remove the tor_strpartition function: its logic was confused,
9376 and it was only used for one thing that could be implemented far
9380 Changes in version 0.2.0.19-alpha - 2008-02-09
9381 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
9382 handshake, makes path selection for relays more secure and IP address
9383 guessing more robust, and generally fixes a lot of bugs in preparation
9384 for calling the 0.2.0 branch stable.
9387 - Do not include recognizeable strings in the commonname part of
9388 Tor's x509 certificates.
9391 - If we're a relay, avoid picking ourselves as an introduction point,
9392 a rendezvous point, or as the final hop for internal circuits. Bug
9393 reported by taranis and lodger. Bugfix on 0.1.2.x.
9394 - Patch from "Andrew S. Lists" to catch when we contact a directory
9395 mirror at IP address X and he says we look like we're coming from
9396 IP address X. Bugfix on 0.1.2.x.
9398 o Minor features (security):
9399 - Be more paranoid about overwriting sensitive memory on free(),
9400 as a defensive programming tactic to ensure forward secrecy.
9402 o Minor features (directory authority):
9403 - Actually validate the options passed to AuthDirReject,
9404 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
9405 - Reject router descriptors with out-of-range bandwidthcapacity or
9406 bandwidthburst values.
9408 o Minor features (controller):
9409 - Reject controller commands over 1MB in length. This keeps rogue
9410 processes from running us out of memory.
9412 o Minor features (misc):
9413 - Give more descriptive well-formedness errors for out-of-range
9414 hidden service descriptor/protocol versions.
9415 - Make memory debugging information describe more about history
9416 of cell allocation, so we can help reduce our memory use.
9418 o Deprecated features (controller):
9419 - The status/version/num-versioning and status/version/num-concurring
9420 GETINFO options are no longer useful in the v3 directory protocol:
9421 treat them as deprecated, and warn when they're used.
9424 - When our consensus networkstatus has been expired for a while, stop
9425 being willing to build circuits using it. Fixes bug 401. Bugfix
9427 - Directory caches now fetch certificates from all authorities
9428 listed in a networkstatus consensus, even when they do not
9429 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
9430 - When connecting to a bridge without specifying its key, insert
9431 the connection into the identity-to-connection map as soon as
9432 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
9433 - Detect versions of OS X where malloc_good_size() is present in the
9434 library but never actually declared. Resolves bug 587. Bugfix
9436 - Stop incorrectly truncating zlib responses to directory authority
9437 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
9438 - Stop recommending that every server operator send mail to tor-ops.
9439 Resolves bug 597. Bugfix on 0.1.2.x.
9440 - Don't trigger an assert if we start a directory authority with a
9441 private IP address (like 127.0.0.1).
9442 - Avoid possible failures when generating a directory with routers
9443 with over-long versions strings, or too many flags set. Bugfix
9445 - If an attempt to launch a DNS resolve request over the control
9446 port fails because we have overrun the limit on the number of
9447 connections, tell the controller that the request has failed.
9448 - Avoid using too little bandwidth when our clock skips a few
9449 seconds. Bugfix on 0.1.2.x.
9450 - Fix shell error when warning about missing packages in configure
9451 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
9452 - Do not become confused when receiving a spurious VERSIONS-like
9453 cell from a confused v1 client. Bugfix on 0.2.0.x.
9454 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
9455 introduction points for a hidden service have failed. Patch from
9456 Karsten Loesing. Bugfix on 0.2.0.x.
9458 o Code simplifications and refactoring:
9459 - Remove some needless generality from cpuworker code, for improved
9461 - Stop overloading the circuit_t.onionskin field for both "onionskin
9462 from a CREATE cell that we are waiting for a cpuworker to be
9463 assigned" and "onionskin from an EXTEND cell that we are going to
9464 send to an OR as soon as we are connected". Might help with bug 600.
9465 - Add an in-place version of aes_crypt() so that we can avoid doing a
9466 needless memcpy() call on each cell payload.
9469 Changes in version 0.2.0.18-alpha - 2008-01-25
9470 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
9471 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
9472 that can warn or reject connections to ports generally associated with
9473 vulnerable-plaintext protocols.
9475 o New directory authorities:
9476 - Set up dannenberg (run by CCC) as the sixth v3 directory
9480 - Fix a major memory leak when attempting to use the v2 TLS
9481 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
9482 - We accidentally enabled the under-development v2 TLS handshake
9483 code, which was causing log entries like "TLS error while
9484 renegotiating handshake". Disable it again. Resolves bug 590.
9485 - We were computing the wrong Content-Length: header for directory
9486 responses that need to be compressed on the fly, causing clients
9487 asking for those items to always fail. Bugfix on 0.2.0.x; partially
9491 - Avoid going directly to the directory authorities even if you're a
9492 relay, if you haven't found yourself reachable yet or if you've
9493 decided not to advertise your dirport yet. Addresses bug 556.
9494 - If we've gone 12 hours since our last bandwidth check, and we
9495 estimate we have less than 50KB bandwidth capacity but we could
9496 handle more, do another bandwidth test.
9497 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
9498 Tor can warn and/or refuse connections to ports commonly used with
9499 vulnerable-plaintext protocols. Currently we warn on ports 23,
9500 109, 110, and 143, but we don't reject any.
9503 - When we setconf ClientOnly to 1, close any current OR and Dir
9504 listeners. Reported by mwenge.
9505 - When we get a consensus that's been signed by more people than
9506 we expect, don't log about it; it's not a big deal. Reported
9510 - Don't answer "/tor/networkstatus-bridges" directory requests if
9511 the request isn't encrypted.
9512 - Make "ClientOnly 1" config option disable directory ports too.
9513 - Patches from Karsten Loesing to make v2 hidden services more
9514 robust: work even when there aren't enough HSDir relays available;
9515 retry when a v2 rend desc fetch fails; but don't retry if we
9516 already have a usable v0 rend desc.
9519 Changes in version 0.2.0.17-alpha - 2008-01-17
9520 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
9523 - Make the tor-gencert man page get included correctly in the tarball.
9526 Changes in version 0.2.0.16-alpha - 2008-01-17
9527 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
9528 Loesing, and generally cleans up a lot of features and minor bugs.
9530 o New directory authorities:
9531 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
9534 o Major performance improvements:
9535 - Switch our old ring buffer implementation for one more like that
9536 used by free Unix kernels. The wasted space in a buffer with 1mb
9537 of data will now be more like 8k than 1mb. The new implementation
9538 also avoids realloc();realloc(); patterns that can contribute to
9539 memory fragmentation.
9542 - Configuration files now accept C-style strings as values. This
9543 helps encode characters not allowed in the current configuration
9544 file format, such as newline or #. Addresses bug 557.
9545 - Although we fixed bug 539 (where servers would send HTTP status 503
9546 responses _and_ send a body too), there are still servers out
9547 there that haven't upgraded. Therefore, make clients parse such
9548 bodies when they receive them.
9549 - When we're not serving v2 directory information, there is no reason
9550 to actually keep any around. Remove the obsolete files and directory
9551 on startup if they are very old and we aren't going to serve them.
9553 o Minor performance improvements:
9554 - Reference-count and share copies of address policy entries; only 5%
9555 of them were actually distinct.
9556 - Never walk through the list of logs if we know that no log is
9557 interested in a given message.
9560 - When an authority has not signed a consensus, do not try to
9561 download a nonexistent "certificate with key 00000000". Bugfix
9562 on 0.2.0.x. Fixes bug 569.
9563 - Fix a rare assert error when we're closing one of our threads:
9564 use a mutex to protect the list of logs, so we never write to the
9565 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
9566 bug 575, which is kind of the revenge of bug 222.
9567 - Patch from Karsten Loesing to complain less at both the client
9568 and the relay when a relay used to have the HSDir flag but doesn't
9569 anymore, and we try to upload a hidden service descriptor.
9570 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
9572 - Do not try to download missing certificates until we have tried
9573 to check our fallback consensus. Fixes bug 583.
9574 - Make bridges round reported GeoIP stats info up to the nearest
9575 estimate, not down. Now we can distinguish between "0 people from
9576 this country" and "1 person from this country".
9577 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
9578 - Avoid possible segfault if key generation fails in
9579 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
9580 - Avoid segfault in the case where a badly behaved v2 versioning
9581 directory sends a signed networkstatus with missing client-versions.
9583 - Avoid segfaults on certain complex invocations of
9584 router_get_by_hexdigest(). Bugfix on 0.1.2.
9585 - Correct bad index on array access in parse_http_time(). Bugfix
9587 - Fix possible bug in vote generation when server versions are present
9588 but client versions are not.
9589 - Fix rare bug on REDIRECTSTREAM control command when called with no
9590 port set: it could erroneously report an error when none had
9592 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
9593 compressing large objects and find ourselves with more than 4k
9594 left over. Bugfix on 0.2.0.
9595 - Fix a small memory leak when setting up a hidden service.
9596 - Fix a few memory leaks that could in theory happen under bizarre
9598 - Fix an assert if we post a general-purpose descriptor via the
9599 control port but that descriptor isn't mentioned in our current
9600 network consensus. Bug reported by Jon McLachlan; bugfix on
9603 o Minor features (controller):
9604 - Get NS events working again. Patch from tup.
9605 - The GETCONF command now escapes and quotes configuration values
9606 that don't otherwise fit into the torrc file.
9607 - The SETCONF command now handles quoted values correctly.
9609 o Minor features (directory authorities):
9610 - New configuration options to override default maximum number of
9611 servers allowed on a single IP address. This is important for
9612 running a test network on a single host.
9613 - Actually implement the -s option to tor-gencert.
9614 - Add a manual page for tor-gencert.
9616 o Minor features (bridges):
9617 - Bridge authorities no longer serve bridge descriptors over
9618 unencrypted connections.
9620 o Minor features (other):
9621 - Add hidden services and DNSPorts to the list of things that make
9622 Tor accept that it has running ports. Change starting Tor with no
9623 ports from a fatal error to a warning; we might change it back if
9624 this turns out to confuse anybody. Fixes bug 579.
9627 Changes in version 0.1.2.19 - 2008-01-17
9628 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
9629 exit policy a little bit more conservative so it's safer to run an
9630 exit relay on a home system, and fixes a variety of smaller issues.
9633 - Exit policies now reject connections that are addressed to a
9634 relay's public (external) IP address too, unless
9635 ExitPolicyRejectPrivate is turned off. We do this because too
9636 many relays are running nearby to services that trust them based
9640 - When the clock jumps forward a lot, do not allow the bandwidth
9641 buckets to become negative. Fixes bug 544.
9642 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9643 on every successful resolve. Reported by Mike Perry.
9644 - Purge old entries from the "rephist" database and the hidden
9645 service descriptor database even when DirPort is zero.
9646 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9647 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9648 crashing or mis-answering these requests.
9649 - When we decide to send a 503 response to a request for servers, do
9650 not then also send the server descriptors: this defeats the whole
9651 purpose. Fixes bug 539.
9654 - Changing the ExitPolicyRejectPrivate setting should cause us to
9655 rebuild our server descriptor.
9656 - Fix handling of hex nicknames when answering controller requests for
9657 networkstatus by name, or when deciding whether to warn about
9658 unknown routers in a config option. (Patch from mwenge.)
9659 - Fix a couple of hard-to-trigger autoconf problems that could result
9660 in really weird results on platforms whose sys/types.h files define
9661 nonstandard integer types.
9662 - Don't try to create the datadir when running --verify-config or
9663 --hash-password. Resolves bug 540.
9664 - If we were having problems getting a particular descriptor from the
9665 directory caches, and then we learned about a new descriptor for
9666 that router, we weren't resetting our failure count. Reported
9668 - Although we fixed bug 539 (where servers would send HTTP status 503
9669 responses _and_ send a body too), there are still servers out there
9670 that haven't upgraded. Therefore, make clients parse such bodies
9671 when they receive them.
9672 - Run correctly on systems where rlim_t is larger than unsigned long.
9673 This includes some 64-bit systems.
9674 - Run correctly on platforms (like some versions of OS X 10.5) where
9675 the real limit for number of open files is OPEN_FILES, not rlim_max
9676 from getrlimit(RLIMIT_NOFILES).
9677 - Avoid a spurious free on base64 failure.
9678 - Avoid segfaults on certain complex invocations of
9679 router_get_by_hexdigest().
9680 - Fix rare bug on REDIRECTSTREAM control command when called with no
9681 port set: it could erroneously report an error when none had
9685 Changes in version 0.2.0.15-alpha - 2007-12-25
9686 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
9687 features added in 0.2.0.13-alpha.
9690 - Fix several remotely triggerable asserts based on DirPort requests
9691 for a v2 or v3 networkstatus object before we were prepared. This
9692 was particularly bad for 0.2.0.13 and later bridge relays, who
9693 would never have a v2 networkstatus and would thus always crash
9694 when used. Bugfixes on 0.2.0.x.
9695 - Estimate the v3 networkstatus size more accurately, rather than
9696 estimating it at zero bytes and giving it artificially high priority
9697 compared to other directory requests. Bugfix on 0.2.0.x.
9700 - Fix configure.in logic for cross-compilation.
9701 - When we load a bridge descriptor from the cache, and it was
9702 previously unreachable, mark it as retriable so we won't just
9703 ignore it. Also, try fetching a new copy immediately. Bugfixes
9705 - The bridge GeoIP stats were counting other relays, for example
9706 self-reachability and authority-reachability tests.
9709 - Support compilation to target iPhone; patch from cjacker huang.
9710 To build for iPhone, pass the --enable-iphone option to configure.
9713 Changes in version 0.2.0.14-alpha - 2007-12-23
9715 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
9716 without a datadirectory from a previous Tor install. Reported
9718 - Fix a crash when we fetch a descriptor that turns out to be
9719 unexpected (it used to be in our networkstatus when we started
9720 fetching it, but it isn't in our current networkstatus), and we
9721 aren't using bridges. Bugfix on 0.2.0.x.
9722 - Fix a crash when accessing hidden services: it would work the first
9723 time you use a given introduction point for your service, but
9724 on subsequent requests we'd be using garbage memory. Fixed by
9725 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
9726 - Fix a crash when we load a bridge descriptor from disk but we don't
9727 currently have a Bridge line for it in our torrc. Bugfix on
9731 - If bridge authorities set BridgePassword, they will serve a
9732 snapshot of known bridge routerstatuses from their DirPort to
9733 anybody who knows that password. Unset by default.
9736 - Make the unit tests build again.
9737 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
9738 - Make PublishServerDescriptor default to 1, so the default doesn't
9739 have to change as we invent new directory protocol versions.
9740 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
9741 be included unless sys/time.h is already included. Fixes
9742 bug 553. Bugfix on 0.2.0.x.
9743 - If we receive a general-purpose descriptor and then receive an
9744 identical bridge-purpose descriptor soon after, don't discard
9745 the next one as a duplicate.
9748 - If BridgeRelay is set to 1, then the default for
9749 PublishServerDescriptor is now "bridge" rather than "v2,v3".
9750 - If the user sets RelayBandwidthRate but doesn't set
9751 RelayBandwidthBurst, then make them equal rather than erroring out.
9754 Changes in version 0.2.0.13-alpha - 2007-12-21
9755 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
9756 Goodell, fixes many more bugs, and adds a lot of infrastructure for
9759 o New directory authorities:
9760 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
9764 - Only update guard status (usable / not usable) once we have
9765 enough directory information. This was causing us to always pick
9766 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
9767 causing us to discard all our guards on startup if we hadn't been
9768 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
9769 - Purge old entries from the "rephist" database and the hidden
9770 service descriptor databases even when DirPort is zero. Bugfix
9772 - We were ignoring our RelayBandwidthRate for the first 30 seconds
9773 after opening a circuit -- even a relayed circuit. Bugfix on
9775 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9776 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9777 crashing or mis-answering these types of requests.
9778 - Relays were publishing their server descriptor to v1 and v2
9779 directory authorities, but they didn't try publishing to v3-only
9780 authorities. Fix this; and also stop publishing to v1 authorities.
9782 - When we were reading router descriptors from cache, we were ignoring
9783 the annotations -- so for example we were reading in bridge-purpose
9784 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
9785 - When we decided to send a 503 response to a request for servers, we
9786 were then also sending the server descriptors: this defeats the
9787 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
9790 - Bridge relays now behave like clients with respect to time
9791 intervals for downloading new consensus documents -- otherwise they
9792 stand out. Bridge users now wait until the end of the interval,
9793 so their bridge relay will be sure to have a new consensus document.
9794 - Three new config options (AlternateDirAuthority,
9795 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
9796 user selectively replace the default directory authorities by type,
9797 rather than the all-or-nothing replacement that DirServer offers.
9798 - Tor can now be configured to read a GeoIP file from disk in one
9799 of two formats. This can be used by controllers to map IP addresses
9800 to countries. Eventually, it may support exit-by-country.
9801 - When possible, bridge relays remember which countries users
9802 are coming from, and report aggregate information in their
9803 extra-info documents, so that the bridge authorities can learn
9804 where Tor is blocked.
9805 - Bridge directory authorities now do reachability testing on the
9806 bridges they know. They provide router status summaries to the
9807 controller via "getinfo ns/purpose/bridge", and also dump summaries
9808 to a file periodically.
9809 - Stop fetching directory info so aggressively if your DirPort is
9810 on but your ORPort is off; stop fetching v2 dir info entirely.
9811 You can override these choices with the new FetchDirInfoEarly
9815 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
9816 consensus documents when there are too many relays at a single
9817 IP address. Now clear it in v2 network status documents too, and
9818 also clear it in routerinfo_t when the relay is no longer listed
9819 in the relevant networkstatus document.
9820 - Don't crash if we get an unexpected value for the
9821 PublishServerDescriptor config option. Reported by Matt Edman;
9822 bugfix on 0.2.0.9-alpha.
9823 - Our new v2 hidden service descriptor format allows descriptors
9824 that have no introduction points. But Tor crashed when we tried
9825 to build a descriptor with no intro points (and it would have
9826 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
9828 - Fix building with dmalloc 5.5.2 with glibc.
9829 - Reject uploaded descriptors and extrainfo documents if they're
9830 huge. Otherwise we'll cache them all over the network and it'll
9831 clog everything up. Reported by Aljosha Judmayer.
9832 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
9833 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
9834 - When the DANGEROUS_VERSION controller status event told us we're
9835 running an obsolete version, it used the string "OLD" to describe
9836 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
9837 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
9838 - If we can't expand our list of entry guards (e.g. because we're
9839 using bridges or we have StrictEntryNodes set), don't mark relays
9840 down when they fail a directory request. Otherwise we're too quick
9841 to mark all our entry points down. Bugfix on 0.1.2.x.
9842 - Fix handling of hex nicknames when answering controller requests for
9843 networkstatus by name, or when deciding whether to warn about unknown
9844 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
9845 - Fix a couple of hard-to-trigger autoconf problems that could result
9846 in really weird results on platforms whose sys/types.h files define
9847 nonstandard integer types. Bugfix on 0.1.2.x.
9848 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
9849 - Don't crash on name lookup when we have no current consensus. Fixes
9850 bug 538; bugfix on 0.2.0.x.
9851 - Only Tors that want to mirror the v2 directory info should
9852 create the "cached-status" directory in their datadir. (All Tors
9853 used to create it.) Bugfix on 0.2.0.9-alpha.
9854 - Directory authorities should only automatically download Extra Info
9855 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
9858 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
9859 consumers. (We already do this on HUP.)
9860 - Authorities and caches fetch the v2 networkstatus documents
9861 less often, now that v3 is encouraged.
9862 - Add a new config option BridgeRelay that specifies you want to
9863 be a bridge relay. Right now the only difference is that it makes
9864 you answer begin_dir requests, and it makes you cache dir info,
9865 even if your DirPort isn't on.
9866 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
9867 ask about source, timestamp of arrival, purpose, etc. We need
9868 something like this to help Vidalia not do GeoIP lookups on bridge
9870 - Allow multiple HashedControlPassword config lines, to support
9871 multiple controller passwords.
9872 - Authorities now decide whether they're authoritative for a given
9873 router based on the router's purpose.
9874 - New config options AuthDirBadDir and AuthDirListBadDirs for
9875 authorities to mark certain relays as "bad directories" in the
9876 networkstatus documents. Also supports the "!baddir" directive in
9877 the approved-routers file.
9880 Changes in version 0.2.0.12-alpha - 2007-11-16
9881 This twelfth development snapshot fixes some more build problems as
9882 well as a few minor bugs.
9885 - Make it build on OpenBSD again. Patch from tup.
9886 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
9887 package-building for Red Hat, OS X, etc.
9889 o Minor bugfixes (on 0.1.2.x):
9890 - Changing the ExitPolicyRejectPrivate setting should cause us to
9891 rebuild our server descriptor.
9893 o Minor bugfixes (on 0.2.0.x):
9894 - When we're lacking a consensus, don't try to perform rendezvous
9895 operations. Reported by Karsten Loesing.
9896 - Fix a small memory leak whenever we decide against using a
9897 newly picked entry guard. Reported by Mike Perry.
9898 - When authorities detected more than two relays running on the same
9899 IP address, they were clearing all the status flags but forgetting
9900 to clear the "hsdir" flag. So clients were being told that a
9901 given relay was the right choice for a v2 hsdir lookup, yet they
9902 never had its descriptor because it was marked as 'not running'
9904 - If we're trying to fetch a bridge descriptor and there's no way
9905 the bridge authority could help us (for example, we don't know
9906 a digest, or there is no bridge authority), don't be so eager to
9907 fall back to asking the bridge authority.
9908 - If we're using bridges or have strictentrynodes set, and our
9909 chosen exit is in the same family as all our bridges/entry guards,
9910 then be flexible about families.
9913 - When we negotiate a v2 link-layer connection (not yet implemented),
9914 accept RELAY_EARLY cells and turn them into RELAY cells if we've
9915 negotiated a v1 connection for their next step. Initial code for
9919 Changes in version 0.2.0.11-alpha - 2007-11-12
9920 This eleventh development snapshot fixes some build problems with
9921 the previous snapshot. It also includes a more secure-by-default exit
9922 policy for relays, fixes an enormous memory leak for exit relays, and
9923 fixes another bug where servers were falling out of the directory list.
9926 - Exit policies now reject connections that are addressed to a
9927 relay's public (external) IP address too, unless
9928 ExitPolicyRejectPrivate is turned off. We do this because too
9929 many relays are running nearby to services that trust them based
9930 on network address. Bugfix on 0.1.2.x.
9933 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9934 on every successful resolve. Reported by Mike Perry; bugfix
9936 - On authorities, never downgrade to old router descriptors simply
9937 because they're listed in the consensus. This created a catch-22
9938 where we wouldn't list a new descriptor because there was an
9939 old one in the consensus, and we couldn't get the new one in the
9940 consensus because we wouldn't list it. Possible fix for bug 548.
9941 Also, this might cause bug 543 to appear on authorities; if so,
9942 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
9944 o Packaging fixes on 0.2.0.10-alpha:
9945 - We were including instructions about what to do with the
9946 src/config/fallback-consensus file, but we weren't actually
9947 including it in the tarball. Disable all of that for now.
9950 - Allow people to say PreferTunnelledDirConns rather than
9951 PreferTunneledDirConns, for those alternate-spellers out there.
9954 - Don't reevaluate all the information from our consensus document
9955 just because we've downloaded a v2 networkstatus that we intend
9956 to cache. Fixes bug 545; bugfix on 0.2.0.x.
9959 Changes in version 0.2.0.10-alpha - 2007-11-10
9960 This tenth development snapshot adds a third v3 directory authority
9961 run by Mike Perry, adds most of Karsten Loesing's new hidden service
9962 descriptor format, fixes a bad crash bug and new bridge bugs introduced
9963 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
9964 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
9965 addresses many more minor issues.
9967 o New directory authorities:
9968 - Set up ides (run by Mike Perry) as the third v3 directory authority.
9971 - Allow tunnelled directory connections to ask for an encrypted
9972 "begin_dir" connection or an anonymized "uses a full Tor circuit"
9973 connection independently. Now we can make anonymized begin_dir
9974 connections for (e.g.) more secure hidden service posting and
9976 - More progress on proposal 114: code from Karsten Loesing to
9977 implement new hidden service descriptor format.
9978 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
9979 accommodate the growing number of servers that use the default
9980 and are reaching it.
9981 - Directory authorities use a new formula for selecting which nodes
9982 to advertise as Guards: they must be in the top 7/8 in terms of
9983 how long we have known about them, and above the median of those
9984 nodes in terms of weighted fractional uptime.
9985 - Make "not enough dir info yet" warnings describe *why* Tor feels
9986 it doesn't have enough directory info yet.
9989 - Stop servers from crashing if they set a Family option (or
9990 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
9992 - Make bridge users work again -- the move to v3 directories in
9993 0.2.0.9-alpha had introduced a number of bugs that made bridges
9994 no longer work for clients.
9995 - When the clock jumps forward a lot, do not allow the bandwidth
9996 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
9998 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
9999 - When the consensus lists a router descriptor that we previously were
10000 mirroring, but that we considered non-canonical, reload the
10001 descriptor as canonical. This fixes bug 543 where Tor servers
10002 would start complaining after a few days that they don't have
10003 enough directory information to build a circuit.
10004 - Consider replacing the current consensus when certificates arrive
10005 that make the pending consensus valid. Previously, we were only
10006 considering replacement when the new certs _didn't_ help.
10007 - Fix an assert error on startup if we didn't already have the
10008 consensus and certs cached in our datadirectory: we were caching
10009 the consensus in consensus_waiting_for_certs but then free'ing it
10011 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
10012 Request) if we need more v3 certs but we've already got pending
10013 requests for all of them.
10014 - Correctly back off from failing certificate downloads. Fixes
10016 - Authorities don't vote on the Running flag if they have been running
10017 for less than 30 minutes themselves. Fixes bug 547, where a newly
10018 started authority would vote that everyone was down.
10020 o New requirements:
10021 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
10022 it, it had no AES, and it hasn't seen any security patches since
10026 - Clients now hold circuitless TLS connections open for 1.5 times
10027 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
10028 rebuild a new circuit over them within that timeframe. Previously,
10029 they held them open only for KeepalivePeriod (5 minutes).
10030 - Use "If-Modified-Since" to avoid retrieving consensus
10031 networkstatuses that we already have.
10032 - When we have no consensus, check FallbackNetworkstatusFile (defaults
10033 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
10034 we start knowing some directory caches.
10035 - When we receive a consensus from the future, warn about skew.
10036 - Improve skew reporting: try to give the user a better log message
10037 about how skewed they are, and how much this matters.
10038 - When we have a certificate for an authority, believe that
10039 certificate's claims about the authority's IP address.
10040 - New --quiet command-line option to suppress the default console log.
10041 Good in combination with --hash-password.
10042 - Authorities send back an X-Descriptor-Not-New header in response to
10043 an accepted-but-discarded descriptor upload. Partially implements
10045 - Make the log message for "tls error. breaking." more useful.
10046 - Better log messages about certificate downloads, to attempt to
10047 track down the second incarnation of bug 546.
10049 o Minor features (bridges):
10050 - If bridge users set UpdateBridgesFromAuthority, but the digest
10051 they ask for is a 404 from the bridge authority, they now fall
10052 back to trying the bridge directly.
10053 - Bridges now use begin_dir to publish their server descriptor to
10054 the bridge authority, even when they haven't set TunnelDirConns.
10056 o Minor features (controller):
10057 - When reporting clock skew, and we know that the clock is _at least
10058 as skewed_ as some value, but we don't know the actual value,
10059 report the value as a "minimum skew."
10062 - Update linux-tor-prio.sh script to allow QoS based on the uid of
10063 the Tor process. Patch from Marco Bonetti with tweaks from Mike
10067 - Refuse to start if both ORPort and UseBridges are set. Bugfix
10068 on 0.2.0.x, suggested by Matt Edman.
10069 - Don't stop fetching descriptors when FetchUselessDescriptors is
10070 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
10071 reported by tup and ioerror.
10072 - Better log message on vote from unknown authority.
10073 - Don't log "Launching 0 request for 0 router" message.
10075 o Minor bugfixes (memory leaks):
10076 - Stop leaking memory every time we parse a v3 certificate. Bugfix
10078 - Stop leaking memory every time we load a v3 certificate. Bugfix
10079 on 0.2.0.1-alpha. Fixes bug 536.
10080 - Stop leaking a cached networkstatus on exit. Bugfix on
10082 - Stop leaking voter information every time we free a consensus.
10083 Bugfix on 0.2.0.3-alpha.
10084 - Stop leaking signed data every time we check a voter signature.
10085 Bugfix on 0.2.0.3-alpha.
10086 - Stop leaking a signature every time we fail to parse a consensus or
10087 a vote. Bugfix on 0.2.0.3-alpha.
10088 - Stop leaking v2_download_status_map on shutdown. Bugfix on
10090 - Stop leaking conn->nickname every time we make a connection to a
10091 Tor relay without knowing its expected identity digest (e.g. when
10092 using bridges). Bugfix on 0.2.0.3-alpha.
10094 - Minor bugfixes (portability):
10095 - Run correctly on platforms where rlim_t is larger than unsigned
10096 long, and/or where the real limit for number of open files is
10097 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
10098 particular, these may be needed for OS X 10.5.
10101 Changes in version 0.1.2.18 - 2007-10-28
10102 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
10103 hidden service introduction that were causing huge delays, and a big
10104 bug that was causing some servers to disappear from the network status
10105 lists for a few hours each day.
10107 o Major bugfixes (crashes):
10108 - If a connection is shut down abruptly because of something that
10109 happened inside connection_flushed_some(), do not call
10110 connection_finished_flushing(). Should fix bug 451:
10111 "connection_stop_writing: Assertion conn->write_event failed"
10112 Bugfix on 0.1.2.7-alpha.
10113 - Fix possible segfaults in functions called from
10114 rend_process_relay_cell().
10116 o Major bugfixes (hidden services):
10117 - Hidden services were choosing introduction points uniquely by
10118 hexdigest, but when constructing the hidden service descriptor
10119 they merely wrote the (potentially ambiguous) nickname.
10120 - Clients now use the v2 intro format for hidden service
10121 connections: they specify their chosen rendezvous point by identity
10122 digest rather than by (potentially ambiguous) nickname. These
10123 changes could speed up hidden service connections dramatically.
10125 o Major bugfixes (other):
10126 - Stop publishing a new server descriptor just because we get a
10127 HUP signal. This led (in a roundabout way) to some servers getting
10128 dropped from the networkstatus lists for a few hours each day.
10129 - When looking for a circuit to cannibalize, consider family as well
10130 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10131 circuit cannibalization).
10132 - When a router wasn't listed in a new networkstatus, we were leaving
10133 the flags for that router alone -- meaning it remained Named,
10134 Running, etc -- even though absence from the networkstatus means
10135 that it shouldn't be considered to exist at all anymore. Now we
10136 clear all the flags for routers that fall out of the networkstatus
10137 consensus. Fixes bug 529.
10140 - Don't try to access (or alter) the state file when running
10141 --list-fingerprint or --verify-config or --hash-password. Resolves
10143 - When generating information telling us how to extend to a given
10144 router, do not try to include the nickname if it is
10145 absent. Resolves bug 467.
10146 - Fix a user-triggerable segfault in expand_filename(). (There isn't
10147 a way to trigger this remotely.)
10148 - When sending a status event to the controller telling it that an
10149 OR address is reachable, set the port correctly. (Previously we
10150 were reporting the dir port.)
10151 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10152 command. Bugfix on 0.1.2.17.
10153 - When loading bandwidth history, do not believe any information in
10154 the future. Fixes bug 434.
10155 - When loading entry guard information, do not believe any information
10157 - When we have our clock set far in the future and generate an
10158 onion key, then re-set our clock to be correct, we should not stop
10159 the onion key from getting rotated.
10160 - On some platforms, accept() can return a broken address. Detect
10161 this more quietly, and deal accordingly. Fixes bug 483.
10162 - It's not actually an error to find a non-pending entry in the DNS
10163 cache when canceling a pending resolve. Don't log unless stuff
10164 is fishy. Resolves bug 463.
10165 - Don't reset trusted dir server list when we set a configuration
10166 option. Patch from Robert Hogan.
10167 - Don't try to create the datadir when running --verify-config or
10168 --hash-password. Resolves bug 540.
10171 Changes in version 0.2.0.9-alpha - 2007-10-24
10172 This ninth development snapshot switches clients to the new v3 directory
10173 system; allows servers to be listed in the network status even when they
10174 have the same nickname as a registered server; and fixes many other
10175 bugs including a big one that was causing some servers to disappear
10176 from the network status lists for a few hours each day.
10178 o Major features (directory system):
10179 - Clients now download v3 consensus networkstatus documents instead
10180 of v2 networkstatus documents. Clients and caches now base their
10181 opinions about routers on these consensus documents. Clients only
10182 download router descriptors listed in the consensus.
10183 - Authorities now list servers who have the same nickname as
10184 a different named server, but list them with a new flag,
10185 "Unnamed". Now we can list servers that happen to pick the same
10186 nickname as a server that registered two years ago and then
10187 disappeared. Partially implements proposal 122.
10188 - If the consensus lists a router as "Unnamed", the name is assigned
10189 to a different router: do not identify the router by that name.
10190 Partially implements proposal 122.
10191 - Authorities can now come to a consensus on which method to use to
10192 compute the consensus. This gives us forward compatibility.
10195 - Stop publishing a new server descriptor just because we HUP or
10196 when we find our DirPort to be reachable but won't actually publish
10197 it. New descriptors without any real changes are dropped by the
10198 authorities, and can screw up our "publish every 18 hours" schedule.
10200 - When a router wasn't listed in a new networkstatus, we were leaving
10201 the flags for that router alone -- meaning it remained Named,
10202 Running, etc -- even though absence from the networkstatus means
10203 that it shouldn't be considered to exist at all anymore. Now we
10204 clear all the flags for routers that fall out of the networkstatus
10205 consensus. Fixes bug 529; bugfix on 0.1.2.x.
10206 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
10207 extrainfo documents and then discard them immediately for not
10208 matching the latest router. Bugfix on 0.2.0.1-alpha.
10210 o Minor features (v3 directory protocol):
10211 - Allow tor-gencert to generate a new certificate without replacing
10213 - Allow certificates to include an address.
10214 - When we change our directory-cache settings, reschedule all voting
10215 and download operations.
10216 - Reattempt certificate downloads immediately on failure, as long as
10217 we haven't failed a threshold number of times yet.
10218 - Delay retrying consensus downloads while we're downloading
10219 certificates to verify the one we just got. Also, count getting a
10220 consensus that we already have (or one that isn't valid) as a failure,
10221 and count failing to get the certificates after 20 minutes as a
10223 - Build circuits and download descriptors even if our consensus is a
10224 little expired. (This feature will go away once authorities are
10227 o Minor features (router descriptor cache):
10228 - If we find a cached-routers file that's been sitting around for more
10229 than 28 days unmodified, then most likely it's a leftover from
10230 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
10232 - When we (as a cache) download a descriptor because it was listed
10233 in a consensus, remember when the consensus was supposed to expire,
10234 and don't expire the descriptor until then.
10236 o Minor features (performance):
10237 - Call routerlist_remove_old_routers() much less often. This should
10238 speed startup, especially on directory caches.
10239 - Don't try to launch new descriptor downloads quite so often when we
10240 already have enough directory information to build circuits.
10241 - Base64 decoding was actually showing up on our profile when parsing
10242 the initial descriptor file; switch to an in-process all-at-once
10243 implementation that's about 3.5x times faster than calling out to
10246 o Minor features (compilation):
10247 - Detect non-ASCII platforms (if any still exist) and refuse to
10248 build there: some of our code assumes that 'A' is 65 and so on.
10250 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
10251 - Make the "next period" votes into "current period" votes immediately
10252 after publishing the consensus; avoid a heisenbug that made them
10253 stick around indefinitely.
10254 - When we discard a vote as a duplicate, do not report this as
10256 - Treat missing v3 keys or certificates as an error when running as a
10257 v3 directory authority.
10258 - When we're configured to be a v3 authority, but we're only listed
10259 as a non-v3 authority in our DirServer line for ourself, correct
10261 - If an authority doesn't have a qualified hostname, just put
10262 its address in the vote. This fixes the problem where we referred to
10263 "moria on moria:9031."
10264 - Distinguish between detached signatures for the wrong period, and
10265 detached signatures for a divergent vote.
10266 - Fix a small memory leak when computing a consensus.
10267 - When there's no concensus, we were forming a vote every 30
10268 minutes, but writing the "valid-after" line in our vote based
10269 on our configured V3AuthVotingInterval: so unless the intervals
10270 matched up, we immediately rejected our own vote because it didn't
10271 start at the voting interval that caused us to construct a vote.
10273 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
10274 - Delete unverified-consensus when the real consensus is set.
10275 - Consider retrying a consensus networkstatus fetch immediately
10276 after one fails: don't wait 60 seconds to notice.
10277 - When fetching a consensus as a cache, wait until a newer consensus
10278 should exist before trying to replace the current one.
10279 - Use a more forgiving schedule for retrying failed consensus
10280 downloads than for other types.
10282 o Minor bugfixes (other directory issues):
10283 - Correct the implementation of "download votes by digest." Bugfix on
10285 - Authorities no longer send back "400 you're unreachable please fix
10286 it" errors to Tor servers that aren't online all the time. We're
10287 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
10289 o Minor bugfixes (controller):
10290 - Don't reset trusted dir server list when we set a configuration
10291 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
10292 - Respond to INT and TERM SIGNAL commands before we execute the
10293 signal, in case the signal shuts us down. We had a patch in
10294 0.1.2.1-alpha that tried to do this by queueing the response on
10295 the connection's buffer before shutting down, but that really
10296 isn't the same thing at all. Bug located by Matt Edman.
10298 o Minor bugfixes (misc):
10299 - Correctly check for bad options to the "PublishServerDescriptor"
10300 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
10301 - Stop leaking memory on failing case of base32_decode, and make
10302 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
10303 - Don't try to download extrainfo documents when we're trying to
10304 fetch enough directory info to build a circuit: having enough
10305 info should get priority. Bugfix on 0.2.0.x.
10306 - Don't complain that "your server has not managed to confirm that its
10307 ports are reachable" if we haven't been able to build any circuits
10308 yet. Bug found by spending four hours without a v3 consensus. Bugfix
10310 - Detect the reason for failing to mmap a descriptor file we just
10311 wrote, and give a more useful log message. Fixes bug 533. Bugfix
10314 o Code simplifications and refactoring:
10315 - Remove support for the old bw_accounting file: we've been storing
10316 bandwidth accounting information in the state file since
10317 0.1.2.5-alpha. This may result in bandwidth accounting errors
10318 if you try to upgrade from 0.1.1.x or earlier, or if you try to
10319 downgrade to 0.1.1.x or earlier.
10320 - New convenience code to locate a file within the DataDirectory.
10321 - Move non-authority functionality out of dirvote.c.
10322 - Refactor the arguments for router_pick_{directory_|trusteddir}server
10323 so that they all take the same named flags.
10326 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
10327 Unix users an easy way to script their Tor process (e.g. by
10328 adjusting bandwidth based on the time of the day).
10331 Changes in version 0.2.0.8-alpha - 2007-10-12
10332 This eighth development snapshot fixes a crash bug that's been bothering
10333 us since February 2007, lets bridge authorities store a list of bridge
10334 descriptors they've seen, gets v3 directory voting closer to working,
10335 starts caching v3 directory consensus documents on directory mirrors,
10336 and fixes a variety of smaller issues including some minor memory leaks.
10338 o Major features (router descriptor cache):
10339 - Store routers in a file called cached-descriptors instead of in
10340 cached-routers. Initialize cached-descriptors from cached-routers
10341 if the old format is around. The new format allows us to store
10342 annotations along with descriptors.
10343 - Use annotations to record the time we received each descriptor, its
10344 source, and its purpose.
10345 - Disable the SETROUTERPURPOSE controller command: it is now
10347 - Controllers should now specify cache=no or cache=yes when using
10348 the +POSTDESCRIPTOR command.
10349 - Bridge authorities now write bridge descriptors to disk, meaning
10350 we can export them to other programs and begin distributing them
10353 o Major features (directory authorities):
10354 - When a v3 authority is missing votes or signatures, it now tries
10356 - Directory authorities track weighted fractional uptime as well as
10357 weighted mean-time-between failures. WFU is suitable for deciding
10358 whether a node is "usually up", while MTBF is suitable for deciding
10359 whether a node is "likely to stay up." We need both, because
10360 "usually up" is a good requirement for guards, while "likely to
10361 stay up" is a good requirement for long-lived connections.
10363 o Major features (v3 directory system):
10364 - Caches now download v3 network status documents as needed,
10365 and download the descriptors listed in them.
10366 - All hosts now attempt to download and keep fresh v3 authority
10367 certificates, and re-attempt after failures.
10368 - More internal-consistency checks for vote parsing.
10370 o Major bugfixes (crashes):
10371 - If a connection is shut down abruptly because of something that
10372 happened inside connection_flushed_some(), do not call
10373 connection_finished_flushing(). Should fix bug 451. Bugfix on
10376 o Major bugfixes (performance):
10377 - Fix really bad O(n^2) performance when parsing a long list of
10378 routers: Instead of searching the entire list for an "extra-info "
10379 string which usually wasn't there, once for every routerinfo
10380 we read, just scan lines forward until we find one we like.
10382 - When we add data to a write buffer in response to the data on that
10383 write buffer getting low because of a flush, do not consider the
10384 newly added data as a candidate for immediate flushing, but rather
10385 make it wait until the next round of writing. Otherwise, we flush
10386 and refill recursively, and a single greedy TLS connection can
10387 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
10389 o Minor features (v3 authority system):
10390 - Add more ways for tools to download the votes that lead to the
10392 - Send a 503 when low on bandwidth and a vote, consensus, or
10393 certificate is requested.
10394 - If-modified-since is now implemented properly for all kinds of
10395 certificate requests.
10397 o Minor bugfixes (network statuses):
10398 - Tweak the implementation of proposal 109 slightly: allow at most
10399 two Tor servers on the same IP address, except if it's the location
10400 of a directory authority, in which case allow five. Bugfix on
10403 o Minor bugfixes (controller):
10404 - When sending a status event to the controller telling it that an
10405 OR address is reachable, set the port correctly. (Previously we
10406 were reporting the dir port.) Bugfix on 0.1.2.x.
10408 o Minor bugfixes (v3 directory system):
10409 - Fix logic to look up a cert by its signing key digest. Bugfix on
10411 - Only change the reply to a vote to "OK" if it's not already
10412 set. This gets rid of annoying "400 OK" log messages, which may
10413 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
10414 - When we get a valid consensus, recompute the voting schedule.
10415 - Base the valid-after time of a vote on the consensus voting
10416 schedule, not on our preferred schedule.
10417 - Make the return values and messages from signature uploads and
10418 downloads more sensible.
10419 - Fix a memory leak when serving votes and consensus documents, and
10420 another when serving certificates.
10422 o Minor bugfixes (performance):
10423 - Use a slightly simpler string hashing algorithm (copying Python's
10424 instead of Java's) and optimize our digest hashing algorithm to take
10425 advantage of 64-bit platforms and to remove some possibly-costly
10427 - Fix a minor memory leak whenever we parse guards from our state
10428 file. Bugfix on 0.2.0.7-alpha.
10429 - Fix a minor memory leak whenever we write out a file. Bugfix on
10431 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10432 command. Bugfix on 0.2.0.5-alpha.
10434 o Minor bugfixes (portability):
10435 - On some platforms, accept() can return a broken address. Detect
10436 this more quietly, and deal accordingly. Fixes bug 483.
10437 - Stop calling tor_strlower() on uninitialized memory in some cases.
10438 Bugfix in 0.2.0.7-alpha.
10440 o Minor bugfixes (usability):
10441 - Treat some 403 responses from directory servers as INFO rather than
10442 WARN-severity events.
10443 - It's not actually an error to find a non-pending entry in the DNS
10444 cache when canceling a pending resolve. Don't log unless stuff is
10445 fishy. Resolves bug 463.
10447 o Minor bugfixes (anonymity):
10448 - Never report that we've used more bandwidth than we're willing to
10449 relay: it leaks how much non-relay traffic we're using. Resolves
10451 - When looking for a circuit to cannibalize, consider family as well
10452 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10453 circuit cannibalization).
10455 o Code simplifications and refactoring:
10456 - Make a bunch of functions static. Remove some dead code.
10457 - Pull out about a third of the really big routerlist.c; put it in a
10458 new module, networkstatus.c.
10459 - Merge the extra fields in local_routerstatus_t back into
10460 routerstatus_t: we used to need one routerstatus_t for each
10461 authority's opinion, plus a local_routerstatus_t for the locally
10462 computed consensus opinion. To save space, we put the locally
10463 modified fields into local_routerstatus_t, and only the common
10464 stuff into routerstatus_t. But once v3 directories are in use,
10465 clients and caches will no longer need to hold authority opinions;
10466 thus, the rationale for keeping the types separate is now gone.
10467 - Make the code used to reschedule and reattempt downloads more
10469 - Turn all 'Are we a directory server/mirror?' logic into a call to
10471 - Remove the code to generate the oldest (v1) directory format.
10472 The code has been disabled since 0.2.0.5-alpha.
10475 Changes in version 0.2.0.7-alpha - 2007-09-21
10476 This seventh development snapshot makes bridges work again, makes bridge
10477 authorities work for the first time, fixes two huge performance flaws
10478 in hidden services, and fixes a variety of minor issues.
10480 o New directory authorities:
10481 - Set up moria1 and tor26 as the first v3 directory authorities. See
10482 doc/spec/dir-spec.txt for details on the new directory design.
10484 o Major bugfixes (crashes):
10485 - Fix possible segfaults in functions called from
10486 rend_process_relay_cell(). Bugfix on 0.1.2.x.
10488 o Major bugfixes (bridges):
10489 - Fix a bug that made servers send a "404 Not found" in response to
10490 attempts to fetch their server descriptor. This caused Tor servers
10491 to take many minutes to establish reachability for their DirPort,
10492 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
10493 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
10494 users configure that and specify a bridge with an identity
10495 fingerprint, now they will lookup the bridge descriptor at the
10496 default bridge authority via a one-hop tunnel, but once circuits
10497 are established they will switch to a three-hop tunnel for later
10498 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
10500 o Major bugfixes (hidden services):
10501 - Hidden services were choosing introduction points uniquely by
10502 hexdigest, but when constructing the hidden service descriptor
10503 they merely wrote the (potentially ambiguous) nickname.
10504 - Clients now use the v2 intro format for hidden service
10505 connections: they specify their chosen rendezvous point by identity
10506 digest rather than by (potentially ambiguous) nickname. Both
10507 are bugfixes on 0.1.2.x, and they could speed up hidden service
10508 connections dramatically. Thanks to Karsten Loesing.
10510 o Minor features (security):
10511 - As a client, do not believe any server that tells us that an
10512 address maps to an internal address space.
10513 - Make it possible to enable HashedControlPassword and
10514 CookieAuthentication at the same time.
10516 o Minor features (guard nodes):
10517 - Tag every guard node in our state file with the version that
10518 we believe added it, or with our own version if we add it. This way,
10519 if a user temporarily runs an old version of Tor and then switches
10520 back to a new one, she doesn't automatically lose her guards.
10522 o Minor features (speed):
10523 - When implementing AES counter mode, update only the portions of the
10524 counter buffer that need to change, and don't keep separate
10525 network-order and host-order counters when they are the same (i.e.,
10526 on big-endian hosts.)
10528 o Minor features (controller):
10529 - Accept LF instead of CRLF on controller, since some software has a
10530 hard time generating real Internet newlines.
10531 - Add GETINFO values for the server status events
10532 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
10535 o Removed features:
10536 - Routers no longer include bandwidth-history lines in their
10537 descriptors; this information is already available in extra-info
10538 documents, and including it in router descriptors took up 60%
10539 (!) of compressed router descriptor downloads. Completes
10540 implementation of proposal 104.
10541 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
10542 and TorControl.py, as they use the old v0 controller protocol,
10543 and are obsoleted by TorFlow anyway.
10544 - Drop support for v1 rendezvous descriptors, since we never used
10545 them anyway, and the code has probably rotted by now. Based on
10546 patch from Karsten Loesing.
10547 - On OSX, stop warning the user that kqueue support in libevent is
10548 "experimental", since it seems to have worked fine for ages.
10551 - When generating information telling us how to extend to a given
10552 router, do not try to include the nickname if it is absent. Fixes
10553 bug 467. Bugfix on 0.2.0.3-alpha.
10554 - Fix a user-triggerable (but not remotely-triggerable) segfault
10555 in expand_filename(). Bugfix on 0.1.2.x.
10556 - Fix a memory leak when freeing incomplete requests from DNSPort.
10557 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
10558 - Don't try to access (or alter) the state file when running
10559 --list-fingerprint or --verify-config or --hash-password. (Resolves
10560 bug 499.) Bugfix on 0.1.2.x.
10561 - Servers used to decline to publish their DirPort if their
10562 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
10563 were below a threshold. Now they only look at BandwidthRate and
10564 RelayBandwidthRate. Bugfix on 0.1.2.x.
10565 - Remove an optimization in the AES counter-mode code that assumed
10566 that the counter never exceeded 2^68. When the counter can be set
10567 arbitrarily as an IV (as it is by Karsten's new hidden services
10568 code), this assumption no longer holds. Bugfix on 0.1.2.x.
10569 - Resume listing "AUTHORITY" flag for authorities in network status.
10570 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
10572 o Code simplifications and refactoring:
10573 - Revamp file-writing logic so we don't need to have the entire
10574 contents of a file in memory at once before we write to disk. Tor,
10576 - Turn "descriptor store" into a full-fledged type.
10577 - Move all NT services code into a separate source file.
10578 - Unify all code that computes medians, percentile elements, etc.
10579 - Get rid of a needless malloc when parsing address policies.
10582 Changes in version 0.1.2.17 - 2007-08-30
10583 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
10584 X bundles. Vidalia 0.0.14 makes authentication required for the
10585 ControlPort in the default configuration, which addresses important
10586 security risks. Everybody who uses Vidalia (or another controller)
10589 In addition, this Tor update fixes major load balancing problems with
10590 path selection, which should speed things up a lot once many people
10593 o Major bugfixes (security):
10594 - We removed support for the old (v0) control protocol. It has been
10595 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
10596 become more of a headache than it's worth.
10598 o Major bugfixes (load balancing):
10599 - When choosing nodes for non-guard positions, weight guards
10600 proportionally less, since they already have enough load. Patch
10602 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10603 will allow fast Tor servers to get more attention.
10604 - When we're upgrading from an old Tor version, forget our current
10605 guards and pick new ones according to the new weightings. These
10606 three load balancing patches could raise effective network capacity
10607 by a factor of four. Thanks to Mike Perry for measurements.
10609 o Major bugfixes (stream expiration):
10610 - Expire not-yet-successful application streams in all cases if
10611 they've been around longer than SocksTimeout. Right now there are
10612 some cases where the stream will live forever, demanding a new
10613 circuit every 15 seconds. Fixes bug 454; reported by lodger.
10615 o Minor features (controller):
10616 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10617 is valid before any authentication has been received. It tells
10618 a controller what kind of authentication is expected, and what
10619 protocol is spoken. Implements proposal 119.
10621 o Minor bugfixes (performance):
10622 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
10623 greatly speeding up loading cached-routers from disk on startup.
10624 - Disable sentinel-based debugging for buffer code: we squashed all
10625 the bugs that this was supposed to detect a long time ago, and now
10626 its only effect is to change our buffer sizes from nice powers of
10627 two (which platform mallocs tend to like) to values slightly over
10628 powers of two (which make some platform mallocs sad).
10630 o Minor bugfixes (misc):
10631 - If exit bandwidth ever exceeds one third of total bandwidth, then
10632 use the correct formula to weight exit nodes when choosing paths.
10633 Based on patch from Mike Perry.
10634 - Choose perfectly fairly among routers when choosing by bandwidth and
10635 weighting by fraction of bandwidth provided by exits. Previously, we
10636 would choose with only approximate fairness, and correct ourselves
10637 if we ran off the end of the list.
10638 - If we require CookieAuthentication but we fail to write the
10639 cookie file, we would warn but not exit, and end up in a state
10640 where no controller could authenticate. Now we exit.
10641 - If we require CookieAuthentication, stop generating a new cookie
10642 every time we change any piece of our config.
10643 - Refuse to start with certain directory authority keys, and
10644 encourage people using them to stop.
10645 - Terminate multi-line control events properly. Original patch
10647 - Fix a minor memory leak when we fail to find enough suitable
10648 servers to choose a circuit.
10649 - Stop leaking part of the descriptor when we run into a particularly
10650 unparseable piece of it.
10653 Changes in version 0.2.0.6-alpha - 2007-08-26
10654 This sixth development snapshot features a new Vidalia version in the
10655 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
10656 the ControlPort in the default configuration, which addresses important
10659 In addition, this snapshot fixes major load balancing problems
10660 with path selection, which should speed things up a lot once many
10661 people have upgraded. The directory authorities also use a new
10662 mean-time-between-failure approach to tracking which servers are stable,
10663 rather than just looking at the most recent uptime.
10665 o New directory authorities:
10666 - Set up Tonga as the default bridge directory authority.
10669 - Directory authorities now track servers by weighted
10670 mean-times-between-failures. When we have 4 or more days of data,
10671 use measured MTBF rather than declared uptime to decide whether
10672 to call a router Stable. Implements proposal 108.
10674 o Major bugfixes (load balancing):
10675 - When choosing nodes for non-guard positions, weight guards
10676 proportionally less, since they already have enough load. Patch
10678 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10679 will allow fast Tor servers to get more attention.
10680 - When we're upgrading from an old Tor version, forget our current
10681 guards and pick new ones according to the new weightings. These
10682 three load balancing patches could raise effective network capacity
10683 by a factor of four. Thanks to Mike Perry for measurements.
10685 o Major bugfixes (descriptor parsing):
10686 - Handle unexpected whitespace better in malformed descriptors. Bug
10687 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
10690 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
10691 GETINFO for Torstat to use until it can switch to using extrainfos.
10692 - Optionally (if built with -DEXPORTMALLINFO) export the output
10693 of mallinfo via http, as tor/mallinfo.txt. Only accessible
10697 - Do not intermix bridge routers with controller-added
10698 routers. (Bugfix on 0.2.0.x)
10699 - Do not fail with an assert when accept() returns an unexpected
10700 address family. Addresses but does not wholly fix bug 483. (Bugfix
10702 - Let directory authorities startup even when they can't generate
10703 a descriptor immediately, e.g. because they don't know their
10705 - Stop putting the authentication cookie in a file called "0"
10706 in your working directory if you don't specify anything for the
10707 new CookieAuthFile option. Reported by Matt Edman.
10708 - Make it possible to read the PROTOCOLINFO response in a way that
10709 conforms to our control-spec. Reported by Matt Edman.
10710 - Fix a minor memory leak when we fail to find enough suitable
10711 servers to choose a circuit. Bugfix on 0.1.2.x.
10712 - Stop leaking part of the descriptor when we run into a particularly
10713 unparseable piece of it. Bugfix on 0.1.2.x.
10714 - Unmap the extrainfo cache file on exit.
10717 Changes in version 0.2.0.5-alpha - 2007-08-19
10718 This fifth development snapshot fixes compilation on Windows again;
10719 fixes an obnoxious client-side bug that slowed things down and put
10720 extra load on the network; gets us closer to using the v3 directory
10721 voting scheme; makes it easier for Tor controllers to use cookie-based
10722 authentication; and fixes a variety of other bugs.
10724 o Removed features:
10725 - Version 1 directories are no longer generated in full. Instead,
10726 authorities generate and serve "stub" v1 directories that list
10727 no servers. This will stop Tor versions 0.1.0.x and earlier from
10728 working, but (for security reasons) nobody should be running those
10731 o Major bugfixes (compilation, 0.2.0.x):
10732 - Try to fix Win32 compilation again: improve checking for IPv6 types.
10733 - Try to fix MSVC compilation: build correctly on platforms that do
10734 not define s6_addr16 or s6_addr32.
10735 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
10738 o Major bugfixes (stream expiration):
10739 - Expire not-yet-successful application streams in all cases if
10740 they've been around longer than SocksTimeout. Right now there are
10741 some cases where the stream will live forever, demanding a new
10742 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
10743 reported by lodger.
10745 o Minor features (directory servers):
10746 - When somebody requests a list of statuses or servers, and we have
10747 none of those, return a 404 rather than an empty 200.
10749 o Minor features (directory voting):
10750 - Store v3 consensus status consensuses on disk, and reload them
10753 o Minor features (security):
10754 - Warn about unsafe ControlPort configurations.
10755 - Refuse to start with certain directory authority keys, and
10756 encourage people using them to stop.
10758 o Minor features (controller):
10759 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10760 is valid before any authentication has been received. It tells
10761 a controller what kind of authentication is expected, and what
10762 protocol is spoken. Implements proposal 119.
10763 - New config option CookieAuthFile to choose a new location for the
10764 cookie authentication file, and config option
10765 CookieAuthFileGroupReadable to make it group-readable.
10767 o Minor features (unit testing):
10768 - Add command-line arguments to unit-test executable so that we can
10769 invoke any chosen test from the command line rather than having
10770 to run the whole test suite at once; and so that we can turn on
10771 logging for the unit tests.
10773 o Minor bugfixes (on 0.1.2.x):
10774 - If we require CookieAuthentication but we fail to write the
10775 cookie file, we would warn but not exit, and end up in a state
10776 where no controller could authenticate. Now we exit.
10777 - If we require CookieAuthentication, stop generating a new cookie
10778 every time we change any piece of our config.
10779 - When loading bandwidth history, do not believe any information in
10780 the future. Fixes bug 434.
10781 - When loading entry guard information, do not believe any information
10783 - When we have our clock set far in the future and generate an
10784 onion key, then re-set our clock to be correct, we should not stop
10785 the onion key from getting rotated.
10786 - Clean up torrc sample config file.
10787 - Do not automatically run configure from autogen.sh. This
10788 non-standard behavior tended to annoy people who have built other
10791 o Minor bugfixes (on 0.2.0.x):
10792 - Fix a bug with AutomapHostsOnResolve that would always cause
10793 the second request to fail. Bug reported by Kate. Bugfix on
10795 - Fix a bug in ADDRMAP controller replies that would sometimes
10796 try to print a NULL. Patch from tup.
10797 - Read v3 directory authority keys from the right location.
10798 - Numerous bugfixes to directory voting code.
10801 Changes in version 0.1.2.16 - 2007-08-01
10802 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
10803 remote attacker in certain situations to rewrite the user's torrc
10804 configuration file. This can completely compromise anonymity of users
10805 in most configurations, including those running the Vidalia bundles,
10806 TorK, etc. Or worse.
10808 o Major security fixes:
10809 - Close immediately after missing authentication on control port;
10810 do not allow multiple authentication attempts.
10813 Changes in version 0.2.0.4-alpha - 2007-08-01
10814 This fourth development snapshot fixes a critical security vulnerability
10815 for most users, specifically those running Vidalia, TorK, etc. Everybody
10816 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
10818 o Major security fixes:
10819 - Close immediately after missing authentication on control port;
10820 do not allow multiple authentication attempts.
10822 o Major bugfixes (compilation):
10823 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
10826 o Minor features (performance):
10827 - Be even more aggressive about releasing RAM from small
10828 empty buffers. Thanks to our free-list code, this shouldn't be too
10829 performance-intensive.
10830 - Disable sentinel-based debugging for buffer code: we squashed all
10831 the bugs that this was supposed to detect a long time ago, and
10832 now its only effect is to change our buffer sizes from nice
10833 powers of two (which platform mallocs tend to like) to values
10834 slightly over powers of two (which make some platform mallocs sad).
10835 - Log malloc statistics from mallinfo() on platforms where it
10839 Changes in version 0.2.0.3-alpha - 2007-07-29
10840 This third development snapshot introduces new experimental
10841 blocking-resistance features and a preliminary version of the v3
10842 directory voting design, and includes many other smaller features
10846 - The first pieces of our "bridge" design for blocking-resistance
10847 are implemented. People can run bridge directory authorities;
10848 people can run bridges; and people can configure their Tor clients
10849 with a set of bridges to use as the first hop into the Tor network.
10850 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
10852 - Create listener connections before we setuid to the configured
10853 User and Group. Now non-Windows users can choose port values
10854 under 1024, start Tor as root, and have Tor bind those ports
10855 before it changes to another UID. (Windows users could already
10857 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
10858 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
10859 on "vserver" accounts. (Patch from coderman.)
10860 - Be even more aggressive about separating local traffic from relayed
10861 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
10863 o Major features (experimental):
10864 - First cut of code for "v3 dir voting": directory authorities will
10865 vote on a common network status document rather than each publishing
10866 their own opinion. This code needs more testing and more corner-case
10867 handling before it's ready for use.
10870 - Directory authorities now call routers Fast if their bandwidth is
10871 at least 100KB/s, and consider their bandwidth adequate to be a
10872 Guard if it is at least 250KB/s, no matter the medians. This fix
10873 complements proposal 107. [Bugfix on 0.1.2.x]
10874 - Directory authorities now never mark more than 3 servers per IP as
10875 Valid and Running. (Implements proposal 109, by Kevin Bauer and
10877 - Minor change to organizationName and commonName generation
10878 procedures in TLS certificates during Tor handshakes, to invalidate
10879 some earlier censorware approaches. This is not a long-term
10880 solution, but applying it will give us a bit of time to look into
10881 the epidemiology of countermeasures as they spread.
10883 o Major bugfixes (directory):
10884 - Rewrite directory tokenization code to never run off the end of
10885 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
10887 o Minor features (controller):
10888 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
10889 match requests to applications. (Patch from Robert Hogan.)
10890 - Report address and port correctly on connections to DNSPort. (Patch
10891 from Robert Hogan.)
10892 - Add a RESOLVE command to launch hostname lookups. (Original patch
10893 from Robert Hogan.)
10894 - Add GETINFO status/enough-dir-info to let controllers tell whether
10895 Tor has downloaded sufficient directory information. (Patch
10897 - You can now use the ControlSocket option to tell Tor to listen for
10898 controller connections on Unix domain sockets on systems that
10899 support them. (Patch from Peter Palfrader.)
10900 - STREAM NEW events are generated for DNSPort requests and for
10901 tunneled directory connections. (Patch from Robert Hogan.)
10902 - New "GETINFO address-mappings/*" command to get address mappings
10903 with expiry information. "addr-mappings/*" is now deprecated.
10906 o Minor features (misc):
10907 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
10909 - The tor-gencert tool for v3 directory authorities now creates all
10910 files as readable to the file creator only, and write-protects
10911 the authority identity key.
10912 - When dumping memory usage, list bytes used in buffer memory
10914 - When running with dmalloc, dump more stats on hup and on exit.
10915 - Directory authorities now fail quickly and (relatively) harmlessly
10916 if they generate a network status document that is somehow
10919 o Traffic load balancing improvements:
10920 - If exit bandwidth ever exceeds one third of total bandwidth, then
10921 use the correct formula to weight exit nodes when choosing paths.
10922 (Based on patch from Mike Perry.)
10923 - Choose perfectly fairly among routers when choosing by bandwidth and
10924 weighting by fraction of bandwidth provided by exits. Previously, we
10925 would choose with only approximate fairness, and correct ourselves
10926 if we ran off the end of the list. [Bugfix on 0.1.2.x]
10928 o Performance improvements:
10929 - Be more aggressive with freeing buffer RAM or putting it on the
10931 - Use Critical Sections rather than Mutexes for synchronizing threads
10932 on win32; Mutexes are heavier-weight, and designed for synchronizing
10935 o Deprecated and removed features:
10936 - RedirectExits is now deprecated.
10937 - Stop allowing address masks that do not correspond to bit prefixes.
10938 We have warned about these for a really long time; now it's time
10939 to reject them. (Patch from croup.)
10941 o Minor bugfixes (directory):
10942 - Fix another crash bug related to extra-info caching. (Bug found by
10943 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
10944 - Directories no longer return a "304 not modified" when they don't
10945 have the networkstatus the client asked for. Also fix a memory
10946 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
10947 - We had accidentally labelled 0.1.2.x directory servers as not
10948 suitable for begin_dir requests, and had labelled no directory
10949 servers as suitable for uploading extra-info documents. [Bugfix
10952 o Minor bugfixes (dns):
10953 - Fix a crash when DNSPort is set more than once. (Patch from Robert
10954 Hogan.) [Bugfix on 0.2.0.2-alpha]
10955 - Add DNSPort connections to the global connection list, so that we
10956 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
10958 - Fix a dangling reference that could lead to a crash when DNSPort is
10959 changed or closed (Patch from Robert Hogan.) [Bugfix on
10962 o Minor bugfixes (controller):
10963 - Provide DNS expiry times in GMT, not in local time. For backward
10964 compatibility, ADDRMAP events only provide GMT expiry in an extended
10965 field. "GETINFO address-mappings" always does the right thing.
10966 - Use CRLF line endings properly in NS events.
10967 - Terminate multi-line control events properly. (Original patch
10968 from tup.) [Bugfix on 0.1.2.x-alpha]
10969 - Do not include spaces in SOURCE_ADDR fields in STREAM
10970 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
10973 Changes in version 0.1.2.15 - 2007-07-17
10974 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
10975 problems, fixes compilation on BSD, and fixes a variety of other
10976 bugs. Everybody should upgrade.
10978 o Major bugfixes (compilation):
10979 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
10981 o Major bugfixes (crashes):
10982 - Try even harder not to dereference the first character after
10983 an mmap(). Reported by lodger.
10984 - Fix a crash bug in directory authorities when we re-number the
10985 routerlist while inserting a new router.
10986 - When the cached-routers file is an even multiple of the page size,
10987 don't run off the end and crash. (Fixes bug 455; based on idea
10989 - Fix eventdns.c behavior on Solaris: It is critical to include
10990 orconfig.h _before_ sys/types.h, so that we can get the expected
10991 definition of _FILE_OFFSET_BITS.
10993 o Major bugfixes (security):
10994 - Fix a possible buffer overrun when using BSD natd support. Bug
10996 - When sending destroy cells from a circuit's origin, don't include
10997 the reason for tearing down the circuit. The spec says we didn't,
10998 and now we actually don't. Reported by lodger.
10999 - Keep streamids from different exits on a circuit separate. This
11000 bug may have allowed other routers on a given circuit to inject
11001 cells into streams. Reported by lodger; fixes bug 446.
11002 - If there's a never-before-connected-to guard node in our list,
11003 never choose any guards past it. This way we don't expand our
11004 guard list unless we need to.
11006 o Minor bugfixes (guard nodes):
11007 - Weight guard selection by bandwidth, so that low-bandwidth nodes
11008 don't get overused as guards.
11010 o Minor bugfixes (directory):
11011 - Correctly count the number of authorities that recommend each
11012 version. Previously, we were under-counting by 1.
11013 - Fix a potential crash bug when we load many server descriptors at
11014 once and some of them make others of them obsolete. Fixes bug 458.
11016 o Minor bugfixes (hidden services):
11017 - Stop tearing down the whole circuit when the user asks for a
11018 connection to a port that the hidden service didn't configure.
11021 o Minor bugfixes (misc):
11022 - On Windows, we were preventing other processes from reading
11023 cached-routers while Tor was running. Reported by janbar.
11024 - Fix a possible (but very unlikely) bug in picking routers by
11025 bandwidth. Add a log message to confirm that it is in fact
11026 unlikely. Patch from lodger.
11027 - Backport a couple of memory leak fixes.
11028 - Backport miscellaneous cosmetic bugfixes.
11031 Changes in version 0.2.0.2-alpha - 2007-06-02
11032 o Major bugfixes on 0.2.0.1-alpha:
11033 - Fix an assertion failure related to servers without extra-info digests.
11034 Resolves bugs 441 and 442.
11036 o Minor features (directory):
11037 - Support "If-Modified-Since" when answering HTTP requests for
11038 directories, running-routers documents, and network-status documents.
11039 (There's no need to support it for router descriptors, since those
11040 are downloaded by descriptor digest.)
11042 o Minor build issues:
11043 - Clear up some MIPSPro compiler warnings.
11044 - When building from a tarball on a machine that happens to have SVK
11045 installed, report the micro-revision as whatever version existed
11046 in the tarball, not as "x".
11049 Changes in version 0.2.0.1-alpha - 2007-06-01
11050 This early development snapshot provides new features for people running
11051 Tor as both a client and a server (check out the new RelayBandwidth
11052 config options); lets Tor run as a DNS proxy; and generally moves us
11053 forward on a lot of fronts.
11055 o Major features, server usability:
11056 - New config options RelayBandwidthRate and RelayBandwidthBurst:
11057 a separate set of token buckets for relayed traffic. Right now
11058 relayed traffic is defined as answers to directory requests, and
11059 OR connections that don't have any local circuits on them.
11061 o Major features, client usability:
11062 - A client-side DNS proxy feature to replace the need for
11063 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
11064 for DNS requests on port 9999, use the Tor network to resolve them
11065 anonymously, and send the reply back like a regular DNS server.
11066 The code still only implements a subset of DNS.
11067 - Make PreferTunneledDirConns and TunnelDirConns work even when
11068 we have no cached directory info. This means Tor clients can now
11069 do all of their connections protected by TLS.
11071 o Major features, performance and efficiency:
11072 - Directory authorities accept and serve "extra info" documents for
11073 routers. These documents contain fields from router descriptors
11074 that aren't usually needed, and that use a lot of excess
11075 bandwidth. Once these fields are removed from router descriptors,
11076 the bandwidth savings should be about 60%. [Partially implements
11078 - Servers upload extra-info documents to any authority that accepts
11079 them. Authorities (and caches that have been configured to download
11080 extra-info documents) download them as needed. [Partially implements
11082 - Change the way that Tor buffers data that it is waiting to write.
11083 Instead of queueing data cells in an enormous ring buffer for each
11084 client->OR or OR->OR connection, we now queue cells on a separate
11085 queue for each circuit. This lets us use less slack memory, and
11086 will eventually let us be smarter about prioritizing different kinds
11088 - Use memory pools to allocate cells with better speed and memory
11089 efficiency, especially on platforms where malloc() is inefficient.
11090 - Stop reading on edge connections when their corresponding circuit
11091 buffers are full; start again as the circuits empty out.
11093 o Major features, other:
11094 - Add an HSAuthorityRecordStats option that hidden service authorities
11095 can use to track statistics of overall hidden service usage without
11096 logging information that would be very useful to an attacker.
11097 - Start work implementing multi-level keys for directory authorities:
11098 Add a standalone tool to generate key certificates. (Proposal 103.)
11101 - Directory authorities now call routers Stable if they have an
11102 uptime of at least 30 days, even if that's not the median uptime
11103 in the network. Implements proposal 107, suggested by Kevin Bauer
11106 o Minor fixes (resource management):
11107 - Count the number of open sockets separately from the number
11108 of active connection_t objects. This will let us avoid underusing
11109 our allocated connection limit.
11110 - We no longer use socket pairs to link an edge connection to an
11111 anonymous directory connection or a DirPort test connection.
11112 Instead, we track the link internally and transfer the data
11113 in-process. This saves two sockets per "linked" connection (at the
11114 client and at the server), and avoids the nasty Windows socketpair()
11116 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
11117 for every single inactive connection_t. Free items from the
11118 4k/16k-buffer free lists when they haven't been used for a while.
11120 o Minor features (build):
11121 - Make autoconf search for libevent, openssl, and zlib consistently.
11122 - Update deprecated macros in configure.in.
11123 - When warning about missing headers, tell the user to let us
11124 know if the compile succeeds anyway, so we can downgrade the
11126 - Include the current subversion revision as part of the version
11127 string: either fetch it directly if we're in an SVN checkout, do
11128 some magic to guess it if we're in an SVK checkout, or use
11129 the last-detected version if we're building from a .tar.gz.
11130 Use this version consistently in log messages.
11132 o Minor features (logging):
11133 - Always prepend "Bug: " to any log message about a bug.
11134 - Put a platform string (e.g. "Linux i686") in the startup log
11135 message, so when people paste just their logs, we know if it's
11136 OpenBSD or Windows or what.
11137 - When logging memory usage, break down memory used in buffers by
11140 o Minor features (directory system):
11141 - New config option V2AuthoritativeDirectory that all directory
11142 authorities should set. This will let future authorities choose
11143 not to serve V2 directory information.
11144 - Directory authorities allow multiple router descriptors and/or extra
11145 info documents to be uploaded in a single go. This will make
11146 implementing proposal 104 simpler.
11148 o Minor features (controller):
11149 - Add a new config option __DisablePredictedCircuits designed for
11150 use by the controller, when we don't want Tor to build any circuits
11152 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
11153 so we can exit from the middle of the circuit.
11154 - Implement "getinfo status/circuit-established".
11155 - Implement "getinfo status/version/..." so a controller can tell
11156 whether the current version is recommended, and whether any versions
11157 are good, and how many authorities agree. (Patch from shibz.)
11159 o Minor features (hidden services):
11160 - Allow multiple HiddenServicePort directives with the same virtual
11161 port; when they occur, the user is sent round-robin to one
11162 of the target ports chosen at random. Partially fixes bug 393 by
11163 adding limited ad-hoc round-robining.
11165 o Minor features (other):
11167 - Add a new AutomapHostsOnResolve option: when it is enabled, any
11168 resolve request for hosts matching a given pattern causes Tor to
11169 generate an internal virtual address mapping for that host. This
11170 allows DNSPort to work sensibly with hidden service users. By
11171 default, .exit and .onion addresses are remapped; the list of
11172 patterns can be reconfigured with AutomapHostsSuffixes.
11173 - Add an "-F" option to tor-resolve to force a resolve for a .onion
11174 address. Thanks to the AutomapHostsOnResolve option, this is no
11175 longer a completely silly thing to do.
11176 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
11177 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
11178 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
11179 minus 1 byte: the actual maximum declared bandwidth.
11181 o Removed features:
11182 - Removed support for the old binary "version 0" controller protocol.
11183 This has been deprecated since 0.1.1, and warnings have been issued
11184 since 0.1.2. When we encounter a v0 control message, we now send
11185 back an error and close the connection.
11186 - Remove the old "dns worker" server DNS code: it hasn't been default
11187 since 0.1.2.2-alpha, and all the servers seem to be using the new
11190 o Minor bugfixes (portability):
11191 - Even though Windows is equally happy with / and \ as path separators,
11192 try to use \ consistently on Windows and / consistently on Unix: it
11193 makes the log messages nicer.
11194 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
11195 - Read resolv.conf files correctly on platforms where read() returns
11196 partial results on small file reads.
11198 o Minor bugfixes (directory):
11199 - Correctly enforce that elements of directory objects do not appear
11200 more often than they are allowed to appear.
11201 - When we are reporting the DirServer line we just parsed, we were
11202 logging the second stanza of the key fingerprint, not the first.
11204 o Minor bugfixes (logging):
11205 - When we hit an EOF on a log (probably because we're shutting down),
11206 don't try to remove the log from the list: just mark it as
11207 unusable. (Bulletproofs against bug 222.)
11209 o Minor bugfixes (other):
11210 - In the exitlist script, only consider the most recently published
11211 server descriptor for each server. Also, when the user requests
11212 a list of servers that _reject_ connections to a given address,
11213 explicitly exclude the IPs that also have servers that accept
11214 connections to that address. (Resolves bug 405.)
11215 - Stop allowing hibernating servers to be "stable" or "fast".
11216 - On Windows, we were preventing other processes from reading
11217 cached-routers while Tor was running. (Reported by janbar)
11218 - Make the NodeFamilies config option work. (Reported by
11219 lodger -- it has never actually worked, even though we added it
11221 - Check return values from pthread_mutex functions.
11222 - Don't save non-general-purpose router descriptors to the disk cache,
11223 because we have no way of remembering what their purpose was when
11225 - Add even more asserts to hunt down bug 417.
11226 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
11227 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
11228 Add a log message to confirm that it is in fact unlikely.
11230 o Minor bugfixes (controller):
11231 - Make 'getinfo fingerprint' return a 551 error if we're not a
11232 server, so we match what the control spec claims we do. Reported
11234 - Fix a typo in an error message when extendcircuit fails that
11235 caused us to not follow the \r\n-based delimiter protocol. Reported
11238 o Code simplifications and refactoring:
11239 - Stop passing around circuit_t and crypt_path_t pointers that are
11240 implicit in other procedure arguments.
11241 - Drop the old code to choke directory connections when the
11242 corresponding OR connections got full: thanks to the cell queue
11243 feature, OR conns don't get full any more.
11244 - Make dns_resolve() handle attaching connections to circuits
11245 properly, so the caller doesn't have to.
11246 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
11247 - Keep the connection array as a dynamic smartlist_t, rather than as
11248 a fixed-sized array. This is important, as the number of connections
11249 is becoming increasingly decoupled from the number of sockets.
11252 Changes in version 0.1.2.14 - 2007-05-25
11253 Tor 0.1.2.14 changes the addresses of two directory authorities (this
11254 change especially affects those who serve or use hidden services),
11255 and fixes several other crash- and security-related bugs.
11257 o Directory authority changes:
11258 - Two directory authorities (moria1 and moria2) just moved to new
11259 IP addresses. This change will particularly affect those who serve
11260 or use hidden services.
11262 o Major bugfixes (crashes):
11263 - If a directory server runs out of space in the connection table
11264 as it's processing a begin_dir request, it will free the exit stream
11265 but leave it attached to the circuit, leading to unpredictable
11266 behavior. (Reported by seeess, fixes bug 425.)
11267 - Fix a bug in dirserv_remove_invalid() that would cause authorities
11268 to corrupt memory under some really unlikely scenarios.
11269 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
11270 - Avoid segfaults when reading from mmaped descriptor file. (Reported
11273 o Major bugfixes (security):
11274 - When choosing an entry guard for a circuit, avoid using guards
11275 that are in the same family as the chosen exit -- not just guards
11276 that are exactly the chosen exit. (Reported by lodger.)
11278 o Major bugfixes (resource management):
11279 - If a directory authority is down, skip it when deciding where to get
11280 networkstatus objects or descriptors. Otherwise we keep asking
11281 every 10 seconds forever. Fixes bug 384.
11282 - Count it as a failure if we fetch a valid network-status but we
11283 don't want to keep it. Otherwise we'll keep fetching it and keep
11284 not wanting to keep it. Fixes part of bug 422.
11285 - If all of our dirservers have given us bad or no networkstatuses
11286 lately, then stop hammering them once per minute even when we
11287 think they're failed. Fixes another part of bug 422.
11290 - Actually set the purpose correctly for descriptors inserted with
11291 purpose=controller.
11292 - When we have k non-v2 authorities in our DirServer config,
11293 we ignored the last k authorities in the list when updating our
11295 - Correctly back-off from requesting router descriptors that we are
11296 having a hard time downloading.
11297 - Read resolv.conf files correctly on platforms where read() returns
11298 partial results on small file reads.
11299 - Don't rebuild the entire router store every time we get 32K of
11300 routers: rebuild it when the journal gets very large, or when
11301 the gaps in the store get very large.
11304 - When routers publish SVN revisions in their router descriptors,
11305 authorities now include those versions correctly in networkstatus
11307 - Warn when using a version of libevent before 1.3b to run a server on
11308 OSX or BSD: these versions interact badly with userspace threads.
11311 Changes in version 0.1.2.13 - 2007-04-24
11312 This release features some major anonymity fixes, such as safer path
11313 selection; better client performance; faster bootstrapping, better
11314 address detection, and better DNS support for servers; write limiting as
11315 well as read limiting to make servers easier to run; and a huge pile of
11316 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
11318 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
11319 of the Freenode IRC network, remembering his patience and vision for
11320 free speech on the Internet.
11323 - Fix a memory leak when we ask for "all" networkstatuses and we
11324 get one we don't recognize.
11325 - Add more asserts to hunt down bug 417.
11326 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
11329 Changes in version 0.1.2.12-rc - 2007-03-16
11331 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
11332 directory information requested inside Tor connections (i.e. via
11333 begin_dir cells). It only triggered when the same connection was
11334 serving other data at the same time. Reported by seeess.
11337 - When creating a circuit via the controller, send a 'launched'
11338 event when we're done, so we follow the spec better.
11341 Changes in version 0.1.2.11-rc - 2007-03-15
11342 o Minor bugfixes (controller), reported by daejees:
11343 - Correct the control spec to match how the code actually responds
11344 to 'getinfo addr-mappings/*'.
11345 - The control spec described a GUARDS event, but the code
11346 implemented a GUARD event. Standardize on GUARD, but let people
11347 ask for GUARDS too.
11350 Changes in version 0.1.2.10-rc - 2007-03-07
11351 o Major bugfixes (Windows):
11352 - Do not load the NT services library functions (which may not exist)
11353 just to detect if we're a service trying to shut down. Now we run
11354 on Win98 and friends again.
11356 o Minor bugfixes (other):
11357 - Clarify a couple of log messages.
11358 - Fix a misleading socks5 error number.
11361 Changes in version 0.1.2.9-rc - 2007-03-02
11362 o Major bugfixes (Windows):
11363 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
11364 of the usual GCC "%llu". This prevents a bug when saving 64-bit
11365 int configuration values: the high-order 32 bits would get
11366 truncated. In particular, we were being bitten by the default
11367 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
11368 and maybe also bug 397.)
11370 o Minor bugfixes (performance):
11371 - Use OpenSSL's AES implementation on platforms where it's faster.
11372 This could save us as much as 10% CPU usage.
11374 o Minor bugfixes (server):
11375 - Do not rotate onion key immediately after setting it for the first
11378 o Minor bugfixes (directory authorities):
11379 - Stop calling servers that have been hibernating for a long time
11380 "stable". Also, stop letting hibernating or obsolete servers affect
11381 uptime and bandwidth cutoffs.
11382 - Stop listing hibernating servers in the v1 directory.
11384 o Minor bugfixes (hidden services):
11385 - Upload hidden service descriptors slightly less often, to reduce
11386 load on authorities.
11388 o Minor bugfixes (other):
11389 - Fix an assert that could trigger if a controller quickly set then
11390 cleared EntryNodes. Bug found by Udo van den Heuvel.
11391 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
11393 - Fix a potential race condition in the rpm installer. Found by
11395 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
11396 of 2 as indicating that the server is completely bad; it sometimes
11397 means that the server is just bad for the request in question. (may fix
11398 the last of bug 326.)
11399 - Disable encrypted directory connections when we don't have a server
11400 descriptor for the destination. We'll get this working again in
11404 Changes in version 0.1.2.8-beta - 2007-02-26
11405 o Major bugfixes (crashes):
11406 - Stop crashing when the controller asks us to resetconf more than
11407 one config option at once. (Vidalia 0.0.11 does this.)
11408 - Fix a crash that happened on Win98 when we're given command-line
11409 arguments: don't try to load NT service functions from advapi32.dll
11410 except when we need them. (Bug introduced in 0.1.2.7-alpha;
11412 - Fix a longstanding obscure crash bug that could occur when
11413 we run out of DNS worker processes. (Resolves bug 390.)
11415 o Major bugfixes (hidden services):
11416 - Correctly detect whether hidden service descriptor downloads are
11417 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
11419 o Major bugfixes (accounting):
11420 - When we start during an accounting interval before it's time to wake
11421 up, remember to wake up at the correct time. (May fix bug 342.)
11423 o Minor bugfixes (controller):
11424 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
11425 clear the corresponding on_circuit variable, and remember later
11426 that we don't need to send a redundant CLOSED event. Resolves part
11428 - Report events where a resolve succeeded or where we got a socks
11429 protocol error correctly, rather than calling both of them
11431 - Change reported stream target addresses to IP consistently when
11432 we finally get the IP from an exit node.
11433 - Send log messages to the controller even if they happen to be very
11436 o Minor bugfixes (other):
11437 - Display correct results when reporting which versions are
11438 recommended, and how recommended they are. (Resolves bug 383.)
11439 - Improve our estimates for directory bandwidth to be less random:
11440 guess that an unrecognized directory will have the average bandwidth
11441 from all known directories, not that it will have the average
11442 bandwidth from those directories earlier than it on the list.
11443 - If we start a server with ClientOnly 1, then set ClientOnly to 0
11444 and hup, stop triggering an assert based on an empty onion_key.
11445 - On platforms with no working mmap() equivalent, don't warn the
11446 user when cached-routers doesn't exist.
11447 - Warn the user when mmap() [or its equivalent] fails for some reason
11448 other than file-not-found.
11449 - Don't warn the user when cached-routers.new doesn't exist: that's
11450 perfectly fine when starting up for the first time.
11451 - When EntryNodes are configured, rebuild the guard list to contain,
11452 in order: the EntryNodes that were guards before; the rest of the
11453 EntryNodes; the nodes that were guards before.
11454 - Mask out all signals in sub-threads; only the libevent signal
11455 handler should be processing them. This should prevent some crashes
11456 on some machines using pthreads. (Patch from coderman.)
11457 - Fix switched arguments on memset in the implementation of
11458 tor_munmap() for systems with no mmap() call.
11459 - When Tor receives a router descriptor that it asked for, but
11460 no longer wants (because it has received fresh networkstatuses
11461 in the meantime), do not warn the user. Cache the descriptor if
11462 we're a cache; drop it if we aren't.
11463 - Make earlier entry guards _really_ get retried when the network
11465 - On a malformed DNS reply, always give an error to the corresponding
11467 - Build with recent libevents on platforms that do not define the
11468 nonstandard types "u_int8_t" and friends.
11470 o Minor features (controller):
11471 - Warn the user when an application uses the obsolete binary v0
11472 control protocol. We're planning to remove support for it during
11473 the next development series, so it's good to give people some
11475 - Add STREAM_BW events to report per-entry-stream bandwidth
11476 use. (Patch from Robert Hogan.)
11477 - Rate-limit SIGNEWNYM signals in response to controllers that
11478 impolitely generate them for every single stream. (Patch from
11479 mwenge; closes bug 394.)
11480 - Make REMAP stream events have a SOURCE (cache or exit), and
11481 make them generated in every case where we get a successful
11482 connected or resolved cell.
11484 o Minor bugfixes (performance):
11485 - Call router_have_min_dir_info half as often. (This is showing up in
11486 some profiles, but not others.)
11487 - When using GCC, make log_debug never get called at all, and its
11488 arguments never get evaluated, when no debug logs are configured.
11489 (This is showing up in some profiles, but not others.)
11492 - Remove some never-implemented options. Mark PathlenCoinWeight as
11494 - Implement proposal 106: Stop requiring clients to have well-formed
11495 certificates; stop checking nicknames in certificates. (Clients
11496 have certificates so that they can look like Tor servers, but in
11497 the future we might want to allow them to look like regular TLS
11498 clients instead. Nicknames in certificates serve no purpose other
11499 than making our protocol easier to recognize on the wire.)
11500 - Revise messages on handshake failure again to be even more clear about
11501 which are incoming connections and which are outgoing.
11502 - Discard any v1 directory info that's over 1 month old (for
11503 directories) or over 1 week old (for running-routers lists).
11504 - Do not warn when individual nodes in the configuration's EntryNodes,
11505 ExitNodes, etc are down: warn only when all possible nodes
11506 are down. (Fixes bug 348.)
11507 - Always remove expired routers and networkstatus docs before checking
11508 whether we have enough information to build circuits. (Fixes
11510 - Put a lower-bound on MaxAdvertisedBandwidth.
11513 Changes in version 0.1.2.7-alpha - 2007-02-06
11514 o Major bugfixes (rate limiting):
11515 - Servers decline directory requests much more aggressively when
11516 they're low on bandwidth. Otherwise they end up queueing more and
11517 more directory responses, which can't be good for latency.
11518 - But never refuse directory requests from local addresses.
11519 - Fix a memory leak when sending a 503 response for a networkstatus
11521 - Be willing to read or write on local connections (e.g. controller
11522 connections) even when the global rate limiting buckets are empty.
11523 - If our system clock jumps back in time, don't publish a negative
11524 uptime in the descriptor. Also, don't let the global rate limiting
11525 buckets go absurdly negative.
11526 - Flush local controller connection buffers periodically as we're
11527 writing to them, so we avoid queueing 4+ megabytes of data before
11530 o Major bugfixes (NT services):
11531 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
11532 command-line flag so that admins can override the default by saying
11533 "tor --service install --user "SomeUser"". This will not affect
11534 existing installed services. Also, warn the user that the service
11535 will look for its configuration file in the service user's
11536 %appdata% directory. (We can't do the 'hardwire the user's appdata
11537 directory' trick any more, since we may not have read access to that
11540 o Major bugfixes (other):
11541 - Previously, we would cache up to 16 old networkstatus documents
11542 indefinitely, if they came from nontrusted authorities. Now we
11543 discard them if they are more than 10 days old.
11544 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
11546 - Detect and reject malformed DNS responses containing circular
11548 - If exits are rare enough that we're not marking exits as guards,
11549 ignore exit bandwidth when we're deciding the required bandwidth
11551 - When we're handling a directory connection tunneled over Tor,
11552 don't fill up internal memory buffers with all the data we want
11553 to tunnel; instead, only add it if the OR connection that will
11554 eventually receive it has some room for it. (This can lead to
11555 slowdowns in tunneled dir connections; a better solution will have
11556 to wait for 0.2.0.)
11558 o Minor bugfixes (dns):
11559 - Add some defensive programming to eventdns.c in an attempt to catch
11560 possible memory-stomping bugs.
11561 - Detect and reject DNS replies containing IPv4 or IPv6 records with
11562 an incorrect number of bytes. (Previously, we would ignore the
11564 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
11565 in the correct order, and doesn't crash.
11566 - Free memory held in recently-completed DNS lookup attempts on exit.
11567 This was not a memory leak, but may have been hiding memory leaks.
11568 - Handle TTL values correctly on reverse DNS lookups.
11569 - Treat failure to parse resolv.conf as an error.
11571 o Minor bugfixes (other):
11572 - Fix crash with "tor --list-fingerprint" (reported by seeess).
11573 - When computing clock skew from directory HTTP headers, consider what
11574 time it was when we finished asking for the directory, not what
11576 - Expire socks connections if they spend too long waiting for the
11577 handshake to finish. Previously we would let them sit around for
11578 days, if the connecting application didn't close them either.
11579 - And if the socks handshake hasn't started, don't send a
11580 "DNS resolve socks failed" handshake reply; just close it.
11581 - Stop using C functions that OpenBSD's linker doesn't like.
11582 - Don't launch requests for descriptors unless we have networkstatuses
11583 from at least half of the authorities. This delays the first
11584 download slightly under pathological circumstances, but can prevent
11585 us from downloading a bunch of descriptors we don't need.
11586 - Do not log IPs with TLS failures for incoming TLS
11587 connections. (Fixes bug 382.)
11588 - If the user asks to use invalid exit nodes, be willing to use
11590 - Stop using the reserved ac_cv namespace in our configure script.
11591 - Call stat() slightly less often; use fstat() when possible.
11592 - Refactor the way we handle pending circuits when an OR connection
11593 completes or fails, in an attempt to fix a rare crash bug.
11594 - Only rewrite a conn's address based on X-Forwarded-For: headers
11595 if it's a parseable public IP address; and stop adding extra quotes
11596 to the resulting address.
11599 - Weight directory requests by advertised bandwidth. Now we can
11600 let servers enable write limiting but still allow most clients to
11601 succeed at their directory requests. (We still ignore weights when
11602 choosing a directory authority; I hope this is a feature.)
11605 - Create a new file ReleaseNotes which was the old ChangeLog. The
11606 new ChangeLog file now includes the summaries for all development
11608 - Check for addresses with invalid characters at the exit as well
11609 as at the client, and warn less verbosely when they fail. You can
11610 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
11611 - Adapt a patch from goodell to let the contrib/exitlist script
11612 take arguments rather than require direct editing.
11613 - Inform the server operator when we decide not to advertise a
11614 DirPort due to AccountingMax enabled or a low BandwidthRate. It
11615 was confusing Zax, so now we're hopefully more helpful.
11616 - Bring us one step closer to being able to establish an encrypted
11617 directory tunnel without knowing a descriptor first. Still not
11618 ready yet. As part of the change, now assume we can use a
11619 create_fast cell if we don't know anything about a router.
11620 - Allow exit nodes to use nameservers running on ports other than 53.
11621 - Servers now cache reverse DNS replies.
11622 - Add an --ignore-missing-torrc command-line option so that we can
11623 get the "use sensible defaults if the configuration file doesn't
11624 exist" behavior even when specifying a torrc location on the command
11627 o Minor features (controller):
11628 - Track reasons for OR connection failure; make these reasons
11629 available via the controller interface. (Patch from Mike Perry.)
11630 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
11631 can learn when clients are sending malformed hostnames to Tor.
11632 - Clean up documentation for controller status events.
11633 - Add a REMAP status to stream events to note that a stream's
11634 address has changed because of a cached address or a MapAddress
11638 Changes in version 0.1.2.6-alpha - 2007-01-09
11640 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
11641 connection handles more than 4 gigs in either direction, we crash.
11642 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
11643 advertised exit node, somebody might try to exit from us when
11644 we're bootstrapping and before we've built our descriptor yet.
11645 Refuse the connection rather than crashing.
11648 - Warn if we (as a server) find that we've resolved an address that we
11649 weren't planning to resolve.
11650 - Warn that using select() on any libevent version before 1.1 will be
11651 unnecessarily slow (even for select()).
11652 - Flush ERR-level controller status events just like we currently
11653 flush ERR-level log events, so that a Tor shutdown doesn't prevent
11654 the controller from learning about current events.
11656 o Minor features (more controller status events):
11657 - Implement EXTERNAL_ADDRESS server status event so controllers can
11658 learn when our address changes.
11659 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
11660 can learn when directories reject our descriptor.
11661 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
11662 can learn when a client application is speaking a non-socks protocol
11664 - Implement DANGEROUS_SOCKS client status event so controllers
11665 can learn when a client application is leaking DNS addresses.
11666 - Implement BUG general status event so controllers can learn when
11667 Tor is unhappy about its internal invariants.
11668 - Implement CLOCK_SKEW general status event so controllers can learn
11669 when Tor thinks the system clock is set incorrectly.
11670 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
11671 server status events so controllers can learn when their descriptors
11672 are accepted by a directory.
11673 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
11674 server status events so controllers can learn about Tor's progress in
11675 deciding whether it's reachable from the outside.
11676 - Implement BAD_LIBEVENT general status event so controllers can learn
11677 when we have a version/method combination in libevent that needs to
11679 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
11680 and DNS_USELESS server status events so controllers can learn
11681 about changes to DNS server status.
11683 o Minor features (directory):
11684 - Authorities no longer recommend exits as guards if this would shift
11685 too much load to the exit nodes.
11688 Changes in version 0.1.2.5-alpha - 2007-01-06
11690 - Enable write limiting as well as read limiting. Now we sacrifice
11691 capacity if we're pushing out lots of directory traffic, rather
11692 than overrunning the user's intended bandwidth limits.
11693 - Include TLS overhead when counting bandwidth usage; previously, we
11694 would count only the bytes sent over TLS, but not the bytes used
11696 - Support running the Tor service with a torrc not in the same
11697 directory as tor.exe and default to using the torrc located in
11698 the %appdata%\Tor\ of the user who installed the service. Patch
11700 - Servers now check for the case when common DNS requests are going to
11701 wildcarded addresses (i.e. all getting the same answer), and change
11702 their exit policy to reject *:* if it's happening.
11703 - Implement BEGIN_DIR cells, so we can connect to the directory
11704 server via TLS to do encrypted directory requests rather than
11705 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
11706 config options if you like.
11708 o Minor features (config and docs):
11709 - Start using the state file to store bandwidth accounting data:
11710 the bw_accounting file is now obsolete. We'll keep generating it
11711 for a while for people who are still using 0.1.2.4-alpha.
11712 - Try to batch changes to the state file so that we do as few
11713 disk writes as possible while still storing important things in
11715 - The state file and the bw_accounting file get saved less often when
11716 the AvoidDiskWrites config option is set.
11717 - Make PIDFile work on Windows (untested).
11718 - Add internal descriptions for a bunch of configuration options:
11719 accessible via controller interface and in comments in saved
11721 - Reject *:563 (NNTPS) in the default exit policy. We already reject
11722 NNTP by default, so this seems like a sensible addition.
11723 - Clients now reject hostnames with invalid characters. This should
11724 avoid some inadvertent info leaks. Add an option
11725 AllowNonRFC953Hostnames to disable this behavior, in case somebody
11726 is running a private network with hosts called @, !, and #.
11727 - Add a maintainer script to tell us which options are missing
11728 documentation: "make check-docs".
11729 - Add a new address-spec.txt document to describe our special-case
11730 addresses: .exit, .onion, and .noconnnect.
11732 o Minor features (DNS):
11733 - Ongoing work on eventdns infrastructure: now it has dns server
11734 and ipv6 support. One day Tor will make use of it.
11735 - Add client-side caching for reverse DNS lookups.
11736 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
11737 - When we change nameservers or IP addresses, reset and re-launch
11738 our tests for DNS hijacking.
11740 o Minor features (directory):
11741 - Authorities now specify server versions in networkstatus. This adds
11742 about 2% to the size of compressed networkstatus docs, and allows
11743 clients to tell which servers support BEGIN_DIR and which don't.
11744 The implementation is forward-compatible with a proposed future
11745 protocol version scheme not tied to Tor versions.
11746 - DirServer configuration lines now have an orport= option so
11747 clients can open encrypted tunnels to the authorities without
11748 having downloaded their descriptors yet. Enabled for moria1,
11749 moria2, tor26, and lefkada now in the default configuration.
11750 - Directory servers are more willing to send a 503 "busy" if they
11751 are near their write limit, especially for v1 directory requests.
11752 Now they can use their limited bandwidth for actual Tor traffic.
11753 - Clients track responses with status 503 from dirservers. After a
11754 dirserver has given us a 503, we try not to use it until an hour has
11755 gone by, or until we have no dirservers that haven't given us a 503.
11756 - When we get a 503 from a directory, and we're not a server, we don't
11757 count the failure against the total number of failures allowed
11758 for the thing we're trying to download.
11759 - Report X-Your-Address-Is correctly from tunneled directory
11760 connections; don't report X-Your-Address-Is when it's an internal
11761 address; and never believe reported remote addresses when they're
11763 - Protect against an unlikely DoS attack on directory servers.
11764 - Add a BadDirectory flag to network status docs so that authorities
11765 can (eventually) tell clients about caches they believe to be
11768 o Minor features (controller):
11769 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
11770 - Reimplement GETINFO so that info/names stays in sync with the
11772 - Implement "GETINFO fingerprint".
11773 - Implement "SETEVENTS GUARD" so controllers can get updates on
11774 entry guard status as it changes.
11776 o Minor features (clean up obsolete pieces):
11777 - Remove some options that have been deprecated since at least
11778 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
11779 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
11780 to set log options.
11781 - We no longer look for identity and onion keys in "identity.key" and
11782 "onion.key" -- these were replaced by secret_id_key and
11783 secret_onion_key in 0.0.8pre1.
11784 - We no longer require unrecognized directory entries to be
11787 o Major bugfixes (security):
11788 - Stop sending the HttpProxyAuthenticator string to directory
11789 servers when directory connections are tunnelled through Tor.
11790 - Clients no longer store bandwidth history in the state file.
11791 - Do not log introduction points for hidden services if SafeLogging
11793 - When generating bandwidth history, round down to the nearest
11794 1k. When storing accounting data, round up to the nearest 1k.
11795 - When we're running as a server, remember when we last rotated onion
11796 keys, so that we will rotate keys once they're a week old even if
11797 we never stay up for a week ourselves.
11799 o Major bugfixes (other):
11800 - Fix a longstanding bug in eventdns that prevented the count of
11801 timed-out resolves from ever being reset. This bug caused us to
11802 give up on a nameserver the third time it timed out, and try it
11803 10 seconds later... and to give up on it every time it timed out
11805 - Take out the '5 second' timeout from the connection retry
11806 schedule. Now the first connect attempt will wait a full 10
11807 seconds before switching to a new circuit. Perhaps this will help
11808 a lot. Based on observations from Mike Perry.
11809 - Fix a bug on the Windows implementation of tor_mmap_file() that
11810 would prevent the cached-routers file from ever loading. Reported
11814 - Fix an assert failure when a directory authority sets
11815 AuthDirRejectUnlisted and then receives a descriptor from an
11816 unlisted router. Reported by seeess.
11817 - Avoid a double-free when parsing malformed DirServer lines.
11818 - Fix a bug when a BSD-style PF socket is first used. Patch from
11820 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
11821 to resolve an address at a given exit node even when they ask for
11823 - Servers no longer ever list themselves in their "family" line,
11824 even if configured to do so. This makes it easier to configure
11825 family lists conveniently.
11826 - When running as a server, don't fall back to 127.0.0.1 when no
11827 nameservers are configured in /etc/resolv.conf; instead, make the
11828 user fix resolv.conf or specify nameservers explicitly. (Resolves
11830 - Stop accepting certain malformed ports in configured exit policies.
11831 - Don't re-write the fingerprint file every restart, unless it has
11833 - Stop warning when a single nameserver fails: only warn when _all_ of
11834 our nameservers have failed. Also, when we only have one nameserver,
11835 raise the threshold for deciding that the nameserver is dead.
11836 - Directory authorities now only decide that routers are reachable
11837 if their identity keys are as expected.
11838 - When the user uses bad syntax in the Log config line, stop
11839 suggesting other bad syntax as a replacement.
11840 - Correctly detect ipv6 DNS capability on OpenBSD.
11842 o Minor bugfixes (controller):
11843 - Report the circuit number correctly in STREAM CLOSED events. Bug
11844 reported by Mike Perry.
11845 - Do not report bizarre values for results of accounting GETINFOs
11846 when the last second's write or read exceeds the allotted bandwidth.
11847 - Report "unrecognized key" rather than an empty string when the
11848 controller tries to fetch a networkstatus that doesn't exist.
11851 Changes in version 0.1.1.26 - 2006-12-14
11852 o Security bugfixes:
11853 - Stop sending the HttpProxyAuthenticator string to directory
11854 servers when directory connections are tunnelled through Tor.
11855 - Clients no longer store bandwidth history in the state file.
11856 - Do not log introduction points for hidden services if SafeLogging
11860 - Fix an assert failure when a directory authority sets
11861 AuthDirRejectUnlisted and then receives a descriptor from an
11862 unlisted router (reported by seeess).
11865 Changes in version 0.1.2.4-alpha - 2006-12-03
11867 - Add support for using natd; this allows FreeBSDs earlier than
11868 5.1.2 to have ipfw send connections through Tor without using
11869 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
11872 - Make all connections to addresses of the form ".noconnect"
11873 immediately get closed. This lets application/controller combos
11874 successfully test whether they're talking to the same Tor by
11875 watching for STREAM events.
11876 - Make cross.sh cross-compilation script work even when autogen.sh
11877 hasn't been run. (Patch from Michael Mohr.)
11878 - Statistics dumped by -USR2 now include a breakdown of public key
11879 operations, for profiling.
11882 - Fix a major leak when directory authorities parse their
11883 approved-routers list, a minor memory leak when we fail to pick
11884 an exit node, and a few rare leaks on errors.
11885 - Handle TransPort connections even when the server sends data before
11886 the client sends data. Previously, the connection would just hang
11887 until the client sent data. (Patch from tup based on patch from
11889 - Avoid assert failure when our cached-routers file is empty on
11893 - Don't log spurious warnings when we see a circuit close reason we
11894 don't recognize; it's probably just from a newer version of Tor.
11895 - Have directory authorities allow larger amounts of drift in uptime
11896 without replacing the server descriptor: previously, a server that
11897 restarted every 30 minutes could have 48 "interesting" descriptors
11899 - Start linking to the Tor specification and Tor reference manual
11900 correctly in the Windows installer.
11901 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11902 Tor/Privoxy we also uninstall Vidalia.
11903 - Resume building on Irix64, and fix a lot of warnings from its
11904 MIPSpro C compiler.
11905 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
11906 when we're running as a client.
11909 Changes in version 0.1.1.25 - 2006-11-04
11911 - When a client asks us to resolve (rather than connect to)
11912 an address, and we have a cached answer, give them the cached
11913 answer. Previously, we would give them no answer at all.
11914 - We were building exactly the wrong circuits when we predict
11915 hidden service requirements, meaning Tor would have to build all
11916 its circuits on demand.
11917 - If none of our live entry guards have a high uptime, but we
11918 require a guard with a high uptime, try adding a new guard before
11919 we give up on the requirement. This patch should make long-lived
11920 connections more stable on average.
11921 - When testing reachability of our DirPort, don't launch new
11922 tests when there's already one in progress -- unreachable
11923 servers were stacking up dozens of testing streams.
11925 o Security bugfixes:
11926 - When the user sends a NEWNYM signal, clear the client-side DNS
11927 cache too. Otherwise we continue to act on previous information.
11930 - Avoid a memory corruption bug when creating a hash table for
11932 - Avoid possibility of controller-triggered crash when misusing
11933 certain commands from a v0 controller on platforms that do not
11934 handle printf("%s",NULL) gracefully.
11935 - Avoid infinite loop on unexpected controller input.
11936 - Don't log spurious warnings when we see a circuit close reason we
11937 don't recognize; it's probably just from a newer version of Tor.
11938 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11939 Tor/Privoxy we also uninstall Vidalia.
11942 Changes in version 0.1.2.3-alpha - 2006-10-29
11944 - Prepare for servers to publish descriptors less often: never
11945 discard a descriptor simply for being too old until either it is
11946 recommended by no authorities, or until we get a better one for
11947 the same router. Make caches consider retaining old recommended
11948 routers for even longer.
11949 - If most authorities set a BadExit flag for a server, clients
11950 don't think of it as a general-purpose exit. Clients only consider
11951 authorities that advertise themselves as listing bad exits.
11952 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
11953 headers for content, so that we can work better in the presence of
11954 caching HTTP proxies.
11955 - Allow authorities to list nodes as bad exits by fingerprint or by
11958 o Minor features, controller:
11959 - Add a REASON field to CIRC events; for backward compatibility, this
11960 field is sent only to controllers that have enabled the extended
11961 event format. Also, add additional reason codes to explain why
11962 a given circuit has been destroyed or truncated. (Patches from
11964 - Add a REMOTE_REASON field to extended CIRC events to tell the
11965 controller about why a remote OR told us to close a circuit.
11966 - Stream events also now have REASON and REMOTE_REASON fields,
11967 working much like those for circuit events.
11968 - There's now a GETINFO ns/... field so that controllers can ask Tor
11969 about the current status of a router.
11970 - A new event type "NS" to inform a controller when our opinion of
11971 a router's status has changed.
11972 - Add a GETINFO events/names and GETINFO features/names so controllers
11973 can tell which events and features are supported.
11974 - A new CLEARDNSCACHE signal to allow controllers to clear the
11975 client-side DNS cache without expiring circuits.
11977 o Security bugfixes:
11978 - When the user sends a NEWNYM signal, clear the client-side DNS
11979 cache too. Otherwise we continue to act on previous information.
11982 - Avoid sending junk to controllers or segfaulting when a controller
11983 uses EVENT_NEW_DESC with verbose nicknames.
11984 - Stop triggering asserts if the controller tries to extend hidden
11985 service circuits (reported by mwenge).
11986 - Avoid infinite loop on unexpected controller input.
11987 - When the controller does a "GETINFO network-status", tell it
11988 about even those routers whose descriptors are very old, and use
11989 long nicknames where appropriate.
11990 - Change NT service functions to be loaded on demand. This lets us
11991 build with MinGW without breaking Tor for Windows 98 users.
11992 - Do DirPort reachability tests less often, since a single test
11993 chews through many circuits before giving up.
11994 - In the hidden service example in torrc.sample, stop recommending
11995 esoteric and discouraged hidden service options.
11996 - When stopping an NT service, wait up to 10 sec for it to actually
11997 stop. Patch from Matt Edman; resolves bug 295.
11998 - Fix handling of verbose nicknames with ORCONN controller events:
11999 make them show up exactly when requested, rather than exactly when
12001 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
12002 printing a duplicate "$" in the keys we send (reported by mwenge).
12003 - Correctly set maximum connection limit on Cygwin. (This time
12005 - Try to detect Windows correctly when cross-compiling.
12006 - Detect the size of the routers file correctly even if it is
12007 corrupted (on systems without mmap) or not page-aligned (on systems
12008 with mmap). This bug was harmless.
12009 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
12010 to open a stream fails; now we do in more cases. This should
12011 make clients able to find a good exit faster in some cases, since
12012 unhandleable requests will now get an error rather than timing out.
12013 - Resolve two memory leaks when rebuilding the on-disk router cache
12014 (reported by fookoowa).
12015 - Clean up minor code warnings suggested by the MIPSpro C compiler,
12016 and reported by some Centos users.
12017 - Controller signals now work on non-Unix platforms that don't define
12018 SIGUSR1 and SIGUSR2 the way we expect.
12019 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
12020 values before failing, and always enables eventdns.
12021 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
12022 Try to fix this in configure.in by checking for most functions
12023 before we check for libevent.
12026 Changes in version 0.1.2.2-alpha - 2006-10-07
12028 - Make our async eventdns library on-by-default for Tor servers,
12029 and plan to deprecate the separate dnsworker threads.
12030 - Add server-side support for "reverse" DNS lookups (using PTR
12031 records so clients can determine the canonical hostname for a given
12032 IPv4 address). Only supported by servers using eventdns; servers
12033 now announce in their descriptors whether they support eventdns.
12034 - Specify and implement client-side SOCKS5 interface for reverse DNS
12035 lookups (see doc/socks-extensions.txt).
12036 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
12037 connect to directory servers through Tor. Previously, clients needed
12038 to find Tor exits to make private connections to directory servers.
12039 - Avoid choosing Exit nodes for entry or middle hops when the
12040 total bandwidth available from non-Exit nodes is much higher than
12041 the total bandwidth available from Exit nodes.
12042 - Workaround for name servers (like Earthlink's) that hijack failing
12043 DNS requests and replace the no-such-server answer with a "helpful"
12044 redirect to an advertising-driven search portal. Also work around
12045 DNS hijackers who "helpfully" decline to hijack known-invalid
12046 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
12047 lets you turn it off.
12048 - Send out a burst of long-range padding cells once we've established
12049 that we're reachable. Spread them over 4 circuits, so hopefully
12050 a few will be fast. This exercises our bandwidth and bootstraps
12051 us into the directory more quickly.
12053 o New/improved config options:
12054 - Add new config option "ResolvConf" to let the server operator
12055 choose an alternate resolve.conf file when using eventdns.
12056 - Add an "EnforceDistinctSubnets" option to control our "exclude
12057 servers on the same /16" behavior. It's still on by default; this
12058 is mostly for people who want to operate private test networks with
12059 all the machines on the same subnet.
12060 - If one of our entry guards is on the ExcludeNodes list, or the
12061 directory authorities don't think it's a good guard, treat it as
12062 if it were unlisted: stop using it as a guard, and throw it off
12063 the guards list if it stays that way for a long time.
12064 - Allow directory authorities to be marked separately as authorities
12065 for the v1 directory protocol, the v2 directory protocol, and
12066 as hidden service directories, to make it easier to retire old
12067 authorities. V1 authorities should set "HSAuthoritativeDir 1"
12068 to continue being hidden service authorities too.
12069 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
12071 o Minor features, controller:
12072 - Fix CIRC controller events so that controllers can learn the
12073 identity digests of non-Named servers used in circuit paths.
12074 - Let controllers ask for more useful identifiers for servers. Instead
12075 of learning identity digests for un-Named servers and nicknames
12076 for Named servers, the new identifiers include digest, nickname,
12077 and indication of Named status. Off by default; see control-spec.txt
12078 for more information.
12079 - Add a "getinfo address" controller command so it can display Tor's
12080 best guess to the user.
12081 - New controller event to alert the controller when our server
12082 descriptor has changed.
12083 - Give more meaningful errors on controller authentication failure.
12085 o Minor features, other:
12086 - When asked to resolve a hostname, don't use non-exit servers unless
12087 requested to do so. This allows servers with broken DNS to be
12088 useful to the network.
12089 - Divide eventdns log messages into warn and info messages.
12090 - Reserve the nickname "Unnamed" for routers that can't pick
12091 a hostname: any router can call itself Unnamed; directory
12092 authorities will never allocate Unnamed to any particular router;
12093 clients won't believe that any router is the canonical Unnamed.
12094 - Only include function names in log messages for info/debug messages.
12095 For notice/warn/err, the content of the message should be clear on
12096 its own, and printing the function name only confuses users.
12097 - Avoid some false positives during reachability testing: don't try
12098 to test via a server that's on the same /24 as us.
12099 - If we fail to build a circuit to an intended enclave, and it's
12100 not mandatory that we use that enclave, stop wanting it.
12101 - When eventdns is enabled, allow multithreaded builds on NetBSD and
12102 OpenBSD. (We had previously disabled threads on these platforms
12103 because they didn't have working thread-safe resolver functions.)
12105 o Major bugfixes, anonymity/security:
12106 - If a client asked for a server by name, and there's a named server
12107 in our network-status but we don't have its descriptor yet, we
12108 could return an unnamed server instead.
12109 - Fix NetBSD bug that could allow someone to force uninitialized RAM
12110 to be sent to a server's DNS resolver. This only affects NetBSD
12111 and other platforms that do not bounds-check tolower().
12112 - Reject (most) attempts to use Tor circuits with length one. (If
12113 many people start using Tor as a one-hop proxy, exit nodes become
12114 a more attractive target for compromise.)
12115 - Just because your DirPort is open doesn't mean people should be
12116 able to remotely teach you about hidden service descriptors. Now
12117 only accept rendezvous posts if you've got HSAuthoritativeDir set.
12119 o Major bugfixes, other:
12120 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
12121 - When a client asks the server to resolve (not connect to)
12122 an address, and it has a cached answer, give them the cached answer.
12123 Previously, the server would give them no answer at all.
12124 - Allow really slow clients to not hang up five minutes into their
12125 directory downloads (suggested by Adam J. Richter).
12126 - We were building exactly the wrong circuits when we anticipated
12127 hidden service requirements, meaning Tor would have to build all
12128 its circuits on demand.
12129 - Avoid crashing when we mmap a router cache file of size 0.
12130 - When testing reachability of our DirPort, don't launch new
12131 tests when there's already one in progress -- unreachable
12132 servers were stacking up dozens of testing streams.
12134 o Minor bugfixes, correctness:
12135 - If we're a directory mirror and we ask for "all" network status
12136 documents, we would discard status documents from authorities
12137 we don't recognize.
12138 - Avoid a memory corruption bug when creating a hash table for
12140 - Avoid controller-triggered crash when misusing certain commands
12141 from a v0 controller on platforms that do not handle
12142 printf("%s",NULL) gracefully.
12143 - Don't crash when a controller sends a third argument to an
12144 "extendcircuit" request.
12145 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12146 response; fix error code when "getinfo dir/status/" fails.
12147 - Avoid crash when telling controller stream-status and a stream
12149 - Patch from Adam Langley to fix assert() in eventdns.c.
12150 - Fix a debug log message in eventdns to say "X resolved to Y"
12151 instead of "X resolved to X".
12152 - Make eventdns give strings for DNS errors, not just error numbers.
12153 - Track unreachable entry guards correctly: don't conflate
12154 'unreachable by us right now' with 'listed as down by the directory
12155 authorities'. With the old code, if a guard was unreachable by
12156 us but listed as running, it would clog our guard list forever.
12157 - Behave correctly in case we ever have a network with more than
12158 2GB/s total advertised capacity.
12159 - Make TrackExitHosts case-insensitive, and fix the behavior of
12160 ".suffix" TrackExitHosts items to avoid matching in the middle of
12162 - Finally fix the openssl warnings from newer gccs that believe that
12163 ignoring a return value is okay, but casting a return value and
12164 then ignoring it is a sign of madness.
12165 - Prevent the contrib/exitlist script from printing the same
12166 result more than once.
12167 - Patch from Steve Hildrey: Generate network status correctly on
12168 non-versioning dirservers.
12169 - Don't listen to the X-Your-Address-Is hint if you did the lookup
12170 via Tor; otherwise you'll think you're the exit node's IP address.
12172 o Minor bugfixes, performance:
12173 - Two small performance improvements on parsing descriptors.
12174 - Major performance improvement on inserting descriptors: change
12175 algorithm from O(n^2) to O(n).
12176 - Make the common memory allocation path faster on machines where
12177 malloc(0) returns a pointer.
12178 - Start remembering X-Your-Address-Is directory hints even if you're
12179 a client, so you can become a server more smoothly.
12180 - Avoid duplicate entries on MyFamily line in server descriptor.
12182 o Packaging, features:
12183 - Remove architecture from OS X builds. The official builds are
12184 now universal binaries.
12185 - The Debian package now uses --verify-config when (re)starting,
12186 to distinguish configuration errors from other errors.
12187 - Update RPMs to require libevent 1.1b.
12189 o Packaging, bugfixes:
12190 - Patches so Tor builds with MinGW on Windows.
12191 - Patches so Tor might run on Cygwin again.
12192 - Resume building on non-gcc compilers and ancient gcc. Resume
12193 building with the -O0 compile flag. Resume building cleanly on
12195 - Run correctly on OS X platforms with case-sensitive filesystems.
12196 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
12197 - Add autoconf checks so Tor can build on Solaris x86 again.
12200 - Documented (and renamed) ServerDNSSearchDomains and
12201 ServerDNSResolvConfFile options.
12202 - Be clearer that the *ListenAddress directives can be repeated
12206 Changes in version 0.1.1.24 - 2006-09-29
12208 - Allow really slow clients to not hang up five minutes into their
12209 directory downloads (suggested by Adam J. Richter).
12210 - Fix major performance regression from 0.1.0.x: instead of checking
12211 whether we have enough directory information every time we want to
12212 do something, only check when the directory information has changed.
12213 This should improve client CPU usage by 25-50%.
12214 - Don't crash if, after a server has been running for a while,
12215 it can't resolve its hostname.
12218 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12219 - Don't crash when the controller receives a third argument to an
12220 "extendcircuit" request.
12221 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12222 response; fix error code when "getinfo dir/status/" fails.
12223 - Fix configure.in to not produce broken configure files with
12224 more recent versions of autoconf. Thanks to Clint for his auto*
12226 - Fix security bug on NetBSD that could allow someone to force
12227 uninitialized RAM to be sent to a server's DNS resolver. This
12228 only affects NetBSD and other platforms that do not bounds-check
12230 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
12231 methods: these are known to be buggy.
12232 - If we're a directory mirror and we ask for "all" network status
12233 documents, we would discard status documents from authorities
12234 we don't recognize.
12237 Changes in version 0.1.2.1-alpha - 2006-08-27
12239 - Add "eventdns" async dns library from Adam Langley, tweaked to
12240 build on OSX and Windows. Only enabled if you pass the
12241 --enable-eventdns argument to configure.
12242 - Allow servers with no hostname or IP address to learn their
12243 IP address by asking the directory authorities. This code only
12244 kicks in when you would normally have exited with a "no address"
12245 error. Nothing's authenticated, so use with care.
12246 - Rather than waiting a fixed amount of time between retrying
12247 application connections, we wait only 5 seconds for the first,
12248 10 seconds for the second, and 15 seconds for each retry after
12249 that. Hopefully this will improve the expected user experience.
12250 - Patch from Tup to add support for transparent AP connections:
12251 this basically bundles the functionality of trans-proxy-tor
12252 into the Tor mainline. Now hosts with compliant pf/netfilter
12253 implementations can redirect TCP connections straight to Tor
12254 without diverting through SOCKS. Needs docs.
12255 - Busy directory servers save lots of memory by spooling server
12256 descriptors, v1 directories, and v2 networkstatus docs to buffers
12257 as needed rather than en masse. Also mmap the cached-routers
12258 files, so we don't need to keep the whole thing in memory too.
12259 - Automatically avoid picking more than one node from the same
12260 /16 network when constructing a circuit.
12261 - Revise and clean up the torrc.sample that we ship with; add
12262 a section for BandwidthRate and BandwidthBurst.
12265 - Split circuit_t into origin_circuit_t and or_circuit_t, and
12266 split connection_t into edge, or, dir, control, and base structs.
12267 These will save quite a bit of memory on busy servers, and they'll
12268 also help us track down bugs in the code and bugs in the spec.
12269 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
12270 or later. Log when we are doing this, so we can diagnose it when
12271 it fails. (Also, recommend libevent 1.1b for kqueue and
12272 win32 methods; deprecate libevent 1.0b harder; make libevent
12273 recommendation system saner.)
12274 - Start being able to build universal binaries on OS X (thanks
12276 - Export the default exit policy via the control port, so controllers
12277 don't need to guess what it is / will be later.
12278 - Add a man page entry for ProtocolWarnings.
12279 - Add TestVia config option to the man page.
12280 - Remove even more protocol-related warnings from Tor server logs,
12281 such as bad TLS handshakes and malformed begin cells.
12282 - Stop fetching descriptors if you're not a dir mirror and you
12283 haven't tried to establish any circuits lately. [This currently
12284 causes some dangerous behavior, because when you start up again
12285 you'll use your ancient server descriptors.]
12286 - New DirPort behavior: if you have your dirport set, you download
12287 descriptors aggressively like a directory mirror, whether or not
12288 your ORPort is set.
12289 - Get rid of the router_retry_connections notion. Now routers
12290 no longer try to rebuild long-term connections to directory
12291 authorities, and directory authorities no longer try to rebuild
12292 long-term connections to all servers. We still don't hang up
12293 connections in these two cases though -- we need to look at it
12294 more carefully to avoid flapping, and we likely need to wait til
12295 0.1.1.x is obsolete.
12296 - Drop compatibility with obsolete Tors that permit create cells
12297 to have the wrong circ_id_type.
12298 - Re-enable per-connection rate limiting. Get rid of the "OP
12299 bandwidth" concept. Lay groundwork for "bandwidth classes" --
12300 separate global buckets that apply depending on what sort of conn
12302 - Start publishing one minute or so after we find our ORPort
12303 to be reachable. This will help reduce the number of descriptors
12304 we have for ourselves floating around, since it's quite likely
12305 other things (e.g. DirPort) will change during that minute too.
12306 - Fork the v1 directory protocol into its own spec document,
12307 and mark dir-spec.txt as the currently correct (v2) spec.
12310 - When we find our DirPort to be reachable, publish a new descriptor
12311 so we'll tell the world (reported by pnx).
12312 - Publish a new descriptor after we hup/reload. This is important
12313 if our config has changed such that we'll want to start advertising
12314 our DirPort now, etc.
12315 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12316 - When we have a state file we cannot parse, tell the user and
12317 move it aside. Now we avoid situations where the user starts
12318 Tor in 1904, Tor writes a state file with that timestamp in it,
12319 the user fixes her clock, and Tor refuses to start.
12320 - Fix configure.in to not produce broken configure files with
12321 more recent versions of autoconf. Thanks to Clint for his auto*
12323 - "tor --verify-config" now exits with -1(255) or 0 depending on
12324 whether the config options are bad or good.
12325 - Resolve bug 321 when using dnsworkers: append a period to every
12326 address we resolve at the exit node, so that we do not accidentally
12327 pick up local addresses, and so that failing searches are retried
12328 in the resolver search domains. (This is already solved for
12329 eventdns.) (This breaks Blossom servers for now.)
12330 - If we are using an exit enclave and we can't connect, e.g. because
12331 its webserver is misconfigured to not listen on localhost, then
12332 back off and try connecting from somewhere else before we fail.
12335 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
12336 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
12337 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
12338 when the IP address is mapped through MapAddress to a hostname.
12339 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
12340 useless IPv6 DNS resolves.
12341 - Patch suggested by Karsten Loesing: respond to SIGNAL command
12342 before we execute the signal, in case the signal shuts us down.
12343 - Clean up AllowInvalidNodes man page entry.
12344 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
12345 - Add more asserts to track down an assert error on a windows Tor
12346 server with connection_add being called with socket == -1.
12347 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
12348 - Fix misleading log messages: an entry guard that is "unlisted",
12349 as well as not known to be "down" (because we've never heard
12350 of it), is not therefore "up".
12351 - Remove code to special-case "-cvs" ending, since it has not
12352 actually mattered since 0.0.9.
12353 - Make our socks5 handling more robust to broken socks clients:
12354 throw out everything waiting on the buffer in between socks
12355 handshake phases, since they can't possibly (so the theory
12356 goes) have predicted what we plan to respond to them.
12359 Changes in version 0.1.1.23 - 2006-07-30
12361 - Fast Tor servers, especially exit nodes, were triggering asserts
12362 due to a bug in handling the list of pending DNS resolves. Some
12363 bugs still remain here; we're hunting them.
12364 - Entry guards could crash clients by sending unexpected input.
12365 - More fixes on reachability testing: if you find yourself reachable,
12366 then don't ever make any client requests (so you stop predicting
12367 circuits), then hup or have your clock jump, then later your IP
12368 changes, you won't think circuits are working, so you won't try to
12369 test reachability, so you won't publish.
12372 - Avoid a crash if the controller does a resetconf firewallports
12373 and then a setconf fascistfirewall=1.
12374 - Avoid an integer underflow when the dir authority decides whether
12375 a router is stable: we might wrongly label it stable, and compute
12376 a slightly wrong median stability, when a descriptor is published
12378 - Fix a place where we might trigger an assert if we can't build our
12379 own server descriptor yet.
12382 Changes in version 0.1.1.22 - 2006-07-05
12384 - Fix a big bug that was causing servers to not find themselves
12385 reachable if they changed IP addresses. Since only 0.1.1.22+
12386 servers can do reachability testing correctly, now we automatically
12387 make sure to test via one of these.
12388 - Fix to allow clients and mirrors to learn directory info from
12389 descriptor downloads that get cut off partway through.
12390 - Directory authorities had a bug in deciding if a newly published
12391 descriptor was novel enough to make everybody want a copy -- a few
12392 servers seem to be publishing new descriptors many times a minute.
12394 - Fix a rare bug that was causing some servers to complain about
12395 "closing wedged cpuworkers" and skip some circuit create requests.
12396 - Make the Exit flag in directory status documents actually work.
12399 Changes in version 0.1.1.21 - 2006-06-10
12400 o Crash and assert fixes from 0.1.1.20:
12401 - Fix a rare crash on Tor servers that have enabled hibernation.
12402 - Fix a seg fault on startup for Tor networks that use only one
12403 directory authority.
12404 - Fix an assert from a race condition that occurs on Tor servers
12405 while exiting, where various threads are trying to log that they're
12406 exiting, and delete the logs, at the same time.
12407 - Make our unit tests pass again on certain obscure platforms.
12410 - Add support for building SUSE RPM packages.
12411 - Speed up initial bootstrapping for clients: if we are making our
12412 first ever connection to any entry guard, then don't mark it down
12414 - When only one Tor server in the network is labelled as a guard,
12415 and we've already picked him, we would cycle endlessly picking him
12416 again, being unhappy about it, etc. Now we specifically exclude
12417 current guards when picking a new guard.
12418 - Servers send create cells more reliably after the TLS connection
12419 is established: we were sometimes forgetting to send half of them
12420 when we had more than one pending.
12421 - If we get a create cell that asks us to extend somewhere, but the
12422 Tor server there doesn't match the expected digest, we now send
12423 a destroy cell back, rather than silently doing nothing.
12424 - Make options->RedirectExit work again.
12425 - Make cookie authentication for the controller work again.
12426 - Stop being picky about unusual characters in the arguments to
12427 mapaddress. It's none of our business.
12428 - Add a new config option "TestVia" that lets you specify preferred
12429 middle hops to use for test circuits. Perhaps this will let me
12430 debug the reachability problems better.
12432 o Log / documentation fixes:
12433 - If we're a server and some peer has a broken TLS certificate, don't
12434 log about it unless ProtocolWarnings is set, i.e., we want to hear
12435 about protocol violations by others.
12436 - Fix spelling of VirtualAddrNetwork in man page.
12437 - Add a better explanation at the top of the autogenerated torrc file
12438 about what happened to our old torrc.
12441 Changes in version 0.1.1.20 - 2006-05-23
12443 - Downgrade a log severity where servers complain that they're
12445 - Avoid a compile warning on FreeBSD.
12446 - Remove string size limit on NEWDESC messages; solve bug 291.
12447 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
12448 more thoroughly when we're running on windows.
12451 Changes in version 0.1.1.19-rc - 2006-05-03
12453 - Regenerate our local descriptor if it's dirty and we try to use
12454 it locally (e.g. if it changes during reachability detection).
12455 - If we setconf our ORPort to 0, we continued to listen on the
12456 old ORPort and receive connections.
12457 - Avoid a second warning about machine/limits.h on Debian
12459 - Be willing to add our own routerinfo into the routerlist.
12460 Now authorities will include themselves in their directories
12461 and network-statuses.
12462 - Stop trying to upload rendezvous descriptors to every
12463 directory authority: only try the v1 authorities.
12464 - Servers no longer complain when they think they're not
12465 registered with the directory authorities. There were too many
12467 - Backport dist-rpm changes so rpms can be built without errors.
12470 - Implement an option, VirtualAddrMask, to set which addresses
12471 get handed out in response to mapaddress requests. This works
12472 around a bug in tsocks where 127.0.0.0/8 is never socksified.
12475 Changes in version 0.1.1.18-rc - 2006-04-10
12477 - Work harder to download live network-statuses from all the
12478 directory authorities we know about. Improve the threshold
12479 decision logic so we're more robust to edge cases.
12480 - When fetching rendezvous descriptors, we were willing to ask
12481 v2 authorities too, which would always return 404.
12484 - Stop listing down or invalid nodes in the v1 directory. This will
12485 reduce its bulk by about 1/3, and reduce load on directory
12487 - When deciding whether a router is Fast or Guard-worthy, consider
12488 his advertised BandwidthRate and not just the BandwidthCapacity.
12489 - No longer ship INSTALL and README files -- they are useless now.
12490 - Force rpmbuild to behave and honor target_cpu.
12491 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
12492 - Start to include translated versions of the tor-doc-*.html
12493 files, along with the screenshots. Still needs more work.
12494 - Start sending back 512 and 451 errors if mapaddress fails,
12495 rather than not sending anything back at all.
12496 - When we fail to bind or listen on an incoming or outgoing
12497 socket, we should close it before failing. otherwise we just
12498 leak it. (thanks to weasel for finding.)
12499 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
12500 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
12501 - Make NoPublish (even though deprecated) work again.
12502 - Fix a minor security flaw where a versioning auth dirserver
12503 could list a recommended version many times in a row to make
12504 clients more convinced that it's recommended.
12505 - Fix crash bug if there are two unregistered servers running
12506 with the same nickname, one of them is down, and you ask for
12507 them by nickname in your EntryNodes or ExitNodes. Also, try
12508 to pick the one that's running rather than an arbitrary one.
12509 - Fix an infinite loop we could hit if we go offline for too long.
12510 - Complain when we hit WSAENOBUFS on recv() or write() too.
12511 Perhaps this will help us hunt the bug.
12512 - If you're not a versioning dirserver, don't put the string
12513 "client-versions \nserver-versions \n" in your network-status.
12514 - Lower the minimum required number of file descriptors to 1000,
12515 so we can have some overhead for Valgrind on Linux, where the
12516 default ulimit -n is 1024.
12519 - Add tor.dizum.com as the fifth authoritative directory server.
12520 - Add a new config option FetchUselessDescriptors, off by default,
12521 for when you plan to run "exitlist" on your client and you want
12522 to know about even the non-running descriptors.
12525 Changes in version 0.1.1.17-rc - 2006-03-28
12527 - Clients and servers since 0.1.1.10-alpha have been expiring
12528 connections whenever they are idle for 5 minutes and they *do*
12529 have circuits on them. Oops. With this new version, clients will
12530 discard their previous entry guard choices and avoid choosing
12531 entry guards running these flawed versions.
12532 - Fix memory leak when uncompressing concatenated zlib streams. This
12533 was causing substantial leaks over time on Tor servers.
12534 - The v1 directory was including servers as much as 48 hours old,
12535 because that's how the new routerlist->routers works. Now only
12536 include them if they're 20 hours old or less.
12539 - Resume building on irix64, netbsd 2.0, etc.
12540 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
12542 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
12543 and it is confusing some users.
12544 - Mirrors stop caching the v1 directory so often.
12545 - Make the max number of old descriptors that a cache will hold
12546 rise with the number of directory authorities, so we can scale.
12547 - Change our win32 uname() hack to be more forgiving about what
12548 win32 versions it thinks it's found.
12551 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
12553 - When the controller's *setconf commands fail, collect an error
12554 message in a string and hand it back to the controller.
12555 - Make the v2 dir's "Fast" flag based on relative capacity, just
12556 like "Stable" is based on median uptime. Name everything in the
12557 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
12558 - Log server fingerprint on startup, so new server operators don't
12559 have to go hunting around their filesystem for it.
12560 - Return a robots.txt on our dirport to discourage google indexing.
12561 - Let the controller ask for GETINFO dir/status/foo so it can ask
12562 directly rather than connecting to the dir port. Only works when
12563 dirport is set for now.
12565 o New config options rather than constants in the code:
12566 - SocksTimeout: How long do we let a socks connection wait
12567 unattached before we fail it?
12568 - CircuitBuildTimeout: Cull non-open circuits that were born
12569 at least this many seconds ago.
12570 - CircuitIdleTimeout: Cull open clean circuits that were born
12571 at least this many seconds ago.
12574 Changes in version 0.1.1.16-rc - 2006-03-18
12575 o Bugfixes on 0.1.1.15-rc:
12576 - Fix assert when the controller asks to attachstream a connect-wait
12577 or resolve-wait stream.
12578 - Now do address rewriting when the controller asks us to attach
12579 to a particular circuit too. This will let Blossom specify
12580 "moria2.exit" without having to learn what moria2's IP address is.
12581 - Make the "tor --verify-config" command-line work again, so people
12582 can automatically check if their torrc will parse.
12583 - Authoritative dirservers no longer require an open connection from
12584 a server to consider him "reachable". We need this change because
12585 when we add new auth dirservers, old servers won't know not to
12587 - Let Tor build on Sun CC again.
12588 - Fix an off-by-one buffer size in dirserv.c that magically never
12589 hit our three authorities but broke sjmurdoch's own tor network.
12590 - If we as a directory mirror don't know of any v1 directory
12591 authorities, then don't try to cache any v1 directories.
12592 - Stop warning about unknown servers in our family when they are
12593 given as hex digests.
12594 - Stop complaining as quickly to the server operator that he
12595 hasn't registered his nickname/key binding.
12596 - Various cleanups so we can add new V2 Auth Dirservers.
12597 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
12598 reflect the updated flags in our v2 dir protocol.
12599 - Resume allowing non-printable characters for exit streams (both
12600 for connecting and for resolving). Now we tolerate applications
12601 that don't follow the RFCs. But continue to block malformed names
12604 o Bugfixes on 0.1.0.x:
12605 - Fix assert bug in close_logs(): when we close and delete logs,
12606 remove them all from the global "logfiles" list.
12607 - Fix minor integer overflow in calculating when we expect to use up
12608 our bandwidth allocation before hibernating.
12609 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
12610 there are multiple SSLs installed with different versions.
12611 - When we try to be a server and Address is not explicitly set and
12612 our hostname resolves to a private IP address, try to use an
12613 interface address if it has a public address. Now Windows machines
12614 that think of themselves as localhost can work by default.
12617 - Let the controller ask for GETINFO dir/server/foo so it can ask
12618 directly rather than connecting to the dir port.
12619 - Let the controller tell us about certain router descriptors
12620 that it doesn't want Tor to use in circuits. Implement
12621 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
12622 - New config option SafeSocks to reject all application connections
12623 using unsafe socks protocols. Defaults to off.
12626 Changes in version 0.1.1.15-rc - 2006-03-11
12627 o Bugfixes and cleanups:
12628 - When we're printing strings from the network, don't try to print
12629 non-printable characters. This protects us against shell escape
12630 sequence exploits, and also against attacks to fool humans into
12631 misreading their logs.
12632 - Fix a bug where Tor would fail to establish any connections if you
12633 left it off for 24 hours and then started it: we were happy with
12634 the obsolete network statuses, but they all referred to router
12635 descriptors that were too old to fetch, so we ended up with no
12636 valid router descriptors.
12637 - Fix a seg fault in the controller's "getinfo orconn-status"
12638 command while listing status on incoming handshaking connections.
12639 Introduce a status name "NEW" for these connections.
12640 - If we get a linelist or linelist_s config option from the torrc
12641 (e.g. ExitPolicy) and it has no value, warn and skip rather than
12642 silently resetting it to its default.
12643 - Don't abandon entry guards until they've been down or gone for
12645 - Cleaner and quieter log messages.
12648 - New controller signal NEWNYM that makes new application requests
12649 use clean circuits.
12650 - Add a new circuit purpose 'controller' to let the controller ask
12651 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
12652 controller command to let you specify the purpose if you're
12653 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
12654 command to let you change a circuit's purpose after it's been
12656 - Accept "private:*" in routerdesc exit policies; not generated yet
12657 because older Tors do not understand it.
12658 - Add BSD-style contributed startup script "rc.subr" from Peter
12662 Changes in version 0.1.1.14-alpha - 2006-02-20
12663 o Bugfixes on 0.1.1.x:
12664 - Don't die if we ask for a stdout or stderr log (even implicitly)
12665 and we're set to RunAsDaemon -- just warn.
12666 - We still had a few bugs in the OR connection rotation code that
12667 caused directory servers to slowly aggregate connections to other
12668 fast Tor servers. This time for sure!
12669 - Make log entries on Win32 include the name of the function again.
12670 - We were treating a pair of exit policies if they were equal even
12671 if one said accept and the other said reject -- causing us to
12672 not always publish a new descriptor since we thought nothing
12674 - Retry pending server downloads as well as pending networkstatus
12675 downloads when we unexpectedly get a socks request.
12676 - We were ignoring the IS_FAST flag in the directory status,
12677 meaning we were willing to pick trivial-bandwidth nodes for "fast"
12679 - If the controller's SAVECONF command fails (e.g. due to file
12680 permissions), let the controller know that it failed.
12683 - If we're trying to be a Tor server and running Windows 95/98/ME
12684 as a server, explain that we'll likely crash.
12685 - When we're a server, a client asks for an old-style directory,
12686 and our write bucket is empty, don't give it to him. This way
12687 small servers can continue to serve the directory *sometimes*,
12688 without getting overloaded.
12689 - Compress exit policies even more -- look for duplicate lines
12691 - Clients now honor the "guard" flag in the router status when
12692 picking entry guards, rather than looking at is_fast or is_stable.
12693 - Retain unrecognized lines in $DATADIR/state file, so that we can
12694 be forward-compatible.
12695 - Generate 18.0.0.0/8 address policy format in descs when we can;
12696 warn when the mask is not reducible to a bit-prefix.
12697 - Let the user set ControlListenAddress in the torrc. This can be
12698 dangerous, but there are some cases (like a secured LAN) where it
12700 - Split ReachableAddresses into ReachableDirAddresses and
12701 ReachableORAddresses, so we can restrict Dir conns to port 80
12702 and OR conns to port 443.
12703 - Now we can target arch and OS in rpm builds (contributed by
12704 Phobos). Also make the resulting dist-rpm filename match the
12706 - New config options to help controllers: FetchServerDescriptors
12707 and FetchHidServDescriptors for whether to fetch server
12708 info and hidserv info or let the controller do it, and
12709 PublishServerDescriptor and PublishHidServDescriptors.
12710 - Also let the controller set the __AllDirActionsPrivate config
12711 option if you want all directory fetches/publishes to happen via
12712 Tor (it assumes your controller bootstraps your circuits).
12715 Changes in version 0.1.0.17 - 2006-02-17
12716 o Crash bugfixes on 0.1.0.x:
12717 - When servers with a non-zero DirPort came out of hibernation,
12718 sometimes they would trigger an assert.
12720 o Other important bugfixes:
12721 - On platforms that don't have getrlimit (like Windows), we were
12722 artificially constraining ourselves to a max of 1024
12723 connections. Now just assume that we can handle as many as 15000
12724 connections. Hopefully this won't cause other problems.
12726 o Backported features:
12727 - When we're a server, a client asks for an old-style directory,
12728 and our write bucket is empty, don't give it to him. This way
12729 small servers can continue to serve the directory *sometimes*,
12730 without getting overloaded.
12731 - Whenever you get a 503 in response to a directory fetch, try
12732 once more. This will become important once servers start sending
12733 503's whenever they feel busy.
12734 - Fetch a new directory every 120 minutes, not every 40 minutes.
12735 Now that we have hundreds of thousands of users running the old
12736 directory algorithm, it's starting to hurt a lot.
12737 - Bump up the period for forcing a hidden service descriptor upload
12738 from 20 minutes to 1 hour.
12741 Changes in version 0.1.1.13-alpha - 2006-02-09
12742 o Crashes in 0.1.1.x:
12743 - When you tried to setconf ORPort via the controller, Tor would
12744 crash. So people using TorCP to become a server were sad.
12745 - Solve (I hope) the stack-smashing bug that we were seeing on fast
12746 servers. The problem appears to be something do with OpenSSL's
12747 random number generation, or how we call it, or something. Let me
12748 know if the crashes continue.
12749 - Turn crypto hardware acceleration off by default, until we find
12750 somebody smart who can test it for us. (It appears to produce
12751 seg faults in at least some cases.)
12752 - Fix a rare assert error when we've tried all intro points for
12753 a hidden service and we try fetching the service descriptor again:
12754 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
12757 - Fix a major load balance bug: we were round-robining in 16 KB
12758 chunks, and servers with bandwidthrate of 20 KB, while downloading
12759 a 600 KB directory, would starve their other connections. Now we
12760 try to be a bit more fair.
12761 - Dir authorities and mirrors were never expiring the newest
12762 descriptor for each server, causing memory and directory bloat.
12763 - Fix memory-bloating and connection-bloating bug on servers: We
12764 were never closing any connection that had ever had a circuit on
12765 it, because we were checking conn->n_circuits == 0, yet we had a
12766 bug that let it go negative.
12767 - Make Tor work using squid as your http proxy again -- squid
12768 returns an error if you ask for a URL that's too long, and it uses
12769 a really generic error message. Plus, many people are behind a
12770 transparent squid so they don't even realize it.
12771 - On platforms that don't have getrlimit (like Windows), we were
12772 artificially constraining ourselves to a max of 1024
12773 connections. Now just assume that we can handle as many as 15000
12774 connections. Hopefully this won't cause other problems.
12775 - Add a new config option ExitPolicyRejectPrivate which defaults to
12776 1. This means all exit policies will begin with rejecting private
12777 addresses, unless the server operator explicitly turns it off.
12780 - Clients no longer download descriptors for non-running
12782 - Before we add new directory authorities, we should make it
12783 clear that only v1 authorities should receive/publish hidden
12784 service descriptors.
12787 - As soon as we've fetched some more directory info, immediately
12788 try to download more server descriptors. This way we don't have
12789 a 10 second pause during initial bootstrapping.
12790 - Remove even more loud log messages that the server operator can't
12792 - When we're running an obsolete or un-recommended version, make
12793 the log message more clear about what the problem is and what
12794 versions *are* still recommended.
12795 - Provide a more useful warn message when our onion queue gets full:
12796 the CPU is too slow or the exit policy is too liberal.
12797 - Don't warn when we receive a 503 from a dirserver/cache -- this
12798 will pave the way for them being able to refuse if they're busy.
12799 - When we fail to bind a listener, try to provide a more useful
12800 log message: e.g., "Is Tor already running?"
12801 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
12802 Goldberg can prove things about our handshake protocol more
12804 - MaxConn has been obsolete for a while now. Document the ConnLimit
12805 config option, which is a *minimum* number of file descriptors
12806 that must be available else Tor refuses to start.
12807 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
12808 if you log to syslog and want something other than LOG_DAEMON.
12809 - Make dirservers generate a separate "guard" flag to mean,
12810 "would make a good entry guard". Make clients parse it and vote
12811 on it. Not used by clients yet.
12812 - Implement --with-libevent-dir option to ./configure. Also, improve
12813 search techniques to find libevent, and use those for openssl too.
12814 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
12815 - Only start testing reachability once we've established a
12816 circuit. This will make startup on dirservers less noisy.
12817 - Don't try to upload hidden service descriptors until we have
12818 established a circuit.
12819 - Fix the controller's "attachstream 0" command to treat conn like
12820 it just connected, doing address remapping, handling .exit and
12821 .onion idioms, and so on. Now we're more uniform in making sure
12822 that the controller hears about new and closing connections.
12825 Changes in version 0.1.1.12-alpha - 2006-01-11
12826 o Bugfixes on 0.1.1.x:
12827 - The fix to close duplicate server connections was closing all
12828 Tor client connections if they didn't establish a circuit
12829 quickly enough. Oops.
12830 - Fix minor memory issue (double-free) that happened on exit.
12832 o Bugfixes on 0.1.0.x:
12833 - Tor didn't warn when it failed to open a log file.
12836 Changes in version 0.1.1.11-alpha - 2006-01-10
12837 o Crashes in 0.1.1.x:
12838 - Include all the assert/crash fixes from 0.1.0.16.
12839 - If you start Tor and then quit very quickly, there were some
12840 races that tried to free things that weren't allocated yet.
12841 - Fix a rare memory stomp if you're running hidden services.
12842 - Fix segfault when specifying DirServer in config without nickname.
12843 - Fix a seg fault when you finish connecting to a server but at
12844 that moment you dump his server descriptor.
12845 - Extendcircuit and Attachstream controller commands would
12846 assert/crash if you don't give them enough arguments.
12847 - Fix an assert error when we're out of space in the connection_list
12848 and we try to post a hidden service descriptor (reported by weasel).
12849 - If you specify a relative torrc path and you set RunAsDaemon in
12850 your torrc, then it chdir()'s to the new directory. If you HUP,
12851 it tries to load the new torrc location, fails, and exits.
12852 The fix: no longer allow a relative path to torrc using -f.
12855 - Implement "entry guards": automatically choose a handful of entry
12856 nodes and stick with them for all circuits. Only pick new guards
12857 when the ones you have are unsuitable, and if the old guards
12858 become suitable again, switch back. This will increase security
12859 dramatically against certain end-point attacks. The EntryNodes
12860 config option now provides some hints about which entry guards you
12861 want to use most; and StrictEntryNodes means to only use those.
12862 - New directory logic: download by descriptor digest, not by
12863 fingerprint. Caches try to download all listed digests from
12864 authorities; clients try to download "best" digests from caches.
12865 This avoids partitioning and isolating attacks better.
12866 - Make the "stable" router flag in network-status be the median of
12867 the uptimes of running valid servers, and make clients pay
12868 attention to the network-status flags. Thus the cutoff adapts
12869 to the stability of the network as a whole, making IRC, IM, etc
12870 connections more reliable.
12873 - Tor servers with dynamic IP addresses were needing to wait 18
12874 hours before they could start doing reachability testing using
12875 the new IP address and ports. This is because they were using
12876 the internal descriptor to learn what to test, yet they were only
12877 rebuilding the descriptor once they decided they were reachable.
12878 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
12879 to download certain server descriptors, throw them away, and then
12880 fetch them again after 30 minutes. Now mirrors throw away these
12881 server descriptors so clients can't get them.
12882 - We were leaving duplicate connections to other ORs open for a week,
12883 rather than closing them once we detect a duplicate. This only
12884 really affected authdirservers, but it affected them a lot.
12885 - Spread the authdirservers' reachability testing over the entire
12886 testing interval, so we don't try to do 500 TLS's at once every
12890 - If the network is down, and we try to connect to a conn because
12891 we have a circuit in mind, and we timeout (30 seconds) because the
12892 network never answers, we were expiring the circuit, but we weren't
12893 obsoleting the connection or telling the entry_guards functions.
12894 - Some Tor servers process billions of cells per day. These statistics
12895 need to be uint64_t's.
12896 - Check for integer overflows in more places, when adding elements
12897 to smartlists. This could possibly prevent a buffer overflow
12898 on malicious huge inputs. I don't see any, but I haven't looked
12900 - ReachableAddresses kept growing new "reject *:*" lines on every
12902 - When you "setconf log" via the controller, it should remove all
12903 logs. We were automatically adding back in a "log notice stdout".
12904 - Newly bootstrapped Tor networks couldn't establish hidden service
12905 circuits until they had nodes with high uptime. Be more tolerant.
12906 - We were marking servers down when they could not answer every piece
12907 of the directory request we sent them. This was far too harsh.
12908 - Fix the torify (tsocks) config file to not use Tor for localhost
12910 - Directory authorities now go to the proper authority when asking for
12911 a networkstatus, even when they want a compressed one.
12912 - Fix a harmless bug that was causing Tor servers to log
12913 "Got an end because of misc error, but we're not an AP. Closing."
12914 - Authorities were treating their own descriptor changes as cosmetic,
12915 meaning the descriptor available in the network-status and the
12916 descriptor that clients downloaded were different.
12917 - The OS X installer was adding a symlink for tor_resolve but
12918 the binary was called tor-resolve (reported by Thomas Hardly).
12919 - Workaround a problem with some http proxies where they refuse GET
12920 requests that specify "Content-Length: 0" (reported by Adrian).
12921 - Fix wrong log message when you add a "HiddenServiceNodes" config
12922 line without any HiddenServiceDir line (reported by Chris Thomas).
12925 - Write the TorVersion into the state file so we have a prayer of
12926 keeping forward and backward compatibility.
12927 - Revive the FascistFirewall config option rather than eliminating it:
12928 now it's a synonym for ReachableAddresses *:80,*:443.
12929 - Clients choose directory servers from the network status lists,
12930 not from their internal list of router descriptors. Now they can
12931 go to caches directly rather than needing to go to authorities
12933 - Directory authorities ignore router descriptors that have only
12934 cosmetic differences: do this for 0.1.0.x servers now too.
12935 - Add a new flag to network-status indicating whether the server
12936 can answer v2 directory requests too.
12937 - Authdirs now stop whining so loudly about bad descriptors that
12938 they fetch from other dirservers. So when there's a log complaint,
12939 it's for sure from a freshly uploaded descriptor.
12940 - Reduce memory requirements in our structs by changing the order
12942 - There used to be two ways to specify your listening ports in a
12943 server descriptor: on the "router" line and with a separate "ports"
12944 line. Remove support for the "ports" line.
12945 - New config option "AuthDirRejectUnlisted" for auth dirservers as
12946 a panic button: if we get flooded with unusable servers we can
12947 revert to only listing servers in the approved-routers file.
12948 - Auth dir servers can now mark a fingerprint as "!reject" or
12949 "!invalid" in the approved-routers file (as its nickname), to
12950 refuse descriptors outright or include them but marked as invalid.
12951 - Servers store bandwidth history across restarts/crashes.
12952 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
12953 get a better idea of why their circuits failed. Not used yet.
12954 - Directory mirrors now cache up to 16 unrecognized network-status
12955 docs. Now we can add new authdirservers and they'll be cached too.
12956 - When picking a random directory, prefer non-authorities if any
12958 - New controller option "getinfo desc/all-recent" to fetch the
12959 latest server descriptor for every router that Tor knows about.
12962 Changes in version 0.1.0.16 - 2006-01-02
12963 o Crash bugfixes on 0.1.0.x:
12964 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
12965 corrupting the heap, losing FDs, or crashing when we need to resize
12966 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
12967 - It turns out sparc64 platforms crash on unaligned memory access
12968 too -- so detect and avoid this.
12969 - Handle truncated compressed data correctly (by detecting it and
12971 - Fix possible-but-unlikely free(NULL) in control.c.
12972 - When we were closing connections, there was a rare case that
12973 stomped on memory, triggering seg faults and asserts.
12974 - Avoid potential infinite recursion when building a descriptor. (We
12975 don't know that it ever happened, but better to fix it anyway.)
12976 - We were neglecting to unlink marked circuits from soon-to-close OR
12977 connections, which caused some rare scribbling on freed memory.
12978 - Fix a memory stomping race bug when closing the joining point of two
12979 rendezvous circuits.
12980 - Fix an assert in time parsing found by Steven Murdoch.
12982 o Other bugfixes on 0.1.0.x:
12983 - When we're doing reachability testing, provide more useful log
12984 messages so the operator knows what to expect.
12985 - Do not check whether DirPort is reachable when we are suppressing
12986 advertising it because of hibernation.
12987 - When building with -static or on Solaris, we sometimes needed -ldl.
12988 - When we're deciding whether a stream has enough circuits around
12989 that can handle it, count the freshly dirty ones and not the ones
12990 that are so dirty they won't be able to handle it.
12991 - When we're expiring old circuits, we had a logic error that caused
12992 us to close new rendezvous circuits rather than old ones.
12993 - Give a more helpful log message when you try to change ORPort via
12994 the controller: you should upgrade Tor if you want that to work.
12995 - We were failing to parse Tor versions that start with "Tor ".
12996 - Tolerate faulty streams better: when a stream fails for reason
12997 exitpolicy, stop assuming that the router is lying about his exit
12998 policy. When a stream fails for reason misc, allow it to retry just
12999 as if it was resolvefailed. When a stream has failed three times,
13000 reset its failure count so we can try again and get all three tries.
13003 Changes in version 0.1.1.10-alpha - 2005-12-11
13004 o Correctness bugfixes on 0.1.0.x:
13005 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
13006 corrupting the heap, losing FDs, or crashing when we need to resize
13007 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
13008 - Stop doing the complex voodoo overkill checking for insecure
13009 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
13010 - When we were closing connections, there was a rare case that
13011 stomped on memory, triggering seg faults and asserts.
13012 - We were neglecting to unlink marked circuits from soon-to-close OR
13013 connections, which caused some rare scribbling on freed memory.
13014 - When we're deciding whether a stream has enough circuits around
13015 that can handle it, count the freshly dirty ones and not the ones
13016 that are so dirty they won't be able to handle it.
13017 - Recover better from TCP connections to Tor servers that are
13018 broken but don't tell you (it happens!); and rotate TLS
13019 connections once a week.
13020 - When we're expiring old circuits, we had a logic error that caused
13021 us to close new rendezvous circuits rather than old ones.
13022 - Fix a scary-looking but apparently harmless bug where circuits
13023 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
13024 servers, and never switch to state CIRCUIT_STATE_OPEN.
13025 - When building with -static or on Solaris, we sometimes needed to
13027 - Give a useful message when people run Tor as the wrong user,
13028 rather than telling them to start chowning random directories.
13029 - We were failing to inform the controller about new .onion streams.
13031 o Security bugfixes on 0.1.0.x:
13032 - Refuse server descriptors if the fingerprint line doesn't match
13033 the included identity key. Tor doesn't care, but other apps (and
13034 humans) might actually be trusting the fingerprint line.
13035 - We used to kill the circuit when we receive a relay command we
13036 don't recognize. Now we just drop it.
13037 - Start obeying our firewall options more rigorously:
13038 . If we can't get to a dirserver directly, try going via Tor.
13039 . Don't ever try to connect (as a client) to a place our
13040 firewall options forbid.
13041 . If we specify a proxy and also firewall options, obey the
13042 firewall options even when we're using the proxy: some proxies
13043 can only proxy to certain destinations.
13044 - Fix a bug found by Lasse Overlier: when we were making internal
13045 circuits (intended to be cannibalized later for rendezvous and
13046 introduction circuits), we were picking them so that they had
13047 useful exit nodes. There was no need for this, and it actually
13048 aids some statistical attacks.
13049 - Start treating internal circuits and exit circuits separately.
13050 It's important to keep them separate because internal circuits
13051 have their last hops picked like middle hops, rather than like
13052 exit hops. So exiting on them will break the user's expectations.
13054 o Bugfixes on 0.1.1.x:
13055 - Take out the mis-feature where we tried to detect IP address
13056 flapping for people with DynDNS, and chose not to upload a new
13057 server descriptor sometimes.
13058 - Try to be compatible with OpenSSL 0.9.6 again.
13059 - Log fix: when the controller is logging about .onion addresses,
13060 sometimes it didn't include the ".onion" part of the address.
13061 - Don't try to modify options->DirServers internally -- if the
13062 user didn't specify any, just add the default ones directly to
13063 the trusted dirserver list. This fixes a bug where people running
13064 controllers would use SETCONF on some totally unrelated config
13065 option, and Tor would start yelling at them about changing their
13067 - Let the controller's redirectstream command specify a port, in
13068 case the controller wants to change that too.
13069 - When we requested a pile of server descriptors, we sometimes
13070 accidentally launched a duplicate request for the first one.
13071 - Bugfix for trackhostexits: write down the fingerprint of the
13072 chosen exit, not its nickname, because the chosen exit might not
13074 - When parsing foo.exit, if foo is unknown, and we are leaving
13075 circuits unattached, set the chosen_exit field and leave the
13076 address empty. This matters because controllers got confused
13078 - Directory authorities no longer try to download server
13079 descriptors that they know they will reject.
13081 o Features and updates:
13082 - Replace balanced trees with hash tables: this should make stuff
13083 significantly faster.
13084 - Resume using the AES counter-mode implementation that we ship,
13085 rather than OpenSSL's. Ours is significantly faster.
13086 - Many other CPU and memory improvements.
13087 - Add a new config option FastFirstHopPK (on by default) so clients
13088 do a trivial crypto handshake for their first hop, since TLS has
13089 already taken care of confidentiality and authentication.
13090 - Add a new config option TestSocks so people can see if their
13091 applications are using socks4, socks4a, socks5-with-ip, or
13092 socks5-with-hostname. This way they don't have to keep mucking
13093 with tcpdump and wondering if something got cached somewhere.
13094 - Warn when listening on a public address for socks. I suspect a
13095 lot of people are setting themselves up as open socks proxies,
13096 and they have no idea that jerks on the Internet are using them,
13097 since they simply proxy the traffic into the Tor network.
13098 - Add "private:*" as an alias in configuration for policies. Now
13099 you can simplify your exit policy rather than needing to list
13100 every single internal or nonroutable network space.
13101 - Add a new controller event type that allows controllers to get
13102 all server descriptors that were uploaded to a router in its role
13103 as authoritative dirserver.
13104 - Start shipping socks-extensions.txt, tor-doc-unix.html,
13105 tor-doc-server.html, and stylesheet.css in the tarball.
13106 - Stop shipping tor-doc.html in the tarball.
13109 Changes in version 0.1.1.9-alpha - 2005-11-15
13110 o Usability improvements:
13111 - Start calling it FooListenAddress rather than FooBindAddress,
13112 since few of our users know what it means to bind an address
13114 - Reduce clutter in server logs. We're going to try to make
13115 them actually usable now. New config option ProtocolWarnings that
13116 lets you hear about how _other Tors_ are breaking the protocol. Off
13118 - Divide log messages into logging domains. Once we put some sort
13119 of interface on this, it will let people looking at more verbose
13120 log levels specify the topics they want to hear more about.
13121 - Make directory servers return better http 404 error messages
13122 instead of a generic "Servers unavailable".
13123 - Check for even more Windows version flags when writing the platform
13124 string in server descriptors, and note any we don't recognize.
13125 - Clean up more of the OpenSSL memory when exiting, so we can detect
13126 memory leaks better.
13127 - Make directory authorities be non-versioning, non-naming by
13128 default. Now we can add new directory servers without requiring
13129 their operators to pay close attention.
13130 - When logging via syslog, include the pid whenever we provide
13131 a log entry. Suggested by Todd Fries.
13133 o Performance improvements:
13134 - Directory servers now silently throw away new descriptors that
13135 haven't changed much if the timestamps are similar. We do this to
13136 tolerate older Tor servers that upload a new descriptor every 15
13137 minutes. (It seemed like a good idea at the time.)
13138 - Inline bottleneck smartlist functions; use fast versions by default.
13139 - Add a "Map from digest to void*" abstraction digestmap_t so we
13140 can do less hex encoding/decoding. Use it in router_get_by_digest()
13141 to resolve a performance bottleneck.
13142 - Allow tor_gzip_uncompress to extract as much as possible from
13143 truncated compressed data. Try to extract as many
13144 descriptors as possible from truncated http responses (when
13145 DIR_PURPOSE_FETCH_ROUTERDESC).
13146 - Make circ->onionskin a pointer, not a static array. moria2 was using
13147 125000 circuit_t's after it had been up for a few weeks, which
13148 translates to 20+ megs of wasted space.
13149 - The private half of our EDH handshake keys are now chosen out
13150 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
13152 o Security improvements:
13153 - Start making directory caches retain old routerinfos, so soon
13154 clients can start asking by digest of descriptor rather than by
13155 fingerprint of server.
13156 - Add half our entropy from RAND_poll in OpenSSL. This knows how
13157 to use egd (if present), openbsd weirdness (if present), vms/os2
13158 weirdness (if we ever port there), and more in the future.
13160 o Bugfixes on 0.1.0.x:
13161 - Do round-robin writes of at most 16 kB per write. This might be
13162 more fair on loaded Tor servers, and it might resolve our Windows
13163 crash bug. It might also slow things down.
13164 - Our TLS handshakes were generating a single public/private
13165 keypair for the TLS context, rather than making a new one for
13166 each new connections. Oops. (But we were still rotating them
13167 periodically, so it's not so bad.)
13168 - When we were cannibalizing a circuit with a particular exit
13169 node in mind, we weren't checking to see if that exit node was
13170 already present earlier in the circuit. Oops.
13171 - When a Tor server's IP changes (e.g. from a dyndns address),
13172 upload a new descriptor so clients will learn too.
13173 - Really busy servers were keeping enough circuits open on stable
13174 connections that they were wrapping around the circuit_id
13175 space. (It's only two bytes.) This exposed a bug where we would
13176 feel free to reuse a circuit_id even if it still exists but has
13177 been marked for close. Try to fix this bug. Some bug remains.
13178 - If we would close a stream early (e.g. it asks for a .exit that
13179 we know would refuse it) but the LeaveStreamsUnattached config
13180 option is set by the controller, then don't close it.
13182 o Bugfixes on 0.1.1.8-alpha:
13183 - Fix a big pile of memory leaks, some of them serious.
13184 - Do not try to download a routerdesc if we would immediately reject
13186 - Resume inserting a newline between all router descriptors when
13187 generating (old style) signed directories, since our spec says
13189 - When providing content-type application/octet-stream for
13190 server descriptors using .z, we were leaving out the
13191 content-encoding header. Oops. (Everything tolerated this just
13192 fine, but that doesn't mean we need to be part of the problem.)
13193 - Fix a potential seg fault in getconf and getinfo using version 1
13194 of the controller protocol.
13195 - Avoid crash: do not check whether DirPort is reachable when we
13196 are suppressing it because of hibernation.
13197 - Make --hash-password not crash on exit.
13200 Changes in version 0.1.1.8-alpha - 2005-10-07
13201 o New features (major):
13202 - Clients don't download or use the directory anymore. Now they
13203 download and use network-statuses from the trusted dirservers,
13204 and fetch individual server descriptors as needed from mirrors.
13205 See dir-spec.txt for all the gory details.
13206 - Be more conservative about whether to advertise our DirPort.
13207 The main change is to not advertise if we're running at capacity
13208 and either a) we could hibernate or b) our capacity is low and
13209 we're using a default DirPort.
13210 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
13212 o New features (minor):
13213 - Try to be smart about when to retry network-status and
13214 server-descriptor fetches. Still needs some tuning.
13215 - Stop parsing, storing, or using running-routers output (but
13216 mirrors still cache and serve it).
13217 - Consider a threshold of versioning dirservers (dirservers who have
13218 an opinion about which Tor versions are still recommended) before
13219 deciding whether to warn the user that he's obsolete.
13220 - Dirservers can now reject/invalidate by key and IP, with the
13221 config options "AuthDirInvalid" and "AuthDirReject". This is
13222 useful since currently we automatically list servers as running
13223 and usable even if we know they're jerks.
13224 - Provide dire warnings to any users who set DirServer; move it out
13225 of torrc.sample and into torrc.complete.
13226 - Add MyFamily to torrc.sample in the server section.
13227 - Add nicknames to the DirServer line, so we can refer to them
13228 without requiring all our users to memorize their IP addresses.
13229 - When we get an EOF or a timeout on a directory connection, note
13230 how many bytes of serverdesc we are dropping. This will help
13231 us determine whether it is smart to parse incomplete serverdesc
13233 - Add a new function to "change pseudonyms" -- that is, to stop
13234 using any currently-dirty circuits for new streams, so we don't
13235 link new actions to old actions. Currently it's only called on
13236 HUP (or SIGNAL RELOAD).
13237 - On sighup, if UseHelperNodes changed to 1, use new circuits.
13238 - Start using RAND_bytes rather than RAND_pseudo_bytes from
13239 OpenSSL. Also, reseed our entropy every hour, not just at
13240 startup. And entropy in 512-bit chunks, not 160-bit chunks.
13242 o Fixes on 0.1.1.7-alpha:
13243 - Nobody ever implemented EVENT_ADDRMAP for control protocol
13244 version 0, so don't let version 0 controllers ask for it.
13245 - If you requested something with too many newlines via the
13246 v1 controller protocol, you could crash tor.
13247 - Fix a number of memory leaks, including some pretty serious ones.
13248 - Re-enable DirPort testing again, so Tor servers will be willing
13249 to advertise their DirPort if it's reachable.
13250 - On TLS handshake, only check the other router's nickname against
13251 its expected nickname if is_named is set.
13253 o Fixes forward-ported from 0.1.0.15:
13254 - Don't crash when we don't have any spare file descriptors and we
13255 try to spawn a dns or cpu worker.
13256 - Make the numbers in read-history and write-history into uint64s,
13257 so they don't overflow and publish negatives in the descriptor.
13259 o Fixes on 0.1.0.x:
13260 - For the OS X package's modified privoxy config file, comment
13261 out the "logfile" line so we don't log everything passed
13263 - We were whining about using socks4 or socks5-with-local-lookup
13264 even when it's an IP in the "virtual" range we designed exactly
13266 - We were leaking some memory every time the client changes IPs.
13267 - Never call free() on tor_malloc()d memory. This will help us
13268 use dmalloc to detect memory leaks.
13269 - Check for named servers when looking them up by nickname;
13270 warn when we'recalling a non-named server by its nickname;
13271 don't warn twice about the same name.
13272 - Try to list MyFamily elements by key, not by nickname, and warn
13273 if we've not heard of the server.
13274 - Make windows platform detection (uname equivalent) smarter.
13275 - It turns out sparc64 doesn't like unaligned access either.
13278 Changes in version 0.1.0.15 - 2005-09-23
13279 o Bugfixes on 0.1.0.x:
13280 - Reject ports 465 and 587 (spam targets) in default exit policy.
13281 - Don't crash when we don't have any spare file descriptors and we
13282 try to spawn a dns or cpu worker.
13283 - Get rid of IgnoreVersion undocumented config option, and make us
13284 only warn, never exit, when we're running an obsolete version.
13285 - Don't try to print a null string when your server finds itself to
13286 be unreachable and the Address config option is empty.
13287 - Make the numbers in read-history and write-history into uint64s,
13288 so they don't overflow and publish negatives in the descriptor.
13289 - Fix a minor memory leak in smartlist_string_remove().
13290 - We were only allowing ourselves to upload a server descriptor at
13291 most every 20 minutes, even if it changed earlier than that.
13292 - Clean up log entries that pointed to old URLs.
13295 Changes in version 0.1.1.7-alpha - 2005-09-14
13296 o Fixes on 0.1.1.6-alpha:
13297 - Exit servers were crashing when people asked them to make a
13298 connection to an address not in their exit policy.
13299 - Looking up a non-existent stream for a v1 control connection would
13301 - Fix a seg fault if we ask a dirserver for a descriptor by
13302 fingerprint but he doesn't know about him.
13303 - SETCONF was appending items to linelists, not clearing them.
13304 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
13305 out and refuse the setconf if it would fail.
13306 - Downgrade the dirserver log messages when whining about
13310 - Add Peter Palfrader's check-tor script to tor/contrib/
13311 It lets you easily check whether a given server (referenced by
13312 nickname) is reachable by you.
13313 - Numerous changes to move towards client-side v2 directories. Not
13316 o Fixes on 0.1.0.x:
13317 - If the user gave tor an odd number of command-line arguments,
13318 we were silently ignoring the last one. Now we complain and fail.
13319 [This wins the oldest-bug prize -- this bug has been present since
13320 November 2002, as released in Tor 0.0.0.]
13321 - Do not use unaligned memory access on alpha, mips, or mipsel.
13322 It *works*, but is very slow, so we treat them as if it doesn't.
13323 - Retry directory requests if we fail to get an answer we like
13324 from a given dirserver (we were retrying before, but only if
13325 we fail to connect).
13326 - When writing the RecommendedVersions line, sort them first.
13327 - When the client asked for a rendezvous port that the hidden
13328 service didn't want to provide, we were sending an IP address
13329 back along with the end cell. Fortunately, it was zero. But stop
13331 - Correct "your server is reachable" log entries to indicate that
13332 it was self-testing that told us so.
13335 Changes in version 0.1.1.6-alpha - 2005-09-09
13336 o Fixes on 0.1.1.5-alpha:
13337 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
13338 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
13339 - Fix bug with tor_memmem finding a match at the end of the string.
13340 - Make unit tests run without segfaulting.
13341 - Resolve some solaris x86 compile warnings.
13342 - Handle duplicate lines in approved-routers files without warning.
13343 - Fix bug where as soon as a server refused any requests due to his
13344 exit policy (e.g. when we ask for localhost and he tells us that's
13345 127.0.0.1 and he won't do it), we decided he wasn't obeying his
13346 exit policy using him for any exits.
13347 - Only do openssl hardware accelerator stuff if openssl version is
13350 o New controller features/fixes:
13351 - Add a "RESETCONF" command so you can set config options like
13352 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
13353 a config option in the torrc with no value, then it clears it
13354 entirely (rather than setting it to its default).
13355 - Add a "GETINFO config-file" to tell us where torrc is.
13356 - Avoid sending blank lines when GETINFO replies should be empty.
13357 - Add a QUIT command for the controller (for using it manually).
13358 - Fix a bug in SAVECONF that was adding default dirservers and
13359 other redundant entries to the torrc file.
13361 o Start on the new directory design:
13362 - Generate, publish, cache, serve new network-status format.
13363 - Publish individual descriptors (by fingerprint, by "all", and by
13365 - Publish client and server recommended versions separately.
13366 - Allow tor_gzip_uncompress() to handle multiple concatenated
13367 compressed strings. Serve compressed groups of router
13368 descriptors. The compression logic here could be more
13370 - Distinguish v1 authorities (all currently trusted directories)
13371 from v2 authorities (all trusted directories).
13372 - Change DirServers config line to note which dirs are v1 authorities.
13373 - Add configuration option "V1AuthoritativeDirectory 1" which
13374 moria1, moria2, and tor26 should set.
13375 - Remove option when getting directory cache to see whether they
13376 support running-routers; they all do now. Replace it with one
13377 to see whether caches support v2 stuff.
13380 - Dirservers now do their own external reachability testing of each
13381 Tor server, and only list them as running if they've been found to
13382 be reachable. We also send back warnings to the server's logs if
13383 it uploads a descriptor that we already believe is unreachable.
13384 - Implement exit enclaves: if we know an IP address for the
13385 destination, and there's a running Tor server at that address
13386 which allows exit to the destination, then extend the circuit to
13387 that exit first. This provides end-to-end encryption and end-to-end
13388 authentication. Also, if the user wants a .exit address or enclave,
13389 use 4 hops rather than 3, and cannibalize a general circ for it
13391 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
13392 controller. Also, rotate dns and cpu workers if the controller
13393 changes options that will affect them; and initialize the dns
13394 worker cache tree whether or not we start out as a server.
13395 - Only upload a new server descriptor when options change, 18
13396 hours have passed, uptime is reset, or bandwidth changes a lot.
13397 - Check [X-]Forwarded-For headers in HTTP requests when generating
13398 log messages. This lets people run dirservers (and caches) behind
13399 Apache but still know which IP addresses are causing warnings.
13401 o Config option changes:
13402 - Replace (Fascist)Firewall* config options with a new
13403 ReachableAddresses option that understands address policies.
13404 For example, "ReachableAddresses *:80,*:443"
13405 - Get rid of IgnoreVersion undocumented config option, and make us
13406 only warn, never exit, when we're running an obsolete version.
13407 - Make MonthlyAccountingStart config option truly obsolete now.
13409 o Fixes on 0.1.0.x:
13410 - Reject ports 465 and 587 in the default exit policy, since
13411 people have started using them for spam too.
13412 - It turns out we couldn't bootstrap a network since we added
13413 reachability detection in 0.1.0.1-rc. Good thing the Tor network
13414 has never gone down. Add an AssumeReachable config option to let
13415 servers and dirservers bootstrap. When we're trying to build a
13416 high-uptime or high-bandwidth circuit but there aren't enough
13417 suitable servers, try being less picky rather than simply failing.
13418 - Our logic to decide if the OR we connected to was the right guy
13419 was brittle and maybe open to a mitm for unverified routers.
13420 - We weren't cannibalizing circuits correctly for
13421 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
13422 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
13423 build those from scratch. This should make hidden services faster.
13424 - Predict required circuits better, with an eye toward making hidden
13425 services faster on the service end.
13426 - Retry streams if the exit node sends back a 'misc' failure. This
13427 should result in fewer random failures. Also, after failing
13428 from resolve failed or misc, reset the num failures, so we give
13429 it a fair shake next time we try.
13430 - Clean up the rendezvous warn log msgs, and downgrade some to info.
13431 - Reduce severity on logs about dns worker spawning and culling.
13432 - When we're shutting down and we do something like try to post a
13433 server descriptor or rendezvous descriptor, don't complain that
13434 we seem to be unreachable. Of course we are, we're shutting down.
13435 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
13436 We don't use them yet, but maybe one day our DNS resolver will be
13437 able to discover them.
13438 - Make ContactInfo mandatory for authoritative directory servers.
13439 - Require server descriptors to list IPv4 addresses -- hostnames
13440 are no longer allowed. This also fixes some potential security
13441 problems with people providing hostnames as their address and then
13442 preferentially resolving them to partition users.
13443 - Change log line for unreachability to explicitly suggest /etc/hosts
13444 as the culprit. Also make it clearer what IP address and ports we're
13445 testing for reachability.
13446 - Put quotes around user-supplied strings when logging so users are
13447 more likely to realize if they add bad characters (like quotes)
13449 - Let auth dir servers start without specifying an Address config
13451 - Make unit tests (and other invocations that aren't the real Tor)
13452 run without launching listeners, creating subdirectories, and so on.
13455 Changes in version 0.1.1.5-alpha - 2005-08-08
13456 o Bugfixes included in 0.1.0.14.
13458 o Bugfixes on 0.1.0.x:
13459 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
13460 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
13461 it would silently using ignore the 6668.
13464 Changes in version 0.1.0.14 - 2005-08-08
13465 o Bugfixes on 0.1.0.x:
13466 - Fix the other half of the bug with crypto handshakes
13468 - Fix an assert trigger if you send a 'signal term' via the
13469 controller when it's listening for 'event info' messages.
13472 Changes in version 0.1.1.4-alpha - 2005-08-04
13473 o Bugfixes included in 0.1.0.13.
13476 - Improve tor_gettimeofday() granularity on windows.
13477 - Make clients regenerate their keys when their IP address changes.
13478 - Implement some more GETINFO goodness: expose helper nodes, config
13479 options, getinfo keys.
13482 Changes in version 0.1.0.13 - 2005-08-04
13483 o Bugfixes on 0.1.0.x:
13484 - Fix a critical bug in the security of our crypto handshakes.
13485 - Fix a size_t underflow in smartlist_join_strings2() that made
13486 it do bad things when you hand it an empty smartlist.
13487 - Fix Windows installer to ship Tor license (thanks to Aphex for
13488 pointing out this oversight) and put a link to the doc directory
13490 - Explicitly set no-unaligned-access for sparc: it turns out the
13491 new gcc's let you compile broken code, but that doesn't make it
13495 Changes in version 0.1.1.3-alpha - 2005-07-23
13496 o Bugfixes on 0.1.1.2-alpha:
13497 - Fix a bug in handling the controller's "post descriptor"
13499 - Fix several bugs in handling the controller's "extend circuit"
13501 - Fix a bug in handling the controller's "stream status" event.
13502 - Fix an assert failure if we have a controller listening for
13503 circuit events and we go offline.
13504 - Re-allow hidden service descriptors to publish 0 intro points.
13505 - Fix a crash when generating your hidden service descriptor if
13506 you don't have enough intro points already.
13508 o New features on 0.1.1.2-alpha:
13509 - New controller function "getinfo accounting", to ask how
13510 many bytes we've used in this time period.
13511 - Experimental support for helper nodes: a lot of the risk from
13512 a small static adversary comes because users pick new random
13513 nodes every time they rebuild a circuit. Now users will try to
13514 stick to the same small set of entry nodes if they can. Not
13515 enabled by default yet.
13517 o Bugfixes on 0.1.0.12:
13518 - If you're an auth dir server, always publish your dirport,
13519 even if you haven't yet found yourself to be reachable.
13520 - Fix a size_t underflow in smartlist_join_strings2() that made
13521 it do bad things when you hand it an empty smartlist.
13524 Changes in version 0.1.0.12 - 2005-07-18
13525 o New directory servers:
13526 - tor26 has changed IP address.
13528 o Bugfixes on 0.1.0.x:
13529 - Fix a possible double-free in tor_gzip_uncompress().
13530 - When --disable-threads is set, do not search for or link against
13531 pthreads libraries.
13532 - Don't trigger an assert if an authoritative directory server
13533 claims its dirport is 0.
13534 - Fix bug with removing Tor as an NT service: some people were
13535 getting "The service did not return an error." Thanks to Matt
13539 Changes in version 0.1.1.2-alpha - 2005-07-15
13540 o New directory servers:
13541 - tor26 has changed IP address.
13543 o Bugfixes on 0.1.0.x, crashes/leaks:
13544 - Port the servers-not-obeying-their-exit-policies fix from
13546 - Fix an fd leak in start_daemon().
13547 - On Windows, you can't always reopen a port right after you've
13548 closed it. So change retry_listeners() to only close and re-open
13549 ports that have changed.
13550 - Fix a possible double-free in tor_gzip_uncompress().
13552 o Bugfixes on 0.1.0.x, usability:
13553 - When tor_socketpair() fails in Windows, give a reasonable
13554 Windows-style errno back.
13555 - Let people type "tor --install" as well as "tor -install" when
13557 want to make it an NT service.
13558 - NT service patch from Matt Edman to improve error messages.
13559 - When the controller asks for a config option with an abbreviated
13560 name, give the full name in our response.
13561 - Correct the man page entry on TrackHostExitsExpire.
13562 - Looks like we were never delivering deflated (i.e. compressed)
13563 running-routers lists, even when asked. Oops.
13564 - When --disable-threads is set, do not search for or link against
13565 pthreads libraries.
13567 o Bugfixes on 0.1.1.x:
13568 - Fix a seg fault with autodetecting which controller version is
13572 - New hidden service descriptor format: put a version in it, and
13573 let people specify introduction/rendezvous points that aren't
13574 in "the directory" (which is subjective anyway).
13575 - Allow the DEBUG controller event to work again. Mark certain log
13576 entries as "don't tell this to controllers", so we avoid cycles.
13579 Changes in version 0.1.0.11 - 2005-06-30
13580 o Bugfixes on 0.1.0.x:
13581 - Fix major security bug: servers were disregarding their
13582 exit policies if clients behaved unexpectedly.
13583 - Make OS X init script check for missing argument, so we don't
13584 confuse users who invoke it incorrectly.
13585 - Fix a seg fault in "tor --hash-password foo".
13586 - The MAPADDRESS control command was broken.
13589 Changes in version 0.1.1.1-alpha - 2005-06-29
13591 - Make OS X init script check for missing argument, so we don't
13592 confuse users who invoke it incorrectly.
13593 - Fix a seg fault in "tor --hash-password foo".
13594 - Fix a possible way to DoS dirservers.
13595 - When we complain that your exit policy implicitly allows local or
13596 private address spaces, name them explicitly so operators can
13598 - Make the log message less scary when all the dirservers are
13599 temporarily unreachable.
13600 - We were printing the number of idle dns workers incorrectly when
13604 - Revised controller protocol (version 1) that uses ascii rather
13605 than binary. Add supporting libraries in python and java so you
13606 can use the controller from your applications without caring how
13607 our protocol works.
13608 - Spiffy new support for crypto hardware accelerators. Can somebody
13612 Changes in version 0.0.9.10 - 2005-06-16
13613 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
13614 - Refuse relay cells that claim to have a length larger than the
13615 maximum allowed. This prevents a potential attack that could read
13616 arbitrary memory (e.g. keys) from an exit server's process
13620 Changes in version 0.1.0.10 - 2005-06-14
13621 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
13622 libevent before 1.1a.
13625 Changes in version 0.1.0.9-rc - 2005-06-09
13627 - Reset buf->highwater every time buf_shrink() is called, not just on
13628 a successful shrink. This was causing significant memory bloat.
13629 - Fix buffer overflow when checking hashed passwords.
13630 - Security fix: if seeding the RNG on Win32 fails, quit.
13631 - Allow seeding the RNG on Win32 even when you're not running as
13633 - Disable threading on Solaris too. Something is wonky with it,
13634 cpuworkers, and reentrant libs.
13635 - Reenable the part of the code that tries to flush as soon as an
13636 OR outbuf has a full TLS record available. Perhaps this will make
13637 OR outbufs not grow as huge except in rare cases, thus saving lots
13638 of CPU time plus memory.
13639 - Reject malformed .onion addresses rather then passing them on as
13640 normal web requests.
13641 - Adapt patch from Adam Langley: fix possible memory leak in
13642 tor_lookup_hostname().
13643 - Initialize libevent later in the startup process, so the logs are
13644 already established by the time we start logging libevent warns.
13645 - Use correct errno on win32 if libevent fails.
13646 - Check and warn about known-bad/slow libevent versions.
13647 - Pay more attention to the ClientOnly config option.
13648 - Have torctl.in/tor.sh.in check for location of su binary (needed
13650 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
13651 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
13652 HttpProxyAuthenticator
13653 - Stop warning about sigpipes in the logs. We're going to
13654 pretend that getting these occassionally is normal and fine.
13655 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
13657 installer screens; and don't put stuff into StartupItems unless
13658 the user asks you to.
13659 - Require servers that use the default dirservers to have public IP
13660 addresses. We have too many servers that are configured with private
13661 IPs and their admins never notice the log entries complaining that
13662 their descriptors are being rejected.
13663 - Add OSX uninstall instructions. An actual uninstall script will
13667 Changes in version 0.1.0.8-rc - 2005-05-23
13669 - It turns out that kqueue on OS X 10.3.9 was causing kernel
13670 panics. Disable kqueue on all OS X Tors.
13671 - Fix RPM: remove duplicate line accidentally added to the rpm
13673 - Disable threads on openbsd too, since its gethostaddr is not
13675 - Tolerate libevent 0.8 since it still works, even though it's
13677 - Enable building on Red Hat 9.0 again.
13678 - Allow the middle hop of the testing circuit to be running any
13679 version, now that most of them have the bugfix to let them connect
13680 to unknown servers. This will allow reachability testing to work
13681 even when 0.0.9.7-0.0.9.9 become obsolete.
13682 - Handle relay cells with rh.length too large. This prevents
13683 a potential attack that could read arbitrary memory (maybe even
13684 keys) from the exit server's process.
13685 - We screwed up the dirport reachability testing when we don't yet
13686 have a cached version of the directory. Hopefully now fixed.
13687 - Clean up router_load_single_router() (used by the controller),
13688 so it doesn't seg fault on error.
13689 - Fix a minor memory leak when somebody establishes an introduction
13690 point at your Tor server.
13691 - If a socks connection ends because read fails, don't warn that
13692 you're not sending a socks reply back.
13695 - Add HttpProxyAuthenticator config option too, that works like
13696 the HttpsProxyAuthenticator config option.
13697 - Encode hashed controller passwords in hex instead of base64,
13698 to make it easier to write controllers.
13701 Changes in version 0.1.0.7-rc - 2005-05-17
13703 - Fix a bug in the OS X package installer that prevented it from
13704 installing on Tiger.
13705 - Fix a script bug in the OS X package installer that made it
13706 complain during installation.
13707 - Find libevent even if it's hiding in /usr/local/ and your
13708 CFLAGS and LDFLAGS don't tell you to look there.
13709 - Be able to link with libevent as a shared library (the default
13710 after 1.0d), even if it's hiding in /usr/local/lib and even
13711 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
13712 assuming you're running gcc. Otherwise fail and give a useful
13714 - Fix a bug in the RPM packager: set home directory for _tor to
13715 something more reasonable when first installing.
13716 - Free a minor amount of memory that is still reachable on exit.
13719 Changes in version 0.1.0.6-rc - 2005-05-14
13721 - Implement --disable-threads configure option. Disable threads on
13722 netbsd by default, because it appears to have no reentrant resolver
13724 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
13725 release (1.1) detects and disables kqueue if it's broken.
13726 - Append default exit policy before checking for implicit internal
13727 addresses. Now we don't log a bunch of complaints on startup
13728 when using the default exit policy.
13729 - Some people were putting "Address " in their torrc, and they had
13730 a buggy resolver that resolved " " to 0.0.0.0. Oops.
13731 - If DataDir is ~/.tor, and that expands to /.tor, then default to
13732 LOCALSTATEDIR/tor instead.
13733 - Fix fragmented-message bug in TorControl.py.
13734 - Resolve a minor bug which would prevent unreachable dirports
13735 from getting suppressed in the published descriptor.
13736 - When the controller gave us a new descriptor, we weren't resolving
13737 it immediately, so Tor would think its address was 0.0.0.0 until
13738 we fetched a new directory.
13739 - Fix an uppercase/lowercase case error in suppressing a bogus
13740 libevent warning on some Linuxes.
13743 - Begin scrubbing sensitive strings from logs by default. Turn off
13744 the config option SafeLogging if you need to do debugging.
13745 - Switch to a new buffer management algorithm, which tries to avoid
13746 reallocing and copying quite as much. In first tests it looks like
13747 it uses *more* memory on average, but less cpu.
13748 - First cut at support for "create-fast" cells. Clients can use
13749 these when extending to their first hop, since the TLS already
13750 provides forward secrecy and authentication. Not enabled on
13752 - When dirservers refuse a router descriptor, we now log its
13753 contactinfo, platform, and the poster's IP address.
13754 - Call tor_free_all instead of connections_free_all after forking, to
13755 save memory on systems that need to fork.
13756 - Whine at you if you're a server and you don't set your contactinfo.
13757 - Implement --verify-config command-line option to check if your torrc
13758 is valid without actually launching Tor.
13759 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
13760 rather than just rejecting it.
13763 Changes in version 0.1.0.5-rc - 2005-04-27
13765 - Stop trying to print a null pointer if an OR conn fails because
13766 we didn't like its cert.
13768 - Switch our internal buffers implementation to use a ring buffer,
13769 to hopefully improve performance for fast servers a lot.
13770 - Add HttpsProxyAuthenticator support (basic auth only), based
13771 on patch from Adam Langley.
13772 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
13773 the fast servers that have been joining lately.
13774 - Give hidden service accesses extra time on the first attempt,
13775 since 60 seconds is often only barely enough. This might improve
13777 - Improve performance for dirservers: stop re-parsing the whole
13778 directory every time you regenerate it.
13779 - Add more debugging info to help us find the weird dns freebsd
13780 pthreads bug; cleaner debug messages to help track future issues.
13783 Changes in version 0.0.9.9 - 2005-04-23
13784 o Bugfixes on 0.0.9.x:
13785 - If unofficial Tor clients connect and send weird TLS certs, our
13786 Tor server triggers an assert. This release contains a minimal
13787 backport from the broader fix that we put into 0.1.0.4-rc.
13790 Changes in version 0.1.0.4-rc - 2005-04-23
13792 - If unofficial Tor clients connect and send weird TLS certs, our
13793 Tor server triggers an assert. Stop asserting, and start handling
13794 TLS errors better in other situations too.
13795 - When the controller asks us to tell it about all the debug-level
13796 logs, it turns out we were generating debug-level logs while
13797 telling it about them, which turns into a bad loop. Now keep
13798 track of whether you're sending a debug log to the controller,
13799 and don't log when you are.
13800 - Fix the "postdescriptor" feature of the controller interface: on
13801 non-complete success, only say "done" once.
13803 - Clients are now willing to load balance over up to 2mB, not 1mB,
13804 of advertised bandwidth capacity.
13805 - Add a NoPublish config option, so you can be a server (e.g. for
13806 testing running Tor servers in other Tor networks) without
13807 publishing your descriptor to the primary dirservers.
13810 Changes in version 0.1.0.3-rc - 2005-04-08
13811 o Improvements on 0.1.0.2-rc:
13812 - Client now retries when streams end early for 'hibernating' or
13813 'resource limit' reasons, rather than failing them.
13814 - More automated handling for dirserver operators:
13815 - Automatically approve nodes running 0.1.0.2-rc or later,
13816 now that the the reachability detection stuff is working.
13817 - Now we allow two unverified servers with the same nickname
13818 but different keys. But if a nickname is verified, only that
13819 nickname+key are allowed.
13820 - If you're an authdirserver connecting to an address:port,
13821 and it's not the OR you were expecting, forget about that
13822 descriptor. If he *was* the one you were expecting, then forget
13823 about all other descriptors for that address:port.
13824 - Allow servers to publish descriptors from 12 hours in the future.
13825 Corollary: only whine about clock skew from the dirserver if
13826 he's a trusted dirserver (since now even verified servers could
13827 have quite wrong clocks).
13828 - Adjust maximum skew and age for rendezvous descriptors: let skew
13829 be 48 hours rather than 90 minutes.
13830 - Efficiency improvements:
13831 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
13832 it much faster to look up a circuit for each relay cell.
13833 - Remove most calls to assert_all_pending_dns_resolves_ok(),
13834 since they're eating our cpu on exit nodes.
13835 - Stop wasting time doing a case insensitive comparison for every
13836 dns name every time we do any lookup. Canonicalize the names to
13837 lowercase and be done with it.
13838 - Start sending 'truncated' cells back rather than destroy cells,
13839 if the circuit closes in front of you. This means we won't have
13840 to abandon partially built circuits.
13841 - Only warn once per nickname from add_nickname_list_to_smartlist
13842 per failure, so an entrynode or exitnode choice that's down won't
13844 - Put a note in the torrc about abuse potential with the default
13846 - Revise control spec and implementation to allow all log messages to
13847 be sent to controller with their severities intact (suggested by
13848 Matt Edman). Update TorControl to handle new log event types.
13849 - Provide better explanation messages when controller's POSTDESCRIPTOR
13851 - Stop putting nodename in the Platform string in server descriptors.
13852 It doesn't actually help, and it is confusing/upsetting some people.
13854 o Bugfixes on 0.1.0.2-rc:
13855 - We were printing the host mask wrong in exit policies in server
13856 descriptors. This isn't a critical bug though, since we were still
13857 obeying the exit policy internally.
13858 - Fix Tor when compiled with libevent but without pthreads: move
13859 connection_unregister() from _connection_free() to
13861 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
13862 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
13863 when we look through the connection array, we'll find any of the
13864 cpu/dnsworkers. This is no good.
13866 o Bugfixes on 0.0.9.8:
13867 - Fix possible bug on threading platforms (e.g. win32) which was
13868 leaking a file descriptor whenever a cpuworker or dnsworker died.
13869 - When using preferred entry or exit nodes, ignore whether the
13870 circuit wants uptime or capacity. They asked for the nodes, they
13872 - chdir() to your datadirectory at the *end* of the daemonize process,
13873 not the beginning. This was a problem because the first time you
13874 run tor, if your datadir isn't there, and you have runasdaemon set
13875 to 1, it will try to chdir to it before it tries to create it. Oops.
13876 - Handle changed router status correctly when dirserver reloads
13877 fingerprint file. We used to be dropping all unverified descriptors
13878 right then. The bug was hidden because we would immediately
13879 fetch a directory from another dirserver, which would include the
13880 descriptors we just dropped.
13881 - When we're connecting to an OR and he's got a different nickname/key
13882 than we were expecting, only complain loudly if we're an OP or a
13883 dirserver. Complaining loudly to the OR admins just confuses them.
13884 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
13885 artificially capped at 500kB.
13888 Changes in version 0.0.9.8 - 2005-04-07
13889 o Bugfixes on 0.0.9.x:
13890 - We have a bug that I haven't found yet. Sometimes, very rarely,
13891 cpuworkers get stuck in the 'busy' state, even though the cpuworker
13892 thinks of itself as idle. This meant that no new circuits ever got
13893 established. Here's a workaround to kill any cpuworker that's been
13894 busy for more than 100 seconds.
13897 Changes in version 0.1.0.2-rc - 2005-04-01
13898 o Bugfixes on 0.1.0.1-rc:
13899 - Fixes on reachability detection:
13900 - Don't check for reachability while hibernating.
13901 - If ORPort is reachable but DirPort isn't, still publish the
13902 descriptor, but zero out DirPort until it's found reachable.
13903 - When building testing circs for ORPort testing, use only
13904 high-bandwidth nodes, so fewer circuits fail.
13905 - Complain about unreachable ORPort separately from unreachable
13906 DirPort, so the user knows what's going on.
13907 - Make sure we only conclude ORPort reachability if we didn't
13908 initiate the conn. Otherwise we could falsely conclude that
13909 we're reachable just because we connected to the guy earlier
13910 and he used that same pipe to extend to us.
13911 - Authdirservers shouldn't do ORPort reachability detection,
13912 since they're in clique mode, so it will be rare to find a
13913 server not already connected to them.
13914 - When building testing circuits, always pick middle hops running
13915 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
13916 bug. (This is a kludge; it will go away when 0.0.9.x becomes
13918 - When we decide we're reachable, actually publish our descriptor
13920 - Fix bug in redirectstream in the controller.
13921 - Fix the state descriptor strings so logs don't claim edge streams
13922 are in a different state than they actually are.
13923 - Use recent libevent features when possible (this only really affects
13924 win32 and osx right now, because the new libevent with these
13925 features hasn't been released yet). Add code to suppress spurious
13927 - Prevent possible segfault in connection_close_unattached_ap().
13928 - Fix newlines on torrc in win32.
13929 - Improve error msgs when tor-resolve fails.
13931 o Improvements on 0.0.9.x:
13932 - New experimental script tor/contrib/ExerciseServer.py (needs more
13933 work) that uses the controller interface to build circuits and
13934 fetch pages over them. This will help us bootstrap servers that
13935 have lots of capacity but haven't noticed it yet.
13936 - New experimental script tor/contrib/PathDemo.py (needs more work)
13937 that uses the controller interface to let you choose whole paths
13939 "<hostname>.<path,separated by dots>.<length of path>.path"
13940 - When we've connected to an OR and handshaked but didn't like
13941 the result, we were closing the conn without sending destroy
13942 cells back for pending circuits. Now send those destroys.
13945 Changes in version 0.0.9.7 - 2005-04-01
13946 o Bugfixes on 0.0.9.x:
13947 - Fix another race crash bug (thanks to Glenn Fink for reporting).
13948 - Compare identity to identity, not to nickname, when extending to
13949 a router not already in the directory. This was preventing us from
13950 extending to unknown routers. Oops.
13951 - Make sure to create OS X Tor user in <500 range, so we aren't
13952 creating actual system users.
13953 - Note where connection-that-hasn't-sent-end was marked, and fix
13954 a few really loud instances of this harmless bug (it's fixed more
13958 Changes in version 0.1.0.1-rc - 2005-03-28
13960 - Add reachability testing. Your Tor server will automatically try
13961 to see if its ORPort and DirPort are reachable from the outside,
13962 and it won't upload its descriptor until it decides they are.
13963 - Handle unavailable hidden services better. Handle slow or busy
13964 hidden services better.
13965 - Add support for CONNECTing through https proxies, with "HttpsProxy"
13967 - New exit policy: accept most low-numbered ports, rather than
13968 rejecting most low-numbered ports.
13969 - More Tor controller support (still experimental). See
13970 http://tor.eff.org/doc/control-spec.txt for all the new features,
13971 including signals to emulate unix signals from any platform;
13972 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
13973 closestream; closecircuit; etc.
13974 - Make nt services work and start on startup on win32 (based on
13975 patch by Matt Edman).
13976 - Add a new AddressMap config directive to rewrite incoming socks
13977 addresses. This lets you, for example, declare an implicit
13978 required exit node for certain sites.
13979 - Add a new TrackHostExits config directive to trigger addressmaps
13980 for certain incoming socks addresses -- for sites that break when
13981 your exit keeps changing (based on patch by Mike Perry).
13982 - Redo the client-side dns cache so it's just an addressmap too.
13983 - Notice when our IP changes, and reset stats/uptime/reachability.
13984 - When an application is using socks5, give him the whole variety of
13985 potential socks5 responses (connect refused, host unreachable, etc),
13986 rather than just "success" or "failure".
13987 - A more sane version numbering system. See
13988 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
13989 - New contributed script "exitlist": a simple python script to
13990 parse directories and find Tor nodes that exit to listed
13992 - New contributed script "privoxy-tor-toggle" to toggle whether
13993 Privoxy uses Tor. Seems to be configured for Debian by default.
13994 - Report HTTP reasons to client when getting a response from directory
13995 servers -- so you can actually know what went wrong.
13996 - New config option MaxAdvertisedBandwidth which lets you advertise
13997 a low bandwidthrate (to not attract as many circuits) while still
13998 allowing a higher bandwidthrate in reality.
14000 o Robustness/stability fixes:
14001 - Make Tor use Niels Provos's libevent instead of its current
14002 poll-but-sometimes-select mess. This will let us use faster async
14003 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
14005 - pthread support now too. This was forced because when we forked,
14006 we ended up wasting a lot of duplicate ram over time. Also switch
14007 to foo_r versions of some library calls to allow reentry and
14009 - Better handling for heterogeneous / unreliable nodes:
14010 - Annotate circuits w/ whether they aim to contain high uptime nodes
14011 and/or high capacity nodes. When building circuits, choose
14013 - This means that every single node in an intro rend circuit,
14014 not just the last one, will have a minimum uptime.
14015 - New config option LongLivedPorts to indicate application streams
14016 that will want high uptime circuits.
14017 - Servers reset uptime when a dir fetch entirely fails. This
14018 hopefully reflects stability of the server's network connectivity.
14019 - If somebody starts his tor server in Jan 2004 and then fixes his
14020 clock, don't make his published uptime be a year.
14021 - Reset published uptime when you wake up from hibernation.
14022 - Introduce a notion of 'internal' circs, which are chosen without
14023 regard to the exit policy of the last hop. Intro and rendezvous
14024 circs must be internal circs, to avoid leaking information. Resolve
14025 and connect streams can use internal circs if they want.
14026 - New circuit pooling algorithm: make sure to have enough circs around
14027 to satisfy any predicted ports, and also make sure to have 2 internal
14028 circs around if we've required internal circs lately (and with high
14029 uptime if we've seen that lately too).
14030 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
14031 which describes how often we retry making new circuits if current
14032 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
14033 how long we're willing to make use of an already-dirty circuit.
14034 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
14035 circ as necessary, if there are any completed ones lying around
14036 when we try to launch one.
14037 - Make hidden services try to establish a rendezvous for 30 seconds,
14038 rather than for n (where n=3) attempts to build a circuit.
14039 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
14040 "ShutdownWaitLength".
14041 - Try to be more zealous about calling connection_edge_end when
14042 things go bad with edge conns in connection.c.
14043 - Revise tor-spec to add more/better stream end reasons.
14044 - Revise all calls to connection_edge_end to avoid sending "misc",
14045 and to take errno into account where possible.
14048 - Fix a race condition that can trigger an assert, when we have a
14049 pending create cell and an OR connection fails right then.
14050 - Fix several double-mark-for-close bugs, e.g. where we were finding
14051 a conn for a cell even if that conn is already marked for close.
14052 - Make sequence of log messages when starting on win32 with no config
14053 file more reasonable.
14054 - When choosing an exit node for a new non-internal circ, don't take
14055 into account whether it'll be useful for any pending x.onion
14056 addresses -- it won't.
14057 - Turn addr_policy_compare from a tristate to a quadstate; this should
14058 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
14059 for google.com" problem.
14060 - Make "platform" string in descriptor more accurate for Win32 servers,
14061 so it's not just "unknown platform".
14062 - Fix an edge case in parsing config options (thanks weasel).
14063 If they say "--" on the commandline, it's not an option.
14064 - Reject odd-looking addresses at the client (e.g. addresses that
14065 contain a colon), rather than having the server drop them because
14067 - tor-resolve requests were ignoring .exit if there was a working circuit
14068 they could use instead.
14069 - REUSEADDR on normal platforms means you can rebind to the port
14070 right after somebody else has let it go. But REUSEADDR on win32
14071 means to let you bind to the port _even when somebody else
14072 already has it bound_! So, don't do that on Win32.
14073 - Change version parsing logic: a version is "obsolete" if it is not
14074 recommended and (1) there is a newer recommended version in the
14075 same series, or (2) there are no recommended versions in the same
14076 series, but there are some recommended versions in a newer series.
14077 A version is "new" if it is newer than any recommended version in
14079 - Stop most cases of hanging up on a socks connection without sending
14083 - Require BandwidthRate to be at least 20kB/s for servers.
14084 - When a dirserver causes you to give a warn, mention which dirserver
14086 - New config option DirAllowPrivateAddresses for authdirservers.
14087 Now by default they refuse router descriptors that have non-IP or
14088 private-IP addresses.
14089 - Stop publishing socksport in the directory, since it's not
14090 actually meant to be public. For compatibility, publish a 0 there
14092 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
14093 smart" value, that is low for servers and high for clients.
14094 - If our clock jumps forward by 100 seconds or more, assume something
14095 has gone wrong with our network and abandon all not-yet-used circs.
14096 - Warn when exit policy implicitly allows local addresses.
14097 - If we get an incredibly skewed timestamp from a dirserver mirror
14098 that isn't a verified OR, don't warn -- it's probably him that's
14100 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
14101 cookies to disk and doesn't log each web request to disk. (Thanks
14102 to Brett Carrington for pointing this out.)
14103 - When a client asks us for a dir mirror and we don't have one,
14104 launch an attempt to get a fresh one.
14105 - If we're hibernating and we get a SIGINT, exit immediately.
14106 - Add --with-dmalloc ./configure option, to track memory leaks.
14107 - And try to free all memory on closing, so we can detect what
14109 - Cache local dns resolves correctly even when they're .exit
14111 - Give a better warning when some other server advertises an
14112 ORPort that is actually an apache running ssl.
14113 - Add "opt hibernating 1" to server descriptor to make it clearer
14114 whether the server is hibernating.
14117 Changes in version 0.0.9.6 - 2005-03-24
14118 o Bugfixes on 0.0.9.x (crashes and asserts):
14119 - Add new end stream reasons to maintainance branch. Fix bug where
14120 reason (8) could trigger an assert. Prevent bug from recurring.
14121 - Apparently win32 stat wants paths to not end with a slash.
14122 - Fix assert triggers in assert_cpath_layer_ok(), where we were
14123 blowing away the circuit that conn->cpath_layer points to, then
14124 checking to see if the circ is well-formed. Backport check to make
14125 sure we dont use the cpath on a closed connection.
14126 - Prevent circuit_resume_edge_reading_helper() from trying to package
14127 inbufs for marked-for-close streams.
14128 - Don't crash on hup if your options->address has become unresolvable.
14129 - Some systems (like OS X) sometimes accept() a connection and tell
14130 you the remote host is 0.0.0.0:0. If this happens, due to some
14131 other mis-features, we get confused; so refuse the conn for now.
14133 o Bugfixes on 0.0.9.x (other):
14134 - Fix harmless but scary "Unrecognized content encoding" warn message.
14135 - Add new stream error reason: TORPROTOCOL reason means "you are not
14136 speaking a version of Tor I understand; say bye-bye to your stream."
14137 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
14138 into the future, now that we are more tolerant of skew. This
14139 resolves a bug where a Tor server would refuse to cache a directory
14140 because all the directories it gets are too far in the future;
14141 yet the Tor server never logs any complaints about clock skew.
14142 - Mac packaging magic: make man pages useable, and do not overwrite
14143 existing torrc files.
14144 - Make OS X log happily to /var/log/tor/tor.log
14147 Changes in version 0.0.9.5 - 2005-02-22
14148 o Bugfixes on 0.0.9.x:
14149 - Fix an assert race at exit nodes when resolve requests fail.
14150 - Stop picking unverified dir mirrors--it only leads to misery.
14151 - Patch from Matt Edman to make NT services work better. Service
14152 support is still not compiled into the executable by default.
14153 - Patch from Dmitri Bely so the Tor service runs better under
14154 the win32 SYSTEM account.
14155 - Make tor-resolve actually work (?) on Win32.
14156 - Fix a sign bug when getrlimit claims to have 4+ billion
14157 file descriptors available.
14158 - Stop refusing to start when bandwidthburst == bandwidthrate.
14159 - When create cells have been on the onion queue more than five
14160 seconds, just send back a destroy and take them off the list.
14163 Changes in version 0.0.9.4 - 2005-02-03
14164 o Bugfixes on 0.0.9:
14165 - Fix an assert bug that took down most of our servers: when
14166 a server claims to have 1 GB of bandwidthburst, don't
14168 - Don't crash as badly if we have spawned the max allowed number
14169 of dnsworkers, or we're out of file descriptors.
14170 - Block more file-sharing ports in the default exit policy.
14171 - MaxConn is now automatically set to the hard limit of max
14172 file descriptors we're allowed (ulimit -n), minus a few for
14174 - Give a clearer message when servers need to raise their
14175 ulimit -n when they start running out of file descriptors.
14176 - SGI Compatibility patches from Jan Schaumann.
14177 - Tolerate a corrupt cached directory better.
14178 - When a dirserver hasn't approved your server, list which one.
14179 - Go into soft hibernation after 95% of the bandwidth is used,
14180 not 99%. This is especially important for daily hibernators who
14181 have a small accounting max. Hopefully it will result in fewer
14182 cut connections when the hard hibernation starts.
14183 - Load-balance better when using servers that claim more than
14184 800kB/s of capacity.
14185 - Make NT services work (experimental, only used if compiled in).
14188 Changes in version 0.0.9.3 - 2005-01-21
14189 o Bugfixes on 0.0.9:
14190 - Backport the cpu use fixes from main branch, so busy servers won't
14191 need as much processor time.
14192 - Work better when we go offline and then come back, or when we
14193 run Tor at boot before the network is up. We do this by
14194 optimistically trying to fetch a new directory whenever an
14195 application request comes in and we think we're offline -- the
14196 human is hopefully a good measure of when the network is back.
14197 - Backport some minimal hidserv bugfixes: keep rend circuits open as
14198 long as you keep using them; actually publish hidserv descriptors
14199 shortly after they change, rather than waiting 20-40 minutes.
14200 - Enable Mac startup script by default.
14201 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
14202 - When you update AllowUnverifiedNodes or FirewallPorts via the
14203 controller's setconf feature, we were always appending, never
14205 - When you update HiddenServiceDir via setconf, it was screwing up
14206 the order of reading the lines, making it fail.
14207 - Do not rewrite a cached directory back to the cache; otherwise we
14208 will think it is recent and not fetch a newer one on startup.
14209 - Workaround for webservers that lie about Content-Encoding: Tor
14210 now tries to autodetect compressed directories and compression
14211 itself. This lets us Proxypass dir fetches through apache.
14214 Changes in version 0.0.9.2 - 2005-01-04
14215 o Bugfixes on 0.0.9 (crashes and asserts):
14216 - Fix an assert on startup when the disk is full and you're logging
14218 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
14219 style address, then we'd crash.
14220 - Fix an assert trigger when the running-routers string we get from
14221 a dirserver is broken.
14222 - Make worker threads start and run on win32. Now win32 servers
14224 - Bandaid (not actually fix, but now it doesn't crash) an assert
14225 where the dns worker dies mysteriously and the main Tor process
14226 doesn't remember anything about the address it was resolving.
14228 o Bugfixes on 0.0.9 (Win32):
14229 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
14230 name out of the warning/assert messages.
14231 - Fix a superficial "unhandled error on read" bug on win32.
14232 - The win32 installer no longer requires a click-through for our
14233 license, since our Free Software license grants rights but does not
14235 - Win32: When connecting to a dirserver fails, try another one
14236 immediately. (This was already working for non-win32 Tors.)
14237 - Stop trying to parse $HOME on win32 when hunting for default
14239 - Make tor-resolve.c work on win32 by calling network_init().
14241 o Bugfixes on 0.0.9 (other):
14242 - Make 0.0.9.x build on Solaris again.
14243 - Due to a fencepost error, we were blowing away the \n when reporting
14244 confvalue items in the controller. So asking for multiple config
14245 values at once couldn't work.
14246 - When listing circuits that are pending on an opening OR connection,
14247 if we're an OR we were listing circuits that *end* at us as
14248 being pending on every listener, dns/cpu worker, etc. Stop that.
14249 - Dirservers were failing to create 'running-routers' or 'directory'
14250 strings if we had more than some threshold of routers. Fix them so
14251 they can handle any number of routers.
14252 - Fix a superficial "Duplicate mark for close" bug.
14253 - Stop checking for clock skew for OR connections, even for servers.
14254 - Fix a fencepost error that was chopping off the last letter of any
14255 nickname that is the maximum allowed nickname length.
14256 - Update URLs in log messages so they point to the new website.
14257 - Fix a potential problem in mangling server private keys while
14258 writing to disk (not triggered yet, as far as we know).
14259 - Include the licenses for other free software we include in Tor,
14260 now that we're shipping binary distributions more regularly.
14263 Changes in version 0.0.9.1 - 2004-12-15
14264 o Bugfixes on 0.0.9:
14265 - Make hibernation actually work.
14266 - Make HashedControlPassword config option work.
14267 - When we're reporting event circuit status to a controller,
14268 don't use the stream status code.
14271 Changes in version 0.0.9 - 2004-12-12
14273 - Clean up manpage and torrc.sample file.
14274 - Clean up severities and text of log warnings.
14276 - Make servers trigger an assert when they enter hibernation.
14279 Changes in version 0.0.9rc7 - 2004-12-08
14280 o Bugfixes on 0.0.9rc:
14281 - Fix a stack-trashing crash when an exit node begins hibernating.
14282 - Avoid looking at unallocated memory while considering which
14283 ports we need to build circuits to cover.
14284 - Stop a sigpipe: when an 'end' cell races with eof from the app,
14285 we shouldn't hold-open-until-flush if the eof arrived first.
14286 - Fix a bug with init_cookie_authentication() in the controller.
14287 - When recommending new-format log lines, if the upper bound is
14288 LOG_ERR, leave it implicit.
14290 o Bugfixes on 0.0.8.1:
14291 - Fix a whole slew of memory leaks.
14292 - Fix isspace() and friends so they still make Solaris happy
14293 but also so they don't trigger asserts on win32.
14294 - Fix parse_iso_time on platforms without strptime (eg win32).
14295 - win32: tolerate extra "readable" events better.
14296 - win32: when being multithreaded, leave parent fdarray open.
14297 - Make unit tests work on win32.
14300 Changes in version 0.0.9rc6 - 2004-12-06
14301 o Bugfixes on 0.0.9pre:
14302 - Clean up some more integer underflow opportunities (not exploitable
14304 - While hibernating, hup should not regrow our listeners.
14305 - Send an end to the streams we close when we hibernate, rather
14306 than just chopping them off.
14307 - React to eof immediately on non-open edge connections.
14309 o Bugfixes on 0.0.8.1:
14310 - Calculate timeout for waiting for a connected cell from the time
14311 we sent the begin cell, not from the time the stream started. If
14312 it took a long time to establish the circuit, we would time out
14313 right after sending the begin cell.
14314 - Fix router_compare_addr_to_addr_policy: it was not treating a port
14315 of * as always matching, so we were picking reject *:* nodes as
14316 exit nodes too. Oops.
14319 - New circuit building strategy: keep a list of ports that we've
14320 used in the past 6 hours, and always try to have 2 circuits open
14321 or on the way that will handle each such port. Seed us with port
14322 80 so web users won't complain that Tor is "slow to start up".
14323 - Make kill -USR1 dump more useful stats about circuits.
14324 - When warning about retrying or giving up, print the address, so
14325 the user knows which one it's talking about.
14326 - If you haven't used a clean circuit in an hour, throw it away,
14327 just to be on the safe side. (This means after 6 hours a totally
14328 unused Tor client will have no circuits open.)
14331 Changes in version 0.0.9rc5 - 2004-12-01
14332 o Bugfixes on 0.0.8.1:
14333 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
14334 - Let resolve conns retry/expire also, rather than sticking around
14336 - If we are using select, make sure we stay within FD_SETSIZE.
14338 o Bugfixes on 0.0.9pre:
14339 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
14340 but doesn't seem to be currently; thanks to Ilja van Sprundel for
14342 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
14343 instead. Impose minima and maxima for all *Period options; impose
14344 even tighter maxima for fetching if we are a caching dirserver.
14345 Clip rather than rejecting.
14346 - Fetch cached running-routers from servers that serve it (that is,
14347 authdirservers and servers running 0.0.9rc5-cvs or later.)
14350 - Accept *:706 (silc) in default exit policy.
14351 - Implement new versioning format for post 0.1.
14352 - Support "foo.nickname.exit" addresses, to let Alice request the
14353 address "foo" as viewed by exit node "nickname". Based on a patch
14355 - Make tor --version --version dump the cvs Id of every file.
14358 Changes in version 0.0.9rc4 - 2004-11-28
14359 o Bugfixes on 0.0.8.1:
14360 - Make windows sockets actually non-blocking (oops), and handle
14361 win32 socket errors better.
14363 o Bugfixes on 0.0.9rc1:
14364 - Actually catch the -USR2 signal.
14367 Changes in version 0.0.9rc3 - 2004-11-25
14368 o Bugfixes on 0.0.8.1:
14369 - Flush the log file descriptor after we print "Tor opening log file",
14370 so we don't see those messages days later.
14372 o Bugfixes on 0.0.9rc1:
14373 - Make tor-resolve work again.
14374 - Avoid infinite loop in tor-resolve if tor hangs up on it.
14375 - Fix an assert trigger for clients/servers handling resolves.
14378 Changes in version 0.0.9rc2 - 2004-11-24
14379 o Bugfixes on 0.0.9rc1:
14380 - I broke socks5 support while fixing the eof bug.
14381 - Allow unitless bandwidths and intervals; they default to bytes
14383 - New servers don't start out hibernating; they are active until
14384 they run out of bytes, so they have a better estimate of how
14385 long it takes, and so their operators can know they're working.
14388 Changes in version 0.0.9rc1 - 2004-11-23
14389 o Bugfixes on 0.0.8.1:
14390 - Finally fix a bug that's been plaguing us for a year:
14391 With high load, circuit package window was reaching 0. Whenever
14392 we got a circuit-level sendme, we were reading a lot on each
14393 socket, but only writing out a bit. So we would eventually reach
14394 eof. This would be noticed and acted on even when there were still
14395 bytes sitting in the inbuf.
14396 - When poll() is interrupted, we shouldn't believe the revents values.
14398 o Bugfixes on 0.0.9pre6:
14399 - Fix hibernate bug that caused pre6 to be broken.
14400 - Don't keep rephist info for routers that haven't had activity for
14401 24 hours. (This matters now that clients have keys, since we track
14403 - Never call close_temp_logs while validating log options.
14404 - Fix backslash-escaping on tor.sh.in and torctl.in.
14407 - Implement weekly/monthly/daily accounting: now you specify your
14408 hibernation properties by
14409 AccountingMax N bytes|KB|MB|GB|TB
14410 AccountingStart day|week|month [day] HH:MM
14411 Defaults to "month 1 0:00".
14412 - Let bandwidth and interval config options be specified as 5 bytes,
14413 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
14414 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
14415 get back to normal.)
14416 - If your requested entry or exit node has advertised bandwidth 0,
14418 - Be more greedy about filling up relay cells -- we try reading again
14419 once we've processed the stuff we read, in case enough has arrived
14420 to fill the last cell completely.
14421 - Apply NT service patch from Osamu Fujino. Still needs more work.
14424 Changes in version 0.0.9pre6 - 2004-11-15
14425 o Bugfixes on 0.0.8.1:
14426 - Fix assert failure on malformed socks4a requests.
14427 - Use identity comparison, not nickname comparison, to choose which
14428 half of circuit-ID-space each side gets to use. This is needed
14429 because sometimes we think of a router as a nickname, and sometimes
14430 as a hex ID, and we can't predict what the other side will do.
14431 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
14432 write() call will fail and we handle it there.
14433 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
14434 and smartlist_len, which are two major profiling offenders.
14436 o Bugfixes on 0.0.9pre5:
14437 - Fix a bug in read_all that was corrupting config files on windows.
14438 - When we're raising the max number of open file descriptors to
14439 'unlimited', don't log that we just raised it to '-1'.
14440 - Include event code with events, as required by control-spec.txt.
14441 - Don't give a fingerprint when clients do --list-fingerprint:
14442 it's misleading, because it will never be the same again.
14443 - Stop using strlcpy in tor_strndup, since it was slowing us
14445 - Remove warn on startup about missing cached-directory file.
14446 - Make kill -USR1 work again.
14447 - Hibernate if we start tor during the "wait for wakeup-time" phase
14448 of an accounting interval. Log our hibernation plans better.
14449 - Authoritative dirservers now also cache their directory, so they
14450 have it on start-up.
14453 - Fetch running-routers; cache running-routers; compress
14454 running-routers; serve compressed running-routers.z
14455 - Add NSI installer script contributed by J Doe.
14456 - Commit VC6 and VC7 workspace/project files.
14457 - Commit a tor.spec for making RPM files, with help from jbash.
14458 - Add contrib/torctl.in contributed by Glenn Fink.
14459 - Implement the control-spec's SAVECONF command, to write your
14460 configuration to torrc.
14461 - Get cookie authentication for the controller closer to working.
14462 - Include control-spec.txt in the tarball.
14463 - When set_conf changes our server descriptor, upload a new copy.
14464 But don't upload it too often if there are frequent changes.
14465 - Document authentication config in man page, and document signals
14467 - Clean up confusing parts of man page and torrc.sample.
14468 - Make expand_filename handle ~ and ~username.
14469 - Use autoconf to enable largefile support where necessary. Use
14470 ftello where available, since ftell can fail at 2GB.
14471 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
14472 log more informatively.
14473 - Give a slightly more useful output for "tor -h".
14474 - Refuse application socks connections to port 0.
14475 - Check clock skew for verified servers, but allow unverified
14476 servers and clients to have any clock skew.
14477 - Break DirFetchPostPeriod into:
14478 - DirFetchPeriod for fetching full directory,
14479 - StatusFetchPeriod for fetching running-routers,
14480 - DirPostPeriod for posting server descriptor,
14481 - RendPostPeriod for posting hidden service descriptors.
14482 - Make sure the hidden service descriptors are at a random offset
14483 from each other, to hinder linkability.
14486 Changes in version 0.0.9pre5 - 2004-11-09
14487 o Bugfixes on 0.0.9pre4:
14488 - Fix a seg fault in unit tests (doesn't affect main program).
14489 - Fix an assert bug where a hidden service provider would fail if
14490 the first hop of his rendezvous circuit was down.
14491 - Hidden service operators now correctly handle version 1 style
14492 INTRODUCE1 cells (nobody generates them still, so not a critical
14494 - If do_hup fails, actually notice.
14495 - Handle more errnos from accept() without closing the listener.
14496 Some OpenBSD machines were closing their listeners because
14497 they ran out of file descriptors.
14498 - Send resolve cells to exit routers that are running a new
14499 enough version of the resolve code to work right.
14500 - Better handling of winsock includes on non-MSV win32 compilers.
14501 - Some people had wrapped their tor client/server in a script
14502 that would restart it whenever it died. This did not play well
14503 with our "shut down if your version is obsolete" code. Now people
14504 don't fetch a new directory if their local cached version is
14506 - Make our autogen.sh work on ksh as well as bash.
14509 - Hibernation: New config option "AccountingMaxKB" lets you
14510 set how many KBytes per month you want to allow your server to
14511 consume. Rather than spreading those bytes out evenly over the
14512 month, we instead hibernate for some of the month and pop up
14513 at a deterministic time, work until the bytes are consumed, then
14514 hibernate again. Config option "MonthlyAccountingStart" lets you
14515 specify which day of the month your billing cycle starts on.
14516 - Control interface: a separate program can now talk to your
14517 client/server over a socket, and get/set config options, receive
14518 notifications of circuits and streams starting/finishing/dying,
14519 bandwidth used, etc. The next step is to get some GUIs working.
14520 Let us know if you want to help out. See doc/control-spec.txt .
14521 - Ship a contrib/tor-control.py as an example script to interact
14522 with the control port.
14523 - "tor --hash-password zzyxz" will output a salted password for
14524 use in authenticating to the control interface.
14525 - New log format in config:
14526 "Log minsev[-maxsev] stdout|stderr|syslog" or
14527 "Log minsev[-maxsev] file /var/foo"
14530 - DirPolicy config option, to let people reject incoming addresses
14531 from their dirserver.
14532 - "tor --list-fingerprint" will list your identity key fingerprint
14534 - Add "pass" target for RedirectExit, to make it easier to break
14535 out of a sequence of RedirectExit rules.
14536 - Clients now generate a TLS cert too, in preparation for having
14537 them act more like real nodes.
14538 - Ship src/win32/ in the tarball, so people can use it to build.
14539 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
14541 - New "router-status" line in directory, to better bind each verified
14542 nickname to its identity key.
14543 - Deprecate unofficial config option abbreviations, and abbreviations
14544 not on the command line.
14545 - Add a pure-C tor-resolve implementation.
14546 - Use getrlimit and friends to ensure we can reach MaxConn (currently
14547 1024) file descriptors.
14549 o Code security improvements, inspired by Ilja:
14550 - Replace sprintf with snprintf. (I think they were all safe, but
14552 - Replace strcpy/strncpy with strlcpy in more places.
14553 - Avoid strcat; use snprintf or strlcat instead.
14554 - snprintf wrapper with consistent (though not C99) overflow behavior.
14557 Changes in version 0.0.9pre4 - 2004-10-17
14558 o Bugfixes on 0.0.9pre3:
14559 - If the server doesn't specify an exit policy, use the real default
14560 exit policy, not reject *:*.
14561 - Ignore fascistfirewall when uploading/downloading hidden service
14562 descriptors, since we go through Tor for those; and when using
14563 an HttpProxy, since we assume it can reach them all.
14564 - When looking for an authoritative dirserver, use only the ones
14565 configured at boot. Don't bother looking in the directory.
14566 - The rest of the fix for get_default_conf_file() on older win32.
14567 - Make 'Routerfile' config option obsolete.
14570 - New 'MyFamily nick1,...' config option for a server to
14571 specify other servers that shouldn't be used in the same circuit
14572 with it. Only believed if nick1 also specifies us.
14573 - New 'NodeFamily nick1,nick2,...' config option for a client to
14574 specify nodes that it doesn't want to use in the same circuit.
14575 - New 'Redirectexit pattern address:port' config option for a
14576 server to redirect exit connections, e.g. to a local squid.
14579 Changes in version 0.0.9pre3 - 2004-10-13
14580 o Bugfixes on 0.0.8.1:
14581 - Better torrc example lines for dirbindaddress and orbindaddress.
14582 - Improved bounds checking on parsed ints (e.g. config options and
14583 the ones we find in directories.)
14584 - Better handling of size_t vs int, so we're more robust on 64
14586 - Fix the rest of the bug where a newly started OR would appear
14587 as unverified even after we've added his fingerprint and hupped
14589 - Fix a bug from 0.0.7: when read() failed on a stream, we would
14590 close it without sending back an end. So 'connection refused'
14591 would simply be ignored and the user would get no response.
14593 o Bugfixes on 0.0.9pre2:
14594 - Serving the cached-on-disk directory to people is bad. We now
14595 provide no directory until we've fetched a fresh one.
14596 - Workaround for bug on windows where cached-directories get crlf
14598 - Make get_default_conf_file() work on older windows too.
14599 - If we write a *:* exit policy line in the descriptor, don't write
14600 any more exit policy lines.
14603 - Use only 0.0.9pre1 and later servers for resolve cells.
14604 - Make the dirservers file obsolete.
14605 - Include a dir-signing-key token in directories to tell the
14606 parsing entity which key is being used to sign.
14607 - Remove the built-in bulky default dirservers string.
14608 - New config option "Dirserver %s:%d [fingerprint]", which can be
14609 repeated as many times as needed. If no dirservers specified,
14610 default to moria1,moria2,tor26.
14611 - Make moria2 advertise a dirport of 80, so people behind firewalls
14612 will be able to get a directory.
14613 - Http proxy support
14614 - Dirservers translate requests for http://%s:%d/x to /x
14615 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
14616 be routed through this host.
14617 - Clients ask for /tor/x rather than /x for new enough dirservers.
14618 This way we can one day coexist peacefully with apache.
14619 - Clients specify a "Host: %s%d" http header, to be compatible
14620 with more proxies, and so running squid on an exit node can work.
14623 Changes in version 0.0.8.1 - 2004-10-13
14625 - Fix a seg fault that can be triggered remotely for Tor
14626 clients/servers with an open dirport.
14627 - Fix a rare assert trigger, where routerinfos for entries in
14628 our cpath would expire while we're building the path.
14629 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14630 - Fix a rare seg fault for people running hidden services on
14631 intermittent connections.
14632 - Fix a bug in parsing opt keywords with objects.
14633 - Fix a stale pointer assert bug when a stream detaches and
14635 - Fix a string format vulnerability (probably not exploitable)
14636 in reporting stats locally.
14637 - Fix an assert trigger: sometimes launching circuits can fail
14638 immediately, e.g. because too many circuits have failed recently.
14639 - Fix a compile warning on 64 bit platforms.
14642 Changes in version 0.0.9pre2 - 2004-10-03
14644 - Make fetching a cached directory work for 64-bit platforms too.
14645 - Make zlib.h a required header, not an optional header.
14648 Changes in version 0.0.9pre1 - 2004-10-01
14650 - Stop using separate defaults for no-config-file and
14651 empty-config-file. Now you have to explicitly turn off SocksPort,
14652 if you don't want it open.
14653 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14654 - Improve man page to mention more of the 0.0.8 features.
14655 - Fix a rare seg fault for people running hidden services on
14656 intermittent connections.
14657 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
14659 - Fix more dns related bugs: send back resolve_failed and end cells
14660 more reliably when the resolve fails, rather than closing the
14661 circuit and then trying to send the cell. Also attach dummy resolve
14662 connections to a circuit *before* calling dns_resolve(), to fix
14663 a bug where cached answers would never be sent in RESOLVED cells.
14664 - When we run out of disk space, or other log writing error, don't
14665 crash. Just stop logging to that log and continue.
14666 - We were starting to daemonize before we opened our logs, so if
14667 there were any problems opening logs, we would complain to stderr,
14668 which wouldn't work, and then mysteriously exit.
14669 - Fix a rare bug where sometimes a verified OR would connect to us
14670 before he'd uploaded his descriptor, which would cause us to
14671 assign conn->nickname as though he's unverified. Now we look through
14672 the fingerprint list to see if he's there.
14673 - Fix a rare assert trigger, where routerinfos for entries in
14674 our cpath would expire while we're building the path.
14677 - Clients can ask dirservers for /dir.z to get a compressed version
14678 of the directory. Only works for servers running 0.0.9, of course.
14679 - Make clients cache directories and use them to seed their router
14680 lists at startup. This means clients have a datadir again.
14681 - Configuration infrastructure support for warning on obsolete
14683 - Respond to content-encoding headers by trying to uncompress as
14685 - Reply with a deflated directory when a client asks for "dir.z".
14686 We could use allow-encodings instead, but allow-encodings isn't
14687 specified in HTTP 1.0.
14688 - Raise the max dns workers from 50 to 100.
14689 - Discourage people from setting their dirfetchpostperiod more often
14690 than once per minute.
14691 - Protect dirservers from overzealous descriptor uploading -- wait
14692 10 seconds after directory gets dirty, before regenerating.
14695 Changes in version 0.0.8 - 2004-08-25
14696 o Port it to SunOS 5.9 / Athena
14699 Changes in version 0.0.8rc2 - 2004-08-20
14700 o Make it compile on cygwin again.
14701 o When picking unverified routers, skip those with low uptime and/or
14702 low bandwidth, depending on what properties you care about.
14705 Changes in version 0.0.8rc1 - 2004-08-18
14706 o Changes from 0.0.7.3:
14708 - Fix assert triggers: if the other side returns an address 0.0.0.0,
14709 don't put it into the client dns cache.
14710 - If a begin failed due to exit policy, but we believe the IP address
14711 should have been allowed, switch that router to exitpolicy reject *:*
14712 until we get our next directory.
14714 - Clients choose nodes proportional to advertised bandwidth.
14715 - Avoid using nodes with low uptime as introduction points.
14716 - Handle servers with dynamic IP addresses: don't replace
14717 options->Address with the resolved one at startup, and
14718 detect our address right before we make a routerinfo each time.
14719 - 'FascistFirewall' option to pick dirservers and ORs on specific
14720 ports; plus 'FirewallPorts' config option to tell FascistFirewall
14721 which ports are open. (Defaults to 80,443)
14722 - Be more aggressive about trying to make circuits when the network
14723 has changed (e.g. when you unsuspend your laptop).
14724 - Check for time skew on http headers; report date in response to
14726 - If the entrynode config line has only one node, don't pick it as
14728 - Add strict{entry|exit}nodes config options. If set to 1, then
14729 we refuse to build circuits that don't include the specified entry
14731 - OutboundBindAddress config option, to bind to a specific
14732 IP address for outgoing connect()s.
14733 - End truncated log entries (e.g. directories) with "[truncated]".
14735 o Patches to 0.0.8preX:
14737 - Patches to compile and run on win32 again (maybe)?
14738 - Fix crash when looking for ~/.torrc with no $HOME set.
14739 - Fix a race bug in the unit tests.
14740 - Handle verified/unverified name collisions better when new
14741 routerinfo's arrive in a directory.
14742 - Sometimes routers were getting entered into the stats before
14743 we'd assigned their identity_digest. Oops.
14744 - Only pick and establish intro points after we've gotten a
14747 - AllowUnverifiedNodes config option to let circuits choose no-name
14748 routers in entry,middle,exit,introduction,rendezvous positions.
14749 Allow middle and rendezvous positions by default.
14750 - Add a man page for tor-resolve.
14753 Changes in version 0.0.7.3 - 2004-08-12
14754 o Stop dnsworkers from triggering an assert failure when you
14755 ask them to resolve the host "".
14758 Changes in version 0.0.8pre3 - 2004-08-09
14759 o Changes from 0.0.7.2:
14760 - Allow multiple ORs with same nickname in routerlist -- now when
14761 people give us one identity key for a nickname, then later
14762 another, we don't constantly complain until the first expires.
14763 - Remember used bandwidth (both in and out), and publish 15-minute
14764 snapshots for the past day into our descriptor.
14765 - You can now fetch $DIRURL/running-routers to get just the
14766 running-routers line, not the whole descriptor list. (But
14767 clients don't use this yet.)
14768 - When people mistakenly use Tor as an http proxy, point them
14769 at the tor-doc.html rather than the INSTALL.
14770 - Remove our mostly unused -- and broken -- hex_encode()
14771 function. Use base16_encode() instead. (Thanks to Timo Lindfors
14772 for pointing out this bug.)
14773 - Rotate onion keys every 12 hours, not every 2 hours, so we have
14774 fewer problems with people using the wrong key.
14775 - Change the default exit policy to reject the default edonkey,
14776 kazaa, gnutella ports.
14777 - Add replace_file() to util.[ch] to handle win32's rename().
14779 o Changes from 0.0.8preX:
14780 - Fix two bugs in saving onion keys to disk when rotating, so
14781 hopefully we'll get fewer people using old onion keys.
14782 - Fix an assert error that was making SocksPolicy not work.
14783 - Be willing to expire routers that have an open dirport -- it's
14784 just the authoritative dirservers we want to not forget.
14785 - Reject tor-resolve requests for .onion addresses early, so we
14786 don't build a whole rendezvous circuit and then fail.
14787 - When you're warning a server that he's unverified, don't cry
14788 wolf unpredictably.
14789 - Fix a race condition: don't try to extend onto a connection
14790 that's still handshaking.
14791 - For servers in clique mode, require the conn to be open before
14792 you'll choose it for your path.
14793 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
14794 end relay cell, etc.
14795 - Measure bandwidth capacity over the last 24 hours, not just 12
14796 - Bugfix: authoritative dirservers were making and signing a new
14797 directory for each client, rather than reusing the cached one.
14800 Changes in version 0.0.8pre2 - 2004-08-04
14801 o Changes from 0.0.7.2:
14803 - Check directory signature _before_ you decide whether you're
14804 you're running an obsolete version and should exit.
14805 - Check directory signature _before_ you parse the running-routers
14806 list to decide who's running or verified.
14807 - Bugfixes and features:
14808 - Check return value of fclose while writing to disk, so we don't
14809 end up with broken files when servers run out of disk space.
14810 - Log a warning if the user uses an unsafe socks variant, so people
14811 are more likely to learn about privoxy or socat.
14812 - Dirservers now include RFC1123-style dates in the HTTP headers,
14813 which one day we will use to better detect clock skew.
14815 o Changes from 0.0.8pre1:
14816 - Make it compile without warnings again on win32.
14817 - Log a warning if you're running an unverified server, to let you
14818 know you might want to get it verified.
14819 - Only pick a default nickname if you plan to be a server.
14822 Changes in version 0.0.8pre1 - 2004-07-23
14824 - Made our unit tests compile again on OpenBSD 3.5, and tor
14825 itself compile again on OpenBSD on a sparc64.
14826 - We were neglecting milliseconds when logging on win32, so
14827 everything appeared to happen at the beginning of each second.
14829 o Protocol changes:
14830 - 'Extend' relay cell payloads now include the digest of the
14831 intended next hop's identity key. Now we can verify that we're
14832 extending to the right router, and also extend to routers we
14833 hadn't heard of before.
14836 - Tor nodes can now act as relays (with an advertised ORPort)
14837 without being manually verified by the dirserver operators.
14838 - Uploaded descriptors of unverified routers are now accepted
14839 by the dirservers, and included in the directory.
14840 - Verified routers are listed by nickname in the running-routers
14841 list; unverified routers are listed as "$<fingerprint>".
14842 - We now use hash-of-identity-key in most places rather than
14843 nickname or addr:port, for improved security/flexibility.
14844 - To avoid Sybil attacks, paths still use only verified servers.
14845 But now we have a chance to play around with hybrid approaches.
14846 - Nodes track bandwidth usage to estimate capacity (not used yet).
14847 - ClientOnly option for nodes that never want to become servers.
14848 - Directory caching.
14849 - "AuthoritativeDir 1" option for the official dirservers.
14850 - Now other nodes (clients and servers) will cache the latest
14851 directory they've pulled down.
14852 - They can enable their DirPort to serve it to others.
14853 - Clients will pull down a directory from any node with an open
14854 DirPort, and check the signature/timestamp correctly.
14855 - Authoritative dirservers now fetch directories from other
14856 authdirservers, to stay better synced.
14857 - Running-routers list tells who's down also, along with noting
14858 if they're verified (listed by nickname) or unverified (listed
14860 - Allow dirservers to serve running-router list separately.
14861 This isn't used yet.
14862 - ORs connect-on-demand to other ORs
14863 - If you get an extend cell to an OR you're not connected to,
14864 connect, handshake, and forward the create cell.
14865 - The authoritative dirservers stay connected to everybody,
14866 and everybody stays connected to 0.0.7 servers, but otherwise
14867 clients/servers expire unused connections after 5 minutes.
14868 - When servers get a sigint, they delay 30 seconds (refusing new
14869 connections) then exit. A second sigint causes immediate exit.
14870 - File and name management:
14871 - Look for .torrc if no CONFDIR "torrc" is found.
14872 - If no datadir is defined, then choose, make, and secure ~/.tor
14874 - If torrc not found, exitpolicy reject *:*.
14875 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
14876 - If no nickname is defined, derive default from hostname.
14877 - Rename secret key files, e.g. identity.key -> secret_id_key,
14878 to discourage people from mailing their identity key to tor-ops.
14879 - Refuse to build a circuit before the directory has arrived --
14880 it won't work anyway, since you won't know the right onion keys
14882 - Try other dirservers immediately if the one you try is down. This
14883 should tolerate down dirservers better now.
14884 - Parse tor version numbers so we can do an is-newer-than check
14885 rather than an is-in-the-list check.
14886 - New socks command 'resolve', to let us shim gethostbyname()
14888 - A 'tor_resolve' script to access the socks resolve functionality.
14889 - A new socks-extensions.txt doc file to describe our
14890 interpretation and extensions to the socks protocols.
14891 - Add a ContactInfo option, which gets published in descriptor.
14892 - Publish OR uptime in descriptor (and thus in directory) too.
14893 - Write tor version at the top of each log file
14894 - New docs in the tarball:
14896 - Document that you should proxy your SSL traffic too.
14899 Changes in version 0.0.7.2 - 2004-07-07
14900 o A better fix for the 0.0.0.0 problem, that will hopefully
14901 eliminate the remaining related assertion failures.
14904 Changes in version 0.0.7.1 - 2004-07-04
14905 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
14906 since internally we use 0.0.0.0 to signify "not yet resolved".
14909 Changes in version 0.0.7 - 2004-06-07
14910 o Updated the man page to reflect the new features.
14913 Changes in version 0.0.7rc2 - 2004-06-06
14914 o Changes from 0.0.7rc1:
14915 - Make it build on Win32 again.
14916 o Changes from 0.0.6.2:
14917 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
14921 Changes in version 0.0.7rc1 - 2004-06-02
14923 - On sighup, we were adding another log without removing the first
14924 one. So log messages would get duplicated n times for n sighups.
14925 - Several cases of using a connection after we'd freed it. The
14926 problem was that connections that are pending resolve are in both
14927 the pending_resolve tree, and also the circuit's resolving_streams
14928 list. When you want to remove one, you must remove it from both.
14929 - Fix a double-mark-for-close where an end cell arrived for a
14930 resolving stream, and then the resolve failed.
14931 - Check directory signatures based on name of signer, not on whom
14932 we got the directory from. This will let us cache directories more
14935 - Crank up some of our constants to handle more users.
14938 Changes in version 0.0.7pre1 - 2004-06-02
14939 o Fixes for crashes and other obnoxious bugs:
14940 - Fix an epipe bug: sometimes when directory connections failed
14941 to connect, we would give them a chance to flush before closing
14943 - When we detached from a circuit because of resolvefailed, we
14944 would immediately try the same circuit twice more, and then
14945 give up on the resolve thinking we'd tried three different
14947 - Limit the number of intro circuits we'll attempt to build for a
14948 hidden service per 15-minute period.
14949 - Check recommended-software string *early*, before actually parsing
14950 the directory. Thus we can detect an obsolete version and exit,
14951 even if the new directory format doesn't parse.
14952 o Fixes for security bugs:
14953 - Remember which nodes are dirservers when you startup, and if a
14954 random OR enables his dirport, don't automatically assume he's
14955 a trusted dirserver.
14957 - Directory connections were asking the wrong poll socket to
14958 start writing, and not asking themselves to start writing.
14959 - When we detached from a circuit because we sent a begin but
14960 didn't get a connected, we would use it again the first time;
14961 but after that we would correctly switch to a different one.
14962 - Stop warning when the first onion decrypt attempt fails; they
14963 will sometimes legitimately fail now that we rotate keys.
14964 - Override unaligned-access-ok check when $host_cpu is ia64 or
14965 arm. Apparently they allow it but the kernel whines.
14966 - Dirservers try to reconnect periodically too, in case connections
14968 - Fix some memory leaks in directory servers.
14969 - Allow backslash in Win32 filenames.
14970 - Made Tor build complain-free on FreeBSD, hopefully without
14971 breaking other BSD builds. We'll see.
14973 - Doxygen markup on all functions and global variables.
14974 - Make directory functions update routerlist, not replace it. So
14975 now directory disagreements are not so critical a problem.
14976 - Remove the upper limit on number of descriptors in a dirserver's
14977 directory (not that we were anywhere close).
14978 - Allow multiple logfiles at different severity ranges.
14979 - Allow *BindAddress to specify ":port" rather than setting *Port
14980 separately. Allow multiple instances of each BindAddress config
14981 option, so you can bind to multiple interfaces if you want.
14982 - Allow multiple exit policy lines, which are processed in order.
14983 Now we don't need that huge line with all the commas in it.
14984 - Enable accept/reject policies on SOCKS connections, so you can bind
14985 to 0.0.0.0 but still control who can use your OP.
14988 Changes in version 0.0.6.2 - 2004-05-16
14989 o Our integrity-checking digest was checking only the most recent cell,
14990 not the previous cells like we'd thought.
14991 Thanks to Stefan Mark for finding the flaw!
14994 Changes in version 0.0.6.1 - 2004-05-06
14995 o Fix two bugs in our AES counter-mode implementation (this affected
14996 onion-level stream encryption, but not TLS-level). It turns
14997 out we were doing something much more akin to a 16-character
14998 polyalphabetic cipher. Oops.
14999 Thanks to Stefan Mark for finding the flaw!
15000 o Retire moria3 as a directory server, and add tor26 as a directory
15004 Changes in version 0.0.6 - 2004-05-02
15005 [version bump only]
15008 Changes in version 0.0.6rc4 - 2004-05-01
15009 o Update the built-in dirservers list to use the new directory format
15010 o Fix a rare seg fault: if a node offering a hidden service attempts
15011 to build a circuit to Alice's rendezvous point and fails before it
15012 reaches the last hop, it retries with a different circuit, but
15014 o Handle windows socket errors correctly.
15017 Changes in version 0.0.6rc3 - 2004-04-28
15018 o Don't expire non-general excess circuits (if we had enough
15019 circuits open, we were expiring rendezvous circuits -- even
15020 when they had a stream attached. oops.)
15021 o Fetch randomness from /dev/urandom better (not via fopen/fread)
15022 o Better debugging for tls errors
15023 o Some versions of openssl have an SSL_pending function that erroneously
15024 returns bytes when there is a non-application record pending.
15025 o Set Content-Type on the directory and hidserv descriptor.
15026 o Remove IVs from cipher code, since AES-ctr has none.
15027 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
15028 o We were using an array of length zero in a few places.
15029 o win32's gethostbyname can't resolve an IP to an IP.
15030 o win32's close can't close a socket.
15033 Changes in version 0.0.6rc2 - 2004-04-26
15034 o Fix a bug where we were closing tls connections intermittently.
15035 It turns out openssl keeps its errors around -- so if an error
15036 happens, and you don't ask about it, and then another openssl
15037 operation happens and succeeds, and you ask if there was an error,
15038 it tells you about the first error. Fun fun.
15039 o Fix a bug that's been lurking since 27 may 03 (!)
15040 When passing back a destroy cell, we would use the wrong circ id.
15041 'Mostly harmless', but still worth fixing.
15042 o Since we don't support truncateds much, don't bother sending them;
15043 just close the circ.
15044 o check for <machine/limits.h> so we build on NetBSD again (I hope).
15045 o don't crash if a conn that sent a begin has suddenly lost its circuit
15046 (this was quite rare).
15049 Changes in version 0.0.6rc1 - 2004-04-25
15050 o We now rotate link (tls context) keys and onion keys.
15051 o CREATE cells now include oaep padding, so you can tell
15052 if you decrypted them correctly.
15053 o Add bandwidthburst to server descriptor.
15054 o Directories now say which dirserver signed them.
15055 o Use a tor_assert macro that logs failed assertions too.
15058 Changes in version 0.0.6pre5 - 2004-04-18
15059 o changes from 0.0.6pre4:
15060 - make tor build on broken freebsd 5.2 installs
15061 - fix a failed assert when you try an intro point, get a nack, and try
15062 a second one and it works.
15063 - when alice uses a port that the hidden service doesn't accept,
15064 it now sends back an end cell (denied by exit policy). otherwise
15065 alice would just have to wait to time out.
15066 - fix another rare bug: when we had tried all the intro
15067 points for a hidden service, we fetched the descriptor
15068 again, but we left our introcirc thinking it had already
15069 sent an intro, so it kept waiting for a response...
15070 - bugfix: when you sleep your hidden-service laptop, as soon
15071 as it wakes up it tries to upload a service descriptor, but
15072 socketpair fails for some reason (localhost not up yet?).
15073 now we simply give up on that upload, and we'll try again later.
15074 i'd still like to find the bug though.
15075 - if an intro circ waiting for an ack dies before getting one, then
15077 - we were reusing stale service descriptors and refetching usable
15081 Changes in version 0.0.6pre4 - 2004-04-14
15082 o changes from 0.0.6pre3:
15083 - when bob fails to connect to the rendezvous point, and his
15084 circ didn't fail because of the rendezvous point itself, then
15085 he retries a couple of times
15086 - we expire introduction and rendezvous circs more thoroughly
15087 (sometimes they were hanging around forever)
15088 - we expire unattached rendezvous streams that have been around
15089 too long (they were sticking around forever).
15090 - fix a measly fencepost error that was crashing everybody with
15094 Changes in version 0.0.6pre3 - 2004-04-14
15095 o changes from 0.0.6pre2:
15096 - make hup work again
15097 - fix some memory leaks for dirservers
15098 - allow more skew in rendezvous descriptor timestamps, to help
15099 handle people like blanu who don't know what time it is
15100 - normal circs are 3 hops, but some rend/intro circs are 4, if
15101 the initiator doesn't get to choose the last hop
15102 - send acks for introductions, so alice can know whether to try
15104 - bob publishes intro points more correctly
15105 o changes from 0.0.5:
15106 - fix an assert trigger that's been plaguing us since the days
15107 of 0.0.2prexx (thanks weasel!)
15108 - retry stream correctly when we fail to connect because of
15109 exit-policy-reject (should try another) or can't-resolve-address
15110 (also should try another, because dns on random internet servers
15112 - when we hup a dirserver and we've *removed* a server from the
15113 approved-routers list, now we remove that server from the
15114 in-memory directories too
15117 Changes in version 0.0.6pre2 - 2004-04-08
15118 o We fixed our base32 implementation. Now it works on all architectures.
15121 Changes in version 0.0.6pre1 - 2004-04-08
15123 - Hidden services and rendezvous points are implemented. Go to
15124 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
15125 hidden services. (This only works via a socks4a proxy such as
15126 Privoxy, and currently it's quite slow.)
15129 Changes in version 0.0.5 - 2004-03-30
15130 [version bump only]
15133 Changes in version 0.0.5rc3 - 2004-03-29
15134 o Install torrc as torrc.sample -- we no longer clobber your
15136 o Re-enable recommendedversion checking (we broke it in rc2, oops)
15137 o Add in a 'notice' log level for things the operator should hear
15138 but that aren't warnings
15141 Changes in version 0.0.5rc2 - 2004-03-29
15142 o Hold socks connection open until reply is flushed (if possible)
15143 o Make exit nodes resolve IPs to IPs immediately, rather than asking
15144 the dns farm to do it.
15145 o Fix c99 aliasing warnings in rephist.c
15146 o Don't include server descriptors that are older than 24 hours in the
15148 o Give socks 'reject' replies their whole 15s to attempt to flush,
15149 rather than seeing the 60s timeout and assuming the flush had failed.
15150 o Clean automake droppings from the cvs repository
15153 Changes in version 0.0.5rc1 - 2004-03-28
15154 o Fix mangled-state bug in directory fetching (was causing sigpipes).
15155 o Only build circuits after we've fetched the directory: clients were
15156 using only the directory servers before they'd fetched a directory.
15157 This also means longer startup time; so it goes.
15158 o Fix an assert trigger where an OP would fail to handshake, and we'd
15159 expect it to have a nickname.
15160 o Work around a tsocks bug: do a socks reject when AP connection dies
15161 early, else tsocks goes into an infinite loop.
15164 Changes in version 0.0.4 - 2004-03-26
15165 o When connecting to a dirserver or OR and the network is down,
15169 Changes in version 0.0.3 - 2004-03-26
15170 o Warn and fail if server chose a nickname with illegal characters
15171 o Port to Solaris and Sparc:
15172 - include missing header fcntl.h
15173 - have autoconf find -lsocket -lnsl automatically
15174 - deal with hardware word alignment
15175 - make uname() work (solaris has a different return convention)
15176 - switch from using signal() to sigaction()
15177 o Preliminary work on reputation system:
15178 - Keep statistics on success/fail of connect attempts; they're published
15179 by kill -USR1 currently.
15180 - Add a RunTesting option to try to learn link state by creating test
15181 circuits, even when SocksPort is off.
15182 - Remove unused open circuits when there are too many.
15185 Changes in version 0.0.2 - 2004-03-19
15186 - Include strlcpy and strlcat for safer string ops
15187 - define INADDR_NONE so we compile (but still not run) on solaris
15190 Changes in version 0.0.2pre27 - 2004-03-14
15192 - Allow internal tor networks (we were rejecting internal IPs,
15193 now we allow them if they're set explicitly).
15194 - And fix a few endian issues.
15197 Changes in version 0.0.2pre26 - 2004-03-14
15199 - If a stream times out after 15s without a connected cell, don't
15200 try that circuit again: try a new one.
15201 - Retry streams at most 4 times. Then give up.
15202 - When a dirserver gets a descriptor from an unknown router, it
15203 logs its fingerprint (so the dirserver operator can choose to
15204 accept it even without mail from the server operator).
15205 - Inform unapproved servers when we reject their descriptors.
15206 - Make tor build on Windows again. It works as a client, who knows
15208 - Clearer instructions in the torrc for how to set up a server.
15209 - Be more efficient about reading fd's when our global token bucket
15210 (used for rate limiting) becomes empty.
15212 - Stop asserting that computers always go forward in time. It's
15214 - When we sent a cell (e.g. destroy) and then marked an OR connection
15215 expired, we might close it before finishing a flush if the other
15216 side isn't reading right then.
15217 - Don't allow dirservers to start if they haven't defined
15218 RecommendedVersions
15219 - We were caching transient dns failures. Oops.
15220 - Prevent servers from publishing an internal IP as their address.
15221 - Address a strcat vulnerability in circuit.c
15224 Changes in version 0.0.2pre25 - 2004-03-04
15226 - Put the OR's IP in its router descriptor, not its fqdn. That way
15227 we'll stop being stalled by gethostbyname for nodes with flaky dns,
15230 - If the user typed in an address that didn't resolve, the server
15234 Changes in version 0.0.2pre24 - 2004-03-03
15236 - Fix an assertion failure in dns.c, where we were trying to dequeue
15237 a pending dns resolve even if it wasn't pending
15238 - Fix a spurious socks5 warning about still trying to write after the
15239 connection is finished.
15240 - Hold certain marked_for_close connections open until they're finished
15241 flushing, rather than losing bytes by closing them too early.
15242 - Correctly report the reason for ending a stream
15243 - Remove some duplicate calls to connection_mark_for_close
15244 - Put switch_id and start_daemon earlier in the boot sequence, so it
15245 will actually try to chdir() to options.DataDirectory
15246 - Make 'make test' exit(1) if a test fails; fix some unit tests
15247 - Make tor fail when you use a config option it doesn't know about,
15248 rather than warn and continue.
15249 - Make --version work
15250 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
15253 Changes in version 0.0.2pre23 - 2004-02-29
15255 - Print a statement when the first circ is finished, so the user
15256 knows it's working.
15257 - If a relay cell is unrecognized at the end of the circuit,
15258 send back a destroy. (So attacks to mutate cells are more
15260 - New config option 'excludenodes' to avoid certain nodes for circuits.
15261 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
15262 so you can collect coredumps there.
15264 - Fix a bug in tls flushing where sometimes data got wedged and
15265 didn't flush until more data got sent. Hopefully this bug was
15266 a big factor in the random delays we were seeing.
15267 - Make 'connected' cells include the resolved IP, so the client
15268 dns cache actually gets populated.
15269 - Disallow changing from ORPort=0 to ORPort>0 on hup.
15270 - When we time-out on a stream and detach from the circuit, send an
15271 end cell down it first.
15272 - Only warn about an unknown router (in exitnodes, entrynodes,
15273 excludenodes) after we've fetched a directory.
15276 Changes in version 0.0.2pre22 - 2004-02-26
15278 - Servers publish less revealing uname information in descriptors.
15279 - More memory tracking and assertions, to crash more usefully when
15281 - If the default torrc isn't there, just use some default defaults.
15282 Plus provide an internal dirservers file if they don't have one.
15283 - When the user tries to use Tor as an http proxy, give them an http
15284 501 failure explaining that we're a socks proxy.
15285 - Dump a new router.desc on hup, to help confused people who change
15286 their exit policies and then wonder why router.desc doesn't reflect
15288 - Clean up the generic tor.sh init script that we ship with.
15290 - If the exit stream is pending on the resolve, and a destroy arrives,
15291 then the stream wasn't getting removed from the pending list. I
15292 think this was the one causing recent server crashes.
15293 - Use a more robust poll on OSX 10.3, since their poll is flaky.
15294 - When it couldn't resolve any dirservers, it was useless from then on.
15295 Now it reloads the RouterFile (or default dirservers) if it has no
15297 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
15298 many users don't even *have* a /usr/local/sbin/.
15301 Changes in version 0.0.2pre21 - 2004-02-18
15303 - There's a ChangeLog file that actually reflects the changelog.
15304 - There's a 'torify' wrapper script, with an accompanying
15305 tor-tsocks.conf, that simplifies the process of using tsocks for
15306 tor. It even has a man page.
15307 - The tor binary gets installed to sbin rather than bin now.
15308 - Retry streams where the connected cell hasn't arrived in 15 seconds
15309 - Clean up exit policy handling -- get the default out of the torrc,
15310 so we can update it without forcing each server operator to fix
15312 - Allow imaps and pop3s in default exit policy
15314 - Prevent picking middleman nodes as the last node in the circuit
15317 Changes in version 0.0.2pre20 - 2004-01-30
15319 - We now have a deb package, and it's in debian unstable. Go to
15320 it, apt-getters. :)
15321 - I've split the TotalBandwidth option into BandwidthRate (how many
15322 bytes per second you want to allow, long-term) and
15323 BandwidthBurst (how many bytes you will allow at once before the cap
15324 kicks in). This better token bucket approach lets you, say, set
15325 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
15326 performance while not exceeding your monthly bandwidth quota.
15327 - Push out a tls record's worth of data once you've got it, rather
15328 than waiting until you've read everything waiting to be read. This
15329 may improve performance by pipelining better. We'll see.
15330 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
15331 from failed circuits (if they haven't been connected yet) and attach
15333 - Expire old streams that haven't managed to connect. Some day we'll
15334 have them reattach to new circuits instead.
15337 - Fix several memory leaks that were causing servers to become bloated
15339 - Fix a few very rare assert triggers. A few more remain.
15340 - Setuid to User _before_ complaining about running as root.
15343 Changes in version 0.0.2pre19 - 2004-01-07
15345 - Fix deadlock condition in dns farm. We were telling a child to die by
15346 closing the parent's file descriptor to him. But newer children were
15347 inheriting the open file descriptor from the parent, and since they
15348 weren't closing it, the socket never closed, so the child never read
15349 eof, so he never knew to exit. Similarly, dns workers were holding
15350 open other sockets, leading to all sorts of chaos.
15351 - New cleaner daemon() code for forking and backgrounding.
15352 - If you log to a file, it now prints an entry at the top of the
15353 logfile so you know it's working.
15354 - The onionskin challenge length was 30 bytes longer than necessary.
15355 - Started to patch up the spec so it's not quite so out of date.
15358 Changes in version 0.0.2pre18 - 2004-01-02
15360 - Fix endian issues with the 'integrity' field in the relay header.
15361 - Fix a potential bug where connections in state
15362 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
15365 Changes in version 0.0.2pre17 - 2003-12-30
15367 - Made --debuglogfile (or any second log file, actually) work.
15368 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
15369 adversary could force us into an infinite loop.
15372 - Each onionskin handshake now includes a hash of the computed key,
15373 to prove the server's identity and help perfect forward secrecy.
15374 - Changed cell size from 256 to 512 bytes (working toward compatibility
15376 - Changed cell length to 2 bytes, and moved it to the relay header.
15377 - Implemented end-to-end integrity checking for the payloads of
15379 - Separated streamid from 'recognized' (otherwise circuits will get
15380 messed up when we try to have streams exit from the middle). We
15381 use the integrity-checking to confirm that a cell is addressed to
15383 - Randomize the initial circid and streamid values, so an adversary who
15384 breaks into a node can't learn how many circuits or streams have
15388 Changes in version 0.0.2pre16 - 2003-12-14
15390 - Fixed a bug that made HUP trigger an assert
15391 - Fixed a bug where a circuit that immediately failed wasn't being
15392 counted as a failed circuit in counting retries.
15395 - Now we close the circuit when we get a truncated cell: otherwise we're
15396 open to an anonymity attack where a bad node in the path truncates
15397 the circuit and then we open streams at him.
15398 - Add port ranges to exit policies
15399 - Add a conservative default exit policy
15400 - Warn if you're running tor as root
15401 - on HUP, retry OR connections and close/rebind listeners
15402 - options.EntryNodes: try these nodes first when picking the first node
15403 - options.ExitNodes: if your best choices happen to include any of
15404 your preferred exit nodes, you choose among just those preferred
15406 - options.ExcludedNodes: nodes that are never picked in path building
15409 Changes in version 0.0.2pre15 - 2003-12-03
15410 o Robustness and bugfixes:
15411 - Sometimes clients would cache incorrect DNS resolves, which would
15412 really screw things up.
15413 - An OP that goes offline would slowly leak all its sockets and stop
15415 - A wide variety of bugfixes in exit node selection, exit policy
15416 handling, and processing pending streams when a new circuit is
15418 - Pick nodes for a path only from those the directory says are up
15419 - Choose randomly from all running dirservers, not always the first one
15420 - Increase allowed http header size for directory fetch.
15421 - Stop writing to stderr (if we're daemonized it will be closed).
15422 - Enable -g always, so cores will be more useful to me.
15423 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
15426 - Wrote a man page. It lists commonly used options.
15429 - Change default loglevel to warn.
15430 - Make PidFile default to null rather than littering in your CWD.
15431 - OnionRouter config option is now obsolete. Instead it just checks
15433 - Moved to a single unified torrc file for both clients and servers.
15436 Changes in version 0.0.2pre14 - 2003-11-29
15437 o Robustness and bugfixes:
15438 - Force the admin to make the DataDirectory himself
15439 - to get ownership/permissions right
15440 - so clients no longer make a DataDirectory and then never use it
15441 - fix bug where a client who was offline for 45 minutes would never
15442 pull down a directory again
15443 - fix (or at least hide really well) the dns assert bug that was
15444 causing server crashes
15445 - warnings and improved robustness wrt clockskew for certs
15446 - use the native daemon(3) to daemonize, when available
15447 - exit if bind() fails
15448 - exit if neither socksport nor orport is defined
15449 - include our own tor_timegm (Win32 doesn't have its own)
15450 - bugfix for win32 with lots of connections
15451 - fix minor bias in PRNG
15452 - make dirserver more robust to corrupt cached directory
15455 - Wrote the design document (woo)
15457 o Circuit building and exit policies:
15458 - Circuits no longer try to use nodes that the directory has told them
15460 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
15461 bitcounts (18.0.0.0/8).
15462 - Make AP connections standby for a circuit if no suitable circuit
15463 exists, rather than failing
15464 - Circuits choose exit node based on addr/port, exit policies, and
15465 which AP connections are standing by
15466 - Bump min pathlen from 2 to 3
15467 - Relay end cells have a payload to describe why the stream ended.
15468 - If the stream failed because of exit policy, try again with a new
15470 - Clients have a dns cache to remember resolved addresses.
15471 - Notice more quickly when we have no working circuits
15474 - APPort is now called SocksPort
15475 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
15477 - RecommendedVersions is now a config variable rather than
15478 hardcoded (for dirservers)
15479 - Reloads config on HUP
15480 - Usage info on -h or --help
15481 - If you set User and Group config vars, it'll setu/gid to them.
15484 Changes in version 0.0.2pre13 - 2003-10-19
15485 o General stability:
15486 - SSL_write no longer fails when it returns WANTWRITE and the number
15487 of bytes in the buf has changed by the next SSL_write call.
15488 - Fix segfault fetching directory when network is down
15489 - Fix a variety of minor memory leaks
15490 - Dirservers reload the fingerprints file on HUP, so I don't have
15491 to take down the network when I approve a new router
15492 - Default server config file has explicit Address line to specify fqdn
15495 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
15496 - Make listener connections not ever alloc bufs
15498 o Autoconf improvements:
15499 - don't clobber an external CFLAGS in ./configure
15500 - Make install now works
15501 - create var/lib/tor on make install
15502 - autocreate a tor.sh initscript to help distribs
15503 - autocreate the torrc and sample-server-torrc with correct paths
15505 o Log files and Daemonizing now work:
15506 - If --DebugLogFile is specified, log to it at -l debug
15507 - If --LogFile is specified, use it instead of commandline
15508 - If --RunAsDaemon is set, tor forks and backgrounds on startup