1 Changes in version 0.2.4.21 - 2014-02-28
2 Tor 0.2.4.21 further improves security against potential adversaries who
3 find breaking 1024-bit crypto doable, and backports several stability
4 and robustness patches from the 0.2.5 branch.
6 o Major features (client security):
7 - When we choose a path for a 3-hop circuit, make sure it contains
8 at least one relay that supports the NTor circuit extension
9 handshake. Otherwise, there is a chance that we're building
10 a circuit that's worth attacking by an adversary who finds
11 breaking 1024-bit crypto doable, and that chance changes the game
12 theory. Implements ticket 9777.
15 - Do not treat streams that fail with reason
16 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
17 since it could also indicate an ENETUNREACH connection error. Fixes
18 part of bug 10777; bugfix on 0.2.4.8-alpha.
20 o Code simplification and refactoring:
21 - Remove data structures which were introduced to implement the
22 CellStatistics option: they are now redundant with the new timestamp
23 field in the regular packed_cell_t data structure, which we did
24 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
27 - Always clear OpenSSL bignums before freeing them -- even bignums
28 that don't contain secrets. Resolves ticket 10793. Patch by
30 - Build without warnings under clang 3.4. (We have some macros that
31 define static functions only some of which will get used later in
32 the module. Starting with clang 3.4, these give a warning unless the
33 unused attribute is set on them.) Resolves ticket 10904.
34 - Update geoip and geoip6 files to the February 7 2014 Maxmind
35 GeoLite2 Country database.
38 - Set the listen() backlog limit to the largest actually supported
39 on the system, not to the value in a header file. Fixes bug 9716;
40 bugfix on every released Tor.
41 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
42 exit node as a NOROUTE error, not an INTERNAL error, since they
43 can apparently happen when trying to connect to the wrong sort
44 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
45 - Fix build warnings about missing "a2x" comment when building the
46 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
47 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
48 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
49 not entirely remove it from the connection lists. Fixes bug 9602;
50 bugfix on 0.2.4.4-alpha.
51 - Fix a segmentation fault in our benchmark code when running with
52 Fedora's OpenSSL package, or any other OpenSSL that provides
53 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
54 - Turn "circuit handshake stats since last time" log messages into a
55 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
57 o Documentation fixes:
58 - Document that all but one DirPort entry must have the NoAdvertise
59 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
62 Changes in version 0.2.5.2-alpha - 2013-02-13
63 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
64 like the "poor random number generation" fix and the "building too many
65 circuits" fix. It also further improves security against potential
66 adversaries who find breaking 1024-bit crypto doable, and launches
67 pluggable transports on demand (which gets us closer to integrating
68 pluggable transport support by default -- not to be confused with Tor
69 bundles enabling pluggable transports and bridges by default).
71 o Major features (client security):
72 - When we choose a path for a 3-hop circuit, make sure it contains
73 at least one relay that supports the NTor circuit extension
74 handshake. Otherwise, there is a chance that we're building
75 a circuit that's worth attacking by an adversary who finds
76 breaking 1024-bit crypto doable, and that chance changes the game
77 theory. Implements ticket 9777.
78 - Clients now look at the "usecreatefast" consensus parameter to
79 decide whether to use CREATE_FAST or CREATE cells for the first hop
80 of their circuit. This approach can improve security on connections
81 where Tor's circuit handshake is stronger than the available TLS
82 connection security levels, but the tradeoff is more computational
83 load on guard relays. Implements proposal 221. Resolves ticket 9386.
85 o Major features (bridges):
86 - Don't launch pluggable transport proxies if we don't have any
87 bridges configured that would use them. Now we can list many
88 pluggable transports, and Tor will dynamically start one when it
89 hears a bridge address that needs it. Resolves ticket 5018.
90 - The bridge directory authority now assigns status flags (Stable,
91 Guard, etc) to bridges based on thresholds calculated over all
92 Running bridges. Now bridgedb can finally make use of its features
93 to e.g. include at least one Stable bridge in its answers. Fixes
96 o Major features (other):
97 - Extend ORCONN controller event to include an "ID" parameter,
98 and add four new controller event types CONN_BW, CIRC_BW,
99 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
100 The new events are emitted in private Tor networks only, with the
101 goal of being able to better track performance and load during
102 full-network simulations. Implements proposal 218 and ticket 7359.
103 - On some platforms (currently: recent OSX versions, glibc-based
104 platforms that support the ELF format, and a few other
105 Unix-like operating systems), Tor can now dump stack traces
106 when a crash occurs or an assertion fails. By default, traces
107 are dumped to stderr (if possible) and to any logs that are
108 reporting errors. Implements ticket 9299.
111 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
112 not entirely remove it from the connection lists. Fixes bug 9602;
113 bugfix on 0.2.4.4-alpha.
114 - Do not treat streams that fail with reason
115 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
116 since it could also indicate an ENETUNREACH connection error. Fixes
117 part of bug 10777; bugfix on 0.2.4.8-alpha.
119 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
120 - Do not allow OpenSSL engines to replace the PRNG, even when
121 HardwareAccel is set. The only default builtin PRNG engine uses
122 the Intel RDRAND instruction to replace the entire PRNG, and
123 ignores all attempts to seed it with more entropy. That's
124 cryptographically stupid: the right response to a new alleged
125 entropy source is never to discard all previously used entropy
126 sources. Fixes bug 10402; works around behavior introduced in
127 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
129 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
130 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
131 - Avoid launching spurious extra circuits when a stream is pending.
132 This fixes a bug where any circuit that _wasn't_ unusable for new
133 streams would be treated as if it were, causing extra circuits to
134 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
136 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
137 - No longer stop reading or writing on cpuworker connections when
138 our rate limiting buckets go empty. Now we should handle circuit
139 handshake requests more promptly. Resolves bug 9731.
140 - Stop trying to bootstrap all our directory information from
141 only our first guard. Discovered while fixing bug 9946; bugfix
144 o Minor features (bridges, pluggable transports):
145 - Add threshold cutoffs to the networkstatus document created by
146 the Bridge Authority. Fixes bug 1117.
147 - On Windows, spawn background processes using the CREATE_NO_WINDOW
148 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
149 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
150 Vidalia set this option for us.) Implements ticket 10297.
152 o Minor features (security):
153 - Always clear OpenSSL bignums before freeing them -- even bignums
154 that don't contain secrets. Resolves ticket 10793. Patch by
157 o Minor features (config options and command line):
158 - Add an --allow-missing-torrc commandline option that tells Tor to
159 run even if the configuration file specified by -f is not available.
160 Implements ticket 10060.
161 - Add support for the TPROXY transparent proxying facility on Linux.
162 See documentation for the new TransProxyType option for more
163 details. Implementation by "thomo". Closes ticket 10582.
165 o Minor features (controller):
166 - Add a new "HS_DESC" controller event that reports activities
167 related to hidden service descriptors. Resolves ticket 8510.
168 - New "DROPGUARDS" controller command to forget all current entry
169 guards. Not recommended for ordinary use, since replacing guards
170 too frequently makes several attacks easier. Resolves ticket 9934;
173 o Minor features (build):
174 - Assume that a user using ./configure --host wants to cross-compile,
175 and give an error if we cannot find a properly named
176 tool-chain. Add a --disable-tool-name-check option to proceed
177 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
178 - If we run ./configure and the compiler recognizes -fstack-protector
179 but the linker rejects it, warn the user about a potentially missing
180 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
182 o Minor features (testing):
183 - If Python is installed, "make check" now runs extra tests beyond
184 the unit test scripts.
185 - When bootstrapping a test network, sometimes very few relays get
186 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
187 specify a set of relays which should be voted Guard regardless of
188 their uptime or bandwidth. Addresses ticket 9206.
190 o Minor features (log messages):
191 - When ServerTransportPlugin is set on a bridge, Tor can write more
192 useful statistics about bridge use in its extrainfo descriptors,
193 but only if the Extended ORPort ("ExtORPort") is set too. Add a
194 log message to inform the user in this case. Resolves ticket 9651.
195 - When receiving a new controller connection, log the origin address.
196 Resolves ticket 9698; patch from "sigpipe".
197 - When logging OpenSSL engine status at startup, log the status of
198 more engines. Fixes ticket 10043; patch from Joshua Datko.
199 - Turn "circuit handshake stats since last time" log messages into a
200 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
202 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
203 - Improve the circuit queue out-of-memory handler. Previously, when
204 we ran low on memory, we'd close whichever circuits had the most
205 queued cells. Now, we close those that have the *oldest* queued
206 cells, on the theory that those are most responsible for us
207 running low on memory. Based on analysis from a forthcoming paper
208 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
209 - Generate bootstrapping status update events correctly when fetching
210 microdescriptors. Fixes bug 9927.
211 - Update to the October 2 2013 Maxmind GeoLite Country database.
213 o Minor bugfixes (clients):
214 - When closing a channel that has already been open, do not close
215 pending circuits that were waiting to connect to the same relay.
216 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
219 o Minor bugfixes (relays):
220 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
221 exit node as a NOROUTE error, not an INTERNAL error, since they
222 can apparently happen when trying to connect to the wrong sort
223 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
225 o Minor bugfixes (bridges):
226 - Fix a bug where the first connection works to a bridge that uses a
227 pluggable transport with client-side parameters, but we don't send
228 the client-side parameters on subsequent connections. (We don't
229 use any pluggable transports with client-side parameters yet,
230 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
231 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
233 o Minor bugfixes (node selection):
234 - If ExcludeNodes is set, consider non-excluded hidden service
235 directory servers before excluded ones. Do not consider excluded
236 hidden service directory servers at all if StrictNodes is
237 set. (Previously, we would sometimes decide to connect to those
238 servers, and then realize before we initiated a connection that
239 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
241 - If we set the ExitNodes option but it doesn't include any nodes
242 that have the Exit flag, we would choose not to bootstrap. Now we
243 bootstrap so long as ExitNodes includes nodes which can exit to
244 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
246 o Minor bugfixes (controller and command-line):
247 - If changing a config option via "setconf" fails in a recoverable
248 way, we used to nonetheless write our new control ports to the
249 file described by the "ControlPortWriteToFile" option. Now we only
250 write out that file if we successfully switch to the new config
251 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
252 - When a command-line option such as --version or --help that
253 ordinarily implies --hush appears on the command line along with
254 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
255 only if it appeared later on the command line. Fixes bug 9578;
256 bugfix on 0.2.5.1-alpha.
258 o Minor bugfixes (code correctness):
259 - Previously we used two temporary files when writing descriptors to
260 disk; now we only use one. Fixes bug 1376.
261 - Remove an erroneous (but impossible and thus harmless) pointer
262 comparison that would have allowed compilers to skip a bounds
263 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
264 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
265 - Fix an always-true assertion in pluggable transports code so it
266 actually checks what it was trying to check. Fixes bug 10046;
267 bugfix on 0.2.3.9-alpha. Found by "dcb".
269 o Minor bugfixes (protocol correctness):
270 - When receiving a VERSIONS cell with an odd number of bytes, close
271 the connection immediately since the cell is malformed. Fixes bug
272 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
275 o Minor bugfixes (build):
276 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
277 turned off (that is, without support for v2 link handshakes). Fixes
278 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
279 - Fix compilation warnings and startup issues when running with
280 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
282 - Fix compilation on Solaris 9, which didn't like us having an
283 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
285 o Minor bugfixes (testing):
286 - Fix a segmentation fault in our benchmark code when running with
287 Fedora's OpenSSL package, or any other OpenSSL that provides
288 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
290 o Minor bugfixes (log messages):
291 - Fix a bug where clients using bridges would report themselves
292 as 50% bootstrapped even without a live consensus document.
293 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
294 - Suppress a warning where, if there's only one directory authority
295 in the network, we would complain that votes and signatures cannot
296 be uploaded to other directory authorities. Fixes bug 10842;
297 bugfix on 0.2.2.26-beta.
298 - Report bootstrapping progress correctly when we're downloading
299 microdescriptors. We had updated our "do we have enough microdescs
300 to begin building circuits?" logic most recently in 0.2.4.10-alpha
301 (see bug 5956), but we left the bootstrap status event logic at
302 "how far through getting 1/4 of them are we?" Fixes bug 9958;
303 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
305 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
306 - Avoid a crash bug when starting with a corrupted microdescriptor
307 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
308 - If we fail to dump a previously cached microdescriptor to disk, avoid
309 freeing duplicate data later on. Fixes bug 10423; bugfix on
310 0.2.4.13-alpha. Spotted by "bobnomnom".
312 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
313 - Correctly log long IPv6 exit policies, instead of truncating them
314 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
315 - Our default TLS ecdhe groups were backwards: we meant to be using
316 P224 for relays (for performance win) and P256 for bridges (since
317 it is more common in the wild). Instead we had it backwards. After
318 reconsideration, we decided that the default should be P256 on all
319 hosts, since its security is probably better, and since P224 is
320 reportedly used quite little in the wild. Found by "skruffy" on
321 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
322 - Free directory authority certificate download statuses on exit
323 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
325 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
326 - If the guard we choose first doesn't answer, we would try the
327 second guard, but once we connected to the second guard we would
328 abandon it and retry the first one, slowing down bootstrapping.
329 The fix is to treat all our initially chosen guards as acceptable
330 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
331 - Fix an assertion failure that would occur when disabling the
332 ORPort setting on a running Tor process while accounting was
333 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
334 - When examining the list of network interfaces to find our address,
335 do not consider non-running or disabled network interfaces. Fixes
336 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
337 - Avoid an off-by-one error when checking buffer boundaries when
338 formatting the exit status of a pluggable transport helper.
339 This is probably not an exploitable bug, but better safe than
340 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
343 o Removed code and features:
344 - Clients now reject any directory authority certificates lacking
345 a dir-key-crosscert element. These have been included since
346 0.2.1.9-alpha, so there's no real reason for them to be optional
347 any longer. Completes proposal 157. Resolves ticket 10162.
348 - Remove all code that existed to support the v2 directory system,
349 since there are no longer any v2 directory authorities. Resolves
351 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
352 options, which were used for designating authorities as "Hidden
353 service authorities". There has been no use of hidden service
354 authorities since 0.2.2.1-alpha, when we stopped uploading or
355 downloading v0 hidden service descriptors. Fixes bug 10881; also
356 part of a fix for bug 10841.
358 o Code simplification and refactoring:
359 - Remove some old fallback code designed to keep Tor clients working
360 in a network with only two working relays. Elsewhere in the code we
361 have long since stopped supporting such networks, so there wasn't
362 much point in keeping it around. Addresses ticket 9926.
363 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
364 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
365 - Remove data structures which were introduced to implement the
366 CellStatistics option: they are now redundant with the addition
367 of a timestamp to the regular packed_cell_t data structure, which
368 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
371 o Documentation (man page) fixes:
372 - Update manpage to describe some of the files you can expect to
373 find in Tor's DataDirectory. Addresses ticket 9839.
374 - Document that all but one DirPort entry must have the NoAdvertise
375 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
377 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
378 - Clarify the usage and risks of setting the ContactInfo torrc line
379 for your relay or bridge. Resolves ticket 9854.
380 - Add anchors to the manpage so we can link to the html version of
381 the documentation for specific options. Resolves ticket 9866.
382 - Replace remaining references to DirServer in man page and
383 log entries. Resolves ticket 10124.
386 - Make the "tor-gencert" tool used by directory authority operators
387 create 2048-bit signing keys by default (rather than 1024-bit, since
388 1024-bit is uncomfortably small these days). Addresses ticket 10324.
391 Changes in version 0.2.4.20 - 2013-12-22
392 Tor 0.2.4.20 fixes potentially poor random number generation for users
393 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
394 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
395 and 4) have no state file in their DataDirectory (as would happen on
396 first start). Users who generated relay or hidden service identity
397 keys in such a situation should discard them and generate new ones.
399 This release also fixes a logic error that caused Tor clients to build
400 many more preemptive circuits than they actually need.
403 - Do not allow OpenSSL engines to replace the PRNG, even when
404 HardwareAccel is set. The only default builtin PRNG engine uses
405 the Intel RDRAND instruction to replace the entire PRNG, and
406 ignores all attempts to seed it with more entropy. That's
407 cryptographically stupid: the right response to a new alleged
408 entropy source is never to discard all previously used entropy
409 sources. Fixes bug 10402; works around behavior introduced in
410 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
412 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
413 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
414 - Avoid launching spurious extra circuits when a stream is pending.
415 This fixes a bug where any circuit that _wasn't_ unusable for new
416 streams would be treated as if it were, causing extra circuits to
417 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
420 - Avoid a crash bug when starting with a corrupted microdescriptor
421 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
422 - If we fail to dump a previously cached microdescriptor to disk, avoid
423 freeing duplicate data later on. Fixes bug 10423; bugfix on
424 0.2.4.13-alpha. Spotted by "bobnomnom".
427 Changes in version 0.2.4.19 - 2013-12-11
428 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
429 (1986-2013). Aaron worked on diverse projects including helping to guide
430 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
431 transparency to the U.S government's PACER documents, and contributing
432 design and development for Tor and Tor2Web. Aaron was one of the latest
433 martyrs in our collective fight for civil liberties and human rights,
434 and his death is all the more painful because he was one of us.
436 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
437 a new circuit handshake and link encryption that use ECC to provide
438 better security and efficiency; makes relays better manage circuit
439 creation requests; uses "directory guards" to reduce client enumeration
440 risks; makes bridges collect and report statistics about the pluggable
441 transports they support; cleans up and improves our geoip database;
442 gets much closer to IPv6 support for clients, bridges, and relays; makes
443 directory authorities use measured bandwidths rather than advertised
444 ones when computing flags and thresholds; disables client-side DNS
445 caching to reduce tracking risks; and fixes a big bug in bridge
446 reachability testing. This release introduces two new design
447 abstractions in the code: a new "channel" abstraction between circuits
448 and or_connections to allow for implementing alternate relay-to-relay
449 transports, and a new "circuitmux" abstraction storing the queue of
450 circuits for a channel. The release also includes many stability,
451 security, and privacy fixes.
454 Changes in version 0.2.4.18-rc - 2013-11-16
455 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
456 series. It takes a variety of fixes from the 0.2.5.x branch to improve
457 stability, performance, and better handling of edge cases.
460 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
461 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
462 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
463 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
464 them to solve bug 6033.)
467 - No longer stop reading or writing on cpuworker connections when
468 our rate limiting buckets go empty. Now we should handle circuit
469 handshake requests more promptly. Resolves bug 9731.
470 - If we are unable to save a microdescriptor to the journal, do not
471 drop it from memory and then reattempt downloading it. Fixes bug
472 9645; bugfix on 0.2.2.6-alpha.
473 - Stop trying to bootstrap all our directory information from
474 only our first guard. Discovered while fixing bug 9946; bugfix
476 - The new channel code sometimes lost track of in-progress circuits,
477 causing long-running clients to stop building new circuits. The
478 fix is to always call circuit_n_chan_done(chan, 0) from
479 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
481 o Minor bugfixes (on 0.2.4.x):
482 - Correctly log long IPv6 exit policies, instead of truncating them
483 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
484 - Our default TLS ecdhe groups were backwards: we meant to be using
485 P224 for relays (for performance win) and P256 for bridges (since
486 it is more common in the wild). Instead we had it backwards. After
487 reconsideration, we decided that the default should be P256 on all
488 hosts, since its security is probably better, and since P224 is
489 reportedly used quite little in the wild. Found by "skruffy" on
490 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
491 - Free directory authority certificate download statuses on exit
492 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
494 o Minor bugfixes (on 0.2.3.x and earlier):
495 - If the guard we choose first doesn't answer, we would try the
496 second guard, but once we connected to the second guard we would
497 abandon it and retry the first one, slowing down bootstrapping.
498 The fix is to treat all our initially chosen guards as acceptable
499 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
500 - Fix an assertion failure that would occur when disabling the
501 ORPort setting on a running Tor process while accounting was
502 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
503 - When examining the list of network interfaces to find our address,
504 do not consider non-running or disabled network interfaces. Fixes
505 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
506 - Avoid an off-by-one error when checking buffer boundaries when
507 formatting the exit status of a pluggable transport helper.
508 This is probably not an exploitable bug, but better safe than
509 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
512 o Minor features (protecting client timestamps):
513 - Clients no longer send timestamps in their NETINFO cells. These were
514 not used for anything, and they provided one small way for clients
515 to be distinguished from each other as they moved from network to
516 network or behind NAT. Implements part of proposal 222.
517 - Clients now round timestamps in INTRODUCE cells down to the nearest
518 10 minutes. If a new Support022HiddenServices option is set to 0, or
519 if it's set to "auto" and the feature is disabled in the consensus,
520 the timestamp is sent as 0 instead. Implements part of proposal 222.
521 - Stop sending timestamps in AUTHENTICATE cells. This is not such
522 a big deal from a security point of view, but it achieves no actual
523 good purpose, and isn't needed. Implements part of proposal 222.
524 - Reduce down accuracy of timestamps in hidden service descriptors.
525 Implements part of proposal 222.
527 o Minor features (other):
528 - Improve the circuit queue out-of-memory handler. Previously, when
529 we ran low on memory, we'd close whichever circuits had the most
530 queued cells. Now, we close those that have the *oldest* queued
531 cells, on the theory that those are most responsible for us
532 running low on memory. Based on analysis from a forthcoming paper
533 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
534 - Generate bootstrapping status update events correctly when fetching
535 microdescriptors. Fixes bug 9927.
536 - Update to the October 2 2013 Maxmind GeoLite Country database.
538 o Documentation fixes:
539 - Clarify the usage and risks of setting the ContactInfo torrc line
540 for your relay or bridge. Resolves ticket 9854.
541 - Add anchors to the manpage so we can link to the html version of
542 the documentation for specific options. Resolves ticket 9866.
543 - Replace remaining references to DirServer in man page and
544 log entries. Resolves ticket 10124.
547 Changes in version 0.2.5.1-alpha - 2013-10-02
548 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
549 on Linux, allows bridges that offer pluggable transports to report usage
550 statistics, fixes many issues to make testing easier, and provides
551 a pile of minor features and bugfixes that have been waiting for a
552 release of the new branch.
554 This is the first alpha release in a new series, so expect there to
555 be bugs. Users who would rather test out a more stable branch should
556 stay with 0.2.4.x for now.
558 o Major features (security):
559 - Use the seccomp2 syscall filtering facility on Linux to limit
560 which system calls Tor can invoke. This is an experimental,
561 Linux-only feature to provide defense-in-depth against unknown
562 attacks. To try turning it on, set "Sandbox 1" in your torrc
563 file. Please be ready to report bugs. We hope to add support
564 for better sandboxing in the future, including more fine-grained
565 filters, better division of responsibility, and support for more
566 platforms. This work has been done by Cristian-Matei Toader for
567 Google Summer of Code.
568 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
569 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
570 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
571 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
572 them to solve bug 6033.)
574 o Major features (other):
575 - Add support for passing arguments to managed pluggable transport
576 proxies. Implements ticket 3594.
577 - Bridges now track GeoIP information and the number of their users
578 even when pluggable transports are in use, and report usage
579 statistics in their extra-info descriptors. Resolves tickets 4773
581 - Make testing Tor networks bootstrap better: lower directory fetch
582 retry schedules and maximum interval without directory requests,
583 and raise maximum download tries. Implements ticket 6752.
584 - Add make target 'test-network' to run tests on a Chutney network.
585 Implements ticket 8530.
586 - The ntor handshake is now on-by-default, no matter what the
587 directory authorities recommend. Implements ticket 8561.
590 - Instead of writing destroy cells directly to outgoing connection
591 buffers, queue them and intersperse them with other outgoing cells.
592 This can prevent a set of resource starvation conditions where too
593 many pending destroy cells prevent data cells from actually getting
594 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
595 bugfix on 0.2.0.1-alpha.
596 - If we are unable to save a microdescriptor to the journal, do not
597 drop it from memory and then reattempt downloading it. Fixes bug
598 9645; bugfix on 0.2.2.6-alpha.
599 - The new channel code sometimes lost track of in-progress circuits,
600 causing long-running clients to stop building new circuits. The
601 fix is to always call circuit_n_chan_done(chan, 0) from
602 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
605 - Tor now builds each source file in two modes: a mode that avoids
606 exposing identifiers needlessly, and another mode that exposes
607 more identifiers for testing. This lets the compiler do better at
608 optimizing the production code, while enabling us to take more
609 radical measures to let the unit tests test things.
610 - The production builds no longer include functions used only in
611 the unit tests; all functions exposed from a module only for
612 unit-testing are now static in production builds.
613 - Add an --enable-coverage configuration option to make the unit
614 tests (and a new src/or/tor-cov target) to build with gcov test
618 - We now have rudimentary function mocking support that our unit
619 tests can use to test functions in isolation. Function mocking
620 lets the tests temporarily replace a function's dependencies with
621 stub functions, so that the tests can check the function without
622 invoking the other functions it calls.
623 - Add more unit tests for the <circid,channel>->circuit map, and
624 the destroy-cell-tracking code to fix bug 7912.
625 - Unit tests for failing cases of the TAP onion handshake.
626 - More unit tests for address-manipulation functions.
628 o Minor features (protecting client timestamps):
629 - Clients no longer send timestamps in their NETINFO cells. These were
630 not used for anything, and they provided one small way for clients
631 to be distinguished from each other as they moved from network to
632 network or behind NAT. Implements part of proposal 222.
633 - Clients now round timestamps in INTRODUCE cells down to the nearest
634 10 minutes. If a new Support022HiddenServices option is set to 0, or
635 if it's set to "auto" and the feature is disabled in the consensus,
636 the timestamp is sent as 0 instead. Implements part of proposal 222.
637 - Stop sending timestamps in AUTHENTICATE cells. This is not such
638 a big deal from a security point of view, but it achieves no actual
639 good purpose, and isn't needed. Implements part of proposal 222.
640 - Reduce down accuracy of timestamps in hidden service descriptors.
641 Implements part of proposal 222.
643 o Minor features (config options):
644 - Config (torrc) lines now handle fingerprints which are missing
645 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
646 - Support a --dump-config option to print some or all of the
647 configured options. Mainly useful for debugging the command-line
648 option parsing code. Helps resolve ticket 4647.
649 - Raise awareness of safer logging: notify user of potentially
650 unsafe config options, like logging more verbosely than severity
651 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
652 - Add a new configuration option TestingV3AuthVotingStartOffset
653 that bootstraps a network faster by changing the timing for
654 consensus votes. Addresses ticket 8532.
655 - Add a new torrc option "ServerTransportOptions" that allows
656 bridge operators to pass configuration parameters to their
657 pluggable transports. Resolves ticket 8929.
658 - The config (torrc) file now accepts bandwidth and space limits in
659 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
660 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
663 o Minor features (build):
664 - Add support for `--library-versions` flag. Implements ticket 6384.
665 - Return the "unexpected sendme" warnings to a warn severity, but make
666 them rate limited, to help diagnose ticket 8093.
667 - Detect a missing asciidoc, and warn the user about it, during
668 configure rather than at build time. Fixes issue 6506. Patch from
671 o Minor features (other):
672 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
673 sockets in a single system call. Implements ticket 5129.
674 - Log current accounting state (bytes sent and received + remaining
675 time for the current accounting period) in the relay's heartbeat
676 message. Implements ticket 5526; patch from Peter Retzlaff.
677 - Implement the TRANSPORT_LAUNCHED control port event that
678 notifies controllers about new launched pluggable
679 transports. Resolves ticket 5609.
680 - If we're using the pure-C 32-bit curve25519_donna implementation
681 of curve25519, build it with the -fomit-frame-pointer option to
682 make it go faster on register-starved hosts. This improves our
683 handshake performance by about 6% on i386 hosts without nacl.
685 - Update to the September 4 2013 Maxmind GeoLite Country database.
688 - Set the listen() backlog limit to the largest actually supported
689 on the system, not to the value in a header file. Fixes bug 9716;
690 bugfix on every released Tor.
691 - No longer accept malformed http headers when parsing urls from
692 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
694 - In munge_extrainfo_into_routerinfo(), check the return value of
695 memchr(). This would have been a serious issue if we ever passed
696 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
698 - On the chance that somebody manages to build Tor on a
699 platform where time_t is unsigned, correct the way that
700 microdesc_add_to_cache() handles negative time arguments.
701 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
702 - Reject relative control socket paths and emit a warning. Previously,
703 single-component control socket paths would be rejected, but Tor
704 would not log why it could not validate the config. Fixes bug 9258;
705 bugfix on 0.2.3.16-alpha.
707 o Minor bugfixes (command line):
708 - Use a single command-line parser for parsing torrc options on the
709 command line and for finding special command-line options to avoid
710 inconsistent behavior for torrc option arguments that have the same
711 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
713 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
714 9573; bugfix on 0.0.9pre5.
716 o Minor fixes (build, auxiliary programs):
717 - Stop preprocessing the "torify" script with autoconf, since
718 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
720 - The tor-fw-helper program now follows the standard convention and
721 exits with status code "0" on success. Fixes bug 9030; bugfix on
722 0.2.3.1-alpha. Patch by Arlo Breault.
723 - Corrected ./configure advice for what openssl dev package you should
724 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
726 o Minor code improvements:
727 - Remove constants and tests for PKCS1 padding; it's insecure and
728 shouldn't be used for anything new. Fixes bug 8792; patch
730 - Remove instances of strcpy() from the unit tests. They weren't
731 hurting anything, since they were only in the unit tests, but it's
732 embarassing to have strcpy() in the code at all, and some analysis
733 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
734 0.2.3.8-alpha. Patch from Arlo Breault.
737 - Remove migration code from when we renamed the "cached-routers"
738 file to "cached-descriptors" back in 0.2.0.8-alpha. This
739 incidentally resolves ticket 6502 by cleaning up the related code
740 a bit. Patch from Akshay Hebbar.
742 o Code simplification and refactoring:
743 - Extract the common duplicated code for creating a subdirectory
744 of the data directory and writing to a file in it. Fixes ticket
745 4282; patch from Peter Retzlaff.
746 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
747 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
748 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
749 - Add a set of accessor functions for the circuit timeout data
750 structure. Fixes ticket 6153; patch from "piet".
751 - Clean up exit paths from connection_listener_new(). Closes ticket
752 8789. Patch from Arlo Breault.
753 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
754 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
755 - Use a doubly-linked list to implement the global circuit list.
756 Resolves ticket 9108. Patch from Marek Majkowski.
757 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
760 Changes in version 0.2.4.17-rc - 2013-09-05
761 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
762 series. It adds an emergency step to help us tolerate the massive
763 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
764 circuit-level handshakes now effectively jump the queue compared to
765 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
766 big bug hindering bridge reachability tests.
769 - Relays now process the new "NTor" circuit-level handshake requests
770 with higher priority than the old "TAP" circuit-level handshake
771 requests. We still process some TAP requests to not totally starve
772 0.2.3 clients when NTor becomes popular. A new consensus parameter
773 "NumNTorsPerTAP" lets us tune the balance later if we need to.
774 Implements ticket 9574.
777 - If the circuit build timeout logic is disabled (via the consensus,
778 or because we are an authority), then don't build testing circuits.
779 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
780 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
781 previously they did not, which prevented them from receiving
782 successful connections from relays for self-test or bandwidth
783 testing. Also, when a relay is extending a circuit to a bridge,
784 it needs to send a NETINFO cell, even when the bridge hasn't sent
785 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
786 - If the time to download the next old-style networkstatus is in
787 the future, do not decline to consider whether to download the
788 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
792 - Avoid double-closing the listener socket in our socketpair()
793 replacement (used on Windows) in the case where the addresses on
794 our opened sockets don't match what we expected. Fixes bug 9400;
795 bugfix on 0.0.2pre7. Found by Coverity.
797 o Minor fixes (config options):
798 - Avoid overflows when the user sets MaxCircuitDirtiness to a
799 ridiculously high value, by imposing a (ridiculously high) 30-day
800 maximum on MaxCircuitDirtiness.
801 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
802 message is logged at notice, not at info.
803 - Warn and fail if a server is configured not to advertise any
804 ORPorts at all. (We need *something* to put in our descriptor,
805 or we just won't work.)
808 - Track how many "TAP" and "NTor" circuit handshake requests we get,
809 and how many we complete, and log it every hour to help relay
810 operators follow trends in network load. Addresses ticket 9658.
811 - Update to the August 7 2013 Maxmind GeoLite Country database.
814 Changes in version 0.2.4.16-rc - 2013-08-10
815 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
816 series. It fixes several crash bugs in the 0.2.4 branch.
819 - Fix a bug in the voting algorithm that could yield incorrect results
820 when a non-naming authority declared too many flags. Fixes bug 9200;
821 bugfix on 0.2.0.3-alpha.
822 - Fix an uninitialized read that could in some cases lead to a remote
823 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
824 Anybody running a hidden service on the experimental 0.2.4.x
825 branch should upgrade. (This is, so far as we know, unrelated to
827 - Avoid an assertion failure when processing DNS replies without the
828 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
829 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
830 0.2.4.15-rc. Found by stem integration tests.
833 - Fix an invalid memory read that occured when a pluggable
834 transport proxy failed its configuration protocol.
835 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
836 - When evaluating whether to use a connection that we haven't
837 decided is canonical using a recent link protocol version,
838 decide that it's canonical only if it used address _does_
839 match the desired address. Fixes bug 9309; bugfix on
840 0.2.4.4-alpha. Reported by skruffy.
841 - Make the default behavior of NumDirectoryGuards be to track
842 NumEntryGuards. Now a user who changes only NumEntryGuards will get
843 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
844 - Fix a spurious compilation warning with some older versions of
845 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
848 - Update to the July 3 2013 Maxmind GeoLite Country database.
851 Changes in version 0.2.4.15-rc - 2013-07-01
852 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
853 series. It fixes a few smaller bugs, but generally appears stable.
854 Please test it and let us know whether it is!
857 - When receiving a new configuration file via the control port's
858 LOADCONF command, do not treat the defaults file as absent.
859 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
862 - Issue a warning when running with the bufferevents backend enabled.
863 It's still not stable, and people should know that they're likely
864 to hit unexpected problems. Closes ticket 9147.
867 Changes in version 0.2.4.14-alpha - 2013-06-18
868 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
869 present in 0.2.4.13-alpha.
872 - When we have too much memory queued in circuits (according to a new
873 MaxMemInCellQueues option), close the circuits consuming the most
874 memory. This prevents us from running out of memory as a relay if
875 circuits fill up faster than they can be drained. Fixes bug 9063;
876 bugfix on the 54th commit of Tor. This bug is a further fix beyond
877 bug 6252, whose fix was merged into 0.2.3.21-rc.
879 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
880 where we tried to solve this issue simply by imposing an upper limit
881 on the number of queued cells for a single circuit. That approach
882 proved to be problematic, since there are ways to provoke clients to
883 send a number of cells in excess of any such reasonable limit. Fixes
884 bug 9072; bugfix on 0.2.4.13-alpha.
886 - Limit hidden service descriptors to at most ten introduction
887 points, to slow one kind of guard enumeration. Fixes bug 9002;
888 bugfix on 0.1.1.11-alpha.
891 Changes in version 0.2.4.13-alpha - 2013-06-14
892 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
893 vulnerabilities, makes socks5 username/password circuit isolation
894 actually actually work (this time for sure!), and cleans up a bunch
895 of other issues in preparation for a release candidate.
897 o Major bugfixes (robustness):
898 - Close any circuit that has too many cells queued on it. Fixes
899 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
900 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
901 - Prevent the get_freelists() function from running off the end of
902 the list of freelists if it somehow gets an unrecognized
903 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
905 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
906 when an exit connection with optimistic data succeeds immediately
907 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
909 - Fix a directory authority crash bug when building a consensus
910 using an older consensus as its basis. Fixes bug 8833. Bugfix
914 - Avoid a memory leak where we would leak a consensus body when we
915 find that a consensus which we couldn't previously verify due to
916 missing certificates is now verifiable. Fixes bug 8719; bugfix
918 - We used to always request authority certificates by identity digest,
919 meaning we'd get the newest one even when we wanted one with a
920 different signing key. Then we would complain about being given
921 a certificate we already had, and never get the one we really
922 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
923 resource to request the one we want. Fixes bug 5595; bugfix on
925 - Follow the socks5 protocol when offering username/password
926 authentication. The fix for bug 8117 exposed this bug, and it
927 turns out real-world applications like Pidgin do care. Bugfix on
928 0.2.3.2-alpha; fixes bug 8879.
929 - Prevent failures on Windows Vista and later when rebuilding the
930 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
931 bugfix on 0.2.4.12-alpha.
934 - Fix an impossible buffer overrun in the AES unit tests. Fixes
935 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
936 - If for some reason we fail to write a microdescriptor while
937 rebuilding the cache, do not let the annotations from that
938 microdescriptor linger in the cache file, and do not let the
939 microdescriptor stay recorded as present in its old location.
940 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
941 - Fix a memory leak that would occur whenever a configuration
942 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
943 - Paste the description for PathBias parameters from the man
944 page into or.h, so the code documents them too. Fixes bug 7982;
945 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
946 - Relays now treat a changed IPv6 ORPort as sufficient reason to
947 publish an updated descriptor. Fixes bug 6026; bugfix on
949 - When launching a resolve request on behalf of an AF_UNIX control
950 socket, omit the address field of the new entry connection, used in
951 subsequent controller events, rather than letting tor_dup_addr()
952 set it to "<unknown address type>". Fixes bug 8639; bugfix on
955 o Minor bugfixes (log messages):
956 - Fix a scaling issue in the path bias accounting code that
957 resulted in "Bug:" log messages from either
958 pathbias_scale_close_rates() or pathbias_count_build_success().
959 This represents a bugfix on a previous bugfix: the original fix
960 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
962 - Give a less useless error message when the user asks for an IPv4
963 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
967 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
968 to tolerate bug 8093 for now.
969 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
970 in directory authority votes to describe whether they have enough
971 measured bandwidths to ignore advertised (relay descriptor)
972 bandwidth claims. Resolves ticket 8711.
973 - Update to the June 5 2013 Maxmind GeoLite Country database.
975 o Removed documentation:
976 - Remove some of the older contents of doc/ as obsolete; move others
977 to torspec.git. Fixes bug 8965.
979 o Code simplification and refactoring:
980 - Avoid using character buffers when constructing most directory
981 objects: this approach was unwieldy and error-prone. Instead,
982 build smartlists of strings, and concatenate them when done.
985 Changes in version 0.2.4.12-alpha - 2013-04-18
986 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
987 process for lengthening the guard rotation period, makes directory
988 authority opinions in the consensus a bit less gameable, makes socks5
989 username/password circuit isolation actually work, and fixes a wide
990 variety of other issues.
993 - Raise the default time that a client keeps an entry guard from
994 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
995 2012 paper. (We would make it even longer, but we need better client
996 load balancing first.) Also, make the guard lifetime controllable
997 via a new GuardLifetime torrc option and a GuardLifetime consensus
998 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
999 - Directory authorities now prefer using measured bandwidths to
1000 advertised ones when computing flags and thresholds. Resolves
1002 - Directory authorities that have more than a threshold number
1003 of relays with measured bandwidths now treat relays with unmeasured
1004 bandwidths as having bandwidth 0. Resolves ticket 8435.
1006 o Major bugfixes (assert / resource use):
1007 - Avoid a bug where our response to TLS renegotiation under certain
1008 network conditions could lead to a busy-loop, with 100% CPU
1009 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
1010 - Avoid an assertion when we discover that we'd like to write a cell
1011 onto a closing connection: just discard the cell. Fixes another
1012 case of bug 7350; bugfix on 0.2.4.4-alpha.
1014 o Major bugfixes (client-side privacy):
1015 - When we mark a circuit as unusable for new circuits, have it
1016 continue to be unusable for new circuits even if MaxCircuitDirtiness
1017 is increased too much at the wrong time, or the system clock jumps
1018 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
1019 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
1020 which have resolved to internal addresses") is set, apply that
1021 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
1022 - When an exit relay rejects a stream with reason "exit policy", but
1023 we only know an exit policy summary (e.g. from the microdesc
1024 consensus) for it, do not mark the relay as useless for all exiting.
1025 Instead, mark just the circuit as unsuitable for that particular
1026 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
1027 - Allow applications to get proper stream isolation with
1028 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
1029 username/password authentication also offer "no authentication". Tor
1030 had previously preferred "no authentication", so the applications
1031 never actually sent Tor their auth details. Now Tor selects
1032 username/password authentication if it's offered. You can disable
1033 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
1034 bug 8117; bugfix on 0.2.3.3-alpha.
1036 o Major bugfixes (other):
1037 - When unable to find any working directory nodes to use as a
1038 directory guard, give up rather than adding the same non-working
1039 nodes to the directory guard list over and over. Fixes bug 8231;
1040 bugfix on 0.2.4.8-alpha.
1043 - Reject as invalid most directory objects containing a NUL.
1044 Belt-and-suspender fix for bug 8037.
1045 - In our testsuite, create temporary directories with a bit more
1046 entropy in their name to make name collisions less likely. Fixes
1048 - Add CACHED keyword to ADDRMAP events in the control protocol
1049 to indicate whether a DNS result will be cached or not. Resolves
1051 - Update to the April 3 2013 Maxmind GeoLite Country database.
1053 o Minor features (build):
1054 - Detect and reject attempts to build Tor with threading support
1055 when OpenSSL has been compiled without threading support.
1057 - Clarify that when autoconf is checking for nacl, it is checking
1058 specifically for nacl with a fast curve25519 implementation.
1060 - Warn if building on a platform with an unsigned time_t: there
1061 are too many places where Tor currently assumes that time_t can
1062 hold negative values. We'd like to fix them all, but probably
1065 o Minor bugfixes (build):
1066 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
1067 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
1068 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
1069 - Add the old src/or/micro-revision.i filename to CLEANFILES.
1070 On the off chance that somebody has one, it will go away as soon
1071 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
1072 - Build Tor correctly on 32-bit platforms where the compiler can build
1073 but not run code using the "uint128_t" construction. Fixes bug 8587;
1074 bugfix on 0.2.4.8-alpha.
1075 - Fix compilation warning with some versions of clang that would
1076 prefer the -Wswitch-enum compiler flag to warn about switch
1077 statements with missing enum values, even if those switch
1078 statements have a "default:" statement. Fixes bug 8598; bugfix
1081 o Minor bugfixes (protocol):
1082 - Fix the handling of a TRUNCATE cell when it arrives while the
1083 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
1084 - Fix a misframing issue when reading the version numbers in a
1085 VERSIONS cell. Previously we would recognize [00 01 00 02] as
1086 'version 1, version 2, and version 0x100', when it should have
1087 only included versions 1 and 2. Fixes bug 8059; bugfix on
1088 0.2.0.10-alpha. Reported pseudonymously.
1089 - Make the format and order of STREAM events for DNS lookups
1090 consistent among the various ways to launch DNS lookups. Fixes
1091 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
1092 - Correct our check for which versions of Tor support the EXTEND2
1093 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
1094 later, when support was really added in version 0.2.4.8-alpha.
1095 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
1097 o Minor bugfixes (other):
1098 - Correctly store microdescriptors and extrainfo descriptors with
1099 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
1100 Bug reported by "cypherpunks".
1101 - Increase the width of the field used to remember a connection's
1102 link protocol version to two bytes. Harmless for now, since the
1103 only currently recognized versions are one byte long. Reported
1104 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
1105 - If the state file's path bias counts are invalid (presumably from a
1106 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
1107 additional checks and log messages to the scaling of Path Bias
1108 counts, in case there still are remaining issues with scaling.
1109 Should help resolve bug 8235.
1110 - Eliminate several instances where we use "Nickname=ID" to refer to
1111 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
1112 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
1113 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
1115 o Minor bugfixes (syscalls):
1116 - Always check the return values of functions fcntl() and
1117 setsockopt(). We don't believe these are ever actually failing in
1118 practice, but better safe than sorry. Also, checking these return
1119 values should please analysis tools like Coverity. Patch from
1120 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
1121 - Use direct writes rather than stdio when building microdescriptor
1122 caches, in an attempt to mitigate bug 8031, or at least make it
1125 o Minor bugfixes (config):
1126 - When rejecting a configuration because we were unable to parse a
1127 quoted string, log an actual error message. Fixes bug 7950; bugfix
1129 - Behave correctly when the user disables LearnCircuitBuildTimeout
1130 but doesn't tell us what they would like the timeout to be. Fixes
1131 bug 6304; bugfix on 0.2.2.14-alpha.
1132 - When autodetecting the number of CPUs, use the number of available
1133 CPUs in preference to the number of configured CPUs. Inform the
1134 user if this reduces the number of available CPUs. Fixes bug 8002;
1135 bugfix on 0.2.3.1-alpha.
1136 - Make it an error when you set EntryNodes but disable UseGuardNodes,
1137 since it will (surprisingly to some users) ignore EntryNodes. Fixes
1138 bug 8180; bugfix on 0.2.3.11-alpha.
1139 - Allow TestingTorNetworks to override the 4096-byte minimum for
1140 the Fast threshold. Otherwise they can't bootstrap until they've
1141 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
1142 - Fix some logic errors when the user manually overrides the
1143 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
1146 o Minor bugfixes (log messages to help diagnose bugs):
1147 - If we fail to free a microdescriptor because of bug 7164, log
1148 the filename and line number from which we tried to free it.
1149 - Add another diagnostic to the heartbeat message: track and log
1150 overhead that TLS is adding to the data we write. If this is
1151 high, we are sending too little data to SSL_write at a time.
1152 Diagnostic for bug 7707.
1153 - Add more detail to a log message about relaxed timeouts, to help
1155 - Warn more aggressively when flushing microdescriptors to a
1156 microdescriptor cache fails, in an attempt to mitigate bug 8031,
1157 or at least make it more diagnosable.
1158 - Improve debugging output to help track down bug 8185 ("Bug:
1159 outgoing relay cell has n_chan==NULL. Dropping.")
1160 - Log the purpose of a path-bias testing circuit correctly.
1161 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
1163 o Minor bugfixes (0.2.4.x log messages that were too noisy):
1164 - Don't attempt to relax the timeout of already opened 1-hop circuits.
1165 They might never timeout. This should eliminate some/all cases of
1166 the relaxed timeout log message.
1167 - Use circuit creation time for network liveness evaluation. This
1168 should eliminate warning log messages about liveness caused
1169 by changes in timeout evaluation. Fixes bug 6572; bugfix on
1171 - Reduce a path bias length check from notice to info. The message
1172 is triggered when creating controller circuits. Fixes bug 8196;
1173 bugfix on 0.2.4.8-alpha.
1174 - Fix a path state issue that triggered a notice during relay startup.
1175 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
1176 - Reduce occurrences of warns about circuit purpose in
1177 connection_ap_expire_building(). Fixes bug 8477; bugfix on
1180 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
1181 - If we encounter a write failure on a SOCKS connection before we
1182 finish our SOCKS handshake, don't warn that we closed the
1183 connection before we could send a SOCKS reply. Fixes bug 8427;
1184 bugfix on 0.1.0.1-rc.
1185 - Correctly recognize that [::1] is a loopback address. Fixes
1186 bug 8377; bugfix on 0.2.1.3-alpha.
1187 - Fix a directory authority warn caused when we have a large amount
1188 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
1189 - Don't log inappropriate heartbeat messages when hibernating: a
1190 hibernating node is _expected_ to drop out of the consensus,
1191 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
1192 bugfix on 0.2.3.1-alpha.
1193 - Don't complain about bootstrapping problems while hibernating.
1194 These complaints reflect a general code problem, but not one
1195 with any problematic effects (no connections are actually
1196 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
1198 o Documentation fixes:
1199 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
1200 names match. Fixes bug 7768.
1201 - Make the torify manpage no longer refer to tsocks; torify hasn't
1202 supported tsocks since 0.2.3.14-alpha.
1203 - Make the tor manpage no longer reference tsocks.
1204 - Fix the GeoIPExcludeUnknown documentation to refer to
1205 ExcludeExitNodes rather than the currently nonexistent
1206 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
1209 - The tor-tsocks.conf is no longer distributed or installed. We
1210 recommend that tsocks users use torsocks instead. Resolves
1214 Changes in version 0.2.4.11-alpha - 2013-03-11
1215 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
1216 more robust, makes hidden service authentication work again, and
1217 resolves a DPI fingerprint for Tor's SSL transport.
1219 o Major features (directory authorities):
1220 - Directory authorities now support a new consensus method (17)
1221 where they cap the published bandwidth of servers for which
1222 insufficient bandwidth measurements exist. Fixes part of bug 2286.
1223 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
1224 serve any v2 directory information. Now we can test disabling the
1225 old deprecated v2 directory format, and see whether doing so has
1226 any effect on network load. Begins to fix bug 6783.
1227 - Directory authorities now include inside each vote a statement of
1228 the performance thresholds they used when assigning flags.
1229 Implements ticket 8151.
1231 o Major bugfixes (directory authorities):
1232 - Stop marking every relay as having been down for one hour every
1233 time we restart a directory authority. These artificial downtimes
1234 were messing with our Stable and Guard flag calculations. Fixes
1235 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
1237 o Major bugfixes (hidden services):
1238 - Allow hidden service authentication to succeed again. When we
1239 refactored the hidden service introduction code back
1240 in 0.2.4.1-alpha, we didn't update the code that checks
1241 whether authentication information is present, causing all
1242 authentication checks to return "false". Fix for bug 8207; bugfix
1243 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
1245 o Minor features (relays, bridges):
1246 - Make bridge relays check once a minute for whether their IP
1247 address has changed, rather than only every 15 minutes. Resolves
1249 - Refactor resolve_my_address() so it returns the method by which we
1250 decided our public IP address (explicitly configured, resolved from
1251 explicit hostname, guessed from interfaces, learned by gethostname).
1252 Now we can provide more helpful log messages when a relay guesses
1253 its IP address incorrectly (e.g. due to unexpected lines in
1254 /etc/hosts). Resolves ticket 2267.
1255 - Teach bridge-using clients to avoid 0.2.2 bridges when making
1256 microdescriptor-related dir requests, and only fall back to normal
1257 descriptors if none of their bridges can handle microdescriptors
1258 (as opposed to the fix in ticket 4013, which caused them to fall
1259 back to normal descriptors if *any* of their bridges preferred
1260 them). Resolves ticket 4994.
1261 - Randomize the lifetime of our SSL link certificate, so censors can't
1262 use the static value for filtering Tor flows. Resolves ticket 8443;
1263 related to ticket 4014 which was included in 0.2.2.33.
1265 o Minor features (portability):
1266 - Tweak the curve25519-donna*.c implementations to tolerate systems
1267 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
1268 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
1269 the signs of types during autoconf. This is better than our old
1270 approach, which didn't work when cross-compiling.
1271 - Detect the sign of enum values, rather than assuming that MSC is the
1272 only compiler where enum types are all signed. Fixes bug 7727;
1273 bugfix on 0.2.4.10-alpha.
1275 o Minor features (other):
1276 - Say "KBytes" rather than "KB" in the man page (for various values
1277 of K), to further reduce confusion about whether Tor counts in
1278 units of memory or fractions of units of memory. Resolves ticket 7054.
1279 - Clear the high bit on curve25519 public keys before passing them to
1280 our backend, in case we ever wind up using a backend that doesn't do
1281 so itself. If we used such a backend, and *didn't* clear the high bit,
1282 we could wind up in a situation where users with such backends would
1283 be distinguishable from users without. Fixes bug 8121; bugfix on
1285 - Update to the March 6 2013 Maxmind GeoLite Country database.
1287 o Minor bugfixes (clients):
1288 - When we receive a RELAY_END cell with the reason DONE, or with no
1289 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
1290 status as "connection refused". Previously we reported these cases
1291 as success but then immediately closed the connection. Fixes bug
1292 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
1293 - Downgrade an assertion in connection_ap_expire_beginning to an
1294 LD_BUG message. The fix for bug 8024 should prevent this message
1295 from displaying, but just in case, a warn that we can diagnose
1296 is better than more assert crashes. Fixes bug 8065; bugfix on
1298 - Lower path use bias thresholds to .80 for notice and .60 for warn.
1299 Also make the rate limiting flags for the path use bias log messages
1300 independent from the original path bias flags. Fixes bug 8161;
1301 bugfix on 0.2.4.10-alpha.
1303 o Minor bugfixes (relays):
1304 - Stop trying to resolve our hostname so often (e.g. every time we
1305 think about doing a directory fetch). Now we reuse the cached
1306 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
1307 and 2410 (bugfix on 0.1.2.2-alpha).
1308 - Stop sending a stray "(null)" in some cases for the server status
1309 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
1311 - When choosing which stream on a formerly stalled circuit to wake
1312 first, make better use of the platform's weak RNG. Previously,
1313 we had been using the % ("modulo") operator to try to generate a
1314 1/N chance of picking each stream, but this behaves badly with
1315 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
1317 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
1318 Irix's random() only return 15 bits; Solaris's random() returns more
1319 bits but its RAND_MAX says it only returns 15, and so on. Motivated
1320 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
1322 o Minor bugfixes (directory authorities):
1323 - Directory authorities now use less space when formatting identical
1324 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
1327 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
1328 - Avoid leaking memory if we fail to compute a consensus signature
1329 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
1330 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
1332 - Fix a memory leak during safe-cookie controller authentication.
1333 Bugfix on 0.2.3.13-alpha.
1334 - Avoid memory leak of IPv6 policy content if we fail to format it into
1335 a router descriptor. Bugfix on 0.2.4.7-alpha.
1337 o Minor bugfixes (other code correctness issues):
1338 - Avoid a crash if we fail to generate an extrainfo descriptor.
1339 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
1341 - When detecting the largest possible file descriptor (in order to
1342 close all file descriptors when launching a new program), actually
1343 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
1344 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
1346 - Fix a copy-and-paste error when adding a missing A1 to a routerset
1347 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
1348 Bugfix on 0.2.4.10-alpha.
1349 - Fix an impossible-to-trigger integer overflow when estimating how
1350 long our onionskin queue would take. (This overflow would require us
1351 to accept 4 million onionskins before processing 100 of them.) Fixes
1352 bug 8210; bugfix on 0.2.4.10-alpha.
1354 o Code simplification and refactoring:
1355 - Add a wrapper function for the common "log a message with a
1359 Changes in version 0.2.4.10-alpha - 2013-02-04
1360 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
1361 certain attacks that flood the network with relays; changes the queue
1362 for circuit create requests from a sized-based limit to a time-based
1363 limit; resumes building with MSVC on Windows; and fixes a wide variety
1366 o Major bugfixes (directory authority):
1367 - When computing directory thresholds, ignore any rejected-as-sybil
1368 nodes during the computation so that they can't influence Fast,
1369 Guard, etc. (We should have done this for proposal 109.) Fixes
1371 - When marking a node as a likely sybil, reset its uptime metrics
1372 to zero, so that it cannot time towards getting marked as Guard,
1373 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
1377 - When a TLS write is partially successful but incomplete, remember
1378 that the flushed part has been flushed, and notice that bytes were
1379 actually written. Reported and fixed pseudonymously. Fixes bug
1380 7708; bugfix on Tor 0.1.0.5-rc.
1381 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
1382 ID: these could be used to create unexpected streams and circuits
1383 which would count as "present" to some parts of Tor but "absent"
1384 to others, leading to zombie circuits and streams or to a bandwidth
1385 denial-of-service. Fixes bug 7889; bugfix on every released version
1386 of Tor. Reported by "oftc_must_be_destroyed".
1387 - Rename all macros in our local copy of queue.h to begin with "TOR_".
1388 This change seems the only good way to permanently prevent conflicts
1389 with queue.h on various operating systems. Fixes bug 8107; bugfix
1392 o Major features (relay):
1393 - Instead of limiting the number of queued onionskins (aka circuit
1394 create requests) to a fixed, hard-to-configure number, we limit
1395 the size of the queue based on how many we expect to be able to
1396 process in a given amount of time. We estimate the time it will
1397 take to process an onionskin based on average processing time
1398 of previous onionskins. Closes ticket 7291. You'll never have to
1399 configure MaxOnionsPending again.
1401 o Major features (portability):
1402 - Resume building correctly with MSVC and Makefile.nmake. This patch
1403 resolves numerous bugs and fixes reported by ultramage, including
1404 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
1405 - Make the ntor and curve25519 code build correctly with MSVC.
1406 Fix on 0.2.4.8-alpha.
1409 - When directory authorities are computing thresholds for flags,
1410 never let the threshold for the Fast flag fall below 4096
1411 bytes. Also, do not consider nodes with extremely low bandwidths
1412 when deciding thresholds for various directory flags. This change
1413 should raise our threshold for Fast relays, possibly in turn
1414 improving overall network performance; see ticket 1854. Resolves
1416 - The Tor client now ignores sub-domain components of a .onion
1417 address. This change makes HTTP "virtual" hosting
1418 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
1419 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
1420 hosted on the same hidden service. Implements proposal 204.
1421 - We compute the overhead from passing onionskins back and forth to
1422 cpuworkers, and report it when dumping statistics in response to
1423 SIGUSR1. Supports ticket 7291.
1425 o Minor features (path selection):
1426 - When deciding whether we have enough descriptors to build circuits,
1427 instead of looking at raw relay counts, look at which fraction
1428 of (bandwidth-weighted) paths we're able to build. This approach
1429 keeps clients from building circuits if their paths are likely to
1430 stand out statistically. The default fraction of paths needed is
1431 taken from the consensus directory; you can override it with the
1432 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
1433 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
1434 and we have GeoIP information, also exclude all nodes with unknown
1435 countries "??" and "A1". This behavior is controlled by the
1436 new GeoIPExcludeUnknown option: you can make such nodes always
1437 excluded with "GeoIPExcludeUnknown 1", and disable the feature
1438 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
1439 gets you the default behavior. Implements feature 7706.
1440 - Path Use Bias: Perform separate accounting for successful circuit
1441 use. Keep separate statistics on stream attempt rates versus stream
1442 success rates for each guard. Provide configurable thresholds to
1443 determine when to emit log messages or disable use of guards that
1444 fail too many stream attempts. Resolves ticket 7802.
1446 o Minor features (log messages):
1447 - When learning a fingerprint for a bridge, log its corresponding
1448 transport type. Implements ticket 7896.
1449 - Improve the log message when "Bug/attack: unexpected sendme cell
1450 from client" occurs, to help us track bug 8093.
1453 - Remove a couple of extraneous semicolons that were upsetting the
1454 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
1455 bugfix on 0.2.2.1-alpha.
1456 - Remove a source of rounding error during path bias count scaling;
1457 don't count cannibalized circuits as used for path bias until we
1458 actually try to use them; and fix a circuit_package_relay_cell()
1459 warning message about n_chan==NULL. Fixes bug 7802.
1460 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
1461 actually link against nacl when we're configured to use it. Fixes
1462 bug 7972; bugfix on 0.2.4.8-alpha.
1463 - Compile correctly with the --disable-curve25519 option. Fixes
1464 bug 8153; bugfix on 0.2.4.8-alpha.
1466 o Build improvements:
1467 - Do not report status verbosely from autogen.sh unless the -v flag
1468 is specified. Fixes issue 4664. Patch from Onizuka.
1469 - Replace all calls to snprintf() outside of src/ext with
1470 tor_snprintf(). Also remove the #define to replace snprintf with
1471 _snprintf on Windows; they have different semantics, and all of
1472 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
1473 - Try to detect if we are ever building on a platform where
1474 memset(...,0,...) does not set the value of a double to 0.0. Such
1475 platforms are permitted by the C standard, though in practice
1476 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
1477 currently support them, but it's better to detect them and fail
1478 than to perform erroneously.
1481 - Stop exporting estimates of v2 and v3 directory traffic shares
1482 in extrainfo documents. They were unneeded and sometimes inaccurate.
1483 Also stop exporting any v2 directory request statistics. Resolves
1485 - Drop support for detecting and warning about versions of Libevent
1486 before 1.3e. Nothing reasonable ships with them any longer;
1487 warning the user about them shouldn't be needed. Resolves ticket
1490 o Code simplifications and refactoring:
1491 - Rename "isin" functions to "contains", for grammar. Resolves
1493 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
1494 with the natural logarithm function from the system libm. Resolves
1498 Changes in version 0.2.4.9-alpha - 2013-01-15
1499 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
1503 - Fix backward compatibility logic when receiving an embedded ntor
1504 handshake tunneled in a CREATE cell. This clears up the "Bug:
1505 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
1509 Changes in version 0.2.4.8-alpha - 2013-01-14
1510 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
1511 risks, adds a new stronger and faster circuit handshake, and offers
1512 stronger and faster link encryption when both sides support it.
1515 - Preliminary support for directory guards (proposal 207): when
1516 possible, clients now use their entry guards for non-anonymous
1517 directory requests. This can help prevent client enumeration. Note
1518 that this behavior only works when we have a usable consensus
1519 directory, and when options about what to download are more or less
1520 standard. In the future we should re-bootstrap from our guards,
1521 rather than re-bootstrapping from the preconfigured list of
1522 directory sources that ships with Tor. Resolves ticket 6526.
1523 - Tor relays and clients now support a better CREATE/EXTEND cell
1524 format, allowing the sender to specify multiple address, identity,
1525 and handshake types. Implements Robert Ransom's proposal 200;
1528 o Major features (new circuit handshake):
1529 - Tor now supports a new circuit extension handshake designed by Ian
1530 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
1531 circuit extension handshake, later called "TAP", was a bit slow
1532 (especially on the relay side), had a fragile security proof, and
1533 used weaker keys than we'd now prefer. The new circuit handshake
1534 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
1535 function, making it significantly more secure than the older
1536 handshake, and significantly faster. Tor can use one of two built-in
1537 pure-C curve25519-donna implementations by Adam Langley, or it
1538 can link against the "nacl" library for a tuned version if present.
1540 The built-in version is very fast for 64-bit systems when building
1541 with GCC. The built-in 32-bit version is still faster than the
1542 old TAP protocol, but using libnacl is better on most such hosts.
1544 Clients don't currently use this protocol by default, since
1545 comparatively few clients support it so far. To try it, set
1546 UseNTorHandshake to 1.
1548 Implements proposal 216; closes ticket 7202.
1550 o Major features (better link encryption):
1551 - Relays can now enable the ECDHE TLS ciphersuites when available
1552 and appropriate. These ciphersuites let us negotiate forward-secure
1553 TLS secret keys more safely and more efficiently than with our
1554 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
1555 public relays prefer the (faster) P224 group, and bridges prefer
1556 the (more common) P256 group; you can override this with the
1559 Enabling these ciphers was a little tricky, since for a long time,
1560 clients had been claiming to support them without actually doing
1561 so, in order to foil fingerprinting. But with the client-side
1562 implementation of proposal 198 in 0.2.3.17-beta, clients can now
1563 match the ciphers from recent Firefox versions *and* list the
1564 ciphers they actually mean, so relays can believe such clients
1565 when they advertise ECDHE support in their TLS ClientHello messages.
1567 This feature requires clients running 0.2.3.17-beta or later,
1568 and requires both sides to be running OpenSSL 1.0.0 or later
1569 with ECC support. OpenSSL 1.0.1, with the compile-time option
1570 "enable-ec_nistp_64_gcc_128", is highly recommended.
1572 Implements the relay side of proposal 198; closes ticket 7200.
1575 - Avoid crashing when, as a relay without IPv6-exit support, a
1576 client insists on getting an IPv6 address or nothing. Fixes bug
1577 7814; bugfix on 0.2.4.7-alpha.
1580 - Improve circuit build timeout handling for hidden services.
1581 In particular: adjust build timeouts more accurately depending
1582 upon the number of hop-RTTs that a particular circuit type
1583 undergoes. Additionally, launch intro circuits in parallel
1584 if they timeout, and take the first one to reply as valid.
1585 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
1586 separate error codes; or at least, don't break for that reason.
1587 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
1588 - Update to the January 2 2013 Maxmind GeoLite Country database.
1590 o Minor features (testing):
1591 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
1592 (P-256) Diffie-Hellman handshakes to src/or/bench.
1593 - Add benchmark functions to test onion handshake performance.
1595 o Minor features (path bias detection):
1596 - Alter the Path Bias log messages to be more descriptive in terms
1597 of reporting timeouts and other statistics.
1598 - Create three levels of Path Bias log messages, as opposed to just
1599 two. These are configurable via consensus as well as via the torrc
1600 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
1601 The default values are 0.70, 0.50, and 0.30 respectively.
1602 - Separate the log message levels from the decision to drop guards,
1603 which also is available via torrc option PathBiasDropGuards.
1604 PathBiasDropGuards still defaults to 0 (off).
1605 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
1606 in combination with PathBiasExtremeRate.
1607 - Increase the default values for PathBiasScaleThreshold and
1608 PathBiasCircThreshold from (200, 20) to (300, 150).
1609 - Add in circuit usage accounting to path bias. If we try to use a
1610 built circuit but fail for any reason, it counts as path bias.
1611 Certain classes of circuits where the adversary gets to pick your
1612 destination node are exempt from this accounting. Usage accounting
1613 can be specifically disabled via consensus parameter or torrc.
1614 - Convert all internal path bias state to double-precision floating
1615 point, to avoid roundoff error and other issues.
1616 - Only record path bias information for circuits that have completed
1617 *two* hops. Assuming end-to-end tagging is the attack vector, this
1618 makes us more resilient to ambient circuit failure without any
1619 detection capability loss.
1621 o Minor bugfixes (log messages):
1622 - Rate-limit the "No circuits are opened. Relaxed timeout for a
1623 circuit with channel state open..." message to once per hour to
1624 keep it from filling the notice logs. Mitigates bug 7799 but does
1625 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
1626 - Avoid spurious warnings when configuring multiple client ports of
1627 which only some are nonlocal. Previously, we had claimed that some
1628 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
1631 o Code simplifications and refactoring:
1632 - Get rid of a couple of harmless clang warnings, where we compared
1633 enums to ints. These warnings are newly introduced in clang 3.2.
1634 - Split the onion.c file into separate modules for the onion queue
1635 and the different handshakes it supports.
1636 - Remove the marshalling/unmarshalling code for sending requests to
1637 cpuworkers over a socket, and instead just send structs. The
1638 recipient will always be the same Tor binary as the sender, so
1639 any encoding is overkill.
1642 Changes in version 0.2.4.7-alpha - 2012-12-24
1643 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
1644 directory mirrors for more robust bootstrapping; fixes more issues where
1645 clients with changing network conditions refuse to make any circuits;
1646 adds initial support for exiting to IPv6 addresses; resumes being able
1647 to update our GeoIP database, and includes the geoip6 file this time;
1648 turns off the client-side DNS cache by default due to privacy risks;
1649 and fixes a variety of other issues.
1651 o Major features (client resilience):
1652 - Add a new "FallbackDir" torrc option to use when we can't use
1653 a directory mirror from the consensus (either because we lack a
1654 consensus, or because they're all down). Currently, all authorities
1655 are fallbacks by default, and there are no other default fallbacks,
1656 but that will change. This option will allow us to give clients a
1657 longer list of servers to try to get a consensus from when first
1658 connecting to the Tor network, and thereby reduce load on the
1659 directory authorities. Implements proposal 206, "Preconfigured
1660 directory sources for bootstrapping". We also removed the old
1661 "FallbackNetworkstatus" option, since we never got it working well
1662 enough to use it. Closes bug 572.
1663 - If we have no circuits open, use a relaxed timeout (the
1664 95-percentile cutoff) until a circuit succeeds. This heuristic
1665 should allow Tor to succeed at building circuits even when the
1666 network connection drastically changes. Should help with bug 3443.
1668 o Major features (IPv6):
1669 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
1670 connectivity, then set the IPv6Exit flag to 1. Also make sure your
1671 exit policy reads as you would like: the address * applies to all
1672 address families, whereas *4 is IPv4 address only, and *6 is IPv6
1673 addresses only. On the client side, you'll need to wait until the
1674 authorities have upgraded, wait for enough exits to support IPv6,
1675 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
1676 ticket 5547, implements proposal 117 as revised in proposal 208.
1678 We DO NOT recommend that clients with actual anonymity needs start
1679 using IPv6 over Tor yet, since not enough exits support it yet.
1681 o Major features (geoip database):
1682 - Maxmind began labelling Tor relays as being in country "A1",
1683 which breaks by-country node selection inside Tor. Now we use a
1684 script to replace "A1" ("Anonymous Proxy") entries in our geoip
1685 file with real country codes. This script fixes about 90% of "A1"
1686 entries automatically and uses manual country code assignments to
1687 fix the remaining 10%. See src/config/README.geoip for details.
1688 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
1689 Country database, as modified above.
1691 o Major bugfixes (client-side DNS):
1692 - Turn off the client-side DNS cache by default. Updating and using
1693 the DNS cache is now configurable on a per-client-port
1694 level. SOCKSPort, DNSPort, etc lines may now contain
1695 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
1696 cache these types of DNS answers when we receive them from an
1697 exit node in response to an application request on this port, and
1698 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
1699 cached DNS answers of these types, we shouldn't use them. It's
1700 potentially risky to use cached DNS answers at the client, since
1701 doing so can indicate to one exit what answers we've gotten
1702 for DNS lookups in the past. With IPv6, this becomes especially
1703 problematic. Using cached DNS answers for requests on the same
1704 circuit would present less linkability risk, since all traffic
1705 on a circuit is already linkable, but it would also provide
1706 little performance benefit: the exit node caches DNS replies
1707 too. Implements a simplified version of Proposal 205. Implements
1710 o Major bugfixes (other):
1711 - Alter circuit build timeout measurement to start at the point
1712 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
1713 initialization). This should make our timeout measurements more
1714 uniform. Previously, we were sometimes including ORconn setup time
1715 in our circuit build time measurements. Should resolve bug 3443.
1716 - Fix an assertion that could trigger in hibernate_go_dormant() when
1717 closing an or_connection_t: call channel_mark_for_close() rather
1718 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
1720 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
1721 7655; bugfix on 0.2.4.6-alpha.
1724 - Add a new torrc option "ServerTransportListenAddr" to let bridge
1725 operators select the address where their pluggable transports will
1726 listen for connections. Resolves ticket 7013.
1727 - Allow an optional $ before the node identity digest in the
1728 controller command GETINFO ns/id/<identity>, for consistency with
1729 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
1730 - Log packaged cell fullness as part of the heartbeat message.
1731 Diagnosis to try to determine the extent of bug 7743.
1733 o Minor features (IPv6):
1734 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
1735 prefer to hand out virtual IPv6 addresses, since there are more of
1736 them and we can't run out. To override this behavior and make IPv4
1737 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
1738 or DNSPort you're using for resolving. Implements ticket 7571.
1739 - AutomapHostsOnResolve responses are now randomized, to avoid
1740 annoying situations where Tor is restarted and applications
1741 connect to the wrong addresses.
1742 - Never try more than 1000 times to pick a new virtual address when
1743 AutomapHostsOnResolve is set. That's good enough so long as we
1744 aren't close to handing out our entire virtual address space;
1745 if you're getting there, it's best to switch to IPv6 virtual
1749 - The ADDRMAP command can no longer generate an ill-formed error
1750 code on a failed MAPADDRESS. It now says "internal" rather than
1751 an English sentence fragment with spaces in the middle. Bugfix on
1753 - Fix log messages and comments to avoid saying "GMT" when we mean
1754 "UTC". Fixes bug 6113.
1755 - Compile on win64 using mingw64. Fixes bug 7260; patches from
1757 - Fix a crash when debugging unit tests on Windows: deallocate a
1758 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
1759 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
1762 - The DirServer option is now DirAuthority, for consistency with
1763 current naming patterns. You can still use the old DirServer form.
1765 o Code simplification and refactoring:
1766 - Move the client-side address-map/virtual-address/DNS-cache code
1767 out of connection_edge.c into a new addressmap.c module.
1768 - Remove unused code for parsing v1 directories and "running routers"
1769 documents. Fixes bug 6887.
1772 Changes in version 0.2.3.25 - 2012-11-19
1773 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
1774 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
1775 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
1776 programmer, and friend. Unstinting in his dedication to the cause of
1777 freedom, he inspired and helped many of us as we began our work on
1778 anonymity, and inspires us still. Please honor his memory by writing
1779 software to protect people's freedoms, and by helping others to do so.
1781 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
1782 significantly reduced directory overhead (via microdescriptors),
1783 enormous crypto performance improvements for fast relays on new
1784 enough hardware, a new v3 TLS handshake protocol that can better
1785 resist fingerprinting, support for protocol obfuscation plugins (aka
1786 pluggable transports), better scalability for hidden services, IPv6
1787 support for bridges, performance improvements like allowing clients
1788 to skip the first round-trip on the circuit ("optimistic data") and
1789 refilling token buckets more often, a new "stream isolation" design
1790 to isolate different applications on different circuits, and many
1791 stability, security, and privacy fixes.
1794 - Tor tries to wipe potentially sensitive data after using it, so
1795 that if some subsequent security failure exposes Tor's memory,
1796 the damage will be limited. But we had a bug where the compiler
1797 was eliminating these wipe operations when it decided that the
1798 memory was no longer visible to a (correctly running) program,
1799 hence defeating our attempt at defense in depth. We fix that
1800 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1801 is unlikely to optimize away. Future versions of Tor may use
1802 a less ridiculously heavy approach for this. Fixes bug 7352.
1803 Reported in an article by Andrey Karpov.
1806 - Fix a harmless bug when opting against publishing a relay descriptor
1807 because DisableNetwork is set. Fixes bug 7464; bugfix on
1811 Changes in version 0.2.4.6-alpha - 2012-11-13
1812 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
1813 makes our defense-in-depth memory wiping more reliable, and begins to
1814 count IPv6 addresses in bridge statistics,
1817 - Fix an assertion failure that could occur when closing a connection
1818 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
1820 - Tor tries to wipe potentially sensitive data after using it, so
1821 that if some subsequent security failure exposes Tor's memory,
1822 the damage will be limited. But we had a bug where the compiler
1823 was eliminating these wipe operations when it decided that the
1824 memory was no longer visible to a (correctly running) program,
1825 hence defeating our attempt at defense in depth. We fix that
1826 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1827 is unlikely to optimize away. Future versions of Tor may use
1828 a less ridiculously heavy approach for this. Fixes bug 7352.
1829 Reported in an article by Andrey Karpov.
1832 - Add GeoIP database for IPv6 addresses. The new config option
1834 - Bridge statistics now count bridge clients connecting over IPv6:
1835 bridge statistics files now list "bridge-ip-versions" and
1836 extra-info documents list "geoip6-db-digest". The control protocol
1837 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
1838 implementation by "shkoo", addressing ticket 5055.
1841 - Warn when we are binding low ports when hibernation is enabled;
1842 previously we had warned when we were _advertising_ low ports with
1843 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
1844 - Fix a harmless bug when opting against publishing a relay descriptor
1845 because DisableNetwork is set. Fixes bug 7464; bugfix on
1847 - Add warning message when a managed proxy dies during configuration.
1848 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
1849 - Fix a linking error when building tor-fw-helper without miniupnp.
1850 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
1851 - Check for closing an or_connection_t without going through correct
1852 channel functions; emit a warning and then call
1853 connection_or_close_for_error() so we don't assert as in bugs 7212
1855 - Compile correctly on compilers without C99 designated initializer
1856 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
1857 - Avoid a possible assert that can occur when channel_send_destroy() is
1858 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
1859 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
1860 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
1861 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
1862 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
1864 o Code simplification and refactoring:
1865 - Start using OpenBSD's implementation of queue.h, so that we don't
1866 need to hand-roll our own pointer and list structures whenever we
1867 need them. (We can't rely on a sys/queue.h, since some operating
1868 systems don't have them, and the ones that do have them don't all
1869 present the same extensions.)
1872 Changes in version 0.2.4.5-alpha - 2012-10-25
1873 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
1874 two important security vulnerabilities that could lead to remotely
1875 triggerable relay crashes, fix a major bug that was preventing clients
1876 from choosing suitable exit nodes, and refactor some of our code.
1878 o Major bugfixes (security, also in 0.2.3.24-rc):
1879 - Fix a group of remotely triggerable assertion failures related to
1880 incorrect link protocol negotiation. Found, diagnosed, and fixed
1881 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1883 - Fix a denial of service attack by which any directory authority
1884 could crash all the others, or by which a single v2 directory
1885 authority could crash everybody downloading v2 directory
1886 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1888 o Major bugfixes (also in 0.2.3.24-rc):
1889 - When parsing exit policy summaries from microdescriptors, we had
1890 previously been ignoring the last character in each one, so that
1891 "accept 80,443,8080" would be treated by clients as indicating
1892 a node that allows access to ports 80, 443, and 808. That would
1893 lead to clients attempting connections that could never work,
1894 and ignoring exit nodes that would support their connections. Now
1895 clients parse these exit policy summaries correctly. Fixes bug 7192;
1896 bugfix on 0.2.3.1-alpha.
1898 o Minor bugfixes (also in 0.2.3.24-rc):
1899 - Clients now consider the ClientRejectInternalAddresses config option
1900 when using a microdescriptor consensus stanza to decide whether
1901 an exit relay would allow exiting to an internal address. Fixes
1902 bug 7190; bugfix on 0.2.3.1-alpha.
1905 - Only disable TLS session ticket support when running as a TLS
1906 server. Now clients will blend better with regular Firefox
1907 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
1909 o Code simplification and refactoring:
1910 - Start using OpenBSD's implementation of queue.h (originally by
1912 - Move the entry node code from circuitbuild.c to its own file.
1913 - Move the circuit build timeout tracking code from circuitbuild.c
1917 Changes in version 0.2.3.24-rc - 2012-10-25
1918 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
1919 could lead to remotely triggerable relay crashes, and fixes
1920 a major bug that was preventing clients from choosing suitable exit
1923 o Major bugfixes (security):
1924 - Fix a group of remotely triggerable assertion failures related to
1925 incorrect link protocol negotiation. Found, diagnosed, and fixed
1926 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1928 - Fix a denial of service attack by which any directory authority
1929 could crash all the others, or by which a single v2 directory
1930 authority could crash everybody downloading v2 directory
1931 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1934 - When parsing exit policy summaries from microdescriptors, we had
1935 previously been ignoring the last character in each one, so that
1936 "accept 80,443,8080" would be treated by clients as indicating
1937 a node that allows access to ports 80, 443, and 808. That would
1938 lead to clients attempting connections that could never work,
1939 and ignoring exit nodes that would support their connections. Now
1940 clients parse these exit policy summaries correctly. Fixes bug 7192;
1941 bugfix on 0.2.3.1-alpha.
1944 - Clients now consider the ClientRejectInternalAddresses config option
1945 when using a microdescriptor consensus stanza to decide whether
1946 an exit relay would allow exiting to an internal address. Fixes
1947 bug 7190; bugfix on 0.2.3.1-alpha.
1950 Changes in version 0.2.4.4-alpha - 2012-10-20
1951 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
1952 vulnerability introduced by a change in OpenSSL, fixes a remotely
1953 triggerable assert, and adds new channel_t and circuitmux_t abstractions
1954 that will make it easier to test new connection transport and cell
1955 scheduling algorithms.
1957 o New directory authorities (also in 0.2.3.23-rc):
1958 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1959 authority. Closes ticket 5749.
1961 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
1962 - Disable TLS session tickets. OpenSSL's implementation was giving
1963 our TLS session keys the lifetime of our TLS context objects, when
1964 perfect forward secrecy would want us to discard anything that
1965 could decrypt a link connection as soon as the link connection
1966 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1967 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1968 - Discard extraneous renegotiation attempts once the V3 link
1969 protocol has been initiated. Failure to do so left us open to
1970 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1971 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1973 o Internal abstraction features:
1974 - Introduce new channel_t abstraction between circuits and
1975 or_connection_t to allow for implementing alternate OR-to-OR
1976 transports. A channel_t is an abstract object which can either be a
1977 cell-bearing channel, which is responsible for authenticating and
1978 handshaking with the remote OR and transmitting cells to and from
1979 it, or a listening channel, which spawns new cell-bearing channels
1980 at the request of remote ORs. Implements part of ticket 6465.
1981 - Also new is the channel_tls_t subclass of channel_t, adapting it
1982 to the existing or_connection_t code. The V2/V3 protocol handshaking
1983 code which formerly resided in command.c has been moved below the
1984 channel_t abstraction layer and may be found in channeltls.c now.
1985 Implements the rest of ticket 6465.
1986 - Introduce new circuitmux_t storing the queue of circuits for
1987 a channel; this encapsulates and abstracts the queue logic and
1988 circuit selection policy, and allows the latter to be overridden
1989 easily by switching out a policy object. The existing EWMA behavior
1990 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
1992 o Required libraries:
1993 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
1994 strongly recommended.
1997 - Warn users who run hidden services on a Tor client with
1998 UseEntryGuards disabled that their hidden services will be
1999 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
2000 attack which motivated Tor to support entry guards in the first
2001 place). Resolves ticket 6889.
2002 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
2003 dhill. Resolves ticket 6982.
2004 - Option OutboundBindAddress can be specified multiple times and
2005 accepts IPv6 addresses. Resolves ticket 6876.
2007 o Minor bugfixes (also in 0.2.3.23-rc):
2008 - Don't serve or accept v2 hidden service descriptors over a
2009 relay's DirPort. It's never correct to do so, and disabling it
2010 might make it more annoying to exploit any bugs that turn up in the
2011 descriptor-parsing code. Fixes bug 7149.
2012 - Fix two cases in src/or/transports.c where we were calling
2013 fmt_addr() twice in a parameter list. Bug found by David
2014 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
2015 - Fix memory leaks whenever we logged any message about the "path
2016 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
2017 - When relays refuse a "create" cell because their queue of pending
2018 create cells is too big (typically because their cpu can't keep up
2019 with the arrival rate), send back reason "resource limit" rather
2020 than reason "internal", so network measurement scripts can get a
2021 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
2024 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
2025 - Free some more still-in-use memory at exit, to make hunting for
2026 memory leaks easier. Resolves bug 7029.
2027 - When a Tor client gets a "truncated" relay cell, the first byte of
2028 its payload specifies why the circuit was truncated. We were
2029 ignoring this 'reason' byte when tearing down the circuit, resulting
2030 in the controller not being told why the circuit closed. Now we
2031 pass the reason from the truncated cell to the controller. Bugfix
2032 on 0.1.2.3-alpha; fixes bug 7039.
2033 - Downgrade "Failed to hand off onionskin" messages to "debug"
2034 severity, since they're typically redundant with the "Your computer
2035 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
2036 - Make clients running with IPv6 bridges connect over IPv6 again,
2037 even without setting new config options ClientUseIPv6 and
2038 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
2039 - Use square brackets around IPv6 addresses in numerous places
2040 that needed them, including log messages, HTTPS CONNECT proxy
2041 requests, TransportProxy statefile entries, and pluggable transport
2042 extra-info lines. Fixes bug 7011; patch by David Fifield.
2044 o Code refactoring and cleanup:
2045 - Source files taken from other packages now reside in src/ext;
2046 previously they were scattered around the rest of Tor.
2047 - Avoid use of reserved identifiers in our C code. The C standard
2048 doesn't like us declaring anything that starts with an
2049 underscore, so let's knock it off before we get in trouble. Fix
2050 for bug 1031; bugfix on the first Tor commit.
2053 Changes in version 0.2.3.23-rc - 2012-10-20
2054 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
2055 vulnerability introduced by a change in OpenSSL, and fixes a variety
2056 of smaller bugs in preparation for the release.
2058 o New directory authorities:
2059 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
2060 authority. Closes ticket 5749.
2062 o Major bugfixes (security/privacy):
2063 - Disable TLS session tickets. OpenSSL's implementation was giving
2064 our TLS session keys the lifetime of our TLS context objects, when
2065 perfect forward secrecy would want us to discard anything that
2066 could decrypt a link connection as soon as the link connection
2067 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
2068 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
2069 - Discard extraneous renegotiation attempts once the V3 link
2070 protocol has been initiated. Failure to do so left us open to
2071 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
2072 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
2075 - Fix a possible crash bug when checking for deactivated circuits
2076 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
2077 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
2079 o Minor bugfixes (on 0.2.3.x):
2080 - Fix two cases in src/or/transports.c where we were calling
2081 fmt_addr() twice in a parameter list. Bug found by David
2082 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
2083 - Convert an assert in the pathbias code to a log message. The assert
2084 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
2085 bugfix on 0.2.3.17-beta.
2086 - Fix memory leaks whenever we logged any message about the "path
2087 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
2089 o Minor bugfixes (on 0.2.2.x and earlier):
2090 - Don't serve or accept v2 hidden service descriptors over a relay's
2091 DirPort. It's never correct to do so, and disabling it might
2092 make it more annoying to exploit any bugs that turn up in the
2093 descriptor-parsing code. Fixes bug 7149.
2094 - When relays refuse a "create" cell because their queue of pending
2095 create cells is too big (typically because their cpu can't keep up
2096 with the arrival rate), send back reason "resource limit" rather
2097 than reason "internal", so network measurement scripts can get a
2098 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
2099 - Correct file sizes when reading binary files on Cygwin, to avoid
2100 a bug where Tor would fail to read its state file. Fixes bug 6844;
2101 bugfix on 0.1.2.7-alpha.
2102 - Avoid undefined behaviour when parsing the list of supported
2103 rendezvous/introduction protocols in a hidden service descriptor.
2104 Previously, Tor would have confused (as-yet-unused) protocol version
2105 numbers greater than 32 with lower ones on many platforms. Fixes
2106 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
2108 o Documentation fixes:
2109 - Clarify that hidden services are TCP only. Fixes bug 6024.
2112 Changes in version 0.2.4.3-alpha - 2012-09-22
2113 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
2114 assertion, resumes letting relays test reachability of their DirPort,
2115 and cleans up a bunch of smaller bugs.
2118 - Fix an assertion failure in tor_timegm() that could be triggered
2119 by a badly formatted directory object. Bug found by fuzzing with
2120 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
2123 - Fix a possible crash bug when checking for deactivated circuits
2124 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
2125 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
2126 - Allow routers to detect that their own DirPorts are running. When
2127 we removed support for versions_supports_begindir, we also
2128 accidentally removed the mechanism we used to self-test our
2129 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
2130 bugfix on 0.2.4.2-alpha.
2132 o Security features:
2133 - Switch to a completely time-invariant approach for picking nodes
2134 weighted by bandwidth. Our old approach would run through the
2135 part of the loop after it had made its choice slightly slower
2136 than it ran through the part of the loop before it had made its
2137 choice. Addresses ticket 6538.
2138 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
2139 by tor2web clients allows hidden services to identify tor2web
2140 clients through their repeated selection of the same rendezvous
2141 and introduction point circuit endpoints (their guards). Resolves
2145 - Enable Tor to read configuration, state, and key information from
2146 a FIFO. Previously Tor would only read from files with a positive
2147 stat.st_size. Code from meejah; fixes bug 6044.
2150 - Correct file sizes when reading binary files on Cygwin, to avoid
2151 a bug where Tor would fail to read its state file. Fixes bug 6844;
2152 bugfix on 0.1.2.7-alpha.
2153 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
2154 bugfix on 0.2.0.3-alpha.
2155 - When complaining about a client port on a public address, log
2156 which address we're complaining about. Fixes bug 4020; bugfix on
2157 0.2.3.3-alpha. Patch by Tom Fitzhenry.
2158 - Convert an assert in the pathbias code to a log message. The assert
2159 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
2160 bugfix on 0.2.3.17-beta.
2161 - Our new buildsystem was overzealous about rebuilding manpages: it
2162 would rebuild them all whenever any one of them changed. Now our
2163 dependency checking should be correct. Fixes bug 6843; bugfix on
2165 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
2166 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
2167 - Correct log printout about which address family is preferred
2168 when connecting to a bridge with both an IPv4 and IPv6 OR port.
2169 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
2171 o Minor bugfixes (code cleanliness):
2172 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
2173 with large values. This situation was untriggered, but nevertheless
2174 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
2175 - Reject consensus votes with more than 64 known-flags. We aren't even
2176 close to that limit yet, and our code doesn't handle it correctly.
2177 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
2178 - Avoid undefined behaviour when parsing the list of supported
2179 rendezvous/introduction protocols in a hidden service descriptor.
2180 Previously, Tor would have confused (as-yet-unused) protocol version
2181 numbers greater than 32 with lower ones on many platforms. Fixes
2182 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
2183 - Fix handling of rendezvous client authorization types over 8.
2184 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
2185 - Fix building with older versions of GCC (2.95, for one) that don't
2186 like preprocessor directives inside macro arguments. Found by
2187 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
2188 - Switch weighted node selection rule from using a list of doubles
2189 to using a list of int64_t. This change should make the process
2190 slightly easier to debug and maintain. Needed to finish ticket 6538.
2192 o Code simplification and refactoring:
2193 - Move the generic "config" code into a new file, and have "config.c"
2194 hold only torrc- and state-related code. Resolves ticket 6823.
2195 - Move the core of our "choose a weighted element at random" logic
2196 into its own function, and give it unit tests. Now the logic is
2197 testable, and a little less fragile too.
2198 - Removed the testing_since field of node_t, which hasn't been used
2199 for anything since 0.2.0.9-alpha.
2201 o Documentation fixes:
2202 - Clarify that hidden services are TCP only. Fixes bug 6024.
2203 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
2207 Changes in version 0.2.3.22-rc - 2012-09-11
2208 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
2212 - Fix an assertion failure in tor_timegm() that could be triggered
2213 by a badly formatted directory object. Bug found by fuzzing with
2214 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
2217 - Avoid segfault when starting up having run with an extremely old
2218 version of Tor and parsing its state file. Fixes bug 6801; bugfix
2222 Changes in version 0.2.2.39 - 2012-09-11
2223 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
2227 - Fix an assertion failure in tor_timegm() that could be triggered
2228 by a badly formatted directory object. Bug found by fuzzing with
2229 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
2230 - Do not crash when comparing an address with port value 0 to an
2231 address policy. This bug could have been used to cause a remote
2232 assertion failure by or against directory authorities, or to
2233 allow some applications to crash clients. Fixes bug 6690; bugfix
2237 Changes in version 0.2.4.2-alpha - 2012-09-10
2238 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
2239 raises the default rate limiting even more, and makes the bootstrapping
2240 log messages less noisy.
2243 - Automatically forward the TCP ports of pluggable transport
2244 proxies using tor-fw-helper if PortForwarding is enabled. Implements
2248 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
2249 to 1GB/1GB. The previous defaults were intended to be "basically
2250 infinite", but it turns out they're now limiting our 100mbit+
2251 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
2252 last time we raised it).
2255 - Detect when we're running with a version of OpenSSL other than the
2256 one we compiled with. This has occasionally given people hard-to-
2258 - Log fewer lines at level "notice" about our OpenSSL and Libevent
2259 versions and capabilities when everything is going right. Resolves
2260 part of ticket 6736.
2261 - Directory authorities no long accept descriptors for any version of
2262 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
2263 These versions are insecure, unsupported, or both. Implements
2267 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
2268 to start with a triple-underscore so the controller won't touch it.
2269 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
2270 - Avoid segfault when starting up having run with an extremely old
2271 version of Tor and parsing its state file. Fixes bug 6801; bugfix
2273 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
2274 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
2275 - Don't follow the NULL pointer if microdescriptor generation fails.
2276 (This does not appear to be triggerable, but it's best to be safe.)
2277 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
2278 - Fix mis-declared dependencies on src/common/crypto.c and
2279 src/or/tor_main.c that could break out-of-tree builds under some
2280 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
2281 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
2282 6778; bugfix on 0.2.4.1-alpha.
2283 - Fix a harmless (in this case) build warning for implicitly
2284 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
2287 - Now that all versions before 0.2.2.x are disallowed, we no longer
2288 need to work around their missing features. Thus we can remove a
2289 bunch of compatibility code.
2292 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
2293 TCP ports to forward. In the past it only accepted two ports:
2294 the ORPort and the DirPort.
2297 Changes in version 0.2.4.1-alpha - 2012-09-05
2298 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
2299 bridgedb; lets relays use IPv6 addresses and directory authorities
2300 advertise them; and switches to a cleaner build interface.
2302 This is the first alpha release in a new series, so expect there to
2303 be bugs. Users who would rather test out a more stable branch should
2304 stay with 0.2.3.x for now.
2306 o Major features (bridges):
2307 - Bridges now report the pluggable transports they support to the
2308 bridge authority, so it can pass the supported transports on to
2309 bridgedb and/or eventually do reachability testing. Implements
2312 o Major features (IPv6):
2313 - Bridge authorities now accept IPv6 bridge addresses and include
2314 them in network status documents. Implements ticket 5534.
2315 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
2316 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
2317 to happen. Implements ticket 5535.
2318 - All kind of relays, not just bridges, can now advertise an IPv6
2319 OR port. Implements ticket 6362.
2320 - Directory authorities vote on IPv6 OR ports using the new consensus
2321 method 14. Implements ticket 6363.
2323 o Major features (build):
2324 - Switch to a nonrecursive Makefile structure. Now instead of each
2325 Makefile.am invoking other Makefile.am's, there is a master
2326 Makefile.am that includes the others. This change makes our build
2327 process slightly more maintainable, and improves parallelism for
2328 building with make -j. Original patch by Stewart Smith; various
2329 fixes by Jim Meyering.
2330 - Where available, we now use automake's "silent" make rules by
2331 default, so that warnings are easier to spot. You can get the old
2332 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
2334 o Minor features (code security and spec conformance):
2335 - Clear keys and key-derived material left on the stack in
2336 rendservice.c and rendclient.c. Check return value of
2337 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
2338 These fixes should make us more forward-secure against cold-boot
2339 attacks and the like. Fixes bug 2385.
2340 - Reject EXTEND cells sent to nonexistent streams. According to the
2341 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
2342 we were only checking for stream IDs that were currently in use.
2343 Found while hunting for more instances of bug 6271. Bugfix on
2344 0.0.2pre8, which introduced incremental circuit construction.
2346 o Minor features (streamlining);
2347 - No longer include the "opt" prefix when generating routerinfos
2348 or v2 directories: it has been needless since Tor 0.1.2. Closes
2350 - Remove some now-needless code that tried to aggressively flush
2351 OR connections as data was added to them. Since 0.2.0.1-alpha, our
2352 cell queue logic has saved us from the failure mode that this code
2353 was supposed to prevent. Removing this code will limit the number
2354 of baroque control flow paths through Tor's network logic. Reported
2355 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
2357 o Minor features (controller):
2358 - Add a "GETINFO signal/names" control port command. Implements
2360 - Provide default values for all options via "GETINFO config/defaults".
2361 Implements ticket 4971.
2363 o Minor features (IPv6):
2364 - New config option "AuthDirHasIPv6Connectivity 1" that directory
2365 authorities should set if they have IPv6 connectivity and want to
2366 do reachability tests for IPv6 relays. Implements feature 5974.
2367 - A relay with an IPv6 OR port now sends that address in NETINFO
2368 cells (in addition to its other address). Implements ticket 6364.
2370 o Minor features (log messages):
2371 - Omit the first heartbeat log message, because it never has anything
2372 useful to say, and it clutters up the bootstrapping messages.
2373 Resolves ticket 6758.
2374 - Don't log about reloading the microdescriptor cache at startup. Our
2375 bootstrap warnings are supposed to tell the user when there's a
2376 problem, and our bootstrap notices say when there isn't. Resolves
2377 ticket 6759; bugfix on 0.2.2.6-alpha.
2378 - Don't log "I learned some more directory information" when we're
2379 reading cached directory information. Reserve it for when new
2380 directory information arrives in response to a fetch. Resolves
2382 - Prevent rounding error in path bias counts when scaling
2383 them down, and use the correct scale factor default. Also demote
2384 some path bias related log messages down a level and make others
2385 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
2386 - We no longer warn so much when generating manpages from their
2389 o Code simplifications and refactoring:
2390 - Enhance our internal sscanf replacement so that we can eliminate
2391 the last remaining uses of the system sscanf. (Though those uses
2392 of sscanf were safe, sscanf itself is generally error prone, so
2393 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
2395 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
2396 - Move last_reachable and testing_since from routerinfo_t to node_t.
2397 Implements ticket 5529.
2398 - Add replaycache_t structure, functions and unit tests, then refactor
2399 rend_service_introduce() to be more clear to read, improve, debug,
2400 and test. Resolves bug 6177.
2401 - Finally remove support for malloc_good_size and malloc_usable_size.
2402 We had hoped that these functions would let us eke a little more
2403 memory out of our malloc implementation. Unfortunately, the only
2404 implementations that provided these functions are also ones that
2405 are already efficient about not overallocation: they never got us
2406 more than 7 or so bytes per allocation. Removing them saves us a
2407 little code complexity and a nontrivial amount of build complexity.
2410 - Tor maintainers now require Automake version 1.9 or later to build
2411 Tor from the Git repository. (Automake is not required when building
2412 from a source distribution.)
2415 Changes in version 0.2.3.21-rc - 2012-09-05
2416 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
2417 series. It fixes a trio of potential security bugs, fixes a bug where
2418 we were leaving some of the fast relays out of the microdescriptor
2419 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
2420 and cleans up other smaller issues.
2422 o Major bugfixes (security):
2423 - Tear down the circuit if we get an unexpected SENDME cell. Clients
2424 could use this trick to make their circuits receive cells faster
2425 than our flow control would have allowed, or to gum up the network,
2426 or possibly to do targeted memory denial-of-service attacks on
2427 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
2428 from July 2002, before the release of Tor 0.0.0. We had committed
2429 this patch previously, but we had to revert it because of bug 6271.
2430 Now that 6271 is fixed, this patch appears to work.
2431 - Reject any attempt to extend to an internal address. Without
2432 this fix, a router could be used to probe addresses on an internal
2433 network to see whether they were accepting connections. Fixes bug
2434 6710; bugfix on 0.0.8pre1.
2435 - Do not crash when comparing an address with port value 0 to an
2436 address policy. This bug could have been used to cause a remote
2437 assertion failure by or against directory authorities, or to
2438 allow some applications to crash clients. Fixes bug 6690; bugfix
2442 - Remove the upper bound on microdescriptor length. We were hitting
2443 the limit for routers with complex exit policies or family
2444 declarations, causing clients to not use them. Fixes the first
2445 piece of bug 6404; fix on 0.2.2.6-alpha.
2446 - Detect "ORPort 0" as meaning, uniformly, that we're not running
2447 as a relay. Previously, some of our code would treat the presence
2448 of any ORPort line as meaning that we should act like a relay,
2449 even though our new listener code would correctly not open any
2450 ORPorts for ORPort 0. Similar bugs in other Port options are also
2451 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
2454 - Avoid a pair of double-free and use-after-mark bugs that can
2455 occur with certain timings in canceled and re-received DNS
2456 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
2457 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
2458 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
2459 - Allow one-hop directory fetching circuits the full "circuit build
2460 timeout" period, rather than just half of it, before failing them
2461 and marking the relay down. This fix should help reduce cases where
2462 clients declare relays (or worse, bridges) unreachable because
2463 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
2464 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
2466 - Authorities no longer include any router in their microdescriptor
2467 consensuses for which they couldn't generate or agree on a
2468 microdescriptor. Fixes the second piece of bug 6404; fix on
2470 - Detect and reject attempts to specify both "FooPort" and
2471 "FooPort 0" in the same configuration domain. (It's still okay
2472 to have a FooPort in your configuration file, and use "FooPort 0"
2473 on the command line to disable it.) Fixes the second half of bug
2474 6507; bugfix on 0.2.3.3-alpha.
2475 - Make wildcarded addresses (that is, ones beginning with "*.") work
2476 when provided via the controller's MapAddress command. Previously,
2477 they were accepted, but we never actually noticed that they were
2478 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
2479 - Avoid crashing on a malformed state file where EntryGuardPathBias
2480 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
2481 - Add a (probably redundant) memory clear between iterations of
2482 the router status voting loop, to prevent future coding errors
2483 where data might leak between iterations of the loop. Resolves
2486 o Minor bugfixes (log messages):
2487 - Downgrade "set buildtimeout to low value" messages to "info"
2488 severity; they were never an actual problem, there was never
2489 anything reasonable to do about them, and they tended to spam logs
2490 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
2491 - Downgrade path-bias warning messages to "info". We'll try to get
2492 them working better in 0.2.4. Add internal circuit construction
2493 state to protect against the noisy warn message "Unexpectedly high
2494 circuit_successes". Also add some additional rate-limited notice
2495 messages to help determine the root cause of the warn. Fixes bug
2496 6475. Bugfix against 0.2.3.17-beta.
2497 - Move log message when unable to find a microdesc in a routerstatus
2498 entry to parse time. Previously we'd spam this warning every time
2499 we tried to figure out which microdescriptors to download. Fixes
2500 the third piece of bug 6404; fix on 0.2.3.18-rc.
2503 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
2504 change when the authority is deciding whether to accept a newly
2505 uploaded descriptor. Implements ticket 6423.
2506 - Add missing documentation for consensus and microdesc files.
2507 Resolves ticket 6732.
2510 Changes in version 0.2.2.38 - 2012-08-12
2511 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
2512 attack that could in theory leak path information.
2515 - Avoid an uninitialized memory read when reading a vote or consensus
2516 document that has an unrecognized flavor name. This read could
2517 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
2518 - Try to leak less information about what relays a client is
2519 choosing to a side-channel attacker. Previously, a Tor client would
2520 stop iterating through the list of available relays as soon as it
2521 had chosen one, thus finishing a little earlier when it picked
2522 a router earlier in the list. If an attacker can recover this
2523 timing information (nontrivial but not proven to be impossible),
2524 they could learn some coarse-grained information about which relays
2525 a client was picking (middle nodes in particular are likelier to
2526 be affected than exits). The timing attack might be mitigated by
2527 other factors (see bug 6537 for some discussion), but it's best
2528 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
2531 Changes in version 0.2.3.20-rc - 2012-08-05
2532 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
2533 series. It fixes a pair of code security bugs and a potential anonymity
2534 issue, updates our RPM spec files, and cleans up other smaller issues.
2537 - Avoid read-from-freed-memory and double-free bugs that could occur
2538 when a DNS request fails while launching it. Fixes bug 6480;
2539 bugfix on 0.2.0.1-alpha.
2540 - Avoid an uninitialized memory read when reading a vote or consensus
2541 document that has an unrecognized flavor name. This read could
2542 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
2543 - Try to leak less information about what relays a client is
2544 choosing to a side-channel attacker. Previously, a Tor client would
2545 stop iterating through the list of available relays as soon as it
2546 had chosen one, thus finishing a little earlier when it picked
2547 a router earlier in the list. If an attacker can recover this
2548 timing information (nontrivial but not proven to be impossible),
2549 they could learn some coarse-grained information about which relays
2550 a client was picking (middle nodes in particular are likelier to
2551 be affected than exits). The timing attack might be mitigated by
2552 other factors (see bug 6537 for some discussion), but it's best
2553 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
2556 - Try to make the warning when giving an obsolete SOCKSListenAddress
2557 a little more useful.
2558 - Terminate active server managed proxies if Tor stops being a
2559 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
2560 - Provide a better error message about possible OSX Asciidoc failure
2561 reasons. Fixes bug 6436.
2562 - Warn when Tor is configured to use accounting in a way that can
2563 link a hidden service to some other hidden service or public
2564 address. Resolves ticket 6490.
2567 - Check return value of fputs() when writing authority certificate
2568 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
2569 - Ignore ServerTransportPlugin lines when Tor is not configured as
2570 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
2571 - When disabling guards for having too high a proportion of failed
2572 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
2576 - Update our default RPM spec files to work with mock and rpmbuild
2577 on RHEL/Fedora. They have an updated set of dependencies and
2578 conflicts, a fix for an ancient typo when creating the "_tor"
2579 user, and better instructions. Thanks to Ondrej Mikle for the
2580 patch series. Fixes bug 6043.
2583 - Make it possible to set the TestingTorNetwork configuration
2584 option using AlternateDirAuthority and AlternateBridgeAuthority
2585 as an alternative to setting DirServer. Addresses ticket 6377.
2588 - Clarify the documentation for the Alternate*Authority options.
2590 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
2592 o Code simplification and refactoring:
2593 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
2594 10 lines. Also, don't nest them. Doing so in the past has
2595 led to hard-to-debug code. The new style is to use the
2596 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
2599 Changes in version 0.2.3.19-rc - 2012-07-06
2600 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
2601 series. It fixes the compile on Windows, reverts to a GeoIP database
2602 that isn't as broken, and fixes a flow control bug that has been around
2603 since the beginning of Tor.
2606 - Fix a bug handling SENDME cells on nonexistent streams that could
2607 result in bizarre window values. Report and patch contributed
2608 pseudonymously. Fixes part of bug 6271. This bug was introduced
2609 before the first Tor release, in svn commit r152.
2610 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
2611 June 2012 database, Maxmind marked many Tor relays as country "A1",
2612 which will cause risky behavior for clients that set EntryNodes
2613 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
2614 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
2615 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
2618 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
2619 bugfix on 0.2.1.10-alpha.
2622 Changes in version 0.2.3.18-rc - 2012-06-28
2623 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
2624 series. It fixes a few smaller bugs, but generally appears stable.
2625 Please test it and let us know whether it is!
2628 - Allow wildcarded mapaddress targets to be specified on the
2629 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
2630 - Make our linker option detection code more robust against linkers
2631 such as on FreeBSD 8, where a bad combination of options completes
2632 successfully but makes an unrunnable binary. Fixes bug 6173;
2633 bugfix on 0.2.3.17-beta.
2635 o Minor bugfixes (on 0.2.2.x and earlier):
2636 - Avoid a false positive in the util/threads unit test by increasing
2637 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
2638 - Replace "Sending publish request" log messages with "Launching
2639 upload", so that they no longer confusingly imply that we're
2640 sending something to a directory we might not even be connected
2641 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
2642 - Make sure to set *socket_error in all error cases in
2643 connection_connect(), so it can't produce a warning about
2644 errno being zero from errno_to_orconn_end_reason(). Bugfix on
2645 0.2.1.1-alpha; resolves ticket 6028.
2646 - Downgrade "Got a certificate, but we already have it" log messages
2647 from warning to info, except when we're a dirauth. Fixes bug 5238;
2648 bugfix on 0.2.1.7-alpha.
2649 - When checking for requested signatures on the latest consensus
2650 before serving it to a client, make sure to check the right
2651 consensus flavor. Bugfix on 0.2.2.6-alpha.
2652 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
2653 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
2655 o Minor bugfixes (on 0.2.3.x):
2656 - Make format_helper_exit_status() avoid unnecessary space padding
2657 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
2659 - Downgrade a message about cleaning the microdescriptor cache to
2660 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
2661 - Log a BUG message at severity INFO if we have a networkstatus with
2662 a missing entry for some microdescriptor. Continues on a patch
2664 - Improve the log message when a managed proxy fails to launch. Fixes
2665 bug 5099; bugfix on 0.2.3.6-alpha.
2666 - Don't do DNS lookups when parsing corrupted managed proxy protocol
2667 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
2668 - When formatting wildcarded address mappings for the controller,
2669 be sure to include "*." as appropriate. Partially fixes bug 6244;
2670 bugfix on 0.2.3.9-alpha.
2671 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
2672 Bugfix on 0.2.3.13-alpha.
2673 - Stop logging messages about running with circuit timeout learning
2674 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
2675 - Disable a spurious warning about reading on a marked and flushing
2676 connection. We shouldn't be doing that, but apparently we
2677 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
2678 - Fix a bug that stopped AllowDotExit from working on addresses
2679 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
2682 o Code simplification, refactoring, unit tests:
2683 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
2684 Libevent's notion of cached time when possible.
2685 - Remove duplicate code for invoking getrlimit() from control.c.
2686 - Add a unit test for the environment_variable_names_equal function.
2689 - Document the --defaults-torrc option, and the new (in 0.2.3)
2690 semantics for overriding, extending, and clearing lists of
2691 options. Closes bug 4748.
2694 Changes in version 0.2.3.17-beta - 2012-06-15
2695 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
2696 gets our TLS handshake back on track for being able to blend in with
2697 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
2698 with Vidalia, and otherwise continues to get us closer to a release
2702 - Enable gcc and ld hardening by default. Resolves ticket 5210.
2703 - Update TLS cipher list to match Firefox 8 and later. Resolves
2705 - Implement the client side of proposal 198: remove support for
2706 clients falsely claiming to support standard ciphersuites that
2707 they can actually provide. As of modern OpenSSL versions, it's not
2708 necessary to fake any standard ciphersuite, and doing so prevents
2709 us from using better ciphersuites in the future, since servers
2710 can't know whether an advertised ciphersuite is really supported or
2711 not. Some hosts -- notably, ones with very old versions of OpenSSL
2712 or where OpenSSL has been built with ECC disabled -- will stand
2713 out because of this change; TBB users should not be affected.
2716 - Change the default value for DynamicDHGroups (introduced in
2717 0.2.3.9-alpha) to 0. This feature can make Tor relays less
2718 identifiable by their use of the mod_ssl DH group, but at
2719 the cost of some usability (#4721) and bridge tracing (#6087)
2720 regressions. Resolves ticket 5598.
2721 - Send a CRLF at the end of each STATUS_* control protocol event. This
2722 bug tickled a bug in Vidalia which would make it freeze. Fixes
2723 bug 6094; bugfix on 0.2.3.16-alpha.
2726 - Disable writing on marked-for-close connections when they are
2727 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
2728 bug 5263; bugfix on 0.0.2pre13, where we first added a special
2729 case for flushing marked connections.
2730 - Detect SSL handshake even when the initial attempt to write the
2731 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
2732 - Change the AllowDotExit rules so they should actually work.
2733 We now enforce AllowDotExit only immediately after receiving an
2734 address via SOCKS or DNSPort: other sources are free to provide
2735 .exit addresses after the resolution occurs. Fixes bug 3940;
2736 bugfix on 0.2.2.1-alpha.
2737 - Fix a (harmless) integer overflow in cell statistics reported by
2738 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
2739 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
2740 right places and never depends on the consensus parameters or
2741 computes adaptive timeouts when it is disabled. Fixes bug 5049;
2742 bugfix on 0.2.2.14-alpha.
2743 - When building Tor on Windows with -DUNICODE (not default), ensure
2744 that error messages, filenames, and DNS server names are always
2745 NUL-terminated when we convert them to a single-byte encoding.
2746 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
2747 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
2748 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
2749 - Fix an edge case where TestingTorNetwork is set but the authorities
2750 and relays all have an uptime of zero, where the private Tor network
2751 could briefly lack support for hidden services. Fixes bug 3886;
2752 bugfix on 0.2.2.18-alpha.
2753 - Correct the manpage's descriptions for the default values of
2754 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
2756 - Fix the documentation for the --hush and --quiet command line
2757 options, which changed their behavior back in 0.2.3.3-alpha.
2758 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
2762 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
2763 more information to it, so that we can track it down in case it
2764 returns again. Mitigates bug 5235.
2765 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
2766 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
2767 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
2768 - Warn the user when HTTPProxy, but no other proxy type, is
2769 configured. This can cause surprising behavior: it doesn't send
2770 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
2771 directory traffic only. Resolves ticket 4663.
2772 - Issue a notice if a guard completes less than 40% of your circuits.
2773 Threshold is configurable by torrc option PathBiasNoticeRate and
2774 consensus parameter pb_noticepct. There is additional, off-by-
2775 default code to disable guards which fail too many circuits.
2776 Addresses ticket 5458.
2777 - Update to the June 6 2012 Maxmind GeoLite Country database.
2779 o Code simplifications and refactoring:
2780 - Remove validate_pluggable_transports_config(): its warning
2781 message is now handled by connection_or_connect().
2784 Changes in version 0.2.2.37 - 2012-06-06
2785 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
2786 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2790 - Work around a bug in OpenSSL that broke renegotiation with TLS
2791 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2792 the v2 Tor connection protocol when both sides were using OpenSSL
2793 1.0.1 would fail. Resolves ticket 6033.
2794 - When waiting for a client to renegotiate, don't allow it to add
2795 any bytes to the input buffer. This fixes a potential DoS issue.
2796 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2797 - Fix an edge case where if we fetch or publish a hidden service
2798 descriptor, we might build a 4-hop circuit and then use that circuit
2799 for exiting afterwards -- even if the new last hop doesn't obey our
2800 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2803 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2804 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2807 - Tell GCC and Clang to check for any errors in format strings passed
2808 to the tor_v*(print|scan)f functions.
2811 Changes in version 0.2.3.16-alpha - 2012-06-05
2812 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
2813 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2814 currently). It also fixes a variety of smaller bugs and other cleanups
2815 that get us closer to a release candidate.
2817 o Major bugfixes (general):
2818 - Work around a bug in OpenSSL that broke renegotiation with TLS
2819 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2820 the v2 Tor connection protocol when both sides were using OpenSSL
2821 1.0.1 would fail. Resolves ticket 6033.
2822 - When waiting for a client to renegotiate, don't allow it to add
2823 any bytes to the input buffer. This fixes a potential DoS issue.
2824 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2825 - Pass correct OR address to managed proxies (like obfsproxy),
2826 even when ORListenAddress is used. Fixes bug 4865; bugfix on
2828 - The advertised platform of a router now includes only its operating
2829 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
2830 service pack level (for Windows) or its CPU architecture (for Unix).
2831 We also no longer include the "git-XYZ" tag in the version. Resolves
2834 o Major bugfixes (clients):
2835 - If we are unable to find any exit that supports our predicted ports,
2836 stop calling them predicted, so that we don't loop and build
2837 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
2838 which introduced predicted ports.
2839 - Fix an edge case where if we fetch or publish a hidden service
2840 descriptor, we might build a 4-hop circuit and then use that circuit
2841 for exiting afterwards -- even if the new last hop doesn't obey our
2842 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2843 - Check at each new consensus whether our entry guards were picked
2844 long enough ago that we should rotate them. Previously, we only
2845 did this check at startup, which could lead to us holding a guard
2846 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
2847 - When fetching a bridge descriptor from a bridge authority,
2848 always do so anonymously, whether we have been able to open
2849 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
2850 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
2851 but we'll need to wait for bug 6010 before it's actually usable.
2853 o Major bugfixes (directory authorities):
2854 - When computing weight parameters, behave more robustly in the
2855 presence of a bad bwweightscale value. Previously, the authorities
2856 would crash if they agreed on a sufficiently broken weight_scale
2857 value: now, they use a reasonable default and carry on. Partial
2858 fix for 5786; bugfix on 0.2.2.17-alpha.
2859 - Check more thoroughly to prevent a rogue authority from
2860 double-voting on any consensus directory parameter. Previously,
2861 authorities would crash in this case if the total number of
2862 votes for any parameter exceeded the number of active voters,
2863 but would let it pass otherwise. Partial fix for bug 5786; bugfix
2867 - Rate-limit log messages when asked to connect anonymously to
2868 a private address. When these hit, they tended to hit fast and
2869 often. Also, don't bother trying to connect to addresses that we
2870 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
2871 reply makes us think we have been lied to, even when the address the
2872 client tried to connect to was "localhost." Resolves ticket 2822.
2873 - Allow packagers to insert an extra string in server descriptor
2874 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
2875 Resolves the rest of ticket 2988.
2876 - Raise the threshold of server descriptors needed (75%) and exit
2877 server descriptors needed (50%) before we will declare ourselves
2878 bootstrapped. This will make clients start building circuits a
2879 little later, but makes the initially constructed circuits less
2880 skewed and less in conflict with further directory fetches. Fixes
2882 - Close any connection that sends unrecognized junk before the
2883 handshake. Solves an issue noted in bug 4369.
2884 - Improve log messages about managed transports. Resolves ticket 5070.
2885 - Tag a bridge's descriptor as "never to be sent unencrypted".
2886 This shouldn't matter, since bridges don't open non-anonymous
2887 connections to the bridge authority and don't allow unencrypted
2888 directory connections from clients, but we might as well make
2889 sure. Closes bug 5139.
2890 - Expose our view of whether we have gone dormant to the controller,
2891 via a new "GETINFO dormant" value. Torbutton and other controllers
2892 can use this to avoid doing periodic requests through Tor while
2893 it's dormant (bug 4718). Fixes bug 5954.
2894 - Tell GCC and Clang to check for any errors in format strings passed
2895 to the tor_v*(print|scan)f functions.
2896 - Update to the May 1 2012 Maxmind GeoLite Country database.
2898 o Minor bugfixes (already included in 0.2.2.36):
2899 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2900 Fixes bug 5346; bugfix on 0.0.8pre3.
2901 - Correct parsing of certain date types in parse_http_time().
2902 Without this patch, If-Modified-Since would behave
2903 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2904 Esteban Manchado Velázques.
2905 - Make our number-parsing functions always treat too-large values
2906 as an error, even when those values exceed the width of the
2907 underlying type. Previously, if the caller provided these
2908 functions with minima or maxima set to the extreme values of the
2909 underlying integer type, these functions would return those
2910 values on overflow rather than treating overflow as an error.
2911 Fixes part of bug 5786; bugfix on 0.0.9.
2912 - If we hit the error case where routerlist_insert() replaces an
2913 existing (old) server descriptor, make sure to remove that
2914 server descriptor from the old_routers list. Fix related to bug
2915 1776. Bugfix on 0.2.2.18-alpha.
2916 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2917 circuits. Fixes issue 5259.
2919 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
2920 - Prevent a null-pointer dereference when receiving a data cell
2921 for a nonexistent stream when the circuit in question has an
2922 empty deliver window. We don't believe this is triggerable,
2923 since we don't currently allow deliver windows to become empty,
2924 but the logic is tricky enough that it's better to make the code
2925 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
2926 - Fix a memory leak when trying to launch a DNS request when the
2927 network is disabled or the nameservers are unconfigurable. Fixes
2928 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
2929 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
2930 - Don't hold a Windows file handle open for every file mapping;
2931 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
2933 - Avoid O(n^2) performance characteristics when parsing a large
2934 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
2935 - Format more doubles with %f, not %lf. Patch from grarpamp to make
2936 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
2938 - Make our replacement implementation of strtok_r() compatible with
2939 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
2940 bugfix on 0.2.2.1-alpha.
2941 - Fix a NULL-pointer dereference on a badly formed
2942 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
2943 bugfix on 0.2.2.9-alpha.
2944 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2945 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2946 - Defensively refactor rend_mid_rendezvous() so that protocol
2947 violations and length checks happen in the beginning. Fixes
2949 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
2950 that IPv6 stuff will compile on MSVC, and compilation issues
2951 will be easier to track down. Fixes bug 5861.
2953 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
2954 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
2955 resource exhaustion, so that clients can adjust their load to
2956 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
2957 started using END_STREAM_REASON_RESOURCELIMIT.
2958 - Don't check for whether the address we're using for outbound
2959 connections has changed until after the outbound connection has
2960 completed. On Windows, getsockname() doesn't succeed until the
2961 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
2962 - If the configuration tries to set MyFamily on a bridge, refuse to
2963 do so, and warn about the security implications. Fixes bug 4657;
2964 bugfix on 0.2.0.3-alpha.
2965 - If the client fails to set a reasonable set of ciphersuites
2966 during its v2 handshake renegotiation, allow the renegotiation to
2967 continue nevertheless (i.e. send all the required certificates).
2968 Fixes bug 4591; bugfix on 0.2.0.20-rc.
2969 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
2970 option is set to 0 (which Vidalia version 0.2.16 now does when
2971 a SAVECONF attempt fails), perform other actions that SIGHUP
2972 usually causes (like reopening the logs). Fixes bug 5095; bugfix
2974 - If we fail to write a microdescriptor to the disk cache, do not
2975 continue replacing the old microdescriptor file. Fixes bug 2954;
2976 bugfix on 0.2.2.6-alpha.
2977 - Exit nodes don't need to fetch certificates for authorities that
2978 they don't recognize; only directory authorities, bridges,
2979 and caches need to do that. Fixes part of bug 2297; bugfix on
2981 - Correctly handle checking the permissions on the parent
2982 directory of a control socket in the root directory. Bug found
2983 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
2985 - When told to add a bridge with the same digest as a preexisting
2986 bridge but a different addr:port, change the addr:port as
2987 requested. Previously we would not notice the change. Fixes half
2988 of bug 5603; fix on 0.2.2.26-beta.
2989 - End AUTHCHALLENGE error messages (in the control protocol) with
2990 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
2992 o Minor bugfixes (on 0.2.3.x):
2993 - Turn an assertion (that the number of handshakes received as a
2994 server is not < 1) into a warning. Fixes bug 4873; bugfix on
2996 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
2997 we had reversed them when the answer was cached.) Fixes bug
2998 5723; bugfix on 0.2.3.1-alpha.
2999 - Work correctly on Linux systems with accept4 support advertised in
3000 their headers, but without accept4 support in the kernel. Fix
3001 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
3002 - When told to add a bridge with the same addr:port as a preexisting
3003 bridge but a different transport, change the transport as
3004 requested. Previously we would not notice the change. Fixes half
3005 of bug 5603; fix on 0.2.3.2-alpha.
3006 - Avoid a "double-reply" warning when replying to a SOCKS request
3007 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
3008 bugfix on 0.2.3.4-alpha.
3009 - Fix a bug where a bridge authority crashes if it has seen no
3010 directory requests when it's time to write statistics to disk.
3011 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
3013 - Don't try to open non-control listeners when DisableNetwork is set.
3014 Previously, we'd open all listeners, then immediately close them.
3015 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
3016 - Don't abort the managed proxy protocol if the managed proxy
3017 sends us an unrecognized line; ignore it instead. Fixes bug
3018 5910; bugfix on 0.2.3.9-alpha.
3019 - Fix a compile warning in crypto.c when compiling with clang 3.1.
3020 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
3021 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
3022 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
3023 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
3024 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
3025 - Resolve numerous small warnings and build issues with MSVC. Resolves
3028 o Documentation fixes:
3029 - Improve the manual's documentation for the NT Service command-line
3030 options. Addresses ticket 3964.
3031 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
3032 - Document the changes to the ORPort and DirPort options, and the
3033 fact that {OR/Dir}ListenAddress is now unnecessary (and
3034 therefore deprecated). Resolves ticket 5597.
3037 - Remove the torrc.bridge file: we don't use it for anything, and
3038 it had become badly desynchronized from torrc.sample. Resolves
3042 Changes in version 0.2.2.36 - 2012-05-24
3043 Tor 0.2.2.36 updates the addresses for two of the eight directory
3044 authorities, fixes some potential anonymity and security issues,
3045 and fixes several crash bugs.
3047 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
3048 known flaws, and nobody should be using them. You should upgrade. If
3049 you're using a Linux or BSD and its packages are obsolete, stop using
3050 those packages and upgrade anyway.
3052 o Directory authority changes:
3053 - Change IP address for maatuska (v3 directory authority).
3054 - Change IP address for ides (v3 directory authority), and rename
3058 - When building or running with any version of OpenSSL earlier
3059 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
3060 versions have a bug (CVE-2011-4576) in which their block cipher
3061 padding includes uninitialized data, potentially leaking sensitive
3062 information to any peer with whom they make a SSLv3 connection. Tor
3063 does not use SSL v3 by default, but a hostile client or server
3064 could force an SSLv3 connection in order to gain information that
3065 they shouldn't have been able to get. The best solution here is to
3066 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
3067 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
3068 to make sure that the bug can't happen.
3069 - Never use a bridge or a controller-supplied node as an exit, even
3070 if its exit policy allows it. Found by wanoskarnet. Fixes bug
3071 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
3072 and 0.2.0.3-alpha (for bridge-purpose descriptors).
3073 - Only build circuits if we have a sufficient threshold of the total
3074 descriptors that are marked in the consensus with the "Exit"
3075 flag. This mitigates an attack proposed by wanoskarnet, in which
3076 all of a client's bridges collude to restrict the exit nodes that
3077 the client knows about. Fixes bug 5343.
3078 - Provide controllers with a safer way to implement the cookie
3079 authentication mechanism. With the old method, if another locally
3080 running program could convince a controller that it was the Tor
3081 process, then that program could trick the controller into telling
3082 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
3083 authentication method uses a challenge-response approach to prevent
3084 this attack. Fixes bug 5185; implements proposal 193.
3087 - Avoid logging uninitialized data when unable to decode a hidden
3088 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
3089 - Avoid a client-side assertion failure when receiving an INTRODUCE2
3090 cell on a general purpose circuit. Fixes bug 5644; bugfix on
3092 - Fix builds when the path to sed, openssl, or sha1sum contains
3093 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
3095 - Correct our replacements for the timeradd() and timersub() functions
3096 on platforms that lack them (for example, Windows). The timersub()
3097 function is used when expiring circuits, while timeradd() is
3098 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
3099 bugfix on 0.2.2.24-alpha.
3100 - Fix the SOCKET_OK test that we use to tell when socket
3101 creation fails so that it works on Win64. Fixes part of bug 4533;
3102 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
3105 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
3106 Fixes bug 5346; bugfix on 0.0.8pre3.
3107 - Make our number-parsing functions always treat too-large values
3108 as an error, even when those values exceed the width of the
3109 underlying type. Previously, if the caller provided these
3110 functions with minima or maxima set to the extreme values of the
3111 underlying integer type, these functions would return those
3112 values on overflow rather than treating overflow as an error.
3113 Fixes part of bug 5786; bugfix on 0.0.9.
3114 - Older Linux kernels erroneously respond to strange nmap behavior
3115 by having accept() return successfully with a zero-length
3116 socket. When this happens, just close the connection. Previously,
3117 we would try harder to learn the remote address: but there was
3118 no such remote address to learn, and our method for trying to
3119 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
3120 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
3121 - Correct parsing of certain date types in parse_http_time().
3122 Without this patch, If-Modified-Since would behave
3123 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
3124 Esteban Manchado Velázques.
3125 - Change the BridgePassword feature (part of the "bridge community"
3126 design, which is not yet implemented) to use a time-independent
3127 comparison. The old behavior might have allowed an adversary
3128 to use timing to guess the BridgePassword value. Fixes bug 5543;
3129 bugfix on 0.2.0.14-alpha.
3130 - Detect and reject certain misformed escape sequences in
3131 configuration values. Previously, these values would cause us
3132 to crash if received in a torrc file or over an authenticated
3133 control port. Bug found by Esteban Manchado Velázquez, and
3134 independently by Robert Connolly from Matta Consulting who further
3135 noted that it allows a post-authentication heap overflow. Patch
3136 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
3137 bugfix on 0.2.0.16-alpha.
3138 - Fix a compile warning when using the --enable-openbsd-malloc
3139 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
3140 - During configure, detect when we're building with clang version
3141 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
3142 CFLAGS. clang doesn't support them yet.
3143 - When sending an HTTP/1.1 proxy request, include a Host header.
3144 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
3145 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
3146 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
3147 - If we hit the error case where routerlist_insert() replaces an
3148 existing (old) server descriptor, make sure to remove that
3149 server descriptor from the old_routers list. Fix related to bug
3150 1776. Bugfix on 0.2.2.18-alpha.
3152 o Minor bugfixes (documentation and log messages):
3153 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
3154 Fixes bug 4856; bugfix on Tor 0.0.6.
3155 - Update "ClientOnly" man page entry to explain that there isn't
3156 really any point to messing with it. Resolves ticket 5005.
3157 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
3158 directory authority option (introduced in Tor 0.2.2.34).
3159 - Downgrade the "We're missing a certificate" message from notice
3160 to info: people kept mistaking it for a real problem, whereas it
3161 is seldom the problem even when we are failing to bootstrap. Fixes
3162 bug 5067; bugfix on 0.2.0.10-alpha.
3163 - Correctly spell "connect" in a log message on failure to create a
3164 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
3165 - Clarify the behavior of MaxCircuitDirtiness with hidden service
3166 circuits. Fixes issue 5259.
3169 - Directory authorities now reject versions of Tor older than
3170 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
3171 inclusive. These versions accounted for only a small fraction of
3172 the Tor network, and have numerous known security issues. Resolves
3174 - Update to the May 1 2012 Maxmind GeoLite Country database.
3177 - When sending or relaying a RELAY_EARLY cell, we used to convert
3178 it to a RELAY cell if the connection was using the v1 link
3179 protocol. This was a workaround for older versions of Tor, which
3180 didn't handle RELAY_EARLY cells properly. Now that all supported
3181 versions can handle RELAY_EARLY cells, and now that we're enforcing
3182 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
3183 remove this workaround. Addresses bug 4786.
3186 Changes in version 0.2.3.15-alpha - 2012-04-30
3187 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
3188 the development branch build on Windows again.
3190 o Minor bugfixes (on 0.2.2.x and earlier):
3191 - Make sure that there are no unhandled pending TLS errors before
3192 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
3193 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
3194 Bugfix on 0.1.0.5-rc; fixes bug 4528.
3195 - Fix an assert that directory authorities could trigger on sighup
3196 during some configuration state transitions. We now don't treat
3197 it as a fatal error when the new descriptor we just generated in
3198 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
3199 - After we pick a directory mirror, we would refuse to use it if
3200 it's in our ExcludeExitNodes list, resulting in mysterious failures
3201 to bootstrap for people who just wanted to avoid exiting from
3202 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
3203 - When building with --enable-static-tor on OpenBSD, do not
3204 erroneously attempt to link -lrt. Fixes bug 5103.
3206 o Minor bugfixes (on 0.2.3.x):
3207 - When Tor is built with kernel headers from a recent (last few
3208 years) Linux kernel, do not fail to run on older (pre-2.6.28
3209 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
3210 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
3212 - Fix compilation with miniupnpc version 1.6; patch from
3213 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
3214 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
3215 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
3216 - Fix compilation on platforms without unistd.h, or where environ
3217 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
3220 - Directory authorities are now a little more lenient at accepting
3221 older router descriptors, or newer router descriptors that don't
3222 make big changes. This should help ameliorate past and future
3223 issues where routers think they have uploaded valid descriptors,
3224 but the authorities don't think so. Fix for ticket 2479.
3225 - Make the code that clients use to detect an address change be
3226 IPv6-aware, so that it won't fill clients' logs with error
3227 messages when trying to get the IPv4 address of an IPv6
3228 connection. Implements ticket 5537.
3231 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
3232 authorities needed to use it for a while to keep the network working
3233 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
3234 that was six months ago. As of now, it should no longer be needed
3238 Changes in version 0.2.3.14-alpha - 2012-04-23
3239 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
3240 candidate. It also dramatically speeds up AES: fast relays should
3241 consider switching to the newer OpenSSL library.
3243 o Directory authority changes:
3244 - Change IP address for ides (v3 directory authority), and rename
3248 - Avoid logging uninitialized data when unable to decode a hidden
3249 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
3250 - Avoid a client-side assertion failure when receiving an INTRODUCE2
3251 cell on a general purpose circuit. Fixes bug 5644; bugfix on
3253 - If authorities are unable to get a v2 consensus document from other
3254 directory authorities, they no longer fall back to fetching
3255 them from regular directory caches. Fixes bug 5635; bugfix on
3256 0.2.2.26-beta, where routers stopped downloading v2 consensus
3258 - When we start a Tor client with a normal consensus already cached,
3259 be willing to download a microdescriptor consensus. Fixes bug 4011;
3260 fix on 0.2.3.1-alpha.
3262 o Major features (performance):
3263 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
3264 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
3265 vectorized AES implementations as appropriate. These can be much,
3266 much faster than other AES implementations.
3268 o Minor bugfixes (0.2.2.x and earlier):
3269 - Don't launch more than 10 service-side introduction-point circuits
3270 for a hidden service in five minutes. Previously, we would consider
3271 launching more introduction-point circuits if at least one second
3272 had passed without any introduction-point circuits failing. Fixes
3273 bug 4607; bugfix on 0.0.7pre1.
3274 - Change the BridgePassword feature (part of the "bridge community"
3275 design, which is not yet implemented) to use a time-independent
3276 comparison. The old behavior might have allowed an adversary
3277 to use timing to guess the BridgePassword value. Fixes bug 5543;
3278 bugfix on 0.2.0.14-alpha.
3279 - Enforce correct return behavior of tor_vsscanf() when the '%%'
3280 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
3281 - When sending an HTTP/1.1 proxy request, include a Host header.
3282 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
3283 - Don't log that we have "decided to publish new relay descriptor"
3284 unless we are actually publishing a descriptor. Fixes bug 3942;
3285 bugfix on 0.2.2.28-beta.
3287 o Minor bugfixes (0.2.3.x):
3288 - Fix a bug where a bridge authority crashes (on a failed assert)
3289 if it has seen no directory requests when it's time to write
3290 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
3291 - Fix bug stomping on ORPort option NoListen and ignoring option
3292 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
3293 - In the testsuite, provide a large enough buffer in the tor_sscanf
3294 unit test. Otherwise we'd overrun that buffer and crash during
3295 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
3297 - Make sure we create the keys directory if it doesn't exist and we're
3298 about to store the dynamic Diffie-Hellman parameters. Fixes bug
3299 5572; bugfix on 0.2.3.13-alpha.
3300 - Fix a small memory leak when trying to decode incorrect base16
3301 authenticator during SAFECOOKIE authentication. Found by
3302 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
3305 - Add more information to a log statement that might help track down
3306 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
3307 non-IP address" messages (or any Bug messages, for that matter!),
3308 please let us know about it.
3309 - Relays now understand an IPv6 address when they get one from a
3310 directory server. Resolves ticket 4875.
3311 - Resolve IPv6 addresses in bridge and entry statistics to country
3312 code "??" which means we at least count them. Resolves ticket 5053;
3313 improves on 0.2.3.9-alpha.
3314 - Update to the April 3 2012 Maxmind GeoLite Country database.
3315 - Begin a doc/state-contents.txt file to explain the contents of
3316 the Tor state file. Fixes bug 2987.
3318 o Default torrc changes:
3319 - Stop listing "socksport 9050" in torrc.sample. We open a socks
3320 port on 9050 by default anyway, so this should not change anything
3322 - Stop mentioning the deprecated *ListenAddress options in
3323 torrc.sample. Fixes bug 5438.
3324 - Document unit of bandwidth related options in sample torrc.
3328 - The "torify" script no longer supports the "tsocks" socksifier
3329 tool, since tsocks doesn't support DNS and UDP right for Tor.
3330 Everyone should be using torsocks instead. Fixes bugs 3530 and
3331 5180. Based on a patch by "ugh".
3334 - Change the symmetric cipher interface so that creating and
3335 initializing a stream cipher are no longer separate functions.
3336 - Remove all internal support for unpadded RSA. We never used it, and
3337 it would be a bad idea to start.
3340 Changes in version 0.2.3.13-alpha - 2012-03-26
3341 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
3342 in managed pluggable transports, as well as providing other cleanups
3343 that get us closer to a release candidate.
3345 o Directory authority changes:
3346 - Change IP address for maatuska (v3 directory authority).
3349 - Provide controllers with a safer way to implement the cookie
3350 authentication mechanism. With the old method, if another locally
3351 running program could convince a controller that it was the Tor
3352 process, then that program could trick the controller into telling
3353 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
3354 authentication method uses a challenge-response approach to prevent
3355 this attack. Fixes bug 5185, implements proposal 193.
3356 - Never use a bridge or a controller-supplied node as an exit, even
3357 if its exit policy allows it. Found by wanoskarnet. Fixes bug
3358 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
3359 and 0.2.0.3-alpha (for bridge-purpose descriptors).
3360 - Only build circuits if we have a sufficient threshold of the total
3361 descriptors that are marked in the consensus with the "Exit"
3362 flag. This mitigates an attack proposed by wanoskarnet, in which
3363 all of a client's bridges collude to restrict the exit nodes that
3364 the client knows about. Fixes bug 5343.
3366 o Major bugfixes (on Tor 0.2.3.x):
3367 - Avoid an assert when managed proxies like obfsproxy are configured,
3368 and we receive HUP signals or setconf attempts too rapidly. This
3369 situation happens most commonly when Vidalia tries to attach to
3370 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
3371 bugfix on 0.2.3.6-alpha.
3372 - Fix a relay-side pluggable transports bug where managed proxies were
3373 unreachable from the Internet, because Tor asked them to bind on
3374 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
3375 - Stop discarding command-line arguments when TestingTorNetwork
3376 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
3377 0.2.3.9-alpha, where task 4552 added support for two layers of
3379 - Resume allowing the unit tests to run in gdb. This was accidentally
3380 made impossible when the DisableDebuggerAttachment option was
3381 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
3382 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
3383 0.2.3.11-alpha. Reported by Anthony G. Basile.
3385 o Minor bugfixes (on 0.2.2.x and earlier):
3386 - Ensure we don't cannibalize circuits that are longer than three hops
3387 already, so we don't end up making circuits with 5 or more
3388 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
3389 0.1.0.1-rc which introduced cannibalization.
3390 - Detect and reject certain misformed escape sequences in
3391 configuration values. Previously, these values would cause us
3392 to crash if received in a torrc file or over an authenticated
3393 control port. Bug found by Esteban Manchado Velázquez, and
3394 independently by Robert Connolly from Matta Consulting who further
3395 noted that it allows a post-authentication heap overflow. Patch
3396 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
3397 bugfix on 0.2.0.16-alpha.
3398 - Fix a compile warning when using the --enable-openbsd-malloc
3399 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
3400 - Directory caches no longer refuse to clean out descriptors because
3401 of missing v2 networkstatus documents, unless they're configured
3402 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
3403 0.2.2.26-beta. Patch by Daniel Bryg.
3404 - Update to the latest version of the tinytest unit testing framework.
3405 This includes a couple of bugfixes that can be relevant for
3406 running forked unit tests on Windows, and removes all reserved
3409 o Minor bugfixes (on 0.2.3.x):
3410 - On a failed pipe() call, don't leak file descriptors. Fixes bug
3411 4296; bugfix on 0.2.3.1-alpha.
3412 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
3413 until after we have received a CERTS cell. Fixes bug 4361; bugfix
3414 on 0.2.3.6-alpha. Patch by "frosty".
3415 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
3416 option, so that the IP stack doesn't decide to use it for IPv4
3417 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
3418 - Ensure that variables set in Tor's environment cannot override
3419 environment variables that Tor passes to a managed
3420 pluggable-transport proxy. Previously, Tor would pass every
3421 variable in its environment to managed proxies along with the new
3422 ones, in such a way that on many operating systems, the inherited
3423 environment variables would override those which Tor tried to
3424 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
3425 bugfix on 0.2.3.9-alpha for Windows.
3428 - A wide variety of new unit tests by Esteban Manchado Velázquez.
3429 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
3430 - Update to the March 6 2012 Maxmind GeoLite Country database.
3433 Changes in version 0.2.3.12-alpha - 2012-02-13
3434 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
3435 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
3436 when Tor is configured to use a pluggable transport like obfsproxy.
3439 - Fix builds when the path to sed, openssl, or sha1sum contains
3440 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
3442 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
3443 connections. This change should allow busy exit relays to stop
3444 running out of available sockets as quickly. Fixes bug 4950;
3445 bugfix on 0.2.2.26-beta.
3446 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
3447 would ask the bridge for microdescriptors, which are only supported
3448 in 0.2.3.x, and then fail to bootstrap when it didn't get the
3449 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
3450 - Properly set up obfsproxy's environment when in managed mode. The
3451 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
3452 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
3453 5076 and 5082; bugfix on 0.2.3.6-alpha.
3456 - Use the dead_strip option when building Tor on OS X. This reduces
3457 binary size by almost 19% when linking openssl and libevent
3458 statically, which we do for Tor Browser Bundle.
3459 - Fix broken URLs in the sample torrc file, and tell readers about
3460 the OutboundBindAddress, ExitPolicyRejectPrivate, and
3461 PublishServerDescriptor options. Addresses bug 4652.
3462 - Update to the February 7 2012 Maxmind GeoLite Country database.
3465 - Downgrade the "We're missing a certificate" message from notice
3466 to info: people kept mistaking it for a real problem, whereas it
3467 is seldom the problem even when we are failing to bootstrap. Fixes
3468 bug 5067; bugfix on 0.2.0.10-alpha.
3469 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
3470 managed pluggable transport server proxy's environment.
3471 Previously, we would put it there, even though Tor doesn't
3472 implement an 'extended server port' yet, and even though Tor
3473 almost certainly isn't listening at that address. For now, we set
3474 it to an empty string to avoid crashing older obfsproxies. Bugfix
3476 - Log the heartbeat message every HeartbeatPeriod seconds, not every
3477 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
3478 0.2.3.1-alpha. Bug reported by Scott Bennett.
3479 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
3480 bugfix on 0.2.3.11-alpha.
3481 - Update "ClientOnly" man page entry to explain that there isn't
3482 really any point to messing with it. Resolves ticket 5005.
3483 - Use the correct CVE number for CVE-2011-4576 in our comments and
3484 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
3487 o Code simplifications and refactoring:
3488 - Use the _WIN32 macro throughout our code to detect Windows.
3489 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
3493 Changes in version 0.2.3.11-alpha - 2012-01-22
3494 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
3495 the last step of the plan to limit maximum circuit length, includes
3496 a wide variety of hidden service performance and correctness fixes,
3497 works around an OpenSSL security flaw if your distro is too stubborn
3498 to upgrade, and fixes a bunch of smaller issues.
3501 - Now that Tor 0.2.0.x is completely deprecated, enable the final
3502 part of "Proposal 110: Avoiding infinite length circuits" by
3503 refusing all circuit-extend requests that do not use a relay_early
3504 cell. This change helps Tor resist a class of denial-of-service
3505 attacks by limiting the maximum circuit length.
3506 - Adjust the number of introduction points that a hidden service
3507 will try to maintain based on how long its introduction points
3508 remain in use and how many introductions they handle. Fixes
3510 - Try to use system facilities for enumerating local interface
3511 addresses, before falling back to our old approach (which was
3512 binding a UDP socket, and calling getsockname() on it). That
3513 approach was scaring OS X users whose draconian firewall
3514 software warned about binding to UDP sockets, regardless of
3515 whether packets were sent. Now we try to use getifaddrs(),
3516 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
3517 system supports. Resolves ticket 1827.
3519 o Major security workaround:
3520 - When building or running with any version of OpenSSL earlier
3521 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
3522 versions have a bug (CVE-2011-4576) in which their block cipher
3523 padding includes uninitialized data, potentially leaking sensitive
3524 information to any peer with whom they make a SSLv3 connection. Tor
3525 does not use SSL v3 by default, but a hostile client or server
3526 could force an SSLv3 connection in order to gain information that
3527 they shouldn't have been able to get. The best solution here is to
3528 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
3529 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
3530 to make sure that the bug can't happen.
3533 - Fix the SOCKET_OK test that we use to tell when socket
3534 creation fails so that it works on Win64. Fixes part of bug 4533;
3535 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
3536 - Correct our replacements for the timeradd() and timersub() functions
3537 on platforms that lack them (for example, Windows). The timersub()
3538 function is used when expiring circuits, while timeradd() is
3539 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
3540 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
3541 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
3542 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
3543 bug at runtime, not compile time, because some distributions hack
3544 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
3545 on 0.2.3.9-alpha. Found by Pascal.
3547 o Minor features (controller):
3548 - Use absolute path names when reporting the torrc filename in the
3549 control protocol, so a controller can more easily find the torrc
3550 file. Resolves bug 1101.
3551 - Extend the control protocol to report flags that control a circuit's
3552 path selection in CIRC events and in replies to 'GETINFO
3553 circuit-status'. Implements part of ticket 2411.
3554 - Extend the control protocol to report the hidden service address
3555 and current state of a hidden-service-related circuit in CIRC
3556 events and in replies to 'GETINFO circuit-status'. Implements part
3558 - When reporting the path to the cookie file to the controller,
3559 give an absolute path. Resolves ticket 4881.
3560 - Allow controllers to request an event notification whenever a
3561 circuit is cannibalized or its purpose is changed. Implements
3562 part of ticket 3457.
3563 - Include the creation time of a circuit in CIRC and CIRC2
3564 control-port events and the list produced by the 'GETINFO
3565 circuit-status' control-port command.
3567 o Minor features (directory authorities):
3568 - Directory authorities now reject versions of Tor older than
3569 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
3570 inclusive. These versions accounted for only a small fraction of
3571 the Tor network, and have numerous known security issues. Resolves
3573 - Authority operators can now vote for all relays in a given
3574 set of countries to be BadDir/BadExit/Invalid/Rejected.
3575 - Provide two consensus parameters (FastFlagMinThreshold and
3576 FastFlagMaxThreshold) to control the range of allowable bandwidths
3577 for the Fast directory flag. These allow authorities to run
3578 experiments on appropriate requirements for being a "Fast" node.
3579 The AuthDirFastGuarantee config value still applies. Implements
3581 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
3582 directory authority option (introduced in Tor 0.2.2.34).
3584 o Minor features (other):
3585 - Don't disable the DirPort when we cannot exceed our AccountingMax
3586 limit during this interval because the effective bandwidthrate is
3587 low enough. This is useful in a situation where AccountMax is only
3588 used as an additional safeguard or to provide statistics.
3589 - Prepend an informative header to generated dynamic_dh_params files.
3590 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
3591 EntryNodes will have no effect. Resolves issue 2571.
3592 - Log more useful messages when we fail to disable debugger
3594 - Log which authority we're missing votes from when we go to fetch
3595 them from the other auths.
3596 - Log (at debug level) whenever a circuit's purpose is changed.
3597 - Add missing documentation for the MaxClientCircuitsPending,
3598 UseMicrodescriptors, UserspaceIOCPBuffers, and
3599 _UseFilteringSSLBufferevents options, all introduced during
3601 - Update to the January 3 2012 Maxmind GeoLite Country database.
3603 o Minor bugfixes (hidden services):
3604 - Don't close hidden service client circuits which have almost
3605 finished connecting to their destination when they reach
3606 the normal circuit-build timeout. Previously, we would close
3607 introduction circuits which are waiting for an acknowledgement
3608 from the introduction point, and rendezvous circuits which have
3609 been specified in an INTRODUCE1 cell sent to a hidden service,
3610 after the normal CBT. Now, we mark them as 'timed out', and launch
3611 another rendezvous attempt in parallel. This behavior change can
3612 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
3613 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
3614 - Don't close hidden-service-side rendezvous circuits when they
3615 reach the normal circuit-build timeout. This behaviour change can
3616 be disabled using the new
3617 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
3618 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
3619 - Make sure we never mark the wrong rendezvous circuit as having
3620 had its introduction cell acknowleged by the introduction-point
3621 relay. Previously, when we received an INTRODUCE_ACK cell on a
3622 client-side hidden-service introduction circuit, we might have
3623 marked a rendezvous circuit other than the one we specified in
3624 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
3625 a warning message and interfered with the hidden service
3626 connection-establishment process. Fixes bug 4759; bugfix on
3627 0.2.3.3-alpha, when we added the stream-isolation feature which
3628 might cause Tor to open multiple rendezvous circuits for the same
3630 - Don't trigger an assertion failure when we mark a new client-side
3631 hidden-service introduction circuit for close during the process
3632 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
3635 o Minor bugfixes (log messages):
3636 - Correctly spell "connect" in a log message on failure to create a
3637 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
3639 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
3640 Fixes bug 4856; bugfix on Tor 0.0.6.
3641 - Fix the log message describing how we work around discovering
3642 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
3643 4837; bugfix on 0.2.2.9-alpha.
3644 - When logging about a disallowed .exit name, do not also call it
3645 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
3647 o Minor bugfixes (build fixes):
3648 - During configure, detect when we're building with clang version
3649 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
3650 CFLAGS. clang doesn't support them yet.
3651 - During configure, search for library containing cos function as
3652 libm lives in libcore on some platforms (BeOS/Haiku). Linking
3653 against libm was hard-coded before. Fixes the first part of bug
3654 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
3656 - Detect attempts to build Tor on (as yet hypothetical) versions
3657 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
3658 fix for bug 4533. Bugfix on 0.2.2.28-beta.
3659 - Preprocessor directives should not be put inside the arguments
3660 of a macro. This would break compilation with GCC releases prior
3661 to version 3.3. We would never recommend such an old GCC version,
3662 but it is apparently required for binary compatibility on some
3663 platforms (namely, certain builds of Haiku). Fixes the other part
3664 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
3667 o Minor bugfixes (other):
3668 - Older Linux kernels erroneously respond to strange nmap behavior
3669 by having accept() return successfully with a zero-length
3670 socket. When this happens, just close the connection. Previously,
3671 we would try harder to learn the remote address: but there was
3672 no such remote address to learn, and our method for trying to
3673 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
3674 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
3675 - Fix null-pointer access that could occur if TLS allocation failed.
3676 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
3677 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
3678 accidentally been reverted.
3679 - Fix our implementation of crypto_random_hostname() so it can't
3680 overflow on ridiculously large inputs. (No Tor version has ever
3681 provided this kind of bad inputs, but let's be correct in depth.)
3682 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
3683 - Find more places in the code that should have been testing for
3684 invalid sockets using the SOCKET_OK macro. Required for a fix
3685 for bug 4533. Bugfix on 0.2.2.28-beta.
3686 - Fix an assertion failure when, while running with bufferevents, a
3687 connection finishes connecting after it is marked for close, but
3688 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
3689 - test_util_spawn_background_ok() hardcoded the expected value
3690 for ENOENT to 2. This isn't portable as error numbers are
3691 platform specific, and particularly the hurd has ENOENT at
3692 0x40000002. Construct expected string at runtime, using the correct
3693 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
3694 - Reject attempts to disable DisableDebuggerAttachment while Tor is
3695 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
3696 - Use an appropriate-width type for sockets in tor-fw-helper on
3697 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
3700 - When sending or relaying a RELAY_EARLY cell, we used to convert
3701 it to a RELAY cell if the connection was using the v1 link
3702 protocol. This was a workaround for older versions of Tor, which
3703 didn't handle RELAY_EARLY cells properly. Now that all supported
3704 versions can handle RELAY_EARLY cells, and now that we're enforcing
3705 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
3706 remove this workaround. Addresses bug 4786.
3708 o Code simplifications and refactoring:
3709 - Use OpenSSL's built-in SSL_state_string_long() instead of our
3710 own homebrewed ssl_state_to_string() replacement. Patch from
3711 Emile Snyder. Fixes bug 4653.
3712 - Use macros to indicate OpenSSL versions, so we don't need to worry
3713 about accidental hexadecimal bit shifts.
3714 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
3716 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
3717 - Use the smartlist_add_asprintf() alias more consistently.
3718 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
3719 invalid value, rather than just -1.
3720 - Rename a handful of old identifiers, mostly related to crypto
3721 structures and crypto functions. By convention, our "create an
3722 object" functions are called "type_new()", our "free an object"
3723 functions are called "type_free()", and our types indicate that
3724 they are types only with a final "_t". But a handful of older
3725 types and functions broke these rules, with function names like
3726 "type_create" or "subsystem_op_type", or with type names like
3730 Changes in version 0.2.3.10-alpha - 2011-12-16
3731 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
3732 Tor's buffers code. Absolutely everybody should upgrade.
3734 The bug relied on an incorrect calculation when making data continuous
3735 in one of our IO buffers, if the first chunk of the buffer was
3736 misaligned by just the wrong amount. The miscalculation would allow an
3737 attacker to overflow a piece of heap-allocated memory. To mount this
3738 attack, the attacker would need to either open a SOCKS connection to
3739 Tor's SocksPort (usually restricted to localhost), or target a Tor
3740 instance configured to make its connections through a SOCKS proxy
3741 (which Tor does not do by default).
3743 Good security practice requires that all heap-overflow bugs should be
3744 presumed to be exploitable until proven otherwise, so we are treating
3745 this as a potential code execution attack. Please upgrade immediately!
3746 This bug does not affect bufferevents-based builds of Tor. Special
3747 thanks to "Vektor" for reporting this issue to us!
3749 This release also contains a few minor bugfixes for issues discovered
3753 - Fix a heap overflow bug that could occur when trying to pull
3754 data into the first chunk of a buffer, when that chunk had
3755 already had some data drained from it. Fixes CVE-2011-2778;
3756 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3759 - If we can't attach streams to a rendezvous circuit when we
3760 finish connecting to a hidden service, clear the rendezvous
3761 circuit's stream-isolation state and try to attach streams
3762 again. Previously, we cleared rendezvous circuits' isolation
3763 state either too early (if they were freshly built) or not at all
3764 (if they had been built earlier and were cannibalized). Bugfix on
3765 0.2.3.3-alpha; fixes bug 4655.
3766 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
3767 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
3768 - Fix an assertion failure when a relay with accounting enabled
3769 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
3772 - Update to the December 6 2011 Maxmind GeoLite Country database.
3775 Changes in version 0.2.2.35 - 2011-12-16
3776 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
3777 buffers code. Absolutely everybody should upgrade.
3779 The bug relied on an incorrect calculation when making data continuous
3780 in one of our IO buffers, if the first chunk of the buffer was
3781 misaligned by just the wrong amount. The miscalculation would allow an
3782 attacker to overflow a piece of heap-allocated memory. To mount this
3783 attack, the attacker would need to either open a SOCKS connection to
3784 Tor's SocksPort (usually restricted to localhost), or target a Tor
3785 instance configured to make its connections through a SOCKS proxy
3786 (which Tor does not do by default).
3788 Good security practice requires that all heap-overflow bugs should be
3789 presumed to be exploitable until proven otherwise, so we are treating
3790 this as a potential code execution attack. Please upgrade immediately!
3791 This bug does not affect bufferevents-based builds of Tor. Special
3792 thanks to "Vektor" for reporting this issue to us!
3794 Tor 0.2.2.35 also fixes several bugs in previous versions, including
3795 crash bugs for unusual configurations, and a long-term bug that
3796 would prevent Tor from starting on Windows machines with draconian
3799 With this release, we remind everyone that 0.2.0.x has reached its
3800 formal end-of-life. Those Tor versions have many known flaws, and
3801 nobody should be using them. You should upgrade -- ideally to the
3802 0.2.2.x series. If you're using a Linux or BSD and its packages are
3803 obsolete, stop using those packages and upgrade anyway.
3805 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
3806 longer receive support after some time in early 2012.
3809 - Fix a heap overflow bug that could occur when trying to pull
3810 data into the first chunk of a buffer, when that chunk had
3811 already had some data drained from it. Fixes CVE-2011-2778;
3812 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3813 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3814 that it doesn't attempt to allocate a socketpair. This could cause
3815 some problems on Windows systems with overzealous firewalls. Fix for
3816 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3818 - If we mark an OR connection for close based on a cell we process,
3819 don't process any further cells on it. We already avoid further
3820 reads on marked-for-close connections, but now we also discard the
3821 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3822 which was the first version where we might mark a connection for
3823 close based on processing a cell on it.
3824 - Correctly sanity-check that we don't underflow on a memory
3825 allocation (and then assert) for hidden service introduction
3826 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3827 bugfix on 0.2.1.5-alpha.
3828 - Fix a memory leak when we check whether a hidden service
3829 descriptor has any usable introduction points left. Fixes bug
3830 4424. Bugfix on 0.2.2.25-alpha.
3831 - Don't crash when we're running as a relay and don't have a GeoIP
3832 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
3833 we've had in the 0.2.3.x branch already.
3834 - When running as a client, do not print a misleading (and plain
3835 wrong) log message that we're collecting "directory request"
3836 statistics: clients don't collect statistics. Also don't create a
3837 useless (because empty) stats file in the stats/ directory. Fixes
3838 bug 4353; bugfix on 0.2.2.34.
3841 - Detect failure to initialize Libevent. This fix provides better
3842 detection for future instances of bug 4457.
3843 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3844 function. This was eating up hideously large amounts of time on some
3845 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3846 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3847 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3849 - Don't warn about unused log_mutex in log.c when building with
3850 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3851 0.1.0.6-rc which introduced --disable-threads.
3852 - When configuring, starting, or stopping an NT service, stop
3853 immediately after the service configuration attempt has succeeded
3854 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3855 - When sending a NETINFO cell, include the original address
3856 received for the other side, not its canonical address. Found
3857 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3858 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
3859 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3860 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3861 occurred when a client tried to fetch a descriptor for a bridge
3862 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3863 - Backport fixes for a pair of compilation warnings on Windows.
3864 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
3865 - If we had ever tried to call tor_addr_to_str on an address of
3866 unknown type, we would have done a strdup on an uninitialized
3867 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3868 Reported by "troll_un".
3869 - Correctly detect and handle transient lookup failures from
3870 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3871 Reported by "troll_un".
3872 - Fix null-pointer access that could occur if TLS allocation failed.
3873 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3874 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3875 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3878 - Add two new config options for directory authorities:
3879 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3880 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3881 that is always sufficient to satisfy the bandwidth requirement for
3882 the Guard flag. Now it will be easier for researchers to simulate
3883 Tor networks with different values. Resolves ticket 4484.
3884 - When Tor ignores a hidden service specified in its configuration,
3885 include the hidden service's directory in the warning message.
3886 Previously, we would only tell the user that some hidden service
3887 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3888 - Update to the December 6 2011 Maxmind GeoLite Country database.
3890 o Packaging changes:
3891 - Make it easier to automate expert package builds on Windows,
3892 by removing an absolute path from makensis.exe command.
3895 Changes in version 0.2.1.32 - 2011-12-16
3896 Tor 0.2.1.32 backports important security and privacy fixes for
3897 oldstable. This release is intended only for package maintainers and
3898 others who cannot use the 0.2.2 stable series. All others should be
3899 using Tor 0.2.2.x or newer.
3901 The Tor 0.2.1.x series will reach formal end-of-life some time in
3902 early 2012; we will stop releasing patches for it then.
3904 o Major bugfixes (also included in 0.2.2.x):
3905 - Correctly sanity-check that we don't underflow on a memory
3906 allocation (and then assert) for hidden service introduction
3907 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3908 bugfix on 0.2.1.5-alpha.
3909 - Fix a heap overflow bug that could occur when trying to pull
3910 data into the first chunk of a buffer, when that chunk had
3911 already had some data drained from it. Fixes CVE-2011-2778;
3912 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3915 - Update to the December 6 2011 Maxmind GeoLite Country database.
3918 Changes in version 0.2.3.9-alpha - 2011-12-08
3919 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
3920 a "DisableNetwork" security feature that bundles can use to avoid
3921 touching the network until bridges are configured, moves forward on
3922 the pluggable transport design, fixes a flaw in the hidden service
3923 design that unnecessarily prevented clients with wrong clocks from
3924 reaching hidden services, and fixes a wide variety of other issues.
3927 - Clients can now connect to private bridges over IPv6. Bridges
3928 still need at least one IPv4 address in order to connect to
3929 other relays. Note that we don't yet handle the case where the
3930 user has two bridge lines for the same bridge (one IPv4, one
3931 IPv6). Implements parts of proposal 186.
3932 - New "DisableNetwork" config option to prevent Tor from launching any
3933 connections or accepting any connections except on a control port.
3934 Bundles and controllers can set this option before letting Tor talk
3935 to the rest of the network, for example to prevent any connections
3936 to a non-bridge address. Packages like Orbot can also use this
3937 option to instruct Tor to save power when the network is off.
3938 - Clients and bridges can now be configured to use a separate
3939 "transport" proxy. This approach makes the censorship arms race
3940 easier by allowing bridges to use protocol obfuscation plugins. It
3941 implements the "managed proxy" part of proposal 180 (ticket 3472).
3942 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
3943 implementation. It makes AES_CTR about 7% faster than our old one
3944 (which was about 10% faster than the one OpenSSL used to provide).
3945 Resolves ticket 4526.
3946 - Add a "tor2web mode" for clients that want to connect to hidden
3947 services non-anonymously (and possibly more quickly). As a safety
3948 measure to try to keep users from turning this on without knowing
3949 what they are doing, tor2web mode must be explicitly enabled at
3950 compile time, and a copy of Tor compiled to run in tor2web mode
3951 cannot be used as a normal Tor client. Implements feature 2553.
3952 - Add experimental support for running on Windows with IOCP and no
3953 kernel-space socket buffers. This feature is controlled by a new
3954 "UserspaceIOCPBuffers" config option (off by default), which has
3955 no effect unless Tor has been built with support for bufferevents,
3956 is running on Windows, and has enabled IOCP. This may, in the long
3957 run, help solve or mitigate bug 98.
3958 - Use a more secure consensus parameter voting algorithm. Now at
3959 least three directory authorities or a majority of them must
3960 vote on a given parameter before it will be included in the
3961 consensus. Implements proposal 178.
3964 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
3965 They used to check that the timestamp was within 30 minutes
3966 of their system clock, so they could cap the size of their
3967 replay-detection cache, but that approach unnecessarily refused
3968 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
3969 the v3 intro-point protocol (the first one which sent a timestamp
3970 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
3971 - Only use the EVP interface when AES acceleration is enabled,
3972 to avoid a 5-7% performance regression. Resolves issue 4525;
3973 bugfix on 0.2.3.8-alpha.
3975 o Privacy/anonymity features (bridge detection):
3976 - Make bridge SSL certificates a bit more stealthy by using random
3977 serial numbers, in the same fashion as OpenSSL when generating
3978 self-signed certificates. Implements ticket 4584.
3979 - Introduce a new config option "DynamicDHGroups", enabled by
3980 default, which provides each bridge with a unique prime DH modulus
3981 to be used during SSL handshakes. This option attempts to help
3982 against censors who might use the Apache DH modulus as a static
3983 identifier for bridges. Addresses ticket 4548.
3985 o Minor features (new/different config options):
3986 - New configuration option "DisableDebuggerAttachment" (on by default)
3987 to prevent basic debugging attachment attempts by other processes.
3988 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
3989 - Allow MapAddress directives to specify matches against super-domains,
3990 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
3991 Implements issue 933.
3992 - Slightly change behavior of "list" options (that is, config
3993 options that can appear more than once) when they appear both in
3994 torrc and on the command line. Previously, the command-line options
3995 would be appended to the ones from torrc. Now, the command-line
3996 options override the torrc options entirely. This new behavior
3997 allows the user to override list options (like exit policies and
3998 ports to listen on) from the command line, rather than simply
3999 appending to the list.
4000 - You can get the old (appending) command-line behavior for "list"
4001 options by prefixing the option name with a "+".
4002 - You can remove all the values for a "list" option from the command
4003 line without adding any new ones by prefixing the option name
4005 - Add experimental support for a "defaults" torrc file to be parsed
4006 before the regular torrc. Torrc options override the defaults file's
4007 options in the same way that the command line overrides the torrc.
4008 The SAVECONF controller command saves only those options which
4009 differ between the current configuration and the defaults file. HUP
4010 reloads both files. (Note: This is an experimental feature; its
4011 behavior will probably be refined in future 0.2.3.x-alpha versions
4012 to better meet packagers' needs.) Implements task 4552.
4015 - Try to make the introductory warning message that Tor prints on
4016 startup more useful for actually finding help and information.
4017 Resolves ticket 2474.
4018 - Running "make version" now displays the version of Tor that
4019 we're about to build. Idea from katmagic; resolves issue 4400.
4020 - Expire old or over-used hidden service introduction points.
4021 Required by fix for bug 3460.
4022 - Move the replay-detection cache for the RSA-encrypted parts of
4023 INTRODUCE2 cells to the introduction point data structures.
4024 Previously, we would use one replay-detection cache per hidden
4025 service. Required by fix for bug 3460.
4026 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
4027 public key replay-detection cache from 60 minutes to 5 minutes. This
4028 replay-detection cache is now used only to detect multiple
4029 INTRODUCE2 cells specifying the same rendezvous point, so we can
4030 avoid launching multiple simultaneous attempts to connect to it.
4032 o Minor bugfixes (on Tor 0.2.2.x and earlier):
4033 - Resolve an integer overflow bug in smartlist_ensure_capacity().
4034 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
4036 - Fix a minor formatting issue in one of tor-gencert's error messages.
4038 - Prevent a false positive from the check-spaces script, by disabling
4039 the "whitespace between function name and (" check for functions
4041 - Fix a log message suggesting that people contact a non-existent
4042 email address. Fixes bug 3448.
4043 - Fix null-pointer access that could occur if TLS allocation failed.
4044 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
4045 - Report a real bootstrap problem to the controller on router
4046 identity mismatch. Previously we just said "foo", which probably
4047 made a lot of sense at the time. Fixes bug 4169; bugfix on
4049 - If we had ever tried to call tor_addr_to_str() on an address of
4050 unknown type, we would have done a strdup() on an uninitialized
4051 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
4052 Reported by "troll_un".
4053 - Correctly detect and handle transient lookup failures from
4054 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
4055 Reported by "troll_un".
4056 - Use tor_socket_t type for listener argument to accept(). Fixes bug
4057 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
4058 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
4059 bug 4532; found by "troll_un".
4061 o Minor bugfixes (on Tor 0.2.3.x):
4062 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
4064 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
4065 circuit for use as a hidden service client's rendezvous point.
4066 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
4067 with help from wanoskarnet.
4068 - Restore behavior of overriding SocksPort, ORPort, and similar
4069 options from the command line. Bugfix on 0.2.3.3-alpha.
4072 - Properly handle the case where the build-tree is not the same
4073 as the source tree when generating src/common/common_sha1.i,
4074 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
4075 bugfix on 0.2.0.1-alpha.
4077 o Code simplifications, cleanups, and refactorings:
4078 - Remove the pure attribute from all functions that used it
4079 previously. In many cases we assigned it incorrectly, because the
4080 functions might assert or call impure functions, and we don't have
4081 evidence that keeping the pure attribute is worthwhile. Implements
4082 changes suggested in ticket 4421.
4083 - Remove some dead code spotted by coverity. Fixes cid 432.
4084 Bugfix on 0.2.3.1-alpha, closes bug 4637.
4087 Changes in version 0.2.3.8-alpha - 2011-11-22
4088 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
4089 socketpair-related bug that has been bothering Windows users. It adds
4090 support to serve microdescriptors to controllers, so Vidalia's network
4091 map can resume listing relays (once Vidalia implements its side),
4092 and adds better support for hardware AES acceleration. Finally, it
4093 starts the process of adjusting the bandwidth cutoff for getting the
4094 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
4095 that tiny relays harm performance more than they help network capacity.
4098 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
4099 that it doesn't attempt to allocate a socketpair. This could cause
4100 some problems on Windows systems with overzealous firewalls. Fix for
4101 bug 4457; workaround for Libevent versions 2.0.1-alpha through
4103 - Correctly sanity-check that we don't underflow on a memory
4104 allocation (and then assert) for hidden service introduction
4105 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
4106 bugfix on 0.2.1.5-alpha.
4107 - Remove the artificially low cutoff of 20KB to guarantee the Fast
4108 flag. In the past few years the average relay speed has picked
4109 up, and while the "top 7/8 of the network get the Fast flag" and
4110 "all relays with 20KB or more of capacity get the Fast flag" rules
4111 used to have the same result, now the top 7/8 of the network has
4112 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
4113 - Fix a rare assertion failure when checking whether a v0 hidden
4114 service descriptor has any usable introduction points left, and
4115 we don't have enough information to build a circuit to the first
4116 intro point named in the descriptor. The HS client code in
4117 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
4118 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
4119 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
4120 - Make bridge authorities not crash when they are asked for their own
4121 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
4122 - When running as a client, do not print a misleading (and plain
4123 wrong) log message that we're collecting "directory request"
4124 statistics: clients don't collect statistics. Also don't create a
4125 useless (because empty) stats file in the stats/ directory. Fixes
4126 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
4129 - Allow Tor controllers like Vidalia to obtain the microdescriptor
4130 for a relay by identity digest or nickname. Previously,
4131 microdescriptors were only available by their own digests, so a
4132 controller would have to ask for and parse the whole microdescriptor
4133 consensus in order to look up a single relay's microdesc. Fixes
4134 bug 3832; bugfix on 0.2.3.1-alpha.
4135 - Use OpenSSL's EVP interface for AES encryption, so that all AES
4136 operations can use hardware acceleration (if present). Resolves
4139 o Minor bugfixes (on 0.2.2.x and earlier):
4140 - Detect failure to initialize Libevent. This fix provides better
4141 detection for future instances of bug 4457.
4142 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
4143 function. This was eating up hideously large amounts of time on some
4144 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
4145 - Don't warn about unused log_mutex in log.c when building with
4146 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
4147 0.1.0.6-rc which introduced --disable-threads.
4148 - Allow manual 'authenticate' commands to the controller interface
4149 from netcat (nc) as well as telnet. We were rejecting them because
4150 they didn't come with the expected whitespace at the end of the
4151 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
4152 - Fix some (not actually triggerable) buffer size checks in usage of
4153 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
4155 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
4156 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
4157 - When configuring, starting, or stopping an NT service, stop
4158 immediately after the service configuration attempt has succeeded
4159 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
4160 - When sending a NETINFO cell, include the original address
4161 received for the other side, not its canonical address. Found
4162 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
4163 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
4164 can pick them up when the tests aren't disabled. Bugfix on
4165 0.2.2.4-alpha which introduced tinytest.
4166 - Fix a memory leak when we check whether a hidden service
4167 descriptor has any usable introduction points left. Fixes bug
4168 4424. Bugfix on 0.2.2.25-alpha.
4169 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
4170 occurred when a client tried to fetch a descriptor for a bridge
4171 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
4173 o Minor bugfixes (on 0.2.3.x):
4174 - Make util unit tests build correctly with MSVC. Bugfix on
4175 0.2.3.3-alpha. Patch by Gisle Vanem.
4176 - Successfully detect AUTH_CHALLENGE cells with no recognized
4177 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
4179 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
4180 it should still send a NETINFO cell to allow the connection to
4181 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
4183 - Log less loudly when we get an invalid authentication certificate
4184 from a source other than a directory authority: it's not unusual
4185 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
4187 - Tolerate servers with more clock skew in their authentication
4188 certificates than previously. Fixes bug 4371; bugfix on
4190 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
4191 on 0.2.3.4-alpha and 0.2.3.6-alpha.
4194 - Add two new config options for directory authorities:
4195 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
4196 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
4197 that is always sufficient to satisfy the bandwidth requirement for
4198 the Guard flag. Now it will be easier for researchers to simulate
4199 Tor networks with different values. Resolves ticket 4484.
4200 - When Tor ignores a hidden service specified in its configuration,
4201 include the hidden service's directory in the warning message.
4202 Previously, we would only tell the user that some hidden service
4203 was ignored. Bugfix on 0.0.6; fixes bug 4426.
4204 - When we fail to initialize Libevent, retry with IOCP disabled so we
4205 don't need to turn on multi-threading support in Libevent, which in
4206 turn requires a working socketpair(). This is a workaround for bug
4207 4457, which affects Libevent versions from 2.0.1-alpha through
4209 - Detect when we try to build on a platform that doesn't define
4210 AF_UNSPEC to 0. We don't work there, so refuse to compile.
4211 - Update to the November 1 2011 Maxmind GeoLite Country database.
4213 o Packaging changes:
4214 - Make it easier to automate expert package builds on Windows,
4215 by removing an absolute path from makensis.exe command.
4217 o Code simplifications and refactoring:
4218 - Remove some redundant #include directives throughout the code.
4219 Patch from Andrea Gelmini.
4220 - Unconditionally use OpenSSL's AES implementation instead of our
4221 old built-in one. OpenSSL's AES has been better for a while, and
4222 relatively few servers should still be on any version of OpenSSL
4223 that doesn't have good optimized assembly AES.
4224 - Use the name "CERTS" consistently to refer to the new cell type;
4225 we were calling it CERT in some places and CERTS in others.
4228 - Numerous new unit tests for functions in util.c and address.c by
4230 - The long-disabled benchmark tests are now split into their own
4231 ./src/test/bench binary.
4232 - The benchmark tests can now use more accurate timers than
4233 gettimeofday() when such timers are available.
4236 Changes in version 0.2.3.7-alpha - 2011-10-30
4237 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
4238 the new v3 handshake. It also resolves yet another bridge address
4242 - If we mark an OR connection for close based on a cell we process,
4243 don't process any further cells on it. We already avoid further
4244 reads on marked-for-close connections, but now we also discard the
4245 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
4246 which was the first version where we might mark a connection for
4247 close based on processing a cell on it.
4248 - Fix a double-free bug that would occur when we received an invalid
4249 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
4250 bugfix on 0.2.3.6-alpha.
4251 - Bridges no longer include their address in NETINFO cells on outgoing
4252 OR connections, to allow them to blend in better with clients.
4253 Removes another avenue for enumerating bridges. Reported by
4254 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
4255 cells were introduced.
4258 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
4259 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
4262 Changes in version 0.2.3.6-alpha - 2011-10-26
4263 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
4264 anonymity vulnerability where an attacker can deanonymize Tor
4265 users. Everybody should upgrade.
4267 This release also features support for a new v3 connection handshake
4268 protocol, and fixes to make hidden service connections more robust.
4271 - Implement a new handshake protocol (v3) for authenticating Tors to
4272 each other over TLS. It should be more resistant to fingerprinting
4273 than previous protocols, and should require less TLS hacking for
4274 future Tor implementations. Implements proposal 176.
4275 - Allow variable-length padding cells to disguise the length of
4276 Tor's TLS records. Implements part of proposal 184.
4278 o Privacy/anonymity fixes (clients):
4279 - Clients and bridges no longer send TLS certificate chains on
4280 outgoing OR connections. Previously, each client or bridge would
4281 use the same cert chain for all outgoing OR connections until
4282 its IP address changes, which allowed any relay that the client
4283 or bridge contacted to determine which entry guards it is using.
4284 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
4285 - If a relay receives a CREATE_FAST cell on a TLS connection, it
4286 no longer considers that connection as suitable for satisfying a
4287 circuit EXTEND request. Now relays can protect clients from the
4288 CVE-2011-2768 issue even if the clients haven't upgraded yet.
4289 - Directory authorities no longer assign the Guard flag to relays
4290 that haven't upgraded to the above "refuse EXTEND requests
4291 to client connections" fix. Now directory authorities can
4292 protect clients from the CVE-2011-2768 issue even if neither
4293 the clients nor the relays have upgraded yet. There's a new
4294 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
4295 to let us transition smoothly, else tomorrow there would be no
4298 o Major bugfixes (hidden services):
4299 - Improve hidden service robustness: when an attempt to connect to
4300 a hidden service ends, be willing to refetch its hidden service
4301 descriptors from each of the HSDir relays responsible for them
4302 immediately. Previously, we would not consider refetching the
4303 service's descriptors from each HSDir for 15 minutes after the last
4304 fetch, which was inconvenient if the hidden service was not running
4305 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
4306 - When one of a hidden service's introduction points appears to be
4307 unreachable, stop trying it. Previously, we would keep trying
4308 to build circuits to the introduction point until we lost the
4309 descriptor, usually because the user gave up and restarted Tor.
4310 Partly fixes bug 3825.
4311 - Don't launch a useless circuit after failing to use one of a
4312 hidden service's introduction points. Previously, we would
4313 launch a new introduction circuit, but not set the hidden service
4314 which that circuit was intended to connect to, so it would never
4315 actually be used. A different piece of code would then create a
4316 new introduction circuit correctly. Bug reported by katmagic and
4317 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
4319 o Major bugfixes (other):
4320 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
4321 that they initiated. Relays could distinguish incoming bridge
4322 connections from client connections, creating another avenue for
4323 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
4324 Found by "frosty_un".
4325 - Don't update the AccountingSoftLimitHitAt state file entry whenever
4326 tor gets started. This prevents a wrong average bandwidth
4327 estimate, which would cause relays to always start a new accounting
4328 interval at the earliest possible moment. Fixes bug 2003; bugfix
4329 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
4330 immensely in tracking this bug down.
4331 - Fix a crash bug when changing node restrictions while a DNS lookup
4332 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
4335 o Minor bugfixes (on 0.2.2.x and earlier):
4336 - When a hidden service turns an extra service-side introduction
4337 circuit into a general-purpose circuit, free the rend_data and
4338 intro_key fields first, so we won't leak memory if the circuit
4339 is cannibalized for use as another service-side introduction
4340 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
4341 - Rephrase the log message emitted if the TestSocks check is
4342 successful. Patch from Fabian Keil; fixes bug 4094.
4343 - Bridges now skip DNS self-tests, to act a little more stealthily.
4344 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
4345 bridges. Patch by "warms0x".
4346 - Remove a confusing dollar sign from the example fingerprint in the
4347 man page, and also make the example fingerprint a valid one. Fixes
4348 bug 4309; bugfix on 0.2.1.3-alpha.
4349 - Fix internal bug-checking logic that was supposed to catch
4350 failures in digest generation so that it will fail more robustly
4351 if we ask for a nonexistent algorithm. Found by Coverity Scan.
4352 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
4353 - Report any failure in init_keys() calls launched because our
4354 IP address has changed. Spotted by Coverity Scan. Bugfix on
4355 0.1.1.4-alpha; fixes CID 484.
4357 o Minor bugfixes (on 0.2.3.x):
4358 - Fix a bug in configure.in that kept it from building a configure
4359 script with autoconf versions earlier than 2.61. Fixes bug 2430;
4360 bugfix on 0.2.3.1-alpha.
4361 - Don't warn users that they are exposing a client port to the
4362 Internet if they have specified an RFC1918 address. Previously,
4363 we would warn if the user had specified any non-loopback
4364 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
4365 - Fix memory leaks in the failing cases of the new SocksPort and
4366 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
4367 fixes coverity CIDs 485, 486, and 487.
4370 - When a hidden service's introduction point times out, consider
4371 trying it again during the next attempt to connect to the
4372 HS. Previously, we would not try it again unless a newly fetched
4373 descriptor contained it. Required by fixes for bugs 1297 and 3825.
4374 - The next version of Windows will be called Windows 8, and it has
4375 a major version of 6, minor version of 2. Correctly identify that
4376 version instead of calling it "Very recent version". Resolves
4377 ticket 4153; reported by funkstar.
4378 - The Bridge Authority now writes statistics on how many bridge
4379 descriptors it gave out in total, and how many unique descriptors
4380 it gave out. It also lists how often the most and least commonly
4381 fetched descriptors were given out, as well as the median and
4382 25th/75th percentile. Implements tickets 4200 and 4294.
4383 - Update to the October 4 2011 Maxmind GeoLite Country database.
4385 o Code simplifications and refactoring:
4386 - Remove some old code to remember statistics about which descriptors
4387 we've served as a directory mirror. The feature wasn't used and
4388 is outdated now that microdescriptors are around.
4389 - Rename Tor functions that turn strings into addresses, so that
4390 "parse" indicates that no hostname resolution occurs, and
4391 "lookup" indicates that hostname resolution may occur. This
4392 should help prevent mistakes in the future. Fixes bug 3512.
4395 Changes in version 0.2.2.34 - 2011-10-26
4396 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
4397 can deanonymize Tor users. Everybody should upgrade.
4399 The attack relies on four components: 1) Clients reuse their TLS cert
4400 when talking to different relays, so relays can recognize a user by
4401 the identity key in her cert. 2) An attacker who knows the client's
4402 identity key can probe each guard relay to see if that identity key
4403 is connected to that guard relay right now. 3) A variety of active
4404 attacks in the literature (starting from "Low-Cost Traffic Analysis
4405 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
4406 discover the guard relays that a Tor user visiting the website is using.
4407 4) Clients typically pick three guards at random, so the set of guards
4408 for a given user could well be a unique fingerprint for her. This
4409 release fixes components #1 and #2, which is enough to block the attack;
4410 the other two remain as open research problems. Special thanks to
4411 "frosty_un" for reporting the issue to us!
4413 Clients should upgrade so they are no longer recognizable by the TLS
4414 certs they present. Relays should upgrade so they no longer allow a
4415 remote attacker to probe them to test whether unpatched clients are
4416 currently connected to them.
4418 This release also fixes several vulnerabilities that allow an attacker
4419 to enumerate bridge relays. Some bridge enumeration attacks still
4420 remain; see for example proposal 188.
4422 o Privacy/anonymity fixes (clients):
4423 - Clients and bridges no longer send TLS certificate chains on
4424 outgoing OR connections. Previously, each client or bridge would
4425 use the same cert chain for all outgoing OR connections until
4426 its IP address changes, which allowed any relay that the client
4427 or bridge contacted to determine which entry guards it is using.
4428 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
4429 - If a relay receives a CREATE_FAST cell on a TLS connection, it
4430 no longer considers that connection as suitable for satisfying a
4431 circuit EXTEND request. Now relays can protect clients from the
4432 CVE-2011-2768 issue even if the clients haven't upgraded yet.
4433 - Directory authorities no longer assign the Guard flag to relays
4434 that haven't upgraded to the above "refuse EXTEND requests
4435 to client connections" fix. Now directory authorities can
4436 protect clients from the CVE-2011-2768 issue even if neither
4437 the clients nor the relays have upgraded yet. There's a new
4438 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
4439 to let us transition smoothly, else tomorrow there would be no
4442 o Privacy/anonymity fixes (bridge enumeration):
4443 - Bridge relays now do their directory fetches inside Tor TLS
4444 connections, like all the other clients do, rather than connecting
4445 directly to the DirPort like public relays do. Removes another
4446 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
4447 - Bridges relays now build circuits for themselves in a more similar
4448 way to how clients build them. Removes another avenue for
4449 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
4450 when bridges were introduced.
4451 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
4452 that they initiated. Relays could distinguish incoming bridge
4453 connections from client connections, creating another avenue for
4454 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
4455 Found by "frosty_un".
4458 - Fix a crash bug when changing node restrictions while a DNS lookup
4459 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
4461 - Don't launch a useless circuit after failing to use one of a
4462 hidden service's introduction points. Previously, we would
4463 launch a new introduction circuit, but not set the hidden service
4464 which that circuit was intended to connect to, so it would never
4465 actually be used. A different piece of code would then create a
4466 new introduction circuit correctly. Bug reported by katmagic and
4467 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
4470 - Change an integer overflow check in the OpenBSD_Malloc code so
4471 that GCC is less likely to eliminate it as impossible. Patch
4472 from Mansour Moufid. Fixes bug 4059.
4473 - When a hidden service turns an extra service-side introduction
4474 circuit into a general-purpose circuit, free the rend_data and
4475 intro_key fields first, so we won't leak memory if the circuit
4476 is cannibalized for use as another service-side introduction
4477 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
4478 - Bridges now skip DNS self-tests, to act a little more stealthily.
4479 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
4480 bridges. Patch by "warms0x".
4481 - Fix internal bug-checking logic that was supposed to catch
4482 failures in digest generation so that it will fail more robustly
4483 if we ask for a nonexistent algorithm. Found by Coverity Scan.
4484 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
4485 - Report any failure in init_keys() calls launched because our
4486 IP address has changed. Spotted by Coverity Scan. Bugfix on
4487 0.1.1.4-alpha; fixes CID 484.
4489 o Minor bugfixes (log messages and documentation):
4490 - Remove a confusing dollar sign from the example fingerprint in the
4491 man page, and also make the example fingerprint a valid one. Fixes
4492 bug 4309; bugfix on 0.2.1.3-alpha.
4493 - The next version of Windows will be called Windows 8, and it has
4494 a major version of 6, minor version of 2. Correctly identify that
4495 version instead of calling it "Very recent version". Resolves
4496 ticket 4153; reported by funkstar.
4497 - Downgrade log messages about circuit timeout calibration from
4498 "notice" to "info": they don't require or suggest any human
4499 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
4500 bugfix on 0.2.2.14-alpha.
4503 - Turn on directory request statistics by default and include them in
4504 extra-info descriptors. Don't break if we have no GeoIP database.
4505 Backported from 0.2.3.1-alpha; implements ticket 3951.
4506 - Update to the October 4 2011 Maxmind GeoLite Country database.
4509 Changes in version 0.2.1.31 - 2011-10-26
4510 Tor 0.2.1.31 backports important security and privacy fixes for
4511 oldstable. This release is intended only for package maintainers and
4512 others who cannot use the 0.2.2 stable series. All others should be
4513 using Tor 0.2.2.x or newer.
4515 o Security fixes (also included in 0.2.2.x):
4516 - Replace all potentially sensitive memory comparison operations
4517 with versions whose runtime does not depend on the data being
4518 compared. This will help resist a class of attacks where an
4519 adversary can use variations in timing information to learn
4520 sensitive data. Fix for one case of bug 3122. (Safe memcmp
4521 implementation by Robert Ransom based partially on code by DJB.)
4522 - Fix an assert in parsing router descriptors containing IPv6
4523 addresses. This one took down the directory authorities when
4524 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
4526 o Privacy/anonymity fixes (also included in 0.2.2.x):
4527 - Clients and bridges no longer send TLS certificate chains on
4528 outgoing OR connections. Previously, each client or bridge would
4529 use the same cert chain for all outgoing OR connections until
4530 its IP address changes, which allowed any relay that the client
4531 or bridge contacted to determine which entry guards it is using.
4532 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
4533 - If a relay receives a CREATE_FAST cell on a TLS connection, it
4534 no longer considers that connection as suitable for satisfying a
4535 circuit EXTEND request. Now relays can protect clients from the
4536 CVE-2011-2768 issue even if the clients haven't upgraded yet.
4537 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
4538 that they initiated. Relays could distinguish incoming bridge
4539 connections from client connections, creating another avenue for
4540 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
4541 Found by "frosty_un".
4542 - When receiving a hidden service descriptor, check that it is for
4543 the hidden service we wanted. Previously, Tor would store any
4544 hidden service descriptors that a directory gave it, whether it
4545 wanted them or not. This wouldn't have let an attacker impersonate
4546 a hidden service, but it did let directories pre-seed a client
4547 with descriptors that it didn't want. Bugfix on 0.0.6.
4548 - Avoid linkability based on cached hidden service descriptors: forget
4549 all hidden service descriptors cached as a client when processing a
4550 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
4551 - Make the bridge directory authority refuse to answer directory
4552 requests for "all" descriptors. It used to include bridge
4553 descriptors in its answer, which was a major information leak.
4554 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
4555 - Don't attach new streams to old rendezvous circuits after SIGNAL
4556 NEWNYM. Previously, we would keep using an existing rendezvous
4557 circuit if it remained open (i.e. if it were kept open by a
4558 long-lived stream, or if a new stream were attached to it before
4559 Tor could notice that it was old and no longer in use). Bugfix on
4560 0.1.1.15-rc; fixes bug 3375.
4562 o Minor bugfixes (also included in 0.2.2.x):
4563 - When we restart our relay, we might get a successful connection
4564 from the outside before we've started our reachability tests,
4565 triggering a warning: "ORPort found reachable, but I have no
4566 routerinfo yet. Failing to inform controller of success." This
4567 bug was harmless unless Tor is running under a controller
4568 like Vidalia, in which case the controller would never get a
4569 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
4571 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
4572 enabled. Fixes bug 1526.
4573 - Remove undocumented option "-F" from tor-resolve: it hasn't done
4574 anything since 0.2.1.16-rc.
4575 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
4576 None of the cases where we did this before were wrong, but by making
4577 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
4578 - Fix a rare crash bug that could occur when a client was configured
4579 with a large number of bridges. Fixes bug 2629; bugfix on
4580 0.2.1.2-alpha. Bugfix by trac user "shitlei".
4581 - Correct the warning displayed when a rendezvous descriptor exceeds
4582 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
4584 - Fix an uncommon assertion failure when running with DNSPort under
4585 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
4586 - When warning about missing zlib development packages during compile,
4587 give the correct package names. Bugfix on 0.2.0.1-alpha.
4588 - Require that introduction point keys and onion keys have public
4589 exponent 65537. Bugfix on 0.2.0.10-alpha.
4590 - Do not crash when our configuration file becomes unreadable, for
4591 example due to a permissions change, between when we start up
4592 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
4594 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4596 - Always NUL-terminate the sun_path field of a sockaddr_un before
4597 passing it to the kernel. (Not a security issue: kernels are
4598 smart enough to reject bad sockaddr_uns.) Found by Coverity;
4599 CID #428. Bugfix on Tor 0.2.0.3-alpha.
4600 - Don't stack-allocate the list of supplementary GIDs when we're
4601 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4602 could take up to 256K, which is way too much stack. Found by
4603 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4605 o Minor bugfixes (only in 0.2.1.x):
4606 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
4607 rely on them. Bugfix on 0.2.1.30.
4608 - Use git revisions instead of svn revisions when generating our
4609 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
4611 o Minor features (also included in 0.2.2.x):
4612 - Adjust the expiration time on our SSL session certificates to
4613 better match SSL certs seen in the wild. Resolves ticket 4014.
4614 - Allow nameservers with IPv6 address. Resolves bug 2574.
4615 - Update to the October 4 2011 Maxmind GeoLite Country database.
4618 Changes in version 0.2.3.5-alpha - 2011-09-28
4619 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
4620 bridge relays; fixes an assertion error that many users started hitting
4621 today; and adds the ability to refill token buckets more often than
4622 once per second, allowing significant performance improvements.
4625 - Bridge relays now do their directory fetches inside Tor TLS
4626 connections, like all the other clients do, rather than connecting
4627 directly to the DirPort like public relays do. Removes another
4628 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
4629 - Bridges relays now build circuits for themselves in a more similar
4630 way to how clients build them. Removes another avenue for
4631 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
4632 when bridges were introduced.
4635 - Fix an "Assertion md->held_by_node == 1 failed" error that could
4636 occur when the same microdescriptor was referenced by two node_t
4637 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
4639 o Major features (networking):
4640 - Add a new TokenBucketRefillInterval option to refill token buckets
4641 more frequently than once per second. This should improve network
4642 performance, alleviate queueing problems, and make traffic less
4643 bursty. Implements proposal 183; closes ticket 3630. Design by
4644 Florian Tschorsch and Björn Scheuermann; implementation by
4648 - Change an integer overflow check in the OpenBSD_Malloc code so
4649 that GCC is less likely to eliminate it as impossible. Patch
4650 from Mansour Moufid. Fixes bug 4059.
4652 o Minor bugfixes (usability):
4653 - Downgrade log messages about circuit timeout calibration from
4654 "notice" to "info": they don't require or suggest any human
4655 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
4656 bugfix on 0.2.2.14-alpha.
4658 o Minor features (diagnostics):
4659 - When the system call to create a listener socket fails, log the
4660 error message explaining why. This may help diagnose bug 4027.
4663 Changes in version 0.2.3.4-alpha - 2011-09-13
4664 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
4665 tweak to Tor's TLS handshake that makes relays and bridges that run
4666 this new version reachable from Iran again. It also fixes a few new
4667 bugs in 0.2.3.x, and teaches relays to recognize when they're not
4668 listed in the network consensus and republish.
4670 o Major bugfixes (also part of 0.2.2.33):
4671 - Avoid an assertion failure when reloading a configuration with
4672 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
4673 3923; bugfix on 0.2.2.25-alpha.
4675 o Minor features (security, also part of 0.2.2.33):
4676 - Check for replays of the public-key encrypted portion of an
4677 INTRODUCE1 cell, in addition to the current check for replays of
4678 the g^x value. This prevents a possible class of active attacks
4679 by an attacker who controls both an introduction point and a
4680 rendezvous point, and who uses the malleability of AES-CTR to
4681 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
4682 that these attacks are infeasible (requiring the attacker to send
4683 on the order of zettabytes of altered cells in a short interval),
4684 but we'd rather block them off in case there are any classes of
4685 this attack that we missed. Reported by Willem Pinckaers.
4687 o Minor features (also part of 0.2.2.33):
4688 - Adjust the expiration time on our SSL session certificates to
4689 better match SSL certs seen in the wild. Resolves ticket 4014.
4690 - Change the default required uptime for a relay to be accepted as
4691 a HSDir (hidden service directory) from 24 hours to 25 hours.
4692 Improves on 0.2.0.10-alpha; resolves ticket 2649.
4693 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
4694 authorities to abstain from voting on assignment of the HSDir
4695 consensus flag. Related to bug 2649.
4696 - Update to the September 6 2011 Maxmind GeoLite Country database.
4698 o Minor bugfixes (also part of 0.2.2.33):
4699 - Demote the 'replay detected' log message emitted when a hidden
4700 service receives the same Diffie-Hellman public key in two different
4701 INTRODUCE2 cells to info level. A normal Tor client can cause that
4702 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4703 fixes part of bug 2442.
4704 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4705 level. There is nothing that a hidden service's operator can do
4706 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4708 - Clarify a log message specifying the characters permitted in
4709 HiddenServiceAuthorizeClient client names. Previously, the log
4710 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4711 given the impression that every ASCII character between "+" and "_"
4712 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4714 o Build fixes (also part of 0.2.2.33):
4715 - Clean up some code issues that prevented Tor from building on older
4716 BSDs. Fixes bug 3894; reported by "grarpamp".
4717 - Search for a platform-specific version of "ar" when cross-compiling.
4718 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4721 - Fix a bug where the SocksPort option (for example) would get
4722 ignored and replaced by the default if a SocksListenAddress
4723 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
4727 - Relays now try regenerating and uploading their descriptor more
4728 frequently if they are not listed in the consensus, or if the
4729 version of their descriptor listed in the consensus is too
4730 old. This fix should prevent situations where a server declines
4731 to re-publish itself because it has done so too recently, even
4732 though the authorities decided not to list its recent-enough
4733 descriptor. Fix for bug 3327.
4736 - Relays now include a reason for regenerating their descriptors
4737 in an HTTP header when uploading to the authorities. This will
4738 make it easier to debug descriptor-upload issues in the future.
4739 - When starting as root and then changing our UID via the User
4740 control option, and we have a ControlSocket configured, make sure
4741 that the ControlSocket is owned by the same account that Tor will
4742 run under. Implements ticket 3421; fix by Jérémy Bobbio.
4745 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
4746 utility function used in the control-port code). This shouldn't
4747 ever happen unless Tor is completely out of memory, but if it did
4748 happen and Tor somehow recovered from it, Tor could have sent a log
4749 message to a control port in the middle of a reply to a controller
4750 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
4751 - Make 'FetchUselessDescriptors' cause all descriptor types and
4752 all consensus types (including microdescriptors) to get fetched.
4753 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
4756 - Make a new "entry connection" struct as an internal subtype of "edge
4757 connection", to simplify the code and make exit connections smaller.
4760 Changes in version 0.2.2.33 - 2011-09-13
4761 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
4762 TLS handshake that makes relays and bridges that run this new version
4763 reachable from Iran again.
4766 - Avoid an assertion failure when reloading a configuration with
4767 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
4768 3923; bugfix on 0.2.2.25-alpha.
4770 o Minor features (security):
4771 - Check for replays of the public-key encrypted portion of an
4772 INTRODUCE1 cell, in addition to the current check for replays of
4773 the g^x value. This prevents a possible class of active attacks
4774 by an attacker who controls both an introduction point and a
4775 rendezvous point, and who uses the malleability of AES-CTR to
4776 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
4777 that these attacks are infeasible (requiring the attacker to send
4778 on the order of zettabytes of altered cells in a short interval),
4779 but we'd rather block them off in case there are any classes of
4780 this attack that we missed. Reported by Willem Pinckaers.
4783 - Adjust the expiration time on our SSL session certificates to
4784 better match SSL certs seen in the wild. Resolves ticket 4014.
4785 - Change the default required uptime for a relay to be accepted as
4786 a HSDir (hidden service directory) from 24 hours to 25 hours.
4787 Improves on 0.2.0.10-alpha; resolves ticket 2649.
4788 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
4789 authorities to abstain from voting on assignment of the HSDir
4790 consensus flag. Related to bug 2649.
4791 - Update to the September 6 2011 Maxmind GeoLite Country database.
4793 o Minor bugfixes (documentation and log messages):
4794 - Correct the man page to explain that HashedControlPassword and
4795 CookieAuthentication can both be set, in which case either method
4796 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4797 when we decided to allow these config options to both be set. Issue
4799 - Demote the 'replay detected' log message emitted when a hidden
4800 service receives the same Diffie-Hellman public key in two different
4801 INTRODUCE2 cells to info level. A normal Tor client can cause that
4802 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4803 fixes part of bug 2442.
4804 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4805 level. There is nothing that a hidden service's operator can do
4806 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4808 - Clarify a log message specifying the characters permitted in
4809 HiddenServiceAuthorizeClient client names. Previously, the log
4810 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4811 given the impression that every ASCII character between "+" and "_"
4812 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4815 - Provide a substitute implementation of lround() for MSVC, which
4816 apparently lacks it. Patch from Gisle Vanem.
4817 - Clean up some code issues that prevented Tor from building on older
4818 BSDs. Fixes bug 3894; reported by "grarpamp".
4819 - Search for a platform-specific version of "ar" when cross-compiling.
4820 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4823 Changes in version 0.2.3.3-alpha - 2011-09-01
4824 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
4825 security, and provides client-side support for the microdescriptor
4826 and optimistic data features introduced earlier in the 0.2.3.x
4827 series. It also includes numerous critical bugfixes in the (optional)
4828 bufferevent-based networking backend.
4830 o Major features (stream isolation):
4831 - You can now configure Tor so that streams from different
4832 applications are isolated on different circuits, to prevent an
4833 attacker who sees your streams as they leave an exit node from
4834 linking your sessions to one another. To do this, choose some way
4835 to distinguish the applications: have them connect to different
4836 SocksPorts, or have one of them use SOCKS4 while the other uses
4837 SOCKS5, or have them pass different authentication strings to the
4838 SOCKS proxy. Then, use the new SocksPort syntax to configure the
4839 degree of isolation you need. This implements Proposal 171.
4840 - There's a new syntax for specifying multiple client ports (such as
4841 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
4842 multiple *Port entries with full addr:port syntax on each.
4843 The old *ListenAddress format is still supported, but you can't
4844 mix it with the new *Port syntax.
4846 o Major features (other):
4847 - Enable microdescriptor fetching by default for clients. This allows
4848 clients to download a much smaller amount of directory information.
4849 To disable it (and go back to the old-style consensus and
4850 descriptors), set "UseMicrodescriptors 0" in your torrc file.
4851 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
4852 "PortForwarding" config option), now supports Windows.
4853 - When using an exit relay running 0.2.3.x, clients can now
4854 "optimistically" send data before the exit relay reports that
4855 the stream has opened. This saves a round trip when starting
4856 connections where the client speaks first (such as web browsing).
4857 This behavior is controlled by a consensus parameter (currently
4858 disabled). To turn it on or off manually, use the "OptimisticData"
4859 torrc option. Implements proposal 181; code by Ian Goldberg.
4861 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
4862 - When using IOCP on Windows, we need to enable Libevent windows
4864 - The IOCP backend now works even when the user has not specified
4865 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
4866 Fixes part of bug 3752.
4867 - Correctly record the bytes we've read and written when using
4868 bufferevents, so that we can include them in our bandwidth history
4869 and advertised bandwidth. Fixes bug 3803.
4870 - Apply rate-limiting only at the bottom of a chain of filtering
4871 bufferevents. This prevents us from filling up internal read
4872 buffers and violating rate-limits when filtering bufferevents
4873 are enabled. Fixes part of bug 3804.
4874 - Add high-watermarks to the output buffers for filtered
4875 bufferevents. This prevents us from filling up internal write
4876 buffers and wasting CPU cycles when filtering bufferevents are
4877 enabled. Fixes part of bug 3804.
4878 - Correctly notice when data has been written from a bufferevent
4879 without flushing it completely. Fixes bug 3805.
4880 - Fix a bug where server-side tunneled bufferevent-based directory
4881 streams would get closed prematurely. Fixes bug 3814.
4882 - Fix a use-after-free error with per-connection rate-limiting
4883 buckets. Fixes bug 3888.
4885 o Major bugfixes (also part of 0.2.2.31-rc):
4886 - If we're configured to write our ControlPorts to disk, only write
4887 them after switching UID and creating the data directory. This way,
4888 we don't fail when starting up with a nonexistent DataDirectory
4889 and a ControlPortWriteToFile setting based on that directory. Fixes
4890 bug 3747; bugfix on Tor 0.2.2.26-beta.
4893 - Added a new CONF_CHANGED event so that controllers can be notified
4894 of any configuration changes made by other controllers, or by the
4895 user. Implements ticket 1692.
4896 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
4897 leak when using bufferevents, and lets Libevent worry about how to
4898 best copy data out of a buffer.
4899 - Replace files in stats/ rather than appending to them. Now that we
4900 include statistics in extra-info descriptors, it makes no sense to
4901 keep old statistics forever. Implements ticket 2930.
4903 o Minor features (build compatibility):
4904 - Limited, experimental support for building with nmake and MSVC.
4905 - Provide a substitute implementation of lround() for MSVC, which
4906 apparently lacks it. Patch from Gisle Vanem.
4908 o Minor features (also part of 0.2.2.31-rc):
4909 - Update to the August 2 2011 Maxmind GeoLite Country database.
4911 o Minor bugfixes (on 0.2.3.x-alpha):
4912 - Fix a spurious warning when parsing SOCKS requests with
4913 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
4914 - Get rid of a harmless warning that could happen on relays running
4915 with bufferevents. The warning was caused by someone doing an http
4916 request to a relay's orport. Also don't warn for a few related
4917 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
4919 o Minor bugfixes (on 2.2.x and earlier):
4920 - Correct the man page to explain that HashedControlPassword and
4921 CookieAuthentication can both be set, in which case either method
4922 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4923 when we decided to allow these config options to both be set. Issue
4925 - The "--quiet" and "--hush" options now apply not only to Tor's
4926 behavior before logs are configured, but also to Tor's behavior in
4927 the absense of configured logs. Fixes bug 3550; bugfix on
4930 o Minor bugfixes (also part of 0.2.2.31-rc):
4931 - Write several files in text mode, on OSes that distinguish text
4932 mode from binary mode (namely, Windows). These files are:
4933 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4934 that collect those statistics; 'client_keys' and 'hostname' for
4935 hidden services that use authentication; and (in the tor-gencert
4936 utility) newly generated identity and signing keys. Previously,
4937 we wouldn't specify text mode or binary mode, leading to an
4938 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4939 the DirRecordUsageByCountry option which would have triggered
4940 the assertion failure was added), although this assertion failure
4941 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4942 - Selectively disable deprecation warnings on OS X because Lion
4943 started deprecating the shipped copy of openssl. Fixes bug 3643.
4944 - Remove an extra pair of quotation marks around the error
4945 message in control-port STATUS_GENERAL BUG events. Bugfix on
4946 0.1.2.6-alpha; fixes bug 3732.
4947 - When unable to format an address as a string, report its value
4948 as "???" rather than reusing the last formatted address. Bugfix
4951 o Code simplifications and refactoring:
4952 - Rewrite the listener-selection logic so that parsing which ports
4953 we want to listen on is now separate from binding to the ports
4957 - Building Tor with bufferevent support now requires Libevent
4958 2.0.13-stable or later. Previous versions of Libevent had bugs in
4959 SSL-related bufferevents and related issues that would make Tor
4960 work badly with bufferevents. Requiring 2.0.13-stable also allows
4961 Tor with bufferevents to take advantage of Libevent APIs
4962 introduced after 2.0.8-rc.
4965 Changes in version 0.2.2.32 - 2011-08-27
4966 The Tor 0.2.2 release series is dedicated to the memory of Andreas
4967 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
4968 a founder of the PETS community, a leader in our field, a mentor,
4969 and a friend. He left us with these words: "I had the possibility
4970 to contribute to this world that is not as it should be. I hope I
4971 could help in some areas to make the world a better place, and that
4972 I could also encourage other people to be engaged in improving the
4973 world. Please, stay engaged. This world needs you, your love, your
4974 initiative -- now I cannot be part of that anymore."
4976 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
4977 ready. More than two years in the making, this release features improved
4978 client performance and hidden service reliability, better compatibility
4979 for Android, correct behavior for bridges that listen on more than
4980 one address, more extensible and flexible directory object handling,
4981 better reporting of network statistics, improved code security, and
4982 many many other features and bugfixes.
4985 Changes in version 0.2.2.31-rc - 2011-08-17
4986 Tor 0.2.2.31-rc is the second and hopefully final release candidate
4987 for the Tor 0.2.2.x series.
4990 - Remove an extra pair of quotation marks around the error
4991 message in control-port STATUS_GENERAL BUG events. Bugfix on
4992 0.1.2.6-alpha; fixes bug 3732.
4993 - If we're configured to write our ControlPorts to disk, only write
4994 them after switching UID and creating the data directory. This way,
4995 we don't fail when starting up with a nonexistent DataDirectory
4996 and a ControlPortWriteToFile setting based on that directory. Fixes
4997 bug 3747; bugfix on Tor 0.2.2.26-beta.
5000 - Update to the August 2 2011 Maxmind GeoLite Country database.
5003 - Allow GETINFO fingerprint to return a fingerprint even when
5004 we have not yet built a router descriptor. Fixes bug 3577;
5005 bugfix on 0.2.0.1-alpha.
5006 - Write several files in text mode, on OSes that distinguish text
5007 mode from binary mode (namely, Windows). These files are:
5008 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
5009 that collect those statistics; 'client_keys' and 'hostname' for
5010 hidden services that use authentication; and (in the tor-gencert
5011 utility) newly generated identity and signing keys. Previously,
5012 we wouldn't specify text mode or binary mode, leading to an
5013 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
5014 the DirRecordUsageByCountry option which would have triggered
5015 the assertion failure was added), although this assertion failure
5016 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
5017 - Selectively disable deprecation warnings on OS X because Lion
5018 started deprecating the shipped copy of openssl. Fixes bug 3643.
5019 - When unable to format an address as a string, report its value
5020 as "???" rather than reusing the last formatted address. Bugfix
5024 Changes in version 0.2.3.2-alpha - 2011-07-18
5025 Tor 0.2.3.2-alpha introduces two new experimental features:
5026 microdescriptors and pluggable transports. It also continues cleaning
5027 up a variety of recently introduced features.
5030 - Clients can now use microdescriptors instead of regular descriptors
5031 to build circuits. Microdescriptors are authority-generated
5032 summaries of regular descriptors' contents, designed to change
5033 very rarely (see proposal 158 for details). This feature is
5034 designed to save bandwidth, especially for clients on slow internet
5035 connections. It's off by default for now, since nearly no caches
5036 support it, but it will be on-by-default for clients in a future
5037 version. You can use the UseMicrodescriptors option to turn it on.
5038 - Tor clients using bridges can now be configured to use a separate
5039 'transport' proxy for each bridge. This approach helps to resist
5040 censorship by allowing bridges to use protocol obfuscation
5041 plugins. It implements part of proposal 180. Implements ticket 2841.
5042 - While we're trying to bootstrap, record how many TLS connections
5043 fail in each state, and report which states saw the most failures
5044 in response to any bootstrap failures. This feature may speed up
5045 diagnosis of censorship events. Implements ticket 3116.
5047 o Major bugfixes (on 0.2.3.1-alpha):
5048 - When configuring a large set of nodes in EntryNodes (as with
5049 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
5050 random subset to be guards, and choose them in random
5051 order. Fixes bug 2798.
5052 - Tor could crash when remembering a consensus in a non-used consensus
5053 flavor without having a current consensus set. Fixes bug 3361.
5054 - Comparing an unknown address to a microdescriptor's shortened exit
5055 policy would always give a "rejected" result. Fixes bug 3599.
5056 - Using microdescriptors as a client no longer prevents Tor from
5057 uploading and downloading hidden service descriptors. Fixes
5061 - Allow nameservers with IPv6 address. Resolves bug 2574.
5062 - Accept attempts to include a password authenticator in the
5063 handshake, as supported by SOCKS5. This handles SOCKS clients that
5064 don't know how to omit a password when authenticating. Resolves
5066 - When configuring a large set of nodes in EntryNodes, and there are
5067 enough of them listed as Guard so that we don't need to consider
5068 the non-guard entries, prefer the ones listed with the Guard flag.
5069 - Check for and recover from inconsistency in the microdescriptor
5070 cache. This will make it harder for us to accidentally free a
5071 microdescriptor without removing it from the appropriate data
5072 structures. Fixes issue 3135; issue noted by "wanoskarnet".
5073 - Log SSL state transitions at log level DEBUG, log domain
5074 HANDSHAKE. This can be useful for debugging censorship events.
5075 Implements ticket 3264.
5076 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
5077 implements ticket 3439.
5079 o Minor bugfixes (on 0.2.3.1-alpha):
5080 - Do not free all general-purpose regular descriptors just
5081 because microdescriptor use is enabled. Fixes bug 3113.
5082 - Correctly link libevent_openssl when --enable-static-libevent
5083 is passed to configure. Fixes bug 3118.
5084 - Bridges should not complain during their heartbeat log messages that
5085 they are unlisted in the consensus: that's more or less the point
5086 of being a bridge. Fixes bug 3183.
5087 - Report a SIGNAL event to controllers when acting on a delayed
5088 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
5089 event to the controller if we acted on a SIGNAL NEWNYM command
5090 immediately, and otherwise not report a SIGNAL event for the
5091 command at all. Fixes bug 3349.
5092 - Fix a crash when handling the SIGNAL controller command or
5093 reporting ERR-level status events with bufferevents enabled. Found
5094 by Robert Ransom. Fixes bug 3367.
5095 - Always ship the tor-fw-helper manpage in our release tarballs.
5096 Fixes bug 3389. Reported by Stephen Walker.
5097 - Fix a class of double-mark-for-close bugs when bufferevents
5098 are enabled. Fixes bug 3403.
5099 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
5100 - Add SIGNAL to the list returned by the 'GETINFO events/names'
5101 control-port command. Fixes part of bug 3465.
5102 - Prevent using negative indices during unit test runs when read_all()
5103 fails. Spotted by coverity.
5104 - Fix a rare memory leak when checking the nodelist without it being
5105 present. Found by coverity.
5106 - Only try to download a microdescriptor-flavored consensus from
5107 a directory cache that provides them.
5109 o Minor bugfixes (on 0.2.2.x and earlier):
5110 - Assert that hidden-service-related operations are not performed
5111 using single-hop circuits. Previously, Tor would assert that
5112 client-side streams are not attached to single-hop circuits,
5113 but not that other sensitive operations on the client and service
5114 side are not performed using single-hop circuits. Fixes bug 3332;
5116 - Don't publish a new relay descriptor when we reload our onion key,
5117 unless the onion key has actually changed. Fixes bug 3263 and
5118 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
5119 - Allow GETINFO fingerprint to return a fingerprint even when
5120 we have not yet built a router descriptor. Fixes bug 3577;
5121 bugfix on 0.2.0.1-alpha.
5122 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
5123 on 0.2.2.4-alpha; fixes bug 3427.
5125 o Code simplification and refactoring:
5126 - Use tor_sscanf() in place of scanf() in more places through the
5127 code. This makes us a little more locale-independent, and
5128 should help shut up code-analysis tools that can't tell
5129 a safe sscanf string from a dangerous one.
5130 - Use tt_assert(), not tor_assert(), for checking for test failures.
5131 This makes the unit tests more able to go on in the event that
5133 - Split connection_about_to_close() into separate functions for each
5137 - On Windows, we now define the _WIN32_WINNT macros only if they
5138 are not already defined. This lets the person building Tor decide,
5139 if they want, to require a later version of Windows.
5142 Changes in version 0.2.2.30-rc - 2011-07-07
5143 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
5144 series. It fixes a few smaller bugs, but generally appears stable.
5145 Please test it and let us know whether it is!
5148 - Send a SUCCEEDED stream event to the controller when a reverse
5149 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
5150 discovered by katmagic.
5151 - Always NUL-terminate the sun_path field of a sockaddr_un before
5152 passing it to the kernel. (Not a security issue: kernels are
5153 smart enough to reject bad sockaddr_uns.) Found by Coverity;
5154 CID #428. Bugfix on Tor 0.2.0.3-alpha.
5155 - Don't stack-allocate the list of supplementary GIDs when we're
5156 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
5157 could take up to 256K, which is way too much stack. Found by
5158 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
5159 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
5160 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
5161 fixes part of bug 3465.
5162 - Fix a memory leak when receiving a descriptor for a hidden
5163 service we didn't ask for. Found by Coverity; CID #30. Bugfix
5167 - Update to the July 1 2011 Maxmind GeoLite Country database.
5170 Changes in version 0.2.2.29-beta - 2011-06-20
5171 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
5172 have bridge lines in their torrc but don't want to use them; gets
5173 us closer to having the control socket feature working on Debian;
5174 and fixes a variety of smaller bugs.
5177 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
5178 When we changed the default behavior to "use bridges if any
5179 are listed in the torrc", we surprised users who had bridges
5180 in their torrc files but who didn't actually want to use them.
5181 Partial resolution for bug 3354.
5184 - Don't attach new streams to old rendezvous circuits after SIGNAL
5185 NEWNYM. Previously, we would keep using an existing rendezvous
5186 circuit if it remained open (i.e. if it were kept open by a
5187 long-lived stream, or if a new stream were attached to it before
5188 Tor could notice that it was old and no longer in use). Bugfix on
5189 0.1.1.15-rc; fixes bug 3375.
5192 - Fix a bug when using ControlSocketsGroupWritable with User. The
5193 directory's group would be checked against the current group, not
5194 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
5195 bugfix on 0.2.2.26-beta.
5196 - Make connection_printf_to_buf()'s behaviour sane. Its callers
5197 expect it to emit a CRLF iff the format string ends with CRLF;
5198 it actually emitted a CRLF iff (a) the format string ended with
5199 CRLF or (b) the resulting string was over 1023 characters long or
5200 (c) the format string did not end with CRLF *and* the resulting
5201 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
5202 fixes part of bug 3407.
5203 - Make send_control_event_impl()'s behaviour sane. Its callers
5204 expect it to always emit a CRLF at the end of the string; it
5205 might have emitted extra control characters as well. Bugfix on
5206 0.1.1.9-alpha; fixes another part of bug 3407.
5207 - Make crypto_rand_int() check the value of its input correctly.
5208 Previously, it accepted values up to UINT_MAX, but could return a
5209 negative number if given a value above INT_MAX+1. Found by George
5210 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
5211 - Avoid a segfault when reading a malformed circuit build state
5212 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
5214 - When asked about a DNS record type we don't support via a
5215 client DNSPort, reply with NOTIMPL rather than an empty
5216 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
5217 - Fix a rare memory leak during stats writing. Found by coverity.
5220 - Update to the June 1 2011 Maxmind GeoLite Country database.
5222 o Code simplifications and refactoring:
5223 - Remove some dead code as indicated by coverity.
5224 - Remove a few dead assignments during router parsing. Found by
5226 - Add some forgotten return value checks during unit tests. Found
5228 - Don't use 1-bit wide signed bit fields. Found by coverity.
5231 Changes in version 0.2.2.28-beta - 2011-06-04
5232 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
5233 fixed a big bug in whether relays stay in the consensus consistently,
5234 we moved closer to handling bridges and hidden services correctly,
5235 and we started the process of better handling the dreaded "my Vidalia
5236 died, and now my Tor demands a password when I try to reconnect to it"
5240 - Don't decide to make a new descriptor when receiving a HUP signal.
5241 This bug has caused a lot of 0.2.2.x relays to disappear from the
5242 consensus periodically. Fixes the most common case of triggering
5243 bug 1810; bugfix on 0.2.2.7-alpha.
5244 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
5245 - Don't try to build descriptors if "ORPort auto" is set and we
5246 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
5248 - Resolve a crash that occurred when setting BridgeRelay to 1 with
5249 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
5250 - Apply circuit timeouts to opened hidden-service-related circuits
5251 based on the correct start time. Previously, we would apply the
5252 circuit build timeout based on time since the circuit's creation;
5253 it was supposed to be applied based on time since the circuit
5254 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
5255 - Use the same circuit timeout for client-side introduction
5256 circuits as for other four-hop circuits, rather than the timeout
5257 for single-hop directory-fetch circuits; the shorter timeout may
5258 have been appropriate with the static circuit build timeout in
5259 0.2.1.x and earlier, but caused many hidden service access attempts
5260 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
5261 on 0.2.2.2-alpha; fixes another part of bug 1297.
5262 - In ticket 2511 we fixed a case where you could use an unconfigured
5263 bridge if you had configured it as a bridge the last time you ran
5264 Tor. Now fix another edge case: if you had configured it as a bridge
5265 but then switched to a different bridge via the controller, you
5266 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
5270 - Add an __OwningControllerProcess configuration option and a
5271 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
5272 that when it exits, Tor will shut down. Implements feature 3049.
5273 - If "UseBridges 1" is set and no bridges are configured, Tor will
5274 now refuse to build any circuits until some bridges are set.
5275 If "UseBridges auto" is set, Tor will use bridges if they are
5276 configured and we are not running as a server, but otherwise will
5277 make circuits as usual. The new default is "auto". Patch by anonym,
5278 so the Tails LiveCD can stop automatically revealing you as a Tor
5282 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
5283 - Remove a trailing asterisk from "exit-policy/default" in the
5284 output of the control port command "GETINFO info/names". Bugfix
5286 - Use a wide type to hold sockets when built for 64-bit Windows builds.
5288 - Warn when the user configures two HiddenServiceDir lines that point
5289 to the same directory. Bugfix on 0.0.6 (the version introducing
5290 HiddenServiceDir); fixes bug 3289.
5291 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
5292 part of bug 2748; bugfix on 0.2.0.10-alpha.
5293 - Log malformed requests for rendezvous descriptors as protocol
5294 warnings, not warnings. Also, use a more informative log message
5295 in case someone sees it at log level warning without prior
5296 info-level messages. Fixes the other part of bug 2748; bugfix
5298 - Clear the table recording the time of the last request for each
5299 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
5300 Previously, we would clear our HS descriptor cache on SIGNAL
5301 NEWNYM, but if we had previously retrieved a descriptor (or tried
5302 to) from every directory responsible for it, we would refuse to
5303 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
5305 - Fix a log message that said "bits" while displaying a value in
5306 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
5308 - When checking for 1024-bit keys, check for 1024 bits, not 128
5309 bytes. This allows Tor to correctly discard keys of length 1017
5310 through 1023. Bugfix on 0.0.9pre5.
5313 - Relays now log the reason for publishing a new relay descriptor,
5314 so we have a better chance of hunting down instances of bug 1810.
5315 Resolves ticket 3252.
5316 - Revise most log messages that refer to nodes by nickname to
5317 instead use the "$key=nickname at address" format. This should be
5318 more useful, especially since nicknames are less and less likely
5319 to be unique. Resolves ticket 3045.
5320 - Log (at info level) when purging pieces of hidden-service-client
5321 state because of SIGNAL NEWNYM.
5324 - Remove undocumented option "-F" from tor-resolve: it hasn't done
5325 anything since 0.2.1.16-rc.
5328 Changes in version 0.2.2.27-beta - 2011-05-18
5329 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
5330 release, and also adds a few more general bugfixes.
5333 - Fix a crash bug when changing bridges in a running Tor process.
5334 Fixes bug 3213; bugfix on 0.2.2.26-beta.
5335 - When the controller configures a new bridge, don't wait 10 to 60
5336 seconds before trying to fetch its descriptor. Bugfix on
5337 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
5340 - Require that onion keys have exponent 65537 in microdescriptors too.
5341 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
5342 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
5343 Changed the limit to 512 characters by removing base64 newlines.
5344 Fixes bug 2752. Fix by Michael Yakubovich.
5345 - When a client starts or stops using bridges, never use a circuit
5346 that was built before the configuration change. This behavior could
5347 put at risk a user who uses bridges to ensure that her traffic
5348 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
5352 Changes in version 0.2.2.26-beta - 2011-05-17
5353 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
5354 also introduces a new "socksport auto" approach that should make it
5355 easier to run multiple Tors on the same system, and does a lot of
5356 cleanup to get us closer to a release candidate.
5358 o Security/privacy fixes:
5359 - Replace all potentially sensitive memory comparison operations
5360 with versions whose runtime does not depend on the data being
5361 compared. This will help resist a class of attacks where an
5362 adversary can use variations in timing information to learn
5363 sensitive data. Fix for one case of bug 3122. (Safe memcmp
5364 implementation by Robert Ransom based partially on code by DJB.)
5365 - When receiving a hidden service descriptor, check that it is for
5366 the hidden service we wanted. Previously, Tor would store any
5367 hidden service descriptors that a directory gave it, whether it
5368 wanted them or not. This wouldn't have let an attacker impersonate
5369 a hidden service, but it did let directories pre-seed a client
5370 with descriptors that it didn't want. Bugfix on 0.0.6.
5371 - On SIGHUP, do not clear out all TrackHostExits mappings, client
5372 DNS cache entries, and virtual address mappings: that's what
5373 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
5376 - The options SocksPort, ControlPort, and so on now all accept a
5377 value "auto" that opens a socket on an OS-selected port. A
5378 new ControlPortWriteToFile option tells Tor to write its
5379 actual control port or ports to a chosen file. If the option
5380 ControlPortFileGroupReadable is set, the file is created as
5381 group-readable. Now users can run two Tor clients on the same
5382 system without needing to manually mess with parameters. Resolves
5383 part of ticket 3076.
5384 - Set SO_REUSEADDR on all sockets, not just listeners. This should
5385 help busy exit nodes avoid running out of useable ports just
5386 because all the ports have been used in the near past. Resolves
5390 - New "GETINFO net/listeners/(type)" controller command to return
5391 a list of addresses and ports that are bound for listeners for a
5392 given connection type. This is useful when the user has configured
5393 "SocksPort auto" and the controller needs to know which port got
5394 chosen. Resolves another part of ticket 3076.
5395 - Add a new ControlSocketsGroupWritable configuration option: when
5396 it is turned on, ControlSockets are group-writeable by the default
5397 group of the current user. Patch by Jérémy Bobbio; implements
5399 - Tor now refuses to create a ControlSocket in a directory that is
5400 world-readable (or group-readable if ControlSocketsGroupWritable
5401 is 0). This is necessary because some operating systems do not
5402 enforce permissions on an AF_UNIX sockets. Permissions on the
5403 directory holding the socket, however, seems to work everywhere.
5404 - Rate-limit a warning about failures to download v2 networkstatus
5405 documents. Resolves part of bug 1352.
5406 - Backport code from 0.2.3.x that allows directory authorities to
5407 clean their microdescriptor caches. Needed to resolve bug 2230.
5408 - When an HTTPS proxy reports "403 Forbidden", we now explain
5409 what it means rather than calling it an unexpected status code.
5410 Closes bug 2503. Patch from Michael Yakubovich.
5411 - Update to the May 1 2011 Maxmind GeoLite Country database.
5414 - Authorities now clean their microdesc cache periodically and when
5415 reading from disk initially, not only when adding new descriptors.
5416 This prevents a bug where we could lose microdescriptors. Bugfix
5417 on 0.2.2.6-alpha. Fixes bug 2230.
5418 - Do not crash when our configuration file becomes unreadable, for
5419 example due to a permissions change, between when we start up
5420 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
5422 - Avoid a bug that would keep us from replacing a microdescriptor
5423 cache on Windows. (We would try to replace the file while still
5424 holding it open. That's fine on Unix, but Windows doesn't let us
5425 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
5426 - Add missing explanations for the authority-related torrc options
5427 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
5428 man page. Resolves issue 2379.
5429 - As an authority, do not upload our own vote or signature set to
5430 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
5431 it would get flagged as a duplicate. Resolves bug 3026.
5432 - Accept hidden service descriptors if we think we might be a hidden
5433 service directory, regardless of what our consensus says. This
5434 helps robustness, since clients and hidden services can sometimes
5435 have a more up-to-date view of the network consensus than we do,
5436 and if they think that the directory authorities list us a HSDir,
5437 we might actually be one. Related to bug 2732; bugfix on
5439 - When a controller changes TrackHostExits, remove mappings for
5440 hosts that should no longer have their exits tracked. Bugfix on
5442 - When a controller changes VirtualAddrNetwork, remove any mappings
5443 for hosts that were automapped to the old network. Bugfix on
5445 - When a controller changes one of the AutomapHosts* options, remove
5446 any mappings for hosts that should no longer be automapped. Bugfix
5448 - Do not reset the bridge descriptor download status every time we
5449 re-parse our configuration or get a configuration change. Fixes
5450 bug 3019; bugfix on 0.2.0.3-alpha.
5452 o Minor bugfixes (code cleanup):
5453 - When loading the microdesc journal, remember its current size.
5454 In 0.2.2, this helps prevent the microdesc journal from growing
5455 without limit on authorities (who are the only ones to use it in
5456 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
5457 Fix posted by "cypherpunks."
5458 - The microdesc journal is supposed to get rebuilt only if it is
5459 at least _half_ the length of the store, not _twice_ the length
5460 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
5461 - Fix a potential null-pointer dereference while computing a
5462 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
5464 - Avoid a possible null-pointer dereference when rebuilding the mdesc
5465 cache without actually having any descriptors to cache. Bugfix on
5466 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
5467 - If we fail to compute the identity digest of a v3 legacy keypair,
5468 warn, and don't use a buffer-full of junk instead. Bugfix on
5469 0.2.1.1-alpha; fixes bug 3106.
5470 - Resolve an untriggerable issue in smartlist_string_num_isin(),
5471 where if the function had ever in the future been used to check
5472 for the presence of a too-large number, it would have given an
5473 incorrect result. (Fortunately, we only used it for 16-bit
5474 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
5475 - Require that introduction point keys and onion handshake keys
5476 have a public exponent of 65537. Starts to fix bug 3207; bugfix
5480 - Caches no longer download and serve v2 networkstatus documents
5481 unless FetchV2Networkstatus flag is set: these documents haven't
5482 haven't been used by clients or relays since 0.2.0.x. Resolves
5486 Changes in version 0.2.3.1-alpha - 2011-05-05
5487 Tor 0.2.3.1-alpha adds some new experimental features, including support
5488 for an improved network IO backend, IOCP networking on Windows,
5489 microdescriptor caching, "fast-start" support for streams, and automatic
5490 home router configuration. There are also numerous internal improvements
5491 to try to make the code easier for developers to work with.
5493 This is the first alpha release in a new series, so expect there to be
5494 bugs. Users who would rather test out a more stable branch should
5495 stay with 0.2.2.x for now.
5498 - Tor can now optionally build with the "bufferevents" buffered IO
5499 backend provided by Libevent 2. To use this feature, make sure you
5500 have the latest possible version of Libevent, and pass the
5501 --enable-bufferevents flag to configure when building Tor from
5502 source. This feature will make our networking code more flexible,
5503 let us stack layers on each other, and let us use more efficient
5504 zero-copy transports where available.
5505 - As an experimental feature, Tor can use IOCP for networking on Windows.
5506 Once this code is tuned and optimized, it promises much better
5507 performance than the select-based backend we've used in the past. To
5508 try this feature, you must build Tor with Libevent 2, configure Tor
5509 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
5510 your torrc. There are known bugs here: only try this if you can help
5511 debug it as it breaks.
5512 - The EntryNodes option can now include country codes like {de} or IP
5513 addresses or network masks. Previously we had disallowed these options
5514 because we didn't have an efficient way to keep the list up to
5515 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
5516 - Exit nodes now accept and queue data on not-yet-connected streams.
5517 Previously, the client wasn't allowed to send data until the stream was
5518 connected, which slowed down all connections. This change will enable
5519 clients to perform a "fast-start" on streams and send data without
5520 having to wait for a confirmation that the stream has opened. (Patch
5521 from Ian Goldberg; implements the server side of Proposal 174.)
5522 - Tor now has initial support for automatic port mapping on the many
5523 home routers that support NAT-PMP or UPnP. (Not yet supported on
5524 Windows). To build the support code, you'll need to have libnatpnp
5525 library and/or the libminiupnpc library, and you'll need to enable the
5526 feature specifically by passing "--enable-upnp" and/or
5527 "--enable-natpnp" to configure. To turn it on, use the new
5528 PortForwarding option.
5529 - Caches now download, cache, and serve multiple "flavors" of the
5530 consensus, including a flavor that describes microdescriptors.
5531 - Caches now download, cache, and serve microdescriptors -- small
5532 summaries of router descriptors that are authenticated by all of the
5533 directory authorities. Once enough caches are running this code,
5534 clients will be able to save significant amounts of directory bandwidth
5535 by downloading microdescriptors instead of router descriptors.
5538 - Make logging resolution configurable with a new LogTimeGranularity
5539 option, and change the default from 1 millisecond to 1 second.
5540 Implements enhancement 1668.
5541 - We log which torrc file we're using on startup. Implements ticket
5543 - Ordinarily, Tor does not count traffic from private addresses (like
5544 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
5545 There is now a new option, CountPrivateBandwidth, to disable this
5546 behavior. Patch from Daniel Cagara.
5547 - New --enable-static-tor configure option for building Tor as
5548 statically as possible. Idea, general hackery and thoughts from
5549 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
5551 - If you set the NumCPUs option to 0, Tor will now try to detect how
5552 many CPUs you have. This is the new default behavior.
5553 - Turn on directory request statistics by default and include them in
5554 extra-info descriptors. Don't break if we have no GeoIP database.
5555 - Relays that set "ConnDirectionStatistics 1" write statistics on the
5556 bidirectional use of connections to disk every 24 hours.
5557 - Add a GeoIP file digest to the extra-info descriptor. Implements
5559 - The NodeFamily option -- which let you declare that you want to
5560 consider nodes to be part of a family whether they list themselves
5561 that way or not -- now allows IP address ranges and country codes.
5562 - Add a new 'Heartbeat' log message type to periodically log a message
5563 describing Tor's status at level Notice. This feature is meant for
5564 operators who log at notice, and want to make sure that their Tor
5565 server is still working. Implementation by George Kadianakis.
5567 o Minor bugfixes (on 0.2.2.25-alpha):
5568 - When loading the microdesc journal, remember its current size.
5569 In 0.2.2, this helps prevent the microdesc journal from growing
5570 without limit on authorities (who are the only ones to use it in
5571 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
5572 Fix posted by "cypherpunks."
5573 - The microdesc journal is supposed to get rebuilt only if it is
5574 at least _half_ the length of the store, not _twice_ the length
5575 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
5576 - If as an authority we fail to compute the identity digest of a v3
5577 legacy keypair, warn, and don't use a buffer-full of junk instead.
5578 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
5579 - Authorities now clean their microdesc cache periodically and when
5580 reading from disk initially, not only when adding new descriptors.
5581 This prevents a bug where we could lose microdescriptors. Bugfix
5584 o Minor features (controller):
5585 - Add a new SIGNAL event to the controller interface so that
5586 controllers can be notified when Tor handles a signal. Resolves
5587 issue 1955. Patch by John Brooks.
5588 - Add a new GETINFO option to get total bytes read and written. Patch
5589 from pipe, revised by atagar. Resolves ticket 2345.
5590 - Implement some GETINFO controller fields to provide information about
5591 the Tor process's pid, euid, username, and resource limits.
5594 - Our build system requires automake 1.6 or later to create the
5595 Makefile.in files. Previously, you could have used 1.4.
5596 This only affects developers and people building Tor from git;
5597 people who build Tor from the source distribution without changing
5598 the Makefile.am files should be fine.
5599 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
5600 so on. This is more robust against some of the failure modes
5601 associated with running the autotools pieces on their own.
5603 o Minor packaging issues:
5604 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
5605 already created. Patch from Andreas Stieger. Fixes bug 2573.
5607 o Code simplifications and refactoring:
5608 - A major revision to our internal node-selecting and listing logic.
5609 Tor already had at least two major ways to look at the question of
5610 "which Tor servers do we know about": a list of router descriptors,
5611 and a list of entries in the current consensus. With
5612 microdescriptors, we're adding a third. Having so many systems
5613 without an abstraction layer over them was hurting the codebase.
5614 Now, we have a new "node_t" abstraction that presents a consistent
5615 interface to a client's view of a Tor node, and holds (nearly) all
5616 of the mutable state formerly in routerinfo_t and routerstatus_t.
5617 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
5618 no longer link against Libevent: they never used it, but
5619 our library structure used to force them to link it.
5622 - Remove some old code to work around even older versions of Tor that
5623 used forked processes to handle DNS requests. Such versions of Tor
5624 are no longer in use as servers.
5626 o Documentation fixes:
5627 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
5628 - Add missing documentation for the authority-related torrc options
5629 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
5633 Changes in version 0.2.2.25-alpha - 2011-04-29
5634 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
5635 robust, routers no longer overreport their bandwidth, Win7 should crash
5636 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
5637 now prevents hidden service-related activity from being linkable. It
5638 provides more information to Vidalia so you can see if your bridge is
5639 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
5640 StrictNodes configuration options to make them more reliable, more
5641 understandable, and more regularly applied. If you use those options,
5642 please see the revised documentation for them in the manual page.
5645 - Relays were publishing grossly inflated bandwidth values because
5646 they were writing their state files wrong--now they write the
5647 correct value. Also, resume reading bandwidth history from the
5648 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
5649 - Improve hidden service robustness: When we find that we have
5650 extended a hidden service's introduction circuit to a relay not
5651 listed as an introduction point in the HS descriptor we currently
5652 have, retry with an introduction point from the current
5653 descriptor. Previously we would just give up. Fixes bugs 1024 and
5654 1930; bugfix on 0.2.0.10-alpha.
5655 - Clients now stop trying to use an exit node associated with a given
5656 destination by TrackHostExits if they fail to reach that exit node.
5657 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
5658 - Fix crash bug on platforms where gmtime and localtime can return
5659 NULL. Windows 7 users were running into this one. Fixes part of bug
5660 2077. Bugfix on all versions of Tor. Found by boboper.
5662 o Security and stability fixes:
5663 - Don't double-free a parsable, but invalid, microdescriptor, even if
5664 it is followed in the blob we're parsing by an unparsable
5665 microdescriptor. Fixes an issue reported in a comment on bug 2954.
5666 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
5667 - If the Nickname configuration option isn't given, Tor would pick a
5668 nickname based on the local hostname as the nickname for a relay.
5669 Because nicknames are not very important in today's Tor and the
5670 "Unnamed" nickname has been implemented, this is now problematic
5671 behavior: It leaks information about the hostname without being
5672 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
5673 introduced the Unnamed nickname. Reported by tagnaq.
5674 - Fix an uncommon assertion failure when running with DNSPort under
5675 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
5676 - Avoid linkability based on cached hidden service descriptors: forget
5677 all hidden service descriptors cached as a client when processing a
5678 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
5681 - Export GeoIP information on bridge usage to controllers even if we
5682 have not yet been running for 24 hours. Now Vidalia bridge operators
5683 can get more accurate and immediate feedback about their
5684 contributions to the network.
5686 o Major features and bugfixes (node selection):
5687 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
5688 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
5689 options. Previously, we had been ambiguous in describing what
5690 counted as an "exit" node, and what operations exactly "StrictNodes
5691 0" would permit. This created confusion when people saw nodes built
5692 through unexpected circuits, and made it hard to tell real bugs from
5693 surprises. Now the intended behavior is:
5694 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
5695 a node that delivers user traffic outside the Tor network.
5696 . "Entry", in the context of EntryNodes, means a node used as the
5697 first hop of a multihop circuit. It doesn't include direct
5698 connections to directory servers.
5699 . "ExcludeNodes" applies to all nodes.
5700 . "StrictNodes" changes the behavior of ExcludeNodes only. When
5701 StrictNodes is set, Tor should avoid all nodes listed in
5702 ExcludeNodes, even when it will make user requests fail. When
5703 StrictNodes is *not* set, then Tor should follow ExcludeNodes
5704 whenever it can, except when it must use an excluded node to
5705 perform self-tests, connect to a hidden service, provide a
5706 hidden service, fulfill a .exit request, upload directory
5707 information, or fetch directory information.
5708 Collectively, the changes to implement the behavior fix bug 1090.
5709 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
5710 a node is listed in both, it's treated as excluded.
5711 - ExcludeNodes now applies to directory nodes -- as a preference if
5712 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
5713 Don't exclude all the directory authorities and set StrictNodes to 1
5714 unless you really want your Tor to break.
5715 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
5716 - ExcludeExitNodes now overrides .exit requests.
5717 - We don't use bridges listed in ExcludeNodes.
5718 - When StrictNodes is 1:
5719 . We now apply ExcludeNodes to hidden service introduction points
5720 and to rendezvous points selected by hidden service users. This
5721 can make your hidden service less reliable: use it with caution!
5722 . If we have used ExcludeNodes on ourself, do not try relay
5723 reachability self-tests.
5724 . If we have excluded all the directory authorities, we will not
5725 even try to upload our descriptor if we're a relay.
5726 . Do not honor .exit requests to an excluded node.
5727 - Remove a misfeature that caused us to ignore the Fast/Stable flags
5728 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
5729 - When the set of permitted nodes changes, we now remove any mappings
5730 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
5732 - We never cannibalize a circuit that had excluded nodes on it, even
5733 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
5734 - Revert a change where we would be laxer about attaching streams to
5735 circuits than when building the circuits. This was meant to prevent
5736 a set of bugs where streams were never attachable, but our improved
5737 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
5738 - Keep track of how many times we launch a new circuit to handle a
5739 given stream. Too many launches could indicate an inconsistency
5740 between our "launch a circuit to handle this stream" logic and our
5741 "attach this stream to one of the available circuits" logic.
5742 - Improve log messages related to excluded nodes.
5745 - Fix a spurious warning when moving from a short month to a long
5746 month on relays with month-based BandwidthAccounting. Bugfix on
5747 0.2.2.17-alpha; fixes bug 3020.
5748 - When a client finds that an origin circuit has run out of 16-bit
5749 stream IDs, we now mark it as unusable for new streams. Previously,
5750 we would try to close the entire circuit. Bugfix on 0.0.6.
5751 - Add a forgotten cast that caused a compile warning on OS X 10.6.
5752 Bugfix on 0.2.2.24-alpha.
5753 - Be more careful about reporting the correct error from a failed
5754 connect() system call. Under some circumstances, it was possible to
5755 look at an incorrect value for errno when sending the end reason.
5756 Bugfix on 0.1.0.1-rc.
5757 - Correctly handle an "impossible" overflow cases in connection byte
5758 counting, where we write or read more than 4GB on an edge connection
5759 in a single second. Bugfix on 0.1.2.8-beta.
5760 - Correct the warning displayed when a rendezvous descriptor exceeds
5761 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
5763 - Clients and hidden services now use HSDir-flagged relays for hidden
5764 service descriptor downloads and uploads even if the relays have no
5765 DirPort set and the client has disabled TunnelDirConns. This will
5766 eventually allow us to give the HSDir flag to relays with no
5767 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
5768 - Downgrade "no current certificates known for authority" message from
5769 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
5770 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
5771 2917. Bugfix on 0.1.1.1-alpha.
5772 - Only limit the lengths of single HS descriptors, even when multiple
5773 HS descriptors are published to an HSDir relay in a single POST
5774 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
5775 - Write the current time into the LastWritten line in our state file,
5776 rather than the time from the previous write attempt. Also, stop
5777 trying to use a time of -1 in our log statements. Fixes bug 3039;
5778 bugfix on 0.2.2.14-alpha.
5779 - Be more consistent in our treatment of file system paths. "~" should
5780 get expanded to the user's home directory in the Log config option.
5781 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
5782 feature for the -f and --DataDirectory options.
5785 - Make sure every relay writes a state file at least every 12 hours.
5786 Previously, a relay could go for weeks without writing its state
5787 file, and on a crash could lose its bandwidth history, capacity
5788 estimates, client country statistics, and so on. Addresses bug 3012.
5789 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
5790 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
5791 clients are already deprecated because of security bugs.
5792 - Don't allow v0 hidden service authorities to act as clients.
5793 Required by fix for bug 3000.
5794 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
5795 by fix for bug 3000.
5796 - Ensure that no empty [dirreq-](read|write)-history lines are added
5797 to an extrainfo document. Implements ticket 2497.
5799 o Code simplification and refactoring:
5800 - Remove workaround code to handle directory responses from servers
5801 that had bug 539 (they would send HTTP status 503 responses _and_
5802 send a body too). Since only server versions before
5803 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
5804 keep the workaround in place.
5805 - Remove the old 'fuzzy time' logic. It was supposed to be used for
5806 handling calculations where we have a known amount of clock skew and
5807 an allowed amount of unknown skew. But we only used it in three
5808 places, and we never adjusted the known/unknown skew values. This is
5809 still something we might want to do someday, but if we do, we'll
5810 want to do it differently.
5811 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
5812 None of the cases where we did this before were wrong, but by making
5813 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
5814 - Use GetTempDir to find the proper temporary directory location on
5815 Windows when generating temporary files for the unit tests. Patch by
5819 Changes in version 0.2.2.24-alpha - 2011-04-08
5820 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
5821 prevented Tor clients from effectively using "multihomed" bridges,
5822 that is, bridges that listen on multiple ports or IP addresses so users
5823 can continue to use some of their addresses even if others get blocked.
5826 - Fix a bug where bridge users who configure the non-canonical
5827 address of a bridge automatically switch to its canonical
5828 address. If a bridge listens at more than one address, it should be
5829 able to advertise those addresses independently and any non-blocked
5830 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
5832 - If you configured Tor to use bridge A, and then quit and
5833 configured Tor to use bridge B instead, it would happily continue
5834 to use bridge A if it's still reachable. While this behavior is
5835 a feature if your goal is connectivity, in some scenarios it's a
5836 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
5837 - Directory authorities now use data collected from their own
5838 uptime observations when choosing whether to assign the HSDir flag
5839 to relays, instead of trusting the uptime value the relay reports in
5840 its descriptor. This change helps prevent an attack where a small
5841 set of nodes with frequently-changing identity keys can blackhole
5842 a hidden service. (Only authorities need upgrade; others will be
5843 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
5846 - When we restart our relay, we might get a successful connection
5847 from the outside before we've started our reachability tests,
5848 triggering a warning: "ORPort found reachable, but I have no
5849 routerinfo yet. Failing to inform controller of success." This
5850 bug was harmless unless Tor is running under a controller
5851 like Vidalia, in which case the controller would never get a
5852 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
5854 - Make directory authorities more accurate at recording when
5855 relays that have failed several reachability tests became
5856 unreachable, so we can provide more accuracy at assigning Stable,
5857 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
5858 - Fix an issue that prevented static linking of libevent on
5859 some platforms (notably Linux). Fixes bug 2698; bugfix on
5860 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
5861 the --with-static-libevent configure option).
5862 - We now ask the other side of a stream (the client or the exit)
5863 for more data on that stream when the amount of queued data on
5864 that stream dips low enough. Previously, we wouldn't ask the
5865 other side for more data until either it sent us more data (which
5866 it wasn't supposed to do if it had exhausted its window!) or we
5867 had completely flushed all our queued data. This flow control fix
5868 should improve throughput. Fixes bug 2756; bugfix on the earliest
5869 released versions of Tor (svn commit r152).
5870 - Avoid a double-mark-for-free warning when failing to attach a
5871 transparent proxy connection. (We thought we had fixed this in
5872 0.2.2.23-alpha, but it turns out our fix was checking the wrong
5873 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
5874 bug) and 0.2.2.23-alpha (the incorrect fix).
5875 - When warning about missing zlib development packages during compile,
5876 give the correct package names. Bugfix on 0.2.0.1-alpha.
5879 - Directory authorities now log the source of a rejected POSTed v3
5881 - Make compilation with clang possible when using
5882 --enable-gcc-warnings by removing two warning options that clang
5883 hasn't implemented yet and by fixing a few warnings. Implements
5885 - When expiring circuits, use microsecond timers rather than
5886 one-second timers. This can avoid an unpleasant situation where a
5887 circuit is launched near the end of one second and expired right
5888 near the beginning of the next, and prevent fluctuations in circuit
5890 - Use computed circuit-build timeouts to decide when to launch
5891 parallel introduction circuits for hidden services. (Previously,
5892 we would retry after 15 seconds.)
5893 - Update to the April 1 2011 Maxmind GeoLite Country database.
5896 - Create the /var/run/tor directory on startup on OpenSUSE if it is
5897 not already created. Patch from Andreas Stieger. Fixes bug 2573.
5899 o Documentation changes:
5900 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
5901 - Resolve all doxygen warnings except those for missing documentation.
5903 - Add doxygen documentation for more functions, fields, and types.
5906 Changes in version 0.2.2.23-alpha - 2011-03-08
5907 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
5908 they restart they don't lose their bandwidth capacity estimate. This
5909 release also fixes a diverse set of user-facing bugs, ranging from
5910 relays overrunning their rate limiting to clients falsely warning about
5911 clock skew to bridge descriptor leaks by our bridge directory authority.
5914 - Stop sending a CLOCK_SKEW controller status event whenever
5915 we fetch directory information from a relay that has a wrong clock.
5916 Instead, only inform the controller when it's a trusted authority
5917 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5918 the rest of bug 1074.
5919 - Fix an assert in parsing router descriptors containing IPv6
5920 addresses. This one took down the directory authorities when
5921 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
5922 - Make the bridge directory authority refuse to answer directory
5923 requests for "all" descriptors. It used to include bridge
5924 descriptors in its answer, which was a major information leak.
5925 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
5926 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5927 Tor would ignore their RelayBandwidthBurst setting,
5928 potentially using more bandwidth than expected. Bugfix on
5929 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5930 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5931 hidserv" in her torrc. The 'hidserv' argument never controlled
5932 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5935 - Relays now save observed peak bandwidth throughput rates to their
5936 state file (along with total usage, which was already saved)
5937 so that they can determine their correct estimated bandwidth on
5938 restart. Resolves bug 1863, where Tor relays would reset their
5939 estimated bandwidth to 0 after restarting.
5940 - Directory authorities now take changes in router IP address and
5941 ORPort into account when determining router stability. Previously,
5942 if a router changed its IP or ORPort, the authorities would not
5943 treat it as having any downtime for the purposes of stability
5944 calculation, whereas clients would experience downtime since the
5945 change could take a while to propagate to them. Resolves issue 1035.
5946 - Enable Address Space Layout Randomization (ASLR) and Data Execution
5947 Prevention (DEP) by default on Windows to make it harder for
5948 attackers to exploit vulnerabilities. Patch from John Brooks.
5950 o Minor bugfixes (on 0.2.1.x and earlier):
5951 - Fix a rare crash bug that could occur when a client was configured
5952 with a large number of bridges. Fixes bug 2629; bugfix on
5953 0.2.1.2-alpha. Bugfix by trac user "shitlei".
5954 - Avoid a double mark-for-free warning when failing to attach a
5955 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
5957 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
5958 found by "cypherpunks". This bug was introduced before the first
5959 Tor release, in svn commit r110.
5960 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
5961 don't mention them in the manpage. Fixes bug 2450; issue
5962 spotted by keb and G-Lo.
5963 - Fix a bug in bandwidth history state parsing that could have been
5964 triggered if a future version of Tor ever changed the timing
5965 granularity at which bandwidth history is measured. Bugfix on
5967 - When a relay decides that its DNS is too broken for it to serve
5968 as an exit server, it advertised itself as a non-exit, but
5969 continued to act as an exit. This could create accidental
5970 partitioning opportunities for users. Instead, if a relay is
5971 going to advertise reject *:* as its exit policy, it should
5972 really act with exit policy "reject *:*". Fixes bug 2366.
5973 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
5974 - In the special case where you configure a public exit relay as your
5975 bridge, Tor would be willing to use that exit relay as the last
5976 hop in your circuit as well. Now we fail that circuit instead.
5977 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
5978 - Fix a bug with our locking implementation on Windows that couldn't
5979 correctly detect when a file was already locked. Fixes bug 2504,
5980 bugfix on 0.2.1.6-alpha.
5981 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
5982 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
5984 - Set target port in get_interface_address6() correctly. Bugfix
5985 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
5986 - Directory authorities are now more robust to hops back in time
5987 when calculating router stability. Previously, if a run of uptime
5988 or downtime appeared to be negative, the calculation could give
5989 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
5991 - Fix an assert that got triggered when using the TestingTorNetwork
5992 configuration option and then issuing a GETINFO config-text control
5993 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
5995 o Minor bugfixes (on 0.2.2.x):
5996 - Clients should not weight BadExit nodes as Exits in their node
5997 selection. Similarly, directory authorities should not count BadExit
5998 bandwidth as Exit bandwidth when computing bandwidth-weights.
5999 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
6000 - Correctly clear our dir_read/dir_write history when there is an
6001 error parsing any bw history value from the state file. Bugfix on
6003 - Resolve a bug in verifying signatures of directory objects
6004 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
6005 Fixes bug 2409. Found by "piebeer".
6006 - Bridge authorities no longer crash on SIGHUP when they try to
6007 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
6011 - Log less aggressively about circuit timeout changes, and improve
6012 some other circuit timeout messages. Resolves bug 2004.
6013 - Log a little more clearly about the times at which we're no longer
6014 accepting new connections. Resolves bug 2181.
6015 - Reject attempts at the client side to open connections to private
6016 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
6017 a randomly chosen exit node. Attempts to do so are always
6018 ill-defined, generally prevented by exit policies, and usually
6019 in error. This will also help to detect loops in transparent
6020 proxy configurations. You can disable this feature by setting
6021 "ClientRejectInternalAddresses 0" in your torrc.
6022 - Always treat failure to allocate an RSA key as an unrecoverable
6024 - Update to the March 1 2011 Maxmind GeoLite Country database.
6026 o Minor features (log subsystem):
6027 - Add documentation for configuring logging at different severities in
6028 different log domains. We've had this feature since 0.2.1.1-alpha,
6029 but for some reason it never made it into the manpage. Fixes
6031 - Make it simpler to specify "All log domains except for A and B".
6032 Previously you needed to say "[*,~A,~B]". Now you can just say
6034 - Add a "LogMessageDomains 1" option to include the domains of log
6035 messages along with the messages. Without this, there's no way
6036 to use log domains without reading the source or doing a lot
6039 o Packaging changes:
6040 - Stop shipping the Tor specs files and development proposal documents
6041 in the tarball. They are now in a separate git repository at
6042 git://git.torproject.org/torspec.git
6045 Changes in version 0.2.1.30 - 2011-02-23
6046 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
6047 change is a slight tweak to Tor's TLS handshake that makes relays
6048 and bridges that run this new version reachable from Iran again.
6049 We don't expect this tweak will win the arms race long-term, but it
6050 buys us time until we roll out a better solution.
6053 - Stop sending a CLOCK_SKEW controller status event whenever
6054 we fetch directory information from a relay that has a wrong clock.
6055 Instead, only inform the controller when it's a trusted authority
6056 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
6057 the rest of bug 1074.
6058 - Fix a bounds-checking error that could allow an attacker to
6059 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
6061 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
6062 Tor would ignore their RelayBandwidthBurst setting,
6063 potentially using more bandwidth than expected. Bugfix on
6064 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
6065 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
6066 hidserv" in her torrc. The 'hidserv' argument never controlled
6067 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
6070 - Adjust our TLS Diffie-Hellman parameters to match those used by
6072 - Update to the February 1 2011 Maxmind GeoLite Country database.
6075 - Check for and reject overly long directory certificates and
6076 directory tokens before they have a chance to hit any assertions.
6077 Bugfix on 0.2.1.28. Found by "doorss".
6078 - Bring the logic that gathers routerinfos and assesses the
6079 acceptability of circuits into line. This prevents a Tor OP from
6080 getting locked in a cycle of choosing its local OR as an exit for a
6081 path (due to a .exit request) and then rejecting the circuit because
6082 its OR is not listed yet. It also prevents Tor clients from using an
6083 OR running in the same instance as an exit (due to a .exit request)
6084 if the OR does not meet the same requirements expected of an OR
6085 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
6087 o Packaging changes:
6088 - Stop shipping the Tor specs files and development proposal documents
6089 in the tarball. They are now in a separate git repository at
6090 git://git.torproject.org/torspec.git
6091 - Do not include Git version tags as though they are SVN tags when
6092 generating a tarball from inside a repository that has switched
6093 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
6096 Changes in version 0.2.2.22-alpha - 2011-01-25
6097 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
6098 main other change is a slight tweak to Tor's TLS handshake that makes
6099 relays and bridges that run this new version reachable from Iran again.
6100 We don't expect this tweak will win the arms race long-term, but it
6101 will buy us a bit more time until we roll out a better solution.
6104 - Fix a bounds-checking error that could allow an attacker to
6105 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
6107 - Don't assert when changing from bridge to relay or vice versa
6108 via the controller. The assert happened because we didn't properly
6109 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
6110 bug 2433. Reported by bastik.
6113 - Adjust our TLS Diffie-Hellman parameters to match those used by
6115 - Provide a log message stating which geoip file we're parsing
6116 instead of just stating that we're parsing the geoip file.
6117 Implements ticket 2432.
6120 - Check for and reject overly long directory certificates and
6121 directory tokens before they have a chance to hit any assertions.
6122 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
6125 Changes in version 0.2.2.21-alpha - 2011-01-15
6126 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
6127 continues our recent code security audit work. The main fix resolves
6128 a remote heap overflow vulnerability that can allow remote code
6129 execution (CVE-2011-0427). Other fixes address a variety of assert
6130 and crash bugs, most of which we think are hard to exploit remotely.
6132 o Major bugfixes (security), also included in 0.2.1.29:
6133 - Fix a heap overflow bug where an adversary could cause heap
6134 corruption. This bug probably allows remote code execution
6135 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
6137 - Prevent a denial-of-service attack by disallowing any
6138 zlib-compressed data whose compression factor is implausibly
6139 high. Fixes part of bug 2324; reported by "doorss".
6140 - Zero out a few more keys in memory before freeing them. Fixes
6141 bug 2384 and part of bug 2385. These key instances found by
6142 "cypherpunks", based on Andrew Case's report about being able
6143 to find sensitive data in Tor's memory space if you have enough
6144 permissions. Bugfix on 0.0.2pre9.
6146 o Major bugfixes (crashes), also included in 0.2.1.29:
6147 - Prevent calls to Libevent from inside Libevent log handlers.
6148 This had potential to cause a nasty set of crashes, especially
6149 if running Libevent with debug logging enabled, and running
6150 Tor with a controller watching for low-severity log messages.
6151 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
6152 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
6153 underflow errors there too. Fixes the other part of bug 2324.
6154 - Fix a bug where we would assert if we ever had a
6155 cached-descriptors.new file (or another file read directly into
6156 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
6157 on 0.2.1.25. Found by doorss.
6158 - Fix some potential asserts and parsing issues with grossly
6159 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
6162 o Minor bugfixes (other), also included in 0.2.1.29:
6163 - Fix a bug with handling misformed replies to reverse DNS lookup
6164 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
6165 bug reported by doorss.
6166 - Fix compilation on mingw when a pthreads compatibility library
6167 has been installed. (We don't want to use it, so we shouldn't
6168 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
6169 - Fix a bug where we would declare that we had run out of virtual
6170 addresses when the address space was only half-exhausted. Bugfix
6172 - Correctly handle the case where AutomapHostsOnResolve is set but
6173 no virtual addresses are available. Fixes bug 2328; bugfix on
6174 0.1.2.1-alpha. Bug found by doorss.
6175 - Correctly handle wrapping around when we run out of virtual
6176 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
6178 o Minor features, also included in 0.2.1.29:
6179 - Update to the January 1 2011 Maxmind GeoLite Country database.
6180 - Introduce output size checks on all of our decryption functions.
6182 o Build changes, also included in 0.2.1.29:
6183 - Tor does not build packages correctly with Automake 1.6 and earlier;
6184 added a check to Makefile.am to make sure that we're building with
6185 Automake 1.7 or later.
6186 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
6187 because we built it with a too-old version of automake. Thus that
6188 release broke ./configure --enable-openbsd-malloc, which is popular
6189 among really fast exit relays on Linux.
6191 o Major bugfixes, new in 0.2.2.21-alpha:
6192 - Prevent crash/heap corruption when the cbtnummodes consensus
6193 parameter is set to 0 or large values. Fixes bug 2317; bugfix
6196 o Major features, new in 0.2.2.21-alpha:
6197 - Introduce minimum/maximum values that clients will believe
6198 from the consensus. Now we'll have a better chance to avoid crashes
6199 or worse when a consensus param has a weird value.
6201 o Minor features, new in 0.2.2.21-alpha:
6202 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
6203 used on bridges, and it makes bridge scanning somewhat easier.
6204 - If writing the state file to disk fails, wait up to an hour before
6205 retrying again, rather than trying again each second. Fixes bug
6206 2346; bugfix on Tor 0.1.1.3-alpha.
6207 - Make Libevent log messages get delivered to controllers later,
6208 and not from inside the Libevent log handler. This prevents unsafe
6209 reentrant Libevent calls while still letting the log messages
6211 - Detect platforms that brokenly use a signed size_t, and refuse to
6212 build there. Found and analyzed by doorss and rransom.
6213 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
6216 o Minor bugfixes, new in 0.2.2.21-alpha:
6217 - Handle SOCKS messages longer than 128 bytes long correctly, rather
6218 than waiting forever for them to finish. Fixes bug 2330; bugfix
6219 on 0.2.0.16-alpha. Found by doorss.
6220 - Add assertions to check for overflow in arguments to
6221 base32_encode() and base32_decode(); fix a signed-unsigned
6222 comparison there too. These bugs are not actually reachable in Tor,
6223 but it's good to prevent future errors too. Found by doorss.
6224 - Correctly detect failures to create DNS requests when using Libevent
6225 versions before v2. (Before Libevent 2, we used our own evdns
6226 implementation. Its return values for Libevent's evdns_resolve_*()
6227 functions are not consistent with those from Libevent.) Fixes bug
6228 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
6230 o Documentation, new in 0.2.2.21-alpha:
6231 - Document the default socks host and port (127.0.0.1:9050) for
6235 Changes in version 0.2.1.29 - 2011-01-15
6236 Tor 0.2.1.29 continues our recent code security audit work. The main
6237 fix resolves a remote heap overflow vulnerability that can allow remote
6238 code execution. Other fixes address a variety of assert and crash bugs,
6239 most of which we think are hard to exploit remotely.
6241 o Major bugfixes (security):
6242 - Fix a heap overflow bug where an adversary could cause heap
6243 corruption. This bug probably allows remote code execution
6244 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
6246 - Prevent a denial-of-service attack by disallowing any
6247 zlib-compressed data whose compression factor is implausibly
6248 high. Fixes part of bug 2324; reported by "doorss".
6249 - Zero out a few more keys in memory before freeing them. Fixes
6250 bug 2384 and part of bug 2385. These key instances found by
6251 "cypherpunks", based on Andrew Case's report about being able
6252 to find sensitive data in Tor's memory space if you have enough
6253 permissions. Bugfix on 0.0.2pre9.
6255 o Major bugfixes (crashes):
6256 - Prevent calls to Libevent from inside Libevent log handlers.
6257 This had potential to cause a nasty set of crashes, especially
6258 if running Libevent with debug logging enabled, and running
6259 Tor with a controller watching for low-severity log messages.
6260 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
6261 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
6262 underflow errors there too. Fixes the other part of bug 2324.
6263 - Fix a bug where we would assert if we ever had a
6264 cached-descriptors.new file (or another file read directly into
6265 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
6266 on 0.2.1.25. Found by doorss.
6267 - Fix some potential asserts and parsing issues with grossly
6268 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
6271 o Minor bugfixes (other):
6272 - Fix a bug with handling misformed replies to reverse DNS lookup
6273 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
6274 bug reported by doorss.
6275 - Fix compilation on mingw when a pthreads compatibility library
6276 has been installed. (We don't want to use it, so we shouldn't
6277 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
6278 - Fix a bug where we would declare that we had run out of virtual
6279 addresses when the address space was only half-exhausted. Bugfix
6281 - Correctly handle the case where AutomapHostsOnResolve is set but
6282 no virtual addresses are available. Fixes bug 2328; bugfix on
6283 0.1.2.1-alpha. Bug found by doorss.
6284 - Correctly handle wrapping around to when we run out of virtual
6285 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
6286 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
6287 because we built it with a too-old version of automake. Thus that
6288 release broke ./configure --enable-openbsd-malloc, which is popular
6289 among really fast exit relays on Linux.
6292 - Update to the January 1 2011 Maxmind GeoLite Country database.
6293 - Introduce output size checks on all of our decryption functions.
6296 - Tor does not build packages correctly with Automake 1.6 and earlier;
6297 added a check to Makefile.am to make sure that we're building with
6298 Automake 1.7 or later.
6301 Changes in version 0.2.2.20-alpha - 2010-12-17
6302 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
6303 exploitable bugs. We also fix a variety of other significant bugs,
6304 change the IP address for one of our directory authorities, and update
6305 the minimum version that Tor relays must run to join the network.
6308 - Fix a remotely exploitable bug that could be used to crash instances
6309 of Tor remotely by overflowing on the heap. Remote-code execution
6310 hasn't been confirmed, but can't be ruled out. Everyone should
6311 upgrade. Bugfix on the 0.1.1 series and later.
6312 - Fix a bug that could break accounting on 64-bit systems with large
6313 time_t values, making them hibernate for impossibly long intervals.
6314 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
6315 - Fix a logic error in directory_fetches_from_authorities() that
6316 would cause all _non_-exits refusing single-hop-like circuits
6317 to fetch from authorities, when we wanted to have _exits_ fetch
6318 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
6320 - Fix a stream fairness bug that would cause newer streams on a given
6321 circuit to get preference when reading bytes from the origin or
6322 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
6323 introduced before the first Tor release, in svn revision r152.
6325 o Directory authority changes:
6326 - Change IP address and ports for gabelmoo (v3 directory authority).
6329 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
6330 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
6331 - Fix an off-by-one error in calculating some controller command
6332 argument lengths. Fortunately, this mistake is harmless since
6333 the controller code does redundant NUL termination too. Found by
6334 boboper. Bugfix on 0.1.1.1-alpha.
6335 - Do not dereference NULL if a bridge fails to build its
6336 extra-info descriptor. Found by an anonymous commenter on
6337 Trac. Bugfix on 0.2.2.19-alpha.
6340 - Update to the December 1 2010 Maxmind GeoLite Country database.
6341 - Directory authorities now reject relays running any versions of
6342 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
6343 known bugs that keep RELAY_EARLY cells from working on rendezvous
6344 circuits. Followup to fix for bug 2081.
6345 - Directory authorities now reject relays running any version of Tor
6346 older than 0.2.0.26-rc. That version is the earliest that fetches
6347 current directory information correctly. Fixes bug 2156.
6348 - Report only the top 10 ports in exit-port stats in order not to
6349 exceed the maximum extra-info descriptor length of 50 KB. Implements
6353 Changes in version 0.2.1.28 - 2010-12-17
6354 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
6355 exploitable bugs. We also took this opportunity to change the IP address
6356 for one of our directory authorities, and to update the geoip database
6360 - Fix a remotely exploitable bug that could be used to crash instances
6361 of Tor remotely by overflowing on the heap. Remote-code execution
6362 hasn't been confirmed, but can't be ruled out. Everyone should
6363 upgrade. Bugfix on the 0.1.1 series and later.
6365 o Directory authority changes:
6366 - Change IP address and ports for gabelmoo (v3 directory authority).
6369 - Update to the December 1 2010 Maxmind GeoLite Country database.
6372 Changes in version 0.2.1.27 - 2010-11-23
6373 Yet another OpenSSL security patch broke its compatibility with Tor:
6374 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
6375 also took this opportunity to fix several crash bugs, integrate a new
6376 directory authority, and update the bundled GeoIP database.
6379 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
6380 No longer set the tlsext_host_name extension on server SSL objects;
6381 but continue to set it on client SSL objects. Our goal in setting
6382 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
6383 bugfix on 0.2.1.1-alpha.
6384 - Do not log messages to the controller while shrinking buffer
6385 freelists. Doing so would sometimes make the controller connection
6386 try to allocate a buffer chunk, which would mess up the internals
6387 of the freelist and cause an assertion failure. Fixes bug 1125;
6388 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
6389 - Learn our external IP address when we're a relay or bridge, even if
6390 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
6391 where we introduced bridge relays that don't need to publish to
6392 be useful. Fixes bug 2050.
6393 - Do even more to reject (and not just ignore) annotations on
6394 router descriptors received anywhere but from the cache. Previously
6395 we would ignore such annotations at first, but cache them to disk
6396 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
6397 - When you're using bridges and your network goes away and your
6398 bridges get marked as down, recover when you attempt a new socks
6399 connection (if the network is back), rather than waiting up to an
6400 hour to try fetching new descriptors for your bridges. Bugfix on
6401 0.2.0.3-alpha; fixes bug 1981.
6404 - Move to the November 2010 Maxmind GeoLite country db (rather
6405 than the June 2009 ip-to-country GeoIP db) for our statistics that
6406 count how many users relays are seeing from each country. Now we'll
6407 have more accurate data, especially for many African countries.
6409 o New directory authorities:
6410 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
6414 - Fix an assertion failure that could occur in directory caches or
6415 bridge users when using a very short voting interval on a testing
6416 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
6418 - Enforce multiplicity rules when parsing annotations. Bugfix on
6419 0.2.0.8-alpha. Found by piebeer.
6420 - Allow handshaking OR connections to take a full KeepalivePeriod
6421 seconds to handshake. Previously, we would close them after
6422 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
6423 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
6425 - When building with --enable-gcc-warnings on OpenBSD, disable
6426 warnings in system headers. This makes --enable-gcc-warnings
6427 pass on OpenBSD 4.8.
6430 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
6431 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
6432 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
6433 Servers can start sending this code when enough clients recognize
6434 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
6435 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
6436 Patch from mingw-san.
6439 - Remove the old debian/ directory from the main Tor distribution.
6440 The official Tor-for-debian git repository lives at the URL
6441 https://git.torproject.org/debian/tor.git
6442 - Stop shipping the old doc/website/ directory in the tarball. We
6443 changed the website format in late 2010, and what we shipped in
6444 0.2.1.26 really wasn't that useful anyway.
6447 Changes in version 0.2.2.19-alpha - 2010-11-22
6448 Yet another OpenSSL security patch broke its compatibility with Tor:
6449 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
6452 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
6453 No longer set the tlsext_host_name extension on server SSL objects;
6454 but continue to set it on client SSL objects. Our goal in setting
6455 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
6456 bugfix on 0.2.1.1-alpha.
6459 - Try harder not to exceed the maximum length of 50 KB when writing
6460 statistics to extra-info descriptors. This bug was triggered by very
6461 fast relays reporting exit-port, entry, and dirreq statistics.
6462 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
6463 - Publish a router descriptor even if generating an extra-info
6464 descriptor fails. Previously we would not publish a router
6465 descriptor without an extra-info descriptor; this can cause fast
6466 exit relays collecting exit-port statistics to drop from the
6467 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
6470 Changes in version 0.2.2.18-alpha - 2010-11-16
6471 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
6472 us lately, makes unpublished bridge relays able to detect their IP
6473 address, and fixes a wide variety of other bugs to get us much closer
6474 to a stable release.
6477 - Do even more to reject (and not just ignore) annotations on
6478 router descriptors received anywhere but from the cache. Previously
6479 we would ignore such annotations at first, but cache them to disk
6480 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
6481 - Do not log messages to the controller while shrinking buffer
6482 freelists. Doing so would sometimes make the controller connection
6483 try to allocate a buffer chunk, which would mess up the internals
6484 of the freelist and cause an assertion failure. Fixes bug 1125;
6485 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
6486 - Learn our external IP address when we're a relay or bridge, even if
6487 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
6488 where we introduced bridge relays that don't need to publish to
6489 be useful. Fixes bug 2050.
6490 - Maintain separate TLS contexts and certificates for incoming and
6491 outgoing connections in bridge relays. Previously we would use the
6492 same TLS contexts and certs for incoming and outgoing connections.
6493 Bugfix on 0.2.0.3-alpha; addresses bug 988.
6494 - Maintain separate identity keys for incoming and outgoing TLS
6495 contexts in bridge relays. Previously we would use the same
6496 identity keys for incoming and outgoing TLS contexts. Bugfix on
6497 0.2.0.3-alpha; addresses the other half of bug 988.
6498 - Avoid an assertion failure when we as an authority receive a
6499 duplicate upload of a router descriptor that we already have,
6500 but which we previously considered an obsolete descriptor.
6501 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
6502 - Avoid a crash bug triggered by looking at a dangling pointer while
6503 setting the network status consensus. Found by Robert Ransom.
6504 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
6505 - Fix a logic error where servers that _didn't_ act as exits would
6506 try to keep their server lists more aggressively up to date than
6507 exits, when it was supposed to be the other way around. Bugfix
6510 o Minor bugfixes (on Tor 0.2.1.x and earlier):
6511 - When we're trying to guess whether we know our IP address as
6512 a relay, we would log various ways that we failed to guess
6513 our address, but never log that we ended up guessing it
6514 successfully. Now add a log line to help confused and anxious
6515 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
6516 - Bring the logic that gathers routerinfos and assesses the
6517 acceptability of circuits into line. This prevents a Tor OP from
6518 getting locked in a cycle of choosing its local OR as an exit for a
6519 path (due to a .exit request) and then rejecting the circuit because
6520 its OR is not listed yet. It also prevents Tor clients from using an
6521 OR running in the same instance as an exit (due to a .exit request)
6522 if the OR does not meet the same requirements expected of an OR
6523 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
6524 - Correctly describe errors that occur when generating a TLS object.
6525 Previously we would attribute them to a failure while generating a
6526 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
6528 - Enforce multiplicity rules when parsing annotations. Bugfix on
6529 0.2.0.8-alpha. Found by piebeer.
6530 - Fix warnings that newer versions of autoconf produced during
6531 ./autogen.sh. These warnings appear to be harmless in our case,
6532 but they were extremely verbose. Fixes bug 2020.
6534 o Minor bugfixes (on Tor 0.2.2.x):
6535 - Enable protection of small arrays whenever we build with gcc
6536 hardening features, not only when also building with warnings
6537 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
6540 - Make hidden services work better in private Tor networks by not
6541 requiring any uptime to join the hidden service descriptor
6542 DHT. Implements ticket 2088.
6543 - Rate-limit the "your application is giving Tor only an IP address"
6544 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
6545 - When AllowSingleHopExits is set, print a warning to explain to the
6546 relay operator why most clients are avoiding her relay.
6547 - Update to the November 1 2010 Maxmind GeoLite Country database.
6549 o Code simplifications and refactoring:
6550 - When we fixed bug 1038 we had to put in a restriction not to send
6551 RELAY_EARLY cells on rend circuits. This was necessary as long
6552 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
6553 active. Now remove this obsolete check. Resolves bug 2081.
6554 - Some options used different conventions for uppercasing of acronyms
6555 when comparing manpage and source. Fix those in favor of the
6556 manpage, as it makes sense to capitalize acronyms.
6557 - Remove the torrc.complete file. It hasn't been kept up to date
6558 and users will have better luck checking out the manpage.
6559 - Remove the obsolete "NoPublish" option; it has been flagged
6560 as obsolete and has produced a warning since 0.1.1.18-rc.
6561 - Remove everything related to building the expert bundle for OS X.
6562 It has confused many users, doesn't work right on OS X 10.6,
6563 and is hard to get rid of once installed. Resolves bug 1274.
6566 Changes in version 0.2.2.17-alpha - 2010-09-30
6567 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
6568 to use one-hop circuits (which can put the exit relays at higher risk,
6569 plus unbalance the network); fixes a big bug in bandwidth accounting
6570 for relays that want to limit their monthly bandwidth use; fixes a
6571 big pile of bugs in how clients tolerate temporary network failure;
6572 and makes our adaptive circuit build timeout feature (which improves
6573 client performance if your network is fast while not breaking things
6574 if your network is slow) better handle bad networks.
6577 - Exit relays now try harder to block exit attempts from unknown
6578 relays, to make it harder for people to use them as one-hop proxies
6579 a la tortunnel. Controlled by the refuseunknownexits consensus
6580 parameter (currently enabled), or you can override it on your
6581 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
6583 o Major bugfixes (0.2.1.x and earlier):
6584 - Fix a bug in bandwidth accounting that could make us use twice
6585 the intended bandwidth when our interval start changes due to
6586 daylight saving time. Now we tolerate skew in stored vs computed
6587 interval starts: if the start of the period changes by no more than
6588 50% of the period's duration, we remember bytes that we transferred
6589 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
6590 - Always search the Windows system directory for system DLLs, and
6591 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
6592 - When you're using bridges and your network goes away and your
6593 bridges get marked as down, recover when you attempt a new socks
6594 connection (if the network is back), rather than waiting up to an
6595 hour to try fetching new descriptors for your bridges. Bugfix on
6596 0.2.0.3-alpha; fixes bug 1981.
6598 o Major bugfixes (on 0.2.2.x):
6599 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
6601 - Fix a segfault that could happen when operating a bridge relay with
6602 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
6603 - The consensus bandwidth-weights (used by clients to choose fast
6604 relays) entered an unexpected edge case in September where
6605 Exits were much scarcer than Guards, resulting in bad weight
6606 recommendations. Now we compute them using new constraints that
6607 should succeed in all cases. Also alter directory authorities to
6608 not include the bandwidth-weights line if they fail to produce
6609 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
6610 - When weighting bridges during path selection, we used to trust
6611 the bandwidths they provided in their descriptor, only capping them
6612 at 10MB/s. This turned out to be problematic for two reasons:
6613 Bridges could claim to handle a lot more traffic then they
6614 actually would, thus making more clients pick them and have a
6615 pretty effective DoS attack. The other issue is that new bridges
6616 that might not have a good estimate for their bw capacity yet
6617 would not get used at all unless no other bridges are available
6618 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
6620 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
6621 - Ignore cannibalized circuits when recording circuit build times.
6622 This should provide for a minor performance improvement for hidden
6623 service users using 0.2.2.14-alpha, and should remove two spurious
6624 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
6625 - Simplify the logic that causes us to decide if the network is
6626 unavailable for purposes of recording circuit build times. If we
6627 receive no cells whatsoever for the entire duration of a circuit's
6628 full measured lifetime, the network is probably down. Also ignore
6629 one-hop directory fetching circuit timeouts when calculating our
6630 circuit build times. These changes should hopefully reduce the
6631 cases where we see ridiculous circuit build timeouts for people
6632 with spotty wireless connections. Fixes part of bug 1772; bugfix
6634 - Prevent the circuit build timeout from becoming larger than
6635 the maximum build time we have ever seen. Also, prevent the time
6636 period for measurement circuits from becoming larger than twice that
6637 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
6640 - When we run out of directory information such that we can't build
6641 circuits, but then get enough that we can build circuits, log when
6642 we actually construct a circuit, so the user has a better chance of
6643 knowing what's going on. Fixes bug 1362.
6644 - Be more generous with how much bandwidth we'd use up (with
6645 accounting enabled) before entering "soft hibernation". Previously,
6646 we'd refuse new connections and circuits once we'd used up 95% of
6647 our allotment. Now, we use up 95% of our allotment, AND make sure
6648 that we have no more than 500MB (or 3 hours of expected traffic,
6649 whichever is lower) remaining before we enter soft hibernation.
6650 - If we've configured EntryNodes and our network goes away and/or all
6651 our entrynodes get marked down, optimistically retry them all when
6652 a new socks application request appears. Fixes bug 1882.
6653 - Add some more defensive programming for architectures that can't
6654 handle unaligned integer accesses. We don't know of any actual bugs
6655 right now, but that's the best time to fix them. Fixes bug 1943.
6656 - Support line continuations in the torrc config file. If a line
6657 ends with a single backslash character, the newline is ignored, and
6658 the configuration value is treated as continuing on the next line.
6661 o Minor bugfixes (on 0.2.1.x and earlier):
6662 - For bandwidth accounting, calculate our expected bandwidth rate
6663 based on the time during which we were active and not in
6664 soft-hibernation during the last interval. Previously, we were
6665 also considering the time spent in soft-hibernation. If this
6666 was a long time, we would wind up underestimating our bandwidth
6667 by a lot, and skewing our wakeup time towards the start of the
6668 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
6670 o Minor bugfixes (on 0.2.2.x):
6671 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
6672 which were disabled by the circuit build timeout changes in
6673 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
6674 - Make sure we don't warn about missing bandwidth weights when
6675 choosing bridges or other relays not in the consensus. Bugfix on
6676 0.2.2.10-alpha; fixes bug 1805.
6677 - In our logs, do not double-report signatures from unrecognized
6678 authorities both as "from unknown authority" and "not
6679 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
6682 Changes in version 0.2.2.16-alpha - 2010-09-17
6683 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
6684 evident at exit relays), and also continues to resolve all the little
6685 bugs that have been filling up trac lately.
6687 o Major bugfixes (stream-level fairness):
6688 - When receiving a circuit-level SENDME for a blocked circuit, try
6689 to package cells fairly from all the streams that had previously
6690 been blocked on that circuit. Previously, we had started with the
6691 oldest stream, and allowed each stream to potentially exhaust
6692 the circuit's package window. This gave older streams on any
6693 given circuit priority over newer ones. Fixes bug 1937. Detected
6694 originally by Camilo Viecco. This bug was introduced before the
6695 first Tor release, in svn commit r152: it is the new winner of
6696 the longest-lived bug prize.
6697 - When the exit relay got a circuit-level sendme cell, it started
6698 reading on the exit streams, even if had 500 cells queued in the
6699 circuit queue already, so the circuit queue just grew and grew in
6700 some cases. We fix this by not re-enabling reading on receipt of a
6701 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
6702 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
6704 - Newly created streams were allowed to read cells onto circuits,
6705 even if the circuit's cell queue was blocked and waiting to drain.
6706 This created potential unfairness, as older streams would be
6707 blocked, but newer streams would gladly fill the queue completely.
6708 We add code to detect this situation and prevent any stream from
6709 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
6713 - Update to the September 1 2010 Maxmind GeoLite Country database.
6714 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
6715 not. This would lead to a cookie that is still not group readable.
6716 Closes bug 1843. Suggested by katmagic.
6717 - When logging a rate-limited warning, we now mention how many messages
6718 got suppressed since the last warning.
6719 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
6720 do individual connection-level rate limiting of clients. The torrc
6721 config options with the same names trump the consensus params, if
6722 both are present. Replaces the old "bwconnrate" and "bwconnburst"
6723 consensus params which were broken from 0.2.2.7-alpha through
6724 0.2.2.14-alpha. Closes bug 1947.
6725 - When a router changes IP address or port, authorities now launch
6726 a new reachability test for it. Implements ticket 1899.
6727 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
6728 2 no signature, 4 required" messages about consensus signatures
6729 easier to read, and make sure they get logged at the same severity
6730 as the messages explaining which keys are which. Fixes bug 1290.
6731 - Don't warn when we have a consensus that we can't verify because
6732 of missing certificates, unless those certificates are ones
6733 that we have been trying and failing to download. Fixes bug 1145.
6734 - If you configure your bridge with a known identity fingerprint,
6735 and the bridge authority is unreachable (as it is in at least
6736 one country now), fall back to directly requesting the descriptor
6737 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
6739 - When building with --enable-gcc-warnings on OpenBSD, disable
6740 warnings in system headers. This makes --enable-gcc-warnings
6741 pass on OpenBSD 4.8.
6743 o Minor bugfixes (on 0.2.1.x and earlier):
6744 - Authorities will now attempt to download consensuses if their
6745 own efforts to make a live consensus have failed. This change
6746 means authorities that restart will fetch a valid consensus, and
6747 it means authorities that didn't agree with the current consensus
6748 will still fetch and serve it if it has enough signatures. Bugfix
6749 on 0.2.0.9-alpha; fixes bug 1300.
6750 - Ensure DNS requests launched by "RESOLVE" commands from the
6751 controller respect the __LeaveStreamsUnattached setconf options. The
6752 same goes for requests launched via DNSPort or transparent
6753 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
6754 - Allow handshaking OR connections to take a full KeepalivePeriod
6755 seconds to handshake. Previously, we would close them after
6756 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
6757 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
6759 - Rate-limit "Failed to hand off onionskin" warnings.
6760 - Never relay a cell for a circuit we have already destroyed.
6761 Between marking a circuit as closeable and finally closing it,
6762 it may have been possible for a few queued cells to get relayed,
6763 even though they would have been immediately dropped by the next
6764 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
6765 - Never queue a cell for a circuit that's already been marked
6767 - Never vote for a server as "Running" if we have a descriptor for
6768 it claiming to be hibernating, and that descriptor was published
6769 more recently than our last contact with the server. Bugfix on
6770 0.2.0.3-alpha; fixes bug 911.
6771 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
6774 o Minor bugfixes (on 0.2.2.x):
6775 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
6776 down if a directory fetch fails and you've configured either
6777 bridges or EntryNodes. The intent was to mark the relay as down
6778 _unless_ you're using bridges or EntryNodes, since if you are
6779 then you could quickly run out of entry points.
6780 - Fix the Windows directory-listing code. A bug introduced in
6781 0.2.2.14-alpha could make Windows directory servers forget to load
6782 some of their cached v2 networkstatus files.
6783 - Really allow clients to use relays as bridges. Fixes bug 1776;
6784 bugfix on 0.2.2.15-alpha.
6785 - Demote a warn to info that happens when the CellStatistics option
6786 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
6787 Reported by Moritz Bartl.
6788 - On Windows, build correctly either with or without Unicode support.
6789 This is necessary so that Tor can support fringe platforms like
6790 Windows 98 (which has no Unicode), or Windows CE (which has no
6791 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
6794 - Add a unit test for cross-platform directory-listing code.
6797 Changes in version 0.2.2.15-alpha - 2010-08-18
6798 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
6799 fixes a variety of other bugs that were preventing performance
6800 experiments from moving forward, fixes several bothersome memory leaks,
6801 and generally closes a lot of smaller bugs that have been filling up
6805 - Stop assigning the HSDir flag to relays that disable their
6806 DirPort (and thus will refuse to answer directory requests). This
6807 fix should dramatically improve the reachability of hidden services:
6808 hidden services and hidden service clients pick six HSDir relays
6809 to store and retrieve the hidden service descriptor, and currently
6810 about half of the HSDir relays will refuse to work. Bugfix on
6811 0.2.0.10-alpha; fixes part of bug 1693.
6812 - The PerConnBWRate and Burst config options, along with the
6813 bwconnrate and bwconnburst consensus params, initialized each conn's
6814 token bucket values only when the connection is established. Now we
6815 update them if the config options change, and update them every time
6816 we get a new consensus. Otherwise we can encounter an ugly edge
6817 case where we initialize an OR conn to client-level bandwidth,
6818 but then later the relay joins the consensus and we leave it
6819 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
6820 - Fix a regression that caused Tor to rebind its ports if it receives
6821 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
6824 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
6825 should give us approximately 40-50% more Guard-flagged nodes,
6826 improving the anonymity the Tor network can provide and also
6827 decreasing the dropoff in throughput that relays experience when
6828 they first get the Guard flag.
6829 - Allow enabling or disabling the *Statistics config options while
6833 - Update to the August 1 2010 Maxmind GeoLite Country database.
6834 - Have the controller interface give a more useful message than
6835 "Internal Error" in response to failed GETINFO requests.
6836 - Warn when the same option is provided more than once in a torrc
6837 file, on the command line, or in a single SETCONF statement, and
6838 the option is one that only accepts a single line. Closes bug 1384.
6839 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
6840 Patch from mingw-san.
6841 - Add support for the country code "{??}" in torrc options like
6842 ExcludeNodes, to indicate all routers of unknown country. Closes
6844 - Relays report the number of bytes spent on answering directory
6845 requests in extra-info descriptors similar to {read,write}-history.
6846 Implements enhancement 1790.
6848 o Minor bugfixes (on 0.2.1.x and earlier):
6849 - Complain if PublishServerDescriptor is given multiple arguments that
6850 include 0 or 1. This configuration will be rejected in the future.
6851 Bugfix on 0.2.0.1-alpha; closes bug 1107.
6852 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
6853 Bugfix on 0.2.0.13-alpha; closes bug 928.
6854 - Change "Application request when we're believed to be offline."
6855 notice to "Application request when we haven't used client
6856 functionality lately.", to clarify that it's not an error. Bugfix
6857 on 0.0.9.3; fixes bug 1222.
6858 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
6859 would return "551 Internal error" rather than "552 Unrecognized key
6860 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
6861 - Users can't configure a regular relay to be their bridge. It didn't
6862 work because when Tor fetched the bridge descriptor, it found
6863 that it already had it, and didn't realize that the purpose of the
6864 descriptor had changed. Now we replace routers with a purpose other
6865 than bridge with bridge descriptors when fetching them. Bugfix on
6866 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
6867 refetch the descriptor with router purpose 'general', disabling
6869 - Fix a rare bug in rend_fn unit tests: we would fail a test when
6870 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
6871 on 0.2.0.10-alpha; fixes bug 1808.
6872 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
6873 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
6874 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
6875 Servers can start sending this code when enough clients recognize
6876 it. Also update the spec to reflect this new reason. Bugfix on
6877 0.1.0.1-rc; fixes part of bug 1793.
6878 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
6879 when we switch from being a public relay to a bridge. Otherwise
6880 there will still be clients that see the relay in their consensus,
6881 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
6883 - Instead of giving an assertion failure on an internal mismatch
6884 on estimated freelist size, just log a BUG warning and try later.
6885 Mitigates but does not fix bug 1125.
6886 - Fix an assertion failure that could occur in caches or bridge users
6887 when using a very short voting interval on a testing network.
6888 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
6890 o Minor bugfixes (on 0.2.2.x):
6891 - Alter directory authorities to always consider Exit-flagged nodes
6892 as potential Guard nodes in their votes. The actual decision to
6893 use Exits as Guards is done in the consensus bandwidth weights.
6894 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
6895 - When the controller is reporting the purpose of circuits that
6896 didn't finish building before the circuit build timeout, it was
6897 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
6898 - Our libevent version parsing code couldn't handle versions like
6899 1.4.14b-stable and incorrectly warned the user about using an
6900 old and broken version of libevent. Treat 1.4.14b-stable like
6901 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
6903 - Don't use substitution references like $(VAR:MOD) when
6904 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
6905 '$(:x)' to 'x' rather than the empty string. This bites us in
6906 doc/ when configured with --disable-asciidoc. Bugfix on
6907 0.2.2.9-alpha; fixes bug 1773.
6908 - Remove a spurious hidden service server-side log notice about
6909 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
6911 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
6913 - Correctly report written bytes on linked connections. Found while
6914 implementing 1790. Bugfix on 0.2.2.4-alpha.
6915 - Fix three memory leaks: one in circuit_build_times_parse_state(),
6916 one in dirvote_add_signatures_to_pending_consensus(), and one every
6917 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
6918 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
6920 o Code simplifications and refactoring:
6921 - Take a first step towards making or.h smaller by splitting out
6922 function definitions for all source files in src/or/. Leave
6923 structures and defines in or.h for now.
6924 - Remove a bunch of unused function declarations as well as a block of
6925 #if 0'd code from the unit tests. Closes bug 1824.
6926 - New unit tests for exit-port history statistics; refactored exit
6927 statistics code to be more easily tested.
6928 - Remove the old debian/ directory from the main Tor distribution.
6929 The official Tor-for-debian git repository lives at the URL
6930 https://git.torproject.org/debian/tor.git
6933 Changes in version 0.2.2.14-alpha - 2010-07-12
6934 Tor 0.2.2.14-alpha greatly improves client-side handling of
6935 circuit build timeouts, which are used to estimate speed and improve
6936 performance. We also move to a much better GeoIP database, port Tor to
6937 Windows CE, introduce new compile flags that improve code security,
6938 add an eighth v3 directory authority, and address a lot of more
6942 - Tor directory authorities no longer crash when started with a
6943 cached-microdesc-consensus file in their data directory. Bugfix
6944 on 0.2.2.6-alpha; fixes bug 1532.
6945 - Treat an unset $HOME like an empty $HOME rather than triggering an
6946 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
6947 - Ignore negative and large circuit build timeout values that can
6948 happen during a suspend or hibernate. These values caused various
6949 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
6950 - Alter calculation of Pareto distribution parameter 'Xm' for
6951 Circuit Build Timeout learning to use the weighted average of the
6952 top N=3 modes (because we have three entry guards). Considering
6953 multiple modes should improve the timeout calculation in some cases,
6954 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
6956 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
6957 right censored distribution model. This approach improves over the
6958 synthetic timeout generation approach that was producing insanely
6959 high timeout values. Now we calculate build timeouts using truncated
6960 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
6961 - Do not close circuits that are under construction when they reach
6962 the circuit build timeout. Instead, leave them building (but do not
6963 use them) for up until the time corresponding to the 95th percentile
6964 on the Pareto CDF or 60 seconds, whichever is greater. This is done
6965 to provide better data for the new Pareto model. This percentile
6966 can be controlled by the consensus.
6969 - Move to the June 2010 Maxmind GeoLite country db (rather than the
6970 June 2009 ip-to-country GeoIP db) for our statistics that count
6971 how many users relays are seeing from each country. Now we have
6972 more accurate data for many African countries.
6973 - Port Tor to build and run correctly on Windows CE systems, using
6974 the wcecompat library. Contributed by Valerio Lupi.
6975 - New "--enable-gcc-hardening" ./configure flag (off by default)
6976 to turn on gcc compile time hardening options. It ensures
6977 that signed ints have defined behavior (-fwrapv), enables
6978 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
6979 with canaries (-fstack-protector-all), turns on ASLR protection if
6980 supported by the kernel (-fPIE, -pie), and adds additional security
6981 related warnings. Verified to work on Mac OS X and Debian Lenny.
6982 - New "--enable-linker-hardening" ./configure flag (off by default)
6983 to turn on ELF specific hardening features (relro, now). This does
6984 not work with Mac OS X or any other non-ELF binary format.
6986 o New directory authorities:
6987 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
6991 - New config option "WarnUnsafeSocks 0" disables the warning that
6992 occurs whenever Tor receives a socks handshake using a version of
6993 the socks protocol that can only provide an IP address (rather
6994 than a hostname). Setups that do DNS locally over Tor are fine,
6995 and we shouldn't spam the logs in that case.
6996 - Convert the HACKING file to asciidoc, and add a few new sections
6997 to it, explaining how we use Git, how we make changelogs, and
6998 what should go in a patch.
6999 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
7000 event, to give information on the current rate of circuit timeouts
7001 over our stored history.
7002 - Add ability to disable circuit build time learning via consensus
7003 parameter and via a LearnCircuitBuildTimeout config option. Also
7004 automatically disable circuit build time calculation if we are
7005 either a AuthoritativeDirectory, or if we fail to write our state
7006 file. Fixes bug 1296.
7007 - More gracefully handle corrupt state files, removing asserts
7008 in favor of saving a backup and resetting state.
7009 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
7013 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
7015 - When a2x fails, mention that the user could disable manpages instead
7016 of trying to fix their asciidoc installation.
7017 - Where available, use Libevent 2.0's periodic timers so that our
7018 once-per-second cleanup code gets called even more closely to
7019 once per second than it would otherwise. Fixes bug 943.
7020 - If you run a bridge that listens on multiple IP addresses, and
7021 some user configures a bridge address that uses a different IP
7022 address than your bridge writes in its router descriptor, and the
7023 user doesn't specify an identity key, their Tor would discard the
7024 descriptor because "it isn't one of our configured bridges", and
7025 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
7026 Bugfix on 0.2.0.3-alpha.
7027 - If OpenSSL fails to make a duplicate of a private or public key, log
7028 an error message and try to exit cleanly. May help with debugging
7029 if bug 1209 ever remanifests.
7030 - Save a couple bytes in memory allocation every time we escape
7031 certain characters in a string. Patch from Florian Zumbiehl.
7032 - Make it explicit that we don't cannibalize one-hop circuits. This
7033 happens in the wild, but doesn't turn out to be a problem because
7034 we fortunately don't use those circuits. Many thanks to outofwords
7035 for the initial analysis and to swissknife who confirmed that
7036 two-hop circuits are actually created.
7037 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
7038 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
7039 - Eliminate a case where a circuit build time warning was displayed
7040 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
7043 Changes in version 0.2.1.26 - 2010-05-02
7044 Tor 0.2.1.26 addresses the recent connection and memory overload
7045 problems we've been seeing on relays, especially relays with their
7046 DirPort open. If your relay has been crashing, or you turned it off
7047 because it used too many resources, give this release a try.
7049 This release also fixes yet another instance of broken OpenSSL libraries
7050 that was causing some relays to drop out of the consensus.
7053 - Teach relays to defend themselves from connection overload. Relays
7054 now close idle circuits early if it looks like they were intended
7055 for directory fetches. Relays are also more aggressive about closing
7056 TLS connections that have no circuits on them. Such circuits are
7057 unlikely to be re-used, and tens of thousands of them were piling
7058 up at the fast relays, causing the relays to run out of sockets
7059 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
7060 their directory fetches over TLS).
7061 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
7062 that claim to be earlier than 0.9.8m, but which have in reality
7063 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
7064 behavior. Possible fix for some cases of bug 1346.
7065 - Directory mirrors were fetching relay descriptors only from v2
7066 directory authorities, rather than v3 authorities like they should.
7067 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
7068 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
7071 - Finally get rid of the deprecated and now harmful notion of "clique
7072 mode", where directory authorities maintain TLS connections to
7076 - In the util/threads test, no longer free the test_mutex before all
7077 worker threads have finished. Bugfix on 0.2.1.6-alpha.
7078 - The master thread could starve the worker threads quite badly on
7079 certain systems, causing them to run only partially in the allowed
7080 window. This resulted in test failures. Now the master thread sleeps
7081 occasionally for a few microseconds while the two worker-threads
7082 compete for the mutex. Bugfix on 0.2.0.1-alpha.
7085 Changes in version 0.2.2.13-alpha - 2010-04-24
7086 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
7087 problems we've been seeing on relays, especially relays with their
7088 DirPort open. If your relay has been crashing, or you turned it off
7089 because it used too many resources, give this release a try.
7092 - Teach relays to defend themselves from connection overload. Relays
7093 now close idle circuits early if it looks like they were intended
7094 for directory fetches. Relays are also more aggressive about closing
7095 TLS connections that have no circuits on them. Such circuits are
7096 unlikely to be re-used, and tens of thousands of them were piling
7097 up at the fast relays, causing the relays to run out of sockets
7098 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
7099 their directory fetches over TLS).
7102 - Finally get rid of the deprecated and now harmful notion of "clique
7103 mode", where directory authorities maintain TLS connections to
7105 - Directory authorities now do an immediate reachability check as soon
7106 as they hear about a new relay. This change should slightly reduce
7107 the time between setting up a relay and getting listed as running
7108 in the consensus. It should also improve the time between setting
7109 up a bridge and seeing use by bridge users.
7110 - Directory authorities no longer launch a TLS connection to every
7111 relay as they startup. Now that we have 2k+ descriptors cached,
7112 the resulting network hiccup is becoming a burden. Besides,
7113 authorities already avoid voting about Running for the first half
7114 hour of their uptime.
7117 Changes in version 0.2.2.12-alpha - 2010-04-20
7118 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
7119 handle and vote on descriptors. It was causing relays to drop out of
7123 - Many relays have been falling out of the consensus lately because
7124 not enough authorities know about their descriptor for them to get
7125 a majority of votes. When we deprecated the v2 directory protocol,
7126 we got rid of the only way that v3 authorities can hear from each
7127 other about other descriptors. Now authorities examine every v3
7128 vote for new descriptors, and fetch them from that authority. Bugfix
7130 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
7131 and a warning in or.h related to bandwidth_weight_rule_t that
7132 prevented clean compile on OS X. Fixes bug 1363; bugfix on
7134 - Fix a segfault on relays when DirReqStatistics is enabled
7135 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
7139 - Demote a confusing TLS warning that relay operators might get when
7140 someone tries to talk to their OrPort. It is neither the operator's
7141 fault nor can they do anything about it. Fixes bug 1364; bugfix
7145 Changes in version 0.2.2.11-alpha - 2010-04-15
7146 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
7147 libraries that was causing some relays to drop out of the consensus.
7150 - Directory mirrors were fetching relay descriptors only from v2
7151 directory authorities, rather than v3 authorities like they should.
7152 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
7153 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
7154 - Fix a parsing error that made every possible value of
7155 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
7156 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
7157 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
7158 about the option without breaking older ones.
7159 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
7160 that claim to be earlier than 0.9.8m, but which have in reality
7161 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
7162 behavior. Possible fix for some cases of bug 1346.
7165 - Experiment with a more aggressive approach to preventing clients
7166 from making one-hop exit streams. Exit relays who want to try it
7167 out can set "RefuseUnknownExits 1" in their torrc, and then look
7168 for "Attempt by %s to open a stream" log messages. Let us know
7170 - Add support for statically linking zlib by specifying
7171 --enable-static-zlib, to go with our support for statically linking
7172 openssl and libevent. Resolves bug 1358.
7175 - Fix a segfault that happens whenever a Tor client that is using
7176 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
7178 - When we cleaned up the contrib/tor-exit-notice.html file, we left
7179 out the first line. Fixes bug 1295.
7180 - When building the manpage from a tarball, we required asciidoc, but
7181 the asciidoc -> roff/html conversion was already done for the
7182 tarball. Make 'make' complain only when we need asciidoc (either
7183 because we're compiling directly from git, or because we altered
7184 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
7185 - When none of the directory authorities vote on any params, Tor
7186 segfaulted when trying to make the consensus from the votes. We
7187 didn't trigger the bug in practice, because authorities do include
7188 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
7191 - In the util/threads test, no longer free the test_mutex before all
7192 worker threads have finished. Bugfix on 0.2.1.6-alpha.
7193 - The master thread could starve the worker threads quite badly on
7194 certain systems, causing them to run only partially in the allowed
7195 window. This resulted in test failures. Now the master thread sleeps
7196 occasionally for a few microseconds while the two worker-threads
7197 compete for the mutex. Bugfix on 0.2.0.1-alpha.
7200 Changes in version 0.2.2.10-alpha - 2010-03-07
7201 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
7202 could prevent relays from guessing their IP address correctly. It also
7203 starts the groundwork for another client-side performance boost, since
7204 currently we're not making efficient use of relays that have both the
7205 Guard flag and the Exit flag.
7208 - Fix a regression from our patch for bug 1244 that caused relays
7209 to guess their IP address incorrectly if they didn't set Address
7210 in their torrc and/or their address fails to resolve. Bugfix on
7211 0.2.2.9-alpha; fixes bug 1269.
7213 o Major features (performance):
7214 - Directory authorities now compute consensus weightings that instruct
7215 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
7216 and no flag. Clients that use these weightings will distribute
7217 network load more evenly across these different relay types. The
7218 weightings are in the consensus so we can change them globally in
7219 the future. Extra thanks to "outofwords" for finding some nasty
7220 security bugs in the first implementation of this feature.
7222 o Minor features (performance):
7223 - Always perform router selections using weighted relay bandwidth,
7224 even if we don't need a high capacity circuit at the time. Non-fast
7225 circuits now only differ from fast ones in that they can use relays
7226 not marked with the Fast flag. This "feature" could turn out to
7227 be a horrible bug; we should investigate more before it goes into
7231 - Allow disabling building of the manpages. Skipping the manpage
7232 speeds up the build considerably.
7234 o Minor bugfixes (on 0.2.2.x):
7235 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
7236 Bugfix on 0.2.2.9-alpha.
7237 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
7238 config option. Bugfix on 0.2.2.7-alpha.
7239 - Ship the asciidoc-helper file in the tarball, so that people can
7240 build from source if they want to, and touching the .1.txt files
7241 doesn't break the build. Bugfix on 0.2.2.9-alpha.
7243 o Minor bugfixes (on 0.2.1.x or earlier):
7244 - Fix a dereference-then-NULL-check sequence when publishing
7245 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
7247 - Fix another dereference-then-NULL-check sequence. Bugfix on
7248 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
7249 - Make sure we treat potentially not NUL-terminated strings correctly.
7250 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
7252 o Code simplifications and refactoring:
7253 - Fix some urls in the exit notice file and make it XHTML1.1 strict
7254 compliant. Based on a patch from Christian Kujau.
7255 - Don't use sed in asciidoc-helper anymore.
7256 - Make the build process fail if asciidoc cannot be found and
7257 building with asciidoc isn't disabled.
7260 Changes in version 0.2.2.9-alpha - 2010-02-22
7261 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
7262 location of a directory authority, and cleans up a bunch of small bugs.
7264 o Directory authority changes:
7265 - Change IP address for dannenberg (v3 directory authority), and
7266 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
7267 service directory authority) from the list.
7270 - Make Tor work again on the latest OS X: when deciding whether to
7271 use strange flags to turn TLS renegotiation on, detect the OpenSSL
7272 version at run-time, not compile time. We need to do this because
7273 Apple doesn't update its dev-tools headers when it updates its
7274 libraries in a security patch.
7275 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
7276 that could happen on 32-bit platforms with 64-bit time_t. Also fix
7277 a memory leak when requesting a hidden service descriptor we've
7278 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
7280 - Authorities could be tricked into giving out the Exit flag to relays
7281 that didn't allow exiting to any ports. This bug could screw
7282 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
7283 1238. Bug discovered by Martin Kowalczyk.
7284 - When freeing a session key, zero it out completely. We only zeroed
7285 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
7286 patched by ekir. Fixes bug 1254.
7289 - Fix static compilation by listing the openssl libraries in the right
7290 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
7291 - Resume handling .exit hostnames in a special way: originally we
7292 stripped the .exit part and used the requested exit relay. In
7293 0.2.2.1-alpha we stopped treating them in any special way, meaning
7294 if you use a .exit address then Tor will pass it on to the exit
7295 relay. Now we reject the .exit stream outright, since that behavior
7296 might be more expected by the user. Found and diagnosed by Scott
7297 Bennett and Downie on or-talk.
7298 - Don't spam the controller with events when we have no file
7299 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
7300 for log messages was already solved from bug 748.)
7301 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
7303 - Make the DNSPort option work with libevent 2.x. Don't alter the
7304 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
7305 - Emit a GUARD DROPPED controller event for a case we missed.
7306 - Make more fields in the controller protocol case-insensitive, since
7307 control-spec.txt said they were.
7308 - Refactor resolve_my_address() to not use gethostbyname() anymore.
7309 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
7310 - Fix a spec conformance issue: the network-status-version token
7311 must be the first token in a v3 consensus or vote. Discovered by
7312 parakeep. Bugfix on 0.2.0.3-alpha.
7314 o Code simplifications and refactoring:
7315 - Generate our manpage and HTML documentation using Asciidoc. This
7316 change should make it easier to maintain the documentation, and
7318 - Remove the --enable-iphone option. According to reports from Marco
7319 Bonetti, Tor builds fine without any special tweaking on recent
7320 iPhone SDK versions.
7321 - Removed some unnecessary files from the source distribution. The
7322 AUTHORS file has now been merged into the people page on the
7323 website. The roadmaps and design doc can now be found in the
7324 projects directory in svn.
7325 - Enabled various circuit build timeout constants to be controlled
7326 by consensus parameters. Also set better defaults for these
7327 parameters based on experimentation on broadband and simulated
7331 - The 'EXTENDCIRCUIT' control port command can now be used with
7332 a circ id of 0 and no path. This feature will cause Tor to build
7333 a new 'fast' general purpose circuit using its own path selection
7335 - Added a BUILDTIMEOUT_SET controller event to describe changes
7336 to the circuit build timeout.
7337 - Future-proof the controller protocol a bit by ignoring keyword
7338 arguments we do not recognize.
7339 - Expand homedirs passed to tor-checkkey. This should silence a
7340 coverity complaint about passing a user-supplied string into
7341 open() without checking it.
7344 Changes in version 0.2.1.25 - 2010-03-16
7345 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
7346 prevent relays from guessing their IP address correctly. It also fixes
7347 several minor potential security bugs.
7350 - Fix a regression from our patch for bug 1244 that caused relays
7351 to guess their IP address incorrectly if they didn't set Address
7352 in their torrc and/or their address fails to resolve. Bugfix on
7353 0.2.1.23; fixes bug 1269.
7354 - When freeing a session key, zero it out completely. We only zeroed
7355 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
7356 patched by ekir. Fixes bug 1254.
7359 - Fix a dereference-then-NULL-check sequence when publishing
7360 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
7362 - Fix another dereference-then-NULL-check sequence. Bugfix on
7363 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
7364 - Make sure we treat potentially not NUL-terminated strings correctly.
7365 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
7369 Changes in version 0.2.1.24 - 2010-02-21
7370 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
7374 - Work correctly out-of-the-box with even more vendor-patched versions
7375 of OpenSSL. In particular, make it so Debian and OS X don't need
7376 customized patches to run/build.
7379 Changes in version 0.2.1.23 - 2010-02-13
7380 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
7381 again on the latest OS X, and updates the location of a directory
7384 o Major bugfixes (performance):
7385 - We were selecting our guards uniformly at random, and then weighting
7386 which of our guards we'd use uniformly at random. This imbalance
7387 meant that Tor clients were severely limited on throughput (and
7388 probably latency too) by the first hop in their circuit. Now we
7389 select guards weighted by currently advertised bandwidth. We also
7390 automatically discard guards picked using the old algorithm. Fixes
7391 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
7394 - Make Tor work again on the latest OS X: when deciding whether to
7395 use strange flags to turn TLS renegotiation on, detect the OpenSSL
7396 version at run-time, not compile time. We need to do this because
7397 Apple doesn't update its dev-tools headers when it updates its
7398 libraries in a security patch.
7399 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
7400 that could happen on 32-bit platforms with 64-bit time_t. Also fix
7401 a memory leak when requesting a hidden service descriptor we've
7402 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
7405 o Directory authority changes:
7406 - Change IP address for dannenberg (v3 directory authority), and
7407 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
7408 service directory authority) from the list.
7411 - Refactor resolve_my_address() to not use gethostbyname() anymore.
7412 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
7415 - Avoid a mad rush at the beginning of each month when each client
7416 rotates half of its guards. Instead we spread the rotation out
7417 throughout the month, but we still avoid leaving a precise timestamp
7418 in the state file about when we first picked the guard. Improves
7419 over the behavior introduced in 0.1.2.17.
7422 Changes in version 0.2.2.8-alpha - 2010-01-26
7423 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
7424 causing bridge relays to disappear. If you're running a bridge,
7428 - Fix a memory corruption bug on bridges that occured during the
7429 inclusion of stats data in extra-info descriptors. Also fix the
7430 interface for geoip_get_bridge_stats* to prevent similar bugs in
7431 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
7432 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
7435 - Ignore OutboundBindAddress when connecting to localhost.
7436 Connections to localhost need to come _from_ localhost, or else
7437 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
7441 Changes in version 0.2.2.7-alpha - 2010-01-19
7442 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
7443 as laying the groundwork for further relay-side performance fixes. It
7444 also starts cleaning up client behavior with respect to the EntryNodes,
7445 ExitNodes, and StrictNodes config options.
7447 This release also rotates two directory authority keys, due to a
7448 security breach of some of the Torproject servers.
7450 o Directory authority changes:
7451 - Rotate keys (both v3 identity and relay identity) for moria1
7454 o Major features (performance):
7455 - We were selecting our guards uniformly at random, and then weighting
7456 which of our guards we'd use uniformly at random. This imbalance
7457 meant that Tor clients were severely limited on throughput (and
7458 probably latency too) by the first hop in their circuit. Now we
7459 select guards weighted by currently advertised bandwidth. We also
7460 automatically discard guards picked using the old algorithm. Fixes
7461 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
7462 - When choosing which cells to relay first, relays can now favor
7463 circuits that have been quiet recently, to provide lower latency
7464 for low-volume circuits. By default, relays enable or disable this
7465 feature based on a setting in the consensus. You can override
7466 this default by using the new "CircuitPriorityHalflife" config
7467 option. Design and code by Ian Goldberg, Can Tang, and Chris
7469 - Add separate per-conn write limiting to go with the per-conn read
7470 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
7471 but never per-conn write limits.
7472 - New consensus params "bwconnrate" and "bwconnburst" to let us
7473 rate-limit client connections as they enter the network. It's
7474 controlled in the consensus so we can turn it on and off for
7475 experiments. It's starting out off. Based on proposal 163.
7477 o Major features (relay selection options):
7478 - Switch to a StrictNodes config option, rather than the previous
7479 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
7480 "StrictExcludeNodes" option.
7481 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
7482 change during a config reload, mark and discard all our origin
7483 circuits. This fix should address edge cases where we change the
7484 config options and but then choose a circuit that we created before
7486 - If EntryNodes or ExitNodes are set, be more willing to use an
7487 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
7489 - Make EntryNodes config option much more aggressive even when
7490 StrictNodes is not set. Before it would prepend your requested
7491 entrynodes to your list of guard nodes, but feel free to use others
7492 after that. Now it chooses only from your EntryNodes if any of
7493 those are available, and only falls back to others if a) they're
7494 all down and b) StrictNodes is not set.
7495 - Now we refresh your entry guards from EntryNodes at each consensus
7496 fetch -- rather than just at startup and then they slowly rot as
7497 the network changes.
7500 - Stop bridge directory authorities from answering dbg-stability.txt
7501 directory queries, which would let people fetch a list of all
7502 bridge identities they track. Bugfix on 0.2.1.6-alpha.
7505 - Log a notice when we get a new control connection. Now it's easier
7506 for security-conscious users to recognize when a local application
7507 is knocking on their controller door. Suggested by bug 1196.
7508 - New config option "CircuitStreamTimeout" to override our internal
7509 timeout schedule for how many seconds until we detach a stream from
7510 a circuit and try a new circuit. If your network is particularly
7511 slow, you might want to set this to a number like 60.
7512 - New controller command "getinfo config-text". It returns the
7513 contents that Tor would write if you send it a SAVECONF command,
7514 so the controller can write the file to disk itself.
7515 - New options for SafeLogging to allow scrubbing only log messages
7516 generated while acting as a relay.
7517 - Ship the bridges spec file in the tarball too.
7518 - Avoid a mad rush at the beginning of each month when each client
7519 rotates half of its guards. Instead we spread the rotation out
7520 throughout the month, but we still avoid leaving a precise timestamp
7521 in the state file about when we first picked the guard. Improves
7522 over the behavior introduced in 0.1.2.17.
7524 o Minor bugfixes (compiling):
7525 - Fix compilation on OS X 10.3, which has a stub mlockall() but
7526 hides it. Bugfix on 0.2.2.6-alpha.
7527 - Fix compilation on Solaris by removing support for the
7528 DisableAllSwap config option. Solaris doesn't have an rlimit for
7529 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
7532 o Minor bugfixes (crashes):
7533 - Do not segfault when writing buffer stats when we haven't observed
7534 a single circuit to report about. Found by Fabian Lanze. Bugfix on
7536 - If we're in the pathological case where there's no exit bandwidth
7537 but there is non-exit bandwidth, or no guard bandwidth but there
7538 is non-guard bandwidth, don't crash during path selection. Bugfix
7540 - Fix an impossible-to-actually-trigger buffer overflow in relay
7541 descriptor generation. Bugfix on 0.1.0.15.
7543 o Minor bugfixes (privacy):
7544 - Fix an instance where a Tor directory mirror might accidentally
7545 log the IP address of a misbehaving Tor client. Bugfix on
7547 - Don't list Windows capabilities in relay descriptors. We never made
7548 use of them, and maybe it's a bad idea to publish them. Bugfix
7551 o Minor bugfixes (other):
7552 - Resolve an edge case in path weighting that could make us misweight
7553 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
7554 - Fix statistics on client numbers by country as seen by bridges that
7555 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
7556 intervals instead of variable 12-to-48-hour intervals.
7557 - After we free an internal connection structure, overwrite it
7558 with a different memory value than we use for overwriting a freed
7559 internal circuit structure. Should help with debugging. Suggested
7561 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
7565 - Remove the HSAuthorityRecordStats option that version 0 hidden
7566 service authorities could have used to track statistics of overall
7567 hidden service usage.
7570 Changes in version 0.2.1.22 - 2010-01-19
7571 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
7572 authorities -- it would tell you its whole history of bridge descriptors
7573 if you make the right directory request. This stable update also
7574 rotates two of the seven v3 directory authority keys and locations.
7576 o Directory authority changes:
7577 - Rotate keys (both v3 identity and relay identity) for moria1
7581 - Stop bridge directory authorities from answering dbg-stability.txt
7582 directory queries, which would let people fetch a list of all
7583 bridge identities they track. Bugfix on 0.2.1.6-alpha.
7586 Changes in version 0.2.1.21 - 2009-12-21
7587 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
7588 library. If you use Tor on Linux / Unix and you're getting SSL
7589 renegotiation errors, upgrading should help. We also recommend an
7590 upgrade if you're an exit relay.
7593 - Work around a security feature in OpenSSL 0.9.8l that prevents our
7594 handshake from working unless we explicitly tell OpenSSL that we
7595 are using SSL renegotiation safely. We are, of course, but OpenSSL
7596 0.9.8l won't work unless we say we are.
7597 - Avoid crashing if the client is trying to upload many bytes and the
7598 circuit gets torn down at the same time, or if the flip side
7599 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
7602 - Do not refuse to learn about authority certs and v2 networkstatus
7603 documents that are older than the latest consensus. This bug might
7604 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
7605 Spotted and fixed by xmux.
7606 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
7607 trigger platform-specific option misparsing case found by Coverity
7609 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
7610 trigger assert. Fixes bug 1173.
7613 Changes in version 0.2.2.6-alpha - 2009-11-19
7614 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
7615 support for the new lower-footprint "microdescriptor" directory design,
7616 future-proofing our consensus format against new hash functions or
7617 other changes, and an Android port. It also makes Tor compatible with
7618 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
7621 - Directory authorities can now create, vote on, and serve multiple
7622 parallel formats of directory data as part of their voting process.
7623 Partially implements Proposal 162: "Publish the consensus in
7625 - Directory authorities can now agree on and publish small summaries
7626 of router information that clients can use in place of regular
7627 server descriptors. This transition will eventually allow clients
7628 to use far less bandwidth for downloading information about the
7629 network. Begins the implementation of Proposal 158: "Clients
7630 download consensus + microdescriptors".
7631 - The directory voting system is now extensible to use multiple hash
7632 algorithms for signatures and resource selection. Newer formats
7633 are signed with SHA256, with a possibility for moving to a better
7634 hash algorithm in the future.
7635 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
7636 current and future memory pages via mlockall(). On supported
7637 platforms (modern Linux and probably BSD but not Windows or OS X),
7638 this should effectively disable any and all attempts to page out
7639 memory. This option requires that you start your Tor as root --
7640 if you use DisableAllSwap, please consider using the User option
7641 to properly reduce the privileges of your Tor.
7642 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
7643 to help Tor build correctly for Android phones.
7646 - Work around a security feature in OpenSSL 0.9.8l that prevents our
7647 handshake from working unless we explicitly tell OpenSSL that we
7648 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
7649 won't work unless we say we are.
7652 - Fix a crash bug when trying to initialize the evdns module in
7653 Libevent 2. Bugfix on 0.2.1.16-rc.
7654 - Stop logging at severity 'warn' when some other Tor client tries
7655 to establish a circuit with us using weak DH keys. It's a protocol
7656 violation, but that doesn't mean ordinary users need to hear about
7657 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
7658 - Do not refuse to learn about authority certs and v2 networkstatus
7659 documents that are older than the latest consensus. This bug might
7660 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
7661 Spotted and fixed by xmux.
7662 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
7663 - If all authorities restart at once right before a consensus vote,
7664 nobody will vote about "Running", and clients will get a consensus
7665 with no usable relays. Instead, authorities refuse to build a
7666 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
7667 - If your relay can't keep up with the number of incoming create
7668 cells, it would log one warning per failure into your logs. Limit
7669 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
7670 - Bridges now use "reject *:*" as their default exit policy. Bugfix
7671 on 0.2.0.3-alpha; fixes bug 1113.
7672 - Fix a memory leak on directory authorities during voting that was
7673 introduced in 0.2.2.1-alpha. Found via valgrind.
7676 Changes in version 0.2.1.20 - 2009-10-15
7677 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
7678 services at once, prepares for more performance improvements, and
7679 fixes a bunch of smaller bugs.
7681 The Windows and OS X bundles also include a more recent Vidalia,
7682 and switch from Privoxy to Polipo.
7684 The OS X installers are now drag and drop. It's best to un-install
7685 Tor/Vidalia and then install this new bundle, rather than upgrade. If
7686 you want to upgrade, you'll need to update the paths for Tor and Polipo
7687 in the Vidalia Settings window.
7690 - Send circuit or stream sendme cells when our window has decreased
7691 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
7692 by Karsten when testing the "reduce circuit window" performance
7693 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7694 before the release of Tor 0.0.0. This is the new winner of the
7696 - Fix a remotely triggerable memory leak when a consensus document
7697 contains more than one signature from the same voter. Bugfix on
7699 - Avoid segfault in rare cases when finishing an introduction circuit
7700 as a client and finding out that we don't have an introduction key
7701 for it. Fixes bug 1073. Reported by Aaron Swartz.
7704 - Tor now reads the "circwindow" parameter out of the consensus,
7705 and uses that value for its circuit package window rather than the
7706 default of 1000 cells. Begins the implementation of proposal 168.
7708 o New directory authorities:
7709 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
7711 - Move moria1 and tonga to alternate IP addresses.
7714 - Fix a signed/unsigned compile warning in 0.2.1.19.
7715 - Fix possible segmentation fault on directory authorities. Bugfix on
7717 - Fix an extremely rare infinite recursion bug that could occur if
7718 we tried to log a message after shutting down the log subsystem.
7719 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
7720 - Fix an obscure bug where hidden services on 64-bit big-endian
7721 systems might mis-read the timestamp in v3 introduce cells, and
7722 refuse to connect back to the client. Discovered by "rotor".
7723 Bugfix on 0.2.1.6-alpha.
7724 - We were triggering a CLOCK_SKEW controller status event whenever
7725 we connect via the v2 connection protocol to any relay that has
7726 a wrong clock. Instead, we should only inform the controller when
7727 it's a trusted authority that claims our clock is wrong. Bugfix
7728 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
7729 - We were telling the controller about CHECKING_REACHABILITY and
7730 REACHABILITY_FAILED status events whenever we launch a testing
7731 circuit or notice that one has failed. Instead, only tell the
7732 controller when we want to inform the user of overall success or
7733 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7735 - Don't warn when we're using a circuit that ends with a node
7736 excluded in ExcludeExitNodes, but the circuit is not used to access
7737 the outside world. This should help fix bug 1090. Bugfix on
7739 - Work around a small memory leak in some versions of OpenSSL that
7740 stopped the memory used by the hostname TLS extension from being
7744 - Add a "getinfo status/accepted-server-descriptor" controller
7745 command, which is the recommended way for controllers to learn
7746 whether our server descriptor has been successfully received by at
7747 least on directory authority. Un-recommend good-server-descriptor
7748 getinfo and status events until we have a better design for them.
7751 Changes in version 0.2.2.5-alpha - 2009-10-11
7752 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
7755 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
7757 o Directory authorities:
7758 - Temporarily (just for this release) move dizum to an alternate
7762 Changes in version 0.2.2.4-alpha - 2009-10-10
7763 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
7764 introduces a new unit test framework, shifts directry authority
7765 addresses around to reduce the impact from recent blocking events,
7766 and fixes a few smaller bugs.
7769 - Fix several more asserts in the circuit_build_times code, for
7770 example one that causes Tor to fail to start once we have
7771 accumulated 5000 build times in the state file. Bugfixes on
7772 0.2.2.2-alpha; fixes bug 1108.
7774 o New directory authorities:
7775 - Move moria1 and Tonga to alternate IP addresses.
7778 - Log SSL state transitions at debug level during handshake, and
7779 include SSL states in error messages. This may help debug future
7780 SSL handshake issues.
7781 - Add a new "Handshake" log domain for activities that happen
7782 during the TLS handshake.
7783 - Revert to the "June 3 2009" ip-to-country file. The September one
7784 seems to have removed most US IP addresses.
7785 - Directory authorities now reject Tor relays with versions less than
7786 0.1.2.14. This step cuts out four relays from the current network,
7787 none of which are very big.
7790 - Fix a couple of smaller issues with gathering statistics. Bugfixes
7792 - Fix two memory leaks in the error case of
7793 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
7794 - Don't count one-hop circuits when we're estimating how long it
7795 takes circuits to build on average. Otherwise we'll set our circuit
7796 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
7797 - Directory authorities no longer change their opinion of, or vote on,
7798 whether a router is Running, unless they have themselves been
7799 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
7802 o Code simplifications and refactoring:
7803 - Revise our unit tests to use the "tinytest" framework, so we
7804 can run tests in their own processes, have smarter setup/teardown
7805 code, and so on. The unit test code has moved to its own
7806 subdirectory, and has been split into multiple modules.
7809 Changes in version 0.2.2.3-alpha - 2009-09-23
7810 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
7813 - Fix an overzealous assert in our new circuit build timeout code.
7814 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
7817 - If the networkstatus consensus tells us that we should use a
7818 negative circuit package window, ignore it. Otherwise we'll
7819 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
7822 Changes in version 0.2.2.2-alpha - 2009-09-21
7823 Tor 0.2.2.2-alpha introduces our latest performance improvement for
7824 clients: Tor tracks the average time it takes to build a circuit, and
7825 avoids using circuits that take too long to build. For fast connections,
7826 this feature can cut your expected latency in half. For slow or flaky
7827 connections, it could ruin your Tor experience. Let us know if it does!
7830 - Tor now tracks how long it takes to build client-side circuits
7831 over time, and adapts its timeout to local network performance.
7832 Since a circuit that takes a long time to build will also provide
7833 bad performance, we get significant latency improvements by
7834 discarding the slowest 20% of circuits. Specifically, Tor creates
7835 circuits more aggressively than usual until it has enough data
7836 points for a good timeout estimate. Implements proposal 151.
7837 We are especially looking for reports (good and bad) from users with
7838 both EDGE and broadband connections that can move from broadband
7839 to EDGE and find out if the build-time data in the .tor/state gets
7840 reset without loss of Tor usability. You should also see a notice
7841 log message telling you that Tor has reset its timeout.
7842 - Directory authorities can now vote on arbitary integer values as
7843 part of the consensus process. This is designed to help set
7844 network-wide parameters. Implements proposal 167.
7845 - Tor now reads the "circwindow" parameter out of the consensus,
7846 and uses that value for its circuit package window rather than the
7847 default of 1000 cells. Begins the implementation of proposal 168.
7850 - Fix a remotely triggerable memory leak when a consensus document
7851 contains more than one signature from the same voter. Bugfix on
7855 - Fix an extremely rare infinite recursion bug that could occur if
7856 we tried to log a message after shutting down the log subsystem.
7857 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
7858 - Fix parsing for memory or time units given without a space between
7859 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
7860 - A networkstatus vote must contain exactly one signature. Spec
7861 conformance issue. Bugfix on 0.2.0.3-alpha.
7862 - Fix an obscure bug where hidden services on 64-bit big-endian
7863 systems might mis-read the timestamp in v3 introduce cells, and
7864 refuse to connect back to the client. Discovered by "rotor".
7865 Bugfix on 0.2.1.6-alpha.
7866 - We were triggering a CLOCK_SKEW controller status event whenever
7867 we connect via the v2 connection protocol to any relay that has
7868 a wrong clock. Instead, we should only inform the controller when
7869 it's a trusted authority that claims our clock is wrong. Bugfix
7870 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
7871 - We were telling the controller about CHECKING_REACHABILITY and
7872 REACHABILITY_FAILED status events whenever we launch a testing
7873 circuit or notice that one has failed. Instead, only tell the
7874 controller when we want to inform the user of overall success or
7875 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7877 - Don't warn when we're using a circuit that ends with a node
7878 excluded in ExcludeExitNodes, but the circuit is not used to access
7879 the outside world. This should help fix bug 1090, but more problems
7880 remain. Bugfix on 0.2.1.6-alpha.
7881 - Work around a small memory leak in some versions of OpenSSL that
7882 stopped the memory used by the hostname TLS extension from being
7884 - Make our 'torify' script more portable; if we have only one of
7885 'torsocks' or 'tsocks' installed, don't complain to the user;
7886 and explain our warning about tsocks better.
7889 - Add a "getinfo status/accepted-server-descriptor" controller
7890 command, which is the recommended way for controllers to learn
7891 whether our server descriptor has been successfully received by at
7892 least on directory authority. Un-recommend good-server-descriptor
7893 getinfo and status events until we have a better design for them.
7894 - Update to the "September 4 2009" ip-to-country file.
7897 Changes in version 0.2.2.1-alpha - 2009-08-26
7898 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
7899 Tor clients to bootstrap on networks where only port 80 is reachable,
7900 makes it more straightforward to support hardware crypto accelerators,
7901 and starts the groundwork for gathering stats safely at relays.
7904 - Start the process of disabling ".exit" address notation, since it
7905 can be used for a variety of esoteric application-level attacks
7906 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
7909 o New directory authorities:
7910 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
7914 - New AccelName and AccelDir options add support for dynamic OpenSSL
7915 hardware crypto acceleration engines.
7916 - Tor now supports tunneling all of its outgoing connections over
7917 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
7918 configuration options. Code by Christopher Davis.
7921 - Send circuit or stream sendme cells when our window has decreased
7922 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
7923 by Karsten when testing the "reduce circuit window" performance
7924 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7925 before the release of Tor 0.0.0. This is the new winner of the
7928 o New options for gathering stats safely:
7929 - Directory mirrors that set "DirReqStatistics 1" write statistics
7930 about directory requests to disk every 24 hours. As compared to the
7931 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
7932 1) stats are written to disk exactly every 24 hours; 2) estimated
7933 shares of v2 and v3 requests are determined as mean values, not at
7934 the end of a measurement period; 3) unresolved requests are listed
7935 with country code '??'; 4) directories also measure download times.
7936 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
7937 number of exit streams and transferred bytes per port to disk every
7939 - Relays that set "CellStatistics 1" write statistics on how long
7940 cells spend in their circuit queues to disk every 24 hours.
7941 - Entry nodes that set "EntryStatistics 1" write statistics on the
7942 rough number and origins of connecting clients to disk every 24
7944 - Relays that write any of the above statistics to disk and set
7945 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
7946 their extra-info documents.
7949 - New --digests command-line switch to output the digests of the
7950 source files Tor was built with.
7951 - The "torify" script now uses torsocks where available.
7952 - The memarea code now uses a sentinel value at the end of each area
7953 to make sure nothing writes beyond the end of an area. This might
7954 help debug some conceivable causes of bug 930.
7955 - Time and memory units in the configuration file can now be set to
7956 fractional units. For example, "2.5 GB" is now a valid value for
7958 - Certain Tor clients (such as those behind check.torproject.org) may
7959 want to fetch the consensus in an extra early manner. To enable this
7960 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
7961 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
7962 as only certain clients who must have this information sooner should
7964 - Instead of adding the svn revision to the Tor version string, report
7965 the git commit (when we're building from a git checkout).
7968 - If any of the v3 certs we download are unparseable, we should
7969 actually notice the failure so we don't retry indefinitely. Bugfix
7970 on 0.2.0.x; reported by "rotator".
7971 - If the cached cert file is unparseable, warn but don't exit.
7972 - Fix possible segmentation fault on directory authorities. Bugfix on
7974 - When Tor fails to parse a descriptor of any kind, dump it to disk.
7975 Might help diagnosing bug 1051.
7977 o Deprecated and removed features:
7978 - The controller no longer accepts the old obsolete "addr-mappings/"
7979 or "unregistered-servers-" GETINFO values.
7980 - Hidden services no longer publish version 0 descriptors, and clients
7981 do not request or use version 0 descriptors. However, the old hidden
7982 service authorities still accept and serve version 0 descriptors
7983 when contacted by older hidden services/clients.
7984 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
7985 always on; using them is necessary for correct forward-compatible
7987 - Remove support for .noconnect style addresses. Nobody was using
7988 them, and they provided another avenue for detecting Tor users
7989 via application-level web tricks.
7991 o Packaging changes:
7992 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
7993 installer bundles. See
7994 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
7995 for details of what's new in Vidalia 0.2.3.
7996 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
7997 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
7998 configuration file, rather than the old Privoxy.
7999 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
8000 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
8001 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
8002 better compatibility with OS X 10.6, aka Snow Leopard.
8003 - OS X Vidalia Bundle: The multi-package installer is now replaced
8004 by a simple drag and drop to the /Applications folder. This change
8005 occurred with the upgrade to Vidalia 0.2.3.
8008 Changes in version 0.2.1.19 - 2009-07-28
8009 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
8010 services on Tor 0.2.1.3-alpha through 0.2.1.18.
8013 - Make accessing hidden services on 0.2.1.x work right again.
8014 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
8015 part of patch provided by "optimist".
8018 - When a relay/bridge is writing out its identity key fingerprint to
8019 the "fingerprint" file and to its logs, write it without spaces. Now
8020 it will look like the fingerprints in our bridges documentation,
8021 and confuse fewer users.
8024 - Relays no longer publish a new server descriptor if they change
8025 their MaxAdvertisedBandwidth config option but it doesn't end up
8026 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
8027 fixes bug 1026. Patch from Sebastian.
8028 - Avoid leaking memory every time we get a create cell but we have
8029 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
8030 fixes bug 1034. Reported by BarkerJr.
8033 Changes in version 0.2.1.18 - 2009-07-24
8034 Tor 0.2.1.18 lays the foundations for performance improvements,
8035 adds status events to help users diagnose bootstrap problems, adds
8036 optional authentication/authorization for hidden services, fixes a
8037 variety of potential anonymity problems, and includes a huge pile of
8038 other features and bug fixes.
8041 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
8044 Changes in version 0.2.1.17-rc - 2009-07-07
8045 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
8046 candidate for the 0.2.1.x series. It lays the groundwork for further
8047 client performance improvements, and also fixes a big bug with directory
8048 authorities that were causing them to assign Guard and Stable flags
8051 The Windows bundles also finally include the geoip database that we
8052 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
8053 should actually install Torbutton rather than giving you a cryptic
8054 failure message (oops).
8057 - Clients now use the bandwidth values in the consensus, rather than
8058 the bandwidth values in each relay descriptor. This approach opens
8059 the door to more accurate bandwidth estimates once the directory
8060 authorities start doing active measurements. Implements more of
8064 - When Tor clients restart after 1-5 days, they discard all their
8065 cached descriptors as too old, but they still use the cached
8066 consensus document. This approach is good for robustness, but
8067 bad for performance: since they don't know any bandwidths, they
8068 end up choosing at random rather than weighting their choice by
8069 speed. Fixed by the above feature of putting bandwidths in the
8070 consensus. Bugfix on 0.2.0.x.
8071 - Directory authorities were neglecting to mark relays down in their
8072 internal histories if the relays fall off the routerlist without
8073 ever being found unreachable. So there were relays in the histories
8074 that haven't been seen for eight months, and are listed as being
8075 up for eight months. This wreaked havoc on the "median wfu"
8076 and "median mtbf" calculations, in turn making Guard and Stable
8077 flags very wrong, hurting network performance. Fixes bugs 696 and
8078 969. Bugfix on 0.2.0.6-alpha.
8081 - Serve the DirPortFrontPage page even when we have been approaching
8082 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
8083 - The control port would close the connection before flushing long
8084 replies, such as the network consensus, if a QUIT command was issued
8085 before the reply had completed. Now, the control port flushes all
8086 pending replies before closing the connection. Also fixed a spurious
8087 warning when a QUIT command is issued after a malformed or rejected
8088 AUTHENTICATE command, but before the connection was closed. Patch
8089 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
8090 - When we can't find an intro key for a v2 hidden service descriptor,
8091 fall back to the v0 hidden service descriptor and log a bug message.
8092 Workaround for bug 1024.
8093 - Fix a log message that did not respect the SafeLogging option.
8097 - If we're a relay and we change our IP address, be more verbose
8098 about the reason that made us change. Should help track down
8099 further bugs for relays on dynamic IP addresses.
8102 Changes in version 0.2.0.35 - 2009-06-24
8104 - Avoid crashing in the presence of certain malformed descriptors.
8105 Found by lark, and by automated fuzzing.
8106 - Fix an edge case where a malicious exit relay could convince a
8107 controller that the client's DNS question resolves to an internal IP
8108 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
8111 - Finally fix the bug where dynamic-IP relays disappear when their
8112 IP address changes: directory mirrors were mistakenly telling
8113 them their old address if they asked via begin_dir, so they
8114 never got an accurate answer about their new address, so they
8115 just vanished after a day. For belt-and-suspenders, relays that
8116 don't set Address in their config now avoid using begin_dir for
8117 all direct connections. Should fix bugs 827, 883, and 900.
8118 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
8119 that would occur on some exit nodes when DNS failures and timeouts
8120 occurred in certain patterns. Fix for bug 957.
8123 - When starting with a cache over a few days old, do not leak
8124 memory for the obsolete router descriptors in it. Bugfix on
8125 0.2.0.33; fixes bug 672.
8126 - Hidden service clients didn't use a cached service descriptor that
8127 was older than 15 minutes, but wouldn't fetch a new one either,
8128 because there was already one in the cache. Now, fetch a v2
8129 descriptor unless the same descriptor was added to the cache within
8130 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
8133 Changes in version 0.2.1.16-rc - 2009-06-20
8134 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
8135 a bunch of minor bugs.
8138 - Fix an edge case where a malicious exit relay could convince a
8139 controller that the client's DNS question resolves to an internal IP
8140 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
8142 o Major performance improvements (on 0.2.0.x):
8143 - Disable and refactor some debugging checks that forced a linear scan
8144 over the whole server-side DNS cache. These accounted for over 50%
8145 of CPU time on a relatively busy exit node's gprof profile. Found
8147 - Disable some debugging checks that appeared in exit node profile
8151 - Update to the "June 3 2009" ip-to-country file.
8152 - Do not have tor-resolve automatically refuse all .onion addresses;
8153 if AutomapHostsOnResolve is set in your torrc, this will work fine.
8155 o Minor bugfixes (on 0.2.0.x):
8156 - Log correct error messages for DNS-related network errors on
8158 - Fix a race condition that could cause crashes or memory corruption
8159 when running as a server with a controller listening for log
8161 - Avoid crashing when we have a policy specified in a DirPolicy or
8162 SocksPolicy or ReachableAddresses option with ports set on it,
8163 and we re-load the policy. May fix bug 996.
8164 - Hidden service clients didn't use a cached service descriptor that
8165 was older than 15 minutes, but wouldn't fetch a new one either,
8166 because there was already one in the cache. Now, fetch a v2
8167 descriptor unless the same descriptor was added to the cache within
8168 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
8170 o Minor bugfixes (on 0.2.1.x):
8171 - Don't warn users about low port and hibernation mix when they
8172 provide a *ListenAddress directive to fix that. Bugfix on
8174 - When switching back and forth between bridge mode, do not start
8175 gathering GeoIP data until two hours have passed.
8176 - Do not complain that the user has requested an excluded node as
8177 an exit when the node is not really an exit. This could happen
8178 because the circuit was for testing, or an introduction point.
8182 Changes in version 0.2.1.15-rc - 2009-05-25
8183 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
8184 series. It fixes a major bug on fast exit relays, as well as a variety
8187 o Major bugfixes (on 0.2.0.x):
8188 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
8189 that would occur on some exit nodes when DNS failures and timeouts
8190 occurred in certain patterns. Fix for bug 957.
8192 o Minor bugfixes (on 0.2.0.x):
8193 - Actually return -1 in the error case for read_bandwidth_usage().
8194 Harmless bug, since we currently don't care about the return value
8195 anywhere. Bugfix on 0.2.0.9-alpha.
8196 - Provide a more useful log message if bug 977 (related to buffer
8197 freelists) ever reappears, and do not crash right away.
8198 - Fix an assertion failure on 64-bit platforms when we allocated
8199 memory right up to the end of a memarea, then realigned the memory
8200 one step beyond the end. Fixes a possible cause of bug 930.
8201 - Protect the count of open sockets with a mutex, so we can't
8202 corrupt it when two threads are closing or opening sockets at once.
8203 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
8204 - Don't allow a bridge to publish its router descriptor to a
8205 non-bridge directory authority. Fixes part of bug 932.
8206 - When we change to or from being a bridge, reset our counts of
8207 client usage by country. Fixes bug 932.
8208 - Fix a bug that made stream bandwidth get misreported to the
8210 - Stop using malloc_usable_size() to use more area than we had
8211 actually allocated: it was safe, but made valgrind really unhappy.
8212 - Fix a memory leak when v3 directory authorities load their keys
8213 and cert from disk. Bugfix on 0.2.0.1-alpha.
8215 o Minor bugfixes (on 0.2.1.x):
8216 - Fix use of freed memory when deciding to mark a non-addable
8217 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
8220 Changes in version 0.2.1.14-rc - 2009-04-12
8221 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
8222 series. It begins fixing some major performance problems, and also
8223 finally addresses the bug that was causing relays on dynamic IP
8224 addresses to fall out of the directory.
8227 - Clients replace entry guards that were chosen more than a few months
8228 ago. This change should significantly improve client performance,
8229 especially once more people upgrade, since relays that have been
8230 a guard for a long time are currently overloaded.
8232 o Major bugfixes (on 0.2.0):
8233 - Finally fix the bug where dynamic-IP relays disappear when their
8234 IP address changes: directory mirrors were mistakenly telling
8235 them their old address if they asked via begin_dir, so they
8236 never got an accurate answer about their new address, so they
8237 just vanished after a day. For belt-and-suspenders, relays that
8238 don't set Address in their config now avoid using begin_dir for
8239 all direct connections. Should fix bugs 827, 883, and 900.
8240 - Relays were falling out of the networkstatus consensus for
8241 part of a day if they changed their local config but the
8242 authorities discarded their new descriptor as "not sufficiently
8243 different". Now directory authorities accept a descriptor as changed
8244 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
8246 - Avoid crashing in the presence of certain malformed descriptors.
8247 Found by lark, and by automated fuzzing.
8250 - When generating circuit events with verbose nicknames for
8251 controllers, try harder to look up nicknames for routers on a
8252 circuit. (Previously, we would look in the router descriptors we had
8253 for nicknames, but not in the consensus.) Partial fix for bug 941.
8254 - If the bridge config line doesn't specify a port, assume 443.
8255 This makes bridge lines a bit smaller and easier for users to
8257 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
8258 bytes (aka 20KB/s), to match our documentation. Also update
8259 directory authorities so they always assign the Fast flag to relays
8260 with 20KB/s of capacity. Now people running relays won't suddenly
8261 find themselves not seeing any use, if the network gets faster
8263 - Update to the "April 3 2009" ip-to-country file.
8266 - Avoid trying to print raw memory to the logs when we decide to
8267 give up on downloading a given relay descriptor. Bugfix on
8269 - In tor-resolve, when the Tor client to use is specified by
8270 <hostname>:<port>, actually use the specified port rather than
8271 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
8272 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
8273 - When starting with a cache over a few days old, do not leak
8274 memory for the obsolete router descriptors in it. Bugfix on
8276 - Avoid double-free on list of successfully uploaded hidden
8277 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
8278 - Change memarea_strndup() implementation to work even when
8279 duplicating a string at the end of a page. This bug was
8280 harmless for now, but could have meant crashes later. Fix by
8281 lark. Bugfix on 0.2.1.1-alpha.
8282 - Limit uploaded directory documents to be 16M rather than 500K.
8283 The directory authorities were refusing v3 consensus votes from
8284 other authorities, since the votes are now 504K. Fixes bug 959;
8285 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
8286 - Directory authorities should never send a 503 "busy" response to
8287 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
8291 Changes in version 0.2.1.13-alpha - 2009-03-09
8292 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
8293 cleanups. We're finally getting close to a release candidate.
8296 - Correctly update the list of which countries we exclude as
8297 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
8298 lark. Bugfix on 0.2.1.6-alpha.
8300 o Minor bugfixes (on 0.2.0.x and earlier):
8301 - Automatically detect MacOSX versions earlier than 10.4.0, and
8302 disable kqueue from inside Tor when running with these versions.
8303 We previously did this from the startup script, but that was no
8304 help to people who didn't use the startup script. Resolves bug 863.
8305 - When we had picked an exit node for a connection, but marked it as
8306 "optional", and it turned out we had no onion key for the exit,
8307 stop wanting that exit and try again. This situation may not
8308 be possible now, but will probably become feasible with proposal
8309 158. Spotted by rovv. Fixes another case of bug 752.
8310 - Clients no longer cache certificates for authorities they do not
8311 recognize. Bugfix on 0.2.0.9-alpha.
8312 - When we can't transmit a DNS request due to a network error, retry
8313 it after a while, and eventually transmit a failing response to
8314 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
8315 - If the controller claimed responsibility for a stream, but that
8316 stream never finished making its connection, it would live
8317 forever in circuit_wait state. Now we close it after SocksTimeout
8318 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
8319 - Drop begin cells to a hidden service if they come from the middle
8320 of a circuit. Patch from lark.
8321 - When we erroneously receive two EXTEND cells for the same circuit
8322 ID on the same connection, drop the second. Patch from lark.
8323 - Fix a crash that occurs on exit nodes when a nameserver request
8324 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
8325 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
8327 - Do not assume that a stack-allocated character array will be
8328 64-bit aligned on platforms that demand that uint64_t access is
8329 aligned. Possible fix for bug 604.
8330 - Parse dates and IPv4 addresses in a locale- and libc-independent
8331 manner, to avoid platform-dependent behavior on malformed input.
8332 - Build correctly when configured to build outside the main source
8333 path. Patch from Michael Gold.
8334 - We were already rejecting relay begin cells with destination port
8335 of 0. Now also reject extend cells with destination port or address
8336 of 0. Suggested by lark.
8338 o Minor bugfixes (on 0.2.1.x):
8339 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
8340 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
8341 - If we're an exit node, scrub the IP address to which we are exiting
8342 in the logs. Bugfix on 0.2.1.8-alpha.
8345 - On Linux, use the prctl call to re-enable core dumps when the user
8347 - New controller event NEWCONSENSUS that lists the networkstatus
8348 lines for every recommended relay. Now controllers like Torflow
8349 can keep up-to-date on which relays they should be using.
8350 - Update to the "February 26 2009" ip-to-country file.
8353 Changes in version 0.2.0.34 - 2009-02-08
8354 Tor 0.2.0.34 features several more security-related fixes. You should
8355 upgrade, especially if you run an exit relay (remote crash) or a
8356 directory authority (remote infinite loop), or you're on an older
8357 (pre-XP) or not-recently-patched Windows (remote exploit).
8359 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
8360 have many known flaws, and nobody should be using them. You should
8361 upgrade. If you're using a Linux or BSD and its packages are obsolete,
8362 stop using those packages and upgrade anyway.
8365 - Fix an infinite-loop bug on handling corrupt votes under certain
8366 circumstances. Bugfix on 0.2.0.8-alpha.
8367 - Fix a temporary DoS vulnerability that could be performed by
8368 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
8369 - Avoid a potential crash on exit nodes when processing malformed
8370 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
8371 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
8372 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
8375 - Fix compilation on systems where time_t is a 64-bit integer.
8376 Patch from Matthias Drochner.
8377 - Don't consider expiring already-closed client connections. Fixes
8378 bug 893. Bugfix on 0.0.2pre20.
8381 Changes in version 0.2.1.12-alpha - 2009-02-08
8382 Tor 0.2.1.12-alpha features several more security-related fixes. You
8383 should upgrade, especially if you run an exit relay (remote crash) or
8384 a directory authority (remote infinite loop), or you're on an older
8385 (pre-XP) or not-recently-patched Windows (remote exploit). It also
8386 includes a big pile of minor bugfixes and cleanups.
8389 - Fix an infinite-loop bug on handling corrupt votes under certain
8390 circumstances. Bugfix on 0.2.0.8-alpha.
8391 - Fix a temporary DoS vulnerability that could be performed by
8392 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
8393 - Avoid a potential crash on exit nodes when processing malformed
8394 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
8397 - Let controllers actually ask for the "clients_seen" event for
8398 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
8399 reported by Matt Edman.
8400 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
8402 - Fix a bug in address parsing that was preventing bridges or hidden
8403 service targets from being at IPv6 addresses.
8404 - Solve a bug that kept hardware crypto acceleration from getting
8405 enabled when accounting was turned on. Fixes bug 907. Bugfix on
8407 - Remove a bash-ism from configure.in to build properly on non-Linux
8408 platforms. Bugfix on 0.2.1.1-alpha.
8409 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
8410 headers. Bugfix on 0.2.0.10-alpha.
8411 - Don't consider expiring already-closed client connections. Fixes
8412 bug 893. Bugfix on 0.0.2pre20.
8413 - Fix another interesting corner-case of bug 891 spotted by rovv:
8414 Previously, if two hosts had different amounts of clock drift, and
8415 one of them created a new connection with just the wrong timing,
8416 the other might decide to deprecate the new connection erroneously.
8417 Bugfix on 0.1.1.13-alpha.
8418 - Resolve a very rare crash bug that could occur when the user forced
8419 a nameserver reconfiguration during the middle of a nameserver
8420 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
8421 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
8422 Bugfix on 0.2.1.7-alpha.
8423 - If we're using bridges and our network goes away, be more willing
8424 to forgive our bridges and try again when we get an application
8425 request. Bugfix on 0.2.0.x.
8428 - Support platforms where time_t is 64 bits long. (Congratulations,
8429 NetBSD!) Patch from Matthias Drochner.
8430 - Add a 'getinfo status/clients-seen' controller command, in case
8431 controllers want to hear clients_seen events but connect late.
8434 - Disable GCC's strict alias optimization by default, to avoid the
8435 likelihood of its introducing subtle bugs whenever our code violates
8436 the letter of C99's alias rules.
8439 Changes in version 0.2.0.33 - 2009-01-21
8440 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
8441 useful to users. It also finally fixes a bug where a relay or client
8442 that's been off for many days would take a long time to bootstrap.
8444 This update also fixes an important security-related bug reported by
8445 Ilja van Sprundel. You should upgrade. (We'll send out more details
8446 about the bug once people have had some time to upgrade.)
8449 - Fix a heap-corruption bug that may be remotely triggerable on
8450 some platforms. Reported by Ilja van Sprundel.
8453 - When a stream at an exit relay is in state "resolving" or
8454 "connecting" and it receives an "end" relay cell, the exit relay
8455 would silently ignore the end cell and not close the stream. If
8456 the client never closes the circuit, then the exit relay never
8457 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
8459 - When sending CREATED cells back for a given circuit, use a 64-bit
8460 connection ID to find the right connection, rather than an addr:port
8461 combination. Now that we can have multiple OR connections between
8462 the same ORs, it is no longer possible to use addr:port to uniquely
8463 identify a connection.
8464 - Bridge relays that had DirPort set to 0 would stop fetching
8465 descriptors shortly after startup, and then briefly resume
8466 after a new bandwidth test and/or after publishing a new bridge
8467 descriptor. Bridge users that try to bootstrap from them would
8468 get a recent networkstatus but would get descriptors from up to
8469 18 hours earlier, meaning most of the descriptors were obsolete
8470 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
8471 - Prevent bridge relays from serving their 'extrainfo' document
8472 to anybody who asks, now that extrainfo docs include potentially
8473 sensitive aggregated client geoip summaries. Bugfix on
8475 - If the cached networkstatus consensus is more than five days old,
8476 discard it rather than trying to use it. In theory it could be
8477 useful because it lists alternate directory mirrors, but in practice
8478 it just means we spend many minutes trying directory mirrors that
8479 are long gone from the network. Also discard router descriptors as
8480 we load them if they are more than five days old, since the onion
8481 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
8484 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
8485 could make gcc generate non-functional binary search code. Bugfix
8487 - Build correctly on platforms without socklen_t.
8488 - Compile without warnings on solaris.
8489 - Avoid potential crash on internal error during signature collection.
8490 Fixes bug 864. Patch from rovv.
8491 - Correct handling of possible malformed authority signing key
8492 certificates with internal signature types. Fixes bug 880.
8493 Bugfix on 0.2.0.3-alpha.
8494 - Fix a hard-to-trigger resource leak when logging credential status.
8496 - When we can't initialize DNS because the network is down, do not
8497 automatically stop Tor from starting. Instead, we retry failed
8498 dns_init() every 10 minutes, and change the exit policy to reject
8499 *:* until one succeeds. Fixes bug 691.
8500 - Use 64 bits instead of 32 bits for connection identifiers used with
8501 the controller protocol, to greatly reduce risk of identifier reuse.
8502 - When we're choosing an exit node for a circuit, and we have
8503 no pending streams, choose a good general exit rather than one that
8504 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
8505 - Fix another case of assuming, when a specific exit is requested,
8506 that we know more than the user about what hosts it allows.
8507 Fixes one case of bug 752. Patch from rovv.
8508 - Clip the MaxCircuitDirtiness config option to a minimum of 10
8509 seconds. Warn the user if lower values are given in the
8510 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
8511 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
8512 user if lower values are given in the configuration. Bugfix on
8513 0.1.1.17-rc. Patch by Sebastian.
8514 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
8515 the cache because we already had a v0 descriptor with the same ID.
8516 Bugfix on 0.2.0.18-alpha.
8517 - Fix a race condition when freeing keys shared between main thread
8518 and CPU workers that could result in a memory leak. Bugfix on
8519 0.1.0.1-rc. Fixes bug 889.
8520 - Send a valid END cell back when a client tries to connect to a
8521 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
8522 840. Patch from rovv.
8523 - Check which hops rendezvous stream cells are associated with to
8524 prevent possible guess-the-streamid injection attacks from
8525 intermediate hops. Fixes another case of bug 446. Based on patch
8527 - If a broken client asks a non-exit router to connect somewhere,
8528 do not even do the DNS lookup before rejecting the connection.
8529 Fixes another case of bug 619. Patch from rovv.
8530 - When a relay gets a create cell it can't decrypt (e.g. because it's
8531 using the wrong onion key), we were dropping it and letting the
8532 client time out. Now actually answer with a destroy cell. Fixes
8533 bug 904. Bugfix on 0.0.2pre8.
8535 o Minor bugfixes (hidden services):
8536 - Do not throw away existing introduction points on SIGHUP. Bugfix on
8537 0.0.6pre1. Patch by Karsten. Fixes bug 874.
8540 - Report the case where all signatures in a detached set are rejected
8541 differently than the case where there is an error handling the
8543 - When we realize that another process has modified our cached
8544 descriptors, print out a more useful error message rather than
8545 triggering an assertion. Fixes bug 885. Patch from Karsten.
8546 - Implement the 0x20 hack to better resist DNS poisoning: set the
8547 case on outgoing DNS requests randomly, and reject responses that do
8548 not match the case correctly. This logic can be disabled with the
8549 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
8550 of servers that do not reliably preserve case in replies. See
8551 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
8553 - Check DNS replies for more matching fields to better resist DNS
8555 - Never use OpenSSL compression: it wastes RAM and CPU trying to
8556 compress cells, which are basically all encrypted, compressed, or
8560 Changes in version 0.2.1.11-alpha - 2009-01-20
8561 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
8562 week it will take a long time to bootstrap again" bug. It also fixes
8563 an important security-related bug reported by Ilja van Sprundel. You
8564 should upgrade. (We'll send out more details about the bug once people
8565 have had some time to upgrade.)
8568 - Fix a heap-corruption bug that may be remotely triggerable on
8569 some platforms. Reported by Ilja van Sprundel.
8572 - Discard router descriptors as we load them if they are more than
8573 five days old. Otherwise if Tor is off for a long time and then
8574 starts with cached descriptors, it will try to use the onion
8575 keys in those obsolete descriptors when building circuits. Bugfix
8576 on 0.2.0.x. Fixes bug 887.
8579 - Try to make sure that the version of Libevent we're running with
8580 is binary-compatible with the one we built with. May address bug
8582 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
8583 for bug 905. Bugfix on 0.2.1.7-alpha.
8584 - Add a new --enable-local-appdata configuration switch to change
8585 the default location of the datadir on win32 from APPDATA to
8586 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
8587 entirely. Patch from coderman.
8590 - Make outbound DNS packets respect the OutboundBindAddress setting.
8591 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
8592 - When our circuit fails at the first hop (e.g. we get a destroy
8593 cell back), avoid using that OR connection anymore, and also
8594 tell all the one-hop directory requests waiting for it that they
8595 should fail. Bugfix on 0.2.1.3-alpha.
8596 - In the torify(1) manpage, mention that tsocks will leak your
8600 Changes in version 0.2.1.10-alpha - 2009-01-06
8601 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
8602 would make the bridge relay not so useful if it had DirPort set to 0,
8603 and one that could let an attacker learn a little bit of information
8604 about the bridge's users), and a bug that would cause your Tor relay
8605 to ignore a circuit create request it can't decrypt (rather than reply
8606 with an error). It also fixes a wide variety of other bugs.
8609 - If the cached networkstatus consensus is more than five days old,
8610 discard it rather than trying to use it. In theory it could
8611 be useful because it lists alternate directory mirrors, but in
8612 practice it just means we spend many minutes trying directory
8613 mirrors that are long gone from the network. Helps bug 887 a bit;
8615 - Bridge relays that had DirPort set to 0 would stop fetching
8616 descriptors shortly after startup, and then briefly resume
8617 after a new bandwidth test and/or after publishing a new bridge
8618 descriptor. Bridge users that try to bootstrap from them would
8619 get a recent networkstatus but would get descriptors from up to
8620 18 hours earlier, meaning most of the descriptors were obsolete
8621 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
8622 - Prevent bridge relays from serving their 'extrainfo' document
8623 to anybody who asks, now that extrainfo docs include potentially
8624 sensitive aggregated client geoip summaries. Bugfix on
8628 - New controller event "clients_seen" to report a geoip-based summary
8629 of which countries we've seen clients from recently. Now controllers
8630 like Vidalia can show bridge operators that they're actually making
8632 - Build correctly against versions of OpenSSL 0.9.8 or later built
8633 without support for deprecated functions.
8634 - Update to the "December 19 2008" ip-to-country file.
8636 o Minor bugfixes (on 0.2.0.x):
8637 - Authorities now vote for the Stable flag for any router whose
8638 weighted MTBF is at least 5 days, regardless of the mean MTBF.
8639 - Do not remove routers as too old if we do not have any consensus
8640 document. Bugfix on 0.2.0.7-alpha.
8641 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
8642 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
8643 - When an exit relay resolves a stream address to a local IP address,
8644 do not just keep retrying that same exit relay over and
8645 over. Instead, just close the stream. Addresses bug 872. Bugfix
8646 on 0.2.0.32. Patch from rovv.
8647 - If a hidden service sends us an END cell, do not consider
8648 retrying the connection; just close it. Patch from rovv.
8649 - When we made bridge authorities stop serving bridge descriptors over
8650 unencrypted links, we also broke DirPort reachability testing for
8651 bridges. So bridges with a non-zero DirPort were printing spurious
8652 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
8653 - When a relay gets a create cell it can't decrypt (e.g. because it's
8654 using the wrong onion key), we were dropping it and letting the
8655 client time out. Now actually answer with a destroy cell. Fixes
8656 bug 904. Bugfix on 0.0.2pre8.
8657 - Squeeze 2-5% out of client performance (according to oprofile) by
8658 improving the implementation of some policy-manipulation functions.
8660 o Minor bugfixes (on 0.2.1.x):
8661 - Make get_interface_address() function work properly again; stop
8662 guessing the wrong parts of our address as our address.
8663 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
8664 send on that circuit. Otherwise we might violate the proposal-110
8665 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
8667 - When we're sending non-EXTEND cells to the first hop in a circuit,
8668 for example to use an encrypted directory connection, we don't need
8669 to use RELAY_EARLY cells: the first hop knows what kind of cell
8670 it is, and nobody else can even see the cell type. Conserving
8671 RELAY_EARLY cells makes it easier to cannibalize circuits like
8673 - Stop logging nameserver addresses in reverse order.
8674 - If we are retrying a directory download slowly over and over, do
8675 not automatically give up after the 254th failure. Bugfix on
8677 - Resume reporting accurate "stream end" reasons to the local control
8678 port. They were lost in the changes for Proposal 148. Bugfix on
8681 o Deprecated and removed features:
8682 - The old "tor --version --version" command, which would print out
8683 the subversion "Id" of most of the source files, is now removed. It
8684 turned out to be less useful than we'd expected, and harder to
8687 o Code simplifications and refactoring:
8688 - Change our header file guard macros to be less likely to conflict
8689 with system headers. Adam Langley noticed that we were conflicting
8690 with log.h on Android.
8691 - Tool-assisted documentation cleanup. Nearly every function or
8692 static variable in Tor should have its own documentation now.
8695 Changes in version 0.2.1.9-alpha - 2008-12-25
8696 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
8698 o New directory authorities:
8699 - gabelmoo (the authority run by Karsten Loesing) now has a new
8703 - Never use a connection with a mismatched address to extend a
8704 circuit, unless that connection is canonical. A canonical
8705 connection is one whose address is authenticated by the router's
8706 identity key, either in a NETINFO cell or in a router descriptor.
8707 - Avoid a possible memory corruption bug when receiving hidden service
8708 descriptors. Bugfix on 0.2.1.6-alpha.
8711 - Fix a logic error that would automatically reject all but the first
8712 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
8713 part of bug 813/868. Bug spotted by coderman.
8714 - When a stream at an exit relay is in state "resolving" or
8715 "connecting" and it receives an "end" relay cell, the exit relay
8716 would silently ignore the end cell and not close the stream. If
8717 the client never closes the circuit, then the exit relay never
8718 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
8720 - When we can't initialize DNS because the network is down, do not
8721 automatically stop Tor from starting. Instead, retry failed
8722 dns_init() every 10 minutes, and change the exit policy to reject
8723 *:* until one succeeds. Fixes bug 691.
8726 - Give a better error message when an overzealous init script says
8727 "sudo -u username tor --user username". Makes Bug 882 easier for
8729 - When a directory authority gives us a new guess for our IP address,
8730 log which authority we used. Hopefully this will help us debug
8731 the recent complaints about bad IP address guesses.
8732 - Detect svn revision properly when we're using git-svn.
8733 - Try not to open more than one descriptor-downloading connection
8734 to an authority at once. This should reduce load on directory
8735 authorities. Fixes bug 366.
8736 - Add cross-certification to newly generated certificates, so that
8737 a signing key is enough information to look up a certificate.
8738 Partial implementation of proposal 157.
8739 - Start serving certificates by <identity digest, signing key digest>
8740 pairs. Partial implementation of proposal 157.
8741 - Clients now never report any stream end reason except 'MISC'.
8742 Implements proposal 148.
8743 - On platforms with a maximum syslog string length, truncate syslog
8744 messages to that length ourselves, rather than relying on the
8745 system to do it for us.
8746 - Optimize out calls to time(NULL) that occur for every IO operation,
8747 or for every cell. On systems where time() is a slow syscall,
8748 this fix will be slightly helpful.
8749 - Exit servers can now answer resolve requests for ip6.arpa addresses.
8750 - When we download a descriptor that we then immediately (as
8751 a directory authority) reject, do not retry downloading it right
8752 away. Should save some bandwidth on authorities. Fix for bug
8753 888. Patch by Sebastian Hahn.
8754 - When a download gets us zero good descriptors, do not notify
8755 Tor that new directory information has arrived.
8756 - Avoid some nasty corner cases in the logic for marking connections
8757 as too old or obsolete or noncanonical for circuits. Partial
8760 o Minor features (controller):
8761 - New CONSENSUS_ARRIVED event to note when a new consensus has
8762 been fetched and validated.
8763 - When we realize that another process has modified our cached
8764 descriptors file, print out a more useful error message rather
8765 than triggering an assertion. Fixes bug 885. Patch from Karsten.
8766 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
8767 controllers to prevent SIGHUP from reloading the
8768 configuration. Fixes bug 856.
8771 - Resume using the correct "REASON=" stream when telling the
8772 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
8773 - When a canonical connection appears later in our internal list
8774 than a noncanonical one for a given OR ID, always use the
8775 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
8777 - Clip the MaxCircuitDirtiness config option to a minimum of 10
8778 seconds. Warn the user if lower values are given in the
8779 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
8780 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
8781 user if lower values are given in the configuration. Bugfix on
8782 0.1.1.17-rc. Patch by Sebastian.
8783 - Fix a race condition when freeing keys shared between main thread
8784 and CPU workers that could result in a memory leak. Bugfix on
8785 0.1.0.1-rc. Fixes bug 889.
8787 o Minor bugfixes (hidden services):
8788 - Do not throw away existing introduction points on SIGHUP (bugfix on
8789 0.0.6pre1); also, do not stall hidden services because we're
8790 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
8791 by John Brooks. Patch by Karsten. Fixes bug 874.
8792 - Fix a memory leak when we decline to add a v2 rendezvous
8793 descriptor to the cache because we already had a v0 descriptor
8794 with the same ID. Bugfix on 0.2.0.18-alpha.
8796 o Deprecated and removed features:
8797 - RedirectExits has been removed. It was deprecated since
8799 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
8800 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
8801 - Cell pools are now always enabled; --disable-cell-pools is ignored.
8803 o Code simplifications and refactoring:
8804 - Rename the confusing or_is_obsolete field to the more appropriate
8805 is_bad_for_new_circs, and move it to or_connection_t where it
8807 - Move edge-only flags from connection_t to edge_connection_t: not
8808 only is this better coding, but on machines of plausible alignment,
8809 it should save 4-8 bytes per connection_t. "Every little bit helps."
8810 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
8811 for consistency; keep old option working for backward compatibility.
8812 - Simplify the code for finding connections to use for a circuit.
8815 Changes in version 0.2.1.8-alpha - 2008-12-08
8816 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
8817 builds better on unusual platforms like Solaris and old OS X, and
8818 fixes a variety of other issues.
8821 - New DirPortFrontPage option that takes an html file and publishes
8822 it as "/" on the DirPort. Now relay operators can provide a
8823 disclaimer without needing to set up a separate webserver. There's
8824 a sample disclaimer in contrib/tor-exit-notice.html.
8827 - When the client is choosing entry guards, now it selects at most
8828 one guard from a given relay family. Otherwise we could end up with
8829 all of our entry points into the network run by the same operator.
8830 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
8833 - Fix a DOS opportunity during the voting signature collection process
8834 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8835 - Fix a possible segfault when establishing an exit connection. Bugfix
8839 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
8841 - Made Tor a little less aggressive about deleting expired
8842 certificates. Partial fix for bug 854.
8843 - Stop doing unaligned memory access that generated bus errors on
8844 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
8845 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
8846 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
8847 - Make USR2 log-level switch take effect immediately. Bugfix on
8849 - If one win32 nameserver fails to get added, continue adding the
8850 rest, and don't automatically fail.
8851 - Use fcntl() for locking when flock() is not available. Should fix
8852 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
8853 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
8854 could make gcc generate non-functional binary search code. Bugfix
8856 - Build correctly on platforms without socklen_t.
8857 - Avoid potential crash on internal error during signature collection.
8858 Fixes bug 864. Patch from rovv.
8859 - Do not use C's stdio library for writing to log files. This will
8860 improve logging performance by a minute amount, and will stop
8861 leaking fds when our disk is full. Fixes bug 861.
8862 - Stop erroneous use of O_APPEND in cases where we did not in fact
8863 want to re-seek to the end of a file before every last write().
8864 - Correct handling of possible malformed authority signing key
8865 certificates with internal signature types. Fixes bug 880. Bugfix
8867 - Fix a hard-to-trigger resource leak when logging credential status.
8871 - Directory mirrors no longer fetch the v1 directory or
8872 running-routers files. They are obsolete, and nobody asks for them
8873 anymore. This is the first step to making v1 authorities obsolete.
8875 o Minor features (controller):
8876 - Return circuit purposes in response to GETINFO circuit-status. Fixes
8880 Changes in version 0.2.0.32 - 2008-11-20
8881 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
8882 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8883 a smaller security flaw that might allow an attacker to access local
8884 services, further improves hidden service performance, and fixes a
8885 variety of other issues.
8888 - The "User" and "Group" config options did not clear the
8889 supplementary group entries for the Tor process. The "User" option
8890 is now more robust, and we now set the groups to the specified
8891 user's primary group. The "Group" option is now ignored. For more
8892 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8893 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8894 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
8895 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8896 consistently obeyed: if an exit relay refuses a stream because its
8897 exit policy doesn't allow it, we would remember what IP address
8898 the relay said the destination address resolves to, even if it's
8899 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8902 - Fix a DOS opportunity during the voting signature collection process
8903 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8905 o Major bugfixes (hidden services):
8906 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8907 we were failing the whole hidden service request when the v0
8908 descriptor fetch fails, even if the v2 fetch is still pending and
8909 might succeed. Similarly, if the last v2 fetch fails, we were
8910 failing the whole hidden service request even if a v0 fetch is
8911 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8912 - When extending a circuit to a hidden service directory to upload a
8913 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8914 requests failed, because the router descriptor has not been
8915 downloaded yet. In these cases, do not attempt to upload the
8916 rendezvous descriptor, but wait until the router descriptor is
8917 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
8918 descriptor from a hidden service directory for which the router
8919 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
8923 - Fix several infrequent memory leaks spotted by Coverity.
8924 - When testing for libevent functions, set the LDFLAGS variable
8925 correctly. Found by Riastradh.
8926 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8927 bootstrapping with tunneled directory connections. Bugfix on
8928 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8929 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8930 and we know that server B rejects most-but-not all connections to
8931 port 80, we would previously reject the connection. Now, we assume
8932 the user knows what they were asking for. Fixes bug 752. Bugfix
8933 on 0.0.9rc5. Diagnosed by BarkerJr.
8934 - If we overrun our per-second write limits a little, count this as
8935 having used up our write allocation for the second, and choke
8936 outgoing directory writes. Previously, we had only counted this when
8937 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
8938 Bugfix on 0.2.0.x (??).
8939 - Remove the old v2 directory authority 'lefkada' from the default
8940 list. It has been gone for many months.
8941 - Stop doing unaligned memory access that generated bus errors on
8942 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
8943 - Make USR2 log-level switch take effect immediately. Bugfix on
8946 o Minor bugfixes (controller):
8947 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
8948 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
8951 Changes in version 0.2.1.7-alpha - 2008-11-08
8952 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
8953 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8954 a smaller security flaw that might allow an attacker to access local
8955 services, adds better defense against DNS poisoning attacks on exit
8956 relays, further improves hidden service performance, and fixes a
8957 variety of other issues.
8960 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8961 consistently obeyed: if an exit relay refuses a stream because its
8962 exit policy doesn't allow it, we would remember what IP address
8963 the relay said the destination address resolves to, even if it's
8964 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8965 - The "User" and "Group" config options did not clear the
8966 supplementary group entries for the Tor process. The "User" option
8967 is now more robust, and we now set the groups to the specified
8968 user's primary group. The "Group" option is now ignored. For more
8969 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8970 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8971 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
8972 - Do not use or believe expired v3 authority certificates. Patch
8973 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
8976 - Now NodeFamily and MyFamily config options allow spaces in
8977 identity fingerprints, so it's easier to paste them in.
8978 Suggested by Lucky Green.
8979 - Implement the 0x20 hack to better resist DNS poisoning: set the
8980 case on outgoing DNS requests randomly, and reject responses that do
8981 not match the case correctly. This logic can be disabled with the
8982 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
8983 of servers that do not reliably preserve case in replies. See
8984 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
8986 - Preserve case in replies to DNSPort requests in order to support
8987 the 0x20 hack for resisting DNS poisoning attacks.
8989 o Hidden service performance improvements:
8990 - When the client launches an introduction circuit, retry with a
8991 new circuit after 30 seconds rather than 60 seconds.
8992 - Launch a second client-side introduction circuit in parallel
8993 after a delay of 15 seconds (based on work by Christian Wilms).
8994 - Hidden services start out building five intro circuits rather
8995 than three, and when the first three finish they publish a service
8996 descriptor using those. Now we publish our service descriptor much
8997 faster after restart.
9000 - Minor fix in the warning messages when you're having problems
9001 bootstrapping; also, be more forgiving of bootstrap problems when
9002 we're still making incremental progress on a given bootstrap phase.
9003 - When we're choosing an exit node for a circuit, and we have
9004 no pending streams, choose a good general exit rather than one that
9005 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
9006 - Send a valid END cell back when a client tries to connect to a
9007 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
9008 840. Patch from rovv.
9009 - If a broken client asks a non-exit router to connect somewhere,
9010 do not even do the DNS lookup before rejecting the connection.
9011 Fixes another case of bug 619. Patch from rovv.
9012 - Fix another case of assuming, when a specific exit is requested,
9013 that we know more than the user about what hosts it allows.
9014 Fixes another case of bug 752. Patch from rovv.
9015 - Check which hops rendezvous stream cells are associated with to
9016 prevent possible guess-the-streamid injection attacks from
9017 intermediate hops. Fixes another case of bug 446. Based on patch
9019 - Avoid using a negative right-shift when comparing 32-bit
9020 addresses. Possible fix for bug 845 and bug 811.
9021 - Make the assert_circuit_ok() function work correctly on circuits that
9022 have already been marked for close.
9023 - Fix read-off-the-end-of-string error in unit tests when decoding
9024 introduction points.
9025 - Fix uninitialized size field for memory area allocation: may improve
9026 memory performance during directory parsing.
9027 - Treat duplicate certificate fetches as failures, so that we do
9028 not try to re-fetch an expired certificate over and over and over.
9029 - Do not say we're fetching a certificate when we'll in fact skip it
9030 because of a pending download.
9033 Changes in version 0.2.1.6-alpha - 2008-09-30
9034 Tor 0.2.1.6-alpha further improves performance and robustness of
9035 hidden services, starts work on supporting per-country relay selection,
9036 and fixes a variety of smaller issues.
9039 - Implement proposal 121: make it possible to build hidden services
9040 that only certain clients are allowed to connect to. This is
9041 enforced at several points, so that unauthorized clients are unable
9042 to send INTRODUCE cells to the service, or even (depending on the
9043 type of authentication) to learn introduction points. This feature
9044 raises the bar for certain kinds of active attacks against hidden
9045 services. Code by Karsten Loesing.
9046 - Relays now store and serve v2 hidden service descriptors by default,
9047 i.e., the new default value for HidServDirectoryV2 is 1. This is
9048 the last step in proposal 114, which aims to make hidden service
9049 lookups more reliable.
9050 - Start work to allow node restrictions to include country codes. The
9051 syntax to exclude nodes in a country with country code XX is
9052 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
9053 refinement to decide what config options should take priority if
9054 you ask to both use a particular node and exclude it.
9055 - Allow ExitNodes list to include IP ranges and country codes, just
9056 like the Exclude*Nodes lists. Patch from Robert Hogan.
9059 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
9060 Tor to fail to start if you had it configured to use a bridge
9061 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
9062 - When extending a circuit to a hidden service directory to upload a
9063 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
9064 requests failed, because the router descriptor had not been
9065 downloaded yet. In these cases, we now wait until the router
9066 descriptor is downloaded, and then retry. Likewise, clients
9067 now skip over a hidden service directory if they don't yet have
9068 its router descriptor, rather than futilely requesting it and
9069 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
9071 - When fetching v0 and v2 rendezvous service descriptors in parallel,
9072 we were failing the whole hidden service request when the v0
9073 descriptor fetch fails, even if the v2 fetch is still pending and
9074 might succeed. Similarly, if the last v2 fetch fails, we were
9075 failing the whole hidden service request even if a v0 fetch is
9076 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
9077 - DNS replies need to have names matching their requests, but
9078 these names should be in the questions section, not necessarily
9079 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
9082 - Update to the "September 1 2008" ip-to-country file.
9083 - Allow ports 465 and 587 in the default exit policy again. We had
9084 rejected them in 0.1.0.15, because back in 2005 they were commonly
9085 misconfigured and ended up as spam targets. We hear they are better
9086 locked down these days.
9087 - Use a lockfile to make sure that two Tor processes are not
9088 simultaneously running with the same datadir.
9089 - Serve the latest v3 networkstatus consensus via the control
9090 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
9091 - Better logging about stability/reliability calculations on directory
9093 - Drop the requirement to have an open dir port for storing and
9094 serving v2 hidden service descriptors.
9095 - Directory authorities now serve a /tor/dbg-stability.txt URL to
9096 help debug WFU and MTBF calculations.
9097 - Implement most of Proposal 152: allow specialized servers to permit
9098 single-hop circuits, and clients to use those servers to build
9099 single-hop circuits when using a specialized controller. Patch
9100 from Josh Albrecht. Resolves feature request 768.
9101 - Add a -p option to tor-resolve for specifying the SOCKS port: some
9102 people find host:port too confusing.
9103 - Make TrackHostExit mappings expire a while after their last use, not
9104 after their creation. Patch from Robert Hogan.
9105 - Provide circuit purposes along with circuit events to the controller.
9108 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
9110 - Fixed some memory leaks -- some quite frequent, some almost
9111 impossible to trigger -- based on results from Coverity.
9112 - When testing for libevent functions, set the LDFLAGS variable
9113 correctly. Found by Riastradh.
9114 - Fix an assertion bug in parsing policy-related options; possible fix
9116 - Catch and report a few more bootstrapping failure cases when Tor
9117 fails to establish a TCP connection. Cleanup on 0.2.1.x.
9118 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
9119 bootstrapping with tunneled directory connections. Bugfix on
9120 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
9121 - When asked to connect to A.B.exit:80, if we don't know the IP for A
9122 and we know that server B rejects most-but-not all connections to
9123 port 80, we would previously reject the connection. Now, we assume
9124 the user knows what they were asking for. Fixes bug 752. Bugfix
9125 on 0.0.9rc5. Diagnosed by BarkerJr.
9126 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
9127 service directories if they have no advertised dir port. Bugfix
9129 - If we overrun our per-second write limits a little, count this as
9130 having used up our write allocation for the second, and choke
9131 outgoing directory writes. Previously, we had only counted this when
9132 we had met our limits precisely. Fixes bug 824. Patch by rovv.
9133 Bugfix on 0.2.0.x (??).
9134 - Avoid a "0 divided by 0" calculation when calculating router uptime
9135 at directory authorities. Bugfix on 0.2.0.8-alpha.
9136 - Make DNS resolved controller events into "CLOSED", not
9137 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
9139 - Fix a bug where an unreachable relay would establish enough
9140 reachability testing circuits to do a bandwidth test -- if
9141 we already have a connection to the middle hop of the testing
9142 circuit, then it could establish the last hop by using the existing
9143 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
9144 circuits no longer use entry guards in 0.2.1.3-alpha.
9145 - If we have correct permissions on $datadir, we complain to stdout
9146 and fail to start. But dangerous permissions on
9147 $datadir/cached-status/ would cause us to open a log and complain
9148 there. Now complain to stdout and fail to start in both cases. Fixes
9149 bug 820, reported by seeess.
9150 - Remove the old v2 directory authority 'lefkada' from the default
9151 list. It has been gone for many months.
9153 o Code simplifications and refactoring:
9154 - Revise the connection_new functions so that a more typesafe variant
9155 exists. This will work better with Coverity, and let us find any
9156 actual mistakes we're making here.
9157 - Refactor unit testing logic so that dmalloc can be used sensibly
9158 with unit tests to check for memory leaks.
9159 - Move all hidden-service related fields from connection and circuit
9160 structure to substructures: this way they won't eat so much memory.
9163 Changes in version 0.2.0.31 - 2008-09-03
9164 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
9165 a big bug we're seeing where in rare cases traffic from one Tor stream
9166 gets mixed into another stream, and fixes a variety of smaller issues.
9169 - Make sure that two circuits can never exist on the same connection
9170 with the same circuit ID, even if one is marked for close. This
9171 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
9172 - Relays now reject risky extend cells: if the extend cell includes
9173 a digest of all zeroes, or asks to extend back to the relay that
9174 sent the extend cell, tear down the circuit. Ideas suggested
9176 - If not enough of our entry guards are available so we add a new
9177 one, we might use the new one even if it overlapped with the
9178 current circuit's exit relay (or its family). Anonymity bugfix
9179 pointed out by rovv.
9182 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
9183 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
9184 - Correctly detect the presence of the linux/netfilter_ipv4.h header
9185 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
9186 - Pick size of default geoip filename string correctly on windows.
9187 Fixes bug 806. Bugfix on 0.2.0.30.
9188 - Make the autoconf script accept the obsolete --with-ssl-dir
9189 option as an alias for the actually-working --with-openssl-dir
9190 option. Fix the help documentation to recommend --with-openssl-dir.
9191 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
9192 - When using the TransPort option on OpenBSD, and using the User
9193 option to change UID and drop privileges, make sure to open
9194 /dev/pf before dropping privileges. Fixes bug 782. Patch from
9195 Christopher Davis. Bugfix on 0.1.2.1-alpha.
9196 - Try to attach connections immediately upon receiving a RENDEZVOUS2
9197 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
9198 on the client side when connecting to a hidden service. Bugfix
9199 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
9200 - When closing an application-side connection because its circuit is
9201 getting torn down, generate the stream event correctly. Bugfix on
9202 0.1.2.x. Anonymous patch.
9205 Changes in version 0.2.1.5-alpha - 2008-08-31
9206 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
9207 in a lot of the infrastructure for adding authorization to hidden
9208 services, lays the groundwork for having clients read their load
9209 balancing information out of the networkstatus consensus rather than
9210 the individual router descriptors, addresses two potential anonymity
9211 issues, and fixes a variety of smaller issues.
9214 - Convert many internal address representations to optionally hold
9216 - Generate and accept IPv6 addresses in many protocol elements.
9217 - Make resolver code handle nameservers located at ipv6 addresses.
9218 - Begin implementation of proposal 121 ("Client authorization for
9219 hidden services"): configure hidden services with client
9220 authorization, publish descriptors for them, and configure
9221 authorization data for hidden services at clients. The next
9222 step is to actually access hidden services that perform client
9224 - More progress toward proposal 141: Network status consensus
9225 documents and votes now contain bandwidth information for each
9226 router and a summary of that router's exit policy. Eventually this
9227 will be used by clients so that they do not have to download every
9228 known descriptor before building circuits.
9230 o Major bugfixes (on 0.2.0.x and before):
9231 - When sending CREATED cells back for a given circuit, use a 64-bit
9232 connection ID to find the right connection, rather than an addr:port
9233 combination. Now that we can have multiple OR connections between
9234 the same ORs, it is no longer possible to use addr:port to uniquely
9235 identify a connection.
9236 - Relays now reject risky extend cells: if the extend cell includes
9237 a digest of all zeroes, or asks to extend back to the relay that
9238 sent the extend cell, tear down the circuit. Ideas suggested
9240 - If not enough of our entry guards are available so we add a new
9241 one, we might use the new one even if it overlapped with the
9242 current circuit's exit relay (or its family). Anonymity bugfix
9243 pointed out by rovv.
9246 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
9247 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
9248 - When using the TransPort option on OpenBSD, and using the User
9249 option to change UID and drop privileges, make sure to open /dev/pf
9250 before dropping privileges. Fixes bug 782. Patch from Christopher
9251 Davis. Bugfix on 0.1.2.1-alpha.
9252 - Correctly detect the presence of the linux/netfilter_ipv4.h header
9253 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
9254 - Add a missing safe_str() call for a debug log message.
9255 - Use 64 bits instead of 32 bits for connection identifiers used with
9256 the controller protocol, to greatly reduce risk of identifier reuse.
9257 - Make the autoconf script accept the obsolete --with-ssl-dir
9258 option as an alias for the actually-working --with-openssl-dir
9259 option. Fix the help documentation to recommend --with-openssl-dir.
9260 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
9263 - Rate-limit too-many-sockets messages: when they happen, they happen
9264 a lot. Resolves bug 748.
9265 - Resist DNS poisoning a little better by making sure that names in
9266 answer sections match.
9267 - Print the SOCKS5 error message string as well as the error code
9268 when a tor-resolve request fails. Patch from Jacob.
9271 Changes in version 0.2.1.4-alpha - 2008-08-04
9272 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
9275 - The address part of exit policies was not correctly written
9276 to router descriptors. This generated router descriptors that failed
9277 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
9279 - Tor triggered a false assert when extending a circuit to a relay
9280 but we already have a connection open to that relay. Noticed by
9281 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
9284 - Fix a hidden service logging bug: in some edge cases, the router
9285 descriptor of a previously picked introduction point becomes
9286 obsolete and we need to give up on it rather than continually
9287 complaining that it has become obsolete. Observed by xiando. Bugfix
9291 - Take out the TestVia config option, since it was a workaround for
9292 a bug that was fixed in Tor 0.1.1.21.
9295 Changes in version 0.2.1.3-alpha - 2008-08-03
9296 Tor 0.2.1.3-alpha implements most of the pieces to prevent
9297 infinite-length circuit attacks (see proposal 110); fixes a bug that
9298 might cause exit relays to corrupt streams they send back; allows
9299 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
9300 ExcludeExitNodes config options; and fixes a big pile of bugs.
9302 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
9303 - Send a bootstrap problem "warn" event on the first problem if the
9304 reason is NO_ROUTE (that is, our network is down).
9307 - Implement most of proposal 110: The first K cells to be sent
9308 along a circuit are marked as special "early" cells; only K "early"
9309 cells will be allowed. Once this code is universal, we can block
9310 certain kinds of DOS attack by requiring that EXTEND commands must
9311 be sent using an "early" cell.
9314 - Try to attach connections immediately upon receiving a RENDEZVOUS2
9315 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
9316 on the client side when connecting to a hidden service. Bugfix
9317 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
9318 - Ensure that two circuits can never exist on the same connection
9319 with the same circuit ID, even if one is marked for close. This
9320 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
9323 - When relays do their initial bandwidth measurement, don't limit
9324 to just our entry guards for the test circuits. Otherwise we tend
9325 to have multiple test circuits going through a single entry guard,
9326 which makes our bandwidth test less accurate. Fixes part of bug 654;
9327 patch contributed by Josh Albrecht.
9328 - Add an ExcludeExitNodes option so users can list a set of nodes
9329 that should be be excluded from the exit node position, but
9330 allowed elsewhere. Implements proposal 151.
9331 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
9332 ExcludeNodes and ExcludeExitNodes lists.
9333 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
9334 be more efficient. Formerly it was quadratic in the number of
9335 servers; now it should be linear. Fixes bug 509.
9336 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
9337 and n_conn_id_digest fields into a separate structure that's
9338 only needed when the circuit has not yet attached to an n_conn.
9341 - Change the contrib/tor.logrotate script so it makes the new
9342 logs as "_tor:_tor" rather than the default, which is generally
9343 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
9344 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
9345 warnings (occasionally), but it can also cause the compiler to
9346 eliminate error-checking code. Suggested by Peter Gutmann.
9347 - When a hidden service is giving up on an introduction point candidate
9348 that was not included in the last published rendezvous descriptor,
9349 don't reschedule publication of the next descriptor. Fixes bug 763.
9351 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
9352 HiddenServiceExcludeNodes as obsolete: they never worked properly,
9353 and nobody claims to be using them. Fixes bug 754. Bugfix on
9354 0.1.0.1-rc. Patch from Christian Wilms.
9355 - Fix a small alignment and memory-wasting bug on buffer chunks.
9358 o Minor bugfixes (controller):
9359 - When closing an application-side connection because its circuit
9360 is getting torn down, generate the stream event correctly.
9361 Bugfix on 0.1.2.x. Anonymous patch.
9364 - Remove all backward-compatibility code to support relays running
9365 versions of Tor so old that they no longer work at all on the
9369 Changes in version 0.2.0.30 - 2008-07-15
9371 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
9372 warnings (occasionally), but it can also cause the compiler to
9373 eliminate error-checking code. Suggested by Peter Gutmann.
9376 Changes in version 0.2.0.29-rc - 2008-07-08
9377 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
9378 hidden-service performance bugs, and fixes a bunch of smaller bugs.
9381 - If you have more than one bridge but don't know their keys,
9382 you would only launch a request for the descriptor of the first one
9383 on your list. (Tor considered launching requests for the others, but
9384 found that it already had a connection on the way for $0000...0000
9385 so it didn't open another.) Bugfix on 0.2.0.x.
9386 - If you have more than one bridge but don't know their keys, and the
9387 connection to one of the bridges failed, you would cancel all
9388 pending bridge connections. (After all, they all have the same
9389 digest.) Bugfix on 0.2.0.x.
9390 - When a hidden service was trying to establish an introduction point,
9391 and Tor had built circuits preemptively for such purposes, we
9392 were ignoring all the preemptive circuits and launching a new one
9393 instead. Bugfix on 0.2.0.14-alpha.
9394 - When a hidden service was trying to establish an introduction point,
9395 and Tor *did* manage to reuse one of the preemptively built
9396 circuits, it didn't correctly remember which one it used,
9397 so it asked for another one soon after, until there were no
9398 more preemptive circuits, at which point it launched one from
9399 scratch. Bugfix on 0.0.9.x.
9400 - Make directory servers include the X-Your-Address-Is: http header in
9401 their responses even for begin_dir conns. Now clients who only
9402 ever use begin_dir connections still have a way to learn their IP
9403 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
9406 - Fix a macro/CPP interaction that was confusing some compilers:
9407 some GCCs don't like #if/#endif pairs inside macro arguments.
9409 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
9410 Fixes bug 704; fix from Steven Murdoch.
9411 - When opening /dev/null in finish_daemonize(), do not pass the
9412 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
9413 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
9414 - Correctly detect transparent proxy support on Linux hosts that
9415 require in.h to be included before netfilter_ipv4.h. Patch
9417 - Disallow session resumption attempts during the renegotiation
9418 stage of the v2 handshake protocol. Clients should never be trying
9419 session resumption at this point, but apparently some did, in
9420 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
9421 found by Geoff Goodell.
9424 Changes in version 0.2.1.2-alpha - 2008-06-20
9425 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
9426 make it easier to set up your own private Tor network; fixes several
9427 big bugs with using more than one bridge relay; fixes a big bug with
9428 offering hidden services quickly after Tor starts; and uses a better
9429 API for reporting potential bootstrapping problems to the controller.
9432 - New TestingTorNetwork config option to allow adjustment of
9433 previously constant values that, while reasonable, could slow
9434 bootstrapping. Implements proposal 135. Patch from Karsten.
9437 - If you have more than one bridge but don't know their digests,
9438 you would only learn a request for the descriptor of the first one
9439 on your list. (Tor considered launching requests for the others, but
9440 found that it already had a connection on the way for $0000...0000
9441 so it didn't open another.) Bugfix on 0.2.0.x.
9442 - If you have more than one bridge but don't know their digests,
9443 and the connection to one of the bridges failed, you would cancel
9444 all pending bridge connections. (After all, they all have the
9445 same digest.) Bugfix on 0.2.0.x.
9446 - When establishing a hidden service, introduction points that
9447 originate from cannibalized circuits are completely ignored and not
9448 included in rendezvous service descriptors. This might be another
9449 reason for delay in making a hidden service available. Bugfix
9450 from long ago (0.0.9.x?)
9453 - Allow OpenSSL to use dynamic locks if it wants.
9454 - When building a consensus, do not include routers that are down.
9455 This will cut down 30% to 40% on consensus size. Implements
9457 - In directory authorities' approved-routers files, allow
9458 fingerprints with or without space.
9459 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
9460 controller can query our current bootstrap state in case it attaches
9461 partway through and wants to catch up.
9462 - Send an initial "Starting" bootstrap status event, so we have a
9463 state to start out in.
9466 - Asking for a conditional consensus at .../consensus/<fingerprints>
9467 would crash a dirserver if it did not already have a
9468 consensus. Bugfix on 0.2.1.1-alpha.
9469 - Clean up some macro/CPP interactions: some GCC versions don't like
9470 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
9473 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
9474 - Directory authorities shouldn't complain about bootstrapping
9475 problems just because they do a lot of reachability testing and
9476 some of the connection attempts fail.
9477 - Start sending "count" and "recommendation" key/value pairs in
9478 bootstrap problem status events, so the controller can hear about
9479 problems even before Tor decides they're worth reporting for sure.
9480 - If you're using bridges, generate "bootstrap problem" warnings
9481 as soon as you run out of working bridges, rather than waiting
9482 for ten failures -- which will never happen if you have less than
9484 - If we close our OR connection because there's been a circuit
9485 pending on it for too long, we were telling our bootstrap status
9486 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
9489 Changes in version 0.2.1.1-alpha - 2008-06-13
9490 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
9491 were making the Tor process bloat especially on Linux; makes our TLS
9492 handshake blend in better; sends "bootstrap phase" status events to
9493 the controller, so it can keep the user informed of progress (and
9494 problems) fetching directory information and establishing circuits;
9495 and adds a variety of smaller features.
9498 - More work on making our TLS handshake blend in: modify the list
9499 of ciphers advertised by OpenSSL in client mode to even more
9500 closely resemble a common web browser. We cheat a little so that
9501 we can advertise ciphers that the locally installed OpenSSL doesn't
9503 - Start sending "bootstrap phase" status events to the controller,
9504 so it can keep the user informed of progress fetching directory
9505 information and establishing circuits. Also inform the controller
9506 if we think we're stuck at a particular bootstrap phase. Implements
9508 - Resume using OpenSSL's RAND_poll() for better (and more portable)
9509 cross-platform entropy collection again. We used to use it, then
9510 stopped using it because of a bug that could crash systems that
9511 called RAND_poll when they had a lot of fds open. It looks like the
9512 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
9513 at startup, and to call RAND_poll() when we reseed later only if
9514 we have a non-buggy OpenSSL version.
9517 - When we choose to abandon a new entry guard because we think our
9518 older ones might be better, close any circuits pending on that
9519 new entry guard connection. This fix should make us recover much
9520 faster when our network is down and then comes back. Bugfix on
9521 0.1.2.8-beta; found by lodger.
9523 o Memory fixes and improvements:
9524 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
9525 to avoid unused RAM in buffer chunks and memory pools.
9526 - Speed up parsing and cut down on memory fragmentation by using
9527 stack-style allocations for parsing directory objects. Previously,
9528 this accounted for over 40% of allocations from within Tor's code
9529 on a typical directory cache.
9530 - Use a Bloom filter rather than a digest-based set to track which
9531 descriptors we need to keep around when we're cleaning out old
9532 router descriptors. This speeds up the computation significantly,
9533 and may reduce fragmentation.
9534 - Reduce the default smartlist size from 32 to 16; it turns out that
9535 most smartlists hold around 8-12 elements tops.
9536 - Make dumpstats() log the fullness and size of openssl-internal
9538 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
9539 patch to their OpenSSL, turn it on to save memory on servers. This
9540 patch will (with any luck) get included in a mainline distribution
9542 - Never use OpenSSL compression: it wastes RAM and CPU trying to
9543 compress cells, which are basically all encrypted, compressed,
9547 - Stop reloading the router list from disk for no reason when we
9548 run out of reachable directory mirrors. Once upon a time reloading
9549 it would set the 'is_running' flag back to 1 for them. It hasn't
9550 done that for a long time.
9551 - In very rare situations new hidden service descriptors were
9552 published earlier than 30 seconds after the last change to the
9553 service. (We currently think that a hidden service descriptor
9554 that's been stable for 30 seconds is worth publishing.)
9557 - Allow separate log levels to be configured for different logging
9558 domains. For example, this allows one to log all notices, warnings,
9559 or errors, plus all memory management messages of level debug or
9560 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
9561 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
9562 and stop using a warning that had become unfixably verbose under
9564 - New --hush command-line option similar to --quiet. While --quiet
9565 disables all logging to the console on startup, --hush limits the
9566 output to messages of warning and error severity.
9567 - Servers support a new URL scheme for consensus downloads that
9568 allows the client to specify which authorities are trusted.
9569 The server then only sends the consensus if the client will trust
9570 it. Otherwise a 404 error is sent back. Clients use this
9571 new scheme when the server supports it (meaning it's running
9572 0.2.1.1-alpha or later). Implements proposal 134.
9573 - New configure/torrc options (--enable-geoip-stats,
9574 DirRecordUsageByCountry) to record how many IPs we've served
9575 directory info to in each country code, how many status documents
9576 total we've sent to each country code, and what share of the total
9577 directory requests we should expect to see.
9578 - Use the TLS1 hostname extension to more closely resemble browser
9580 - Lots of new unit tests.
9581 - Add a macro to implement the common pattern of iterating through
9582 two parallel lists in lockstep.
9585 Changes in version 0.2.0.28-rc - 2008-06-13
9586 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
9587 performance bug, and fixes a bunch of smaller bugs.
9590 - Fix a bug where, when we were choosing the 'end stream reason' to
9591 put in our relay end cell that we send to the exit relay, Tor
9592 clients on Windows were sometimes sending the wrong 'reason'. The
9593 anonymity problem is that exit relays may be able to guess whether
9594 the client is running Windows, thus helping partition the anonymity
9595 set. Down the road we should stop sending reasons to exit relays,
9596 or otherwise prevent future versions of this bug.
9599 - While setting up a hidden service, some valid introduction circuits
9600 were overlooked and abandoned. This might be the reason for
9601 the long delay in making a hidden service available. Bugfix on
9605 - Update to the "June 9 2008" ip-to-country file.
9606 - Run 'make test' as part of 'make dist', so we stop releasing so
9607 many development snapshots that fail their unit tests.
9610 - When we're checking if we have enough dir info for each relay
9611 to begin establishing circuits, make sure that we actually have
9612 the descriptor listed in the consensus, not just any descriptor.
9614 - Bridge relays no longer print "xx=0" in their extrainfo document
9615 for every single country code in the geoip db. Bugfix on
9617 - Only warn when we fail to load the geoip file if we were planning to
9618 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
9619 - If we change our MaxAdvertisedBandwidth and then reload torrc,
9620 Tor won't realize it should publish a new relay descriptor. Fixes
9621 bug 688, reported by mfr. Bugfix on 0.1.2.x.
9622 - When we haven't had any application requests lately, don't bother
9623 logging that we have expired a bunch of descriptors. Bugfix
9625 - Make relay cells written on a connection count as non-padding when
9626 tracking how long a connection has been in use. Bugfix on
9627 0.2.0.1-alpha. Spotted by lodger.
9628 - Fix unit tests in 0.2.0.27-rc.
9629 - Fix compile on Windows.
9632 Changes in version 0.2.0.27-rc - 2008-06-03
9633 Tor 0.2.0.27-rc adds a few features we left out of the earlier
9634 release candidates. In particular, we now include an IP-to-country
9635 GeoIP database, so controllers can easily look up what country a
9636 given relay is in, and so bridge relays can give us some sanitized
9637 summaries about which countries are making use of bridges. (See proposal
9638 126-geoip-fetching.txt for details.)
9641 - Include an IP-to-country GeoIP file in the tarball, so bridge
9642 relays can report sanitized summaries of the usage they're seeing.
9645 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
9646 Robert Hogan. Fixes the first part of bug 681.
9647 - Make bridge authorities never serve extrainfo docs.
9648 - Add support to detect Libevent versions in the 1.4.x series
9650 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
9651 - Include a new contrib/tor-exit-notice.html file that exit relay
9652 operators can put on their website to help reduce abuse queries.
9655 - When tunneling an encrypted directory connection, and its first
9656 circuit fails, do not leave it unattached and ask the controller
9657 to deal. Fixes the second part of bug 681.
9658 - Make bridge authorities correctly expire old extrainfo documents
9662 Changes in version 0.2.0.26-rc - 2008-05-13
9663 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
9664 in Debian's OpenSSL packages. All users running any 0.2.0.x version
9665 should upgrade, whether they're running Debian or not.
9667 o Major security fixes:
9668 - Use new V3 directory authority keys on the tor26, gabelmoo, and
9669 moria1 V3 directory authorities. The old keys were generated with
9670 a vulnerable version of Debian's OpenSSL package, and must be
9671 considered compromised. Other authorities' keys were not generated
9672 with an affected version of OpenSSL.
9675 - List authority signatures as "unrecognized" based on DirServer
9676 lines, not on cert cache. Bugfix on 0.2.0.x.
9679 - Add a new V3AuthUseLegacyKey option to make it easier for
9680 authorities to change their identity keys if they have to.
9683 Changes in version 0.2.0.25-rc - 2008-04-23
9684 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
9687 - Remember to initialize threading before initializing logging.
9688 Otherwise, many BSD-family implementations will crash hard on
9689 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
9692 - Authorities correctly free policies on bad servers on
9693 exit. Fixes bug 672. Bugfix on 0.2.0.x.
9696 Changes in version 0.2.0.24-rc - 2008-04-22
9697 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
9698 v3 directory authority, makes relays with dynamic IP addresses and no
9699 DirPort notice more quickly when their IP address changes, fixes a few
9700 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
9702 o New directory authorities:
9703 - Take lefkada out of the list of v3 directory authorities, since
9704 it has been down for months.
9705 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
9709 - Detect address changes more quickly on non-directory mirror
9710 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
9712 o Minor features (security):
9713 - Reject requests for reverse-dns lookup of names that are in
9714 a private address space. Patch from lodger.
9715 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
9718 o Minor bugfixes (crashes):
9719 - Avoid a rare assert that can trigger when Tor doesn't have much
9720 directory information yet and it tries to fetch a v2 hidden
9721 service descriptor. Fixes bug 651, reported by nwf.
9722 - Initialize log mutex before initializing dmalloc. Otherwise,
9723 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
9724 - Use recursive pthread mutexes in order to avoid deadlock when
9725 logging debug-level messages to a controller. Bug spotted by nwf,
9726 bugfix on 0.2.0.16-alpha.
9728 o Minor bugfixes (resource management):
9729 - Keep address policies from leaking memory: start their refcount
9730 at 1, not 2. Bugfix on 0.2.0.16-alpha.
9731 - Free authority certificates on exit, so they don't look like memory
9732 leaks. Bugfix on 0.2.0.19-alpha.
9733 - Free static hashtables for policy maps and for TLS connections on
9734 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
9735 - Avoid allocating extra space when computing consensuses on 64-bit
9736 platforms. Bug spotted by aakova.
9738 o Minor bugfixes (misc):
9739 - Do not read the configuration file when we've only been told to
9740 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
9741 based on patch from Sebastian Hahn.
9742 - Exit relays that are used as a client can now reach themselves
9743 using the .exit notation, rather than just launching an infinite
9744 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
9745 - When attempting to open a logfile fails, tell us why.
9746 - Fix a dumb bug that was preventing us from knowing that we should
9747 preemptively build circuits to handle expected directory requests.
9748 Fixes bug 660. Bugfix on 0.1.2.x.
9749 - Warn less verbosely about clock skew from netinfo cells from
9750 untrusted sources. Fixes bug 663.
9751 - Make controller stream events for DNS requests more consistent,
9752 by adding "new stream" events for DNS requests, and removing
9753 spurious "stream closed" events" for cached reverse resolves.
9754 Patch from mwenge. Fixes bug 646.
9755 - Correctly notify one-hop connections when a circuit build has
9756 failed. Possible fix for bug 669. Found by lodger.
9759 Changes in version 0.2.0.23-rc - 2008-03-24
9760 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
9761 makes bootstrapping faster if the first directory mirror you contact
9762 is down. The bundles also include the new Vidalia 0.1.2 release.
9765 - When a tunneled directory request is made to a directory server
9766 that's down, notice after 30 seconds rather than 120 seconds. Also,
9767 fail any begindir streams that are pending on it, so they can
9768 retry elsewhere. This was causing multi-minute delays on bootstrap.
9771 Changes in version 0.2.0.22-rc - 2008-03-18
9772 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
9773 enables encrypted directory connections by default for non-relays, fixes
9774 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
9775 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
9778 - Enable encrypted directory connections by default for non-relays,
9779 so censor tools that block Tor directory connections based on their
9780 plaintext patterns will no longer work. This means Tor works in
9781 certain censored countries by default again.
9784 - Make sure servers always request certificates from clients during
9785 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
9786 - Do not enter a CPU-eating loop when a connection is closed in
9787 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
9788 diagnosed by lodger; bugfix on 0.2.0.20-rc.
9789 - Fix assertion failure that could occur when a blocked circuit
9790 became unblocked, and it had pending client DNS requests. Bugfix
9791 on 0.2.0.1-alpha. Fixes bug 632.
9793 o Minor bugfixes (on 0.1.2.x):
9794 - Generate "STATUS_SERVER" events rather than misspelled
9795 "STATUS_SEVER" events. Caught by mwenge.
9796 - When counting the number of bytes written on a TLS connection,
9797 look at the BIO actually used for writing to the network, not
9798 at the BIO used (sometimes) to buffer data for the network.
9799 Looking at different BIOs could result in write counts on the
9800 order of ULONG_MAX. Fixes bug 614.
9801 - On Windows, correctly detect errors when listing the contents of
9802 a directory. Fix from lodger.
9804 o Minor bugfixes (on 0.2.0.x):
9805 - Downgrade "sslv3 alert handshake failure" message to INFO.
9806 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
9807 left BandwidthRate and BandwidthBurst at the default, we would be
9808 silently limited by those defaults. Now raise them to match the
9809 RelayBandwidth* values.
9810 - Fix the SVK version detection logic to work correctly on a branch.
9811 - Make --enable-openbsd-malloc work correctly on Linux with alpha
9812 CPUs. Fixes bug 625.
9813 - Logging functions now check that the passed severity is sane.
9814 - Use proper log levels in the testsuite call of
9815 get_interface_address6().
9816 - When using a nonstandard malloc, do not use the platform values for
9817 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
9818 - Make the openbsd malloc code use 8k pages on alpha CPUs and
9820 - Detect mismatched page sizes when using --enable-openbsd-malloc.
9821 - Avoid double-marked-for-close warning when certain kinds of invalid
9822 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
9823 for bug 617. Bugfix on 0.2.0.1-alpha.
9824 - Make sure that the "NULL-means-reject *:*" convention is followed by
9825 all the policy manipulation functions, avoiding some possible crash
9826 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
9827 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
9828 actually works, and doesn't warn about every single reverse lookup.
9829 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
9832 - Only log guard node status when guard node status has changed.
9833 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
9834 make "INFO" 75% less verbose.
9837 Changes in version 0.2.0.21-rc - 2008-03-02
9838 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
9839 makes Tor work well with Vidalia again, fixes a rare assert bug,
9840 and fixes a pair of more minor bugs. The bundles also include Vidalia
9841 0.1.0 and Torbutton 1.1.16.
9844 - The control port should declare that it requires password auth
9845 when HashedControlSessionPassword is set too. Patch from Matt Edman;
9846 bugfix on 0.2.0.20-rc. Fixes bug 615.
9847 - Downgrade assert in connection_buckets_decrement() to a log message.
9848 This may help us solve bug 614, and in any case will make its
9849 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
9850 - We were sometimes miscounting the number of bytes read from the
9851 network, causing our rate limiting to not be followed exactly.
9852 Bugfix on 0.2.0.16-alpha. Reported by lodger.
9855 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
9856 OpenSSL versions should have been working fine. Diagnosis and patch
9857 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
9858 Bugfix on 0.2.0.20-rc.
9861 Changes in version 0.2.0.20-rc - 2008-02-24
9862 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
9863 makes more progress towards normalizing Tor's TLS handshake, makes
9864 hidden services work better again, helps relays bootstrap if they don't
9865 know their IP address, adds optional support for linking in openbsd's
9866 allocator or tcmalloc, allows really fast relays to scale past 15000
9867 sockets, and fixes a bunch of minor bugs reported by Veracode.
9870 - Enable the revised TLS handshake based on the one designed by
9871 Steven Murdoch in proposal 124, as revised in proposal 130. It
9872 includes version negotiation for OR connections as described in
9873 proposal 105. The new handshake is meant to be harder for censors
9874 to fingerprint, and it adds the ability to detect certain kinds of
9875 man-in-the-middle traffic analysis attacks. The version negotiation
9876 feature will allow us to improve Tor's link protocol more safely
9878 - Choose which bridge to use proportional to its advertised bandwidth,
9879 rather than uniformly at random. This should speed up Tor for
9880 bridge users. Also do this for people who set StrictEntryNodes.
9881 - When a TrackHostExits-chosen exit fails too many times in a row,
9882 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
9885 - Resolved problems with (re-)fetching hidden service descriptors.
9886 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
9888 - If we only ever used Tor for hidden service lookups or posts, we
9889 would stop building circuits and start refusing connections after
9890 24 hours, since we falsely believed that Tor was dormant. Reported
9891 by nwf; bugfix on 0.1.2.x.
9892 - Servers that don't know their own IP address should go to the
9893 authorities for their first directory fetch, even if their DirPort
9894 is off or if they don't know they're reachable yet. This will help
9895 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
9896 - When counting the number of open sockets, count not only the number
9897 of sockets we have received from the socket() call, but also
9898 the number we've gotten from accept() and socketpair(). This bug
9899 made us fail to count all sockets that we were using for incoming
9900 connections. Bugfix on 0.2.0.x.
9901 - Fix code used to find strings within buffers, when those strings
9902 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
9903 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
9904 - Add a new __HashedControlSessionPassword option for controllers
9905 to use for one-off session password hashes that shouldn't get
9906 saved to disk by SAVECONF --- Vidalia users were accumulating a
9907 pile of HashedControlPassword lines in their torrc files, one for
9908 each time they had restarted Tor and then clicked Save. Make Tor
9909 automatically convert "HashedControlPassword" to this new option but
9910 only when it's given on the command line. Partial fix for bug 586.
9912 o Minor features (performance):
9913 - Tune parameters for cell pool allocation to minimize amount of
9915 - Add OpenBSD malloc code from phk as an optional malloc
9916 replacement on Linux: some glibc libraries do very poorly
9917 with Tor's memory allocation patterns. Pass
9918 --enable-openbsd-malloc to get the replacement malloc code.
9919 - Add a --with-tcmalloc option to the configure script to link
9920 against tcmalloc (if present). Does not yet search for
9921 non-system include paths.
9922 - Stop imposing an arbitrary maximum on the number of file descriptors
9923 used for busy servers. Bug reported by Olaf Selke; patch from
9926 o Minor features (other):
9927 - When SafeLogging is disabled, log addresses along with all TLS
9929 - When building with --enable-gcc-warnings, check for whether Apple's
9930 warning "-Wshorten-64-to-32" is available.
9931 - Add a --passphrase-fd argument to the tor-gencert command for
9934 o Minor bugfixes (memory leaks and code problems):
9935 - We were leaking a file descriptor if Tor started with a zero-length
9936 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
9937 - Detect size overflow in zlib code. Reported by Justin Ferguson and
9939 - We were comparing the raw BridgePassword entry with a base64'ed
9940 version of it, when handling a "/tor/networkstatus-bridges"
9941 directory request. Now compare correctly. Noticed by Veracode.
9942 - Recover from bad tracked-since value in MTBF-history file.
9944 - Alter the code that tries to recover from unhandled write
9945 errors, to not try to flush onto a socket that's given us
9946 unhandled errors. Bugfix on 0.1.2.x.
9947 - Make Unix controlsockets work correctly on OpenBSD. Patch from
9948 tup. Bugfix on 0.2.0.3-alpha.
9950 o Minor bugfixes (other):
9951 - If we have an extra-info document for our server, always make
9952 it available on the control port, even if we haven't gotten
9953 a copy of it from an authority yet. Patch from mwenge.
9954 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
9955 - Directory mirrors no longer include a guess at the client's IP
9956 address if the connection appears to be coming from the same /24
9957 network; it was producing too many wrong guesses.
9958 - Make the new hidden service code respect the SafeLogging setting.
9959 Bugfix on 0.2.0.x. Patch from Karsten.
9960 - When starting as an authority, do not overwrite all certificates
9961 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
9962 - If we're trying to flush the last bytes on a connection (for
9963 example, when answering a directory request), reset the
9964 time-to-give-up timeout every time we manage to write something
9965 on the socket. Bugfix on 0.1.2.x.
9966 - Change the behavior of "getinfo status/good-server-descriptor"
9967 so it doesn't return failure when any authority disappears.
9968 - Even though the man page said that "TrackHostExits ." should
9969 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
9970 - Report TLS "zero return" case as a "clean close" and "IO error"
9971 as a "close". Stop calling closes "unexpected closes": existing
9972 Tors don't use SSL_close(), so having a connection close without
9973 the TLS shutdown handshake is hardly unexpected.
9974 - Send NAMESERVER_STATUS messages for a single failed nameserver
9977 o Code simplifications and refactoring:
9978 - Remove the tor_strpartition function: its logic was confused,
9979 and it was only used for one thing that could be implemented far
9983 Changes in version 0.2.0.19-alpha - 2008-02-09
9984 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
9985 handshake, makes path selection for relays more secure and IP address
9986 guessing more robust, and generally fixes a lot of bugs in preparation
9987 for calling the 0.2.0 branch stable.
9990 - Do not include recognizeable strings in the commonname part of
9991 Tor's x509 certificates.
9994 - If we're a relay, avoid picking ourselves as an introduction point,
9995 a rendezvous point, or as the final hop for internal circuits. Bug
9996 reported by taranis and lodger. Bugfix on 0.1.2.x.
9997 - Patch from "Andrew S. Lists" to catch when we contact a directory
9998 mirror at IP address X and he says we look like we're coming from
9999 IP address X. Bugfix on 0.1.2.x.
10001 o Minor features (security):
10002 - Be more paranoid about overwriting sensitive memory on free(),
10003 as a defensive programming tactic to ensure forward secrecy.
10005 o Minor features (directory authority):
10006 - Actually validate the options passed to AuthDirReject,
10007 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
10008 - Reject router descriptors with out-of-range bandwidthcapacity or
10009 bandwidthburst values.
10011 o Minor features (controller):
10012 - Reject controller commands over 1MB in length. This keeps rogue
10013 processes from running us out of memory.
10015 o Minor features (misc):
10016 - Give more descriptive well-formedness errors for out-of-range
10017 hidden service descriptor/protocol versions.
10018 - Make memory debugging information describe more about history
10019 of cell allocation, so we can help reduce our memory use.
10021 o Deprecated features (controller):
10022 - The status/version/num-versioning and status/version/num-concurring
10023 GETINFO options are no longer useful in the v3 directory protocol:
10024 treat them as deprecated, and warn when they're used.
10027 - When our consensus networkstatus has been expired for a while, stop
10028 being willing to build circuits using it. Fixes bug 401. Bugfix
10030 - Directory caches now fetch certificates from all authorities
10031 listed in a networkstatus consensus, even when they do not
10032 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
10033 - When connecting to a bridge without specifying its key, insert
10034 the connection into the identity-to-connection map as soon as
10035 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
10036 - Detect versions of OS X where malloc_good_size() is present in the
10037 library but never actually declared. Resolves bug 587. Bugfix
10039 - Stop incorrectly truncating zlib responses to directory authority
10040 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
10041 - Stop recommending that every server operator send mail to tor-ops.
10042 Resolves bug 597. Bugfix on 0.1.2.x.
10043 - Don't trigger an assert if we start a directory authority with a
10044 private IP address (like 127.0.0.1).
10045 - Avoid possible failures when generating a directory with routers
10046 with over-long versions strings, or too many flags set. Bugfix
10048 - If an attempt to launch a DNS resolve request over the control
10049 port fails because we have overrun the limit on the number of
10050 connections, tell the controller that the request has failed.
10051 - Avoid using too little bandwidth when our clock skips a few
10052 seconds. Bugfix on 0.1.2.x.
10053 - Fix shell error when warning about missing packages in configure
10054 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
10055 - Do not become confused when receiving a spurious VERSIONS-like
10056 cell from a confused v1 client. Bugfix on 0.2.0.x.
10057 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
10058 introduction points for a hidden service have failed. Patch from
10059 Karsten Loesing. Bugfix on 0.2.0.x.
10061 o Code simplifications and refactoring:
10062 - Remove some needless generality from cpuworker code, for improved
10064 - Stop overloading the circuit_t.onionskin field for both "onionskin
10065 from a CREATE cell that we are waiting for a cpuworker to be
10066 assigned" and "onionskin from an EXTEND cell that we are going to
10067 send to an OR as soon as we are connected". Might help with bug 600.
10068 - Add an in-place version of aes_crypt() so that we can avoid doing a
10069 needless memcpy() call on each cell payload.
10072 Changes in version 0.2.0.18-alpha - 2008-01-25
10073 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
10074 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
10075 that can warn or reject connections to ports generally associated with
10076 vulnerable-plaintext protocols.
10078 o New directory authorities:
10079 - Set up dannenberg (run by CCC) as the sixth v3 directory
10083 - Fix a major memory leak when attempting to use the v2 TLS
10084 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
10085 - We accidentally enabled the under-development v2 TLS handshake
10086 code, which was causing log entries like "TLS error while
10087 renegotiating handshake". Disable it again. Resolves bug 590.
10088 - We were computing the wrong Content-Length: header for directory
10089 responses that need to be compressed on the fly, causing clients
10090 asking for those items to always fail. Bugfix on 0.2.0.x; partially
10094 - Avoid going directly to the directory authorities even if you're a
10095 relay, if you haven't found yourself reachable yet or if you've
10096 decided not to advertise your dirport yet. Addresses bug 556.
10097 - If we've gone 12 hours since our last bandwidth check, and we
10098 estimate we have less than 50KB bandwidth capacity but we could
10099 handle more, do another bandwidth test.
10100 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
10101 Tor can warn and/or refuse connections to ports commonly used with
10102 vulnerable-plaintext protocols. Currently we warn on ports 23,
10103 109, 110, and 143, but we don't reject any.
10106 - When we setconf ClientOnly to 1, close any current OR and Dir
10107 listeners. Reported by mwenge.
10108 - When we get a consensus that's been signed by more people than
10109 we expect, don't log about it; it's not a big deal. Reported
10113 - Don't answer "/tor/networkstatus-bridges" directory requests if
10114 the request isn't encrypted.
10115 - Make "ClientOnly 1" config option disable directory ports too.
10116 - Patches from Karsten Loesing to make v2 hidden services more
10117 robust: work even when there aren't enough HSDir relays available;
10118 retry when a v2 rend desc fetch fails; but don't retry if we
10119 already have a usable v0 rend desc.
10122 Changes in version 0.2.0.17-alpha - 2008-01-17
10123 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
10126 - Make the tor-gencert man page get included correctly in the tarball.
10129 Changes in version 0.2.0.16-alpha - 2008-01-17
10130 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
10131 Loesing, and generally cleans up a lot of features and minor bugs.
10133 o New directory authorities:
10134 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
10137 o Major performance improvements:
10138 - Switch our old ring buffer implementation for one more like that
10139 used by free Unix kernels. The wasted space in a buffer with 1mb
10140 of data will now be more like 8k than 1mb. The new implementation
10141 also avoids realloc();realloc(); patterns that can contribute to
10142 memory fragmentation.
10145 - Configuration files now accept C-style strings as values. This
10146 helps encode characters not allowed in the current configuration
10147 file format, such as newline or #. Addresses bug 557.
10148 - Although we fixed bug 539 (where servers would send HTTP status 503
10149 responses _and_ send a body too), there are still servers out
10150 there that haven't upgraded. Therefore, make clients parse such
10151 bodies when they receive them.
10152 - When we're not serving v2 directory information, there is no reason
10153 to actually keep any around. Remove the obsolete files and directory
10154 on startup if they are very old and we aren't going to serve them.
10156 o Minor performance improvements:
10157 - Reference-count and share copies of address policy entries; only 5%
10158 of them were actually distinct.
10159 - Never walk through the list of logs if we know that no log is
10160 interested in a given message.
10163 - When an authority has not signed a consensus, do not try to
10164 download a nonexistent "certificate with key 00000000". Bugfix
10165 on 0.2.0.x. Fixes bug 569.
10166 - Fix a rare assert error when we're closing one of our threads:
10167 use a mutex to protect the list of logs, so we never write to the
10168 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
10169 bug 575, which is kind of the revenge of bug 222.
10170 - Patch from Karsten Loesing to complain less at both the client
10171 and the relay when a relay used to have the HSDir flag but doesn't
10172 anymore, and we try to upload a hidden service descriptor.
10173 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
10175 - Do not try to download missing certificates until we have tried
10176 to check our fallback consensus. Fixes bug 583.
10177 - Make bridges round reported GeoIP stats info up to the nearest
10178 estimate, not down. Now we can distinguish between "0 people from
10179 this country" and "1 person from this country".
10180 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
10181 - Avoid possible segfault if key generation fails in
10182 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
10183 - Avoid segfault in the case where a badly behaved v2 versioning
10184 directory sends a signed networkstatus with missing client-versions.
10186 - Avoid segfaults on certain complex invocations of
10187 router_get_by_hexdigest(). Bugfix on 0.1.2.
10188 - Correct bad index on array access in parse_http_time(). Bugfix
10190 - Fix possible bug in vote generation when server versions are present
10191 but client versions are not.
10192 - Fix rare bug on REDIRECTSTREAM control command when called with no
10193 port set: it could erroneously report an error when none had
10195 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
10196 compressing large objects and find ourselves with more than 4k
10197 left over. Bugfix on 0.2.0.
10198 - Fix a small memory leak when setting up a hidden service.
10199 - Fix a few memory leaks that could in theory happen under bizarre
10201 - Fix an assert if we post a general-purpose descriptor via the
10202 control port but that descriptor isn't mentioned in our current
10203 network consensus. Bug reported by Jon McLachlan; bugfix on
10206 o Minor features (controller):
10207 - Get NS events working again. Patch from tup.
10208 - The GETCONF command now escapes and quotes configuration values
10209 that don't otherwise fit into the torrc file.
10210 - The SETCONF command now handles quoted values correctly.
10212 o Minor features (directory authorities):
10213 - New configuration options to override default maximum number of
10214 servers allowed on a single IP address. This is important for
10215 running a test network on a single host.
10216 - Actually implement the -s option to tor-gencert.
10217 - Add a manual page for tor-gencert.
10219 o Minor features (bridges):
10220 - Bridge authorities no longer serve bridge descriptors over
10221 unencrypted connections.
10223 o Minor features (other):
10224 - Add hidden services and DNSPorts to the list of things that make
10225 Tor accept that it has running ports. Change starting Tor with no
10226 ports from a fatal error to a warning; we might change it back if
10227 this turns out to confuse anybody. Fixes bug 579.
10230 Changes in version 0.1.2.19 - 2008-01-17
10231 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
10232 exit policy a little bit more conservative so it's safer to run an
10233 exit relay on a home system, and fixes a variety of smaller issues.
10236 - Exit policies now reject connections that are addressed to a
10237 relay's public (external) IP address too, unless
10238 ExitPolicyRejectPrivate is turned off. We do this because too
10239 many relays are running nearby to services that trust them based
10240 on network address.
10243 - When the clock jumps forward a lot, do not allow the bandwidth
10244 buckets to become negative. Fixes bug 544.
10245 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
10246 on every successful resolve. Reported by Mike Perry.
10247 - Purge old entries from the "rephist" database and the hidden
10248 service descriptor database even when DirPort is zero.
10249 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
10250 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
10251 crashing or mis-answering these requests.
10252 - When we decide to send a 503 response to a request for servers, do
10253 not then also send the server descriptors: this defeats the whole
10254 purpose. Fixes bug 539.
10257 - Changing the ExitPolicyRejectPrivate setting should cause us to
10258 rebuild our server descriptor.
10259 - Fix handling of hex nicknames when answering controller requests for
10260 networkstatus by name, or when deciding whether to warn about
10261 unknown routers in a config option. (Patch from mwenge.)
10262 - Fix a couple of hard-to-trigger autoconf problems that could result
10263 in really weird results on platforms whose sys/types.h files define
10264 nonstandard integer types.
10265 - Don't try to create the datadir when running --verify-config or
10266 --hash-password. Resolves bug 540.
10267 - If we were having problems getting a particular descriptor from the
10268 directory caches, and then we learned about a new descriptor for
10269 that router, we weren't resetting our failure count. Reported
10271 - Although we fixed bug 539 (where servers would send HTTP status 503
10272 responses _and_ send a body too), there are still servers out there
10273 that haven't upgraded. Therefore, make clients parse such bodies
10274 when they receive them.
10275 - Run correctly on systems where rlim_t is larger than unsigned long.
10276 This includes some 64-bit systems.
10277 - Run correctly on platforms (like some versions of OS X 10.5) where
10278 the real limit for number of open files is OPEN_FILES, not rlim_max
10279 from getrlimit(RLIMIT_NOFILES).
10280 - Avoid a spurious free on base64 failure.
10281 - Avoid segfaults on certain complex invocations of
10282 router_get_by_hexdigest().
10283 - Fix rare bug on REDIRECTSTREAM control command when called with no
10284 port set: it could erroneously report an error when none had
10288 Changes in version 0.2.0.15-alpha - 2007-12-25
10289 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
10290 features added in 0.2.0.13-alpha.
10293 - Fix several remotely triggerable asserts based on DirPort requests
10294 for a v2 or v3 networkstatus object before we were prepared. This
10295 was particularly bad for 0.2.0.13 and later bridge relays, who
10296 would never have a v2 networkstatus and would thus always crash
10297 when used. Bugfixes on 0.2.0.x.
10298 - Estimate the v3 networkstatus size more accurately, rather than
10299 estimating it at zero bytes and giving it artificially high priority
10300 compared to other directory requests. Bugfix on 0.2.0.x.
10303 - Fix configure.in logic for cross-compilation.
10304 - When we load a bridge descriptor from the cache, and it was
10305 previously unreachable, mark it as retriable so we won't just
10306 ignore it. Also, try fetching a new copy immediately. Bugfixes
10308 - The bridge GeoIP stats were counting other relays, for example
10309 self-reachability and authority-reachability tests.
10312 - Support compilation to target iPhone; patch from cjacker huang.
10313 To build for iPhone, pass the --enable-iphone option to configure.
10316 Changes in version 0.2.0.14-alpha - 2007-12-23
10318 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
10319 without a datadirectory from a previous Tor install. Reported
10321 - Fix a crash when we fetch a descriptor that turns out to be
10322 unexpected (it used to be in our networkstatus when we started
10323 fetching it, but it isn't in our current networkstatus), and we
10324 aren't using bridges. Bugfix on 0.2.0.x.
10325 - Fix a crash when accessing hidden services: it would work the first
10326 time you use a given introduction point for your service, but
10327 on subsequent requests we'd be using garbage memory. Fixed by
10328 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
10329 - Fix a crash when we load a bridge descriptor from disk but we don't
10330 currently have a Bridge line for it in our torrc. Bugfix on
10334 - If bridge authorities set BridgePassword, they will serve a
10335 snapshot of known bridge routerstatuses from their DirPort to
10336 anybody who knows that password. Unset by default.
10339 - Make the unit tests build again.
10340 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
10341 - Make PublishServerDescriptor default to 1, so the default doesn't
10342 have to change as we invent new directory protocol versions.
10343 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
10344 be included unless sys/time.h is already included. Fixes
10345 bug 553. Bugfix on 0.2.0.x.
10346 - If we receive a general-purpose descriptor and then receive an
10347 identical bridge-purpose descriptor soon after, don't discard
10348 the next one as a duplicate.
10351 - If BridgeRelay is set to 1, then the default for
10352 PublishServerDescriptor is now "bridge" rather than "v2,v3".
10353 - If the user sets RelayBandwidthRate but doesn't set
10354 RelayBandwidthBurst, then make them equal rather than erroring out.
10357 Changes in version 0.2.0.13-alpha - 2007-12-21
10358 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
10359 Goodell, fixes many more bugs, and adds a lot of infrastructure for
10362 o New directory authorities:
10363 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
10367 - Only update guard status (usable / not usable) once we have
10368 enough directory information. This was causing us to always pick
10369 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
10370 causing us to discard all our guards on startup if we hadn't been
10371 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
10372 - Purge old entries from the "rephist" database and the hidden
10373 service descriptor databases even when DirPort is zero. Bugfix
10375 - We were ignoring our RelayBandwidthRate for the first 30 seconds
10376 after opening a circuit -- even a relayed circuit. Bugfix on
10378 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
10379 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
10380 crashing or mis-answering these types of requests.
10381 - Relays were publishing their server descriptor to v1 and v2
10382 directory authorities, but they didn't try publishing to v3-only
10383 authorities. Fix this; and also stop publishing to v1 authorities.
10385 - When we were reading router descriptors from cache, we were ignoring
10386 the annotations -- so for example we were reading in bridge-purpose
10387 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
10388 - When we decided to send a 503 response to a request for servers, we
10389 were then also sending the server descriptors: this defeats the
10390 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
10393 - Bridge relays now behave like clients with respect to time
10394 intervals for downloading new consensus documents -- otherwise they
10395 stand out. Bridge users now wait until the end of the interval,
10396 so their bridge relay will be sure to have a new consensus document.
10397 - Three new config options (AlternateDirAuthority,
10398 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
10399 user selectively replace the default directory authorities by type,
10400 rather than the all-or-nothing replacement that DirServer offers.
10401 - Tor can now be configured to read a GeoIP file from disk in one
10402 of two formats. This can be used by controllers to map IP addresses
10403 to countries. Eventually, it may support exit-by-country.
10404 - When possible, bridge relays remember which countries users
10405 are coming from, and report aggregate information in their
10406 extra-info documents, so that the bridge authorities can learn
10407 where Tor is blocked.
10408 - Bridge directory authorities now do reachability testing on the
10409 bridges they know. They provide router status summaries to the
10410 controller via "getinfo ns/purpose/bridge", and also dump summaries
10411 to a file periodically.
10412 - Stop fetching directory info so aggressively if your DirPort is
10413 on but your ORPort is off; stop fetching v2 dir info entirely.
10414 You can override these choices with the new FetchDirInfoEarly
10418 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
10419 consensus documents when there are too many relays at a single
10420 IP address. Now clear it in v2 network status documents too, and
10421 also clear it in routerinfo_t when the relay is no longer listed
10422 in the relevant networkstatus document.
10423 - Don't crash if we get an unexpected value for the
10424 PublishServerDescriptor config option. Reported by Matt Edman;
10425 bugfix on 0.2.0.9-alpha.
10426 - Our new v2 hidden service descriptor format allows descriptors
10427 that have no introduction points. But Tor crashed when we tried
10428 to build a descriptor with no intro points (and it would have
10429 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
10430 by Karsten Loesing.
10431 - Fix building with dmalloc 5.5.2 with glibc.
10432 - Reject uploaded descriptors and extrainfo documents if they're
10433 huge. Otherwise we'll cache them all over the network and it'll
10434 clog everything up. Reported by Aljosha Judmayer.
10435 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
10436 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
10437 - When the DANGEROUS_VERSION controller status event told us we're
10438 running an obsolete version, it used the string "OLD" to describe
10439 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
10440 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
10441 - If we can't expand our list of entry guards (e.g. because we're
10442 using bridges or we have StrictEntryNodes set), don't mark relays
10443 down when they fail a directory request. Otherwise we're too quick
10444 to mark all our entry points down. Bugfix on 0.1.2.x.
10445 - Fix handling of hex nicknames when answering controller requests for
10446 networkstatus by name, or when deciding whether to warn about unknown
10447 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
10448 - Fix a couple of hard-to-trigger autoconf problems that could result
10449 in really weird results on platforms whose sys/types.h files define
10450 nonstandard integer types. Bugfix on 0.1.2.x.
10451 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
10452 - Don't crash on name lookup when we have no current consensus. Fixes
10453 bug 538; bugfix on 0.2.0.x.
10454 - Only Tors that want to mirror the v2 directory info should
10455 create the "cached-status" directory in their datadir. (All Tors
10456 used to create it.) Bugfix on 0.2.0.9-alpha.
10457 - Directory authorities should only automatically download Extra Info
10458 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
10461 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
10462 consumers. (We already do this on HUP.)
10463 - Authorities and caches fetch the v2 networkstatus documents
10464 less often, now that v3 is encouraged.
10465 - Add a new config option BridgeRelay that specifies you want to
10466 be a bridge relay. Right now the only difference is that it makes
10467 you answer begin_dir requests, and it makes you cache dir info,
10468 even if your DirPort isn't on.
10469 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
10470 ask about source, timestamp of arrival, purpose, etc. We need
10471 something like this to help Vidalia not do GeoIP lookups on bridge
10473 - Allow multiple HashedControlPassword config lines, to support
10474 multiple controller passwords.
10475 - Authorities now decide whether they're authoritative for a given
10476 router based on the router's purpose.
10477 - New config options AuthDirBadDir and AuthDirListBadDirs for
10478 authorities to mark certain relays as "bad directories" in the
10479 networkstatus documents. Also supports the "!baddir" directive in
10480 the approved-routers file.
10483 Changes in version 0.2.0.12-alpha - 2007-11-16
10484 This twelfth development snapshot fixes some more build problems as
10485 well as a few minor bugs.
10488 - Make it build on OpenBSD again. Patch from tup.
10489 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
10490 package-building for Red Hat, OS X, etc.
10492 o Minor bugfixes (on 0.1.2.x):
10493 - Changing the ExitPolicyRejectPrivate setting should cause us to
10494 rebuild our server descriptor.
10496 o Minor bugfixes (on 0.2.0.x):
10497 - When we're lacking a consensus, don't try to perform rendezvous
10498 operations. Reported by Karsten Loesing.
10499 - Fix a small memory leak whenever we decide against using a
10500 newly picked entry guard. Reported by Mike Perry.
10501 - When authorities detected more than two relays running on the same
10502 IP address, they were clearing all the status flags but forgetting
10503 to clear the "hsdir" flag. So clients were being told that a
10504 given relay was the right choice for a v2 hsdir lookup, yet they
10505 never had its descriptor because it was marked as 'not running'
10507 - If we're trying to fetch a bridge descriptor and there's no way
10508 the bridge authority could help us (for example, we don't know
10509 a digest, or there is no bridge authority), don't be so eager to
10510 fall back to asking the bridge authority.
10511 - If we're using bridges or have strictentrynodes set, and our
10512 chosen exit is in the same family as all our bridges/entry guards,
10513 then be flexible about families.
10516 - When we negotiate a v2 link-layer connection (not yet implemented),
10517 accept RELAY_EARLY cells and turn them into RELAY cells if we've
10518 negotiated a v1 connection for their next step. Initial code for
10522 Changes in version 0.2.0.11-alpha - 2007-11-12
10523 This eleventh development snapshot fixes some build problems with
10524 the previous snapshot. It also includes a more secure-by-default exit
10525 policy for relays, fixes an enormous memory leak for exit relays, and
10526 fixes another bug where servers were falling out of the directory list.
10529 - Exit policies now reject connections that are addressed to a
10530 relay's public (external) IP address too, unless
10531 ExitPolicyRejectPrivate is turned off. We do this because too
10532 many relays are running nearby to services that trust them based
10533 on network address. Bugfix on 0.1.2.x.
10536 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
10537 on every successful resolve. Reported by Mike Perry; bugfix
10539 - On authorities, never downgrade to old router descriptors simply
10540 because they're listed in the consensus. This created a catch-22
10541 where we wouldn't list a new descriptor because there was an
10542 old one in the consensus, and we couldn't get the new one in the
10543 consensus because we wouldn't list it. Possible fix for bug 548.
10544 Also, this might cause bug 543 to appear on authorities; if so,
10545 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
10547 o Packaging fixes on 0.2.0.10-alpha:
10548 - We were including instructions about what to do with the
10549 src/config/fallback-consensus file, but we weren't actually
10550 including it in the tarball. Disable all of that for now.
10553 - Allow people to say PreferTunnelledDirConns rather than
10554 PreferTunneledDirConns, for those alternate-spellers out there.
10557 - Don't reevaluate all the information from our consensus document
10558 just because we've downloaded a v2 networkstatus that we intend
10559 to cache. Fixes bug 545; bugfix on 0.2.0.x.
10562 Changes in version 0.2.0.10-alpha - 2007-11-10
10563 This tenth development snapshot adds a third v3 directory authority
10564 run by Mike Perry, adds most of Karsten Loesing's new hidden service
10565 descriptor format, fixes a bad crash bug and new bridge bugs introduced
10566 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
10567 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
10568 addresses many more minor issues.
10570 o New directory authorities:
10571 - Set up ides (run by Mike Perry) as the third v3 directory authority.
10574 - Allow tunnelled directory connections to ask for an encrypted
10575 "begin_dir" connection or an anonymized "uses a full Tor circuit"
10576 connection independently. Now we can make anonymized begin_dir
10577 connections for (e.g.) more secure hidden service posting and
10579 - More progress on proposal 114: code from Karsten Loesing to
10580 implement new hidden service descriptor format.
10581 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
10582 accommodate the growing number of servers that use the default
10583 and are reaching it.
10584 - Directory authorities use a new formula for selecting which nodes
10585 to advertise as Guards: they must be in the top 7/8 in terms of
10586 how long we have known about them, and above the median of those
10587 nodes in terms of weighted fractional uptime.
10588 - Make "not enough dir info yet" warnings describe *why* Tor feels
10589 it doesn't have enough directory info yet.
10592 - Stop servers from crashing if they set a Family option (or
10593 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
10595 - Make bridge users work again -- the move to v3 directories in
10596 0.2.0.9-alpha had introduced a number of bugs that made bridges
10597 no longer work for clients.
10598 - When the clock jumps forward a lot, do not allow the bandwidth
10599 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
10601 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
10602 - When the consensus lists a router descriptor that we previously were
10603 mirroring, but that we considered non-canonical, reload the
10604 descriptor as canonical. This fixes bug 543 where Tor servers
10605 would start complaining after a few days that they don't have
10606 enough directory information to build a circuit.
10607 - Consider replacing the current consensus when certificates arrive
10608 that make the pending consensus valid. Previously, we were only
10609 considering replacement when the new certs _didn't_ help.
10610 - Fix an assert error on startup if we didn't already have the
10611 consensus and certs cached in our datadirectory: we were caching
10612 the consensus in consensus_waiting_for_certs but then free'ing it
10614 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
10615 Request) if we need more v3 certs but we've already got pending
10616 requests for all of them.
10617 - Correctly back off from failing certificate downloads. Fixes
10619 - Authorities don't vote on the Running flag if they have been running
10620 for less than 30 minutes themselves. Fixes bug 547, where a newly
10621 started authority would vote that everyone was down.
10623 o New requirements:
10624 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
10625 it, it had no AES, and it hasn't seen any security patches since
10629 - Clients now hold circuitless TLS connections open for 1.5 times
10630 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
10631 rebuild a new circuit over them within that timeframe. Previously,
10632 they held them open only for KeepalivePeriod (5 minutes).
10633 - Use "If-Modified-Since" to avoid retrieving consensus
10634 networkstatuses that we already have.
10635 - When we have no consensus, check FallbackNetworkstatusFile (defaults
10636 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
10637 we start knowing some directory caches.
10638 - When we receive a consensus from the future, warn about skew.
10639 - Improve skew reporting: try to give the user a better log message
10640 about how skewed they are, and how much this matters.
10641 - When we have a certificate for an authority, believe that
10642 certificate's claims about the authority's IP address.
10643 - New --quiet command-line option to suppress the default console log.
10644 Good in combination with --hash-password.
10645 - Authorities send back an X-Descriptor-Not-New header in response to
10646 an accepted-but-discarded descriptor upload. Partially implements
10648 - Make the log message for "tls error. breaking." more useful.
10649 - Better log messages about certificate downloads, to attempt to
10650 track down the second incarnation of bug 546.
10652 o Minor features (bridges):
10653 - If bridge users set UpdateBridgesFromAuthority, but the digest
10654 they ask for is a 404 from the bridge authority, they now fall
10655 back to trying the bridge directly.
10656 - Bridges now use begin_dir to publish their server descriptor to
10657 the bridge authority, even when they haven't set TunnelDirConns.
10659 o Minor features (controller):
10660 - When reporting clock skew, and we know that the clock is _at least
10661 as skewed_ as some value, but we don't know the actual value,
10662 report the value as a "minimum skew."
10665 - Update linux-tor-prio.sh script to allow QoS based on the uid of
10666 the Tor process. Patch from Marco Bonetti with tweaks from Mike
10670 - Refuse to start if both ORPort and UseBridges are set. Bugfix
10671 on 0.2.0.x, suggested by Matt Edman.
10672 - Don't stop fetching descriptors when FetchUselessDescriptors is
10673 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
10674 reported by tup and ioerror.
10675 - Better log message on vote from unknown authority.
10676 - Don't log "Launching 0 request for 0 router" message.
10678 o Minor bugfixes (memory leaks):
10679 - Stop leaking memory every time we parse a v3 certificate. Bugfix
10681 - Stop leaking memory every time we load a v3 certificate. Bugfix
10682 on 0.2.0.1-alpha. Fixes bug 536.
10683 - Stop leaking a cached networkstatus on exit. Bugfix on
10685 - Stop leaking voter information every time we free a consensus.
10686 Bugfix on 0.2.0.3-alpha.
10687 - Stop leaking signed data every time we check a voter signature.
10688 Bugfix on 0.2.0.3-alpha.
10689 - Stop leaking a signature every time we fail to parse a consensus or
10690 a vote. Bugfix on 0.2.0.3-alpha.
10691 - Stop leaking v2_download_status_map on shutdown. Bugfix on
10693 - Stop leaking conn->nickname every time we make a connection to a
10694 Tor relay without knowing its expected identity digest (e.g. when
10695 using bridges). Bugfix on 0.2.0.3-alpha.
10697 - Minor bugfixes (portability):
10698 - Run correctly on platforms where rlim_t is larger than unsigned
10699 long, and/or where the real limit for number of open files is
10700 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
10701 particular, these may be needed for OS X 10.5.
10704 Changes in version 0.1.2.18 - 2007-10-28
10705 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
10706 hidden service introduction that were causing huge delays, and a big
10707 bug that was causing some servers to disappear from the network status
10708 lists for a few hours each day.
10710 o Major bugfixes (crashes):
10711 - If a connection is shut down abruptly because of something that
10712 happened inside connection_flushed_some(), do not call
10713 connection_finished_flushing(). Should fix bug 451:
10714 "connection_stop_writing: Assertion conn->write_event failed"
10715 Bugfix on 0.1.2.7-alpha.
10716 - Fix possible segfaults in functions called from
10717 rend_process_relay_cell().
10719 o Major bugfixes (hidden services):
10720 - Hidden services were choosing introduction points uniquely by
10721 hexdigest, but when constructing the hidden service descriptor
10722 they merely wrote the (potentially ambiguous) nickname.
10723 - Clients now use the v2 intro format for hidden service
10724 connections: they specify their chosen rendezvous point by identity
10725 digest rather than by (potentially ambiguous) nickname. These
10726 changes could speed up hidden service connections dramatically.
10728 o Major bugfixes (other):
10729 - Stop publishing a new server descriptor just because we get a
10730 HUP signal. This led (in a roundabout way) to some servers getting
10731 dropped from the networkstatus lists for a few hours each day.
10732 - When looking for a circuit to cannibalize, consider family as well
10733 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10734 circuit cannibalization).
10735 - When a router wasn't listed in a new networkstatus, we were leaving
10736 the flags for that router alone -- meaning it remained Named,
10737 Running, etc -- even though absence from the networkstatus means
10738 that it shouldn't be considered to exist at all anymore. Now we
10739 clear all the flags for routers that fall out of the networkstatus
10740 consensus. Fixes bug 529.
10743 - Don't try to access (or alter) the state file when running
10744 --list-fingerprint or --verify-config or --hash-password. Resolves
10746 - When generating information telling us how to extend to a given
10747 router, do not try to include the nickname if it is
10748 absent. Resolves bug 467.
10749 - Fix a user-triggerable segfault in expand_filename(). (There isn't
10750 a way to trigger this remotely.)
10751 - When sending a status event to the controller telling it that an
10752 OR address is reachable, set the port correctly. (Previously we
10753 were reporting the dir port.)
10754 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10755 command. Bugfix on 0.1.2.17.
10756 - When loading bandwidth history, do not believe any information in
10757 the future. Fixes bug 434.
10758 - When loading entry guard information, do not believe any information
10760 - When we have our clock set far in the future and generate an
10761 onion key, then re-set our clock to be correct, we should not stop
10762 the onion key from getting rotated.
10763 - On some platforms, accept() can return a broken address. Detect
10764 this more quietly, and deal accordingly. Fixes bug 483.
10765 - It's not actually an error to find a non-pending entry in the DNS
10766 cache when canceling a pending resolve. Don't log unless stuff
10767 is fishy. Resolves bug 463.
10768 - Don't reset trusted dir server list when we set a configuration
10769 option. Patch from Robert Hogan.
10770 - Don't try to create the datadir when running --verify-config or
10771 --hash-password. Resolves bug 540.
10774 Changes in version 0.2.0.9-alpha - 2007-10-24
10775 This ninth development snapshot switches clients to the new v3 directory
10776 system; allows servers to be listed in the network status even when they
10777 have the same nickname as a registered server; and fixes many other
10778 bugs including a big one that was causing some servers to disappear
10779 from the network status lists for a few hours each day.
10781 o Major features (directory system):
10782 - Clients now download v3 consensus networkstatus documents instead
10783 of v2 networkstatus documents. Clients and caches now base their
10784 opinions about routers on these consensus documents. Clients only
10785 download router descriptors listed in the consensus.
10786 - Authorities now list servers who have the same nickname as
10787 a different named server, but list them with a new flag,
10788 "Unnamed". Now we can list servers that happen to pick the same
10789 nickname as a server that registered two years ago and then
10790 disappeared. Partially implements proposal 122.
10791 - If the consensus lists a router as "Unnamed", the name is assigned
10792 to a different router: do not identify the router by that name.
10793 Partially implements proposal 122.
10794 - Authorities can now come to a consensus on which method to use to
10795 compute the consensus. This gives us forward compatibility.
10798 - Stop publishing a new server descriptor just because we HUP or
10799 when we find our DirPort to be reachable but won't actually publish
10800 it. New descriptors without any real changes are dropped by the
10801 authorities, and can screw up our "publish every 18 hours" schedule.
10803 - When a router wasn't listed in a new networkstatus, we were leaving
10804 the flags for that router alone -- meaning it remained Named,
10805 Running, etc -- even though absence from the networkstatus means
10806 that it shouldn't be considered to exist at all anymore. Now we
10807 clear all the flags for routers that fall out of the networkstatus
10808 consensus. Fixes bug 529; bugfix on 0.1.2.x.
10809 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
10810 extrainfo documents and then discard them immediately for not
10811 matching the latest router. Bugfix on 0.2.0.1-alpha.
10813 o Minor features (v3 directory protocol):
10814 - Allow tor-gencert to generate a new certificate without replacing
10816 - Allow certificates to include an address.
10817 - When we change our directory-cache settings, reschedule all voting
10818 and download operations.
10819 - Reattempt certificate downloads immediately on failure, as long as
10820 we haven't failed a threshold number of times yet.
10821 - Delay retrying consensus downloads while we're downloading
10822 certificates to verify the one we just got. Also, count getting a
10823 consensus that we already have (or one that isn't valid) as a failure,
10824 and count failing to get the certificates after 20 minutes as a
10826 - Build circuits and download descriptors even if our consensus is a
10827 little expired. (This feature will go away once authorities are
10830 o Minor features (router descriptor cache):
10831 - If we find a cached-routers file that's been sitting around for more
10832 than 28 days unmodified, then most likely it's a leftover from
10833 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
10835 - When we (as a cache) download a descriptor because it was listed
10836 in a consensus, remember when the consensus was supposed to expire,
10837 and don't expire the descriptor until then.
10839 o Minor features (performance):
10840 - Call routerlist_remove_old_routers() much less often. This should
10841 speed startup, especially on directory caches.
10842 - Don't try to launch new descriptor downloads quite so often when we
10843 already have enough directory information to build circuits.
10844 - Base64 decoding was actually showing up on our profile when parsing
10845 the initial descriptor file; switch to an in-process all-at-once
10846 implementation that's about 3.5x times faster than calling out to
10849 o Minor features (compilation):
10850 - Detect non-ASCII platforms (if any still exist) and refuse to
10851 build there: some of our code assumes that 'A' is 65 and so on.
10853 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
10854 - Make the "next period" votes into "current period" votes immediately
10855 after publishing the consensus; avoid a heisenbug that made them
10856 stick around indefinitely.
10857 - When we discard a vote as a duplicate, do not report this as
10859 - Treat missing v3 keys or certificates as an error when running as a
10860 v3 directory authority.
10861 - When we're configured to be a v3 authority, but we're only listed
10862 as a non-v3 authority in our DirServer line for ourself, correct
10864 - If an authority doesn't have a qualified hostname, just put
10865 its address in the vote. This fixes the problem where we referred to
10866 "moria on moria:9031."
10867 - Distinguish between detached signatures for the wrong period, and
10868 detached signatures for a divergent vote.
10869 - Fix a small memory leak when computing a consensus.
10870 - When there's no concensus, we were forming a vote every 30
10871 minutes, but writing the "valid-after" line in our vote based
10872 on our configured V3AuthVotingInterval: so unless the intervals
10873 matched up, we immediately rejected our own vote because it didn't
10874 start at the voting interval that caused us to construct a vote.
10876 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
10877 - Delete unverified-consensus when the real consensus is set.
10878 - Consider retrying a consensus networkstatus fetch immediately
10879 after one fails: don't wait 60 seconds to notice.
10880 - When fetching a consensus as a cache, wait until a newer consensus
10881 should exist before trying to replace the current one.
10882 - Use a more forgiving schedule for retrying failed consensus
10883 downloads than for other types.
10885 o Minor bugfixes (other directory issues):
10886 - Correct the implementation of "download votes by digest." Bugfix on
10888 - Authorities no longer send back "400 you're unreachable please fix
10889 it" errors to Tor servers that aren't online all the time. We're
10890 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
10892 o Minor bugfixes (controller):
10893 - Don't reset trusted dir server list when we set a configuration
10894 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
10895 - Respond to INT and TERM SIGNAL commands before we execute the
10896 signal, in case the signal shuts us down. We had a patch in
10897 0.1.2.1-alpha that tried to do this by queueing the response on
10898 the connection's buffer before shutting down, but that really
10899 isn't the same thing at all. Bug located by Matt Edman.
10901 o Minor bugfixes (misc):
10902 - Correctly check for bad options to the "PublishServerDescriptor"
10903 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
10904 - Stop leaking memory on failing case of base32_decode, and make
10905 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
10906 - Don't try to download extrainfo documents when we're trying to
10907 fetch enough directory info to build a circuit: having enough
10908 info should get priority. Bugfix on 0.2.0.x.
10909 - Don't complain that "your server has not managed to confirm that its
10910 ports are reachable" if we haven't been able to build any circuits
10911 yet. Bug found by spending four hours without a v3 consensus. Bugfix
10913 - Detect the reason for failing to mmap a descriptor file we just
10914 wrote, and give a more useful log message. Fixes bug 533. Bugfix
10917 o Code simplifications and refactoring:
10918 - Remove support for the old bw_accounting file: we've been storing
10919 bandwidth accounting information in the state file since
10920 0.1.2.5-alpha. This may result in bandwidth accounting errors
10921 if you try to upgrade from 0.1.1.x or earlier, or if you try to
10922 downgrade to 0.1.1.x or earlier.
10923 - New convenience code to locate a file within the DataDirectory.
10924 - Move non-authority functionality out of dirvote.c.
10925 - Refactor the arguments for router_pick_{directory_|trusteddir}server
10926 so that they all take the same named flags.
10929 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
10930 Unix users an easy way to script their Tor process (e.g. by
10931 adjusting bandwidth based on the time of the day).
10934 Changes in version 0.2.0.8-alpha - 2007-10-12
10935 This eighth development snapshot fixes a crash bug that's been bothering
10936 us since February 2007, lets bridge authorities store a list of bridge
10937 descriptors they've seen, gets v3 directory voting closer to working,
10938 starts caching v3 directory consensus documents on directory mirrors,
10939 and fixes a variety of smaller issues including some minor memory leaks.
10941 o Major features (router descriptor cache):
10942 - Store routers in a file called cached-descriptors instead of in
10943 cached-routers. Initialize cached-descriptors from cached-routers
10944 if the old format is around. The new format allows us to store
10945 annotations along with descriptors.
10946 - Use annotations to record the time we received each descriptor, its
10947 source, and its purpose.
10948 - Disable the SETROUTERPURPOSE controller command: it is now
10950 - Controllers should now specify cache=no or cache=yes when using
10951 the +POSTDESCRIPTOR command.
10952 - Bridge authorities now write bridge descriptors to disk, meaning
10953 we can export them to other programs and begin distributing them
10956 o Major features (directory authorities):
10957 - When a v3 authority is missing votes or signatures, it now tries
10959 - Directory authorities track weighted fractional uptime as well as
10960 weighted mean-time-between failures. WFU is suitable for deciding
10961 whether a node is "usually up", while MTBF is suitable for deciding
10962 whether a node is "likely to stay up." We need both, because
10963 "usually up" is a good requirement for guards, while "likely to
10964 stay up" is a good requirement for long-lived connections.
10966 o Major features (v3 directory system):
10967 - Caches now download v3 network status documents as needed,
10968 and download the descriptors listed in them.
10969 - All hosts now attempt to download and keep fresh v3 authority
10970 certificates, and re-attempt after failures.
10971 - More internal-consistency checks for vote parsing.
10973 o Major bugfixes (crashes):
10974 - If a connection is shut down abruptly because of something that
10975 happened inside connection_flushed_some(), do not call
10976 connection_finished_flushing(). Should fix bug 451. Bugfix on
10979 o Major bugfixes (performance):
10980 - Fix really bad O(n^2) performance when parsing a long list of
10981 routers: Instead of searching the entire list for an "extra-info "
10982 string which usually wasn't there, once for every routerinfo
10983 we read, just scan lines forward until we find one we like.
10985 - When we add data to a write buffer in response to the data on that
10986 write buffer getting low because of a flush, do not consider the
10987 newly added data as a candidate for immediate flushing, but rather
10988 make it wait until the next round of writing. Otherwise, we flush
10989 and refill recursively, and a single greedy TLS connection can
10990 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
10992 o Minor features (v3 authority system):
10993 - Add more ways for tools to download the votes that lead to the
10995 - Send a 503 when low on bandwidth and a vote, consensus, or
10996 certificate is requested.
10997 - If-modified-since is now implemented properly for all kinds of
10998 certificate requests.
11000 o Minor bugfixes (network statuses):
11001 - Tweak the implementation of proposal 109 slightly: allow at most
11002 two Tor servers on the same IP address, except if it's the location
11003 of a directory authority, in which case allow five. Bugfix on
11006 o Minor bugfixes (controller):
11007 - When sending a status event to the controller telling it that an
11008 OR address is reachable, set the port correctly. (Previously we
11009 were reporting the dir port.) Bugfix on 0.1.2.x.
11011 o Minor bugfixes (v3 directory system):
11012 - Fix logic to look up a cert by its signing key digest. Bugfix on
11014 - Only change the reply to a vote to "OK" if it's not already
11015 set. This gets rid of annoying "400 OK" log messages, which may
11016 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
11017 - When we get a valid consensus, recompute the voting schedule.
11018 - Base the valid-after time of a vote on the consensus voting
11019 schedule, not on our preferred schedule.
11020 - Make the return values and messages from signature uploads and
11021 downloads more sensible.
11022 - Fix a memory leak when serving votes and consensus documents, and
11023 another when serving certificates.
11025 o Minor bugfixes (performance):
11026 - Use a slightly simpler string hashing algorithm (copying Python's
11027 instead of Java's) and optimize our digest hashing algorithm to take
11028 advantage of 64-bit platforms and to remove some possibly-costly
11030 - Fix a minor memory leak whenever we parse guards from our state
11031 file. Bugfix on 0.2.0.7-alpha.
11032 - Fix a minor memory leak whenever we write out a file. Bugfix on
11034 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
11035 command. Bugfix on 0.2.0.5-alpha.
11037 o Minor bugfixes (portability):
11038 - On some platforms, accept() can return a broken address. Detect
11039 this more quietly, and deal accordingly. Fixes bug 483.
11040 - Stop calling tor_strlower() on uninitialized memory in some cases.
11041 Bugfix in 0.2.0.7-alpha.
11043 o Minor bugfixes (usability):
11044 - Treat some 403 responses from directory servers as INFO rather than
11045 WARN-severity events.
11046 - It's not actually an error to find a non-pending entry in the DNS
11047 cache when canceling a pending resolve. Don't log unless stuff is
11048 fishy. Resolves bug 463.
11050 o Minor bugfixes (anonymity):
11051 - Never report that we've used more bandwidth than we're willing to
11052 relay: it leaks how much non-relay traffic we're using. Resolves
11054 - When looking for a circuit to cannibalize, consider family as well
11055 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
11056 circuit cannibalization).
11058 o Code simplifications and refactoring:
11059 - Make a bunch of functions static. Remove some dead code.
11060 - Pull out about a third of the really big routerlist.c; put it in a
11061 new module, networkstatus.c.
11062 - Merge the extra fields in local_routerstatus_t back into
11063 routerstatus_t: we used to need one routerstatus_t for each
11064 authority's opinion, plus a local_routerstatus_t for the locally
11065 computed consensus opinion. To save space, we put the locally
11066 modified fields into local_routerstatus_t, and only the common
11067 stuff into routerstatus_t. But once v3 directories are in use,
11068 clients and caches will no longer need to hold authority opinions;
11069 thus, the rationale for keeping the types separate is now gone.
11070 - Make the code used to reschedule and reattempt downloads more
11072 - Turn all 'Are we a directory server/mirror?' logic into a call to
11074 - Remove the code to generate the oldest (v1) directory format.
11075 The code has been disabled since 0.2.0.5-alpha.
11078 Changes in version 0.2.0.7-alpha - 2007-09-21
11079 This seventh development snapshot makes bridges work again, makes bridge
11080 authorities work for the first time, fixes two huge performance flaws
11081 in hidden services, and fixes a variety of minor issues.
11083 o New directory authorities:
11084 - Set up moria1 and tor26 as the first v3 directory authorities. See
11085 doc/spec/dir-spec.txt for details on the new directory design.
11087 o Major bugfixes (crashes):
11088 - Fix possible segfaults in functions called from
11089 rend_process_relay_cell(). Bugfix on 0.1.2.x.
11091 o Major bugfixes (bridges):
11092 - Fix a bug that made servers send a "404 Not found" in response to
11093 attempts to fetch their server descriptor. This caused Tor servers
11094 to take many minutes to establish reachability for their DirPort,
11095 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
11096 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
11097 users configure that and specify a bridge with an identity
11098 fingerprint, now they will lookup the bridge descriptor at the
11099 default bridge authority via a one-hop tunnel, but once circuits
11100 are established they will switch to a three-hop tunnel for later
11101 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
11103 o Major bugfixes (hidden services):
11104 - Hidden services were choosing introduction points uniquely by
11105 hexdigest, but when constructing the hidden service descriptor
11106 they merely wrote the (potentially ambiguous) nickname.
11107 - Clients now use the v2 intro format for hidden service
11108 connections: they specify their chosen rendezvous point by identity
11109 digest rather than by (potentially ambiguous) nickname. Both
11110 are bugfixes on 0.1.2.x, and they could speed up hidden service
11111 connections dramatically. Thanks to Karsten Loesing.
11113 o Minor features (security):
11114 - As a client, do not believe any server that tells us that an
11115 address maps to an internal address space.
11116 - Make it possible to enable HashedControlPassword and
11117 CookieAuthentication at the same time.
11119 o Minor features (guard nodes):
11120 - Tag every guard node in our state file with the version that
11121 we believe added it, or with our own version if we add it. This way,
11122 if a user temporarily runs an old version of Tor and then switches
11123 back to a new one, she doesn't automatically lose her guards.
11125 o Minor features (speed):
11126 - When implementing AES counter mode, update only the portions of the
11127 counter buffer that need to change, and don't keep separate
11128 network-order and host-order counters when they are the same (i.e.,
11129 on big-endian hosts.)
11131 o Minor features (controller):
11132 - Accept LF instead of CRLF on controller, since some software has a
11133 hard time generating real Internet newlines.
11134 - Add GETINFO values for the server status events
11135 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
11138 o Removed features:
11139 - Routers no longer include bandwidth-history lines in their
11140 descriptors; this information is already available in extra-info
11141 documents, and including it in router descriptors took up 60%
11142 (!) of compressed router descriptor downloads. Completes
11143 implementation of proposal 104.
11144 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
11145 and TorControl.py, as they use the old v0 controller protocol,
11146 and are obsoleted by TorFlow anyway.
11147 - Drop support for v1 rendezvous descriptors, since we never used
11148 them anyway, and the code has probably rotted by now. Based on
11149 patch from Karsten Loesing.
11150 - On OSX, stop warning the user that kqueue support in libevent is
11151 "experimental", since it seems to have worked fine for ages.
11154 - When generating information telling us how to extend to a given
11155 router, do not try to include the nickname if it is absent. Fixes
11156 bug 467. Bugfix on 0.2.0.3-alpha.
11157 - Fix a user-triggerable (but not remotely-triggerable) segfault
11158 in expand_filename(). Bugfix on 0.1.2.x.
11159 - Fix a memory leak when freeing incomplete requests from DNSPort.
11160 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
11161 - Don't try to access (or alter) the state file when running
11162 --list-fingerprint or --verify-config or --hash-password. (Resolves
11163 bug 499.) Bugfix on 0.1.2.x.
11164 - Servers used to decline to publish their DirPort if their
11165 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
11166 were below a threshold. Now they only look at BandwidthRate and
11167 RelayBandwidthRate. Bugfix on 0.1.2.x.
11168 - Remove an optimization in the AES counter-mode code that assumed
11169 that the counter never exceeded 2^68. When the counter can be set
11170 arbitrarily as an IV (as it is by Karsten's new hidden services
11171 code), this assumption no longer holds. Bugfix on 0.1.2.x.
11172 - Resume listing "AUTHORITY" flag for authorities in network status.
11173 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
11175 o Code simplifications and refactoring:
11176 - Revamp file-writing logic so we don't need to have the entire
11177 contents of a file in memory at once before we write to disk. Tor,
11179 - Turn "descriptor store" into a full-fledged type.
11180 - Move all NT services code into a separate source file.
11181 - Unify all code that computes medians, percentile elements, etc.
11182 - Get rid of a needless malloc when parsing address policies.
11185 Changes in version 0.1.2.17 - 2007-08-30
11186 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
11187 X bundles. Vidalia 0.0.14 makes authentication required for the
11188 ControlPort in the default configuration, which addresses important
11189 security risks. Everybody who uses Vidalia (or another controller)
11192 In addition, this Tor update fixes major load balancing problems with
11193 path selection, which should speed things up a lot once many people
11196 o Major bugfixes (security):
11197 - We removed support for the old (v0) control protocol. It has been
11198 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
11199 become more of a headache than it's worth.
11201 o Major bugfixes (load balancing):
11202 - When choosing nodes for non-guard positions, weight guards
11203 proportionally less, since they already have enough load. Patch
11205 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
11206 will allow fast Tor servers to get more attention.
11207 - When we're upgrading from an old Tor version, forget our current
11208 guards and pick new ones according to the new weightings. These
11209 three load balancing patches could raise effective network capacity
11210 by a factor of four. Thanks to Mike Perry for measurements.
11212 o Major bugfixes (stream expiration):
11213 - Expire not-yet-successful application streams in all cases if
11214 they've been around longer than SocksTimeout. Right now there are
11215 some cases where the stream will live forever, demanding a new
11216 circuit every 15 seconds. Fixes bug 454; reported by lodger.
11218 o Minor features (controller):
11219 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
11220 is valid before any authentication has been received. It tells
11221 a controller what kind of authentication is expected, and what
11222 protocol is spoken. Implements proposal 119.
11224 o Minor bugfixes (performance):
11225 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
11226 greatly speeding up loading cached-routers from disk on startup.
11227 - Disable sentinel-based debugging for buffer code: we squashed all
11228 the bugs that this was supposed to detect a long time ago, and now
11229 its only effect is to change our buffer sizes from nice powers of
11230 two (which platform mallocs tend to like) to values slightly over
11231 powers of two (which make some platform mallocs sad).
11233 o Minor bugfixes (misc):
11234 - If exit bandwidth ever exceeds one third of total bandwidth, then
11235 use the correct formula to weight exit nodes when choosing paths.
11236 Based on patch from Mike Perry.
11237 - Choose perfectly fairly among routers when choosing by bandwidth and
11238 weighting by fraction of bandwidth provided by exits. Previously, we
11239 would choose with only approximate fairness, and correct ourselves
11240 if we ran off the end of the list.
11241 - If we require CookieAuthentication but we fail to write the
11242 cookie file, we would warn but not exit, and end up in a state
11243 where no controller could authenticate. Now we exit.
11244 - If we require CookieAuthentication, stop generating a new cookie
11245 every time we change any piece of our config.
11246 - Refuse to start with certain directory authority keys, and
11247 encourage people using them to stop.
11248 - Terminate multi-line control events properly. Original patch
11250 - Fix a minor memory leak when we fail to find enough suitable
11251 servers to choose a circuit.
11252 - Stop leaking part of the descriptor when we run into a particularly
11253 unparseable piece of it.
11256 Changes in version 0.2.0.6-alpha - 2007-08-26
11257 This sixth development snapshot features a new Vidalia version in the
11258 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
11259 the ControlPort in the default configuration, which addresses important
11262 In addition, this snapshot fixes major load balancing problems
11263 with path selection, which should speed things up a lot once many
11264 people have upgraded. The directory authorities also use a new
11265 mean-time-between-failure approach to tracking which servers are stable,
11266 rather than just looking at the most recent uptime.
11268 o New directory authorities:
11269 - Set up Tonga as the default bridge directory authority.
11272 - Directory authorities now track servers by weighted
11273 mean-times-between-failures. When we have 4 or more days of data,
11274 use measured MTBF rather than declared uptime to decide whether
11275 to call a router Stable. Implements proposal 108.
11277 o Major bugfixes (load balancing):
11278 - When choosing nodes for non-guard positions, weight guards
11279 proportionally less, since they already have enough load. Patch
11281 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
11282 will allow fast Tor servers to get more attention.
11283 - When we're upgrading from an old Tor version, forget our current
11284 guards and pick new ones according to the new weightings. These
11285 three load balancing patches could raise effective network capacity
11286 by a factor of four. Thanks to Mike Perry for measurements.
11288 o Major bugfixes (descriptor parsing):
11289 - Handle unexpected whitespace better in malformed descriptors. Bug
11290 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
11293 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
11294 GETINFO for Torstat to use until it can switch to using extrainfos.
11295 - Optionally (if built with -DEXPORTMALLINFO) export the output
11296 of mallinfo via http, as tor/mallinfo.txt. Only accessible
11300 - Do not intermix bridge routers with controller-added
11301 routers. (Bugfix on 0.2.0.x)
11302 - Do not fail with an assert when accept() returns an unexpected
11303 address family. Addresses but does not wholly fix bug 483. (Bugfix
11305 - Let directory authorities startup even when they can't generate
11306 a descriptor immediately, e.g. because they don't know their
11308 - Stop putting the authentication cookie in a file called "0"
11309 in your working directory if you don't specify anything for the
11310 new CookieAuthFile option. Reported by Matt Edman.
11311 - Make it possible to read the PROTOCOLINFO response in a way that
11312 conforms to our control-spec. Reported by Matt Edman.
11313 - Fix a minor memory leak when we fail to find enough suitable
11314 servers to choose a circuit. Bugfix on 0.1.2.x.
11315 - Stop leaking part of the descriptor when we run into a particularly
11316 unparseable piece of it. Bugfix on 0.1.2.x.
11317 - Unmap the extrainfo cache file on exit.
11320 Changes in version 0.2.0.5-alpha - 2007-08-19
11321 This fifth development snapshot fixes compilation on Windows again;
11322 fixes an obnoxious client-side bug that slowed things down and put
11323 extra load on the network; gets us closer to using the v3 directory
11324 voting scheme; makes it easier for Tor controllers to use cookie-based
11325 authentication; and fixes a variety of other bugs.
11327 o Removed features:
11328 - Version 1 directories are no longer generated in full. Instead,
11329 authorities generate and serve "stub" v1 directories that list
11330 no servers. This will stop Tor versions 0.1.0.x and earlier from
11331 working, but (for security reasons) nobody should be running those
11334 o Major bugfixes (compilation, 0.2.0.x):
11335 - Try to fix Win32 compilation again: improve checking for IPv6 types.
11336 - Try to fix MSVC compilation: build correctly on platforms that do
11337 not define s6_addr16 or s6_addr32.
11338 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
11341 o Major bugfixes (stream expiration):
11342 - Expire not-yet-successful application streams in all cases if
11343 they've been around longer than SocksTimeout. Right now there are
11344 some cases where the stream will live forever, demanding a new
11345 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
11346 reported by lodger.
11348 o Minor features (directory servers):
11349 - When somebody requests a list of statuses or servers, and we have
11350 none of those, return a 404 rather than an empty 200.
11352 o Minor features (directory voting):
11353 - Store v3 consensus status consensuses on disk, and reload them
11356 o Minor features (security):
11357 - Warn about unsafe ControlPort configurations.
11358 - Refuse to start with certain directory authority keys, and
11359 encourage people using them to stop.
11361 o Minor features (controller):
11362 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
11363 is valid before any authentication has been received. It tells
11364 a controller what kind of authentication is expected, and what
11365 protocol is spoken. Implements proposal 119.
11366 - New config option CookieAuthFile to choose a new location for the
11367 cookie authentication file, and config option
11368 CookieAuthFileGroupReadable to make it group-readable.
11370 o Minor features (unit testing):
11371 - Add command-line arguments to unit-test executable so that we can
11372 invoke any chosen test from the command line rather than having
11373 to run the whole test suite at once; and so that we can turn on
11374 logging for the unit tests.
11376 o Minor bugfixes (on 0.1.2.x):
11377 - If we require CookieAuthentication but we fail to write the
11378 cookie file, we would warn but not exit, and end up in a state
11379 where no controller could authenticate. Now we exit.
11380 - If we require CookieAuthentication, stop generating a new cookie
11381 every time we change any piece of our config.
11382 - When loading bandwidth history, do not believe any information in
11383 the future. Fixes bug 434.
11384 - When loading entry guard information, do not believe any information
11386 - When we have our clock set far in the future and generate an
11387 onion key, then re-set our clock to be correct, we should not stop
11388 the onion key from getting rotated.
11389 - Clean up torrc sample config file.
11390 - Do not automatically run configure from autogen.sh. This
11391 non-standard behavior tended to annoy people who have built other
11394 o Minor bugfixes (on 0.2.0.x):
11395 - Fix a bug with AutomapHostsOnResolve that would always cause
11396 the second request to fail. Bug reported by Kate. Bugfix on
11398 - Fix a bug in ADDRMAP controller replies that would sometimes
11399 try to print a NULL. Patch from tup.
11400 - Read v3 directory authority keys from the right location.
11401 - Numerous bugfixes to directory voting code.
11404 Changes in version 0.1.2.16 - 2007-08-01
11405 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
11406 remote attacker in certain situations to rewrite the user's torrc
11407 configuration file. This can completely compromise anonymity of users
11408 in most configurations, including those running the Vidalia bundles,
11409 TorK, etc. Or worse.
11411 o Major security fixes:
11412 - Close immediately after missing authentication on control port;
11413 do not allow multiple authentication attempts.
11416 Changes in version 0.2.0.4-alpha - 2007-08-01
11417 This fourth development snapshot fixes a critical security vulnerability
11418 for most users, specifically those running Vidalia, TorK, etc. Everybody
11419 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
11421 o Major security fixes:
11422 - Close immediately after missing authentication on control port;
11423 do not allow multiple authentication attempts.
11425 o Major bugfixes (compilation):
11426 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
11429 o Minor features (performance):
11430 - Be even more aggressive about releasing RAM from small
11431 empty buffers. Thanks to our free-list code, this shouldn't be too
11432 performance-intensive.
11433 - Disable sentinel-based debugging for buffer code: we squashed all
11434 the bugs that this was supposed to detect a long time ago, and
11435 now its only effect is to change our buffer sizes from nice
11436 powers of two (which platform mallocs tend to like) to values
11437 slightly over powers of two (which make some platform mallocs sad).
11438 - Log malloc statistics from mallinfo() on platforms where it
11442 Changes in version 0.2.0.3-alpha - 2007-07-29
11443 This third development snapshot introduces new experimental
11444 blocking-resistance features and a preliminary version of the v3
11445 directory voting design, and includes many other smaller features
11449 - The first pieces of our "bridge" design for blocking-resistance
11450 are implemented. People can run bridge directory authorities;
11451 people can run bridges; and people can configure their Tor clients
11452 with a set of bridges to use as the first hop into the Tor network.
11453 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
11455 - Create listener connections before we setuid to the configured
11456 User and Group. Now non-Windows users can choose port values
11457 under 1024, start Tor as root, and have Tor bind those ports
11458 before it changes to another UID. (Windows users could already
11460 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
11461 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
11462 on "vserver" accounts. (Patch from coderman.)
11463 - Be even more aggressive about separating local traffic from relayed
11464 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
11466 o Major features (experimental):
11467 - First cut of code for "v3 dir voting": directory authorities will
11468 vote on a common network status document rather than each publishing
11469 their own opinion. This code needs more testing and more corner-case
11470 handling before it's ready for use.
11473 - Directory authorities now call routers Fast if their bandwidth is
11474 at least 100KB/s, and consider their bandwidth adequate to be a
11475 Guard if it is at least 250KB/s, no matter the medians. This fix
11476 complements proposal 107. [Bugfix on 0.1.2.x]
11477 - Directory authorities now never mark more than 3 servers per IP as
11478 Valid and Running. (Implements proposal 109, by Kevin Bauer and
11480 - Minor change to organizationName and commonName generation
11481 procedures in TLS certificates during Tor handshakes, to invalidate
11482 some earlier censorware approaches. This is not a long-term
11483 solution, but applying it will give us a bit of time to look into
11484 the epidemiology of countermeasures as they spread.
11486 o Major bugfixes (directory):
11487 - Rewrite directory tokenization code to never run off the end of
11488 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
11490 o Minor features (controller):
11491 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
11492 match requests to applications. (Patch from Robert Hogan.)
11493 - Report address and port correctly on connections to DNSPort. (Patch
11494 from Robert Hogan.)
11495 - Add a RESOLVE command to launch hostname lookups. (Original patch
11496 from Robert Hogan.)
11497 - Add GETINFO status/enough-dir-info to let controllers tell whether
11498 Tor has downloaded sufficient directory information. (Patch
11500 - You can now use the ControlSocket option to tell Tor to listen for
11501 controller connections on Unix domain sockets on systems that
11502 support them. (Patch from Peter Palfrader.)
11503 - STREAM NEW events are generated for DNSPort requests and for
11504 tunneled directory connections. (Patch from Robert Hogan.)
11505 - New "GETINFO address-mappings/*" command to get address mappings
11506 with expiry information. "addr-mappings/*" is now deprecated.
11509 o Minor features (misc):
11510 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
11512 - The tor-gencert tool for v3 directory authorities now creates all
11513 files as readable to the file creator only, and write-protects
11514 the authority identity key.
11515 - When dumping memory usage, list bytes used in buffer memory
11517 - When running with dmalloc, dump more stats on hup and on exit.
11518 - Directory authorities now fail quickly and (relatively) harmlessly
11519 if they generate a network status document that is somehow
11522 o Traffic load balancing improvements:
11523 - If exit bandwidth ever exceeds one third of total bandwidth, then
11524 use the correct formula to weight exit nodes when choosing paths.
11525 (Based on patch from Mike Perry.)
11526 - Choose perfectly fairly among routers when choosing by bandwidth and
11527 weighting by fraction of bandwidth provided by exits. Previously, we
11528 would choose with only approximate fairness, and correct ourselves
11529 if we ran off the end of the list. [Bugfix on 0.1.2.x]
11531 o Performance improvements:
11532 - Be more aggressive with freeing buffer RAM or putting it on the
11534 - Use Critical Sections rather than Mutexes for synchronizing threads
11535 on win32; Mutexes are heavier-weight, and designed for synchronizing
11538 o Deprecated and removed features:
11539 - RedirectExits is now deprecated.
11540 - Stop allowing address masks that do not correspond to bit prefixes.
11541 We have warned about these for a really long time; now it's time
11542 to reject them. (Patch from croup.)
11544 o Minor bugfixes (directory):
11545 - Fix another crash bug related to extra-info caching. (Bug found by
11546 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
11547 - Directories no longer return a "304 not modified" when they don't
11548 have the networkstatus the client asked for. Also fix a memory
11549 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
11550 - We had accidentally labelled 0.1.2.x directory servers as not
11551 suitable for begin_dir requests, and had labelled no directory
11552 servers as suitable for uploading extra-info documents. [Bugfix
11555 o Minor bugfixes (dns):
11556 - Fix a crash when DNSPort is set more than once. (Patch from Robert
11557 Hogan.) [Bugfix on 0.2.0.2-alpha]
11558 - Add DNSPort connections to the global connection list, so that we
11559 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
11561 - Fix a dangling reference that could lead to a crash when DNSPort is
11562 changed or closed (Patch from Robert Hogan.) [Bugfix on
11565 o Minor bugfixes (controller):
11566 - Provide DNS expiry times in GMT, not in local time. For backward
11567 compatibility, ADDRMAP events only provide GMT expiry in an extended
11568 field. "GETINFO address-mappings" always does the right thing.
11569 - Use CRLF line endings properly in NS events.
11570 - Terminate multi-line control events properly. (Original patch
11571 from tup.) [Bugfix on 0.1.2.x-alpha]
11572 - Do not include spaces in SOURCE_ADDR fields in STREAM
11573 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
11576 Changes in version 0.1.2.15 - 2007-07-17
11577 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
11578 problems, fixes compilation on BSD, and fixes a variety of other
11579 bugs. Everybody should upgrade.
11581 o Major bugfixes (compilation):
11582 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
11584 o Major bugfixes (crashes):
11585 - Try even harder not to dereference the first character after
11586 an mmap(). Reported by lodger.
11587 - Fix a crash bug in directory authorities when we re-number the
11588 routerlist while inserting a new router.
11589 - When the cached-routers file is an even multiple of the page size,
11590 don't run off the end and crash. (Fixes bug 455; based on idea
11592 - Fix eventdns.c behavior on Solaris: It is critical to include
11593 orconfig.h _before_ sys/types.h, so that we can get the expected
11594 definition of _FILE_OFFSET_BITS.
11596 o Major bugfixes (security):
11597 - Fix a possible buffer overrun when using BSD natd support. Bug
11599 - When sending destroy cells from a circuit's origin, don't include
11600 the reason for tearing down the circuit. The spec says we didn't,
11601 and now we actually don't. Reported by lodger.
11602 - Keep streamids from different exits on a circuit separate. This
11603 bug may have allowed other routers on a given circuit to inject
11604 cells into streams. Reported by lodger; fixes bug 446.
11605 - If there's a never-before-connected-to guard node in our list,
11606 never choose any guards past it. This way we don't expand our
11607 guard list unless we need to.
11609 o Minor bugfixes (guard nodes):
11610 - Weight guard selection by bandwidth, so that low-bandwidth nodes
11611 don't get overused as guards.
11613 o Minor bugfixes (directory):
11614 - Correctly count the number of authorities that recommend each
11615 version. Previously, we were under-counting by 1.
11616 - Fix a potential crash bug when we load many server descriptors at
11617 once and some of them make others of them obsolete. Fixes bug 458.
11619 o Minor bugfixes (hidden services):
11620 - Stop tearing down the whole circuit when the user asks for a
11621 connection to a port that the hidden service didn't configure.
11624 o Minor bugfixes (misc):
11625 - On Windows, we were preventing other processes from reading
11626 cached-routers while Tor was running. Reported by janbar.
11627 - Fix a possible (but very unlikely) bug in picking routers by
11628 bandwidth. Add a log message to confirm that it is in fact
11629 unlikely. Patch from lodger.
11630 - Backport a couple of memory leak fixes.
11631 - Backport miscellaneous cosmetic bugfixes.
11634 Changes in version 0.2.0.2-alpha - 2007-06-02
11635 o Major bugfixes on 0.2.0.1-alpha:
11636 - Fix an assertion failure related to servers without extra-info digests.
11637 Resolves bugs 441 and 442.
11639 o Minor features (directory):
11640 - Support "If-Modified-Since" when answering HTTP requests for
11641 directories, running-routers documents, and network-status documents.
11642 (There's no need to support it for router descriptors, since those
11643 are downloaded by descriptor digest.)
11645 o Minor build issues:
11646 - Clear up some MIPSPro compiler warnings.
11647 - When building from a tarball on a machine that happens to have SVK
11648 installed, report the micro-revision as whatever version existed
11649 in the tarball, not as "x".
11652 Changes in version 0.2.0.1-alpha - 2007-06-01
11653 This early development snapshot provides new features for people running
11654 Tor as both a client and a server (check out the new RelayBandwidth
11655 config options); lets Tor run as a DNS proxy; and generally moves us
11656 forward on a lot of fronts.
11658 o Major features, server usability:
11659 - New config options RelayBandwidthRate and RelayBandwidthBurst:
11660 a separate set of token buckets for relayed traffic. Right now
11661 relayed traffic is defined as answers to directory requests, and
11662 OR connections that don't have any local circuits on them.
11664 o Major features, client usability:
11665 - A client-side DNS proxy feature to replace the need for
11666 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
11667 for DNS requests on port 9999, use the Tor network to resolve them
11668 anonymously, and send the reply back like a regular DNS server.
11669 The code still only implements a subset of DNS.
11670 - Make PreferTunneledDirConns and TunnelDirConns work even when
11671 we have no cached directory info. This means Tor clients can now
11672 do all of their connections protected by TLS.
11674 o Major features, performance and efficiency:
11675 - Directory authorities accept and serve "extra info" documents for
11676 routers. These documents contain fields from router descriptors
11677 that aren't usually needed, and that use a lot of excess
11678 bandwidth. Once these fields are removed from router descriptors,
11679 the bandwidth savings should be about 60%. [Partially implements
11681 - Servers upload extra-info documents to any authority that accepts
11682 them. Authorities (and caches that have been configured to download
11683 extra-info documents) download them as needed. [Partially implements
11685 - Change the way that Tor buffers data that it is waiting to write.
11686 Instead of queueing data cells in an enormous ring buffer for each
11687 client->OR or OR->OR connection, we now queue cells on a separate
11688 queue for each circuit. This lets us use less slack memory, and
11689 will eventually let us be smarter about prioritizing different kinds
11691 - Use memory pools to allocate cells with better speed and memory
11692 efficiency, especially on platforms where malloc() is inefficient.
11693 - Stop reading on edge connections when their corresponding circuit
11694 buffers are full; start again as the circuits empty out.
11696 o Major features, other:
11697 - Add an HSAuthorityRecordStats option that hidden service authorities
11698 can use to track statistics of overall hidden service usage without
11699 logging information that would be very useful to an attacker.
11700 - Start work implementing multi-level keys for directory authorities:
11701 Add a standalone tool to generate key certificates. (Proposal 103.)
11704 - Directory authorities now call routers Stable if they have an
11705 uptime of at least 30 days, even if that's not the median uptime
11706 in the network. Implements proposal 107, suggested by Kevin Bauer
11709 o Minor fixes (resource management):
11710 - Count the number of open sockets separately from the number
11711 of active connection_t objects. This will let us avoid underusing
11712 our allocated connection limit.
11713 - We no longer use socket pairs to link an edge connection to an
11714 anonymous directory connection or a DirPort test connection.
11715 Instead, we track the link internally and transfer the data
11716 in-process. This saves two sockets per "linked" connection (at the
11717 client and at the server), and avoids the nasty Windows socketpair()
11719 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
11720 for every single inactive connection_t. Free items from the
11721 4k/16k-buffer free lists when they haven't been used for a while.
11723 o Minor features (build):
11724 - Make autoconf search for libevent, openssl, and zlib consistently.
11725 - Update deprecated macros in configure.in.
11726 - When warning about missing headers, tell the user to let us
11727 know if the compile succeeds anyway, so we can downgrade the
11729 - Include the current subversion revision as part of the version
11730 string: either fetch it directly if we're in an SVN checkout, do
11731 some magic to guess it if we're in an SVK checkout, or use
11732 the last-detected version if we're building from a .tar.gz.
11733 Use this version consistently in log messages.
11735 o Minor features (logging):
11736 - Always prepend "Bug: " to any log message about a bug.
11737 - Put a platform string (e.g. "Linux i686") in the startup log
11738 message, so when people paste just their logs, we know if it's
11739 OpenBSD or Windows or what.
11740 - When logging memory usage, break down memory used in buffers by
11743 o Minor features (directory system):
11744 - New config option V2AuthoritativeDirectory that all directory
11745 authorities should set. This will let future authorities choose
11746 not to serve V2 directory information.
11747 - Directory authorities allow multiple router descriptors and/or extra
11748 info documents to be uploaded in a single go. This will make
11749 implementing proposal 104 simpler.
11751 o Minor features (controller):
11752 - Add a new config option __DisablePredictedCircuits designed for
11753 use by the controller, when we don't want Tor to build any circuits
11755 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
11756 so we can exit from the middle of the circuit.
11757 - Implement "getinfo status/circuit-established".
11758 - Implement "getinfo status/version/..." so a controller can tell
11759 whether the current version is recommended, and whether any versions
11760 are good, and how many authorities agree. (Patch from shibz.)
11762 o Minor features (hidden services):
11763 - Allow multiple HiddenServicePort directives with the same virtual
11764 port; when they occur, the user is sent round-robin to one
11765 of the target ports chosen at random. Partially fixes bug 393 by
11766 adding limited ad-hoc round-robining.
11768 o Minor features (other):
11770 - Add a new AutomapHostsOnResolve option: when it is enabled, any
11771 resolve request for hosts matching a given pattern causes Tor to
11772 generate an internal virtual address mapping for that host. This
11773 allows DNSPort to work sensibly with hidden service users. By
11774 default, .exit and .onion addresses are remapped; the list of
11775 patterns can be reconfigured with AutomapHostsSuffixes.
11776 - Add an "-F" option to tor-resolve to force a resolve for a .onion
11777 address. Thanks to the AutomapHostsOnResolve option, this is no
11778 longer a completely silly thing to do.
11779 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
11780 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
11781 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
11782 minus 1 byte: the actual maximum declared bandwidth.
11784 o Removed features:
11785 - Removed support for the old binary "version 0" controller protocol.
11786 This has been deprecated since 0.1.1, and warnings have been issued
11787 since 0.1.2. When we encounter a v0 control message, we now send
11788 back an error and close the connection.
11789 - Remove the old "dns worker" server DNS code: it hasn't been default
11790 since 0.1.2.2-alpha, and all the servers seem to be using the new
11793 o Minor bugfixes (portability):
11794 - Even though Windows is equally happy with / and \ as path separators,
11795 try to use \ consistently on Windows and / consistently on Unix: it
11796 makes the log messages nicer.
11797 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
11798 - Read resolv.conf files correctly on platforms where read() returns
11799 partial results on small file reads.
11801 o Minor bugfixes (directory):
11802 - Correctly enforce that elements of directory objects do not appear
11803 more often than they are allowed to appear.
11804 - When we are reporting the DirServer line we just parsed, we were
11805 logging the second stanza of the key fingerprint, not the first.
11807 o Minor bugfixes (logging):
11808 - When we hit an EOF on a log (probably because we're shutting down),
11809 don't try to remove the log from the list: just mark it as
11810 unusable. (Bulletproofs against bug 222.)
11812 o Minor bugfixes (other):
11813 - In the exitlist script, only consider the most recently published
11814 server descriptor for each server. Also, when the user requests
11815 a list of servers that _reject_ connections to a given address,
11816 explicitly exclude the IPs that also have servers that accept
11817 connections to that address. (Resolves bug 405.)
11818 - Stop allowing hibernating servers to be "stable" or "fast".
11819 - On Windows, we were preventing other processes from reading
11820 cached-routers while Tor was running. (Reported by janbar)
11821 - Make the NodeFamilies config option work. (Reported by
11822 lodger -- it has never actually worked, even though we added it
11824 - Check return values from pthread_mutex functions.
11825 - Don't save non-general-purpose router descriptors to the disk cache,
11826 because we have no way of remembering what their purpose was when
11828 - Add even more asserts to hunt down bug 417.
11829 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
11830 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
11831 Add a log message to confirm that it is in fact unlikely.
11833 o Minor bugfixes (controller):
11834 - Make 'getinfo fingerprint' return a 551 error if we're not a
11835 server, so we match what the control spec claims we do. Reported
11837 - Fix a typo in an error message when extendcircuit fails that
11838 caused us to not follow the \r\n-based delimiter protocol. Reported
11841 o Code simplifications and refactoring:
11842 - Stop passing around circuit_t and crypt_path_t pointers that are
11843 implicit in other procedure arguments.
11844 - Drop the old code to choke directory connections when the
11845 corresponding OR connections got full: thanks to the cell queue
11846 feature, OR conns don't get full any more.
11847 - Make dns_resolve() handle attaching connections to circuits
11848 properly, so the caller doesn't have to.
11849 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
11850 - Keep the connection array as a dynamic smartlist_t, rather than as
11851 a fixed-sized array. This is important, as the number of connections
11852 is becoming increasingly decoupled from the number of sockets.
11855 Changes in version 0.1.2.14 - 2007-05-25
11856 Tor 0.1.2.14 changes the addresses of two directory authorities (this
11857 change especially affects those who serve or use hidden services),
11858 and fixes several other crash- and security-related bugs.
11860 o Directory authority changes:
11861 - Two directory authorities (moria1 and moria2) just moved to new
11862 IP addresses. This change will particularly affect those who serve
11863 or use hidden services.
11865 o Major bugfixes (crashes):
11866 - If a directory server runs out of space in the connection table
11867 as it's processing a begin_dir request, it will free the exit stream
11868 but leave it attached to the circuit, leading to unpredictable
11869 behavior. (Reported by seeess, fixes bug 425.)
11870 - Fix a bug in dirserv_remove_invalid() that would cause authorities
11871 to corrupt memory under some really unlikely scenarios.
11872 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
11873 - Avoid segfaults when reading from mmaped descriptor file. (Reported
11876 o Major bugfixes (security):
11877 - When choosing an entry guard for a circuit, avoid using guards
11878 that are in the same family as the chosen exit -- not just guards
11879 that are exactly the chosen exit. (Reported by lodger.)
11881 o Major bugfixes (resource management):
11882 - If a directory authority is down, skip it when deciding where to get
11883 networkstatus objects or descriptors. Otherwise we keep asking
11884 every 10 seconds forever. Fixes bug 384.
11885 - Count it as a failure if we fetch a valid network-status but we
11886 don't want to keep it. Otherwise we'll keep fetching it and keep
11887 not wanting to keep it. Fixes part of bug 422.
11888 - If all of our dirservers have given us bad or no networkstatuses
11889 lately, then stop hammering them once per minute even when we
11890 think they're failed. Fixes another part of bug 422.
11893 - Actually set the purpose correctly for descriptors inserted with
11894 purpose=controller.
11895 - When we have k non-v2 authorities in our DirServer config,
11896 we ignored the last k authorities in the list when updating our
11898 - Correctly back-off from requesting router descriptors that we are
11899 having a hard time downloading.
11900 - Read resolv.conf files correctly on platforms where read() returns
11901 partial results on small file reads.
11902 - Don't rebuild the entire router store every time we get 32K of
11903 routers: rebuild it when the journal gets very large, or when
11904 the gaps in the store get very large.
11907 - When routers publish SVN revisions in their router descriptors,
11908 authorities now include those versions correctly in networkstatus
11910 - Warn when using a version of libevent before 1.3b to run a server on
11911 OSX or BSD: these versions interact badly with userspace threads.
11914 Changes in version 0.1.2.13 - 2007-04-24
11915 This release features some major anonymity fixes, such as safer path
11916 selection; better client performance; faster bootstrapping, better
11917 address detection, and better DNS support for servers; write limiting as
11918 well as read limiting to make servers easier to run; and a huge pile of
11919 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
11921 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
11922 of the Freenode IRC network, remembering his patience and vision for
11923 free speech on the Internet.
11926 - Fix a memory leak when we ask for "all" networkstatuses and we
11927 get one we don't recognize.
11928 - Add more asserts to hunt down bug 417.
11929 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
11932 Changes in version 0.1.2.12-rc - 2007-03-16
11934 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
11935 directory information requested inside Tor connections (i.e. via
11936 begin_dir cells). It only triggered when the same connection was
11937 serving other data at the same time. Reported by seeess.
11940 - When creating a circuit via the controller, send a 'launched'
11941 event when we're done, so we follow the spec better.
11944 Changes in version 0.1.2.11-rc - 2007-03-15
11945 o Minor bugfixes (controller), reported by daejees:
11946 - Correct the control spec to match how the code actually responds
11947 to 'getinfo addr-mappings/*'.
11948 - The control spec described a GUARDS event, but the code
11949 implemented a GUARD event. Standardize on GUARD, but let people
11950 ask for GUARDS too.
11953 Changes in version 0.1.2.10-rc - 2007-03-07
11954 o Major bugfixes (Windows):
11955 - Do not load the NT services library functions (which may not exist)
11956 just to detect if we're a service trying to shut down. Now we run
11957 on Win98 and friends again.
11959 o Minor bugfixes (other):
11960 - Clarify a couple of log messages.
11961 - Fix a misleading socks5 error number.
11964 Changes in version 0.1.2.9-rc - 2007-03-02
11965 o Major bugfixes (Windows):
11966 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
11967 of the usual GCC "%llu". This prevents a bug when saving 64-bit
11968 int configuration values: the high-order 32 bits would get
11969 truncated. In particular, we were being bitten by the default
11970 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
11971 and maybe also bug 397.)
11973 o Minor bugfixes (performance):
11974 - Use OpenSSL's AES implementation on platforms where it's faster.
11975 This could save us as much as 10% CPU usage.
11977 o Minor bugfixes (server):
11978 - Do not rotate onion key immediately after setting it for the first
11981 o Minor bugfixes (directory authorities):
11982 - Stop calling servers that have been hibernating for a long time
11983 "stable". Also, stop letting hibernating or obsolete servers affect
11984 uptime and bandwidth cutoffs.
11985 - Stop listing hibernating servers in the v1 directory.
11987 o Minor bugfixes (hidden services):
11988 - Upload hidden service descriptors slightly less often, to reduce
11989 load on authorities.
11991 o Minor bugfixes (other):
11992 - Fix an assert that could trigger if a controller quickly set then
11993 cleared EntryNodes. Bug found by Udo van den Heuvel.
11994 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
11996 - Fix a potential race condition in the rpm installer. Found by
11998 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
11999 of 2 as indicating that the server is completely bad; it sometimes
12000 means that the server is just bad for the request in question. (may fix
12001 the last of bug 326.)
12002 - Disable encrypted directory connections when we don't have a server
12003 descriptor for the destination. We'll get this working again in
12007 Changes in version 0.1.2.8-beta - 2007-02-26
12008 o Major bugfixes (crashes):
12009 - Stop crashing when the controller asks us to resetconf more than
12010 one config option at once. (Vidalia 0.0.11 does this.)
12011 - Fix a crash that happened on Win98 when we're given command-line
12012 arguments: don't try to load NT service functions from advapi32.dll
12013 except when we need them. (Bug introduced in 0.1.2.7-alpha;
12015 - Fix a longstanding obscure crash bug that could occur when
12016 we run out of DNS worker processes. (Resolves bug 390.)
12018 o Major bugfixes (hidden services):
12019 - Correctly detect whether hidden service descriptor downloads are
12020 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
12022 o Major bugfixes (accounting):
12023 - When we start during an accounting interval before it's time to wake
12024 up, remember to wake up at the correct time. (May fix bug 342.)
12026 o Minor bugfixes (controller):
12027 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
12028 clear the corresponding on_circuit variable, and remember later
12029 that we don't need to send a redundant CLOSED event. Resolves part
12031 - Report events where a resolve succeeded or where we got a socks
12032 protocol error correctly, rather than calling both of them
12034 - Change reported stream target addresses to IP consistently when
12035 we finally get the IP from an exit node.
12036 - Send log messages to the controller even if they happen to be very
12039 o Minor bugfixes (other):
12040 - Display correct results when reporting which versions are
12041 recommended, and how recommended they are. (Resolves bug 383.)
12042 - Improve our estimates for directory bandwidth to be less random:
12043 guess that an unrecognized directory will have the average bandwidth
12044 from all known directories, not that it will have the average
12045 bandwidth from those directories earlier than it on the list.
12046 - If we start a server with ClientOnly 1, then set ClientOnly to 0
12047 and hup, stop triggering an assert based on an empty onion_key.
12048 - On platforms with no working mmap() equivalent, don't warn the
12049 user when cached-routers doesn't exist.
12050 - Warn the user when mmap() [or its equivalent] fails for some reason
12051 other than file-not-found.
12052 - Don't warn the user when cached-routers.new doesn't exist: that's
12053 perfectly fine when starting up for the first time.
12054 - When EntryNodes are configured, rebuild the guard list to contain,
12055 in order: the EntryNodes that were guards before; the rest of the
12056 EntryNodes; the nodes that were guards before.
12057 - Mask out all signals in sub-threads; only the libevent signal
12058 handler should be processing them. This should prevent some crashes
12059 on some machines using pthreads. (Patch from coderman.)
12060 - Fix switched arguments on memset in the implementation of
12061 tor_munmap() for systems with no mmap() call.
12062 - When Tor receives a router descriptor that it asked for, but
12063 no longer wants (because it has received fresh networkstatuses
12064 in the meantime), do not warn the user. Cache the descriptor if
12065 we're a cache; drop it if we aren't.
12066 - Make earlier entry guards _really_ get retried when the network
12068 - On a malformed DNS reply, always give an error to the corresponding
12070 - Build with recent libevents on platforms that do not define the
12071 nonstandard types "u_int8_t" and friends.
12073 o Minor features (controller):
12074 - Warn the user when an application uses the obsolete binary v0
12075 control protocol. We're planning to remove support for it during
12076 the next development series, so it's good to give people some
12078 - Add STREAM_BW events to report per-entry-stream bandwidth
12079 use. (Patch from Robert Hogan.)
12080 - Rate-limit SIGNEWNYM signals in response to controllers that
12081 impolitely generate them for every single stream. (Patch from
12082 mwenge; closes bug 394.)
12083 - Make REMAP stream events have a SOURCE (cache or exit), and
12084 make them generated in every case where we get a successful
12085 connected or resolved cell.
12087 o Minor bugfixes (performance):
12088 - Call router_have_min_dir_info half as often. (This is showing up in
12089 some profiles, but not others.)
12090 - When using GCC, make log_debug never get called at all, and its
12091 arguments never get evaluated, when no debug logs are configured.
12092 (This is showing up in some profiles, but not others.)
12095 - Remove some never-implemented options. Mark PathlenCoinWeight as
12097 - Implement proposal 106: Stop requiring clients to have well-formed
12098 certificates; stop checking nicknames in certificates. (Clients
12099 have certificates so that they can look like Tor servers, but in
12100 the future we might want to allow them to look like regular TLS
12101 clients instead. Nicknames in certificates serve no purpose other
12102 than making our protocol easier to recognize on the wire.)
12103 - Revise messages on handshake failure again to be even more clear about
12104 which are incoming connections and which are outgoing.
12105 - Discard any v1 directory info that's over 1 month old (for
12106 directories) or over 1 week old (for running-routers lists).
12107 - Do not warn when individual nodes in the configuration's EntryNodes,
12108 ExitNodes, etc are down: warn only when all possible nodes
12109 are down. (Fixes bug 348.)
12110 - Always remove expired routers and networkstatus docs before checking
12111 whether we have enough information to build circuits. (Fixes
12113 - Put a lower-bound on MaxAdvertisedBandwidth.
12116 Changes in version 0.1.2.7-alpha - 2007-02-06
12117 o Major bugfixes (rate limiting):
12118 - Servers decline directory requests much more aggressively when
12119 they're low on bandwidth. Otherwise they end up queueing more and
12120 more directory responses, which can't be good for latency.
12121 - But never refuse directory requests from local addresses.
12122 - Fix a memory leak when sending a 503 response for a networkstatus
12124 - Be willing to read or write on local connections (e.g. controller
12125 connections) even when the global rate limiting buckets are empty.
12126 - If our system clock jumps back in time, don't publish a negative
12127 uptime in the descriptor. Also, don't let the global rate limiting
12128 buckets go absurdly negative.
12129 - Flush local controller connection buffers periodically as we're
12130 writing to them, so we avoid queueing 4+ megabytes of data before
12133 o Major bugfixes (NT services):
12134 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
12135 command-line flag so that admins can override the default by saying
12136 "tor --service install --user "SomeUser"". This will not affect
12137 existing installed services. Also, warn the user that the service
12138 will look for its configuration file in the service user's
12139 %appdata% directory. (We can't do the 'hardwire the user's appdata
12140 directory' trick any more, since we may not have read access to that
12143 o Major bugfixes (other):
12144 - Previously, we would cache up to 16 old networkstatus documents
12145 indefinitely, if they came from nontrusted authorities. Now we
12146 discard them if they are more than 10 days old.
12147 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
12149 - Detect and reject malformed DNS responses containing circular
12151 - If exits are rare enough that we're not marking exits as guards,
12152 ignore exit bandwidth when we're deciding the required bandwidth
12154 - When we're handling a directory connection tunneled over Tor,
12155 don't fill up internal memory buffers with all the data we want
12156 to tunnel; instead, only add it if the OR connection that will
12157 eventually receive it has some room for it. (This can lead to
12158 slowdowns in tunneled dir connections; a better solution will have
12159 to wait for 0.2.0.)
12161 o Minor bugfixes (dns):
12162 - Add some defensive programming to eventdns.c in an attempt to catch
12163 possible memory-stomping bugs.
12164 - Detect and reject DNS replies containing IPv4 or IPv6 records with
12165 an incorrect number of bytes. (Previously, we would ignore the
12167 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
12168 in the correct order, and doesn't crash.
12169 - Free memory held in recently-completed DNS lookup attempts on exit.
12170 This was not a memory leak, but may have been hiding memory leaks.
12171 - Handle TTL values correctly on reverse DNS lookups.
12172 - Treat failure to parse resolv.conf as an error.
12174 o Minor bugfixes (other):
12175 - Fix crash with "tor --list-fingerprint" (reported by seeess).
12176 - When computing clock skew from directory HTTP headers, consider what
12177 time it was when we finished asking for the directory, not what
12179 - Expire socks connections if they spend too long waiting for the
12180 handshake to finish. Previously we would let them sit around for
12181 days, if the connecting application didn't close them either.
12182 - And if the socks handshake hasn't started, don't send a
12183 "DNS resolve socks failed" handshake reply; just close it.
12184 - Stop using C functions that OpenBSD's linker doesn't like.
12185 - Don't launch requests for descriptors unless we have networkstatuses
12186 from at least half of the authorities. This delays the first
12187 download slightly under pathological circumstances, but can prevent
12188 us from downloading a bunch of descriptors we don't need.
12189 - Do not log IPs with TLS failures for incoming TLS
12190 connections. (Fixes bug 382.)
12191 - If the user asks to use invalid exit nodes, be willing to use
12193 - Stop using the reserved ac_cv namespace in our configure script.
12194 - Call stat() slightly less often; use fstat() when possible.
12195 - Refactor the way we handle pending circuits when an OR connection
12196 completes or fails, in an attempt to fix a rare crash bug.
12197 - Only rewrite a conn's address based on X-Forwarded-For: headers
12198 if it's a parseable public IP address; and stop adding extra quotes
12199 to the resulting address.
12202 - Weight directory requests by advertised bandwidth. Now we can
12203 let servers enable write limiting but still allow most clients to
12204 succeed at their directory requests. (We still ignore weights when
12205 choosing a directory authority; I hope this is a feature.)
12208 - Create a new file ReleaseNotes which was the old ChangeLog. The
12209 new ChangeLog file now includes the summaries for all development
12211 - Check for addresses with invalid characters at the exit as well
12212 as at the client, and warn less verbosely when they fail. You can
12213 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
12214 - Adapt a patch from goodell to let the contrib/exitlist script
12215 take arguments rather than require direct editing.
12216 - Inform the server operator when we decide not to advertise a
12217 DirPort due to AccountingMax enabled or a low BandwidthRate. It
12218 was confusing Zax, so now we're hopefully more helpful.
12219 - Bring us one step closer to being able to establish an encrypted
12220 directory tunnel without knowing a descriptor first. Still not
12221 ready yet. As part of the change, now assume we can use a
12222 create_fast cell if we don't know anything about a router.
12223 - Allow exit nodes to use nameservers running on ports other than 53.
12224 - Servers now cache reverse DNS replies.
12225 - Add an --ignore-missing-torrc command-line option so that we can
12226 get the "use sensible defaults if the configuration file doesn't
12227 exist" behavior even when specifying a torrc location on the command
12230 o Minor features (controller):
12231 - Track reasons for OR connection failure; make these reasons
12232 available via the controller interface. (Patch from Mike Perry.)
12233 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
12234 can learn when clients are sending malformed hostnames to Tor.
12235 - Clean up documentation for controller status events.
12236 - Add a REMAP status to stream events to note that a stream's
12237 address has changed because of a cached address or a MapAddress
12241 Changes in version 0.1.2.6-alpha - 2007-01-09
12243 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
12244 connection handles more than 4 gigs in either direction, we crash.
12245 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
12246 advertised exit node, somebody might try to exit from us when
12247 we're bootstrapping and before we've built our descriptor yet.
12248 Refuse the connection rather than crashing.
12251 - Warn if we (as a server) find that we've resolved an address that we
12252 weren't planning to resolve.
12253 - Warn that using select() on any libevent version before 1.1 will be
12254 unnecessarily slow (even for select()).
12255 - Flush ERR-level controller status events just like we currently
12256 flush ERR-level log events, so that a Tor shutdown doesn't prevent
12257 the controller from learning about current events.
12259 o Minor features (more controller status events):
12260 - Implement EXTERNAL_ADDRESS server status event so controllers can
12261 learn when our address changes.
12262 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
12263 can learn when directories reject our descriptor.
12264 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
12265 can learn when a client application is speaking a non-socks protocol
12267 - Implement DANGEROUS_SOCKS client status event so controllers
12268 can learn when a client application is leaking DNS addresses.
12269 - Implement BUG general status event so controllers can learn when
12270 Tor is unhappy about its internal invariants.
12271 - Implement CLOCK_SKEW general status event so controllers can learn
12272 when Tor thinks the system clock is set incorrectly.
12273 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
12274 server status events so controllers can learn when their descriptors
12275 are accepted by a directory.
12276 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
12277 server status events so controllers can learn about Tor's progress in
12278 deciding whether it's reachable from the outside.
12279 - Implement BAD_LIBEVENT general status event so controllers can learn
12280 when we have a version/method combination in libevent that needs to
12282 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
12283 and DNS_USELESS server status events so controllers can learn
12284 about changes to DNS server status.
12286 o Minor features (directory):
12287 - Authorities no longer recommend exits as guards if this would shift
12288 too much load to the exit nodes.
12291 Changes in version 0.1.2.5-alpha - 2007-01-06
12293 - Enable write limiting as well as read limiting. Now we sacrifice
12294 capacity if we're pushing out lots of directory traffic, rather
12295 than overrunning the user's intended bandwidth limits.
12296 - Include TLS overhead when counting bandwidth usage; previously, we
12297 would count only the bytes sent over TLS, but not the bytes used
12299 - Support running the Tor service with a torrc not in the same
12300 directory as tor.exe and default to using the torrc located in
12301 the %appdata%\Tor\ of the user who installed the service. Patch
12303 - Servers now check for the case when common DNS requests are going to
12304 wildcarded addresses (i.e. all getting the same answer), and change
12305 their exit policy to reject *:* if it's happening.
12306 - Implement BEGIN_DIR cells, so we can connect to the directory
12307 server via TLS to do encrypted directory requests rather than
12308 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
12309 config options if you like.
12311 o Minor features (config and docs):
12312 - Start using the state file to store bandwidth accounting data:
12313 the bw_accounting file is now obsolete. We'll keep generating it
12314 for a while for people who are still using 0.1.2.4-alpha.
12315 - Try to batch changes to the state file so that we do as few
12316 disk writes as possible while still storing important things in
12318 - The state file and the bw_accounting file get saved less often when
12319 the AvoidDiskWrites config option is set.
12320 - Make PIDFile work on Windows (untested).
12321 - Add internal descriptions for a bunch of configuration options:
12322 accessible via controller interface and in comments in saved
12324 - Reject *:563 (NNTPS) in the default exit policy. We already reject
12325 NNTP by default, so this seems like a sensible addition.
12326 - Clients now reject hostnames with invalid characters. This should
12327 avoid some inadvertent info leaks. Add an option
12328 AllowNonRFC953Hostnames to disable this behavior, in case somebody
12329 is running a private network with hosts called @, !, and #.
12330 - Add a maintainer script to tell us which options are missing
12331 documentation: "make check-docs".
12332 - Add a new address-spec.txt document to describe our special-case
12333 addresses: .exit, .onion, and .noconnnect.
12335 o Minor features (DNS):
12336 - Ongoing work on eventdns infrastructure: now it has dns server
12337 and ipv6 support. One day Tor will make use of it.
12338 - Add client-side caching for reverse DNS lookups.
12339 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
12340 - When we change nameservers or IP addresses, reset and re-launch
12341 our tests for DNS hijacking.
12343 o Minor features (directory):
12344 - Authorities now specify server versions in networkstatus. This adds
12345 about 2% to the size of compressed networkstatus docs, and allows
12346 clients to tell which servers support BEGIN_DIR and which don't.
12347 The implementation is forward-compatible with a proposed future
12348 protocol version scheme not tied to Tor versions.
12349 - DirServer configuration lines now have an orport= option so
12350 clients can open encrypted tunnels to the authorities without
12351 having downloaded their descriptors yet. Enabled for moria1,
12352 moria2, tor26, and lefkada now in the default configuration.
12353 - Directory servers are more willing to send a 503 "busy" if they
12354 are near their write limit, especially for v1 directory requests.
12355 Now they can use their limited bandwidth for actual Tor traffic.
12356 - Clients track responses with status 503 from dirservers. After a
12357 dirserver has given us a 503, we try not to use it until an hour has
12358 gone by, or until we have no dirservers that haven't given us a 503.
12359 - When we get a 503 from a directory, and we're not a server, we don't
12360 count the failure against the total number of failures allowed
12361 for the thing we're trying to download.
12362 - Report X-Your-Address-Is correctly from tunneled directory
12363 connections; don't report X-Your-Address-Is when it's an internal
12364 address; and never believe reported remote addresses when they're
12366 - Protect against an unlikely DoS attack on directory servers.
12367 - Add a BadDirectory flag to network status docs so that authorities
12368 can (eventually) tell clients about caches they believe to be
12371 o Minor features (controller):
12372 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
12373 - Reimplement GETINFO so that info/names stays in sync with the
12375 - Implement "GETINFO fingerprint".
12376 - Implement "SETEVENTS GUARD" so controllers can get updates on
12377 entry guard status as it changes.
12379 o Minor features (clean up obsolete pieces):
12380 - Remove some options that have been deprecated since at least
12381 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
12382 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
12383 to set log options.
12384 - We no longer look for identity and onion keys in "identity.key" and
12385 "onion.key" -- these were replaced by secret_id_key and
12386 secret_onion_key in 0.0.8pre1.
12387 - We no longer require unrecognized directory entries to be
12390 o Major bugfixes (security):
12391 - Stop sending the HttpProxyAuthenticator string to directory
12392 servers when directory connections are tunnelled through Tor.
12393 - Clients no longer store bandwidth history in the state file.
12394 - Do not log introduction points for hidden services if SafeLogging
12396 - When generating bandwidth history, round down to the nearest
12397 1k. When storing accounting data, round up to the nearest 1k.
12398 - When we're running as a server, remember when we last rotated onion
12399 keys, so that we will rotate keys once they're a week old even if
12400 we never stay up for a week ourselves.
12402 o Major bugfixes (other):
12403 - Fix a longstanding bug in eventdns that prevented the count of
12404 timed-out resolves from ever being reset. This bug caused us to
12405 give up on a nameserver the third time it timed out, and try it
12406 10 seconds later... and to give up on it every time it timed out
12408 - Take out the '5 second' timeout from the connection retry
12409 schedule. Now the first connect attempt will wait a full 10
12410 seconds before switching to a new circuit. Perhaps this will help
12411 a lot. Based on observations from Mike Perry.
12412 - Fix a bug on the Windows implementation of tor_mmap_file() that
12413 would prevent the cached-routers file from ever loading. Reported
12417 - Fix an assert failure when a directory authority sets
12418 AuthDirRejectUnlisted and then receives a descriptor from an
12419 unlisted router. Reported by seeess.
12420 - Avoid a double-free when parsing malformed DirServer lines.
12421 - Fix a bug when a BSD-style PF socket is first used. Patch from
12423 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
12424 to resolve an address at a given exit node even when they ask for
12426 - Servers no longer ever list themselves in their "family" line,
12427 even if configured to do so. This makes it easier to configure
12428 family lists conveniently.
12429 - When running as a server, don't fall back to 127.0.0.1 when no
12430 nameservers are configured in /etc/resolv.conf; instead, make the
12431 user fix resolv.conf or specify nameservers explicitly. (Resolves
12433 - Stop accepting certain malformed ports in configured exit policies.
12434 - Don't re-write the fingerprint file every restart, unless it has
12436 - Stop warning when a single nameserver fails: only warn when _all_ of
12437 our nameservers have failed. Also, when we only have one nameserver,
12438 raise the threshold for deciding that the nameserver is dead.
12439 - Directory authorities now only decide that routers are reachable
12440 if their identity keys are as expected.
12441 - When the user uses bad syntax in the Log config line, stop
12442 suggesting other bad syntax as a replacement.
12443 - Correctly detect ipv6 DNS capability on OpenBSD.
12445 o Minor bugfixes (controller):
12446 - Report the circuit number correctly in STREAM CLOSED events. Bug
12447 reported by Mike Perry.
12448 - Do not report bizarre values for results of accounting GETINFOs
12449 when the last second's write or read exceeds the allotted bandwidth.
12450 - Report "unrecognized key" rather than an empty string when the
12451 controller tries to fetch a networkstatus that doesn't exist.
12454 Changes in version 0.1.1.26 - 2006-12-14
12455 o Security bugfixes:
12456 - Stop sending the HttpProxyAuthenticator string to directory
12457 servers when directory connections are tunnelled through Tor.
12458 - Clients no longer store bandwidth history in the state file.
12459 - Do not log introduction points for hidden services if SafeLogging
12463 - Fix an assert failure when a directory authority sets
12464 AuthDirRejectUnlisted and then receives a descriptor from an
12465 unlisted router (reported by seeess).
12468 Changes in version 0.1.2.4-alpha - 2006-12-03
12470 - Add support for using natd; this allows FreeBSDs earlier than
12471 5.1.2 to have ipfw send connections through Tor without using
12472 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
12475 - Make all connections to addresses of the form ".noconnect"
12476 immediately get closed. This lets application/controller combos
12477 successfully test whether they're talking to the same Tor by
12478 watching for STREAM events.
12479 - Make cross.sh cross-compilation script work even when autogen.sh
12480 hasn't been run. (Patch from Michael Mohr.)
12481 - Statistics dumped by -USR2 now include a breakdown of public key
12482 operations, for profiling.
12485 - Fix a major leak when directory authorities parse their
12486 approved-routers list, a minor memory leak when we fail to pick
12487 an exit node, and a few rare leaks on errors.
12488 - Handle TransPort connections even when the server sends data before
12489 the client sends data. Previously, the connection would just hang
12490 until the client sent data. (Patch from tup based on patch from
12492 - Avoid assert failure when our cached-routers file is empty on
12496 - Don't log spurious warnings when we see a circuit close reason we
12497 don't recognize; it's probably just from a newer version of Tor.
12498 - Have directory authorities allow larger amounts of drift in uptime
12499 without replacing the server descriptor: previously, a server that
12500 restarted every 30 minutes could have 48 "interesting" descriptors
12502 - Start linking to the Tor specification and Tor reference manual
12503 correctly in the Windows installer.
12504 - Add Vidalia to the OS X uninstaller script, so when we uninstall
12505 Tor/Privoxy we also uninstall Vidalia.
12506 - Resume building on Irix64, and fix a lot of warnings from its
12507 MIPSpro C compiler.
12508 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
12509 when we're running as a client.
12512 Changes in version 0.1.1.25 - 2006-11-04
12514 - When a client asks us to resolve (rather than connect to)
12515 an address, and we have a cached answer, give them the cached
12516 answer. Previously, we would give them no answer at all.
12517 - We were building exactly the wrong circuits when we predict
12518 hidden service requirements, meaning Tor would have to build all
12519 its circuits on demand.
12520 - If none of our live entry guards have a high uptime, but we
12521 require a guard with a high uptime, try adding a new guard before
12522 we give up on the requirement. This patch should make long-lived
12523 connections more stable on average.
12524 - When testing reachability of our DirPort, don't launch new
12525 tests when there's already one in progress -- unreachable
12526 servers were stacking up dozens of testing streams.
12528 o Security bugfixes:
12529 - When the user sends a NEWNYM signal, clear the client-side DNS
12530 cache too. Otherwise we continue to act on previous information.
12533 - Avoid a memory corruption bug when creating a hash table for
12535 - Avoid possibility of controller-triggered crash when misusing
12536 certain commands from a v0 controller on platforms that do not
12537 handle printf("%s",NULL) gracefully.
12538 - Avoid infinite loop on unexpected controller input.
12539 - Don't log spurious warnings when we see a circuit close reason we
12540 don't recognize; it's probably just from a newer version of Tor.
12541 - Add Vidalia to the OS X uninstaller script, so when we uninstall
12542 Tor/Privoxy we also uninstall Vidalia.
12545 Changes in version 0.1.2.3-alpha - 2006-10-29
12547 - Prepare for servers to publish descriptors less often: never
12548 discard a descriptor simply for being too old until either it is
12549 recommended by no authorities, or until we get a better one for
12550 the same router. Make caches consider retaining old recommended
12551 routers for even longer.
12552 - If most authorities set a BadExit flag for a server, clients
12553 don't think of it as a general-purpose exit. Clients only consider
12554 authorities that advertise themselves as listing bad exits.
12555 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
12556 headers for content, so that we can work better in the presence of
12557 caching HTTP proxies.
12558 - Allow authorities to list nodes as bad exits by fingerprint or by
12561 o Minor features, controller:
12562 - Add a REASON field to CIRC events; for backward compatibility, this
12563 field is sent only to controllers that have enabled the extended
12564 event format. Also, add additional reason codes to explain why
12565 a given circuit has been destroyed or truncated. (Patches from
12567 - Add a REMOTE_REASON field to extended CIRC events to tell the
12568 controller about why a remote OR told us to close a circuit.
12569 - Stream events also now have REASON and REMOTE_REASON fields,
12570 working much like those for circuit events.
12571 - There's now a GETINFO ns/... field so that controllers can ask Tor
12572 about the current status of a router.
12573 - A new event type "NS" to inform a controller when our opinion of
12574 a router's status has changed.
12575 - Add a GETINFO events/names and GETINFO features/names so controllers
12576 can tell which events and features are supported.
12577 - A new CLEARDNSCACHE signal to allow controllers to clear the
12578 client-side DNS cache without expiring circuits.
12580 o Security bugfixes:
12581 - When the user sends a NEWNYM signal, clear the client-side DNS
12582 cache too. Otherwise we continue to act on previous information.
12585 - Avoid sending junk to controllers or segfaulting when a controller
12586 uses EVENT_NEW_DESC with verbose nicknames.
12587 - Stop triggering asserts if the controller tries to extend hidden
12588 service circuits (reported by mwenge).
12589 - Avoid infinite loop on unexpected controller input.
12590 - When the controller does a "GETINFO network-status", tell it
12591 about even those routers whose descriptors are very old, and use
12592 long nicknames where appropriate.
12593 - Change NT service functions to be loaded on demand. This lets us
12594 build with MinGW without breaking Tor for Windows 98 users.
12595 - Do DirPort reachability tests less often, since a single test
12596 chews through many circuits before giving up.
12597 - In the hidden service example in torrc.sample, stop recommending
12598 esoteric and discouraged hidden service options.
12599 - When stopping an NT service, wait up to 10 sec for it to actually
12600 stop. Patch from Matt Edman; resolves bug 295.
12601 - Fix handling of verbose nicknames with ORCONN controller events:
12602 make them show up exactly when requested, rather than exactly when
12604 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
12605 printing a duplicate "$" in the keys we send (reported by mwenge).
12606 - Correctly set maximum connection limit on Cygwin. (This time
12608 - Try to detect Windows correctly when cross-compiling.
12609 - Detect the size of the routers file correctly even if it is
12610 corrupted (on systems without mmap) or not page-aligned (on systems
12611 with mmap). This bug was harmless.
12612 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
12613 to open a stream fails; now we do in more cases. This should
12614 make clients able to find a good exit faster in some cases, since
12615 unhandleable requests will now get an error rather than timing out.
12616 - Resolve two memory leaks when rebuilding the on-disk router cache
12617 (reported by fookoowa).
12618 - Clean up minor code warnings suggested by the MIPSpro C compiler,
12619 and reported by some Centos users.
12620 - Controller signals now work on non-Unix platforms that don't define
12621 SIGUSR1 and SIGUSR2 the way we expect.
12622 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
12623 values before failing, and always enables eventdns.
12624 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
12625 Try to fix this in configure.in by checking for most functions
12626 before we check for libevent.
12629 Changes in version 0.1.2.2-alpha - 2006-10-07
12631 - Make our async eventdns library on-by-default for Tor servers,
12632 and plan to deprecate the separate dnsworker threads.
12633 - Add server-side support for "reverse" DNS lookups (using PTR
12634 records so clients can determine the canonical hostname for a given
12635 IPv4 address). Only supported by servers using eventdns; servers
12636 now announce in their descriptors whether they support eventdns.
12637 - Specify and implement client-side SOCKS5 interface for reverse DNS
12638 lookups (see doc/socks-extensions.txt).
12639 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
12640 connect to directory servers through Tor. Previously, clients needed
12641 to find Tor exits to make private connections to directory servers.
12642 - Avoid choosing Exit nodes for entry or middle hops when the
12643 total bandwidth available from non-Exit nodes is much higher than
12644 the total bandwidth available from Exit nodes.
12645 - Workaround for name servers (like Earthlink's) that hijack failing
12646 DNS requests and replace the no-such-server answer with a "helpful"
12647 redirect to an advertising-driven search portal. Also work around
12648 DNS hijackers who "helpfully" decline to hijack known-invalid
12649 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
12650 lets you turn it off.
12651 - Send out a burst of long-range padding cells once we've established
12652 that we're reachable. Spread them over 4 circuits, so hopefully
12653 a few will be fast. This exercises our bandwidth and bootstraps
12654 us into the directory more quickly.
12656 o New/improved config options:
12657 - Add new config option "ResolvConf" to let the server operator
12658 choose an alternate resolve.conf file when using eventdns.
12659 - Add an "EnforceDistinctSubnets" option to control our "exclude
12660 servers on the same /16" behavior. It's still on by default; this
12661 is mostly for people who want to operate private test networks with
12662 all the machines on the same subnet.
12663 - If one of our entry guards is on the ExcludeNodes list, or the
12664 directory authorities don't think it's a good guard, treat it as
12665 if it were unlisted: stop using it as a guard, and throw it off
12666 the guards list if it stays that way for a long time.
12667 - Allow directory authorities to be marked separately as authorities
12668 for the v1 directory protocol, the v2 directory protocol, and
12669 as hidden service directories, to make it easier to retire old
12670 authorities. V1 authorities should set "HSAuthoritativeDir 1"
12671 to continue being hidden service authorities too.
12672 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
12674 o Minor features, controller:
12675 - Fix CIRC controller events so that controllers can learn the
12676 identity digests of non-Named servers used in circuit paths.
12677 - Let controllers ask for more useful identifiers for servers. Instead
12678 of learning identity digests for un-Named servers and nicknames
12679 for Named servers, the new identifiers include digest, nickname,
12680 and indication of Named status. Off by default; see control-spec.txt
12681 for more information.
12682 - Add a "getinfo address" controller command so it can display Tor's
12683 best guess to the user.
12684 - New controller event to alert the controller when our server
12685 descriptor has changed.
12686 - Give more meaningful errors on controller authentication failure.
12688 o Minor features, other:
12689 - When asked to resolve a hostname, don't use non-exit servers unless
12690 requested to do so. This allows servers with broken DNS to be
12691 useful to the network.
12692 - Divide eventdns log messages into warn and info messages.
12693 - Reserve the nickname "Unnamed" for routers that can't pick
12694 a hostname: any router can call itself Unnamed; directory
12695 authorities will never allocate Unnamed to any particular router;
12696 clients won't believe that any router is the canonical Unnamed.
12697 - Only include function names in log messages for info/debug messages.
12698 For notice/warn/err, the content of the message should be clear on
12699 its own, and printing the function name only confuses users.
12700 - Avoid some false positives during reachability testing: don't try
12701 to test via a server that's on the same /24 as us.
12702 - If we fail to build a circuit to an intended enclave, and it's
12703 not mandatory that we use that enclave, stop wanting it.
12704 - When eventdns is enabled, allow multithreaded builds on NetBSD and
12705 OpenBSD. (We had previously disabled threads on these platforms
12706 because they didn't have working thread-safe resolver functions.)
12708 o Major bugfixes, anonymity/security:
12709 - If a client asked for a server by name, and there's a named server
12710 in our network-status but we don't have its descriptor yet, we
12711 could return an unnamed server instead.
12712 - Fix NetBSD bug that could allow someone to force uninitialized RAM
12713 to be sent to a server's DNS resolver. This only affects NetBSD
12714 and other platforms that do not bounds-check tolower().
12715 - Reject (most) attempts to use Tor circuits with length one. (If
12716 many people start using Tor as a one-hop proxy, exit nodes become
12717 a more attractive target for compromise.)
12718 - Just because your DirPort is open doesn't mean people should be
12719 able to remotely teach you about hidden service descriptors. Now
12720 only accept rendezvous posts if you've got HSAuthoritativeDir set.
12722 o Major bugfixes, other:
12723 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
12724 - When a client asks the server to resolve (not connect to)
12725 an address, and it has a cached answer, give them the cached answer.
12726 Previously, the server would give them no answer at all.
12727 - Allow really slow clients to not hang up five minutes into their
12728 directory downloads (suggested by Adam J. Richter).
12729 - We were building exactly the wrong circuits when we anticipated
12730 hidden service requirements, meaning Tor would have to build all
12731 its circuits on demand.
12732 - Avoid crashing when we mmap a router cache file of size 0.
12733 - When testing reachability of our DirPort, don't launch new
12734 tests when there's already one in progress -- unreachable
12735 servers were stacking up dozens of testing streams.
12737 o Minor bugfixes, correctness:
12738 - If we're a directory mirror and we ask for "all" network status
12739 documents, we would discard status documents from authorities
12740 we don't recognize.
12741 - Avoid a memory corruption bug when creating a hash table for
12743 - Avoid controller-triggered crash when misusing certain commands
12744 from a v0 controller on platforms that do not handle
12745 printf("%s",NULL) gracefully.
12746 - Don't crash when a controller sends a third argument to an
12747 "extendcircuit" request.
12748 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12749 response; fix error code when "getinfo dir/status/" fails.
12750 - Avoid crash when telling controller stream-status and a stream
12752 - Patch from Adam Langley to fix assert() in eventdns.c.
12753 - Fix a debug log message in eventdns to say "X resolved to Y"
12754 instead of "X resolved to X".
12755 - Make eventdns give strings for DNS errors, not just error numbers.
12756 - Track unreachable entry guards correctly: don't conflate
12757 'unreachable by us right now' with 'listed as down by the directory
12758 authorities'. With the old code, if a guard was unreachable by
12759 us but listed as running, it would clog our guard list forever.
12760 - Behave correctly in case we ever have a network with more than
12761 2GB/s total advertised capacity.
12762 - Make TrackExitHosts case-insensitive, and fix the behavior of
12763 ".suffix" TrackExitHosts items to avoid matching in the middle of
12765 - Finally fix the openssl warnings from newer gccs that believe that
12766 ignoring a return value is okay, but casting a return value and
12767 then ignoring it is a sign of madness.
12768 - Prevent the contrib/exitlist script from printing the same
12769 result more than once.
12770 - Patch from Steve Hildrey: Generate network status correctly on
12771 non-versioning dirservers.
12772 - Don't listen to the X-Your-Address-Is hint if you did the lookup
12773 via Tor; otherwise you'll think you're the exit node's IP address.
12775 o Minor bugfixes, performance:
12776 - Two small performance improvements on parsing descriptors.
12777 - Major performance improvement on inserting descriptors: change
12778 algorithm from O(n^2) to O(n).
12779 - Make the common memory allocation path faster on machines where
12780 malloc(0) returns a pointer.
12781 - Start remembering X-Your-Address-Is directory hints even if you're
12782 a client, so you can become a server more smoothly.
12783 - Avoid duplicate entries on MyFamily line in server descriptor.
12785 o Packaging, features:
12786 - Remove architecture from OS X builds. The official builds are
12787 now universal binaries.
12788 - The Debian package now uses --verify-config when (re)starting,
12789 to distinguish configuration errors from other errors.
12790 - Update RPMs to require libevent 1.1b.
12792 o Packaging, bugfixes:
12793 - Patches so Tor builds with MinGW on Windows.
12794 - Patches so Tor might run on Cygwin again.
12795 - Resume building on non-gcc compilers and ancient gcc. Resume
12796 building with the -O0 compile flag. Resume building cleanly on
12798 - Run correctly on OS X platforms with case-sensitive filesystems.
12799 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
12800 - Add autoconf checks so Tor can build on Solaris x86 again.
12803 - Documented (and renamed) ServerDNSSearchDomains and
12804 ServerDNSResolvConfFile options.
12805 - Be clearer that the *ListenAddress directives can be repeated
12809 Changes in version 0.1.1.24 - 2006-09-29
12811 - Allow really slow clients to not hang up five minutes into their
12812 directory downloads (suggested by Adam J. Richter).
12813 - Fix major performance regression from 0.1.0.x: instead of checking
12814 whether we have enough directory information every time we want to
12815 do something, only check when the directory information has changed.
12816 This should improve client CPU usage by 25-50%.
12817 - Don't crash if, after a server has been running for a while,
12818 it can't resolve its hostname.
12821 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12822 - Don't crash when the controller receives a third argument to an
12823 "extendcircuit" request.
12824 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12825 response; fix error code when "getinfo dir/status/" fails.
12826 - Fix configure.in to not produce broken configure files with
12827 more recent versions of autoconf. Thanks to Clint for his auto*
12829 - Fix security bug on NetBSD that could allow someone to force
12830 uninitialized RAM to be sent to a server's DNS resolver. This
12831 only affects NetBSD and other platforms that do not bounds-check
12833 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
12834 methods: these are known to be buggy.
12835 - If we're a directory mirror and we ask for "all" network status
12836 documents, we would discard status documents from authorities
12837 we don't recognize.
12840 Changes in version 0.1.2.1-alpha - 2006-08-27
12842 - Add "eventdns" async dns library from Adam Langley, tweaked to
12843 build on OSX and Windows. Only enabled if you pass the
12844 --enable-eventdns argument to configure.
12845 - Allow servers with no hostname or IP address to learn their
12846 IP address by asking the directory authorities. This code only
12847 kicks in when you would normally have exited with a "no address"
12848 error. Nothing's authenticated, so use with care.
12849 - Rather than waiting a fixed amount of time between retrying
12850 application connections, we wait only 5 seconds for the first,
12851 10 seconds for the second, and 15 seconds for each retry after
12852 that. Hopefully this will improve the expected user experience.
12853 - Patch from Tup to add support for transparent AP connections:
12854 this basically bundles the functionality of trans-proxy-tor
12855 into the Tor mainline. Now hosts with compliant pf/netfilter
12856 implementations can redirect TCP connections straight to Tor
12857 without diverting through SOCKS. Needs docs.
12858 - Busy directory servers save lots of memory by spooling server
12859 descriptors, v1 directories, and v2 networkstatus docs to buffers
12860 as needed rather than en masse. Also mmap the cached-routers
12861 files, so we don't need to keep the whole thing in memory too.
12862 - Automatically avoid picking more than one node from the same
12863 /16 network when constructing a circuit.
12864 - Revise and clean up the torrc.sample that we ship with; add
12865 a section for BandwidthRate and BandwidthBurst.
12868 - Split circuit_t into origin_circuit_t and or_circuit_t, and
12869 split connection_t into edge, or, dir, control, and base structs.
12870 These will save quite a bit of memory on busy servers, and they'll
12871 also help us track down bugs in the code and bugs in the spec.
12872 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
12873 or later. Log when we are doing this, so we can diagnose it when
12874 it fails. (Also, recommend libevent 1.1b for kqueue and
12875 win32 methods; deprecate libevent 1.0b harder; make libevent
12876 recommendation system saner.)
12877 - Start being able to build universal binaries on OS X (thanks
12879 - Export the default exit policy via the control port, so controllers
12880 don't need to guess what it is / will be later.
12881 - Add a man page entry for ProtocolWarnings.
12882 - Add TestVia config option to the man page.
12883 - Remove even more protocol-related warnings from Tor server logs,
12884 such as bad TLS handshakes and malformed begin cells.
12885 - Stop fetching descriptors if you're not a dir mirror and you
12886 haven't tried to establish any circuits lately. [This currently
12887 causes some dangerous behavior, because when you start up again
12888 you'll use your ancient server descriptors.]
12889 - New DirPort behavior: if you have your dirport set, you download
12890 descriptors aggressively like a directory mirror, whether or not
12891 your ORPort is set.
12892 - Get rid of the router_retry_connections notion. Now routers
12893 no longer try to rebuild long-term connections to directory
12894 authorities, and directory authorities no longer try to rebuild
12895 long-term connections to all servers. We still don't hang up
12896 connections in these two cases though -- we need to look at it
12897 more carefully to avoid flapping, and we likely need to wait til
12898 0.1.1.x is obsolete.
12899 - Drop compatibility with obsolete Tors that permit create cells
12900 to have the wrong circ_id_type.
12901 - Re-enable per-connection rate limiting. Get rid of the "OP
12902 bandwidth" concept. Lay groundwork for "bandwidth classes" --
12903 separate global buckets that apply depending on what sort of conn
12905 - Start publishing one minute or so after we find our ORPort
12906 to be reachable. This will help reduce the number of descriptors
12907 we have for ourselves floating around, since it's quite likely
12908 other things (e.g. DirPort) will change during that minute too.
12909 - Fork the v1 directory protocol into its own spec document,
12910 and mark dir-spec.txt as the currently correct (v2) spec.
12913 - When we find our DirPort to be reachable, publish a new descriptor
12914 so we'll tell the world (reported by pnx).
12915 - Publish a new descriptor after we hup/reload. This is important
12916 if our config has changed such that we'll want to start advertising
12917 our DirPort now, etc.
12918 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12919 - When we have a state file we cannot parse, tell the user and
12920 move it aside. Now we avoid situations where the user starts
12921 Tor in 1904, Tor writes a state file with that timestamp in it,
12922 the user fixes her clock, and Tor refuses to start.
12923 - Fix configure.in to not produce broken configure files with
12924 more recent versions of autoconf. Thanks to Clint for his auto*
12926 - "tor --verify-config" now exits with -1(255) or 0 depending on
12927 whether the config options are bad or good.
12928 - Resolve bug 321 when using dnsworkers: append a period to every
12929 address we resolve at the exit node, so that we do not accidentally
12930 pick up local addresses, and so that failing searches are retried
12931 in the resolver search domains. (This is already solved for
12932 eventdns.) (This breaks Blossom servers for now.)
12933 - If we are using an exit enclave and we can't connect, e.g. because
12934 its webserver is misconfigured to not listen on localhost, then
12935 back off and try connecting from somewhere else before we fail.
12938 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
12939 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
12940 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
12941 when the IP address is mapped through MapAddress to a hostname.
12942 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
12943 useless IPv6 DNS resolves.
12944 - Patch suggested by Karsten Loesing: respond to SIGNAL command
12945 before we execute the signal, in case the signal shuts us down.
12946 - Clean up AllowInvalidNodes man page entry.
12947 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
12948 - Add more asserts to track down an assert error on a windows Tor
12949 server with connection_add being called with socket == -1.
12950 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
12951 - Fix misleading log messages: an entry guard that is "unlisted",
12952 as well as not known to be "down" (because we've never heard
12953 of it), is not therefore "up".
12954 - Remove code to special-case "-cvs" ending, since it has not
12955 actually mattered since 0.0.9.
12956 - Make our socks5 handling more robust to broken socks clients:
12957 throw out everything waiting on the buffer in between socks
12958 handshake phases, since they can't possibly (so the theory
12959 goes) have predicted what we plan to respond to them.
12962 Changes in version 0.1.1.23 - 2006-07-30
12964 - Fast Tor servers, especially exit nodes, were triggering asserts
12965 due to a bug in handling the list of pending DNS resolves. Some
12966 bugs still remain here; we're hunting them.
12967 - Entry guards could crash clients by sending unexpected input.
12968 - More fixes on reachability testing: if you find yourself reachable,
12969 then don't ever make any client requests (so you stop predicting
12970 circuits), then hup or have your clock jump, then later your IP
12971 changes, you won't think circuits are working, so you won't try to
12972 test reachability, so you won't publish.
12975 - Avoid a crash if the controller does a resetconf firewallports
12976 and then a setconf fascistfirewall=1.
12977 - Avoid an integer underflow when the dir authority decides whether
12978 a router is stable: we might wrongly label it stable, and compute
12979 a slightly wrong median stability, when a descriptor is published
12981 - Fix a place where we might trigger an assert if we can't build our
12982 own server descriptor yet.
12985 Changes in version 0.1.1.22 - 2006-07-05
12987 - Fix a big bug that was causing servers to not find themselves
12988 reachable if they changed IP addresses. Since only 0.1.1.22+
12989 servers can do reachability testing correctly, now we automatically
12990 make sure to test via one of these.
12991 - Fix to allow clients and mirrors to learn directory info from
12992 descriptor downloads that get cut off partway through.
12993 - Directory authorities had a bug in deciding if a newly published
12994 descriptor was novel enough to make everybody want a copy -- a few
12995 servers seem to be publishing new descriptors many times a minute.
12997 - Fix a rare bug that was causing some servers to complain about
12998 "closing wedged cpuworkers" and skip some circuit create requests.
12999 - Make the Exit flag in directory status documents actually work.
13002 Changes in version 0.1.1.21 - 2006-06-10
13003 o Crash and assert fixes from 0.1.1.20:
13004 - Fix a rare crash on Tor servers that have enabled hibernation.
13005 - Fix a seg fault on startup for Tor networks that use only one
13006 directory authority.
13007 - Fix an assert from a race condition that occurs on Tor servers
13008 while exiting, where various threads are trying to log that they're
13009 exiting, and delete the logs, at the same time.
13010 - Make our unit tests pass again on certain obscure platforms.
13013 - Add support for building SUSE RPM packages.
13014 - Speed up initial bootstrapping for clients: if we are making our
13015 first ever connection to any entry guard, then don't mark it down
13017 - When only one Tor server in the network is labelled as a guard,
13018 and we've already picked him, we would cycle endlessly picking him
13019 again, being unhappy about it, etc. Now we specifically exclude
13020 current guards when picking a new guard.
13021 - Servers send create cells more reliably after the TLS connection
13022 is established: we were sometimes forgetting to send half of them
13023 when we had more than one pending.
13024 - If we get a create cell that asks us to extend somewhere, but the
13025 Tor server there doesn't match the expected digest, we now send
13026 a destroy cell back, rather than silently doing nothing.
13027 - Make options->RedirectExit work again.
13028 - Make cookie authentication for the controller work again.
13029 - Stop being picky about unusual characters in the arguments to
13030 mapaddress. It's none of our business.
13031 - Add a new config option "TestVia" that lets you specify preferred
13032 middle hops to use for test circuits. Perhaps this will let me
13033 debug the reachability problems better.
13035 o Log / documentation fixes:
13036 - If we're a server and some peer has a broken TLS certificate, don't
13037 log about it unless ProtocolWarnings is set, i.e., we want to hear
13038 about protocol violations by others.
13039 - Fix spelling of VirtualAddrNetwork in man page.
13040 - Add a better explanation at the top of the autogenerated torrc file
13041 about what happened to our old torrc.
13044 Changes in version 0.1.1.20 - 2006-05-23
13046 - Downgrade a log severity where servers complain that they're
13048 - Avoid a compile warning on FreeBSD.
13049 - Remove string size limit on NEWDESC messages; solve bug 291.
13050 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
13051 more thoroughly when we're running on windows.
13054 Changes in version 0.1.1.19-rc - 2006-05-03
13056 - Regenerate our local descriptor if it's dirty and we try to use
13057 it locally (e.g. if it changes during reachability detection).
13058 - If we setconf our ORPort to 0, we continued to listen on the
13059 old ORPort and receive connections.
13060 - Avoid a second warning about machine/limits.h on Debian
13062 - Be willing to add our own routerinfo into the routerlist.
13063 Now authorities will include themselves in their directories
13064 and network-statuses.
13065 - Stop trying to upload rendezvous descriptors to every
13066 directory authority: only try the v1 authorities.
13067 - Servers no longer complain when they think they're not
13068 registered with the directory authorities. There were too many
13070 - Backport dist-rpm changes so rpms can be built without errors.
13073 - Implement an option, VirtualAddrMask, to set which addresses
13074 get handed out in response to mapaddress requests. This works
13075 around a bug in tsocks where 127.0.0.0/8 is never socksified.
13078 Changes in version 0.1.1.18-rc - 2006-04-10
13080 - Work harder to download live network-statuses from all the
13081 directory authorities we know about. Improve the threshold
13082 decision logic so we're more robust to edge cases.
13083 - When fetching rendezvous descriptors, we were willing to ask
13084 v2 authorities too, which would always return 404.
13087 - Stop listing down or invalid nodes in the v1 directory. This will
13088 reduce its bulk by about 1/3, and reduce load on directory
13090 - When deciding whether a router is Fast or Guard-worthy, consider
13091 his advertised BandwidthRate and not just the BandwidthCapacity.
13092 - No longer ship INSTALL and README files -- they are useless now.
13093 - Force rpmbuild to behave and honor target_cpu.
13094 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
13095 - Start to include translated versions of the tor-doc-*.html
13096 files, along with the screenshots. Still needs more work.
13097 - Start sending back 512 and 451 errors if mapaddress fails,
13098 rather than not sending anything back at all.
13099 - When we fail to bind or listen on an incoming or outgoing
13100 socket, we should close it before failing. otherwise we just
13101 leak it. (thanks to weasel for finding.)
13102 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
13103 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
13104 - Make NoPublish (even though deprecated) work again.
13105 - Fix a minor security flaw where a versioning auth dirserver
13106 could list a recommended version many times in a row to make
13107 clients more convinced that it's recommended.
13108 - Fix crash bug if there are two unregistered servers running
13109 with the same nickname, one of them is down, and you ask for
13110 them by nickname in your EntryNodes or ExitNodes. Also, try
13111 to pick the one that's running rather than an arbitrary one.
13112 - Fix an infinite loop we could hit if we go offline for too long.
13113 - Complain when we hit WSAENOBUFS on recv() or write() too.
13114 Perhaps this will help us hunt the bug.
13115 - If you're not a versioning dirserver, don't put the string
13116 "client-versions \nserver-versions \n" in your network-status.
13117 - Lower the minimum required number of file descriptors to 1000,
13118 so we can have some overhead for Valgrind on Linux, where the
13119 default ulimit -n is 1024.
13122 - Add tor.dizum.com as the fifth authoritative directory server.
13123 - Add a new config option FetchUselessDescriptors, off by default,
13124 for when you plan to run "exitlist" on your client and you want
13125 to know about even the non-running descriptors.
13128 Changes in version 0.1.1.17-rc - 2006-03-28
13130 - Clients and servers since 0.1.1.10-alpha have been expiring
13131 connections whenever they are idle for 5 minutes and they *do*
13132 have circuits on them. Oops. With this new version, clients will
13133 discard their previous entry guard choices and avoid choosing
13134 entry guards running these flawed versions.
13135 - Fix memory leak when uncompressing concatenated zlib streams. This
13136 was causing substantial leaks over time on Tor servers.
13137 - The v1 directory was including servers as much as 48 hours old,
13138 because that's how the new routerlist->routers works. Now only
13139 include them if they're 20 hours old or less.
13142 - Resume building on irix64, netbsd 2.0, etc.
13143 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
13145 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
13146 and it is confusing some users.
13147 - Mirrors stop caching the v1 directory so often.
13148 - Make the max number of old descriptors that a cache will hold
13149 rise with the number of directory authorities, so we can scale.
13150 - Change our win32 uname() hack to be more forgiving about what
13151 win32 versions it thinks it's found.
13154 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
13156 - When the controller's *setconf commands fail, collect an error
13157 message in a string and hand it back to the controller.
13158 - Make the v2 dir's "Fast" flag based on relative capacity, just
13159 like "Stable" is based on median uptime. Name everything in the
13160 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
13161 - Log server fingerprint on startup, so new server operators don't
13162 have to go hunting around their filesystem for it.
13163 - Return a robots.txt on our dirport to discourage google indexing.
13164 - Let the controller ask for GETINFO dir/status/foo so it can ask
13165 directly rather than connecting to the dir port. Only works when
13166 dirport is set for now.
13168 o New config options rather than constants in the code:
13169 - SocksTimeout: How long do we let a socks connection wait
13170 unattached before we fail it?
13171 - CircuitBuildTimeout: Cull non-open circuits that were born
13172 at least this many seconds ago.
13173 - CircuitIdleTimeout: Cull open clean circuits that were born
13174 at least this many seconds ago.
13177 Changes in version 0.1.1.16-rc - 2006-03-18
13178 o Bugfixes on 0.1.1.15-rc:
13179 - Fix assert when the controller asks to attachstream a connect-wait
13180 or resolve-wait stream.
13181 - Now do address rewriting when the controller asks us to attach
13182 to a particular circuit too. This will let Blossom specify
13183 "moria2.exit" without having to learn what moria2's IP address is.
13184 - Make the "tor --verify-config" command-line work again, so people
13185 can automatically check if their torrc will parse.
13186 - Authoritative dirservers no longer require an open connection from
13187 a server to consider him "reachable". We need this change because
13188 when we add new auth dirservers, old servers won't know not to
13190 - Let Tor build on Sun CC again.
13191 - Fix an off-by-one buffer size in dirserv.c that magically never
13192 hit our three authorities but broke sjmurdoch's own tor network.
13193 - If we as a directory mirror don't know of any v1 directory
13194 authorities, then don't try to cache any v1 directories.
13195 - Stop warning about unknown servers in our family when they are
13196 given as hex digests.
13197 - Stop complaining as quickly to the server operator that he
13198 hasn't registered his nickname/key binding.
13199 - Various cleanups so we can add new V2 Auth Dirservers.
13200 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
13201 reflect the updated flags in our v2 dir protocol.
13202 - Resume allowing non-printable characters for exit streams (both
13203 for connecting and for resolving). Now we tolerate applications
13204 that don't follow the RFCs. But continue to block malformed names
13207 o Bugfixes on 0.1.0.x:
13208 - Fix assert bug in close_logs(): when we close and delete logs,
13209 remove them all from the global "logfiles" list.
13210 - Fix minor integer overflow in calculating when we expect to use up
13211 our bandwidth allocation before hibernating.
13212 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
13213 there are multiple SSLs installed with different versions.
13214 - When we try to be a server and Address is not explicitly set and
13215 our hostname resolves to a private IP address, try to use an
13216 interface address if it has a public address. Now Windows machines
13217 that think of themselves as localhost can work by default.
13220 - Let the controller ask for GETINFO dir/server/foo so it can ask
13221 directly rather than connecting to the dir port.
13222 - Let the controller tell us about certain router descriptors
13223 that it doesn't want Tor to use in circuits. Implement
13224 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
13225 - New config option SafeSocks to reject all application connections
13226 using unsafe socks protocols. Defaults to off.
13229 Changes in version 0.1.1.15-rc - 2006-03-11
13230 o Bugfixes and cleanups:
13231 - When we're printing strings from the network, don't try to print
13232 non-printable characters. This protects us against shell escape
13233 sequence exploits, and also against attacks to fool humans into
13234 misreading their logs.
13235 - Fix a bug where Tor would fail to establish any connections if you
13236 left it off for 24 hours and then started it: we were happy with
13237 the obsolete network statuses, but they all referred to router
13238 descriptors that were too old to fetch, so we ended up with no
13239 valid router descriptors.
13240 - Fix a seg fault in the controller's "getinfo orconn-status"
13241 command while listing status on incoming handshaking connections.
13242 Introduce a status name "NEW" for these connections.
13243 - If we get a linelist or linelist_s config option from the torrc
13244 (e.g. ExitPolicy) and it has no value, warn and skip rather than
13245 silently resetting it to its default.
13246 - Don't abandon entry guards until they've been down or gone for
13248 - Cleaner and quieter log messages.
13251 - New controller signal NEWNYM that makes new application requests
13252 use clean circuits.
13253 - Add a new circuit purpose 'controller' to let the controller ask
13254 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
13255 controller command to let you specify the purpose if you're
13256 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
13257 command to let you change a circuit's purpose after it's been
13259 - Accept "private:*" in routerdesc exit policies; not generated yet
13260 because older Tors do not understand it.
13261 - Add BSD-style contributed startup script "rc.subr" from Peter
13265 Changes in version 0.1.1.14-alpha - 2006-02-20
13266 o Bugfixes on 0.1.1.x:
13267 - Don't die if we ask for a stdout or stderr log (even implicitly)
13268 and we're set to RunAsDaemon -- just warn.
13269 - We still had a few bugs in the OR connection rotation code that
13270 caused directory servers to slowly aggregate connections to other
13271 fast Tor servers. This time for sure!
13272 - Make log entries on Win32 include the name of the function again.
13273 - We were treating a pair of exit policies if they were equal even
13274 if one said accept and the other said reject -- causing us to
13275 not always publish a new descriptor since we thought nothing
13277 - Retry pending server downloads as well as pending networkstatus
13278 downloads when we unexpectedly get a socks request.
13279 - We were ignoring the IS_FAST flag in the directory status,
13280 meaning we were willing to pick trivial-bandwidth nodes for "fast"
13282 - If the controller's SAVECONF command fails (e.g. due to file
13283 permissions), let the controller know that it failed.
13286 - If we're trying to be a Tor server and running Windows 95/98/ME
13287 as a server, explain that we'll likely crash.
13288 - When we're a server, a client asks for an old-style directory,
13289 and our write bucket is empty, don't give it to him. This way
13290 small servers can continue to serve the directory *sometimes*,
13291 without getting overloaded.
13292 - Compress exit policies even more -- look for duplicate lines
13294 - Clients now honor the "guard" flag in the router status when
13295 picking entry guards, rather than looking at is_fast or is_stable.
13296 - Retain unrecognized lines in $DATADIR/state file, so that we can
13297 be forward-compatible.
13298 - Generate 18.0.0.0/8 address policy format in descs when we can;
13299 warn when the mask is not reducible to a bit-prefix.
13300 - Let the user set ControlListenAddress in the torrc. This can be
13301 dangerous, but there are some cases (like a secured LAN) where it
13303 - Split ReachableAddresses into ReachableDirAddresses and
13304 ReachableORAddresses, so we can restrict Dir conns to port 80
13305 and OR conns to port 443.
13306 - Now we can target arch and OS in rpm builds (contributed by
13307 Phobos). Also make the resulting dist-rpm filename match the
13309 - New config options to help controllers: FetchServerDescriptors
13310 and FetchHidServDescriptors for whether to fetch server
13311 info and hidserv info or let the controller do it, and
13312 PublishServerDescriptor and PublishHidServDescriptors.
13313 - Also let the controller set the __AllDirActionsPrivate config
13314 option if you want all directory fetches/publishes to happen via
13315 Tor (it assumes your controller bootstraps your circuits).
13318 Changes in version 0.1.0.17 - 2006-02-17
13319 o Crash bugfixes on 0.1.0.x:
13320 - When servers with a non-zero DirPort came out of hibernation,
13321 sometimes they would trigger an assert.
13323 o Other important bugfixes:
13324 - On platforms that don't have getrlimit (like Windows), we were
13325 artificially constraining ourselves to a max of 1024
13326 connections. Now just assume that we can handle as many as 15000
13327 connections. Hopefully this won't cause other problems.
13329 o Backported features:
13330 - When we're a server, a client asks for an old-style directory,
13331 and our write bucket is empty, don't give it to him. This way
13332 small servers can continue to serve the directory *sometimes*,
13333 without getting overloaded.
13334 - Whenever you get a 503 in response to a directory fetch, try
13335 once more. This will become important once servers start sending
13336 503's whenever they feel busy.
13337 - Fetch a new directory every 120 minutes, not every 40 minutes.
13338 Now that we have hundreds of thousands of users running the old
13339 directory algorithm, it's starting to hurt a lot.
13340 - Bump up the period for forcing a hidden service descriptor upload
13341 from 20 minutes to 1 hour.
13344 Changes in version 0.1.1.13-alpha - 2006-02-09
13345 o Crashes in 0.1.1.x:
13346 - When you tried to setconf ORPort via the controller, Tor would
13347 crash. So people using TorCP to become a server were sad.
13348 - Solve (I hope) the stack-smashing bug that we were seeing on fast
13349 servers. The problem appears to be something do with OpenSSL's
13350 random number generation, or how we call it, or something. Let me
13351 know if the crashes continue.
13352 - Turn crypto hardware acceleration off by default, until we find
13353 somebody smart who can test it for us. (It appears to produce
13354 seg faults in at least some cases.)
13355 - Fix a rare assert error when we've tried all intro points for
13356 a hidden service and we try fetching the service descriptor again:
13357 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
13360 - Fix a major load balance bug: we were round-robining in 16 KB
13361 chunks, and servers with bandwidthrate of 20 KB, while downloading
13362 a 600 KB directory, would starve their other connections. Now we
13363 try to be a bit more fair.
13364 - Dir authorities and mirrors were never expiring the newest
13365 descriptor for each server, causing memory and directory bloat.
13366 - Fix memory-bloating and connection-bloating bug on servers: We
13367 were never closing any connection that had ever had a circuit on
13368 it, because we were checking conn->n_circuits == 0, yet we had a
13369 bug that let it go negative.
13370 - Make Tor work using squid as your http proxy again -- squid
13371 returns an error if you ask for a URL that's too long, and it uses
13372 a really generic error message. Plus, many people are behind a
13373 transparent squid so they don't even realize it.
13374 - On platforms that don't have getrlimit (like Windows), we were
13375 artificially constraining ourselves to a max of 1024
13376 connections. Now just assume that we can handle as many as 15000
13377 connections. Hopefully this won't cause other problems.
13378 - Add a new config option ExitPolicyRejectPrivate which defaults to
13379 1. This means all exit policies will begin with rejecting private
13380 addresses, unless the server operator explicitly turns it off.
13383 - Clients no longer download descriptors for non-running
13385 - Before we add new directory authorities, we should make it
13386 clear that only v1 authorities should receive/publish hidden
13387 service descriptors.
13390 - As soon as we've fetched some more directory info, immediately
13391 try to download more server descriptors. This way we don't have
13392 a 10 second pause during initial bootstrapping.
13393 - Remove even more loud log messages that the server operator can't
13395 - When we're running an obsolete or un-recommended version, make
13396 the log message more clear about what the problem is and what
13397 versions *are* still recommended.
13398 - Provide a more useful warn message when our onion queue gets full:
13399 the CPU is too slow or the exit policy is too liberal.
13400 - Don't warn when we receive a 503 from a dirserver/cache -- this
13401 will pave the way for them being able to refuse if they're busy.
13402 - When we fail to bind a listener, try to provide a more useful
13403 log message: e.g., "Is Tor already running?"
13404 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
13405 Goldberg can prove things about our handshake protocol more
13407 - MaxConn has been obsolete for a while now. Document the ConnLimit
13408 config option, which is a *minimum* number of file descriptors
13409 that must be available else Tor refuses to start.
13410 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
13411 if you log to syslog and want something other than LOG_DAEMON.
13412 - Make dirservers generate a separate "guard" flag to mean,
13413 "would make a good entry guard". Make clients parse it and vote
13414 on it. Not used by clients yet.
13415 - Implement --with-libevent-dir option to ./configure. Also, improve
13416 search techniques to find libevent, and use those for openssl too.
13417 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
13418 - Only start testing reachability once we've established a
13419 circuit. This will make startup on dirservers less noisy.
13420 - Don't try to upload hidden service descriptors until we have
13421 established a circuit.
13422 - Fix the controller's "attachstream 0" command to treat conn like
13423 it just connected, doing address remapping, handling .exit and
13424 .onion idioms, and so on. Now we're more uniform in making sure
13425 that the controller hears about new and closing connections.
13428 Changes in version 0.1.1.12-alpha - 2006-01-11
13429 o Bugfixes on 0.1.1.x:
13430 - The fix to close duplicate server connections was closing all
13431 Tor client connections if they didn't establish a circuit
13432 quickly enough. Oops.
13433 - Fix minor memory issue (double-free) that happened on exit.
13435 o Bugfixes on 0.1.0.x:
13436 - Tor didn't warn when it failed to open a log file.
13439 Changes in version 0.1.1.11-alpha - 2006-01-10
13440 o Crashes in 0.1.1.x:
13441 - Include all the assert/crash fixes from 0.1.0.16.
13442 - If you start Tor and then quit very quickly, there were some
13443 races that tried to free things that weren't allocated yet.
13444 - Fix a rare memory stomp if you're running hidden services.
13445 - Fix segfault when specifying DirServer in config without nickname.
13446 - Fix a seg fault when you finish connecting to a server but at
13447 that moment you dump his server descriptor.
13448 - Extendcircuit and Attachstream controller commands would
13449 assert/crash if you don't give them enough arguments.
13450 - Fix an assert error when we're out of space in the connection_list
13451 and we try to post a hidden service descriptor (reported by weasel).
13452 - If you specify a relative torrc path and you set RunAsDaemon in
13453 your torrc, then it chdir()'s to the new directory. If you HUP,
13454 it tries to load the new torrc location, fails, and exits.
13455 The fix: no longer allow a relative path to torrc using -f.
13458 - Implement "entry guards": automatically choose a handful of entry
13459 nodes and stick with them for all circuits. Only pick new guards
13460 when the ones you have are unsuitable, and if the old guards
13461 become suitable again, switch back. This will increase security
13462 dramatically against certain end-point attacks. The EntryNodes
13463 config option now provides some hints about which entry guards you
13464 want to use most; and StrictEntryNodes means to only use those.
13465 - New directory logic: download by descriptor digest, not by
13466 fingerprint. Caches try to download all listed digests from
13467 authorities; clients try to download "best" digests from caches.
13468 This avoids partitioning and isolating attacks better.
13469 - Make the "stable" router flag in network-status be the median of
13470 the uptimes of running valid servers, and make clients pay
13471 attention to the network-status flags. Thus the cutoff adapts
13472 to the stability of the network as a whole, making IRC, IM, etc
13473 connections more reliable.
13476 - Tor servers with dynamic IP addresses were needing to wait 18
13477 hours before they could start doing reachability testing using
13478 the new IP address and ports. This is because they were using
13479 the internal descriptor to learn what to test, yet they were only
13480 rebuilding the descriptor once they decided they were reachable.
13481 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
13482 to download certain server descriptors, throw them away, and then
13483 fetch them again after 30 minutes. Now mirrors throw away these
13484 server descriptors so clients can't get them.
13485 - We were leaving duplicate connections to other ORs open for a week,
13486 rather than closing them once we detect a duplicate. This only
13487 really affected authdirservers, but it affected them a lot.
13488 - Spread the authdirservers' reachability testing over the entire
13489 testing interval, so we don't try to do 500 TLS's at once every
13493 - If the network is down, and we try to connect to a conn because
13494 we have a circuit in mind, and we timeout (30 seconds) because the
13495 network never answers, we were expiring the circuit, but we weren't
13496 obsoleting the connection or telling the entry_guards functions.
13497 - Some Tor servers process billions of cells per day. These statistics
13498 need to be uint64_t's.
13499 - Check for integer overflows in more places, when adding elements
13500 to smartlists. This could possibly prevent a buffer overflow
13501 on malicious huge inputs. I don't see any, but I haven't looked
13503 - ReachableAddresses kept growing new "reject *:*" lines on every
13505 - When you "setconf log" via the controller, it should remove all
13506 logs. We were automatically adding back in a "log notice stdout".
13507 - Newly bootstrapped Tor networks couldn't establish hidden service
13508 circuits until they had nodes with high uptime. Be more tolerant.
13509 - We were marking servers down when they could not answer every piece
13510 of the directory request we sent them. This was far too harsh.
13511 - Fix the torify (tsocks) config file to not use Tor for localhost
13513 - Directory authorities now go to the proper authority when asking for
13514 a networkstatus, even when they want a compressed one.
13515 - Fix a harmless bug that was causing Tor servers to log
13516 "Got an end because of misc error, but we're not an AP. Closing."
13517 - Authorities were treating their own descriptor changes as cosmetic,
13518 meaning the descriptor available in the network-status and the
13519 descriptor that clients downloaded were different.
13520 - The OS X installer was adding a symlink for tor_resolve but
13521 the binary was called tor-resolve (reported by Thomas Hardly).
13522 - Workaround a problem with some http proxies where they refuse GET
13523 requests that specify "Content-Length: 0" (reported by Adrian).
13524 - Fix wrong log message when you add a "HiddenServiceNodes" config
13525 line without any HiddenServiceDir line (reported by Chris Thomas).
13528 - Write the TorVersion into the state file so we have a prayer of
13529 keeping forward and backward compatibility.
13530 - Revive the FascistFirewall config option rather than eliminating it:
13531 now it's a synonym for ReachableAddresses *:80,*:443.
13532 - Clients choose directory servers from the network status lists,
13533 not from their internal list of router descriptors. Now they can
13534 go to caches directly rather than needing to go to authorities
13536 - Directory authorities ignore router descriptors that have only
13537 cosmetic differences: do this for 0.1.0.x servers now too.
13538 - Add a new flag to network-status indicating whether the server
13539 can answer v2 directory requests too.
13540 - Authdirs now stop whining so loudly about bad descriptors that
13541 they fetch from other dirservers. So when there's a log complaint,
13542 it's for sure from a freshly uploaded descriptor.
13543 - Reduce memory requirements in our structs by changing the order
13545 - There used to be two ways to specify your listening ports in a
13546 server descriptor: on the "router" line and with a separate "ports"
13547 line. Remove support for the "ports" line.
13548 - New config option "AuthDirRejectUnlisted" for auth dirservers as
13549 a panic button: if we get flooded with unusable servers we can
13550 revert to only listing servers in the approved-routers file.
13551 - Auth dir servers can now mark a fingerprint as "!reject" or
13552 "!invalid" in the approved-routers file (as its nickname), to
13553 refuse descriptors outright or include them but marked as invalid.
13554 - Servers store bandwidth history across restarts/crashes.
13555 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
13556 get a better idea of why their circuits failed. Not used yet.
13557 - Directory mirrors now cache up to 16 unrecognized network-status
13558 docs. Now we can add new authdirservers and they'll be cached too.
13559 - When picking a random directory, prefer non-authorities if any
13561 - New controller option "getinfo desc/all-recent" to fetch the
13562 latest server descriptor for every router that Tor knows about.
13565 Changes in version 0.1.0.16 - 2006-01-02
13566 o Crash bugfixes on 0.1.0.x:
13567 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
13568 corrupting the heap, losing FDs, or crashing when we need to resize
13569 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
13570 - It turns out sparc64 platforms crash on unaligned memory access
13571 too -- so detect and avoid this.
13572 - Handle truncated compressed data correctly (by detecting it and
13574 - Fix possible-but-unlikely free(NULL) in control.c.
13575 - When we were closing connections, there was a rare case that
13576 stomped on memory, triggering seg faults and asserts.
13577 - Avoid potential infinite recursion when building a descriptor. (We
13578 don't know that it ever happened, but better to fix it anyway.)
13579 - We were neglecting to unlink marked circuits from soon-to-close OR
13580 connections, which caused some rare scribbling on freed memory.
13581 - Fix a memory stomping race bug when closing the joining point of two
13582 rendezvous circuits.
13583 - Fix an assert in time parsing found by Steven Murdoch.
13585 o Other bugfixes on 0.1.0.x:
13586 - When we're doing reachability testing, provide more useful log
13587 messages so the operator knows what to expect.
13588 - Do not check whether DirPort is reachable when we are suppressing
13589 advertising it because of hibernation.
13590 - When building with -static or on Solaris, we sometimes needed -ldl.
13591 - When we're deciding whether a stream has enough circuits around
13592 that can handle it, count the freshly dirty ones and not the ones
13593 that are so dirty they won't be able to handle it.
13594 - When we're expiring old circuits, we had a logic error that caused
13595 us to close new rendezvous circuits rather than old ones.
13596 - Give a more helpful log message when you try to change ORPort via
13597 the controller: you should upgrade Tor if you want that to work.
13598 - We were failing to parse Tor versions that start with "Tor ".
13599 - Tolerate faulty streams better: when a stream fails for reason
13600 exitpolicy, stop assuming that the router is lying about his exit
13601 policy. When a stream fails for reason misc, allow it to retry just
13602 as if it was resolvefailed. When a stream has failed three times,
13603 reset its failure count so we can try again and get all three tries.
13606 Changes in version 0.1.1.10-alpha - 2005-12-11
13607 o Correctness bugfixes on 0.1.0.x:
13608 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
13609 corrupting the heap, losing FDs, or crashing when we need to resize
13610 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
13611 - Stop doing the complex voodoo overkill checking for insecure
13612 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
13613 - When we were closing connections, there was a rare case that
13614 stomped on memory, triggering seg faults and asserts.
13615 - We were neglecting to unlink marked circuits from soon-to-close OR
13616 connections, which caused some rare scribbling on freed memory.
13617 - When we're deciding whether a stream has enough circuits around
13618 that can handle it, count the freshly dirty ones and not the ones
13619 that are so dirty they won't be able to handle it.
13620 - Recover better from TCP connections to Tor servers that are
13621 broken but don't tell you (it happens!); and rotate TLS
13622 connections once a week.
13623 - When we're expiring old circuits, we had a logic error that caused
13624 us to close new rendezvous circuits rather than old ones.
13625 - Fix a scary-looking but apparently harmless bug where circuits
13626 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
13627 servers, and never switch to state CIRCUIT_STATE_OPEN.
13628 - When building with -static or on Solaris, we sometimes needed to
13630 - Give a useful message when people run Tor as the wrong user,
13631 rather than telling them to start chowning random directories.
13632 - We were failing to inform the controller about new .onion streams.
13634 o Security bugfixes on 0.1.0.x:
13635 - Refuse server descriptors if the fingerprint line doesn't match
13636 the included identity key. Tor doesn't care, but other apps (and
13637 humans) might actually be trusting the fingerprint line.
13638 - We used to kill the circuit when we receive a relay command we
13639 don't recognize. Now we just drop it.
13640 - Start obeying our firewall options more rigorously:
13641 . If we can't get to a dirserver directly, try going via Tor.
13642 . Don't ever try to connect (as a client) to a place our
13643 firewall options forbid.
13644 . If we specify a proxy and also firewall options, obey the
13645 firewall options even when we're using the proxy: some proxies
13646 can only proxy to certain destinations.
13647 - Fix a bug found by Lasse Overlier: when we were making internal
13648 circuits (intended to be cannibalized later for rendezvous and
13649 introduction circuits), we were picking them so that they had
13650 useful exit nodes. There was no need for this, and it actually
13651 aids some statistical attacks.
13652 - Start treating internal circuits and exit circuits separately.
13653 It's important to keep them separate because internal circuits
13654 have their last hops picked like middle hops, rather than like
13655 exit hops. So exiting on them will break the user's expectations.
13657 o Bugfixes on 0.1.1.x:
13658 - Take out the mis-feature where we tried to detect IP address
13659 flapping for people with DynDNS, and chose not to upload a new
13660 server descriptor sometimes.
13661 - Try to be compatible with OpenSSL 0.9.6 again.
13662 - Log fix: when the controller is logging about .onion addresses,
13663 sometimes it didn't include the ".onion" part of the address.
13664 - Don't try to modify options->DirServers internally -- if the
13665 user didn't specify any, just add the default ones directly to
13666 the trusted dirserver list. This fixes a bug where people running
13667 controllers would use SETCONF on some totally unrelated config
13668 option, and Tor would start yelling at them about changing their
13670 - Let the controller's redirectstream command specify a port, in
13671 case the controller wants to change that too.
13672 - When we requested a pile of server descriptors, we sometimes
13673 accidentally launched a duplicate request for the first one.
13674 - Bugfix for trackhostexits: write down the fingerprint of the
13675 chosen exit, not its nickname, because the chosen exit might not
13677 - When parsing foo.exit, if foo is unknown, and we are leaving
13678 circuits unattached, set the chosen_exit field and leave the
13679 address empty. This matters because controllers got confused
13681 - Directory authorities no longer try to download server
13682 descriptors that they know they will reject.
13684 o Features and updates:
13685 - Replace balanced trees with hash tables: this should make stuff
13686 significantly faster.
13687 - Resume using the AES counter-mode implementation that we ship,
13688 rather than OpenSSL's. Ours is significantly faster.
13689 - Many other CPU and memory improvements.
13690 - Add a new config option FastFirstHopPK (on by default) so clients
13691 do a trivial crypto handshake for their first hop, since TLS has
13692 already taken care of confidentiality and authentication.
13693 - Add a new config option TestSocks so people can see if their
13694 applications are using socks4, socks4a, socks5-with-ip, or
13695 socks5-with-hostname. This way they don't have to keep mucking
13696 with tcpdump and wondering if something got cached somewhere.
13697 - Warn when listening on a public address for socks. I suspect a
13698 lot of people are setting themselves up as open socks proxies,
13699 and they have no idea that jerks on the Internet are using them,
13700 since they simply proxy the traffic into the Tor network.
13701 - Add "private:*" as an alias in configuration for policies. Now
13702 you can simplify your exit policy rather than needing to list
13703 every single internal or nonroutable network space.
13704 - Add a new controller event type that allows controllers to get
13705 all server descriptors that were uploaded to a router in its role
13706 as authoritative dirserver.
13707 - Start shipping socks-extensions.txt, tor-doc-unix.html,
13708 tor-doc-server.html, and stylesheet.css in the tarball.
13709 - Stop shipping tor-doc.html in the tarball.
13712 Changes in version 0.1.1.9-alpha - 2005-11-15
13713 o Usability improvements:
13714 - Start calling it FooListenAddress rather than FooBindAddress,
13715 since few of our users know what it means to bind an address
13717 - Reduce clutter in server logs. We're going to try to make
13718 them actually usable now. New config option ProtocolWarnings that
13719 lets you hear about how _other Tors_ are breaking the protocol. Off
13721 - Divide log messages into logging domains. Once we put some sort
13722 of interface on this, it will let people looking at more verbose
13723 log levels specify the topics they want to hear more about.
13724 - Make directory servers return better http 404 error messages
13725 instead of a generic "Servers unavailable".
13726 - Check for even more Windows version flags when writing the platform
13727 string in server descriptors, and note any we don't recognize.
13728 - Clean up more of the OpenSSL memory when exiting, so we can detect
13729 memory leaks better.
13730 - Make directory authorities be non-versioning, non-naming by
13731 default. Now we can add new directory servers without requiring
13732 their operators to pay close attention.
13733 - When logging via syslog, include the pid whenever we provide
13734 a log entry. Suggested by Todd Fries.
13736 o Performance improvements:
13737 - Directory servers now silently throw away new descriptors that
13738 haven't changed much if the timestamps are similar. We do this to
13739 tolerate older Tor servers that upload a new descriptor every 15
13740 minutes. (It seemed like a good idea at the time.)
13741 - Inline bottleneck smartlist functions; use fast versions by default.
13742 - Add a "Map from digest to void*" abstraction digestmap_t so we
13743 can do less hex encoding/decoding. Use it in router_get_by_digest()
13744 to resolve a performance bottleneck.
13745 - Allow tor_gzip_uncompress to extract as much as possible from
13746 truncated compressed data. Try to extract as many
13747 descriptors as possible from truncated http responses (when
13748 DIR_PURPOSE_FETCH_ROUTERDESC).
13749 - Make circ->onionskin a pointer, not a static array. moria2 was using
13750 125000 circuit_t's after it had been up for a few weeks, which
13751 translates to 20+ megs of wasted space.
13752 - The private half of our EDH handshake keys are now chosen out
13753 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
13755 o Security improvements:
13756 - Start making directory caches retain old routerinfos, so soon
13757 clients can start asking by digest of descriptor rather than by
13758 fingerprint of server.
13759 - Add half our entropy from RAND_poll in OpenSSL. This knows how
13760 to use egd (if present), openbsd weirdness (if present), vms/os2
13761 weirdness (if we ever port there), and more in the future.
13763 o Bugfixes on 0.1.0.x:
13764 - Do round-robin writes of at most 16 kB per write. This might be
13765 more fair on loaded Tor servers, and it might resolve our Windows
13766 crash bug. It might also slow things down.
13767 - Our TLS handshakes were generating a single public/private
13768 keypair for the TLS context, rather than making a new one for
13769 each new connections. Oops. (But we were still rotating them
13770 periodically, so it's not so bad.)
13771 - When we were cannibalizing a circuit with a particular exit
13772 node in mind, we weren't checking to see if that exit node was
13773 already present earlier in the circuit. Oops.
13774 - When a Tor server's IP changes (e.g. from a dyndns address),
13775 upload a new descriptor so clients will learn too.
13776 - Really busy servers were keeping enough circuits open on stable
13777 connections that they were wrapping around the circuit_id
13778 space. (It's only two bytes.) This exposed a bug where we would
13779 feel free to reuse a circuit_id even if it still exists but has
13780 been marked for close. Try to fix this bug. Some bug remains.
13781 - If we would close a stream early (e.g. it asks for a .exit that
13782 we know would refuse it) but the LeaveStreamsUnattached config
13783 option is set by the controller, then don't close it.
13785 o Bugfixes on 0.1.1.8-alpha:
13786 - Fix a big pile of memory leaks, some of them serious.
13787 - Do not try to download a routerdesc if we would immediately reject
13789 - Resume inserting a newline between all router descriptors when
13790 generating (old style) signed directories, since our spec says
13792 - When providing content-type application/octet-stream for
13793 server descriptors using .z, we were leaving out the
13794 content-encoding header. Oops. (Everything tolerated this just
13795 fine, but that doesn't mean we need to be part of the problem.)
13796 - Fix a potential seg fault in getconf and getinfo using version 1
13797 of the controller protocol.
13798 - Avoid crash: do not check whether DirPort is reachable when we
13799 are suppressing it because of hibernation.
13800 - Make --hash-password not crash on exit.
13803 Changes in version 0.1.1.8-alpha - 2005-10-07
13804 o New features (major):
13805 - Clients don't download or use the directory anymore. Now they
13806 download and use network-statuses from the trusted dirservers,
13807 and fetch individual server descriptors as needed from mirrors.
13808 See dir-spec.txt for all the gory details.
13809 - Be more conservative about whether to advertise our DirPort.
13810 The main change is to not advertise if we're running at capacity
13811 and either a) we could hibernate or b) our capacity is low and
13812 we're using a default DirPort.
13813 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
13815 o New features (minor):
13816 - Try to be smart about when to retry network-status and
13817 server-descriptor fetches. Still needs some tuning.
13818 - Stop parsing, storing, or using running-routers output (but
13819 mirrors still cache and serve it).
13820 - Consider a threshold of versioning dirservers (dirservers who have
13821 an opinion about which Tor versions are still recommended) before
13822 deciding whether to warn the user that he's obsolete.
13823 - Dirservers can now reject/invalidate by key and IP, with the
13824 config options "AuthDirInvalid" and "AuthDirReject". This is
13825 useful since currently we automatically list servers as running
13826 and usable even if we know they're jerks.
13827 - Provide dire warnings to any users who set DirServer; move it out
13828 of torrc.sample and into torrc.complete.
13829 - Add MyFamily to torrc.sample in the server section.
13830 - Add nicknames to the DirServer line, so we can refer to them
13831 without requiring all our users to memorize their IP addresses.
13832 - When we get an EOF or a timeout on a directory connection, note
13833 how many bytes of serverdesc we are dropping. This will help
13834 us determine whether it is smart to parse incomplete serverdesc
13836 - Add a new function to "change pseudonyms" -- that is, to stop
13837 using any currently-dirty circuits for new streams, so we don't
13838 link new actions to old actions. Currently it's only called on
13839 HUP (or SIGNAL RELOAD).
13840 - On sighup, if UseHelperNodes changed to 1, use new circuits.
13841 - Start using RAND_bytes rather than RAND_pseudo_bytes from
13842 OpenSSL. Also, reseed our entropy every hour, not just at
13843 startup. And entropy in 512-bit chunks, not 160-bit chunks.
13845 o Fixes on 0.1.1.7-alpha:
13846 - Nobody ever implemented EVENT_ADDRMAP for control protocol
13847 version 0, so don't let version 0 controllers ask for it.
13848 - If you requested something with too many newlines via the
13849 v1 controller protocol, you could crash tor.
13850 - Fix a number of memory leaks, including some pretty serious ones.
13851 - Re-enable DirPort testing again, so Tor servers will be willing
13852 to advertise their DirPort if it's reachable.
13853 - On TLS handshake, only check the other router's nickname against
13854 its expected nickname if is_named is set.
13856 o Fixes forward-ported from 0.1.0.15:
13857 - Don't crash when we don't have any spare file descriptors and we
13858 try to spawn a dns or cpu worker.
13859 - Make the numbers in read-history and write-history into uint64s,
13860 so they don't overflow and publish negatives in the descriptor.
13862 o Fixes on 0.1.0.x:
13863 - For the OS X package's modified privoxy config file, comment
13864 out the "logfile" line so we don't log everything passed
13866 - We were whining about using socks4 or socks5-with-local-lookup
13867 even when it's an IP in the "virtual" range we designed exactly
13869 - We were leaking some memory every time the client changes IPs.
13870 - Never call free() on tor_malloc()d memory. This will help us
13871 use dmalloc to detect memory leaks.
13872 - Check for named servers when looking them up by nickname;
13873 warn when we'recalling a non-named server by its nickname;
13874 don't warn twice about the same name.
13875 - Try to list MyFamily elements by key, not by nickname, and warn
13876 if we've not heard of the server.
13877 - Make windows platform detection (uname equivalent) smarter.
13878 - It turns out sparc64 doesn't like unaligned access either.
13881 Changes in version 0.1.0.15 - 2005-09-23
13882 o Bugfixes on 0.1.0.x:
13883 - Reject ports 465 and 587 (spam targets) in default exit policy.
13884 - Don't crash when we don't have any spare file descriptors and we
13885 try to spawn a dns or cpu worker.
13886 - Get rid of IgnoreVersion undocumented config option, and make us
13887 only warn, never exit, when we're running an obsolete version.
13888 - Don't try to print a null string when your server finds itself to
13889 be unreachable and the Address config option is empty.
13890 - Make the numbers in read-history and write-history into uint64s,
13891 so they don't overflow and publish negatives in the descriptor.
13892 - Fix a minor memory leak in smartlist_string_remove().
13893 - We were only allowing ourselves to upload a server descriptor at
13894 most every 20 minutes, even if it changed earlier than that.
13895 - Clean up log entries that pointed to old URLs.
13898 Changes in version 0.1.1.7-alpha - 2005-09-14
13899 o Fixes on 0.1.1.6-alpha:
13900 - Exit servers were crashing when people asked them to make a
13901 connection to an address not in their exit policy.
13902 - Looking up a non-existent stream for a v1 control connection would
13904 - Fix a seg fault if we ask a dirserver for a descriptor by
13905 fingerprint but he doesn't know about him.
13906 - SETCONF was appending items to linelists, not clearing them.
13907 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
13908 out and refuse the setconf if it would fail.
13909 - Downgrade the dirserver log messages when whining about
13913 - Add Peter Palfrader's check-tor script to tor/contrib/
13914 It lets you easily check whether a given server (referenced by
13915 nickname) is reachable by you.
13916 - Numerous changes to move towards client-side v2 directories. Not
13919 o Fixes on 0.1.0.x:
13920 - If the user gave tor an odd number of command-line arguments,
13921 we were silently ignoring the last one. Now we complain and fail.
13922 [This wins the oldest-bug prize -- this bug has been present since
13923 November 2002, as released in Tor 0.0.0.]
13924 - Do not use unaligned memory access on alpha, mips, or mipsel.
13925 It *works*, but is very slow, so we treat them as if it doesn't.
13926 - Retry directory requests if we fail to get an answer we like
13927 from a given dirserver (we were retrying before, but only if
13928 we fail to connect).
13929 - When writing the RecommendedVersions line, sort them first.
13930 - When the client asked for a rendezvous port that the hidden
13931 service didn't want to provide, we were sending an IP address
13932 back along with the end cell. Fortunately, it was zero. But stop
13934 - Correct "your server is reachable" log entries to indicate that
13935 it was self-testing that told us so.
13938 Changes in version 0.1.1.6-alpha - 2005-09-09
13939 o Fixes on 0.1.1.5-alpha:
13940 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
13941 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
13942 - Fix bug with tor_memmem finding a match at the end of the string.
13943 - Make unit tests run without segfaulting.
13944 - Resolve some solaris x86 compile warnings.
13945 - Handle duplicate lines in approved-routers files without warning.
13946 - Fix bug where as soon as a server refused any requests due to his
13947 exit policy (e.g. when we ask for localhost and he tells us that's
13948 127.0.0.1 and he won't do it), we decided he wasn't obeying his
13949 exit policy using him for any exits.
13950 - Only do openssl hardware accelerator stuff if openssl version is
13953 o New controller features/fixes:
13954 - Add a "RESETCONF" command so you can set config options like
13955 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
13956 a config option in the torrc with no value, then it clears it
13957 entirely (rather than setting it to its default).
13958 - Add a "GETINFO config-file" to tell us where torrc is.
13959 - Avoid sending blank lines when GETINFO replies should be empty.
13960 - Add a QUIT command for the controller (for using it manually).
13961 - Fix a bug in SAVECONF that was adding default dirservers and
13962 other redundant entries to the torrc file.
13964 o Start on the new directory design:
13965 - Generate, publish, cache, serve new network-status format.
13966 - Publish individual descriptors (by fingerprint, by "all", and by
13968 - Publish client and server recommended versions separately.
13969 - Allow tor_gzip_uncompress() to handle multiple concatenated
13970 compressed strings. Serve compressed groups of router
13971 descriptors. The compression logic here could be more
13973 - Distinguish v1 authorities (all currently trusted directories)
13974 from v2 authorities (all trusted directories).
13975 - Change DirServers config line to note which dirs are v1 authorities.
13976 - Add configuration option "V1AuthoritativeDirectory 1" which
13977 moria1, moria2, and tor26 should set.
13978 - Remove option when getting directory cache to see whether they
13979 support running-routers; they all do now. Replace it with one
13980 to see whether caches support v2 stuff.
13983 - Dirservers now do their own external reachability testing of each
13984 Tor server, and only list them as running if they've been found to
13985 be reachable. We also send back warnings to the server's logs if
13986 it uploads a descriptor that we already believe is unreachable.
13987 - Implement exit enclaves: if we know an IP address for the
13988 destination, and there's a running Tor server at that address
13989 which allows exit to the destination, then extend the circuit to
13990 that exit first. This provides end-to-end encryption and end-to-end
13991 authentication. Also, if the user wants a .exit address or enclave,
13992 use 4 hops rather than 3, and cannibalize a general circ for it
13994 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
13995 controller. Also, rotate dns and cpu workers if the controller
13996 changes options that will affect them; and initialize the dns
13997 worker cache tree whether or not we start out as a server.
13998 - Only upload a new server descriptor when options change, 18
13999 hours have passed, uptime is reset, or bandwidth changes a lot.
14000 - Check [X-]Forwarded-For headers in HTTP requests when generating
14001 log messages. This lets people run dirservers (and caches) behind
14002 Apache but still know which IP addresses are causing warnings.
14004 o Config option changes:
14005 - Replace (Fascist)Firewall* config options with a new
14006 ReachableAddresses option that understands address policies.
14007 For example, "ReachableAddresses *:80,*:443"
14008 - Get rid of IgnoreVersion undocumented config option, and make us
14009 only warn, never exit, when we're running an obsolete version.
14010 - Make MonthlyAccountingStart config option truly obsolete now.
14012 o Fixes on 0.1.0.x:
14013 - Reject ports 465 and 587 in the default exit policy, since
14014 people have started using them for spam too.
14015 - It turns out we couldn't bootstrap a network since we added
14016 reachability detection in 0.1.0.1-rc. Good thing the Tor network
14017 has never gone down. Add an AssumeReachable config option to let
14018 servers and dirservers bootstrap. When we're trying to build a
14019 high-uptime or high-bandwidth circuit but there aren't enough
14020 suitable servers, try being less picky rather than simply failing.
14021 - Our logic to decide if the OR we connected to was the right guy
14022 was brittle and maybe open to a mitm for unverified routers.
14023 - We weren't cannibalizing circuits correctly for
14024 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
14025 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
14026 build those from scratch. This should make hidden services faster.
14027 - Predict required circuits better, with an eye toward making hidden
14028 services faster on the service end.
14029 - Retry streams if the exit node sends back a 'misc' failure. This
14030 should result in fewer random failures. Also, after failing
14031 from resolve failed or misc, reset the num failures, so we give
14032 it a fair shake next time we try.
14033 - Clean up the rendezvous warn log msgs, and downgrade some to info.
14034 - Reduce severity on logs about dns worker spawning and culling.
14035 - When we're shutting down and we do something like try to post a
14036 server descriptor or rendezvous descriptor, don't complain that
14037 we seem to be unreachable. Of course we are, we're shutting down.
14038 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
14039 We don't use them yet, but maybe one day our DNS resolver will be
14040 able to discover them.
14041 - Make ContactInfo mandatory for authoritative directory servers.
14042 - Require server descriptors to list IPv4 addresses -- hostnames
14043 are no longer allowed. This also fixes some potential security
14044 problems with people providing hostnames as their address and then
14045 preferentially resolving them to partition users.
14046 - Change log line for unreachability to explicitly suggest /etc/hosts
14047 as the culprit. Also make it clearer what IP address and ports we're
14048 testing for reachability.
14049 - Put quotes around user-supplied strings when logging so users are
14050 more likely to realize if they add bad characters (like quotes)
14052 - Let auth dir servers start without specifying an Address config
14054 - Make unit tests (and other invocations that aren't the real Tor)
14055 run without launching listeners, creating subdirectories, and so on.
14058 Changes in version 0.1.1.5-alpha - 2005-08-08
14059 o Bugfixes included in 0.1.0.14.
14061 o Bugfixes on 0.1.0.x:
14062 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
14063 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
14064 it would silently using ignore the 6668.
14067 Changes in version 0.1.0.14 - 2005-08-08
14068 o Bugfixes on 0.1.0.x:
14069 - Fix the other half of the bug with crypto handshakes
14071 - Fix an assert trigger if you send a 'signal term' via the
14072 controller when it's listening for 'event info' messages.
14075 Changes in version 0.1.1.4-alpha - 2005-08-04
14076 o Bugfixes included in 0.1.0.13.
14079 - Improve tor_gettimeofday() granularity on windows.
14080 - Make clients regenerate their keys when their IP address changes.
14081 - Implement some more GETINFO goodness: expose helper nodes, config
14082 options, getinfo keys.
14085 Changes in version 0.1.0.13 - 2005-08-04
14086 o Bugfixes on 0.1.0.x:
14087 - Fix a critical bug in the security of our crypto handshakes.
14088 - Fix a size_t underflow in smartlist_join_strings2() that made
14089 it do bad things when you hand it an empty smartlist.
14090 - Fix Windows installer to ship Tor license (thanks to Aphex for
14091 pointing out this oversight) and put a link to the doc directory
14093 - Explicitly set no-unaligned-access for sparc: it turns out the
14094 new gcc's let you compile broken code, but that doesn't make it
14098 Changes in version 0.1.1.3-alpha - 2005-07-23
14099 o Bugfixes on 0.1.1.2-alpha:
14100 - Fix a bug in handling the controller's "post descriptor"
14102 - Fix several bugs in handling the controller's "extend circuit"
14104 - Fix a bug in handling the controller's "stream status" event.
14105 - Fix an assert failure if we have a controller listening for
14106 circuit events and we go offline.
14107 - Re-allow hidden service descriptors to publish 0 intro points.
14108 - Fix a crash when generating your hidden service descriptor if
14109 you don't have enough intro points already.
14111 o New features on 0.1.1.2-alpha:
14112 - New controller function "getinfo accounting", to ask how
14113 many bytes we've used in this time period.
14114 - Experimental support for helper nodes: a lot of the risk from
14115 a small static adversary comes because users pick new random
14116 nodes every time they rebuild a circuit. Now users will try to
14117 stick to the same small set of entry nodes if they can. Not
14118 enabled by default yet.
14120 o Bugfixes on 0.1.0.12:
14121 - If you're an auth dir server, always publish your dirport,
14122 even if you haven't yet found yourself to be reachable.
14123 - Fix a size_t underflow in smartlist_join_strings2() that made
14124 it do bad things when you hand it an empty smartlist.
14127 Changes in version 0.1.0.12 - 2005-07-18
14128 o New directory servers:
14129 - tor26 has changed IP address.
14131 o Bugfixes on 0.1.0.x:
14132 - Fix a possible double-free in tor_gzip_uncompress().
14133 - When --disable-threads is set, do not search for or link against
14134 pthreads libraries.
14135 - Don't trigger an assert if an authoritative directory server
14136 claims its dirport is 0.
14137 - Fix bug with removing Tor as an NT service: some people were
14138 getting "The service did not return an error." Thanks to Matt
14142 Changes in version 0.1.1.2-alpha - 2005-07-15
14143 o New directory servers:
14144 - tor26 has changed IP address.
14146 o Bugfixes on 0.1.0.x, crashes/leaks:
14147 - Port the servers-not-obeying-their-exit-policies fix from
14149 - Fix an fd leak in start_daemon().
14150 - On Windows, you can't always reopen a port right after you've
14151 closed it. So change retry_listeners() to only close and re-open
14152 ports that have changed.
14153 - Fix a possible double-free in tor_gzip_uncompress().
14155 o Bugfixes on 0.1.0.x, usability:
14156 - When tor_socketpair() fails in Windows, give a reasonable
14157 Windows-style errno back.
14158 - Let people type "tor --install" as well as "tor -install" when
14160 want to make it an NT service.
14161 - NT service patch from Matt Edman to improve error messages.
14162 - When the controller asks for a config option with an abbreviated
14163 name, give the full name in our response.
14164 - Correct the man page entry on TrackHostExitsExpire.
14165 - Looks like we were never delivering deflated (i.e. compressed)
14166 running-routers lists, even when asked. Oops.
14167 - When --disable-threads is set, do not search for or link against
14168 pthreads libraries.
14170 o Bugfixes on 0.1.1.x:
14171 - Fix a seg fault with autodetecting which controller version is
14175 - New hidden service descriptor format: put a version in it, and
14176 let people specify introduction/rendezvous points that aren't
14177 in "the directory" (which is subjective anyway).
14178 - Allow the DEBUG controller event to work again. Mark certain log
14179 entries as "don't tell this to controllers", so we avoid cycles.
14182 Changes in version 0.1.0.11 - 2005-06-30
14183 o Bugfixes on 0.1.0.x:
14184 - Fix major security bug: servers were disregarding their
14185 exit policies if clients behaved unexpectedly.
14186 - Make OS X init script check for missing argument, so we don't
14187 confuse users who invoke it incorrectly.
14188 - Fix a seg fault in "tor --hash-password foo".
14189 - The MAPADDRESS control command was broken.
14192 Changes in version 0.1.1.1-alpha - 2005-06-29
14194 - Make OS X init script check for missing argument, so we don't
14195 confuse users who invoke it incorrectly.
14196 - Fix a seg fault in "tor --hash-password foo".
14197 - Fix a possible way to DoS dirservers.
14198 - When we complain that your exit policy implicitly allows local or
14199 private address spaces, name them explicitly so operators can
14201 - Make the log message less scary when all the dirservers are
14202 temporarily unreachable.
14203 - We were printing the number of idle dns workers incorrectly when
14207 - Revised controller protocol (version 1) that uses ascii rather
14208 than binary. Add supporting libraries in python and java so you
14209 can use the controller from your applications without caring how
14210 our protocol works.
14211 - Spiffy new support for crypto hardware accelerators. Can somebody
14215 Changes in version 0.0.9.10 - 2005-06-16
14216 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
14217 - Refuse relay cells that claim to have a length larger than the
14218 maximum allowed. This prevents a potential attack that could read
14219 arbitrary memory (e.g. keys) from an exit server's process
14223 Changes in version 0.1.0.10 - 2005-06-14
14224 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
14225 libevent before 1.1a.
14228 Changes in version 0.1.0.9-rc - 2005-06-09
14230 - Reset buf->highwater every time buf_shrink() is called, not just on
14231 a successful shrink. This was causing significant memory bloat.
14232 - Fix buffer overflow when checking hashed passwords.
14233 - Security fix: if seeding the RNG on Win32 fails, quit.
14234 - Allow seeding the RNG on Win32 even when you're not running as
14236 - Disable threading on Solaris too. Something is wonky with it,
14237 cpuworkers, and reentrant libs.
14238 - Reenable the part of the code that tries to flush as soon as an
14239 OR outbuf has a full TLS record available. Perhaps this will make
14240 OR outbufs not grow as huge except in rare cases, thus saving lots
14241 of CPU time plus memory.
14242 - Reject malformed .onion addresses rather then passing them on as
14243 normal web requests.
14244 - Adapt patch from Adam Langley: fix possible memory leak in
14245 tor_lookup_hostname().
14246 - Initialize libevent later in the startup process, so the logs are
14247 already established by the time we start logging libevent warns.
14248 - Use correct errno on win32 if libevent fails.
14249 - Check and warn about known-bad/slow libevent versions.
14250 - Pay more attention to the ClientOnly config option.
14251 - Have torctl.in/tor.sh.in check for location of su binary (needed
14253 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
14254 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
14255 HttpProxyAuthenticator
14256 - Stop warning about sigpipes in the logs. We're going to
14257 pretend that getting these occassionally is normal and fine.
14258 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
14260 installer screens; and don't put stuff into StartupItems unless
14261 the user asks you to.
14262 - Require servers that use the default dirservers to have public IP
14263 addresses. We have too many servers that are configured with private
14264 IPs and their admins never notice the log entries complaining that
14265 their descriptors are being rejected.
14266 - Add OSX uninstall instructions. An actual uninstall script will
14270 Changes in version 0.1.0.8-rc - 2005-05-23
14272 - It turns out that kqueue on OS X 10.3.9 was causing kernel
14273 panics. Disable kqueue on all OS X Tors.
14274 - Fix RPM: remove duplicate line accidentally added to the rpm
14276 - Disable threads on openbsd too, since its gethostaddr is not
14278 - Tolerate libevent 0.8 since it still works, even though it's
14280 - Enable building on Red Hat 9.0 again.
14281 - Allow the middle hop of the testing circuit to be running any
14282 version, now that most of them have the bugfix to let them connect
14283 to unknown servers. This will allow reachability testing to work
14284 even when 0.0.9.7-0.0.9.9 become obsolete.
14285 - Handle relay cells with rh.length too large. This prevents
14286 a potential attack that could read arbitrary memory (maybe even
14287 keys) from the exit server's process.
14288 - We screwed up the dirport reachability testing when we don't yet
14289 have a cached version of the directory. Hopefully now fixed.
14290 - Clean up router_load_single_router() (used by the controller),
14291 so it doesn't seg fault on error.
14292 - Fix a minor memory leak when somebody establishes an introduction
14293 point at your Tor server.
14294 - If a socks connection ends because read fails, don't warn that
14295 you're not sending a socks reply back.
14298 - Add HttpProxyAuthenticator config option too, that works like
14299 the HttpsProxyAuthenticator config option.
14300 - Encode hashed controller passwords in hex instead of base64,
14301 to make it easier to write controllers.
14304 Changes in version 0.1.0.7-rc - 2005-05-17
14306 - Fix a bug in the OS X package installer that prevented it from
14307 installing on Tiger.
14308 - Fix a script bug in the OS X package installer that made it
14309 complain during installation.
14310 - Find libevent even if it's hiding in /usr/local/ and your
14311 CFLAGS and LDFLAGS don't tell you to look there.
14312 - Be able to link with libevent as a shared library (the default
14313 after 1.0d), even if it's hiding in /usr/local/lib and even
14314 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
14315 assuming you're running gcc. Otherwise fail and give a useful
14317 - Fix a bug in the RPM packager: set home directory for _tor to
14318 something more reasonable when first installing.
14319 - Free a minor amount of memory that is still reachable on exit.
14322 Changes in version 0.1.0.6-rc - 2005-05-14
14324 - Implement --disable-threads configure option. Disable threads on
14325 netbsd by default, because it appears to have no reentrant resolver
14327 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
14328 release (1.1) detects and disables kqueue if it's broken.
14329 - Append default exit policy before checking for implicit internal
14330 addresses. Now we don't log a bunch of complaints on startup
14331 when using the default exit policy.
14332 - Some people were putting "Address " in their torrc, and they had
14333 a buggy resolver that resolved " " to 0.0.0.0. Oops.
14334 - If DataDir is ~/.tor, and that expands to /.tor, then default to
14335 LOCALSTATEDIR/tor instead.
14336 - Fix fragmented-message bug in TorControl.py.
14337 - Resolve a minor bug which would prevent unreachable dirports
14338 from getting suppressed in the published descriptor.
14339 - When the controller gave us a new descriptor, we weren't resolving
14340 it immediately, so Tor would think its address was 0.0.0.0 until
14341 we fetched a new directory.
14342 - Fix an uppercase/lowercase case error in suppressing a bogus
14343 libevent warning on some Linuxes.
14346 - Begin scrubbing sensitive strings from logs by default. Turn off
14347 the config option SafeLogging if you need to do debugging.
14348 - Switch to a new buffer management algorithm, which tries to avoid
14349 reallocing and copying quite as much. In first tests it looks like
14350 it uses *more* memory on average, but less cpu.
14351 - First cut at support for "create-fast" cells. Clients can use
14352 these when extending to their first hop, since the TLS already
14353 provides forward secrecy and authentication. Not enabled on
14355 - When dirservers refuse a router descriptor, we now log its
14356 contactinfo, platform, and the poster's IP address.
14357 - Call tor_free_all instead of connections_free_all after forking, to
14358 save memory on systems that need to fork.
14359 - Whine at you if you're a server and you don't set your contactinfo.
14360 - Implement --verify-config command-line option to check if your torrc
14361 is valid without actually launching Tor.
14362 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
14363 rather than just rejecting it.
14366 Changes in version 0.1.0.5-rc - 2005-04-27
14368 - Stop trying to print a null pointer if an OR conn fails because
14369 we didn't like its cert.
14371 - Switch our internal buffers implementation to use a ring buffer,
14372 to hopefully improve performance for fast servers a lot.
14373 - Add HttpsProxyAuthenticator support (basic auth only), based
14374 on patch from Adam Langley.
14375 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
14376 the fast servers that have been joining lately.
14377 - Give hidden service accesses extra time on the first attempt,
14378 since 60 seconds is often only barely enough. This might improve
14380 - Improve performance for dirservers: stop re-parsing the whole
14381 directory every time you regenerate it.
14382 - Add more debugging info to help us find the weird dns freebsd
14383 pthreads bug; cleaner debug messages to help track future issues.
14386 Changes in version 0.0.9.9 - 2005-04-23
14387 o Bugfixes on 0.0.9.x:
14388 - If unofficial Tor clients connect and send weird TLS certs, our
14389 Tor server triggers an assert. This release contains a minimal
14390 backport from the broader fix that we put into 0.1.0.4-rc.
14393 Changes in version 0.1.0.4-rc - 2005-04-23
14395 - If unofficial Tor clients connect and send weird TLS certs, our
14396 Tor server triggers an assert. Stop asserting, and start handling
14397 TLS errors better in other situations too.
14398 - When the controller asks us to tell it about all the debug-level
14399 logs, it turns out we were generating debug-level logs while
14400 telling it about them, which turns into a bad loop. Now keep
14401 track of whether you're sending a debug log to the controller,
14402 and don't log when you are.
14403 - Fix the "postdescriptor" feature of the controller interface: on
14404 non-complete success, only say "done" once.
14406 - Clients are now willing to load balance over up to 2mB, not 1mB,
14407 of advertised bandwidth capacity.
14408 - Add a NoPublish config option, so you can be a server (e.g. for
14409 testing running Tor servers in other Tor networks) without
14410 publishing your descriptor to the primary dirservers.
14413 Changes in version 0.1.0.3-rc - 2005-04-08
14414 o Improvements on 0.1.0.2-rc:
14415 - Client now retries when streams end early for 'hibernating' or
14416 'resource limit' reasons, rather than failing them.
14417 - More automated handling for dirserver operators:
14418 - Automatically approve nodes running 0.1.0.2-rc or later,
14419 now that the the reachability detection stuff is working.
14420 - Now we allow two unverified servers with the same nickname
14421 but different keys. But if a nickname is verified, only that
14422 nickname+key are allowed.
14423 - If you're an authdirserver connecting to an address:port,
14424 and it's not the OR you were expecting, forget about that
14425 descriptor. If he *was* the one you were expecting, then forget
14426 about all other descriptors for that address:port.
14427 - Allow servers to publish descriptors from 12 hours in the future.
14428 Corollary: only whine about clock skew from the dirserver if
14429 he's a trusted dirserver (since now even verified servers could
14430 have quite wrong clocks).
14431 - Adjust maximum skew and age for rendezvous descriptors: let skew
14432 be 48 hours rather than 90 minutes.
14433 - Efficiency improvements:
14434 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
14435 it much faster to look up a circuit for each relay cell.
14436 - Remove most calls to assert_all_pending_dns_resolves_ok(),
14437 since they're eating our cpu on exit nodes.
14438 - Stop wasting time doing a case insensitive comparison for every
14439 dns name every time we do any lookup. Canonicalize the names to
14440 lowercase and be done with it.
14441 - Start sending 'truncated' cells back rather than destroy cells,
14442 if the circuit closes in front of you. This means we won't have
14443 to abandon partially built circuits.
14444 - Only warn once per nickname from add_nickname_list_to_smartlist
14445 per failure, so an entrynode or exitnode choice that's down won't
14447 - Put a note in the torrc about abuse potential with the default
14449 - Revise control spec and implementation to allow all log messages to
14450 be sent to controller with their severities intact (suggested by
14451 Matt Edman). Update TorControl to handle new log event types.
14452 - Provide better explanation messages when controller's POSTDESCRIPTOR
14454 - Stop putting nodename in the Platform string in server descriptors.
14455 It doesn't actually help, and it is confusing/upsetting some people.
14457 o Bugfixes on 0.1.0.2-rc:
14458 - We were printing the host mask wrong in exit policies in server
14459 descriptors. This isn't a critical bug though, since we were still
14460 obeying the exit policy internally.
14461 - Fix Tor when compiled with libevent but without pthreads: move
14462 connection_unregister() from _connection_free() to
14464 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
14465 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
14466 when we look through the connection array, we'll find any of the
14467 cpu/dnsworkers. This is no good.
14469 o Bugfixes on 0.0.9.8:
14470 - Fix possible bug on threading platforms (e.g. win32) which was
14471 leaking a file descriptor whenever a cpuworker or dnsworker died.
14472 - When using preferred entry or exit nodes, ignore whether the
14473 circuit wants uptime or capacity. They asked for the nodes, they
14475 - chdir() to your datadirectory at the *end* of the daemonize process,
14476 not the beginning. This was a problem because the first time you
14477 run tor, if your datadir isn't there, and you have runasdaemon set
14478 to 1, it will try to chdir to it before it tries to create it. Oops.
14479 - Handle changed router status correctly when dirserver reloads
14480 fingerprint file. We used to be dropping all unverified descriptors
14481 right then. The bug was hidden because we would immediately
14482 fetch a directory from another dirserver, which would include the
14483 descriptors we just dropped.
14484 - When we're connecting to an OR and he's got a different nickname/key
14485 than we were expecting, only complain loudly if we're an OP or a
14486 dirserver. Complaining loudly to the OR admins just confuses them.
14487 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
14488 artificially capped at 500kB.
14491 Changes in version 0.0.9.8 - 2005-04-07
14492 o Bugfixes on 0.0.9.x:
14493 - We have a bug that I haven't found yet. Sometimes, very rarely,
14494 cpuworkers get stuck in the 'busy' state, even though the cpuworker
14495 thinks of itself as idle. This meant that no new circuits ever got
14496 established. Here's a workaround to kill any cpuworker that's been
14497 busy for more than 100 seconds.
14500 Changes in version 0.1.0.2-rc - 2005-04-01
14501 o Bugfixes on 0.1.0.1-rc:
14502 - Fixes on reachability detection:
14503 - Don't check for reachability while hibernating.
14504 - If ORPort is reachable but DirPort isn't, still publish the
14505 descriptor, but zero out DirPort until it's found reachable.
14506 - When building testing circs for ORPort testing, use only
14507 high-bandwidth nodes, so fewer circuits fail.
14508 - Complain about unreachable ORPort separately from unreachable
14509 DirPort, so the user knows what's going on.
14510 - Make sure we only conclude ORPort reachability if we didn't
14511 initiate the conn. Otherwise we could falsely conclude that
14512 we're reachable just because we connected to the guy earlier
14513 and he used that same pipe to extend to us.
14514 - Authdirservers shouldn't do ORPort reachability detection,
14515 since they're in clique mode, so it will be rare to find a
14516 server not already connected to them.
14517 - When building testing circuits, always pick middle hops running
14518 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
14519 bug. (This is a kludge; it will go away when 0.0.9.x becomes
14521 - When we decide we're reachable, actually publish our descriptor
14523 - Fix bug in redirectstream in the controller.
14524 - Fix the state descriptor strings so logs don't claim edge streams
14525 are in a different state than they actually are.
14526 - Use recent libevent features when possible (this only really affects
14527 win32 and osx right now, because the new libevent with these
14528 features hasn't been released yet). Add code to suppress spurious
14530 - Prevent possible segfault in connection_close_unattached_ap().
14531 - Fix newlines on torrc in win32.
14532 - Improve error msgs when tor-resolve fails.
14534 o Improvements on 0.0.9.x:
14535 - New experimental script tor/contrib/ExerciseServer.py (needs more
14536 work) that uses the controller interface to build circuits and
14537 fetch pages over them. This will help us bootstrap servers that
14538 have lots of capacity but haven't noticed it yet.
14539 - New experimental script tor/contrib/PathDemo.py (needs more work)
14540 that uses the controller interface to let you choose whole paths
14542 "<hostname>.<path,separated by dots>.<length of path>.path"
14543 - When we've connected to an OR and handshaked but didn't like
14544 the result, we were closing the conn without sending destroy
14545 cells back for pending circuits. Now send those destroys.
14548 Changes in version 0.0.9.7 - 2005-04-01
14549 o Bugfixes on 0.0.9.x:
14550 - Fix another race crash bug (thanks to Glenn Fink for reporting).
14551 - Compare identity to identity, not to nickname, when extending to
14552 a router not already in the directory. This was preventing us from
14553 extending to unknown routers. Oops.
14554 - Make sure to create OS X Tor user in <500 range, so we aren't
14555 creating actual system users.
14556 - Note where connection-that-hasn't-sent-end was marked, and fix
14557 a few really loud instances of this harmless bug (it's fixed more
14561 Changes in version 0.1.0.1-rc - 2005-03-28
14563 - Add reachability testing. Your Tor server will automatically try
14564 to see if its ORPort and DirPort are reachable from the outside,
14565 and it won't upload its descriptor until it decides they are.
14566 - Handle unavailable hidden services better. Handle slow or busy
14567 hidden services better.
14568 - Add support for CONNECTing through https proxies, with "HttpsProxy"
14570 - New exit policy: accept most low-numbered ports, rather than
14571 rejecting most low-numbered ports.
14572 - More Tor controller support (still experimental). See
14573 http://tor.eff.org/doc/control-spec.txt for all the new features,
14574 including signals to emulate unix signals from any platform;
14575 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
14576 closestream; closecircuit; etc.
14577 - Make nt services work and start on startup on win32 (based on
14578 patch by Matt Edman).
14579 - Add a new AddressMap config directive to rewrite incoming socks
14580 addresses. This lets you, for example, declare an implicit
14581 required exit node for certain sites.
14582 - Add a new TrackHostExits config directive to trigger addressmaps
14583 for certain incoming socks addresses -- for sites that break when
14584 your exit keeps changing (based on patch by Mike Perry).
14585 - Redo the client-side dns cache so it's just an addressmap too.
14586 - Notice when our IP changes, and reset stats/uptime/reachability.
14587 - When an application is using socks5, give him the whole variety of
14588 potential socks5 responses (connect refused, host unreachable, etc),
14589 rather than just "success" or "failure".
14590 - A more sane version numbering system. See
14591 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
14592 - New contributed script "exitlist": a simple python script to
14593 parse directories and find Tor nodes that exit to listed
14595 - New contributed script "privoxy-tor-toggle" to toggle whether
14596 Privoxy uses Tor. Seems to be configured for Debian by default.
14597 - Report HTTP reasons to client when getting a response from directory
14598 servers -- so you can actually know what went wrong.
14599 - New config option MaxAdvertisedBandwidth which lets you advertise
14600 a low bandwidthrate (to not attract as many circuits) while still
14601 allowing a higher bandwidthrate in reality.
14603 o Robustness/stability fixes:
14604 - Make Tor use Niels Provos's libevent instead of its current
14605 poll-but-sometimes-select mess. This will let us use faster async
14606 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
14608 - pthread support now too. This was forced because when we forked,
14609 we ended up wasting a lot of duplicate ram over time. Also switch
14610 to foo_r versions of some library calls to allow reentry and
14612 - Better handling for heterogeneous / unreliable nodes:
14613 - Annotate circuits w/ whether they aim to contain high uptime nodes
14614 and/or high capacity nodes. When building circuits, choose
14616 - This means that every single node in an intro rend circuit,
14617 not just the last one, will have a minimum uptime.
14618 - New config option LongLivedPorts to indicate application streams
14619 that will want high uptime circuits.
14620 - Servers reset uptime when a dir fetch entirely fails. This
14621 hopefully reflects stability of the server's network connectivity.
14622 - If somebody starts his tor server in Jan 2004 and then fixes his
14623 clock, don't make his published uptime be a year.
14624 - Reset published uptime when you wake up from hibernation.
14625 - Introduce a notion of 'internal' circs, which are chosen without
14626 regard to the exit policy of the last hop. Intro and rendezvous
14627 circs must be internal circs, to avoid leaking information. Resolve
14628 and connect streams can use internal circs if they want.
14629 - New circuit pooling algorithm: make sure to have enough circs around
14630 to satisfy any predicted ports, and also make sure to have 2 internal
14631 circs around if we've required internal circs lately (and with high
14632 uptime if we've seen that lately too).
14633 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
14634 which describes how often we retry making new circuits if current
14635 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
14636 how long we're willing to make use of an already-dirty circuit.
14637 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
14638 circ as necessary, if there are any completed ones lying around
14639 when we try to launch one.
14640 - Make hidden services try to establish a rendezvous for 30 seconds,
14641 rather than for n (where n=3) attempts to build a circuit.
14642 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
14643 "ShutdownWaitLength".
14644 - Try to be more zealous about calling connection_edge_end when
14645 things go bad with edge conns in connection.c.
14646 - Revise tor-spec to add more/better stream end reasons.
14647 - Revise all calls to connection_edge_end to avoid sending "misc",
14648 and to take errno into account where possible.
14651 - Fix a race condition that can trigger an assert, when we have a
14652 pending create cell and an OR connection fails right then.
14653 - Fix several double-mark-for-close bugs, e.g. where we were finding
14654 a conn for a cell even if that conn is already marked for close.
14655 - Make sequence of log messages when starting on win32 with no config
14656 file more reasonable.
14657 - When choosing an exit node for a new non-internal circ, don't take
14658 into account whether it'll be useful for any pending x.onion
14659 addresses -- it won't.
14660 - Turn addr_policy_compare from a tristate to a quadstate; this should
14661 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
14662 for google.com" problem.
14663 - Make "platform" string in descriptor more accurate for Win32 servers,
14664 so it's not just "unknown platform".
14665 - Fix an edge case in parsing config options (thanks weasel).
14666 If they say "--" on the commandline, it's not an option.
14667 - Reject odd-looking addresses at the client (e.g. addresses that
14668 contain a colon), rather than having the server drop them because
14670 - tor-resolve requests were ignoring .exit if there was a working circuit
14671 they could use instead.
14672 - REUSEADDR on normal platforms means you can rebind to the port
14673 right after somebody else has let it go. But REUSEADDR on win32
14674 means to let you bind to the port _even when somebody else
14675 already has it bound_! So, don't do that on Win32.
14676 - Change version parsing logic: a version is "obsolete" if it is not
14677 recommended and (1) there is a newer recommended version in the
14678 same series, or (2) there are no recommended versions in the same
14679 series, but there are some recommended versions in a newer series.
14680 A version is "new" if it is newer than any recommended version in
14682 - Stop most cases of hanging up on a socks connection without sending
14686 - Require BandwidthRate to be at least 20kB/s for servers.
14687 - When a dirserver causes you to give a warn, mention which dirserver
14689 - New config option DirAllowPrivateAddresses for authdirservers.
14690 Now by default they refuse router descriptors that have non-IP or
14691 private-IP addresses.
14692 - Stop publishing socksport in the directory, since it's not
14693 actually meant to be public. For compatibility, publish a 0 there
14695 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
14696 smart" value, that is low for servers and high for clients.
14697 - If our clock jumps forward by 100 seconds or more, assume something
14698 has gone wrong with our network and abandon all not-yet-used circs.
14699 - Warn when exit policy implicitly allows local addresses.
14700 - If we get an incredibly skewed timestamp from a dirserver mirror
14701 that isn't a verified OR, don't warn -- it's probably him that's
14703 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
14704 cookies to disk and doesn't log each web request to disk. (Thanks
14705 to Brett Carrington for pointing this out.)
14706 - When a client asks us for a dir mirror and we don't have one,
14707 launch an attempt to get a fresh one.
14708 - If we're hibernating and we get a SIGINT, exit immediately.
14709 - Add --with-dmalloc ./configure option, to track memory leaks.
14710 - And try to free all memory on closing, so we can detect what
14712 - Cache local dns resolves correctly even when they're .exit
14714 - Give a better warning when some other server advertises an
14715 ORPort that is actually an apache running ssl.
14716 - Add "opt hibernating 1" to server descriptor to make it clearer
14717 whether the server is hibernating.
14720 Changes in version 0.0.9.6 - 2005-03-24
14721 o Bugfixes on 0.0.9.x (crashes and asserts):
14722 - Add new end stream reasons to maintainance branch. Fix bug where
14723 reason (8) could trigger an assert. Prevent bug from recurring.
14724 - Apparently win32 stat wants paths to not end with a slash.
14725 - Fix assert triggers in assert_cpath_layer_ok(), where we were
14726 blowing away the circuit that conn->cpath_layer points to, then
14727 checking to see if the circ is well-formed. Backport check to make
14728 sure we dont use the cpath on a closed connection.
14729 - Prevent circuit_resume_edge_reading_helper() from trying to package
14730 inbufs for marked-for-close streams.
14731 - Don't crash on hup if your options->address has become unresolvable.
14732 - Some systems (like OS X) sometimes accept() a connection and tell
14733 you the remote host is 0.0.0.0:0. If this happens, due to some
14734 other mis-features, we get confused; so refuse the conn for now.
14736 o Bugfixes on 0.0.9.x (other):
14737 - Fix harmless but scary "Unrecognized content encoding" warn message.
14738 - Add new stream error reason: TORPROTOCOL reason means "you are not
14739 speaking a version of Tor I understand; say bye-bye to your stream."
14740 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
14741 into the future, now that we are more tolerant of skew. This
14742 resolves a bug where a Tor server would refuse to cache a directory
14743 because all the directories it gets are too far in the future;
14744 yet the Tor server never logs any complaints about clock skew.
14745 - Mac packaging magic: make man pages useable, and do not overwrite
14746 existing torrc files.
14747 - Make OS X log happily to /var/log/tor/tor.log
14750 Changes in version 0.0.9.5 - 2005-02-22
14751 o Bugfixes on 0.0.9.x:
14752 - Fix an assert race at exit nodes when resolve requests fail.
14753 - Stop picking unverified dir mirrors--it only leads to misery.
14754 - Patch from Matt Edman to make NT services work better. Service
14755 support is still not compiled into the executable by default.
14756 - Patch from Dmitri Bely so the Tor service runs better under
14757 the win32 SYSTEM account.
14758 - Make tor-resolve actually work (?) on Win32.
14759 - Fix a sign bug when getrlimit claims to have 4+ billion
14760 file descriptors available.
14761 - Stop refusing to start when bandwidthburst == bandwidthrate.
14762 - When create cells have been on the onion queue more than five
14763 seconds, just send back a destroy and take them off the list.
14766 Changes in version 0.0.9.4 - 2005-02-03
14767 o Bugfixes on 0.0.9:
14768 - Fix an assert bug that took down most of our servers: when
14769 a server claims to have 1 GB of bandwidthburst, don't
14771 - Don't crash as badly if we have spawned the max allowed number
14772 of dnsworkers, or we're out of file descriptors.
14773 - Block more file-sharing ports in the default exit policy.
14774 - MaxConn is now automatically set to the hard limit of max
14775 file descriptors we're allowed (ulimit -n), minus a few for
14777 - Give a clearer message when servers need to raise their
14778 ulimit -n when they start running out of file descriptors.
14779 - SGI Compatibility patches from Jan Schaumann.
14780 - Tolerate a corrupt cached directory better.
14781 - When a dirserver hasn't approved your server, list which one.
14782 - Go into soft hibernation after 95% of the bandwidth is used,
14783 not 99%. This is especially important for daily hibernators who
14784 have a small accounting max. Hopefully it will result in fewer
14785 cut connections when the hard hibernation starts.
14786 - Load-balance better when using servers that claim more than
14787 800kB/s of capacity.
14788 - Make NT services work (experimental, only used if compiled in).
14791 Changes in version 0.0.9.3 - 2005-01-21
14792 o Bugfixes on 0.0.9:
14793 - Backport the cpu use fixes from main branch, so busy servers won't
14794 need as much processor time.
14795 - Work better when we go offline and then come back, or when we
14796 run Tor at boot before the network is up. We do this by
14797 optimistically trying to fetch a new directory whenever an
14798 application request comes in and we think we're offline -- the
14799 human is hopefully a good measure of when the network is back.
14800 - Backport some minimal hidserv bugfixes: keep rend circuits open as
14801 long as you keep using them; actually publish hidserv descriptors
14802 shortly after they change, rather than waiting 20-40 minutes.
14803 - Enable Mac startup script by default.
14804 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
14805 - When you update AllowUnverifiedNodes or FirewallPorts via the
14806 controller's setconf feature, we were always appending, never
14808 - When you update HiddenServiceDir via setconf, it was screwing up
14809 the order of reading the lines, making it fail.
14810 - Do not rewrite a cached directory back to the cache; otherwise we
14811 will think it is recent and not fetch a newer one on startup.
14812 - Workaround for webservers that lie about Content-Encoding: Tor
14813 now tries to autodetect compressed directories and compression
14814 itself. This lets us Proxypass dir fetches through apache.
14817 Changes in version 0.0.9.2 - 2005-01-04
14818 o Bugfixes on 0.0.9 (crashes and asserts):
14819 - Fix an assert on startup when the disk is full and you're logging
14821 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
14822 style address, then we'd crash.
14823 - Fix an assert trigger when the running-routers string we get from
14824 a dirserver is broken.
14825 - Make worker threads start and run on win32. Now win32 servers
14827 - Bandaid (not actually fix, but now it doesn't crash) an assert
14828 where the dns worker dies mysteriously and the main Tor process
14829 doesn't remember anything about the address it was resolving.
14831 o Bugfixes on 0.0.9 (Win32):
14832 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
14833 name out of the warning/assert messages.
14834 - Fix a superficial "unhandled error on read" bug on win32.
14835 - The win32 installer no longer requires a click-through for our
14836 license, since our Free Software license grants rights but does not
14838 - Win32: When connecting to a dirserver fails, try another one
14839 immediately. (This was already working for non-win32 Tors.)
14840 - Stop trying to parse $HOME on win32 when hunting for default
14842 - Make tor-resolve.c work on win32 by calling network_init().
14844 o Bugfixes on 0.0.9 (other):
14845 - Make 0.0.9.x build on Solaris again.
14846 - Due to a fencepost error, we were blowing away the \n when reporting
14847 confvalue items in the controller. So asking for multiple config
14848 values at once couldn't work.
14849 - When listing circuits that are pending on an opening OR connection,
14850 if we're an OR we were listing circuits that *end* at us as
14851 being pending on every listener, dns/cpu worker, etc. Stop that.
14852 - Dirservers were failing to create 'running-routers' or 'directory'
14853 strings if we had more than some threshold of routers. Fix them so
14854 they can handle any number of routers.
14855 - Fix a superficial "Duplicate mark for close" bug.
14856 - Stop checking for clock skew for OR connections, even for servers.
14857 - Fix a fencepost error that was chopping off the last letter of any
14858 nickname that is the maximum allowed nickname length.
14859 - Update URLs in log messages so they point to the new website.
14860 - Fix a potential problem in mangling server private keys while
14861 writing to disk (not triggered yet, as far as we know).
14862 - Include the licenses for other free software we include in Tor,
14863 now that we're shipping binary distributions more regularly.
14866 Changes in version 0.0.9.1 - 2004-12-15
14867 o Bugfixes on 0.0.9:
14868 - Make hibernation actually work.
14869 - Make HashedControlPassword config option work.
14870 - When we're reporting event circuit status to a controller,
14871 don't use the stream status code.
14874 Changes in version 0.0.9 - 2004-12-12
14876 - Clean up manpage and torrc.sample file.
14877 - Clean up severities and text of log warnings.
14879 - Make servers trigger an assert when they enter hibernation.
14882 Changes in version 0.0.9rc7 - 2004-12-08
14883 o Bugfixes on 0.0.9rc:
14884 - Fix a stack-trashing crash when an exit node begins hibernating.
14885 - Avoid looking at unallocated memory while considering which
14886 ports we need to build circuits to cover.
14887 - Stop a sigpipe: when an 'end' cell races with eof from the app,
14888 we shouldn't hold-open-until-flush if the eof arrived first.
14889 - Fix a bug with init_cookie_authentication() in the controller.
14890 - When recommending new-format log lines, if the upper bound is
14891 LOG_ERR, leave it implicit.
14893 o Bugfixes on 0.0.8.1:
14894 - Fix a whole slew of memory leaks.
14895 - Fix isspace() and friends so they still make Solaris happy
14896 but also so they don't trigger asserts on win32.
14897 - Fix parse_iso_time on platforms without strptime (eg win32).
14898 - win32: tolerate extra "readable" events better.
14899 - win32: when being multithreaded, leave parent fdarray open.
14900 - Make unit tests work on win32.
14903 Changes in version 0.0.9rc6 - 2004-12-06
14904 o Bugfixes on 0.0.9pre:
14905 - Clean up some more integer underflow opportunities (not exploitable
14907 - While hibernating, hup should not regrow our listeners.
14908 - Send an end to the streams we close when we hibernate, rather
14909 than just chopping them off.
14910 - React to eof immediately on non-open edge connections.
14912 o Bugfixes on 0.0.8.1:
14913 - Calculate timeout for waiting for a connected cell from the time
14914 we sent the begin cell, not from the time the stream started. If
14915 it took a long time to establish the circuit, we would time out
14916 right after sending the begin cell.
14917 - Fix router_compare_addr_to_addr_policy: it was not treating a port
14918 of * as always matching, so we were picking reject *:* nodes as
14919 exit nodes too. Oops.
14922 - New circuit building strategy: keep a list of ports that we've
14923 used in the past 6 hours, and always try to have 2 circuits open
14924 or on the way that will handle each such port. Seed us with port
14925 80 so web users won't complain that Tor is "slow to start up".
14926 - Make kill -USR1 dump more useful stats about circuits.
14927 - When warning about retrying or giving up, print the address, so
14928 the user knows which one it's talking about.
14929 - If you haven't used a clean circuit in an hour, throw it away,
14930 just to be on the safe side. (This means after 6 hours a totally
14931 unused Tor client will have no circuits open.)
14934 Changes in version 0.0.9rc5 - 2004-12-01
14935 o Bugfixes on 0.0.8.1:
14936 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
14937 - Let resolve conns retry/expire also, rather than sticking around
14939 - If we are using select, make sure we stay within FD_SETSIZE.
14941 o Bugfixes on 0.0.9pre:
14942 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
14943 but doesn't seem to be currently; thanks to Ilja van Sprundel for
14945 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
14946 instead. Impose minima and maxima for all *Period options; impose
14947 even tighter maxima for fetching if we are a caching dirserver.
14948 Clip rather than rejecting.
14949 - Fetch cached running-routers from servers that serve it (that is,
14950 authdirservers and servers running 0.0.9rc5-cvs or later.)
14953 - Accept *:706 (silc) in default exit policy.
14954 - Implement new versioning format for post 0.1.
14955 - Support "foo.nickname.exit" addresses, to let Alice request the
14956 address "foo" as viewed by exit node "nickname". Based on a patch
14958 - Make tor --version --version dump the cvs Id of every file.
14961 Changes in version 0.0.9rc4 - 2004-11-28
14962 o Bugfixes on 0.0.8.1:
14963 - Make windows sockets actually non-blocking (oops), and handle
14964 win32 socket errors better.
14966 o Bugfixes on 0.0.9rc1:
14967 - Actually catch the -USR2 signal.
14970 Changes in version 0.0.9rc3 - 2004-11-25
14971 o Bugfixes on 0.0.8.1:
14972 - Flush the log file descriptor after we print "Tor opening log file",
14973 so we don't see those messages days later.
14975 o Bugfixes on 0.0.9rc1:
14976 - Make tor-resolve work again.
14977 - Avoid infinite loop in tor-resolve if tor hangs up on it.
14978 - Fix an assert trigger for clients/servers handling resolves.
14981 Changes in version 0.0.9rc2 - 2004-11-24
14982 o Bugfixes on 0.0.9rc1:
14983 - I broke socks5 support while fixing the eof bug.
14984 - Allow unitless bandwidths and intervals; they default to bytes
14986 - New servers don't start out hibernating; they are active until
14987 they run out of bytes, so they have a better estimate of how
14988 long it takes, and so their operators can know they're working.
14991 Changes in version 0.0.9rc1 - 2004-11-23
14992 o Bugfixes on 0.0.8.1:
14993 - Finally fix a bug that's been plaguing us for a year:
14994 With high load, circuit package window was reaching 0. Whenever
14995 we got a circuit-level sendme, we were reading a lot on each
14996 socket, but only writing out a bit. So we would eventually reach
14997 eof. This would be noticed and acted on even when there were still
14998 bytes sitting in the inbuf.
14999 - When poll() is interrupted, we shouldn't believe the revents values.
15001 o Bugfixes on 0.0.9pre6:
15002 - Fix hibernate bug that caused pre6 to be broken.
15003 - Don't keep rephist info for routers that haven't had activity for
15004 24 hours. (This matters now that clients have keys, since we track
15006 - Never call close_temp_logs while validating log options.
15007 - Fix backslash-escaping on tor.sh.in and torctl.in.
15010 - Implement weekly/monthly/daily accounting: now you specify your
15011 hibernation properties by
15012 AccountingMax N bytes|KB|MB|GB|TB
15013 AccountingStart day|week|month [day] HH:MM
15014 Defaults to "month 1 0:00".
15015 - Let bandwidth and interval config options be specified as 5 bytes,
15016 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
15017 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
15018 get back to normal.)
15019 - If your requested entry or exit node has advertised bandwidth 0,
15021 - Be more greedy about filling up relay cells -- we try reading again
15022 once we've processed the stuff we read, in case enough has arrived
15023 to fill the last cell completely.
15024 - Apply NT service patch from Osamu Fujino. Still needs more work.
15027 Changes in version 0.0.9pre6 - 2004-11-15
15028 o Bugfixes on 0.0.8.1:
15029 - Fix assert failure on malformed socks4a requests.
15030 - Use identity comparison, not nickname comparison, to choose which
15031 half of circuit-ID-space each side gets to use. This is needed
15032 because sometimes we think of a router as a nickname, and sometimes
15033 as a hex ID, and we can't predict what the other side will do.
15034 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
15035 write() call will fail and we handle it there.
15036 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
15037 and smartlist_len, which are two major profiling offenders.
15039 o Bugfixes on 0.0.9pre5:
15040 - Fix a bug in read_all that was corrupting config files on windows.
15041 - When we're raising the max number of open file descriptors to
15042 'unlimited', don't log that we just raised it to '-1'.
15043 - Include event code with events, as required by control-spec.txt.
15044 - Don't give a fingerprint when clients do --list-fingerprint:
15045 it's misleading, because it will never be the same again.
15046 - Stop using strlcpy in tor_strndup, since it was slowing us
15048 - Remove warn on startup about missing cached-directory file.
15049 - Make kill -USR1 work again.
15050 - Hibernate if we start tor during the "wait for wakeup-time" phase
15051 of an accounting interval. Log our hibernation plans better.
15052 - Authoritative dirservers now also cache their directory, so they
15053 have it on start-up.
15056 - Fetch running-routers; cache running-routers; compress
15057 running-routers; serve compressed running-routers.z
15058 - Add NSI installer script contributed by J Doe.
15059 - Commit VC6 and VC7 workspace/project files.
15060 - Commit a tor.spec for making RPM files, with help from jbash.
15061 - Add contrib/torctl.in contributed by Glenn Fink.
15062 - Implement the control-spec's SAVECONF command, to write your
15063 configuration to torrc.
15064 - Get cookie authentication for the controller closer to working.
15065 - Include control-spec.txt in the tarball.
15066 - When set_conf changes our server descriptor, upload a new copy.
15067 But don't upload it too often if there are frequent changes.
15068 - Document authentication config in man page, and document signals
15070 - Clean up confusing parts of man page and torrc.sample.
15071 - Make expand_filename handle ~ and ~username.
15072 - Use autoconf to enable largefile support where necessary. Use
15073 ftello where available, since ftell can fail at 2GB.
15074 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
15075 log more informatively.
15076 - Give a slightly more useful output for "tor -h".
15077 - Refuse application socks connections to port 0.
15078 - Check clock skew for verified servers, but allow unverified
15079 servers and clients to have any clock skew.
15080 - Break DirFetchPostPeriod into:
15081 - DirFetchPeriod for fetching full directory,
15082 - StatusFetchPeriod for fetching running-routers,
15083 - DirPostPeriod for posting server descriptor,
15084 - RendPostPeriod for posting hidden service descriptors.
15085 - Make sure the hidden service descriptors are at a random offset
15086 from each other, to hinder linkability.
15089 Changes in version 0.0.9pre5 - 2004-11-09
15090 o Bugfixes on 0.0.9pre4:
15091 - Fix a seg fault in unit tests (doesn't affect main program).
15092 - Fix an assert bug where a hidden service provider would fail if
15093 the first hop of his rendezvous circuit was down.
15094 - Hidden service operators now correctly handle version 1 style
15095 INTRODUCE1 cells (nobody generates them still, so not a critical
15097 - If do_hup fails, actually notice.
15098 - Handle more errnos from accept() without closing the listener.
15099 Some OpenBSD machines were closing their listeners because
15100 they ran out of file descriptors.
15101 - Send resolve cells to exit routers that are running a new
15102 enough version of the resolve code to work right.
15103 - Better handling of winsock includes on non-MSV win32 compilers.
15104 - Some people had wrapped their tor client/server in a script
15105 that would restart it whenever it died. This did not play well
15106 with our "shut down if your version is obsolete" code. Now people
15107 don't fetch a new directory if their local cached version is
15109 - Make our autogen.sh work on ksh as well as bash.
15112 - Hibernation: New config option "AccountingMaxKB" lets you
15113 set how many KBytes per month you want to allow your server to
15114 consume. Rather than spreading those bytes out evenly over the
15115 month, we instead hibernate for some of the month and pop up
15116 at a deterministic time, work until the bytes are consumed, then
15117 hibernate again. Config option "MonthlyAccountingStart" lets you
15118 specify which day of the month your billing cycle starts on.
15119 - Control interface: a separate program can now talk to your
15120 client/server over a socket, and get/set config options, receive
15121 notifications of circuits and streams starting/finishing/dying,
15122 bandwidth used, etc. The next step is to get some GUIs working.
15123 Let us know if you want to help out. See doc/control-spec.txt .
15124 - Ship a contrib/tor-control.py as an example script to interact
15125 with the control port.
15126 - "tor --hash-password zzyxz" will output a salted password for
15127 use in authenticating to the control interface.
15128 - New log format in config:
15129 "Log minsev[-maxsev] stdout|stderr|syslog" or
15130 "Log minsev[-maxsev] file /var/foo"
15133 - DirPolicy config option, to let people reject incoming addresses
15134 from their dirserver.
15135 - "tor --list-fingerprint" will list your identity key fingerprint
15137 - Add "pass" target for RedirectExit, to make it easier to break
15138 out of a sequence of RedirectExit rules.
15139 - Clients now generate a TLS cert too, in preparation for having
15140 them act more like real nodes.
15141 - Ship src/win32/ in the tarball, so people can use it to build.
15142 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
15144 - New "router-status" line in directory, to better bind each verified
15145 nickname to its identity key.
15146 - Deprecate unofficial config option abbreviations, and abbreviations
15147 not on the command line.
15148 - Add a pure-C tor-resolve implementation.
15149 - Use getrlimit and friends to ensure we can reach MaxConn (currently
15150 1024) file descriptors.
15152 o Code security improvements, inspired by Ilja:
15153 - Replace sprintf with snprintf. (I think they were all safe, but
15155 - Replace strcpy/strncpy with strlcpy in more places.
15156 - Avoid strcat; use snprintf or strlcat instead.
15157 - snprintf wrapper with consistent (though not C99) overflow behavior.
15160 Changes in version 0.0.9pre4 - 2004-10-17
15161 o Bugfixes on 0.0.9pre3:
15162 - If the server doesn't specify an exit policy, use the real default
15163 exit policy, not reject *:*.
15164 - Ignore fascistfirewall when uploading/downloading hidden service
15165 descriptors, since we go through Tor for those; and when using
15166 an HttpProxy, since we assume it can reach them all.
15167 - When looking for an authoritative dirserver, use only the ones
15168 configured at boot. Don't bother looking in the directory.
15169 - The rest of the fix for get_default_conf_file() on older win32.
15170 - Make 'Routerfile' config option obsolete.
15173 - New 'MyFamily nick1,...' config option for a server to
15174 specify other servers that shouldn't be used in the same circuit
15175 with it. Only believed if nick1 also specifies us.
15176 - New 'NodeFamily nick1,nick2,...' config option for a client to
15177 specify nodes that it doesn't want to use in the same circuit.
15178 - New 'Redirectexit pattern address:port' config option for a
15179 server to redirect exit connections, e.g. to a local squid.
15182 Changes in version 0.0.9pre3 - 2004-10-13
15183 o Bugfixes on 0.0.8.1:
15184 - Better torrc example lines for dirbindaddress and orbindaddress.
15185 - Improved bounds checking on parsed ints (e.g. config options and
15186 the ones we find in directories.)
15187 - Better handling of size_t vs int, so we're more robust on 64
15189 - Fix the rest of the bug where a newly started OR would appear
15190 as unverified even after we've added his fingerprint and hupped
15192 - Fix a bug from 0.0.7: when read() failed on a stream, we would
15193 close it without sending back an end. So 'connection refused'
15194 would simply be ignored and the user would get no response.
15196 o Bugfixes on 0.0.9pre2:
15197 - Serving the cached-on-disk directory to people is bad. We now
15198 provide no directory until we've fetched a fresh one.
15199 - Workaround for bug on windows where cached-directories get crlf
15201 - Make get_default_conf_file() work on older windows too.
15202 - If we write a *:* exit policy line in the descriptor, don't write
15203 any more exit policy lines.
15206 - Use only 0.0.9pre1 and later servers for resolve cells.
15207 - Make the dirservers file obsolete.
15208 - Include a dir-signing-key token in directories to tell the
15209 parsing entity which key is being used to sign.
15210 - Remove the built-in bulky default dirservers string.
15211 - New config option "Dirserver %s:%d [fingerprint]", which can be
15212 repeated as many times as needed. If no dirservers specified,
15213 default to moria1,moria2,tor26.
15214 - Make moria2 advertise a dirport of 80, so people behind firewalls
15215 will be able to get a directory.
15216 - Http proxy support
15217 - Dirservers translate requests for http://%s:%d/x to /x
15218 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
15219 be routed through this host.
15220 - Clients ask for /tor/x rather than /x for new enough dirservers.
15221 This way we can one day coexist peacefully with apache.
15222 - Clients specify a "Host: %s%d" http header, to be compatible
15223 with more proxies, and so running squid on an exit node can work.
15226 Changes in version 0.0.8.1 - 2004-10-13
15228 - Fix a seg fault that can be triggered remotely for Tor
15229 clients/servers with an open dirport.
15230 - Fix a rare assert trigger, where routerinfos for entries in
15231 our cpath would expire while we're building the path.
15232 - Fix a bug in OutboundBindAddress so it (hopefully) works.
15233 - Fix a rare seg fault for people running hidden services on
15234 intermittent connections.
15235 - Fix a bug in parsing opt keywords with objects.
15236 - Fix a stale pointer assert bug when a stream detaches and
15238 - Fix a string format vulnerability (probably not exploitable)
15239 in reporting stats locally.
15240 - Fix an assert trigger: sometimes launching circuits can fail
15241 immediately, e.g. because too many circuits have failed recently.
15242 - Fix a compile warning on 64 bit platforms.
15245 Changes in version 0.0.9pre2 - 2004-10-03
15247 - Make fetching a cached directory work for 64-bit platforms too.
15248 - Make zlib.h a required header, not an optional header.
15251 Changes in version 0.0.9pre1 - 2004-10-01
15253 - Stop using separate defaults for no-config-file and
15254 empty-config-file. Now you have to explicitly turn off SocksPort,
15255 if you don't want it open.
15256 - Fix a bug in OutboundBindAddress so it (hopefully) works.
15257 - Improve man page to mention more of the 0.0.8 features.
15258 - Fix a rare seg fault for people running hidden services on
15259 intermittent connections.
15260 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
15262 - Fix more dns related bugs: send back resolve_failed and end cells
15263 more reliably when the resolve fails, rather than closing the
15264 circuit and then trying to send the cell. Also attach dummy resolve
15265 connections to a circuit *before* calling dns_resolve(), to fix
15266 a bug where cached answers would never be sent in RESOLVED cells.
15267 - When we run out of disk space, or other log writing error, don't
15268 crash. Just stop logging to that log and continue.
15269 - We were starting to daemonize before we opened our logs, so if
15270 there were any problems opening logs, we would complain to stderr,
15271 which wouldn't work, and then mysteriously exit.
15272 - Fix a rare bug where sometimes a verified OR would connect to us
15273 before he'd uploaded his descriptor, which would cause us to
15274 assign conn->nickname as though he's unverified. Now we look through
15275 the fingerprint list to see if he's there.
15276 - Fix a rare assert trigger, where routerinfos for entries in
15277 our cpath would expire while we're building the path.
15280 - Clients can ask dirservers for /dir.z to get a compressed version
15281 of the directory. Only works for servers running 0.0.9, of course.
15282 - Make clients cache directories and use them to seed their router
15283 lists at startup. This means clients have a datadir again.
15284 - Configuration infrastructure support for warning on obsolete
15286 - Respond to content-encoding headers by trying to uncompress as
15288 - Reply with a deflated directory when a client asks for "dir.z".
15289 We could use allow-encodings instead, but allow-encodings isn't
15290 specified in HTTP 1.0.
15291 - Raise the max dns workers from 50 to 100.
15292 - Discourage people from setting their dirfetchpostperiod more often
15293 than once per minute.
15294 - Protect dirservers from overzealous descriptor uploading -- wait
15295 10 seconds after directory gets dirty, before regenerating.
15298 Changes in version 0.0.8 - 2004-08-25
15299 o Port it to SunOS 5.9 / Athena
15302 Changes in version 0.0.8rc2 - 2004-08-20
15303 o Make it compile on cygwin again.
15304 o When picking unverified routers, skip those with low uptime and/or
15305 low bandwidth, depending on what properties you care about.
15308 Changes in version 0.0.8rc1 - 2004-08-18
15309 o Changes from 0.0.7.3:
15311 - Fix assert triggers: if the other side returns an address 0.0.0.0,
15312 don't put it into the client dns cache.
15313 - If a begin failed due to exit policy, but we believe the IP address
15314 should have been allowed, switch that router to exitpolicy reject *:*
15315 until we get our next directory.
15317 - Clients choose nodes proportional to advertised bandwidth.
15318 - Avoid using nodes with low uptime as introduction points.
15319 - Handle servers with dynamic IP addresses: don't replace
15320 options->Address with the resolved one at startup, and
15321 detect our address right before we make a routerinfo each time.
15322 - 'FascistFirewall' option to pick dirservers and ORs on specific
15323 ports; plus 'FirewallPorts' config option to tell FascistFirewall
15324 which ports are open. (Defaults to 80,443)
15325 - Be more aggressive about trying to make circuits when the network
15326 has changed (e.g. when you unsuspend your laptop).
15327 - Check for time skew on http headers; report date in response to
15329 - If the entrynode config line has only one node, don't pick it as
15331 - Add strict{entry|exit}nodes config options. If set to 1, then
15332 we refuse to build circuits that don't include the specified entry
15334 - OutboundBindAddress config option, to bind to a specific
15335 IP address for outgoing connect()s.
15336 - End truncated log entries (e.g. directories) with "[truncated]".
15338 o Patches to 0.0.8preX:
15340 - Patches to compile and run on win32 again (maybe)?
15341 - Fix crash when looking for ~/.torrc with no $HOME set.
15342 - Fix a race bug in the unit tests.
15343 - Handle verified/unverified name collisions better when new
15344 routerinfo's arrive in a directory.
15345 - Sometimes routers were getting entered into the stats before
15346 we'd assigned their identity_digest. Oops.
15347 - Only pick and establish intro points after we've gotten a
15350 - AllowUnverifiedNodes config option to let circuits choose no-name
15351 routers in entry,middle,exit,introduction,rendezvous positions.
15352 Allow middle and rendezvous positions by default.
15353 - Add a man page for tor-resolve.
15356 Changes in version 0.0.7.3 - 2004-08-12
15357 o Stop dnsworkers from triggering an assert failure when you
15358 ask them to resolve the host "".
15361 Changes in version 0.0.8pre3 - 2004-08-09
15362 o Changes from 0.0.7.2:
15363 - Allow multiple ORs with same nickname in routerlist -- now when
15364 people give us one identity key for a nickname, then later
15365 another, we don't constantly complain until the first expires.
15366 - Remember used bandwidth (both in and out), and publish 15-minute
15367 snapshots for the past day into our descriptor.
15368 - You can now fetch $DIRURL/running-routers to get just the
15369 running-routers line, not the whole descriptor list. (But
15370 clients don't use this yet.)
15371 - When people mistakenly use Tor as an http proxy, point them
15372 at the tor-doc.html rather than the INSTALL.
15373 - Remove our mostly unused -- and broken -- hex_encode()
15374 function. Use base16_encode() instead. (Thanks to Timo Lindfors
15375 for pointing out this bug.)
15376 - Rotate onion keys every 12 hours, not every 2 hours, so we have
15377 fewer problems with people using the wrong key.
15378 - Change the default exit policy to reject the default edonkey,
15379 kazaa, gnutella ports.
15380 - Add replace_file() to util.[ch] to handle win32's rename().
15382 o Changes from 0.0.8preX:
15383 - Fix two bugs in saving onion keys to disk when rotating, so
15384 hopefully we'll get fewer people using old onion keys.
15385 - Fix an assert error that was making SocksPolicy not work.
15386 - Be willing to expire routers that have an open dirport -- it's
15387 just the authoritative dirservers we want to not forget.
15388 - Reject tor-resolve requests for .onion addresses early, so we
15389 don't build a whole rendezvous circuit and then fail.
15390 - When you're warning a server that he's unverified, don't cry
15391 wolf unpredictably.
15392 - Fix a race condition: don't try to extend onto a connection
15393 that's still handshaking.
15394 - For servers in clique mode, require the conn to be open before
15395 you'll choose it for your path.
15396 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
15397 end relay cell, etc.
15398 - Measure bandwidth capacity over the last 24 hours, not just 12
15399 - Bugfix: authoritative dirservers were making and signing a new
15400 directory for each client, rather than reusing the cached one.
15403 Changes in version 0.0.8pre2 - 2004-08-04
15404 o Changes from 0.0.7.2:
15406 - Check directory signature _before_ you decide whether you're
15407 you're running an obsolete version and should exit.
15408 - Check directory signature _before_ you parse the running-routers
15409 list to decide who's running or verified.
15410 - Bugfixes and features:
15411 - Check return value of fclose while writing to disk, so we don't
15412 end up with broken files when servers run out of disk space.
15413 - Log a warning if the user uses an unsafe socks variant, so people
15414 are more likely to learn about privoxy or socat.
15415 - Dirservers now include RFC1123-style dates in the HTTP headers,
15416 which one day we will use to better detect clock skew.
15418 o Changes from 0.0.8pre1:
15419 - Make it compile without warnings again on win32.
15420 - Log a warning if you're running an unverified server, to let you
15421 know you might want to get it verified.
15422 - Only pick a default nickname if you plan to be a server.
15425 Changes in version 0.0.8pre1 - 2004-07-23
15427 - Made our unit tests compile again on OpenBSD 3.5, and tor
15428 itself compile again on OpenBSD on a sparc64.
15429 - We were neglecting milliseconds when logging on win32, so
15430 everything appeared to happen at the beginning of each second.
15432 o Protocol changes:
15433 - 'Extend' relay cell payloads now include the digest of the
15434 intended next hop's identity key. Now we can verify that we're
15435 extending to the right router, and also extend to routers we
15436 hadn't heard of before.
15439 - Tor nodes can now act as relays (with an advertised ORPort)
15440 without being manually verified by the dirserver operators.
15441 - Uploaded descriptors of unverified routers are now accepted
15442 by the dirservers, and included in the directory.
15443 - Verified routers are listed by nickname in the running-routers
15444 list; unverified routers are listed as "$<fingerprint>".
15445 - We now use hash-of-identity-key in most places rather than
15446 nickname or addr:port, for improved security/flexibility.
15447 - To avoid Sybil attacks, paths still use only verified servers.
15448 But now we have a chance to play around with hybrid approaches.
15449 - Nodes track bandwidth usage to estimate capacity (not used yet).
15450 - ClientOnly option for nodes that never want to become servers.
15451 - Directory caching.
15452 - "AuthoritativeDir 1" option for the official dirservers.
15453 - Now other nodes (clients and servers) will cache the latest
15454 directory they've pulled down.
15455 - They can enable their DirPort to serve it to others.
15456 - Clients will pull down a directory from any node with an open
15457 DirPort, and check the signature/timestamp correctly.
15458 - Authoritative dirservers now fetch directories from other
15459 authdirservers, to stay better synced.
15460 - Running-routers list tells who's down also, along with noting
15461 if they're verified (listed by nickname) or unverified (listed
15463 - Allow dirservers to serve running-router list separately.
15464 This isn't used yet.
15465 - ORs connect-on-demand to other ORs
15466 - If you get an extend cell to an OR you're not connected to,
15467 connect, handshake, and forward the create cell.
15468 - The authoritative dirservers stay connected to everybody,
15469 and everybody stays connected to 0.0.7 servers, but otherwise
15470 clients/servers expire unused connections after 5 minutes.
15471 - When servers get a sigint, they delay 30 seconds (refusing new
15472 connections) then exit. A second sigint causes immediate exit.
15473 - File and name management:
15474 - Look for .torrc if no CONFDIR "torrc" is found.
15475 - If no datadir is defined, then choose, make, and secure ~/.tor
15477 - If torrc not found, exitpolicy reject *:*.
15478 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
15479 - If no nickname is defined, derive default from hostname.
15480 - Rename secret key files, e.g. identity.key -> secret_id_key,
15481 to discourage people from mailing their identity key to tor-ops.
15482 - Refuse to build a circuit before the directory has arrived --
15483 it won't work anyway, since you won't know the right onion keys
15485 - Try other dirservers immediately if the one you try is down. This
15486 should tolerate down dirservers better now.
15487 - Parse tor version numbers so we can do an is-newer-than check
15488 rather than an is-in-the-list check.
15489 - New socks command 'resolve', to let us shim gethostbyname()
15491 - A 'tor_resolve' script to access the socks resolve functionality.
15492 - A new socks-extensions.txt doc file to describe our
15493 interpretation and extensions to the socks protocols.
15494 - Add a ContactInfo option, which gets published in descriptor.
15495 - Publish OR uptime in descriptor (and thus in directory) too.
15496 - Write tor version at the top of each log file
15497 - New docs in the tarball:
15499 - Document that you should proxy your SSL traffic too.
15502 Changes in version 0.0.7.2 - 2004-07-07
15503 o A better fix for the 0.0.0.0 problem, that will hopefully
15504 eliminate the remaining related assertion failures.
15507 Changes in version 0.0.7.1 - 2004-07-04
15508 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
15509 since internally we use 0.0.0.0 to signify "not yet resolved".
15512 Changes in version 0.0.7 - 2004-06-07
15513 o Updated the man page to reflect the new features.
15516 Changes in version 0.0.7rc2 - 2004-06-06
15517 o Changes from 0.0.7rc1:
15518 - Make it build on Win32 again.
15519 o Changes from 0.0.6.2:
15520 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
15524 Changes in version 0.0.7rc1 - 2004-06-02
15526 - On sighup, we were adding another log without removing the first
15527 one. So log messages would get duplicated n times for n sighups.
15528 - Several cases of using a connection after we'd freed it. The
15529 problem was that connections that are pending resolve are in both
15530 the pending_resolve tree, and also the circuit's resolving_streams
15531 list. When you want to remove one, you must remove it from both.
15532 - Fix a double-mark-for-close where an end cell arrived for a
15533 resolving stream, and then the resolve failed.
15534 - Check directory signatures based on name of signer, not on whom
15535 we got the directory from. This will let us cache directories more
15538 - Crank up some of our constants to handle more users.
15541 Changes in version 0.0.7pre1 - 2004-06-02
15542 o Fixes for crashes and other obnoxious bugs:
15543 - Fix an epipe bug: sometimes when directory connections failed
15544 to connect, we would give them a chance to flush before closing
15546 - When we detached from a circuit because of resolvefailed, we
15547 would immediately try the same circuit twice more, and then
15548 give up on the resolve thinking we'd tried three different
15550 - Limit the number of intro circuits we'll attempt to build for a
15551 hidden service per 15-minute period.
15552 - Check recommended-software string *early*, before actually parsing
15553 the directory. Thus we can detect an obsolete version and exit,
15554 even if the new directory format doesn't parse.
15555 o Fixes for security bugs:
15556 - Remember which nodes are dirservers when you startup, and if a
15557 random OR enables his dirport, don't automatically assume he's
15558 a trusted dirserver.
15560 - Directory connections were asking the wrong poll socket to
15561 start writing, and not asking themselves to start writing.
15562 - When we detached from a circuit because we sent a begin but
15563 didn't get a connected, we would use it again the first time;
15564 but after that we would correctly switch to a different one.
15565 - Stop warning when the first onion decrypt attempt fails; they
15566 will sometimes legitimately fail now that we rotate keys.
15567 - Override unaligned-access-ok check when $host_cpu is ia64 or
15568 arm. Apparently they allow it but the kernel whines.
15569 - Dirservers try to reconnect periodically too, in case connections
15571 - Fix some memory leaks in directory servers.
15572 - Allow backslash in Win32 filenames.
15573 - Made Tor build complain-free on FreeBSD, hopefully without
15574 breaking other BSD builds. We'll see.
15576 - Doxygen markup on all functions and global variables.
15577 - Make directory functions update routerlist, not replace it. So
15578 now directory disagreements are not so critical a problem.
15579 - Remove the upper limit on number of descriptors in a dirserver's
15580 directory (not that we were anywhere close).
15581 - Allow multiple logfiles at different severity ranges.
15582 - Allow *BindAddress to specify ":port" rather than setting *Port
15583 separately. Allow multiple instances of each BindAddress config
15584 option, so you can bind to multiple interfaces if you want.
15585 - Allow multiple exit policy lines, which are processed in order.
15586 Now we don't need that huge line with all the commas in it.
15587 - Enable accept/reject policies on SOCKS connections, so you can bind
15588 to 0.0.0.0 but still control who can use your OP.
15591 Changes in version 0.0.6.2 - 2004-05-16
15592 o Our integrity-checking digest was checking only the most recent cell,
15593 not the previous cells like we'd thought.
15594 Thanks to Stefan Mark for finding the flaw!
15597 Changes in version 0.0.6.1 - 2004-05-06
15598 o Fix two bugs in our AES counter-mode implementation (this affected
15599 onion-level stream encryption, but not TLS-level). It turns
15600 out we were doing something much more akin to a 16-character
15601 polyalphabetic cipher. Oops.
15602 Thanks to Stefan Mark for finding the flaw!
15603 o Retire moria3 as a directory server, and add tor26 as a directory
15607 Changes in version 0.0.6 - 2004-05-02
15608 [version bump only]
15611 Changes in version 0.0.6rc4 - 2004-05-01
15612 o Update the built-in dirservers list to use the new directory format
15613 o Fix a rare seg fault: if a node offering a hidden service attempts
15614 to build a circuit to Alice's rendezvous point and fails before it
15615 reaches the last hop, it retries with a different circuit, but
15617 o Handle windows socket errors correctly.
15620 Changes in version 0.0.6rc3 - 2004-04-28
15621 o Don't expire non-general excess circuits (if we had enough
15622 circuits open, we were expiring rendezvous circuits -- even
15623 when they had a stream attached. oops.)
15624 o Fetch randomness from /dev/urandom better (not via fopen/fread)
15625 o Better debugging for tls errors
15626 o Some versions of openssl have an SSL_pending function that erroneously
15627 returns bytes when there is a non-application record pending.
15628 o Set Content-Type on the directory and hidserv descriptor.
15629 o Remove IVs from cipher code, since AES-ctr has none.
15630 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
15631 o We were using an array of length zero in a few places.
15632 o win32's gethostbyname can't resolve an IP to an IP.
15633 o win32's close can't close a socket.
15636 Changes in version 0.0.6rc2 - 2004-04-26
15637 o Fix a bug where we were closing tls connections intermittently.
15638 It turns out openssl keeps its errors around -- so if an error
15639 happens, and you don't ask about it, and then another openssl
15640 operation happens and succeeds, and you ask if there was an error,
15641 it tells you about the first error. Fun fun.
15642 o Fix a bug that's been lurking since 27 may 03 (!)
15643 When passing back a destroy cell, we would use the wrong circ id.
15644 'Mostly harmless', but still worth fixing.
15645 o Since we don't support truncateds much, don't bother sending them;
15646 just close the circ.
15647 o check for <machine/limits.h> so we build on NetBSD again (I hope).
15648 o don't crash if a conn that sent a begin has suddenly lost its circuit
15649 (this was quite rare).
15652 Changes in version 0.0.6rc1 - 2004-04-25
15653 o We now rotate link (tls context) keys and onion keys.
15654 o CREATE cells now include oaep padding, so you can tell
15655 if you decrypted them correctly.
15656 o Add bandwidthburst to server descriptor.
15657 o Directories now say which dirserver signed them.
15658 o Use a tor_assert macro that logs failed assertions too.
15661 Changes in version 0.0.6pre5 - 2004-04-18
15662 o changes from 0.0.6pre4:
15663 - make tor build on broken freebsd 5.2 installs
15664 - fix a failed assert when you try an intro point, get a nack, and try
15665 a second one and it works.
15666 - when alice uses a port that the hidden service doesn't accept,
15667 it now sends back an end cell (denied by exit policy). otherwise
15668 alice would just have to wait to time out.
15669 - fix another rare bug: when we had tried all the intro
15670 points for a hidden service, we fetched the descriptor
15671 again, but we left our introcirc thinking it had already
15672 sent an intro, so it kept waiting for a response...
15673 - bugfix: when you sleep your hidden-service laptop, as soon
15674 as it wakes up it tries to upload a service descriptor, but
15675 socketpair fails for some reason (localhost not up yet?).
15676 now we simply give up on that upload, and we'll try again later.
15677 i'd still like to find the bug though.
15678 - if an intro circ waiting for an ack dies before getting one, then
15680 - we were reusing stale service descriptors and refetching usable
15684 Changes in version 0.0.6pre4 - 2004-04-14
15685 o changes from 0.0.6pre3:
15686 - when bob fails to connect to the rendezvous point, and his
15687 circ didn't fail because of the rendezvous point itself, then
15688 he retries a couple of times
15689 - we expire introduction and rendezvous circs more thoroughly
15690 (sometimes they were hanging around forever)
15691 - we expire unattached rendezvous streams that have been around
15692 too long (they were sticking around forever).
15693 - fix a measly fencepost error that was crashing everybody with
15697 Changes in version 0.0.6pre3 - 2004-04-14
15698 o changes from 0.0.6pre2:
15699 - make hup work again
15700 - fix some memory leaks for dirservers
15701 - allow more skew in rendezvous descriptor timestamps, to help
15702 handle people like blanu who don't know what time it is
15703 - normal circs are 3 hops, but some rend/intro circs are 4, if
15704 the initiator doesn't get to choose the last hop
15705 - send acks for introductions, so alice can know whether to try
15707 - bob publishes intro points more correctly
15708 o changes from 0.0.5:
15709 - fix an assert trigger that's been plaguing us since the days
15710 of 0.0.2prexx (thanks weasel!)
15711 - retry stream correctly when we fail to connect because of
15712 exit-policy-reject (should try another) or can't-resolve-address
15713 (also should try another, because dns on random internet servers
15715 - when we hup a dirserver and we've *removed* a server from the
15716 approved-routers list, now we remove that server from the
15717 in-memory directories too
15720 Changes in version 0.0.6pre2 - 2004-04-08
15721 o We fixed our base32 implementation. Now it works on all architectures.
15724 Changes in version 0.0.6pre1 - 2004-04-08
15726 - Hidden services and rendezvous points are implemented. Go to
15727 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
15728 hidden services. (This only works via a socks4a proxy such as
15729 Privoxy, and currently it's quite slow.)
15732 Changes in version 0.0.5 - 2004-03-30
15733 [version bump only]
15736 Changes in version 0.0.5rc3 - 2004-03-29
15737 o Install torrc as torrc.sample -- we no longer clobber your
15739 o Re-enable recommendedversion checking (we broke it in rc2, oops)
15740 o Add in a 'notice' log level for things the operator should hear
15741 but that aren't warnings
15744 Changes in version 0.0.5rc2 - 2004-03-29
15745 o Hold socks connection open until reply is flushed (if possible)
15746 o Make exit nodes resolve IPs to IPs immediately, rather than asking
15747 the dns farm to do it.
15748 o Fix c99 aliasing warnings in rephist.c
15749 o Don't include server descriptors that are older than 24 hours in the
15751 o Give socks 'reject' replies their whole 15s to attempt to flush,
15752 rather than seeing the 60s timeout and assuming the flush had failed.
15753 o Clean automake droppings from the cvs repository
15756 Changes in version 0.0.5rc1 - 2004-03-28
15757 o Fix mangled-state bug in directory fetching (was causing sigpipes).
15758 o Only build circuits after we've fetched the directory: clients were
15759 using only the directory servers before they'd fetched a directory.
15760 This also means longer startup time; so it goes.
15761 o Fix an assert trigger where an OP would fail to handshake, and we'd
15762 expect it to have a nickname.
15763 o Work around a tsocks bug: do a socks reject when AP connection dies
15764 early, else tsocks goes into an infinite loop.
15767 Changes in version 0.0.4 - 2004-03-26
15768 o When connecting to a dirserver or OR and the network is down,
15772 Changes in version 0.0.3 - 2004-03-26
15773 o Warn and fail if server chose a nickname with illegal characters
15774 o Port to Solaris and Sparc:
15775 - include missing header fcntl.h
15776 - have autoconf find -lsocket -lnsl automatically
15777 - deal with hardware word alignment
15778 - make uname() work (solaris has a different return convention)
15779 - switch from using signal() to sigaction()
15780 o Preliminary work on reputation system:
15781 - Keep statistics on success/fail of connect attempts; they're published
15782 by kill -USR1 currently.
15783 - Add a RunTesting option to try to learn link state by creating test
15784 circuits, even when SocksPort is off.
15785 - Remove unused open circuits when there are too many.
15788 Changes in version 0.0.2 - 2004-03-19
15789 - Include strlcpy and strlcat for safer string ops
15790 - define INADDR_NONE so we compile (but still not run) on solaris
15793 Changes in version 0.0.2pre27 - 2004-03-14
15795 - Allow internal tor networks (we were rejecting internal IPs,
15796 now we allow them if they're set explicitly).
15797 - And fix a few endian issues.
15800 Changes in version 0.0.2pre26 - 2004-03-14
15802 - If a stream times out after 15s without a connected cell, don't
15803 try that circuit again: try a new one.
15804 - Retry streams at most 4 times. Then give up.
15805 - When a dirserver gets a descriptor from an unknown router, it
15806 logs its fingerprint (so the dirserver operator can choose to
15807 accept it even without mail from the server operator).
15808 - Inform unapproved servers when we reject their descriptors.
15809 - Make tor build on Windows again. It works as a client, who knows
15811 - Clearer instructions in the torrc for how to set up a server.
15812 - Be more efficient about reading fd's when our global token bucket
15813 (used for rate limiting) becomes empty.
15815 - Stop asserting that computers always go forward in time. It's
15817 - When we sent a cell (e.g. destroy) and then marked an OR connection
15818 expired, we might close it before finishing a flush if the other
15819 side isn't reading right then.
15820 - Don't allow dirservers to start if they haven't defined
15821 RecommendedVersions
15822 - We were caching transient dns failures. Oops.
15823 - Prevent servers from publishing an internal IP as their address.
15824 - Address a strcat vulnerability in circuit.c
15827 Changes in version 0.0.2pre25 - 2004-03-04
15829 - Put the OR's IP in its router descriptor, not its fqdn. That way
15830 we'll stop being stalled by gethostbyname for nodes with flaky dns,
15833 - If the user typed in an address that didn't resolve, the server
15837 Changes in version 0.0.2pre24 - 2004-03-03
15839 - Fix an assertion failure in dns.c, where we were trying to dequeue
15840 a pending dns resolve even if it wasn't pending
15841 - Fix a spurious socks5 warning about still trying to write after the
15842 connection is finished.
15843 - Hold certain marked_for_close connections open until they're finished
15844 flushing, rather than losing bytes by closing them too early.
15845 - Correctly report the reason for ending a stream
15846 - Remove some duplicate calls to connection_mark_for_close
15847 - Put switch_id and start_daemon earlier in the boot sequence, so it
15848 will actually try to chdir() to options.DataDirectory
15849 - Make 'make test' exit(1) if a test fails; fix some unit tests
15850 - Make tor fail when you use a config option it doesn't know about,
15851 rather than warn and continue.
15852 - Make --version work
15853 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
15856 Changes in version 0.0.2pre23 - 2004-02-29
15858 - Print a statement when the first circ is finished, so the user
15859 knows it's working.
15860 - If a relay cell is unrecognized at the end of the circuit,
15861 send back a destroy. (So attacks to mutate cells are more
15863 - New config option 'excludenodes' to avoid certain nodes for circuits.
15864 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
15865 so you can collect coredumps there.
15867 - Fix a bug in tls flushing where sometimes data got wedged and
15868 didn't flush until more data got sent. Hopefully this bug was
15869 a big factor in the random delays we were seeing.
15870 - Make 'connected' cells include the resolved IP, so the client
15871 dns cache actually gets populated.
15872 - Disallow changing from ORPort=0 to ORPort>0 on hup.
15873 - When we time-out on a stream and detach from the circuit, send an
15874 end cell down it first.
15875 - Only warn about an unknown router (in exitnodes, entrynodes,
15876 excludenodes) after we've fetched a directory.
15879 Changes in version 0.0.2pre22 - 2004-02-26
15881 - Servers publish less revealing uname information in descriptors.
15882 - More memory tracking and assertions, to crash more usefully when
15884 - If the default torrc isn't there, just use some default defaults.
15885 Plus provide an internal dirservers file if they don't have one.
15886 - When the user tries to use Tor as an http proxy, give them an http
15887 501 failure explaining that we're a socks proxy.
15888 - Dump a new router.desc on hup, to help confused people who change
15889 their exit policies and then wonder why router.desc doesn't reflect
15891 - Clean up the generic tor.sh init script that we ship with.
15893 - If the exit stream is pending on the resolve, and a destroy arrives,
15894 then the stream wasn't getting removed from the pending list. I
15895 think this was the one causing recent server crashes.
15896 - Use a more robust poll on OSX 10.3, since their poll is flaky.
15897 - When it couldn't resolve any dirservers, it was useless from then on.
15898 Now it reloads the RouterFile (or default dirservers) if it has no
15900 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
15901 many users don't even *have* a /usr/local/sbin/.
15904 Changes in version 0.0.2pre21 - 2004-02-18
15906 - There's a ChangeLog file that actually reflects the changelog.
15907 - There's a 'torify' wrapper script, with an accompanying
15908 tor-tsocks.conf, that simplifies the process of using tsocks for
15909 tor. It even has a man page.
15910 - The tor binary gets installed to sbin rather than bin now.
15911 - Retry streams where the connected cell hasn't arrived in 15 seconds
15912 - Clean up exit policy handling -- get the default out of the torrc,
15913 so we can update it without forcing each server operator to fix
15915 - Allow imaps and pop3s in default exit policy
15917 - Prevent picking middleman nodes as the last node in the circuit
15920 Changes in version 0.0.2pre20 - 2004-01-30
15922 - We now have a deb package, and it's in debian unstable. Go to
15923 it, apt-getters. :)
15924 - I've split the TotalBandwidth option into BandwidthRate (how many
15925 bytes per second you want to allow, long-term) and
15926 BandwidthBurst (how many bytes you will allow at once before the cap
15927 kicks in). This better token bucket approach lets you, say, set
15928 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
15929 performance while not exceeding your monthly bandwidth quota.
15930 - Push out a tls record's worth of data once you've got it, rather
15931 than waiting until you've read everything waiting to be read. This
15932 may improve performance by pipelining better. We'll see.
15933 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
15934 from failed circuits (if they haven't been connected yet) and attach
15936 - Expire old streams that haven't managed to connect. Some day we'll
15937 have them reattach to new circuits instead.
15940 - Fix several memory leaks that were causing servers to become bloated
15942 - Fix a few very rare assert triggers. A few more remain.
15943 - Setuid to User _before_ complaining about running as root.
15946 Changes in version 0.0.2pre19 - 2004-01-07
15948 - Fix deadlock condition in dns farm. We were telling a child to die by
15949 closing the parent's file descriptor to him. But newer children were
15950 inheriting the open file descriptor from the parent, and since they
15951 weren't closing it, the socket never closed, so the child never read
15952 eof, so he never knew to exit. Similarly, dns workers were holding
15953 open other sockets, leading to all sorts of chaos.
15954 - New cleaner daemon() code for forking and backgrounding.
15955 - If you log to a file, it now prints an entry at the top of the
15956 logfile so you know it's working.
15957 - The onionskin challenge length was 30 bytes longer than necessary.
15958 - Started to patch up the spec so it's not quite so out of date.
15961 Changes in version 0.0.2pre18 - 2004-01-02
15963 - Fix endian issues with the 'integrity' field in the relay header.
15964 - Fix a potential bug where connections in state
15965 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
15968 Changes in version 0.0.2pre17 - 2003-12-30
15970 - Made --debuglogfile (or any second log file, actually) work.
15971 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
15972 adversary could force us into an infinite loop.
15975 - Each onionskin handshake now includes a hash of the computed key,
15976 to prove the server's identity and help perfect forward secrecy.
15977 - Changed cell size from 256 to 512 bytes (working toward compatibility
15979 - Changed cell length to 2 bytes, and moved it to the relay header.
15980 - Implemented end-to-end integrity checking for the payloads of
15982 - Separated streamid from 'recognized' (otherwise circuits will get
15983 messed up when we try to have streams exit from the middle). We
15984 use the integrity-checking to confirm that a cell is addressed to
15986 - Randomize the initial circid and streamid values, so an adversary who
15987 breaks into a node can't learn how many circuits or streams have
15991 Changes in version 0.0.2pre16 - 2003-12-14
15993 - Fixed a bug that made HUP trigger an assert
15994 - Fixed a bug where a circuit that immediately failed wasn't being
15995 counted as a failed circuit in counting retries.
15998 - Now we close the circuit when we get a truncated cell: otherwise we're
15999 open to an anonymity attack where a bad node in the path truncates
16000 the circuit and then we open streams at him.
16001 - Add port ranges to exit policies
16002 - Add a conservative default exit policy
16003 - Warn if you're running tor as root
16004 - on HUP, retry OR connections and close/rebind listeners
16005 - options.EntryNodes: try these nodes first when picking the first node
16006 - options.ExitNodes: if your best choices happen to include any of
16007 your preferred exit nodes, you choose among just those preferred
16009 - options.ExcludedNodes: nodes that are never picked in path building
16012 Changes in version 0.0.2pre15 - 2003-12-03
16013 o Robustness and bugfixes:
16014 - Sometimes clients would cache incorrect DNS resolves, which would
16015 really screw things up.
16016 - An OP that goes offline would slowly leak all its sockets and stop
16018 - A wide variety of bugfixes in exit node selection, exit policy
16019 handling, and processing pending streams when a new circuit is
16021 - Pick nodes for a path only from those the directory says are up
16022 - Choose randomly from all running dirservers, not always the first one
16023 - Increase allowed http header size for directory fetch.
16024 - Stop writing to stderr (if we're daemonized it will be closed).
16025 - Enable -g always, so cores will be more useful to me.
16026 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
16029 - Wrote a man page. It lists commonly used options.
16032 - Change default loglevel to warn.
16033 - Make PidFile default to null rather than littering in your CWD.
16034 - OnionRouter config option is now obsolete. Instead it just checks
16036 - Moved to a single unified torrc file for both clients and servers.
16039 Changes in version 0.0.2pre14 - 2003-11-29
16040 o Robustness and bugfixes:
16041 - Force the admin to make the DataDirectory himself
16042 - to get ownership/permissions right
16043 - so clients no longer make a DataDirectory and then never use it
16044 - fix bug where a client who was offline for 45 minutes would never
16045 pull down a directory again
16046 - fix (or at least hide really well) the dns assert bug that was
16047 causing server crashes
16048 - warnings and improved robustness wrt clockskew for certs
16049 - use the native daemon(3) to daemonize, when available
16050 - exit if bind() fails
16051 - exit if neither socksport nor orport is defined
16052 - include our own tor_timegm (Win32 doesn't have its own)
16053 - bugfix for win32 with lots of connections
16054 - fix minor bias in PRNG
16055 - make dirserver more robust to corrupt cached directory
16058 - Wrote the design document (woo)
16060 o Circuit building and exit policies:
16061 - Circuits no longer try to use nodes that the directory has told them
16063 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
16064 bitcounts (18.0.0.0/8).
16065 - Make AP connections standby for a circuit if no suitable circuit
16066 exists, rather than failing
16067 - Circuits choose exit node based on addr/port, exit policies, and
16068 which AP connections are standing by
16069 - Bump min pathlen from 2 to 3
16070 - Relay end cells have a payload to describe why the stream ended.
16071 - If the stream failed because of exit policy, try again with a new
16073 - Clients have a dns cache to remember resolved addresses.
16074 - Notice more quickly when we have no working circuits
16077 - APPort is now called SocksPort
16078 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
16080 - RecommendedVersions is now a config variable rather than
16081 hardcoded (for dirservers)
16082 - Reloads config on HUP
16083 - Usage info on -h or --help
16084 - If you set User and Group config vars, it'll setu/gid to them.
16087 Changes in version 0.0.2pre13 - 2003-10-19
16088 o General stability:
16089 - SSL_write no longer fails when it returns WANTWRITE and the number
16090 of bytes in the buf has changed by the next SSL_write call.
16091 - Fix segfault fetching directory when network is down
16092 - Fix a variety of minor memory leaks
16093 - Dirservers reload the fingerprints file on HUP, so I don't have
16094 to take down the network when I approve a new router
16095 - Default server config file has explicit Address line to specify fqdn
16098 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
16099 - Make listener connections not ever alloc bufs
16101 o Autoconf improvements:
16102 - don't clobber an external CFLAGS in ./configure
16103 - Make install now works
16104 - create var/lib/tor on make install
16105 - autocreate a tor.sh initscript to help distribs
16106 - autocreate the torrc and sample-server-torrc with correct paths
16108 o Log files and Daemonizing now work:
16109 - If --DebugLogFile is specified, log to it at -l debug
16110 - If --LogFile is specified, use it instead of commandline
16111 - If --RunAsDaemon is set, tor forks and backgrounds on startup