1 Changes in version 0.2.4.21 - 2014-02-2?
2 o Major features (client security):
3 - When we choose a path for a 3-hop circuit, make sure it contains
4 at least one relay that supports the NTor circuit extension
5 handshake. Otherwise, there is a chance that we're building
6 a circuit that's worth attacking by an adversary who finds
7 breaking 1024-bit crypto doable, and that chance changes the game
8 theory. Implements ticket 9777.
11 - Do not treat streams that fail with reason
12 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
13 since it could also indicate an ENETUNREACH connection error. Fixes
14 part of bug 10777; bugfix on 0.2.4.8-alpha.
16 o Code simplification and refactoring:
17 - Remove data structures which were introduced to implement the
18 CellStatistics option: they are now redundant with the new timestamp
19 field in the regular packed_cell_t data structure, which we did
20 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
23 - Always clear OpenSSL bignums before freeing them -- even bignums
24 that don't contain secrets. Resolves ticket 10793. Patch by
26 - Build without warnings under clang 3.4. (We have some macros that
27 define static functions only some of which will get used later in
28 the module. Starting with clang 3.4, these give a warning unless the
29 unused attribute is set on them.) Resolves ticket 10904.
30 - Update geoip and geoip6 files to the February 7 2014 Maxmind
31 GeoLite2 Country database.
34 - Set the listen() backlog limit to the largest actually supported
35 on the system, not to the value in a header file. Fixes bug 9716;
36 bugfix on every released Tor.
37 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
38 exit node as a NOROUTE error, not an INTERNAL error, since they
39 can apparently happen when trying to connect to the wrong sort
40 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
41 - Fix build warnings about missing "a2x" comment when building the
42 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
43 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
44 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
45 not entirely remove it from the connection lists. Fixes bug 9602;
46 bugfix on 0.2.4.4-alpha.
47 - Fix a segmentation fault in our benchmark code when running with
48 Fedora's OpenSSL package, or any other OpenSSL that provides
49 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
50 - Turn "circuit handshake stats since last time" log messages into a
51 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
53 o Documentation fixes:
54 - Document that all but one DirPort entry must have the NoAdvertise
55 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
58 Changes in version 0.2.4.20 - 2013-12-22
59 Tor 0.2.4.20 fixes potentially poor random number generation for users
60 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
61 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
62 and 4) have no state file in their DataDirectory (as would happen on
63 first start). Users who generated relay or hidden service identity
64 keys in such a situation should discard them and generate new ones.
66 This release also fixes a logic error that caused Tor clients to build
67 many more preemptive circuits than they actually need.
70 - Do not allow OpenSSL engines to replace the PRNG, even when
71 HardwareAccel is set. The only default builtin PRNG engine uses
72 the Intel RDRAND instruction to replace the entire PRNG, and
73 ignores all attempts to seed it with more entropy. That's
74 cryptographically stupid: the right response to a new alleged
75 entropy source is never to discard all previously used entropy
76 sources. Fixes bug 10402; works around behavior introduced in
77 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
79 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
80 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
81 - Avoid launching spurious extra circuits when a stream is pending.
82 This fixes a bug where any circuit that _wasn't_ unusable for new
83 streams would be treated as if it were, causing extra circuits to
84 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
87 - Avoid a crash bug when starting with a corrupted microdescriptor
88 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
89 - If we fail to dump a previously cached microdescriptor to disk, avoid
90 freeing duplicate data later on. Fixes bug 10423; bugfix on
91 0.2.4.13-alpha. Spotted by "bobnomnom".
94 Changes in version 0.2.4.19 - 2013-12-11
95 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
96 (1986-2013). Aaron worked on diverse projects including helping to guide
97 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
98 transparency to the U.S government's PACER documents, and contributing
99 design and development for Tor and Tor2Web. Aaron was one of the latest
100 martyrs in our collective fight for civil liberties and human rights,
101 and his death is all the more painful because he was one of us.
103 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
104 a new circuit handshake and link encryption that use ECC to provide
105 better security and efficiency; makes relays better manage circuit
106 creation requests; uses "directory guards" to reduce client enumeration
107 risks; makes bridges collect and report statistics about the pluggable
108 transports they support; cleans up and improves our geoip database;
109 gets much closer to IPv6 support for clients, bridges, and relays; makes
110 directory authorities use measured bandwidths rather than advertised
111 ones when computing flags and thresholds; disables client-side DNS
112 caching to reduce tracking risks; and fixes a big bug in bridge
113 reachability testing. This release introduces two new design
114 abstractions in the code: a new "channel" abstraction between circuits
115 and or_connections to allow for implementing alternate relay-to-relay
116 transports, and a new "circuitmux" abstraction storing the queue of
117 circuits for a channel. The release also includes many stability,
118 security, and privacy fixes.
121 Changes in version 0.2.4.18-rc - 2013-11-16
122 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
123 series. It takes a variety of fixes from the 0.2.5.x branch to improve
124 stability, performance, and better handling of edge cases.
127 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
128 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
129 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
130 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
131 them to solve bug 6033.)
134 - No longer stop reading or writing on cpuworker connections when
135 our rate limiting buckets go empty. Now we should handle circuit
136 handshake requests more promptly. Resolves bug 9731.
137 - If we are unable to save a microdescriptor to the journal, do not
138 drop it from memory and then reattempt downloading it. Fixes bug
139 9645; bugfix on 0.2.2.6-alpha.
140 - Stop trying to bootstrap all our directory information from
141 only our first guard. Discovered while fixing bug 9946; bugfix
143 - The new channel code sometimes lost track of in-progress circuits,
144 causing long-running clients to stop building new circuits. The
145 fix is to always call circuit_n_chan_done(chan, 0) from
146 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
148 o Minor bugfixes (on 0.2.4.x):
149 - Correctly log long IPv6 exit policies, instead of truncating them
150 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
151 - Our default TLS ecdhe groups were backwards: we meant to be using
152 P224 for relays (for performance win) and P256 for bridges (since
153 it is more common in the wild). Instead we had it backwards. After
154 reconsideration, we decided that the default should be P256 on all
155 hosts, since its security is probably better, and since P224 is
156 reportedly used quite little in the wild. Found by "skruffy" on
157 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
158 - Free directory authority certificate download statuses on exit
159 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
161 o Minor bugfixes (on 0.2.3.x and earlier):
162 - If the guard we choose first doesn't answer, we would try the
163 second guard, but once we connected to the second guard we would
164 abandon it and retry the first one, slowing down bootstrapping.
165 The fix is to treat all our initially chosen guards as acceptable
166 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
167 - Fix an assertion failure that would occur when disabling the
168 ORPort setting on a running Tor process while accounting was
169 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
170 - When examining the list of network interfaces to find our address,
171 do not consider non-running or disabled network interfaces. Fixes
172 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
173 - Avoid an off-by-one error when checking buffer boundaries when
174 formatting the exit status of a pluggable transport helper.
175 This is probably not an exploitable bug, but better safe than
176 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
179 o Minor features (protecting client timestamps):
180 - Clients no longer send timestamps in their NETINFO cells. These were
181 not used for anything, and they provided one small way for clients
182 to be distinguished from each other as they moved from network to
183 network or behind NAT. Implements part of proposal 222.
184 - Clients now round timestamps in INTRODUCE cells down to the nearest
185 10 minutes. If a new Support022HiddenServices option is set to 0, or
186 if it's set to "auto" and the feature is disabled in the consensus,
187 the timestamp is sent as 0 instead. Implements part of proposal 222.
188 - Stop sending timestamps in AUTHENTICATE cells. This is not such
189 a big deal from a security point of view, but it achieves no actual
190 good purpose, and isn't needed. Implements part of proposal 222.
191 - Reduce down accuracy of timestamps in hidden service descriptors.
192 Implements part of proposal 222.
194 o Minor features (other):
195 - Improve the circuit queue out-of-memory handler. Previously, when
196 we ran low on memory, we'd close whichever circuits had the most
197 queued cells. Now, we close those that have the *oldest* queued
198 cells, on the theory that those are most responsible for us
199 running low on memory. Based on analysis from a forthcoming paper
200 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
201 - Generate bootstrapping status update events correctly when fetching
202 microdescriptors. Fixes bug 9927.
203 - Update to the October 2 2013 Maxmind GeoLite Country database.
205 o Documentation fixes:
206 - Clarify the usage and risks of setting the ContactInfo torrc line
207 for your relay or bridge. Resolves ticket 9854.
208 - Add anchors to the manpage so we can link to the html version of
209 the documentation for specific options. Resolves ticket 9866.
210 - Replace remaining references to DirServer in man page and
211 log entries. Resolves ticket 10124.
214 Changes in version 0.2.4.17-rc - 2013-09-05
215 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
216 series. It adds an emergency step to help us tolerate the massive
217 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
218 circuit-level handshakes now effectively jump the queue compared to
219 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
220 big bug hindering bridge reachability tests.
223 - Relays now process the new "NTor" circuit-level handshake requests
224 with higher priority than the old "TAP" circuit-level handshake
225 requests. We still process some TAP requests to not totally starve
226 0.2.3 clients when NTor becomes popular. A new consensus parameter
227 "NumNTorsPerTAP" lets us tune the balance later if we need to.
228 Implements ticket 9574.
231 - If the circuit build timeout logic is disabled (via the consensus,
232 or because we are an authority), then don't build testing circuits.
233 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
234 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
235 previously they did not, which prevented them from receiving
236 successful connections from relays for self-test or bandwidth
237 testing. Also, when a relay is extending a circuit to a bridge,
238 it needs to send a NETINFO cell, even when the bridge hasn't sent
239 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
240 - If the time to download the next old-style networkstatus is in
241 the future, do not decline to consider whether to download the
242 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
246 - Avoid double-closing the listener socket in our socketpair()
247 replacement (used on Windows) in the case where the addresses on
248 our opened sockets don't match what we expected. Fixes bug 9400;
249 bugfix on 0.0.2pre7. Found by Coverity.
251 o Minor fixes (config options):
252 - Avoid overflows when the user sets MaxCircuitDirtiness to a
253 ridiculously high value, by imposing a (ridiculously high) 30-day
254 maximum on MaxCircuitDirtiness.
255 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
256 message is logged at notice, not at info.
257 - Warn and fail if a server is configured not to advertise any
258 ORPorts at all. (We need *something* to put in our descriptor,
259 or we just won't work.)
262 - Track how many "TAP" and "NTor" circuit handshake requests we get,
263 and how many we complete, and log it every hour to help relay
264 operators follow trends in network load. Addresses ticket 9658.
265 - Update to the August 7 2013 Maxmind GeoLite Country database.
268 Changes in version 0.2.4.16-rc - 2013-08-10
269 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
270 series. It fixes several crash bugs in the 0.2.4 branch.
273 - Fix a bug in the voting algorithm that could yield incorrect results
274 when a non-naming authority declared too many flags. Fixes bug 9200;
275 bugfix on 0.2.0.3-alpha.
276 - Fix an uninitialized read that could in some cases lead to a remote
277 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
278 Anybody running a hidden service on the experimental 0.2.4.x
279 branch should upgrade. (This is, so far as we know, unrelated to
281 - Avoid an assertion failure when processing DNS replies without the
282 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
283 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
284 0.2.4.15-rc. Found by stem integration tests.
287 - Fix an invalid memory read that occured when a pluggable
288 transport proxy failed its configuration protocol.
289 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
290 - When evaluating whether to use a connection that we haven't
291 decided is canonical using a recent link protocol version,
292 decide that it's canonical only if it used address _does_
293 match the desired address. Fixes bug 9309; bugfix on
294 0.2.4.4-alpha. Reported by skruffy.
295 - Make the default behavior of NumDirectoryGuards be to track
296 NumEntryGuards. Now a user who changes only NumEntryGuards will get
297 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
298 - Fix a spurious compilation warning with some older versions of
299 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
302 - Update to the July 3 2013 Maxmind GeoLite Country database.
305 Changes in version 0.2.4.15-rc - 2013-07-01
306 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
307 series. It fixes a few smaller bugs, but generally appears stable.
308 Please test it and let us know whether it is!
311 - When receiving a new configuration file via the control port's
312 LOADCONF command, do not treat the defaults file as absent.
313 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
316 - Issue a warning when running with the bufferevents backend enabled.
317 It's still not stable, and people should know that they're likely
318 to hit unexpected problems. Closes ticket 9147.
321 Changes in version 0.2.4.14-alpha - 2013-06-18
322 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
323 present in 0.2.4.13-alpha.
326 - When we have too much memory queued in circuits (according to a new
327 MaxMemInCellQueues option), close the circuits consuming the most
328 memory. This prevents us from running out of memory as a relay if
329 circuits fill up faster than they can be drained. Fixes bug 9063;
330 bugfix on the 54th commit of Tor. This bug is a further fix beyond
331 bug 6252, whose fix was merged into 0.2.3.21-rc.
333 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
334 where we tried to solve this issue simply by imposing an upper limit
335 on the number of queued cells for a single circuit. That approach
336 proved to be problematic, since there are ways to provoke clients to
337 send a number of cells in excess of any such reasonable limit. Fixes
338 bug 9072; bugfix on 0.2.4.13-alpha.
340 - Limit hidden service descriptors to at most ten introduction
341 points, to slow one kind of guard enumeration. Fixes bug 9002;
342 bugfix on 0.1.1.11-alpha.
345 Changes in version 0.2.4.13-alpha - 2013-06-14
346 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
347 vulnerabilities, makes socks5 username/password circuit isolation
348 actually actually work (this time for sure!), and cleans up a bunch
349 of other issues in preparation for a release candidate.
351 o Major bugfixes (robustness):
352 - Close any circuit that has too many cells queued on it. Fixes
353 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
354 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
355 - Prevent the get_freelists() function from running off the end of
356 the list of freelists if it somehow gets an unrecognized
357 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
359 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
360 when an exit connection with optimistic data succeeds immediately
361 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
363 - Fix a directory authority crash bug when building a consensus
364 using an older consensus as its basis. Fixes bug 8833. Bugfix
368 - Avoid a memory leak where we would leak a consensus body when we
369 find that a consensus which we couldn't previously verify due to
370 missing certificates is now verifiable. Fixes bug 8719; bugfix
372 - We used to always request authority certificates by identity digest,
373 meaning we'd get the newest one even when we wanted one with a
374 different signing key. Then we would complain about being given
375 a certificate we already had, and never get the one we really
376 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
377 resource to request the one we want. Fixes bug 5595; bugfix on
379 - Follow the socks5 protocol when offering username/password
380 authentication. The fix for bug 8117 exposed this bug, and it
381 turns out real-world applications like Pidgin do care. Bugfix on
382 0.2.3.2-alpha; fixes bug 8879.
383 - Prevent failures on Windows Vista and later when rebuilding the
384 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
385 bugfix on 0.2.4.12-alpha.
388 - Fix an impossible buffer overrun in the AES unit tests. Fixes
389 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
390 - If for some reason we fail to write a microdescriptor while
391 rebuilding the cache, do not let the annotations from that
392 microdescriptor linger in the cache file, and do not let the
393 microdescriptor stay recorded as present in its old location.
394 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
395 - Fix a memory leak that would occur whenever a configuration
396 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
397 - Paste the description for PathBias parameters from the man
398 page into or.h, so the code documents them too. Fixes bug 7982;
399 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
400 - Relays now treat a changed IPv6 ORPort as sufficient reason to
401 publish an updated descriptor. Fixes bug 6026; bugfix on
403 - When launching a resolve request on behalf of an AF_UNIX control
404 socket, omit the address field of the new entry connection, used in
405 subsequent controller events, rather than letting tor_dup_addr()
406 set it to "<unknown address type>". Fixes bug 8639; bugfix on
409 o Minor bugfixes (log messages):
410 - Fix a scaling issue in the path bias accounting code that
411 resulted in "Bug:" log messages from either
412 pathbias_scale_close_rates() or pathbias_count_build_success().
413 This represents a bugfix on a previous bugfix: the original fix
414 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
416 - Give a less useless error message when the user asks for an IPv4
417 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
421 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
422 to tolerate bug 8093 for now.
423 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
424 in directory authority votes to describe whether they have enough
425 measured bandwidths to ignore advertised (relay descriptor)
426 bandwidth claims. Resolves ticket 8711.
427 - Update to the June 5 2013 Maxmind GeoLite Country database.
429 o Removed documentation:
430 - Remove some of the older contents of doc/ as obsolete; move others
431 to torspec.git. Fixes bug 8965.
433 o Code simplification and refactoring:
434 - Avoid using character buffers when constructing most directory
435 objects: this approach was unwieldy and error-prone. Instead,
436 build smartlists of strings, and concatenate them when done.
439 Changes in version 0.2.4.12-alpha - 2013-04-18
440 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
441 process for lengthening the guard rotation period, makes directory
442 authority opinions in the consensus a bit less gameable, makes socks5
443 username/password circuit isolation actually work, and fixes a wide
444 variety of other issues.
447 - Raise the default time that a client keeps an entry guard from
448 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
449 2012 paper. (We would make it even longer, but we need better client
450 load balancing first.) Also, make the guard lifetime controllable
451 via a new GuardLifetime torrc option and a GuardLifetime consensus
452 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
453 - Directory authorities now prefer using measured bandwidths to
454 advertised ones when computing flags and thresholds. Resolves
456 - Directory authorities that have more than a threshold number
457 of relays with measured bandwidths now treat relays with unmeasured
458 bandwidths as having bandwidth 0. Resolves ticket 8435.
460 o Major bugfixes (assert / resource use):
461 - Avoid a bug where our response to TLS renegotiation under certain
462 network conditions could lead to a busy-loop, with 100% CPU
463 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
464 - Avoid an assertion when we discover that we'd like to write a cell
465 onto a closing connection: just discard the cell. Fixes another
466 case of bug 7350; bugfix on 0.2.4.4-alpha.
468 o Major bugfixes (client-side privacy):
469 - When we mark a circuit as unusable for new circuits, have it
470 continue to be unusable for new circuits even if MaxCircuitDirtiness
471 is increased too much at the wrong time, or the system clock jumps
472 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
473 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
474 which have resolved to internal addresses") is set, apply that
475 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
476 - When an exit relay rejects a stream with reason "exit policy", but
477 we only know an exit policy summary (e.g. from the microdesc
478 consensus) for it, do not mark the relay as useless for all exiting.
479 Instead, mark just the circuit as unsuitable for that particular
480 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
481 - Allow applications to get proper stream isolation with
482 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
483 username/password authentication also offer "no authentication". Tor
484 had previously preferred "no authentication", so the applications
485 never actually sent Tor their auth details. Now Tor selects
486 username/password authentication if it's offered. You can disable
487 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
488 bug 8117; bugfix on 0.2.3.3-alpha.
490 o Major bugfixes (other):
491 - When unable to find any working directory nodes to use as a
492 directory guard, give up rather than adding the same non-working
493 nodes to the directory guard list over and over. Fixes bug 8231;
494 bugfix on 0.2.4.8-alpha.
497 - Reject as invalid most directory objects containing a NUL.
498 Belt-and-suspender fix for bug 8037.
499 - In our testsuite, create temporary directories with a bit more
500 entropy in their name to make name collisions less likely. Fixes
502 - Add CACHED keyword to ADDRMAP events in the control protocol
503 to indicate whether a DNS result will be cached or not. Resolves
505 - Update to the April 3 2013 Maxmind GeoLite Country database.
507 o Minor features (build):
508 - Detect and reject attempts to build Tor with threading support
509 when OpenSSL has been compiled without threading support.
511 - Clarify that when autoconf is checking for nacl, it is checking
512 specifically for nacl with a fast curve25519 implementation.
514 - Warn if building on a platform with an unsigned time_t: there
515 are too many places where Tor currently assumes that time_t can
516 hold negative values. We'd like to fix them all, but probably
519 o Minor bugfixes (build):
520 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
521 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
522 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
523 - Add the old src/or/micro-revision.i filename to CLEANFILES.
524 On the off chance that somebody has one, it will go away as soon
525 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
526 - Build Tor correctly on 32-bit platforms where the compiler can build
527 but not run code using the "uint128_t" construction. Fixes bug 8587;
528 bugfix on 0.2.4.8-alpha.
529 - Fix compilation warning with some versions of clang that would
530 prefer the -Wswitch-enum compiler flag to warn about switch
531 statements with missing enum values, even if those switch
532 statements have a "default:" statement. Fixes bug 8598; bugfix
535 o Minor bugfixes (protocol):
536 - Fix the handling of a TRUNCATE cell when it arrives while the
537 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
538 - Fix a misframing issue when reading the version numbers in a
539 VERSIONS cell. Previously we would recognize [00 01 00 02] as
540 'version 1, version 2, and version 0x100', when it should have
541 only included versions 1 and 2. Fixes bug 8059; bugfix on
542 0.2.0.10-alpha. Reported pseudonymously.
543 - Make the format and order of STREAM events for DNS lookups
544 consistent among the various ways to launch DNS lookups. Fixes
545 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
546 - Correct our check for which versions of Tor support the EXTEND2
547 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
548 later, when support was really added in version 0.2.4.8-alpha.
549 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
551 o Minor bugfixes (other):
552 - Correctly store microdescriptors and extrainfo descriptors with
553 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
554 Bug reported by "cypherpunks".
555 - Increase the width of the field used to remember a connection's
556 link protocol version to two bytes. Harmless for now, since the
557 only currently recognized versions are one byte long. Reported
558 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
559 - If the state file's path bias counts are invalid (presumably from a
560 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
561 additional checks and log messages to the scaling of Path Bias
562 counts, in case there still are remaining issues with scaling.
563 Should help resolve bug 8235.
564 - Eliminate several instances where we use "Nickname=ID" to refer to
565 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
566 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
567 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
569 o Minor bugfixes (syscalls):
570 - Always check the return values of functions fcntl() and
571 setsockopt(). We don't believe these are ever actually failing in
572 practice, but better safe than sorry. Also, checking these return
573 values should please analysis tools like Coverity. Patch from
574 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
575 - Use direct writes rather than stdio when building microdescriptor
576 caches, in an attempt to mitigate bug 8031, or at least make it
579 o Minor bugfixes (config):
580 - When rejecting a configuration because we were unable to parse a
581 quoted string, log an actual error message. Fixes bug 7950; bugfix
583 - Behave correctly when the user disables LearnCircuitBuildTimeout
584 but doesn't tell us what they would like the timeout to be. Fixes
585 bug 6304; bugfix on 0.2.2.14-alpha.
586 - When autodetecting the number of CPUs, use the number of available
587 CPUs in preference to the number of configured CPUs. Inform the
588 user if this reduces the number of available CPUs. Fixes bug 8002;
589 bugfix on 0.2.3.1-alpha.
590 - Make it an error when you set EntryNodes but disable UseGuardNodes,
591 since it will (surprisingly to some users) ignore EntryNodes. Fixes
592 bug 8180; bugfix on 0.2.3.11-alpha.
593 - Allow TestingTorNetworks to override the 4096-byte minimum for
594 the Fast threshold. Otherwise they can't bootstrap until they've
595 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
596 - Fix some logic errors when the user manually overrides the
597 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
600 o Minor bugfixes (log messages to help diagnose bugs):
601 - If we fail to free a microdescriptor because of bug 7164, log
602 the filename and line number from which we tried to free it.
603 - Add another diagnostic to the heartbeat message: track and log
604 overhead that TLS is adding to the data we write. If this is
605 high, we are sending too little data to SSL_write at a time.
606 Diagnostic for bug 7707.
607 - Add more detail to a log message about relaxed timeouts, to help
609 - Warn more aggressively when flushing microdescriptors to a
610 microdescriptor cache fails, in an attempt to mitigate bug 8031,
611 or at least make it more diagnosable.
612 - Improve debugging output to help track down bug 8185 ("Bug:
613 outgoing relay cell has n_chan==NULL. Dropping.")
614 - Log the purpose of a path-bias testing circuit correctly.
615 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
617 o Minor bugfixes (0.2.4.x log messages that were too noisy):
618 - Don't attempt to relax the timeout of already opened 1-hop circuits.
619 They might never timeout. This should eliminate some/all cases of
620 the relaxed timeout log message.
621 - Use circuit creation time for network liveness evaluation. This
622 should eliminate warning log messages about liveness caused
623 by changes in timeout evaluation. Fixes bug 6572; bugfix on
625 - Reduce a path bias length check from notice to info. The message
626 is triggered when creating controller circuits. Fixes bug 8196;
627 bugfix on 0.2.4.8-alpha.
628 - Fix a path state issue that triggered a notice during relay startup.
629 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
630 - Reduce occurrences of warns about circuit purpose in
631 connection_ap_expire_building(). Fixes bug 8477; bugfix on
634 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
635 - If we encounter a write failure on a SOCKS connection before we
636 finish our SOCKS handshake, don't warn that we closed the
637 connection before we could send a SOCKS reply. Fixes bug 8427;
638 bugfix on 0.1.0.1-rc.
639 - Correctly recognize that [::1] is a loopback address. Fixes
640 bug 8377; bugfix on 0.2.1.3-alpha.
641 - Fix a directory authority warn caused when we have a large amount
642 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
643 - Don't log inappropriate heartbeat messages when hibernating: a
644 hibernating node is _expected_ to drop out of the consensus,
645 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
646 bugfix on 0.2.3.1-alpha.
647 - Don't complain about bootstrapping problems while hibernating.
648 These complaints reflect a general code problem, but not one
649 with any problematic effects (no connections are actually
650 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
652 o Documentation fixes:
653 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
654 names match. Fixes bug 7768.
655 - Make the torify manpage no longer refer to tsocks; torify hasn't
656 supported tsocks since 0.2.3.14-alpha.
657 - Make the tor manpage no longer reference tsocks.
658 - Fix the GeoIPExcludeUnknown documentation to refer to
659 ExcludeExitNodes rather than the currently nonexistent
660 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
663 - The tor-tsocks.conf is no longer distributed or installed. We
664 recommend that tsocks users use torsocks instead. Resolves
668 Changes in version 0.2.4.11-alpha - 2013-03-11
669 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
670 more robust, makes hidden service authentication work again, and
671 resolves a DPI fingerprint for Tor's SSL transport.
673 o Major features (directory authorities):
674 - Directory authorities now support a new consensus method (17)
675 where they cap the published bandwidth of servers for which
676 insufficient bandwidth measurements exist. Fixes part of bug 2286.
677 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
678 serve any v2 directory information. Now we can test disabling the
679 old deprecated v2 directory format, and see whether doing so has
680 any effect on network load. Begins to fix bug 6783.
681 - Directory authorities now include inside each vote a statement of
682 the performance thresholds they used when assigning flags.
683 Implements ticket 8151.
685 o Major bugfixes (directory authorities):
686 - Stop marking every relay as having been down for one hour every
687 time we restart a directory authority. These artificial downtimes
688 were messing with our Stable and Guard flag calculations. Fixes
689 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
691 o Major bugfixes (hidden services):
692 - Allow hidden service authentication to succeed again. When we
693 refactored the hidden service introduction code back
694 in 0.2.4.1-alpha, we didn't update the code that checks
695 whether authentication information is present, causing all
696 authentication checks to return "false". Fix for bug 8207; bugfix
697 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
699 o Minor features (relays, bridges):
700 - Make bridge relays check once a minute for whether their IP
701 address has changed, rather than only every 15 minutes. Resolves
703 - Refactor resolve_my_address() so it returns the method by which we
704 decided our public IP address (explicitly configured, resolved from
705 explicit hostname, guessed from interfaces, learned by gethostname).
706 Now we can provide more helpful log messages when a relay guesses
707 its IP address incorrectly (e.g. due to unexpected lines in
708 /etc/hosts). Resolves ticket 2267.
709 - Teach bridge-using clients to avoid 0.2.2 bridges when making
710 microdescriptor-related dir requests, and only fall back to normal
711 descriptors if none of their bridges can handle microdescriptors
712 (as opposed to the fix in ticket 4013, which caused them to fall
713 back to normal descriptors if *any* of their bridges preferred
714 them). Resolves ticket 4994.
715 - Randomize the lifetime of our SSL link certificate, so censors can't
716 use the static value for filtering Tor flows. Resolves ticket 8443;
717 related to ticket 4014 which was included in 0.2.2.33.
719 o Minor features (portability):
720 - Tweak the curve25519-donna*.c implementations to tolerate systems
721 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
722 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
723 the signs of types during autoconf. This is better than our old
724 approach, which didn't work when cross-compiling.
725 - Detect the sign of enum values, rather than assuming that MSC is the
726 only compiler where enum types are all signed. Fixes bug 7727;
727 bugfix on 0.2.4.10-alpha.
729 o Minor features (other):
730 - Say "KBytes" rather than "KB" in the man page (for various values
731 of K), to further reduce confusion about whether Tor counts in
732 units of memory or fractions of units of memory. Resolves ticket 7054.
733 - Clear the high bit on curve25519 public keys before passing them to
734 our backend, in case we ever wind up using a backend that doesn't do
735 so itself. If we used such a backend, and *didn't* clear the high bit,
736 we could wind up in a situation where users with such backends would
737 be distinguishable from users without. Fixes bug 8121; bugfix on
739 - Update to the March 6 2013 Maxmind GeoLite Country database.
741 o Minor bugfixes (clients):
742 - When we receive a RELAY_END cell with the reason DONE, or with no
743 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
744 status as "connection refused". Previously we reported these cases
745 as success but then immediately closed the connection. Fixes bug
746 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
747 - Downgrade an assertion in connection_ap_expire_beginning to an
748 LD_BUG message. The fix for bug 8024 should prevent this message
749 from displaying, but just in case, a warn that we can diagnose
750 is better than more assert crashes. Fixes bug 8065; bugfix on
752 - Lower path use bias thresholds to .80 for notice and .60 for warn.
753 Also make the rate limiting flags for the path use bias log messages
754 independent from the original path bias flags. Fixes bug 8161;
755 bugfix on 0.2.4.10-alpha.
757 o Minor bugfixes (relays):
758 - Stop trying to resolve our hostname so often (e.g. every time we
759 think about doing a directory fetch). Now we reuse the cached
760 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
761 and 2410 (bugfix on 0.1.2.2-alpha).
762 - Stop sending a stray "(null)" in some cases for the server status
763 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
765 - When choosing which stream on a formerly stalled circuit to wake
766 first, make better use of the platform's weak RNG. Previously,
767 we had been using the % ("modulo") operator to try to generate a
768 1/N chance of picking each stream, but this behaves badly with
769 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
771 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
772 Irix's random() only return 15 bits; Solaris's random() returns more
773 bits but its RAND_MAX says it only returns 15, and so on. Motivated
774 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
776 o Minor bugfixes (directory authorities):
777 - Directory authorities now use less space when formatting identical
778 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
781 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
782 - Avoid leaking memory if we fail to compute a consensus signature
783 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
784 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
786 - Fix a memory leak during safe-cookie controller authentication.
787 Bugfix on 0.2.3.13-alpha.
788 - Avoid memory leak of IPv6 policy content if we fail to format it into
789 a router descriptor. Bugfix on 0.2.4.7-alpha.
791 o Minor bugfixes (other code correctness issues):
792 - Avoid a crash if we fail to generate an extrainfo descriptor.
793 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
795 - When detecting the largest possible file descriptor (in order to
796 close all file descriptors when launching a new program), actually
797 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
798 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
800 - Fix a copy-and-paste error when adding a missing A1 to a routerset
801 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
802 Bugfix on 0.2.4.10-alpha.
803 - Fix an impossible-to-trigger integer overflow when estimating how
804 long our onionskin queue would take. (This overflow would require us
805 to accept 4 million onionskins before processing 100 of them.) Fixes
806 bug 8210; bugfix on 0.2.4.10-alpha.
808 o Code simplification and refactoring:
809 - Add a wrapper function for the common "log a message with a
813 Changes in version 0.2.4.10-alpha - 2013-02-04
814 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
815 certain attacks that flood the network with relays; changes the queue
816 for circuit create requests from a sized-based limit to a time-based
817 limit; resumes building with MSVC on Windows; and fixes a wide variety
820 o Major bugfixes (directory authority):
821 - When computing directory thresholds, ignore any rejected-as-sybil
822 nodes during the computation so that they can't influence Fast,
823 Guard, etc. (We should have done this for proposal 109.) Fixes
825 - When marking a node as a likely sybil, reset its uptime metrics
826 to zero, so that it cannot time towards getting marked as Guard,
827 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
831 - When a TLS write is partially successful but incomplete, remember
832 that the flushed part has been flushed, and notice that bytes were
833 actually written. Reported and fixed pseudonymously. Fixes bug
834 7708; bugfix on Tor 0.1.0.5-rc.
835 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
836 ID: these could be used to create unexpected streams and circuits
837 which would count as "present" to some parts of Tor but "absent"
838 to others, leading to zombie circuits and streams or to a bandwidth
839 denial-of-service. Fixes bug 7889; bugfix on every released version
840 of Tor. Reported by "oftc_must_be_destroyed".
841 - Rename all macros in our local copy of queue.h to begin with "TOR_".
842 This change seems the only good way to permanently prevent conflicts
843 with queue.h on various operating systems. Fixes bug 8107; bugfix
846 o Major features (relay):
847 - Instead of limiting the number of queued onionskins (aka circuit
848 create requests) to a fixed, hard-to-configure number, we limit
849 the size of the queue based on how many we expect to be able to
850 process in a given amount of time. We estimate the time it will
851 take to process an onionskin based on average processing time
852 of previous onionskins. Closes ticket 7291. You'll never have to
853 configure MaxOnionsPending again.
855 o Major features (portability):
856 - Resume building correctly with MSVC and Makefile.nmake. This patch
857 resolves numerous bugs and fixes reported by ultramage, including
858 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
859 - Make the ntor and curve25519 code build correctly with MSVC.
860 Fix on 0.2.4.8-alpha.
863 - When directory authorities are computing thresholds for flags,
864 never let the threshold for the Fast flag fall below 4096
865 bytes. Also, do not consider nodes with extremely low bandwidths
866 when deciding thresholds for various directory flags. This change
867 should raise our threshold for Fast relays, possibly in turn
868 improving overall network performance; see ticket 1854. Resolves
870 - The Tor client now ignores sub-domain components of a .onion
871 address. This change makes HTTP "virtual" hosting
872 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
873 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
874 hosted on the same hidden service. Implements proposal 204.
875 - We compute the overhead from passing onionskins back and forth to
876 cpuworkers, and report it when dumping statistics in response to
877 SIGUSR1. Supports ticket 7291.
879 o Minor features (path selection):
880 - When deciding whether we have enough descriptors to build circuits,
881 instead of looking at raw relay counts, look at which fraction
882 of (bandwidth-weighted) paths we're able to build. This approach
883 keeps clients from building circuits if their paths are likely to
884 stand out statistically. The default fraction of paths needed is
885 taken from the consensus directory; you can override it with the
886 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
887 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
888 and we have GeoIP information, also exclude all nodes with unknown
889 countries "??" and "A1". This behavior is controlled by the
890 new GeoIPExcludeUnknown option: you can make such nodes always
891 excluded with "GeoIPExcludeUnknown 1", and disable the feature
892 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
893 gets you the default behavior. Implements feature 7706.
894 - Path Use Bias: Perform separate accounting for successful circuit
895 use. Keep separate statistics on stream attempt rates versus stream
896 success rates for each guard. Provide configurable thresholds to
897 determine when to emit log messages or disable use of guards that
898 fail too many stream attempts. Resolves ticket 7802.
900 o Minor features (log messages):
901 - When learning a fingerprint for a bridge, log its corresponding
902 transport type. Implements ticket 7896.
903 - Improve the log message when "Bug/attack: unexpected sendme cell
904 from client" occurs, to help us track bug 8093.
907 - Remove a couple of extraneous semicolons that were upsetting the
908 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
909 bugfix on 0.2.2.1-alpha.
910 - Remove a source of rounding error during path bias count scaling;
911 don't count cannibalized circuits as used for path bias until we
912 actually try to use them; and fix a circuit_package_relay_cell()
913 warning message about n_chan==NULL. Fixes bug 7802.
914 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
915 actually link against nacl when we're configured to use it. Fixes
916 bug 7972; bugfix on 0.2.4.8-alpha.
917 - Compile correctly with the --disable-curve25519 option. Fixes
918 bug 8153; bugfix on 0.2.4.8-alpha.
920 o Build improvements:
921 - Do not report status verbosely from autogen.sh unless the -v flag
922 is specified. Fixes issue 4664. Patch from Onizuka.
923 - Replace all calls to snprintf() outside of src/ext with
924 tor_snprintf(). Also remove the #define to replace snprintf with
925 _snprintf on Windows; they have different semantics, and all of
926 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
927 - Try to detect if we are ever building on a platform where
928 memset(...,0,...) does not set the value of a double to 0.0. Such
929 platforms are permitted by the C standard, though in practice
930 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
931 currently support them, but it's better to detect them and fail
932 than to perform erroneously.
935 - Stop exporting estimates of v2 and v3 directory traffic shares
936 in extrainfo documents. They were unneeded and sometimes inaccurate.
937 Also stop exporting any v2 directory request statistics. Resolves
939 - Drop support for detecting and warning about versions of Libevent
940 before 1.3e. Nothing reasonable ships with them any longer;
941 warning the user about them shouldn't be needed. Resolves ticket
944 o Code simplifications and refactoring:
945 - Rename "isin" functions to "contains", for grammar. Resolves
947 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
948 with the natural logarithm function from the system libm. Resolves
952 Changes in version 0.2.4.9-alpha - 2013-01-15
953 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
957 - Fix backward compatibility logic when receiving an embedded ntor
958 handshake tunneled in a CREATE cell. This clears up the "Bug:
959 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
963 Changes in version 0.2.4.8-alpha - 2013-01-14
964 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
965 risks, adds a new stronger and faster circuit handshake, and offers
966 stronger and faster link encryption when both sides support it.
969 - Preliminary support for directory guards (proposal 207): when
970 possible, clients now use their entry guards for non-anonymous
971 directory requests. This can help prevent client enumeration. Note
972 that this behavior only works when we have a usable consensus
973 directory, and when options about what to download are more or less
974 standard. In the future we should re-bootstrap from our guards,
975 rather than re-bootstrapping from the preconfigured list of
976 directory sources that ships with Tor. Resolves ticket 6526.
977 - Tor relays and clients now support a better CREATE/EXTEND cell
978 format, allowing the sender to specify multiple address, identity,
979 and handshake types. Implements Robert Ransom's proposal 200;
982 o Major features (new circuit handshake):
983 - Tor now supports a new circuit extension handshake designed by Ian
984 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
985 circuit extension handshake, later called "TAP", was a bit slow
986 (especially on the relay side), had a fragile security proof, and
987 used weaker keys than we'd now prefer. The new circuit handshake
988 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
989 function, making it significantly more secure than the older
990 handshake, and significantly faster. Tor can use one of two built-in
991 pure-C curve25519-donna implementations by Adam Langley, or it
992 can link against the "nacl" library for a tuned version if present.
994 The built-in version is very fast for 64-bit systems when building
995 with GCC. The built-in 32-bit version is still faster than the
996 old TAP protocol, but using libnacl is better on most such hosts.
998 Clients don't currently use this protocol by default, since
999 comparatively few clients support it so far. To try it, set
1000 UseNTorHandshake to 1.
1002 Implements proposal 216; closes ticket 7202.
1004 o Major features (better link encryption):
1005 - Relays can now enable the ECDHE TLS ciphersuites when available
1006 and appropriate. These ciphersuites let us negotiate forward-secure
1007 TLS secret keys more safely and more efficiently than with our
1008 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
1009 public relays prefer the (faster) P224 group, and bridges prefer
1010 the (more common) P256 group; you can override this with the
1013 Enabling these ciphers was a little tricky, since for a long time,
1014 clients had been claiming to support them without actually doing
1015 so, in order to foil fingerprinting. But with the client-side
1016 implementation of proposal 198 in 0.2.3.17-beta, clients can now
1017 match the ciphers from recent Firefox versions *and* list the
1018 ciphers they actually mean, so relays can believe such clients
1019 when they advertise ECDHE support in their TLS ClientHello messages.
1021 This feature requires clients running 0.2.3.17-beta or later,
1022 and requires both sides to be running OpenSSL 1.0.0 or later
1023 with ECC support. OpenSSL 1.0.1, with the compile-time option
1024 "enable-ec_nistp_64_gcc_128", is highly recommended.
1026 Implements the relay side of proposal 198; closes ticket 7200.
1029 - Avoid crashing when, as a relay without IPv6-exit support, a
1030 client insists on getting an IPv6 address or nothing. Fixes bug
1031 7814; bugfix on 0.2.4.7-alpha.
1034 - Improve circuit build timeout handling for hidden services.
1035 In particular: adjust build timeouts more accurately depending
1036 upon the number of hop-RTTs that a particular circuit type
1037 undergoes. Additionally, launch intro circuits in parallel
1038 if they timeout, and take the first one to reply as valid.
1039 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
1040 separate error codes; or at least, don't break for that reason.
1041 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
1042 - Update to the January 2 2013 Maxmind GeoLite Country database.
1044 o Minor features (testing):
1045 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
1046 (P-256) Diffie-Hellman handshakes to src/or/bench.
1047 - Add benchmark functions to test onion handshake performance.
1049 o Minor features (path bias detection):
1050 - Alter the Path Bias log messages to be more descriptive in terms
1051 of reporting timeouts and other statistics.
1052 - Create three levels of Path Bias log messages, as opposed to just
1053 two. These are configurable via consensus as well as via the torrc
1054 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
1055 The default values are 0.70, 0.50, and 0.30 respectively.
1056 - Separate the log message levels from the decision to drop guards,
1057 which also is available via torrc option PathBiasDropGuards.
1058 PathBiasDropGuards still defaults to 0 (off).
1059 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
1060 in combination with PathBiasExtremeRate.
1061 - Increase the default values for PathBiasScaleThreshold and
1062 PathBiasCircThreshold from (200, 20) to (300, 150).
1063 - Add in circuit usage accounting to path bias. If we try to use a
1064 built circuit but fail for any reason, it counts as path bias.
1065 Certain classes of circuits where the adversary gets to pick your
1066 destination node are exempt from this accounting. Usage accounting
1067 can be specifically disabled via consensus parameter or torrc.
1068 - Convert all internal path bias state to double-precision floating
1069 point, to avoid roundoff error and other issues.
1070 - Only record path bias information for circuits that have completed
1071 *two* hops. Assuming end-to-end tagging is the attack vector, this
1072 makes us more resilient to ambient circuit failure without any
1073 detection capability loss.
1075 o Minor bugfixes (log messages):
1076 - Rate-limit the "No circuits are opened. Relaxed timeout for a
1077 circuit with channel state open..." message to once per hour to
1078 keep it from filling the notice logs. Mitigates bug 7799 but does
1079 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
1080 - Avoid spurious warnings when configuring multiple client ports of
1081 which only some are nonlocal. Previously, we had claimed that some
1082 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
1085 o Code simplifications and refactoring:
1086 - Get rid of a couple of harmless clang warnings, where we compared
1087 enums to ints. These warnings are newly introduced in clang 3.2.
1088 - Split the onion.c file into separate modules for the onion queue
1089 and the different handshakes it supports.
1090 - Remove the marshalling/unmarshalling code for sending requests to
1091 cpuworkers over a socket, and instead just send structs. The
1092 recipient will always be the same Tor binary as the sender, so
1093 any encoding is overkill.
1096 Changes in version 0.2.4.7-alpha - 2012-12-24
1097 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
1098 directory mirrors for more robust bootstrapping; fixes more issues where
1099 clients with changing network conditions refuse to make any circuits;
1100 adds initial support for exiting to IPv6 addresses; resumes being able
1101 to update our GeoIP database, and includes the geoip6 file this time;
1102 turns off the client-side DNS cache by default due to privacy risks;
1103 and fixes a variety of other issues.
1105 o Major features (client resilience):
1106 - Add a new "FallbackDir" torrc option to use when we can't use
1107 a directory mirror from the consensus (either because we lack a
1108 consensus, or because they're all down). Currently, all authorities
1109 are fallbacks by default, and there are no other default fallbacks,
1110 but that will change. This option will allow us to give clients a
1111 longer list of servers to try to get a consensus from when first
1112 connecting to the Tor network, and thereby reduce load on the
1113 directory authorities. Implements proposal 206, "Preconfigured
1114 directory sources for bootstrapping". We also removed the old
1115 "FallbackNetworkstatus" option, since we never got it working well
1116 enough to use it. Closes bug 572.
1117 - If we have no circuits open, use a relaxed timeout (the
1118 95th-percentile cutoff) until a circuit succeeds. This heuristic
1119 should allow Tor to succeed at building circuits even when the
1120 network connection drastically changes. Should help with bug 3443.
1122 o Major features (IPv6):
1123 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
1124 connectivity, then set the IPv6Exit flag to 1. Also make sure your
1125 exit policy reads as you would like: the address * applies to all
1126 address families, whereas *4 is IPv4 address only, and *6 is IPv6
1127 addresses only. On the client side, you'll need to wait until the
1128 authorities have upgraded, wait for enough exits to support IPv6,
1129 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
1130 ticket 5547, implements proposal 117 as revised in proposal 208.
1132 We DO NOT recommend that clients with actual anonymity needs start
1133 using IPv6 over Tor yet, since not enough exits support it yet.
1135 o Major features (geoip database):
1136 - Maxmind began labelling Tor relays as being in country "A1",
1137 which breaks by-country node selection inside Tor. Now we use a
1138 script to replace "A1" ("Anonymous Proxy") entries in our geoip
1139 file with real country codes. This script fixes about 90% of "A1"
1140 entries automatically and uses manual country code assignments to
1141 fix the remaining 10%. See src/config/README.geoip for details.
1142 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
1143 Country database, as modified above.
1145 o Major bugfixes (client-side DNS):
1146 - Turn off the client-side DNS cache by default. Updating and using
1147 the DNS cache is now configurable on a per-client-port
1148 level. SOCKSPort, DNSPort, etc lines may now contain
1149 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
1150 cache these types of DNS answers when we receive them from an
1151 exit node in response to an application request on this port, and
1152 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
1153 cached DNS answers of these types, we shouldn't use them. It's
1154 potentially risky to use cached DNS answers at the client, since
1155 doing so can indicate to one exit what answers we've gotten
1156 for DNS lookups in the past. With IPv6, this becomes especially
1157 problematic. Using cached DNS answers for requests on the same
1158 circuit would present less linkability risk, since all traffic
1159 on a circuit is already linkable, but it would also provide
1160 little performance benefit: the exit node caches DNS replies
1161 too. Implements a simplified version of Proposal 205. Implements
1164 o Major bugfixes (other):
1165 - Alter circuit build timeout measurement to start at the point
1166 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
1167 initialization). This should make our timeout measurements more
1168 uniform. Previously, we were sometimes including ORconn setup time
1169 in our circuit build time measurements. Should resolve bug 3443.
1170 - Fix an assertion that could trigger in hibernate_go_dormant() when
1171 closing an or_connection_t: call channel_mark_for_close() rather
1172 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
1174 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
1175 7655; bugfix on 0.2.4.6-alpha.
1178 - Add a new torrc option "ServerTransportListenAddr" to let bridge
1179 operators select the address where their pluggable transports will
1180 listen for connections. Resolves ticket 7013.
1181 - Allow an optional $ before the node identity digest in the
1182 controller command GETINFO ns/id/<identity>, for consistency with
1183 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
1184 - Log packaged cell fullness as part of the heartbeat message.
1185 Diagnosis to try to determine the extent of bug 7743.
1187 o Minor features (IPv6):
1188 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
1189 prefer to hand out virtual IPv6 addresses, since there are more of
1190 them and we can't run out. To override this behavior and make IPv4
1191 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
1192 or DNSPort you're using for resolving. Implements ticket 7571.
1193 - AutomapHostsOnResolve responses are now randomized, to avoid
1194 annoying situations where Tor is restarted and applications
1195 connect to the wrong addresses.
1196 - Never try more than 1000 times to pick a new virtual address when
1197 AutomapHostsOnResolve is set. That's good enough so long as we
1198 aren't close to handing out our entire virtual address space;
1199 if you're getting there, it's best to switch to IPv6 virtual
1203 - The ADDRMAP command can no longer generate an ill-formed error
1204 code on a failed MAPADDRESS. It now says "internal" rather than
1205 an English sentence fragment with spaces in the middle. Bugfix on
1207 - Fix log messages and comments to avoid saying "GMT" when we mean
1208 "UTC". Fixes bug 6113.
1209 - Compile on win64 using mingw64. Fixes bug 7260; patches from
1211 - Fix a crash when debugging unit tests on Windows: deallocate a
1212 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
1213 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
1216 - The DirServer option is now DirAuthority, for consistency with
1217 current naming patterns. You can still use the old DirServer form.
1219 o Code simplification and refactoring:
1220 - Move the client-side address-map/virtual-address/DNS-cache code
1221 out of connection_edge.c into a new addressmap.c module.
1222 - Remove unused code for parsing v1 directories and "running routers"
1223 documents. Fixes bug 6887.
1226 Changes in version 0.2.3.25 - 2012-11-19
1227 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
1228 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
1229 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
1230 programmer, and friend. Unstinting in his dedication to the cause of
1231 freedom, he inspired and helped many of us as we began our work on
1232 anonymity, and inspires us still. Please honor his memory by writing
1233 software to protect people's freedoms, and by helping others to do so.
1235 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
1236 significantly reduced directory overhead (via microdescriptors),
1237 enormous crypto performance improvements for fast relays on new
1238 enough hardware, a new v3 TLS handshake protocol that can better
1239 resist fingerprinting, support for protocol obfuscation plugins (aka
1240 pluggable transports), better scalability for hidden services, IPv6
1241 support for bridges, performance improvements like allowing clients
1242 to skip the first round-trip on the circuit ("optimistic data") and
1243 refilling token buckets more often, a new "stream isolation" design
1244 to isolate different applications on different circuits, and many
1245 stability, security, and privacy fixes.
1248 - Tor tries to wipe potentially sensitive data after using it, so
1249 that if some subsequent security failure exposes Tor's memory,
1250 the damage will be limited. But we had a bug where the compiler
1251 was eliminating these wipe operations when it decided that the
1252 memory was no longer visible to a (correctly running) program,
1253 hence defeating our attempt at defense in depth. We fix that
1254 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1255 is unlikely to optimize away. Future versions of Tor may use
1256 a less ridiculously heavy approach for this. Fixes bug 7352.
1257 Reported in an article by Andrey Karpov.
1260 - Fix a harmless bug when opting against publishing a relay descriptor
1261 because DisableNetwork is set. Fixes bug 7464; bugfix on
1265 Changes in version 0.2.4.6-alpha - 2012-11-13
1266 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
1267 makes our defense-in-depth memory wiping more reliable, and begins to
1268 count IPv6 addresses in bridge statistics,
1271 - Fix an assertion failure that could occur when closing a connection
1272 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
1274 - Tor tries to wipe potentially sensitive data after using it, so
1275 that if some subsequent security failure exposes Tor's memory,
1276 the damage will be limited. But we had a bug where the compiler
1277 was eliminating these wipe operations when it decided that the
1278 memory was no longer visible to a (correctly running) program,
1279 hence defeating our attempt at defense in depth. We fix that
1280 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1281 is unlikely to optimize away. Future versions of Tor may use
1282 a less ridiculously heavy approach for this. Fixes bug 7352.
1283 Reported in an article by Andrey Karpov.
1286 - Add GeoIP database for IPv6 addresses. The new config option
1288 - Bridge statistics now count bridge clients connecting over IPv6:
1289 bridge statistics files now list "bridge-ip-versions" and
1290 extra-info documents list "geoip6-db-digest". The control protocol
1291 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
1292 implementation by "shkoo", addressing ticket 5055.
1295 - Warn when we are binding low ports when hibernation is enabled;
1296 previously we had warned when we were _advertising_ low ports with
1297 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
1298 - Fix a harmless bug when opting against publishing a relay descriptor
1299 because DisableNetwork is set. Fixes bug 7464; bugfix on
1301 - Add warning message when a managed proxy dies during configuration.
1302 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
1303 - Fix a linking error when building tor-fw-helper without miniupnp.
1304 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
1305 - Check for closing an or_connection_t without going through correct
1306 channel functions; emit a warning and then call
1307 connection_or_close_for_error() so we don't assert as in bugs 7212
1309 - Compile correctly on compilers without C99 designated initializer
1310 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
1311 - Avoid a possible assert that can occur when channel_send_destroy() is
1312 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
1313 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
1314 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
1315 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
1316 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
1318 o Code simplification and refactoring:
1319 - Start using OpenBSD's implementation of queue.h, so that we don't
1320 need to hand-roll our own pointer and list structures whenever we
1321 need them. (We can't rely on a sys/queue.h, since some operating
1322 systems don't have them, and the ones that do have them don't all
1323 present the same extensions.)
1326 Changes in version 0.2.4.5-alpha - 2012-10-25
1327 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
1328 two important security vulnerabilities that could lead to remotely
1329 triggerable relay crashes, fix a major bug that was preventing clients
1330 from choosing suitable exit nodes, and refactor some of our code.
1332 o Major bugfixes (security, also in 0.2.3.24-rc):
1333 - Fix a group of remotely triggerable assertion failures related to
1334 incorrect link protocol negotiation. Found, diagnosed, and fixed
1335 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1337 - Fix a denial of service attack by which any directory authority
1338 could crash all the others, or by which a single v2 directory
1339 authority could crash everybody downloading v2 directory
1340 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1342 o Major bugfixes (also in 0.2.3.24-rc):
1343 - When parsing exit policy summaries from microdescriptors, we had
1344 previously been ignoring the last character in each one, so that
1345 "accept 80,443,8080" would be treated by clients as indicating
1346 a node that allows access to ports 80, 443, and 808. That would
1347 lead to clients attempting connections that could never work,
1348 and ignoring exit nodes that would support their connections. Now
1349 clients parse these exit policy summaries correctly. Fixes bug 7192;
1350 bugfix on 0.2.3.1-alpha.
1352 o Minor bugfixes (also in 0.2.3.24-rc):
1353 - Clients now consider the ClientRejectInternalAddresses config option
1354 when using a microdescriptor consensus stanza to decide whether
1355 an exit relay would allow exiting to an internal address. Fixes
1356 bug 7190; bugfix on 0.2.3.1-alpha.
1359 - Only disable TLS session ticket support when running as a TLS
1360 server. Now clients will blend better with regular Firefox
1361 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
1363 o Code simplification and refactoring:
1364 - Start using OpenBSD's implementation of queue.h (originally by
1366 - Move the entry node code from circuitbuild.c to its own file.
1367 - Move the circuit build timeout tracking code from circuitbuild.c
1371 Changes in version 0.2.3.24-rc - 2012-10-25
1372 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
1373 could lead to remotely triggerable relay crashes, and fixes
1374 a major bug that was preventing clients from choosing suitable exit
1377 o Major bugfixes (security):
1378 - Fix a group of remotely triggerable assertion failures related to
1379 incorrect link protocol negotiation. Found, diagnosed, and fixed
1380 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1382 - Fix a denial of service attack by which any directory authority
1383 could crash all the others, or by which a single v2 directory
1384 authority could crash everybody downloading v2 directory
1385 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1388 - When parsing exit policy summaries from microdescriptors, we had
1389 previously been ignoring the last character in each one, so that
1390 "accept 80,443,8080" would be treated by clients as indicating
1391 a node that allows access to ports 80, 443, and 808. That would
1392 lead to clients attempting connections that could never work,
1393 and ignoring exit nodes that would support their connections. Now
1394 clients parse these exit policy summaries correctly. Fixes bug 7192;
1395 bugfix on 0.2.3.1-alpha.
1398 - Clients now consider the ClientRejectInternalAddresses config option
1399 when using a microdescriptor consensus stanza to decide whether
1400 an exit relay would allow exiting to an internal address. Fixes
1401 bug 7190; bugfix on 0.2.3.1-alpha.
1404 Changes in version 0.2.4.4-alpha - 2012-10-20
1405 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
1406 vulnerability introduced by a change in OpenSSL, fixes a remotely
1407 triggerable assert, and adds new channel_t and circuitmux_t abstractions
1408 that will make it easier to test new connection transport and cell
1409 scheduling algorithms.
1411 o New directory authorities (also in 0.2.3.23-rc):
1412 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1413 authority. Closes ticket 5749.
1415 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
1416 - Disable TLS session tickets. OpenSSL's implementation was giving
1417 our TLS session keys the lifetime of our TLS context objects, when
1418 perfect forward secrecy would want us to discard anything that
1419 could decrypt a link connection as soon as the link connection
1420 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1421 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1422 - Discard extraneous renegotiation attempts once the V3 link
1423 protocol has been initiated. Failure to do so left us open to
1424 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1425 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1427 o Internal abstraction features:
1428 - Introduce new channel_t abstraction between circuits and
1429 or_connection_t to allow for implementing alternate OR-to-OR
1430 transports. A channel_t is an abstract object which can either be a
1431 cell-bearing channel, which is responsible for authenticating and
1432 handshaking with the remote OR and transmitting cells to and from
1433 it, or a listening channel, which spawns new cell-bearing channels
1434 at the request of remote ORs. Implements part of ticket 6465.
1435 - Also new is the channel_tls_t subclass of channel_t, adapting it
1436 to the existing or_connection_t code. The V2/V3 protocol handshaking
1437 code which formerly resided in command.c has been moved below the
1438 channel_t abstraction layer and may be found in channeltls.c now.
1439 Implements the rest of ticket 6465.
1440 - Introduce new circuitmux_t storing the queue of circuits for
1441 a channel; this encapsulates and abstracts the queue logic and
1442 circuit selection policy, and allows the latter to be overridden
1443 easily by switching out a policy object. The existing EWMA behavior
1444 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
1446 o Required libraries:
1447 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
1448 strongly recommended.
1451 - Warn users who run hidden services on a Tor client with
1452 UseEntryGuards disabled that their hidden services will be
1453 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
1454 attack which motivated Tor to support entry guards in the first
1455 place). Resolves ticket 6889.
1456 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
1457 dhill. Resolves ticket 6982.
1458 - Option OutboundBindAddress can be specified multiple times and
1459 accepts IPv6 addresses. Resolves ticket 6876.
1461 o Minor bugfixes (also in 0.2.3.23-rc):
1462 - Don't serve or accept v2 hidden service descriptors over a
1463 relay's DirPort. It's never correct to do so, and disabling it
1464 might make it more annoying to exploit any bugs that turn up in the
1465 descriptor-parsing code. Fixes bug 7149.
1466 - Fix two cases in src/or/transports.c where we were calling
1467 fmt_addr() twice in a parameter list. Bug found by David
1468 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1469 - Fix memory leaks whenever we logged any message about the "path
1470 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1471 - When relays refuse a "create" cell because their queue of pending
1472 create cells is too big (typically because their cpu can't keep up
1473 with the arrival rate), send back reason "resource limit" rather
1474 than reason "internal", so network measurement scripts can get a
1475 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
1478 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
1479 - Free some more still-in-use memory at exit, to make hunting for
1480 memory leaks easier. Resolves bug 7029.
1481 - When a Tor client gets a "truncated" relay cell, the first byte of
1482 its payload specifies why the circuit was truncated. We were
1483 ignoring this 'reason' byte when tearing down the circuit, resulting
1484 in the controller not being told why the circuit closed. Now we
1485 pass the reason from the truncated cell to the controller. Bugfix
1486 on 0.1.2.3-alpha; fixes bug 7039.
1487 - Downgrade "Failed to hand off onionskin" messages to "debug"
1488 severity, since they're typically redundant with the "Your computer
1489 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
1490 - Make clients running with IPv6 bridges connect over IPv6 again,
1491 even without setting new config options ClientUseIPv6 and
1492 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
1493 - Use square brackets around IPv6 addresses in numerous places
1494 that needed them, including log messages, HTTPS CONNECT proxy
1495 requests, TransportProxy statefile entries, and pluggable transport
1496 extra-info lines. Fixes bug 7011; patch by David Fifield.
1498 o Code refactoring and cleanup:
1499 - Source files taken from other packages now reside in src/ext;
1500 previously they were scattered around the rest of Tor.
1501 - Avoid use of reserved identifiers in our C code. The C standard
1502 doesn't like us declaring anything that starts with an
1503 underscore, so let's knock it off before we get in trouble. Fix
1504 for bug 1031; bugfix on the first Tor commit.
1507 Changes in version 0.2.3.23-rc - 2012-10-20
1508 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
1509 vulnerability introduced by a change in OpenSSL, and fixes a variety
1510 of smaller bugs in preparation for the release.
1512 o New directory authorities:
1513 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1514 authority. Closes ticket 5749.
1516 o Major bugfixes (security/privacy):
1517 - Disable TLS session tickets. OpenSSL's implementation was giving
1518 our TLS session keys the lifetime of our TLS context objects, when
1519 perfect forward secrecy would want us to discard anything that
1520 could decrypt a link connection as soon as the link connection
1521 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1522 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1523 - Discard extraneous renegotiation attempts once the V3 link
1524 protocol has been initiated. Failure to do so left us open to
1525 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1526 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1529 - Fix a possible crash bug when checking for deactivated circuits
1530 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1531 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1533 o Minor bugfixes (on 0.2.3.x):
1534 - Fix two cases in src/or/transports.c where we were calling
1535 fmt_addr() twice in a parameter list. Bug found by David
1536 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1537 - Convert an assert in the pathbias code to a log message. The assert
1538 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1539 bugfix on 0.2.3.17-beta.
1540 - Fix memory leaks whenever we logged any message about the "path
1541 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1543 o Minor bugfixes (on 0.2.2.x and earlier):
1544 - Don't serve or accept v2 hidden service descriptors over a relay's
1545 DirPort. It's never correct to do so, and disabling it might
1546 make it more annoying to exploit any bugs that turn up in the
1547 descriptor-parsing code. Fixes bug 7149.
1548 - When relays refuse a "create" cell because their queue of pending
1549 create cells is too big (typically because their cpu can't keep up
1550 with the arrival rate), send back reason "resource limit" rather
1551 than reason "internal", so network measurement scripts can get a
1552 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
1553 - Correct file sizes when reading binary files on Cygwin, to avoid
1554 a bug where Tor would fail to read its state file. Fixes bug 6844;
1555 bugfix on 0.1.2.7-alpha.
1556 - Avoid undefined behaviour when parsing the list of supported
1557 rendezvous/introduction protocols in a hidden service descriptor.
1558 Previously, Tor would have confused (as-yet-unused) protocol version
1559 numbers greater than 32 with lower ones on many platforms. Fixes
1560 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1562 o Documentation fixes:
1563 - Clarify that hidden services are TCP only. Fixes bug 6024.
1566 Changes in version 0.2.4.3-alpha - 2012-09-22
1567 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
1568 assertion, resumes letting relays test reachability of their DirPort,
1569 and cleans up a bunch of smaller bugs.
1572 - Fix an assertion failure in tor_timegm() that could be triggered
1573 by a badly formatted directory object. Bug found by fuzzing with
1574 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1577 - Fix a possible crash bug when checking for deactivated circuits
1578 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1579 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1580 - Allow routers to detect that their own DirPorts are running. When
1581 we removed support for versions_supports_begindir, we also
1582 accidentally removed the mechanism we used to self-test our
1583 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
1584 bugfix on 0.2.4.2-alpha.
1586 o Security features:
1587 - Switch to a completely time-invariant approach for picking nodes
1588 weighted by bandwidth. Our old approach would run through the
1589 part of the loop after it had made its choice slightly slower
1590 than it ran through the part of the loop before it had made its
1591 choice. Addresses ticket 6538.
1592 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
1593 by tor2web clients allows hidden services to identify tor2web
1594 clients through their repeated selection of the same rendezvous
1595 and introduction point circuit endpoints (their guards). Resolves
1599 - Enable Tor to read configuration, state, and key information from
1600 a FIFO. Previously Tor would only read from files with a positive
1601 stat.st_size. Code from meejah; fixes bug 6044.
1604 - Correct file sizes when reading binary files on Cygwin, to avoid
1605 a bug where Tor would fail to read its state file. Fixes bug 6844;
1606 bugfix on 0.1.2.7-alpha.
1607 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
1608 bugfix on 0.2.0.3-alpha.
1609 - When complaining about a client port on a public address, log
1610 which address we're complaining about. Fixes bug 4020; bugfix on
1611 0.2.3.3-alpha. Patch by Tom Fitzhenry.
1612 - Convert an assert in the pathbias code to a log message. The assert
1613 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1614 bugfix on 0.2.3.17-beta.
1615 - Our new buildsystem was overzealous about rebuilding manpages: it
1616 would rebuild them all whenever any one of them changed. Now our
1617 dependency checking should be correct. Fixes bug 6843; bugfix on
1619 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
1620 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
1621 - Correct log printout about which address family is preferred
1622 when connecting to a bridge with both an IPv4 and IPv6 OR port.
1623 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
1625 o Minor bugfixes (code cleanliness):
1626 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
1627 with large values. This situation was untriggered, but nevertheless
1628 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
1629 - Reject consensus votes with more than 64 known-flags. We aren't even
1630 close to that limit yet, and our code doesn't handle it correctly.
1631 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
1632 - Avoid undefined behaviour when parsing the list of supported
1633 rendezvous/introduction protocols in a hidden service descriptor.
1634 Previously, Tor would have confused (as-yet-unused) protocol version
1635 numbers greater than 32 with lower ones on many platforms. Fixes
1636 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1637 - Fix handling of rendezvous client authorization types over 8.
1638 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
1639 - Fix building with older versions of GCC (2.95, for one) that don't
1640 like preprocessor directives inside macro arguments. Found by
1641 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
1642 - Switch weighted node selection rule from using a list of doubles
1643 to using a list of int64_t. This change should make the process
1644 slightly easier to debug and maintain. Needed to finish ticket 6538.
1646 o Code simplification and refactoring:
1647 - Move the generic "config" code into a new file, and have "config.c"
1648 hold only torrc- and state-related code. Resolves ticket 6823.
1649 - Move the core of our "choose a weighted element at random" logic
1650 into its own function, and give it unit tests. Now the logic is
1651 testable, and a little less fragile too.
1652 - Removed the testing_since field of node_t, which hasn't been used
1653 for anything since 0.2.0.9-alpha.
1655 o Documentation fixes:
1656 - Clarify that hidden services are TCP only. Fixes bug 6024.
1657 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
1661 Changes in version 0.2.3.22-rc - 2012-09-11
1662 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
1666 - Fix an assertion failure in tor_timegm() that could be triggered
1667 by a badly formatted directory object. Bug found by fuzzing with
1668 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1671 - Avoid segfault when starting up having run with an extremely old
1672 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1676 Changes in version 0.2.2.39 - 2012-09-11
1677 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
1681 - Fix an assertion failure in tor_timegm() that could be triggered
1682 by a badly formatted directory object. Bug found by fuzzing with
1683 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1684 - Do not crash when comparing an address with port value 0 to an
1685 address policy. This bug could have been used to cause a remote
1686 assertion failure by or against directory authorities, or to
1687 allow some applications to crash clients. Fixes bug 6690; bugfix
1691 Changes in version 0.2.4.2-alpha - 2012-09-10
1692 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
1693 raises the default rate limiting even more, and makes the bootstrapping
1694 log messages less noisy.
1697 - Automatically forward the TCP ports of pluggable transport
1698 proxies using tor-fw-helper if PortForwarding is enabled. Implements
1702 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
1703 to 1GB/1GB. The previous defaults were intended to be "basically
1704 infinite", but it turns out they're now limiting our 100mbit+
1705 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
1706 last time we raised it).
1709 - Detect when we're running with a version of OpenSSL other than the
1710 one we compiled with. This has occasionally given people hard-to-
1712 - Log fewer lines at level "notice" about our OpenSSL and Libevent
1713 versions and capabilities when everything is going right. Resolves
1714 part of ticket 6736.
1715 - Directory authorities no long accept descriptors for any version of
1716 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
1717 These versions are insecure, unsupported, or both. Implements
1721 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
1722 to start with a triple-underscore so the controller won't touch it.
1723 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
1724 - Avoid segfault when starting up having run with an extremely old
1725 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1727 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
1728 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
1729 - Don't follow the NULL pointer if microdescriptor generation fails.
1730 (This does not appear to be triggerable, but it's best to be safe.)
1731 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
1732 - Fix mis-declared dependencies on src/common/crypto.c and
1733 src/or/tor_main.c that could break out-of-tree builds under some
1734 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
1735 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
1736 6778; bugfix on 0.2.4.1-alpha.
1737 - Fix a harmless (in this case) build warning for implicitly
1738 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
1741 - Now that all versions before 0.2.2.x are disallowed, we no longer
1742 need to work around their missing features. Thus we can remove a
1743 bunch of compatibility code.
1746 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
1747 TCP ports to forward. In the past it only accepted two ports:
1748 the ORPort and the DirPort.
1751 Changes in version 0.2.4.1-alpha - 2012-09-05
1752 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
1753 bridgedb; lets relays use IPv6 addresses and directory authorities
1754 advertise them; and switches to a cleaner build interface.
1756 This is the first alpha release in a new series, so expect there to
1757 be bugs. Users who would rather test out a more stable branch should
1758 stay with 0.2.3.x for now.
1760 o Major features (bridges):
1761 - Bridges now report the pluggable transports they support to the
1762 bridge authority, so it can pass the supported transports on to
1763 bridgedb and/or eventually do reachability testing. Implements
1766 o Major features (IPv6):
1767 - Bridge authorities now accept IPv6 bridge addresses and include
1768 them in network status documents. Implements ticket 5534.
1769 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
1770 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
1771 to happen. Implements ticket 5535.
1772 - All kind of relays, not just bridges, can now advertise an IPv6
1773 OR port. Implements ticket 6362.
1774 - Directory authorities vote on IPv6 OR ports using the new consensus
1775 method 14. Implements ticket 6363.
1777 o Major features (build):
1778 - Switch to a nonrecursive Makefile structure. Now instead of each
1779 Makefile.am invoking other Makefile.am's, there is a master
1780 Makefile.am that includes the others. This change makes our build
1781 process slightly more maintainable, and improves parallelism for
1782 building with make -j. Original patch by Stewart Smith; various
1783 fixes by Jim Meyering.
1784 - Where available, we now use automake's "silent" make rules by
1785 default, so that warnings are easier to spot. You can get the old
1786 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
1788 o Minor features (code security and spec conformance):
1789 - Clear keys and key-derived material left on the stack in
1790 rendservice.c and rendclient.c. Check return value of
1791 crypto_pk_write_private_key_to_string() in end_service_load_keys().
1792 These fixes should make us more forward-secure against cold-boot
1793 attacks and the like. Fixes bug 2385.
1794 - Reject EXTEND cells sent to nonexistent streams. According to the
1795 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
1796 we were only checking for stream IDs that were currently in use.
1797 Found while hunting for more instances of bug 6271. Bugfix on
1798 0.0.2pre8, which introduced incremental circuit construction.
1800 o Minor features (streamlining);
1801 - No longer include the "opt" prefix when generating routerinfos
1802 or v2 directories: it has been needless since Tor 0.1.2. Closes
1804 - Remove some now-needless code that tried to aggressively flush
1805 OR connections as data was added to them. Since 0.2.0.1-alpha, our
1806 cell queue logic has saved us from the failure mode that this code
1807 was supposed to prevent. Removing this code will limit the number
1808 of baroque control flow paths through Tor's network logic. Reported
1809 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
1811 o Minor features (controller):
1812 - Add a "GETINFO signal/names" control port command. Implements
1814 - Provide default values for all options via "GETINFO config/defaults".
1815 Implements ticket 4971.
1817 o Minor features (IPv6):
1818 - New config option "AuthDirHasIPv6Connectivity 1" that directory
1819 authorities should set if they have IPv6 connectivity and want to
1820 do reachability tests for IPv6 relays. Implements feature 5974.
1821 - A relay with an IPv6 OR port now sends that address in NETINFO
1822 cells (in addition to its other address). Implements ticket 6364.
1824 o Minor features (log messages):
1825 - Omit the first heartbeat log message, because it never has anything
1826 useful to say, and it clutters up the bootstrapping messages.
1827 Resolves ticket 6758.
1828 - Don't log about reloading the microdescriptor cache at startup. Our
1829 bootstrap warnings are supposed to tell the user when there's a
1830 problem, and our bootstrap notices say when there isn't. Resolves
1831 ticket 6759; bugfix on 0.2.2.6-alpha.
1832 - Don't log "I learned some more directory information" when we're
1833 reading cached directory information. Reserve it for when new
1834 directory information arrives in response to a fetch. Resolves
1836 - Prevent rounding error in path bias counts when scaling
1837 them down, and use the correct scale factor default. Also demote
1838 some path bias related log messages down a level and make others
1839 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
1840 - We no longer warn so much when generating manpages from their
1843 o Code simplifications and refactoring:
1844 - Enhance our internal sscanf replacement so that we can eliminate
1845 the last remaining uses of the system sscanf. (Though those uses
1846 of sscanf were safe, sscanf itself is generally error prone, so
1847 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
1849 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
1850 - Move last_reachable and testing_since from routerinfo_t to node_t.
1851 Implements ticket 5529.
1852 - Add replaycache_t structure, functions and unit tests, then refactor
1853 rend_service_introduce() to be more clear to read, improve, debug,
1854 and test. Resolves bug 6177.
1855 - Finally remove support for malloc_good_size and malloc_usable_size.
1856 We had hoped that these functions would let us eke a little more
1857 memory out of our malloc implementation. Unfortunately, the only
1858 implementations that provided these functions are also ones that
1859 are already efficient about not overallocation: they never got us
1860 more than 7 or so bytes per allocation. Removing them saves us a
1861 little code complexity and a nontrivial amount of build complexity.
1864 - Tor maintainers now require Automake version 1.9 or later to build
1865 Tor from the Git repository. (Automake is not required when building
1866 from a source distribution.)
1869 Changes in version 0.2.3.21-rc - 2012-09-05
1870 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
1871 series. It fixes a trio of potential security bugs, fixes a bug where
1872 we were leaving some of the fast relays out of the microdescriptor
1873 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
1874 and cleans up other smaller issues.
1876 o Major bugfixes (security):
1877 - Tear down the circuit if we get an unexpected SENDME cell. Clients
1878 could use this trick to make their circuits receive cells faster
1879 than our flow control would have allowed, or to gum up the network,
1880 or possibly to do targeted memory denial-of-service attacks on
1881 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
1882 from July 2002, before the release of Tor 0.0.0. We had committed
1883 this patch previously, but we had to revert it because of bug 6271.
1884 Now that 6271 is fixed, this patch appears to work.
1885 - Reject any attempt to extend to an internal address. Without
1886 this fix, a router could be used to probe addresses on an internal
1887 network to see whether they were accepting connections. Fixes bug
1888 6710; bugfix on 0.0.8pre1.
1889 - Do not crash when comparing an address with port value 0 to an
1890 address policy. This bug could have been used to cause a remote
1891 assertion failure by or against directory authorities, or to
1892 allow some applications to crash clients. Fixes bug 6690; bugfix
1896 - Remove the upper bound on microdescriptor length. We were hitting
1897 the limit for routers with complex exit policies or family
1898 declarations, causing clients to not use them. Fixes the first
1899 piece of bug 6404; fix on 0.2.2.6-alpha.
1900 - Detect "ORPort 0" as meaning, uniformly, that we're not running
1901 as a relay. Previously, some of our code would treat the presence
1902 of any ORPort line as meaning that we should act like a relay,
1903 even though our new listener code would correctly not open any
1904 ORPorts for ORPort 0. Similar bugs in other Port options are also
1905 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
1908 - Avoid a pair of double-free and use-after-mark bugs that can
1909 occur with certain timings in canceled and re-received DNS
1910 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
1911 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
1912 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
1913 - Allow one-hop directory fetching circuits the full "circuit build
1914 timeout" period, rather than just half of it, before failing them
1915 and marking the relay down. This fix should help reduce cases where
1916 clients declare relays (or worse, bridges) unreachable because
1917 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
1918 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
1920 - Authorities no longer include any router in their microdescriptor
1921 consensuses for which they couldn't generate or agree on a
1922 microdescriptor. Fixes the second piece of bug 6404; fix on
1924 - Detect and reject attempts to specify both "FooPort" and
1925 "FooPort 0" in the same configuration domain. (It's still okay
1926 to have a FooPort in your configuration file, and use "FooPort 0"
1927 on the command line to disable it.) Fixes the second half of bug
1928 6507; bugfix on 0.2.3.3-alpha.
1929 - Make wildcarded addresses (that is, ones beginning with "*.") work
1930 when provided via the controller's MapAddress command. Previously,
1931 they were accepted, but we never actually noticed that they were
1932 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
1933 - Avoid crashing on a malformed state file where EntryGuardPathBias
1934 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
1935 - Add a (probably redundant) memory clear between iterations of
1936 the router status voting loop, to prevent future coding errors
1937 where data might leak between iterations of the loop. Resolves
1940 o Minor bugfixes (log messages):
1941 - Downgrade "set buildtimeout to low value" messages to "info"
1942 severity; they were never an actual problem, there was never
1943 anything reasonable to do about them, and they tended to spam logs
1944 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
1945 - Downgrade path-bias warning messages to "info". We'll try to get
1946 them working better in 0.2.4. Add internal circuit construction
1947 state to protect against the noisy warn message "Unexpectedly high
1948 circuit_successes". Also add some additional rate-limited notice
1949 messages to help determine the root cause of the warn. Fixes bug
1950 6475. Bugfix against 0.2.3.17-beta.
1951 - Move log message when unable to find a microdesc in a routerstatus
1952 entry to parse time. Previously we'd spam this warning every time
1953 we tried to figure out which microdescriptors to download. Fixes
1954 the third piece of bug 6404; fix on 0.2.3.18-rc.
1957 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
1958 change when the authority is deciding whether to accept a newly
1959 uploaded descriptor. Implements ticket 6423.
1960 - Add missing documentation for consensus and microdesc files.
1961 Resolves ticket 6732.
1964 Changes in version 0.2.2.38 - 2012-08-12
1965 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
1966 attack that could in theory leak path information.
1969 - Avoid an uninitialized memory read when reading a vote or consensus
1970 document that has an unrecognized flavor name. This read could
1971 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1972 - Try to leak less information about what relays a client is
1973 choosing to a side-channel attacker. Previously, a Tor client would
1974 stop iterating through the list of available relays as soon as it
1975 had chosen one, thus finishing a little earlier when it picked
1976 a router earlier in the list. If an attacker can recover this
1977 timing information (nontrivial but not proven to be impossible),
1978 they could learn some coarse-grained information about which relays
1979 a client was picking (middle nodes in particular are likelier to
1980 be affected than exits). The timing attack might be mitigated by
1981 other factors (see bug 6537 for some discussion), but it's best
1982 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
1985 Changes in version 0.2.3.20-rc - 2012-08-05
1986 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
1987 series. It fixes a pair of code security bugs and a potential anonymity
1988 issue, updates our RPM spec files, and cleans up other smaller issues.
1991 - Avoid read-from-freed-memory and double-free bugs that could occur
1992 when a DNS request fails while launching it. Fixes bug 6480;
1993 bugfix on 0.2.0.1-alpha.
1994 - Avoid an uninitialized memory read when reading a vote or consensus
1995 document that has an unrecognized flavor name. This read could
1996 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1997 - Try to leak less information about what relays a client is
1998 choosing to a side-channel attacker. Previously, a Tor client would
1999 stop iterating through the list of available relays as soon as it
2000 had chosen one, thus finishing a little earlier when it picked
2001 a router earlier in the list. If an attacker can recover this
2002 timing information (nontrivial but not proven to be impossible),
2003 they could learn some coarse-grained information about which relays
2004 a client was picking (middle nodes in particular are likelier to
2005 be affected than exits). The timing attack might be mitigated by
2006 other factors (see bug 6537 for some discussion), but it's best
2007 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
2010 - Try to make the warning when giving an obsolete SOCKSListenAddress
2011 a little more useful.
2012 - Terminate active server managed proxies if Tor stops being a
2013 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
2014 - Provide a better error message about possible OSX Asciidoc failure
2015 reasons. Fixes bug 6436.
2016 - Warn when Tor is configured to use accounting in a way that can
2017 link a hidden service to some other hidden service or public
2018 address. Resolves ticket 6490.
2021 - Check return value of fputs() when writing authority certificate
2022 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
2023 - Ignore ServerTransportPlugin lines when Tor is not configured as
2024 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
2025 - When disabling guards for having too high a proportion of failed
2026 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
2030 - Update our default RPM spec files to work with mock and rpmbuild
2031 on RHEL/Fedora. They have an updated set of dependencies and
2032 conflicts, a fix for an ancient typo when creating the "_tor"
2033 user, and better instructions. Thanks to Ondrej Mikle for the
2034 patch series. Fixes bug 6043.
2037 - Make it possible to set the TestingTorNetwork configuration
2038 option using AlternateDirAuthority and AlternateBridgeAuthority
2039 as an alternative to setting DirServer. Addresses ticket 6377.
2042 - Clarify the documentation for the Alternate*Authority options.
2044 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
2046 o Code simplification and refactoring:
2047 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
2048 10 lines. Also, don't nest them. Doing so in the past has
2049 led to hard-to-debug code. The new style is to use the
2050 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
2053 Changes in version 0.2.3.19-rc - 2012-07-06
2054 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
2055 series. It fixes the compile on Windows, reverts to a GeoIP database
2056 that isn't as broken, and fixes a flow control bug that has been around
2057 since the beginning of Tor.
2060 - Fix a bug handling SENDME cells on nonexistent streams that could
2061 result in bizarre window values. Report and patch contributed
2062 pseudonymously. Fixes part of bug 6271. This bug was introduced
2063 before the first Tor release, in svn commit r152.
2064 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
2065 June 2012 database, Maxmind marked many Tor relays as country "A1",
2066 which will cause risky behavior for clients that set EntryNodes
2067 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
2068 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
2069 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
2072 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
2073 bugfix on 0.2.1.10-alpha.
2076 Changes in version 0.2.3.18-rc - 2012-06-28
2077 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
2078 series. It fixes a few smaller bugs, but generally appears stable.
2079 Please test it and let us know whether it is!
2082 - Allow wildcarded mapaddress targets to be specified on the
2083 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
2084 - Make our linker option detection code more robust against linkers
2085 such as on FreeBSD 8, where a bad combination of options completes
2086 successfully but makes an unrunnable binary. Fixes bug 6173;
2087 bugfix on 0.2.3.17-beta.
2089 o Minor bugfixes (on 0.2.2.x and earlier):
2090 - Avoid a false positive in the util/threads unit test by increasing
2091 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
2092 - Replace "Sending publish request" log messages with "Launching
2093 upload", so that they no longer confusingly imply that we're
2094 sending something to a directory we might not even be connected
2095 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
2096 - Make sure to set *socket_error in all error cases in
2097 connection_connect(), so it can't produce a warning about
2098 errno being zero from errno_to_orconn_end_reason(). Bugfix on
2099 0.2.1.1-alpha; resolves ticket 6028.
2100 - Downgrade "Got a certificate, but we already have it" log messages
2101 from warning to info, except when we're a dirauth. Fixes bug 5238;
2102 bugfix on 0.2.1.7-alpha.
2103 - When checking for requested signatures on the latest consensus
2104 before serving it to a client, make sure to check the right
2105 consensus flavor. Bugfix on 0.2.2.6-alpha.
2106 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
2107 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
2109 o Minor bugfixes (on 0.2.3.x):
2110 - Make format_helper_exit_status() avoid unnecessary space padding
2111 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
2113 - Downgrade a message about cleaning the microdescriptor cache to
2114 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
2115 - Log a BUG message at severity INFO if we have a networkstatus with
2116 a missing entry for some microdescriptor. Continues on a patch
2118 - Improve the log message when a managed proxy fails to launch. Fixes
2119 bug 5099; bugfix on 0.2.3.6-alpha.
2120 - Don't do DNS lookups when parsing corrupted managed proxy protocol
2121 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
2122 - When formatting wildcarded address mappings for the controller,
2123 be sure to include "*." as appropriate. Partially fixes bug 6244;
2124 bugfix on 0.2.3.9-alpha.
2125 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
2126 Bugfix on 0.2.3.13-alpha.
2127 - Stop logging messages about running with circuit timeout learning
2128 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
2129 - Disable a spurious warning about reading on a marked and flushing
2130 connection. We shouldn't be doing that, but apparently we
2131 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
2132 - Fix a bug that stopped AllowDotExit from working on addresses
2133 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
2136 o Code simplification, refactoring, unit tests:
2137 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
2138 Libevent's notion of cached time when possible.
2139 - Remove duplicate code for invoking getrlimit() from control.c.
2140 - Add a unit test for the environment_variable_names_equal function.
2143 - Document the --defaults-torrc option, and the new (in 0.2.3)
2144 semantics for overriding, extending, and clearing lists of
2145 options. Closes bug 4748.
2148 Changes in version 0.2.3.17-beta - 2012-06-15
2149 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
2150 gets our TLS handshake back on track for being able to blend in with
2151 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
2152 with Vidalia, and otherwise continues to get us closer to a release
2156 - Enable gcc and ld hardening by default. Resolves ticket 5210.
2157 - Update TLS cipher list to match Firefox 8 and later. Resolves
2159 - Implement the client side of proposal 198: remove support for
2160 clients falsely claiming to support standard ciphersuites that
2161 they can actually provide. As of modern OpenSSL versions, it's not
2162 necessary to fake any standard ciphersuite, and doing so prevents
2163 us from using better ciphersuites in the future, since servers
2164 can't know whether an advertised ciphersuite is really supported or
2165 not. Some hosts -- notably, ones with very old versions of OpenSSL
2166 or where OpenSSL has been built with ECC disabled -- will stand
2167 out because of this change; TBB users should not be affected.
2170 - Change the default value for DynamicDHGroups (introduced in
2171 0.2.3.9-alpha) to 0. This feature can make Tor relays less
2172 identifiable by their use of the mod_ssl DH group, but at
2173 the cost of some usability (#4721) and bridge tracing (#6087)
2174 regressions. Resolves ticket 5598.
2175 - Send a CRLF at the end of each STATUS_* control protocol event. This
2176 bug tickled a bug in Vidalia which would make it freeze. Fixes
2177 bug 6094; bugfix on 0.2.3.16-alpha.
2180 - Disable writing on marked-for-close connections when they are
2181 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
2182 bug 5263; bugfix on 0.0.2pre13, where we first added a special
2183 case for flushing marked connections.
2184 - Detect SSL handshake even when the initial attempt to write the
2185 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
2186 - Change the AllowDotExit rules so they should actually work.
2187 We now enforce AllowDotExit only immediately after receiving an
2188 address via SOCKS or DNSPort: other sources are free to provide
2189 .exit addresses after the resolution occurs. Fixes bug 3940;
2190 bugfix on 0.2.2.1-alpha.
2191 - Fix a (harmless) integer overflow in cell statistics reported by
2192 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
2193 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
2194 right places and never depends on the consensus parameters or
2195 computes adaptive timeouts when it is disabled. Fixes bug 5049;
2196 bugfix on 0.2.2.14-alpha.
2197 - When building Tor on Windows with -DUNICODE (not default), ensure
2198 that error messages, filenames, and DNS server names are always
2199 NUL-terminated when we convert them to a single-byte encoding.
2200 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
2201 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
2202 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
2203 - Fix an edge case where TestingTorNetwork is set but the authorities
2204 and relays all have an uptime of zero, where the private Tor network
2205 could briefly lack support for hidden services. Fixes bug 3886;
2206 bugfix on 0.2.2.18-alpha.
2207 - Correct the manpage's descriptions for the default values of
2208 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
2210 - Fix the documentation for the --hush and --quiet command line
2211 options, which changed their behavior back in 0.2.3.3-alpha.
2212 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
2216 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
2217 more information to it, so that we can track it down in case it
2218 returns again. Mitigates bug 5235.
2219 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
2220 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
2221 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
2222 - Warn the user when HTTPProxy, but no other proxy type, is
2223 configured. This can cause surprising behavior: it doesn't send
2224 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
2225 directory traffic only. Resolves ticket 4663.
2226 - Issue a notice if a guard completes less than 40% of your circuits.
2227 Threshold is configurable by torrc option PathBiasNoticeRate and
2228 consensus parameter pb_noticepct. There is additional, off-by-
2229 default code to disable guards which fail too many circuits.
2230 Addresses ticket 5458.
2231 - Update to the June 6 2012 Maxmind GeoLite Country database.
2233 o Code simplifications and refactoring:
2234 - Remove validate_pluggable_transports_config(): its warning
2235 message is now handled by connection_or_connect().
2238 Changes in version 0.2.2.37 - 2012-06-06
2239 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
2240 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2244 - Work around a bug in OpenSSL that broke renegotiation with TLS
2245 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2246 the v2 Tor connection protocol when both sides were using OpenSSL
2247 1.0.1 would fail. Resolves ticket 6033.
2248 - When waiting for a client to renegotiate, don't allow it to add
2249 any bytes to the input buffer. This fixes a potential DoS issue.
2250 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2251 - Fix an edge case where if we fetch or publish a hidden service
2252 descriptor, we might build a 4-hop circuit and then use that circuit
2253 for exiting afterwards -- even if the new last hop doesn't obey our
2254 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2257 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2258 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2261 - Tell GCC and Clang to check for any errors in format strings passed
2262 to the tor_v*(print|scan)f functions.
2265 Changes in version 0.2.3.16-alpha - 2012-06-05
2266 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
2267 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2268 currently). It also fixes a variety of smaller bugs and other cleanups
2269 that get us closer to a release candidate.
2271 o Major bugfixes (general):
2272 - Work around a bug in OpenSSL that broke renegotiation with TLS
2273 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2274 the v2 Tor connection protocol when both sides were using OpenSSL
2275 1.0.1 would fail. Resolves ticket 6033.
2276 - When waiting for a client to renegotiate, don't allow it to add
2277 any bytes to the input buffer. This fixes a potential DoS issue.
2278 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2279 - Pass correct OR address to managed proxies (like obfsproxy),
2280 even when ORListenAddress is used. Fixes bug 4865; bugfix on
2282 - The advertised platform of a router now includes only its operating
2283 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
2284 service pack level (for Windows) or its CPU architecture (for Unix).
2285 We also no longer include the "git-XYZ" tag in the version. Resolves
2288 o Major bugfixes (clients):
2289 - If we are unable to find any exit that supports our predicted ports,
2290 stop calling them predicted, so that we don't loop and build
2291 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
2292 which introduced predicted ports.
2293 - Fix an edge case where if we fetch or publish a hidden service
2294 descriptor, we might build a 4-hop circuit and then use that circuit
2295 for exiting afterwards -- even if the new last hop doesn't obey our
2296 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2297 - Check at each new consensus whether our entry guards were picked
2298 long enough ago that we should rotate them. Previously, we only
2299 did this check at startup, which could lead to us holding a guard
2300 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
2301 - When fetching a bridge descriptor from a bridge authority,
2302 always do so anonymously, whether we have been able to open
2303 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
2304 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
2305 but we'll need to wait for bug 6010 before it's actually usable.
2307 o Major bugfixes (directory authorities):
2308 - When computing weight parameters, behave more robustly in the
2309 presence of a bad bwweightscale value. Previously, the authorities
2310 would crash if they agreed on a sufficiently broken weight_scale
2311 value: now, they use a reasonable default and carry on. Partial
2312 fix for 5786; bugfix on 0.2.2.17-alpha.
2313 - Check more thoroughly to prevent a rogue authority from
2314 double-voting on any consensus directory parameter. Previously,
2315 authorities would crash in this case if the total number of
2316 votes for any parameter exceeded the number of active voters,
2317 but would let it pass otherwise. Partial fix for bug 5786; bugfix
2321 - Rate-limit log messages when asked to connect anonymously to
2322 a private address. When these hit, they tended to hit fast and
2323 often. Also, don't bother trying to connect to addresses that we
2324 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
2325 reply makes us think we have been lied to, even when the address the
2326 client tried to connect to was "localhost." Resolves ticket 2822.
2327 - Allow packagers to insert an extra string in server descriptor
2328 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
2329 Resolves the rest of ticket 2988.
2330 - Raise the threshold of server descriptors needed (75%) and exit
2331 server descriptors needed (50%) before we will declare ourselves
2332 bootstrapped. This will make clients start building circuits a
2333 little later, but makes the initially constructed circuits less
2334 skewed and less in conflict with further directory fetches. Fixes
2336 - Close any connection that sends unrecognized junk before the
2337 handshake. Solves an issue noted in bug 4369.
2338 - Improve log messages about managed transports. Resolves ticket 5070.
2339 - Tag a bridge's descriptor as "never to be sent unencrypted".
2340 This shouldn't matter, since bridges don't open non-anonymous
2341 connections to the bridge authority and don't allow unencrypted
2342 directory connections from clients, but we might as well make
2343 sure. Closes bug 5139.
2344 - Expose our view of whether we have gone dormant to the controller,
2345 via a new "GETINFO dormant" value. Torbutton and other controllers
2346 can use this to avoid doing periodic requests through Tor while
2347 it's dormant (bug 4718). Fixes bug 5954.
2348 - Tell GCC and Clang to check for any errors in format strings passed
2349 to the tor_v*(print|scan)f functions.
2350 - Update to the May 1 2012 Maxmind GeoLite Country database.
2352 o Minor bugfixes (already included in 0.2.2.36):
2353 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2354 Fixes bug 5346; bugfix on 0.0.8pre3.
2355 - Correct parsing of certain date types in parse_http_time().
2356 Without this patch, If-Modified-Since would behave
2357 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2358 Esteban Manchado Velázques.
2359 - Make our number-parsing functions always treat too-large values
2360 as an error, even when those values exceed the width of the
2361 underlying type. Previously, if the caller provided these
2362 functions with minima or maxima set to the extreme values of the
2363 underlying integer type, these functions would return those
2364 values on overflow rather than treating overflow as an error.
2365 Fixes part of bug 5786; bugfix on 0.0.9.
2366 - If we hit the error case where routerlist_insert() replaces an
2367 existing (old) server descriptor, make sure to remove that
2368 server descriptor from the old_routers list. Fix related to bug
2369 1776. Bugfix on 0.2.2.18-alpha.
2370 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2371 circuits. Fixes issue 5259.
2373 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
2374 - Prevent a null-pointer dereference when receiving a data cell
2375 for a nonexistent stream when the circuit in question has an
2376 empty deliver window. We don't believe this is triggerable,
2377 since we don't currently allow deliver windows to become empty,
2378 but the logic is tricky enough that it's better to make the code
2379 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
2380 - Fix a memory leak when trying to launch a DNS request when the
2381 network is disabled or the nameservers are unconfigurable. Fixes
2382 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
2383 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
2384 - Don't hold a Windows file handle open for every file mapping;
2385 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
2387 - Avoid O(n^2) performance characteristics when parsing a large
2388 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
2389 - Format more doubles with %f, not %lf. Patch from grarpamp to make
2390 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
2392 - Make our replacement implementation of strtok_r() compatible with
2393 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
2394 bugfix on 0.2.2.1-alpha.
2395 - Fix a NULL-pointer dereference on a badly formed
2396 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
2397 bugfix on 0.2.2.9-alpha.
2398 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2399 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2400 - Defensively refactor rend_mid_rendezvous() so that protocol
2401 violations and length checks happen in the beginning. Fixes
2403 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
2404 that IPv6 stuff will compile on MSVC, and compilation issues
2405 will be easier to track down. Fixes bug 5861.
2407 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
2408 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
2409 resource exhaustion, so that clients can adjust their load to
2410 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
2411 started using END_STREAM_REASON_RESOURCELIMIT.
2412 - Don't check for whether the address we're using for outbound
2413 connections has changed until after the outbound connection has
2414 completed. On Windows, getsockname() doesn't succeed until the
2415 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
2416 - If the configuration tries to set MyFamily on a bridge, refuse to
2417 do so, and warn about the security implications. Fixes bug 4657;
2418 bugfix on 0.2.0.3-alpha.
2419 - If the client fails to set a reasonable set of ciphersuites
2420 during its v2 handshake renegotiation, allow the renegotiation to
2421 continue nevertheless (i.e. send all the required certificates).
2422 Fixes bug 4591; bugfix on 0.2.0.20-rc.
2423 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
2424 option is set to 0 (which Vidalia version 0.2.16 now does when
2425 a SAVECONF attempt fails), perform other actions that SIGHUP
2426 usually causes (like reopening the logs). Fixes bug 5095; bugfix
2428 - If we fail to write a microdescriptor to the disk cache, do not
2429 continue replacing the old microdescriptor file. Fixes bug 2954;
2430 bugfix on 0.2.2.6-alpha.
2431 - Exit nodes don't need to fetch certificates for authorities that
2432 they don't recognize; only directory authorities, bridges,
2433 and caches need to do that. Fixes part of bug 2297; bugfix on
2435 - Correctly handle checking the permissions on the parent
2436 directory of a control socket in the root directory. Bug found
2437 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
2439 - When told to add a bridge with the same digest as a preexisting
2440 bridge but a different addr:port, change the addr:port as
2441 requested. Previously we would not notice the change. Fixes half
2442 of bug 5603; fix on 0.2.2.26-beta.
2443 - End AUTHCHALLENGE error messages (in the control protocol) with
2444 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
2446 o Minor bugfixes (on 0.2.3.x):
2447 - Turn an assertion (that the number of handshakes received as a
2448 server is not < 1) into a warning. Fixes bug 4873; bugfix on
2450 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
2451 we had reversed them when the answer was cached.) Fixes bug
2452 5723; bugfix on 0.2.3.1-alpha.
2453 - Work correctly on Linux systems with accept4 support advertised in
2454 their headers, but without accept4 support in the kernel. Fix
2455 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
2456 - When told to add a bridge with the same addr:port as a preexisting
2457 bridge but a different transport, change the transport as
2458 requested. Previously we would not notice the change. Fixes half
2459 of bug 5603; fix on 0.2.3.2-alpha.
2460 - Avoid a "double-reply" warning when replying to a SOCKS request
2461 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
2462 bugfix on 0.2.3.4-alpha.
2463 - Fix a bug where a bridge authority crashes if it has seen no
2464 directory requests when it's time to write statistics to disk.
2465 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
2467 - Don't try to open non-control listeners when DisableNetwork is set.
2468 Previously, we'd open all listeners, then immediately close them.
2469 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
2470 - Don't abort the managed proxy protocol if the managed proxy
2471 sends us an unrecognized line; ignore it instead. Fixes bug
2472 5910; bugfix on 0.2.3.9-alpha.
2473 - Fix a compile warning in crypto.c when compiling with clang 3.1.
2474 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
2475 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
2476 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
2477 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
2478 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
2479 - Resolve numerous small warnings and build issues with MSVC. Resolves
2482 o Documentation fixes:
2483 - Improve the manual's documentation for the NT Service command-line
2484 options. Addresses ticket 3964.
2485 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
2486 - Document the changes to the ORPort and DirPort options, and the
2487 fact that {OR/Dir}ListenAddress is now unnecessary (and
2488 therefore deprecated). Resolves ticket 5597.
2491 - Remove the torrc.bridge file: we don't use it for anything, and
2492 it had become badly desynchronized from torrc.sample. Resolves
2496 Changes in version 0.2.2.36 - 2012-05-24
2497 Tor 0.2.2.36 updates the addresses for two of the eight directory
2498 authorities, fixes some potential anonymity and security issues,
2499 and fixes several crash bugs.
2501 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
2502 known flaws, and nobody should be using them. You should upgrade. If
2503 you're using a Linux or BSD and its packages are obsolete, stop using
2504 those packages and upgrade anyway.
2506 o Directory authority changes:
2507 - Change IP address for maatuska (v3 directory authority).
2508 - Change IP address for ides (v3 directory authority), and rename
2512 - When building or running with any version of OpenSSL earlier
2513 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2514 versions have a bug (CVE-2011-4576) in which their block cipher
2515 padding includes uninitialized data, potentially leaking sensitive
2516 information to any peer with whom they make a SSLv3 connection. Tor
2517 does not use SSL v3 by default, but a hostile client or server
2518 could force an SSLv3 connection in order to gain information that
2519 they shouldn't have been able to get. The best solution here is to
2520 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2521 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2522 to make sure that the bug can't happen.
2523 - Never use a bridge or a controller-supplied node as an exit, even
2524 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2525 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2526 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2527 - Only build circuits if we have a sufficient threshold of the total
2528 descriptors that are marked in the consensus with the "Exit"
2529 flag. This mitigates an attack proposed by wanoskarnet, in which
2530 all of a client's bridges collude to restrict the exit nodes that
2531 the client knows about. Fixes bug 5343.
2532 - Provide controllers with a safer way to implement the cookie
2533 authentication mechanism. With the old method, if another locally
2534 running program could convince a controller that it was the Tor
2535 process, then that program could trick the controller into telling
2536 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2537 authentication method uses a challenge-response approach to prevent
2538 this attack. Fixes bug 5185; implements proposal 193.
2541 - Avoid logging uninitialized data when unable to decode a hidden
2542 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2543 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2544 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2546 - Fix builds when the path to sed, openssl, or sha1sum contains
2547 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2549 - Correct our replacements for the timeradd() and timersub() functions
2550 on platforms that lack them (for example, Windows). The timersub()
2551 function is used when expiring circuits, while timeradd() is
2552 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2553 bugfix on 0.2.2.24-alpha.
2554 - Fix the SOCKET_OK test that we use to tell when socket
2555 creation fails so that it works on Win64. Fixes part of bug 4533;
2556 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2559 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2560 Fixes bug 5346; bugfix on 0.0.8pre3.
2561 - Make our number-parsing functions always treat too-large values
2562 as an error, even when those values exceed the width of the
2563 underlying type. Previously, if the caller provided these
2564 functions with minima or maxima set to the extreme values of the
2565 underlying integer type, these functions would return those
2566 values on overflow rather than treating overflow as an error.
2567 Fixes part of bug 5786; bugfix on 0.0.9.
2568 - Older Linux kernels erroneously respond to strange nmap behavior
2569 by having accept() return successfully with a zero-length
2570 socket. When this happens, just close the connection. Previously,
2571 we would try harder to learn the remote address: but there was
2572 no such remote address to learn, and our method for trying to
2573 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2574 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2575 - Correct parsing of certain date types in parse_http_time().
2576 Without this patch, If-Modified-Since would behave
2577 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2578 Esteban Manchado Velázques.
2579 - Change the BridgePassword feature (part of the "bridge community"
2580 design, which is not yet implemented) to use a time-independent
2581 comparison. The old behavior might have allowed an adversary
2582 to use timing to guess the BridgePassword value. Fixes bug 5543;
2583 bugfix on 0.2.0.14-alpha.
2584 - Detect and reject certain misformed escape sequences in
2585 configuration values. Previously, these values would cause us
2586 to crash if received in a torrc file or over an authenticated
2587 control port. Bug found by Esteban Manchado Velázquez, and
2588 independently by Robert Connolly from Matta Consulting who further
2589 noted that it allows a post-authentication heap overflow. Patch
2590 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2591 bugfix on 0.2.0.16-alpha.
2592 - Fix a compile warning when using the --enable-openbsd-malloc
2593 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2594 - During configure, detect when we're building with clang version
2595 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2596 CFLAGS. clang doesn't support them yet.
2597 - When sending an HTTP/1.1 proxy request, include a Host header.
2598 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2599 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
2600 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
2601 - If we hit the error case where routerlist_insert() replaces an
2602 existing (old) server descriptor, make sure to remove that
2603 server descriptor from the old_routers list. Fix related to bug
2604 1776. Bugfix on 0.2.2.18-alpha.
2606 o Minor bugfixes (documentation and log messages):
2607 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2608 Fixes bug 4856; bugfix on Tor 0.0.6.
2609 - Update "ClientOnly" man page entry to explain that there isn't
2610 really any point to messing with it. Resolves ticket 5005.
2611 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2612 directory authority option (introduced in Tor 0.2.2.34).
2613 - Downgrade the "We're missing a certificate" message from notice
2614 to info: people kept mistaking it for a real problem, whereas it
2615 is seldom the problem even when we are failing to bootstrap. Fixes
2616 bug 5067; bugfix on 0.2.0.10-alpha.
2617 - Correctly spell "connect" in a log message on failure to create a
2618 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
2619 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2620 circuits. Fixes issue 5259.
2623 - Directory authorities now reject versions of Tor older than
2624 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2625 inclusive. These versions accounted for only a small fraction of
2626 the Tor network, and have numerous known security issues. Resolves
2628 - Update to the May 1 2012 Maxmind GeoLite Country database.
2631 - When sending or relaying a RELAY_EARLY cell, we used to convert
2632 it to a RELAY cell if the connection was using the v1 link
2633 protocol. This was a workaround for older versions of Tor, which
2634 didn't handle RELAY_EARLY cells properly. Now that all supported
2635 versions can handle RELAY_EARLY cells, and now that we're enforcing
2636 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2637 remove this workaround. Addresses bug 4786.
2640 Changes in version 0.2.3.15-alpha - 2012-04-30
2641 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
2642 the development branch build on Windows again.
2644 o Minor bugfixes (on 0.2.2.x and earlier):
2645 - Make sure that there are no unhandled pending TLS errors before
2646 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
2647 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
2648 Bugfix on 0.1.0.5-rc; fixes bug 4528.
2649 - Fix an assert that directory authorities could trigger on sighup
2650 during some configuration state transitions. We now don't treat
2651 it as a fatal error when the new descriptor we just generated in
2652 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
2653 - After we pick a directory mirror, we would refuse to use it if
2654 it's in our ExcludeExitNodes list, resulting in mysterious failures
2655 to bootstrap for people who just wanted to avoid exiting from
2656 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
2657 - When building with --enable-static-tor on OpenBSD, do not
2658 erroneously attempt to link -lrt. Fixes bug 5103.
2660 o Minor bugfixes (on 0.2.3.x):
2661 - When Tor is built with kernel headers from a recent (last few
2662 years) Linux kernel, do not fail to run on older (pre-2.6.28
2663 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
2664 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
2666 - Fix compilation with miniupnpc version 1.6; patch from
2667 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
2668 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
2669 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
2670 - Fix compilation on platforms without unistd.h, or where environ
2671 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
2674 - Directory authorities are now a little more lenient at accepting
2675 older router descriptors, or newer router descriptors that don't
2676 make big changes. This should help ameliorate past and future
2677 issues where routers think they have uploaded valid descriptors,
2678 but the authorities don't think so. Fix for ticket 2479.
2679 - Make the code that clients use to detect an address change be
2680 IPv6-aware, so that it won't fill clients' logs with error
2681 messages when trying to get the IPv4 address of an IPv6
2682 connection. Implements ticket 5537.
2685 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
2686 authorities needed to use it for a while to keep the network working
2687 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
2688 that was six months ago. As of now, it should no longer be needed
2692 Changes in version 0.2.3.14-alpha - 2012-04-23
2693 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
2694 candidate. It also dramatically speeds up AES: fast relays should
2695 consider switching to the newer OpenSSL library.
2697 o Directory authority changes:
2698 - Change IP address for ides (v3 directory authority), and rename
2702 - Avoid logging uninitialized data when unable to decode a hidden
2703 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2704 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2705 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2707 - If authorities are unable to get a v2 consensus document from other
2708 directory authorities, they no longer fall back to fetching
2709 them from regular directory caches. Fixes bug 5635; bugfix on
2710 0.2.2.26-beta, where routers stopped downloading v2 consensus
2712 - When we start a Tor client with a normal consensus already cached,
2713 be willing to download a microdescriptor consensus. Fixes bug 4011;
2714 fix on 0.2.3.1-alpha.
2716 o Major features (performance):
2717 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
2718 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
2719 vectorized AES implementations as appropriate. These can be much,
2720 much faster than other AES implementations.
2722 o Minor bugfixes (0.2.2.x and earlier):
2723 - Don't launch more than 10 service-side introduction-point circuits
2724 for a hidden service in five minutes. Previously, we would consider
2725 launching more introduction-point circuits if at least one second
2726 had passed without any introduction-point circuits failing. Fixes
2727 bug 4607; bugfix on 0.0.7pre1.
2728 - Change the BridgePassword feature (part of the "bridge community"
2729 design, which is not yet implemented) to use a time-independent
2730 comparison. The old behavior might have allowed an adversary
2731 to use timing to guess the BridgePassword value. Fixes bug 5543;
2732 bugfix on 0.2.0.14-alpha.
2733 - Enforce correct return behavior of tor_vsscanf() when the '%%'
2734 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
2735 - When sending an HTTP/1.1 proxy request, include a Host header.
2736 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2737 - Don't log that we have "decided to publish new relay descriptor"
2738 unless we are actually publishing a descriptor. Fixes bug 3942;
2739 bugfix on 0.2.2.28-beta.
2741 o Minor bugfixes (0.2.3.x):
2742 - Fix a bug where a bridge authority crashes (on a failed assert)
2743 if it has seen no directory requests when it's time to write
2744 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
2745 - Fix bug stomping on ORPort option NoListen and ignoring option
2746 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
2747 - In the testsuite, provide a large enough buffer in the tor_sscanf
2748 unit test. Otherwise we'd overrun that buffer and crash during
2749 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
2751 - Make sure we create the keys directory if it doesn't exist and we're
2752 about to store the dynamic Diffie-Hellman parameters. Fixes bug
2753 5572; bugfix on 0.2.3.13-alpha.
2754 - Fix a small memory leak when trying to decode incorrect base16
2755 authenticator during SAFECOOKIE authentication. Found by
2756 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
2759 - Add more information to a log statement that might help track down
2760 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
2761 non-IP address" messages (or any Bug messages, for that matter!),
2762 please let us know about it.
2763 - Relays now understand an IPv6 address when they get one from a
2764 directory server. Resolves ticket 4875.
2765 - Resolve IPv6 addresses in bridge and entry statistics to country
2766 code "??" which means we at least count them. Resolves ticket 5053;
2767 improves on 0.2.3.9-alpha.
2768 - Update to the April 3 2012 Maxmind GeoLite Country database.
2769 - Begin a doc/state-contents.txt file to explain the contents of
2770 the Tor state file. Fixes bug 2987.
2772 o Default torrc changes:
2773 - Stop listing "socksport 9050" in torrc.sample. We open a socks
2774 port on 9050 by default anyway, so this should not change anything
2776 - Stop mentioning the deprecated *ListenAddress options in
2777 torrc.sample. Fixes bug 5438.
2778 - Document unit of bandwidth related options in sample torrc.
2782 - The "torify" script no longer supports the "tsocks" socksifier
2783 tool, since tsocks doesn't support DNS and UDP right for Tor.
2784 Everyone should be using torsocks instead. Fixes bugs 3530 and
2785 5180. Based on a patch by "ugh".
2788 - Change the symmetric cipher interface so that creating and
2789 initializing a stream cipher are no longer separate functions.
2790 - Remove all internal support for unpadded RSA. We never used it, and
2791 it would be a bad idea to start.
2794 Changes in version 0.2.3.13-alpha - 2012-03-26
2795 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
2796 in managed pluggable transports, as well as providing other cleanups
2797 that get us closer to a release candidate.
2799 o Directory authority changes:
2800 - Change IP address for maatuska (v3 directory authority).
2803 - Provide controllers with a safer way to implement the cookie
2804 authentication mechanism. With the old method, if another locally
2805 running program could convince a controller that it was the Tor
2806 process, then that program could trick the controller into telling
2807 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2808 authentication method uses a challenge-response approach to prevent
2809 this attack. Fixes bug 5185, implements proposal 193.
2810 - Never use a bridge or a controller-supplied node as an exit, even
2811 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2812 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2813 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2814 - Only build circuits if we have a sufficient threshold of the total
2815 descriptors that are marked in the consensus with the "Exit"
2816 flag. This mitigates an attack proposed by wanoskarnet, in which
2817 all of a client's bridges collude to restrict the exit nodes that
2818 the client knows about. Fixes bug 5343.
2820 o Major bugfixes (on Tor 0.2.3.x):
2821 - Avoid an assert when managed proxies like obfsproxy are configured,
2822 and we receive HUP signals or setconf attempts too rapidly. This
2823 situation happens most commonly when Vidalia tries to attach to
2824 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
2825 bugfix on 0.2.3.6-alpha.
2826 - Fix a relay-side pluggable transports bug where managed proxies were
2827 unreachable from the Internet, because Tor asked them to bind on
2828 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
2829 - Stop discarding command-line arguments when TestingTorNetwork
2830 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
2831 0.2.3.9-alpha, where task 4552 added support for two layers of
2833 - Resume allowing the unit tests to run in gdb. This was accidentally
2834 made impossible when the DisableDebuggerAttachment option was
2835 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
2836 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
2837 0.2.3.11-alpha. Reported by Anthony G. Basile.
2839 o Minor bugfixes (on 0.2.2.x and earlier):
2840 - Ensure we don't cannibalize circuits that are longer than three hops
2841 already, so we don't end up making circuits with 5 or more
2842 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
2843 0.1.0.1-rc which introduced cannibalization.
2844 - Detect and reject certain misformed escape sequences in
2845 configuration values. Previously, these values would cause us
2846 to crash if received in a torrc file or over an authenticated
2847 control port. Bug found by Esteban Manchado Velázquez, and
2848 independently by Robert Connolly from Matta Consulting who further
2849 noted that it allows a post-authentication heap overflow. Patch
2850 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2851 bugfix on 0.2.0.16-alpha.
2852 - Fix a compile warning when using the --enable-openbsd-malloc
2853 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2854 - Directory caches no longer refuse to clean out descriptors because
2855 of missing v2 networkstatus documents, unless they're configured
2856 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
2857 0.2.2.26-beta. Patch by Daniel Bryg.
2858 - Update to the latest version of the tinytest unit testing framework.
2859 This includes a couple of bugfixes that can be relevant for
2860 running forked unit tests on Windows, and removes all reserved
2863 o Minor bugfixes (on 0.2.3.x):
2864 - On a failed pipe() call, don't leak file descriptors. Fixes bug
2865 4296; bugfix on 0.2.3.1-alpha.
2866 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
2867 until after we have received a CERTS cell. Fixes bug 4361; bugfix
2868 on 0.2.3.6-alpha. Patch by "frosty".
2869 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
2870 option, so that the IP stack doesn't decide to use it for IPv4
2871 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
2872 - Ensure that variables set in Tor's environment cannot override
2873 environment variables that Tor passes to a managed
2874 pluggable-transport proxy. Previously, Tor would pass every
2875 variable in its environment to managed proxies along with the new
2876 ones, in such a way that on many operating systems, the inherited
2877 environment variables would override those which Tor tried to
2878 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
2879 bugfix on 0.2.3.9-alpha for Windows.
2882 - A wide variety of new unit tests by Esteban Manchado Velázquez.
2883 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
2884 - Update to the March 6 2012 Maxmind GeoLite Country database.
2887 Changes in version 0.2.3.12-alpha - 2012-02-13
2888 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
2889 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
2890 when Tor is configured to use a pluggable transport like obfsproxy.
2893 - Fix builds when the path to sed, openssl, or sha1sum contains
2894 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2896 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
2897 connections. This change should allow busy exit relays to stop
2898 running out of available sockets as quickly. Fixes bug 4950;
2899 bugfix on 0.2.2.26-beta.
2900 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
2901 would ask the bridge for microdescriptors, which are only supported
2902 in 0.2.3.x, and then fail to bootstrap when it didn't get the
2903 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
2904 - Properly set up obfsproxy's environment when in managed mode. The
2905 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
2906 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
2907 5076 and 5082; bugfix on 0.2.3.6-alpha.
2910 - Use the dead_strip option when building Tor on OS X. This reduces
2911 binary size by almost 19% when linking openssl and libevent
2912 statically, which we do for Tor Browser Bundle.
2913 - Fix broken URLs in the sample torrc file, and tell readers about
2914 the OutboundBindAddress, ExitPolicyRejectPrivate, and
2915 PublishServerDescriptor options. Addresses bug 4652.
2916 - Update to the February 7 2012 Maxmind GeoLite Country database.
2919 - Downgrade the "We're missing a certificate" message from notice
2920 to info: people kept mistaking it for a real problem, whereas it
2921 is seldom the problem even when we are failing to bootstrap. Fixes
2922 bug 5067; bugfix on 0.2.0.10-alpha.
2923 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
2924 managed pluggable transport server proxy's environment.
2925 Previously, we would put it there, even though Tor doesn't
2926 implement an 'extended server port' yet, and even though Tor
2927 almost certainly isn't listening at that address. For now, we set
2928 it to an empty string to avoid crashing older obfsproxies. Bugfix
2930 - Log the heartbeat message every HeartbeatPeriod seconds, not every
2931 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
2932 0.2.3.1-alpha. Bug reported by Scott Bennett.
2933 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
2934 bugfix on 0.2.3.11-alpha.
2935 - Update "ClientOnly" man page entry to explain that there isn't
2936 really any point to messing with it. Resolves ticket 5005.
2937 - Use the correct CVE number for CVE-2011-4576 in our comments and
2938 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
2941 o Code simplifications and refactoring:
2942 - Use the _WIN32 macro throughout our code to detect Windows.
2943 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
2947 Changes in version 0.2.3.11-alpha - 2012-01-22
2948 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
2949 the last step of the plan to limit maximum circuit length, includes
2950 a wide variety of hidden service performance and correctness fixes,
2951 works around an OpenSSL security flaw if your distro is too stubborn
2952 to upgrade, and fixes a bunch of smaller issues.
2955 - Now that Tor 0.2.0.x is completely deprecated, enable the final
2956 part of "Proposal 110: Avoiding infinite length circuits" by
2957 refusing all circuit-extend requests that do not use a relay_early
2958 cell. This change helps Tor resist a class of denial-of-service
2959 attacks by limiting the maximum circuit length.
2960 - Adjust the number of introduction points that a hidden service
2961 will try to maintain based on how long its introduction points
2962 remain in use and how many introductions they handle. Fixes
2964 - Try to use system facilities for enumerating local interface
2965 addresses, before falling back to our old approach (which was
2966 binding a UDP socket, and calling getsockname() on it). That
2967 approach was scaring OS X users whose draconian firewall
2968 software warned about binding to UDP sockets, regardless of
2969 whether packets were sent. Now we try to use getifaddrs(),
2970 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
2971 system supports. Resolves ticket 1827.
2973 o Major security workaround:
2974 - When building or running with any version of OpenSSL earlier
2975 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2976 versions have a bug (CVE-2011-4576) in which their block cipher
2977 padding includes uninitialized data, potentially leaking sensitive
2978 information to any peer with whom they make a SSLv3 connection. Tor
2979 does not use SSL v3 by default, but a hostile client or server
2980 could force an SSLv3 connection in order to gain information that
2981 they shouldn't have been able to get. The best solution here is to
2982 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2983 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2984 to make sure that the bug can't happen.
2987 - Fix the SOCKET_OK test that we use to tell when socket
2988 creation fails so that it works on Win64. Fixes part of bug 4533;
2989 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2990 - Correct our replacements for the timeradd() and timersub() functions
2991 on platforms that lack them (for example, Windows). The timersub()
2992 function is used when expiring circuits, while timeradd() is
2993 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2994 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
2995 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
2996 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
2997 bug at runtime, not compile time, because some distributions hack
2998 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
2999 on 0.2.3.9-alpha. Found by Pascal.
3001 o Minor features (controller):
3002 - Use absolute path names when reporting the torrc filename in the
3003 control protocol, so a controller can more easily find the torrc
3004 file. Resolves bug 1101.
3005 - Extend the control protocol to report flags that control a circuit's
3006 path selection in CIRC events and in replies to 'GETINFO
3007 circuit-status'. Implements part of ticket 2411.
3008 - Extend the control protocol to report the hidden service address
3009 and current state of a hidden-service-related circuit in CIRC
3010 events and in replies to 'GETINFO circuit-status'. Implements part
3012 - When reporting the path to the cookie file to the controller,
3013 give an absolute path. Resolves ticket 4881.
3014 - Allow controllers to request an event notification whenever a
3015 circuit is cannibalized or its purpose is changed. Implements
3016 part of ticket 3457.
3017 - Include the creation time of a circuit in CIRC and CIRC2
3018 control-port events and the list produced by the 'GETINFO
3019 circuit-status' control-port command.
3021 o Minor features (directory authorities):
3022 - Directory authorities now reject versions of Tor older than
3023 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
3024 inclusive. These versions accounted for only a small fraction of
3025 the Tor network, and have numerous known security issues. Resolves
3027 - Authority operators can now vote for all relays in a given
3028 set of countries to be BadDir/BadExit/Invalid/Rejected.
3029 - Provide two consensus parameters (FastFlagMinThreshold and
3030 FastFlagMaxThreshold) to control the range of allowable bandwidths
3031 for the Fast directory flag. These allow authorities to run
3032 experiments on appropriate requirements for being a "Fast" node.
3033 The AuthDirFastGuarantee config value still applies. Implements
3035 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
3036 directory authority option (introduced in Tor 0.2.2.34).
3038 o Minor features (other):
3039 - Don't disable the DirPort when we cannot exceed our AccountingMax
3040 limit during this interval because the effective bandwidthrate is
3041 low enough. This is useful in a situation where AccountMax is only
3042 used as an additional safeguard or to provide statistics.
3043 - Prepend an informative header to generated dynamic_dh_params files.
3044 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
3045 EntryNodes will have no effect. Resolves issue 2571.
3046 - Log more useful messages when we fail to disable debugger
3048 - Log which authority we're missing votes from when we go to fetch
3049 them from the other auths.
3050 - Log (at debug level) whenever a circuit's purpose is changed.
3051 - Add missing documentation for the MaxClientCircuitsPending,
3052 UseMicrodescriptors, UserspaceIOCPBuffers, and
3053 _UseFilteringSSLBufferevents options, all introduced during
3055 - Update to the January 3 2012 Maxmind GeoLite Country database.
3057 o Minor bugfixes (hidden services):
3058 - Don't close hidden service client circuits which have almost
3059 finished connecting to their destination when they reach
3060 the normal circuit-build timeout. Previously, we would close
3061 introduction circuits which are waiting for an acknowledgement
3062 from the introduction point, and rendezvous circuits which have
3063 been specified in an INTRODUCE1 cell sent to a hidden service,
3064 after the normal CBT. Now, we mark them as 'timed out', and launch
3065 another rendezvous attempt in parallel. This behavior change can
3066 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
3067 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
3068 - Don't close hidden-service-side rendezvous circuits when they
3069 reach the normal circuit-build timeout. This behaviour change can
3070 be disabled using the new
3071 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
3072 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
3073 - Make sure we never mark the wrong rendezvous circuit as having
3074 had its introduction cell acknowleged by the introduction-point
3075 relay. Previously, when we received an INTRODUCE_ACK cell on a
3076 client-side hidden-service introduction circuit, we might have
3077 marked a rendezvous circuit other than the one we specified in
3078 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
3079 a warning message and interfered with the hidden service
3080 connection-establishment process. Fixes bug 4759; bugfix on
3081 0.2.3.3-alpha, when we added the stream-isolation feature which
3082 might cause Tor to open multiple rendezvous circuits for the same
3084 - Don't trigger an assertion failure when we mark a new client-side
3085 hidden-service introduction circuit for close during the process
3086 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
3089 o Minor bugfixes (log messages):
3090 - Correctly spell "connect" in a log message on failure to create a
3091 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
3093 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
3094 Fixes bug 4856; bugfix on Tor 0.0.6.
3095 - Fix the log message describing how we work around discovering
3096 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
3097 4837; bugfix on 0.2.2.9-alpha.
3098 - When logging about a disallowed .exit name, do not also call it
3099 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
3101 o Minor bugfixes (build fixes):
3102 - During configure, detect when we're building with clang version
3103 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
3104 CFLAGS. clang doesn't support them yet.
3105 - During configure, search for library containing cos function as
3106 libm lives in libcore on some platforms (BeOS/Haiku). Linking
3107 against libm was hard-coded before. Fixes the first part of bug
3108 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
3110 - Detect attempts to build Tor on (as yet hypothetical) versions
3111 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
3112 fix for bug 4533. Bugfix on 0.2.2.28-beta.
3113 - Preprocessor directives should not be put inside the arguments
3114 of a macro. This would break compilation with GCC releases prior
3115 to version 3.3. We would never recommend such an old GCC version,
3116 but it is apparently required for binary compatibility on some
3117 platforms (namely, certain builds of Haiku). Fixes the other part
3118 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
3121 o Minor bugfixes (other):
3122 - Older Linux kernels erroneously respond to strange nmap behavior
3123 by having accept() return successfully with a zero-length
3124 socket. When this happens, just close the connection. Previously,
3125 we would try harder to learn the remote address: but there was
3126 no such remote address to learn, and our method for trying to
3127 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
3128 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
3129 - Fix null-pointer access that could occur if TLS allocation failed.
3130 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
3131 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
3132 accidentally been reverted.
3133 - Fix our implementation of crypto_random_hostname() so it can't
3134 overflow on ridiculously large inputs. (No Tor version has ever
3135 provided this kind of bad inputs, but let's be correct in depth.)
3136 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
3137 - Find more places in the code that should have been testing for
3138 invalid sockets using the SOCKET_OK macro. Required for a fix
3139 for bug 4533. Bugfix on 0.2.2.28-beta.
3140 - Fix an assertion failure when, while running with bufferevents, a
3141 connection finishes connecting after it is marked for close, but
3142 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
3143 - test_util_spawn_background_ok() hardcoded the expected value
3144 for ENOENT to 2. This isn't portable as error numbers are
3145 platform specific, and particularly the hurd has ENOENT at
3146 0x40000002. Construct expected string at runtime, using the correct
3147 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
3148 - Reject attempts to disable DisableDebuggerAttachment while Tor is
3149 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
3150 - Use an appropriate-width type for sockets in tor-fw-helper on
3151 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
3154 - When sending or relaying a RELAY_EARLY cell, we used to convert
3155 it to a RELAY cell if the connection was using the v1 link
3156 protocol. This was a workaround for older versions of Tor, which
3157 didn't handle RELAY_EARLY cells properly. Now that all supported
3158 versions can handle RELAY_EARLY cells, and now that we're enforcing
3159 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
3160 remove this workaround. Addresses bug 4786.
3162 o Code simplifications and refactoring:
3163 - Use OpenSSL's built-in SSL_state_string_long() instead of our
3164 own homebrewed ssl_state_to_string() replacement. Patch from
3165 Emile Snyder. Fixes bug 4653.
3166 - Use macros to indicate OpenSSL versions, so we don't need to worry
3167 about accidental hexadecimal bit shifts.
3168 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
3170 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
3171 - Use the smartlist_add_asprintf() alias more consistently.
3172 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
3173 invalid value, rather than just -1.
3174 - Rename a handful of old identifiers, mostly related to crypto
3175 structures and crypto functions. By convention, our "create an
3176 object" functions are called "type_new()", our "free an object"
3177 functions are called "type_free()", and our types indicate that
3178 they are types only with a final "_t". But a handful of older
3179 types and functions broke these rules, with function names like
3180 "type_create" or "subsystem_op_type", or with type names like
3184 Changes in version 0.2.3.10-alpha - 2011-12-16
3185 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
3186 Tor's buffers code. Absolutely everybody should upgrade.
3188 The bug relied on an incorrect calculation when making data continuous
3189 in one of our IO buffers, if the first chunk of the buffer was
3190 misaligned by just the wrong amount. The miscalculation would allow an
3191 attacker to overflow a piece of heap-allocated memory. To mount this
3192 attack, the attacker would need to either open a SOCKS connection to
3193 Tor's SocksPort (usually restricted to localhost), or target a Tor
3194 instance configured to make its connections through a SOCKS proxy
3195 (which Tor does not do by default).
3197 Good security practice requires that all heap-overflow bugs should be
3198 presumed to be exploitable until proven otherwise, so we are treating
3199 this as a potential code execution attack. Please upgrade immediately!
3200 This bug does not affect bufferevents-based builds of Tor. Special
3201 thanks to "Vektor" for reporting this issue to us!
3203 This release also contains a few minor bugfixes for issues discovered
3207 - Fix a heap overflow bug that could occur when trying to pull
3208 data into the first chunk of a buffer, when that chunk had
3209 already had some data drained from it. Fixes CVE-2011-2778;
3210 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3213 - If we can't attach streams to a rendezvous circuit when we
3214 finish connecting to a hidden service, clear the rendezvous
3215 circuit's stream-isolation state and try to attach streams
3216 again. Previously, we cleared rendezvous circuits' isolation
3217 state either too early (if they were freshly built) or not at all
3218 (if they had been built earlier and were cannibalized). Bugfix on
3219 0.2.3.3-alpha; fixes bug 4655.
3220 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
3221 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
3222 - Fix an assertion failure when a relay with accounting enabled
3223 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
3226 - Update to the December 6 2011 Maxmind GeoLite Country database.
3229 Changes in version 0.2.2.35 - 2011-12-16
3230 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
3231 buffers code. Absolutely everybody should upgrade.
3233 The bug relied on an incorrect calculation when making data continuous
3234 in one of our IO buffers, if the first chunk of the buffer was
3235 misaligned by just the wrong amount. The miscalculation would allow an
3236 attacker to overflow a piece of heap-allocated memory. To mount this
3237 attack, the attacker would need to either open a SOCKS connection to
3238 Tor's SocksPort (usually restricted to localhost), or target a Tor
3239 instance configured to make its connections through a SOCKS proxy
3240 (which Tor does not do by default).
3242 Good security practice requires that all heap-overflow bugs should be
3243 presumed to be exploitable until proven otherwise, so we are treating
3244 this as a potential code execution attack. Please upgrade immediately!
3245 This bug does not affect bufferevents-based builds of Tor. Special
3246 thanks to "Vektor" for reporting this issue to us!
3248 Tor 0.2.2.35 also fixes several bugs in previous versions, including
3249 crash bugs for unusual configurations, and a long-term bug that
3250 would prevent Tor from starting on Windows machines with draconian
3253 With this release, we remind everyone that 0.2.0.x has reached its
3254 formal end-of-life. Those Tor versions have many known flaws, and
3255 nobody should be using them. You should upgrade -- ideally to the
3256 0.2.2.x series. If you're using a Linux or BSD and its packages are
3257 obsolete, stop using those packages and upgrade anyway.
3259 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
3260 longer receive support after some time in early 2012.
3263 - Fix a heap overflow bug that could occur when trying to pull
3264 data into the first chunk of a buffer, when that chunk had
3265 already had some data drained from it. Fixes CVE-2011-2778;
3266 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3267 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3268 that it doesn't attempt to allocate a socketpair. This could cause
3269 some problems on Windows systems with overzealous firewalls. Fix for
3270 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3272 - If we mark an OR connection for close based on a cell we process,
3273 don't process any further cells on it. We already avoid further
3274 reads on marked-for-close connections, but now we also discard the
3275 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3276 which was the first version where we might mark a connection for
3277 close based on processing a cell on it.
3278 - Correctly sanity-check that we don't underflow on a memory
3279 allocation (and then assert) for hidden service introduction
3280 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3281 bugfix on 0.2.1.5-alpha.
3282 - Fix a memory leak when we check whether a hidden service
3283 descriptor has any usable introduction points left. Fixes bug
3284 4424. Bugfix on 0.2.2.25-alpha.
3285 - Don't crash when we're running as a relay and don't have a GeoIP
3286 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
3287 we've had in the 0.2.3.x branch already.
3288 - When running as a client, do not print a misleading (and plain
3289 wrong) log message that we're collecting "directory request"
3290 statistics: clients don't collect statistics. Also don't create a
3291 useless (because empty) stats file in the stats/ directory. Fixes
3292 bug 4353; bugfix on 0.2.2.34.
3295 - Detect failure to initialize Libevent. This fix provides better
3296 detection for future instances of bug 4457.
3297 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3298 function. This was eating up hideously large amounts of time on some
3299 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3300 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3301 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3303 - Don't warn about unused log_mutex in log.c when building with
3304 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3305 0.1.0.6-rc which introduced --disable-threads.
3306 - When configuring, starting, or stopping an NT service, stop
3307 immediately after the service configuration attempt has succeeded
3308 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3309 - When sending a NETINFO cell, include the original address
3310 received for the other side, not its canonical address. Found
3311 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3312 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
3313 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3314 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3315 occurred when a client tried to fetch a descriptor for a bridge
3316 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3317 - Backport fixes for a pair of compilation warnings on Windows.
3318 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
3319 - If we had ever tried to call tor_addr_to_str on an address of
3320 unknown type, we would have done a strdup on an uninitialized
3321 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3322 Reported by "troll_un".
3323 - Correctly detect and handle transient lookup failures from
3324 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3325 Reported by "troll_un".
3326 - Fix null-pointer access that could occur if TLS allocation failed.
3327 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3328 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3329 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3332 - Add two new config options for directory authorities:
3333 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3334 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3335 that is always sufficient to satisfy the bandwidth requirement for
3336 the Guard flag. Now it will be easier for researchers to simulate
3337 Tor networks with different values. Resolves ticket 4484.
3338 - When Tor ignores a hidden service specified in its configuration,
3339 include the hidden service's directory in the warning message.
3340 Previously, we would only tell the user that some hidden service
3341 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3342 - Update to the December 6 2011 Maxmind GeoLite Country database.
3344 o Packaging changes:
3345 - Make it easier to automate expert package builds on Windows,
3346 by removing an absolute path from makensis.exe command.
3349 Changes in version 0.2.1.32 - 2011-12-16
3350 Tor 0.2.1.32 backports important security and privacy fixes for
3351 oldstable. This release is intended only for package maintainers and
3352 others who cannot use the 0.2.2 stable series. All others should be
3353 using Tor 0.2.2.x or newer.
3355 The Tor 0.2.1.x series will reach formal end-of-life some time in
3356 early 2012; we will stop releasing patches for it then.
3358 o Major bugfixes (also included in 0.2.2.x):
3359 - Correctly sanity-check that we don't underflow on a memory
3360 allocation (and then assert) for hidden service introduction
3361 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3362 bugfix on 0.2.1.5-alpha.
3363 - Fix a heap overflow bug that could occur when trying to pull
3364 data into the first chunk of a buffer, when that chunk had
3365 already had some data drained from it. Fixes CVE-2011-2778;
3366 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3369 - Update to the December 6 2011 Maxmind GeoLite Country database.
3372 Changes in version 0.2.3.9-alpha - 2011-12-08
3373 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
3374 a "DisableNetwork" security feature that bundles can use to avoid
3375 touching the network until bridges are configured, moves forward on
3376 the pluggable transport design, fixes a flaw in the hidden service
3377 design that unnecessarily prevented clients with wrong clocks from
3378 reaching hidden services, and fixes a wide variety of other issues.
3381 - Clients can now connect to private bridges over IPv6. Bridges
3382 still need at least one IPv4 address in order to connect to
3383 other relays. Note that we don't yet handle the case where the
3384 user has two bridge lines for the same bridge (one IPv4, one
3385 IPv6). Implements parts of proposal 186.
3386 - New "DisableNetwork" config option to prevent Tor from launching any
3387 connections or accepting any connections except on a control port.
3388 Bundles and controllers can set this option before letting Tor talk
3389 to the rest of the network, for example to prevent any connections
3390 to a non-bridge address. Packages like Orbot can also use this
3391 option to instruct Tor to save power when the network is off.
3392 - Clients and bridges can now be configured to use a separate
3393 "transport" proxy. This approach makes the censorship arms race
3394 easier by allowing bridges to use protocol obfuscation plugins. It
3395 implements the "managed proxy" part of proposal 180 (ticket 3472).
3396 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
3397 implementation. It makes AES_CTR about 7% faster than our old one
3398 (which was about 10% faster than the one OpenSSL used to provide).
3399 Resolves ticket 4526.
3400 - Add a "tor2web mode" for clients that want to connect to hidden
3401 services non-anonymously (and possibly more quickly). As a safety
3402 measure to try to keep users from turning this on without knowing
3403 what they are doing, tor2web mode must be explicitly enabled at
3404 compile time, and a copy of Tor compiled to run in tor2web mode
3405 cannot be used as a normal Tor client. Implements feature 2553.
3406 - Add experimental support for running on Windows with IOCP and no
3407 kernel-space socket buffers. This feature is controlled by a new
3408 "UserspaceIOCPBuffers" config option (off by default), which has
3409 no effect unless Tor has been built with support for bufferevents,
3410 is running on Windows, and has enabled IOCP. This may, in the long
3411 run, help solve or mitigate bug 98.
3412 - Use a more secure consensus parameter voting algorithm. Now at
3413 least three directory authorities or a majority of them must
3414 vote on a given parameter before it will be included in the
3415 consensus. Implements proposal 178.
3418 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
3419 They used to check that the timestamp was within 30 minutes
3420 of their system clock, so they could cap the size of their
3421 replay-detection cache, but that approach unnecessarily refused
3422 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
3423 the v3 intro-point protocol (the first one which sent a timestamp
3424 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
3425 - Only use the EVP interface when AES acceleration is enabled,
3426 to avoid a 5-7% performance regression. Resolves issue 4525;
3427 bugfix on 0.2.3.8-alpha.
3429 o Privacy/anonymity features (bridge detection):
3430 - Make bridge SSL certificates a bit more stealthy by using random
3431 serial numbers, in the same fashion as OpenSSL when generating
3432 self-signed certificates. Implements ticket 4584.
3433 - Introduce a new config option "DynamicDHGroups", enabled by
3434 default, which provides each bridge with a unique prime DH modulus
3435 to be used during SSL handshakes. This option attempts to help
3436 against censors who might use the Apache DH modulus as a static
3437 identifier for bridges. Addresses ticket 4548.
3439 o Minor features (new/different config options):
3440 - New configuration option "DisableDebuggerAttachment" (on by default)
3441 to prevent basic debugging attachment attempts by other processes.
3442 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
3443 - Allow MapAddress directives to specify matches against super-domains,
3444 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
3445 Implements issue 933.
3446 - Slightly change behavior of "list" options (that is, config
3447 options that can appear more than once) when they appear both in
3448 torrc and on the command line. Previously, the command-line options
3449 would be appended to the ones from torrc. Now, the command-line
3450 options override the torrc options entirely. This new behavior
3451 allows the user to override list options (like exit policies and
3452 ports to listen on) from the command line, rather than simply
3453 appending to the list.
3454 - You can get the old (appending) command-line behavior for "list"
3455 options by prefixing the option name with a "+".
3456 - You can remove all the values for a "list" option from the command
3457 line without adding any new ones by prefixing the option name
3459 - Add experimental support for a "defaults" torrc file to be parsed
3460 before the regular torrc. Torrc options override the defaults file's
3461 options in the same way that the command line overrides the torrc.
3462 The SAVECONF controller command saves only those options which
3463 differ between the current configuration and the defaults file. HUP
3464 reloads both files. (Note: This is an experimental feature; its
3465 behavior will probably be refined in future 0.2.3.x-alpha versions
3466 to better meet packagers' needs.) Implements task 4552.
3469 - Try to make the introductory warning message that Tor prints on
3470 startup more useful for actually finding help and information.
3471 Resolves ticket 2474.
3472 - Running "make version" now displays the version of Tor that
3473 we're about to build. Idea from katmagic; resolves issue 4400.
3474 - Expire old or over-used hidden service introduction points.
3475 Required by fix for bug 3460.
3476 - Move the replay-detection cache for the RSA-encrypted parts of
3477 INTRODUCE2 cells to the introduction point data structures.
3478 Previously, we would use one replay-detection cache per hidden
3479 service. Required by fix for bug 3460.
3480 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
3481 public key replay-detection cache from 60 minutes to 5 minutes. This
3482 replay-detection cache is now used only to detect multiple
3483 INTRODUCE2 cells specifying the same rendezvous point, so we can
3484 avoid launching multiple simultaneous attempts to connect to it.
3486 o Minor bugfixes (on Tor 0.2.2.x and earlier):
3487 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3488 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3490 - Fix a minor formatting issue in one of tor-gencert's error messages.
3492 - Prevent a false positive from the check-spaces script, by disabling
3493 the "whitespace between function name and (" check for functions
3495 - Fix a log message suggesting that people contact a non-existent
3496 email address. Fixes bug 3448.
3497 - Fix null-pointer access that could occur if TLS allocation failed.
3498 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3499 - Report a real bootstrap problem to the controller on router
3500 identity mismatch. Previously we just said "foo", which probably
3501 made a lot of sense at the time. Fixes bug 4169; bugfix on
3503 - If we had ever tried to call tor_addr_to_str() on an address of
3504 unknown type, we would have done a strdup() on an uninitialized
3505 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3506 Reported by "troll_un".
3507 - Correctly detect and handle transient lookup failures from
3508 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3509 Reported by "troll_un".
3510 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3511 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3512 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
3513 bug 4532; found by "troll_un".
3515 o Minor bugfixes (on Tor 0.2.3.x):
3516 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
3518 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
3519 circuit for use as a hidden service client's rendezvous point.
3520 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
3521 with help from wanoskarnet.
3522 - Restore behavior of overriding SocksPort, ORPort, and similar
3523 options from the command line. Bugfix on 0.2.3.3-alpha.
3526 - Properly handle the case where the build-tree is not the same
3527 as the source tree when generating src/common/common_sha1.i,
3528 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
3529 bugfix on 0.2.0.1-alpha.
3531 o Code simplifications, cleanups, and refactorings:
3532 - Remove the pure attribute from all functions that used it
3533 previously. In many cases we assigned it incorrectly, because the
3534 functions might assert or call impure functions, and we don't have
3535 evidence that keeping the pure attribute is worthwhile. Implements
3536 changes suggested in ticket 4421.
3537 - Remove some dead code spotted by coverity. Fixes cid 432.
3538 Bugfix on 0.2.3.1-alpha, closes bug 4637.
3541 Changes in version 0.2.3.8-alpha - 2011-11-22
3542 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
3543 socketpair-related bug that has been bothering Windows users. It adds
3544 support to serve microdescriptors to controllers, so Vidalia's network
3545 map can resume listing relays (once Vidalia implements its side),
3546 and adds better support for hardware AES acceleration. Finally, it
3547 starts the process of adjusting the bandwidth cutoff for getting the
3548 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
3549 that tiny relays harm performance more than they help network capacity.
3552 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3553 that it doesn't attempt to allocate a socketpair. This could cause
3554 some problems on Windows systems with overzealous firewalls. Fix for
3555 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3557 - Correctly sanity-check that we don't underflow on a memory
3558 allocation (and then assert) for hidden service introduction
3559 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3560 bugfix on 0.2.1.5-alpha.
3561 - Remove the artificially low cutoff of 20KB to guarantee the Fast
3562 flag. In the past few years the average relay speed has picked
3563 up, and while the "top 7/8 of the network get the Fast flag" and
3564 "all relays with 20KB or more of capacity get the Fast flag" rules
3565 used to have the same result, now the top 7/8 of the network has
3566 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
3567 - Fix a rare assertion failure when checking whether a v0 hidden
3568 service descriptor has any usable introduction points left, and
3569 we don't have enough information to build a circuit to the first
3570 intro point named in the descriptor. The HS client code in
3571 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
3572 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
3573 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
3574 - Make bridge authorities not crash when they are asked for their own
3575 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
3576 - When running as a client, do not print a misleading (and plain
3577 wrong) log message that we're collecting "directory request"
3578 statistics: clients don't collect statistics. Also don't create a
3579 useless (because empty) stats file in the stats/ directory. Fixes
3580 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
3583 - Allow Tor controllers like Vidalia to obtain the microdescriptor
3584 for a relay by identity digest or nickname. Previously,
3585 microdescriptors were only available by their own digests, so a
3586 controller would have to ask for and parse the whole microdescriptor
3587 consensus in order to look up a single relay's microdesc. Fixes
3588 bug 3832; bugfix on 0.2.3.1-alpha.
3589 - Use OpenSSL's EVP interface for AES encryption, so that all AES
3590 operations can use hardware acceleration (if present). Resolves
3593 o Minor bugfixes (on 0.2.2.x and earlier):
3594 - Detect failure to initialize Libevent. This fix provides better
3595 detection for future instances of bug 4457.
3596 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3597 function. This was eating up hideously large amounts of time on some
3598 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3599 - Don't warn about unused log_mutex in log.c when building with
3600 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3601 0.1.0.6-rc which introduced --disable-threads.
3602 - Allow manual 'authenticate' commands to the controller interface
3603 from netcat (nc) as well as telnet. We were rejecting them because
3604 they didn't come with the expected whitespace at the end of the
3605 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
3606 - Fix some (not actually triggerable) buffer size checks in usage of
3607 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
3609 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
3610 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
3611 - When configuring, starting, or stopping an NT service, stop
3612 immediately after the service configuration attempt has succeeded
3613 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3614 - When sending a NETINFO cell, include the original address
3615 received for the other side, not its canonical address. Found
3616 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3617 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
3618 can pick them up when the tests aren't disabled. Bugfix on
3619 0.2.2.4-alpha which introduced tinytest.
3620 - Fix a memory leak when we check whether a hidden service
3621 descriptor has any usable introduction points left. Fixes bug
3622 4424. Bugfix on 0.2.2.25-alpha.
3623 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3624 occurred when a client tried to fetch a descriptor for a bridge
3625 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3627 o Minor bugfixes (on 0.2.3.x):
3628 - Make util unit tests build correctly with MSVC. Bugfix on
3629 0.2.3.3-alpha. Patch by Gisle Vanem.
3630 - Successfully detect AUTH_CHALLENGE cells with no recognized
3631 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
3633 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
3634 it should still send a NETINFO cell to allow the connection to
3635 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
3637 - Log less loudly when we get an invalid authentication certificate
3638 from a source other than a directory authority: it's not unusual
3639 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
3641 - Tolerate servers with more clock skew in their authentication
3642 certificates than previously. Fixes bug 4371; bugfix on
3644 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
3645 on 0.2.3.4-alpha and 0.2.3.6-alpha.
3648 - Add two new config options for directory authorities:
3649 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3650 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3651 that is always sufficient to satisfy the bandwidth requirement for
3652 the Guard flag. Now it will be easier for researchers to simulate
3653 Tor networks with different values. Resolves ticket 4484.
3654 - When Tor ignores a hidden service specified in its configuration,
3655 include the hidden service's directory in the warning message.
3656 Previously, we would only tell the user that some hidden service
3657 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3658 - When we fail to initialize Libevent, retry with IOCP disabled so we
3659 don't need to turn on multi-threading support in Libevent, which in
3660 turn requires a working socketpair(). This is a workaround for bug
3661 4457, which affects Libevent versions from 2.0.1-alpha through
3663 - Detect when we try to build on a platform that doesn't define
3664 AF_UNSPEC to 0. We don't work there, so refuse to compile.
3665 - Update to the November 1 2011 Maxmind GeoLite Country database.
3667 o Packaging changes:
3668 - Make it easier to automate expert package builds on Windows,
3669 by removing an absolute path from makensis.exe command.
3671 o Code simplifications and refactoring:
3672 - Remove some redundant #include directives throughout the code.
3673 Patch from Andrea Gelmini.
3674 - Unconditionally use OpenSSL's AES implementation instead of our
3675 old built-in one. OpenSSL's AES has been better for a while, and
3676 relatively few servers should still be on any version of OpenSSL
3677 that doesn't have good optimized assembly AES.
3678 - Use the name "CERTS" consistently to refer to the new cell type;
3679 we were calling it CERT in some places and CERTS in others.
3682 - Numerous new unit tests for functions in util.c and address.c by
3684 - The long-disabled benchmark tests are now split into their own
3685 ./src/test/bench binary.
3686 - The benchmark tests can now use more accurate timers than
3687 gettimeofday() when such timers are available.
3690 Changes in version 0.2.3.7-alpha - 2011-10-30
3691 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
3692 the new v3 handshake. It also resolves yet another bridge address
3696 - If we mark an OR connection for close based on a cell we process,
3697 don't process any further cells on it. We already avoid further
3698 reads on marked-for-close connections, but now we also discard the
3699 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3700 which was the first version where we might mark a connection for
3701 close based on processing a cell on it.
3702 - Fix a double-free bug that would occur when we received an invalid
3703 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
3704 bugfix on 0.2.3.6-alpha.
3705 - Bridges no longer include their address in NETINFO cells on outgoing
3706 OR connections, to allow them to blend in better with clients.
3707 Removes another avenue for enumerating bridges. Reported by
3708 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
3709 cells were introduced.
3712 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
3713 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3716 Changes in version 0.2.3.6-alpha - 2011-10-26
3717 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
3718 anonymity vulnerability where an attacker can deanonymize Tor
3719 users. Everybody should upgrade.
3721 This release also features support for a new v3 connection handshake
3722 protocol, and fixes to make hidden service connections more robust.
3725 - Implement a new handshake protocol (v3) for authenticating Tors to
3726 each other over TLS. It should be more resistant to fingerprinting
3727 than previous protocols, and should require less TLS hacking for
3728 future Tor implementations. Implements proposal 176.
3729 - Allow variable-length padding cells to disguise the length of
3730 Tor's TLS records. Implements part of proposal 184.
3732 o Privacy/anonymity fixes (clients):
3733 - Clients and bridges no longer send TLS certificate chains on
3734 outgoing OR connections. Previously, each client or bridge would
3735 use the same cert chain for all outgoing OR connections until
3736 its IP address changes, which allowed any relay that the client
3737 or bridge contacted to determine which entry guards it is using.
3738 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3739 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3740 no longer considers that connection as suitable for satisfying a
3741 circuit EXTEND request. Now relays can protect clients from the
3742 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3743 - Directory authorities no longer assign the Guard flag to relays
3744 that haven't upgraded to the above "refuse EXTEND requests
3745 to client connections" fix. Now directory authorities can
3746 protect clients from the CVE-2011-2768 issue even if neither
3747 the clients nor the relays have upgraded yet. There's a new
3748 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3749 to let us transition smoothly, else tomorrow there would be no
3752 o Major bugfixes (hidden services):
3753 - Improve hidden service robustness: when an attempt to connect to
3754 a hidden service ends, be willing to refetch its hidden service
3755 descriptors from each of the HSDir relays responsible for them
3756 immediately. Previously, we would not consider refetching the
3757 service's descriptors from each HSDir for 15 minutes after the last
3758 fetch, which was inconvenient if the hidden service was not running
3759 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
3760 - When one of a hidden service's introduction points appears to be
3761 unreachable, stop trying it. Previously, we would keep trying
3762 to build circuits to the introduction point until we lost the
3763 descriptor, usually because the user gave up and restarted Tor.
3764 Partly fixes bug 3825.
3765 - Don't launch a useless circuit after failing to use one of a
3766 hidden service's introduction points. Previously, we would
3767 launch a new introduction circuit, but not set the hidden service
3768 which that circuit was intended to connect to, so it would never
3769 actually be used. A different piece of code would then create a
3770 new introduction circuit correctly. Bug reported by katmagic and
3771 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3773 o Major bugfixes (other):
3774 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3775 that they initiated. Relays could distinguish incoming bridge
3776 connections from client connections, creating another avenue for
3777 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3778 Found by "frosty_un".
3779 - Don't update the AccountingSoftLimitHitAt state file entry whenever
3780 tor gets started. This prevents a wrong average bandwidth
3781 estimate, which would cause relays to always start a new accounting
3782 interval at the earliest possible moment. Fixes bug 2003; bugfix
3783 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
3784 immensely in tracking this bug down.
3785 - Fix a crash bug when changing node restrictions while a DNS lookup
3786 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3789 o Minor bugfixes (on 0.2.2.x and earlier):
3790 - When a hidden service turns an extra service-side introduction
3791 circuit into a general-purpose circuit, free the rend_data and
3792 intro_key fields first, so we won't leak memory if the circuit
3793 is cannibalized for use as another service-side introduction
3794 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3795 - Rephrase the log message emitted if the TestSocks check is
3796 successful. Patch from Fabian Keil; fixes bug 4094.
3797 - Bridges now skip DNS self-tests, to act a little more stealthily.
3798 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3799 bridges. Patch by "warms0x".
3800 - Remove a confusing dollar sign from the example fingerprint in the
3801 man page, and also make the example fingerprint a valid one. Fixes
3802 bug 4309; bugfix on 0.2.1.3-alpha.
3803 - Fix internal bug-checking logic that was supposed to catch
3804 failures in digest generation so that it will fail more robustly
3805 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3806 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3807 - Report any failure in init_keys() calls launched because our
3808 IP address has changed. Spotted by Coverity Scan. Bugfix on
3809 0.1.1.4-alpha; fixes CID 484.
3811 o Minor bugfixes (on 0.2.3.x):
3812 - Fix a bug in configure.in that kept it from building a configure
3813 script with autoconf versions earlier than 2.61. Fixes bug 2430;
3814 bugfix on 0.2.3.1-alpha.
3815 - Don't warn users that they are exposing a client port to the
3816 Internet if they have specified an RFC1918 address. Previously,
3817 we would warn if the user had specified any non-loopback
3818 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
3819 - Fix memory leaks in the failing cases of the new SocksPort and
3820 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
3821 fixes coverity CIDs 485, 486, and 487.
3824 - When a hidden service's introduction point times out, consider
3825 trying it again during the next attempt to connect to the
3826 HS. Previously, we would not try it again unless a newly fetched
3827 descriptor contained it. Required by fixes for bugs 1297 and 3825.
3828 - The next version of Windows will be called Windows 8, and it has
3829 a major version of 6, minor version of 2. Correctly identify that
3830 version instead of calling it "Very recent version". Resolves
3831 ticket 4153; reported by funkstar.
3832 - The Bridge Authority now writes statistics on how many bridge
3833 descriptors it gave out in total, and how many unique descriptors
3834 it gave out. It also lists how often the most and least commonly
3835 fetched descriptors were given out, as well as the median and
3836 25th/75th percentile. Implements tickets 4200 and 4294.
3837 - Update to the October 4 2011 Maxmind GeoLite Country database.
3839 o Code simplifications and refactoring:
3840 - Remove some old code to remember statistics about which descriptors
3841 we've served as a directory mirror. The feature wasn't used and
3842 is outdated now that microdescriptors are around.
3843 - Rename Tor functions that turn strings into addresses, so that
3844 "parse" indicates that no hostname resolution occurs, and
3845 "lookup" indicates that hostname resolution may occur. This
3846 should help prevent mistakes in the future. Fixes bug 3512.
3849 Changes in version 0.2.2.34 - 2011-10-26
3850 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
3851 can deanonymize Tor users. Everybody should upgrade.
3853 The attack relies on four components: 1) Clients reuse their TLS cert
3854 when talking to different relays, so relays can recognize a user by
3855 the identity key in her cert. 2) An attacker who knows the client's
3856 identity key can probe each guard relay to see if that identity key
3857 is connected to that guard relay right now. 3) A variety of active
3858 attacks in the literature (starting from "Low-Cost Traffic Analysis
3859 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
3860 discover the guard relays that a Tor user visiting the website is using.
3861 4) Clients typically pick three guards at random, so the set of guards
3862 for a given user could well be a unique fingerprint for her. This
3863 release fixes components #1 and #2, which is enough to block the attack;
3864 the other two remain as open research problems. Special thanks to
3865 "frosty_un" for reporting the issue to us!
3867 Clients should upgrade so they are no longer recognizable by the TLS
3868 certs they present. Relays should upgrade so they no longer allow a
3869 remote attacker to probe them to test whether unpatched clients are
3870 currently connected to them.
3872 This release also fixes several vulnerabilities that allow an attacker
3873 to enumerate bridge relays. Some bridge enumeration attacks still
3874 remain; see for example proposal 188.
3876 o Privacy/anonymity fixes (clients):
3877 - Clients and bridges no longer send TLS certificate chains on
3878 outgoing OR connections. Previously, each client or bridge would
3879 use the same cert chain for all outgoing OR connections until
3880 its IP address changes, which allowed any relay that the client
3881 or bridge contacted to determine which entry guards it is using.
3882 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3883 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3884 no longer considers that connection as suitable for satisfying a
3885 circuit EXTEND request. Now relays can protect clients from the
3886 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3887 - Directory authorities no longer assign the Guard flag to relays
3888 that haven't upgraded to the above "refuse EXTEND requests
3889 to client connections" fix. Now directory authorities can
3890 protect clients from the CVE-2011-2768 issue even if neither
3891 the clients nor the relays have upgraded yet. There's a new
3892 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3893 to let us transition smoothly, else tomorrow there would be no
3896 o Privacy/anonymity fixes (bridge enumeration):
3897 - Bridge relays now do their directory fetches inside Tor TLS
3898 connections, like all the other clients do, rather than connecting
3899 directly to the DirPort like public relays do. Removes another
3900 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
3901 - Bridges relays now build circuits for themselves in a more similar
3902 way to how clients build them. Removes another avenue for
3903 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
3904 when bridges were introduced.
3905 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3906 that they initiated. Relays could distinguish incoming bridge
3907 connections from client connections, creating another avenue for
3908 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3909 Found by "frosty_un".
3912 - Fix a crash bug when changing node restrictions while a DNS lookup
3913 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3915 - Don't launch a useless circuit after failing to use one of a
3916 hidden service's introduction points. Previously, we would
3917 launch a new introduction circuit, but not set the hidden service
3918 which that circuit was intended to connect to, so it would never
3919 actually be used. A different piece of code would then create a
3920 new introduction circuit correctly. Bug reported by katmagic and
3921 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3924 - Change an integer overflow check in the OpenBSD_Malloc code so
3925 that GCC is less likely to eliminate it as impossible. Patch
3926 from Mansour Moufid. Fixes bug 4059.
3927 - When a hidden service turns an extra service-side introduction
3928 circuit into a general-purpose circuit, free the rend_data and
3929 intro_key fields first, so we won't leak memory if the circuit
3930 is cannibalized for use as another service-side introduction
3931 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3932 - Bridges now skip DNS self-tests, to act a little more stealthily.
3933 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3934 bridges. Patch by "warms0x".
3935 - Fix internal bug-checking logic that was supposed to catch
3936 failures in digest generation so that it will fail more robustly
3937 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3938 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3939 - Report any failure in init_keys() calls launched because our
3940 IP address has changed. Spotted by Coverity Scan. Bugfix on
3941 0.1.1.4-alpha; fixes CID 484.
3943 o Minor bugfixes (log messages and documentation):
3944 - Remove a confusing dollar sign from the example fingerprint in the
3945 man page, and also make the example fingerprint a valid one. Fixes
3946 bug 4309; bugfix on 0.2.1.3-alpha.
3947 - The next version of Windows will be called Windows 8, and it has
3948 a major version of 6, minor version of 2. Correctly identify that
3949 version instead of calling it "Very recent version". Resolves
3950 ticket 4153; reported by funkstar.
3951 - Downgrade log messages about circuit timeout calibration from
3952 "notice" to "info": they don't require or suggest any human
3953 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3954 bugfix on 0.2.2.14-alpha.
3957 - Turn on directory request statistics by default and include them in
3958 extra-info descriptors. Don't break if we have no GeoIP database.
3959 Backported from 0.2.3.1-alpha; implements ticket 3951.
3960 - Update to the October 4 2011 Maxmind GeoLite Country database.
3963 Changes in version 0.2.1.31 - 2011-10-26
3964 Tor 0.2.1.31 backports important security and privacy fixes for
3965 oldstable. This release is intended only for package maintainers and
3966 others who cannot use the 0.2.2 stable series. All others should be
3967 using Tor 0.2.2.x or newer.
3969 o Security fixes (also included in 0.2.2.x):
3970 - Replace all potentially sensitive memory comparison operations
3971 with versions whose runtime does not depend on the data being
3972 compared. This will help resist a class of attacks where an
3973 adversary can use variations in timing information to learn
3974 sensitive data. Fix for one case of bug 3122. (Safe memcmp
3975 implementation by Robert Ransom based partially on code by DJB.)
3976 - Fix an assert in parsing router descriptors containing IPv6
3977 addresses. This one took down the directory authorities when
3978 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3980 o Privacy/anonymity fixes (also included in 0.2.2.x):
3981 - Clients and bridges no longer send TLS certificate chains on
3982 outgoing OR connections. Previously, each client or bridge would
3983 use the same cert chain for all outgoing OR connections until
3984 its IP address changes, which allowed any relay that the client
3985 or bridge contacted to determine which entry guards it is using.
3986 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3987 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3988 no longer considers that connection as suitable for satisfying a
3989 circuit EXTEND request. Now relays can protect clients from the
3990 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3991 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3992 that they initiated. Relays could distinguish incoming bridge
3993 connections from client connections, creating another avenue for
3994 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3995 Found by "frosty_un".
3996 - When receiving a hidden service descriptor, check that it is for
3997 the hidden service we wanted. Previously, Tor would store any
3998 hidden service descriptors that a directory gave it, whether it
3999 wanted them or not. This wouldn't have let an attacker impersonate
4000 a hidden service, but it did let directories pre-seed a client
4001 with descriptors that it didn't want. Bugfix on 0.0.6.
4002 - Avoid linkability based on cached hidden service descriptors: forget
4003 all hidden service descriptors cached as a client when processing a
4004 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
4005 - Make the bridge directory authority refuse to answer directory
4006 requests for "all" descriptors. It used to include bridge
4007 descriptors in its answer, which was a major information leak.
4008 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
4009 - Don't attach new streams to old rendezvous circuits after SIGNAL
4010 NEWNYM. Previously, we would keep using an existing rendezvous
4011 circuit if it remained open (i.e. if it were kept open by a
4012 long-lived stream, or if a new stream were attached to it before
4013 Tor could notice that it was old and no longer in use). Bugfix on
4014 0.1.1.15-rc; fixes bug 3375.
4016 o Minor bugfixes (also included in 0.2.2.x):
4017 - When we restart our relay, we might get a successful connection
4018 from the outside before we've started our reachability tests,
4019 triggering a warning: "ORPort found reachable, but I have no
4020 routerinfo yet. Failing to inform controller of success." This
4021 bug was harmless unless Tor is running under a controller
4022 like Vidalia, in which case the controller would never get a
4023 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
4025 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
4026 enabled. Fixes bug 1526.
4027 - Remove undocumented option "-F" from tor-resolve: it hasn't done
4028 anything since 0.2.1.16-rc.
4029 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
4030 None of the cases where we did this before were wrong, but by making
4031 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
4032 - Fix a rare crash bug that could occur when a client was configured
4033 with a large number of bridges. Fixes bug 2629; bugfix on
4034 0.2.1.2-alpha. Bugfix by trac user "shitlei".
4035 - Correct the warning displayed when a rendezvous descriptor exceeds
4036 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
4038 - Fix an uncommon assertion failure when running with DNSPort under
4039 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
4040 - When warning about missing zlib development packages during compile,
4041 give the correct package names. Bugfix on 0.2.0.1-alpha.
4042 - Require that introduction point keys and onion keys have public
4043 exponent 65537. Bugfix on 0.2.0.10-alpha.
4044 - Do not crash when our configuration file becomes unreadable, for
4045 example due to a permissions change, between when we start up
4046 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
4048 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4050 - Always NUL-terminate the sun_path field of a sockaddr_un before
4051 passing it to the kernel. (Not a security issue: kernels are
4052 smart enough to reject bad sockaddr_uns.) Found by Coverity;
4053 CID #428. Bugfix on Tor 0.2.0.3-alpha.
4054 - Don't stack-allocate the list of supplementary GIDs when we're
4055 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4056 could take up to 256K, which is way too much stack. Found by
4057 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4059 o Minor bugfixes (only in 0.2.1.x):
4060 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
4061 rely on them. Bugfix on 0.2.1.30.
4062 - Use git revisions instead of svn revisions when generating our
4063 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
4065 o Minor features (also included in 0.2.2.x):
4066 - Adjust the expiration time on our SSL session certificates to
4067 better match SSL certs seen in the wild. Resolves ticket 4014.
4068 - Allow nameservers with IPv6 address. Resolves bug 2574.
4069 - Update to the October 4 2011 Maxmind GeoLite Country database.
4072 Changes in version 0.2.3.5-alpha - 2011-09-28
4073 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
4074 bridge relays; fixes an assertion error that many users started hitting
4075 today; and adds the ability to refill token buckets more often than
4076 once per second, allowing significant performance improvements.
4079 - Bridge relays now do their directory fetches inside Tor TLS
4080 connections, like all the other clients do, rather than connecting
4081 directly to the DirPort like public relays do. Removes another
4082 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
4083 - Bridges relays now build circuits for themselves in a more similar
4084 way to how clients build them. Removes another avenue for
4085 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
4086 when bridges were introduced.
4089 - Fix an "Assertion md->held_by_node == 1 failed" error that could
4090 occur when the same microdescriptor was referenced by two node_t
4091 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
4093 o Major features (networking):
4094 - Add a new TokenBucketRefillInterval option to refill token buckets
4095 more frequently than once per second. This should improve network
4096 performance, alleviate queueing problems, and make traffic less
4097 bursty. Implements proposal 183; closes ticket 3630. Design by
4098 Florian Tschorsch and Björn Scheuermann; implementation by
4102 - Change an integer overflow check in the OpenBSD_Malloc code so
4103 that GCC is less likely to eliminate it as impossible. Patch
4104 from Mansour Moufid. Fixes bug 4059.
4106 o Minor bugfixes (usability):
4107 - Downgrade log messages about circuit timeout calibration from
4108 "notice" to "info": they don't require or suggest any human
4109 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
4110 bugfix on 0.2.2.14-alpha.
4112 o Minor features (diagnostics):
4113 - When the system call to create a listener socket fails, log the
4114 error message explaining why. This may help diagnose bug 4027.
4117 Changes in version 0.2.3.4-alpha - 2011-09-13
4118 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
4119 tweak to Tor's TLS handshake that makes relays and bridges that run
4120 this new version reachable from Iran again. It also fixes a few new
4121 bugs in 0.2.3.x, and teaches relays to recognize when they're not
4122 listed in the network consensus and republish.
4124 o Major bugfixes (also part of 0.2.2.33):
4125 - Avoid an assertion failure when reloading a configuration with
4126 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
4127 3923; bugfix on 0.2.2.25-alpha.
4129 o Minor features (security, also part of 0.2.2.33):
4130 - Check for replays of the public-key encrypted portion of an
4131 INTRODUCE1 cell, in addition to the current check for replays of
4132 the g^x value. This prevents a possible class of active attacks
4133 by an attacker who controls both an introduction point and a
4134 rendezvous point, and who uses the malleability of AES-CTR to
4135 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
4136 that these attacks is infeasible (requiring the attacker to send
4137 on the order of zettabytes of altered cells in a short interval),
4138 but we'd rather block them off in case there are any classes of
4139 this attack that we missed. Reported by Willem Pinckaers.
4141 o Minor features (also part of 0.2.2.33):
4142 - Adjust the expiration time on our SSL session certificates to
4143 better match SSL certs seen in the wild. Resolves ticket 4014.
4144 - Change the default required uptime for a relay to be accepted as
4145 a HSDir (hidden service directory) from 24 hours to 25 hours.
4146 Improves on 0.2.0.10-alpha; resolves ticket 2649.
4147 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
4148 authorities to abstain from voting on assignment of the HSDir
4149 consensus flag. Related to bug 2649.
4150 - Update to the September 6 2011 Maxmind GeoLite Country database.
4152 o Minor bugfixes (also part of 0.2.2.33):
4153 - Demote the 'replay detected' log message emitted when a hidden
4154 service receives the same Diffie-Hellman public key in two different
4155 INTRODUCE2 cells to info level. A normal Tor client can cause that
4156 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4157 fixes part of bug 2442.
4158 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4159 level. There is nothing that a hidden service's operator can do
4160 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4162 - Clarify a log message specifying the characters permitted in
4163 HiddenServiceAuthorizeClient client names. Previously, the log
4164 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4165 given the impression that every ASCII character between "+" and "_"
4166 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4168 o Build fixes (also part of 0.2.2.33):
4169 - Clean up some code issues that prevented Tor from building on older
4170 BSDs. Fixes bug 3894; reported by "grarpamp".
4171 - Search for a platform-specific version of "ar" when cross-compiling.
4172 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4175 - Fix a bug where the SocksPort option (for example) would get
4176 ignored and replaced by the default if a SocksListenAddress
4177 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
4181 - Relays now try regenerating and uploading their descriptor more
4182 frequently if they are not listed in the consensus, or if the
4183 version of their descriptor listed in the consensus is too
4184 old. This fix should prevent situations where a server declines
4185 to re-publish itself because it has done so too recently, even
4186 though the authorities decided not to list its recent-enough
4187 descriptor. Fix for bug 3327.
4190 - Relays now include a reason for regenerating their descriptors
4191 in an HTTP header when uploading to the authorities. This will
4192 make it easier to debug descriptor-upload issues in the future.
4193 - When starting as root and then changing our UID via the User
4194 control option, and we have a ControlSocket configured, make sure
4195 that the ControlSocket is owned by the same account that Tor will
4196 run under. Implements ticket 3421; fix by Jérémy Bobbio.
4199 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
4200 utility function used in the control-port code). This shouldn't
4201 ever happen unless Tor is completely out of memory, but if it did
4202 happen and Tor somehow recovered from it, Tor could have sent a log
4203 message to a control port in the middle of a reply to a controller
4204 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
4205 - Make 'FetchUselessDescriptors' cause all descriptor types and
4206 all consensus types (including microdescriptors) to get fetched.
4207 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
4210 - Make a new "entry connection" struct as an internal subtype of "edge
4211 connection", to simplify the code and make exit connections smaller.
4214 Changes in version 0.2.2.33 - 2011-09-13
4215 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
4216 TLS handshake that makes relays and bridges that run this new version
4217 reachable from Iran again.
4220 - Avoid an assertion failure when reloading a configuration with
4221 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
4222 3923; bugfix on 0.2.2.25-alpha.
4224 o Minor features (security):
4225 - Check for replays of the public-key encrypted portion of an
4226 INTRODUCE1 cell, in addition to the current check for replays of
4227 the g^x value. This prevents a possible class of active attacks
4228 by an attacker who controls both an introduction point and a
4229 rendezvous point, and who uses the malleability of AES-CTR to
4230 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
4231 that these attacks are infeasible (requiring the attacker to send
4232 on the order of zettabytes of altered cells in a short interval),
4233 but we'd rather block them off in case there are any classes of
4234 this attack that we missed. Reported by Willem Pinckaers.
4237 - Adjust the expiration time on our SSL session certificates to
4238 better match SSL certs seen in the wild. Resolves ticket 4014.
4239 - Change the default required uptime for a relay to be accepted as
4240 a HSDir (hidden service directory) from 24 hours to 25 hours.
4241 Improves on 0.2.0.10-alpha; resolves ticket 2649.
4242 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
4243 authorities to abstain from voting on assignment of the HSDir
4244 consensus flag. Related to bug 2649.
4245 - Update to the September 6 2011 Maxmind GeoLite Country database.
4247 o Minor bugfixes (documentation and log messages):
4248 - Correct the man page to explain that HashedControlPassword and
4249 CookieAuthentication can both be set, in which case either method
4250 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4251 when we decided to allow these config options to both be set. Issue
4253 - Demote the 'replay detected' log message emitted when a hidden
4254 service receives the same Diffie-Hellman public key in two different
4255 INTRODUCE2 cells to info level. A normal Tor client can cause that
4256 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4257 fixes part of bug 2442.
4258 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4259 level. There is nothing that a hidden service's operator can do
4260 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4262 - Clarify a log message specifying the characters permitted in
4263 HiddenServiceAuthorizeClient client names. Previously, the log
4264 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4265 given the impression that every ASCII character between "+" and "_"
4266 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4269 - Provide a substitute implementation of lround() for MSVC, which
4270 apparently lacks it. Patch from Gisle Vanem.
4271 - Clean up some code issues that prevented Tor from building on older
4272 BSDs. Fixes bug 3894; reported by "grarpamp".
4273 - Search for a platform-specific version of "ar" when cross-compiling.
4274 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4277 Changes in version 0.2.3.3-alpha - 2011-09-01
4278 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
4279 security, and provides client-side support for the microdescriptor
4280 and optimistic data features introduced earlier in the 0.2.3.x
4281 series. It also includes numerous critical bugfixes in the (optional)
4282 bufferevent-based networking backend.
4284 o Major features (stream isolation):
4285 - You can now configure Tor so that streams from different
4286 applications are isolated on different circuits, to prevent an
4287 attacker who sees your streams as they leave an exit node from
4288 linking your sessions to one another. To do this, choose some way
4289 to distinguish the applications: have them connect to different
4290 SocksPorts, or have one of them use SOCKS4 while the other uses
4291 SOCKS5, or have them pass different authentication strings to the
4292 SOCKS proxy. Then, use the new SocksPort syntax to configure the
4293 degree of isolation you need. This implements Proposal 171.
4294 - There's a new syntax for specifying multiple client ports (such as
4295 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
4296 multiple *Port entries with full addr:port syntax on each.
4297 The old *ListenAddress format is still supported, but you can't
4298 mix it with the new *Port syntax.
4300 o Major features (other):
4301 - Enable microdescriptor fetching by default for clients. This allows
4302 clients to download a much smaller amount of directory information.
4303 To disable it (and go back to the old-style consensus and
4304 descriptors), set "UseMicrodescriptors 0" in your torrc file.
4305 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
4306 "PortForwarding" config option), now supports Windows.
4307 - When using an exit relay running 0.2.3.x, clients can now
4308 "optimistically" send data before the exit relay reports that
4309 the stream has opened. This saves a round trip when starting
4310 connections where the client speaks first (such as web browsing).
4311 This behavior is controlled by a consensus parameter (currently
4312 disabled). To turn it on or off manually, use the "OptimisticData"
4313 torrc option. Implements proposal 181; code by Ian Goldberg.
4315 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
4316 - When using IOCP on Windows, we need to enable Libevent windows
4318 - The IOCP backend now works even when the user has not specified
4319 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
4320 Fixes part of bug 3752.
4321 - Correctly record the bytes we've read and written when using
4322 bufferevents, so that we can include them in our bandwidth history
4323 and advertised bandwidth. Fixes bug 3803.
4324 - Apply rate-limiting only at the bottom of a chain of filtering
4325 bufferevents. This prevents us from filling up internal read
4326 buffers and violating rate-limits when filtering bufferevents
4327 are enabled. Fixes part of bug 3804.
4328 - Add high-watermarks to the output buffers for filtered
4329 bufferevents. This prevents us from filling up internal write
4330 buffers and wasting CPU cycles when filtering bufferevents are
4331 enabled. Fixes part of bug 3804.
4332 - Correctly notice when data has been written from a bufferevent
4333 without flushing it completely. Fixes bug 3805.
4334 - Fix a bug where server-side tunneled bufferevent-based directory
4335 streams would get closed prematurely. Fixes bug 3814.
4336 - Fix a use-after-free error with per-connection rate-limiting
4337 buckets. Fixes bug 3888.
4339 o Major bugfixes (also part of 0.2.2.31-rc):
4340 - If we're configured to write our ControlPorts to disk, only write
4341 them after switching UID and creating the data directory. This way,
4342 we don't fail when starting up with a nonexistent DataDirectory
4343 and a ControlPortWriteToFile setting based on that directory. Fixes
4344 bug 3747; bugfix on Tor 0.2.2.26-beta.
4347 - Added a new CONF_CHANGED event so that controllers can be notified
4348 of any configuration changes made by other controllers, or by the
4349 user. Implements ticket 1692.
4350 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
4351 leak when using bufferevents, and lets Libevent worry about how to
4352 best copy data out of a buffer.
4353 - Replace files in stats/ rather than appending to them. Now that we
4354 include statistics in extra-info descriptors, it makes no sense to
4355 keep old statistics forever. Implements ticket 2930.
4357 o Minor features (build compatibility):
4358 - Limited, experimental support for building with nmake and MSVC.
4359 - Provide a substitute implementation of lround() for MSVC, which
4360 apparently lacks it. Patch from Gisle Vanem.
4362 o Minor features (also part of 0.2.2.31-rc):
4363 - Update to the August 2 2011 Maxmind GeoLite Country database.
4365 o Minor bugfixes (on 0.2.3.x-alpha):
4366 - Fix a spurious warning when parsing SOCKS requests with
4367 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
4368 - Get rid of a harmless warning that could happen on relays running
4369 with bufferevents. The warning was caused by someone doing an http
4370 request to a relay's orport. Also don't warn for a few related
4371 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
4373 o Minor bugfixes (on 2.2.x and earlier):
4374 - Correct the man page to explain that HashedControlPassword and
4375 CookieAuthentication can both be set, in which case either method
4376 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4377 when we decided to allow these config options to both be set. Issue
4379 - The "--quiet" and "--hush" options now apply not only to Tor's
4380 behavior before logs are configured, but also to Tor's behavior in
4381 the absense of configured logs. Fixes bug 3550; bugfix on
4384 o Minor bugfixes (also part of 0.2.2.31-rc):
4385 - Write several files in text mode, on OSes that distinguish text
4386 mode from binary mode (namely, Windows). These files are:
4387 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4388 that collect those statistics; 'client_keys' and 'hostname' for
4389 hidden services that use authentication; and (in the tor-gencert
4390 utility) newly generated identity and signing keys. Previously,
4391 we wouldn't specify text mode or binary mode, leading to an
4392 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4393 the DirRecordUsageByCountry option which would have triggered
4394 the assertion failure was added), although this assertion failure
4395 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4396 - Selectively disable deprecation warnings on OS X because Lion
4397 started deprecating the shipped copy of openssl. Fixes bug 3643.
4398 - Remove an extra pair of quotation marks around the error
4399 message in control-port STATUS_GENERAL BUG events. Bugfix on
4400 0.1.2.6-alpha; fixes bug 3732.
4401 - When unable to format an address as a string, report its value
4402 as "???" rather than reusing the last formatted address. Bugfix
4405 o Code simplifications and refactoring:
4406 - Rewrite the listener-selection logic so that parsing which ports
4407 we want to listen on is now separate from binding to the ports
4411 - Building Tor with bufferevent support now requires Libevent
4412 2.0.13-stable or later. Previous versions of Libevent had bugs in
4413 SSL-related bufferevents and related issues that would make Tor
4414 work badly with bufferevents. Requiring 2.0.13-stable also allows
4415 Tor with bufferevents to take advantage of Libevent APIs
4416 introduced after 2.0.8-rc.
4419 Changes in version 0.2.2.32 - 2011-08-27
4420 The Tor 0.2.2 release series is dedicated to the memory of Andreas
4421 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
4422 a founder of the PETS community, a leader in our field, a mentor,
4423 and a friend. He left us with these words: "I had the possibility
4424 to contribute to this world that is not as it should be. I hope I
4425 could help in some areas to make the world a better place, and that
4426 I could also encourage other people to be engaged in improving the
4427 world. Please, stay engaged. This world needs you, your love, your
4428 initiative -- now I cannot be part of that anymore."
4430 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
4431 ready. More than two years in the making, this release features improved
4432 client performance and hidden service reliability, better compatibility
4433 for Android, correct behavior for bridges that listen on more than
4434 one address, more extensible and flexible directory object handling,
4435 better reporting of network statistics, improved code security, and
4436 many many other features and bugfixes.
4439 Changes in version 0.2.2.31-rc - 2011-08-17
4440 Tor 0.2.2.31-rc is the second and hopefully final release candidate
4441 for the Tor 0.2.2.x series.
4444 - Remove an extra pair of quotation marks around the error
4445 message in control-port STATUS_GENERAL BUG events. Bugfix on
4446 0.1.2.6-alpha; fixes bug 3732.
4447 - If we're configured to write our ControlPorts to disk, only write
4448 them after switching UID and creating the data directory. This way,
4449 we don't fail when starting up with a nonexistent DataDirectory
4450 and a ControlPortWriteToFile setting based on that directory. Fixes
4451 bug 3747; bugfix on Tor 0.2.2.26-beta.
4454 - Update to the August 2 2011 Maxmind GeoLite Country database.
4457 - Allow GETINFO fingerprint to return a fingerprint even when
4458 we have not yet built a router descriptor. Fixes bug 3577;
4459 bugfix on 0.2.0.1-alpha.
4460 - Write several files in text mode, on OSes that distinguish text
4461 mode from binary mode (namely, Windows). These files are:
4462 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4463 that collect those statistics; 'client_keys' and 'hostname' for
4464 hidden services that use authentication; and (in the tor-gencert
4465 utility) newly generated identity and signing keys. Previously,
4466 we wouldn't specify text mode or binary mode, leading to an
4467 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4468 the DirRecordUsageByCountry option which would have triggered
4469 the assertion failure was added), although this assertion failure
4470 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4471 - Selectively disable deprecation warnings on OS X because Lion
4472 started deprecating the shipped copy of openssl. Fixes bug 3643.
4473 - When unable to format an address as a string, report its value
4474 as "???" rather than reusing the last formatted address. Bugfix
4478 Changes in version 0.2.3.2-alpha - 2011-07-18
4479 Tor 0.2.3.2-alpha introduces two new experimental features:
4480 microdescriptors and pluggable transports. It also continues cleaning
4481 up a variety of recently introduced features.
4484 - Clients can now use microdescriptors instead of regular descriptors
4485 to build circuits. Microdescriptors are authority-generated
4486 summaries of regular descriptors' contents, designed to change
4487 very rarely (see proposal 158 for details). This feature is
4488 designed to save bandwidth, especially for clients on slow internet
4489 connections. It's off by default for now, since nearly no caches
4490 support it, but it will be on-by-default for clients in a future
4491 version. You can use the UseMicrodescriptors option to turn it on.
4492 - Tor clients using bridges can now be configured to use a separate
4493 'transport' proxy for each bridge. This approach helps to resist
4494 censorship by allowing bridges to use protocol obfuscation
4495 plugins. It implements part of proposal 180. Implements ticket 2841.
4496 - While we're trying to bootstrap, record how many TLS connections
4497 fail in each state, and report which states saw the most failures
4498 in response to any bootstrap failures. This feature may speed up
4499 diagnosis of censorship events. Implements ticket 3116.
4501 o Major bugfixes (on 0.2.3.1-alpha):
4502 - When configuring a large set of nodes in EntryNodes (as with
4503 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
4504 random subset to be guards, and choose them in random
4505 order. Fixes bug 2798.
4506 - Tor could crash when remembering a consensus in a non-used consensus
4507 flavor without having a current consensus set. Fixes bug 3361.
4508 - Comparing an unknown address to a microdescriptor's shortened exit
4509 policy would always give a "rejected" result. Fixes bug 3599.
4510 - Using microdescriptors as a client no longer prevents Tor from
4511 uploading and downloading hidden service descriptors. Fixes
4515 - Allow nameservers with IPv6 address. Resolves bug 2574.
4516 - Accept attempts to include a password authenticator in the
4517 handshake, as supported by SOCKS5. This handles SOCKS clients that
4518 don't know how to omit a password when authenticating. Resolves
4520 - When configuring a large set of nodes in EntryNodes, and there are
4521 enough of them listed as Guard so that we don't need to consider
4522 the non-guard entries, prefer the ones listed with the Guard flag.
4523 - Check for and recover from inconsistency in the microdescriptor
4524 cache. This will make it harder for us to accidentally free a
4525 microdescriptor without removing it from the appropriate data
4526 structures. Fixes issue 3135; issue noted by "wanoskarnet".
4527 - Log SSL state transitions at log level DEBUG, log domain
4528 HANDSHAKE. This can be useful for debugging censorship events.
4529 Implements ticket 3264.
4530 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
4531 implements ticket 3439.
4533 o Minor bugfixes (on 0.2.3.1-alpha):
4534 - Do not free all general-purpose regular descriptors just
4535 because microdescriptor use is enabled. Fixes bug 3113.
4536 - Correctly link libevent_openssl when --enable-static-libevent
4537 is passed to configure. Fixes bug 3118.
4538 - Bridges should not complain during their heartbeat log messages that
4539 they are unlisted in the consensus: that's more or less the point
4540 of being a bridge. Fixes bug 3183.
4541 - Report a SIGNAL event to controllers when acting on a delayed
4542 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
4543 event to the controller if we acted on a SIGNAL NEWNYM command
4544 immediately, and otherwise not report a SIGNAL event for the
4545 command at all. Fixes bug 3349.
4546 - Fix a crash when handling the SIGNAL controller command or
4547 reporting ERR-level status events with bufferevents enabled. Found
4548 by Robert Ransom. Fixes bug 3367.
4549 - Always ship the tor-fw-helper manpage in our release tarballs.
4550 Fixes bug 3389. Reported by Stephen Walker.
4551 - Fix a class of double-mark-for-close bugs when bufferevents
4552 are enabled. Fixes bug 3403.
4553 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
4554 - Add SIGNAL to the list returned by the 'GETINFO events/names'
4555 control-port command. Fixes part of bug 3465.
4556 - Prevent using negative indices during unit test runs when read_all()
4557 fails. Spotted by coverity.
4558 - Fix a rare memory leak when checking the nodelist without it being
4559 present. Found by coverity.
4560 - Only try to download a microdescriptor-flavored consensus from
4561 a directory cache that provides them.
4563 o Minor bugfixes (on 0.2.2.x and earlier):
4564 - Assert that hidden-service-related operations are not performed
4565 using single-hop circuits. Previously, Tor would assert that
4566 client-side streams are not attached to single-hop circuits,
4567 but not that other sensitive operations on the client and service
4568 side are not performed using single-hop circuits. Fixes bug 3332;
4570 - Don't publish a new relay descriptor when we reload our onion key,
4571 unless the onion key has actually changed. Fixes bug 3263 and
4572 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
4573 - Allow GETINFO fingerprint to return a fingerprint even when
4574 we have not yet built a router descriptor. Fixes bug 3577;
4575 bugfix on 0.2.0.1-alpha.
4576 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
4577 on 0.2.2.4-alpha; fixes bug 3427.
4579 o Code simplification and refactoring:
4580 - Use tor_sscanf() in place of scanf() in more places through the
4581 code. This makes us a little more locale-independent, and
4582 should help shut up code-analysis tools that can't tell
4583 a safe sscanf string from a dangerous one.
4584 - Use tt_assert(), not tor_assert(), for checking for test failures.
4585 This makes the unit tests more able to go on in the event that
4587 - Split connection_about_to_close() into separate functions for each
4591 - On Windows, we now define the _WIN32_WINNT macros only if they
4592 are not already defined. This lets the person building Tor decide,
4593 if they want, to require a later version of Windows.
4596 Changes in version 0.2.2.30-rc - 2011-07-07
4597 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
4598 series. It fixes a few smaller bugs, but generally appears stable.
4599 Please test it and let us know whether it is!
4602 - Send a SUCCEEDED stream event to the controller when a reverse
4603 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
4604 discovered by katmagic.
4605 - Always NUL-terminate the sun_path field of a sockaddr_un before
4606 passing it to the kernel. (Not a security issue: kernels are
4607 smart enough to reject bad sockaddr_uns.) Found by Coverity;
4608 CID #428. Bugfix on Tor 0.2.0.3-alpha.
4609 - Don't stack-allocate the list of supplementary GIDs when we're
4610 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4611 could take up to 256K, which is way too much stack. Found by
4612 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4613 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
4614 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
4615 fixes part of bug 3465.
4616 - Fix a memory leak when receiving a descriptor for a hidden
4617 service we didn't ask for. Found by Coverity; CID #30. Bugfix
4621 - Update to the July 1 2011 Maxmind GeoLite Country database.
4624 Changes in version 0.2.2.29-beta - 2011-06-20
4625 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
4626 have bridge lines in their torrc but don't want to use them; gets
4627 us closer to having the control socket feature working on Debian;
4628 and fixes a variety of smaller bugs.
4631 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
4632 When we changed the default behavior to "use bridges if any
4633 are listed in the torrc", we surprised users who had bridges
4634 in their torrc files but who didn't actually want to use them.
4635 Partial resolution for bug 3354.
4638 - Don't attach new streams to old rendezvous circuits after SIGNAL
4639 NEWNYM. Previously, we would keep using an existing rendezvous
4640 circuit if it remained open (i.e. if it were kept open by a
4641 long-lived stream, or if a new stream were attached to it before
4642 Tor could notice that it was old and no longer in use). Bugfix on
4643 0.1.1.15-rc; fixes bug 3375.
4646 - Fix a bug when using ControlSocketsGroupWritable with User. The
4647 directory's group would be checked against the current group, not
4648 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
4649 bugfix on 0.2.2.26-beta.
4650 - Make connection_printf_to_buf()'s behaviour sane. Its callers
4651 expect it to emit a CRLF iff the format string ends with CRLF;
4652 it actually emitted a CRLF iff (a) the format string ended with
4653 CRLF or (b) the resulting string was over 1023 characters long or
4654 (c) the format string did not end with CRLF *and* the resulting
4655 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
4656 fixes part of bug 3407.
4657 - Make send_control_event_impl()'s behaviour sane. Its callers
4658 expect it to always emit a CRLF at the end of the string; it
4659 might have emitted extra control characters as well. Bugfix on
4660 0.1.1.9-alpha; fixes another part of bug 3407.
4661 - Make crypto_rand_int() check the value of its input correctly.
4662 Previously, it accepted values up to UINT_MAX, but could return a
4663 negative number if given a value above INT_MAX+1. Found by George
4664 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
4665 - Avoid a segfault when reading a malformed circuit build state
4666 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
4668 - When asked about a DNS record type we don't support via a
4669 client DNSPort, reply with NOTIMPL rather than an empty
4670 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
4671 - Fix a rare memory leak during stats writing. Found by coverity.
4674 - Update to the June 1 2011 Maxmind GeoLite Country database.
4676 o Code simplifications and refactoring:
4677 - Remove some dead code as indicated by coverity.
4678 - Remove a few dead assignments during router parsing. Found by
4680 - Add some forgotten return value checks during unit tests. Found
4682 - Don't use 1-bit wide signed bit fields. Found by coverity.
4685 Changes in version 0.2.2.28-beta - 2011-06-04
4686 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
4687 fixed a big bug in whether relays stay in the consensus consistently,
4688 we moved closer to handling bridges and hidden services correctly,
4689 and we started the process of better handling the dreaded "my Vidalia
4690 died, and now my Tor demands a password when I try to reconnect to it"
4694 - Don't decide to make a new descriptor when receiving a HUP signal.
4695 This bug has caused a lot of 0.2.2.x relays to disappear from the
4696 consensus periodically. Fixes the most common case of triggering
4697 bug 1810; bugfix on 0.2.2.7-alpha.
4698 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
4699 - Don't try to build descriptors if "ORPort auto" is set and we
4700 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
4702 - Resolve a crash that occurred when setting BridgeRelay to 1 with
4703 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
4704 - Apply circuit timeouts to opened hidden-service-related circuits
4705 based on the correct start time. Previously, we would apply the
4706 circuit build timeout based on time since the circuit's creation;
4707 it was supposed to be applied based on time since the circuit
4708 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
4709 - Use the same circuit timeout for client-side introduction
4710 circuits as for other four-hop circuits, rather than the timeout
4711 for single-hop directory-fetch circuits; the shorter timeout may
4712 have been appropriate with the static circuit build timeout in
4713 0.2.1.x and earlier, but caused many hidden service access attempts
4714 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
4715 on 0.2.2.2-alpha; fixes another part of bug 1297.
4716 - In ticket 2511 we fixed a case where you could use an unconfigured
4717 bridge if you had configured it as a bridge the last time you ran
4718 Tor. Now fix another edge case: if you had configured it as a bridge
4719 but then switched to a different bridge via the controller, you
4720 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
4724 - Add an __OwningControllerProcess configuration option and a
4725 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
4726 that when it exits, Tor will shut down. Implements feature 3049.
4727 - If "UseBridges 1" is set and no bridges are configured, Tor will
4728 now refuse to build any circuits until some bridges are set.
4729 If "UseBridges auto" is set, Tor will use bridges if they are
4730 configured and we are not running as a server, but otherwise will
4731 make circuits as usual. The new default is "auto". Patch by anonym,
4732 so the Tails LiveCD can stop automatically revealing you as a Tor
4736 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4737 - Remove a trailing asterisk from "exit-policy/default" in the
4738 output of the control port command "GETINFO info/names". Bugfix
4740 - Use a wide type to hold sockets when built for 64-bit Windows builds.
4742 - Warn when the user configures two HiddenServiceDir lines that point
4743 to the same directory. Bugfix on 0.0.6 (the version introducing
4744 HiddenServiceDir); fixes bug 3289.
4745 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
4746 part of bug 2748; bugfix on 0.2.0.10-alpha.
4747 - Log malformed requests for rendezvous descriptors as protocol
4748 warnings, not warnings. Also, use a more informative log message
4749 in case someone sees it at log level warning without prior
4750 info-level messages. Fixes the other part of bug 2748; bugfix
4752 - Clear the table recording the time of the last request for each
4753 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
4754 Previously, we would clear our HS descriptor cache on SIGNAL
4755 NEWNYM, but if we had previously retrieved a descriptor (or tried
4756 to) from every directory responsible for it, we would refuse to
4757 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
4759 - Fix a log message that said "bits" while displaying a value in
4760 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
4762 - When checking for 1024-bit keys, check for 1024 bits, not 128
4763 bytes. This allows Tor to correctly discard keys of length 1017
4764 through 1023. Bugfix on 0.0.9pre5.
4767 - Relays now log the reason for publishing a new relay descriptor,
4768 so we have a better chance of hunting down instances of bug 1810.
4769 Resolves ticket 3252.
4770 - Revise most log messages that refer to nodes by nickname to
4771 instead use the "$key=nickname at address" format. This should be
4772 more useful, especially since nicknames are less and less likely
4773 to be unique. Resolves ticket 3045.
4774 - Log (at info level) when purging pieces of hidden-service-client
4775 state because of SIGNAL NEWNYM.
4778 - Remove undocumented option "-F" from tor-resolve: it hasn't done
4779 anything since 0.2.1.16-rc.
4782 Changes in version 0.2.2.27-beta - 2011-05-18
4783 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
4784 release, and also adds a few more general bugfixes.
4787 - Fix a crash bug when changing bridges in a running Tor process.
4788 Fixes bug 3213; bugfix on 0.2.2.26-beta.
4789 - When the controller configures a new bridge, don't wait 10 to 60
4790 seconds before trying to fetch its descriptor. Bugfix on
4791 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
4794 - Require that onion keys have exponent 65537 in microdescriptors too.
4795 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
4796 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
4797 Changed the limit to 512 characters by removing base64 newlines.
4798 Fixes bug 2752. Fix by Michael Yakubovich.
4799 - When a client starts or stops using bridges, never use a circuit
4800 that was built before the configuration change. This behavior could
4801 put at risk a user who uses bridges to ensure that her traffic
4802 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
4806 Changes in version 0.2.2.26-beta - 2011-05-17
4807 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
4808 also introduces a new "socksport auto" approach that should make it
4809 easier to run multiple Tors on the same system, and does a lot of
4810 cleanup to get us closer to a release candidate.
4812 o Security/privacy fixes:
4813 - Replace all potentially sensitive memory comparison operations
4814 with versions whose runtime does not depend on the data being
4815 compared. This will help resist a class of attacks where an
4816 adversary can use variations in timing information to learn
4817 sensitive data. Fix for one case of bug 3122. (Safe memcmp
4818 implementation by Robert Ransom based partially on code by DJB.)
4819 - When receiving a hidden service descriptor, check that it is for
4820 the hidden service we wanted. Previously, Tor would store any
4821 hidden service descriptors that a directory gave it, whether it
4822 wanted them or not. This wouldn't have let an attacker impersonate
4823 a hidden service, but it did let directories pre-seed a client
4824 with descriptors that it didn't want. Bugfix on 0.0.6.
4825 - On SIGHUP, do not clear out all TrackHostExits mappings, client
4826 DNS cache entries, and virtual address mappings: that's what
4827 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
4830 - The options SocksPort, ControlPort, and so on now all accept a
4831 value "auto" that opens a socket on an OS-selected port. A
4832 new ControlPortWriteToFile option tells Tor to write its
4833 actual control port or ports to a chosen file. If the option
4834 ControlPortFileGroupReadable is set, the file is created as
4835 group-readable. Now users can run two Tor clients on the same
4836 system without needing to manually mess with parameters. Resolves
4837 part of ticket 3076.
4838 - Set SO_REUSEADDR on all sockets, not just listeners. This should
4839 help busy exit nodes avoid running out of useable ports just
4840 because all the ports have been used in the near past. Resolves
4844 - New "GETINFO net/listeners/(type)" controller command to return
4845 a list of addresses and ports that are bound for listeners for a
4846 given connection type. This is useful when the user has configured
4847 "SocksPort auto" and the controller needs to know which port got
4848 chosen. Resolves another part of ticket 3076.
4849 - Add a new ControlSocketsGroupWritable configuration option: when
4850 it is turned on, ControlSockets are group-writeable by the default
4851 group of the current user. Patch by Jérémy Bobbio; implements
4853 - Tor now refuses to create a ControlSocket in a directory that is
4854 world-readable (or group-readable if ControlSocketsGroupWritable
4855 is 0). This is necessary because some operating systems do not
4856 enforce permissions on an AF_UNIX sockets. Permissions on the
4857 directory holding the socket, however, seems to work everywhere.
4858 - Rate-limit a warning about failures to download v2 networkstatus
4859 documents. Resolves part of bug 1352.
4860 - Backport code from 0.2.3.x that allows directory authorities to
4861 clean their microdescriptor caches. Needed to resolve bug 2230.
4862 - When an HTTPS proxy reports "403 Forbidden", we now explain
4863 what it means rather than calling it an unexpected status code.
4864 Closes bug 2503. Patch from Michael Yakubovich.
4865 - Update to the May 1 2011 Maxmind GeoLite Country database.
4868 - Authorities now clean their microdesc cache periodically and when
4869 reading from disk initially, not only when adding new descriptors.
4870 This prevents a bug where we could lose microdescriptors. Bugfix
4871 on 0.2.2.6-alpha. Fixes bug 2230.
4872 - Do not crash when our configuration file becomes unreadable, for
4873 example due to a permissions change, between when we start up
4874 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
4876 - Avoid a bug that would keep us from replacing a microdescriptor
4877 cache on Windows. (We would try to replace the file while still
4878 holding it open. That's fine on Unix, but Windows doesn't let us
4879 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
4880 - Add missing explanations for the authority-related torrc options
4881 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
4882 man page. Resolves issue 2379.
4883 - As an authority, do not upload our own vote or signature set to
4884 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
4885 it would get flagged as a duplicate. Resolves bug 3026.
4886 - Accept hidden service descriptors if we think we might be a hidden
4887 service directory, regardless of what our consensus says. This
4888 helps robustness, since clients and hidden services can sometimes
4889 have a more up-to-date view of the network consensus than we do,
4890 and if they think that the directory authorities list us a HSDir,
4891 we might actually be one. Related to bug 2732; bugfix on
4893 - When a controller changes TrackHostExits, remove mappings for
4894 hosts that should no longer have their exits tracked. Bugfix on
4896 - When a controller changes VirtualAddrNetwork, remove any mappings
4897 for hosts that were automapped to the old network. Bugfix on
4899 - When a controller changes one of the AutomapHosts* options, remove
4900 any mappings for hosts that should no longer be automapped. Bugfix
4902 - Do not reset the bridge descriptor download status every time we
4903 re-parse our configuration or get a configuration change. Fixes
4904 bug 3019; bugfix on 0.2.0.3-alpha.
4906 o Minor bugfixes (code cleanup):
4907 - When loading the microdesc journal, remember its current size.
4908 In 0.2.2, this helps prevent the microdesc journal from growing
4909 without limit on authorities (who are the only ones to use it in
4910 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
4911 Fix posted by "cypherpunks."
4912 - The microdesc journal is supposed to get rebuilt only if it is
4913 at least _half_ the length of the store, not _twice_ the length
4914 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
4915 - Fix a potential null-pointer dereference while computing a
4916 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
4918 - Avoid a possible null-pointer dereference when rebuilding the mdesc
4919 cache without actually having any descriptors to cache. Bugfix on
4920 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
4921 - If we fail to compute the identity digest of a v3 legacy keypair,
4922 warn, and don't use a buffer-full of junk instead. Bugfix on
4923 0.2.1.1-alpha; fixes bug 3106.
4924 - Resolve an untriggerable issue in smartlist_string_num_isin(),
4925 where if the function had ever in the future been used to check
4926 for the presence of a too-large number, it would have given an
4927 incorrect result. (Fortunately, we only used it for 16-bit
4928 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
4929 - Require that introduction point keys and onion handshake keys
4930 have a public exponent of 65537. Starts to fix bug 3207; bugfix
4934 - Caches no longer download and serve v2 networkstatus documents
4935 unless FetchV2Networkstatus flag is set: these documents haven't
4936 haven't been used by clients or relays since 0.2.0.x. Resolves
4940 Changes in version 0.2.3.1-alpha - 2011-05-05
4941 Tor 0.2.3.1-alpha adds some new experimental features, including support
4942 for an improved network IO backend, IOCP networking on Windows,
4943 microdescriptor caching, "fast-start" support for streams, and automatic
4944 home router configuration. There are also numerous internal improvements
4945 to try to make the code easier for developers to work with.
4947 This is the first alpha release in a new series, so expect there to be
4948 bugs. Users who would rather test out a more stable branch should
4949 stay with 0.2.2.x for now.
4952 - Tor can now optionally build with the "bufferevents" buffered IO
4953 backend provided by Libevent 2. To use this feature, make sure you
4954 have the latest possible version of Libevent, and pass the
4955 --enable-bufferevents flag to configure when building Tor from
4956 source. This feature will make our networking code more flexible,
4957 let us stack layers on each other, and let us use more efficient
4958 zero-copy transports where available.
4959 - As an experimental feature, Tor can use IOCP for networking on Windows.
4960 Once this code is tuned and optimized, it promises much better
4961 performance than the select-based backend we've used in the past. To
4962 try this feature, you must build Tor with Libevent 2, configure Tor
4963 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
4964 your torrc. There are known bugs here: only try this if you can help
4965 debug it as it breaks.
4966 - The EntryNodes option can now include country codes like {de} or IP
4967 addresses or network masks. Previously we had disallowed these options
4968 because we didn't have an efficient way to keep the list up to
4969 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
4970 - Exit nodes now accept and queue data on not-yet-connected streams.
4971 Previously, the client wasn't allowed to send data until the stream was
4972 connected, which slowed down all connections. This change will enable
4973 clients to perform a "fast-start" on streams and send data without
4974 having to wait for a confirmation that the stream has opened. (Patch
4975 from Ian Goldberg; implements the server side of Proposal 174.)
4976 - Tor now has initial support for automatic port mapping on the many
4977 home routers that support NAT-PMP or UPnP. (Not yet supported on
4978 Windows). To build the support code, you'll need to have libnatpnp
4979 library and/or the libminiupnpc library, and you'll need to enable the
4980 feature specifically by passing "--enable-upnp" and/or
4981 "--enable-natpnp" to configure. To turn it on, use the new
4982 PortForwarding option.
4983 - Caches now download, cache, and serve multiple "flavors" of the
4984 consensus, including a flavor that describes microdescriptors.
4985 - Caches now download, cache, and serve microdescriptors -- small
4986 summaries of router descriptors that are authenticated by all of the
4987 directory authorities. Once enough caches are running this code,
4988 clients will be able to save significant amounts of directory bandwidth
4989 by downloading microdescriptors instead of router descriptors.
4992 - Make logging resolution configurable with a new LogTimeGranularity
4993 option, and change the default from 1 millisecond to 1 second.
4994 Implements enhancement 1668.
4995 - We log which torrc file we're using on startup. Implements ticket
4997 - Ordinarily, Tor does not count traffic from private addresses (like
4998 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
4999 There is now a new option, CountPrivateBandwidth, to disable this
5000 behavior. Patch from Daniel Cagara.
5001 - New --enable-static-tor configure option for building Tor as
5002 statically as possible. Idea, general hackery and thoughts from
5003 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
5005 - If you set the NumCPUs option to 0, Tor will now try to detect how
5006 many CPUs you have. This is the new default behavior.
5007 - Turn on directory request statistics by default and include them in
5008 extra-info descriptors. Don't break if we have no GeoIP database.
5009 - Relays that set "ConnDirectionStatistics 1" write statistics on the
5010 bidirectional use of connections to disk every 24 hours.
5011 - Add a GeoIP file digest to the extra-info descriptor. Implements
5013 - The NodeFamily option -- which let you declare that you want to
5014 consider nodes to be part of a family whether they list themselves
5015 that way or not -- now allows IP address ranges and country codes.
5016 - Add a new 'Heartbeat' log message type to periodically log a message
5017 describing Tor's status at level Notice. This feature is meant for
5018 operators who log at notice, and want to make sure that their Tor
5019 server is still working. Implementation by George Kadianakis.
5021 o Minor bugfixes (on 0.2.2.25-alpha):
5022 - When loading the microdesc journal, remember its current size.
5023 In 0.2.2, this helps prevent the microdesc journal from growing
5024 without limit on authorities (who are the only ones to use it in
5025 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
5026 Fix posted by "cypherpunks."
5027 - The microdesc journal is supposed to get rebuilt only if it is
5028 at least _half_ the length of the store, not _twice_ the length
5029 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
5030 - If as an authority we fail to compute the identity digest of a v3
5031 legacy keypair, warn, and don't use a buffer-full of junk instead.
5032 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
5033 - Authorities now clean their microdesc cache periodically and when
5034 reading from disk initially, not only when adding new descriptors.
5035 This prevents a bug where we could lose microdescriptors. Bugfix
5038 o Minor features (controller):
5039 - Add a new SIGNAL event to the controller interface so that
5040 controllers can be notified when Tor handles a signal. Resolves
5041 issue 1955. Patch by John Brooks.
5042 - Add a new GETINFO option to get total bytes read and written. Patch
5043 from pipe, revised by atagar. Resolves ticket 2345.
5044 - Implement some GETINFO controller fields to provide information about
5045 the Tor process's pid, euid, username, and resource limits.
5048 - Our build system requires automake 1.6 or later to create the
5049 Makefile.in files. Previously, you could have used 1.4.
5050 This only affects developers and people building Tor from git;
5051 people who build Tor from the source distribution without changing
5052 the Makefile.am files should be fine.
5053 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
5054 so on. This is more robust against some of the failure modes
5055 associated with running the autotools pieces on their own.
5057 o Minor packaging issues:
5058 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
5059 already created. Patch from Andreas Stieger. Fixes bug 2573.
5061 o Code simplifications and refactoring:
5062 - A major revision to our internal node-selecting and listing logic.
5063 Tor already had at least two major ways to look at the question of
5064 "which Tor servers do we know about": a list of router descriptors,
5065 and a list of entries in the current consensus. With
5066 microdescriptors, we're adding a third. Having so many systems
5067 without an abstraction layer over them was hurting the codebase.
5068 Now, we have a new "node_t" abstraction that presents a consistent
5069 interface to a client's view of a Tor node, and holds (nearly) all
5070 of the mutable state formerly in routerinfo_t and routerstatus_t.
5071 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
5072 no longer link against Libevent: they never used it, but
5073 our library structure used to force them to link it.
5076 - Remove some old code to work around even older versions of Tor that
5077 used forked processes to handle DNS requests. Such versions of Tor
5078 are no longer in use as servers.
5080 o Documentation fixes:
5081 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
5082 - Add missing documentation for the authority-related torrc options
5083 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
5087 Changes in version 0.2.2.25-alpha - 2011-04-29
5088 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
5089 robust, routers no longer overreport their bandwidth, Win7 should crash
5090 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
5091 now prevents hidden service-related activity from being linkable. It
5092 provides more information to Vidalia so you can see if your bridge is
5093 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
5094 StrictNodes configuration options to make them more reliable, more
5095 understandable, and more regularly applied. If you use those options,
5096 please see the revised documentation for them in the manual page.
5099 - Relays were publishing grossly inflated bandwidth values because
5100 they were writing their state files wrong--now they write the
5101 correct value. Also, resume reading bandwidth history from the
5102 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
5103 - Improve hidden service robustness: When we find that we have
5104 extended a hidden service's introduction circuit to a relay not
5105 listed as an introduction point in the HS descriptor we currently
5106 have, retry with an introduction point from the current
5107 descriptor. Previously we would just give up. Fixes bugs 1024 and
5108 1930; bugfix on 0.2.0.10-alpha.
5109 - Clients now stop trying to use an exit node associated with a given
5110 destination by TrackHostExits if they fail to reach that exit node.
5111 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
5112 - Fix crash bug on platforms where gmtime and localtime can return
5113 NULL. Windows 7 users were running into this one. Fixes part of bug
5114 2077. Bugfix on all versions of Tor. Found by boboper.
5116 o Security and stability fixes:
5117 - Don't double-free a parsable, but invalid, microdescriptor, even if
5118 it is followed in the blob we're parsing by an unparsable
5119 microdescriptor. Fixes an issue reported in a comment on bug 2954.
5120 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
5121 - If the Nickname configuration option isn't given, Tor would pick a
5122 nickname based on the local hostname as the nickname for a relay.
5123 Because nicknames are not very important in today's Tor and the
5124 "Unnamed" nickname has been implemented, this is now problematic
5125 behavior: It leaks information about the hostname without being
5126 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
5127 introduced the Unnamed nickname. Reported by tagnaq.
5128 - Fix an uncommon assertion failure when running with DNSPort under
5129 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
5130 - Avoid linkability based on cached hidden service descriptors: forget
5131 all hidden service descriptors cached as a client when processing a
5132 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
5135 - Export GeoIP information on bridge usage to controllers even if we
5136 have not yet been running for 24 hours. Now Vidalia bridge operators
5137 can get more accurate and immediate feedback about their
5138 contributions to the network.
5140 o Major features and bugfixes (node selection):
5141 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
5142 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
5143 options. Previously, we had been ambiguous in describing what
5144 counted as an "exit" node, and what operations exactly "StrictNodes
5145 0" would permit. This created confusion when people saw nodes built
5146 through unexpected circuits, and made it hard to tell real bugs from
5147 surprises. Now the intended behavior is:
5148 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
5149 a node that delivers user traffic outside the Tor network.
5150 . "Entry", in the context of EntryNodes, means a node used as the
5151 first hop of a multihop circuit. It doesn't include direct
5152 connections to directory servers.
5153 . "ExcludeNodes" applies to all nodes.
5154 . "StrictNodes" changes the behavior of ExcludeNodes only. When
5155 StrictNodes is set, Tor should avoid all nodes listed in
5156 ExcludeNodes, even when it will make user requests fail. When
5157 StrictNodes is *not* set, then Tor should follow ExcludeNodes
5158 whenever it can, except when it must use an excluded node to
5159 perform self-tests, connect to a hidden service, provide a
5160 hidden service, fulfill a .exit request, upload directory
5161 information, or fetch directory information.
5162 Collectively, the changes to implement the behavior fix bug 1090.
5163 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
5164 a node is listed in both, it's treated as excluded.
5165 - ExcludeNodes now applies to directory nodes -- as a preference if
5166 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
5167 Don't exclude all the directory authorities and set StrictNodes to 1
5168 unless you really want your Tor to break.
5169 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
5170 - ExcludeExitNodes now overrides .exit requests.
5171 - We don't use bridges listed in ExcludeNodes.
5172 - When StrictNodes is 1:
5173 . We now apply ExcludeNodes to hidden service introduction points
5174 and to rendezvous points selected by hidden service users. This
5175 can make your hidden service less reliable: use it with caution!
5176 . If we have used ExcludeNodes on ourself, do not try relay
5177 reachability self-tests.
5178 . If we have excluded all the directory authorities, we will not
5179 even try to upload our descriptor if we're a relay.
5180 . Do not honor .exit requests to an excluded node.
5181 - Remove a misfeature that caused us to ignore the Fast/Stable flags
5182 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
5183 - When the set of permitted nodes changes, we now remove any mappings
5184 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
5186 - We never cannibalize a circuit that had excluded nodes on it, even
5187 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
5188 - Revert a change where we would be laxer about attaching streams to
5189 circuits than when building the circuits. This was meant to prevent
5190 a set of bugs where streams were never attachable, but our improved
5191 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
5192 - Keep track of how many times we launch a new circuit to handle a
5193 given stream. Too many launches could indicate an inconsistency
5194 between our "launch a circuit to handle this stream" logic and our
5195 "attach this stream to one of the available circuits" logic.
5196 - Improve log messages related to excluded nodes.
5199 - Fix a spurious warning when moving from a short month to a long
5200 month on relays with month-based BandwidthAccounting. Bugfix on
5201 0.2.2.17-alpha; fixes bug 3020.
5202 - When a client finds that an origin circuit has run out of 16-bit
5203 stream IDs, we now mark it as unusable for new streams. Previously,
5204 we would try to close the entire circuit. Bugfix on 0.0.6.
5205 - Add a forgotten cast that caused a compile warning on OS X 10.6.
5206 Bugfix on 0.2.2.24-alpha.
5207 - Be more careful about reporting the correct error from a failed
5208 connect() system call. Under some circumstances, it was possible to
5209 look at an incorrect value for errno when sending the end reason.
5210 Bugfix on 0.1.0.1-rc.
5211 - Correctly handle an "impossible" overflow cases in connection byte
5212 counting, where we write or read more than 4GB on an edge connection
5213 in a single second. Bugfix on 0.1.2.8-beta.
5214 - Correct the warning displayed when a rendezvous descriptor exceeds
5215 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
5217 - Clients and hidden services now use HSDir-flagged relays for hidden
5218 service descriptor downloads and uploads even if the relays have no
5219 DirPort set and the client has disabled TunnelDirConns. This will
5220 eventually allow us to give the HSDir flag to relays with no
5221 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
5222 - Downgrade "no current certificates known for authority" message from
5223 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
5224 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
5225 2917. Bugfix on 0.1.1.1-alpha.
5226 - Only limit the lengths of single HS descriptors, even when multiple
5227 HS descriptors are published to an HSDir relay in a single POST
5228 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
5229 - Write the current time into the LastWritten line in our state file,
5230 rather than the time from the previous write attempt. Also, stop
5231 trying to use a time of -1 in our log statements. Fixes bug 3039;
5232 bugfix on 0.2.2.14-alpha.
5233 - Be more consistent in our treatment of file system paths. "~" should
5234 get expanded to the user's home directory in the Log config option.
5235 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
5236 feature for the -f and --DataDirectory options.
5239 - Make sure every relay writes a state file at least every 12 hours.
5240 Previously, a relay could go for weeks without writing its state
5241 file, and on a crash could lose its bandwidth history, capacity
5242 estimates, client country statistics, and so on. Addresses bug 3012.
5243 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
5244 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
5245 clients are already deprecated because of security bugs.
5246 - Don't allow v0 hidden service authorities to act as clients.
5247 Required by fix for bug 3000.
5248 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
5249 by fix for bug 3000.
5250 - Ensure that no empty [dirreq-](read|write)-history lines are added
5251 to an extrainfo document. Implements ticket 2497.
5253 o Code simplification and refactoring:
5254 - Remove workaround code to handle directory responses from servers
5255 that had bug 539 (they would send HTTP status 503 responses _and_
5256 send a body too). Since only server versions before
5257 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
5258 keep the workaround in place.
5259 - Remove the old 'fuzzy time' logic. It was supposed to be used for
5260 handling calculations where we have a known amount of clock skew and
5261 an allowed amount of unknown skew. But we only used it in three
5262 places, and we never adjusted the known/unknown skew values. This is
5263 still something we might want to do someday, but if we do, we'll
5264 want to do it differently.
5265 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
5266 None of the cases where we did this before were wrong, but by making
5267 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
5268 - Use GetTempDir to find the proper temporary directory location on
5269 Windows when generating temporary files for the unit tests. Patch by
5273 Changes in version 0.2.2.24-alpha - 2011-04-08
5274 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
5275 prevented Tor clients from effectively using "multihomed" bridges,
5276 that is, bridges that listen on multiple ports or IP addresses so users
5277 can continue to use some of their addresses even if others get blocked.
5280 - Fix a bug where bridge users who configure the non-canonical
5281 address of a bridge automatically switch to its canonical
5282 address. If a bridge listens at more than one address, it should be
5283 able to advertise those addresses independently and any non-blocked
5284 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
5286 - If you configured Tor to use bridge A, and then quit and
5287 configured Tor to use bridge B instead, it would happily continue
5288 to use bridge A if it's still reachable. While this behavior is
5289 a feature if your goal is connectivity, in some scenarios it's a
5290 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
5291 - Directory authorities now use data collected from their own
5292 uptime observations when choosing whether to assign the HSDir flag
5293 to relays, instead of trusting the uptime value the relay reports in
5294 its descriptor. This change helps prevent an attack where a small
5295 set of nodes with frequently-changing identity keys can blackhole
5296 a hidden service. (Only authorities need upgrade; others will be
5297 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
5300 - When we restart our relay, we might get a successful connection
5301 from the outside before we've started our reachability tests,
5302 triggering a warning: "ORPort found reachable, but I have no
5303 routerinfo yet. Failing to inform controller of success." This
5304 bug was harmless unless Tor is running under a controller
5305 like Vidalia, in which case the controller would never get a
5306 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
5308 - Make directory authorities more accurate at recording when
5309 relays that have failed several reachability tests became
5310 unreachable, so we can provide more accuracy at assigning Stable,
5311 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
5312 - Fix an issue that prevented static linking of libevent on
5313 some platforms (notably Linux). Fixes bug 2698; bugfix on
5314 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
5315 the --with-static-libevent configure option).
5316 - We now ask the other side of a stream (the client or the exit)
5317 for more data on that stream when the amount of queued data on
5318 that stream dips low enough. Previously, we wouldn't ask the
5319 other side for more data until either it sent us more data (which
5320 it wasn't supposed to do if it had exhausted its window!) or we
5321 had completely flushed all our queued data. This flow control fix
5322 should improve throughput. Fixes bug 2756; bugfix on the earliest
5323 released versions of Tor (svn commit r152).
5324 - Avoid a double-mark-for-free warning when failing to attach a
5325 transparent proxy connection. (We thought we had fixed this in
5326 0.2.2.23-alpha, but it turns out our fix was checking the wrong
5327 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
5328 bug) and 0.2.2.23-alpha (the incorrect fix).
5329 - When warning about missing zlib development packages during compile,
5330 give the correct package names. Bugfix on 0.2.0.1-alpha.
5333 - Directory authorities now log the source of a rejected POSTed v3
5335 - Make compilation with clang possible when using
5336 --enable-gcc-warnings by removing two warning options that clang
5337 hasn't implemented yet and by fixing a few warnings. Implements
5339 - When expiring circuits, use microsecond timers rather than
5340 one-second timers. This can avoid an unpleasant situation where a
5341 circuit is launched near the end of one second and expired right
5342 near the beginning of the next, and prevent fluctuations in circuit
5344 - Use computed circuit-build timeouts to decide when to launch
5345 parallel introduction circuits for hidden services. (Previously,
5346 we would retry after 15 seconds.)
5347 - Update to the April 1 2011 Maxmind GeoLite Country database.
5350 - Create the /var/run/tor directory on startup on OpenSUSE if it is
5351 not already created. Patch from Andreas Stieger. Fixes bug 2573.
5353 o Documentation changes:
5354 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
5355 - Resolve all doxygen warnings except those for missing documentation.
5357 - Add doxygen documentation for more functions, fields, and types.
5360 Changes in version 0.2.2.23-alpha - 2011-03-08
5361 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
5362 they restart they don't lose their bandwidth capacity estimate. This
5363 release also fixes a diverse set of user-facing bugs, ranging from
5364 relays overrunning their rate limiting to clients falsely warning about
5365 clock skew to bridge descriptor leaks by our bridge directory authority.
5368 - Stop sending a CLOCK_SKEW controller status event whenever
5369 we fetch directory information from a relay that has a wrong clock.
5370 Instead, only inform the controller when it's a trusted authority
5371 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5372 the rest of bug 1074.
5373 - Fix an assert in parsing router descriptors containing IPv6
5374 addresses. This one took down the directory authorities when
5375 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
5376 - Make the bridge directory authority refuse to answer directory
5377 requests for "all" descriptors. It used to include bridge
5378 descriptors in its answer, which was a major information leak.
5379 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
5380 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5381 Tor would ignore their RelayBandwidthBurst setting,
5382 potentially using more bandwidth than expected. Bugfix on
5383 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5384 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5385 hidserv" in her torrc. The 'hidserv' argument never controlled
5386 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5389 - Relays now save observed peak bandwidth throughput rates to their
5390 state file (along with total usage, which was already saved)
5391 so that they can determine their correct estimated bandwidth on
5392 restart. Resolves bug 1863, where Tor relays would reset their
5393 estimated bandwidth to 0 after restarting.
5394 - Directory authorities now take changes in router IP address and
5395 ORPort into account when determining router stability. Previously,
5396 if a router changed its IP or ORPort, the authorities would not
5397 treat it as having any downtime for the purposes of stability
5398 calculation, whereas clients would experience downtime since the
5399 change could take a while to propagate to them. Resolves issue 1035.
5400 - Enable Address Space Layout Randomization (ASLR) and Data Execution
5401 Prevention (DEP) by default on Windows to make it harder for
5402 attackers to exploit vulnerabilities. Patch from John Brooks.
5404 o Minor bugfixes (on 0.2.1.x and earlier):
5405 - Fix a rare crash bug that could occur when a client was configured
5406 with a large number of bridges. Fixes bug 2629; bugfix on
5407 0.2.1.2-alpha. Bugfix by trac user "shitlei".
5408 - Avoid a double mark-for-free warning when failing to attach a
5409 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
5411 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
5412 found by "cypherpunks". This bug was introduced before the first
5413 Tor release, in svn commit r110.
5414 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
5415 don't mention them in the manpage. Fixes bug 2450; issue
5416 spotted by keb and G-Lo.
5417 - Fix a bug in bandwidth history state parsing that could have been
5418 triggered if a future version of Tor ever changed the timing
5419 granularity at which bandwidth history is measured. Bugfix on
5421 - When a relay decides that its DNS is too broken for it to serve
5422 as an exit server, it advertised itself as a non-exit, but
5423 continued to act as an exit. This could create accidental
5424 partitioning opportunities for users. Instead, if a relay is
5425 going to advertise reject *:* as its exit policy, it should
5426 really act with exit policy "reject *:*". Fixes bug 2366.
5427 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
5428 - In the special case where you configure a public exit relay as your
5429 bridge, Tor would be willing to use that exit relay as the last
5430 hop in your circuit as well. Now we fail that circuit instead.
5431 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
5432 - Fix a bug with our locking implementation on Windows that couldn't
5433 correctly detect when a file was already locked. Fixes bug 2504,
5434 bugfix on 0.2.1.6-alpha.
5435 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
5436 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
5438 - Set target port in get_interface_address6() correctly. Bugfix
5439 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
5440 - Directory authorities are now more robust to hops back in time
5441 when calculating router stability. Previously, if a run of uptime
5442 or downtime appeared to be negative, the calculation could give
5443 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
5445 - Fix an assert that got triggered when using the TestingTorNetwork
5446 configuration option and then issuing a GETINFO config-text control
5447 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
5449 o Minor bugfixes (on 0.2.2.x):
5450 - Clients should not weight BadExit nodes as Exits in their node
5451 selection. Similarly, directory authorities should not count BadExit
5452 bandwidth as Exit bandwidth when computing bandwidth-weights.
5453 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
5454 - Correctly clear our dir_read/dir_write history when there is an
5455 error parsing any bw history value from the state file. Bugfix on
5457 - Resolve a bug in verifying signatures of directory objects
5458 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
5459 Fixes bug 2409. Found by "piebeer".
5460 - Bridge authorities no longer crash on SIGHUP when they try to
5461 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
5465 - Log less aggressively about circuit timeout changes, and improve
5466 some other circuit timeout messages. Resolves bug 2004.
5467 - Log a little more clearly about the times at which we're no longer
5468 accepting new connections. Resolves bug 2181.
5469 - Reject attempts at the client side to open connections to private
5470 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
5471 a randomly chosen exit node. Attempts to do so are always
5472 ill-defined, generally prevented by exit policies, and usually
5473 in error. This will also help to detect loops in transparent
5474 proxy configurations. You can disable this feature by setting
5475 "ClientRejectInternalAddresses 0" in your torrc.
5476 - Always treat failure to allocate an RSA key as an unrecoverable
5478 - Update to the March 1 2011 Maxmind GeoLite Country database.
5480 o Minor features (log subsystem):
5481 - Add documentation for configuring logging at different severities in
5482 different log domains. We've had this feature since 0.2.1.1-alpha,
5483 but for some reason it never made it into the manpage. Fixes
5485 - Make it simpler to specify "All log domains except for A and B".
5486 Previously you needed to say "[*,~A,~B]". Now you can just say
5488 - Add a "LogMessageDomains 1" option to include the domains of log
5489 messages along with the messages. Without this, there's no way
5490 to use log domains without reading the source or doing a lot
5493 o Packaging changes:
5494 - Stop shipping the Tor specs files and development proposal documents
5495 in the tarball. They are now in a separate git repository at
5496 git://git.torproject.org/torspec.git
5499 Changes in version 0.2.1.30 - 2011-02-23
5500 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
5501 change is a slight tweak to Tor's TLS handshake that makes relays
5502 and bridges that run this new version reachable from Iran again.
5503 We don't expect this tweak will win the arms race long-term, but it
5504 buys us time until we roll out a better solution.
5507 - Stop sending a CLOCK_SKEW controller status event whenever
5508 we fetch directory information from a relay that has a wrong clock.
5509 Instead, only inform the controller when it's a trusted authority
5510 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5511 the rest of bug 1074.
5512 - Fix a bounds-checking error that could allow an attacker to
5513 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5515 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5516 Tor would ignore their RelayBandwidthBurst setting,
5517 potentially using more bandwidth than expected. Bugfix on
5518 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5519 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5520 hidserv" in her torrc. The 'hidserv' argument never controlled
5521 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5524 - Adjust our TLS Diffie-Hellman parameters to match those used by
5526 - Update to the February 1 2011 Maxmind GeoLite Country database.
5529 - Check for and reject overly long directory certificates and
5530 directory tokens before they have a chance to hit any assertions.
5531 Bugfix on 0.2.1.28. Found by "doorss".
5532 - Bring the logic that gathers routerinfos and assesses the
5533 acceptability of circuits into line. This prevents a Tor OP from
5534 getting locked in a cycle of choosing its local OR as an exit for a
5535 path (due to a .exit request) and then rejecting the circuit because
5536 its OR is not listed yet. It also prevents Tor clients from using an
5537 OR running in the same instance as an exit (due to a .exit request)
5538 if the OR does not meet the same requirements expected of an OR
5539 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5541 o Packaging changes:
5542 - Stop shipping the Tor specs files and development proposal documents
5543 in the tarball. They are now in a separate git repository at
5544 git://git.torproject.org/torspec.git
5545 - Do not include Git version tags as though they are SVN tags when
5546 generating a tarball from inside a repository that has switched
5547 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
5550 Changes in version 0.2.2.22-alpha - 2011-01-25
5551 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
5552 main other change is a slight tweak to Tor's TLS handshake that makes
5553 relays and bridges that run this new version reachable from Iran again.
5554 We don't expect this tweak will win the arms race long-term, but it
5555 will buy us a bit more time until we roll out a better solution.
5558 - Fix a bounds-checking error that could allow an attacker to
5559 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5561 - Don't assert when changing from bridge to relay or vice versa
5562 via the controller. The assert happened because we didn't properly
5563 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
5564 bug 2433. Reported by bastik.
5567 - Adjust our TLS Diffie-Hellman parameters to match those used by
5569 - Provide a log message stating which geoip file we're parsing
5570 instead of just stating that we're parsing the geoip file.
5571 Implements ticket 2432.
5574 - Check for and reject overly long directory certificates and
5575 directory tokens before they have a chance to hit any assertions.
5576 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
5579 Changes in version 0.2.2.21-alpha - 2011-01-15
5580 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
5581 continues our recent code security audit work. The main fix resolves
5582 a remote heap overflow vulnerability that can allow remote code
5583 execution (CVE-2011-0427). Other fixes address a variety of assert
5584 and crash bugs, most of which we think are hard to exploit remotely.
5586 o Major bugfixes (security), also included in 0.2.1.29:
5587 - Fix a heap overflow bug where an adversary could cause heap
5588 corruption. This bug probably allows remote code execution
5589 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5591 - Prevent a denial-of-service attack by disallowing any
5592 zlib-compressed data whose compression factor is implausibly
5593 high. Fixes part of bug 2324; reported by "doorss".
5594 - Zero out a few more keys in memory before freeing them. Fixes
5595 bug 2384 and part of bug 2385. These key instances found by
5596 "cypherpunks", based on Andrew Case's report about being able
5597 to find sensitive data in Tor's memory space if you have enough
5598 permissions. Bugfix on 0.0.2pre9.
5600 o Major bugfixes (crashes), also included in 0.2.1.29:
5601 - Prevent calls to Libevent from inside Libevent log handlers.
5602 This had potential to cause a nasty set of crashes, especially
5603 if running Libevent with debug logging enabled, and running
5604 Tor with a controller watching for low-severity log messages.
5605 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5606 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5607 underflow errors there too. Fixes the other part of bug 2324.
5608 - Fix a bug where we would assert if we ever had a
5609 cached-descriptors.new file (or another file read directly into
5610 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5611 on 0.2.1.25. Found by doorss.
5612 - Fix some potential asserts and parsing issues with grossly
5613 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5616 o Minor bugfixes (other), also included in 0.2.1.29:
5617 - Fix a bug with handling misformed replies to reverse DNS lookup
5618 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5619 bug reported by doorss.
5620 - Fix compilation on mingw when a pthreads compatibility library
5621 has been installed. (We don't want to use it, so we shouldn't
5622 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5623 - Fix a bug where we would declare that we had run out of virtual
5624 addresses when the address space was only half-exhausted. Bugfix
5626 - Correctly handle the case where AutomapHostsOnResolve is set but
5627 no virtual addresses are available. Fixes bug 2328; bugfix on
5628 0.1.2.1-alpha. Bug found by doorss.
5629 - Correctly handle wrapping around when we run out of virtual
5630 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
5632 o Minor features, also included in 0.2.1.29:
5633 - Update to the January 1 2011 Maxmind GeoLite Country database.
5634 - Introduce output size checks on all of our decryption functions.
5636 o Build changes, also included in 0.2.1.29:
5637 - Tor does not build packages correctly with Automake 1.6 and earlier;
5638 added a check to Makefile.am to make sure that we're building with
5639 Automake 1.7 or later.
5640 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5641 because we built it with a too-old version of automake. Thus that
5642 release broke ./configure --enable-openbsd-malloc, which is popular
5643 among really fast exit relays on Linux.
5645 o Major bugfixes, new in 0.2.2.21-alpha:
5646 - Prevent crash/heap corruption when the cbtnummodes consensus
5647 parameter is set to 0 or large values. Fixes bug 2317; bugfix
5650 o Major features, new in 0.2.2.21-alpha:
5651 - Introduce minimum/maximum values that clients will believe
5652 from the consensus. Now we'll have a better chance to avoid crashes
5653 or worse when a consensus param has a weird value.
5655 o Minor features, new in 0.2.2.21-alpha:
5656 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
5657 used on bridges, and it makes bridge scanning somewhat easier.
5658 - If writing the state file to disk fails, wait up to an hour before
5659 retrying again, rather than trying again each second. Fixes bug
5660 2346; bugfix on Tor 0.1.1.3-alpha.
5661 - Make Libevent log messages get delivered to controllers later,
5662 and not from inside the Libevent log handler. This prevents unsafe
5663 reentrant Libevent calls while still letting the log messages
5665 - Detect platforms that brokenly use a signed size_t, and refuse to
5666 build there. Found and analyzed by doorss and rransom.
5667 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
5670 o Minor bugfixes, new in 0.2.2.21-alpha:
5671 - Handle SOCKS messages longer than 128 bytes long correctly, rather
5672 than waiting forever for them to finish. Fixes bug 2330; bugfix
5673 on 0.2.0.16-alpha. Found by doorss.
5674 - Add assertions to check for overflow in arguments to
5675 base32_encode() and base32_decode(); fix a signed-unsigned
5676 comparison there too. These bugs are not actually reachable in Tor,
5677 but it's good to prevent future errors too. Found by doorss.
5678 - Correctly detect failures to create DNS requests when using Libevent
5679 versions before v2. (Before Libevent 2, we used our own evdns
5680 implementation. Its return values for Libevent's evdns_resolve_*()
5681 functions are not consistent with those from Libevent.) Fixes bug
5682 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
5684 o Documentation, new in 0.2.2.21-alpha:
5685 - Document the default socks host and port (127.0.0.1:9050) for
5689 Changes in version 0.2.1.29 - 2011-01-15
5690 Tor 0.2.1.29 continues our recent code security audit work. The main
5691 fix resolves a remote heap overflow vulnerability that can allow remote
5692 code execution. Other fixes address a variety of assert and crash bugs,
5693 most of which we think are hard to exploit remotely.
5695 o Major bugfixes (security):
5696 - Fix a heap overflow bug where an adversary could cause heap
5697 corruption. This bug probably allows remote code execution
5698 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5700 - Prevent a denial-of-service attack by disallowing any
5701 zlib-compressed data whose compression factor is implausibly
5702 high. Fixes part of bug 2324; reported by "doorss".
5703 - Zero out a few more keys in memory before freeing them. Fixes
5704 bug 2384 and part of bug 2385. These key instances found by
5705 "cypherpunks", based on Andrew Case's report about being able
5706 to find sensitive data in Tor's memory space if you have enough
5707 permissions. Bugfix on 0.0.2pre9.
5709 o Major bugfixes (crashes):
5710 - Prevent calls to Libevent from inside Libevent log handlers.
5711 This had potential to cause a nasty set of crashes, especially
5712 if running Libevent with debug logging enabled, and running
5713 Tor with a controller watching for low-severity log messages.
5714 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5715 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5716 underflow errors there too. Fixes the other part of bug 2324.
5717 - Fix a bug where we would assert if we ever had a
5718 cached-descriptors.new file (or another file read directly into
5719 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5720 on 0.2.1.25. Found by doorss.
5721 - Fix some potential asserts and parsing issues with grossly
5722 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5725 o Minor bugfixes (other):
5726 - Fix a bug with handling misformed replies to reverse DNS lookup
5727 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5728 bug reported by doorss.
5729 - Fix compilation on mingw when a pthreads compatibility library
5730 has been installed. (We don't want to use it, so we shouldn't
5731 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5732 - Fix a bug where we would declare that we had run out of virtual
5733 addresses when the address space was only half-exhausted. Bugfix
5735 - Correctly handle the case where AutomapHostsOnResolve is set but
5736 no virtual addresses are available. Fixes bug 2328; bugfix on
5737 0.1.2.1-alpha. Bug found by doorss.
5738 - Correctly handle wrapping around to when we run out of virtual
5739 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
5740 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5741 because we built it with a too-old version of automake. Thus that
5742 release broke ./configure --enable-openbsd-malloc, which is popular
5743 among really fast exit relays on Linux.
5746 - Update to the January 1 2011 Maxmind GeoLite Country database.
5747 - Introduce output size checks on all of our decryption functions.
5750 - Tor does not build packages correctly with Automake 1.6 and earlier;
5751 added a check to Makefile.am to make sure that we're building with
5752 Automake 1.7 or later.
5755 Changes in version 0.2.2.20-alpha - 2010-12-17
5756 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
5757 exploitable bugs. We also fix a variety of other significant bugs,
5758 change the IP address for one of our directory authorities, and update
5759 the minimum version that Tor relays must run to join the network.
5762 - Fix a remotely exploitable bug that could be used to crash instances
5763 of Tor remotely by overflowing on the heap. Remote-code execution
5764 hasn't been confirmed, but can't be ruled out. Everyone should
5765 upgrade. Bugfix on the 0.1.1 series and later.
5766 - Fix a bug that could break accounting on 64-bit systems with large
5767 time_t values, making them hibernate for impossibly long intervals.
5768 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
5769 - Fix a logic error in directory_fetches_from_authorities() that
5770 would cause all _non_-exits refusing single-hop-like circuits
5771 to fetch from authorities, when we wanted to have _exits_ fetch
5772 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
5774 - Fix a stream fairness bug that would cause newer streams on a given
5775 circuit to get preference when reading bytes from the origin or
5776 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
5777 introduced before the first Tor release, in svn revision r152.
5779 o Directory authority changes:
5780 - Change IP address and ports for gabelmoo (v3 directory authority).
5783 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
5784 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
5785 - Fix an off-by-one error in calculating some controller command
5786 argument lengths. Fortunately, this mistake is harmless since
5787 the controller code does redundant NUL termination too. Found by
5788 boboper. Bugfix on 0.1.1.1-alpha.
5789 - Do not dereference NULL if a bridge fails to build its
5790 extra-info descriptor. Found by an anonymous commenter on
5791 Trac. Bugfix on 0.2.2.19-alpha.
5794 - Update to the December 1 2010 Maxmind GeoLite Country database.
5795 - Directory authorities now reject relays running any versions of
5796 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
5797 known bugs that keep RELAY_EARLY cells from working on rendezvous
5798 circuits. Followup to fix for bug 2081.
5799 - Directory authorities now reject relays running any version of Tor
5800 older than 0.2.0.26-rc. That version is the earliest that fetches
5801 current directory information correctly. Fixes bug 2156.
5802 - Report only the top 10 ports in exit-port stats in order not to
5803 exceed the maximum extra-info descriptor length of 50 KB. Implements
5807 Changes in version 0.2.1.28 - 2010-12-17
5808 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
5809 exploitable bugs. We also took this opportunity to change the IP address
5810 for one of our directory authorities, and to update the geoip database
5814 - Fix a remotely exploitable bug that could be used to crash instances
5815 of Tor remotely by overflowing on the heap. Remote-code execution
5816 hasn't been confirmed, but can't be ruled out. Everyone should
5817 upgrade. Bugfix on the 0.1.1 series and later.
5819 o Directory authority changes:
5820 - Change IP address and ports for gabelmoo (v3 directory authority).
5823 - Update to the December 1 2010 Maxmind GeoLite Country database.
5826 Changes in version 0.2.1.27 - 2010-11-23
5827 Yet another OpenSSL security patch broke its compatibility with Tor:
5828 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
5829 also took this opportunity to fix several crash bugs, integrate a new
5830 directory authority, and update the bundled GeoIP database.
5833 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5834 No longer set the tlsext_host_name extension on server SSL objects;
5835 but continue to set it on client SSL objects. Our goal in setting
5836 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5837 bugfix on 0.2.1.1-alpha.
5838 - Do not log messages to the controller while shrinking buffer
5839 freelists. Doing so would sometimes make the controller connection
5840 try to allocate a buffer chunk, which would mess up the internals
5841 of the freelist and cause an assertion failure. Fixes bug 1125;
5842 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5843 - Learn our external IP address when we're a relay or bridge, even if
5844 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5845 where we introduced bridge relays that don't need to publish to
5846 be useful. Fixes bug 2050.
5847 - Do even more to reject (and not just ignore) annotations on
5848 router descriptors received anywhere but from the cache. Previously
5849 we would ignore such annotations at first, but cache them to disk
5850 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5851 - When you're using bridges and your network goes away and your
5852 bridges get marked as down, recover when you attempt a new socks
5853 connection (if the network is back), rather than waiting up to an
5854 hour to try fetching new descriptors for your bridges. Bugfix on
5855 0.2.0.3-alpha; fixes bug 1981.
5858 - Move to the November 2010 Maxmind GeoLite country db (rather
5859 than the June 2009 ip-to-country GeoIP db) for our statistics that
5860 count how many users relays are seeing from each country. Now we'll
5861 have more accurate data, especially for many African countries.
5863 o New directory authorities:
5864 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
5868 - Fix an assertion failure that could occur in directory caches or
5869 bridge users when using a very short voting interval on a testing
5870 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
5872 - Enforce multiplicity rules when parsing annotations. Bugfix on
5873 0.2.0.8-alpha. Found by piebeer.
5874 - Allow handshaking OR connections to take a full KeepalivePeriod
5875 seconds to handshake. Previously, we would close them after
5876 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
5877 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
5879 - When building with --enable-gcc-warnings on OpenBSD, disable
5880 warnings in system headers. This makes --enable-gcc-warnings
5881 pass on OpenBSD 4.8.
5884 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
5885 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
5886 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
5887 Servers can start sending this code when enough clients recognize
5888 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
5889 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
5890 Patch from mingw-san.
5893 - Remove the old debian/ directory from the main Tor distribution.
5894 The official Tor-for-debian git repository lives at the URL
5895 https://git.torproject.org/debian/tor.git
5896 - Stop shipping the old doc/website/ directory in the tarball. We
5897 changed the website format in late 2010, and what we shipped in
5898 0.2.1.26 really wasn't that useful anyway.
5901 Changes in version 0.2.2.19-alpha - 2010-11-22
5902 Yet another OpenSSL security patch broke its compatibility with Tor:
5903 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
5906 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5907 No longer set the tlsext_host_name extension on server SSL objects;
5908 but continue to set it on client SSL objects. Our goal in setting
5909 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5910 bugfix on 0.2.1.1-alpha.
5913 - Try harder not to exceed the maximum length of 50 KB when writing
5914 statistics to extra-info descriptors. This bug was triggered by very
5915 fast relays reporting exit-port, entry, and dirreq statistics.
5916 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
5917 - Publish a router descriptor even if generating an extra-info
5918 descriptor fails. Previously we would not publish a router
5919 descriptor without an extra-info descriptor; this can cause fast
5920 exit relays collecting exit-port statistics to drop from the
5921 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
5924 Changes in version 0.2.2.18-alpha - 2010-11-16
5925 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
5926 us lately, makes unpublished bridge relays able to detect their IP
5927 address, and fixes a wide variety of other bugs to get us much closer
5928 to a stable release.
5931 - Do even more to reject (and not just ignore) annotations on
5932 router descriptors received anywhere but from the cache. Previously
5933 we would ignore such annotations at first, but cache them to disk
5934 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5935 - Do not log messages to the controller while shrinking buffer
5936 freelists. Doing so would sometimes make the controller connection
5937 try to allocate a buffer chunk, which would mess up the internals
5938 of the freelist and cause an assertion failure. Fixes bug 1125;
5939 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5940 - Learn our external IP address when we're a relay or bridge, even if
5941 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5942 where we introduced bridge relays that don't need to publish to
5943 be useful. Fixes bug 2050.
5944 - Maintain separate TLS contexts and certificates for incoming and
5945 outgoing connections in bridge relays. Previously we would use the
5946 same TLS contexts and certs for incoming and outgoing connections.
5947 Bugfix on 0.2.0.3-alpha; addresses bug 988.
5948 - Maintain separate identity keys for incoming and outgoing TLS
5949 contexts in bridge relays. Previously we would use the same
5950 identity keys for incoming and outgoing TLS contexts. Bugfix on
5951 0.2.0.3-alpha; addresses the other half of bug 988.
5952 - Avoid an assertion failure when we as an authority receive a
5953 duplicate upload of a router descriptor that we already have,
5954 but which we previously considered an obsolete descriptor.
5955 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
5956 - Avoid a crash bug triggered by looking at a dangling pointer while
5957 setting the network status consensus. Found by Robert Ransom.
5958 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
5959 - Fix a logic error where servers that _didn't_ act as exits would
5960 try to keep their server lists more aggressively up to date than
5961 exits, when it was supposed to be the other way around. Bugfix
5964 o Minor bugfixes (on Tor 0.2.1.x and earlier):
5965 - When we're trying to guess whether we know our IP address as
5966 a relay, we would log various ways that we failed to guess
5967 our address, but never log that we ended up guessing it
5968 successfully. Now add a log line to help confused and anxious
5969 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
5970 - Bring the logic that gathers routerinfos and assesses the
5971 acceptability of circuits into line. This prevents a Tor OP from
5972 getting locked in a cycle of choosing its local OR as an exit for a
5973 path (due to a .exit request) and then rejecting the circuit because
5974 its OR is not listed yet. It also prevents Tor clients from using an
5975 OR running in the same instance as an exit (due to a .exit request)
5976 if the OR does not meet the same requirements expected of an OR
5977 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5978 - Correctly describe errors that occur when generating a TLS object.
5979 Previously we would attribute them to a failure while generating a
5980 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
5982 - Enforce multiplicity rules when parsing annotations. Bugfix on
5983 0.2.0.8-alpha. Found by piebeer.
5984 - Fix warnings that newer versions of autoconf produced during
5985 ./autogen.sh. These warnings appear to be harmless in our case,
5986 but they were extremely verbose. Fixes bug 2020.
5988 o Minor bugfixes (on Tor 0.2.2.x):
5989 - Enable protection of small arrays whenever we build with gcc
5990 hardening features, not only when also building with warnings
5991 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
5994 - Make hidden services work better in private Tor networks by not
5995 requiring any uptime to join the hidden service descriptor
5996 DHT. Implements ticket 2088.
5997 - Rate-limit the "your application is giving Tor only an IP address"
5998 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
5999 - When AllowSingleHopExits is set, print a warning to explain to the
6000 relay operator why most clients are avoiding her relay.
6001 - Update to the November 1 2010 Maxmind GeoLite Country database.
6003 o Code simplifications and refactoring:
6004 - When we fixed bug 1038 we had to put in a restriction not to send
6005 RELAY_EARLY cells on rend circuits. This was necessary as long
6006 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
6007 active. Now remove this obsolete check. Resolves bug 2081.
6008 - Some options used different conventions for uppercasing of acronyms
6009 when comparing manpage and source. Fix those in favor of the
6010 manpage, as it makes sense to capitalize acronyms.
6011 - Remove the torrc.complete file. It hasn't been kept up to date
6012 and users will have better luck checking out the manpage.
6013 - Remove the obsolete "NoPublish" option; it has been flagged
6014 as obsolete and has produced a warning since 0.1.1.18-rc.
6015 - Remove everything related to building the expert bundle for OS X.
6016 It has confused many users, doesn't work right on OS X 10.6,
6017 and is hard to get rid of once installed. Resolves bug 1274.
6020 Changes in version 0.2.2.17-alpha - 2010-09-30
6021 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
6022 to use one-hop circuits (which can put the exit relays at higher risk,
6023 plus unbalance the network); fixes a big bug in bandwidth accounting
6024 for relays that want to limit their monthly bandwidth use; fixes a
6025 big pile of bugs in how clients tolerate temporary network failure;
6026 and makes our adaptive circuit build timeout feature (which improves
6027 client performance if your network is fast while not breaking things
6028 if your network is slow) better handle bad networks.
6031 - Exit relays now try harder to block exit attempts from unknown
6032 relays, to make it harder for people to use them as one-hop proxies
6033 a la tortunnel. Controlled by the refuseunknownexits consensus
6034 parameter (currently enabled), or you can override it on your
6035 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
6037 o Major bugfixes (0.2.1.x and earlier):
6038 - Fix a bug in bandwidth accounting that could make us use twice
6039 the intended bandwidth when our interval start changes due to
6040 daylight saving time. Now we tolerate skew in stored vs computed
6041 interval starts: if the start of the period changes by no more than
6042 50% of the period's duration, we remember bytes that we transferred
6043 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
6044 - Always search the Windows system directory for system DLLs, and
6045 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
6046 - When you're using bridges and your network goes away and your
6047 bridges get marked as down, recover when you attempt a new socks
6048 connection (if the network is back), rather than waiting up to an
6049 hour to try fetching new descriptors for your bridges. Bugfix on
6050 0.2.0.3-alpha; fixes bug 1981.
6052 o Major bugfixes (on 0.2.2.x):
6053 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
6055 - Fix a segfault that could happen when operating a bridge relay with
6056 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
6057 - The consensus bandwidth-weights (used by clients to choose fast
6058 relays) entered an unexpected edge case in September where
6059 Exits were much scarcer than Guards, resulting in bad weight
6060 recommendations. Now we compute them using new constraints that
6061 should succeed in all cases. Also alter directory authorities to
6062 not include the bandwidth-weights line if they fail to produce
6063 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
6064 - When weighting bridges during path selection, we used to trust
6065 the bandwidths they provided in their descriptor, only capping them
6066 at 10MB/s. This turned out to be problematic for two reasons:
6067 Bridges could claim to handle a lot more traffic then they
6068 actually would, thus making more clients pick them and have a
6069 pretty effective DoS attack. The other issue is that new bridges
6070 that might not have a good estimate for their bw capacity yet
6071 would not get used at all unless no other bridges are available
6072 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
6074 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
6075 - Ignore cannibalized circuits when recording circuit build times.
6076 This should provide for a minor performance improvement for hidden
6077 service users using 0.2.2.14-alpha, and should remove two spurious
6078 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
6079 - Simplify the logic that causes us to decide if the network is
6080 unavailable for purposes of recording circuit build times. If we
6081 receive no cells whatsoever for the entire duration of a circuit's
6082 full measured lifetime, the network is probably down. Also ignore
6083 one-hop directory fetching circuit timeouts when calculating our
6084 circuit build times. These changes should hopefully reduce the
6085 cases where we see ridiculous circuit build timeouts for people
6086 with spotty wireless connections. Fixes part of bug 1772; bugfix
6088 - Prevent the circuit build timeout from becoming larger than
6089 the maximum build time we have ever seen. Also, prevent the time
6090 period for measurement circuits from becoming larger than twice that
6091 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
6094 - When we run out of directory information such that we can't build
6095 circuits, but then get enough that we can build circuits, log when
6096 we actually construct a circuit, so the user has a better chance of
6097 knowing what's going on. Fixes bug 1362.
6098 - Be more generous with how much bandwidth we'd use up (with
6099 accounting enabled) before entering "soft hibernation". Previously,
6100 we'd refuse new connections and circuits once we'd used up 95% of
6101 our allotment. Now, we use up 95% of our allotment, AND make sure
6102 that we have no more than 500MB (or 3 hours of expected traffic,
6103 whichever is lower) remaining before we enter soft hibernation.
6104 - If we've configured EntryNodes and our network goes away and/or all
6105 our entrynodes get marked down, optimistically retry them all when
6106 a new socks application request appears. Fixes bug 1882.
6107 - Add some more defensive programming for architectures that can't
6108 handle unaligned integer accesses. We don't know of any actual bugs
6109 right now, but that's the best time to fix them. Fixes bug 1943.
6110 - Support line continuations in the torrc config file. If a line
6111 ends with a single backslash character, the newline is ignored, and
6112 the configuration value is treated as continuing on the next line.
6115 o Minor bugfixes (on 0.2.1.x and earlier):
6116 - For bandwidth accounting, calculate our expected bandwidth rate
6117 based on the time during which we were active and not in
6118 soft-hibernation during the last interval. Previously, we were
6119 also considering the time spent in soft-hibernation. If this
6120 was a long time, we would wind up underestimating our bandwidth
6121 by a lot, and skewing our wakeup time towards the start of the
6122 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
6124 o Minor bugfixes (on 0.2.2.x):
6125 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
6126 which were disabled by the circuit build timeout changes in
6127 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
6128 - Make sure we don't warn about missing bandwidth weights when
6129 choosing bridges or other relays not in the consensus. Bugfix on
6130 0.2.2.10-alpha; fixes bug 1805.
6131 - In our logs, do not double-report signatures from unrecognized
6132 authorities both as "from unknown authority" and "not
6133 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
6136 Changes in version 0.2.2.16-alpha - 2010-09-17
6137 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
6138 evident at exit relays), and also continues to resolve all the little
6139 bugs that have been filling up trac lately.
6141 o Major bugfixes (stream-level fairness):
6142 - When receiving a circuit-level SENDME for a blocked circuit, try
6143 to package cells fairly from all the streams that had previously
6144 been blocked on that circuit. Previously, we had started with the
6145 oldest stream, and allowed each stream to potentially exhaust
6146 the circuit's package window. This gave older streams on any
6147 given circuit priority over newer ones. Fixes bug 1937. Detected
6148 originally by Camilo Viecco. This bug was introduced before the
6149 first Tor release, in svn commit r152: it is the new winner of
6150 the longest-lived bug prize.
6151 - When the exit relay got a circuit-level sendme cell, it started
6152 reading on the exit streams, even if had 500 cells queued in the
6153 circuit queue already, so the circuit queue just grew and grew in
6154 some cases. We fix this by not re-enabling reading on receipt of a
6155 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
6156 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
6158 - Newly created streams were allowed to read cells onto circuits,
6159 even if the circuit's cell queue was blocked and waiting to drain.
6160 This created potential unfairness, as older streams would be
6161 blocked, but newer streams would gladly fill the queue completely.
6162 We add code to detect this situation and prevent any stream from
6163 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
6167 - Update to the September 1 2010 Maxmind GeoLite Country database.
6168 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
6169 not. This would lead to a cookie that is still not group readable.
6170 Closes bug 1843. Suggested by katmagic.
6171 - When logging a rate-limited warning, we now mention how many messages
6172 got suppressed since the last warning.
6173 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
6174 do individual connection-level rate limiting of clients. The torrc
6175 config options with the same names trump the consensus params, if
6176 both are present. Replaces the old "bwconnrate" and "bwconnburst"
6177 consensus params which were broken from 0.2.2.7-alpha through
6178 0.2.2.14-alpha. Closes bug 1947.
6179 - When a router changes IP address or port, authorities now launch
6180 a new reachability test for it. Implements ticket 1899.
6181 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
6182 2 no signature, 4 required" messages about consensus signatures
6183 easier to read, and make sure they get logged at the same severity
6184 as the messages explaining which keys are which. Fixes bug 1290.
6185 - Don't warn when we have a consensus that we can't verify because
6186 of missing certificates, unless those certificates are ones
6187 that we have been trying and failing to download. Fixes bug 1145.
6188 - If you configure your bridge with a known identity fingerprint,
6189 and the bridge authority is unreachable (as it is in at least
6190 one country now), fall back to directly requesting the descriptor
6191 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
6193 - When building with --enable-gcc-warnings on OpenBSD, disable
6194 warnings in system headers. This makes --enable-gcc-warnings
6195 pass on OpenBSD 4.8.
6197 o Minor bugfixes (on 0.2.1.x and earlier):
6198 - Authorities will now attempt to download consensuses if their
6199 own efforts to make a live consensus have failed. This change
6200 means authorities that restart will fetch a valid consensus, and
6201 it means authorities that didn't agree with the current consensus
6202 will still fetch and serve it if it has enough signatures. Bugfix
6203 on 0.2.0.9-alpha; fixes bug 1300.
6204 - Ensure DNS requests launched by "RESOLVE" commands from the
6205 controller respect the __LeaveStreamsUnattached setconf options. The
6206 same goes for requests launched via DNSPort or transparent
6207 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
6208 - Allow handshaking OR connections to take a full KeepalivePeriod
6209 seconds to handshake. Previously, we would close them after
6210 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
6211 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
6213 - Rate-limit "Failed to hand off onionskin" warnings.
6214 - Never relay a cell for a circuit we have already destroyed.
6215 Between marking a circuit as closeable and finally closing it,
6216 it may have been possible for a few queued cells to get relayed,
6217 even though they would have been immediately dropped by the next
6218 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
6219 - Never queue a cell for a circuit that's already been marked
6221 - Never vote for a server as "Running" if we have a descriptor for
6222 it claiming to be hibernating, and that descriptor was published
6223 more recently than our last contact with the server. Bugfix on
6224 0.2.0.3-alpha; fixes bug 911.
6225 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
6228 o Minor bugfixes (on 0.2.2.x):
6229 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
6230 down if a directory fetch fails and you've configured either
6231 bridges or EntryNodes. The intent was to mark the relay as down
6232 _unless_ you're using bridges or EntryNodes, since if you are
6233 then you could quickly run out of entry points.
6234 - Fix the Windows directory-listing code. A bug introduced in
6235 0.2.2.14-alpha could make Windows directory servers forget to load
6236 some of their cached v2 networkstatus files.
6237 - Really allow clients to use relays as bridges. Fixes bug 1776;
6238 bugfix on 0.2.2.15-alpha.
6239 - Demote a warn to info that happens when the CellStatistics option
6240 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
6241 Reported by Moritz Bartl.
6242 - On Windows, build correctly either with or without Unicode support.
6243 This is necessary so that Tor can support fringe platforms like
6244 Windows 98 (which has no Unicode), or Windows CE (which has no
6245 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
6248 - Add a unit test for cross-platform directory-listing code.
6251 Changes in version 0.2.2.15-alpha - 2010-08-18
6252 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
6253 fixes a variety of other bugs that were preventing performance
6254 experiments from moving forward, fixes several bothersome memory leaks,
6255 and generally closes a lot of smaller bugs that have been filling up
6259 - Stop assigning the HSDir flag to relays that disable their
6260 DirPort (and thus will refuse to answer directory requests). This
6261 fix should dramatically improve the reachability of hidden services:
6262 hidden services and hidden service clients pick six HSDir relays
6263 to store and retrieve the hidden service descriptor, and currently
6264 about half of the HSDir relays will refuse to work. Bugfix on
6265 0.2.0.10-alpha; fixes part of bug 1693.
6266 - The PerConnBWRate and Burst config options, along with the
6267 bwconnrate and bwconnburst consensus params, initialized each conn's
6268 token bucket values only when the connection is established. Now we
6269 update them if the config options change, and update them every time
6270 we get a new consensus. Otherwise we can encounter an ugly edge
6271 case where we initialize an OR conn to client-level bandwidth,
6272 but then later the relay joins the consensus and we leave it
6273 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
6274 - Fix a regression that caused Tor to rebind its ports if it receives
6275 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
6278 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
6279 should give us approximately 40-50% more Guard-flagged nodes,
6280 improving the anonymity the Tor network can provide and also
6281 decreasing the dropoff in throughput that relays experience when
6282 they first get the Guard flag.
6283 - Allow enabling or disabling the *Statistics config options while
6287 - Update to the August 1 2010 Maxmind GeoLite Country database.
6288 - Have the controller interface give a more useful message than
6289 "Internal Error" in response to failed GETINFO requests.
6290 - Warn when the same option is provided more than once in a torrc
6291 file, on the command line, or in a single SETCONF statement, and
6292 the option is one that only accepts a single line. Closes bug 1384.
6293 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
6294 Patch from mingw-san.
6295 - Add support for the country code "{??}" in torrc options like
6296 ExcludeNodes, to indicate all routers of unknown country. Closes
6298 - Relays report the number of bytes spent on answering directory
6299 requests in extra-info descriptors similar to {read,write}-history.
6300 Implements enhancement 1790.
6302 o Minor bugfixes (on 0.2.1.x and earlier):
6303 - Complain if PublishServerDescriptor is given multiple arguments that
6304 include 0 or 1. This configuration will be rejected in the future.
6305 Bugfix on 0.2.0.1-alpha; closes bug 1107.
6306 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
6307 Bugfix on 0.2.0.13-alpha; closes bug 928.
6308 - Change "Application request when we're believed to be offline."
6309 notice to "Application request when we haven't used client
6310 functionality lately.", to clarify that it's not an error. Bugfix
6311 on 0.0.9.3; fixes bug 1222.
6312 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
6313 would return "551 Internal error" rather than "552 Unrecognized key
6314 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
6315 - Users can't configure a regular relay to be their bridge. It didn't
6316 work because when Tor fetched the bridge descriptor, it found
6317 that it already had it, and didn't realize that the purpose of the
6318 descriptor had changed. Now we replace routers with a purpose other
6319 than bridge with bridge descriptors when fetching them. Bugfix on
6320 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
6321 refetch the descriptor with router purpose 'general', disabling
6323 - Fix a rare bug in rend_fn unit tests: we would fail a test when
6324 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
6325 on 0.2.0.10-alpha; fixes bug 1808.
6326 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
6327 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
6328 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
6329 Servers can start sending this code when enough clients recognize
6330 it. Also update the spec to reflect this new reason. Bugfix on
6331 0.1.0.1-rc; fixes part of bug 1793.
6332 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
6333 when we switch from being a public relay to a bridge. Otherwise
6334 there will still be clients that see the relay in their consensus,
6335 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
6337 - Instead of giving an assertion failure on an internal mismatch
6338 on estimated freelist size, just log a BUG warning and try later.
6339 Mitigates but does not fix bug 1125.
6340 - Fix an assertion failure that could occur in caches or bridge users
6341 when using a very short voting interval on a testing network.
6342 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
6344 o Minor bugfixes (on 0.2.2.x):
6345 - Alter directory authorities to always consider Exit-flagged nodes
6346 as potential Guard nodes in their votes. The actual decision to
6347 use Exits as Guards is done in the consensus bandwidth weights.
6348 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
6349 - When the controller is reporting the purpose of circuits that
6350 didn't finish building before the circuit build timeout, it was
6351 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
6352 - Our libevent version parsing code couldn't handle versions like
6353 1.4.14b-stable and incorrectly warned the user about using an
6354 old and broken version of libevent. Treat 1.4.14b-stable like
6355 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
6357 - Don't use substitution references like $(VAR:MOD) when
6358 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
6359 '$(:x)' to 'x' rather than the empty string. This bites us in
6360 doc/ when configured with --disable-asciidoc. Bugfix on
6361 0.2.2.9-alpha; fixes bug 1773.
6362 - Remove a spurious hidden service server-side log notice about
6363 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
6365 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
6367 - Correctly report written bytes on linked connections. Found while
6368 implementing 1790. Bugfix on 0.2.2.4-alpha.
6369 - Fix three memory leaks: one in circuit_build_times_parse_state(),
6370 one in dirvote_add_signatures_to_pending_consensus(), and one every
6371 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
6372 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
6374 o Code simplifications and refactoring:
6375 - Take a first step towards making or.h smaller by splitting out
6376 function definitions for all source files in src/or/. Leave
6377 structures and defines in or.h for now.
6378 - Remove a bunch of unused function declarations as well as a block of
6379 #if 0'd code from the unit tests. Closes bug 1824.
6380 - New unit tests for exit-port history statistics; refactored exit
6381 statistics code to be more easily tested.
6382 - Remove the old debian/ directory from the main Tor distribution.
6383 The official Tor-for-debian git repository lives at the URL
6384 https://git.torproject.org/debian/tor.git
6387 Changes in version 0.2.2.14-alpha - 2010-07-12
6388 Tor 0.2.2.14-alpha greatly improves client-side handling of
6389 circuit build timeouts, which are used to estimate speed and improve
6390 performance. We also move to a much better GeoIP database, port Tor to
6391 Windows CE, introduce new compile flags that improve code security,
6392 add an eighth v3 directory authority, and address a lot of more
6396 - Tor directory authorities no longer crash when started with a
6397 cached-microdesc-consensus file in their data directory. Bugfix
6398 on 0.2.2.6-alpha; fixes bug 1532.
6399 - Treat an unset $HOME like an empty $HOME rather than triggering an
6400 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
6401 - Ignore negative and large circuit build timeout values that can
6402 happen during a suspend or hibernate. These values caused various
6403 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
6404 - Alter calculation of Pareto distribution parameter 'Xm' for
6405 Circuit Build Timeout learning to use the weighted average of the
6406 top N=3 modes (because we have three entry guards). Considering
6407 multiple modes should improve the timeout calculation in some cases,
6408 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
6410 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
6411 right censored distribution model. This approach improves over the
6412 synthetic timeout generation approach that was producing insanely
6413 high timeout values. Now we calculate build timeouts using truncated
6414 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
6415 - Do not close circuits that are under construction when they reach
6416 the circuit build timeout. Instead, leave them building (but do not
6417 use them) for up until the time corresponding to the 95th percentile
6418 on the Pareto CDF or 60 seconds, whichever is greater. This is done
6419 to provide better data for the new Pareto model. This percentile
6420 can be controlled by the consensus.
6423 - Move to the June 2010 Maxmind GeoLite country db (rather than the
6424 June 2009 ip-to-country GeoIP db) for our statistics that count
6425 how many users relays are seeing from each country. Now we have
6426 more accurate data for many African countries.
6427 - Port Tor to build and run correctly on Windows CE systems, using
6428 the wcecompat library. Contributed by Valerio Lupi.
6429 - New "--enable-gcc-hardening" ./configure flag (off by default)
6430 to turn on gcc compile time hardening options. It ensures
6431 that signed ints have defined behavior (-fwrapv), enables
6432 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
6433 with canaries (-fstack-protector-all), turns on ASLR protection if
6434 supported by the kernel (-fPIE, -pie), and adds additional security
6435 related warnings. Verified to work on Mac OS X and Debian Lenny.
6436 - New "--enable-linker-hardening" ./configure flag (off by default)
6437 to turn on ELF specific hardening features (relro, now). This does
6438 not work with Mac OS X or any other non-ELF binary format.
6440 o New directory authorities:
6441 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
6445 - New config option "WarnUnsafeSocks 0" disables the warning that
6446 occurs whenever Tor receives a socks handshake using a version of
6447 the socks protocol that can only provide an IP address (rather
6448 than a hostname). Setups that do DNS locally over Tor are fine,
6449 and we shouldn't spam the logs in that case.
6450 - Convert the HACKING file to asciidoc, and add a few new sections
6451 to it, explaining how we use Git, how we make changelogs, and
6452 what should go in a patch.
6453 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
6454 event, to give information on the current rate of circuit timeouts
6455 over our stored history.
6456 - Add ability to disable circuit build time learning via consensus
6457 parameter and via a LearnCircuitBuildTimeout config option. Also
6458 automatically disable circuit build time calculation if we are
6459 either a AuthoritativeDirectory, or if we fail to write our state
6460 file. Fixes bug 1296.
6461 - More gracefully handle corrupt state files, removing asserts
6462 in favor of saving a backup and resetting state.
6463 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
6467 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
6469 - When a2x fails, mention that the user could disable manpages instead
6470 of trying to fix their asciidoc installation.
6471 - Where available, use Libevent 2.0's periodic timers so that our
6472 once-per-second cleanup code gets called even more closely to
6473 once per second than it would otherwise. Fixes bug 943.
6474 - If you run a bridge that listens on multiple IP addresses, and
6475 some user configures a bridge address that uses a different IP
6476 address than your bridge writes in its router descriptor, and the
6477 user doesn't specify an identity key, their Tor would discard the
6478 descriptor because "it isn't one of our configured bridges", and
6479 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
6480 Bugfix on 0.2.0.3-alpha.
6481 - If OpenSSL fails to make a duplicate of a private or public key, log
6482 an error message and try to exit cleanly. May help with debugging
6483 if bug 1209 ever remanifests.
6484 - Save a couple bytes in memory allocation every time we escape
6485 certain characters in a string. Patch from Florian Zumbiehl.
6486 - Make it explicit that we don't cannibalize one-hop circuits. This
6487 happens in the wild, but doesn't turn out to be a problem because
6488 we fortunately don't use those circuits. Many thanks to outofwords
6489 for the initial analysis and to swissknife who confirmed that
6490 two-hop circuits are actually created.
6491 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
6492 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
6493 - Eliminate a case where a circuit build time warning was displayed
6494 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
6497 Changes in version 0.2.1.26 - 2010-05-02
6498 Tor 0.2.1.26 addresses the recent connection and memory overload
6499 problems we've been seeing on relays, especially relays with their
6500 DirPort open. If your relay has been crashing, or you turned it off
6501 because it used too many resources, give this release a try.
6503 This release also fixes yet another instance of broken OpenSSL libraries
6504 that was causing some relays to drop out of the consensus.
6507 - Teach relays to defend themselves from connection overload. Relays
6508 now close idle circuits early if it looks like they were intended
6509 for directory fetches. Relays are also more aggressive about closing
6510 TLS connections that have no circuits on them. Such circuits are
6511 unlikely to be re-used, and tens of thousands of them were piling
6512 up at the fast relays, causing the relays to run out of sockets
6513 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6514 their directory fetches over TLS).
6515 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6516 that claim to be earlier than 0.9.8m, but which have in reality
6517 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6518 behavior. Possible fix for some cases of bug 1346.
6519 - Directory mirrors were fetching relay descriptors only from v2
6520 directory authorities, rather than v3 authorities like they should.
6521 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6522 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6525 - Finally get rid of the deprecated and now harmful notion of "clique
6526 mode", where directory authorities maintain TLS connections to
6530 - In the util/threads test, no longer free the test_mutex before all
6531 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6532 - The master thread could starve the worker threads quite badly on
6533 certain systems, causing them to run only partially in the allowed
6534 window. This resulted in test failures. Now the master thread sleeps
6535 occasionally for a few microseconds while the two worker-threads
6536 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6539 Changes in version 0.2.2.13-alpha - 2010-04-24
6540 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
6541 problems we've been seeing on relays, especially relays with their
6542 DirPort open. If your relay has been crashing, or you turned it off
6543 because it used too many resources, give this release a try.
6546 - Teach relays to defend themselves from connection overload. Relays
6547 now close idle circuits early if it looks like they were intended
6548 for directory fetches. Relays are also more aggressive about closing
6549 TLS connections that have no circuits on them. Such circuits are
6550 unlikely to be re-used, and tens of thousands of them were piling
6551 up at the fast relays, causing the relays to run out of sockets
6552 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6553 their directory fetches over TLS).
6556 - Finally get rid of the deprecated and now harmful notion of "clique
6557 mode", where directory authorities maintain TLS connections to
6559 - Directory authorities now do an immediate reachability check as soon
6560 as they hear about a new relay. This change should slightly reduce
6561 the time between setting up a relay and getting listed as running
6562 in the consensus. It should also improve the time between setting
6563 up a bridge and seeing use by bridge users.
6564 - Directory authorities no longer launch a TLS connection to every
6565 relay as they startup. Now that we have 2k+ descriptors cached,
6566 the resulting network hiccup is becoming a burden. Besides,
6567 authorities already avoid voting about Running for the first half
6568 hour of their uptime.
6571 Changes in version 0.2.2.12-alpha - 2010-04-20
6572 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
6573 handle and vote on descriptors. It was causing relays to drop out of
6577 - Many relays have been falling out of the consensus lately because
6578 not enough authorities know about their descriptor for them to get
6579 a majority of votes. When we deprecated the v2 directory protocol,
6580 we got rid of the only way that v3 authorities can hear from each
6581 other about other descriptors. Now authorities examine every v3
6582 vote for new descriptors, and fetch them from that authority. Bugfix
6584 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
6585 and a warning in or.h related to bandwidth_weight_rule_t that
6586 prevented clean compile on OS X. Fixes bug 1363; bugfix on
6588 - Fix a segfault on relays when DirReqStatistics is enabled
6589 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
6593 - Demote a confusing TLS warning that relay operators might get when
6594 someone tries to talk to their OrPort. It is neither the operator's
6595 fault nor can they do anything about it. Fixes bug 1364; bugfix
6599 Changes in version 0.2.2.11-alpha - 2010-04-15
6600 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
6601 libraries that was causing some relays to drop out of the consensus.
6604 - Directory mirrors were fetching relay descriptors only from v2
6605 directory authorities, rather than v3 authorities like they should.
6606 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6607 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6608 - Fix a parsing error that made every possible value of
6609 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
6610 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
6611 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
6612 about the option without breaking older ones.
6613 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6614 that claim to be earlier than 0.9.8m, but which have in reality
6615 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6616 behavior. Possible fix for some cases of bug 1346.
6619 - Experiment with a more aggressive approach to preventing clients
6620 from making one-hop exit streams. Exit relays who want to try it
6621 out can set "RefuseUnknownExits 1" in their torrc, and then look
6622 for "Attempt by %s to open a stream" log messages. Let us know
6624 - Add support for statically linking zlib by specifying
6625 --enable-static-zlib, to go with our support for statically linking
6626 openssl and libevent. Resolves bug 1358.
6629 - Fix a segfault that happens whenever a Tor client that is using
6630 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
6632 - When we cleaned up the contrib/tor-exit-notice.html file, we left
6633 out the first line. Fixes bug 1295.
6634 - When building the manpage from a tarball, we required asciidoc, but
6635 the asciidoc -> roff/html conversion was already done for the
6636 tarball. Make 'make' complain only when we need asciidoc (either
6637 because we're compiling directly from git, or because we altered
6638 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
6639 - When none of the directory authorities vote on any params, Tor
6640 segfaulted when trying to make the consensus from the votes. We
6641 didn't trigger the bug in practice, because authorities do include
6642 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
6645 - In the util/threads test, no longer free the test_mutex before all
6646 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6647 - The master thread could starve the worker threads quite badly on
6648 certain systems, causing them to run only partially in the allowed
6649 window. This resulted in test failures. Now the master thread sleeps
6650 occasionally for a few microseconds while the two worker-threads
6651 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6654 Changes in version 0.2.2.10-alpha - 2010-03-07
6655 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
6656 could prevent relays from guessing their IP address correctly. It also
6657 starts the groundwork for another client-side performance boost, since
6658 currently we're not making efficient use of relays that have both the
6659 Guard flag and the Exit flag.
6662 - Fix a regression from our patch for bug 1244 that caused relays
6663 to guess their IP address incorrectly if they didn't set Address
6664 in their torrc and/or their address fails to resolve. Bugfix on
6665 0.2.2.9-alpha; fixes bug 1269.
6667 o Major features (performance):
6668 - Directory authorities now compute consensus weightings that instruct
6669 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
6670 and no flag. Clients that use these weightings will distribute
6671 network load more evenly across these different relay types. The
6672 weightings are in the consensus so we can change them globally in
6673 the future. Extra thanks to "outofwords" for finding some nasty
6674 security bugs in the first implementation of this feature.
6676 o Minor features (performance):
6677 - Always perform router selections using weighted relay bandwidth,
6678 even if we don't need a high capacity circuit at the time. Non-fast
6679 circuits now only differ from fast ones in that they can use relays
6680 not marked with the Fast flag. This "feature" could turn out to
6681 be a horrible bug; we should investigate more before it goes into
6685 - Allow disabling building of the manpages. Skipping the manpage
6686 speeds up the build considerably.
6688 o Minor bugfixes (on 0.2.2.x):
6689 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
6690 Bugfix on 0.2.2.9-alpha.
6691 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
6692 config option. Bugfix on 0.2.2.7-alpha.
6693 - Ship the asciidoc-helper file in the tarball, so that people can
6694 build from source if they want to, and touching the .1.txt files
6695 doesn't break the build. Bugfix on 0.2.2.9-alpha.
6697 o Minor bugfixes (on 0.2.1.x or earlier):
6698 - Fix a dereference-then-NULL-check sequence when publishing
6699 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6701 - Fix another dereference-then-NULL-check sequence. Bugfix on
6702 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6703 - Make sure we treat potentially not NUL-terminated strings correctly.
6704 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6706 o Code simplifications and refactoring:
6707 - Fix some urls in the exit notice file and make it XHTML1.1 strict
6708 compliant. Based on a patch from Christian Kujau.
6709 - Don't use sed in asciidoc-helper anymore.
6710 - Make the build process fail if asciidoc cannot be found and
6711 building with asciidoc isn't disabled.
6714 Changes in version 0.2.2.9-alpha - 2010-02-22
6715 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
6716 location of a directory authority, and cleans up a bunch of small bugs.
6718 o Directory authority changes:
6719 - Change IP address for dannenberg (v3 directory authority), and
6720 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6721 service directory authority) from the list.
6724 - Make Tor work again on the latest OS X: when deciding whether to
6725 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6726 version at run-time, not compile time. We need to do this because
6727 Apple doesn't update its dev-tools headers when it updates its
6728 libraries in a security patch.
6729 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6730 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6731 a memory leak when requesting a hidden service descriptor we've
6732 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6734 - Authorities could be tricked into giving out the Exit flag to relays
6735 that didn't allow exiting to any ports. This bug could screw
6736 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
6737 1238. Bug discovered by Martin Kowalczyk.
6738 - When freeing a session key, zero it out completely. We only zeroed
6739 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6740 patched by ekir. Fixes bug 1254.
6743 - Fix static compilation by listing the openssl libraries in the right
6744 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
6745 - Resume handling .exit hostnames in a special way: originally we
6746 stripped the .exit part and used the requested exit relay. In
6747 0.2.2.1-alpha we stopped treating them in any special way, meaning
6748 if you use a .exit address then Tor will pass it on to the exit
6749 relay. Now we reject the .exit stream outright, since that behavior
6750 might be more expected by the user. Found and diagnosed by Scott
6751 Bennett and Downie on or-talk.
6752 - Don't spam the controller with events when we have no file
6753 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
6754 for log messages was already solved from bug 748.)
6755 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
6757 - Make the DNSPort option work with libevent 2.x. Don't alter the
6758 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
6759 - Emit a GUARD DROPPED controller event for a case we missed.
6760 - Make more fields in the controller protocol case-insensitive, since
6761 control-spec.txt said they were.
6762 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6763 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6764 - Fix a spec conformance issue: the network-status-version token
6765 must be the first token in a v3 consensus or vote. Discovered by
6766 parakeep. Bugfix on 0.2.0.3-alpha.
6768 o Code simplifications and refactoring:
6769 - Generate our manpage and HTML documentation using Asciidoc. This
6770 change should make it easier to maintain the documentation, and
6772 - Remove the --enable-iphone option. According to reports from Marco
6773 Bonetti, Tor builds fine without any special tweaking on recent
6774 iPhone SDK versions.
6775 - Removed some unnecessary files from the source distribution. The
6776 AUTHORS file has now been merged into the people page on the
6777 website. The roadmaps and design doc can now be found in the
6778 projects directory in svn.
6779 - Enabled various circuit build timeout constants to be controlled
6780 by consensus parameters. Also set better defaults for these
6781 parameters based on experimentation on broadband and simulated
6785 - The 'EXTENDCIRCUIT' control port command can now be used with
6786 a circ id of 0 and no path. This feature will cause Tor to build
6787 a new 'fast' general purpose circuit using its own path selection
6789 - Added a BUILDTIMEOUT_SET controller event to describe changes
6790 to the circuit build timeout.
6791 - Future-proof the controller protocol a bit by ignoring keyword
6792 arguments we do not recognize.
6793 - Expand homedirs passed to tor-checkkey. This should silence a
6794 coverity complaint about passing a user-supplied string into
6795 open() without checking it.
6798 Changes in version 0.2.1.25 - 2010-03-16
6799 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
6800 prevent relays from guessing their IP address correctly. It also fixes
6801 several minor potential security bugs.
6804 - Fix a regression from our patch for bug 1244 that caused relays
6805 to guess their IP address incorrectly if they didn't set Address
6806 in their torrc and/or their address fails to resolve. Bugfix on
6807 0.2.1.23; fixes bug 1269.
6808 - When freeing a session key, zero it out completely. We only zeroed
6809 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6810 patched by ekir. Fixes bug 1254.
6813 - Fix a dereference-then-NULL-check sequence when publishing
6814 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6816 - Fix another dereference-then-NULL-check sequence. Bugfix on
6817 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6818 - Make sure we treat potentially not NUL-terminated strings correctly.
6819 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6823 Changes in version 0.2.1.24 - 2010-02-21
6824 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
6828 - Work correctly out-of-the-box with even more vendor-patched versions
6829 of OpenSSL. In particular, make it so Debian and OS X don't need
6830 customized patches to run/build.
6833 Changes in version 0.2.1.23 - 2010-02-13
6834 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
6835 again on the latest OS X, and updates the location of a directory
6838 o Major bugfixes (performance):
6839 - We were selecting our guards uniformly at random, and then weighting
6840 which of our guards we'd use uniformly at random. This imbalance
6841 meant that Tor clients were severely limited on throughput (and
6842 probably latency too) by the first hop in their circuit. Now we
6843 select guards weighted by currently advertised bandwidth. We also
6844 automatically discard guards picked using the old algorithm. Fixes
6845 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6848 - Make Tor work again on the latest OS X: when deciding whether to
6849 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6850 version at run-time, not compile time. We need to do this because
6851 Apple doesn't update its dev-tools headers when it updates its
6852 libraries in a security patch.
6853 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6854 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6855 a memory leak when requesting a hidden service descriptor we've
6856 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6859 o Directory authority changes:
6860 - Change IP address for dannenberg (v3 directory authority), and
6861 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6862 service directory authority) from the list.
6865 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6866 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6869 - Avoid a mad rush at the beginning of each month when each client
6870 rotates half of its guards. Instead we spread the rotation out
6871 throughout the month, but we still avoid leaving a precise timestamp
6872 in the state file about when we first picked the guard. Improves
6873 over the behavior introduced in 0.1.2.17.
6876 Changes in version 0.2.2.8-alpha - 2010-01-26
6877 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
6878 causing bridge relays to disappear. If you're running a bridge,
6882 - Fix a memory corruption bug on bridges that occured during the
6883 inclusion of stats data in extra-info descriptors. Also fix the
6884 interface for geoip_get_bridge_stats* to prevent similar bugs in
6885 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
6886 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
6889 - Ignore OutboundBindAddress when connecting to localhost.
6890 Connections to localhost need to come _from_ localhost, or else
6891 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
6895 Changes in version 0.2.2.7-alpha - 2010-01-19
6896 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
6897 as laying the groundwork for further relay-side performance fixes. It
6898 also starts cleaning up client behavior with respect to the EntryNodes,
6899 ExitNodes, and StrictNodes config options.
6901 This release also rotates two directory authority keys, due to a
6902 security breach of some of the Torproject servers.
6904 o Directory authority changes:
6905 - Rotate keys (both v3 identity and relay identity) for moria1
6908 o Major features (performance):
6909 - We were selecting our guards uniformly at random, and then weighting
6910 which of our guards we'd use uniformly at random. This imbalance
6911 meant that Tor clients were severely limited on throughput (and
6912 probably latency too) by the first hop in their circuit. Now we
6913 select guards weighted by currently advertised bandwidth. We also
6914 automatically discard guards picked using the old algorithm. Fixes
6915 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6916 - When choosing which cells to relay first, relays can now favor
6917 circuits that have been quiet recently, to provide lower latency
6918 for low-volume circuits. By default, relays enable or disable this
6919 feature based on a setting in the consensus. You can override
6920 this default by using the new "CircuitPriorityHalflife" config
6921 option. Design and code by Ian Goldberg, Can Tang, and Chris
6923 - Add separate per-conn write limiting to go with the per-conn read
6924 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
6925 but never per-conn write limits.
6926 - New consensus params "bwconnrate" and "bwconnburst" to let us
6927 rate-limit client connections as they enter the network. It's
6928 controlled in the consensus so we can turn it on and off for
6929 experiments. It's starting out off. Based on proposal 163.
6931 o Major features (relay selection options):
6932 - Switch to a StrictNodes config option, rather than the previous
6933 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
6934 "StrictExcludeNodes" option.
6935 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
6936 change during a config reload, mark and discard all our origin
6937 circuits. This fix should address edge cases where we change the
6938 config options and but then choose a circuit that we created before
6940 - If EntryNodes or ExitNodes are set, be more willing to use an
6941 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
6943 - Make EntryNodes config option much more aggressive even when
6944 StrictNodes is not set. Before it would prepend your requested
6945 entrynodes to your list of guard nodes, but feel free to use others
6946 after that. Now it chooses only from your EntryNodes if any of
6947 those are available, and only falls back to others if a) they're
6948 all down and b) StrictNodes is not set.
6949 - Now we refresh your entry guards from EntryNodes at each consensus
6950 fetch -- rather than just at startup and then they slowly rot as
6951 the network changes.
6954 - Stop bridge directory authorities from answering dbg-stability.txt
6955 directory queries, which would let people fetch a list of all
6956 bridge identities they track. Bugfix on 0.2.1.6-alpha.
6959 - Log a notice when we get a new control connection. Now it's easier
6960 for security-conscious users to recognize when a local application
6961 is knocking on their controller door. Suggested by bug 1196.
6962 - New config option "CircuitStreamTimeout" to override our internal
6963 timeout schedule for how many seconds until we detach a stream from
6964 a circuit and try a new circuit. If your network is particularly
6965 slow, you might want to set this to a number like 60.
6966 - New controller command "getinfo config-text". It returns the
6967 contents that Tor would write if you send it a SAVECONF command,
6968 so the controller can write the file to disk itself.
6969 - New options for SafeLogging to allow scrubbing only log messages
6970 generated while acting as a relay.
6971 - Ship the bridges spec file in the tarball too.
6972 - Avoid a mad rush at the beginning of each month when each client
6973 rotates half of its guards. Instead we spread the rotation out
6974 throughout the month, but we still avoid leaving a precise timestamp
6975 in the state file about when we first picked the guard. Improves
6976 over the behavior introduced in 0.1.2.17.
6978 o Minor bugfixes (compiling):
6979 - Fix compilation on OS X 10.3, which has a stub mlockall() but
6980 hides it. Bugfix on 0.2.2.6-alpha.
6981 - Fix compilation on Solaris by removing support for the
6982 DisableAllSwap config option. Solaris doesn't have an rlimit for
6983 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
6986 o Minor bugfixes (crashes):
6987 - Do not segfault when writing buffer stats when we haven't observed
6988 a single circuit to report about. Found by Fabian Lanze. Bugfix on
6990 - If we're in the pathological case where there's no exit bandwidth
6991 but there is non-exit bandwidth, or no guard bandwidth but there
6992 is non-guard bandwidth, don't crash during path selection. Bugfix
6994 - Fix an impossible-to-actually-trigger buffer overflow in relay
6995 descriptor generation. Bugfix on 0.1.0.15.
6997 o Minor bugfixes (privacy):
6998 - Fix an instance where a Tor directory mirror might accidentally
6999 log the IP address of a misbehaving Tor client. Bugfix on
7001 - Don't list Windows capabilities in relay descriptors. We never made
7002 use of them, and maybe it's a bad idea to publish them. Bugfix
7005 o Minor bugfixes (other):
7006 - Resolve an edge case in path weighting that could make us misweight
7007 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
7008 - Fix statistics on client numbers by country as seen by bridges that
7009 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
7010 intervals instead of variable 12-to-48-hour intervals.
7011 - After we free an internal connection structure, overwrite it
7012 with a different memory value than we use for overwriting a freed
7013 internal circuit structure. Should help with debugging. Suggested
7015 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
7019 - Remove the HSAuthorityRecordStats option that version 0 hidden
7020 service authorities could have used to track statistics of overall
7021 hidden service usage.
7024 Changes in version 0.2.1.22 - 2010-01-19
7025 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
7026 authorities -- it would tell you its whole history of bridge descriptors
7027 if you make the right directory request. This stable update also
7028 rotates two of the seven v3 directory authority keys and locations.
7030 o Directory authority changes:
7031 - Rotate keys (both v3 identity and relay identity) for moria1
7035 - Stop bridge directory authorities from answering dbg-stability.txt
7036 directory queries, which would let people fetch a list of all
7037 bridge identities they track. Bugfix on 0.2.1.6-alpha.
7040 Changes in version 0.2.1.21 - 2009-12-21
7041 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
7042 library. If you use Tor on Linux / Unix and you're getting SSL
7043 renegotiation errors, upgrading should help. We also recommend an
7044 upgrade if you're an exit relay.
7047 - Work around a security feature in OpenSSL 0.9.8l that prevents our
7048 handshake from working unless we explicitly tell OpenSSL that we
7049 are using SSL renegotiation safely. We are, of course, but OpenSSL
7050 0.9.8l won't work unless we say we are.
7051 - Avoid crashing if the client is trying to upload many bytes and the
7052 circuit gets torn down at the same time, or if the flip side
7053 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
7056 - Do not refuse to learn about authority certs and v2 networkstatus
7057 documents that are older than the latest consensus. This bug might
7058 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
7059 Spotted and fixed by xmux.
7060 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
7061 trigger platform-specific option misparsing case found by Coverity
7063 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
7064 trigger assert. Fixes bug 1173.
7067 Changes in version 0.2.2.6-alpha - 2009-11-19
7068 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
7069 support for the new lower-footprint "microdescriptor" directory design,
7070 future-proofing our consensus format against new hash functions or
7071 other changes, and an Android port. It also makes Tor compatible with
7072 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
7075 - Directory authorities can now create, vote on, and serve multiple
7076 parallel formats of directory data as part of their voting process.
7077 Partially implements Proposal 162: "Publish the consensus in
7079 - Directory authorities can now agree on and publish small summaries
7080 of router information that clients can use in place of regular
7081 server descriptors. This transition will eventually allow clients
7082 to use far less bandwidth for downloading information about the
7083 network. Begins the implementation of Proposal 158: "Clients
7084 download consensus + microdescriptors".
7085 - The directory voting system is now extensible to use multiple hash
7086 algorithms for signatures and resource selection. Newer formats
7087 are signed with SHA256, with a possibility for moving to a better
7088 hash algorithm in the future.
7089 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
7090 current and future memory pages via mlockall(). On supported
7091 platforms (modern Linux and probably BSD but not Windows or OS X),
7092 this should effectively disable any and all attempts to page out
7093 memory. This option requires that you start your Tor as root --
7094 if you use DisableAllSwap, please consider using the User option
7095 to properly reduce the privileges of your Tor.
7096 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
7097 to help Tor build correctly for Android phones.
7100 - Work around a security feature in OpenSSL 0.9.8l that prevents our
7101 handshake from working unless we explicitly tell OpenSSL that we
7102 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
7103 won't work unless we say we are.
7106 - Fix a crash bug when trying to initialize the evdns module in
7107 Libevent 2. Bugfix on 0.2.1.16-rc.
7108 - Stop logging at severity 'warn' when some other Tor client tries
7109 to establish a circuit with us using weak DH keys. It's a protocol
7110 violation, but that doesn't mean ordinary users need to hear about
7111 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
7112 - Do not refuse to learn about authority certs and v2 networkstatus
7113 documents that are older than the latest consensus. This bug might
7114 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
7115 Spotted and fixed by xmux.
7116 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
7117 - If all authorities restart at once right before a consensus vote,
7118 nobody will vote about "Running", and clients will get a consensus
7119 with no usable relays. Instead, authorities refuse to build a
7120 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
7121 - If your relay can't keep up with the number of incoming create
7122 cells, it would log one warning per failure into your logs. Limit
7123 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
7124 - Bridges now use "reject *:*" as their default exit policy. Bugfix
7125 on 0.2.0.3-alpha; fixes bug 1113.
7126 - Fix a memory leak on directory authorities during voting that was
7127 introduced in 0.2.2.1-alpha. Found via valgrind.
7130 Changes in version 0.2.1.20 - 2009-10-15
7131 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
7132 services at once, prepares for more performance improvements, and
7133 fixes a bunch of smaller bugs.
7135 The Windows and OS X bundles also include a more recent Vidalia,
7136 and switch from Privoxy to Polipo.
7138 The OS X installers are now drag and drop. It's best to un-install
7139 Tor/Vidalia and then install this new bundle, rather than upgrade. If
7140 you want to upgrade, you'll need to update the paths for Tor and Polipo
7141 in the Vidalia Settings window.
7144 - Send circuit or stream sendme cells when our window has decreased
7145 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
7146 by Karsten when testing the "reduce circuit window" performance
7147 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7148 before the release of Tor 0.0.0. This is the new winner of the
7150 - Fix a remotely triggerable memory leak when a consensus document
7151 contains more than one signature from the same voter. Bugfix on
7153 - Avoid segfault in rare cases when finishing an introduction circuit
7154 as a client and finding out that we don't have an introduction key
7155 for it. Fixes bug 1073. Reported by Aaron Swartz.
7158 - Tor now reads the "circwindow" parameter out of the consensus,
7159 and uses that value for its circuit package window rather than the
7160 default of 1000 cells. Begins the implementation of proposal 168.
7162 o New directory authorities:
7163 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
7165 - Move moria1 and tonga to alternate IP addresses.
7168 - Fix a signed/unsigned compile warning in 0.2.1.19.
7169 - Fix possible segmentation fault on directory authorities. Bugfix on
7171 - Fix an extremely rare infinite recursion bug that could occur if
7172 we tried to log a message after shutting down the log subsystem.
7173 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
7174 - Fix an obscure bug where hidden services on 64-bit big-endian
7175 systems might mis-read the timestamp in v3 introduce cells, and
7176 refuse to connect back to the client. Discovered by "rotor".
7177 Bugfix on 0.2.1.6-alpha.
7178 - We were triggering a CLOCK_SKEW controller status event whenever
7179 we connect via the v2 connection protocol to any relay that has
7180 a wrong clock. Instead, we should only inform the controller when
7181 it's a trusted authority that claims our clock is wrong. Bugfix
7182 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
7183 - We were telling the controller about CHECKING_REACHABILITY and
7184 REACHABILITY_FAILED status events whenever we launch a testing
7185 circuit or notice that one has failed. Instead, only tell the
7186 controller when we want to inform the user of overall success or
7187 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7189 - Don't warn when we're using a circuit that ends with a node
7190 excluded in ExcludeExitNodes, but the circuit is not used to access
7191 the outside world. This should help fix bug 1090. Bugfix on
7193 - Work around a small memory leak in some versions of OpenSSL that
7194 stopped the memory used by the hostname TLS extension from being
7198 - Add a "getinfo status/accepted-server-descriptor" controller
7199 command, which is the recommended way for controllers to learn
7200 whether our server descriptor has been successfully received by at
7201 least on directory authority. Un-recommend good-server-descriptor
7202 getinfo and status events until we have a better design for them.
7205 Changes in version 0.2.2.5-alpha - 2009-10-11
7206 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
7209 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
7211 o Directory authorities:
7212 - Temporarily (just for this release) move dizum to an alternate
7216 Changes in version 0.2.2.4-alpha - 2009-10-10
7217 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
7218 introduces a new unit test framework, shifts directry authority
7219 addresses around to reduce the impact from recent blocking events,
7220 and fixes a few smaller bugs.
7223 - Fix several more asserts in the circuit_build_times code, for
7224 example one that causes Tor to fail to start once we have
7225 accumulated 5000 build times in the state file. Bugfixes on
7226 0.2.2.2-alpha; fixes bug 1108.
7228 o New directory authorities:
7229 - Move moria1 and Tonga to alternate IP addresses.
7232 - Log SSL state transitions at debug level during handshake, and
7233 include SSL states in error messages. This may help debug future
7234 SSL handshake issues.
7235 - Add a new "Handshake" log domain for activities that happen
7236 during the TLS handshake.
7237 - Revert to the "June 3 2009" ip-to-country file. The September one
7238 seems to have removed most US IP addresses.
7239 - Directory authorities now reject Tor relays with versions less than
7240 0.1.2.14. This step cuts out four relays from the current network,
7241 none of which are very big.
7244 - Fix a couple of smaller issues with gathering statistics. Bugfixes
7246 - Fix two memory leaks in the error case of
7247 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
7248 - Don't count one-hop circuits when we're estimating how long it
7249 takes circuits to build on average. Otherwise we'll set our circuit
7250 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
7251 - Directory authorities no longer change their opinion of, or vote on,
7252 whether a router is Running, unless they have themselves been
7253 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
7256 o Code simplifications and refactoring:
7257 - Revise our unit tests to use the "tinytest" framework, so we
7258 can run tests in their own processes, have smarter setup/teardown
7259 code, and so on. The unit test code has moved to its own
7260 subdirectory, and has been split into multiple modules.
7263 Changes in version 0.2.2.3-alpha - 2009-09-23
7264 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
7267 - Fix an overzealous assert in our new circuit build timeout code.
7268 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
7271 - If the networkstatus consensus tells us that we should use a
7272 negative circuit package window, ignore it. Otherwise we'll
7273 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
7276 Changes in version 0.2.2.2-alpha - 2009-09-21
7277 Tor 0.2.2.2-alpha introduces our latest performance improvement for
7278 clients: Tor tracks the average time it takes to build a circuit, and
7279 avoids using circuits that take too long to build. For fast connections,
7280 this feature can cut your expected latency in half. For slow or flaky
7281 connections, it could ruin your Tor experience. Let us know if it does!
7284 - Tor now tracks how long it takes to build client-side circuits
7285 over time, and adapts its timeout to local network performance.
7286 Since a circuit that takes a long time to build will also provide
7287 bad performance, we get significant latency improvements by
7288 discarding the slowest 20% of circuits. Specifically, Tor creates
7289 circuits more aggressively than usual until it has enough data
7290 points for a good timeout estimate. Implements proposal 151.
7291 We are especially looking for reports (good and bad) from users with
7292 both EDGE and broadband connections that can move from broadband
7293 to EDGE and find out if the build-time data in the .tor/state gets
7294 reset without loss of Tor usability. You should also see a notice
7295 log message telling you that Tor has reset its timeout.
7296 - Directory authorities can now vote on arbitary integer values as
7297 part of the consensus process. This is designed to help set
7298 network-wide parameters. Implements proposal 167.
7299 - Tor now reads the "circwindow" parameter out of the consensus,
7300 and uses that value for its circuit package window rather than the
7301 default of 1000 cells. Begins the implementation of proposal 168.
7304 - Fix a remotely triggerable memory leak when a consensus document
7305 contains more than one signature from the same voter. Bugfix on
7309 - Fix an extremely rare infinite recursion bug that could occur if
7310 we tried to log a message after shutting down the log subsystem.
7311 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
7312 - Fix parsing for memory or time units given without a space between
7313 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
7314 - A networkstatus vote must contain exactly one signature. Spec
7315 conformance issue. Bugfix on 0.2.0.3-alpha.
7316 - Fix an obscure bug where hidden services on 64-bit big-endian
7317 systems might mis-read the timestamp in v3 introduce cells, and
7318 refuse to connect back to the client. Discovered by "rotor".
7319 Bugfix on 0.2.1.6-alpha.
7320 - We were triggering a CLOCK_SKEW controller status event whenever
7321 we connect via the v2 connection protocol to any relay that has
7322 a wrong clock. Instead, we should only inform the controller when
7323 it's a trusted authority that claims our clock is wrong. Bugfix
7324 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
7325 - We were telling the controller about CHECKING_REACHABILITY and
7326 REACHABILITY_FAILED status events whenever we launch a testing
7327 circuit or notice that one has failed. Instead, only tell the
7328 controller when we want to inform the user of overall success or
7329 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7331 - Don't warn when we're using a circuit that ends with a node
7332 excluded in ExcludeExitNodes, but the circuit is not used to access
7333 the outside world. This should help fix bug 1090, but more problems
7334 remain. Bugfix on 0.2.1.6-alpha.
7335 - Work around a small memory leak in some versions of OpenSSL that
7336 stopped the memory used by the hostname TLS extension from being
7338 - Make our 'torify' script more portable; if we have only one of
7339 'torsocks' or 'tsocks' installed, don't complain to the user;
7340 and explain our warning about tsocks better.
7343 - Add a "getinfo status/accepted-server-descriptor" controller
7344 command, which is the recommended way for controllers to learn
7345 whether our server descriptor has been successfully received by at
7346 least on directory authority. Un-recommend good-server-descriptor
7347 getinfo and status events until we have a better design for them.
7348 - Update to the "September 4 2009" ip-to-country file.
7351 Changes in version 0.2.2.1-alpha - 2009-08-26
7352 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
7353 Tor clients to bootstrap on networks where only port 80 is reachable,
7354 makes it more straightforward to support hardware crypto accelerators,
7355 and starts the groundwork for gathering stats safely at relays.
7358 - Start the process of disabling ".exit" address notation, since it
7359 can be used for a variety of esoteric application-level attacks
7360 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
7363 o New directory authorities:
7364 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
7368 - New AccelName and AccelDir options add support for dynamic OpenSSL
7369 hardware crypto acceleration engines.
7370 - Tor now supports tunneling all of its outgoing connections over
7371 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
7372 configuration options. Code by Christopher Davis.
7375 - Send circuit or stream sendme cells when our window has decreased
7376 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
7377 by Karsten when testing the "reduce circuit window" performance
7378 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7379 before the release of Tor 0.0.0. This is the new winner of the
7382 o New options for gathering stats safely:
7383 - Directory mirrors that set "DirReqStatistics 1" write statistics
7384 about directory requests to disk every 24 hours. As compared to the
7385 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
7386 1) stats are written to disk exactly every 24 hours; 2) estimated
7387 shares of v2 and v3 requests are determined as mean values, not at
7388 the end of a measurement period; 3) unresolved requests are listed
7389 with country code '??'; 4) directories also measure download times.
7390 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
7391 number of exit streams and transferred bytes per port to disk every
7393 - Relays that set "CellStatistics 1" write statistics on how long
7394 cells spend in their circuit queues to disk every 24 hours.
7395 - Entry nodes that set "EntryStatistics 1" write statistics on the
7396 rough number and origins of connecting clients to disk every 24
7398 - Relays that write any of the above statistics to disk and set
7399 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
7400 their extra-info documents.
7403 - New --digests command-line switch to output the digests of the
7404 source files Tor was built with.
7405 - The "torify" script now uses torsocks where available.
7406 - The memarea code now uses a sentinel value at the end of each area
7407 to make sure nothing writes beyond the end of an area. This might
7408 help debug some conceivable causes of bug 930.
7409 - Time and memory units in the configuration file can now be set to
7410 fractional units. For example, "2.5 GB" is now a valid value for
7412 - Certain Tor clients (such as those behind check.torproject.org) may
7413 want to fetch the consensus in an extra early manner. To enable this
7414 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
7415 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
7416 as only certain clients who must have this information sooner should
7418 - Instead of adding the svn revision to the Tor version string, report
7419 the git commit (when we're building from a git checkout).
7422 - If any of the v3 certs we download are unparseable, we should
7423 actually notice the failure so we don't retry indefinitely. Bugfix
7424 on 0.2.0.x; reported by "rotator".
7425 - If the cached cert file is unparseable, warn but don't exit.
7426 - Fix possible segmentation fault on directory authorities. Bugfix on
7428 - When Tor fails to parse a descriptor of any kind, dump it to disk.
7429 Might help diagnosing bug 1051.
7431 o Deprecated and removed features:
7432 - The controller no longer accepts the old obsolete "addr-mappings/"
7433 or "unregistered-servers-" GETINFO values.
7434 - Hidden services no longer publish version 0 descriptors, and clients
7435 do not request or use version 0 descriptors. However, the old hidden
7436 service authorities still accept and serve version 0 descriptors
7437 when contacted by older hidden services/clients.
7438 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
7439 always on; using them is necessary for correct forward-compatible
7441 - Remove support for .noconnect style addresses. Nobody was using
7442 them, and they provided another avenue for detecting Tor users
7443 via application-level web tricks.
7445 o Packaging changes:
7446 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
7447 installer bundles. See
7448 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
7449 for details of what's new in Vidalia 0.2.3.
7450 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
7451 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
7452 configuration file, rather than the old Privoxy.
7453 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
7454 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
7455 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
7456 better compatibility with OS X 10.6, aka Snow Leopard.
7457 - OS X Vidalia Bundle: The multi-package installer is now replaced
7458 by a simple drag and drop to the /Applications folder. This change
7459 occurred with the upgrade to Vidalia 0.2.3.
7462 Changes in version 0.2.1.19 - 2009-07-28
7463 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
7464 services on Tor 0.2.1.3-alpha through 0.2.1.18.
7467 - Make accessing hidden services on 0.2.1.x work right again.
7468 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
7469 part of patch provided by "optimist".
7472 - When a relay/bridge is writing out its identity key fingerprint to
7473 the "fingerprint" file and to its logs, write it without spaces. Now
7474 it will look like the fingerprints in our bridges documentation,
7475 and confuse fewer users.
7478 - Relays no longer publish a new server descriptor if they change
7479 their MaxAdvertisedBandwidth config option but it doesn't end up
7480 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
7481 fixes bug 1026. Patch from Sebastian.
7482 - Avoid leaking memory every time we get a create cell but we have
7483 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
7484 fixes bug 1034. Reported by BarkerJr.
7487 Changes in version 0.2.1.18 - 2009-07-24
7488 Tor 0.2.1.18 lays the foundations for performance improvements,
7489 adds status events to help users diagnose bootstrap problems, adds
7490 optional authentication/authorization for hidden services, fixes a
7491 variety of potential anonymity problems, and includes a huge pile of
7492 other features and bug fixes.
7495 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
7498 Changes in version 0.2.1.17-rc - 2009-07-07
7499 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
7500 candidate for the 0.2.1.x series. It lays the groundwork for further
7501 client performance improvements, and also fixes a big bug with directory
7502 authorities that were causing them to assign Guard and Stable flags
7505 The Windows bundles also finally include the geoip database that we
7506 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
7507 should actually install Torbutton rather than giving you a cryptic
7508 failure message (oops).
7511 - Clients now use the bandwidth values in the consensus, rather than
7512 the bandwidth values in each relay descriptor. This approach opens
7513 the door to more accurate bandwidth estimates once the directory
7514 authorities start doing active measurements. Implements more of
7518 - When Tor clients restart after 1-5 days, they discard all their
7519 cached descriptors as too old, but they still use the cached
7520 consensus document. This approach is good for robustness, but
7521 bad for performance: since they don't know any bandwidths, they
7522 end up choosing at random rather than weighting their choice by
7523 speed. Fixed by the above feature of putting bandwidths in the
7524 consensus. Bugfix on 0.2.0.x.
7525 - Directory authorities were neglecting to mark relays down in their
7526 internal histories if the relays fall off the routerlist without
7527 ever being found unreachable. So there were relays in the histories
7528 that haven't been seen for eight months, and are listed as being
7529 up for eight months. This wreaked havoc on the "median wfu"
7530 and "median mtbf" calculations, in turn making Guard and Stable
7531 flags very wrong, hurting network performance. Fixes bugs 696 and
7532 969. Bugfix on 0.2.0.6-alpha.
7535 - Serve the DirPortFrontPage page even when we have been approaching
7536 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
7537 - The control port would close the connection before flushing long
7538 replies, such as the network consensus, if a QUIT command was issued
7539 before the reply had completed. Now, the control port flushes all
7540 pending replies before closing the connection. Also fixed a spurious
7541 warning when a QUIT command is issued after a malformed or rejected
7542 AUTHENTICATE command, but before the connection was closed. Patch
7543 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
7544 - When we can't find an intro key for a v2 hidden service descriptor,
7545 fall back to the v0 hidden service descriptor and log a bug message.
7546 Workaround for bug 1024.
7547 - Fix a log message that did not respect the SafeLogging option.
7551 - If we're a relay and we change our IP address, be more verbose
7552 about the reason that made us change. Should help track down
7553 further bugs for relays on dynamic IP addresses.
7556 Changes in version 0.2.0.35 - 2009-06-24
7558 - Avoid crashing in the presence of certain malformed descriptors.
7559 Found by lark, and by automated fuzzing.
7560 - Fix an edge case where a malicious exit relay could convince a
7561 controller that the client's DNS question resolves to an internal IP
7562 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7565 - Finally fix the bug where dynamic-IP relays disappear when their
7566 IP address changes: directory mirrors were mistakenly telling
7567 them their old address if they asked via begin_dir, so they
7568 never got an accurate answer about their new address, so they
7569 just vanished after a day. For belt-and-suspenders, relays that
7570 don't set Address in their config now avoid using begin_dir for
7571 all direct connections. Should fix bugs 827, 883, and 900.
7572 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7573 that would occur on some exit nodes when DNS failures and timeouts
7574 occurred in certain patterns. Fix for bug 957.
7577 - When starting with a cache over a few days old, do not leak
7578 memory for the obsolete router descriptors in it. Bugfix on
7579 0.2.0.33; fixes bug 672.
7580 - Hidden service clients didn't use a cached service descriptor that
7581 was older than 15 minutes, but wouldn't fetch a new one either,
7582 because there was already one in the cache. Now, fetch a v2
7583 descriptor unless the same descriptor was added to the cache within
7584 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7587 Changes in version 0.2.1.16-rc - 2009-06-20
7588 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
7589 a bunch of minor bugs.
7592 - Fix an edge case where a malicious exit relay could convince a
7593 controller that the client's DNS question resolves to an internal IP
7594 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7596 o Major performance improvements (on 0.2.0.x):
7597 - Disable and refactor some debugging checks that forced a linear scan
7598 over the whole server-side DNS cache. These accounted for over 50%
7599 of CPU time on a relatively busy exit node's gprof profile. Found
7601 - Disable some debugging checks that appeared in exit node profile
7605 - Update to the "June 3 2009" ip-to-country file.
7606 - Do not have tor-resolve automatically refuse all .onion addresses;
7607 if AutomapHostsOnResolve is set in your torrc, this will work fine.
7609 o Minor bugfixes (on 0.2.0.x):
7610 - Log correct error messages for DNS-related network errors on
7612 - Fix a race condition that could cause crashes or memory corruption
7613 when running as a server with a controller listening for log
7615 - Avoid crashing when we have a policy specified in a DirPolicy or
7616 SocksPolicy or ReachableAddresses option with ports set on it,
7617 and we re-load the policy. May fix bug 996.
7618 - Hidden service clients didn't use a cached service descriptor that
7619 was older than 15 minutes, but wouldn't fetch a new one either,
7620 because there was already one in the cache. Now, fetch a v2
7621 descriptor unless the same descriptor was added to the cache within
7622 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7624 o Minor bugfixes (on 0.2.1.x):
7625 - Don't warn users about low port and hibernation mix when they
7626 provide a *ListenAddress directive to fix that. Bugfix on
7628 - When switching back and forth between bridge mode, do not start
7629 gathering GeoIP data until two hours have passed.
7630 - Do not complain that the user has requested an excluded node as
7631 an exit when the node is not really an exit. This could happen
7632 because the circuit was for testing, or an introduction point.
7636 Changes in version 0.2.1.15-rc - 2009-05-25
7637 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
7638 series. It fixes a major bug on fast exit relays, as well as a variety
7641 o Major bugfixes (on 0.2.0.x):
7642 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7643 that would occur on some exit nodes when DNS failures and timeouts
7644 occurred in certain patterns. Fix for bug 957.
7646 o Minor bugfixes (on 0.2.0.x):
7647 - Actually return -1 in the error case for read_bandwidth_usage().
7648 Harmless bug, since we currently don't care about the return value
7649 anywhere. Bugfix on 0.2.0.9-alpha.
7650 - Provide a more useful log message if bug 977 (related to buffer
7651 freelists) ever reappears, and do not crash right away.
7652 - Fix an assertion failure on 64-bit platforms when we allocated
7653 memory right up to the end of a memarea, then realigned the memory
7654 one step beyond the end. Fixes a possible cause of bug 930.
7655 - Protect the count of open sockets with a mutex, so we can't
7656 corrupt it when two threads are closing or opening sockets at once.
7657 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
7658 - Don't allow a bridge to publish its router descriptor to a
7659 non-bridge directory authority. Fixes part of bug 932.
7660 - When we change to or from being a bridge, reset our counts of
7661 client usage by country. Fixes bug 932.
7662 - Fix a bug that made stream bandwidth get misreported to the
7664 - Stop using malloc_usable_size() to use more area than we had
7665 actually allocated: it was safe, but made valgrind really unhappy.
7666 - Fix a memory leak when v3 directory authorities load their keys
7667 and cert from disk. Bugfix on 0.2.0.1-alpha.
7669 o Minor bugfixes (on 0.2.1.x):
7670 - Fix use of freed memory when deciding to mark a non-addable
7671 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
7674 Changes in version 0.2.1.14-rc - 2009-04-12
7675 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
7676 series. It begins fixing some major performance problems, and also
7677 finally addresses the bug that was causing relays on dynamic IP
7678 addresses to fall out of the directory.
7681 - Clients replace entry guards that were chosen more than a few months
7682 ago. This change should significantly improve client performance,
7683 especially once more people upgrade, since relays that have been
7684 a guard for a long time are currently overloaded.
7686 o Major bugfixes (on 0.2.0):
7687 - Finally fix the bug where dynamic-IP relays disappear when their
7688 IP address changes: directory mirrors were mistakenly telling
7689 them their old address if they asked via begin_dir, so they
7690 never got an accurate answer about their new address, so they
7691 just vanished after a day. For belt-and-suspenders, relays that
7692 don't set Address in their config now avoid using begin_dir for
7693 all direct connections. Should fix bugs 827, 883, and 900.
7694 - Relays were falling out of the networkstatus consensus for
7695 part of a day if they changed their local config but the
7696 authorities discarded their new descriptor as "not sufficiently
7697 different". Now directory authorities accept a descriptor as changed
7698 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
7700 - Avoid crashing in the presence of certain malformed descriptors.
7701 Found by lark, and by automated fuzzing.
7704 - When generating circuit events with verbose nicknames for
7705 controllers, try harder to look up nicknames for routers on a
7706 circuit. (Previously, we would look in the router descriptors we had
7707 for nicknames, but not in the consensus.) Partial fix for bug 941.
7708 - If the bridge config line doesn't specify a port, assume 443.
7709 This makes bridge lines a bit smaller and easier for users to
7711 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
7712 bytes (aka 20KB/s), to match our documentation. Also update
7713 directory authorities so they always assign the Fast flag to relays
7714 with 20KB/s of capacity. Now people running relays won't suddenly
7715 find themselves not seeing any use, if the network gets faster
7717 - Update to the "April 3 2009" ip-to-country file.
7720 - Avoid trying to print raw memory to the logs when we decide to
7721 give up on downloading a given relay descriptor. Bugfix on
7723 - In tor-resolve, when the Tor client to use is specified by
7724 <hostname>:<port>, actually use the specified port rather than
7725 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
7726 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
7727 - When starting with a cache over a few days old, do not leak
7728 memory for the obsolete router descriptors in it. Bugfix on
7730 - Avoid double-free on list of successfully uploaded hidden
7731 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
7732 - Change memarea_strndup() implementation to work even when
7733 duplicating a string at the end of a page. This bug was
7734 harmless for now, but could have meant crashes later. Fix by
7735 lark. Bugfix on 0.2.1.1-alpha.
7736 - Limit uploaded directory documents to be 16M rather than 500K.
7737 The directory authorities were refusing v3 consensus votes from
7738 other authorities, since the votes are now 504K. Fixes bug 959;
7739 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
7740 - Directory authorities should never send a 503 "busy" response to
7741 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
7745 Changes in version 0.2.1.13-alpha - 2009-03-09
7746 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
7747 cleanups. We're finally getting close to a release candidate.
7750 - Correctly update the list of which countries we exclude as
7751 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
7752 lark. Bugfix on 0.2.1.6-alpha.
7754 o Minor bugfixes (on 0.2.0.x and earlier):
7755 - Automatically detect MacOSX versions earlier than 10.4.0, and
7756 disable kqueue from inside Tor when running with these versions.
7757 We previously did this from the startup script, but that was no
7758 help to people who didn't use the startup script. Resolves bug 863.
7759 - When we had picked an exit node for a connection, but marked it as
7760 "optional", and it turned out we had no onion key for the exit,
7761 stop wanting that exit and try again. This situation may not
7762 be possible now, but will probably become feasible with proposal
7763 158. Spotted by rovv. Fixes another case of bug 752.
7764 - Clients no longer cache certificates for authorities they do not
7765 recognize. Bugfix on 0.2.0.9-alpha.
7766 - When we can't transmit a DNS request due to a network error, retry
7767 it after a while, and eventually transmit a failing response to
7768 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
7769 - If the controller claimed responsibility for a stream, but that
7770 stream never finished making its connection, it would live
7771 forever in circuit_wait state. Now we close it after SocksTimeout
7772 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
7773 - Drop begin cells to a hidden service if they come from the middle
7774 of a circuit. Patch from lark.
7775 - When we erroneously receive two EXTEND cells for the same circuit
7776 ID on the same connection, drop the second. Patch from lark.
7777 - Fix a crash that occurs on exit nodes when a nameserver request
7778 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
7779 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
7781 - Do not assume that a stack-allocated character array will be
7782 64-bit aligned on platforms that demand that uint64_t access is
7783 aligned. Possible fix for bug 604.
7784 - Parse dates and IPv4 addresses in a locale- and libc-independent
7785 manner, to avoid platform-dependent behavior on malformed input.
7786 - Build correctly when configured to build outside the main source
7787 path. Patch from Michael Gold.
7788 - We were already rejecting relay begin cells with destination port
7789 of 0. Now also reject extend cells with destination port or address
7790 of 0. Suggested by lark.
7792 o Minor bugfixes (on 0.2.1.x):
7793 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
7794 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
7795 - If we're an exit node, scrub the IP address to which we are exiting
7796 in the logs. Bugfix on 0.2.1.8-alpha.
7799 - On Linux, use the prctl call to re-enable core dumps when the user
7801 - New controller event NEWCONSENSUS that lists the networkstatus
7802 lines for every recommended relay. Now controllers like Torflow
7803 can keep up-to-date on which relays they should be using.
7804 - Update to the "February 26 2009" ip-to-country file.
7807 Changes in version 0.2.0.34 - 2009-02-08
7808 Tor 0.2.0.34 features several more security-related fixes. You should
7809 upgrade, especially if you run an exit relay (remote crash) or a
7810 directory authority (remote infinite loop), or you're on an older
7811 (pre-XP) or not-recently-patched Windows (remote exploit).
7813 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
7814 have many known flaws, and nobody should be using them. You should
7815 upgrade. If you're using a Linux or BSD and its packages are obsolete,
7816 stop using those packages and upgrade anyway.
7819 - Fix an infinite-loop bug on handling corrupt votes under certain
7820 circumstances. Bugfix on 0.2.0.8-alpha.
7821 - Fix a temporary DoS vulnerability that could be performed by
7822 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7823 - Avoid a potential crash on exit nodes when processing malformed
7824 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
7825 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
7826 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
7829 - Fix compilation on systems where time_t is a 64-bit integer.
7830 Patch from Matthias Drochner.
7831 - Don't consider expiring already-closed client connections. Fixes
7832 bug 893. Bugfix on 0.0.2pre20.
7835 Changes in version 0.2.1.12-alpha - 2009-02-08
7836 Tor 0.2.1.12-alpha features several more security-related fixes. You
7837 should upgrade, especially if you run an exit relay (remote crash) or
7838 a directory authority (remote infinite loop), or you're on an older
7839 (pre-XP) or not-recently-patched Windows (remote exploit). It also
7840 includes a big pile of minor bugfixes and cleanups.
7843 - Fix an infinite-loop bug on handling corrupt votes under certain
7844 circumstances. Bugfix on 0.2.0.8-alpha.
7845 - Fix a temporary DoS vulnerability that could be performed by
7846 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7847 - Avoid a potential crash on exit nodes when processing malformed
7848 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
7851 - Let controllers actually ask for the "clients_seen" event for
7852 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
7853 reported by Matt Edman.
7854 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
7856 - Fix a bug in address parsing that was preventing bridges or hidden
7857 service targets from being at IPv6 addresses.
7858 - Solve a bug that kept hardware crypto acceleration from getting
7859 enabled when accounting was turned on. Fixes bug 907. Bugfix on
7861 - Remove a bash-ism from configure.in to build properly on non-Linux
7862 platforms. Bugfix on 0.2.1.1-alpha.
7863 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
7864 headers. Bugfix on 0.2.0.10-alpha.
7865 - Don't consider expiring already-closed client connections. Fixes
7866 bug 893. Bugfix on 0.0.2pre20.
7867 - Fix another interesting corner-case of bug 891 spotted by rovv:
7868 Previously, if two hosts had different amounts of clock drift, and
7869 one of them created a new connection with just the wrong timing,
7870 the other might decide to deprecate the new connection erroneously.
7871 Bugfix on 0.1.1.13-alpha.
7872 - Resolve a very rare crash bug that could occur when the user forced
7873 a nameserver reconfiguration during the middle of a nameserver
7874 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
7875 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
7876 Bugfix on 0.2.1.7-alpha.
7877 - If we're using bridges and our network goes away, be more willing
7878 to forgive our bridges and try again when we get an application
7879 request. Bugfix on 0.2.0.x.
7882 - Support platforms where time_t is 64 bits long. (Congratulations,
7883 NetBSD!) Patch from Matthias Drochner.
7884 - Add a 'getinfo status/clients-seen' controller command, in case
7885 controllers want to hear clients_seen events but connect late.
7888 - Disable GCC's strict alias optimization by default, to avoid the
7889 likelihood of its introducing subtle bugs whenever our code violates
7890 the letter of C99's alias rules.
7893 Changes in version 0.2.0.33 - 2009-01-21
7894 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
7895 useful to users. It also finally fixes a bug where a relay or client
7896 that's been off for many days would take a long time to bootstrap.
7898 This update also fixes an important security-related bug reported by
7899 Ilja van Sprundel. You should upgrade. (We'll send out more details
7900 about the bug once people have had some time to upgrade.)
7903 - Fix a heap-corruption bug that may be remotely triggerable on
7904 some platforms. Reported by Ilja van Sprundel.
7907 - When a stream at an exit relay is in state "resolving" or
7908 "connecting" and it receives an "end" relay cell, the exit relay
7909 would silently ignore the end cell and not close the stream. If
7910 the client never closes the circuit, then the exit relay never
7911 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
7913 - When sending CREATED cells back for a given circuit, use a 64-bit
7914 connection ID to find the right connection, rather than an addr:port
7915 combination. Now that we can have multiple OR connections between
7916 the same ORs, it is no longer possible to use addr:port to uniquely
7917 identify a connection.
7918 - Bridge relays that had DirPort set to 0 would stop fetching
7919 descriptors shortly after startup, and then briefly resume
7920 after a new bandwidth test and/or after publishing a new bridge
7921 descriptor. Bridge users that try to bootstrap from them would
7922 get a recent networkstatus but would get descriptors from up to
7923 18 hours earlier, meaning most of the descriptors were obsolete
7924 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
7925 - Prevent bridge relays from serving their 'extrainfo' document
7926 to anybody who asks, now that extrainfo docs include potentially
7927 sensitive aggregated client geoip summaries. Bugfix on
7929 - If the cached networkstatus consensus is more than five days old,
7930 discard it rather than trying to use it. In theory it could be
7931 useful because it lists alternate directory mirrors, but in practice
7932 it just means we spend many minutes trying directory mirrors that
7933 are long gone from the network. Also discard router descriptors as
7934 we load them if they are more than five days old, since the onion
7935 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
7938 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
7939 could make gcc generate non-functional binary search code. Bugfix
7941 - Build correctly on platforms without socklen_t.
7942 - Compile without warnings on solaris.
7943 - Avoid potential crash on internal error during signature collection.
7944 Fixes bug 864. Patch from rovv.
7945 - Correct handling of possible malformed authority signing key
7946 certificates with internal signature types. Fixes bug 880.
7947 Bugfix on 0.2.0.3-alpha.
7948 - Fix a hard-to-trigger resource leak when logging credential status.
7950 - When we can't initialize DNS because the network is down, do not
7951 automatically stop Tor from starting. Instead, we retry failed
7952 dns_init() every 10 minutes, and change the exit policy to reject
7953 *:* until one succeeds. Fixes bug 691.
7954 - Use 64 bits instead of 32 bits for connection identifiers used with
7955 the controller protocol, to greatly reduce risk of identifier reuse.
7956 - When we're choosing an exit node for a circuit, and we have
7957 no pending streams, choose a good general exit rather than one that
7958 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
7959 - Fix another case of assuming, when a specific exit is requested,
7960 that we know more than the user about what hosts it allows.
7961 Fixes one case of bug 752. Patch from rovv.
7962 - Clip the MaxCircuitDirtiness config option to a minimum of 10
7963 seconds. Warn the user if lower values are given in the
7964 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
7965 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
7966 user if lower values are given in the configuration. Bugfix on
7967 0.1.1.17-rc. Patch by Sebastian.
7968 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
7969 the cache because we already had a v0 descriptor with the same ID.
7970 Bugfix on 0.2.0.18-alpha.
7971 - Fix a race condition when freeing keys shared between main thread
7972 and CPU workers that could result in a memory leak. Bugfix on
7973 0.1.0.1-rc. Fixes bug 889.
7974 - Send a valid END cell back when a client tries to connect to a
7975 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
7976 840. Patch from rovv.
7977 - Check which hops rendezvous stream cells are associated with to
7978 prevent possible guess-the-streamid injection attacks from
7979 intermediate hops. Fixes another case of bug 446. Based on patch
7981 - If a broken client asks a non-exit router to connect somewhere,
7982 do not even do the DNS lookup before rejecting the connection.
7983 Fixes another case of bug 619. Patch from rovv.
7984 - When a relay gets a create cell it can't decrypt (e.g. because it's
7985 using the wrong onion key), we were dropping it and letting the
7986 client time out. Now actually answer with a destroy cell. Fixes
7987 bug 904. Bugfix on 0.0.2pre8.
7989 o Minor bugfixes (hidden services):
7990 - Do not throw away existing introduction points on SIGHUP. Bugfix on
7991 0.0.6pre1. Patch by Karsten. Fixes bug 874.
7994 - Report the case where all signatures in a detached set are rejected
7995 differently than the case where there is an error handling the
7997 - When we realize that another process has modified our cached
7998 descriptors, print out a more useful error message rather than
7999 triggering an assertion. Fixes bug 885. Patch from Karsten.
8000 - Implement the 0x20 hack to better resist DNS poisoning: set the
8001 case on outgoing DNS requests randomly, and reject responses that do
8002 not match the case correctly. This logic can be disabled with the
8003 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
8004 of servers that do not reliably preserve case in replies. See
8005 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
8007 - Check DNS replies for more matching fields to better resist DNS
8009 - Never use OpenSSL compression: it wastes RAM and CPU trying to
8010 compress cells, which are basically all encrypted, compressed, or
8014 Changes in version 0.2.1.11-alpha - 2009-01-20
8015 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
8016 week it will take a long time to bootstrap again" bug. It also fixes
8017 an important security-related bug reported by Ilja van Sprundel. You
8018 should upgrade. (We'll send out more details about the bug once people
8019 have had some time to upgrade.)
8022 - Fix a heap-corruption bug that may be remotely triggerable on
8023 some platforms. Reported by Ilja van Sprundel.
8026 - Discard router descriptors as we load them if they are more than
8027 five days old. Otherwise if Tor is off for a long time and then
8028 starts with cached descriptors, it will try to use the onion
8029 keys in those obsolete descriptors when building circuits. Bugfix
8030 on 0.2.0.x. Fixes bug 887.
8033 - Try to make sure that the version of Libevent we're running with
8034 is binary-compatible with the one we built with. May address bug
8036 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
8037 for bug 905. Bugfix on 0.2.1.7-alpha.
8038 - Add a new --enable-local-appdata configuration switch to change
8039 the default location of the datadir on win32 from APPDATA to
8040 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
8041 entirely. Patch from coderman.
8044 - Make outbound DNS packets respect the OutboundBindAddress setting.
8045 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
8046 - When our circuit fails at the first hop (e.g. we get a destroy
8047 cell back), avoid using that OR connection anymore, and also
8048 tell all the one-hop directory requests waiting for it that they
8049 should fail. Bugfix on 0.2.1.3-alpha.
8050 - In the torify(1) manpage, mention that tsocks will leak your
8054 Changes in version 0.2.1.10-alpha - 2009-01-06
8055 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
8056 would make the bridge relay not so useful if it had DirPort set to 0,
8057 and one that could let an attacker learn a little bit of information
8058 about the bridge's users), and a bug that would cause your Tor relay
8059 to ignore a circuit create request it can't decrypt (rather than reply
8060 with an error). It also fixes a wide variety of other bugs.
8063 - If the cached networkstatus consensus is more than five days old,
8064 discard it rather than trying to use it. In theory it could
8065 be useful because it lists alternate directory mirrors, but in
8066 practice it just means we spend many minutes trying directory
8067 mirrors that are long gone from the network. Helps bug 887 a bit;
8069 - Bridge relays that had DirPort set to 0 would stop fetching
8070 descriptors shortly after startup, and then briefly resume
8071 after a new bandwidth test and/or after publishing a new bridge
8072 descriptor. Bridge users that try to bootstrap from them would
8073 get a recent networkstatus but would get descriptors from up to
8074 18 hours earlier, meaning most of the descriptors were obsolete
8075 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
8076 - Prevent bridge relays from serving their 'extrainfo' document
8077 to anybody who asks, now that extrainfo docs include potentially
8078 sensitive aggregated client geoip summaries. Bugfix on
8082 - New controller event "clients_seen" to report a geoip-based summary
8083 of which countries we've seen clients from recently. Now controllers
8084 like Vidalia can show bridge operators that they're actually making
8086 - Build correctly against versions of OpenSSL 0.9.8 or later built
8087 without support for deprecated functions.
8088 - Update to the "December 19 2008" ip-to-country file.
8090 o Minor bugfixes (on 0.2.0.x):
8091 - Authorities now vote for the Stable flag for any router whose
8092 weighted MTBF is at least 5 days, regardless of the mean MTBF.
8093 - Do not remove routers as too old if we do not have any consensus
8094 document. Bugfix on 0.2.0.7-alpha.
8095 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
8096 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
8097 - When an exit relay resolves a stream address to a local IP address,
8098 do not just keep retrying that same exit relay over and
8099 over. Instead, just close the stream. Addresses bug 872. Bugfix
8100 on 0.2.0.32. Patch from rovv.
8101 - If a hidden service sends us an END cell, do not consider
8102 retrying the connection; just close it. Patch from rovv.
8103 - When we made bridge authorities stop serving bridge descriptors over
8104 unencrypted links, we also broke DirPort reachability testing for
8105 bridges. So bridges with a non-zero DirPort were printing spurious
8106 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
8107 - When a relay gets a create cell it can't decrypt (e.g. because it's
8108 using the wrong onion key), we were dropping it and letting the
8109 client time out. Now actually answer with a destroy cell. Fixes
8110 bug 904. Bugfix on 0.0.2pre8.
8111 - Squeeze 2-5% out of client performance (according to oprofile) by
8112 improving the implementation of some policy-manipulation functions.
8114 o Minor bugfixes (on 0.2.1.x):
8115 - Make get_interface_address() function work properly again; stop
8116 guessing the wrong parts of our address as our address.
8117 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
8118 send on that circuit. Otherwise we might violate the proposal-110
8119 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
8121 - When we're sending non-EXTEND cells to the first hop in a circuit,
8122 for example to use an encrypted directory connection, we don't need
8123 to use RELAY_EARLY cells: the first hop knows what kind of cell
8124 it is, and nobody else can even see the cell type. Conserving
8125 RELAY_EARLY cells makes it easier to cannibalize circuits like
8127 - Stop logging nameserver addresses in reverse order.
8128 - If we are retrying a directory download slowly over and over, do
8129 not automatically give up after the 254th failure. Bugfix on
8131 - Resume reporting accurate "stream end" reasons to the local control
8132 port. They were lost in the changes for Proposal 148. Bugfix on
8135 o Deprecated and removed features:
8136 - The old "tor --version --version" command, which would print out
8137 the subversion "Id" of most of the source files, is now removed. It
8138 turned out to be less useful than we'd expected, and harder to
8141 o Code simplifications and refactoring:
8142 - Change our header file guard macros to be less likely to conflict
8143 with system headers. Adam Langley noticed that we were conflicting
8144 with log.h on Android.
8145 - Tool-assisted documentation cleanup. Nearly every function or
8146 static variable in Tor should have its own documentation now.
8149 Changes in version 0.2.1.9-alpha - 2008-12-25
8150 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
8152 o New directory authorities:
8153 - gabelmoo (the authority run by Karsten Loesing) now has a new
8157 - Never use a connection with a mismatched address to extend a
8158 circuit, unless that connection is canonical. A canonical
8159 connection is one whose address is authenticated by the router's
8160 identity key, either in a NETINFO cell or in a router descriptor.
8161 - Avoid a possible memory corruption bug when receiving hidden service
8162 descriptors. Bugfix on 0.2.1.6-alpha.
8165 - Fix a logic error that would automatically reject all but the first
8166 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
8167 part of bug 813/868. Bug spotted by coderman.
8168 - When a stream at an exit relay is in state "resolving" or
8169 "connecting" and it receives an "end" relay cell, the exit relay
8170 would silently ignore the end cell and not close the stream. If
8171 the client never closes the circuit, then the exit relay never
8172 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
8174 - When we can't initialize DNS because the network is down, do not
8175 automatically stop Tor from starting. Instead, retry failed
8176 dns_init() every 10 minutes, and change the exit policy to reject
8177 *:* until one succeeds. Fixes bug 691.
8180 - Give a better error message when an overzealous init script says
8181 "sudo -u username tor --user username". Makes Bug 882 easier for
8183 - When a directory authority gives us a new guess for our IP address,
8184 log which authority we used. Hopefully this will help us debug
8185 the recent complaints about bad IP address guesses.
8186 - Detect svn revision properly when we're using git-svn.
8187 - Try not to open more than one descriptor-downloading connection
8188 to an authority at once. This should reduce load on directory
8189 authorities. Fixes bug 366.
8190 - Add cross-certification to newly generated certificates, so that
8191 a signing key is enough information to look up a certificate.
8192 Partial implementation of proposal 157.
8193 - Start serving certificates by <identity digest, signing key digest>
8194 pairs. Partial implementation of proposal 157.
8195 - Clients now never report any stream end reason except 'MISC'.
8196 Implements proposal 148.
8197 - On platforms with a maximum syslog string length, truncate syslog
8198 messages to that length ourselves, rather than relying on the
8199 system to do it for us.
8200 - Optimize out calls to time(NULL) that occur for every IO operation,
8201 or for every cell. On systems where time() is a slow syscall,
8202 this fix will be slightly helpful.
8203 - Exit servers can now answer resolve requests for ip6.arpa addresses.
8204 - When we download a descriptor that we then immediately (as
8205 a directory authority) reject, do not retry downloading it right
8206 away. Should save some bandwidth on authorities. Fix for bug
8207 888. Patch by Sebastian Hahn.
8208 - When a download gets us zero good descriptors, do not notify
8209 Tor that new directory information has arrived.
8210 - Avoid some nasty corner cases in the logic for marking connections
8211 as too old or obsolete or noncanonical for circuits. Partial
8214 o Minor features (controller):
8215 - New CONSENSUS_ARRIVED event to note when a new consensus has
8216 been fetched and validated.
8217 - When we realize that another process has modified our cached
8218 descriptors file, print out a more useful error message rather
8219 than triggering an assertion. Fixes bug 885. Patch from Karsten.
8220 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
8221 controllers to prevent SIGHUP from reloading the
8222 configuration. Fixes bug 856.
8225 - Resume using the correct "REASON=" stream when telling the
8226 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
8227 - When a canonical connection appears later in our internal list
8228 than a noncanonical one for a given OR ID, always use the
8229 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
8231 - Clip the MaxCircuitDirtiness config option to a minimum of 10
8232 seconds. Warn the user if lower values are given in the
8233 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
8234 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
8235 user if lower values are given in the configuration. Bugfix on
8236 0.1.1.17-rc. Patch by Sebastian.
8237 - Fix a race condition when freeing keys shared between main thread
8238 and CPU workers that could result in a memory leak. Bugfix on
8239 0.1.0.1-rc. Fixes bug 889.
8241 o Minor bugfixes (hidden services):
8242 - Do not throw away existing introduction points on SIGHUP (bugfix on
8243 0.0.6pre1); also, do not stall hidden services because we're
8244 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
8245 by John Brooks. Patch by Karsten. Fixes bug 874.
8246 - Fix a memory leak when we decline to add a v2 rendezvous
8247 descriptor to the cache because we already had a v0 descriptor
8248 with the same ID. Bugfix on 0.2.0.18-alpha.
8250 o Deprecated and removed features:
8251 - RedirectExits has been removed. It was deprecated since
8253 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
8254 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
8255 - Cell pools are now always enabled; --disable-cell-pools is ignored.
8257 o Code simplifications and refactoring:
8258 - Rename the confusing or_is_obsolete field to the more appropriate
8259 is_bad_for_new_circs, and move it to or_connection_t where it
8261 - Move edge-only flags from connection_t to edge_connection_t: not
8262 only is this better coding, but on machines of plausible alignment,
8263 it should save 4-8 bytes per connection_t. "Every little bit helps."
8264 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
8265 for consistency; keep old option working for backward compatibility.
8266 - Simplify the code for finding connections to use for a circuit.
8269 Changes in version 0.2.1.8-alpha - 2008-12-08
8270 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
8271 builds better on unusual platforms like Solaris and old OS X, and
8272 fixes a variety of other issues.
8275 - New DirPortFrontPage option that takes an html file and publishes
8276 it as "/" on the DirPort. Now relay operators can provide a
8277 disclaimer without needing to set up a separate webserver. There's
8278 a sample disclaimer in contrib/tor-exit-notice.html.
8281 - When the client is choosing entry guards, now it selects at most
8282 one guard from a given relay family. Otherwise we could end up with
8283 all of our entry points into the network run by the same operator.
8284 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
8287 - Fix a DOS opportunity during the voting signature collection process
8288 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8289 - Fix a possible segfault when establishing an exit connection. Bugfix
8293 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
8295 - Made Tor a little less aggressive about deleting expired
8296 certificates. Partial fix for bug 854.
8297 - Stop doing unaligned memory access that generated bus errors on
8298 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
8299 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
8300 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
8301 - Make USR2 log-level switch take effect immediately. Bugfix on
8303 - If one win32 nameserver fails to get added, continue adding the
8304 rest, and don't automatically fail.
8305 - Use fcntl() for locking when flock() is not available. Should fix
8306 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
8307 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
8308 could make gcc generate non-functional binary search code. Bugfix
8310 - Build correctly on platforms without socklen_t.
8311 - Avoid potential crash on internal error during signature collection.
8312 Fixes bug 864. Patch from rovv.
8313 - Do not use C's stdio library for writing to log files. This will
8314 improve logging performance by a minute amount, and will stop
8315 leaking fds when our disk is full. Fixes bug 861.
8316 - Stop erroneous use of O_APPEND in cases where we did not in fact
8317 want to re-seek to the end of a file before every last write().
8318 - Correct handling of possible malformed authority signing key
8319 certificates with internal signature types. Fixes bug 880. Bugfix
8321 - Fix a hard-to-trigger resource leak when logging credential status.
8325 - Directory mirrors no longer fetch the v1 directory or
8326 running-routers files. They are obsolete, and nobody asks for them
8327 anymore. This is the first step to making v1 authorities obsolete.
8329 o Minor features (controller):
8330 - Return circuit purposes in response to GETINFO circuit-status. Fixes
8334 Changes in version 0.2.0.32 - 2008-11-20
8335 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
8336 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8337 a smaller security flaw that might allow an attacker to access local
8338 services, further improves hidden service performance, and fixes a
8339 variety of other issues.
8342 - The "User" and "Group" config options did not clear the
8343 supplementary group entries for the Tor process. The "User" option
8344 is now more robust, and we now set the groups to the specified
8345 user's primary group. The "Group" option is now ignored. For more
8346 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8347 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8348 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
8349 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8350 consistently obeyed: if an exit relay refuses a stream because its
8351 exit policy doesn't allow it, we would remember what IP address
8352 the relay said the destination address resolves to, even if it's
8353 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8356 - Fix a DOS opportunity during the voting signature collection process
8357 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8359 o Major bugfixes (hidden services):
8360 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8361 we were failing the whole hidden service request when the v0
8362 descriptor fetch fails, even if the v2 fetch is still pending and
8363 might succeed. Similarly, if the last v2 fetch fails, we were
8364 failing the whole hidden service request even if a v0 fetch is
8365 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8366 - When extending a circuit to a hidden service directory to upload a
8367 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8368 requests failed, because the router descriptor has not been
8369 downloaded yet. In these cases, do not attempt to upload the
8370 rendezvous descriptor, but wait until the router descriptor is
8371 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
8372 descriptor from a hidden service directory for which the router
8373 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
8377 - Fix several infrequent memory leaks spotted by Coverity.
8378 - When testing for libevent functions, set the LDFLAGS variable
8379 correctly. Found by Riastradh.
8380 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8381 bootstrapping with tunneled directory connections. Bugfix on
8382 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8383 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8384 and we know that server B rejects most-but-not all connections to
8385 port 80, we would previously reject the connection. Now, we assume
8386 the user knows what they were asking for. Fixes bug 752. Bugfix
8387 on 0.0.9rc5. Diagnosed by BarkerJr.
8388 - If we overrun our per-second write limits a little, count this as
8389 having used up our write allocation for the second, and choke
8390 outgoing directory writes. Previously, we had only counted this when
8391 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
8392 Bugfix on 0.2.0.x (??).
8393 - Remove the old v2 directory authority 'lefkada' from the default
8394 list. It has been gone for many months.
8395 - Stop doing unaligned memory access that generated bus errors on
8396 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
8397 - Make USR2 log-level switch take effect immediately. Bugfix on
8400 o Minor bugfixes (controller):
8401 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
8402 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
8405 Changes in version 0.2.1.7-alpha - 2008-11-08
8406 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
8407 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8408 a smaller security flaw that might allow an attacker to access local
8409 services, adds better defense against DNS poisoning attacks on exit
8410 relays, further improves hidden service performance, and fixes a
8411 variety of other issues.
8414 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8415 consistently obeyed: if an exit relay refuses a stream because its
8416 exit policy doesn't allow it, we would remember what IP address
8417 the relay said the destination address resolves to, even if it's
8418 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8419 - The "User" and "Group" config options did not clear the
8420 supplementary group entries for the Tor process. The "User" option
8421 is now more robust, and we now set the groups to the specified
8422 user's primary group. The "Group" option is now ignored. For more
8423 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8424 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8425 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
8426 - Do not use or believe expired v3 authority certificates. Patch
8427 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
8430 - Now NodeFamily and MyFamily config options allow spaces in
8431 identity fingerprints, so it's easier to paste them in.
8432 Suggested by Lucky Green.
8433 - Implement the 0x20 hack to better resist DNS poisoning: set the
8434 case on outgoing DNS requests randomly, and reject responses that do
8435 not match the case correctly. This logic can be disabled with the
8436 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
8437 of servers that do not reliably preserve case in replies. See
8438 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
8440 - Preserve case in replies to DNSPort requests in order to support
8441 the 0x20 hack for resisting DNS poisoning attacks.
8443 o Hidden service performance improvements:
8444 - When the client launches an introduction circuit, retry with a
8445 new circuit after 30 seconds rather than 60 seconds.
8446 - Launch a second client-side introduction circuit in parallel
8447 after a delay of 15 seconds (based on work by Christian Wilms).
8448 - Hidden services start out building five intro circuits rather
8449 than three, and when the first three finish they publish a service
8450 descriptor using those. Now we publish our service descriptor much
8451 faster after restart.
8454 - Minor fix in the warning messages when you're having problems
8455 bootstrapping; also, be more forgiving of bootstrap problems when
8456 we're still making incremental progress on a given bootstrap phase.
8457 - When we're choosing an exit node for a circuit, and we have
8458 no pending streams, choose a good general exit rather than one that
8459 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
8460 - Send a valid END cell back when a client tries to connect to a
8461 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
8462 840. Patch from rovv.
8463 - If a broken client asks a non-exit router to connect somewhere,
8464 do not even do the DNS lookup before rejecting the connection.
8465 Fixes another case of bug 619. Patch from rovv.
8466 - Fix another case of assuming, when a specific exit is requested,
8467 that we know more than the user about what hosts it allows.
8468 Fixes another case of bug 752. Patch from rovv.
8469 - Check which hops rendezvous stream cells are associated with to
8470 prevent possible guess-the-streamid injection attacks from
8471 intermediate hops. Fixes another case of bug 446. Based on patch
8473 - Avoid using a negative right-shift when comparing 32-bit
8474 addresses. Possible fix for bug 845 and bug 811.
8475 - Make the assert_circuit_ok() function work correctly on circuits that
8476 have already been marked for close.
8477 - Fix read-off-the-end-of-string error in unit tests when decoding
8478 introduction points.
8479 - Fix uninitialized size field for memory area allocation: may improve
8480 memory performance during directory parsing.
8481 - Treat duplicate certificate fetches as failures, so that we do
8482 not try to re-fetch an expired certificate over and over and over.
8483 - Do not say we're fetching a certificate when we'll in fact skip it
8484 because of a pending download.
8487 Changes in version 0.2.1.6-alpha - 2008-09-30
8488 Tor 0.2.1.6-alpha further improves performance and robustness of
8489 hidden services, starts work on supporting per-country relay selection,
8490 and fixes a variety of smaller issues.
8493 - Implement proposal 121: make it possible to build hidden services
8494 that only certain clients are allowed to connect to. This is
8495 enforced at several points, so that unauthorized clients are unable
8496 to send INTRODUCE cells to the service, or even (depending on the
8497 type of authentication) to learn introduction points. This feature
8498 raises the bar for certain kinds of active attacks against hidden
8499 services. Code by Karsten Loesing.
8500 - Relays now store and serve v2 hidden service descriptors by default,
8501 i.e., the new default value for HidServDirectoryV2 is 1. This is
8502 the last step in proposal 114, which aims to make hidden service
8503 lookups more reliable.
8504 - Start work to allow node restrictions to include country codes. The
8505 syntax to exclude nodes in a country with country code XX is
8506 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
8507 refinement to decide what config options should take priority if
8508 you ask to both use a particular node and exclude it.
8509 - Allow ExitNodes list to include IP ranges and country codes, just
8510 like the Exclude*Nodes lists. Patch from Robert Hogan.
8513 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
8514 Tor to fail to start if you had it configured to use a bridge
8515 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
8516 - When extending a circuit to a hidden service directory to upload a
8517 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8518 requests failed, because the router descriptor had not been
8519 downloaded yet. In these cases, we now wait until the router
8520 descriptor is downloaded, and then retry. Likewise, clients
8521 now skip over a hidden service directory if they don't yet have
8522 its router descriptor, rather than futilely requesting it and
8523 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
8525 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8526 we were failing the whole hidden service request when the v0
8527 descriptor fetch fails, even if the v2 fetch is still pending and
8528 might succeed. Similarly, if the last v2 fetch fails, we were
8529 failing the whole hidden service request even if a v0 fetch is
8530 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8531 - DNS replies need to have names matching their requests, but
8532 these names should be in the questions section, not necessarily
8533 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
8536 - Update to the "September 1 2008" ip-to-country file.
8537 - Allow ports 465 and 587 in the default exit policy again. We had
8538 rejected them in 0.1.0.15, because back in 2005 they were commonly
8539 misconfigured and ended up as spam targets. We hear they are better
8540 locked down these days.
8541 - Use a lockfile to make sure that two Tor processes are not
8542 simultaneously running with the same datadir.
8543 - Serve the latest v3 networkstatus consensus via the control
8544 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
8545 - Better logging about stability/reliability calculations on directory
8547 - Drop the requirement to have an open dir port for storing and
8548 serving v2 hidden service descriptors.
8549 - Directory authorities now serve a /tor/dbg-stability.txt URL to
8550 help debug WFU and MTBF calculations.
8551 - Implement most of Proposal 152: allow specialized servers to permit
8552 single-hop circuits, and clients to use those servers to build
8553 single-hop circuits when using a specialized controller. Patch
8554 from Josh Albrecht. Resolves feature request 768.
8555 - Add a -p option to tor-resolve for specifying the SOCKS port: some
8556 people find host:port too confusing.
8557 - Make TrackHostExit mappings expire a while after their last use, not
8558 after their creation. Patch from Robert Hogan.
8559 - Provide circuit purposes along with circuit events to the controller.
8562 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
8564 - Fixed some memory leaks -- some quite frequent, some almost
8565 impossible to trigger -- based on results from Coverity.
8566 - When testing for libevent functions, set the LDFLAGS variable
8567 correctly. Found by Riastradh.
8568 - Fix an assertion bug in parsing policy-related options; possible fix
8570 - Catch and report a few more bootstrapping failure cases when Tor
8571 fails to establish a TCP connection. Cleanup on 0.2.1.x.
8572 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8573 bootstrapping with tunneled directory connections. Bugfix on
8574 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8575 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8576 and we know that server B rejects most-but-not all connections to
8577 port 80, we would previously reject the connection. Now, we assume
8578 the user knows what they were asking for. Fixes bug 752. Bugfix
8579 on 0.0.9rc5. Diagnosed by BarkerJr.
8580 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
8581 service directories if they have no advertised dir port. Bugfix
8583 - If we overrun our per-second write limits a little, count this as
8584 having used up our write allocation for the second, and choke
8585 outgoing directory writes. Previously, we had only counted this when
8586 we had met our limits precisely. Fixes bug 824. Patch by rovv.
8587 Bugfix on 0.2.0.x (??).
8588 - Avoid a "0 divided by 0" calculation when calculating router uptime
8589 at directory authorities. Bugfix on 0.2.0.8-alpha.
8590 - Make DNS resolved controller events into "CLOSED", not
8591 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
8593 - Fix a bug where an unreachable relay would establish enough
8594 reachability testing circuits to do a bandwidth test -- if
8595 we already have a connection to the middle hop of the testing
8596 circuit, then it could establish the last hop by using the existing
8597 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
8598 circuits no longer use entry guards in 0.2.1.3-alpha.
8599 - If we have correct permissions on $datadir, we complain to stdout
8600 and fail to start. But dangerous permissions on
8601 $datadir/cached-status/ would cause us to open a log and complain
8602 there. Now complain to stdout and fail to start in both cases. Fixes
8603 bug 820, reported by seeess.
8604 - Remove the old v2 directory authority 'lefkada' from the default
8605 list. It has been gone for many months.
8607 o Code simplifications and refactoring:
8608 - Revise the connection_new functions so that a more typesafe variant
8609 exists. This will work better with Coverity, and let us find any
8610 actual mistakes we're making here.
8611 - Refactor unit testing logic so that dmalloc can be used sensibly
8612 with unit tests to check for memory leaks.
8613 - Move all hidden-service related fields from connection and circuit
8614 structure to substructures: this way they won't eat so much memory.
8617 Changes in version 0.2.0.31 - 2008-09-03
8618 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
8619 a big bug we're seeing where in rare cases traffic from one Tor stream
8620 gets mixed into another stream, and fixes a variety of smaller issues.
8623 - Make sure that two circuits can never exist on the same connection
8624 with the same circuit ID, even if one is marked for close. This
8625 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
8626 - Relays now reject risky extend cells: if the extend cell includes
8627 a digest of all zeroes, or asks to extend back to the relay that
8628 sent the extend cell, tear down the circuit. Ideas suggested
8630 - If not enough of our entry guards are available so we add a new
8631 one, we might use the new one even if it overlapped with the
8632 current circuit's exit relay (or its family). Anonymity bugfix
8633 pointed out by rovv.
8636 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8637 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8638 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8639 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8640 - Pick size of default geoip filename string correctly on windows.
8641 Fixes bug 806. Bugfix on 0.2.0.30.
8642 - Make the autoconf script accept the obsolete --with-ssl-dir
8643 option as an alias for the actually-working --with-openssl-dir
8644 option. Fix the help documentation to recommend --with-openssl-dir.
8645 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8646 - When using the TransPort option on OpenBSD, and using the User
8647 option to change UID and drop privileges, make sure to open
8648 /dev/pf before dropping privileges. Fixes bug 782. Patch from
8649 Christopher Davis. Bugfix on 0.1.2.1-alpha.
8650 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8651 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8652 on the client side when connecting to a hidden service. Bugfix
8653 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8654 - When closing an application-side connection because its circuit is
8655 getting torn down, generate the stream event correctly. Bugfix on
8656 0.1.2.x. Anonymous patch.
8659 Changes in version 0.2.1.5-alpha - 2008-08-31
8660 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
8661 in a lot of the infrastructure for adding authorization to hidden
8662 services, lays the groundwork for having clients read their load
8663 balancing information out of the networkstatus consensus rather than
8664 the individual router descriptors, addresses two potential anonymity
8665 issues, and fixes a variety of smaller issues.
8668 - Convert many internal address representations to optionally hold
8670 - Generate and accept IPv6 addresses in many protocol elements.
8671 - Make resolver code handle nameservers located at ipv6 addresses.
8672 - Begin implementation of proposal 121 ("Client authorization for
8673 hidden services"): configure hidden services with client
8674 authorization, publish descriptors for them, and configure
8675 authorization data for hidden services at clients. The next
8676 step is to actually access hidden services that perform client
8678 - More progress toward proposal 141: Network status consensus
8679 documents and votes now contain bandwidth information for each
8680 router and a summary of that router's exit policy. Eventually this
8681 will be used by clients so that they do not have to download every
8682 known descriptor before building circuits.
8684 o Major bugfixes (on 0.2.0.x and before):
8685 - When sending CREATED cells back for a given circuit, use a 64-bit
8686 connection ID to find the right connection, rather than an addr:port
8687 combination. Now that we can have multiple OR connections between
8688 the same ORs, it is no longer possible to use addr:port to uniquely
8689 identify a connection.
8690 - Relays now reject risky extend cells: if the extend cell includes
8691 a digest of all zeroes, or asks to extend back to the relay that
8692 sent the extend cell, tear down the circuit. Ideas suggested
8694 - If not enough of our entry guards are available so we add a new
8695 one, we might use the new one even if it overlapped with the
8696 current circuit's exit relay (or its family). Anonymity bugfix
8697 pointed out by rovv.
8700 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8701 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8702 - When using the TransPort option on OpenBSD, and using the User
8703 option to change UID and drop privileges, make sure to open /dev/pf
8704 before dropping privileges. Fixes bug 782. Patch from Christopher
8705 Davis. Bugfix on 0.1.2.1-alpha.
8706 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8707 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8708 - Add a missing safe_str() call for a debug log message.
8709 - Use 64 bits instead of 32 bits for connection identifiers used with
8710 the controller protocol, to greatly reduce risk of identifier reuse.
8711 - Make the autoconf script accept the obsolete --with-ssl-dir
8712 option as an alias for the actually-working --with-openssl-dir
8713 option. Fix the help documentation to recommend --with-openssl-dir.
8714 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8717 - Rate-limit too-many-sockets messages: when they happen, they happen
8718 a lot. Resolves bug 748.
8719 - Resist DNS poisoning a little better by making sure that names in
8720 answer sections match.
8721 - Print the SOCKS5 error message string as well as the error code
8722 when a tor-resolve request fails. Patch from Jacob.
8725 Changes in version 0.2.1.4-alpha - 2008-08-04
8726 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
8729 - The address part of exit policies was not correctly written
8730 to router descriptors. This generated router descriptors that failed
8731 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
8733 - Tor triggered a false assert when extending a circuit to a relay
8734 but we already have a connection open to that relay. Noticed by
8735 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
8738 - Fix a hidden service logging bug: in some edge cases, the router
8739 descriptor of a previously picked introduction point becomes
8740 obsolete and we need to give up on it rather than continually
8741 complaining that it has become obsolete. Observed by xiando. Bugfix
8745 - Take out the TestVia config option, since it was a workaround for
8746 a bug that was fixed in Tor 0.1.1.21.
8749 Changes in version 0.2.1.3-alpha - 2008-08-03
8750 Tor 0.2.1.3-alpha implements most of the pieces to prevent
8751 infinite-length circuit attacks (see proposal 110); fixes a bug that
8752 might cause exit relays to corrupt streams they send back; allows
8753 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
8754 ExcludeExitNodes config options; and fixes a big pile of bugs.
8756 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
8757 - Send a bootstrap problem "warn" event on the first problem if the
8758 reason is NO_ROUTE (that is, our network is down).
8761 - Implement most of proposal 110: The first K cells to be sent
8762 along a circuit are marked as special "early" cells; only K "early"
8763 cells will be allowed. Once this code is universal, we can block
8764 certain kinds of DOS attack by requiring that EXTEND commands must
8765 be sent using an "early" cell.
8768 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8769 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8770 on the client side when connecting to a hidden service. Bugfix
8771 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8772 - Ensure that two circuits can never exist on the same connection
8773 with the same circuit ID, even if one is marked for close. This
8774 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
8777 - When relays do their initial bandwidth measurement, don't limit
8778 to just our entry guards for the test circuits. Otherwise we tend
8779 to have multiple test circuits going through a single entry guard,
8780 which makes our bandwidth test less accurate. Fixes part of bug 654;
8781 patch contributed by Josh Albrecht.
8782 - Add an ExcludeExitNodes option so users can list a set of nodes
8783 that should be be excluded from the exit node position, but
8784 allowed elsewhere. Implements proposal 151.
8785 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
8786 ExcludeNodes and ExcludeExitNodes lists.
8787 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
8788 be more efficient. Formerly it was quadratic in the number of
8789 servers; now it should be linear. Fixes bug 509.
8790 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
8791 and n_conn_id_digest fields into a separate structure that's
8792 only needed when the circuit has not yet attached to an n_conn.
8795 - Change the contrib/tor.logrotate script so it makes the new
8796 logs as "_tor:_tor" rather than the default, which is generally
8797 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
8798 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8799 warnings (occasionally), but it can also cause the compiler to
8800 eliminate error-checking code. Suggested by Peter Gutmann.
8801 - When a hidden service is giving up on an introduction point candidate
8802 that was not included in the last published rendezvous descriptor,
8803 don't reschedule publication of the next descriptor. Fixes bug 763.
8805 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
8806 HiddenServiceExcludeNodes as obsolete: they never worked properly,
8807 and nobody claims to be using them. Fixes bug 754. Bugfix on
8808 0.1.0.1-rc. Patch from Christian Wilms.
8809 - Fix a small alignment and memory-wasting bug on buffer chunks.
8812 o Minor bugfixes (controller):
8813 - When closing an application-side connection because its circuit
8814 is getting torn down, generate the stream event correctly.
8815 Bugfix on 0.1.2.x. Anonymous patch.
8818 - Remove all backward-compatibility code to support relays running
8819 versions of Tor so old that they no longer work at all on the
8823 Changes in version 0.2.0.30 - 2008-07-15
8825 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8826 warnings (occasionally), but it can also cause the compiler to
8827 eliminate error-checking code. Suggested by Peter Gutmann.
8830 Changes in version 0.2.0.29-rc - 2008-07-08
8831 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
8832 hidden-service performance bugs, and fixes a bunch of smaller bugs.
8835 - If you have more than one bridge but don't know their keys,
8836 you would only launch a request for the descriptor of the first one
8837 on your list. (Tor considered launching requests for the others, but
8838 found that it already had a connection on the way for $0000...0000
8839 so it didn't open another.) Bugfix on 0.2.0.x.
8840 - If you have more than one bridge but don't know their keys, and the
8841 connection to one of the bridges failed, you would cancel all
8842 pending bridge connections. (After all, they all have the same
8843 digest.) Bugfix on 0.2.0.x.
8844 - When a hidden service was trying to establish an introduction point,
8845 and Tor had built circuits preemptively for such purposes, we
8846 were ignoring all the preemptive circuits and launching a new one
8847 instead. Bugfix on 0.2.0.14-alpha.
8848 - When a hidden service was trying to establish an introduction point,
8849 and Tor *did* manage to reuse one of the preemptively built
8850 circuits, it didn't correctly remember which one it used,
8851 so it asked for another one soon after, until there were no
8852 more preemptive circuits, at which point it launched one from
8853 scratch. Bugfix on 0.0.9.x.
8854 - Make directory servers include the X-Your-Address-Is: http header in
8855 their responses even for begin_dir conns. Now clients who only
8856 ever use begin_dir connections still have a way to learn their IP
8857 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
8860 - Fix a macro/CPP interaction that was confusing some compilers:
8861 some GCCs don't like #if/#endif pairs inside macro arguments.
8863 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
8864 Fixes bug 704; fix from Steven Murdoch.
8865 - When opening /dev/null in finish_daemonize(), do not pass the
8866 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
8867 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
8868 - Correctly detect transparent proxy support on Linux hosts that
8869 require in.h to be included before netfilter_ipv4.h. Patch
8871 - Disallow session resumption attempts during the renegotiation
8872 stage of the v2 handshake protocol. Clients should never be trying
8873 session resumption at this point, but apparently some did, in
8874 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
8875 found by Geoff Goodell.
8878 Changes in version 0.2.1.2-alpha - 2008-06-20
8879 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
8880 make it easier to set up your own private Tor network; fixes several
8881 big bugs with using more than one bridge relay; fixes a big bug with
8882 offering hidden services quickly after Tor starts; and uses a better
8883 API for reporting potential bootstrapping problems to the controller.
8886 - New TestingTorNetwork config option to allow adjustment of
8887 previously constant values that, while reasonable, could slow
8888 bootstrapping. Implements proposal 135. Patch from Karsten.
8891 - If you have more than one bridge but don't know their digests,
8892 you would only learn a request for the descriptor of the first one
8893 on your list. (Tor considered launching requests for the others, but
8894 found that it already had a connection on the way for $0000...0000
8895 so it didn't open another.) Bugfix on 0.2.0.x.
8896 - If you have more than one bridge but don't know their digests,
8897 and the connection to one of the bridges failed, you would cancel
8898 all pending bridge connections. (After all, they all have the
8899 same digest.) Bugfix on 0.2.0.x.
8900 - When establishing a hidden service, introduction points that
8901 originate from cannibalized circuits are completely ignored and not
8902 included in rendezvous service descriptors. This might be another
8903 reason for delay in making a hidden service available. Bugfix
8904 from long ago (0.0.9.x?)
8907 - Allow OpenSSL to use dynamic locks if it wants.
8908 - When building a consensus, do not include routers that are down.
8909 This will cut down 30% to 40% on consensus size. Implements
8911 - In directory authorities' approved-routers files, allow
8912 fingerprints with or without space.
8913 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
8914 controller can query our current bootstrap state in case it attaches
8915 partway through and wants to catch up.
8916 - Send an initial "Starting" bootstrap status event, so we have a
8917 state to start out in.
8920 - Asking for a conditional consensus at .../consensus/<fingerprints>
8921 would crash a dirserver if it did not already have a
8922 consensus. Bugfix on 0.2.1.1-alpha.
8923 - Clean up some macro/CPP interactions: some GCC versions don't like
8924 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
8927 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
8928 - Directory authorities shouldn't complain about bootstrapping
8929 problems just because they do a lot of reachability testing and
8930 some of the connection attempts fail.
8931 - Start sending "count" and "recommendation" key/value pairs in
8932 bootstrap problem status events, so the controller can hear about
8933 problems even before Tor decides they're worth reporting for sure.
8934 - If you're using bridges, generate "bootstrap problem" warnings
8935 as soon as you run out of working bridges, rather than waiting
8936 for ten failures -- which will never happen if you have less than
8938 - If we close our OR connection because there's been a circuit
8939 pending on it for too long, we were telling our bootstrap status
8940 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
8943 Changes in version 0.2.1.1-alpha - 2008-06-13
8944 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
8945 were making the Tor process bloat especially on Linux; makes our TLS
8946 handshake blend in better; sends "bootstrap phase" status events to
8947 the controller, so it can keep the user informed of progress (and
8948 problems) fetching directory information and establishing circuits;
8949 and adds a variety of smaller features.
8952 - More work on making our TLS handshake blend in: modify the list
8953 of ciphers advertised by OpenSSL in client mode to even more
8954 closely resemble a common web browser. We cheat a little so that
8955 we can advertise ciphers that the locally installed OpenSSL doesn't
8957 - Start sending "bootstrap phase" status events to the controller,
8958 so it can keep the user informed of progress fetching directory
8959 information and establishing circuits. Also inform the controller
8960 if we think we're stuck at a particular bootstrap phase. Implements
8962 - Resume using OpenSSL's RAND_poll() for better (and more portable)
8963 cross-platform entropy collection again. We used to use it, then
8964 stopped using it because of a bug that could crash systems that
8965 called RAND_poll when they had a lot of fds open. It looks like the
8966 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
8967 at startup, and to call RAND_poll() when we reseed later only if
8968 we have a non-buggy OpenSSL version.
8971 - When we choose to abandon a new entry guard because we think our
8972 older ones might be better, close any circuits pending on that
8973 new entry guard connection. This fix should make us recover much
8974 faster when our network is down and then comes back. Bugfix on
8975 0.1.2.8-beta; found by lodger.
8977 o Memory fixes and improvements:
8978 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
8979 to avoid unused RAM in buffer chunks and memory pools.
8980 - Speed up parsing and cut down on memory fragmentation by using
8981 stack-style allocations for parsing directory objects. Previously,
8982 this accounted for over 40% of allocations from within Tor's code
8983 on a typical directory cache.
8984 - Use a Bloom filter rather than a digest-based set to track which
8985 descriptors we need to keep around when we're cleaning out old
8986 router descriptors. This speeds up the computation significantly,
8987 and may reduce fragmentation.
8988 - Reduce the default smartlist size from 32 to 16; it turns out that
8989 most smartlists hold around 8-12 elements tops.
8990 - Make dumpstats() log the fullness and size of openssl-internal
8992 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
8993 patch to their OpenSSL, turn it on to save memory on servers. This
8994 patch will (with any luck) get included in a mainline distribution
8996 - Never use OpenSSL compression: it wastes RAM and CPU trying to
8997 compress cells, which are basically all encrypted, compressed,
9001 - Stop reloading the router list from disk for no reason when we
9002 run out of reachable directory mirrors. Once upon a time reloading
9003 it would set the 'is_running' flag back to 1 for them. It hasn't
9004 done that for a long time.
9005 - In very rare situations new hidden service descriptors were
9006 published earlier than 30 seconds after the last change to the
9007 service. (We currently think that a hidden service descriptor
9008 that's been stable for 30 seconds is worth publishing.)
9011 - Allow separate log levels to be configured for different logging
9012 domains. For example, this allows one to log all notices, warnings,
9013 or errors, plus all memory management messages of level debug or
9014 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
9015 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
9016 and stop using a warning that had become unfixably verbose under
9018 - New --hush command-line option similar to --quiet. While --quiet
9019 disables all logging to the console on startup, --hush limits the
9020 output to messages of warning and error severity.
9021 - Servers support a new URL scheme for consensus downloads that
9022 allows the client to specify which authorities are trusted.
9023 The server then only sends the consensus if the client will trust
9024 it. Otherwise a 404 error is sent back. Clients use this
9025 new scheme when the server supports it (meaning it's running
9026 0.2.1.1-alpha or later). Implements proposal 134.
9027 - New configure/torrc options (--enable-geoip-stats,
9028 DirRecordUsageByCountry) to record how many IPs we've served
9029 directory info to in each country code, how many status documents
9030 total we've sent to each country code, and what share of the total
9031 directory requests we should expect to see.
9032 - Use the TLS1 hostname extension to more closely resemble browser
9034 - Lots of new unit tests.
9035 - Add a macro to implement the common pattern of iterating through
9036 two parallel lists in lockstep.
9039 Changes in version 0.2.0.28-rc - 2008-06-13
9040 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
9041 performance bug, and fixes a bunch of smaller bugs.
9044 - Fix a bug where, when we were choosing the 'end stream reason' to
9045 put in our relay end cell that we send to the exit relay, Tor
9046 clients on Windows were sometimes sending the wrong 'reason'. The
9047 anonymity problem is that exit relays may be able to guess whether
9048 the client is running Windows, thus helping partition the anonymity
9049 set. Down the road we should stop sending reasons to exit relays,
9050 or otherwise prevent future versions of this bug.
9053 - While setting up a hidden service, some valid introduction circuits
9054 were overlooked and abandoned. This might be the reason for
9055 the long delay in making a hidden service available. Bugfix on
9059 - Update to the "June 9 2008" ip-to-country file.
9060 - Run 'make test' as part of 'make dist', so we stop releasing so
9061 many development snapshots that fail their unit tests.
9064 - When we're checking if we have enough dir info for each relay
9065 to begin establishing circuits, make sure that we actually have
9066 the descriptor listed in the consensus, not just any descriptor.
9068 - Bridge relays no longer print "xx=0" in their extrainfo document
9069 for every single country code in the geoip db. Bugfix on
9071 - Only warn when we fail to load the geoip file if we were planning to
9072 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
9073 - If we change our MaxAdvertisedBandwidth and then reload torrc,
9074 Tor won't realize it should publish a new relay descriptor. Fixes
9075 bug 688, reported by mfr. Bugfix on 0.1.2.x.
9076 - When we haven't had any application requests lately, don't bother
9077 logging that we have expired a bunch of descriptors. Bugfix
9079 - Make relay cells written on a connection count as non-padding when
9080 tracking how long a connection has been in use. Bugfix on
9081 0.2.0.1-alpha. Spotted by lodger.
9082 - Fix unit tests in 0.2.0.27-rc.
9083 - Fix compile on Windows.
9086 Changes in version 0.2.0.27-rc - 2008-06-03
9087 Tor 0.2.0.27-rc adds a few features we left out of the earlier
9088 release candidates. In particular, we now include an IP-to-country
9089 GeoIP database, so controllers can easily look up what country a
9090 given relay is in, and so bridge relays can give us some sanitized
9091 summaries about which countries are making use of bridges. (See proposal
9092 126-geoip-fetching.txt for details.)
9095 - Include an IP-to-country GeoIP file in the tarball, so bridge
9096 relays can report sanitized summaries of the usage they're seeing.
9099 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
9100 Robert Hogan. Fixes the first part of bug 681.
9101 - Make bridge authorities never serve extrainfo docs.
9102 - Add support to detect Libevent versions in the 1.4.x series
9104 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
9105 - Include a new contrib/tor-exit-notice.html file that exit relay
9106 operators can put on their website to help reduce abuse queries.
9109 - When tunneling an encrypted directory connection, and its first
9110 circuit fails, do not leave it unattached and ask the controller
9111 to deal. Fixes the second part of bug 681.
9112 - Make bridge authorities correctly expire old extrainfo documents
9116 Changes in version 0.2.0.26-rc - 2008-05-13
9117 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
9118 in Debian's OpenSSL packages. All users running any 0.2.0.x version
9119 should upgrade, whether they're running Debian or not.
9121 o Major security fixes:
9122 - Use new V3 directory authority keys on the tor26, gabelmoo, and
9123 moria1 V3 directory authorities. The old keys were generated with
9124 a vulnerable version of Debian's OpenSSL package, and must be
9125 considered compromised. Other authorities' keys were not generated
9126 with an affected version of OpenSSL.
9129 - List authority signatures as "unrecognized" based on DirServer
9130 lines, not on cert cache. Bugfix on 0.2.0.x.
9133 - Add a new V3AuthUseLegacyKey option to make it easier for
9134 authorities to change their identity keys if they have to.
9137 Changes in version 0.2.0.25-rc - 2008-04-23
9138 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
9141 - Remember to initialize threading before initializing logging.
9142 Otherwise, many BSD-family implementations will crash hard on
9143 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
9146 - Authorities correctly free policies on bad servers on
9147 exit. Fixes bug 672. Bugfix on 0.2.0.x.
9150 Changes in version 0.2.0.24-rc - 2008-04-22
9151 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
9152 v3 directory authority, makes relays with dynamic IP addresses and no
9153 DirPort notice more quickly when their IP address changes, fixes a few
9154 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
9156 o New directory authorities:
9157 - Take lefkada out of the list of v3 directory authorities, since
9158 it has been down for months.
9159 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
9163 - Detect address changes more quickly on non-directory mirror
9164 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
9166 o Minor features (security):
9167 - Reject requests for reverse-dns lookup of names that are in
9168 a private address space. Patch from lodger.
9169 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
9172 o Minor bugfixes (crashes):
9173 - Avoid a rare assert that can trigger when Tor doesn't have much
9174 directory information yet and it tries to fetch a v2 hidden
9175 service descriptor. Fixes bug 651, reported by nwf.
9176 - Initialize log mutex before initializing dmalloc. Otherwise,
9177 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
9178 - Use recursive pthread mutexes in order to avoid deadlock when
9179 logging debug-level messages to a controller. Bug spotted by nwf,
9180 bugfix on 0.2.0.16-alpha.
9182 o Minor bugfixes (resource management):
9183 - Keep address policies from leaking memory: start their refcount
9184 at 1, not 2. Bugfix on 0.2.0.16-alpha.
9185 - Free authority certificates on exit, so they don't look like memory
9186 leaks. Bugfix on 0.2.0.19-alpha.
9187 - Free static hashtables for policy maps and for TLS connections on
9188 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
9189 - Avoid allocating extra space when computing consensuses on 64-bit
9190 platforms. Bug spotted by aakova.
9192 o Minor bugfixes (misc):
9193 - Do not read the configuration file when we've only been told to
9194 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
9195 based on patch from Sebastian Hahn.
9196 - Exit relays that are used as a client can now reach themselves
9197 using the .exit notation, rather than just launching an infinite
9198 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
9199 - When attempting to open a logfile fails, tell us why.
9200 - Fix a dumb bug that was preventing us from knowing that we should
9201 preemptively build circuits to handle expected directory requests.
9202 Fixes bug 660. Bugfix on 0.1.2.x.
9203 - Warn less verbosely about clock skew from netinfo cells from
9204 untrusted sources. Fixes bug 663.
9205 - Make controller stream events for DNS requests more consistent,
9206 by adding "new stream" events for DNS requests, and removing
9207 spurious "stream closed" events" for cached reverse resolves.
9208 Patch from mwenge. Fixes bug 646.
9209 - Correctly notify one-hop connections when a circuit build has
9210 failed. Possible fix for bug 669. Found by lodger.
9213 Changes in version 0.2.0.23-rc - 2008-03-24
9214 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
9215 makes bootstrapping faster if the first directory mirror you contact
9216 is down. The bundles also include the new Vidalia 0.1.2 release.
9219 - When a tunneled directory request is made to a directory server
9220 that's down, notice after 30 seconds rather than 120 seconds. Also,
9221 fail any begindir streams that are pending on it, so they can
9222 retry elsewhere. This was causing multi-minute delays on bootstrap.
9225 Changes in version 0.2.0.22-rc - 2008-03-18
9226 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
9227 enables encrypted directory connections by default for non-relays, fixes
9228 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
9229 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
9232 - Enable encrypted directory connections by default for non-relays,
9233 so censor tools that block Tor directory connections based on their
9234 plaintext patterns will no longer work. This means Tor works in
9235 certain censored countries by default again.
9238 - Make sure servers always request certificates from clients during
9239 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
9240 - Do not enter a CPU-eating loop when a connection is closed in
9241 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
9242 diagnosed by lodger; bugfix on 0.2.0.20-rc.
9243 - Fix assertion failure that could occur when a blocked circuit
9244 became unblocked, and it had pending client DNS requests. Bugfix
9245 on 0.2.0.1-alpha. Fixes bug 632.
9247 o Minor bugfixes (on 0.1.2.x):
9248 - Generate "STATUS_SERVER" events rather than misspelled
9249 "STATUS_SEVER" events. Caught by mwenge.
9250 - When counting the number of bytes written on a TLS connection,
9251 look at the BIO actually used for writing to the network, not
9252 at the BIO used (sometimes) to buffer data for the network.
9253 Looking at different BIOs could result in write counts on the
9254 order of ULONG_MAX. Fixes bug 614.
9255 - On Windows, correctly detect errors when listing the contents of
9256 a directory. Fix from lodger.
9258 o Minor bugfixes (on 0.2.0.x):
9259 - Downgrade "sslv3 alert handshake failure" message to INFO.
9260 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
9261 left BandwidthRate and BandwidthBurst at the default, we would be
9262 silently limited by those defaults. Now raise them to match the
9263 RelayBandwidth* values.
9264 - Fix the SVK version detection logic to work correctly on a branch.
9265 - Make --enable-openbsd-malloc work correctly on Linux with alpha
9266 CPUs. Fixes bug 625.
9267 - Logging functions now check that the passed severity is sane.
9268 - Use proper log levels in the testsuite call of
9269 get_interface_address6().
9270 - When using a nonstandard malloc, do not use the platform values for
9271 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
9272 - Make the openbsd malloc code use 8k pages on alpha CPUs and
9274 - Detect mismatched page sizes when using --enable-openbsd-malloc.
9275 - Avoid double-marked-for-close warning when certain kinds of invalid
9276 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
9277 for bug 617. Bugfix on 0.2.0.1-alpha.
9278 - Make sure that the "NULL-means-reject *:*" convention is followed by
9279 all the policy manipulation functions, avoiding some possible crash
9280 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
9281 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
9282 actually works, and doesn't warn about every single reverse lookup.
9283 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
9286 - Only log guard node status when guard node status has changed.
9287 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
9288 make "INFO" 75% less verbose.
9291 Changes in version 0.2.0.21-rc - 2008-03-02
9292 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
9293 makes Tor work well with Vidalia again, fixes a rare assert bug,
9294 and fixes a pair of more minor bugs. The bundles also include Vidalia
9295 0.1.0 and Torbutton 1.1.16.
9298 - The control port should declare that it requires password auth
9299 when HashedControlSessionPassword is set too. Patch from Matt Edman;
9300 bugfix on 0.2.0.20-rc. Fixes bug 615.
9301 - Downgrade assert in connection_buckets_decrement() to a log message.
9302 This may help us solve bug 614, and in any case will make its
9303 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
9304 - We were sometimes miscounting the number of bytes read from the
9305 network, causing our rate limiting to not be followed exactly.
9306 Bugfix on 0.2.0.16-alpha. Reported by lodger.
9309 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
9310 OpenSSL versions should have been working fine. Diagnosis and patch
9311 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
9312 Bugfix on 0.2.0.20-rc.
9315 Changes in version 0.2.0.20-rc - 2008-02-24
9316 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
9317 makes more progress towards normalizing Tor's TLS handshake, makes
9318 hidden services work better again, helps relays bootstrap if they don't
9319 know their IP address, adds optional support for linking in openbsd's
9320 allocator or tcmalloc, allows really fast relays to scale past 15000
9321 sockets, and fixes a bunch of minor bugs reported by Veracode.
9324 - Enable the revised TLS handshake based on the one designed by
9325 Steven Murdoch in proposal 124, as revised in proposal 130. It
9326 includes version negotiation for OR connections as described in
9327 proposal 105. The new handshake is meant to be harder for censors
9328 to fingerprint, and it adds the ability to detect certain kinds of
9329 man-in-the-middle traffic analysis attacks. The version negotiation
9330 feature will allow us to improve Tor's link protocol more safely
9332 - Choose which bridge to use proportional to its advertised bandwidth,
9333 rather than uniformly at random. This should speed up Tor for
9334 bridge users. Also do this for people who set StrictEntryNodes.
9335 - When a TrackHostExits-chosen exit fails too many times in a row,
9336 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
9339 - Resolved problems with (re-)fetching hidden service descriptors.
9340 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
9342 - If we only ever used Tor for hidden service lookups or posts, we
9343 would stop building circuits and start refusing connections after
9344 24 hours, since we falsely believed that Tor was dormant. Reported
9345 by nwf; bugfix on 0.1.2.x.
9346 - Servers that don't know their own IP address should go to the
9347 authorities for their first directory fetch, even if their DirPort
9348 is off or if they don't know they're reachable yet. This will help
9349 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
9350 - When counting the number of open sockets, count not only the number
9351 of sockets we have received from the socket() call, but also
9352 the number we've gotten from accept() and socketpair(). This bug
9353 made us fail to count all sockets that we were using for incoming
9354 connections. Bugfix on 0.2.0.x.
9355 - Fix code used to find strings within buffers, when those strings
9356 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
9357 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
9358 - Add a new __HashedControlSessionPassword option for controllers
9359 to use for one-off session password hashes that shouldn't get
9360 saved to disk by SAVECONF --- Vidalia users were accumulating a
9361 pile of HashedControlPassword lines in their torrc files, one for
9362 each time they had restarted Tor and then clicked Save. Make Tor
9363 automatically convert "HashedControlPassword" to this new option but
9364 only when it's given on the command line. Partial fix for bug 586.
9366 o Minor features (performance):
9367 - Tune parameters for cell pool allocation to minimize amount of
9369 - Add OpenBSD malloc code from phk as an optional malloc
9370 replacement on Linux: some glibc libraries do very poorly
9371 with Tor's memory allocation patterns. Pass
9372 --enable-openbsd-malloc to get the replacement malloc code.
9373 - Add a --with-tcmalloc option to the configure script to link
9374 against tcmalloc (if present). Does not yet search for
9375 non-system include paths.
9376 - Stop imposing an arbitrary maximum on the number of file descriptors
9377 used for busy servers. Bug reported by Olaf Selke; patch from
9380 o Minor features (other):
9381 - When SafeLogging is disabled, log addresses along with all TLS
9383 - When building with --enable-gcc-warnings, check for whether Apple's
9384 warning "-Wshorten-64-to-32" is available.
9385 - Add a --passphrase-fd argument to the tor-gencert command for
9388 o Minor bugfixes (memory leaks and code problems):
9389 - We were leaking a file descriptor if Tor started with a zero-length
9390 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
9391 - Detect size overflow in zlib code. Reported by Justin Ferguson and
9393 - We were comparing the raw BridgePassword entry with a base64'ed
9394 version of it, when handling a "/tor/networkstatus-bridges"
9395 directory request. Now compare correctly. Noticed by Veracode.
9396 - Recover from bad tracked-since value in MTBF-history file.
9398 - Alter the code that tries to recover from unhandled write
9399 errors, to not try to flush onto a socket that's given us
9400 unhandled errors. Bugfix on 0.1.2.x.
9401 - Make Unix controlsockets work correctly on OpenBSD. Patch from
9402 tup. Bugfix on 0.2.0.3-alpha.
9404 o Minor bugfixes (other):
9405 - If we have an extra-info document for our server, always make
9406 it available on the control port, even if we haven't gotten
9407 a copy of it from an authority yet. Patch from mwenge.
9408 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
9409 - Directory mirrors no longer include a guess at the client's IP
9410 address if the connection appears to be coming from the same /24
9411 network; it was producing too many wrong guesses.
9412 - Make the new hidden service code respect the SafeLogging setting.
9413 Bugfix on 0.2.0.x. Patch from Karsten.
9414 - When starting as an authority, do not overwrite all certificates
9415 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
9416 - If we're trying to flush the last bytes on a connection (for
9417 example, when answering a directory request), reset the
9418 time-to-give-up timeout every time we manage to write something
9419 on the socket. Bugfix on 0.1.2.x.
9420 - Change the behavior of "getinfo status/good-server-descriptor"
9421 so it doesn't return failure when any authority disappears.
9422 - Even though the man page said that "TrackHostExits ." should
9423 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
9424 - Report TLS "zero return" case as a "clean close" and "IO error"
9425 as a "close". Stop calling closes "unexpected closes": existing
9426 Tors don't use SSL_close(), so having a connection close without
9427 the TLS shutdown handshake is hardly unexpected.
9428 - Send NAMESERVER_STATUS messages for a single failed nameserver
9431 o Code simplifications and refactoring:
9432 - Remove the tor_strpartition function: its logic was confused,
9433 and it was only used for one thing that could be implemented far
9437 Changes in version 0.2.0.19-alpha - 2008-02-09
9438 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
9439 handshake, makes path selection for relays more secure and IP address
9440 guessing more robust, and generally fixes a lot of bugs in preparation
9441 for calling the 0.2.0 branch stable.
9444 - Do not include recognizeable strings in the commonname part of
9445 Tor's x509 certificates.
9448 - If we're a relay, avoid picking ourselves as an introduction point,
9449 a rendezvous point, or as the final hop for internal circuits. Bug
9450 reported by taranis and lodger. Bugfix on 0.1.2.x.
9451 - Patch from "Andrew S. Lists" to catch when we contact a directory
9452 mirror at IP address X and he says we look like we're coming from
9453 IP address X. Bugfix on 0.1.2.x.
9455 o Minor features (security):
9456 - Be more paranoid about overwriting sensitive memory on free(),
9457 as a defensive programming tactic to ensure forward secrecy.
9459 o Minor features (directory authority):
9460 - Actually validate the options passed to AuthDirReject,
9461 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
9462 - Reject router descriptors with out-of-range bandwidthcapacity or
9463 bandwidthburst values.
9465 o Minor features (controller):
9466 - Reject controller commands over 1MB in length. This keeps rogue
9467 processes from running us out of memory.
9469 o Minor features (misc):
9470 - Give more descriptive well-formedness errors for out-of-range
9471 hidden service descriptor/protocol versions.
9472 - Make memory debugging information describe more about history
9473 of cell allocation, so we can help reduce our memory use.
9475 o Deprecated features (controller):
9476 - The status/version/num-versioning and status/version/num-concurring
9477 GETINFO options are no longer useful in the v3 directory protocol:
9478 treat them as deprecated, and warn when they're used.
9481 - When our consensus networkstatus has been expired for a while, stop
9482 being willing to build circuits using it. Fixes bug 401. Bugfix
9484 - Directory caches now fetch certificates from all authorities
9485 listed in a networkstatus consensus, even when they do not
9486 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
9487 - When connecting to a bridge without specifying its key, insert
9488 the connection into the identity-to-connection map as soon as
9489 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
9490 - Detect versions of OS X where malloc_good_size() is present in the
9491 library but never actually declared. Resolves bug 587. Bugfix
9493 - Stop incorrectly truncating zlib responses to directory authority
9494 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
9495 - Stop recommending that every server operator send mail to tor-ops.
9496 Resolves bug 597. Bugfix on 0.1.2.x.
9497 - Don't trigger an assert if we start a directory authority with a
9498 private IP address (like 127.0.0.1).
9499 - Avoid possible failures when generating a directory with routers
9500 with over-long versions strings, or too many flags set. Bugfix
9502 - If an attempt to launch a DNS resolve request over the control
9503 port fails because we have overrun the limit on the number of
9504 connections, tell the controller that the request has failed.
9505 - Avoid using too little bandwidth when our clock skips a few
9506 seconds. Bugfix on 0.1.2.x.
9507 - Fix shell error when warning about missing packages in configure
9508 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
9509 - Do not become confused when receiving a spurious VERSIONS-like
9510 cell from a confused v1 client. Bugfix on 0.2.0.x.
9511 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
9512 introduction points for a hidden service have failed. Patch from
9513 Karsten Loesing. Bugfix on 0.2.0.x.
9515 o Code simplifications and refactoring:
9516 - Remove some needless generality from cpuworker code, for improved
9518 - Stop overloading the circuit_t.onionskin field for both "onionskin
9519 from a CREATE cell that we are waiting for a cpuworker to be
9520 assigned" and "onionskin from an EXTEND cell that we are going to
9521 send to an OR as soon as we are connected". Might help with bug 600.
9522 - Add an in-place version of aes_crypt() so that we can avoid doing a
9523 needless memcpy() call on each cell payload.
9526 Changes in version 0.2.0.18-alpha - 2008-01-25
9527 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
9528 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
9529 that can warn or reject connections to ports generally associated with
9530 vulnerable-plaintext protocols.
9532 o New directory authorities:
9533 - Set up dannenberg (run by CCC) as the sixth v3 directory
9537 - Fix a major memory leak when attempting to use the v2 TLS
9538 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
9539 - We accidentally enabled the under-development v2 TLS handshake
9540 code, which was causing log entries like "TLS error while
9541 renegotiating handshake". Disable it again. Resolves bug 590.
9542 - We were computing the wrong Content-Length: header for directory
9543 responses that need to be compressed on the fly, causing clients
9544 asking for those items to always fail. Bugfix on 0.2.0.x; partially
9548 - Avoid going directly to the directory authorities even if you're a
9549 relay, if you haven't found yourself reachable yet or if you've
9550 decided not to advertise your dirport yet. Addresses bug 556.
9551 - If we've gone 12 hours since our last bandwidth check, and we
9552 estimate we have less than 50KB bandwidth capacity but we could
9553 handle more, do another bandwidth test.
9554 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
9555 Tor can warn and/or refuse connections to ports commonly used with
9556 vulnerable-plaintext protocols. Currently we warn on ports 23,
9557 109, 110, and 143, but we don't reject any.
9560 - When we setconf ClientOnly to 1, close any current OR and Dir
9561 listeners. Reported by mwenge.
9562 - When we get a consensus that's been signed by more people than
9563 we expect, don't log about it; it's not a big deal. Reported
9567 - Don't answer "/tor/networkstatus-bridges" directory requests if
9568 the request isn't encrypted.
9569 - Make "ClientOnly 1" config option disable directory ports too.
9570 - Patches from Karsten Loesing to make v2 hidden services more
9571 robust: work even when there aren't enough HSDir relays available;
9572 retry when a v2 rend desc fetch fails; but don't retry if we
9573 already have a usable v0 rend desc.
9576 Changes in version 0.2.0.17-alpha - 2008-01-17
9577 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
9580 - Make the tor-gencert man page get included correctly in the tarball.
9583 Changes in version 0.2.0.16-alpha - 2008-01-17
9584 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
9585 Loesing, and generally cleans up a lot of features and minor bugs.
9587 o New directory authorities:
9588 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
9591 o Major performance improvements:
9592 - Switch our old ring buffer implementation for one more like that
9593 used by free Unix kernels. The wasted space in a buffer with 1mb
9594 of data will now be more like 8k than 1mb. The new implementation
9595 also avoids realloc();realloc(); patterns that can contribute to
9596 memory fragmentation.
9599 - Configuration files now accept C-style strings as values. This
9600 helps encode characters not allowed in the current configuration
9601 file format, such as newline or #. Addresses bug 557.
9602 - Although we fixed bug 539 (where servers would send HTTP status 503
9603 responses _and_ send a body too), there are still servers out
9604 there that haven't upgraded. Therefore, make clients parse such
9605 bodies when they receive them.
9606 - When we're not serving v2 directory information, there is no reason
9607 to actually keep any around. Remove the obsolete files and directory
9608 on startup if they are very old and we aren't going to serve them.
9610 o Minor performance improvements:
9611 - Reference-count and share copies of address policy entries; only 5%
9612 of them were actually distinct.
9613 - Never walk through the list of logs if we know that no log is
9614 interested in a given message.
9617 - When an authority has not signed a consensus, do not try to
9618 download a nonexistent "certificate with key 00000000". Bugfix
9619 on 0.2.0.x. Fixes bug 569.
9620 - Fix a rare assert error when we're closing one of our threads:
9621 use a mutex to protect the list of logs, so we never write to the
9622 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
9623 bug 575, which is kind of the revenge of bug 222.
9624 - Patch from Karsten Loesing to complain less at both the client
9625 and the relay when a relay used to have the HSDir flag but doesn't
9626 anymore, and we try to upload a hidden service descriptor.
9627 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
9629 - Do not try to download missing certificates until we have tried
9630 to check our fallback consensus. Fixes bug 583.
9631 - Make bridges round reported GeoIP stats info up to the nearest
9632 estimate, not down. Now we can distinguish between "0 people from
9633 this country" and "1 person from this country".
9634 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
9635 - Avoid possible segfault if key generation fails in
9636 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
9637 - Avoid segfault in the case where a badly behaved v2 versioning
9638 directory sends a signed networkstatus with missing client-versions.
9640 - Avoid segfaults on certain complex invocations of
9641 router_get_by_hexdigest(). Bugfix on 0.1.2.
9642 - Correct bad index on array access in parse_http_time(). Bugfix
9644 - Fix possible bug in vote generation when server versions are present
9645 but client versions are not.
9646 - Fix rare bug on REDIRECTSTREAM control command when called with no
9647 port set: it could erroneously report an error when none had
9649 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
9650 compressing large objects and find ourselves with more than 4k
9651 left over. Bugfix on 0.2.0.
9652 - Fix a small memory leak when setting up a hidden service.
9653 - Fix a few memory leaks that could in theory happen under bizarre
9655 - Fix an assert if we post a general-purpose descriptor via the
9656 control port but that descriptor isn't mentioned in our current
9657 network consensus. Bug reported by Jon McLachlan; bugfix on
9660 o Minor features (controller):
9661 - Get NS events working again. Patch from tup.
9662 - The GETCONF command now escapes and quotes configuration values
9663 that don't otherwise fit into the torrc file.
9664 - The SETCONF command now handles quoted values correctly.
9666 o Minor features (directory authorities):
9667 - New configuration options to override default maximum number of
9668 servers allowed on a single IP address. This is important for
9669 running a test network on a single host.
9670 - Actually implement the -s option to tor-gencert.
9671 - Add a manual page for tor-gencert.
9673 o Minor features (bridges):
9674 - Bridge authorities no longer serve bridge descriptors over
9675 unencrypted connections.
9677 o Minor features (other):
9678 - Add hidden services and DNSPorts to the list of things that make
9679 Tor accept that it has running ports. Change starting Tor with no
9680 ports from a fatal error to a warning; we might change it back if
9681 this turns out to confuse anybody. Fixes bug 579.
9684 Changes in version 0.1.2.19 - 2008-01-17
9685 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
9686 exit policy a little bit more conservative so it's safer to run an
9687 exit relay on a home system, and fixes a variety of smaller issues.
9690 - Exit policies now reject connections that are addressed to a
9691 relay's public (external) IP address too, unless
9692 ExitPolicyRejectPrivate is turned off. We do this because too
9693 many relays are running nearby to services that trust them based
9697 - When the clock jumps forward a lot, do not allow the bandwidth
9698 buckets to become negative. Fixes bug 544.
9699 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9700 on every successful resolve. Reported by Mike Perry.
9701 - Purge old entries from the "rephist" database and the hidden
9702 service descriptor database even when DirPort is zero.
9703 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9704 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9705 crashing or mis-answering these requests.
9706 - When we decide to send a 503 response to a request for servers, do
9707 not then also send the server descriptors: this defeats the whole
9708 purpose. Fixes bug 539.
9711 - Changing the ExitPolicyRejectPrivate setting should cause us to
9712 rebuild our server descriptor.
9713 - Fix handling of hex nicknames when answering controller requests for
9714 networkstatus by name, or when deciding whether to warn about
9715 unknown routers in a config option. (Patch from mwenge.)
9716 - Fix a couple of hard-to-trigger autoconf problems that could result
9717 in really weird results on platforms whose sys/types.h files define
9718 nonstandard integer types.
9719 - Don't try to create the datadir when running --verify-config or
9720 --hash-password. Resolves bug 540.
9721 - If we were having problems getting a particular descriptor from the
9722 directory caches, and then we learned about a new descriptor for
9723 that router, we weren't resetting our failure count. Reported
9725 - Although we fixed bug 539 (where servers would send HTTP status 503
9726 responses _and_ send a body too), there are still servers out there
9727 that haven't upgraded. Therefore, make clients parse such bodies
9728 when they receive them.
9729 - Run correctly on systems where rlim_t is larger than unsigned long.
9730 This includes some 64-bit systems.
9731 - Run correctly on platforms (like some versions of OS X 10.5) where
9732 the real limit for number of open files is OPEN_FILES, not rlim_max
9733 from getrlimit(RLIMIT_NOFILES).
9734 - Avoid a spurious free on base64 failure.
9735 - Avoid segfaults on certain complex invocations of
9736 router_get_by_hexdigest().
9737 - Fix rare bug on REDIRECTSTREAM control command when called with no
9738 port set: it could erroneously report an error when none had
9742 Changes in version 0.2.0.15-alpha - 2007-12-25
9743 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
9744 features added in 0.2.0.13-alpha.
9747 - Fix several remotely triggerable asserts based on DirPort requests
9748 for a v2 or v3 networkstatus object before we were prepared. This
9749 was particularly bad for 0.2.0.13 and later bridge relays, who
9750 would never have a v2 networkstatus and would thus always crash
9751 when used. Bugfixes on 0.2.0.x.
9752 - Estimate the v3 networkstatus size more accurately, rather than
9753 estimating it at zero bytes and giving it artificially high priority
9754 compared to other directory requests. Bugfix on 0.2.0.x.
9757 - Fix configure.in logic for cross-compilation.
9758 - When we load a bridge descriptor from the cache, and it was
9759 previously unreachable, mark it as retriable so we won't just
9760 ignore it. Also, try fetching a new copy immediately. Bugfixes
9762 - The bridge GeoIP stats were counting other relays, for example
9763 self-reachability and authority-reachability tests.
9766 - Support compilation to target iPhone; patch from cjacker huang.
9767 To build for iPhone, pass the --enable-iphone option to configure.
9770 Changes in version 0.2.0.14-alpha - 2007-12-23
9772 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
9773 without a datadirectory from a previous Tor install. Reported
9775 - Fix a crash when we fetch a descriptor that turns out to be
9776 unexpected (it used to be in our networkstatus when we started
9777 fetching it, but it isn't in our current networkstatus), and we
9778 aren't using bridges. Bugfix on 0.2.0.x.
9779 - Fix a crash when accessing hidden services: it would work the first
9780 time you use a given introduction point for your service, but
9781 on subsequent requests we'd be using garbage memory. Fixed by
9782 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
9783 - Fix a crash when we load a bridge descriptor from disk but we don't
9784 currently have a Bridge line for it in our torrc. Bugfix on
9788 - If bridge authorities set BridgePassword, they will serve a
9789 snapshot of known bridge routerstatuses from their DirPort to
9790 anybody who knows that password. Unset by default.
9793 - Make the unit tests build again.
9794 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
9795 - Make PublishServerDescriptor default to 1, so the default doesn't
9796 have to change as we invent new directory protocol versions.
9797 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
9798 be included unless sys/time.h is already included. Fixes
9799 bug 553. Bugfix on 0.2.0.x.
9800 - If we receive a general-purpose descriptor and then receive an
9801 identical bridge-purpose descriptor soon after, don't discard
9802 the next one as a duplicate.
9805 - If BridgeRelay is set to 1, then the default for
9806 PublishServerDescriptor is now "bridge" rather than "v2,v3".
9807 - If the user sets RelayBandwidthRate but doesn't set
9808 RelayBandwidthBurst, then make them equal rather than erroring out.
9811 Changes in version 0.2.0.13-alpha - 2007-12-21
9812 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
9813 Goodell, fixes many more bugs, and adds a lot of infrastructure for
9816 o New directory authorities:
9817 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
9821 - Only update guard status (usable / not usable) once we have
9822 enough directory information. This was causing us to always pick
9823 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
9824 causing us to discard all our guards on startup if we hadn't been
9825 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
9826 - Purge old entries from the "rephist" database and the hidden
9827 service descriptor databases even when DirPort is zero. Bugfix
9829 - We were ignoring our RelayBandwidthRate for the first 30 seconds
9830 after opening a circuit -- even a relayed circuit. Bugfix on
9832 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9833 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9834 crashing or mis-answering these types of requests.
9835 - Relays were publishing their server descriptor to v1 and v2
9836 directory authorities, but they didn't try publishing to v3-only
9837 authorities. Fix this; and also stop publishing to v1 authorities.
9839 - When we were reading router descriptors from cache, we were ignoring
9840 the annotations -- so for example we were reading in bridge-purpose
9841 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
9842 - When we decided to send a 503 response to a request for servers, we
9843 were then also sending the server descriptors: this defeats the
9844 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
9847 - Bridge relays now behave like clients with respect to time
9848 intervals for downloading new consensus documents -- otherwise they
9849 stand out. Bridge users now wait until the end of the interval,
9850 so their bridge relay will be sure to have a new consensus document.
9851 - Three new config options (AlternateDirAuthority,
9852 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
9853 user selectively replace the default directory authorities by type,
9854 rather than the all-or-nothing replacement that DirServer offers.
9855 - Tor can now be configured to read a GeoIP file from disk in one
9856 of two formats. This can be used by controllers to map IP addresses
9857 to countries. Eventually, it may support exit-by-country.
9858 - When possible, bridge relays remember which countries users
9859 are coming from, and report aggregate information in their
9860 extra-info documents, so that the bridge authorities can learn
9861 where Tor is blocked.
9862 - Bridge directory authorities now do reachability testing on the
9863 bridges they know. They provide router status summaries to the
9864 controller via "getinfo ns/purpose/bridge", and also dump summaries
9865 to a file periodically.
9866 - Stop fetching directory info so aggressively if your DirPort is
9867 on but your ORPort is off; stop fetching v2 dir info entirely.
9868 You can override these choices with the new FetchDirInfoEarly
9872 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
9873 consensus documents when there are too many relays at a single
9874 IP address. Now clear it in v2 network status documents too, and
9875 also clear it in routerinfo_t when the relay is no longer listed
9876 in the relevant networkstatus document.
9877 - Don't crash if we get an unexpected value for the
9878 PublishServerDescriptor config option. Reported by Matt Edman;
9879 bugfix on 0.2.0.9-alpha.
9880 - Our new v2 hidden service descriptor format allows descriptors
9881 that have no introduction points. But Tor crashed when we tried
9882 to build a descriptor with no intro points (and it would have
9883 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
9885 - Fix building with dmalloc 5.5.2 with glibc.
9886 - Reject uploaded descriptors and extrainfo documents if they're
9887 huge. Otherwise we'll cache them all over the network and it'll
9888 clog everything up. Reported by Aljosha Judmayer.
9889 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
9890 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
9891 - When the DANGEROUS_VERSION controller status event told us we're
9892 running an obsolete version, it used the string "OLD" to describe
9893 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
9894 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
9895 - If we can't expand our list of entry guards (e.g. because we're
9896 using bridges or we have StrictEntryNodes set), don't mark relays
9897 down when they fail a directory request. Otherwise we're too quick
9898 to mark all our entry points down. Bugfix on 0.1.2.x.
9899 - Fix handling of hex nicknames when answering controller requests for
9900 networkstatus by name, or when deciding whether to warn about unknown
9901 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
9902 - Fix a couple of hard-to-trigger autoconf problems that could result
9903 in really weird results on platforms whose sys/types.h files define
9904 nonstandard integer types. Bugfix on 0.1.2.x.
9905 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
9906 - Don't crash on name lookup when we have no current consensus. Fixes
9907 bug 538; bugfix on 0.2.0.x.
9908 - Only Tors that want to mirror the v2 directory info should
9909 create the "cached-status" directory in their datadir. (All Tors
9910 used to create it.) Bugfix on 0.2.0.9-alpha.
9911 - Directory authorities should only automatically download Extra Info
9912 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
9915 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
9916 consumers. (We already do this on HUP.)
9917 - Authorities and caches fetch the v2 networkstatus documents
9918 less often, now that v3 is encouraged.
9919 - Add a new config option BridgeRelay that specifies you want to
9920 be a bridge relay. Right now the only difference is that it makes
9921 you answer begin_dir requests, and it makes you cache dir info,
9922 even if your DirPort isn't on.
9923 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
9924 ask about source, timestamp of arrival, purpose, etc. We need
9925 something like this to help Vidalia not do GeoIP lookups on bridge
9927 - Allow multiple HashedControlPassword config lines, to support
9928 multiple controller passwords.
9929 - Authorities now decide whether they're authoritative for a given
9930 router based on the router's purpose.
9931 - New config options AuthDirBadDir and AuthDirListBadDirs for
9932 authorities to mark certain relays as "bad directories" in the
9933 networkstatus documents. Also supports the "!baddir" directive in
9934 the approved-routers file.
9937 Changes in version 0.2.0.12-alpha - 2007-11-16
9938 This twelfth development snapshot fixes some more build problems as
9939 well as a few minor bugs.
9942 - Make it build on OpenBSD again. Patch from tup.
9943 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
9944 package-building for Red Hat, OS X, etc.
9946 o Minor bugfixes (on 0.1.2.x):
9947 - Changing the ExitPolicyRejectPrivate setting should cause us to
9948 rebuild our server descriptor.
9950 o Minor bugfixes (on 0.2.0.x):
9951 - When we're lacking a consensus, don't try to perform rendezvous
9952 operations. Reported by Karsten Loesing.
9953 - Fix a small memory leak whenever we decide against using a
9954 newly picked entry guard. Reported by Mike Perry.
9955 - When authorities detected more than two relays running on the same
9956 IP address, they were clearing all the status flags but forgetting
9957 to clear the "hsdir" flag. So clients were being told that a
9958 given relay was the right choice for a v2 hsdir lookup, yet they
9959 never had its descriptor because it was marked as 'not running'
9961 - If we're trying to fetch a bridge descriptor and there's no way
9962 the bridge authority could help us (for example, we don't know
9963 a digest, or there is no bridge authority), don't be so eager to
9964 fall back to asking the bridge authority.
9965 - If we're using bridges or have strictentrynodes set, and our
9966 chosen exit is in the same family as all our bridges/entry guards,
9967 then be flexible about families.
9970 - When we negotiate a v2 link-layer connection (not yet implemented),
9971 accept RELAY_EARLY cells and turn them into RELAY cells if we've
9972 negotiated a v1 connection for their next step. Initial code for
9976 Changes in version 0.2.0.11-alpha - 2007-11-12
9977 This eleventh development snapshot fixes some build problems with
9978 the previous snapshot. It also includes a more secure-by-default exit
9979 policy for relays, fixes an enormous memory leak for exit relays, and
9980 fixes another bug where servers were falling out of the directory list.
9983 - Exit policies now reject connections that are addressed to a
9984 relay's public (external) IP address too, unless
9985 ExitPolicyRejectPrivate is turned off. We do this because too
9986 many relays are running nearby to services that trust them based
9987 on network address. Bugfix on 0.1.2.x.
9990 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9991 on every successful resolve. Reported by Mike Perry; bugfix
9993 - On authorities, never downgrade to old router descriptors simply
9994 because they're listed in the consensus. This created a catch-22
9995 where we wouldn't list a new descriptor because there was an
9996 old one in the consensus, and we couldn't get the new one in the
9997 consensus because we wouldn't list it. Possible fix for bug 548.
9998 Also, this might cause bug 543 to appear on authorities; if so,
9999 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
10001 o Packaging fixes on 0.2.0.10-alpha:
10002 - We were including instructions about what to do with the
10003 src/config/fallback-consensus file, but we weren't actually
10004 including it in the tarball. Disable all of that for now.
10007 - Allow people to say PreferTunnelledDirConns rather than
10008 PreferTunneledDirConns, for those alternate-spellers out there.
10011 - Don't reevaluate all the information from our consensus document
10012 just because we've downloaded a v2 networkstatus that we intend
10013 to cache. Fixes bug 545; bugfix on 0.2.0.x.
10016 Changes in version 0.2.0.10-alpha - 2007-11-10
10017 This tenth development snapshot adds a third v3 directory authority
10018 run by Mike Perry, adds most of Karsten Loesing's new hidden service
10019 descriptor format, fixes a bad crash bug and new bridge bugs introduced
10020 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
10021 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
10022 addresses many more minor issues.
10024 o New directory authorities:
10025 - Set up ides (run by Mike Perry) as the third v3 directory authority.
10028 - Allow tunnelled directory connections to ask for an encrypted
10029 "begin_dir" connection or an anonymized "uses a full Tor circuit"
10030 connection independently. Now we can make anonymized begin_dir
10031 connections for (e.g.) more secure hidden service posting and
10033 - More progress on proposal 114: code from Karsten Loesing to
10034 implement new hidden service descriptor format.
10035 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
10036 accommodate the growing number of servers that use the default
10037 and are reaching it.
10038 - Directory authorities use a new formula for selecting which nodes
10039 to advertise as Guards: they must be in the top 7/8 in terms of
10040 how long we have known about them, and above the median of those
10041 nodes in terms of weighted fractional uptime.
10042 - Make "not enough dir info yet" warnings describe *why* Tor feels
10043 it doesn't have enough directory info yet.
10046 - Stop servers from crashing if they set a Family option (or
10047 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
10049 - Make bridge users work again -- the move to v3 directories in
10050 0.2.0.9-alpha had introduced a number of bugs that made bridges
10051 no longer work for clients.
10052 - When the clock jumps forward a lot, do not allow the bandwidth
10053 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
10055 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
10056 - When the consensus lists a router descriptor that we previously were
10057 mirroring, but that we considered non-canonical, reload the
10058 descriptor as canonical. This fixes bug 543 where Tor servers
10059 would start complaining after a few days that they don't have
10060 enough directory information to build a circuit.
10061 - Consider replacing the current consensus when certificates arrive
10062 that make the pending consensus valid. Previously, we were only
10063 considering replacement when the new certs _didn't_ help.
10064 - Fix an assert error on startup if we didn't already have the
10065 consensus and certs cached in our datadirectory: we were caching
10066 the consensus in consensus_waiting_for_certs but then free'ing it
10068 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
10069 Request) if we need more v3 certs but we've already got pending
10070 requests for all of them.
10071 - Correctly back off from failing certificate downloads. Fixes
10073 - Authorities don't vote on the Running flag if they have been running
10074 for less than 30 minutes themselves. Fixes bug 547, where a newly
10075 started authority would vote that everyone was down.
10077 o New requirements:
10078 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
10079 it, it had no AES, and it hasn't seen any security patches since
10083 - Clients now hold circuitless TLS connections open for 1.5 times
10084 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
10085 rebuild a new circuit over them within that timeframe. Previously,
10086 they held them open only for KeepalivePeriod (5 minutes).
10087 - Use "If-Modified-Since" to avoid retrieving consensus
10088 networkstatuses that we already have.
10089 - When we have no consensus, check FallbackNetworkstatusFile (defaults
10090 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
10091 we start knowing some directory caches.
10092 - When we receive a consensus from the future, warn about skew.
10093 - Improve skew reporting: try to give the user a better log message
10094 about how skewed they are, and how much this matters.
10095 - When we have a certificate for an authority, believe that
10096 certificate's claims about the authority's IP address.
10097 - New --quiet command-line option to suppress the default console log.
10098 Good in combination with --hash-password.
10099 - Authorities send back an X-Descriptor-Not-New header in response to
10100 an accepted-but-discarded descriptor upload. Partially implements
10102 - Make the log message for "tls error. breaking." more useful.
10103 - Better log messages about certificate downloads, to attempt to
10104 track down the second incarnation of bug 546.
10106 o Minor features (bridges):
10107 - If bridge users set UpdateBridgesFromAuthority, but the digest
10108 they ask for is a 404 from the bridge authority, they now fall
10109 back to trying the bridge directly.
10110 - Bridges now use begin_dir to publish their server descriptor to
10111 the bridge authority, even when they haven't set TunnelDirConns.
10113 o Minor features (controller):
10114 - When reporting clock skew, and we know that the clock is _at least
10115 as skewed_ as some value, but we don't know the actual value,
10116 report the value as a "minimum skew."
10119 - Update linux-tor-prio.sh script to allow QoS based on the uid of
10120 the Tor process. Patch from Marco Bonetti with tweaks from Mike
10124 - Refuse to start if both ORPort and UseBridges are set. Bugfix
10125 on 0.2.0.x, suggested by Matt Edman.
10126 - Don't stop fetching descriptors when FetchUselessDescriptors is
10127 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
10128 reported by tup and ioerror.
10129 - Better log message on vote from unknown authority.
10130 - Don't log "Launching 0 request for 0 router" message.
10132 o Minor bugfixes (memory leaks):
10133 - Stop leaking memory every time we parse a v3 certificate. Bugfix
10135 - Stop leaking memory every time we load a v3 certificate. Bugfix
10136 on 0.2.0.1-alpha. Fixes bug 536.
10137 - Stop leaking a cached networkstatus on exit. Bugfix on
10139 - Stop leaking voter information every time we free a consensus.
10140 Bugfix on 0.2.0.3-alpha.
10141 - Stop leaking signed data every time we check a voter signature.
10142 Bugfix on 0.2.0.3-alpha.
10143 - Stop leaking a signature every time we fail to parse a consensus or
10144 a vote. Bugfix on 0.2.0.3-alpha.
10145 - Stop leaking v2_download_status_map on shutdown. Bugfix on
10147 - Stop leaking conn->nickname every time we make a connection to a
10148 Tor relay without knowing its expected identity digest (e.g. when
10149 using bridges). Bugfix on 0.2.0.3-alpha.
10151 - Minor bugfixes (portability):
10152 - Run correctly on platforms where rlim_t is larger than unsigned
10153 long, and/or where the real limit for number of open files is
10154 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
10155 particular, these may be needed for OS X 10.5.
10158 Changes in version 0.1.2.18 - 2007-10-28
10159 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
10160 hidden service introduction that were causing huge delays, and a big
10161 bug that was causing some servers to disappear from the network status
10162 lists for a few hours each day.
10164 o Major bugfixes (crashes):
10165 - If a connection is shut down abruptly because of something that
10166 happened inside connection_flushed_some(), do not call
10167 connection_finished_flushing(). Should fix bug 451:
10168 "connection_stop_writing: Assertion conn->write_event failed"
10169 Bugfix on 0.1.2.7-alpha.
10170 - Fix possible segfaults in functions called from
10171 rend_process_relay_cell().
10173 o Major bugfixes (hidden services):
10174 - Hidden services were choosing introduction points uniquely by
10175 hexdigest, but when constructing the hidden service descriptor
10176 they merely wrote the (potentially ambiguous) nickname.
10177 - Clients now use the v2 intro format for hidden service
10178 connections: they specify their chosen rendezvous point by identity
10179 digest rather than by (potentially ambiguous) nickname. These
10180 changes could speed up hidden service connections dramatically.
10182 o Major bugfixes (other):
10183 - Stop publishing a new server descriptor just because we get a
10184 HUP signal. This led (in a roundabout way) to some servers getting
10185 dropped from the networkstatus lists for a few hours each day.
10186 - When looking for a circuit to cannibalize, consider family as well
10187 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10188 circuit cannibalization).
10189 - When a router wasn't listed in a new networkstatus, we were leaving
10190 the flags for that router alone -- meaning it remained Named,
10191 Running, etc -- even though absence from the networkstatus means
10192 that it shouldn't be considered to exist at all anymore. Now we
10193 clear all the flags for routers that fall out of the networkstatus
10194 consensus. Fixes bug 529.
10197 - Don't try to access (or alter) the state file when running
10198 --list-fingerprint or --verify-config or --hash-password. Resolves
10200 - When generating information telling us how to extend to a given
10201 router, do not try to include the nickname if it is
10202 absent. Resolves bug 467.
10203 - Fix a user-triggerable segfault in expand_filename(). (There isn't
10204 a way to trigger this remotely.)
10205 - When sending a status event to the controller telling it that an
10206 OR address is reachable, set the port correctly. (Previously we
10207 were reporting the dir port.)
10208 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10209 command. Bugfix on 0.1.2.17.
10210 - When loading bandwidth history, do not believe any information in
10211 the future. Fixes bug 434.
10212 - When loading entry guard information, do not believe any information
10214 - When we have our clock set far in the future and generate an
10215 onion key, then re-set our clock to be correct, we should not stop
10216 the onion key from getting rotated.
10217 - On some platforms, accept() can return a broken address. Detect
10218 this more quietly, and deal accordingly. Fixes bug 483.
10219 - It's not actually an error to find a non-pending entry in the DNS
10220 cache when canceling a pending resolve. Don't log unless stuff
10221 is fishy. Resolves bug 463.
10222 - Don't reset trusted dir server list when we set a configuration
10223 option. Patch from Robert Hogan.
10224 - Don't try to create the datadir when running --verify-config or
10225 --hash-password. Resolves bug 540.
10228 Changes in version 0.2.0.9-alpha - 2007-10-24
10229 This ninth development snapshot switches clients to the new v3 directory
10230 system; allows servers to be listed in the network status even when they
10231 have the same nickname as a registered server; and fixes many other
10232 bugs including a big one that was causing some servers to disappear
10233 from the network status lists for a few hours each day.
10235 o Major features (directory system):
10236 - Clients now download v3 consensus networkstatus documents instead
10237 of v2 networkstatus documents. Clients and caches now base their
10238 opinions about routers on these consensus documents. Clients only
10239 download router descriptors listed in the consensus.
10240 - Authorities now list servers who have the same nickname as
10241 a different named server, but list them with a new flag,
10242 "Unnamed". Now we can list servers that happen to pick the same
10243 nickname as a server that registered two years ago and then
10244 disappeared. Partially implements proposal 122.
10245 - If the consensus lists a router as "Unnamed", the name is assigned
10246 to a different router: do not identify the router by that name.
10247 Partially implements proposal 122.
10248 - Authorities can now come to a consensus on which method to use to
10249 compute the consensus. This gives us forward compatibility.
10252 - Stop publishing a new server descriptor just because we HUP or
10253 when we find our DirPort to be reachable but won't actually publish
10254 it. New descriptors without any real changes are dropped by the
10255 authorities, and can screw up our "publish every 18 hours" schedule.
10257 - When a router wasn't listed in a new networkstatus, we were leaving
10258 the flags for that router alone -- meaning it remained Named,
10259 Running, etc -- even though absence from the networkstatus means
10260 that it shouldn't be considered to exist at all anymore. Now we
10261 clear all the flags for routers that fall out of the networkstatus
10262 consensus. Fixes bug 529; bugfix on 0.1.2.x.
10263 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
10264 extrainfo documents and then discard them immediately for not
10265 matching the latest router. Bugfix on 0.2.0.1-alpha.
10267 o Minor features (v3 directory protocol):
10268 - Allow tor-gencert to generate a new certificate without replacing
10270 - Allow certificates to include an address.
10271 - When we change our directory-cache settings, reschedule all voting
10272 and download operations.
10273 - Reattempt certificate downloads immediately on failure, as long as
10274 we haven't failed a threshold number of times yet.
10275 - Delay retrying consensus downloads while we're downloading
10276 certificates to verify the one we just got. Also, count getting a
10277 consensus that we already have (or one that isn't valid) as a failure,
10278 and count failing to get the certificates after 20 minutes as a
10280 - Build circuits and download descriptors even if our consensus is a
10281 little expired. (This feature will go away once authorities are
10284 o Minor features (router descriptor cache):
10285 - If we find a cached-routers file that's been sitting around for more
10286 than 28 days unmodified, then most likely it's a leftover from
10287 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
10289 - When we (as a cache) download a descriptor because it was listed
10290 in a consensus, remember when the consensus was supposed to expire,
10291 and don't expire the descriptor until then.
10293 o Minor features (performance):
10294 - Call routerlist_remove_old_routers() much less often. This should
10295 speed startup, especially on directory caches.
10296 - Don't try to launch new descriptor downloads quite so often when we
10297 already have enough directory information to build circuits.
10298 - Base64 decoding was actually showing up on our profile when parsing
10299 the initial descriptor file; switch to an in-process all-at-once
10300 implementation that's about 3.5x times faster than calling out to
10303 o Minor features (compilation):
10304 - Detect non-ASCII platforms (if any still exist) and refuse to
10305 build there: some of our code assumes that 'A' is 65 and so on.
10307 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
10308 - Make the "next period" votes into "current period" votes immediately
10309 after publishing the consensus; avoid a heisenbug that made them
10310 stick around indefinitely.
10311 - When we discard a vote as a duplicate, do not report this as
10313 - Treat missing v3 keys or certificates as an error when running as a
10314 v3 directory authority.
10315 - When we're configured to be a v3 authority, but we're only listed
10316 as a non-v3 authority in our DirServer line for ourself, correct
10318 - If an authority doesn't have a qualified hostname, just put
10319 its address in the vote. This fixes the problem where we referred to
10320 "moria on moria:9031."
10321 - Distinguish between detached signatures for the wrong period, and
10322 detached signatures for a divergent vote.
10323 - Fix a small memory leak when computing a consensus.
10324 - When there's no concensus, we were forming a vote every 30
10325 minutes, but writing the "valid-after" line in our vote based
10326 on our configured V3AuthVotingInterval: so unless the intervals
10327 matched up, we immediately rejected our own vote because it didn't
10328 start at the voting interval that caused us to construct a vote.
10330 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
10331 - Delete unverified-consensus when the real consensus is set.
10332 - Consider retrying a consensus networkstatus fetch immediately
10333 after one fails: don't wait 60 seconds to notice.
10334 - When fetching a consensus as a cache, wait until a newer consensus
10335 should exist before trying to replace the current one.
10336 - Use a more forgiving schedule for retrying failed consensus
10337 downloads than for other types.
10339 o Minor bugfixes (other directory issues):
10340 - Correct the implementation of "download votes by digest." Bugfix on
10342 - Authorities no longer send back "400 you're unreachable please fix
10343 it" errors to Tor servers that aren't online all the time. We're
10344 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
10346 o Minor bugfixes (controller):
10347 - Don't reset trusted dir server list when we set a configuration
10348 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
10349 - Respond to INT and TERM SIGNAL commands before we execute the
10350 signal, in case the signal shuts us down. We had a patch in
10351 0.1.2.1-alpha that tried to do this by queueing the response on
10352 the connection's buffer before shutting down, but that really
10353 isn't the same thing at all. Bug located by Matt Edman.
10355 o Minor bugfixes (misc):
10356 - Correctly check for bad options to the "PublishServerDescriptor"
10357 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
10358 - Stop leaking memory on failing case of base32_decode, and make
10359 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
10360 - Don't try to download extrainfo documents when we're trying to
10361 fetch enough directory info to build a circuit: having enough
10362 info should get priority. Bugfix on 0.2.0.x.
10363 - Don't complain that "your server has not managed to confirm that its
10364 ports are reachable" if we haven't been able to build any circuits
10365 yet. Bug found by spending four hours without a v3 consensus. Bugfix
10367 - Detect the reason for failing to mmap a descriptor file we just
10368 wrote, and give a more useful log message. Fixes bug 533. Bugfix
10371 o Code simplifications and refactoring:
10372 - Remove support for the old bw_accounting file: we've been storing
10373 bandwidth accounting information in the state file since
10374 0.1.2.5-alpha. This may result in bandwidth accounting errors
10375 if you try to upgrade from 0.1.1.x or earlier, or if you try to
10376 downgrade to 0.1.1.x or earlier.
10377 - New convenience code to locate a file within the DataDirectory.
10378 - Move non-authority functionality out of dirvote.c.
10379 - Refactor the arguments for router_pick_{directory_|trusteddir}server
10380 so that they all take the same named flags.
10383 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
10384 Unix users an easy way to script their Tor process (e.g. by
10385 adjusting bandwidth based on the time of the day).
10388 Changes in version 0.2.0.8-alpha - 2007-10-12
10389 This eighth development snapshot fixes a crash bug that's been bothering
10390 us since February 2007, lets bridge authorities store a list of bridge
10391 descriptors they've seen, gets v3 directory voting closer to working,
10392 starts caching v3 directory consensus documents on directory mirrors,
10393 and fixes a variety of smaller issues including some minor memory leaks.
10395 o Major features (router descriptor cache):
10396 - Store routers in a file called cached-descriptors instead of in
10397 cached-routers. Initialize cached-descriptors from cached-routers
10398 if the old format is around. The new format allows us to store
10399 annotations along with descriptors.
10400 - Use annotations to record the time we received each descriptor, its
10401 source, and its purpose.
10402 - Disable the SETROUTERPURPOSE controller command: it is now
10404 - Controllers should now specify cache=no or cache=yes when using
10405 the +POSTDESCRIPTOR command.
10406 - Bridge authorities now write bridge descriptors to disk, meaning
10407 we can export them to other programs and begin distributing them
10410 o Major features (directory authorities):
10411 - When a v3 authority is missing votes or signatures, it now tries
10413 - Directory authorities track weighted fractional uptime as well as
10414 weighted mean-time-between failures. WFU is suitable for deciding
10415 whether a node is "usually up", while MTBF is suitable for deciding
10416 whether a node is "likely to stay up." We need both, because
10417 "usually up" is a good requirement for guards, while "likely to
10418 stay up" is a good requirement for long-lived connections.
10420 o Major features (v3 directory system):
10421 - Caches now download v3 network status documents as needed,
10422 and download the descriptors listed in them.
10423 - All hosts now attempt to download and keep fresh v3 authority
10424 certificates, and re-attempt after failures.
10425 - More internal-consistency checks for vote parsing.
10427 o Major bugfixes (crashes):
10428 - If a connection is shut down abruptly because of something that
10429 happened inside connection_flushed_some(), do not call
10430 connection_finished_flushing(). Should fix bug 451. Bugfix on
10433 o Major bugfixes (performance):
10434 - Fix really bad O(n^2) performance when parsing a long list of
10435 routers: Instead of searching the entire list for an "extra-info "
10436 string which usually wasn't there, once for every routerinfo
10437 we read, just scan lines forward until we find one we like.
10439 - When we add data to a write buffer in response to the data on that
10440 write buffer getting low because of a flush, do not consider the
10441 newly added data as a candidate for immediate flushing, but rather
10442 make it wait until the next round of writing. Otherwise, we flush
10443 and refill recursively, and a single greedy TLS connection can
10444 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
10446 o Minor features (v3 authority system):
10447 - Add more ways for tools to download the votes that lead to the
10449 - Send a 503 when low on bandwidth and a vote, consensus, or
10450 certificate is requested.
10451 - If-modified-since is now implemented properly for all kinds of
10452 certificate requests.
10454 o Minor bugfixes (network statuses):
10455 - Tweak the implementation of proposal 109 slightly: allow at most
10456 two Tor servers on the same IP address, except if it's the location
10457 of a directory authority, in which case allow five. Bugfix on
10460 o Minor bugfixes (controller):
10461 - When sending a status event to the controller telling it that an
10462 OR address is reachable, set the port correctly. (Previously we
10463 were reporting the dir port.) Bugfix on 0.1.2.x.
10465 o Minor bugfixes (v3 directory system):
10466 - Fix logic to look up a cert by its signing key digest. Bugfix on
10468 - Only change the reply to a vote to "OK" if it's not already
10469 set. This gets rid of annoying "400 OK" log messages, which may
10470 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
10471 - When we get a valid consensus, recompute the voting schedule.
10472 - Base the valid-after time of a vote on the consensus voting
10473 schedule, not on our preferred schedule.
10474 - Make the return values and messages from signature uploads and
10475 downloads more sensible.
10476 - Fix a memory leak when serving votes and consensus documents, and
10477 another when serving certificates.
10479 o Minor bugfixes (performance):
10480 - Use a slightly simpler string hashing algorithm (copying Python's
10481 instead of Java's) and optimize our digest hashing algorithm to take
10482 advantage of 64-bit platforms and to remove some possibly-costly
10484 - Fix a minor memory leak whenever we parse guards from our state
10485 file. Bugfix on 0.2.0.7-alpha.
10486 - Fix a minor memory leak whenever we write out a file. Bugfix on
10488 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10489 command. Bugfix on 0.2.0.5-alpha.
10491 o Minor bugfixes (portability):
10492 - On some platforms, accept() can return a broken address. Detect
10493 this more quietly, and deal accordingly. Fixes bug 483.
10494 - Stop calling tor_strlower() on uninitialized memory in some cases.
10495 Bugfix in 0.2.0.7-alpha.
10497 o Minor bugfixes (usability):
10498 - Treat some 403 responses from directory servers as INFO rather than
10499 WARN-severity events.
10500 - It's not actually an error to find a non-pending entry in the DNS
10501 cache when canceling a pending resolve. Don't log unless stuff is
10502 fishy. Resolves bug 463.
10504 o Minor bugfixes (anonymity):
10505 - Never report that we've used more bandwidth than we're willing to
10506 relay: it leaks how much non-relay traffic we're using. Resolves
10508 - When looking for a circuit to cannibalize, consider family as well
10509 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10510 circuit cannibalization).
10512 o Code simplifications and refactoring:
10513 - Make a bunch of functions static. Remove some dead code.
10514 - Pull out about a third of the really big routerlist.c; put it in a
10515 new module, networkstatus.c.
10516 - Merge the extra fields in local_routerstatus_t back into
10517 routerstatus_t: we used to need one routerstatus_t for each
10518 authority's opinion, plus a local_routerstatus_t for the locally
10519 computed consensus opinion. To save space, we put the locally
10520 modified fields into local_routerstatus_t, and only the common
10521 stuff into routerstatus_t. But once v3 directories are in use,
10522 clients and caches will no longer need to hold authority opinions;
10523 thus, the rationale for keeping the types separate is now gone.
10524 - Make the code used to reschedule and reattempt downloads more
10526 - Turn all 'Are we a directory server/mirror?' logic into a call to
10528 - Remove the code to generate the oldest (v1) directory format.
10529 The code has been disabled since 0.2.0.5-alpha.
10532 Changes in version 0.2.0.7-alpha - 2007-09-21
10533 This seventh development snapshot makes bridges work again, makes bridge
10534 authorities work for the first time, fixes two huge performance flaws
10535 in hidden services, and fixes a variety of minor issues.
10537 o New directory authorities:
10538 - Set up moria1 and tor26 as the first v3 directory authorities. See
10539 doc/spec/dir-spec.txt for details on the new directory design.
10541 o Major bugfixes (crashes):
10542 - Fix possible segfaults in functions called from
10543 rend_process_relay_cell(). Bugfix on 0.1.2.x.
10545 o Major bugfixes (bridges):
10546 - Fix a bug that made servers send a "404 Not found" in response to
10547 attempts to fetch their server descriptor. This caused Tor servers
10548 to take many minutes to establish reachability for their DirPort,
10549 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
10550 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
10551 users configure that and specify a bridge with an identity
10552 fingerprint, now they will lookup the bridge descriptor at the
10553 default bridge authority via a one-hop tunnel, but once circuits
10554 are established they will switch to a three-hop tunnel for later
10555 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
10557 o Major bugfixes (hidden services):
10558 - Hidden services were choosing introduction points uniquely by
10559 hexdigest, but when constructing the hidden service descriptor
10560 they merely wrote the (potentially ambiguous) nickname.
10561 - Clients now use the v2 intro format for hidden service
10562 connections: they specify their chosen rendezvous point by identity
10563 digest rather than by (potentially ambiguous) nickname. Both
10564 are bugfixes on 0.1.2.x, and they could speed up hidden service
10565 connections dramatically. Thanks to Karsten Loesing.
10567 o Minor features (security):
10568 - As a client, do not believe any server that tells us that an
10569 address maps to an internal address space.
10570 - Make it possible to enable HashedControlPassword and
10571 CookieAuthentication at the same time.
10573 o Minor features (guard nodes):
10574 - Tag every guard node in our state file with the version that
10575 we believe added it, or with our own version if we add it. This way,
10576 if a user temporarily runs an old version of Tor and then switches
10577 back to a new one, she doesn't automatically lose her guards.
10579 o Minor features (speed):
10580 - When implementing AES counter mode, update only the portions of the
10581 counter buffer that need to change, and don't keep separate
10582 network-order and host-order counters when they are the same (i.e.,
10583 on big-endian hosts.)
10585 o Minor features (controller):
10586 - Accept LF instead of CRLF on controller, since some software has a
10587 hard time generating real Internet newlines.
10588 - Add GETINFO values for the server status events
10589 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
10592 o Removed features:
10593 - Routers no longer include bandwidth-history lines in their
10594 descriptors; this information is already available in extra-info
10595 documents, and including it in router descriptors took up 60%
10596 (!) of compressed router descriptor downloads. Completes
10597 implementation of proposal 104.
10598 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
10599 and TorControl.py, as they use the old v0 controller protocol,
10600 and are obsoleted by TorFlow anyway.
10601 - Drop support for v1 rendezvous descriptors, since we never used
10602 them anyway, and the code has probably rotted by now. Based on
10603 patch from Karsten Loesing.
10604 - On OSX, stop warning the user that kqueue support in libevent is
10605 "experimental", since it seems to have worked fine for ages.
10608 - When generating information telling us how to extend to a given
10609 router, do not try to include the nickname if it is absent. Fixes
10610 bug 467. Bugfix on 0.2.0.3-alpha.
10611 - Fix a user-triggerable (but not remotely-triggerable) segfault
10612 in expand_filename(). Bugfix on 0.1.2.x.
10613 - Fix a memory leak when freeing incomplete requests from DNSPort.
10614 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
10615 - Don't try to access (or alter) the state file when running
10616 --list-fingerprint or --verify-config or --hash-password. (Resolves
10617 bug 499.) Bugfix on 0.1.2.x.
10618 - Servers used to decline to publish their DirPort if their
10619 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
10620 were below a threshold. Now they only look at BandwidthRate and
10621 RelayBandwidthRate. Bugfix on 0.1.2.x.
10622 - Remove an optimization in the AES counter-mode code that assumed
10623 that the counter never exceeded 2^68. When the counter can be set
10624 arbitrarily as an IV (as it is by Karsten's new hidden services
10625 code), this assumption no longer holds. Bugfix on 0.1.2.x.
10626 - Resume listing "AUTHORITY" flag for authorities in network status.
10627 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
10629 o Code simplifications and refactoring:
10630 - Revamp file-writing logic so we don't need to have the entire
10631 contents of a file in memory at once before we write to disk. Tor,
10633 - Turn "descriptor store" into a full-fledged type.
10634 - Move all NT services code into a separate source file.
10635 - Unify all code that computes medians, percentile elements, etc.
10636 - Get rid of a needless malloc when parsing address policies.
10639 Changes in version 0.1.2.17 - 2007-08-30
10640 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
10641 X bundles. Vidalia 0.0.14 makes authentication required for the
10642 ControlPort in the default configuration, which addresses important
10643 security risks. Everybody who uses Vidalia (or another controller)
10646 In addition, this Tor update fixes major load balancing problems with
10647 path selection, which should speed things up a lot once many people
10650 o Major bugfixes (security):
10651 - We removed support for the old (v0) control protocol. It has been
10652 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
10653 become more of a headache than it's worth.
10655 o Major bugfixes (load balancing):
10656 - When choosing nodes for non-guard positions, weight guards
10657 proportionally less, since they already have enough load. Patch
10659 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10660 will allow fast Tor servers to get more attention.
10661 - When we're upgrading from an old Tor version, forget our current
10662 guards and pick new ones according to the new weightings. These
10663 three load balancing patches could raise effective network capacity
10664 by a factor of four. Thanks to Mike Perry for measurements.
10666 o Major bugfixes (stream expiration):
10667 - Expire not-yet-successful application streams in all cases if
10668 they've been around longer than SocksTimeout. Right now there are
10669 some cases where the stream will live forever, demanding a new
10670 circuit every 15 seconds. Fixes bug 454; reported by lodger.
10672 o Minor features (controller):
10673 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10674 is valid before any authentication has been received. It tells
10675 a controller what kind of authentication is expected, and what
10676 protocol is spoken. Implements proposal 119.
10678 o Minor bugfixes (performance):
10679 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
10680 greatly speeding up loading cached-routers from disk on startup.
10681 - Disable sentinel-based debugging for buffer code: we squashed all
10682 the bugs that this was supposed to detect a long time ago, and now
10683 its only effect is to change our buffer sizes from nice powers of
10684 two (which platform mallocs tend to like) to values slightly over
10685 powers of two (which make some platform mallocs sad).
10687 o Minor bugfixes (misc):
10688 - If exit bandwidth ever exceeds one third of total bandwidth, then
10689 use the correct formula to weight exit nodes when choosing paths.
10690 Based on patch from Mike Perry.
10691 - Choose perfectly fairly among routers when choosing by bandwidth and
10692 weighting by fraction of bandwidth provided by exits. Previously, we
10693 would choose with only approximate fairness, and correct ourselves
10694 if we ran off the end of the list.
10695 - If we require CookieAuthentication but we fail to write the
10696 cookie file, we would warn but not exit, and end up in a state
10697 where no controller could authenticate. Now we exit.
10698 - If we require CookieAuthentication, stop generating a new cookie
10699 every time we change any piece of our config.
10700 - Refuse to start with certain directory authority keys, and
10701 encourage people using them to stop.
10702 - Terminate multi-line control events properly. Original patch
10704 - Fix a minor memory leak when we fail to find enough suitable
10705 servers to choose a circuit.
10706 - Stop leaking part of the descriptor when we run into a particularly
10707 unparseable piece of it.
10710 Changes in version 0.2.0.6-alpha - 2007-08-26
10711 This sixth development snapshot features a new Vidalia version in the
10712 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
10713 the ControlPort in the default configuration, which addresses important
10716 In addition, this snapshot fixes major load balancing problems
10717 with path selection, which should speed things up a lot once many
10718 people have upgraded. The directory authorities also use a new
10719 mean-time-between-failure approach to tracking which servers are stable,
10720 rather than just looking at the most recent uptime.
10722 o New directory authorities:
10723 - Set up Tonga as the default bridge directory authority.
10726 - Directory authorities now track servers by weighted
10727 mean-times-between-failures. When we have 4 or more days of data,
10728 use measured MTBF rather than declared uptime to decide whether
10729 to call a router Stable. Implements proposal 108.
10731 o Major bugfixes (load balancing):
10732 - When choosing nodes for non-guard positions, weight guards
10733 proportionally less, since they already have enough load. Patch
10735 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10736 will allow fast Tor servers to get more attention.
10737 - When we're upgrading from an old Tor version, forget our current
10738 guards and pick new ones according to the new weightings. These
10739 three load balancing patches could raise effective network capacity
10740 by a factor of four. Thanks to Mike Perry for measurements.
10742 o Major bugfixes (descriptor parsing):
10743 - Handle unexpected whitespace better in malformed descriptors. Bug
10744 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
10747 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
10748 GETINFO for Torstat to use until it can switch to using extrainfos.
10749 - Optionally (if built with -DEXPORTMALLINFO) export the output
10750 of mallinfo via http, as tor/mallinfo.txt. Only accessible
10754 - Do not intermix bridge routers with controller-added
10755 routers. (Bugfix on 0.2.0.x)
10756 - Do not fail with an assert when accept() returns an unexpected
10757 address family. Addresses but does not wholly fix bug 483. (Bugfix
10759 - Let directory authorities startup even when they can't generate
10760 a descriptor immediately, e.g. because they don't know their
10762 - Stop putting the authentication cookie in a file called "0"
10763 in your working directory if you don't specify anything for the
10764 new CookieAuthFile option. Reported by Matt Edman.
10765 - Make it possible to read the PROTOCOLINFO response in a way that
10766 conforms to our control-spec. Reported by Matt Edman.
10767 - Fix a minor memory leak when we fail to find enough suitable
10768 servers to choose a circuit. Bugfix on 0.1.2.x.
10769 - Stop leaking part of the descriptor when we run into a particularly
10770 unparseable piece of it. Bugfix on 0.1.2.x.
10771 - Unmap the extrainfo cache file on exit.
10774 Changes in version 0.2.0.5-alpha - 2007-08-19
10775 This fifth development snapshot fixes compilation on Windows again;
10776 fixes an obnoxious client-side bug that slowed things down and put
10777 extra load on the network; gets us closer to using the v3 directory
10778 voting scheme; makes it easier for Tor controllers to use cookie-based
10779 authentication; and fixes a variety of other bugs.
10781 o Removed features:
10782 - Version 1 directories are no longer generated in full. Instead,
10783 authorities generate and serve "stub" v1 directories that list
10784 no servers. This will stop Tor versions 0.1.0.x and earlier from
10785 working, but (for security reasons) nobody should be running those
10788 o Major bugfixes (compilation, 0.2.0.x):
10789 - Try to fix Win32 compilation again: improve checking for IPv6 types.
10790 - Try to fix MSVC compilation: build correctly on platforms that do
10791 not define s6_addr16 or s6_addr32.
10792 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
10795 o Major bugfixes (stream expiration):
10796 - Expire not-yet-successful application streams in all cases if
10797 they've been around longer than SocksTimeout. Right now there are
10798 some cases where the stream will live forever, demanding a new
10799 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
10800 reported by lodger.
10802 o Minor features (directory servers):
10803 - When somebody requests a list of statuses or servers, and we have
10804 none of those, return a 404 rather than an empty 200.
10806 o Minor features (directory voting):
10807 - Store v3 consensus status consensuses on disk, and reload them
10810 o Minor features (security):
10811 - Warn about unsafe ControlPort configurations.
10812 - Refuse to start with certain directory authority keys, and
10813 encourage people using them to stop.
10815 o Minor features (controller):
10816 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10817 is valid before any authentication has been received. It tells
10818 a controller what kind of authentication is expected, and what
10819 protocol is spoken. Implements proposal 119.
10820 - New config option CookieAuthFile to choose a new location for the
10821 cookie authentication file, and config option
10822 CookieAuthFileGroupReadable to make it group-readable.
10824 o Minor features (unit testing):
10825 - Add command-line arguments to unit-test executable so that we can
10826 invoke any chosen test from the command line rather than having
10827 to run the whole test suite at once; and so that we can turn on
10828 logging for the unit tests.
10830 o Minor bugfixes (on 0.1.2.x):
10831 - If we require CookieAuthentication but we fail to write the
10832 cookie file, we would warn but not exit, and end up in a state
10833 where no controller could authenticate. Now we exit.
10834 - If we require CookieAuthentication, stop generating a new cookie
10835 every time we change any piece of our config.
10836 - When loading bandwidth history, do not believe any information in
10837 the future. Fixes bug 434.
10838 - When loading entry guard information, do not believe any information
10840 - When we have our clock set far in the future and generate an
10841 onion key, then re-set our clock to be correct, we should not stop
10842 the onion key from getting rotated.
10843 - Clean up torrc sample config file.
10844 - Do not automatically run configure from autogen.sh. This
10845 non-standard behavior tended to annoy people who have built other
10848 o Minor bugfixes (on 0.2.0.x):
10849 - Fix a bug with AutomapHostsOnResolve that would always cause
10850 the second request to fail. Bug reported by Kate. Bugfix on
10852 - Fix a bug in ADDRMAP controller replies that would sometimes
10853 try to print a NULL. Patch from tup.
10854 - Read v3 directory authority keys from the right location.
10855 - Numerous bugfixes to directory voting code.
10858 Changes in version 0.1.2.16 - 2007-08-01
10859 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
10860 remote attacker in certain situations to rewrite the user's torrc
10861 configuration file. This can completely compromise anonymity of users
10862 in most configurations, including those running the Vidalia bundles,
10863 TorK, etc. Or worse.
10865 o Major security fixes:
10866 - Close immediately after missing authentication on control port;
10867 do not allow multiple authentication attempts.
10870 Changes in version 0.2.0.4-alpha - 2007-08-01
10871 This fourth development snapshot fixes a critical security vulnerability
10872 for most users, specifically those running Vidalia, TorK, etc. Everybody
10873 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
10875 o Major security fixes:
10876 - Close immediately after missing authentication on control port;
10877 do not allow multiple authentication attempts.
10879 o Major bugfixes (compilation):
10880 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
10883 o Minor features (performance):
10884 - Be even more aggressive about releasing RAM from small
10885 empty buffers. Thanks to our free-list code, this shouldn't be too
10886 performance-intensive.
10887 - Disable sentinel-based debugging for buffer code: we squashed all
10888 the bugs that this was supposed to detect a long time ago, and
10889 now its only effect is to change our buffer sizes from nice
10890 powers of two (which platform mallocs tend to like) to values
10891 slightly over powers of two (which make some platform mallocs sad).
10892 - Log malloc statistics from mallinfo() on platforms where it
10896 Changes in version 0.2.0.3-alpha - 2007-07-29
10897 This third development snapshot introduces new experimental
10898 blocking-resistance features and a preliminary version of the v3
10899 directory voting design, and includes many other smaller features
10903 - The first pieces of our "bridge" design for blocking-resistance
10904 are implemented. People can run bridge directory authorities;
10905 people can run bridges; and people can configure their Tor clients
10906 with a set of bridges to use as the first hop into the Tor network.
10907 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
10909 - Create listener connections before we setuid to the configured
10910 User and Group. Now non-Windows users can choose port values
10911 under 1024, start Tor as root, and have Tor bind those ports
10912 before it changes to another UID. (Windows users could already
10914 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
10915 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
10916 on "vserver" accounts. (Patch from coderman.)
10917 - Be even more aggressive about separating local traffic from relayed
10918 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
10920 o Major features (experimental):
10921 - First cut of code for "v3 dir voting": directory authorities will
10922 vote on a common network status document rather than each publishing
10923 their own opinion. This code needs more testing and more corner-case
10924 handling before it's ready for use.
10927 - Directory authorities now call routers Fast if their bandwidth is
10928 at least 100KB/s, and consider their bandwidth adequate to be a
10929 Guard if it is at least 250KB/s, no matter the medians. This fix
10930 complements proposal 107. [Bugfix on 0.1.2.x]
10931 - Directory authorities now never mark more than 3 servers per IP as
10932 Valid and Running. (Implements proposal 109, by Kevin Bauer and
10934 - Minor change to organizationName and commonName generation
10935 procedures in TLS certificates during Tor handshakes, to invalidate
10936 some earlier censorware approaches. This is not a long-term
10937 solution, but applying it will give us a bit of time to look into
10938 the epidemiology of countermeasures as they spread.
10940 o Major bugfixes (directory):
10941 - Rewrite directory tokenization code to never run off the end of
10942 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
10944 o Minor features (controller):
10945 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
10946 match requests to applications. (Patch from Robert Hogan.)
10947 - Report address and port correctly on connections to DNSPort. (Patch
10948 from Robert Hogan.)
10949 - Add a RESOLVE command to launch hostname lookups. (Original patch
10950 from Robert Hogan.)
10951 - Add GETINFO status/enough-dir-info to let controllers tell whether
10952 Tor has downloaded sufficient directory information. (Patch
10954 - You can now use the ControlSocket option to tell Tor to listen for
10955 controller connections on Unix domain sockets on systems that
10956 support them. (Patch from Peter Palfrader.)
10957 - STREAM NEW events are generated for DNSPort requests and for
10958 tunneled directory connections. (Patch from Robert Hogan.)
10959 - New "GETINFO address-mappings/*" command to get address mappings
10960 with expiry information. "addr-mappings/*" is now deprecated.
10963 o Minor features (misc):
10964 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
10966 - The tor-gencert tool for v3 directory authorities now creates all
10967 files as readable to the file creator only, and write-protects
10968 the authority identity key.
10969 - When dumping memory usage, list bytes used in buffer memory
10971 - When running with dmalloc, dump more stats on hup and on exit.
10972 - Directory authorities now fail quickly and (relatively) harmlessly
10973 if they generate a network status document that is somehow
10976 o Traffic load balancing improvements:
10977 - If exit bandwidth ever exceeds one third of total bandwidth, then
10978 use the correct formula to weight exit nodes when choosing paths.
10979 (Based on patch from Mike Perry.)
10980 - Choose perfectly fairly among routers when choosing by bandwidth and
10981 weighting by fraction of bandwidth provided by exits. Previously, we
10982 would choose with only approximate fairness, and correct ourselves
10983 if we ran off the end of the list. [Bugfix on 0.1.2.x]
10985 o Performance improvements:
10986 - Be more aggressive with freeing buffer RAM or putting it on the
10988 - Use Critical Sections rather than Mutexes for synchronizing threads
10989 on win32; Mutexes are heavier-weight, and designed for synchronizing
10992 o Deprecated and removed features:
10993 - RedirectExits is now deprecated.
10994 - Stop allowing address masks that do not correspond to bit prefixes.
10995 We have warned about these for a really long time; now it's time
10996 to reject them. (Patch from croup.)
10998 o Minor bugfixes (directory):
10999 - Fix another crash bug related to extra-info caching. (Bug found by
11000 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
11001 - Directories no longer return a "304 not modified" when they don't
11002 have the networkstatus the client asked for. Also fix a memory
11003 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
11004 - We had accidentally labelled 0.1.2.x directory servers as not
11005 suitable for begin_dir requests, and had labelled no directory
11006 servers as suitable for uploading extra-info documents. [Bugfix
11009 o Minor bugfixes (dns):
11010 - Fix a crash when DNSPort is set more than once. (Patch from Robert
11011 Hogan.) [Bugfix on 0.2.0.2-alpha]
11012 - Add DNSPort connections to the global connection list, so that we
11013 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
11015 - Fix a dangling reference that could lead to a crash when DNSPort is
11016 changed or closed (Patch from Robert Hogan.) [Bugfix on
11019 o Minor bugfixes (controller):
11020 - Provide DNS expiry times in GMT, not in local time. For backward
11021 compatibility, ADDRMAP events only provide GMT expiry in an extended
11022 field. "GETINFO address-mappings" always does the right thing.
11023 - Use CRLF line endings properly in NS events.
11024 - Terminate multi-line control events properly. (Original patch
11025 from tup.) [Bugfix on 0.1.2.x-alpha]
11026 - Do not include spaces in SOURCE_ADDR fields in STREAM
11027 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
11030 Changes in version 0.1.2.15 - 2007-07-17
11031 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
11032 problems, fixes compilation on BSD, and fixes a variety of other
11033 bugs. Everybody should upgrade.
11035 o Major bugfixes (compilation):
11036 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
11038 o Major bugfixes (crashes):
11039 - Try even harder not to dereference the first character after
11040 an mmap(). Reported by lodger.
11041 - Fix a crash bug in directory authorities when we re-number the
11042 routerlist while inserting a new router.
11043 - When the cached-routers file is an even multiple of the page size,
11044 don't run off the end and crash. (Fixes bug 455; based on idea
11046 - Fix eventdns.c behavior on Solaris: It is critical to include
11047 orconfig.h _before_ sys/types.h, so that we can get the expected
11048 definition of _FILE_OFFSET_BITS.
11050 o Major bugfixes (security):
11051 - Fix a possible buffer overrun when using BSD natd support. Bug
11053 - When sending destroy cells from a circuit's origin, don't include
11054 the reason for tearing down the circuit. The spec says we didn't,
11055 and now we actually don't. Reported by lodger.
11056 - Keep streamids from different exits on a circuit separate. This
11057 bug may have allowed other routers on a given circuit to inject
11058 cells into streams. Reported by lodger; fixes bug 446.
11059 - If there's a never-before-connected-to guard node in our list,
11060 never choose any guards past it. This way we don't expand our
11061 guard list unless we need to.
11063 o Minor bugfixes (guard nodes):
11064 - Weight guard selection by bandwidth, so that low-bandwidth nodes
11065 don't get overused as guards.
11067 o Minor bugfixes (directory):
11068 - Correctly count the number of authorities that recommend each
11069 version. Previously, we were under-counting by 1.
11070 - Fix a potential crash bug when we load many server descriptors at
11071 once and some of them make others of them obsolete. Fixes bug 458.
11073 o Minor bugfixes (hidden services):
11074 - Stop tearing down the whole circuit when the user asks for a
11075 connection to a port that the hidden service didn't configure.
11078 o Minor bugfixes (misc):
11079 - On Windows, we were preventing other processes from reading
11080 cached-routers while Tor was running. Reported by janbar.
11081 - Fix a possible (but very unlikely) bug in picking routers by
11082 bandwidth. Add a log message to confirm that it is in fact
11083 unlikely. Patch from lodger.
11084 - Backport a couple of memory leak fixes.
11085 - Backport miscellaneous cosmetic bugfixes.
11088 Changes in version 0.2.0.2-alpha - 2007-06-02
11089 o Major bugfixes on 0.2.0.1-alpha:
11090 - Fix an assertion failure related to servers without extra-info digests.
11091 Resolves bugs 441 and 442.
11093 o Minor features (directory):
11094 - Support "If-Modified-Since" when answering HTTP requests for
11095 directories, running-routers documents, and network-status documents.
11096 (There's no need to support it for router descriptors, since those
11097 are downloaded by descriptor digest.)
11099 o Minor build issues:
11100 - Clear up some MIPSPro compiler warnings.
11101 - When building from a tarball on a machine that happens to have SVK
11102 installed, report the micro-revision as whatever version existed
11103 in the tarball, not as "x".
11106 Changes in version 0.2.0.1-alpha - 2007-06-01
11107 This early development snapshot provides new features for people running
11108 Tor as both a client and a server (check out the new RelayBandwidth
11109 config options); lets Tor run as a DNS proxy; and generally moves us
11110 forward on a lot of fronts.
11112 o Major features, server usability:
11113 - New config options RelayBandwidthRate and RelayBandwidthBurst:
11114 a separate set of token buckets for relayed traffic. Right now
11115 relayed traffic is defined as answers to directory requests, and
11116 OR connections that don't have any local circuits on them.
11118 o Major features, client usability:
11119 - A client-side DNS proxy feature to replace the need for
11120 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
11121 for DNS requests on port 9999, use the Tor network to resolve them
11122 anonymously, and send the reply back like a regular DNS server.
11123 The code still only implements a subset of DNS.
11124 - Make PreferTunneledDirConns and TunnelDirConns work even when
11125 we have no cached directory info. This means Tor clients can now
11126 do all of their connections protected by TLS.
11128 o Major features, performance and efficiency:
11129 - Directory authorities accept and serve "extra info" documents for
11130 routers. These documents contain fields from router descriptors
11131 that aren't usually needed, and that use a lot of excess
11132 bandwidth. Once these fields are removed from router descriptors,
11133 the bandwidth savings should be about 60%. [Partially implements
11135 - Servers upload extra-info documents to any authority that accepts
11136 them. Authorities (and caches that have been configured to download
11137 extra-info documents) download them as needed. [Partially implements
11139 - Change the way that Tor buffers data that it is waiting to write.
11140 Instead of queueing data cells in an enormous ring buffer for each
11141 client->OR or OR->OR connection, we now queue cells on a separate
11142 queue for each circuit. This lets us use less slack memory, and
11143 will eventually let us be smarter about prioritizing different kinds
11145 - Use memory pools to allocate cells with better speed and memory
11146 efficiency, especially on platforms where malloc() is inefficient.
11147 - Stop reading on edge connections when their corresponding circuit
11148 buffers are full; start again as the circuits empty out.
11150 o Major features, other:
11151 - Add an HSAuthorityRecordStats option that hidden service authorities
11152 can use to track statistics of overall hidden service usage without
11153 logging information that would be very useful to an attacker.
11154 - Start work implementing multi-level keys for directory authorities:
11155 Add a standalone tool to generate key certificates. (Proposal 103.)
11158 - Directory authorities now call routers Stable if they have an
11159 uptime of at least 30 days, even if that's not the median uptime
11160 in the network. Implements proposal 107, suggested by Kevin Bauer
11163 o Minor fixes (resource management):
11164 - Count the number of open sockets separately from the number
11165 of active connection_t objects. This will let us avoid underusing
11166 our allocated connection limit.
11167 - We no longer use socket pairs to link an edge connection to an
11168 anonymous directory connection or a DirPort test connection.
11169 Instead, we track the link internally and transfer the data
11170 in-process. This saves two sockets per "linked" connection (at the
11171 client and at the server), and avoids the nasty Windows socketpair()
11173 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
11174 for every single inactive connection_t. Free items from the
11175 4k/16k-buffer free lists when they haven't been used for a while.
11177 o Minor features (build):
11178 - Make autoconf search for libevent, openssl, and zlib consistently.
11179 - Update deprecated macros in configure.in.
11180 - When warning about missing headers, tell the user to let us
11181 know if the compile succeeds anyway, so we can downgrade the
11183 - Include the current subversion revision as part of the version
11184 string: either fetch it directly if we're in an SVN checkout, do
11185 some magic to guess it if we're in an SVK checkout, or use
11186 the last-detected version if we're building from a .tar.gz.
11187 Use this version consistently in log messages.
11189 o Minor features (logging):
11190 - Always prepend "Bug: " to any log message about a bug.
11191 - Put a platform string (e.g. "Linux i686") in the startup log
11192 message, so when people paste just their logs, we know if it's
11193 OpenBSD or Windows or what.
11194 - When logging memory usage, break down memory used in buffers by
11197 o Minor features (directory system):
11198 - New config option V2AuthoritativeDirectory that all directory
11199 authorities should set. This will let future authorities choose
11200 not to serve V2 directory information.
11201 - Directory authorities allow multiple router descriptors and/or extra
11202 info documents to be uploaded in a single go. This will make
11203 implementing proposal 104 simpler.
11205 o Minor features (controller):
11206 - Add a new config option __DisablePredictedCircuits designed for
11207 use by the controller, when we don't want Tor to build any circuits
11209 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
11210 so we can exit from the middle of the circuit.
11211 - Implement "getinfo status/circuit-established".
11212 - Implement "getinfo status/version/..." so a controller can tell
11213 whether the current version is recommended, and whether any versions
11214 are good, and how many authorities agree. (Patch from shibz.)
11216 o Minor features (hidden services):
11217 - Allow multiple HiddenServicePort directives with the same virtual
11218 port; when they occur, the user is sent round-robin to one
11219 of the target ports chosen at random. Partially fixes bug 393 by
11220 adding limited ad-hoc round-robining.
11222 o Minor features (other):
11224 - Add a new AutomapHostsOnResolve option: when it is enabled, any
11225 resolve request for hosts matching a given pattern causes Tor to
11226 generate an internal virtual address mapping for that host. This
11227 allows DNSPort to work sensibly with hidden service users. By
11228 default, .exit and .onion addresses are remapped; the list of
11229 patterns can be reconfigured with AutomapHostsSuffixes.
11230 - Add an "-F" option to tor-resolve to force a resolve for a .onion
11231 address. Thanks to the AutomapHostsOnResolve option, this is no
11232 longer a completely silly thing to do.
11233 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
11234 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
11235 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
11236 minus 1 byte: the actual maximum declared bandwidth.
11238 o Removed features:
11239 - Removed support for the old binary "version 0" controller protocol.
11240 This has been deprecated since 0.1.1, and warnings have been issued
11241 since 0.1.2. When we encounter a v0 control message, we now send
11242 back an error and close the connection.
11243 - Remove the old "dns worker" server DNS code: it hasn't been default
11244 since 0.1.2.2-alpha, and all the servers seem to be using the new
11247 o Minor bugfixes (portability):
11248 - Even though Windows is equally happy with / and \ as path separators,
11249 try to use \ consistently on Windows and / consistently on Unix: it
11250 makes the log messages nicer.
11251 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
11252 - Read resolv.conf files correctly on platforms where read() returns
11253 partial results on small file reads.
11255 o Minor bugfixes (directory):
11256 - Correctly enforce that elements of directory objects do not appear
11257 more often than they are allowed to appear.
11258 - When we are reporting the DirServer line we just parsed, we were
11259 logging the second stanza of the key fingerprint, not the first.
11261 o Minor bugfixes (logging):
11262 - When we hit an EOF on a log (probably because we're shutting down),
11263 don't try to remove the log from the list: just mark it as
11264 unusable. (Bulletproofs against bug 222.)
11266 o Minor bugfixes (other):
11267 - In the exitlist script, only consider the most recently published
11268 server descriptor for each server. Also, when the user requests
11269 a list of servers that _reject_ connections to a given address,
11270 explicitly exclude the IPs that also have servers that accept
11271 connections to that address. (Resolves bug 405.)
11272 - Stop allowing hibernating servers to be "stable" or "fast".
11273 - On Windows, we were preventing other processes from reading
11274 cached-routers while Tor was running. (Reported by janbar)
11275 - Make the NodeFamilies config option work. (Reported by
11276 lodger -- it has never actually worked, even though we added it
11278 - Check return values from pthread_mutex functions.
11279 - Don't save non-general-purpose router descriptors to the disk cache,
11280 because we have no way of remembering what their purpose was when
11282 - Add even more asserts to hunt down bug 417.
11283 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
11284 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
11285 Add a log message to confirm that it is in fact unlikely.
11287 o Minor bugfixes (controller):
11288 - Make 'getinfo fingerprint' return a 551 error if we're not a
11289 server, so we match what the control spec claims we do. Reported
11291 - Fix a typo in an error message when extendcircuit fails that
11292 caused us to not follow the \r\n-based delimiter protocol. Reported
11295 o Code simplifications and refactoring:
11296 - Stop passing around circuit_t and crypt_path_t pointers that are
11297 implicit in other procedure arguments.
11298 - Drop the old code to choke directory connections when the
11299 corresponding OR connections got full: thanks to the cell queue
11300 feature, OR conns don't get full any more.
11301 - Make dns_resolve() handle attaching connections to circuits
11302 properly, so the caller doesn't have to.
11303 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
11304 - Keep the connection array as a dynamic smartlist_t, rather than as
11305 a fixed-sized array. This is important, as the number of connections
11306 is becoming increasingly decoupled from the number of sockets.
11309 Changes in version 0.1.2.14 - 2007-05-25
11310 Tor 0.1.2.14 changes the addresses of two directory authorities (this
11311 change especially affects those who serve or use hidden services),
11312 and fixes several other crash- and security-related bugs.
11314 o Directory authority changes:
11315 - Two directory authorities (moria1 and moria2) just moved to new
11316 IP addresses. This change will particularly affect those who serve
11317 or use hidden services.
11319 o Major bugfixes (crashes):
11320 - If a directory server runs out of space in the connection table
11321 as it's processing a begin_dir request, it will free the exit stream
11322 but leave it attached to the circuit, leading to unpredictable
11323 behavior. (Reported by seeess, fixes bug 425.)
11324 - Fix a bug in dirserv_remove_invalid() that would cause authorities
11325 to corrupt memory under some really unlikely scenarios.
11326 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
11327 - Avoid segfaults when reading from mmaped descriptor file. (Reported
11330 o Major bugfixes (security):
11331 - When choosing an entry guard for a circuit, avoid using guards
11332 that are in the same family as the chosen exit -- not just guards
11333 that are exactly the chosen exit. (Reported by lodger.)
11335 o Major bugfixes (resource management):
11336 - If a directory authority is down, skip it when deciding where to get
11337 networkstatus objects or descriptors. Otherwise we keep asking
11338 every 10 seconds forever. Fixes bug 384.
11339 - Count it as a failure if we fetch a valid network-status but we
11340 don't want to keep it. Otherwise we'll keep fetching it and keep
11341 not wanting to keep it. Fixes part of bug 422.
11342 - If all of our dirservers have given us bad or no networkstatuses
11343 lately, then stop hammering them once per minute even when we
11344 think they're failed. Fixes another part of bug 422.
11347 - Actually set the purpose correctly for descriptors inserted with
11348 purpose=controller.
11349 - When we have k non-v2 authorities in our DirServer config,
11350 we ignored the last k authorities in the list when updating our
11352 - Correctly back-off from requesting router descriptors that we are
11353 having a hard time downloading.
11354 - Read resolv.conf files correctly on platforms where read() returns
11355 partial results on small file reads.
11356 - Don't rebuild the entire router store every time we get 32K of
11357 routers: rebuild it when the journal gets very large, or when
11358 the gaps in the store get very large.
11361 - When routers publish SVN revisions in their router descriptors,
11362 authorities now include those versions correctly in networkstatus
11364 - Warn when using a version of libevent before 1.3b to run a server on
11365 OSX or BSD: these versions interact badly with userspace threads.
11368 Changes in version 0.1.2.13 - 2007-04-24
11369 This release features some major anonymity fixes, such as safer path
11370 selection; better client performance; faster bootstrapping, better
11371 address detection, and better DNS support for servers; write limiting as
11372 well as read limiting to make servers easier to run; and a huge pile of
11373 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
11375 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
11376 of the Freenode IRC network, remembering his patience and vision for
11377 free speech on the Internet.
11380 - Fix a memory leak when we ask for "all" networkstatuses and we
11381 get one we don't recognize.
11382 - Add more asserts to hunt down bug 417.
11383 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
11386 Changes in version 0.1.2.12-rc - 2007-03-16
11388 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
11389 directory information requested inside Tor connections (i.e. via
11390 begin_dir cells). It only triggered when the same connection was
11391 serving other data at the same time. Reported by seeess.
11394 - When creating a circuit via the controller, send a 'launched'
11395 event when we're done, so we follow the spec better.
11398 Changes in version 0.1.2.11-rc - 2007-03-15
11399 o Minor bugfixes (controller), reported by daejees:
11400 - Correct the control spec to match how the code actually responds
11401 to 'getinfo addr-mappings/*'.
11402 - The control spec described a GUARDS event, but the code
11403 implemented a GUARD event. Standardize on GUARD, but let people
11404 ask for GUARDS too.
11407 Changes in version 0.1.2.10-rc - 2007-03-07
11408 o Major bugfixes (Windows):
11409 - Do not load the NT services library functions (which may not exist)
11410 just to detect if we're a service trying to shut down. Now we run
11411 on Win98 and friends again.
11413 o Minor bugfixes (other):
11414 - Clarify a couple of log messages.
11415 - Fix a misleading socks5 error number.
11418 Changes in version 0.1.2.9-rc - 2007-03-02
11419 o Major bugfixes (Windows):
11420 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
11421 of the usual GCC "%llu". This prevents a bug when saving 64-bit
11422 int configuration values: the high-order 32 bits would get
11423 truncated. In particular, we were being bitten by the default
11424 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
11425 and maybe also bug 397.)
11427 o Minor bugfixes (performance):
11428 - Use OpenSSL's AES implementation on platforms where it's faster.
11429 This could save us as much as 10% CPU usage.
11431 o Minor bugfixes (server):
11432 - Do not rotate onion key immediately after setting it for the first
11435 o Minor bugfixes (directory authorities):
11436 - Stop calling servers that have been hibernating for a long time
11437 "stable". Also, stop letting hibernating or obsolete servers affect
11438 uptime and bandwidth cutoffs.
11439 - Stop listing hibernating servers in the v1 directory.
11441 o Minor bugfixes (hidden services):
11442 - Upload hidden service descriptors slightly less often, to reduce
11443 load on authorities.
11445 o Minor bugfixes (other):
11446 - Fix an assert that could trigger if a controller quickly set then
11447 cleared EntryNodes. Bug found by Udo van den Heuvel.
11448 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
11450 - Fix a potential race condition in the rpm installer. Found by
11452 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
11453 of 2 as indicating that the server is completely bad; it sometimes
11454 means that the server is just bad for the request in question. (may fix
11455 the last of bug 326.)
11456 - Disable encrypted directory connections when we don't have a server
11457 descriptor for the destination. We'll get this working again in
11461 Changes in version 0.1.2.8-beta - 2007-02-26
11462 o Major bugfixes (crashes):
11463 - Stop crashing when the controller asks us to resetconf more than
11464 one config option at once. (Vidalia 0.0.11 does this.)
11465 - Fix a crash that happened on Win98 when we're given command-line
11466 arguments: don't try to load NT service functions from advapi32.dll
11467 except when we need them. (Bug introduced in 0.1.2.7-alpha;
11469 - Fix a longstanding obscure crash bug that could occur when
11470 we run out of DNS worker processes. (Resolves bug 390.)
11472 o Major bugfixes (hidden services):
11473 - Correctly detect whether hidden service descriptor downloads are
11474 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
11476 o Major bugfixes (accounting):
11477 - When we start during an accounting interval before it's time to wake
11478 up, remember to wake up at the correct time. (May fix bug 342.)
11480 o Minor bugfixes (controller):
11481 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
11482 clear the corresponding on_circuit variable, and remember later
11483 that we don't need to send a redundant CLOSED event. Resolves part
11485 - Report events where a resolve succeeded or where we got a socks
11486 protocol error correctly, rather than calling both of them
11488 - Change reported stream target addresses to IP consistently when
11489 we finally get the IP from an exit node.
11490 - Send log messages to the controller even if they happen to be very
11493 o Minor bugfixes (other):
11494 - Display correct results when reporting which versions are
11495 recommended, and how recommended they are. (Resolves bug 383.)
11496 - Improve our estimates for directory bandwidth to be less random:
11497 guess that an unrecognized directory will have the average bandwidth
11498 from all known directories, not that it will have the average
11499 bandwidth from those directories earlier than it on the list.
11500 - If we start a server with ClientOnly 1, then set ClientOnly to 0
11501 and hup, stop triggering an assert based on an empty onion_key.
11502 - On platforms with no working mmap() equivalent, don't warn the
11503 user when cached-routers doesn't exist.
11504 - Warn the user when mmap() [or its equivalent] fails for some reason
11505 other than file-not-found.
11506 - Don't warn the user when cached-routers.new doesn't exist: that's
11507 perfectly fine when starting up for the first time.
11508 - When EntryNodes are configured, rebuild the guard list to contain,
11509 in order: the EntryNodes that were guards before; the rest of the
11510 EntryNodes; the nodes that were guards before.
11511 - Mask out all signals in sub-threads; only the libevent signal
11512 handler should be processing them. This should prevent some crashes
11513 on some machines using pthreads. (Patch from coderman.)
11514 - Fix switched arguments on memset in the implementation of
11515 tor_munmap() for systems with no mmap() call.
11516 - When Tor receives a router descriptor that it asked for, but
11517 no longer wants (because it has received fresh networkstatuses
11518 in the meantime), do not warn the user. Cache the descriptor if
11519 we're a cache; drop it if we aren't.
11520 - Make earlier entry guards _really_ get retried when the network
11522 - On a malformed DNS reply, always give an error to the corresponding
11524 - Build with recent libevents on platforms that do not define the
11525 nonstandard types "u_int8_t" and friends.
11527 o Minor features (controller):
11528 - Warn the user when an application uses the obsolete binary v0
11529 control protocol. We're planning to remove support for it during
11530 the next development series, so it's good to give people some
11532 - Add STREAM_BW events to report per-entry-stream bandwidth
11533 use. (Patch from Robert Hogan.)
11534 - Rate-limit SIGNEWNYM signals in response to controllers that
11535 impolitely generate them for every single stream. (Patch from
11536 mwenge; closes bug 394.)
11537 - Make REMAP stream events have a SOURCE (cache or exit), and
11538 make them generated in every case where we get a successful
11539 connected or resolved cell.
11541 o Minor bugfixes (performance):
11542 - Call router_have_min_dir_info half as often. (This is showing up in
11543 some profiles, but not others.)
11544 - When using GCC, make log_debug never get called at all, and its
11545 arguments never get evaluated, when no debug logs are configured.
11546 (This is showing up in some profiles, but not others.)
11549 - Remove some never-implemented options. Mark PathlenCoinWeight as
11551 - Implement proposal 106: Stop requiring clients to have well-formed
11552 certificates; stop checking nicknames in certificates. (Clients
11553 have certificates so that they can look like Tor servers, but in
11554 the future we might want to allow them to look like regular TLS
11555 clients instead. Nicknames in certificates serve no purpose other
11556 than making our protocol easier to recognize on the wire.)
11557 - Revise messages on handshake failure again to be even more clear about
11558 which are incoming connections and which are outgoing.
11559 - Discard any v1 directory info that's over 1 month old (for
11560 directories) or over 1 week old (for running-routers lists).
11561 - Do not warn when individual nodes in the configuration's EntryNodes,
11562 ExitNodes, etc are down: warn only when all possible nodes
11563 are down. (Fixes bug 348.)
11564 - Always remove expired routers and networkstatus docs before checking
11565 whether we have enough information to build circuits. (Fixes
11567 - Put a lower-bound on MaxAdvertisedBandwidth.
11570 Changes in version 0.1.2.7-alpha - 2007-02-06
11571 o Major bugfixes (rate limiting):
11572 - Servers decline directory requests much more aggressively when
11573 they're low on bandwidth. Otherwise they end up queueing more and
11574 more directory responses, which can't be good for latency.
11575 - But never refuse directory requests from local addresses.
11576 - Fix a memory leak when sending a 503 response for a networkstatus
11578 - Be willing to read or write on local connections (e.g. controller
11579 connections) even when the global rate limiting buckets are empty.
11580 - If our system clock jumps back in time, don't publish a negative
11581 uptime in the descriptor. Also, don't let the global rate limiting
11582 buckets go absurdly negative.
11583 - Flush local controller connection buffers periodically as we're
11584 writing to them, so we avoid queueing 4+ megabytes of data before
11587 o Major bugfixes (NT services):
11588 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
11589 command-line flag so that admins can override the default by saying
11590 "tor --service install --user "SomeUser"". This will not affect
11591 existing installed services. Also, warn the user that the service
11592 will look for its configuration file in the service user's
11593 %appdata% directory. (We can't do the 'hardwire the user's appdata
11594 directory' trick any more, since we may not have read access to that
11597 o Major bugfixes (other):
11598 - Previously, we would cache up to 16 old networkstatus documents
11599 indefinitely, if they came from nontrusted authorities. Now we
11600 discard them if they are more than 10 days old.
11601 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
11603 - Detect and reject malformed DNS responses containing circular
11605 - If exits are rare enough that we're not marking exits as guards,
11606 ignore exit bandwidth when we're deciding the required bandwidth
11608 - When we're handling a directory connection tunneled over Tor,
11609 don't fill up internal memory buffers with all the data we want
11610 to tunnel; instead, only add it if the OR connection that will
11611 eventually receive it has some room for it. (This can lead to
11612 slowdowns in tunneled dir connections; a better solution will have
11613 to wait for 0.2.0.)
11615 o Minor bugfixes (dns):
11616 - Add some defensive programming to eventdns.c in an attempt to catch
11617 possible memory-stomping bugs.
11618 - Detect and reject DNS replies containing IPv4 or IPv6 records with
11619 an incorrect number of bytes. (Previously, we would ignore the
11621 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
11622 in the correct order, and doesn't crash.
11623 - Free memory held in recently-completed DNS lookup attempts on exit.
11624 This was not a memory leak, but may have been hiding memory leaks.
11625 - Handle TTL values correctly on reverse DNS lookups.
11626 - Treat failure to parse resolv.conf as an error.
11628 o Minor bugfixes (other):
11629 - Fix crash with "tor --list-fingerprint" (reported by seeess).
11630 - When computing clock skew from directory HTTP headers, consider what
11631 time it was when we finished asking for the directory, not what
11633 - Expire socks connections if they spend too long waiting for the
11634 handshake to finish. Previously we would let them sit around for
11635 days, if the connecting application didn't close them either.
11636 - And if the socks handshake hasn't started, don't send a
11637 "DNS resolve socks failed" handshake reply; just close it.
11638 - Stop using C functions that OpenBSD's linker doesn't like.
11639 - Don't launch requests for descriptors unless we have networkstatuses
11640 from at least half of the authorities. This delays the first
11641 download slightly under pathological circumstances, but can prevent
11642 us from downloading a bunch of descriptors we don't need.
11643 - Do not log IPs with TLS failures for incoming TLS
11644 connections. (Fixes bug 382.)
11645 - If the user asks to use invalid exit nodes, be willing to use
11647 - Stop using the reserved ac_cv namespace in our configure script.
11648 - Call stat() slightly less often; use fstat() when possible.
11649 - Refactor the way we handle pending circuits when an OR connection
11650 completes or fails, in an attempt to fix a rare crash bug.
11651 - Only rewrite a conn's address based on X-Forwarded-For: headers
11652 if it's a parseable public IP address; and stop adding extra quotes
11653 to the resulting address.
11656 - Weight directory requests by advertised bandwidth. Now we can
11657 let servers enable write limiting but still allow most clients to
11658 succeed at their directory requests. (We still ignore weights when
11659 choosing a directory authority; I hope this is a feature.)
11662 - Create a new file ReleaseNotes which was the old ChangeLog. The
11663 new ChangeLog file now includes the summaries for all development
11665 - Check for addresses with invalid characters at the exit as well
11666 as at the client, and warn less verbosely when they fail. You can
11667 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
11668 - Adapt a patch from goodell to let the contrib/exitlist script
11669 take arguments rather than require direct editing.
11670 - Inform the server operator when we decide not to advertise a
11671 DirPort due to AccountingMax enabled or a low BandwidthRate. It
11672 was confusing Zax, so now we're hopefully more helpful.
11673 - Bring us one step closer to being able to establish an encrypted
11674 directory tunnel without knowing a descriptor first. Still not
11675 ready yet. As part of the change, now assume we can use a
11676 create_fast cell if we don't know anything about a router.
11677 - Allow exit nodes to use nameservers running on ports other than 53.
11678 - Servers now cache reverse DNS replies.
11679 - Add an --ignore-missing-torrc command-line option so that we can
11680 get the "use sensible defaults if the configuration file doesn't
11681 exist" behavior even when specifying a torrc location on the command
11684 o Minor features (controller):
11685 - Track reasons for OR connection failure; make these reasons
11686 available via the controller interface. (Patch from Mike Perry.)
11687 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
11688 can learn when clients are sending malformed hostnames to Tor.
11689 - Clean up documentation for controller status events.
11690 - Add a REMAP status to stream events to note that a stream's
11691 address has changed because of a cached address or a MapAddress
11695 Changes in version 0.1.2.6-alpha - 2007-01-09
11697 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
11698 connection handles more than 4 gigs in either direction, we crash.
11699 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
11700 advertised exit node, somebody might try to exit from us when
11701 we're bootstrapping and before we've built our descriptor yet.
11702 Refuse the connection rather than crashing.
11705 - Warn if we (as a server) find that we've resolved an address that we
11706 weren't planning to resolve.
11707 - Warn that using select() on any libevent version before 1.1 will be
11708 unnecessarily slow (even for select()).
11709 - Flush ERR-level controller status events just like we currently
11710 flush ERR-level log events, so that a Tor shutdown doesn't prevent
11711 the controller from learning about current events.
11713 o Minor features (more controller status events):
11714 - Implement EXTERNAL_ADDRESS server status event so controllers can
11715 learn when our address changes.
11716 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
11717 can learn when directories reject our descriptor.
11718 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
11719 can learn when a client application is speaking a non-socks protocol
11721 - Implement DANGEROUS_SOCKS client status event so controllers
11722 can learn when a client application is leaking DNS addresses.
11723 - Implement BUG general status event so controllers can learn when
11724 Tor is unhappy about its internal invariants.
11725 - Implement CLOCK_SKEW general status event so controllers can learn
11726 when Tor thinks the system clock is set incorrectly.
11727 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
11728 server status events so controllers can learn when their descriptors
11729 are accepted by a directory.
11730 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
11731 server status events so controllers can learn about Tor's progress in
11732 deciding whether it's reachable from the outside.
11733 - Implement BAD_LIBEVENT general status event so controllers can learn
11734 when we have a version/method combination in libevent that needs to
11736 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
11737 and DNS_USELESS server status events so controllers can learn
11738 about changes to DNS server status.
11740 o Minor features (directory):
11741 - Authorities no longer recommend exits as guards if this would shift
11742 too much load to the exit nodes.
11745 Changes in version 0.1.2.5-alpha - 2007-01-06
11747 - Enable write limiting as well as read limiting. Now we sacrifice
11748 capacity if we're pushing out lots of directory traffic, rather
11749 than overrunning the user's intended bandwidth limits.
11750 - Include TLS overhead when counting bandwidth usage; previously, we
11751 would count only the bytes sent over TLS, but not the bytes used
11753 - Support running the Tor service with a torrc not in the same
11754 directory as tor.exe and default to using the torrc located in
11755 the %appdata%\Tor\ of the user who installed the service. Patch
11757 - Servers now check for the case when common DNS requests are going to
11758 wildcarded addresses (i.e. all getting the same answer), and change
11759 their exit policy to reject *:* if it's happening.
11760 - Implement BEGIN_DIR cells, so we can connect to the directory
11761 server via TLS to do encrypted directory requests rather than
11762 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
11763 config options if you like.
11765 o Minor features (config and docs):
11766 - Start using the state file to store bandwidth accounting data:
11767 the bw_accounting file is now obsolete. We'll keep generating it
11768 for a while for people who are still using 0.1.2.4-alpha.
11769 - Try to batch changes to the state file so that we do as few
11770 disk writes as possible while still storing important things in
11772 - The state file and the bw_accounting file get saved less often when
11773 the AvoidDiskWrites config option is set.
11774 - Make PIDFile work on Windows (untested).
11775 - Add internal descriptions for a bunch of configuration options:
11776 accessible via controller interface and in comments in saved
11778 - Reject *:563 (NNTPS) in the default exit policy. We already reject
11779 NNTP by default, so this seems like a sensible addition.
11780 - Clients now reject hostnames with invalid characters. This should
11781 avoid some inadvertent info leaks. Add an option
11782 AllowNonRFC953Hostnames to disable this behavior, in case somebody
11783 is running a private network with hosts called @, !, and #.
11784 - Add a maintainer script to tell us which options are missing
11785 documentation: "make check-docs".
11786 - Add a new address-spec.txt document to describe our special-case
11787 addresses: .exit, .onion, and .noconnnect.
11789 o Minor features (DNS):
11790 - Ongoing work on eventdns infrastructure: now it has dns server
11791 and ipv6 support. One day Tor will make use of it.
11792 - Add client-side caching for reverse DNS lookups.
11793 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
11794 - When we change nameservers or IP addresses, reset and re-launch
11795 our tests for DNS hijacking.
11797 o Minor features (directory):
11798 - Authorities now specify server versions in networkstatus. This adds
11799 about 2% to the size of compressed networkstatus docs, and allows
11800 clients to tell which servers support BEGIN_DIR and which don't.
11801 The implementation is forward-compatible with a proposed future
11802 protocol version scheme not tied to Tor versions.
11803 - DirServer configuration lines now have an orport= option so
11804 clients can open encrypted tunnels to the authorities without
11805 having downloaded their descriptors yet. Enabled for moria1,
11806 moria2, tor26, and lefkada now in the default configuration.
11807 - Directory servers are more willing to send a 503 "busy" if they
11808 are near their write limit, especially for v1 directory requests.
11809 Now they can use their limited bandwidth for actual Tor traffic.
11810 - Clients track responses with status 503 from dirservers. After a
11811 dirserver has given us a 503, we try not to use it until an hour has
11812 gone by, or until we have no dirservers that haven't given us a 503.
11813 - When we get a 503 from a directory, and we're not a server, we don't
11814 count the failure against the total number of failures allowed
11815 for the thing we're trying to download.
11816 - Report X-Your-Address-Is correctly from tunneled directory
11817 connections; don't report X-Your-Address-Is when it's an internal
11818 address; and never believe reported remote addresses when they're
11820 - Protect against an unlikely DoS attack on directory servers.
11821 - Add a BadDirectory flag to network status docs so that authorities
11822 can (eventually) tell clients about caches they believe to be
11825 o Minor features (controller):
11826 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
11827 - Reimplement GETINFO so that info/names stays in sync with the
11829 - Implement "GETINFO fingerprint".
11830 - Implement "SETEVENTS GUARD" so controllers can get updates on
11831 entry guard status as it changes.
11833 o Minor features (clean up obsolete pieces):
11834 - Remove some options that have been deprecated since at least
11835 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
11836 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
11837 to set log options.
11838 - We no longer look for identity and onion keys in "identity.key" and
11839 "onion.key" -- these were replaced by secret_id_key and
11840 secret_onion_key in 0.0.8pre1.
11841 - We no longer require unrecognized directory entries to be
11844 o Major bugfixes (security):
11845 - Stop sending the HttpProxyAuthenticator string to directory
11846 servers when directory connections are tunnelled through Tor.
11847 - Clients no longer store bandwidth history in the state file.
11848 - Do not log introduction points for hidden services if SafeLogging
11850 - When generating bandwidth history, round down to the nearest
11851 1k. When storing accounting data, round up to the nearest 1k.
11852 - When we're running as a server, remember when we last rotated onion
11853 keys, so that we will rotate keys once they're a week old even if
11854 we never stay up for a week ourselves.
11856 o Major bugfixes (other):
11857 - Fix a longstanding bug in eventdns that prevented the count of
11858 timed-out resolves from ever being reset. This bug caused us to
11859 give up on a nameserver the third time it timed out, and try it
11860 10 seconds later... and to give up on it every time it timed out
11862 - Take out the '5 second' timeout from the connection retry
11863 schedule. Now the first connect attempt will wait a full 10
11864 seconds before switching to a new circuit. Perhaps this will help
11865 a lot. Based on observations from Mike Perry.
11866 - Fix a bug on the Windows implementation of tor_mmap_file() that
11867 would prevent the cached-routers file from ever loading. Reported
11871 - Fix an assert failure when a directory authority sets
11872 AuthDirRejectUnlisted and then receives a descriptor from an
11873 unlisted router. Reported by seeess.
11874 - Avoid a double-free when parsing malformed DirServer lines.
11875 - Fix a bug when a BSD-style PF socket is first used. Patch from
11877 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
11878 to resolve an address at a given exit node even when they ask for
11880 - Servers no longer ever list themselves in their "family" line,
11881 even if configured to do so. This makes it easier to configure
11882 family lists conveniently.
11883 - When running as a server, don't fall back to 127.0.0.1 when no
11884 nameservers are configured in /etc/resolv.conf; instead, make the
11885 user fix resolv.conf or specify nameservers explicitly. (Resolves
11887 - Stop accepting certain malformed ports in configured exit policies.
11888 - Don't re-write the fingerprint file every restart, unless it has
11890 - Stop warning when a single nameserver fails: only warn when _all_ of
11891 our nameservers have failed. Also, when we only have one nameserver,
11892 raise the threshold for deciding that the nameserver is dead.
11893 - Directory authorities now only decide that routers are reachable
11894 if their identity keys are as expected.
11895 - When the user uses bad syntax in the Log config line, stop
11896 suggesting other bad syntax as a replacement.
11897 - Correctly detect ipv6 DNS capability on OpenBSD.
11899 o Minor bugfixes (controller):
11900 - Report the circuit number correctly in STREAM CLOSED events. Bug
11901 reported by Mike Perry.
11902 - Do not report bizarre values for results of accounting GETINFOs
11903 when the last second's write or read exceeds the allotted bandwidth.
11904 - Report "unrecognized key" rather than an empty string when the
11905 controller tries to fetch a networkstatus that doesn't exist.
11908 Changes in version 0.1.1.26 - 2006-12-14
11909 o Security bugfixes:
11910 - Stop sending the HttpProxyAuthenticator string to directory
11911 servers when directory connections are tunnelled through Tor.
11912 - Clients no longer store bandwidth history in the state file.
11913 - Do not log introduction points for hidden services if SafeLogging
11917 - Fix an assert failure when a directory authority sets
11918 AuthDirRejectUnlisted and then receives a descriptor from an
11919 unlisted router (reported by seeess).
11922 Changes in version 0.1.2.4-alpha - 2006-12-03
11924 - Add support for using natd; this allows FreeBSDs earlier than
11925 5.1.2 to have ipfw send connections through Tor without using
11926 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
11929 - Make all connections to addresses of the form ".noconnect"
11930 immediately get closed. This lets application/controller combos
11931 successfully test whether they're talking to the same Tor by
11932 watching for STREAM events.
11933 - Make cross.sh cross-compilation script work even when autogen.sh
11934 hasn't been run. (Patch from Michael Mohr.)
11935 - Statistics dumped by -USR2 now include a breakdown of public key
11936 operations, for profiling.
11939 - Fix a major leak when directory authorities parse their
11940 approved-routers list, a minor memory leak when we fail to pick
11941 an exit node, and a few rare leaks on errors.
11942 - Handle TransPort connections even when the server sends data before
11943 the client sends data. Previously, the connection would just hang
11944 until the client sent data. (Patch from tup based on patch from
11946 - Avoid assert failure when our cached-routers file is empty on
11950 - Don't log spurious warnings when we see a circuit close reason we
11951 don't recognize; it's probably just from a newer version of Tor.
11952 - Have directory authorities allow larger amounts of drift in uptime
11953 without replacing the server descriptor: previously, a server that
11954 restarted every 30 minutes could have 48 "interesting" descriptors
11956 - Start linking to the Tor specification and Tor reference manual
11957 correctly in the Windows installer.
11958 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11959 Tor/Privoxy we also uninstall Vidalia.
11960 - Resume building on Irix64, and fix a lot of warnings from its
11961 MIPSpro C compiler.
11962 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
11963 when we're running as a client.
11966 Changes in version 0.1.1.25 - 2006-11-04
11968 - When a client asks us to resolve (rather than connect to)
11969 an address, and we have a cached answer, give them the cached
11970 answer. Previously, we would give them no answer at all.
11971 - We were building exactly the wrong circuits when we predict
11972 hidden service requirements, meaning Tor would have to build all
11973 its circuits on demand.
11974 - If none of our live entry guards have a high uptime, but we
11975 require a guard with a high uptime, try adding a new guard before
11976 we give up on the requirement. This patch should make long-lived
11977 connections more stable on average.
11978 - When testing reachability of our DirPort, don't launch new
11979 tests when there's already one in progress -- unreachable
11980 servers were stacking up dozens of testing streams.
11982 o Security bugfixes:
11983 - When the user sends a NEWNYM signal, clear the client-side DNS
11984 cache too. Otherwise we continue to act on previous information.
11987 - Avoid a memory corruption bug when creating a hash table for
11989 - Avoid possibility of controller-triggered crash when misusing
11990 certain commands from a v0 controller on platforms that do not
11991 handle printf("%s",NULL) gracefully.
11992 - Avoid infinite loop on unexpected controller input.
11993 - Don't log spurious warnings when we see a circuit close reason we
11994 don't recognize; it's probably just from a newer version of Tor.
11995 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11996 Tor/Privoxy we also uninstall Vidalia.
11999 Changes in version 0.1.2.3-alpha - 2006-10-29
12001 - Prepare for servers to publish descriptors less often: never
12002 discard a descriptor simply for being too old until either it is
12003 recommended by no authorities, or until we get a better one for
12004 the same router. Make caches consider retaining old recommended
12005 routers for even longer.
12006 - If most authorities set a BadExit flag for a server, clients
12007 don't think of it as a general-purpose exit. Clients only consider
12008 authorities that advertise themselves as listing bad exits.
12009 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
12010 headers for content, so that we can work better in the presence of
12011 caching HTTP proxies.
12012 - Allow authorities to list nodes as bad exits by fingerprint or by
12015 o Minor features, controller:
12016 - Add a REASON field to CIRC events; for backward compatibility, this
12017 field is sent only to controllers that have enabled the extended
12018 event format. Also, add additional reason codes to explain why
12019 a given circuit has been destroyed or truncated. (Patches from
12021 - Add a REMOTE_REASON field to extended CIRC events to tell the
12022 controller about why a remote OR told us to close a circuit.
12023 - Stream events also now have REASON and REMOTE_REASON fields,
12024 working much like those for circuit events.
12025 - There's now a GETINFO ns/... field so that controllers can ask Tor
12026 about the current status of a router.
12027 - A new event type "NS" to inform a controller when our opinion of
12028 a router's status has changed.
12029 - Add a GETINFO events/names and GETINFO features/names so controllers
12030 can tell which events and features are supported.
12031 - A new CLEARDNSCACHE signal to allow controllers to clear the
12032 client-side DNS cache without expiring circuits.
12034 o Security bugfixes:
12035 - When the user sends a NEWNYM signal, clear the client-side DNS
12036 cache too. Otherwise we continue to act on previous information.
12039 - Avoid sending junk to controllers or segfaulting when a controller
12040 uses EVENT_NEW_DESC with verbose nicknames.
12041 - Stop triggering asserts if the controller tries to extend hidden
12042 service circuits (reported by mwenge).
12043 - Avoid infinite loop on unexpected controller input.
12044 - When the controller does a "GETINFO network-status", tell it
12045 about even those routers whose descriptors are very old, and use
12046 long nicknames where appropriate.
12047 - Change NT service functions to be loaded on demand. This lets us
12048 build with MinGW without breaking Tor for Windows 98 users.
12049 - Do DirPort reachability tests less often, since a single test
12050 chews through many circuits before giving up.
12051 - In the hidden service example in torrc.sample, stop recommending
12052 esoteric and discouraged hidden service options.
12053 - When stopping an NT service, wait up to 10 sec for it to actually
12054 stop. Patch from Matt Edman; resolves bug 295.
12055 - Fix handling of verbose nicknames with ORCONN controller events:
12056 make them show up exactly when requested, rather than exactly when
12058 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
12059 printing a duplicate "$" in the keys we send (reported by mwenge).
12060 - Correctly set maximum connection limit on Cygwin. (This time
12062 - Try to detect Windows correctly when cross-compiling.
12063 - Detect the size of the routers file correctly even if it is
12064 corrupted (on systems without mmap) or not page-aligned (on systems
12065 with mmap). This bug was harmless.
12066 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
12067 to open a stream fails; now we do in more cases. This should
12068 make clients able to find a good exit faster in some cases, since
12069 unhandleable requests will now get an error rather than timing out.
12070 - Resolve two memory leaks when rebuilding the on-disk router cache
12071 (reported by fookoowa).
12072 - Clean up minor code warnings suggested by the MIPSpro C compiler,
12073 and reported by some Centos users.
12074 - Controller signals now work on non-Unix platforms that don't define
12075 SIGUSR1 and SIGUSR2 the way we expect.
12076 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
12077 values before failing, and always enables eventdns.
12078 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
12079 Try to fix this in configure.in by checking for most functions
12080 before we check for libevent.
12083 Changes in version 0.1.2.2-alpha - 2006-10-07
12085 - Make our async eventdns library on-by-default for Tor servers,
12086 and plan to deprecate the separate dnsworker threads.
12087 - Add server-side support for "reverse" DNS lookups (using PTR
12088 records so clients can determine the canonical hostname for a given
12089 IPv4 address). Only supported by servers using eventdns; servers
12090 now announce in their descriptors whether they support eventdns.
12091 - Specify and implement client-side SOCKS5 interface for reverse DNS
12092 lookups (see doc/socks-extensions.txt).
12093 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
12094 connect to directory servers through Tor. Previously, clients needed
12095 to find Tor exits to make private connections to directory servers.
12096 - Avoid choosing Exit nodes for entry or middle hops when the
12097 total bandwidth available from non-Exit nodes is much higher than
12098 the total bandwidth available from Exit nodes.
12099 - Workaround for name servers (like Earthlink's) that hijack failing
12100 DNS requests and replace the no-such-server answer with a "helpful"
12101 redirect to an advertising-driven search portal. Also work around
12102 DNS hijackers who "helpfully" decline to hijack known-invalid
12103 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
12104 lets you turn it off.
12105 - Send out a burst of long-range padding cells once we've established
12106 that we're reachable. Spread them over 4 circuits, so hopefully
12107 a few will be fast. This exercises our bandwidth and bootstraps
12108 us into the directory more quickly.
12110 o New/improved config options:
12111 - Add new config option "ResolvConf" to let the server operator
12112 choose an alternate resolve.conf file when using eventdns.
12113 - Add an "EnforceDistinctSubnets" option to control our "exclude
12114 servers on the same /16" behavior. It's still on by default; this
12115 is mostly for people who want to operate private test networks with
12116 all the machines on the same subnet.
12117 - If one of our entry guards is on the ExcludeNodes list, or the
12118 directory authorities don't think it's a good guard, treat it as
12119 if it were unlisted: stop using it as a guard, and throw it off
12120 the guards list if it stays that way for a long time.
12121 - Allow directory authorities to be marked separately as authorities
12122 for the v1 directory protocol, the v2 directory protocol, and
12123 as hidden service directories, to make it easier to retire old
12124 authorities. V1 authorities should set "HSAuthoritativeDir 1"
12125 to continue being hidden service authorities too.
12126 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
12128 o Minor features, controller:
12129 - Fix CIRC controller events so that controllers can learn the
12130 identity digests of non-Named servers used in circuit paths.
12131 - Let controllers ask for more useful identifiers for servers. Instead
12132 of learning identity digests for un-Named servers and nicknames
12133 for Named servers, the new identifiers include digest, nickname,
12134 and indication of Named status. Off by default; see control-spec.txt
12135 for more information.
12136 - Add a "getinfo address" controller command so it can display Tor's
12137 best guess to the user.
12138 - New controller event to alert the controller when our server
12139 descriptor has changed.
12140 - Give more meaningful errors on controller authentication failure.
12142 o Minor features, other:
12143 - When asked to resolve a hostname, don't use non-exit servers unless
12144 requested to do so. This allows servers with broken DNS to be
12145 useful to the network.
12146 - Divide eventdns log messages into warn and info messages.
12147 - Reserve the nickname "Unnamed" for routers that can't pick
12148 a hostname: any router can call itself Unnamed; directory
12149 authorities will never allocate Unnamed to any particular router;
12150 clients won't believe that any router is the canonical Unnamed.
12151 - Only include function names in log messages for info/debug messages.
12152 For notice/warn/err, the content of the message should be clear on
12153 its own, and printing the function name only confuses users.
12154 - Avoid some false positives during reachability testing: don't try
12155 to test via a server that's on the same /24 as us.
12156 - If we fail to build a circuit to an intended enclave, and it's
12157 not mandatory that we use that enclave, stop wanting it.
12158 - When eventdns is enabled, allow multithreaded builds on NetBSD and
12159 OpenBSD. (We had previously disabled threads on these platforms
12160 because they didn't have working thread-safe resolver functions.)
12162 o Major bugfixes, anonymity/security:
12163 - If a client asked for a server by name, and there's a named server
12164 in our network-status but we don't have its descriptor yet, we
12165 could return an unnamed server instead.
12166 - Fix NetBSD bug that could allow someone to force uninitialized RAM
12167 to be sent to a server's DNS resolver. This only affects NetBSD
12168 and other platforms that do not bounds-check tolower().
12169 - Reject (most) attempts to use Tor circuits with length one. (If
12170 many people start using Tor as a one-hop proxy, exit nodes become
12171 a more attractive target for compromise.)
12172 - Just because your DirPort is open doesn't mean people should be
12173 able to remotely teach you about hidden service descriptors. Now
12174 only accept rendezvous posts if you've got HSAuthoritativeDir set.
12176 o Major bugfixes, other:
12177 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
12178 - When a client asks the server to resolve (not connect to)
12179 an address, and it has a cached answer, give them the cached answer.
12180 Previously, the server would give them no answer at all.
12181 - Allow really slow clients to not hang up five minutes into their
12182 directory downloads (suggested by Adam J. Richter).
12183 - We were building exactly the wrong circuits when we anticipated
12184 hidden service requirements, meaning Tor would have to build all
12185 its circuits on demand.
12186 - Avoid crashing when we mmap a router cache file of size 0.
12187 - When testing reachability of our DirPort, don't launch new
12188 tests when there's already one in progress -- unreachable
12189 servers were stacking up dozens of testing streams.
12191 o Minor bugfixes, correctness:
12192 - If we're a directory mirror and we ask for "all" network status
12193 documents, we would discard status documents from authorities
12194 we don't recognize.
12195 - Avoid a memory corruption bug when creating a hash table for
12197 - Avoid controller-triggered crash when misusing certain commands
12198 from a v0 controller on platforms that do not handle
12199 printf("%s",NULL) gracefully.
12200 - Don't crash when a controller sends a third argument to an
12201 "extendcircuit" request.
12202 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12203 response; fix error code when "getinfo dir/status/" fails.
12204 - Avoid crash when telling controller stream-status and a stream
12206 - Patch from Adam Langley to fix assert() in eventdns.c.
12207 - Fix a debug log message in eventdns to say "X resolved to Y"
12208 instead of "X resolved to X".
12209 - Make eventdns give strings for DNS errors, not just error numbers.
12210 - Track unreachable entry guards correctly: don't conflate
12211 'unreachable by us right now' with 'listed as down by the directory
12212 authorities'. With the old code, if a guard was unreachable by
12213 us but listed as running, it would clog our guard list forever.
12214 - Behave correctly in case we ever have a network with more than
12215 2GB/s total advertised capacity.
12216 - Make TrackExitHosts case-insensitive, and fix the behavior of
12217 ".suffix" TrackExitHosts items to avoid matching in the middle of
12219 - Finally fix the openssl warnings from newer gccs that believe that
12220 ignoring a return value is okay, but casting a return value and
12221 then ignoring it is a sign of madness.
12222 - Prevent the contrib/exitlist script from printing the same
12223 result more than once.
12224 - Patch from Steve Hildrey: Generate network status correctly on
12225 non-versioning dirservers.
12226 - Don't listen to the X-Your-Address-Is hint if you did the lookup
12227 via Tor; otherwise you'll think you're the exit node's IP address.
12229 o Minor bugfixes, performance:
12230 - Two small performance improvements on parsing descriptors.
12231 - Major performance improvement on inserting descriptors: change
12232 algorithm from O(n^2) to O(n).
12233 - Make the common memory allocation path faster on machines where
12234 malloc(0) returns a pointer.
12235 - Start remembering X-Your-Address-Is directory hints even if you're
12236 a client, so you can become a server more smoothly.
12237 - Avoid duplicate entries on MyFamily line in server descriptor.
12239 o Packaging, features:
12240 - Remove architecture from OS X builds. The official builds are
12241 now universal binaries.
12242 - The Debian package now uses --verify-config when (re)starting,
12243 to distinguish configuration errors from other errors.
12244 - Update RPMs to require libevent 1.1b.
12246 o Packaging, bugfixes:
12247 - Patches so Tor builds with MinGW on Windows.
12248 - Patches so Tor might run on Cygwin again.
12249 - Resume building on non-gcc compilers and ancient gcc. Resume
12250 building with the -O0 compile flag. Resume building cleanly on
12252 - Run correctly on OS X platforms with case-sensitive filesystems.
12253 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
12254 - Add autoconf checks so Tor can build on Solaris x86 again.
12257 - Documented (and renamed) ServerDNSSearchDomains and
12258 ServerDNSResolvConfFile options.
12259 - Be clearer that the *ListenAddress directives can be repeated
12263 Changes in version 0.1.1.24 - 2006-09-29
12265 - Allow really slow clients to not hang up five minutes into their
12266 directory downloads (suggested by Adam J. Richter).
12267 - Fix major performance regression from 0.1.0.x: instead of checking
12268 whether we have enough directory information every time we want to
12269 do something, only check when the directory information has changed.
12270 This should improve client CPU usage by 25-50%.
12271 - Don't crash if, after a server has been running for a while,
12272 it can't resolve its hostname.
12275 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12276 - Don't crash when the controller receives a third argument to an
12277 "extendcircuit" request.
12278 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12279 response; fix error code when "getinfo dir/status/" fails.
12280 - Fix configure.in to not produce broken configure files with
12281 more recent versions of autoconf. Thanks to Clint for his auto*
12283 - Fix security bug on NetBSD that could allow someone to force
12284 uninitialized RAM to be sent to a server's DNS resolver. This
12285 only affects NetBSD and other platforms that do not bounds-check
12287 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
12288 methods: these are known to be buggy.
12289 - If we're a directory mirror and we ask for "all" network status
12290 documents, we would discard status documents from authorities
12291 we don't recognize.
12294 Changes in version 0.1.2.1-alpha - 2006-08-27
12296 - Add "eventdns" async dns library from Adam Langley, tweaked to
12297 build on OSX and Windows. Only enabled if you pass the
12298 --enable-eventdns argument to configure.
12299 - Allow servers with no hostname or IP address to learn their
12300 IP address by asking the directory authorities. This code only
12301 kicks in when you would normally have exited with a "no address"
12302 error. Nothing's authenticated, so use with care.
12303 - Rather than waiting a fixed amount of time between retrying
12304 application connections, we wait only 5 seconds for the first,
12305 10 seconds for the second, and 15 seconds for each retry after
12306 that. Hopefully this will improve the expected user experience.
12307 - Patch from Tup to add support for transparent AP connections:
12308 this basically bundles the functionality of trans-proxy-tor
12309 into the Tor mainline. Now hosts with compliant pf/netfilter
12310 implementations can redirect TCP connections straight to Tor
12311 without diverting through SOCKS. Needs docs.
12312 - Busy directory servers save lots of memory by spooling server
12313 descriptors, v1 directories, and v2 networkstatus docs to buffers
12314 as needed rather than en masse. Also mmap the cached-routers
12315 files, so we don't need to keep the whole thing in memory too.
12316 - Automatically avoid picking more than one node from the same
12317 /16 network when constructing a circuit.
12318 - Revise and clean up the torrc.sample that we ship with; add
12319 a section for BandwidthRate and BandwidthBurst.
12322 - Split circuit_t into origin_circuit_t and or_circuit_t, and
12323 split connection_t into edge, or, dir, control, and base structs.
12324 These will save quite a bit of memory on busy servers, and they'll
12325 also help us track down bugs in the code and bugs in the spec.
12326 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
12327 or later. Log when we are doing this, so we can diagnose it when
12328 it fails. (Also, recommend libevent 1.1b for kqueue and
12329 win32 methods; deprecate libevent 1.0b harder; make libevent
12330 recommendation system saner.)
12331 - Start being able to build universal binaries on OS X (thanks
12333 - Export the default exit policy via the control port, so controllers
12334 don't need to guess what it is / will be later.
12335 - Add a man page entry for ProtocolWarnings.
12336 - Add TestVia config option to the man page.
12337 - Remove even more protocol-related warnings from Tor server logs,
12338 such as bad TLS handshakes and malformed begin cells.
12339 - Stop fetching descriptors if you're not a dir mirror and you
12340 haven't tried to establish any circuits lately. [This currently
12341 causes some dangerous behavior, because when you start up again
12342 you'll use your ancient server descriptors.]
12343 - New DirPort behavior: if you have your dirport set, you download
12344 descriptors aggressively like a directory mirror, whether or not
12345 your ORPort is set.
12346 - Get rid of the router_retry_connections notion. Now routers
12347 no longer try to rebuild long-term connections to directory
12348 authorities, and directory authorities no longer try to rebuild
12349 long-term connections to all servers. We still don't hang up
12350 connections in these two cases though -- we need to look at it
12351 more carefully to avoid flapping, and we likely need to wait til
12352 0.1.1.x is obsolete.
12353 - Drop compatibility with obsolete Tors that permit create cells
12354 to have the wrong circ_id_type.
12355 - Re-enable per-connection rate limiting. Get rid of the "OP
12356 bandwidth" concept. Lay groundwork for "bandwidth classes" --
12357 separate global buckets that apply depending on what sort of conn
12359 - Start publishing one minute or so after we find our ORPort
12360 to be reachable. This will help reduce the number of descriptors
12361 we have for ourselves floating around, since it's quite likely
12362 other things (e.g. DirPort) will change during that minute too.
12363 - Fork the v1 directory protocol into its own spec document,
12364 and mark dir-spec.txt as the currently correct (v2) spec.
12367 - When we find our DirPort to be reachable, publish a new descriptor
12368 so we'll tell the world (reported by pnx).
12369 - Publish a new descriptor after we hup/reload. This is important
12370 if our config has changed such that we'll want to start advertising
12371 our DirPort now, etc.
12372 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12373 - When we have a state file we cannot parse, tell the user and
12374 move it aside. Now we avoid situations where the user starts
12375 Tor in 1904, Tor writes a state file with that timestamp in it,
12376 the user fixes her clock, and Tor refuses to start.
12377 - Fix configure.in to not produce broken configure files with
12378 more recent versions of autoconf. Thanks to Clint for his auto*
12380 - "tor --verify-config" now exits with -1(255) or 0 depending on
12381 whether the config options are bad or good.
12382 - Resolve bug 321 when using dnsworkers: append a period to every
12383 address we resolve at the exit node, so that we do not accidentally
12384 pick up local addresses, and so that failing searches are retried
12385 in the resolver search domains. (This is already solved for
12386 eventdns.) (This breaks Blossom servers for now.)
12387 - If we are using an exit enclave and we can't connect, e.g. because
12388 its webserver is misconfigured to not listen on localhost, then
12389 back off and try connecting from somewhere else before we fail.
12392 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
12393 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
12394 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
12395 when the IP address is mapped through MapAddress to a hostname.
12396 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
12397 useless IPv6 DNS resolves.
12398 - Patch suggested by Karsten Loesing: respond to SIGNAL command
12399 before we execute the signal, in case the signal shuts us down.
12400 - Clean up AllowInvalidNodes man page entry.
12401 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
12402 - Add more asserts to track down an assert error on a windows Tor
12403 server with connection_add being called with socket == -1.
12404 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
12405 - Fix misleading log messages: an entry guard that is "unlisted",
12406 as well as not known to be "down" (because we've never heard
12407 of it), is not therefore "up".
12408 - Remove code to special-case "-cvs" ending, since it has not
12409 actually mattered since 0.0.9.
12410 - Make our socks5 handling more robust to broken socks clients:
12411 throw out everything waiting on the buffer in between socks
12412 handshake phases, since they can't possibly (so the theory
12413 goes) have predicted what we plan to respond to them.
12416 Changes in version 0.1.1.23 - 2006-07-30
12418 - Fast Tor servers, especially exit nodes, were triggering asserts
12419 due to a bug in handling the list of pending DNS resolves. Some
12420 bugs still remain here; we're hunting them.
12421 - Entry guards could crash clients by sending unexpected input.
12422 - More fixes on reachability testing: if you find yourself reachable,
12423 then don't ever make any client requests (so you stop predicting
12424 circuits), then hup or have your clock jump, then later your IP
12425 changes, you won't think circuits are working, so you won't try to
12426 test reachability, so you won't publish.
12429 - Avoid a crash if the controller does a resetconf firewallports
12430 and then a setconf fascistfirewall=1.
12431 - Avoid an integer underflow when the dir authority decides whether
12432 a router is stable: we might wrongly label it stable, and compute
12433 a slightly wrong median stability, when a descriptor is published
12435 - Fix a place where we might trigger an assert if we can't build our
12436 own server descriptor yet.
12439 Changes in version 0.1.1.22 - 2006-07-05
12441 - Fix a big bug that was causing servers to not find themselves
12442 reachable if they changed IP addresses. Since only 0.1.1.22+
12443 servers can do reachability testing correctly, now we automatically
12444 make sure to test via one of these.
12445 - Fix to allow clients and mirrors to learn directory info from
12446 descriptor downloads that get cut off partway through.
12447 - Directory authorities had a bug in deciding if a newly published
12448 descriptor was novel enough to make everybody want a copy -- a few
12449 servers seem to be publishing new descriptors many times a minute.
12451 - Fix a rare bug that was causing some servers to complain about
12452 "closing wedged cpuworkers" and skip some circuit create requests.
12453 - Make the Exit flag in directory status documents actually work.
12456 Changes in version 0.1.1.21 - 2006-06-10
12457 o Crash and assert fixes from 0.1.1.20:
12458 - Fix a rare crash on Tor servers that have enabled hibernation.
12459 - Fix a seg fault on startup for Tor networks that use only one
12460 directory authority.
12461 - Fix an assert from a race condition that occurs on Tor servers
12462 while exiting, where various threads are trying to log that they're
12463 exiting, and delete the logs, at the same time.
12464 - Make our unit tests pass again on certain obscure platforms.
12467 - Add support for building SUSE RPM packages.
12468 - Speed up initial bootstrapping for clients: if we are making our
12469 first ever connection to any entry guard, then don't mark it down
12471 - When only one Tor server in the network is labelled as a guard,
12472 and we've already picked him, we would cycle endlessly picking him
12473 again, being unhappy about it, etc. Now we specifically exclude
12474 current guards when picking a new guard.
12475 - Servers send create cells more reliably after the TLS connection
12476 is established: we were sometimes forgetting to send half of them
12477 when we had more than one pending.
12478 - If we get a create cell that asks us to extend somewhere, but the
12479 Tor server there doesn't match the expected digest, we now send
12480 a destroy cell back, rather than silently doing nothing.
12481 - Make options->RedirectExit work again.
12482 - Make cookie authentication for the controller work again.
12483 - Stop being picky about unusual characters in the arguments to
12484 mapaddress. It's none of our business.
12485 - Add a new config option "TestVia" that lets you specify preferred
12486 middle hops to use for test circuits. Perhaps this will let me
12487 debug the reachability problems better.
12489 o Log / documentation fixes:
12490 - If we're a server and some peer has a broken TLS certificate, don't
12491 log about it unless ProtocolWarnings is set, i.e., we want to hear
12492 about protocol violations by others.
12493 - Fix spelling of VirtualAddrNetwork in man page.
12494 - Add a better explanation at the top of the autogenerated torrc file
12495 about what happened to our old torrc.
12498 Changes in version 0.1.1.20 - 2006-05-23
12500 - Downgrade a log severity where servers complain that they're
12502 - Avoid a compile warning on FreeBSD.
12503 - Remove string size limit on NEWDESC messages; solve bug 291.
12504 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
12505 more thoroughly when we're running on windows.
12508 Changes in version 0.1.1.19-rc - 2006-05-03
12510 - Regenerate our local descriptor if it's dirty and we try to use
12511 it locally (e.g. if it changes during reachability detection).
12512 - If we setconf our ORPort to 0, we continued to listen on the
12513 old ORPort and receive connections.
12514 - Avoid a second warning about machine/limits.h on Debian
12516 - Be willing to add our own routerinfo into the routerlist.
12517 Now authorities will include themselves in their directories
12518 and network-statuses.
12519 - Stop trying to upload rendezvous descriptors to every
12520 directory authority: only try the v1 authorities.
12521 - Servers no longer complain when they think they're not
12522 registered with the directory authorities. There were too many
12524 - Backport dist-rpm changes so rpms can be built without errors.
12527 - Implement an option, VirtualAddrMask, to set which addresses
12528 get handed out in response to mapaddress requests. This works
12529 around a bug in tsocks where 127.0.0.0/8 is never socksified.
12532 Changes in version 0.1.1.18-rc - 2006-04-10
12534 - Work harder to download live network-statuses from all the
12535 directory authorities we know about. Improve the threshold
12536 decision logic so we're more robust to edge cases.
12537 - When fetching rendezvous descriptors, we were willing to ask
12538 v2 authorities too, which would always return 404.
12541 - Stop listing down or invalid nodes in the v1 directory. This will
12542 reduce its bulk by about 1/3, and reduce load on directory
12544 - When deciding whether a router is Fast or Guard-worthy, consider
12545 his advertised BandwidthRate and not just the BandwidthCapacity.
12546 - No longer ship INSTALL and README files -- they are useless now.
12547 - Force rpmbuild to behave and honor target_cpu.
12548 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
12549 - Start to include translated versions of the tor-doc-*.html
12550 files, along with the screenshots. Still needs more work.
12551 - Start sending back 512 and 451 errors if mapaddress fails,
12552 rather than not sending anything back at all.
12553 - When we fail to bind or listen on an incoming or outgoing
12554 socket, we should close it before failing. otherwise we just
12555 leak it. (thanks to weasel for finding.)
12556 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
12557 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
12558 - Make NoPublish (even though deprecated) work again.
12559 - Fix a minor security flaw where a versioning auth dirserver
12560 could list a recommended version many times in a row to make
12561 clients more convinced that it's recommended.
12562 - Fix crash bug if there are two unregistered servers running
12563 with the same nickname, one of them is down, and you ask for
12564 them by nickname in your EntryNodes or ExitNodes. Also, try
12565 to pick the one that's running rather than an arbitrary one.
12566 - Fix an infinite loop we could hit if we go offline for too long.
12567 - Complain when we hit WSAENOBUFS on recv() or write() too.
12568 Perhaps this will help us hunt the bug.
12569 - If you're not a versioning dirserver, don't put the string
12570 "client-versions \nserver-versions \n" in your network-status.
12571 - Lower the minimum required number of file descriptors to 1000,
12572 so we can have some overhead for Valgrind on Linux, where the
12573 default ulimit -n is 1024.
12576 - Add tor.dizum.com as the fifth authoritative directory server.
12577 - Add a new config option FetchUselessDescriptors, off by default,
12578 for when you plan to run "exitlist" on your client and you want
12579 to know about even the non-running descriptors.
12582 Changes in version 0.1.1.17-rc - 2006-03-28
12584 - Clients and servers since 0.1.1.10-alpha have been expiring
12585 connections whenever they are idle for 5 minutes and they *do*
12586 have circuits on them. Oops. With this new version, clients will
12587 discard their previous entry guard choices and avoid choosing
12588 entry guards running these flawed versions.
12589 - Fix memory leak when uncompressing concatenated zlib streams. This
12590 was causing substantial leaks over time on Tor servers.
12591 - The v1 directory was including servers as much as 48 hours old,
12592 because that's how the new routerlist->routers works. Now only
12593 include them if they're 20 hours old or less.
12596 - Resume building on irix64, netbsd 2.0, etc.
12597 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
12599 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
12600 and it is confusing some users.
12601 - Mirrors stop caching the v1 directory so often.
12602 - Make the max number of old descriptors that a cache will hold
12603 rise with the number of directory authorities, so we can scale.
12604 - Change our win32 uname() hack to be more forgiving about what
12605 win32 versions it thinks it's found.
12608 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
12610 - When the controller's *setconf commands fail, collect an error
12611 message in a string and hand it back to the controller.
12612 - Make the v2 dir's "Fast" flag based on relative capacity, just
12613 like "Stable" is based on median uptime. Name everything in the
12614 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
12615 - Log server fingerprint on startup, so new server operators don't
12616 have to go hunting around their filesystem for it.
12617 - Return a robots.txt on our dirport to discourage google indexing.
12618 - Let the controller ask for GETINFO dir/status/foo so it can ask
12619 directly rather than connecting to the dir port. Only works when
12620 dirport is set for now.
12622 o New config options rather than constants in the code:
12623 - SocksTimeout: How long do we let a socks connection wait
12624 unattached before we fail it?
12625 - CircuitBuildTimeout: Cull non-open circuits that were born
12626 at least this many seconds ago.
12627 - CircuitIdleTimeout: Cull open clean circuits that were born
12628 at least this many seconds ago.
12631 Changes in version 0.1.1.16-rc - 2006-03-18
12632 o Bugfixes on 0.1.1.15-rc:
12633 - Fix assert when the controller asks to attachstream a connect-wait
12634 or resolve-wait stream.
12635 - Now do address rewriting when the controller asks us to attach
12636 to a particular circuit too. This will let Blossom specify
12637 "moria2.exit" without having to learn what moria2's IP address is.
12638 - Make the "tor --verify-config" command-line work again, so people
12639 can automatically check if their torrc will parse.
12640 - Authoritative dirservers no longer require an open connection from
12641 a server to consider him "reachable". We need this change because
12642 when we add new auth dirservers, old servers won't know not to
12644 - Let Tor build on Sun CC again.
12645 - Fix an off-by-one buffer size in dirserv.c that magically never
12646 hit our three authorities but broke sjmurdoch's own tor network.
12647 - If we as a directory mirror don't know of any v1 directory
12648 authorities, then don't try to cache any v1 directories.
12649 - Stop warning about unknown servers in our family when they are
12650 given as hex digests.
12651 - Stop complaining as quickly to the server operator that he
12652 hasn't registered his nickname/key binding.
12653 - Various cleanups so we can add new V2 Auth Dirservers.
12654 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
12655 reflect the updated flags in our v2 dir protocol.
12656 - Resume allowing non-printable characters for exit streams (both
12657 for connecting and for resolving). Now we tolerate applications
12658 that don't follow the RFCs. But continue to block malformed names
12661 o Bugfixes on 0.1.0.x:
12662 - Fix assert bug in close_logs(): when we close and delete logs,
12663 remove them all from the global "logfiles" list.
12664 - Fix minor integer overflow in calculating when we expect to use up
12665 our bandwidth allocation before hibernating.
12666 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
12667 there are multiple SSLs installed with different versions.
12668 - When we try to be a server and Address is not explicitly set and
12669 our hostname resolves to a private IP address, try to use an
12670 interface address if it has a public address. Now Windows machines
12671 that think of themselves as localhost can work by default.
12674 - Let the controller ask for GETINFO dir/server/foo so it can ask
12675 directly rather than connecting to the dir port.
12676 - Let the controller tell us about certain router descriptors
12677 that it doesn't want Tor to use in circuits. Implement
12678 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
12679 - New config option SafeSocks to reject all application connections
12680 using unsafe socks protocols. Defaults to off.
12683 Changes in version 0.1.1.15-rc - 2006-03-11
12684 o Bugfixes and cleanups:
12685 - When we're printing strings from the network, don't try to print
12686 non-printable characters. This protects us against shell escape
12687 sequence exploits, and also against attacks to fool humans into
12688 misreading their logs.
12689 - Fix a bug where Tor would fail to establish any connections if you
12690 left it off for 24 hours and then started it: we were happy with
12691 the obsolete network statuses, but they all referred to router
12692 descriptors that were too old to fetch, so we ended up with no
12693 valid router descriptors.
12694 - Fix a seg fault in the controller's "getinfo orconn-status"
12695 command while listing status on incoming handshaking connections.
12696 Introduce a status name "NEW" for these connections.
12697 - If we get a linelist or linelist_s config option from the torrc
12698 (e.g. ExitPolicy) and it has no value, warn and skip rather than
12699 silently resetting it to its default.
12700 - Don't abandon entry guards until they've been down or gone for
12702 - Cleaner and quieter log messages.
12705 - New controller signal NEWNYM that makes new application requests
12706 use clean circuits.
12707 - Add a new circuit purpose 'controller' to let the controller ask
12708 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
12709 controller command to let you specify the purpose if you're
12710 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
12711 command to let you change a circuit's purpose after it's been
12713 - Accept "private:*" in routerdesc exit policies; not generated yet
12714 because older Tors do not understand it.
12715 - Add BSD-style contributed startup script "rc.subr" from Peter
12719 Changes in version 0.1.1.14-alpha - 2006-02-20
12720 o Bugfixes on 0.1.1.x:
12721 - Don't die if we ask for a stdout or stderr log (even implicitly)
12722 and we're set to RunAsDaemon -- just warn.
12723 - We still had a few bugs in the OR connection rotation code that
12724 caused directory servers to slowly aggregate connections to other
12725 fast Tor servers. This time for sure!
12726 - Make log entries on Win32 include the name of the function again.
12727 - We were treating a pair of exit policies if they were equal even
12728 if one said accept and the other said reject -- causing us to
12729 not always publish a new descriptor since we thought nothing
12731 - Retry pending server downloads as well as pending networkstatus
12732 downloads when we unexpectedly get a socks request.
12733 - We were ignoring the IS_FAST flag in the directory status,
12734 meaning we were willing to pick trivial-bandwidth nodes for "fast"
12736 - If the controller's SAVECONF command fails (e.g. due to file
12737 permissions), let the controller know that it failed.
12740 - If we're trying to be a Tor server and running Windows 95/98/ME
12741 as a server, explain that we'll likely crash.
12742 - When we're a server, a client asks for an old-style directory,
12743 and our write bucket is empty, don't give it to him. This way
12744 small servers can continue to serve the directory *sometimes*,
12745 without getting overloaded.
12746 - Compress exit policies even more -- look for duplicate lines
12748 - Clients now honor the "guard" flag in the router status when
12749 picking entry guards, rather than looking at is_fast or is_stable.
12750 - Retain unrecognized lines in $DATADIR/state file, so that we can
12751 be forward-compatible.
12752 - Generate 18.0.0.0/8 address policy format in descs when we can;
12753 warn when the mask is not reducible to a bit-prefix.
12754 - Let the user set ControlListenAddress in the torrc. This can be
12755 dangerous, but there are some cases (like a secured LAN) where it
12757 - Split ReachableAddresses into ReachableDirAddresses and
12758 ReachableORAddresses, so we can restrict Dir conns to port 80
12759 and OR conns to port 443.
12760 - Now we can target arch and OS in rpm builds (contributed by
12761 Phobos). Also make the resulting dist-rpm filename match the
12763 - New config options to help controllers: FetchServerDescriptors
12764 and FetchHidServDescriptors for whether to fetch server
12765 info and hidserv info or let the controller do it, and
12766 PublishServerDescriptor and PublishHidServDescriptors.
12767 - Also let the controller set the __AllDirActionsPrivate config
12768 option if you want all directory fetches/publishes to happen via
12769 Tor (it assumes your controller bootstraps your circuits).
12772 Changes in version 0.1.0.17 - 2006-02-17
12773 o Crash bugfixes on 0.1.0.x:
12774 - When servers with a non-zero DirPort came out of hibernation,
12775 sometimes they would trigger an assert.
12777 o Other important bugfixes:
12778 - On platforms that don't have getrlimit (like Windows), we were
12779 artificially constraining ourselves to a max of 1024
12780 connections. Now just assume that we can handle as many as 15000
12781 connections. Hopefully this won't cause other problems.
12783 o Backported features:
12784 - When we're a server, a client asks for an old-style directory,
12785 and our write bucket is empty, don't give it to him. This way
12786 small servers can continue to serve the directory *sometimes*,
12787 without getting overloaded.
12788 - Whenever you get a 503 in response to a directory fetch, try
12789 once more. This will become important once servers start sending
12790 503's whenever they feel busy.
12791 - Fetch a new directory every 120 minutes, not every 40 minutes.
12792 Now that we have hundreds of thousands of users running the old
12793 directory algorithm, it's starting to hurt a lot.
12794 - Bump up the period for forcing a hidden service descriptor upload
12795 from 20 minutes to 1 hour.
12798 Changes in version 0.1.1.13-alpha - 2006-02-09
12799 o Crashes in 0.1.1.x:
12800 - When you tried to setconf ORPort via the controller, Tor would
12801 crash. So people using TorCP to become a server were sad.
12802 - Solve (I hope) the stack-smashing bug that we were seeing on fast
12803 servers. The problem appears to be something do with OpenSSL's
12804 random number generation, or how we call it, or something. Let me
12805 know if the crashes continue.
12806 - Turn crypto hardware acceleration off by default, until we find
12807 somebody smart who can test it for us. (It appears to produce
12808 seg faults in at least some cases.)
12809 - Fix a rare assert error when we've tried all intro points for
12810 a hidden service and we try fetching the service descriptor again:
12811 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
12814 - Fix a major load balance bug: we were round-robining in 16 KB
12815 chunks, and servers with bandwidthrate of 20 KB, while downloading
12816 a 600 KB directory, would starve their other connections. Now we
12817 try to be a bit more fair.
12818 - Dir authorities and mirrors were never expiring the newest
12819 descriptor for each server, causing memory and directory bloat.
12820 - Fix memory-bloating and connection-bloating bug on servers: We
12821 were never closing any connection that had ever had a circuit on
12822 it, because we were checking conn->n_circuits == 0, yet we had a
12823 bug that let it go negative.
12824 - Make Tor work using squid as your http proxy again -- squid
12825 returns an error if you ask for a URL that's too long, and it uses
12826 a really generic error message. Plus, many people are behind a
12827 transparent squid so they don't even realize it.
12828 - On platforms that don't have getrlimit (like Windows), we were
12829 artificially constraining ourselves to a max of 1024
12830 connections. Now just assume that we can handle as many as 15000
12831 connections. Hopefully this won't cause other problems.
12832 - Add a new config option ExitPolicyRejectPrivate which defaults to
12833 1. This means all exit policies will begin with rejecting private
12834 addresses, unless the server operator explicitly turns it off.
12837 - Clients no longer download descriptors for non-running
12839 - Before we add new directory authorities, we should make it
12840 clear that only v1 authorities should receive/publish hidden
12841 service descriptors.
12844 - As soon as we've fetched some more directory info, immediately
12845 try to download more server descriptors. This way we don't have
12846 a 10 second pause during initial bootstrapping.
12847 - Remove even more loud log messages that the server operator can't
12849 - When we're running an obsolete or un-recommended version, make
12850 the log message more clear about what the problem is and what
12851 versions *are* still recommended.
12852 - Provide a more useful warn message when our onion queue gets full:
12853 the CPU is too slow or the exit policy is too liberal.
12854 - Don't warn when we receive a 503 from a dirserver/cache -- this
12855 will pave the way for them being able to refuse if they're busy.
12856 - When we fail to bind a listener, try to provide a more useful
12857 log message: e.g., "Is Tor already running?"
12858 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
12859 Goldberg can prove things about our handshake protocol more
12861 - MaxConn has been obsolete for a while now. Document the ConnLimit
12862 config option, which is a *minimum* number of file descriptors
12863 that must be available else Tor refuses to start.
12864 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
12865 if you log to syslog and want something other than LOG_DAEMON.
12866 - Make dirservers generate a separate "guard" flag to mean,
12867 "would make a good entry guard". Make clients parse it and vote
12868 on it. Not used by clients yet.
12869 - Implement --with-libevent-dir option to ./configure. Also, improve
12870 search techniques to find libevent, and use those for openssl too.
12871 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
12872 - Only start testing reachability once we've established a
12873 circuit. This will make startup on dirservers less noisy.
12874 - Don't try to upload hidden service descriptors until we have
12875 established a circuit.
12876 - Fix the controller's "attachstream 0" command to treat conn like
12877 it just connected, doing address remapping, handling .exit and
12878 .onion idioms, and so on. Now we're more uniform in making sure
12879 that the controller hears about new and closing connections.
12882 Changes in version 0.1.1.12-alpha - 2006-01-11
12883 o Bugfixes on 0.1.1.x:
12884 - The fix to close duplicate server connections was closing all
12885 Tor client connections if they didn't establish a circuit
12886 quickly enough. Oops.
12887 - Fix minor memory issue (double-free) that happened on exit.
12889 o Bugfixes on 0.1.0.x:
12890 - Tor didn't warn when it failed to open a log file.
12893 Changes in version 0.1.1.11-alpha - 2006-01-10
12894 o Crashes in 0.1.1.x:
12895 - Include all the assert/crash fixes from 0.1.0.16.
12896 - If you start Tor and then quit very quickly, there were some
12897 races that tried to free things that weren't allocated yet.
12898 - Fix a rare memory stomp if you're running hidden services.
12899 - Fix segfault when specifying DirServer in config without nickname.
12900 - Fix a seg fault when you finish connecting to a server but at
12901 that moment you dump his server descriptor.
12902 - Extendcircuit and Attachstream controller commands would
12903 assert/crash if you don't give them enough arguments.
12904 - Fix an assert error when we're out of space in the connection_list
12905 and we try to post a hidden service descriptor (reported by weasel).
12906 - If you specify a relative torrc path and you set RunAsDaemon in
12907 your torrc, then it chdir()'s to the new directory. If you HUP,
12908 it tries to load the new torrc location, fails, and exits.
12909 The fix: no longer allow a relative path to torrc using -f.
12912 - Implement "entry guards": automatically choose a handful of entry
12913 nodes and stick with them for all circuits. Only pick new guards
12914 when the ones you have are unsuitable, and if the old guards
12915 become suitable again, switch back. This will increase security
12916 dramatically against certain end-point attacks. The EntryNodes
12917 config option now provides some hints about which entry guards you
12918 want to use most; and StrictEntryNodes means to only use those.
12919 - New directory logic: download by descriptor digest, not by
12920 fingerprint. Caches try to download all listed digests from
12921 authorities; clients try to download "best" digests from caches.
12922 This avoids partitioning and isolating attacks better.
12923 - Make the "stable" router flag in network-status be the median of
12924 the uptimes of running valid servers, and make clients pay
12925 attention to the network-status flags. Thus the cutoff adapts
12926 to the stability of the network as a whole, making IRC, IM, etc
12927 connections more reliable.
12930 - Tor servers with dynamic IP addresses were needing to wait 18
12931 hours before they could start doing reachability testing using
12932 the new IP address and ports. This is because they were using
12933 the internal descriptor to learn what to test, yet they were only
12934 rebuilding the descriptor once they decided they were reachable.
12935 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
12936 to download certain server descriptors, throw them away, and then
12937 fetch them again after 30 minutes. Now mirrors throw away these
12938 server descriptors so clients can't get them.
12939 - We were leaving duplicate connections to other ORs open for a week,
12940 rather than closing them once we detect a duplicate. This only
12941 really affected authdirservers, but it affected them a lot.
12942 - Spread the authdirservers' reachability testing over the entire
12943 testing interval, so we don't try to do 500 TLS's at once every
12947 - If the network is down, and we try to connect to a conn because
12948 we have a circuit in mind, and we timeout (30 seconds) because the
12949 network never answers, we were expiring the circuit, but we weren't
12950 obsoleting the connection or telling the entry_guards functions.
12951 - Some Tor servers process billions of cells per day. These statistics
12952 need to be uint64_t's.
12953 - Check for integer overflows in more places, when adding elements
12954 to smartlists. This could possibly prevent a buffer overflow
12955 on malicious huge inputs. I don't see any, but I haven't looked
12957 - ReachableAddresses kept growing new "reject *:*" lines on every
12959 - When you "setconf log" via the controller, it should remove all
12960 logs. We were automatically adding back in a "log notice stdout".
12961 - Newly bootstrapped Tor networks couldn't establish hidden service
12962 circuits until they had nodes with high uptime. Be more tolerant.
12963 - We were marking servers down when they could not answer every piece
12964 of the directory request we sent them. This was far too harsh.
12965 - Fix the torify (tsocks) config file to not use Tor for localhost
12967 - Directory authorities now go to the proper authority when asking for
12968 a networkstatus, even when they want a compressed one.
12969 - Fix a harmless bug that was causing Tor servers to log
12970 "Got an end because of misc error, but we're not an AP. Closing."
12971 - Authorities were treating their own descriptor changes as cosmetic,
12972 meaning the descriptor available in the network-status and the
12973 descriptor that clients downloaded were different.
12974 - The OS X installer was adding a symlink for tor_resolve but
12975 the binary was called tor-resolve (reported by Thomas Hardly).
12976 - Workaround a problem with some http proxies where they refuse GET
12977 requests that specify "Content-Length: 0" (reported by Adrian).
12978 - Fix wrong log message when you add a "HiddenServiceNodes" config
12979 line without any HiddenServiceDir line (reported by Chris Thomas).
12982 - Write the TorVersion into the state file so we have a prayer of
12983 keeping forward and backward compatibility.
12984 - Revive the FascistFirewall config option rather than eliminating it:
12985 now it's a synonym for ReachableAddresses *:80,*:443.
12986 - Clients choose directory servers from the network status lists,
12987 not from their internal list of router descriptors. Now they can
12988 go to caches directly rather than needing to go to authorities
12990 - Directory authorities ignore router descriptors that have only
12991 cosmetic differences: do this for 0.1.0.x servers now too.
12992 - Add a new flag to network-status indicating whether the server
12993 can answer v2 directory requests too.
12994 - Authdirs now stop whining so loudly about bad descriptors that
12995 they fetch from other dirservers. So when there's a log complaint,
12996 it's for sure from a freshly uploaded descriptor.
12997 - Reduce memory requirements in our structs by changing the order
12999 - There used to be two ways to specify your listening ports in a
13000 server descriptor: on the "router" line and with a separate "ports"
13001 line. Remove support for the "ports" line.
13002 - New config option "AuthDirRejectUnlisted" for auth dirservers as
13003 a panic button: if we get flooded with unusable servers we can
13004 revert to only listing servers in the approved-routers file.
13005 - Auth dir servers can now mark a fingerprint as "!reject" or
13006 "!invalid" in the approved-routers file (as its nickname), to
13007 refuse descriptors outright or include them but marked as invalid.
13008 - Servers store bandwidth history across restarts/crashes.
13009 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
13010 get a better idea of why their circuits failed. Not used yet.
13011 - Directory mirrors now cache up to 16 unrecognized network-status
13012 docs. Now we can add new authdirservers and they'll be cached too.
13013 - When picking a random directory, prefer non-authorities if any
13015 - New controller option "getinfo desc/all-recent" to fetch the
13016 latest server descriptor for every router that Tor knows about.
13019 Changes in version 0.1.0.16 - 2006-01-02
13020 o Crash bugfixes on 0.1.0.x:
13021 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
13022 corrupting the heap, losing FDs, or crashing when we need to resize
13023 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
13024 - It turns out sparc64 platforms crash on unaligned memory access
13025 too -- so detect and avoid this.
13026 - Handle truncated compressed data correctly (by detecting it and
13028 - Fix possible-but-unlikely free(NULL) in control.c.
13029 - When we were closing connections, there was a rare case that
13030 stomped on memory, triggering seg faults and asserts.
13031 - Avoid potential infinite recursion when building a descriptor. (We
13032 don't know that it ever happened, but better to fix it anyway.)
13033 - We were neglecting to unlink marked circuits from soon-to-close OR
13034 connections, which caused some rare scribbling on freed memory.
13035 - Fix a memory stomping race bug when closing the joining point of two
13036 rendezvous circuits.
13037 - Fix an assert in time parsing found by Steven Murdoch.
13039 o Other bugfixes on 0.1.0.x:
13040 - When we're doing reachability testing, provide more useful log
13041 messages so the operator knows what to expect.
13042 - Do not check whether DirPort is reachable when we are suppressing
13043 advertising it because of hibernation.
13044 - When building with -static or on Solaris, we sometimes needed -ldl.
13045 - When we're deciding whether a stream has enough circuits around
13046 that can handle it, count the freshly dirty ones and not the ones
13047 that are so dirty they won't be able to handle it.
13048 - When we're expiring old circuits, we had a logic error that caused
13049 us to close new rendezvous circuits rather than old ones.
13050 - Give a more helpful log message when you try to change ORPort via
13051 the controller: you should upgrade Tor if you want that to work.
13052 - We were failing to parse Tor versions that start with "Tor ".
13053 - Tolerate faulty streams better: when a stream fails for reason
13054 exitpolicy, stop assuming that the router is lying about his exit
13055 policy. When a stream fails for reason misc, allow it to retry just
13056 as if it was resolvefailed. When a stream has failed three times,
13057 reset its failure count so we can try again and get all three tries.
13060 Changes in version 0.1.1.10-alpha - 2005-12-11
13061 o Correctness bugfixes on 0.1.0.x:
13062 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
13063 corrupting the heap, losing FDs, or crashing when we need to resize
13064 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
13065 - Stop doing the complex voodoo overkill checking for insecure
13066 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
13067 - When we were closing connections, there was a rare case that
13068 stomped on memory, triggering seg faults and asserts.
13069 - We were neglecting to unlink marked circuits from soon-to-close OR
13070 connections, which caused some rare scribbling on freed memory.
13071 - When we're deciding whether a stream has enough circuits around
13072 that can handle it, count the freshly dirty ones and not the ones
13073 that are so dirty they won't be able to handle it.
13074 - Recover better from TCP connections to Tor servers that are
13075 broken but don't tell you (it happens!); and rotate TLS
13076 connections once a week.
13077 - When we're expiring old circuits, we had a logic error that caused
13078 us to close new rendezvous circuits rather than old ones.
13079 - Fix a scary-looking but apparently harmless bug where circuits
13080 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
13081 servers, and never switch to state CIRCUIT_STATE_OPEN.
13082 - When building with -static or on Solaris, we sometimes needed to
13084 - Give a useful message when people run Tor as the wrong user,
13085 rather than telling them to start chowning random directories.
13086 - We were failing to inform the controller about new .onion streams.
13088 o Security bugfixes on 0.1.0.x:
13089 - Refuse server descriptors if the fingerprint line doesn't match
13090 the included identity key. Tor doesn't care, but other apps (and
13091 humans) might actually be trusting the fingerprint line.
13092 - We used to kill the circuit when we receive a relay command we
13093 don't recognize. Now we just drop it.
13094 - Start obeying our firewall options more rigorously:
13095 . If we can't get to a dirserver directly, try going via Tor.
13096 . Don't ever try to connect (as a client) to a place our
13097 firewall options forbid.
13098 . If we specify a proxy and also firewall options, obey the
13099 firewall options even when we're using the proxy: some proxies
13100 can only proxy to certain destinations.
13101 - Fix a bug found by Lasse Overlier: when we were making internal
13102 circuits (intended to be cannibalized later for rendezvous and
13103 introduction circuits), we were picking them so that they had
13104 useful exit nodes. There was no need for this, and it actually
13105 aids some statistical attacks.
13106 - Start treating internal circuits and exit circuits separately.
13107 It's important to keep them separate because internal circuits
13108 have their last hops picked like middle hops, rather than like
13109 exit hops. So exiting on them will break the user's expectations.
13111 o Bugfixes on 0.1.1.x:
13112 - Take out the mis-feature where we tried to detect IP address
13113 flapping for people with DynDNS, and chose not to upload a new
13114 server descriptor sometimes.
13115 - Try to be compatible with OpenSSL 0.9.6 again.
13116 - Log fix: when the controller is logging about .onion addresses,
13117 sometimes it didn't include the ".onion" part of the address.
13118 - Don't try to modify options->DirServers internally -- if the
13119 user didn't specify any, just add the default ones directly to
13120 the trusted dirserver list. This fixes a bug where people running
13121 controllers would use SETCONF on some totally unrelated config
13122 option, and Tor would start yelling at them about changing their
13124 - Let the controller's redirectstream command specify a port, in
13125 case the controller wants to change that too.
13126 - When we requested a pile of server descriptors, we sometimes
13127 accidentally launched a duplicate request for the first one.
13128 - Bugfix for trackhostexits: write down the fingerprint of the
13129 chosen exit, not its nickname, because the chosen exit might not
13131 - When parsing foo.exit, if foo is unknown, and we are leaving
13132 circuits unattached, set the chosen_exit field and leave the
13133 address empty. This matters because controllers got confused
13135 - Directory authorities no longer try to download server
13136 descriptors that they know they will reject.
13138 o Features and updates:
13139 - Replace balanced trees with hash tables: this should make stuff
13140 significantly faster.
13141 - Resume using the AES counter-mode implementation that we ship,
13142 rather than OpenSSL's. Ours is significantly faster.
13143 - Many other CPU and memory improvements.
13144 - Add a new config option FastFirstHopPK (on by default) so clients
13145 do a trivial crypto handshake for their first hop, since TLS has
13146 already taken care of confidentiality and authentication.
13147 - Add a new config option TestSocks so people can see if their
13148 applications are using socks4, socks4a, socks5-with-ip, or
13149 socks5-with-hostname. This way they don't have to keep mucking
13150 with tcpdump and wondering if something got cached somewhere.
13151 - Warn when listening on a public address for socks. I suspect a
13152 lot of people are setting themselves up as open socks proxies,
13153 and they have no idea that jerks on the Internet are using them,
13154 since they simply proxy the traffic into the Tor network.
13155 - Add "private:*" as an alias in configuration for policies. Now
13156 you can simplify your exit policy rather than needing to list
13157 every single internal or nonroutable network space.
13158 - Add a new controller event type that allows controllers to get
13159 all server descriptors that were uploaded to a router in its role
13160 as authoritative dirserver.
13161 - Start shipping socks-extensions.txt, tor-doc-unix.html,
13162 tor-doc-server.html, and stylesheet.css in the tarball.
13163 - Stop shipping tor-doc.html in the tarball.
13166 Changes in version 0.1.1.9-alpha - 2005-11-15
13167 o Usability improvements:
13168 - Start calling it FooListenAddress rather than FooBindAddress,
13169 since few of our users know what it means to bind an address
13171 - Reduce clutter in server logs. We're going to try to make
13172 them actually usable now. New config option ProtocolWarnings that
13173 lets you hear about how _other Tors_ are breaking the protocol. Off
13175 - Divide log messages into logging domains. Once we put some sort
13176 of interface on this, it will let people looking at more verbose
13177 log levels specify the topics they want to hear more about.
13178 - Make directory servers return better http 404 error messages
13179 instead of a generic "Servers unavailable".
13180 - Check for even more Windows version flags when writing the platform
13181 string in server descriptors, and note any we don't recognize.
13182 - Clean up more of the OpenSSL memory when exiting, so we can detect
13183 memory leaks better.
13184 - Make directory authorities be non-versioning, non-naming by
13185 default. Now we can add new directory servers without requiring
13186 their operators to pay close attention.
13187 - When logging via syslog, include the pid whenever we provide
13188 a log entry. Suggested by Todd Fries.
13190 o Performance improvements:
13191 - Directory servers now silently throw away new descriptors that
13192 haven't changed much if the timestamps are similar. We do this to
13193 tolerate older Tor servers that upload a new descriptor every 15
13194 minutes. (It seemed like a good idea at the time.)
13195 - Inline bottleneck smartlist functions; use fast versions by default.
13196 - Add a "Map from digest to void*" abstraction digestmap_t so we
13197 can do less hex encoding/decoding. Use it in router_get_by_digest()
13198 to resolve a performance bottleneck.
13199 - Allow tor_gzip_uncompress to extract as much as possible from
13200 truncated compressed data. Try to extract as many
13201 descriptors as possible from truncated http responses (when
13202 DIR_PURPOSE_FETCH_ROUTERDESC).
13203 - Make circ->onionskin a pointer, not a static array. moria2 was using
13204 125000 circuit_t's after it had been up for a few weeks, which
13205 translates to 20+ megs of wasted space.
13206 - The private half of our EDH handshake keys are now chosen out
13207 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
13209 o Security improvements:
13210 - Start making directory caches retain old routerinfos, so soon
13211 clients can start asking by digest of descriptor rather than by
13212 fingerprint of server.
13213 - Add half our entropy from RAND_poll in OpenSSL. This knows how
13214 to use egd (if present), openbsd weirdness (if present), vms/os2
13215 weirdness (if we ever port there), and more in the future.
13217 o Bugfixes on 0.1.0.x:
13218 - Do round-robin writes of at most 16 kB per write. This might be
13219 more fair on loaded Tor servers, and it might resolve our Windows
13220 crash bug. It might also slow things down.
13221 - Our TLS handshakes were generating a single public/private
13222 keypair for the TLS context, rather than making a new one for
13223 each new connections. Oops. (But we were still rotating them
13224 periodically, so it's not so bad.)
13225 - When we were cannibalizing a circuit with a particular exit
13226 node in mind, we weren't checking to see if that exit node was
13227 already present earlier in the circuit. Oops.
13228 - When a Tor server's IP changes (e.g. from a dyndns address),
13229 upload a new descriptor so clients will learn too.
13230 - Really busy servers were keeping enough circuits open on stable
13231 connections that they were wrapping around the circuit_id
13232 space. (It's only two bytes.) This exposed a bug where we would
13233 feel free to reuse a circuit_id even if it still exists but has
13234 been marked for close. Try to fix this bug. Some bug remains.
13235 - If we would close a stream early (e.g. it asks for a .exit that
13236 we know would refuse it) but the LeaveStreamsUnattached config
13237 option is set by the controller, then don't close it.
13239 o Bugfixes on 0.1.1.8-alpha:
13240 - Fix a big pile of memory leaks, some of them serious.
13241 - Do not try to download a routerdesc if we would immediately reject
13243 - Resume inserting a newline between all router descriptors when
13244 generating (old style) signed directories, since our spec says
13246 - When providing content-type application/octet-stream for
13247 server descriptors using .z, we were leaving out the
13248 content-encoding header. Oops. (Everything tolerated this just
13249 fine, but that doesn't mean we need to be part of the problem.)
13250 - Fix a potential seg fault in getconf and getinfo using version 1
13251 of the controller protocol.
13252 - Avoid crash: do not check whether DirPort is reachable when we
13253 are suppressing it because of hibernation.
13254 - Make --hash-password not crash on exit.
13257 Changes in version 0.1.1.8-alpha - 2005-10-07
13258 o New features (major):
13259 - Clients don't download or use the directory anymore. Now they
13260 download and use network-statuses from the trusted dirservers,
13261 and fetch individual server descriptors as needed from mirrors.
13262 See dir-spec.txt for all the gory details.
13263 - Be more conservative about whether to advertise our DirPort.
13264 The main change is to not advertise if we're running at capacity
13265 and either a) we could hibernate or b) our capacity is low and
13266 we're using a default DirPort.
13267 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
13269 o New features (minor):
13270 - Try to be smart about when to retry network-status and
13271 server-descriptor fetches. Still needs some tuning.
13272 - Stop parsing, storing, or using running-routers output (but
13273 mirrors still cache and serve it).
13274 - Consider a threshold of versioning dirservers (dirservers who have
13275 an opinion about which Tor versions are still recommended) before
13276 deciding whether to warn the user that he's obsolete.
13277 - Dirservers can now reject/invalidate by key and IP, with the
13278 config options "AuthDirInvalid" and "AuthDirReject". This is
13279 useful since currently we automatically list servers as running
13280 and usable even if we know they're jerks.
13281 - Provide dire warnings to any users who set DirServer; move it out
13282 of torrc.sample and into torrc.complete.
13283 - Add MyFamily to torrc.sample in the server section.
13284 - Add nicknames to the DirServer line, so we can refer to them
13285 without requiring all our users to memorize their IP addresses.
13286 - When we get an EOF or a timeout on a directory connection, note
13287 how many bytes of serverdesc we are dropping. This will help
13288 us determine whether it is smart to parse incomplete serverdesc
13290 - Add a new function to "change pseudonyms" -- that is, to stop
13291 using any currently-dirty circuits for new streams, so we don't
13292 link new actions to old actions. Currently it's only called on
13293 HUP (or SIGNAL RELOAD).
13294 - On sighup, if UseHelperNodes changed to 1, use new circuits.
13295 - Start using RAND_bytes rather than RAND_pseudo_bytes from
13296 OpenSSL. Also, reseed our entropy every hour, not just at
13297 startup. And entropy in 512-bit chunks, not 160-bit chunks.
13299 o Fixes on 0.1.1.7-alpha:
13300 - Nobody ever implemented EVENT_ADDRMAP for control protocol
13301 version 0, so don't let version 0 controllers ask for it.
13302 - If you requested something with too many newlines via the
13303 v1 controller protocol, you could crash tor.
13304 - Fix a number of memory leaks, including some pretty serious ones.
13305 - Re-enable DirPort testing again, so Tor servers will be willing
13306 to advertise their DirPort if it's reachable.
13307 - On TLS handshake, only check the other router's nickname against
13308 its expected nickname if is_named is set.
13310 o Fixes forward-ported from 0.1.0.15:
13311 - Don't crash when we don't have any spare file descriptors and we
13312 try to spawn a dns or cpu worker.
13313 - Make the numbers in read-history and write-history into uint64s,
13314 so they don't overflow and publish negatives in the descriptor.
13316 o Fixes on 0.1.0.x:
13317 - For the OS X package's modified privoxy config file, comment
13318 out the "logfile" line so we don't log everything passed
13320 - We were whining about using socks4 or socks5-with-local-lookup
13321 even when it's an IP in the "virtual" range we designed exactly
13323 - We were leaking some memory every time the client changes IPs.
13324 - Never call free() on tor_malloc()d memory. This will help us
13325 use dmalloc to detect memory leaks.
13326 - Check for named servers when looking them up by nickname;
13327 warn when we'recalling a non-named server by its nickname;
13328 don't warn twice about the same name.
13329 - Try to list MyFamily elements by key, not by nickname, and warn
13330 if we've not heard of the server.
13331 - Make windows platform detection (uname equivalent) smarter.
13332 - It turns out sparc64 doesn't like unaligned access either.
13335 Changes in version 0.1.0.15 - 2005-09-23
13336 o Bugfixes on 0.1.0.x:
13337 - Reject ports 465 and 587 (spam targets) in default exit policy.
13338 - Don't crash when we don't have any spare file descriptors and we
13339 try to spawn a dns or cpu worker.
13340 - Get rid of IgnoreVersion undocumented config option, and make us
13341 only warn, never exit, when we're running an obsolete version.
13342 - Don't try to print a null string when your server finds itself to
13343 be unreachable and the Address config option is empty.
13344 - Make the numbers in read-history and write-history into uint64s,
13345 so they don't overflow and publish negatives in the descriptor.
13346 - Fix a minor memory leak in smartlist_string_remove().
13347 - We were only allowing ourselves to upload a server descriptor at
13348 most every 20 minutes, even if it changed earlier than that.
13349 - Clean up log entries that pointed to old URLs.
13352 Changes in version 0.1.1.7-alpha - 2005-09-14
13353 o Fixes on 0.1.1.6-alpha:
13354 - Exit servers were crashing when people asked them to make a
13355 connection to an address not in their exit policy.
13356 - Looking up a non-existent stream for a v1 control connection would
13358 - Fix a seg fault if we ask a dirserver for a descriptor by
13359 fingerprint but he doesn't know about him.
13360 - SETCONF was appending items to linelists, not clearing them.
13361 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
13362 out and refuse the setconf if it would fail.
13363 - Downgrade the dirserver log messages when whining about
13367 - Add Peter Palfrader's check-tor script to tor/contrib/
13368 It lets you easily check whether a given server (referenced by
13369 nickname) is reachable by you.
13370 - Numerous changes to move towards client-side v2 directories. Not
13373 o Fixes on 0.1.0.x:
13374 - If the user gave tor an odd number of command-line arguments,
13375 we were silently ignoring the last one. Now we complain and fail.
13376 [This wins the oldest-bug prize -- this bug has been present since
13377 November 2002, as released in Tor 0.0.0.]
13378 - Do not use unaligned memory access on alpha, mips, or mipsel.
13379 It *works*, but is very slow, so we treat them as if it doesn't.
13380 - Retry directory requests if we fail to get an answer we like
13381 from a given dirserver (we were retrying before, but only if
13382 we fail to connect).
13383 - When writing the RecommendedVersions line, sort them first.
13384 - When the client asked for a rendezvous port that the hidden
13385 service didn't want to provide, we were sending an IP address
13386 back along with the end cell. Fortunately, it was zero. But stop
13388 - Correct "your server is reachable" log entries to indicate that
13389 it was self-testing that told us so.
13392 Changes in version 0.1.1.6-alpha - 2005-09-09
13393 o Fixes on 0.1.1.5-alpha:
13394 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
13395 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
13396 - Fix bug with tor_memmem finding a match at the end of the string.
13397 - Make unit tests run without segfaulting.
13398 - Resolve some solaris x86 compile warnings.
13399 - Handle duplicate lines in approved-routers files without warning.
13400 - Fix bug where as soon as a server refused any requests due to his
13401 exit policy (e.g. when we ask for localhost and he tells us that's
13402 127.0.0.1 and he won't do it), we decided he wasn't obeying his
13403 exit policy using him for any exits.
13404 - Only do openssl hardware accelerator stuff if openssl version is
13407 o New controller features/fixes:
13408 - Add a "RESETCONF" command so you can set config options like
13409 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
13410 a config option in the torrc with no value, then it clears it
13411 entirely (rather than setting it to its default).
13412 - Add a "GETINFO config-file" to tell us where torrc is.
13413 - Avoid sending blank lines when GETINFO replies should be empty.
13414 - Add a QUIT command for the controller (for using it manually).
13415 - Fix a bug in SAVECONF that was adding default dirservers and
13416 other redundant entries to the torrc file.
13418 o Start on the new directory design:
13419 - Generate, publish, cache, serve new network-status format.
13420 - Publish individual descriptors (by fingerprint, by "all", and by
13422 - Publish client and server recommended versions separately.
13423 - Allow tor_gzip_uncompress() to handle multiple concatenated
13424 compressed strings. Serve compressed groups of router
13425 descriptors. The compression logic here could be more
13427 - Distinguish v1 authorities (all currently trusted directories)
13428 from v2 authorities (all trusted directories).
13429 - Change DirServers config line to note which dirs are v1 authorities.
13430 - Add configuration option "V1AuthoritativeDirectory 1" which
13431 moria1, moria2, and tor26 should set.
13432 - Remove option when getting directory cache to see whether they
13433 support running-routers; they all do now. Replace it with one
13434 to see whether caches support v2 stuff.
13437 - Dirservers now do their own external reachability testing of each
13438 Tor server, and only list them as running if they've been found to
13439 be reachable. We also send back warnings to the server's logs if
13440 it uploads a descriptor that we already believe is unreachable.
13441 - Implement exit enclaves: if we know an IP address for the
13442 destination, and there's a running Tor server at that address
13443 which allows exit to the destination, then extend the circuit to
13444 that exit first. This provides end-to-end encryption and end-to-end
13445 authentication. Also, if the user wants a .exit address or enclave,
13446 use 4 hops rather than 3, and cannibalize a general circ for it
13448 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
13449 controller. Also, rotate dns and cpu workers if the controller
13450 changes options that will affect them; and initialize the dns
13451 worker cache tree whether or not we start out as a server.
13452 - Only upload a new server descriptor when options change, 18
13453 hours have passed, uptime is reset, or bandwidth changes a lot.
13454 - Check [X-]Forwarded-For headers in HTTP requests when generating
13455 log messages. This lets people run dirservers (and caches) behind
13456 Apache but still know which IP addresses are causing warnings.
13458 o Config option changes:
13459 - Replace (Fascist)Firewall* config options with a new
13460 ReachableAddresses option that understands address policies.
13461 For example, "ReachableAddresses *:80,*:443"
13462 - Get rid of IgnoreVersion undocumented config option, and make us
13463 only warn, never exit, when we're running an obsolete version.
13464 - Make MonthlyAccountingStart config option truly obsolete now.
13466 o Fixes on 0.1.0.x:
13467 - Reject ports 465 and 587 in the default exit policy, since
13468 people have started using them for spam too.
13469 - It turns out we couldn't bootstrap a network since we added
13470 reachability detection in 0.1.0.1-rc. Good thing the Tor network
13471 has never gone down. Add an AssumeReachable config option to let
13472 servers and dirservers bootstrap. When we're trying to build a
13473 high-uptime or high-bandwidth circuit but there aren't enough
13474 suitable servers, try being less picky rather than simply failing.
13475 - Our logic to decide if the OR we connected to was the right guy
13476 was brittle and maybe open to a mitm for unverified routers.
13477 - We weren't cannibalizing circuits correctly for
13478 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
13479 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
13480 build those from scratch. This should make hidden services faster.
13481 - Predict required circuits better, with an eye toward making hidden
13482 services faster on the service end.
13483 - Retry streams if the exit node sends back a 'misc' failure. This
13484 should result in fewer random failures. Also, after failing
13485 from resolve failed or misc, reset the num failures, so we give
13486 it a fair shake next time we try.
13487 - Clean up the rendezvous warn log msgs, and downgrade some to info.
13488 - Reduce severity on logs about dns worker spawning and culling.
13489 - When we're shutting down and we do something like try to post a
13490 server descriptor or rendezvous descriptor, don't complain that
13491 we seem to be unreachable. Of course we are, we're shutting down.
13492 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
13493 We don't use them yet, but maybe one day our DNS resolver will be
13494 able to discover them.
13495 - Make ContactInfo mandatory for authoritative directory servers.
13496 - Require server descriptors to list IPv4 addresses -- hostnames
13497 are no longer allowed. This also fixes some potential security
13498 problems with people providing hostnames as their address and then
13499 preferentially resolving them to partition users.
13500 - Change log line for unreachability to explicitly suggest /etc/hosts
13501 as the culprit. Also make it clearer what IP address and ports we're
13502 testing for reachability.
13503 - Put quotes around user-supplied strings when logging so users are
13504 more likely to realize if they add bad characters (like quotes)
13506 - Let auth dir servers start without specifying an Address config
13508 - Make unit tests (and other invocations that aren't the real Tor)
13509 run without launching listeners, creating subdirectories, and so on.
13512 Changes in version 0.1.1.5-alpha - 2005-08-08
13513 o Bugfixes included in 0.1.0.14.
13515 o Bugfixes on 0.1.0.x:
13516 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
13517 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
13518 it would silently using ignore the 6668.
13521 Changes in version 0.1.0.14 - 2005-08-08
13522 o Bugfixes on 0.1.0.x:
13523 - Fix the other half of the bug with crypto handshakes
13525 - Fix an assert trigger if you send a 'signal term' via the
13526 controller when it's listening for 'event info' messages.
13529 Changes in version 0.1.1.4-alpha - 2005-08-04
13530 o Bugfixes included in 0.1.0.13.
13533 - Improve tor_gettimeofday() granularity on windows.
13534 - Make clients regenerate their keys when their IP address changes.
13535 - Implement some more GETINFO goodness: expose helper nodes, config
13536 options, getinfo keys.
13539 Changes in version 0.1.0.13 - 2005-08-04
13540 o Bugfixes on 0.1.0.x:
13541 - Fix a critical bug in the security of our crypto handshakes.
13542 - Fix a size_t underflow in smartlist_join_strings2() that made
13543 it do bad things when you hand it an empty smartlist.
13544 - Fix Windows installer to ship Tor license (thanks to Aphex for
13545 pointing out this oversight) and put a link to the doc directory
13547 - Explicitly set no-unaligned-access for sparc: it turns out the
13548 new gcc's let you compile broken code, but that doesn't make it
13552 Changes in version 0.1.1.3-alpha - 2005-07-23
13553 o Bugfixes on 0.1.1.2-alpha:
13554 - Fix a bug in handling the controller's "post descriptor"
13556 - Fix several bugs in handling the controller's "extend circuit"
13558 - Fix a bug in handling the controller's "stream status" event.
13559 - Fix an assert failure if we have a controller listening for
13560 circuit events and we go offline.
13561 - Re-allow hidden service descriptors to publish 0 intro points.
13562 - Fix a crash when generating your hidden service descriptor if
13563 you don't have enough intro points already.
13565 o New features on 0.1.1.2-alpha:
13566 - New controller function "getinfo accounting", to ask how
13567 many bytes we've used in this time period.
13568 - Experimental support for helper nodes: a lot of the risk from
13569 a small static adversary comes because users pick new random
13570 nodes every time they rebuild a circuit. Now users will try to
13571 stick to the same small set of entry nodes if they can. Not
13572 enabled by default yet.
13574 o Bugfixes on 0.1.0.12:
13575 - If you're an auth dir server, always publish your dirport,
13576 even if you haven't yet found yourself to be reachable.
13577 - Fix a size_t underflow in smartlist_join_strings2() that made
13578 it do bad things when you hand it an empty smartlist.
13581 Changes in version 0.1.0.12 - 2005-07-18
13582 o New directory servers:
13583 - tor26 has changed IP address.
13585 o Bugfixes on 0.1.0.x:
13586 - Fix a possible double-free in tor_gzip_uncompress().
13587 - When --disable-threads is set, do not search for or link against
13588 pthreads libraries.
13589 - Don't trigger an assert if an authoritative directory server
13590 claims its dirport is 0.
13591 - Fix bug with removing Tor as an NT service: some people were
13592 getting "The service did not return an error." Thanks to Matt
13596 Changes in version 0.1.1.2-alpha - 2005-07-15
13597 o New directory servers:
13598 - tor26 has changed IP address.
13600 o Bugfixes on 0.1.0.x, crashes/leaks:
13601 - Port the servers-not-obeying-their-exit-policies fix from
13603 - Fix an fd leak in start_daemon().
13604 - On Windows, you can't always reopen a port right after you've
13605 closed it. So change retry_listeners() to only close and re-open
13606 ports that have changed.
13607 - Fix a possible double-free in tor_gzip_uncompress().
13609 o Bugfixes on 0.1.0.x, usability:
13610 - When tor_socketpair() fails in Windows, give a reasonable
13611 Windows-style errno back.
13612 - Let people type "tor --install" as well as "tor -install" when
13614 want to make it an NT service.
13615 - NT service patch from Matt Edman to improve error messages.
13616 - When the controller asks for a config option with an abbreviated
13617 name, give the full name in our response.
13618 - Correct the man page entry on TrackHostExitsExpire.
13619 - Looks like we were never delivering deflated (i.e. compressed)
13620 running-routers lists, even when asked. Oops.
13621 - When --disable-threads is set, do not search for or link against
13622 pthreads libraries.
13624 o Bugfixes on 0.1.1.x:
13625 - Fix a seg fault with autodetecting which controller version is
13629 - New hidden service descriptor format: put a version in it, and
13630 let people specify introduction/rendezvous points that aren't
13631 in "the directory" (which is subjective anyway).
13632 - Allow the DEBUG controller event to work again. Mark certain log
13633 entries as "don't tell this to controllers", so we avoid cycles.
13636 Changes in version 0.1.0.11 - 2005-06-30
13637 o Bugfixes on 0.1.0.x:
13638 - Fix major security bug: servers were disregarding their
13639 exit policies if clients behaved unexpectedly.
13640 - Make OS X init script check for missing argument, so we don't
13641 confuse users who invoke it incorrectly.
13642 - Fix a seg fault in "tor --hash-password foo".
13643 - The MAPADDRESS control command was broken.
13646 Changes in version 0.1.1.1-alpha - 2005-06-29
13648 - Make OS X init script check for missing argument, so we don't
13649 confuse users who invoke it incorrectly.
13650 - Fix a seg fault in "tor --hash-password foo".
13651 - Fix a possible way to DoS dirservers.
13652 - When we complain that your exit policy implicitly allows local or
13653 private address spaces, name them explicitly so operators can
13655 - Make the log message less scary when all the dirservers are
13656 temporarily unreachable.
13657 - We were printing the number of idle dns workers incorrectly when
13661 - Revised controller protocol (version 1) that uses ascii rather
13662 than binary. Add supporting libraries in python and java so you
13663 can use the controller from your applications without caring how
13664 our protocol works.
13665 - Spiffy new support for crypto hardware accelerators. Can somebody
13669 Changes in version 0.0.9.10 - 2005-06-16
13670 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
13671 - Refuse relay cells that claim to have a length larger than the
13672 maximum allowed. This prevents a potential attack that could read
13673 arbitrary memory (e.g. keys) from an exit server's process
13677 Changes in version 0.1.0.10 - 2005-06-14
13678 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
13679 libevent before 1.1a.
13682 Changes in version 0.1.0.9-rc - 2005-06-09
13684 - Reset buf->highwater every time buf_shrink() is called, not just on
13685 a successful shrink. This was causing significant memory bloat.
13686 - Fix buffer overflow when checking hashed passwords.
13687 - Security fix: if seeding the RNG on Win32 fails, quit.
13688 - Allow seeding the RNG on Win32 even when you're not running as
13690 - Disable threading on Solaris too. Something is wonky with it,
13691 cpuworkers, and reentrant libs.
13692 - Reenable the part of the code that tries to flush as soon as an
13693 OR outbuf has a full TLS record available. Perhaps this will make
13694 OR outbufs not grow as huge except in rare cases, thus saving lots
13695 of CPU time plus memory.
13696 - Reject malformed .onion addresses rather then passing them on as
13697 normal web requests.
13698 - Adapt patch from Adam Langley: fix possible memory leak in
13699 tor_lookup_hostname().
13700 - Initialize libevent later in the startup process, so the logs are
13701 already established by the time we start logging libevent warns.
13702 - Use correct errno on win32 if libevent fails.
13703 - Check and warn about known-bad/slow libevent versions.
13704 - Pay more attention to the ClientOnly config option.
13705 - Have torctl.in/tor.sh.in check for location of su binary (needed
13707 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
13708 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
13709 HttpProxyAuthenticator
13710 - Stop warning about sigpipes in the logs. We're going to
13711 pretend that getting these occassionally is normal and fine.
13712 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
13714 installer screens; and don't put stuff into StartupItems unless
13715 the user asks you to.
13716 - Require servers that use the default dirservers to have public IP
13717 addresses. We have too many servers that are configured with private
13718 IPs and their admins never notice the log entries complaining that
13719 their descriptors are being rejected.
13720 - Add OSX uninstall instructions. An actual uninstall script will
13724 Changes in version 0.1.0.8-rc - 2005-05-23
13726 - It turns out that kqueue on OS X 10.3.9 was causing kernel
13727 panics. Disable kqueue on all OS X Tors.
13728 - Fix RPM: remove duplicate line accidentally added to the rpm
13730 - Disable threads on openbsd too, since its gethostaddr is not
13732 - Tolerate libevent 0.8 since it still works, even though it's
13734 - Enable building on Red Hat 9.0 again.
13735 - Allow the middle hop of the testing circuit to be running any
13736 version, now that most of them have the bugfix to let them connect
13737 to unknown servers. This will allow reachability testing to work
13738 even when 0.0.9.7-0.0.9.9 become obsolete.
13739 - Handle relay cells with rh.length too large. This prevents
13740 a potential attack that could read arbitrary memory (maybe even
13741 keys) from the exit server's process.
13742 - We screwed up the dirport reachability testing when we don't yet
13743 have a cached version of the directory. Hopefully now fixed.
13744 - Clean up router_load_single_router() (used by the controller),
13745 so it doesn't seg fault on error.
13746 - Fix a minor memory leak when somebody establishes an introduction
13747 point at your Tor server.
13748 - If a socks connection ends because read fails, don't warn that
13749 you're not sending a socks reply back.
13752 - Add HttpProxyAuthenticator config option too, that works like
13753 the HttpsProxyAuthenticator config option.
13754 - Encode hashed controller passwords in hex instead of base64,
13755 to make it easier to write controllers.
13758 Changes in version 0.1.0.7-rc - 2005-05-17
13760 - Fix a bug in the OS X package installer that prevented it from
13761 installing on Tiger.
13762 - Fix a script bug in the OS X package installer that made it
13763 complain during installation.
13764 - Find libevent even if it's hiding in /usr/local/ and your
13765 CFLAGS and LDFLAGS don't tell you to look there.
13766 - Be able to link with libevent as a shared library (the default
13767 after 1.0d), even if it's hiding in /usr/local/lib and even
13768 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
13769 assuming you're running gcc. Otherwise fail and give a useful
13771 - Fix a bug in the RPM packager: set home directory for _tor to
13772 something more reasonable when first installing.
13773 - Free a minor amount of memory that is still reachable on exit.
13776 Changes in version 0.1.0.6-rc - 2005-05-14
13778 - Implement --disable-threads configure option. Disable threads on
13779 netbsd by default, because it appears to have no reentrant resolver
13781 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
13782 release (1.1) detects and disables kqueue if it's broken.
13783 - Append default exit policy before checking for implicit internal
13784 addresses. Now we don't log a bunch of complaints on startup
13785 when using the default exit policy.
13786 - Some people were putting "Address " in their torrc, and they had
13787 a buggy resolver that resolved " " to 0.0.0.0. Oops.
13788 - If DataDir is ~/.tor, and that expands to /.tor, then default to
13789 LOCALSTATEDIR/tor instead.
13790 - Fix fragmented-message bug in TorControl.py.
13791 - Resolve a minor bug which would prevent unreachable dirports
13792 from getting suppressed in the published descriptor.
13793 - When the controller gave us a new descriptor, we weren't resolving
13794 it immediately, so Tor would think its address was 0.0.0.0 until
13795 we fetched a new directory.
13796 - Fix an uppercase/lowercase case error in suppressing a bogus
13797 libevent warning on some Linuxes.
13800 - Begin scrubbing sensitive strings from logs by default. Turn off
13801 the config option SafeLogging if you need to do debugging.
13802 - Switch to a new buffer management algorithm, which tries to avoid
13803 reallocing and copying quite as much. In first tests it looks like
13804 it uses *more* memory on average, but less cpu.
13805 - First cut at support for "create-fast" cells. Clients can use
13806 these when extending to their first hop, since the TLS already
13807 provides forward secrecy and authentication. Not enabled on
13809 - When dirservers refuse a router descriptor, we now log its
13810 contactinfo, platform, and the poster's IP address.
13811 - Call tor_free_all instead of connections_free_all after forking, to
13812 save memory on systems that need to fork.
13813 - Whine at you if you're a server and you don't set your contactinfo.
13814 - Implement --verify-config command-line option to check if your torrc
13815 is valid without actually launching Tor.
13816 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
13817 rather than just rejecting it.
13820 Changes in version 0.1.0.5-rc - 2005-04-27
13822 - Stop trying to print a null pointer if an OR conn fails because
13823 we didn't like its cert.
13825 - Switch our internal buffers implementation to use a ring buffer,
13826 to hopefully improve performance for fast servers a lot.
13827 - Add HttpsProxyAuthenticator support (basic auth only), based
13828 on patch from Adam Langley.
13829 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
13830 the fast servers that have been joining lately.
13831 - Give hidden service accesses extra time on the first attempt,
13832 since 60 seconds is often only barely enough. This might improve
13834 - Improve performance for dirservers: stop re-parsing the whole
13835 directory every time you regenerate it.
13836 - Add more debugging info to help us find the weird dns freebsd
13837 pthreads bug; cleaner debug messages to help track future issues.
13840 Changes in version 0.0.9.9 - 2005-04-23
13841 o Bugfixes on 0.0.9.x:
13842 - If unofficial Tor clients connect and send weird TLS certs, our
13843 Tor server triggers an assert. This release contains a minimal
13844 backport from the broader fix that we put into 0.1.0.4-rc.
13847 Changes in version 0.1.0.4-rc - 2005-04-23
13849 - If unofficial Tor clients connect and send weird TLS certs, our
13850 Tor server triggers an assert. Stop asserting, and start handling
13851 TLS errors better in other situations too.
13852 - When the controller asks us to tell it about all the debug-level
13853 logs, it turns out we were generating debug-level logs while
13854 telling it about them, which turns into a bad loop. Now keep
13855 track of whether you're sending a debug log to the controller,
13856 and don't log when you are.
13857 - Fix the "postdescriptor" feature of the controller interface: on
13858 non-complete success, only say "done" once.
13860 - Clients are now willing to load balance over up to 2mB, not 1mB,
13861 of advertised bandwidth capacity.
13862 - Add a NoPublish config option, so you can be a server (e.g. for
13863 testing running Tor servers in other Tor networks) without
13864 publishing your descriptor to the primary dirservers.
13867 Changes in version 0.1.0.3-rc - 2005-04-08
13868 o Improvements on 0.1.0.2-rc:
13869 - Client now retries when streams end early for 'hibernating' or
13870 'resource limit' reasons, rather than failing them.
13871 - More automated handling for dirserver operators:
13872 - Automatically approve nodes running 0.1.0.2-rc or later,
13873 now that the the reachability detection stuff is working.
13874 - Now we allow two unverified servers with the same nickname
13875 but different keys. But if a nickname is verified, only that
13876 nickname+key are allowed.
13877 - If you're an authdirserver connecting to an address:port,
13878 and it's not the OR you were expecting, forget about that
13879 descriptor. If he *was* the one you were expecting, then forget
13880 about all other descriptors for that address:port.
13881 - Allow servers to publish descriptors from 12 hours in the future.
13882 Corollary: only whine about clock skew from the dirserver if
13883 he's a trusted dirserver (since now even verified servers could
13884 have quite wrong clocks).
13885 - Adjust maximum skew and age for rendezvous descriptors: let skew
13886 be 48 hours rather than 90 minutes.
13887 - Efficiency improvements:
13888 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
13889 it much faster to look up a circuit for each relay cell.
13890 - Remove most calls to assert_all_pending_dns_resolves_ok(),
13891 since they're eating our cpu on exit nodes.
13892 - Stop wasting time doing a case insensitive comparison for every
13893 dns name every time we do any lookup. Canonicalize the names to
13894 lowercase and be done with it.
13895 - Start sending 'truncated' cells back rather than destroy cells,
13896 if the circuit closes in front of you. This means we won't have
13897 to abandon partially built circuits.
13898 - Only warn once per nickname from add_nickname_list_to_smartlist
13899 per failure, so an entrynode or exitnode choice that's down won't
13901 - Put a note in the torrc about abuse potential with the default
13903 - Revise control spec and implementation to allow all log messages to
13904 be sent to controller with their severities intact (suggested by
13905 Matt Edman). Update TorControl to handle new log event types.
13906 - Provide better explanation messages when controller's POSTDESCRIPTOR
13908 - Stop putting nodename in the Platform string in server descriptors.
13909 It doesn't actually help, and it is confusing/upsetting some people.
13911 o Bugfixes on 0.1.0.2-rc:
13912 - We were printing the host mask wrong in exit policies in server
13913 descriptors. This isn't a critical bug though, since we were still
13914 obeying the exit policy internally.
13915 - Fix Tor when compiled with libevent but without pthreads: move
13916 connection_unregister() from _connection_free() to
13918 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
13919 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
13920 when we look through the connection array, we'll find any of the
13921 cpu/dnsworkers. This is no good.
13923 o Bugfixes on 0.0.9.8:
13924 - Fix possible bug on threading platforms (e.g. win32) which was
13925 leaking a file descriptor whenever a cpuworker or dnsworker died.
13926 - When using preferred entry or exit nodes, ignore whether the
13927 circuit wants uptime or capacity. They asked for the nodes, they
13929 - chdir() to your datadirectory at the *end* of the daemonize process,
13930 not the beginning. This was a problem because the first time you
13931 run tor, if your datadir isn't there, and you have runasdaemon set
13932 to 1, it will try to chdir to it before it tries to create it. Oops.
13933 - Handle changed router status correctly when dirserver reloads
13934 fingerprint file. We used to be dropping all unverified descriptors
13935 right then. The bug was hidden because we would immediately
13936 fetch a directory from another dirserver, which would include the
13937 descriptors we just dropped.
13938 - When we're connecting to an OR and he's got a different nickname/key
13939 than we were expecting, only complain loudly if we're an OP or a
13940 dirserver. Complaining loudly to the OR admins just confuses them.
13941 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
13942 artificially capped at 500kB.
13945 Changes in version 0.0.9.8 - 2005-04-07
13946 o Bugfixes on 0.0.9.x:
13947 - We have a bug that I haven't found yet. Sometimes, very rarely,
13948 cpuworkers get stuck in the 'busy' state, even though the cpuworker
13949 thinks of itself as idle. This meant that no new circuits ever got
13950 established. Here's a workaround to kill any cpuworker that's been
13951 busy for more than 100 seconds.
13954 Changes in version 0.1.0.2-rc - 2005-04-01
13955 o Bugfixes on 0.1.0.1-rc:
13956 - Fixes on reachability detection:
13957 - Don't check for reachability while hibernating.
13958 - If ORPort is reachable but DirPort isn't, still publish the
13959 descriptor, but zero out DirPort until it's found reachable.
13960 - When building testing circs for ORPort testing, use only
13961 high-bandwidth nodes, so fewer circuits fail.
13962 - Complain about unreachable ORPort separately from unreachable
13963 DirPort, so the user knows what's going on.
13964 - Make sure we only conclude ORPort reachability if we didn't
13965 initiate the conn. Otherwise we could falsely conclude that
13966 we're reachable just because we connected to the guy earlier
13967 and he used that same pipe to extend to us.
13968 - Authdirservers shouldn't do ORPort reachability detection,
13969 since they're in clique mode, so it will be rare to find a
13970 server not already connected to them.
13971 - When building testing circuits, always pick middle hops running
13972 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
13973 bug. (This is a kludge; it will go away when 0.0.9.x becomes
13975 - When we decide we're reachable, actually publish our descriptor
13977 - Fix bug in redirectstream in the controller.
13978 - Fix the state descriptor strings so logs don't claim edge streams
13979 are in a different state than they actually are.
13980 - Use recent libevent features when possible (this only really affects
13981 win32 and osx right now, because the new libevent with these
13982 features hasn't been released yet). Add code to suppress spurious
13984 - Prevent possible segfault in connection_close_unattached_ap().
13985 - Fix newlines on torrc in win32.
13986 - Improve error msgs when tor-resolve fails.
13988 o Improvements on 0.0.9.x:
13989 - New experimental script tor/contrib/ExerciseServer.py (needs more
13990 work) that uses the controller interface to build circuits and
13991 fetch pages over them. This will help us bootstrap servers that
13992 have lots of capacity but haven't noticed it yet.
13993 - New experimental script tor/contrib/PathDemo.py (needs more work)
13994 that uses the controller interface to let you choose whole paths
13996 "<hostname>.<path,separated by dots>.<length of path>.path"
13997 - When we've connected to an OR and handshaked but didn't like
13998 the result, we were closing the conn without sending destroy
13999 cells back for pending circuits. Now send those destroys.
14002 Changes in version 0.0.9.7 - 2005-04-01
14003 o Bugfixes on 0.0.9.x:
14004 - Fix another race crash bug (thanks to Glenn Fink for reporting).
14005 - Compare identity to identity, not to nickname, when extending to
14006 a router not already in the directory. This was preventing us from
14007 extending to unknown routers. Oops.
14008 - Make sure to create OS X Tor user in <500 range, so we aren't
14009 creating actual system users.
14010 - Note where connection-that-hasn't-sent-end was marked, and fix
14011 a few really loud instances of this harmless bug (it's fixed more
14015 Changes in version 0.1.0.1-rc - 2005-03-28
14017 - Add reachability testing. Your Tor server will automatically try
14018 to see if its ORPort and DirPort are reachable from the outside,
14019 and it won't upload its descriptor until it decides they are.
14020 - Handle unavailable hidden services better. Handle slow or busy
14021 hidden services better.
14022 - Add support for CONNECTing through https proxies, with "HttpsProxy"
14024 - New exit policy: accept most low-numbered ports, rather than
14025 rejecting most low-numbered ports.
14026 - More Tor controller support (still experimental). See
14027 http://tor.eff.org/doc/control-spec.txt for all the new features,
14028 including signals to emulate unix signals from any platform;
14029 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
14030 closestream; closecircuit; etc.
14031 - Make nt services work and start on startup on win32 (based on
14032 patch by Matt Edman).
14033 - Add a new AddressMap config directive to rewrite incoming socks
14034 addresses. This lets you, for example, declare an implicit
14035 required exit node for certain sites.
14036 - Add a new TrackHostExits config directive to trigger addressmaps
14037 for certain incoming socks addresses -- for sites that break when
14038 your exit keeps changing (based on patch by Mike Perry).
14039 - Redo the client-side dns cache so it's just an addressmap too.
14040 - Notice when our IP changes, and reset stats/uptime/reachability.
14041 - When an application is using socks5, give him the whole variety of
14042 potential socks5 responses (connect refused, host unreachable, etc),
14043 rather than just "success" or "failure".
14044 - A more sane version numbering system. See
14045 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
14046 - New contributed script "exitlist": a simple python script to
14047 parse directories and find Tor nodes that exit to listed
14049 - New contributed script "privoxy-tor-toggle" to toggle whether
14050 Privoxy uses Tor. Seems to be configured for Debian by default.
14051 - Report HTTP reasons to client when getting a response from directory
14052 servers -- so you can actually know what went wrong.
14053 - New config option MaxAdvertisedBandwidth which lets you advertise
14054 a low bandwidthrate (to not attract as many circuits) while still
14055 allowing a higher bandwidthrate in reality.
14057 o Robustness/stability fixes:
14058 - Make Tor use Niels Provos's libevent instead of its current
14059 poll-but-sometimes-select mess. This will let us use faster async
14060 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
14062 - pthread support now too. This was forced because when we forked,
14063 we ended up wasting a lot of duplicate ram over time. Also switch
14064 to foo_r versions of some library calls to allow reentry and
14066 - Better handling for heterogeneous / unreliable nodes:
14067 - Annotate circuits w/ whether they aim to contain high uptime nodes
14068 and/or high capacity nodes. When building circuits, choose
14070 - This means that every single node in an intro rend circuit,
14071 not just the last one, will have a minimum uptime.
14072 - New config option LongLivedPorts to indicate application streams
14073 that will want high uptime circuits.
14074 - Servers reset uptime when a dir fetch entirely fails. This
14075 hopefully reflects stability of the server's network connectivity.
14076 - If somebody starts his tor server in Jan 2004 and then fixes his
14077 clock, don't make his published uptime be a year.
14078 - Reset published uptime when you wake up from hibernation.
14079 - Introduce a notion of 'internal' circs, which are chosen without
14080 regard to the exit policy of the last hop. Intro and rendezvous
14081 circs must be internal circs, to avoid leaking information. Resolve
14082 and connect streams can use internal circs if they want.
14083 - New circuit pooling algorithm: make sure to have enough circs around
14084 to satisfy any predicted ports, and also make sure to have 2 internal
14085 circs around if we've required internal circs lately (and with high
14086 uptime if we've seen that lately too).
14087 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
14088 which describes how often we retry making new circuits if current
14089 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
14090 how long we're willing to make use of an already-dirty circuit.
14091 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
14092 circ as necessary, if there are any completed ones lying around
14093 when we try to launch one.
14094 - Make hidden services try to establish a rendezvous for 30 seconds,
14095 rather than for n (where n=3) attempts to build a circuit.
14096 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
14097 "ShutdownWaitLength".
14098 - Try to be more zealous about calling connection_edge_end when
14099 things go bad with edge conns in connection.c.
14100 - Revise tor-spec to add more/better stream end reasons.
14101 - Revise all calls to connection_edge_end to avoid sending "misc",
14102 and to take errno into account where possible.
14105 - Fix a race condition that can trigger an assert, when we have a
14106 pending create cell and an OR connection fails right then.
14107 - Fix several double-mark-for-close bugs, e.g. where we were finding
14108 a conn for a cell even if that conn is already marked for close.
14109 - Make sequence of log messages when starting on win32 with no config
14110 file more reasonable.
14111 - When choosing an exit node for a new non-internal circ, don't take
14112 into account whether it'll be useful for any pending x.onion
14113 addresses -- it won't.
14114 - Turn addr_policy_compare from a tristate to a quadstate; this should
14115 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
14116 for google.com" problem.
14117 - Make "platform" string in descriptor more accurate for Win32 servers,
14118 so it's not just "unknown platform".
14119 - Fix an edge case in parsing config options (thanks weasel).
14120 If they say "--" on the commandline, it's not an option.
14121 - Reject odd-looking addresses at the client (e.g. addresses that
14122 contain a colon), rather than having the server drop them because
14124 - tor-resolve requests were ignoring .exit if there was a working circuit
14125 they could use instead.
14126 - REUSEADDR on normal platforms means you can rebind to the port
14127 right after somebody else has let it go. But REUSEADDR on win32
14128 means to let you bind to the port _even when somebody else
14129 already has it bound_! So, don't do that on Win32.
14130 - Change version parsing logic: a version is "obsolete" if it is not
14131 recommended and (1) there is a newer recommended version in the
14132 same series, or (2) there are no recommended versions in the same
14133 series, but there are some recommended versions in a newer series.
14134 A version is "new" if it is newer than any recommended version in
14136 - Stop most cases of hanging up on a socks connection without sending
14140 - Require BandwidthRate to be at least 20kB/s for servers.
14141 - When a dirserver causes you to give a warn, mention which dirserver
14143 - New config option DirAllowPrivateAddresses for authdirservers.
14144 Now by default they refuse router descriptors that have non-IP or
14145 private-IP addresses.
14146 - Stop publishing socksport in the directory, since it's not
14147 actually meant to be public. For compatibility, publish a 0 there
14149 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
14150 smart" value, that is low for servers and high for clients.
14151 - If our clock jumps forward by 100 seconds or more, assume something
14152 has gone wrong with our network and abandon all not-yet-used circs.
14153 - Warn when exit policy implicitly allows local addresses.
14154 - If we get an incredibly skewed timestamp from a dirserver mirror
14155 that isn't a verified OR, don't warn -- it's probably him that's
14157 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
14158 cookies to disk and doesn't log each web request to disk. (Thanks
14159 to Brett Carrington for pointing this out.)
14160 - When a client asks us for a dir mirror and we don't have one,
14161 launch an attempt to get a fresh one.
14162 - If we're hibernating and we get a SIGINT, exit immediately.
14163 - Add --with-dmalloc ./configure option, to track memory leaks.
14164 - And try to free all memory on closing, so we can detect what
14166 - Cache local dns resolves correctly even when they're .exit
14168 - Give a better warning when some other server advertises an
14169 ORPort that is actually an apache running ssl.
14170 - Add "opt hibernating 1" to server descriptor to make it clearer
14171 whether the server is hibernating.
14174 Changes in version 0.0.9.6 - 2005-03-24
14175 o Bugfixes on 0.0.9.x (crashes and asserts):
14176 - Add new end stream reasons to maintainance branch. Fix bug where
14177 reason (8) could trigger an assert. Prevent bug from recurring.
14178 - Apparently win32 stat wants paths to not end with a slash.
14179 - Fix assert triggers in assert_cpath_layer_ok(), where we were
14180 blowing away the circuit that conn->cpath_layer points to, then
14181 checking to see if the circ is well-formed. Backport check to make
14182 sure we dont use the cpath on a closed connection.
14183 - Prevent circuit_resume_edge_reading_helper() from trying to package
14184 inbufs for marked-for-close streams.
14185 - Don't crash on hup if your options->address has become unresolvable.
14186 - Some systems (like OS X) sometimes accept() a connection and tell
14187 you the remote host is 0.0.0.0:0. If this happens, due to some
14188 other mis-features, we get confused; so refuse the conn for now.
14190 o Bugfixes on 0.0.9.x (other):
14191 - Fix harmless but scary "Unrecognized content encoding" warn message.
14192 - Add new stream error reason: TORPROTOCOL reason means "you are not
14193 speaking a version of Tor I understand; say bye-bye to your stream."
14194 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
14195 into the future, now that we are more tolerant of skew. This
14196 resolves a bug where a Tor server would refuse to cache a directory
14197 because all the directories it gets are too far in the future;
14198 yet the Tor server never logs any complaints about clock skew.
14199 - Mac packaging magic: make man pages useable, and do not overwrite
14200 existing torrc files.
14201 - Make OS X log happily to /var/log/tor/tor.log
14204 Changes in version 0.0.9.5 - 2005-02-22
14205 o Bugfixes on 0.0.9.x:
14206 - Fix an assert race at exit nodes when resolve requests fail.
14207 - Stop picking unverified dir mirrors--it only leads to misery.
14208 - Patch from Matt Edman to make NT services work better. Service
14209 support is still not compiled into the executable by default.
14210 - Patch from Dmitri Bely so the Tor service runs better under
14211 the win32 SYSTEM account.
14212 - Make tor-resolve actually work (?) on Win32.
14213 - Fix a sign bug when getrlimit claims to have 4+ billion
14214 file descriptors available.
14215 - Stop refusing to start when bandwidthburst == bandwidthrate.
14216 - When create cells have been on the onion queue more than five
14217 seconds, just send back a destroy and take them off the list.
14220 Changes in version 0.0.9.4 - 2005-02-03
14221 o Bugfixes on 0.0.9:
14222 - Fix an assert bug that took down most of our servers: when
14223 a server claims to have 1 GB of bandwidthburst, don't
14225 - Don't crash as badly if we have spawned the max allowed number
14226 of dnsworkers, or we're out of file descriptors.
14227 - Block more file-sharing ports in the default exit policy.
14228 - MaxConn is now automatically set to the hard limit of max
14229 file descriptors we're allowed (ulimit -n), minus a few for
14231 - Give a clearer message when servers need to raise their
14232 ulimit -n when they start running out of file descriptors.
14233 - SGI Compatibility patches from Jan Schaumann.
14234 - Tolerate a corrupt cached directory better.
14235 - When a dirserver hasn't approved your server, list which one.
14236 - Go into soft hibernation after 95% of the bandwidth is used,
14237 not 99%. This is especially important for daily hibernators who
14238 have a small accounting max. Hopefully it will result in fewer
14239 cut connections when the hard hibernation starts.
14240 - Load-balance better when using servers that claim more than
14241 800kB/s of capacity.
14242 - Make NT services work (experimental, only used if compiled in).
14245 Changes in version 0.0.9.3 - 2005-01-21
14246 o Bugfixes on 0.0.9:
14247 - Backport the cpu use fixes from main branch, so busy servers won't
14248 need as much processor time.
14249 - Work better when we go offline and then come back, or when we
14250 run Tor at boot before the network is up. We do this by
14251 optimistically trying to fetch a new directory whenever an
14252 application request comes in and we think we're offline -- the
14253 human is hopefully a good measure of when the network is back.
14254 - Backport some minimal hidserv bugfixes: keep rend circuits open as
14255 long as you keep using them; actually publish hidserv descriptors
14256 shortly after they change, rather than waiting 20-40 minutes.
14257 - Enable Mac startup script by default.
14258 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
14259 - When you update AllowUnverifiedNodes or FirewallPorts via the
14260 controller's setconf feature, we were always appending, never
14262 - When you update HiddenServiceDir via setconf, it was screwing up
14263 the order of reading the lines, making it fail.
14264 - Do not rewrite a cached directory back to the cache; otherwise we
14265 will think it is recent and not fetch a newer one on startup.
14266 - Workaround for webservers that lie about Content-Encoding: Tor
14267 now tries to autodetect compressed directories and compression
14268 itself. This lets us Proxypass dir fetches through apache.
14271 Changes in version 0.0.9.2 - 2005-01-04
14272 o Bugfixes on 0.0.9 (crashes and asserts):
14273 - Fix an assert on startup when the disk is full and you're logging
14275 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
14276 style address, then we'd crash.
14277 - Fix an assert trigger when the running-routers string we get from
14278 a dirserver is broken.
14279 - Make worker threads start and run on win32. Now win32 servers
14281 - Bandaid (not actually fix, but now it doesn't crash) an assert
14282 where the dns worker dies mysteriously and the main Tor process
14283 doesn't remember anything about the address it was resolving.
14285 o Bugfixes on 0.0.9 (Win32):
14286 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
14287 name out of the warning/assert messages.
14288 - Fix a superficial "unhandled error on read" bug on win32.
14289 - The win32 installer no longer requires a click-through for our
14290 license, since our Free Software license grants rights but does not
14292 - Win32: When connecting to a dirserver fails, try another one
14293 immediately. (This was already working for non-win32 Tors.)
14294 - Stop trying to parse $HOME on win32 when hunting for default
14296 - Make tor-resolve.c work on win32 by calling network_init().
14298 o Bugfixes on 0.0.9 (other):
14299 - Make 0.0.9.x build on Solaris again.
14300 - Due to a fencepost error, we were blowing away the \n when reporting
14301 confvalue items in the controller. So asking for multiple config
14302 values at once couldn't work.
14303 - When listing circuits that are pending on an opening OR connection,
14304 if we're an OR we were listing circuits that *end* at us as
14305 being pending on every listener, dns/cpu worker, etc. Stop that.
14306 - Dirservers were failing to create 'running-routers' or 'directory'
14307 strings if we had more than some threshold of routers. Fix them so
14308 they can handle any number of routers.
14309 - Fix a superficial "Duplicate mark for close" bug.
14310 - Stop checking for clock skew for OR connections, even for servers.
14311 - Fix a fencepost error that was chopping off the last letter of any
14312 nickname that is the maximum allowed nickname length.
14313 - Update URLs in log messages so they point to the new website.
14314 - Fix a potential problem in mangling server private keys while
14315 writing to disk (not triggered yet, as far as we know).
14316 - Include the licenses for other free software we include in Tor,
14317 now that we're shipping binary distributions more regularly.
14320 Changes in version 0.0.9.1 - 2004-12-15
14321 o Bugfixes on 0.0.9:
14322 - Make hibernation actually work.
14323 - Make HashedControlPassword config option work.
14324 - When we're reporting event circuit status to a controller,
14325 don't use the stream status code.
14328 Changes in version 0.0.9 - 2004-12-12
14330 - Clean up manpage and torrc.sample file.
14331 - Clean up severities and text of log warnings.
14333 - Make servers trigger an assert when they enter hibernation.
14336 Changes in version 0.0.9rc7 - 2004-12-08
14337 o Bugfixes on 0.0.9rc:
14338 - Fix a stack-trashing crash when an exit node begins hibernating.
14339 - Avoid looking at unallocated memory while considering which
14340 ports we need to build circuits to cover.
14341 - Stop a sigpipe: when an 'end' cell races with eof from the app,
14342 we shouldn't hold-open-until-flush if the eof arrived first.
14343 - Fix a bug with init_cookie_authentication() in the controller.
14344 - When recommending new-format log lines, if the upper bound is
14345 LOG_ERR, leave it implicit.
14347 o Bugfixes on 0.0.8.1:
14348 - Fix a whole slew of memory leaks.
14349 - Fix isspace() and friends so they still make Solaris happy
14350 but also so they don't trigger asserts on win32.
14351 - Fix parse_iso_time on platforms without strptime (eg win32).
14352 - win32: tolerate extra "readable" events better.
14353 - win32: when being multithreaded, leave parent fdarray open.
14354 - Make unit tests work on win32.
14357 Changes in version 0.0.9rc6 - 2004-12-06
14358 o Bugfixes on 0.0.9pre:
14359 - Clean up some more integer underflow opportunities (not exploitable
14361 - While hibernating, hup should not regrow our listeners.
14362 - Send an end to the streams we close when we hibernate, rather
14363 than just chopping them off.
14364 - React to eof immediately on non-open edge connections.
14366 o Bugfixes on 0.0.8.1:
14367 - Calculate timeout for waiting for a connected cell from the time
14368 we sent the begin cell, not from the time the stream started. If
14369 it took a long time to establish the circuit, we would time out
14370 right after sending the begin cell.
14371 - Fix router_compare_addr_to_addr_policy: it was not treating a port
14372 of * as always matching, so we were picking reject *:* nodes as
14373 exit nodes too. Oops.
14376 - New circuit building strategy: keep a list of ports that we've
14377 used in the past 6 hours, and always try to have 2 circuits open
14378 or on the way that will handle each such port. Seed us with port
14379 80 so web users won't complain that Tor is "slow to start up".
14380 - Make kill -USR1 dump more useful stats about circuits.
14381 - When warning about retrying or giving up, print the address, so
14382 the user knows which one it's talking about.
14383 - If you haven't used a clean circuit in an hour, throw it away,
14384 just to be on the safe side. (This means after 6 hours a totally
14385 unused Tor client will have no circuits open.)
14388 Changes in version 0.0.9rc5 - 2004-12-01
14389 o Bugfixes on 0.0.8.1:
14390 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
14391 - Let resolve conns retry/expire also, rather than sticking around
14393 - If we are using select, make sure we stay within FD_SETSIZE.
14395 o Bugfixes on 0.0.9pre:
14396 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
14397 but doesn't seem to be currently; thanks to Ilja van Sprundel for
14399 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
14400 instead. Impose minima and maxima for all *Period options; impose
14401 even tighter maxima for fetching if we are a caching dirserver.
14402 Clip rather than rejecting.
14403 - Fetch cached running-routers from servers that serve it (that is,
14404 authdirservers and servers running 0.0.9rc5-cvs or later.)
14407 - Accept *:706 (silc) in default exit policy.
14408 - Implement new versioning format for post 0.1.
14409 - Support "foo.nickname.exit" addresses, to let Alice request the
14410 address "foo" as viewed by exit node "nickname". Based on a patch
14412 - Make tor --version --version dump the cvs Id of every file.
14415 Changes in version 0.0.9rc4 - 2004-11-28
14416 o Bugfixes on 0.0.8.1:
14417 - Make windows sockets actually non-blocking (oops), and handle
14418 win32 socket errors better.
14420 o Bugfixes on 0.0.9rc1:
14421 - Actually catch the -USR2 signal.
14424 Changes in version 0.0.9rc3 - 2004-11-25
14425 o Bugfixes on 0.0.8.1:
14426 - Flush the log file descriptor after we print "Tor opening log file",
14427 so we don't see those messages days later.
14429 o Bugfixes on 0.0.9rc1:
14430 - Make tor-resolve work again.
14431 - Avoid infinite loop in tor-resolve if tor hangs up on it.
14432 - Fix an assert trigger for clients/servers handling resolves.
14435 Changes in version 0.0.9rc2 - 2004-11-24
14436 o Bugfixes on 0.0.9rc1:
14437 - I broke socks5 support while fixing the eof bug.
14438 - Allow unitless bandwidths and intervals; they default to bytes
14440 - New servers don't start out hibernating; they are active until
14441 they run out of bytes, so they have a better estimate of how
14442 long it takes, and so their operators can know they're working.
14445 Changes in version 0.0.9rc1 - 2004-11-23
14446 o Bugfixes on 0.0.8.1:
14447 - Finally fix a bug that's been plaguing us for a year:
14448 With high load, circuit package window was reaching 0. Whenever
14449 we got a circuit-level sendme, we were reading a lot on each
14450 socket, but only writing out a bit. So we would eventually reach
14451 eof. This would be noticed and acted on even when there were still
14452 bytes sitting in the inbuf.
14453 - When poll() is interrupted, we shouldn't believe the revents values.
14455 o Bugfixes on 0.0.9pre6:
14456 - Fix hibernate bug that caused pre6 to be broken.
14457 - Don't keep rephist info for routers that haven't had activity for
14458 24 hours. (This matters now that clients have keys, since we track
14460 - Never call close_temp_logs while validating log options.
14461 - Fix backslash-escaping on tor.sh.in and torctl.in.
14464 - Implement weekly/monthly/daily accounting: now you specify your
14465 hibernation properties by
14466 AccountingMax N bytes|KB|MB|GB|TB
14467 AccountingStart day|week|month [day] HH:MM
14468 Defaults to "month 1 0:00".
14469 - Let bandwidth and interval config options be specified as 5 bytes,
14470 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
14471 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
14472 get back to normal.)
14473 - If your requested entry or exit node has advertised bandwidth 0,
14475 - Be more greedy about filling up relay cells -- we try reading again
14476 once we've processed the stuff we read, in case enough has arrived
14477 to fill the last cell completely.
14478 - Apply NT service patch from Osamu Fujino. Still needs more work.
14481 Changes in version 0.0.9pre6 - 2004-11-15
14482 o Bugfixes on 0.0.8.1:
14483 - Fix assert failure on malformed socks4a requests.
14484 - Use identity comparison, not nickname comparison, to choose which
14485 half of circuit-ID-space each side gets to use. This is needed
14486 because sometimes we think of a router as a nickname, and sometimes
14487 as a hex ID, and we can't predict what the other side will do.
14488 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
14489 write() call will fail and we handle it there.
14490 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
14491 and smartlist_len, which are two major profiling offenders.
14493 o Bugfixes on 0.0.9pre5:
14494 - Fix a bug in read_all that was corrupting config files on windows.
14495 - When we're raising the max number of open file descriptors to
14496 'unlimited', don't log that we just raised it to '-1'.
14497 - Include event code with events, as required by control-spec.txt.
14498 - Don't give a fingerprint when clients do --list-fingerprint:
14499 it's misleading, because it will never be the same again.
14500 - Stop using strlcpy in tor_strndup, since it was slowing us
14502 - Remove warn on startup about missing cached-directory file.
14503 - Make kill -USR1 work again.
14504 - Hibernate if we start tor during the "wait for wakeup-time" phase
14505 of an accounting interval. Log our hibernation plans better.
14506 - Authoritative dirservers now also cache their directory, so they
14507 have it on start-up.
14510 - Fetch running-routers; cache running-routers; compress
14511 running-routers; serve compressed running-routers.z
14512 - Add NSI installer script contributed by J Doe.
14513 - Commit VC6 and VC7 workspace/project files.
14514 - Commit a tor.spec for making RPM files, with help from jbash.
14515 - Add contrib/torctl.in contributed by Glenn Fink.
14516 - Implement the control-spec's SAVECONF command, to write your
14517 configuration to torrc.
14518 - Get cookie authentication for the controller closer to working.
14519 - Include control-spec.txt in the tarball.
14520 - When set_conf changes our server descriptor, upload a new copy.
14521 But don't upload it too often if there are frequent changes.
14522 - Document authentication config in man page, and document signals
14524 - Clean up confusing parts of man page and torrc.sample.
14525 - Make expand_filename handle ~ and ~username.
14526 - Use autoconf to enable largefile support where necessary. Use
14527 ftello where available, since ftell can fail at 2GB.
14528 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
14529 log more informatively.
14530 - Give a slightly more useful output for "tor -h".
14531 - Refuse application socks connections to port 0.
14532 - Check clock skew for verified servers, but allow unverified
14533 servers and clients to have any clock skew.
14534 - Break DirFetchPostPeriod into:
14535 - DirFetchPeriod for fetching full directory,
14536 - StatusFetchPeriod for fetching running-routers,
14537 - DirPostPeriod for posting server descriptor,
14538 - RendPostPeriod for posting hidden service descriptors.
14539 - Make sure the hidden service descriptors are at a random offset
14540 from each other, to hinder linkability.
14543 Changes in version 0.0.9pre5 - 2004-11-09
14544 o Bugfixes on 0.0.9pre4:
14545 - Fix a seg fault in unit tests (doesn't affect main program).
14546 - Fix an assert bug where a hidden service provider would fail if
14547 the first hop of his rendezvous circuit was down.
14548 - Hidden service operators now correctly handle version 1 style
14549 INTRODUCE1 cells (nobody generates them still, so not a critical
14551 - If do_hup fails, actually notice.
14552 - Handle more errnos from accept() without closing the listener.
14553 Some OpenBSD machines were closing their listeners because
14554 they ran out of file descriptors.
14555 - Send resolve cells to exit routers that are running a new
14556 enough version of the resolve code to work right.
14557 - Better handling of winsock includes on non-MSV win32 compilers.
14558 - Some people had wrapped their tor client/server in a script
14559 that would restart it whenever it died. This did not play well
14560 with our "shut down if your version is obsolete" code. Now people
14561 don't fetch a new directory if their local cached version is
14563 - Make our autogen.sh work on ksh as well as bash.
14566 - Hibernation: New config option "AccountingMaxKB" lets you
14567 set how many KBytes per month you want to allow your server to
14568 consume. Rather than spreading those bytes out evenly over the
14569 month, we instead hibernate for some of the month and pop up
14570 at a deterministic time, work until the bytes are consumed, then
14571 hibernate again. Config option "MonthlyAccountingStart" lets you
14572 specify which day of the month your billing cycle starts on.
14573 - Control interface: a separate program can now talk to your
14574 client/server over a socket, and get/set config options, receive
14575 notifications of circuits and streams starting/finishing/dying,
14576 bandwidth used, etc. The next step is to get some GUIs working.
14577 Let us know if you want to help out. See doc/control-spec.txt .
14578 - Ship a contrib/tor-control.py as an example script to interact
14579 with the control port.
14580 - "tor --hash-password zzyxz" will output a salted password for
14581 use in authenticating to the control interface.
14582 - New log format in config:
14583 "Log minsev[-maxsev] stdout|stderr|syslog" or
14584 "Log minsev[-maxsev] file /var/foo"
14587 - DirPolicy config option, to let people reject incoming addresses
14588 from their dirserver.
14589 - "tor --list-fingerprint" will list your identity key fingerprint
14591 - Add "pass" target for RedirectExit, to make it easier to break
14592 out of a sequence of RedirectExit rules.
14593 - Clients now generate a TLS cert too, in preparation for having
14594 them act more like real nodes.
14595 - Ship src/win32/ in the tarball, so people can use it to build.
14596 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
14598 - New "router-status" line in directory, to better bind each verified
14599 nickname to its identity key.
14600 - Deprecate unofficial config option abbreviations, and abbreviations
14601 not on the command line.
14602 - Add a pure-C tor-resolve implementation.
14603 - Use getrlimit and friends to ensure we can reach MaxConn (currently
14604 1024) file descriptors.
14606 o Code security improvements, inspired by Ilja:
14607 - Replace sprintf with snprintf. (I think they were all safe, but
14609 - Replace strcpy/strncpy with strlcpy in more places.
14610 - Avoid strcat; use snprintf or strlcat instead.
14611 - snprintf wrapper with consistent (though not C99) overflow behavior.
14614 Changes in version 0.0.9pre4 - 2004-10-17
14615 o Bugfixes on 0.0.9pre3:
14616 - If the server doesn't specify an exit policy, use the real default
14617 exit policy, not reject *:*.
14618 - Ignore fascistfirewall when uploading/downloading hidden service
14619 descriptors, since we go through Tor for those; and when using
14620 an HttpProxy, since we assume it can reach them all.
14621 - When looking for an authoritative dirserver, use only the ones
14622 configured at boot. Don't bother looking in the directory.
14623 - The rest of the fix for get_default_conf_file() on older win32.
14624 - Make 'Routerfile' config option obsolete.
14627 - New 'MyFamily nick1,...' config option for a server to
14628 specify other servers that shouldn't be used in the same circuit
14629 with it. Only believed if nick1 also specifies us.
14630 - New 'NodeFamily nick1,nick2,...' config option for a client to
14631 specify nodes that it doesn't want to use in the same circuit.
14632 - New 'Redirectexit pattern address:port' config option for a
14633 server to redirect exit connections, e.g. to a local squid.
14636 Changes in version 0.0.9pre3 - 2004-10-13
14637 o Bugfixes on 0.0.8.1:
14638 - Better torrc example lines for dirbindaddress and orbindaddress.
14639 - Improved bounds checking on parsed ints (e.g. config options and
14640 the ones we find in directories.)
14641 - Better handling of size_t vs int, so we're more robust on 64
14643 - Fix the rest of the bug where a newly started OR would appear
14644 as unverified even after we've added his fingerprint and hupped
14646 - Fix a bug from 0.0.7: when read() failed on a stream, we would
14647 close it without sending back an end. So 'connection refused'
14648 would simply be ignored and the user would get no response.
14650 o Bugfixes on 0.0.9pre2:
14651 - Serving the cached-on-disk directory to people is bad. We now
14652 provide no directory until we've fetched a fresh one.
14653 - Workaround for bug on windows where cached-directories get crlf
14655 - Make get_default_conf_file() work on older windows too.
14656 - If we write a *:* exit policy line in the descriptor, don't write
14657 any more exit policy lines.
14660 - Use only 0.0.9pre1 and later servers for resolve cells.
14661 - Make the dirservers file obsolete.
14662 - Include a dir-signing-key token in directories to tell the
14663 parsing entity which key is being used to sign.
14664 - Remove the built-in bulky default dirservers string.
14665 - New config option "Dirserver %s:%d [fingerprint]", which can be
14666 repeated as many times as needed. If no dirservers specified,
14667 default to moria1,moria2,tor26.
14668 - Make moria2 advertise a dirport of 80, so people behind firewalls
14669 will be able to get a directory.
14670 - Http proxy support
14671 - Dirservers translate requests for http://%s:%d/x to /x
14672 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
14673 be routed through this host.
14674 - Clients ask for /tor/x rather than /x for new enough dirservers.
14675 This way we can one day coexist peacefully with apache.
14676 - Clients specify a "Host: %s%d" http header, to be compatible
14677 with more proxies, and so running squid on an exit node can work.
14680 Changes in version 0.0.8.1 - 2004-10-13
14682 - Fix a seg fault that can be triggered remotely for Tor
14683 clients/servers with an open dirport.
14684 - Fix a rare assert trigger, where routerinfos for entries in
14685 our cpath would expire while we're building the path.
14686 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14687 - Fix a rare seg fault for people running hidden services on
14688 intermittent connections.
14689 - Fix a bug in parsing opt keywords with objects.
14690 - Fix a stale pointer assert bug when a stream detaches and
14692 - Fix a string format vulnerability (probably not exploitable)
14693 in reporting stats locally.
14694 - Fix an assert trigger: sometimes launching circuits can fail
14695 immediately, e.g. because too many circuits have failed recently.
14696 - Fix a compile warning on 64 bit platforms.
14699 Changes in version 0.0.9pre2 - 2004-10-03
14701 - Make fetching a cached directory work for 64-bit platforms too.
14702 - Make zlib.h a required header, not an optional header.
14705 Changes in version 0.0.9pre1 - 2004-10-01
14707 - Stop using separate defaults for no-config-file and
14708 empty-config-file. Now you have to explicitly turn off SocksPort,
14709 if you don't want it open.
14710 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14711 - Improve man page to mention more of the 0.0.8 features.
14712 - Fix a rare seg fault for people running hidden services on
14713 intermittent connections.
14714 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
14716 - Fix more dns related bugs: send back resolve_failed and end cells
14717 more reliably when the resolve fails, rather than closing the
14718 circuit and then trying to send the cell. Also attach dummy resolve
14719 connections to a circuit *before* calling dns_resolve(), to fix
14720 a bug where cached answers would never be sent in RESOLVED cells.
14721 - When we run out of disk space, or other log writing error, don't
14722 crash. Just stop logging to that log and continue.
14723 - We were starting to daemonize before we opened our logs, so if
14724 there were any problems opening logs, we would complain to stderr,
14725 which wouldn't work, and then mysteriously exit.
14726 - Fix a rare bug where sometimes a verified OR would connect to us
14727 before he'd uploaded his descriptor, which would cause us to
14728 assign conn->nickname as though he's unverified. Now we look through
14729 the fingerprint list to see if he's there.
14730 - Fix a rare assert trigger, where routerinfos for entries in
14731 our cpath would expire while we're building the path.
14734 - Clients can ask dirservers for /dir.z to get a compressed version
14735 of the directory. Only works for servers running 0.0.9, of course.
14736 - Make clients cache directories and use them to seed their router
14737 lists at startup. This means clients have a datadir again.
14738 - Configuration infrastructure support for warning on obsolete
14740 - Respond to content-encoding headers by trying to uncompress as
14742 - Reply with a deflated directory when a client asks for "dir.z".
14743 We could use allow-encodings instead, but allow-encodings isn't
14744 specified in HTTP 1.0.
14745 - Raise the max dns workers from 50 to 100.
14746 - Discourage people from setting their dirfetchpostperiod more often
14747 than once per minute.
14748 - Protect dirservers from overzealous descriptor uploading -- wait
14749 10 seconds after directory gets dirty, before regenerating.
14752 Changes in version 0.0.8 - 2004-08-25
14753 o Port it to SunOS 5.9 / Athena
14756 Changes in version 0.0.8rc2 - 2004-08-20
14757 o Make it compile on cygwin again.
14758 o When picking unverified routers, skip those with low uptime and/or
14759 low bandwidth, depending on what properties you care about.
14762 Changes in version 0.0.8rc1 - 2004-08-18
14763 o Changes from 0.0.7.3:
14765 - Fix assert triggers: if the other side returns an address 0.0.0.0,
14766 don't put it into the client dns cache.
14767 - If a begin failed due to exit policy, but we believe the IP address
14768 should have been allowed, switch that router to exitpolicy reject *:*
14769 until we get our next directory.
14771 - Clients choose nodes proportional to advertised bandwidth.
14772 - Avoid using nodes with low uptime as introduction points.
14773 - Handle servers with dynamic IP addresses: don't replace
14774 options->Address with the resolved one at startup, and
14775 detect our address right before we make a routerinfo each time.
14776 - 'FascistFirewall' option to pick dirservers and ORs on specific
14777 ports; plus 'FirewallPorts' config option to tell FascistFirewall
14778 which ports are open. (Defaults to 80,443)
14779 - Be more aggressive about trying to make circuits when the network
14780 has changed (e.g. when you unsuspend your laptop).
14781 - Check for time skew on http headers; report date in response to
14783 - If the entrynode config line has only one node, don't pick it as
14785 - Add strict{entry|exit}nodes config options. If set to 1, then
14786 we refuse to build circuits that don't include the specified entry
14788 - OutboundBindAddress config option, to bind to a specific
14789 IP address for outgoing connect()s.
14790 - End truncated log entries (e.g. directories) with "[truncated]".
14792 o Patches to 0.0.8preX:
14794 - Patches to compile and run on win32 again (maybe)?
14795 - Fix crash when looking for ~/.torrc with no $HOME set.
14796 - Fix a race bug in the unit tests.
14797 - Handle verified/unverified name collisions better when new
14798 routerinfo's arrive in a directory.
14799 - Sometimes routers were getting entered into the stats before
14800 we'd assigned their identity_digest. Oops.
14801 - Only pick and establish intro points after we've gotten a
14804 - AllowUnverifiedNodes config option to let circuits choose no-name
14805 routers in entry,middle,exit,introduction,rendezvous positions.
14806 Allow middle and rendezvous positions by default.
14807 - Add a man page for tor-resolve.
14810 Changes in version 0.0.7.3 - 2004-08-12
14811 o Stop dnsworkers from triggering an assert failure when you
14812 ask them to resolve the host "".
14815 Changes in version 0.0.8pre3 - 2004-08-09
14816 o Changes from 0.0.7.2:
14817 - Allow multiple ORs with same nickname in routerlist -- now when
14818 people give us one identity key for a nickname, then later
14819 another, we don't constantly complain until the first expires.
14820 - Remember used bandwidth (both in and out), and publish 15-minute
14821 snapshots for the past day into our descriptor.
14822 - You can now fetch $DIRURL/running-routers to get just the
14823 running-routers line, not the whole descriptor list. (But
14824 clients don't use this yet.)
14825 - When people mistakenly use Tor as an http proxy, point them
14826 at the tor-doc.html rather than the INSTALL.
14827 - Remove our mostly unused -- and broken -- hex_encode()
14828 function. Use base16_encode() instead. (Thanks to Timo Lindfors
14829 for pointing out this bug.)
14830 - Rotate onion keys every 12 hours, not every 2 hours, so we have
14831 fewer problems with people using the wrong key.
14832 - Change the default exit policy to reject the default edonkey,
14833 kazaa, gnutella ports.
14834 - Add replace_file() to util.[ch] to handle win32's rename().
14836 o Changes from 0.0.8preX:
14837 - Fix two bugs in saving onion keys to disk when rotating, so
14838 hopefully we'll get fewer people using old onion keys.
14839 - Fix an assert error that was making SocksPolicy not work.
14840 - Be willing to expire routers that have an open dirport -- it's
14841 just the authoritative dirservers we want to not forget.
14842 - Reject tor-resolve requests for .onion addresses early, so we
14843 don't build a whole rendezvous circuit and then fail.
14844 - When you're warning a server that he's unverified, don't cry
14845 wolf unpredictably.
14846 - Fix a race condition: don't try to extend onto a connection
14847 that's still handshaking.
14848 - For servers in clique mode, require the conn to be open before
14849 you'll choose it for your path.
14850 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
14851 end relay cell, etc.
14852 - Measure bandwidth capacity over the last 24 hours, not just 12
14853 - Bugfix: authoritative dirservers were making and signing a new
14854 directory for each client, rather than reusing the cached one.
14857 Changes in version 0.0.8pre2 - 2004-08-04
14858 o Changes from 0.0.7.2:
14860 - Check directory signature _before_ you decide whether you're
14861 you're running an obsolete version and should exit.
14862 - Check directory signature _before_ you parse the running-routers
14863 list to decide who's running or verified.
14864 - Bugfixes and features:
14865 - Check return value of fclose while writing to disk, so we don't
14866 end up with broken files when servers run out of disk space.
14867 - Log a warning if the user uses an unsafe socks variant, so people
14868 are more likely to learn about privoxy or socat.
14869 - Dirservers now include RFC1123-style dates in the HTTP headers,
14870 which one day we will use to better detect clock skew.
14872 o Changes from 0.0.8pre1:
14873 - Make it compile without warnings again on win32.
14874 - Log a warning if you're running an unverified server, to let you
14875 know you might want to get it verified.
14876 - Only pick a default nickname if you plan to be a server.
14879 Changes in version 0.0.8pre1 - 2004-07-23
14881 - Made our unit tests compile again on OpenBSD 3.5, and tor
14882 itself compile again on OpenBSD on a sparc64.
14883 - We were neglecting milliseconds when logging on win32, so
14884 everything appeared to happen at the beginning of each second.
14886 o Protocol changes:
14887 - 'Extend' relay cell payloads now include the digest of the
14888 intended next hop's identity key. Now we can verify that we're
14889 extending to the right router, and also extend to routers we
14890 hadn't heard of before.
14893 - Tor nodes can now act as relays (with an advertised ORPort)
14894 without being manually verified by the dirserver operators.
14895 - Uploaded descriptors of unverified routers are now accepted
14896 by the dirservers, and included in the directory.
14897 - Verified routers are listed by nickname in the running-routers
14898 list; unverified routers are listed as "$<fingerprint>".
14899 - We now use hash-of-identity-key in most places rather than
14900 nickname or addr:port, for improved security/flexibility.
14901 - To avoid Sybil attacks, paths still use only verified servers.
14902 But now we have a chance to play around with hybrid approaches.
14903 - Nodes track bandwidth usage to estimate capacity (not used yet).
14904 - ClientOnly option for nodes that never want to become servers.
14905 - Directory caching.
14906 - "AuthoritativeDir 1" option for the official dirservers.
14907 - Now other nodes (clients and servers) will cache the latest
14908 directory they've pulled down.
14909 - They can enable their DirPort to serve it to others.
14910 - Clients will pull down a directory from any node with an open
14911 DirPort, and check the signature/timestamp correctly.
14912 - Authoritative dirservers now fetch directories from other
14913 authdirservers, to stay better synced.
14914 - Running-routers list tells who's down also, along with noting
14915 if they're verified (listed by nickname) or unverified (listed
14917 - Allow dirservers to serve running-router list separately.
14918 This isn't used yet.
14919 - ORs connect-on-demand to other ORs
14920 - If you get an extend cell to an OR you're not connected to,
14921 connect, handshake, and forward the create cell.
14922 - The authoritative dirservers stay connected to everybody,
14923 and everybody stays connected to 0.0.7 servers, but otherwise
14924 clients/servers expire unused connections after 5 minutes.
14925 - When servers get a sigint, they delay 30 seconds (refusing new
14926 connections) then exit. A second sigint causes immediate exit.
14927 - File and name management:
14928 - Look for .torrc if no CONFDIR "torrc" is found.
14929 - If no datadir is defined, then choose, make, and secure ~/.tor
14931 - If torrc not found, exitpolicy reject *:*.
14932 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
14933 - If no nickname is defined, derive default from hostname.
14934 - Rename secret key files, e.g. identity.key -> secret_id_key,
14935 to discourage people from mailing their identity key to tor-ops.
14936 - Refuse to build a circuit before the directory has arrived --
14937 it won't work anyway, since you won't know the right onion keys
14939 - Try other dirservers immediately if the one you try is down. This
14940 should tolerate down dirservers better now.
14941 - Parse tor version numbers so we can do an is-newer-than check
14942 rather than an is-in-the-list check.
14943 - New socks command 'resolve', to let us shim gethostbyname()
14945 - A 'tor_resolve' script to access the socks resolve functionality.
14946 - A new socks-extensions.txt doc file to describe our
14947 interpretation and extensions to the socks protocols.
14948 - Add a ContactInfo option, which gets published in descriptor.
14949 - Publish OR uptime in descriptor (and thus in directory) too.
14950 - Write tor version at the top of each log file
14951 - New docs in the tarball:
14953 - Document that you should proxy your SSL traffic too.
14956 Changes in version 0.0.7.2 - 2004-07-07
14957 o A better fix for the 0.0.0.0 problem, that will hopefully
14958 eliminate the remaining related assertion failures.
14961 Changes in version 0.0.7.1 - 2004-07-04
14962 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
14963 since internally we use 0.0.0.0 to signify "not yet resolved".
14966 Changes in version 0.0.7 - 2004-06-07
14967 o Updated the man page to reflect the new features.
14970 Changes in version 0.0.7rc2 - 2004-06-06
14971 o Changes from 0.0.7rc1:
14972 - Make it build on Win32 again.
14973 o Changes from 0.0.6.2:
14974 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
14978 Changes in version 0.0.7rc1 - 2004-06-02
14980 - On sighup, we were adding another log without removing the first
14981 one. So log messages would get duplicated n times for n sighups.
14982 - Several cases of using a connection after we'd freed it. The
14983 problem was that connections that are pending resolve are in both
14984 the pending_resolve tree, and also the circuit's resolving_streams
14985 list. When you want to remove one, you must remove it from both.
14986 - Fix a double-mark-for-close where an end cell arrived for a
14987 resolving stream, and then the resolve failed.
14988 - Check directory signatures based on name of signer, not on whom
14989 we got the directory from. This will let us cache directories more
14992 - Crank up some of our constants to handle more users.
14995 Changes in version 0.0.7pre1 - 2004-06-02
14996 o Fixes for crashes and other obnoxious bugs:
14997 - Fix an epipe bug: sometimes when directory connections failed
14998 to connect, we would give them a chance to flush before closing
15000 - When we detached from a circuit because of resolvefailed, we
15001 would immediately try the same circuit twice more, and then
15002 give up on the resolve thinking we'd tried three different
15004 - Limit the number of intro circuits we'll attempt to build for a
15005 hidden service per 15-minute period.
15006 - Check recommended-software string *early*, before actually parsing
15007 the directory. Thus we can detect an obsolete version and exit,
15008 even if the new directory format doesn't parse.
15009 o Fixes for security bugs:
15010 - Remember which nodes are dirservers when you startup, and if a
15011 random OR enables his dirport, don't automatically assume he's
15012 a trusted dirserver.
15014 - Directory connections were asking the wrong poll socket to
15015 start writing, and not asking themselves to start writing.
15016 - When we detached from a circuit because we sent a begin but
15017 didn't get a connected, we would use it again the first time;
15018 but after that we would correctly switch to a different one.
15019 - Stop warning when the first onion decrypt attempt fails; they
15020 will sometimes legitimately fail now that we rotate keys.
15021 - Override unaligned-access-ok check when $host_cpu is ia64 or
15022 arm. Apparently they allow it but the kernel whines.
15023 - Dirservers try to reconnect periodically too, in case connections
15025 - Fix some memory leaks in directory servers.
15026 - Allow backslash in Win32 filenames.
15027 - Made Tor build complain-free on FreeBSD, hopefully without
15028 breaking other BSD builds. We'll see.
15030 - Doxygen markup on all functions and global variables.
15031 - Make directory functions update routerlist, not replace it. So
15032 now directory disagreements are not so critical a problem.
15033 - Remove the upper limit on number of descriptors in a dirserver's
15034 directory (not that we were anywhere close).
15035 - Allow multiple logfiles at different severity ranges.
15036 - Allow *BindAddress to specify ":port" rather than setting *Port
15037 separately. Allow multiple instances of each BindAddress config
15038 option, so you can bind to multiple interfaces if you want.
15039 - Allow multiple exit policy lines, which are processed in order.
15040 Now we don't need that huge line with all the commas in it.
15041 - Enable accept/reject policies on SOCKS connections, so you can bind
15042 to 0.0.0.0 but still control who can use your OP.
15045 Changes in version 0.0.6.2 - 2004-05-16
15046 o Our integrity-checking digest was checking only the most recent cell,
15047 not the previous cells like we'd thought.
15048 Thanks to Stefan Mark for finding the flaw!
15051 Changes in version 0.0.6.1 - 2004-05-06
15052 o Fix two bugs in our AES counter-mode implementation (this affected
15053 onion-level stream encryption, but not TLS-level). It turns
15054 out we were doing something much more akin to a 16-character
15055 polyalphabetic cipher. Oops.
15056 Thanks to Stefan Mark for finding the flaw!
15057 o Retire moria3 as a directory server, and add tor26 as a directory
15061 Changes in version 0.0.6 - 2004-05-02
15062 [version bump only]
15065 Changes in version 0.0.6rc4 - 2004-05-01
15066 o Update the built-in dirservers list to use the new directory format
15067 o Fix a rare seg fault: if a node offering a hidden service attempts
15068 to build a circuit to Alice's rendezvous point and fails before it
15069 reaches the last hop, it retries with a different circuit, but
15071 o Handle windows socket errors correctly.
15074 Changes in version 0.0.6rc3 - 2004-04-28
15075 o Don't expire non-general excess circuits (if we had enough
15076 circuits open, we were expiring rendezvous circuits -- even
15077 when they had a stream attached. oops.)
15078 o Fetch randomness from /dev/urandom better (not via fopen/fread)
15079 o Better debugging for tls errors
15080 o Some versions of openssl have an SSL_pending function that erroneously
15081 returns bytes when there is a non-application record pending.
15082 o Set Content-Type on the directory and hidserv descriptor.
15083 o Remove IVs from cipher code, since AES-ctr has none.
15084 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
15085 o We were using an array of length zero in a few places.
15086 o win32's gethostbyname can't resolve an IP to an IP.
15087 o win32's close can't close a socket.
15090 Changes in version 0.0.6rc2 - 2004-04-26
15091 o Fix a bug where we were closing tls connections intermittently.
15092 It turns out openssl keeps its errors around -- so if an error
15093 happens, and you don't ask about it, and then another openssl
15094 operation happens and succeeds, and you ask if there was an error,
15095 it tells you about the first error. Fun fun.
15096 o Fix a bug that's been lurking since 27 may 03 (!)
15097 When passing back a destroy cell, we would use the wrong circ id.
15098 'Mostly harmless', but still worth fixing.
15099 o Since we don't support truncateds much, don't bother sending them;
15100 just close the circ.
15101 o check for <machine/limits.h> so we build on NetBSD again (I hope).
15102 o don't crash if a conn that sent a begin has suddenly lost its circuit
15103 (this was quite rare).
15106 Changes in version 0.0.6rc1 - 2004-04-25
15107 o We now rotate link (tls context) keys and onion keys.
15108 o CREATE cells now include oaep padding, so you can tell
15109 if you decrypted them correctly.
15110 o Add bandwidthburst to server descriptor.
15111 o Directories now say which dirserver signed them.
15112 o Use a tor_assert macro that logs failed assertions too.
15115 Changes in version 0.0.6pre5 - 2004-04-18
15116 o changes from 0.0.6pre4:
15117 - make tor build on broken freebsd 5.2 installs
15118 - fix a failed assert when you try an intro point, get a nack, and try
15119 a second one and it works.
15120 - when alice uses a port that the hidden service doesn't accept,
15121 it now sends back an end cell (denied by exit policy). otherwise
15122 alice would just have to wait to time out.
15123 - fix another rare bug: when we had tried all the intro
15124 points for a hidden service, we fetched the descriptor
15125 again, but we left our introcirc thinking it had already
15126 sent an intro, so it kept waiting for a response...
15127 - bugfix: when you sleep your hidden-service laptop, as soon
15128 as it wakes up it tries to upload a service descriptor, but
15129 socketpair fails for some reason (localhost not up yet?).
15130 now we simply give up on that upload, and we'll try again later.
15131 i'd still like to find the bug though.
15132 - if an intro circ waiting for an ack dies before getting one, then
15134 - we were reusing stale service descriptors and refetching usable
15138 Changes in version 0.0.6pre4 - 2004-04-14
15139 o changes from 0.0.6pre3:
15140 - when bob fails to connect to the rendezvous point, and his
15141 circ didn't fail because of the rendezvous point itself, then
15142 he retries a couple of times
15143 - we expire introduction and rendezvous circs more thoroughly
15144 (sometimes they were hanging around forever)
15145 - we expire unattached rendezvous streams that have been around
15146 too long (they were sticking around forever).
15147 - fix a measly fencepost error that was crashing everybody with
15151 Changes in version 0.0.6pre3 - 2004-04-14
15152 o changes from 0.0.6pre2:
15153 - make hup work again
15154 - fix some memory leaks for dirservers
15155 - allow more skew in rendezvous descriptor timestamps, to help
15156 handle people like blanu who don't know what time it is
15157 - normal circs are 3 hops, but some rend/intro circs are 4, if
15158 the initiator doesn't get to choose the last hop
15159 - send acks for introductions, so alice can know whether to try
15161 - bob publishes intro points more correctly
15162 o changes from 0.0.5:
15163 - fix an assert trigger that's been plaguing us since the days
15164 of 0.0.2prexx (thanks weasel!)
15165 - retry stream correctly when we fail to connect because of
15166 exit-policy-reject (should try another) or can't-resolve-address
15167 (also should try another, because dns on random internet servers
15169 - when we hup a dirserver and we've *removed* a server from the
15170 approved-routers list, now we remove that server from the
15171 in-memory directories too
15174 Changes in version 0.0.6pre2 - 2004-04-08
15175 o We fixed our base32 implementation. Now it works on all architectures.
15178 Changes in version 0.0.6pre1 - 2004-04-08
15180 - Hidden services and rendezvous points are implemented. Go to
15181 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
15182 hidden services. (This only works via a socks4a proxy such as
15183 Privoxy, and currently it's quite slow.)
15186 Changes in version 0.0.5 - 2004-03-30
15187 [version bump only]
15190 Changes in version 0.0.5rc3 - 2004-03-29
15191 o Install torrc as torrc.sample -- we no longer clobber your
15193 o Re-enable recommendedversion checking (we broke it in rc2, oops)
15194 o Add in a 'notice' log level for things the operator should hear
15195 but that aren't warnings
15198 Changes in version 0.0.5rc2 - 2004-03-29
15199 o Hold socks connection open until reply is flushed (if possible)
15200 o Make exit nodes resolve IPs to IPs immediately, rather than asking
15201 the dns farm to do it.
15202 o Fix c99 aliasing warnings in rephist.c
15203 o Don't include server descriptors that are older than 24 hours in the
15205 o Give socks 'reject' replies their whole 15s to attempt to flush,
15206 rather than seeing the 60s timeout and assuming the flush had failed.
15207 o Clean automake droppings from the cvs repository
15210 Changes in version 0.0.5rc1 - 2004-03-28
15211 o Fix mangled-state bug in directory fetching (was causing sigpipes).
15212 o Only build circuits after we've fetched the directory: clients were
15213 using only the directory servers before they'd fetched a directory.
15214 This also means longer startup time; so it goes.
15215 o Fix an assert trigger where an OP would fail to handshake, and we'd
15216 expect it to have a nickname.
15217 o Work around a tsocks bug: do a socks reject when AP connection dies
15218 early, else tsocks goes into an infinite loop.
15221 Changes in version 0.0.4 - 2004-03-26
15222 o When connecting to a dirserver or OR and the network is down,
15226 Changes in version 0.0.3 - 2004-03-26
15227 o Warn and fail if server chose a nickname with illegal characters
15228 o Port to Solaris and Sparc:
15229 - include missing header fcntl.h
15230 - have autoconf find -lsocket -lnsl automatically
15231 - deal with hardware word alignment
15232 - make uname() work (solaris has a different return convention)
15233 - switch from using signal() to sigaction()
15234 o Preliminary work on reputation system:
15235 - Keep statistics on success/fail of connect attempts; they're published
15236 by kill -USR1 currently.
15237 - Add a RunTesting option to try to learn link state by creating test
15238 circuits, even when SocksPort is off.
15239 - Remove unused open circuits when there are too many.
15242 Changes in version 0.0.2 - 2004-03-19
15243 - Include strlcpy and strlcat for safer string ops
15244 - define INADDR_NONE so we compile (but still not run) on solaris
15247 Changes in version 0.0.2pre27 - 2004-03-14
15249 - Allow internal tor networks (we were rejecting internal IPs,
15250 now we allow them if they're set explicitly).
15251 - And fix a few endian issues.
15254 Changes in version 0.0.2pre26 - 2004-03-14
15256 - If a stream times out after 15s without a connected cell, don't
15257 try that circuit again: try a new one.
15258 - Retry streams at most 4 times. Then give up.
15259 - When a dirserver gets a descriptor from an unknown router, it
15260 logs its fingerprint (so the dirserver operator can choose to
15261 accept it even without mail from the server operator).
15262 - Inform unapproved servers when we reject their descriptors.
15263 - Make tor build on Windows again. It works as a client, who knows
15265 - Clearer instructions in the torrc for how to set up a server.
15266 - Be more efficient about reading fd's when our global token bucket
15267 (used for rate limiting) becomes empty.
15269 - Stop asserting that computers always go forward in time. It's
15271 - When we sent a cell (e.g. destroy) and then marked an OR connection
15272 expired, we might close it before finishing a flush if the other
15273 side isn't reading right then.
15274 - Don't allow dirservers to start if they haven't defined
15275 RecommendedVersions
15276 - We were caching transient dns failures. Oops.
15277 - Prevent servers from publishing an internal IP as their address.
15278 - Address a strcat vulnerability in circuit.c
15281 Changes in version 0.0.2pre25 - 2004-03-04
15283 - Put the OR's IP in its router descriptor, not its fqdn. That way
15284 we'll stop being stalled by gethostbyname for nodes with flaky dns,
15287 - If the user typed in an address that didn't resolve, the server
15291 Changes in version 0.0.2pre24 - 2004-03-03
15293 - Fix an assertion failure in dns.c, where we were trying to dequeue
15294 a pending dns resolve even if it wasn't pending
15295 - Fix a spurious socks5 warning about still trying to write after the
15296 connection is finished.
15297 - Hold certain marked_for_close connections open until they're finished
15298 flushing, rather than losing bytes by closing them too early.
15299 - Correctly report the reason for ending a stream
15300 - Remove some duplicate calls to connection_mark_for_close
15301 - Put switch_id and start_daemon earlier in the boot sequence, so it
15302 will actually try to chdir() to options.DataDirectory
15303 - Make 'make test' exit(1) if a test fails; fix some unit tests
15304 - Make tor fail when you use a config option it doesn't know about,
15305 rather than warn and continue.
15306 - Make --version work
15307 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
15310 Changes in version 0.0.2pre23 - 2004-02-29
15312 - Print a statement when the first circ is finished, so the user
15313 knows it's working.
15314 - If a relay cell is unrecognized at the end of the circuit,
15315 send back a destroy. (So attacks to mutate cells are more
15317 - New config option 'excludenodes' to avoid certain nodes for circuits.
15318 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
15319 so you can collect coredumps there.
15321 - Fix a bug in tls flushing where sometimes data got wedged and
15322 didn't flush until more data got sent. Hopefully this bug was
15323 a big factor in the random delays we were seeing.
15324 - Make 'connected' cells include the resolved IP, so the client
15325 dns cache actually gets populated.
15326 - Disallow changing from ORPort=0 to ORPort>0 on hup.
15327 - When we time-out on a stream and detach from the circuit, send an
15328 end cell down it first.
15329 - Only warn about an unknown router (in exitnodes, entrynodes,
15330 excludenodes) after we've fetched a directory.
15333 Changes in version 0.0.2pre22 - 2004-02-26
15335 - Servers publish less revealing uname information in descriptors.
15336 - More memory tracking and assertions, to crash more usefully when
15338 - If the default torrc isn't there, just use some default defaults.
15339 Plus provide an internal dirservers file if they don't have one.
15340 - When the user tries to use Tor as an http proxy, give them an http
15341 501 failure explaining that we're a socks proxy.
15342 - Dump a new router.desc on hup, to help confused people who change
15343 their exit policies and then wonder why router.desc doesn't reflect
15345 - Clean up the generic tor.sh init script that we ship with.
15347 - If the exit stream is pending on the resolve, and a destroy arrives,
15348 then the stream wasn't getting removed from the pending list. I
15349 think this was the one causing recent server crashes.
15350 - Use a more robust poll on OSX 10.3, since their poll is flaky.
15351 - When it couldn't resolve any dirservers, it was useless from then on.
15352 Now it reloads the RouterFile (or default dirservers) if it has no
15354 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
15355 many users don't even *have* a /usr/local/sbin/.
15358 Changes in version 0.0.2pre21 - 2004-02-18
15360 - There's a ChangeLog file that actually reflects the changelog.
15361 - There's a 'torify' wrapper script, with an accompanying
15362 tor-tsocks.conf, that simplifies the process of using tsocks for
15363 tor. It even has a man page.
15364 - The tor binary gets installed to sbin rather than bin now.
15365 - Retry streams where the connected cell hasn't arrived in 15 seconds
15366 - Clean up exit policy handling -- get the default out of the torrc,
15367 so we can update it without forcing each server operator to fix
15369 - Allow imaps and pop3s in default exit policy
15371 - Prevent picking middleman nodes as the last node in the circuit
15374 Changes in version 0.0.2pre20 - 2004-01-30
15376 - We now have a deb package, and it's in debian unstable. Go to
15377 it, apt-getters. :)
15378 - I've split the TotalBandwidth option into BandwidthRate (how many
15379 bytes per second you want to allow, long-term) and
15380 BandwidthBurst (how many bytes you will allow at once before the cap
15381 kicks in). This better token bucket approach lets you, say, set
15382 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
15383 performance while not exceeding your monthly bandwidth quota.
15384 - Push out a tls record's worth of data once you've got it, rather
15385 than waiting until you've read everything waiting to be read. This
15386 may improve performance by pipelining better. We'll see.
15387 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
15388 from failed circuits (if they haven't been connected yet) and attach
15390 - Expire old streams that haven't managed to connect. Some day we'll
15391 have them reattach to new circuits instead.
15394 - Fix several memory leaks that were causing servers to become bloated
15396 - Fix a few very rare assert triggers. A few more remain.
15397 - Setuid to User _before_ complaining about running as root.
15400 Changes in version 0.0.2pre19 - 2004-01-07
15402 - Fix deadlock condition in dns farm. We were telling a child to die by
15403 closing the parent's file descriptor to him. But newer children were
15404 inheriting the open file descriptor from the parent, and since they
15405 weren't closing it, the socket never closed, so the child never read
15406 eof, so he never knew to exit. Similarly, dns workers were holding
15407 open other sockets, leading to all sorts of chaos.
15408 - New cleaner daemon() code for forking and backgrounding.
15409 - If you log to a file, it now prints an entry at the top of the
15410 logfile so you know it's working.
15411 - The onionskin challenge length was 30 bytes longer than necessary.
15412 - Started to patch up the spec so it's not quite so out of date.
15415 Changes in version 0.0.2pre18 - 2004-01-02
15417 - Fix endian issues with the 'integrity' field in the relay header.
15418 - Fix a potential bug where connections in state
15419 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
15422 Changes in version 0.0.2pre17 - 2003-12-30
15424 - Made --debuglogfile (or any second log file, actually) work.
15425 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
15426 adversary could force us into an infinite loop.
15429 - Each onionskin handshake now includes a hash of the computed key,
15430 to prove the server's identity and help perfect forward secrecy.
15431 - Changed cell size from 256 to 512 bytes (working toward compatibility
15433 - Changed cell length to 2 bytes, and moved it to the relay header.
15434 - Implemented end-to-end integrity checking for the payloads of
15436 - Separated streamid from 'recognized' (otherwise circuits will get
15437 messed up when we try to have streams exit from the middle). We
15438 use the integrity-checking to confirm that a cell is addressed to
15440 - Randomize the initial circid and streamid values, so an adversary who
15441 breaks into a node can't learn how many circuits or streams have
15445 Changes in version 0.0.2pre16 - 2003-12-14
15447 - Fixed a bug that made HUP trigger an assert
15448 - Fixed a bug where a circuit that immediately failed wasn't being
15449 counted as a failed circuit in counting retries.
15452 - Now we close the circuit when we get a truncated cell: otherwise we're
15453 open to an anonymity attack where a bad node in the path truncates
15454 the circuit and then we open streams at him.
15455 - Add port ranges to exit policies
15456 - Add a conservative default exit policy
15457 - Warn if you're running tor as root
15458 - on HUP, retry OR connections and close/rebind listeners
15459 - options.EntryNodes: try these nodes first when picking the first node
15460 - options.ExitNodes: if your best choices happen to include any of
15461 your preferred exit nodes, you choose among just those preferred
15463 - options.ExcludedNodes: nodes that are never picked in path building
15466 Changes in version 0.0.2pre15 - 2003-12-03
15467 o Robustness and bugfixes:
15468 - Sometimes clients would cache incorrect DNS resolves, which would
15469 really screw things up.
15470 - An OP that goes offline would slowly leak all its sockets and stop
15472 - A wide variety of bugfixes in exit node selection, exit policy
15473 handling, and processing pending streams when a new circuit is
15475 - Pick nodes for a path only from those the directory says are up
15476 - Choose randomly from all running dirservers, not always the first one
15477 - Increase allowed http header size for directory fetch.
15478 - Stop writing to stderr (if we're daemonized it will be closed).
15479 - Enable -g always, so cores will be more useful to me.
15480 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
15483 - Wrote a man page. It lists commonly used options.
15486 - Change default loglevel to warn.
15487 - Make PidFile default to null rather than littering in your CWD.
15488 - OnionRouter config option is now obsolete. Instead it just checks
15490 - Moved to a single unified torrc file for both clients and servers.
15493 Changes in version 0.0.2pre14 - 2003-11-29
15494 o Robustness and bugfixes:
15495 - Force the admin to make the DataDirectory himself
15496 - to get ownership/permissions right
15497 - so clients no longer make a DataDirectory and then never use it
15498 - fix bug where a client who was offline for 45 minutes would never
15499 pull down a directory again
15500 - fix (or at least hide really well) the dns assert bug that was
15501 causing server crashes
15502 - warnings and improved robustness wrt clockskew for certs
15503 - use the native daemon(3) to daemonize, when available
15504 - exit if bind() fails
15505 - exit if neither socksport nor orport is defined
15506 - include our own tor_timegm (Win32 doesn't have its own)
15507 - bugfix for win32 with lots of connections
15508 - fix minor bias in PRNG
15509 - make dirserver more robust to corrupt cached directory
15512 - Wrote the design document (woo)
15514 o Circuit building and exit policies:
15515 - Circuits no longer try to use nodes that the directory has told them
15517 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
15518 bitcounts (18.0.0.0/8).
15519 - Make AP connections standby for a circuit if no suitable circuit
15520 exists, rather than failing
15521 - Circuits choose exit node based on addr/port, exit policies, and
15522 which AP connections are standing by
15523 - Bump min pathlen from 2 to 3
15524 - Relay end cells have a payload to describe why the stream ended.
15525 - If the stream failed because of exit policy, try again with a new
15527 - Clients have a dns cache to remember resolved addresses.
15528 - Notice more quickly when we have no working circuits
15531 - APPort is now called SocksPort
15532 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
15534 - RecommendedVersions is now a config variable rather than
15535 hardcoded (for dirservers)
15536 - Reloads config on HUP
15537 - Usage info on -h or --help
15538 - If you set User and Group config vars, it'll setu/gid to them.
15541 Changes in version 0.0.2pre13 - 2003-10-19
15542 o General stability:
15543 - SSL_write no longer fails when it returns WANTWRITE and the number
15544 of bytes in the buf has changed by the next SSL_write call.
15545 - Fix segfault fetching directory when network is down
15546 - Fix a variety of minor memory leaks
15547 - Dirservers reload the fingerprints file on HUP, so I don't have
15548 to take down the network when I approve a new router
15549 - Default server config file has explicit Address line to specify fqdn
15552 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
15553 - Make listener connections not ever alloc bufs
15555 o Autoconf improvements:
15556 - don't clobber an external CFLAGS in ./configure
15557 - Make install now works
15558 - create var/lib/tor on make install
15559 - autocreate a tor.sh initscript to help distribs
15560 - autocreate the torrc and sample-server-torrc with correct paths
15562 o Log files and Daemonizing now work:
15563 - If --DebugLogFile is specified, log to it at -l debug
15564 - If --LogFile is specified, use it instead of commandline
15565 - If --RunAsDaemon is set, tor forks and backgrounds on startup